cancel
Showing results for 
Search instead for 
Did you mean: 

Error 156 and 4207

Mastana420
Level 5

Hi

 

I am encountering an error in Netbackup with the VmWare snapshot. Had a peak and i find 2 errors, 156 which is generally an error getting the snapshot, and the another error which says the following:

Critical bpbrm (pid=35437) from client SVVTPOBBE03: FTL - cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.SVVTPOBBE03_1436968819.1.0

 

What i dont understand is that this client is a Windows 2008 server, why is it looking up for the state file in /usr/openv...... location? Sins this client is a windows server, it should have been looking for this state file in something similar to C:/programfiles........ location.

 

Will appreciate help here. Thanks.

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

The error you found is a 'red herring'. 

You need to troubleshoot reason for failed snapshot.

What is ESX/vShpere version?
Can you perform VMware snapshot?

Is vmtools installed in the VM?

Are there any RDMs on this VM?

Have a look at this TN for possible reasons for VMware snapshot failures:

NetBackup for VMware status 156 
http://www.symantec.com/docs/HOWTO70949

 

View solution in original post

Mastana420
Level 5

Seems like it is working now. Did not do anything spesific, but seems it fixed by itself. Giving credit to Marianne for giving good suggestions.

 

 

View solution in original post

8 REPLIES 8

sdo
Moderator
Moderator
Partner    VIP    Certified
Would you be able to post the activity monitor job log please?

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Does the snapshot complete and then the backup job fails? Or does the snapshot not work at all. That would determine which log to look at. BPFIS or VXMS

Marianne
Level 6
Partner    VIP    Accredited Certified

The error you found is a 'red herring'. 

You need to troubleshoot reason for failed snapshot.

What is ESX/vShpere version?
Can you perform VMware snapshot?

Is vmtools installed in the VM?

Are there any RDMs on this VM?

Have a look at this TN for possible reasons for VMware snapshot failures:

NetBackup for VMware status 156 
http://www.symantec.com/docs/HOWTO70949

 

Mastana420
Level 5

Hi 

 

Here is the entire job log from Activity Monitor.

 

We are running version 5.5 on Esx\Vsphere. VmTools are installed and we have snapshot allowed since we have multiple other servers having snapshot run on a daily basis. 

 

My understanding is that we are not utilizing the RDM on VmWare.

 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

You will notice that the TN is listing more possible reasons that the ones I have listed (e.g. The attempt to create a snapshot exceeded the VMware timeout). 

VMware error received: An error occurred while quiescing the virtual machine. See the virtual machine's event log for details.

Have you checked the VMs Event log as per the message above?

Have you checked vSphere event logs while snapshot is attempted?

Have you enabled logs on the Backup Host as per Riaan's advice?

 

 

 

Mastana420
Level 5

 

Hi.

 

VMs event log did not show anything spesific apart from services having multiple attempts to start and stop. 

Vsphere eventlog on the other hand is clearly showing errors, as follows:

  • An error occured while quiescing the virtual machine, see the virtual machines even log for details:

And here is what it shows in detail:

  • The guest OS has reported an error during quiescing. The error code was: 5 The error message was: 'VssSyncStart' operation failed: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (0x80070422) 

I have not yet enable any logs yet on the Backup host.

 

 

 

revarooo
Level 6
Employee

This is a VMWare issue not NetBackup.

quiescing is NOT performed by NetBackup. Try snapshotting this VMware from the Vsphere client

Mastana420
Level 5

Seems like it is working now. Did not do anything spesific, but seems it fixed by itself. Giving credit to Marianne for giving good suggestions.