Considerations and Limitations

Before you restore VM guest OS files, check the following considerations and limitations.


Restore changes functionality is included in the Veeam Universal License. When using a legacy socket-based license, the Enterprise or Enterprise Plus editions of Veeam Backup & Replication are required.

Infrastructure Components

  • You can restore files from basic disks and dynamic disks (including simple, mirrored and striped volumes).
  • [For restore to another VM, to original location, or permissions only] If the target VM uses the gMSA account and you restore files from a backup, you must also install this account on the mount server associated with the backup repository on which the backup resides. If you restore from a replica, you must install the gMSA account on the backup server.
  • [For restore to original location] VM guest OS must be accessible from the backup server over the network, or over PowerShell Direct (for VMs that reside on Microsoft Hyper-V Server 2016 or later).

Source for Data Recovery

  • You can restore VM guest OS files from a backup that has at least one successfully created restore point.
  • You cannot restore files from a backup created in the reverse incremental mode if the backup job is being performed. If the backup is created in the incremental backup mode and the backup job is being performed, you can restore files from any available restore point.
  • You cannot restore pipes and other file system objects. Guest OS file restore supports recovery of files and folders only.
  • You cannot restore guest OS files encrypted with Windows EFS.
  • You cannot restore and browse guest OS files on disks encrypted by BitLocker.
  • Processing of reparse points is supported only for NTFS. Note that reparse points with reparse tag values other than IO_REPARSE_TAG_MOUNT_POINT, IO_REPARSE_TAG_SYMLINK and IO_REPARSE_TAG_DEDUP may be processed and restored incorrectly.
  • [For restore to original location] You cannot restore VM guest OS files if you have excluded the system disk from the VM backup used for restore and the volume GUID of the system disk was changed after the VM backup creation.
  • The comparison functionality is not available for backups created by Veeam Backup for OLVM and RHV, for backups exported with K10 policies and for backups stored in external repositories (for example, backups created by Veeam Backup for AWS, Veeam Backup for Microsoft Azure and so on).
  • [For permission restore] Permissions can be restored only for files and folders that are still present on the original VMs. If files and folders are missing, restore fails.

Page updated 5/29/2024

Page content applies to build