01-13-2012 02:57 PM
My VM backup is failing with 156.
When i run the VM backup with DNS name the snap fails with the below error
01/13/2012 14:30:50 - Critical bpbrm (pid=16745) from client Clientname.com: FTL - snapshot creation failed, status 156
01/13/2012 14:30:50 - Warning bpbrm (pid=16745) from client clientname.com: WRN - ALL_LOCAL_DRIVES is not frozen
01/13/2012 14:30:50 - Info bpfis (pid=7948) done. status: 156
But when i change the setting to run with the display name its snaps and backup got completed successfully.
Can any one tell me how to fix the VM to run with the DNS name.
Solved! Go to Solution.
06-13-2012 10:57 PM
When i discovered the VM, there was 2 entry with the same DNS name, which was conflicting.
I deleted the power off'd VM and the VM backup started to work again successfully with the DNS name.
01-14-2012 08:00 AM
Are you typing the DNS name in manually or are you letting the Browse for Virtual Machine determine the DNS name.
Create a new policy, set the Snapshot options to DNS name. Then perform a browse for virtual machine and select the VMs you would like to backup. This will select the correct DNS name, and the snapshots should work.
If you configured the backups with Display name first and then switch it to DNS name, you must delete the clients from the policy and re-add them as DNS name.
01-15-2012 10:32 PM
Still the snap is failing with the DNS name.
01-16-2012 07:05 AM
However the strategy of using DNS name associated with the IP addresses for virtual machines may not be suitable for certain environments ...
01-19-2012 10:14 PM
we are using NBU 7.1. Is there any update that we can provide to VMware or wintel team to check from their end on why the snap is not happening if we are using the DNS name for backup
06-13-2012 10:57 PM
When i discovered the VM, there was 2 entry with the same DNS name, which was conflicting.
I deleted the power off'd VM and the VM backup started to work again successfully with the DNS name.