Skip to main content
Druva Documentation

Reconfigure virtual machines configured for backup

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Overview

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
  • Phoenix uses the backup proxy pool you have selected
  • The server is listed under the Resources tab of the administrative group you choose for a virtual machine

Note: You cannot change the storage assigned to a virtual machine

Prerequisites

Create backup policy, backup proxy pool, and administrative group before reconfiguring virtual machines for backup. 

To reconfigure virtual machines from the listing page

  1. On the Phoenix Management Console menu bar, click All Organizations, and then select the required organization from the drop-down list.
  2. On the Phoenix Management Console menu bar, click Protect > VMware. List of all the registered hypervisors appear. The servers are listed using their IP address or domain name.
  3. Select the desired vCenter Server or ESXi Hypervisor, which hosts the virtual machines you want to reconfigure. The hypervisor page appears that lists all virtual machines it hosts. You can see the following options in the hypervisor page: 
    • All Virtual Machines
    • Configured Virtual Machines
    • Backup Proxy Pools
    • Auto Configuration
  4. Select the Configured Virtual Machines tab.
  5. Under Configured Virtual Machines tab, search and select the virtual machines that you want to reconfigure.
  6. Click Reconfigure VMs from the bottom of the page. You get the following options:
    • Change Backup Policy
      If you select this option, you see the Change Backup Policy dialog that lets you select a different backup policy. In addition, the dialog displays the backup policy settings, such as backup schedule, ignore backup duration for first backup, automatic retry, retention, auto-enable CBT, enable VMware tools quiescing, and enable application-aware processing. For more details on the backup policy options, see: Manage Backup Policy.
      Select a new backup policy and click Save
    • Change Administrative Group
      If you select this option, Change Administrative Group dialog appears that lets you select a different group. Select a different group and click Save
    • Change Backup Proxy Pool
      If you select this option, Change Backup Proxy Pool dialog appears that lets you select a different backup proxy pool. Select a different backup proxy pool and click Save
      For more information on backup proxy pool and load balancing, see Backup Proxy Load Balancing

