Druva Phoenix lets you reconfigure your virtual machines if:
- You want to change backup policy
- Change administrative group
- Change backup proxy pool
After you reconfigure a virtual machine
- Virtual machine is backed up as per the schedule defined in the backup policy associated with it
- Backup snapshots are retained as per the retention settings specified in the backup policy
- Druva Phoenix uses the backup proxy pool you have selected
Note: You cannot change the storage assigned to a virtual machine
Create backup policy, backup proxy pool, and administrative group before reconfiguring virtual machines for backup.
- Log in to the Phoenix Management Console.
- Under Product & Services > Phoenix, click VMware.
- Select your organization.
- The All vCenters/ESXi Hosts page appears that lists all the registered vCenter/hypervisors.
- You can either select the registered vCenter/hypervisors from the list or select it from the vCenter/ESXi host list in the left navigation pane.
- In the navigation pane, click Configured VMs.
- Click on the virtual machine you want to reconfigure.
- Click the more options button and click Reconfigure.
- In the Reconfigure of backup page update the required settings.
Administrative groups are formed to simplify server management. It is a logical categorization of servers and virtual machines that share similar attributes. Servers can be grouped based on similar attributes like server type, server location, and operating system.
Cloud Storage: Region where you want to store the snapshots. You cannot change storage later.
If you want to configure MS-SQL server for application-aware backups select a policy accordingly.
From here, you can review the following information specified in the backup policy :
You can leave the Backup Content section empty to include all virtual disks for backup.
|Backup Proxy Pool||You can select the default backup proxy pool, or you can select a user-created pool. For more details on backup proxy pools, see Backup Proxy Load Balancing.|
Note: If a virtual machine was attached to a administrative group for which the storage was different than the new administrative group, the reconfiguration fails. For example, if a virtual machine was attached to a administrative group with storage selected as US-West. If you are attaching your virtual machine to a new administrative group with storage selected as US-East, your reconfiguration will fail with an error message.
If you try to reconfigure your virtual machines using rules, reconfiguration still fails if the administrative group specified in the rule uses a different storage. For example, you add virtual machines VM1 and VM2 under folder VMFD1 in a vCenter setup. You attach VM1 and VM2 to the administrative group G1 that uses storage US-West. Later, you create an auto-configuration rule R1 for folder VMFD1 in which you specify administrative group G2 that uses storage US-East. In the rule R1, you disable Exclude already configured VMs ensuring auto-configuration of all virtual machines in the folder when the rule is applied.
When the rule R1 to folder VMFD1 is applied:
- VM1 and VM2 remain attached to the administrative group G1 using US-West since the reconfiguration fails due to the different storage
- You do not see an error message as in manual reconfiguration