PowerProtect Data Manager 19.11 Virtual Machine User Guide

Consider the following:

• Ensure that the target virtual machine's SCSI Controller 0, SCSI(0:0) slot is not empty by attaching the slot to a virtual disk. Otherwise, the file-level restore is unable to mount the disks from the backup copy.
• Ensure that the virtual machine has enough free slots to accommodate the disks that will mounted as part of the restore. The total number of supported disks is 60 (4 scsi controllers with 15 disks each).
• Windows 2012 R2 and earlier versions do not support paths longer than 255 characters. To reduce the number of characters in the restore path, you might be required to remove the Windows drive letter, the colon, the slash, and the trailing null character. Since the Windows vProxy Agent mount point already uses around 90 characters, you might need to select a folder at a higher directory level for the restore.

  For Windows 2016 and later, an option to enable support for longer file paths is available. See the following article.

• When performing a file-level restore, VMDKs fail to mount with the following error if the vProxy Agent service is not running on the target virtual machine: "Cannot connect to vProxy Agent: dial tcp <127.0.0.1:<port>: connectex: No connection could be made because the target machine actively refused it."
• When a file-level restore or SQL-restore operation is in progress on a virtual machine, no other backup or recovery operation can be performed on this virtual machine. Wait until the file-level restore session completes before starting any other operation on the virtual machine.
• Clean up from a suspended or cancelled mount operation requires a restart of the virtual machine before you can initiate a new mount for the file-level restore.
• When you enable Admin Approval Mode (AAM) on the operating system for a virtual machine (for example, by setting Registry/FilterAdministratorToken to 1), the administrator user cannot perform a file-level restore to the end user's profile, and an error displays indicating "Unable to browse destination." For any user account control (UAC) interactions, the administrator must wait for the mount operation to complete, and then access the backup folders located at C:\Program Files (x86)\EMC\vProxy FLR Agent\flr\mountpoints by logging into the guest virtual machine using Windows Explorer or a command prompt.
• When you perform file-level restore on Windows 2012 R2 virtual machines, the volumes listed under the virtual machine display as "unknown." File-restore operations are not impacted by this issue.
• When you perform file-level restore on Ubuntu/Debian platforms, you must enable the root account in the operating system. By default, the root account will be in locked state.
• You can only restore files and/or folders from a Windows backup to a Windows machine, or from a Linux backup to a Linux machine.
• You must install VMware Tools version 10 or later. For best results, ensure that all virtual machines run the latest available version of VMware Tools. Older versions are known to cause failures when you perform browse actions during file-level restore or SQL restore operations.
• You can perform file-level restores across vCenter servers as long as the vCenters are configured in PowerProtect Data Manager, and the source and target virtual machine have the same guest operating system. For example, Linux to Linux, or Windows to Windows.
• File-level restores do not support the following virtual disk configurations:
  • LVM thin provisioning
  • Windows VMs that contain unformatted disks
    NOTE FLR of Linux VMs that contain unformatted disks is supported.
  • FAT16 file systems
  • FAT32 file systems
  • Extended partitions (Types: 05h, 0Fh, 85h, C5h, D5h)
  • Two or more virtual disks mapped to single partition
  • Encrypted partitions
  • Compressed partitions
• File-level restores of virtual machines with Windows dynamic disks are supported with the following limitations:
  • The restore can only be performed when recovering to a virtual machine different from the original. Also, this virtual machine cannot be a clone of the original.
  • The restore can only be performed by virtual machine administrator users.
  • If Windows virtual machines were created by cloning or deploying the same template, then all of these Windows virtual machines may end up using the same GUID on their dynamic volumes.
• File-level restores do not restore or browse symbolic links.
• File-level restores of Windows 8, Windows Server 2012 and Windows Server 2016 virtual machines are not supported on the following file systems:
  • Deduplicated NTFS
  • Resilient File System (ReFS)
  • EFI bootloader