After upgrade to NetBackup 7.x, VMWare clients with multiple IP addresses are failing with status 156

Article:TECH130452  |  Created: 2010-01-24  |  Updated: 2011-05-20  |  Article URL http://www.symantec.com/docs/TECH130452
Article Type
Technical Solution



Issue



After upgrade to NetBackup 7.x, VMWare clients with multiple IP addresses are failing with status 156.

 


Error



From bpfis:

13:58:11.273 [6300.6616] <2> logparams: D:\Program Files\Veritas\NetBackup\bin\bpfis.exe create -nbu -owner NBU -id vmclient.symantec.com_1273859886 -bpstart_to 300 -bpend_to 300 -backup_copy 0 -ru root -pt 29 -vm_type 2 -vm_client vmclient.symantec.com -clnt pine -st FULL -rg root -fim VMware:mntpt=G:\mnt,trantype=0,Virtual_machine_backup=2,disable_quiesce=0,vmdktype=0,nameuse=0 -class ITSS-pine-vm04 -sched Full -fso -S walleye
13:58:11.273 [6300.6616] <2> bpfis main: received FIM as [94] VMware:mntpt=G:\mnt,trantype=0,Virtual_machine_backup=2,disable_quiesce=0,vmdktype=0,nameuse=0
13:58:11.304 [6300.6616] <4> bpfis: INF - BACKUP START 6300
13:58:11.304 [6300.6616] <2> bpfis main: receive filelist:<NEW_STREAM>
13:58:11.320 [6300.6616] <2> bpfis main: receive filelist:<ALL_LOCAL_DRIVES>
13:58:11.320 [6300.6616] <2> bpfis main: receive filelist:<CONTINUE>
13:58:11.507 [6300.6616] <2> vnet_connect_to_vnetd_extra: ../../libvlibs/vnet_vnetd.c.188: msg: VNETD CONNECT FROM 172.30.219.100.1441 TO 172.30.217.195.13724 fd = 1408
13:58:11.523 [6300.6616] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2054: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
13:58:11.523 [6300.6616] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2068: service: bprd
13:58:11.539 [6300.6616] <2> logconnections: BPRD CONNECT FROM 172.30.219.100.1441 TO 172.30.217.195.13724
13:58:11.976 [6300.6616] <8> bpfis: WRN - VfMS error 10; see following messages:
13:58:11.976 [6300.6616] <8> bpfis: WRN - Non-fatal method error was reported
13:58:11.976 [6300.6616] <8> bpfis: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init
13:58:11.976 [6300.6616] <8> bpfis: WRN - VfMS method error 3; see following message:
13:58:11.976 [6300.6616] <8> bpfis: WRN - FlashSnap_init: Veritas Volume Manager not installed.
13:58:11.992 [6300.6616] <8> bpfis: WRN - VfMS error 10; see following messages:
13:58:11.992 [6300.6616] <8> bpfis: WRN - Non-fatal method error was reported
13:58:11.992 [6300.6616] <8> bpfis: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init
13:58:11.992 [6300.6616] <8> bpfis: WRN - VfMS method error 3; see following message:
13:58:11.992 [6300.6616] <8> bpfis: WRN - vxvm_init: Veritas Volume Manager not installed.
13:58:12.398 [6300.6616] <4> bpfis: INF - FIS_ID=vmclient.symantec.com_1273859886
13:58:12.398 [6300.6616] <4> bpfis: INF - Freezing ALL_LOCAL_DRIVES using snapshot method VMware.
13:58:12.398 [6300.6616] <4> bpfis: INF - ACT=vmclient.symantec.com
13:58:12.398 [6300.6616] <4> bpfis: INF - Created mount point D:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_ALL_LOCAL_DRIVES_6300
13:58:12.414 [6300.6616] <2> vnet_connect_to_vnetd_extra: ../../libvlibs/vnet_vnetd.c.188: msg: VNETD CONNECT FROM 172.30.219.100.1442 TO 172.30.217.195.13724 fd = 1340
13:58:12.445 [6300.6616] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2054: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
13:58:12.445 [6300.6616] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2068: service: bprd
13:58:12.445 [6300.6616] <2> logconnections: BPRD CONNECT FROM 172.30.219.100.1442 TO 172.30.217.195.13724
13:58:15.164 [6300.6616] <4> bpfis: INF - Deleted mount point D:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_ALL_LOCAL_DRIVES_6300
13:58:15.164 [6300.6616] <32> bpfis: FTL - VfMS error 11; see following messages:
13:58:15.164 [6300.6616] <32> bpfis: FTL - Fatal method error was reported
13:58:15.164 [6300.6616] <32> bpfis: FTL - vfm_freeze: method: VMware, type: FIM, function: VMware_freeze
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
13:58:15.164 [6300.6616] <32> bpfis: FTL - VfMS error 11; see following messages:
13:58:15.164 [6300.6616] <32> bpfis: FTL - Fatal method error was reported
13:58:15.164 [6300.6616] <32> bpfis: FTL - vfm_freeze: method: VMware, type: FIM, function: VMware_freeze
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
13:58:15.164 [6300.6616] <16> bpfis: FTL - snapshot creation failed, status 156
13:58:15.164 [6300.6616] <4> bpfis: INF - Thawing ALL_LOCAL_DRIVES using snapshot method VMware.
13:58:15.164 [6300.6616] <8> bpfis: WRN - ALL_LOCAL_DRIVES is not frozen
13:58:15.164 [6300.6616] <8> bpfis: WRN - snapshot delete returned status 20
13:58:15.164 [6300.6616] <2> vnet_connect_to_vnetd_extra: ../../libvlibs/vnet_vnetd.c.188: msg: VNETD CONNECT FROM 172.30.219.100.1447 TO 172.30.217.195.13724 fd = 1404
13:58:15.179 [6300.6616] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2054: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
13:58:15.179 [6300.6616] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2068: service: bprd
13:58:15.179 [6300.6616] <2> logconnections: BPRD CONNECT FROM 172.30.219.100.1447 TO 172.30.217.195.13724
13:58:15.929 [6300.6616] <4> bpfis: INF - EXIT STATUS 156: snapshot error encountered 
 
 


Cause



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.


Solution



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
\HKEY_LOCAL_MACHINE\SOFTWARE\NetBackup\VERITAS\CurrentVersion\Config\BACKUP\useVMhostname.

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.

 

 



Legacy ID



354770


Article URL http://www.symantec.com/docs/TECH130452


Terms of use for this information are found in Legal Notices