01-21-2019 04:31 PM
Me too facing similar error.
Need help
1/21/2019 18:54:34 - begin Parent Job
01/21/2019 18:54:34 - begin Application Snapshot: Step By Condition
Operation Status: 0
01/21/2019 18:54:34 - end Application Snapshot: Step By Condition; elapsed time 0:00:00
01/21/2019 18:54:34 - begin Application Snapshot: Read File List
Operation Status: 0
01/21/2019 18:54:34 - end Application Snapshot: Read File List; elapsed time 0:00:00
01/21/2019 18:54:34 - begin Application Snapshot: Create Snapshot
01/21/2019 18:54:35 - started process bpbrm (pid=109605)
01/21/2019 18:54:36 - Info bpbrm (pid=109605) SUD04 is the host to backup data from
01/21/2019 18:54:36 - Info bpbrm (pid=109605) reading file list for client
01/21/2019 18:54:36 - Info bpbrm (pid=109605) start bpfis on client
01/21/2019 18:54:36 - Info bpbrm (pid=109605) Starting create snapshot processing
01/21/2019 18:54:37 - Info bpfis (pid=109648) Backup started
01/21/2019 18:54:37 - snapshot backup of client SUD04 using method VMware_v2
01/21/2019 18:56:45 - Info bpbrm (pid=109605) INF - vmwareLogger: RegisterExtensionAPI: SYM_VMC_ERROR: SOAP_ERROR
01/21/2019 18:56:45 - Info bpbrm (pid=109605) INF - vmwareLogger: SOAP 1.1 fault: "":ServerFaultCode [no subcode]
01/21/2019 18:56:45 - Critical bpbrm (pid=109605) from client SUD04: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
01/21/2019 18:56:45 - Critical bpbrm (pid=109605) from client SUD04: FTL -
01/21/2019 18:56:45 - Critical bpbrm (pid=109605) from client SUD04: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze
01/21/2019 18:56:46 - Critical bpbrm (pid=109605) from client SUD04: FTL -
01/21/2019 18:56:46 - Critical bpbrm (pid=109605) from client SUD04: FTL - snapshot processing failed, status 156
01/21/2019 18:56:46 - Critical bpbrm (pid=109605) from client SUD04: FTL - snapshot creation failed, status 156
01/21/2019 18:56:46 - Warning bpbrm (pid=109605) from client SUD04: WRN - ALL_LOCAL_DRIVES is not frozen
01/21/2019 18:56:46 - Info bpfis (pid=109648) done. status: 156
01/21/2019 18:56:46 - end Application Snapshot: Create Snapshot; elapsed time 0:02:12
01/21/2019 18:56:46 - Info bpfis (pid=109648) done. status: 156: snapshot error encountered
01/21/2019 18:56:46 - end writing
Operation Status: 156
01/21/2019 18:56:46 - end Parent Job; elapsed time 0:02:12
01/21/2019 18:56:46 - begin Application Snapshot: Stop On Error
Operation Status: 0
01/21/2019 18:56:46 - end Application Snapshot: Stop On Error; elapsed time 0:00:00
01/21/2019 18:56:46 - begin Application Snapshot: Cleanup Resources
01/21/2019 18:56:46 - end Application Snapshot: Cleanup Resources; elapsed time 0:00:00
01/21/2019 18:56:46 - begin Application Snapshot: Delete Snapshot
01/21/2019 18:56:47 - started process bpbrm (pid=112069)
01/21/2019 18:56:48 - Info bpbrm (pid=112069) Starting delete snapshot processing
01/21/2019 18:56:48 - Info bpfis (pid=112088) Backup started
01/21/2019 18:56:48 - Warning bpbrm (pid=112069) from client SUD04: cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.SUD04_1548057274.1.0
01/21/2019 18:56:48 - Info bpfis (pid=112088) done. status: 4207
01/21/2019 18:56:48 - end Application Snapshot: Delete Snapshot; elapsed time 0:00:02
01/21/2019 18:56:48 - Info bpfis (pid=112088) done. status: 4207: Could not fetch snapshot metadata or state files
01/21/2019 18:56:48 - end writing
Operation Status: 4207
Operation Status: 156
* NO RDM mapped
01-21-2019 10:45 PM
I have moved your comment in this discussion to a new post as each situation is potentially different.
Do you have bpfis log on the backup host?
Which OS and filesystem type(s) on the failing VM?
Can you take a snapshot of the failing VM from VMware?
Is vmtools installed?
Herewith possible reasons for snapshot failure:
https://www.veritas.com/content/support/en_US/doc/21902280-133434834-0/v109940494-133434834
https://www.veritas.com/content/support/en_US/doc/21902280-133434834-0/v37089113-133434834
https://www.veritas.com/support/en_US/article.100024559.html