Loading...
Loading...
The Avamar Bare Metal Recovery (BMR) Wizard stops progressing after entry of Avamar server credentials and account details. The wizard remains at retrieving critical volumes in backup for an extended period. The avtar debug log shows activity related to volume enumeration without completion. [avtar] utar_commands::do_restore Building mount points list for all volumes on the system [ade-async] GComMgr::check_all_link_health() -- sending ping every 1800 seconds. [ade-async] servercontext::sendPingToAll(): dpninx=0, connections=1 [ade-async] servercontext::sendPingToAll(): done [ade-async] async: dropping response, message DPNPING=216 serial=4 seq=0 flags=R:N:0 kind=0 rsp=MSG_ERR_NONE
The avtar process stops responding during a Windows operating system API call. Avtar calls ::GetDriveType() from winInfo::get_local_drives() to identify volume types. Each ::GetDriveType() call takes several minutes to return. Avtar processes each disk sequentially. Systems with many disks encounter excessive delays, which cause the wizard to appear to stop responding.
Power off the target Windows server. Detach all noncritical disks from the system. Keep only operating system disks and critical volumes attached. Launch the Avamar Bare Metal Recovery Wizard. Complete the BMR operation. Reattach the detached disks after recovery completes. Important Windows rarely identifies many disks as critical. If the operating system identifies many disks as critical, contact Dell Support .
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.