• Druva automatically identifies the Backup proxy within the default pool that will run the restore request based on a load balancing algorithm.
• The restore request is queued if the identified Backup proxy is busy processing other restore jobs. The request is reinitiated when the Backup proxy is available.

Step 3

For full virtual machine restores to the original location, Druva:

• Uses the same storage container that the original VM uses to store its vDisks. Druva then creates a volume group using the vDisks that need to be restored.
• Downloads the data from Druva Cloud and writes to the newly created virtual disks (vDisks) using an iSCSI connection.
• Detaches all the existing disks (except CDROM) in the VM and attaches the restored ones from the above volume group for original restore.

The network settings remain unchanged.
For full virtual machine restores to an alternate location, Druva:

• Uses the storage container specified in the restore settings to create a volume group for the vDisks to be restored.
• Downloads the data from Druva Cloud and writes to the newly created virtual disks (vDisks) using an iSCSI connection.
• Creates a new VM and attaches the restored vDisks to it.

You can select the network before submitting the restore job.
For disk restores, Druva:

• Creates a new virtual machine with the same configuration as the original virtual machine at the specific location with the following name Phoenix-Restored-VM-<Original_VM_Name>-<Job_Id>

• Uses the first network in the list of networks returned by Prism Element or Prism Central and assigns it to the newly created VM.

• Druva creates a new VM when full VM restores to an alternate location, and disk restores are successful.
• Druva alters the vDisks and updates the original VM if a full VM restore to the original location is successful
• No VMs are created or updated if the restores fail.