Skip to main content

How can we help you?

Druva Documentation

Restore prerequisites and considerations

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

 

Considerations for restoring a virtual machine

  • If you are a group administrator, you can only restore data to a virtual machine that belongs to an administrative group that you manage. Cloud administrators and data protection officers can restore virtual machines across groups. 
  • In the event of a network connection failure at the time of restores, backup proxies attempt to connect to Druva Cloud. After the restoration of connectivity, backup proxies restart restores from the state in which they were interrupted. 
  • If you restart or reboot a Backup proxy during a restore, the restore operation resumes after the proxy machine is up and running.
  • The Restore Points follow the Backup proxy pool time zone.
  • Druva supports restore of virtual machines to a different Prism Element/Cluster, as well as the source Prism Element/Cluster associated with an installed Backup proxy.
  • During an ongoing restore or backup, if the target VM (during original restore) or the VM being backed up is restarted then the job may fail.

Firewall rules for data protection of Nutanix AHV virtual machines

If a firewall is configured in your environment, ensure that the following patterns are allowed for seamless backups and restores.

*s3.amazonaws.com/*

s3-*.amazonaws.com

s3*.*.amazonaws.com

*.druva.com

 

Considerations for full virtual machine restore to the original location

  • If the backup is running for a VM and a restore to the original location is triggered for the same VM, then you have the option to either cancel the current backup job or trigger the restore later.
  • If restore is running for a VM and backup is triggered for the same VM, then the backup will be queued until the restore is complete.
  • Two restores to the original location cannot run in parallel on the same virtual machine.
  • If the virtual machine has new vDisks attached at the time of restore and if they were not backed up, then all those vDisks will be detached from the virtual machine.
  • If the virtual machine has CD-ROM attached during restore, then it will not be detached whether or not it was present during backup.
  • Only the data on the virtual machine is restored. The VM configuration remains the same as what it was before the restore.
  • The boot configuration is preserved during Original restore, only if: 
    • The VM uses UEFI boot.
    • The VM does not use UEFI boot and the Boot device type is Disk.
  • Boot configuration is not preserved in all other cases, and you must configure it manually after the restore.
  • Before performing the original restore, a snapshot of the VM is taken. In the worst case this snapshot can be used to recover the original VM. however this needs to be done manually using the Nutanix APIs. The snapshot name is "druva-org-<restore_job_id>".
  • In the case of a virtual machine restored to the original location, Druva restores the virtual machine to its original network configuration. However, for a virtual disk restore or restore to an alternate location, Druva restores the virtual machine to the network configuration selected while triggering the job.
  • Original restore reserves the power state after the restore, meaning it will power on only if it was powered on before the restore; otherwise not.

Considerations for full virtual machine restore to the alternate location

  • If the backup is running for the VM and alternate restore is triggered for the same VM, then they can run in parallel.
  • If an alternate restore is running for the VM and a backup is triggered for the same VM, they can run in parallel.
  • Two restores to alternate locations can be triggered from the same virtual machine. 
  • If the virtual machine has CD-ROM attached during backup, it will be attached to the VM after the restore.
  • The virtual machine parameters like memory and CPU remain the same as in the original virtual machine even after it is restored to an alternate location. 
  • The boot configuration is preserved during Alternate restore, only if: 
    • The VM uses UEFI boot.
    • The VM does not use UEFI boot and the Boot device type is Disk.
  • Boot configuration is not preserved in all other cases, and you must configure it manually after the restore.
  • After an alternate restore, the virtual machine is always powered off. You must manually power on the virtual machine.
  • Druva creates a new virtual machine with the same configuration as the original VM.

Considerations for a disk restore

  • If a backup is running for a VM and a disk restore is triggered for the same VM, then they can run in parallel.
  • If a disk restore is running for a VM and a backup is triggered for the same VM, then they can run in parallel.
  • Two Disk restore requests can run in parallel on the same virtual machine.
  • Druva creates a new virtual machine with the same configuration as the original VM and associates the virtual disk files that you selected to it.
    1. One of the Networks in the Selected cluster is attached to the restored VM.
    2. The boot configuration is not added for disk restore, User must configure it manually after the restore.
    3.  If the virtual machine has CD-ROM attached during backup, it will be attached to the VM after the restore.
    4. The virtual machine parameters like memory and CPU remain the same as in the original virtual machine even after the restore. 
  • If a Disk restore fails, then the virtual machine is not created.
  • After a Disk restore, the virtual machine is always powered off. You must manually power on the virtual machine.