Getting status 11 or status 13 on hyper-v backups or VMware Backups.

Article:TECH73597  |  Created: 2009-01-17  |  Updated: 2011-09-23  |  Article URL http://www.symantec.com/docs/TECH73597
Article Type
Technical Solution


Issue



Getting status 11 or status 13 on hyper-v backups or VMware Backups


Error



Getting the following error message(s) while running backups of Hyper-V virtual machines:

"ERR - FIML_initialize_vxms failed (15)"
"ERR - FIML_initialize_vxms failed (14)"

The following log entries are seen in the bpbkar log on the Hyper-V host:

12:15:58.189 PM: [3476.4624] <4> tar_base::V_vTarMsgW: INF - tar message received from vxms_vfm_start
12:15:58.189 PM: [3476.4624] <2> tar_base::V_vTarMsgW: INF - FIML initialize
12:15:58.189 PM: [3476.4624] <4> tar_base::V_vTarMsgW: INF - tar message received from vxms_vfm_start
12:15:58.189 PM: [3476.4624] <2> tar_base::V_vTarMsgW: ERR - FIML_initialize_vxms failed (14)
12:15:58.189 PM: [3476.4624] <4> tar_backup::backup_done_state: INF - number of file directives not found: 0
12:15:58.189 PM: [3476.4624] <4> tar_backup::backup_done_state: INF - number of file directives found: 1
12:15:58.189 PM: [3476.4624] <2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup
12:15:58.189 PM: [3476.4624] <4> tar_base::stopKeepaliveThread: INF - waiting for keepalive thread to exit ...
12:15:58.189 PM: [3476.4624] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
12:15:58.189 PM: [3476.4624] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 11: system call failed
 

Cause



The errors above as well as the log entry show a failure to initialize the VxMS binaries.

The errors can be traced to a registry entry that specifies an incorrect location for the VxMS binaries.

Registry location on 64 bit systems:
HKLM\SOFTWARE\VERITAS\VxMS\InstallDir64

Registry location on 32 bit systems:
HKLM\SOFTWARE\VERITAS\VxMS\InstallDir32

By default, the VxMS binaries are located here:
C:\Program Files\Common Files\VERITAS\VxMS\

In the example logged above, the value for the above registry entry was "V:\"

NOTE: Observe the trailing "\" on the above path. This is required, otherwise the backup will continue to fail with status 11.

Once the corresponding Registry key is corrected, the backups should began to run correctly.

This issue can occur for any Flashbackup policy type, including Hyper-V and VMware backups.
It can also occur for Flashbackup restores.
 


Solution



On the Vmware Backup Host or on the Hyper-V host, correct the "HKLM\SOFTWARE\VERITAS\VxMS\InstallDir64" registry value to point to the correct location for the VxMS binaries.


Legacy ID



329906


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


Terms of use for this information are found in Legal Notices