VMware agent backup fails with Status 156 - snapshot error encountered

VMware agent backup fails with Status 156 - snapshot error encountered

  • Article ID:100015239
  • Last Published:
  • Product(s):NetBackup

Problem

VMware backups failing during snapshot job with Status 156.

Error Message

From activity monitor job details -

03/20/2015 09:37:29 - snapshot backup of client <vm_name>.com using method VMware_v2
03/20/2015 09:37:31 - Info bpbrm (pid=1684) INF - vmwareLogger: VmPowerOp: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:37:31 - Info bpbrm (pid=1684) INF - vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode]
03/20/2015 09:37:31 - Info bpbrm (pid=1684) INF - vmwareLogger: SetVmPowerStateAPI: Operation: enableChangeTracking failed
03/20/2015 09:37:31 - Info bpbrm (pid=1684) INF - vmwareLogger: SetVmPowerStateAPI: enableChangeTracking: Error: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:37:34 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:37:47 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:37:57 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:38:07 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:38:20 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:38:30 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:38:40 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:38:53 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:39:03 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:39:13 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:39:26 - Info bpbrm (pid=1684) INF - vmwareLogger: CreateSnapshotExAPI: SYM_VMC_ERROR:  SOAP_ERROR
03/20/2015 09:39:37 - Critical bpbrm (pid=1684) from client <vm_name>: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error
03/20/2015 09:39:37 - Critical bpbrm (pid=1684) from client <vm_name>: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
03/20/2015 09:39:37 - Critical bpbrm (pid=1684) from client <vm_name>: FTL -
03/20/2015 09:39:37 - Critical bpbrm (pid=1684) from client <vm_name>: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
03/20/2015 09:39:37 - Critical bpbrm (pid=1684) from client <vm_name>: FTL -
03/20/2015 09:39:37 - Critical bpbrm (pid=1684) from client <vm_name>: FTL - snapshot processing failed, status 156
03/20/2015 09:39:37 - Critical bpbrm (pid=1684) from client <vm_name>: FTL - snapshot creation failed, status 156
03/20/2015 09:39:37 - Warning bpbrm (pid=1684) from client <vm_name>: WRN - ALL_LOCAL_DRIVES is not frozen
03/20/2015 09:39:37 - Info bpfis (pid=1709) done. status: 156
03/20/2015 09:39:37 - end VMware: Create Snapshot; elapsed time 0:02:11
03/20/2015 09:39:37 - Info bpfis (pid=1709) done. status: 156: snapshot error encountered
 

Cause

The ESXi host where this virtual machine resides is not licensed for vStorage APIs.

Check ESX/ESXi licensing to ensure it is licensed for vStorage APIs for Data Protection (VADP).

This licensing requirement is described in the following VMware article -

vStorage APIs for Data Protection (VADP) FAQ (1021175)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1021175

Where it states:

What licensing is required to use VADP?

The Data Protection APIs are included with all licensed vSphere editions: Standard, Enterprise and Enterprise Plus.

 

Solution

To protect this virtual machine take one of the following two actions:

1.  Add the VMware vStorage APIs for Data Protection (VADP) licensing to the ESX/ESXi host currently hosting this virtual machine.

2.  vMotion or otherwise migrate/move this virtual machine to a properly licensed ESX/ESXi host.


Applies To

NetBackup VMware agent.

Was this content helpful?