Skip to main content



How can we help you?


Druva Documentation

Manually configure virtual machines for backup

Heads up!

We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.

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


Before you begin

  • Decide to use the default or create a new administrative group.
    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.
    See, Manage administrative groups.

  • Decide to use the default or create a new backup policy.
    A backup policy is a set of rules that defines the schedule for automatic backups that occur on virtual machines configured for backup.
    See, Manage backup policy.

  • Review the prerequisites for configuring virtual machines for backup.

  • The discovered virtual machine list is refreshed every 24 hours. You can also manually refresh the list by clicking the Refresh button. 

  • Ensure that you provide the VM credentials to Druva when you configure application-aware backups on virtual machines. See Manage credentials for VMware servers for details.

  • If you want to store your backups in local storage, configure the CloudCache. For more information, see Configure CloudCache
  • If you want to restore the virtual machines instantly, map the virtual machines to CloudCache (Linux  version) and enable Instant Restore for the selected virtual machines.
  • Migrate to production job for a VM cannot reuse the staging datastore used for the instant restore job of that VM. If you want to migrate a virtual machine to production, ensure you have another datastore on the same or different ESXi host, depending on whether you are migrating to the same or alternate host.


  1. Log in to the Management Console
  2. From the top menu bar, select your organization if organizations are enabled. 
  3. Click Protect > VMware
    The All vCenters/ESXi Hosts page appears that lists all the registered vCenters/Hypervisors. 
  4. You can either select the registered vCenter/ESXi host from the card view or list view or select it from the vCenter/ESXi host list in the left navigation pane.
  5. Select the virtual machines you want to configure.
    For ease of operation, you can filter the virtual machines according to their configuration status and select the ones with Not Configured status.
  6. Click Configure for Backup.
  7. In the Configure for Backup page, enter the following details: 

Field Description
Administrative Group

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.

You can either:

Choose an existing or the default administrative group. 

Create a new administrative group. See Manage administrative groups.

Backup settings

Cloud Storage: Region where you want to store the backups of backup recovery points. You cannot change storage later.

Backup Policy:
You can:

Choose an existing or the default backup policy.

From here, you can review the following information specified in the backup policy :

Backup Details

  • Ignore backup duration for the first backup
    Defines whether Druva 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.
  • Retention
    The period for which Druva retains a recovery point in the cloud.
  • Auto-enable CBT
  • Druva uses VMware Changed Block Tracking (CBT) capabilities to optimize data scanning. Druva can attempt to turn on CBT if the Auto-enable CBT setting is enabled. Yes is the default and recommended setting. See, Changed Block Tracking. 
  • Enable VMware tools quiecing
    VMware tools quiescing brings a virtual machine to a backup ready state. Druva can attempt to turn on VMware tools quiescing if the setting is enabled. Yes is the default and recommended setting. See, VMware Tools Quiescing.
  • Enable application-aware processing
    Druva 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 Druva can detect the application running inside the guest OS. At the moment, Druva provides SQL Server aware backups. However, leave this field disabled if you don't plan on running an application-aware backup at the moment.
    For more information, see:
  • Transaction log backup frequency
    Interval for the log backups.
  • Local Storage 

    • Map to CloudCache: Select the option to store the backups in local storage configured as part of the CloudCache. To use this option you must first configure the CloudCache.  For more information, see Configure CloudCache
    • CloudCache: Select the CloudCache you want to use. You must select a CloudCache that belongs to the same data center. 
    • If you want to restore the virtual machine instantly, select a Linux CloudCache.
      If you dissociate the virtual machine from CloudCache, the subsequent backups are directly stored to the Druva Cloud and instant restoration of the virtual machine is not possible.
    • Retain backups for: Select the number of days you want to retain the backups in the local storage. 
  • Instant restore: Select this option to instantly restore virtual machines from CloudCache. If this option is disabled, map the selected virtual machine to Linux CloudCache.


  • After enabling instant restore for a VM, the next backup will be a full backup.

  • If you switch to Windows storage after enabling Instant Restore, the Instant Restore is disabled for the selected VMs.

Backup Content

You can leave the Backup Content field empty to include all virtual disks for backup.

Or, enter the virtual disks that you don't want Druva to backup.  Druva does not list the virtual disks automatically. Manually enter the virtual disks you want to exclude. 

To exclude virtual disks, provide:

The 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
To exclude a virtual disk, Druva recommends that you copy the virtual disk name or path from the vSphere web client. For more information, see VMware backup and restore FAQs

Note: We recommend you to copy the path to the Notepad to remove any formatting or special characters and ensure that there is no space at the beginning and at the end. Space is important between [Datastore] and the name.

A wildcard 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.

Backup Proxy Pool

You can select the default backup proxy pool, or you can select a user-created pool. 

The backup of virtual machines mapped to this pool is triggered in this time zone.

For more details on backup proxy pools, see Backup Proxy Load Balancing.
  1. Click Save. The status of the virtual machines is updated to Configured and they are also listed on the Configured VMs page.



  • MS-SQL servers that are available for app-aware backups can be identified with App_aware_icon.pngicon next to them after the first backup is run. 
  • Makes sure to avoid Backup Window overlap by changing the scheduled start time, if the same VM machine is configured for SQL backups, that is, the SQL backups and VMware backups of the same VM should have a different start time.
  • To avoid backup errors, SQL backups and VMware backups should not coincide for the same server.
  • Indicates VMs that are configured for instant restore. 

  • Indicates VMs that are configured for CloudCache but not for instant restore.

  1. You can click on the configured machine to view its details.

Note: When creating a virtual machine, you can add a Virtual Trusted Platform Module (vTPM) to provide enhanced security to the guest operating system. You must create a key provider before you can add a vTPM.
You can back up these vTPM-enabled VMs. However, v-TPM settings will not be copied in the recovery points during backup. Therefore, whenever you are doing a restore of these VMs, you will have to manually add the vTPM settings later.

  • Was this article helpful?