12-27-2015 03:05 PM
Hi All,
Sorry this is a repost from a few days ago, not sure how but I mistakenly deleted two duplicated posts on this thread.
We have a vm backup just recently put on the backup scheduled that is getting the 156 error code. It has been getting the code from the start therefore no
backup has successfully completed (full or incremental).
Here is some answers to questions that I believe was posted before I deleted the two duplicate threads.
What is the Policy type? VMware policy
What do you have in Backup Selection in the Policy? All local drives
This machine was rebooted and has vm tools up until recently it was backing up as a physical machine.
It is a Windows 2003 R2 machine
The bpfis log, the bpcd log and the vssadmin writers command have been attached.
Solved! Go to Solution.
12-27-2015 09:07 PM
12-27-2015 08:46 PM
Does it create the snapshot for the vm or not?
Also, have you selected any of the "Application backup" boxes on the VMware TAB in the policy?
12-27-2015 09:07 PM
01-03-2016 04:06 PM
Thanks Riaan and Marianne for your replies.
Riaan, no snapshot is created and no "Application backup" boxes on the VMware TAB in the policy are checked.
Marianne, I checked the TN still trying to troubleshoot
FYI - Trying to understand VM more
Best Regards
01-03-2016 07:33 PM
01-03-2016 11:07 PM
Hi,
As Marianne stated, please check with the VM team and try to create a snapshot. From the logs you can see its waiting for one hour to obtain a VSS Snapshot lock. 1 hour is the default but I can't see how increasing it beyond that would make a difference.
You could try the disable the quiescing of the client and see if you get a backup through that way but then you'll have a crash consistent backup only.
00:00:31.657 [9804.2628] <4> bpfis main: read_registry_dw_value for VSS_CONCURRENT_OPERATIONS: return status 2, return value 0 01:00:31.841 [9804.2628] <16> bpfis main: Failed to get VSS Snapshot Mutex lock!!
01-04-2016 06:38 AM
I would look in the system and application event logs for clues to the OS not been able to create VSS snapshot(s), the usual culprit is a too small shadow copy area.
Unfortunately VSS things are not always written in the event log.
Other problems I have seen cause no snapshot in windows is memory exhaustion and very high CPU load, unformat drives
01-05-2016 06:21 AM
Thanks Marianne, Rianne and Micheal,
I checked with the VM admin he said there is no backup nic available on vmware host that may be the problem. Not exactly sure what that means as far as the error I will work with the VM admins further.
Micheal, I checked the system and application event logs however I didn't see anything unusual.
Best Regards
01-05-2016 01:01 PM
01-07-2016 12:29 AM
Hi,
Did you try to take VMware Snapshot of the server in question...? Please do that first.. Try with both options (with and without quiescing option)
If the snapshot doesnt work in the Vmware level itself, netbackup will not be able to take snapshots as well.
01-12-2016 08:20 AM
Thanks for all your responses!
We are still working on the issue with the VM admins, The VM admin was able to take a VMware Snapshot.
Best Regards
01-12-2016 08:57 AM
1) vmx version of the VM?
2) VMtools version inside the guest?
3) Guest OS Windows 2003 R2 is 64-bit, correct?
4) Is this guest a P2V?
5) Did both manual snapshot styles work? You were asked to try with quiesce and without quiesce. Did both work?
02-21-2016 02:27 PM
Thanks,
The end result (for now) we did below this for the vm client
Install a NetBackup client on the virtual machine and select another backup method for the policy (not the VMware snapshot method).
Best Regards to everyone!