Cannot snapshot SLES 11 SP2 with Netbackup 7.6.0.1

[leszakandras]

Hello,

I have a problem with the backup of SLES 11. I have a clientless install, for only vmware backup. Other vms are backed up with the policy, (windows and opensuse) but not SLES.

Error message is the following:
 

08/05/2014 09:57:59 - Info nbjm (pid=8133) starting backup job (jobid=97) for client xxxxxxxx, policy VMWare_teszt, schedule Full
08/05/2014 09:57:59 - Info nbjm (pid=8133) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=97, request id:{37BF1288-1C76-11E4-A55A-8565C13A4CAD})
08/05/2014 09:57:59 - requesting resource Any
08/05/2014 09:57:59 - requesting resource xxxxxx.NBU_CLIENT.MAXJOBS.xxxxxx
08/05/2014 09:57:59 - requesting resource xxxxxx.NBU_POLICY.MAXJOBS.VMWare_teszt
08/05/2014 09:57:59 - Waiting for scan drive stop HP.ULTRIUM6-SCSI.005, Media server: rokipribck1.terex.local
08/05/2014 09:58:00 - granted resource  xxxxxx.NBU_CLIENT.MAXJOBS.xxxxxx
08/05/2014 09:58:00 - granted resource xxxxxx.NBU_POLICY.MAXJOBS.VMWare_teszt
08/05/2014 09:58:00 - granted resource  8236L6
08/05/2014 09:58:00 - granted resource  HP.ULTRIUM6-SCSI.005
08/05/2014 09:58:00 - granted resource  xxxxxx-hcart3-robot-tld-0
08/05/2014 09:58:00 - estimated 0 kbytes needed
08/05/2014 09:58:00 - begin Parent Job
08/05/2014 09:58:00 - begin VMware: Start Notify Script
08/05/2014 09:58:00 - Info RUNCMD (pid=3685) started
08/05/2014 09:58:00 - Info RUNCMD (pid=3685) exiting with status: 0
Operation Status: 0
08/05/2014 09:58:00 - end VMware: Start Notify Script; elapsed time 0:00:00
08/05/2014 09:58:00 - begin VMware: Step By Condition
Operation Status: 0
08/05/2014 09:58:00 - end VMware: Step By Condition; elapsed time 0:00:00
08/05/2014 09:58:00 - begin VMware: Read File List
Operation Status: 0
08/05/2014 09:58:00 - end VMware: Read File List; elapsed time 0:00:00
08/05/2014 09:58:00 - begin VMware: Create Snapshot
08/05/2014 09:58:00 - started process bpbrm (pid=3691)
08/05/2014 09:58:01 - Info bpbrm (pid=3691) xxxxxx is the host to backup data from
08/05/2014 09:58:01 - Info bpbrm (pid=3691) reading file list for client
08/05/2014 09:58:01 - Info bpbrm (pid=3691) start bpfis on client
08/05/2014 09:58:01 - Info bpbrm (pid=3691) Starting create snapshot processing
08/05/2014 09:58:01 - Info bpfis (pid=3702) Backup started
08/05/2014 09:58:01 - snapshot backup of client xxxxxx using method VMware_v2
08/05/2014 09:58:06 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:58:19 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:58:32 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:58:45 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:58:58 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:59:11 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:59:24 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:59:34 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 09:59:47 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 10:00:00 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 10:00:13 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
08/05/2014 10:00:27 - Critical bpbrm (pid=3691) from client xxxxxx: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error
08/05/2014 10:00:27 - Critical bpbrm (pid=3691) from client xxxxxx: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
08/05/2014 10:00:27 - Critical bpbrm (pid=3691) from client xxxxxx: FTL -
08/05/2014 10:00:27 - Critical bpbrm (pid=3691) from client xxxxxx: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
08/05/2014 10:00:27 - Critical bpbrm (pid=3691) from client xxxxxx: FTL -
08/05/2014 10:00:27 - Critical bpbrm (pid=3691) from client xxxxxx: FTL - snapshot processing failed, status 156
08/05/2014 10:00:27 - Critical bpbrm (pid=3691) from client xxxxxx: FTL - snapshot creation failed, status 156
08/05/2014 10:00:27 - Warning bpbrm (pid=3691) from client xxxxxx: WRN - ALL_LOCAL_DRIVES is not frozen
08/05/2014 10:00:27 - Info bpfis (pid=3702) done. status: 156
08/05/2014 10:00:27 - end VMware: Create Snapshot; elapsed time 0:02:27
08/05/2014 10:00:27 - Info bpfis (pid=3702) done. status: 156: snapshot error encountered
08/05/2014 10:00:27 - Info bpbrm (pid=3907) Starting delete snapshot processing
08/05/2014 10:00:27 - Info bpfis (pid=3920) Backup started
08/05/2014 10:00:27 - Critical bpbrm (pid=3907) from client xxxxxx: FTL - cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.Rokiwebteszt1_1407225480.1.0
08/05/2014 10:00:27 - Info bpfis (pid=3920) done. status: 4207
08/05/2014 10:00:27 - end Parent Job; elapsed time 0:02:27
08/05/2014 10:00:27 - Info bpfis (pid=3920) done. status: 4207: Could not fetch snapshot metadata or state files
08/05/2014 10:00:27 - end writing
Operation Status: 156
08/05/2014 10:00:27 - begin VMware: Stop On Error
Operation Status: 0
08/05/2014 10:00:27 - end VMware: Stop On Error; elapsed time 0:00:00
08/05/2014 10:00:27 - begin VMware: Delete Snapshot
08/05/2014 10:00:27 - started process bpbrm (pid=3907)
08/05/2014 10:00:27 - end writing
Operation Status: 4207
08/05/2014 10:00:27 - end VMware: Delete Snapshot; elapsed time 0:00:00
Operation Status: 156
snapshot error encountered  (156)