To reconfigure a virtual machine from the virtual machine page

  1. On the Phoenix Management Console menu bar, click All Organizations, and then select the required organization from the drop-down list.
  2. On the Phoenix Management Console menu bar, click Protect > VMware. List of all the registered hypervisors appear. The servers are listed using their IP address or domain name.
  3. Select the desired vCenter Server or ESXi Hypervisor, which hosts the virtual machines you want to reconfigure. The hypervisor page appears that lists all virtual machines it hosts. You can see the following options on the hypervisor page: 
    • All Virtual Machines
    • Configured Virtual Machines
    • Backup Proxy Pools
    • Auto Configuration
  4. Select the Configured Virtual Machines tab.
  5. Under Configured Virtual Machines tab, search and click the virtual machine that you want to reconfigure.
    The virtual machine page appears. 
  6. In the virtual machine page, click Reconfigure VM for Backup. The Reconfigure VM for backup wizard appears.
  7. In the Backup Settings section of the configuration wizard, provide the following options:
    Field Description
    Administrative Group Phoenix lets you create a group for better management of resources. For example, you can create an administrative group for all virtual machines with Linux as the guest operating system. Later, you can directly access all servers using the administrative group page. 

    In this field, you can:
    • Choose an existing administrative group, or
    • You can create a new administrative group
    If you click Create New GroupCreate New Administrative Group window appears. Provide a name and description for the administrative group. For example,
    • In the Name field, enter Linux Virtual Machines
    • In the Description field, enter an administrative group for all virtual machines with Linux Guest OS.
      After you provide a name and description for the administrative group, click Save. After you click Save, the configuration wizard reappears with the group you created as an option for you to select. 
    Backup Policy The Backup Policy in Phoenix specifies: Backup Schedule
    Settings in the backup schedule are:
    • The day, date, and time when Phoenix should trigger a backup
    • The backup duration that specifies for how long Phoenix should run a backup job 
    • The bandwidth available for backup job
    Ignore backup duration for the first backup
    Defines whether Phoenix should ignore backup duration for the first job. Typically, a lot of data is scanned and uploaded in the first job, and it lasts longer than the subsequent incremental backup jobs. The default and recommended setting for this option is Yes.

    Automatic Retry
    Lets you specify the behavior if a backup job fails. Phoenix can retry triggering a backup job if a backup fails for an issue like network failure. You can choose the number of retries and specify the interval after which Phoenix retries triggering the backup job.  Retention
    Specifies the period for which Phoenix retains a snapshot in the cloud.

    Auto-enable CBT
    Phoenix uses VMware Changed Block Tracking (CBT) capabilities to optimize data scanning. Phoenix can attempt to turn on CBT if the Auto-enable CBT setting is enabled. Yes is the default and recommended setting. 

    Enable VMware tools quiescing
    VMware tools quiescing brings a virtual machine to a backup ready state. Tools quiescing avoids unnecessary errors when Phoenix creates a snapshot. Phoenix can attempt to turn on VMware tools quiescing if the setting is enabled. Yes is the default and recommended setting. 

    Enable application-aware processing
    Phoenix provides you an option to run application-aware backups. You can use this feature to backup and restore data that an application generates, as long as Phoenix can detect the application running inside the guest OS. At the moment, Phoenix provides SQL Server aware backups. When you enable this setting, Phoenix takes a backup of the SQL Server instances on the virtual machine. In addition, Phoenix provides you an option to run transaction log backups of the databases on the SQL Server instances. For more information on how Phoenix runs SQL Server aware backups, see Workflow of application-aware backups on VMware virtual machines.

    You can either select an already created backup policy or create a new backup policy using the Create New button. 

    If you click the Create New button, the Create New Backup Policy: VMware wizard appears with the following tabs:

    Summary
    Provide a name and description for the backup policy. For example,
    • Name: Backup policy for SQL VMs.
    • Description: Backup policy for VMware virtual machines on which we want to run SQL Server aware backups. 
    Backup Schedule
    Lets you specify the backup schedule, ignore backup duration for the first backup, and automatic retry settings described above.  Retention
    Lets you specify the period for which you want Phoenix to retain snapshots for virtual machines.  VMware Settings
    Lets you enable following VMware functionalities
    • Auto-enable CBT
    • VMware Tools Quiescing
    • Application-aware processing
      At the moment, Phoenix supports the backup of SQL Server databases. When you enable application-aware processing, Phoenix runs a backup of SQL Server instances on the virtual machine. In addition:
      • You get an option to enable transaction log backups and specify an interval for the log backups.
      • You get an option to specify the bandwidth for a log backup. 
        log_backup_VMware_policy.png
        Here, if you specify an interval of 10 minutes in the transaction log backup frequency field, and the full virtual machine SQL Server aware backup got completed at 12:00 PM, the first log backup happens at 12:00 PM. If the first log backup completes at 12:05 PM, the next log backup starts according to the schedule at 12:10 PM. If the log backup runs until 12:45 PM, the next log backup starts immediately as soon as the current log backup ends.  
    After you select your options in the Backup Settings section, click Next
  8. You can leave the Backup Content section empty to include all virtual disks for backup.
    Or, in the Backup Content section, enter the virtual disks that you don't want Phoenix to backup.  Phoenix does not list the virtual disks automatically. Manually enter the virtual disks you want to exclude. To exclude virtual disks, provide:
    • Entire path to the virtual disk location if you want to exclude a specific virtual disk. For example [datastore]/virtual_machine_name/folder/virtual_disk.vmdk

      Note: To exclude a virtual disk, Phoenix recommends that you copy the virtual disk name or path from the vSphere web client. For more information, see VMware backup and restore FAQs.

    • A wildcard character with a string. For example, enter *test* to exclude virtual disks that contain the string test in the path of the virtual disk.  For more information on how to use the wildcard character, see VMware backup and restore FAQs
  9. In the Backup Proxy Pool section of the configuration wizard, select a backup proxy pool. A backup proxy pool is a collection of backup proxies deployed in the vCenter or ESXi server. Phoenix provides a default backup proxy pool, and when you deploy a backup proxy to the hypervisor, it is added to the default backup proxy pool. If multiple backup proxies are available under a pool, Phoenix optimizes backup jobs by concurrently scanning and uploading data using different backup proxies available. 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
  10. After selecting a backup proxy pool, click Finish

The virtual machine is reconfigured for backup and is listed under the Configured Virtual Machines tab. The reconfigured virtual machine is backed up based on the schedule defined in the backup policy. You can click the virtual machine name and see its details. 

If you reconfigure an individual virtual machine created in a vCenter folder that is has a configuration rule applied to it, then the folder is added to the rule's exclusion list. 

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