VM backup is failing

[john10]

Hi All, NBU VERSION: - 7.6.1 OS - 2012 One of my vm client backup is failing with 156 and Vm team able to create and delete the snaps manually and system writers are also stable on the server side. Error from detail job summary :- Vmware_freeze vixapi freeze (VMware snapshot) failed with 1 - unrecognised error An error occurred while saving the snap shot :failed to quiesce the virtual machine Vfm_freeze Please confirm whether “virtual disk” service is required mandate to start in the server as its in stopped state .

[Michael_G_Ander]

When the VM team is doing the snapshots are they using quiesce file system ? Ask as this in principle what netbackup does

In my experience 99% of snapshot problems are caused by things inside the VM, on Windows systems a problem with the VSS system is usually the culprit

Besides the abovem I have see low available memory, high CPU load, high disk latency cause this kind of problem.

[john10]

Hi Michael, Thanks for your reply. No VMware team is not using to quiesce while creating snapshot . And also Vss writers are stable on box . Coming latency and high I/O utilisation I will once again check with respective teams

[john10]

Hi Michael, When vm team is selecting an option "quiesce file system" snap shot is failing , but only "Sql writers are not stable " on server and wintel restated VMware service also still backup is failing with error code 40 so what would be next troubleshooting steps to fix the issue

[watsons]

1. Check if this is relevant: 

http://www.veritas.com/docs/000021380

2. Since VMware side can create & delete snapshot manually, try this to see if the snapshot creation/deletion works via the API (that NBU is using):

http://www.veritas.com/docs/000042545

[Michael_G_Ander]

"Sql writers are not stable" points to the problem being with the VSS snapshot of the SQL inside the VM, the usually problem is a too small shadow area. The next thing I would look for is memory/resources exhaustion messages in the event logs inside the VM.

[PatS729]

Try re-installing vmware tools on the vm in question.