I have not found any match on this one: 08/05/2014 09:58:06 - Info bpbrm (pid=3691) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR.

Nothing found on vcenter or esxi host level. VMware is 5.1. Rights are fine, I try it with the highest level administrator, and vmware tools are installed. I also tried with SYMCquiesce utility, but not succeeded. (Anyway, the opensuse did work without quiesce)

Thanks for any advice!

Best regards

Andras

[SymTerry]

Hello,

status code  4207  is when Snapshot metadata that the NetBackup client requires is missing or cannot be fetched from the NetBackup master server.

from HOWTO91745:

Verify the following:

• The NetBackup client can communicate with the NetBackup master.

• The state file location on the NetBackup client has write permission. The typical location of the NetBackup state file on the NetBackup client is as follows:

  Windows: C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\

  UNIX: /usr/openv/netbackup/online_util/fi_cntl

[leszakandras]

Hello,

thanks for answering. There is no client, I want to backup the vm with snapshot, without client. Anyway, if client solves this, I can install it.

Thanks

Andras

[AAlmroth]

Have you tried testing without quiesce option set in the policy? If that works, then it is probably an issue inside the SLES guest. 

You could possibly try to install the SYMCquiesce tool. It does require that VMWare tools is installed and running. Installing NBU client should not be required, but practical if you would like to restore files directly from inside the OS.

"NetBackup for VMware: notes on Linux virtual machines" http://www.symantec.com/docs/HOWTO70958

There are some links in that technote which gives you more info about the tools and requirements.

/A

[leszakandras]

Hello,

I tried both, without quiesce, and with SYMCquiesce utility, neither worked. I read that notes on Linux vms documentation, but nothing usable for me.

Andras

[Anonymous]

Confirm you can perform snapshot of that specific from within vSphere and also Delete All. Preferably as the user specified in NetBackup credentials.

Further do you have quiesce VM option set. If so try a backup without quiesce OS.

Do you have freeze and thaw scripts on this VM guest OS?

Tools must be in running state prior and after backup/error. Confirm this. (Make sure tools up to date. Are you using OSP tools or VMware Tools?)

You could review the vmware.log file for the SLES vm and check around the time of backup failure if there is a problem with the VM.

vmware.log is in the same location/datastore folder as the VM config .vmx file

You can download through the vsphere client by browsing the datastore to that location.

There is this to look at
VMware KB: Snapshot quiescing fails on Linux guests after upgrading to ESXi and VMware Tools 5.1

[leszakandras · Accepted solution]

Hello everyone,

sorry for delayed update. Thanks for all for the replies, finally the problem was - at least I hope - that we use SRM, and vm names possibly found duplicatedly - and therefore the diskless "vm" get into the backup, but it failed, because it could not be snapshoted. The resolution, or workaround was to check "ignore diskless vms" in the policy vmware advanced settings.

Best regards

Andras