cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup 7.7.3 VMware policy restore error(2820)

billvel
Level 3

Hi Guys,
Good Day.

While i'm trying to restore entire VM always getting bellow issues: tried different dates and different Transport Type still same.

PS: but backup was ended with successfully.

Error: when restore using Transport Type = san:

15:12:28 (602967.001) INF - Transport Type = san
15:12:28 (602967.001) WRN - Cannot set metadata (key:geometry.biosCylinders, value:16383) when using san or hotadd transport.
15:12:28 (602967.001) WRN - Cannot set metadata (key:geometry.biosHeads, value:16) when using san or hotadd transport.
15:12:28 (602967.001) WRN - Cannot set metadata (key:geometry.cylinders, value:16383) when using san or hotadd transport.
15:12:28 (602967.001) WRN - Cannot set metadata (key:geometry.heads, value:16) when using san or hotadd transport.
15:12:28 (602967.001) WRN - Unable to set vmdk metadata using san or hotadd transport. VM may not boot unless manually changed in disk discriptor file.
15:12:28 (602967.001) ERR - Virtual machine restore file write failed
15:12:28 (602967.001) ERR - An API returned an unexpected value
15:12:28 (602967.001) ERR - An API returned an unexpected value
15:12:29 (602967.001) INF - TAR EXITING WITH STATUS = 14
15:12:29 (602967.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY
15:12:29 (602967.001) INF - TAR KEPT 0 EXISTING FILES
15:12:29 (602967.001) INF - TAR PARTIALLY RESTORED 0 FILES
15:13:42 (602967.001) Status of restore from copy 1 of image created Fri Nov 10 19:25:42 2017 = the restore failed to recover the requested files

15:13:43 (602967.xxx) INF - Status = VMware policy restore error.

 Error: when restore using Transport Type = nbd:

16:12:43 (602981.001) WRN - Error opening snapshot disk(s) using given transport mode(s)
16:12:43 (602981.001) ERR - Error opening the snapshot disks using given transport mode: nbd Status 23
16:12:43 (602981.001) ERR - Unable to initialize VxMS
16:12:43 (602981.001) ERR - An API returned an unexpected value
16:12:43 (602981.001) ERR - An API returned an unexpected value
16:12:45 (602981.001) INF - TAR EXITING WITH STATUS = 103
16:12:45 (602981.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY
16:12:45 (602981.001) INF - TAR KEPT 0 EXISTING FILES
16:12:45 (602981.001) INF - TAR PARTIALLY RESTORED 0 FILES
16:13:58 (602981.001) Status of restore from copy 1 of image created Fri Nov 10 19:25:42 2017 = the restore failed to recover the requested files

 Error: when restore using Transport Type =san or hotadd 

16:26:59 (602988.001) WRN - Cannot set metadata (key:geometry.biosCylinders, value:16383) when using san or hotadd transport.
16:26:59 (602988.001) WRN - Cannot set metadata (key:geometry.biosHeads, value:16) when using san or hotadd transport.
16:26:59 (602988.001) WRN - Cannot set metadata (key:geometry.cylinders, value:16383) when using san or hotadd transport.
16:26:59 (602988.001) WRN - Cannot set metadata (key:geometry.heads, value:16) when using san or hotadd transport.
16:26:59 (602988.001) WRN - Unable to set vmdk metadata using san or hotadd transport. VM may not boot unless manually changed in disk discriptor file.
16:26:59 (602988.001) ERR - Virtual machine restore file write failed
16:26:59 (602988.001) ERR - An API returned an unexpected value
16:26:59 (602988.001) ERR - An API returned an unexpected value
16:27:01 (602988.001) INF - TAR EXITING WITH STATUS = 14
16:27:01 (602988.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY
16:27:01 (602988.001) INF - TAR KEPT 0 EXISTING FILES
16:27:01 (602988.001) INF - TAR PARTIALLY RESTORED 0 FILES

Detailed message from Activity monitor:
11/16/2017 16:26:59 - Info tar32 (pid=7108) INF - Transport Type = san
11/16/2017 16:26:59 - Warning bpbrm (pid=5832) from client xxxx: WRN - Cannot set metadata (key:geometry.biosCylinders, value:16383) when using san or hotadd transport.
11/16/2017 16:26:59 - Warning bpbrm (pid=5832) from client xxxx: WRN - Cannot set metadata (key:geometry.biosHeads, value:16) when using san or hotadd transport.
11/16/2017 16:26:59 - Warning bpbrm (pid=5832) from client xxxx: WRN - Cannot set metadata (key:geometry.cylinders, value:16383) when using san or hotadd transport.
11/16/2017 16:26:59 - Warning bpbrm (pid=5832) from client xxxx: WRN - Cannot set metadata (key:geometry.heads, value:16) when using san or hotadd transport.
11/16/2017 16:26:59 - Error bptm (pid=4636) cannot write data to socket, 10053
11/16/2017 16:26:59 - Info bptm (pid=5328) EXITING with status 24 <----------
11/16/2017 16:27:01 - Info tar32 (pid=7108) done. status: 14
11/16/2017 16:27:01 - Info tar32 (pid=7108) done. status: 24: socket write failed
11/16/2017 16:27:01 - Error bpbrm (pid=5832) client restore EXIT STATUS 24: socket write failed
11/16/2017 16:27:39 - restored from image hostnamexxx_1510313142; restore time: 0:06:31
11/16/2017 16:27:40 - end Restore; elapsed time 0:06:34
NetBackup VMware policy restore error (2820)

2 REPLIES 2

GeForce123
Level 5

The failure you see when using SAN and Hotadd are expected, writing metadata is not supported by those transport modes, you should be able to restore over NBD just fine but that is failing for an entirely different reason.

You could use the restore that you performed using SAN, turn the power on and if it comes up with no issues, you can use that restore. Nothing was affected or lost. If it didn't come up without issues, you could edit the descriptors and then boot the VM and it will be fine.
https://www.veritas.com/support/en_US/article.TECH210611

To figure out why it is failing over NBD, I would suggest looking at the VxMS logs. Please upload them if you have them.

 

Hi 

Makesure you add ESX host IP's to media server when you using NBD Transport mode.

If you using SAN , datastore must be online in Media server to able to write the data(Applicable only to windows.)

 

Rahul