Recipe11.9.Performing Disaster Recovery of a Cluster Node to a Nonclustered Server

Recipe 11.9. Performing Disaster Recovery of a Cluster Node to a Nonclustered Server

Problem

Your clustered Exchange server is down. While you restore it, you want to offer service using its databases on a regular, unclustered node.

Solution

Using a graphical user interface

1. Use ADSI Edit to remove the cluster's AD object:

   1. Launch ADSIEdit.msc.

   2. Expand the forest configuration container.

   3. Expand the container for the administrative group that contains the clustered server (it'll be located under CN=Services, CN=Microsoft Exchange, CN=Administrative Groups).

   4. Expand the Servers container in the AG.

   5. Right-click on the target server and use the Delete command. When ADSI Edit prompts you to confirm the deletion, click Yes.

2. Remove mailbox attributes from the user accounts whose mailboxes were on the former server:

   1. On the Exchange server or on a computer with the Exchange Management tools installed, launch the ADUC snap-in.

   2. Make sure that the advanced features mode is on (use the View Advanced Features command to toggle it if necessary).

   3. Select the users whose mailbox attributes you want to remove. You can select them one at a time or by using the standard Windows selection modifier keys.

   4. Right-click the user and use the Exchange Tasks command to start the Exchange Task Wizard.

   5. In the Available Tasks window, select Remove Exchange Attributes and click Next.

   6. In the Remove Exchange Attributes window, click Next to indicate your understanding of the tool's dire warnings.

   7. Click Finish.

3. Build the new server, using the same name as the cluster's virtual server and the same version (and service pack level) of Windows.

4. Install Exchange on the new server, but don't use the /disasterrecovery switch.

5. After Exchange is installed, create storage groups and databases whose names and locations match what was on the original server.

6. Restore your databases from a backup (or copying them from the original server or SAN).

7. Mount the databases and check the event log to verify that there were no errors.

8. Reconnect the restored mailboxes to their users using the Mbconn utility (described in Recipe 11.13).

Discussion

While it's rare that you'll want to restore a database from a clustered server to a non-clustered server, the need to do so might occur, especially in cases where you simply do not have enough hardware to replace your clustered servers. Whenever possible, it's best to restore Exchange databases to the original hardware configuration they used.