Debian compatibility 8 Netbackup 7.6.0.4

[Leandro_Vieira]

Good day,

Netbackup 7.6.0.4 is compatible with Debian 8???? for VM backup.

I did a test, the backup processed normally, the normal restore backup ok.

The virtual machine restore submitted error (2820).

[revarooo · Accepted solution]

Debian 8 is not supported

Click the link before which takes you to the Compatibility guide and shows only upto Debian 7 is supported:

https://symwisedownload.symantec.com/resources/sites/SYMWISE/content/live/SOLUTIONS/76000/TECH76648/en_US/nbu_76_scl.html?__gda__=1433307933_67ae316afa63a880922b727311927445#operating_systems-debian_gnu_linux-debian_gnu_linux_-_netbackup_client

[Marianne]

For VMware compatibility, download this doc:

Statement of Support for NetBackup 7.x in a Virtual Environment:    http://www.symantec.com/docs/TECH127089  

[Leandro_Vieira]

I could do to original location, virtual machine.

For alternate location presented this error.

03/06/2015 14:26:28 - begin Restore
03/06/2015 14:26:29 - media needed: RJ0005
03/06/2015 14:26:29 - restoring from image GAVIAO_1433344665
03/06/2015 14:26:29 - Info bprd (pid=1209) Restoring from copy 1 of image created Wed Jun  3 12:17:45 2015 from policy Linux_Teste
03/06/2015 14:26:30 - Info bprd.sfr (pid=1209) Restoring to vCenter server quimera.datasus.gov, ESX host hstclsrj-01.datasus.gov, Datacenter /Datasus-Rio, Folder /Datasus-Rio/vm/Pool de Recursos GARES/Outros/, Display Name GAVIAO_restore, Resource Pool/vApp /Datasus-Rio/host/Produção/Resources, Datastore/Datastore Cluster VSP_04
03/06/2015 14:26:31 - Info bptm (pid=4700) start
03/06/2015 14:26:31 - started process bptm (pid=4700)
03/06/2015 14:26:31 - Info bptm (pid=4700) reading backup image
03/06/2015 14:26:31 - Info bptm (pid=4700) using 30 data buffers
03/06/2015 14:26:31 - Info bptm (pid=4700) spawning a child process
03/06/2015 14:26:31 - Info bptm (pid=4700) child pid: 3372
03/06/2015 14:26:31 - Info bptm (pid=3372) start
03/06/2015 14:26:31 - started process bptm (pid=3372)
03/06/2015 14:26:33 - Info bptm (pid=4700) Waiting for mount of media id RJ0005 (copy 1) on server dtsbkp-media.datasus.gov.
03/06/2015 14:26:33 - started process bptm (pid=4700)
03/06/2015 14:26:33 - mounting RJ0005
03/06/2015 14:26:33 - requesting resource RJ0005
03/06/2015 14:26:33 - Waiting for scan drive stop DRIVE_5, Media server: dtsbkp-media
03/06/2015 14:26:34 - granted resource  RJ0005
03/06/2015 14:26:34 - granted resource  DRIVE_5
03/06/2015 14:26:35 - Info bptm (pid=4700) INF - Waiting for mount of media id RJ0005 on server dtsbkp-media.datasus.gov for reading.
03/06/2015 14:27:18 - mounted RJ0005; mount time: 0:00:45
03/06/2015 14:27:18 - Info bptm (pid=4700) RJ0005
03/06/2015 14:27:19 - Info bptm (pid=4700) INF - Waiting for positioning of media id RJ0005 on server dtsbkp-media.datasus.gov for reading.
03/06/2015 14:27:19 - positioning RJ0005 to file 7
03/06/2015 14:29:34 - positioned RJ0005; position time: 0:02:15
03/06/2015 14:29:35 - begin reading
03/06/2015 14:29:36 - Info bptm (pid=4700) waited for empty buffer 1 times, delayed 6 times
03/06/2015 14:29:36 - end reading; read time: 0:00:01
03/06/2015 14:29:37 - Info bptm (pid=4700) completed reading backup image
03/06/2015 14:29:37 - Info bptm (pid=4700) EXITING with status 0 <----------
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) INF - vmwareLogger: RetrieveMorByInventoryPath: FindByInventoryPath for /Datasus-Rio/host/Produção/Resources, failed
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) INF - vmwareLogger: RetrieveMorByInventoryPath: SYM_VMC_ERROR:  SOAP_ERROR
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) INF - vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode]
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) "
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) Error returned by expat parser: not well-formed (invalid token)
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) 
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) INF - vmwareLogger: CreateVirtualMachineExAPI: SYM_VMC_ERROR:  FAILED_TO_GET_POOL_MOR
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) while parsing serialized value of type string
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) at line 2, column 435
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) 
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) while parsing call information for method FindByInventoryPath
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) at line 2, column 273
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) 
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) while parsing SOAP body
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) at line 2, column 258
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) 
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) while parsing SOAP envelope
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) at line 2, column 0
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) 
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) while parsing HTTP request for method findByInventoryPath
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) on object of type vim.SearchIndex
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) at line 1, column 0"
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) Detail: <InvalidRequestFault xmlns="urn:vim25" xsi:type="InvalidRequest"></InvalidRequestFault>
03/06/2015 14:29:46 - Info bpVMutil (pid=11188) 
03/06/2015 14:29:47 - end Restore; elapsed time 0:03:19
NBU VMware policy restore error  (2820)

[Marianne]

Looks like there may be something wrong with the destination that you have specified.

We cannot comment without knowing what you have specified or what destinations exist in the environment.

PS:

This post is about compatibility - have you checked the docs that we have provided above?

The Support for NetBackup 7.x in virtual environments  doc says the following on page 16:

Supported VMware guest operating systems NetBackup for VMware supports virtual machine backup and recovery on all guest operating systems supported by VMware. To check VMware support for a particular operating system, consult the VMware Compatibility Guide. 

[Leandro_Vieira]

Yes,

I am restoring to the same location, just changing the name of the Display Name.

[Marianne]

Again - your post was about compatibility. Not changing VM display name...

[Leandro_Vieira]

I did not understand what I meant.

[RZPLinux]

revarooo,

do you have any information regarding future support for debian 8?