Problem description
Restore job is successful but the files are not restored at the destination.
Please check below 3 scenario to understand if this is due to de-dupe Volume on Source VM.
Job logs says “Skipping symbolic link”.
[2023-05-24 14:43:11,487] [INFO] FlrRestore: Skipping symbolic link [/mnt/flr_1069r/volume2/ServerFolders/Company/Departments/Accounting/Payroll Summary/2022/01-01-2022.pdf]We can browse through the files in FLR window but the files size shows “34 B” in case of a dedupe file.
If we login to the proxy and navigate to the required folder then we can see unsupported reparse tag error for the deduped file.
Eg:
unsupported reparse tag 0x80000013”
Cause
Source VM have De-dupe enabled volumes.
Traceback
[2023-05-24 14:43:11,487] [INFO] FlrRestore: Skipping symbolic link [/mnt/flr_1069r/volume2/ServerFolders/Company/Departments/Accounting/Payroll Summary/2022/01-01-2022.pdf]
Resolution
De-dupe volume is not supported for VMware FLR( Click Here )
Workaround
Restore a Virtual machine Disk/VMDK ( Click Here ) and attached the VMDK to the source VM ( Click Here ) or
Restore the full VM ( Click Here ).
Note:There are 2 basic requirements for restoring files from VMDK having dedupe enabled volume on any VM other than the source VM:
The Data Deduplication feature must be enabled in the Windows server.
The OS version must be the same as the source VM. It may or may not work with older or newer versions.
See also
File_Level_Restore Considerations( Click Here )
Install and enable De-dupe( Click Here )