Dell EMC Avamar for Windows Servers 19.7 User Guide

After the BMR completes and the system restarts, perform these required tasks:

• If a critical volume was compressed, then reenable compression.
• If you performed a P2V restore, then perform the following steps:
  1. Install VMware tools.
  2. Remove disabled devices.
  3. Configure the virtual NIC.
• Check the disk and volume configuration of the host. All disks and volumes likely appear as they did on the original system. However, if disk signatures do not match the original disks, then non-critical disks may be offline or not mounted. Use Microsoft Disk Manager to bring the disks online or mount the disks. After the disks are online, restart the host to reassign disk drive letters, or assign drive letters to non-critical disks as necessary. Non-critical volumes that are accessed by mount points may have similar issues.
• If required, import disks so that they are known by Windows Storage Manager.
• If required, use the Avamar Plug-in for the Windows File System to restore application data or non-critical disks. If you use an application plug-in, such as the Avamar Plug-in for Exchange VSS or the Avamar Plug-in for SQL Server, then use the application plug-in to restore the application data.

• When a Windows Server 2008 or Windows Server 2019, 2016, or 2012 role uses SQL Server instances instead of the WID, then perform the SQL Server disaster recovery steps:

  1. Complete the SQL Server disaster recovery procedure that Microsoft recommends in the MSDN article “Recovering from a Disaster.”
  2. Install the Avamar Plug-in for SQL Server.
  3. Use the Avamar Plug-in for SQL Server to restore the system databases.
  4. Use the Avamar Plug-in for SQL Server to restore the SQL Server instances.

  The Avamar for SQL Server User Guide provides instructions for installing and using the SQL Server plug-in.

• The Active Directory RMS service depends on the Microsoft Message Queuing Service (MSMQ). If an Active Directory service does not restart after BMR, verify whether MSMQ is a service on the system and determine if the service restarted correctly. You can also check the Windows Event Application Log to see if MSMQ recorded Event 2078, The Message Queuing service cannot start.

  If MSMQ is enabled but did not start on reboot, then restart the service, as described is the “Event ID 2078 -- Message Queuing Logging and Checkpoint Events” article on the Microsoft TechNet website.

• When you mount a volume on a parent volume and the mounted volume becomes a critical volume, then the BMR restores only the critical volume. Use the Avamar Plug-in for the Windows File System to restore the parent volume after the BMR of the critical volume. File System Restore provides instructions.