Before you restore VM guest OS files, check the following prerequisites:
- 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.
- If you plan to restore VM guest OS files to their initial location, Hyper-V Integration Services must be installed on the target VM.
- Veeam Backup & Replication must have access to the guest OS of the target VM to deploy a coordination process. The coordination process performs a number of administrative actions on the target VM guest OS, for example, collects information about mount points.
- [For Linux/Unix-based target VM] Veeam Backup & Replication uses the SSH protocol to communicate with the target Linux/Unix VM and requires the SCP utility on the target VM. Make sure that the SSH daemon is properly configured and SCP utility is available on the target VM.
- Veeam Backup & Replication can restore ACL for recovered VM guest OS files. To let Veeam Backup & Replication detect the target Linux system architecture and kernel version, the following utilities must be present in the minimal configuration of the system: arch and uname.
Mind the following limitations:
- You cannot restore pipes and other file system objects. File-level restore supports recovery of files and folders only.
- You cannot restore files directly to the original location from backups of BSD, Mac and Solaris VMs. Use the Copy to option instead.
- The multi-OS file-level restore wizard does not support restore of deduplicated volumes (for example, Microsoft Windows volumes with Data Deduplication enabled).