NVP vProxy: Windows VM File Level Recovery Fails for Some Files With Message "Some objects, or security properties could not be recovered."

• A File Level Recovery (FLR) is performed for a Windows VM using the NetWorker VMware Protection (NVP) vProxy appliance. The FLR fails with the message "Some objects, or security properties could not be recovered."

YYYY-MM-DDTHH:mm:SS-TZ INFO:   [@(#) Build number: 35] Recovery: SOME_FILE
YYYY-MM-DDTHH:mm:SS-TZ ERROR:  [@(#) Build number: 35] Recovery: Cannot open 'C:\Program Files (x86)\EMC\vProxy FLR Agent\flr\mountpoints\FLR760973190\00-E$\SOME_DIRECTORY\SOME_FILE': open C:\Program Files (x86)\EMC\vProxy FLR Agent\flr\mountpoints\FLR760973190\00-E$\SOME_DIRECTORY\SOME_FILE: The file cannot be accessed by the system.
YYYY-MM-DDTHH:mm:SS-TZ INFO:   [@(#) Build number: 35] File copying completed.
YYYY-MM-DDTHH:mm:SS-TZ ERROR:  [@(#) Build number: 35] C:\Program Files (x86)\EMC\vProxy FLR Agent\bin\vflrcopy.exe: : Some objects or security properties could not be recovered. 

• The source VM and target VM are separate VMs.
• Attempting to copy the file from the FLR mountpoint under C:\Program Files (x86)\EMC\vProxy FLR Agent\flr\mountpoints fails with: Error 0x80070780

Figure 1: Copying the file from the FLR mountpoint fails with Error 0x80070780.

File Server Data Deduplication feature is installed on the source VM. This is determined with the following PowerShell command on the source VM:

Get-WindowsFeature -Name FS-Data-Deduplication

Figure 2: Confirmation that the File Server Data Deduplication feature is installed on the source VM.

Get-DedupStatus -Volume "<DRIVE_LETTER>:"

Figure 3: Confirmation that Volume deduplication is enabled on the volume that you are trying to restore data from.

Expected behavior - Deduplicated New Technology File System (NTFS) is not supported for FLR. This is per the NetWorker VMware Integration Guide. This documentation is available on the Dell Support Product Page. 

Deduplicated NTFS is considered unsupported by vProxy FLR. Configuring deduplicated volumes should be avoided.

Workaround:
Use one of the following options:

• Perform the FLR recovering the data to the original VM. 

Figure 4: Selecting destination as Recover to the original virtual machine

• On the target VM, install the "Data Deduplication" feature from the Windows Server Roles.

Figure 5: From the target VM, install the "Data Deduplication" feature from the Windows Server Roles.

Once the Data Deduplication feature is installed, do not configure any deduplicated volumes. Perform the FLR to the target VM. 

Similar errors can appear on Windows VM where Win32 long path is disabled and the File path exceeds 260 characters: NVP vProxy: FLR fails on Windows VM "The filename, directory name, or volume label syntax is incorrect"