Considerations and Limitations

Before you restore a VM from a backup, consider the following:

  • You can restore a VM from a backup that has at least one successfully created restore point.
  • If you back up a VM with vRDM disks, Veeam Backup & Replication converts the disks into VMDK files. Thus, when you restore a VM with a vRDM disk, Veeam Backup & Replication restores this disk as a VMDK file. If you want to preserve the vRDM format for restored disks, use Quick Rollback. For more information, see Quick Rollback.
  • After you restore a VM, the hard disk may appear with a different Hard drive number in the Virtual Hardware settings in the vCenter console. VMware assigns the hard disk number depending on the order in which each disk is restored. However, the .VMDK disk file remains associated with the correct SCSI, IDE or SATA disk ID. The restored VM operates normally.
  • If you want to scan VM data for viruses, check the secure restore requirements and limitations.
  • If you want to run an executable script for a VM, check the staged restore requirements and limitations.
  • [For restore to original location] If the original VM has vSphere Fault Tolerance (FT) enabled, you need to reenable FT manually after restore.
  • When you restore a VM, consider the Virtual Hardware version compatibility. For more information, see this VMware KB article.

Page updated 1/15/2026

Page content applies to build 13.0.1.1071