Highlighted

VMware backup

HI All,

In our backup enviorment we are facing Error code 156 and Error code 6 , for the VMware backup currently we are using VMware query based policy but few of our clients are failing when ever we enabled the quiesce the VM , 6 month back Symantec suggested we need to upgrade all Virtual Machine , vmare tools to version 10.1.x or later , now even we upgraded all our VM , vmware tools but sill facing this kind of issue .

 

Kindly let us know is there any patch is avilable my current NBU version is 7.6.1

Tags (3)
7 Replies

Re: VMware backup

This is not a VERITAS issue to fix.  If you VMs are failing to snapshot with quiesce enabled, that means that vCenter would also fail to snapshot the VM if you select the File System Quiesce option only in vCenter.

NetBackup doesn't Snapshot the VM, we request the vCenter perform this task.

https://www.veritas.com/support/en_US/article.000042545

If you are using VERITAS VSS Provider, there is an issue with the new vmware tools version that might cause VERITAS VSS Provider to fail.  So I suggest switching to VMware VSS Provider and working with VMware to address why it is failing.

https://kb.vmware.com/kb/2149640

Re: VMware backup

Hi @RohitNayal

Tell us more about your environment.

Are your Master Server in 7.6.1 version?
Are your VM backup Host in 7.6.1 version?
Whats S.O of your VM backup Host? Linux/Windows?
Whats your Vsphere version?
Whats your transport mode type? san? nbd?

About VMware tools is important to update it,but as you said that all VMs are updated, we need to find other things. I've seen status code 6 associated to the transport mode. Post here Detailed status of Job to start.

 

Regards,

 

Thiago

Re: VMware backup

There is no patch available for 7.6.x as this version reached EOSL more than 6 months ago.

Re: VMware backup

Appology I have mentioed the wrong NBU Verison 

 

Are your Master Server in 7.6.1 version?

NBU 7.7.3

Are your VM backup Host in 7.6.1 version?

NBU 7.7.3
Whats S.O of your VM backup Host? Linux/Windows?

x86_64 x86_64 x86_64 GNU/Linux


Whats your Vsphere version?

Vsphere Version 6.3


Whats your transport mode type? san? nbd?

nbd

Re: VMware backup

Hi,

Thanks for answer..Did you check the TCP ports  443 and 902 from VMware backup Host and Esx Hosts are opened?

The vmware backup host should be able to connect to this TCP ports. If you have doubts, take a look this TNs.

https://vox.veritas.com/t5/Netting-Out-NetBackup/Nuts-and-bolts-in-NetBackup-for-VMware-Transport-me...

https://www.veritas.com/support/en_US/article.TECH183072

 

Regards,

 

Thiago

Re: VMware backup

As the others have specified, status 156 and status 6 on vmware backups are issues with the vm or the vmware environment, not with netbackup.

Netbackup will communicate with the vcenter and instruct vcenter to snapshot the machine, after which the underlying vmdk files are backed up. 

Status 156 means that there is a snapshot failure. The cause of this can vary with every machine and at every time. For troubleshooting purposes you can try to take a manual snapshot with quiescing enabled. If this fails as well, you should take a look at the eventlogs on the vm itself, which can contain useful information about your issue. Keep an eye out for vss errors, and take a look at the vss writer state as well (vssadmin list writers). If any of those are failed you may want to reset the writers by restarting the corresponding services (more information on which writer and which service correspond can be found on: http://www.planetcobalt.net/sdb/vss_writers.shtml)

Status 6 usually means that the snapshot has been correctly taken, but the files cannot be accessed by netbackup. Again, this can happen for various reasons, but usually this means that the datastore cannot be accessed by your mediaservers. If using SAN as a transport mode, this usually means that the LUN is not accessible (zoning?) to your backup environment. If using LAN, this usually means that there is a firewall or port issue. 

I hope this has shed some more light on your issue.

Re: VMware backup

Hi 

if you are getting alerts for quiescing, then try a non-quiesced snapshot from Vmware, if it works then it has nothing to do with NBU, then check with VMWARE, if it fails then check bpfis and vxms logging in Netbackup.

ALso ensure port 902 & 443 is opened on ESXI and VCenter for backup host.

VXMS logging can shed more light in to the issue. ENter line VMXS_VERBOSE= 3 in bp.conf of backup host and create vxms folder under /usr/openv/netbackup/logs

Post your VXMS logs here.