- #Preflight phoenix upgrade
- #Preflight phoenix software
- #Preflight phoenix download
- #Preflight phoenix free
- #Preflight phoenix windows
#Preflight phoenix software
Ensure that all Druva processes are whitelisted in any antivirus software running on the virtual machine.
#Preflight phoenix free
The VM must have at least 1 GB of free space on the boot partition.The VM must have VMware tools installed on it.The VM must be running for the prerequisite check to work.If the user does not have sudo privileges or does not have the NOPASSWD: ALL tag enabled in the sudoers file, the command will generate the following output and will prompt for a password. If the user has sudo privileges and the NOPASSWD: ALL tag has been enabled in the sudoers file, the command will generate the following output without prompting for a password. Login to the Linux machine using the user account that needs to be tested.Įxecute the sudo -l command. Where username, is the username that can execute all commands without prompting for a password. Edit the sudoers file and ensure that the non-root user has the following entry at the end:
#Preflight phoenix windows
See disabling UAC on Windows server for more information.Ī non-root user must have sudo rights and must have the NOPASSWD: ALL tag enabled in the sudoers file.
#Preflight phoenix download
If the VM is unable to connect to Druva download portal and download the DR Failover Checks - Guest OS executables, ensure that: The DR Failover Checks - Guest OS may not execute at all if the VM cannot connect to Druva download portal at to download the DR Failover Checks - Guest OS executables while the VM backup is in progress.
#Preflight phoenix upgrade
Upgrade the VMware backup proxy to the latest version, and ensure that the first VM backup after the proxy upgrade is successful.
![preflight phoenix preflight phoenix](https://images.freeimages.com/images/large-previews/b63/landing-in-phoenix-1197551.jpg)
The recommended EC2 instance size for the Phoenix AWS proxy is c5.2xlarge.Note: Each DR proxy can run three DR restore jobs concurrently. Druva recommends that you deploy at least two DR proxies in separate availability zones for high availability.The DR proxy deployment takes less than 10 minutes. The DR proxy is deployed using the AWS CloudFormation template. The Phoenix AWS proxy runs the Phoenix Disaster Recovery service and is responsible for orchestrating the DR Restore, DR failback, and DR failover. Phoenix AWS proxy, also referred to as DR proxy, is an EC2 instance that runs in the customer’s AWS account.