I'm trying to restore a full VM and I'm getting this error:
13:45:08 (139713.001) TAR - .....vmdk
13:46:30 (139713.001) Status of restore from copy 1 of image created 29/06/2019 10:47:16 = the restore failed to recover the requested files
13:46:30 (139713.001) The following files/folders were not restored:
13:46:30 (139713.001) UTF - ........vmdk
13:46:39 (139713.xxx) INF - Status = VMware policy restore error.
The backup was completed without any error.
I'm running the restore using NBC, removing any attached device to the VM.
The VM appears in vCenter and have the vmdk properly transferred to the datastores, but when try to boot the VM get the error "Operating System not found" and if I try to add the vmdk to another VM it appears as Unallocated and I can't see the data.
This VM has aroung 2TB data, I could recover sucessfully a smaller VM (400GB).
Someone have any idea what could be the issue?
With what protocol are you running the restore? NBD? HotAdd? SAN?
This sounds like maybe the wrong one is selected; I personally have only had luck running a restore via NBD protocol (even if the backup was taken via SAN or HotAdd).
follow the debugging advice here: https://www.veritas.com/support/en_US/article.100022695, I would especially enable tar and bpVMutil logs on the Backup Host.
It seems that permission for VM creation is in place, but permission to write into it is missing.
P.S. all timestamps in your log are from 13:mm, but one in the middle is from 10:mm ?
Here some details I got from the logs:
00:06:20 (139710.001) Restoring from copy 1 of image created 29/06/2019 08:46:15 from policy xxxxx
00:06:30 (139710.xxx) Restoring to vCenter server xxxxxx, ESX host xxxxxx, Datacenter /xxxx, Folder /xxxx/vm/, Display Name xxxx, Resource Pool/vApp /xxxx/host/Cluster xxxx/Resources, Datastore/Datastore Cluster xxxx
00:07:36 INF - If Media id xxxxx is not in a robotic library administrative interaction may be required to satisfy this mount request.
00:07:39 INF - Waiting for mount of media id xxxxx on server xxxx for reading.
00:08:43 INF - Waiting for positioning of media id xxxxx on server xxxx for reading.
00:12:38 INF - Beginning read-blockmap on server xxxx of client xxxx.
00:13:06 (139710.xxx) Executing Virtual machine creation on xxxx to server xxxx.
09:42:26 (139710.001) Status of restore from copy 1 of image created 29/06/2019 08:46:15 = Restore failed due to failure to create the virtual machine
09:42:26 (139710.001) The following files/folders were not restored:
09:42:26 (139710.001) UTF - /xxx.vmdk
09:42:26 (139710.001) UTF - /xxxx_1.vmdk
09:42:26 (139710.001) UTF - /xxxx_2.vmdk
09:42:26 (139710.001) UTF - /xxxx_3.vmdk
09:42:26 (139710.001) UTF - /xxxx_1.vmdk
09:42:34 (139710.xxx) INF - Status = VMware policy restore error.
I also tried to restore individual files for this VM and some files are not restoring with the same error above.
I already followed the procedure and enabled the logs but don't see any aparent error on the logs:
bpVMutil or bpcd
The tar folder at the logs is not creating any logfile.
All tests on Pre Recovery Check is also passed.
so - was the target VM created or no? If no, then a problem is within vSphere permissions.
08:46:15 = Restore failed due to failure to create the virtual machine
The VM is being created in vcenter and also VMDKs are on the datastores.
I tried to use Original Provisioning and other types but is the only one works. VM when powered on gives the message "Operational System not found" and if I try to open the VMDKs restored in another VM the disk appear with a volume "Unallocated".
I figured out on the restore job log the error below is appearing:
10/02/2020 10:32:17 - restored image xxxxxxxxxxx_1581123632 - (the restore failed to recover the requested files(5)); restore time 0:15:15
10/02/2020 10:32:23 - end Restore; elapsed time: 0:15:24
VMware policy restore error(2820)
10/02/2020 10:43:12 - Error bptm(pid=5740) get_string() failed reading file list from bprd, (0), premature end of file encountered
10/02/2020 10:43:14 - Info bptm(pid=5672) EXITING with status 23 <----------
10/02/2020 10:43:18 - Error bpbrm(pid=6864) could not write EXIT STATUS to OUTSOCK
10/02/2020 10:43:19 - Info tar32(pid=6780) done. status: 23: socket read failed
10/02/2020 10:43:19 - Error bpbrm(pid=6864) client restore EXIT STATUS 23: socket read failed