Step V:         Completing the integrated bare metal recovery

After you have restored the critical volumes, injected necessary drivers, and successfully rebooted your restored client, use the steps described in this section to complete the recovery.

To complete the integrated bare metal recovery

1        Configure network settings for the restored client. The network settings that you used for the restore in WinPE are not retained when you restore the failed client’s operating system.

Consider the following when configuring network settings for the restored client:

     If you assign it the same IP address as the failed client, the backup system treats it as if it is the original failed client.

     If you are using DHCP to assign IP addresses and you registered the original client to the backup system using only the client’s name, the backup system detects the restored client after you connect it to the network unless you rename it. The backup system then treats the restored client as if it is the original client.

     If the original client is still connected to the network, you must assign the restored client a unique IP address and rename it before connecting to the network to avoid conflicts.

2        If necessary, you can now restore data that resides on non-critical volumes. For details, see Executing a point-in-time restore. To restore data on non-critical volumes from a replication target, see Restoring replicated backups. If all of your data resides on the critical volumes, then it has already been restored.

3        The backup system now protects the restored client using the same settings it used to protect the failed client. Existing backup and archive schedules for the failed client are now applied to the restored client. It is not necessary to create new schedules for the restored client.

Note for Exchange servers: If you are unable to mount Exchange databases after performing the restore, the databases may be in a Dirty Shutdown state. See this Microsoft article for details: Exchange Database is in a Dirty Shutdown State.

Note for Hyper-V servers: After booting the recovered Hyper-V server, you must run the following command on the Hyper-V server: bcdedit /set hypervisorlaunchtype Auto. You should then reboot the server.