VMWare backups are hanging or failing with status 41 due to WMI hanging on IsSystemBootedUsingEFIFirmware()
|Article:TECH199036|||||Created: 2012-10-26|||||Updated: 2013-07-01|||||Article URL http://www.symantec.com/docs/TECH199036|
When the VMware Backup Host has a uEFI configured partition, NetBackup has to query Windows Management Instrumentation (WMI) to obtain information about BCD uEFI configured partition. If WMI queries hang or are slow, NetBackup will hang or slow down waiting on a response from WMI.
From the bpbkar log you will see a delay in between the EFI call:
11:05:46.199 PM: [4000.6600] <2> ov_log::V_GlobalLog: INF -IsSystemBootedUsingEFIFirmware() - Enter
11:15:51.557 PM: [4000.6600] <2> ov_log::V_GlobalLog: INF - Boot Manager Path: \EFI\Microsoft\Boot\bootmgfw.efi
8/30/2012 2:57:49 AM - Info bpbrm(pid=11260) starting bpbkar32 on client
8/30/2012 2:57:49 AM - connecting
8/30/2012 2:57:49 AM - connected; connect time: 00:00:00
8/30/2012 3:13:50 AM - end writing
network connection timed out(41)
This issue was seen on a Windows 2008 system with and EFI configured BCD configuration.
The issue is caused by a delay in Windows Management and Instrumentation(WMI). NetBackup waits until WMI responds before moving forward.
The formal resolution for this issue (Etrack 3131436) is included in the following release:
- NetBackup for VMware 7.5 Maintenance Release 6 (184.108.40.206)
NetBackup 220.127.116.11 is now available - please access the Related Article below for more information.
1. Engage Microsoft to identify why a query to WMI is taking so long.
2. Rebuild the Operation System without the EFI partition.
If neither of these workarounds are feasible, please contact Symantec technical support, referencing this document and Etrack 3131418 to obtain an Emergency Engineering Binary (EEB) bundle for NetBackup 18.104.22.168 containing a fix for this issue.
VMware backups are hanging on EFI information
Article URL http://www.symantec.com/docs/TECH199036