My environment: NBU 7 - windows server 2008 x64
14:57:06.612 [12852.3776] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe create -nbu -owner NBU -id glseccprd03.ag.ad.local_1385391426 -bpstart_to 300 -bpend_to 300 -backup_copy 0 -ru root -pt 29 -vm_type 2 -vm_client glseccprd03.ag.ad.local -clnt gbstbck01.ag.ad.local -st FULL -rg other -fim VMware:nameuse=0,Virtual_machine_backup=2,trantype=0,disable_quiesce=1,file_system_optimization=1,snapact=2,vmmono=0,nameuse=0 -class ST1_WSYVCBT21_DLY -sched ST1_VCB2100_DLY -fso -S gbstbck01.ag.ad.local
Solved! Go to Solution.
Hi Aman ,
When a virtual machine has multiple IP addresses, sometimes the vStorage API might not return the IP address expected. Thus the snapshot will fail because the IP address does not translate to the name of the virtual machine in the policy.
Provided engineering binary for Etrack 2024766 and created the appropriate registry key to workaround this issue. The fix can also be found in later versions of the binary bundles.
Enumeration and backups will check for the existence of a registry entry
If found, the VM hostname returned from the vADP will be used instead of a reverse IP lookup in the IP address returned. After adding the registry entry, the policy clients will have to be redone after a rebuild of the VM cache.
Nagalla, I am not too sure that this is related. The error seems to differ in the link
13:58:15.164 [6300.6616] <32> bpfis: FTL - VfMS method error 7; see following message:
13:58:15.164 [6300.6616] <32> bpfis: FTL - VMware_freeze: Unable to locate VM vmclient.symantec.com
Where as my issue has a different error
It may help you please verify this below link :
The IP address was set to dynamic.
Change the IP address to Static
Please keep us posted..
Does this backup ever worked....?
if not, you need to check the credentials and permissions...
if you are not sure about the permissions, try to create a snaphost by loggin into Vcenter using the same user id that is used in netbackup configurations.
Hi Aman ,
Another method to see what error actually happen for code 156 is to login directly to vm host via vsphere client before you run backup job. There you can see what error occur that make the job fail with error 156.
My usual troubleshooting list for a 156 error...
- Are any of the drives on the VM out of space?
- Does the VM have high IO at the time of backup?
- Does the VM have any raw disks?
- Are there VSS errors on the VM? - vssadmin list writers
- Are there excessive delta files in the datastore?
- Is the datastore out of space?
- Turn off quiescing and take a backup, does the backup work?
- Take a snapshot from vCentre, does it work?
- Migrate the VM and backup again
- Reboot the VM