vRanger is unable to restore the VM no matter what workarounds you attempt to use.
Sometimes vRanger runs into a restore issue and nothing can be done to resolve it at the time of the restore and would take a very long time to determine what may be causing the issue.
Because the troubleshooting of the restore issue will take to long to do it is now time to perform a manual restore. Please follow these steps to perform the manual restore.
1. Provide the customer the PhysRestore 5.x.zip which contains the vRanger manual restore utility
2. Open powershell and run the following command Set-ExecutionPolicy remotesigned
3. Create a new VM on the ESX host, the drive/drives should be the same size drive/drives as the original(the sizes can be found in the VMconfig.metadata file)
4. Run the phys extractor(browse to the directory that contains the Physrestore5.x.ps1 and run it by using the following command .\Physrestore5.x.ps1)
5. Select the var file to extract by clicking on the 3 button next to select var file
6. Provide a name and a destination for the -flat.vmdk or -delta.vmdk file that will be extracted ( the name of the .vmdk can be anything, but using the same name as the created VM is recommended, ex. VM-flat.vmdk)
7. Click Extract vmdk
8. Once the extraction is complete the Close button will change to Finish
9. If in step 4 you didn't name the .vmdk as the created VM now change the name to be the same as the -flat.vmdk or -delta.vmdk on the ESX(i) host
10. Use a tool like WinSCP to upload the extracted -flat.vmdk or -delta.vmdk to the directory that contains the newly created VM on the ESX(i) host during the upload you are replacing the -flat.vmdk or -delta.vmdk that was created during the new VM creation
11. Repeat steps 2-9 for all the drive the you need to restore
12. After all the drives have been restored and uploaded to the ESX(i) host power on the VM it should be fully operational