Considerations and Limitations

This section lists considerations and limitations common for recovery guest OS files and folders from Microsoft Windows and Linux workloads. For information on considerations and limitations specific for recovering Microsoft Windows and Linux workloads, see Microsoft Windows Limitations and Considerations Guest OS Recovery and Linux Limitations and Considerations Guest OS Recovery.

Infrastructure Components

Source for Data Recovery

  • You can recover guest OS files from a backup, replica, Cloud Director replica or CDP replica that has at least one successfully created restore point.
  • You cannot recover 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 recover files from any available restore point.
  • [For vSphere] You cannot recover guest OS files from a running VM replica or if the replication job with the necessary VM is being performed. However, recovery is possible for CDP replicas if the CDP policy is running.

Target for Data Recovery

[For vSphere and Hyper-V] If you plan to recover guest OS files to their original location or to another VM of the same platform, check the following:

  • [For vSphere] VMware Tools or OpenVM Tools are installed and running on the target workload.
  • [For Hyper-V] Hyper-V Integration Services are installed and on the target workload.

Linux Helper Host as Mount Server

If you plan to use a Linux helper host as a mount server (select the <Linux_host_name> or Specify a different Linux host option at the Restore point step), consider the following:

  • Check the supported OSes listed in System Requirements.
  • The backup server and the mount server, associated with the repository where the backup is stored, must be able to resolve the FQDN of the helper host.
  • You can recover from ZFS if the zfsutils-linux package is installed on the specified Linux helper host. The package zfs-fuse package is not supported.
  • The Linux helper host OS kernel must support the file system that you plan to mount on this host. Otherwise, mount will be refused and in rare cases it may cause kernel panic.
  • Make sure that the /tmp directory is mounted with the exec option. Otherwise, you will get an error with the permission denial.
  • For the Linux helper host option, mounting of LVM snapshots is not supported. Thus, LVM snapshots are skipped from processing.
  • Recovery from a Btrfs disk using the original server as the Linux helper host is not possible. The issue occurs due to restriction of mounting two Btrfs disks with identical IDs to the same machine. To avoid this issue, use the helper appliance option or a different Linux-based server that supports Btrfs. However, note that Btrfs disks can be recovered for backups created by Veeam Agent for Linux. During the backup process, Veeam Agent for Linux changes disk IDs in the backup file.
  • Recovery from a ZFS pool using the original server as the mount server is not possible. The issue occurs due to restriction of mounting two ZFS pools with identical UUIDs to the same machine. To avoid this issue, use the helper appliance option or a different Linux-based server that supports ZFS pools.
  • Hardened repositories cannot be selected as Linux helper hosts.

CDP Replicas

  • You can launch restore for a CDP replica if its CDP policy is currently running. CDP will continue working.
  • During restore, the CDP policy does not create new long-term restore points and does not delete the existing ones. Short-term restore points are still created.
  • You cannot launch guest OS file restore, SureReplica, application item restore and failover in parallel for one VM or replica.

Storage Snapshots

Requirements for guest OS file restore from storage snapshots are listed in the Data Recovery from Storage Snapshots section.

Page updated 8/28/2025

Page content applies to build 13.0.0.4967