Restoring your Exchange environment

This topic describes the recovery from catastrophic loss of a SnapManager for Exchange environment:

Overview

The following paragraphs outline the process of recovering from catastrophic loss of a SnapManager for Exchange environment.

Exchange environment recovery processes

Recovery from catastrophic loss of an Exchange environment that integrates SnapManager for Microsoft Exchange and NetApp storage systems is outlined in the following process.

Task	Process
1	Recovering the Windows environment All procedures in this document assume that you already recovered your Windows environment. For more information about recovering your Windows environment, see the Microsoft documentation listed in Guides you should read and have at hand.
2	Recovering the Exchange server This process is performed using the backup application you used to back up the Exchange server.
3	Recovering the Exchange databases This process is performed using SnapManager for Microsoft Exchange.

Task

Process

Recovering the Windows environment

All procedures in this document assume that you already recovered your Windows environment.

For more information about recovering your Windows environment, see the Microsoft documentation listed in Guides you should read and have at hand.

Recovering the Exchange server

This process is performed using the backup application you used to back up the Exchange server.

Recovering the Exchange databases

This process is performed using SnapManager for Microsoft Exchange.

A SnapManager for Exchange restore from archive operation should be considered a "point-in-time" restore

A SnapManager for Exchange restore from archive operation is typically considered a point-in-time restore based on the time that the backup was created by SnapManager, regardless of whether the "Up-to-the-minute restore" option or the "Point-in-time restore" option was selected on the SnapManager Restore tab.

For a SnapManager up-to-the-minute restore operation to successfully restore an Exchange database up to the point of failure, a contiguous set of Exchange transaction log files that were generated between the time that the archived backup set was created and the time that the failure occurred would need to be available to SnapManager. This means that all SnapManager backups taken after the archived backup was created need to be online and available, in addition to any transaction logs that were generated between the time of the most recent SnapManager backup and the time of the failure.

The reason that a restore from archive is considered a point-in-time restore is that a restore from archive operation is typically performed when none of the SnapManager online backups are available or usable. Selecting the "Up-to-the-minute restore" option instructs SnapManager to use any contiguous log files that it can find to perform the restore. If it does not find any logs in addition to the logs captured by the backup which is being restored, then the restore will still succeed. The SnapManager restore report that is generated as part of the restore operation will include the file names of the Exchange transaction log files that were restored.

Rules and guidelines for disaster recovery

Before you perform disaster recovery using SnapManager for Microsoft Exchange, make sure that you understand the following rules and guidelines:

If you archive only your database LUNs (and not the LUN containing the transaction logs), you will only be able to perform a point-in-time restore. The Exchange databases will be restored back to the time when the backup was created. Changes made to the databases after this time cannot be recovered.
If you archive and restore your transaction log LUN along with the database LUNs, and the transaction log LUN contains transaction logs that accumulated after the archived backup was created, then you have the option of selecting an up-to-the-minute restore. In this case, the database would be restored up to the time when the archive was created. Changes made to the database after the archive was created cannot be recovered.
If you are using SnapMirror, you can use an up-to-the-minute restore to restore your databases to the point in time of the last SnapMirror replication to the target volume containing the transaction logs LUN.
If you are restoring from an archive, the LUN files from the archive must be restored into their original location in the active file system of the storage system's volume.
The drive letters assigned to the LUNs that are restored must be the same drive letters that were used when the archive was created.
You cannot recover a LUN or transaction logs into a read-only file system, such as a Snapshot copy.
For SnapManager Restore to work properly, SnapManager for Microsoft Exchange must be licensed on the storage system that stores the Exchange databases or the local Windows machine running SnapManager.
For SnapManager Restore to work properly, SnapRestore must be licensed on the storage system that stores the Exchange databases.
The recovery processes in this guide do not address a large-scale disaster in which supporting Windows infrastructure, such as Active Directory and DNS, is damaged or lost. Before attempting recovery of the Exchange server or the storage system, you must recover the supporting infrastructure.

Which recovery procedure to use

You can use the following table to determine which recovery process most closely matches your needs.

If...	Then use...
You want to recover Exchange databases from a SnapMirror destination volume	Recovering Exchange data using SnapMirror
Your Exchange server is online and you want to recover Exchange databases from archive	Recovering Exchange data using archives
Your storage system volume has failed or been destroyed and you used archiving	Restoring a storage system volume using SnapManager backup archives
Your Exchange server has failed or been destroyed	Recovering a failed Exchange server
Both your Exchange server and your storage system have failed and you want to recover on the same hardware	The applicable procedure: About recovering both a failed storage system and a failed Exchange server Recovering both a failed storage system and Exchange server using SnapMirror Recovering both a failed storage system and Exchange server using archiving
Both your Exchange server and your storage system have failed or been destroyed, and you want to recover your Exchange environment using a replicated environment on a new Exchange server	The applicable procedure: Recovering a failed storage system and server to a replicated environment Returning to your original site replication configuration

Recovering Exchange data using archives

To restore the Exchange databases from an archive of a SnapManager backup set, complete the following steps.

Step	Action
Prepare your environment
1	Identify and locate the archived backup set that you want to restore.
2	If your Exchange databases are still mounted, dismount all databases belonging to the storage group to be restored.
3	Note the drive letter belonging to the storage group to be restored from archive.
4	As an extra safety measure, use SnapDrive to manually create a Snapshot copy of the LUNs to be restored from archive.
5	Use SnapDrive to delete the LUNs to be restored to avoid a file name conflict when the LUNs are restored from archive.
Restore storage system data
6	Using the archive tool you used to create the archive, restore the archived LUNs to the storage system volume.
7	Use SnapDrive to connect to the restored LUNs, using the same drive letters you used before.
8	Verify that the reconnected LUNs are accessible.
9	Restore the SnapInfo directory and all of its contents from the archive to a temporary location accessible from the SnapManager host. SnapManager requires the SnapInfo directory to restore from the archive, and will request this location in a later step. Note You might have archived only the SnapInfo directory or the entire LUN containing it. In either case, you now need access only to the SnapInfo directory on that LUN or to a copy of the SnapInfo directory.
Restore Exchange data
10	Exit SnapManager if it is running, and restart it in Restore From Archive mode by opening a command window and using the following command-line flag: `restorearchive` Example C:\Program Files\NetApp\SnapManager For Microsoft Exchange\SnapManager.exe -restorearchive Note Use this SnapManager mode only to restore SnapManager archives. Before performing any other SnapManager operations, close SnapManager and restart it without the command-line flag. Result The SnapManager Restore From Archive window is displayed.
11	In the Restore From Archive window, enter or browse to the path where the SnapInfo directory was restored. The path to the restored SnapInfo directory includes the following components: \`snapinfo`\server_name\storage_group_name\snapshot_name. The snapshot_name should be the same name as the Snapshot copy from which the LUN file for the database was archived.
12	Click OK.
13	In the Restore From Archive window, double-click to select the backup set that you want to restore. Note When peforming a restore from archive operation with SnapManager on systems running Windows 2000 Server, the backup sets displayed under the restore tab will show up as unverified whether or not they have in fact been verified. The administrator will have to either verify the database again as part of the restore prodedure or restore the database unverified if you have knowledge that it had been previously verified.
14	Click Start Restore. If the backup is not verified, you are prompted whether to verify it. Note You can override the verification requirement; however, you are strongly advised to use only verified backups for restore.
15	Click Yes to continue.
16	Click Start Now to begin the restore process.
17	After the restore is complete, launch the Outlook® client and verify that your data was properly restored and that the Exchange server is operating correctly.
18	Perform a SnapManager backup and verification to verify that your restored database is free of physical-level corruption.

Recovering Exchange data using SnapMirror

This section explains how to recover LUNs from a failed volume on a storage system or a failed storage system using SnapMirror. These LUNs contain the Snapshot copies of the databases to be restored.

You can configure SnapMirror to use a destination volume on the same storage system or a different, remote storage system. Whether the destination volume is on the same storage system as the failed volume or a different one, the procedure you follow to recover is largely the same.

To recover Exchange data using a SnapMirror destination volume, complete the following steps.

Step	Action
1	Identify the destination mirror volume so that you know the volume to mount when you encounter that step.
2	Ensure that the storage system hosting the SnapMirror destination volumes is online and that the volumes are available and shared through CIFS. For information about creating CIFS shares, see your SnapDrive documentation. For information about general storage system administration, see your Data ONTAP System Administration Storage Management Guide.
3	Make sure that all databases that are stored on LUNs on the failed volume are dismounted. For information about dismounting stores, see the Microsoft Exchange documentation.
4	From the SnapDrive MMC, disconnect the LUNs that resided on the failed volume. Take note of the drive letters or mount points that were used for these disks. For information about disconnecting LUNs, see your SnapDrive documentation. Note If you are unable to disconnect a LUN, it might contain databases that are still online, or there could be another application that is still accessing that LUN.
5	From the SnapDrive MMC or command-line interface, connect to the LUN files in the active file system of the SnapMirror destination volume. SnapDrive will also break the mirror during this process. Note Do not mount the Exchange databases yet. The SnapManager Restore process mounts the databases. If you get an error when connecting, such as "Disk is in exclusive use," use FilerView to ensure that the LUN is unmapped from all igroups and online. For information about connecting LUNs, see your SnapDrive documentation. Result A Single File Snap Restore (SFSR) is automatically performed, using the most recent Snapshot copy (which could have been created by SnapDrive or SnapManager).
6	Run SnapManager and use SnapManager Restore to restore the most recent backup for each storage group. For more information about using SnapManager Restore, see Restoring Databases with SnapManager.
7	Launch the Outlook client and verify that your data was properly restored and that the Exchange server is operating correctly.
8	Perform a SnapManager backup and verification to verify that your restored database is free of physical-level corruption.

Restoring a storage system volume using SnapManager backup archives

This scenario explains how to recover LUNs from a failed storage system volume or a failed storage system using archived SnapManager backups.

To recover a failed storage system volume using SnapManager backup archives, complete the following steps.

Step	Action
1	Recover the storage system so that it is online and available. For information about bringing the storage system online and making it available to your client, see the Software Setup Guide and System Administration Storage Management Guide for your version of Data ONTAP.
2	Prepare the archive media and the backup application so that they are ready to be used for the recovery. If you are using a NearStore system, ensure that the data is accessible.
3	Perform the procedure for archive recovery described in Recovering Exchange data using archives.

Step

Action

Recover the storage system so that it is online and available.

For information about bringing the storage system online and making it available to your client, see the Software Setup Guide and System Administration Storage Management Guide for your version of Data ONTAP.

Prepare the archive media and the backup application so that they are ready to be used for the recovery.

If you are using a NearStore system, ensure that the data is accessible.

Perform the procedure for archive recovery described in Recovering Exchange data using archives.

Recovering a failed Exchange server

To recover an Exchange server, you must use NTBackup or a third-party backup and restore application, relying on its documentation for direction. To recover the Exchange databases, you use SnapManager.

This procedure assumes that backups of the Exchange server were made; it also assumes that the most recent backup includes the system state of the Exchange server just before the disaster occurred.

Recovering a failed Exchange 2000 or 2003 server

To recover a failed Exchange 2000 or 2003 server, complete the following steps.

If you are restoring to different hardware, you might need to refer to one of the following Microsoft Knowledge Base articles, as appropriate for your operating system:

For Exchange 2000, see article 297289.
For Exchange 2003, see article 822945.

Steps	Action
1	Ensure that the storage system is online and that the volumes containing the LUN files are available across CIFS. For information about creating CIFS shares, see your SnapDrive documentation. For information about general storage system administration, see the System Administration Storage Management Guide for your version of Data ONTAP.
2	The server you restore Exchange on does not need to be the same hardware you were running Exchange on before the disaster. However, it must have the same name as the previous Exchange server, and it must have sufficient capacity.
	If...	Then...
	You are restoring your Exchange server back to the same hardware	Proceed to Step 3.
	You are restoring your Exchange server to a brand new server	Name the new server using the same name as the original Exchange server and proceed to Step 3. Note If you are restoring from tape, your new hardware configuration must match the old hardware configuration exactly, including interface cards and firmware versions.
	You are restoring your Exchange server to a different, preexisting server	Reset the machine account in the domain and name the server, using the same name as the original Exchange server, and proceed to Step 4. For more information about performing this step, see the appropriate Microsoft Knowledge Base article, as listed before this procedure. Attention Do not install Exchange at this time. Use the KB article only to rename the server. Make sure that you perform the account reset, as specified in the Knowledge Base article, rather than deleting the account and re-creating it.
3	Perform a full restore of the Exchange server, without the Exchange databases, using the backup application you used to create the backup. See the documentation for your backup software and the Disaster Recovery for Microsoft Exchange 2000 Server document.
4	If...	Then...
	Your backup software backed up the SnapDrive software	Proceed to Step 5.
	Your backup software was not configured to back up the SnapDrive software	Reinstall the same version of SnapDrive used before the disaster occurred. For information about installing SnapDrive, see your SnapDrive documentation.
5	Using SnapDrive, connect the LUNs, or ensure that they are connected, and that you are using the same drive letters used before the disaster.
6	If...	Then...
	Your backup software backed up the Exchange Server software	Proceed to Step 7.
	Your backup software was not configured to back up the Exchange Server software	Install Exchange and any required Exchange service packs in disaster recovery mode. For details, see the appropriate Microsoft Knowledge Base article, as listed before this procedure. Note Do not mount any storage groups yet.


7	If...	Then...
	Your backup software backed up the SnapManager software	Proceed to Step 8.
	Your backup software was not configured to back up the SnapManager software	Reinstall the same version of SnapManager used before the disaster and run the Configuration Wizard to ensure that your configuration matches exactly the configuration used before the disaster. Note Because you are reconstructing your original configuration, no data is moved by the Configuration Wizard. However, running the Configuration Wizard is necessary for SnapManager to function correctly.
8	Restore the most recent backup using SnapManager Restore. For more information about using SnapManager Restore, see Restoring Databases with SnapManager.
9	Launch the Outlook client and verify that your data was properly restored and that the Exchange server is operating correctly.
10	Perform a SnapManager backup and verification to verify that your restored database is free of physical-level corruption.

About recovering both a failed storage system and a failed Exchange server

If both the storage system and the Exchange server fail, in most cases, you should recover the storage system first so that the data--or the space to recover the data--is available.

Successful recovery of the Exchange server depends on the existence of following components:

A recent, usable backup of the Exchange server or a replicated Windows environment to enable the re-creation of the Exchange server
Archive of a recent, verified SnapManager backup set or SnapMirror destination volumes containing the SnapManager backup set

Which failed storage system and server recovery procedure to use

The procedure you use to recover both a failed storage system and a failed Exchange server depends on whether you employed SnapMirror or archiving. Use the appropriate procedure, as follows.

If you employed...	Then use...
SnapMirror	Recovering both a failed storage system and Exchange server using SnapMirror
Archiving	Recovering both a failed storage system and Exchange server using archiving

Recovering both a failed storage system and Exchange server using SnapMirror

To recover both the storage system and the Exchange server using SnapMirror replication, complete the following steps.

Step	Action
1	Ensure that the storage system hosting the SnapManager destination volumes is online and that the volumes are available and shared through CIFS. For information about creating CIFS shares, see your SnapDrive documentation. For information about general storage system administration, see the Data ONTAP System Administration Storage Management Guide for your version of Data ONTAP.
2	Perform a full restore of the Exchange server, without the Exchange databases, using the backup application you used to create the backup. For more information about restoring your Exchange server, see the documentation for your backup software and the appropriate Microsoft disaster recovery document as described in Guides you should read and have at hand. Note If a backup of the Exchange server is not available and your Windows environment is an exact duplicate of the environment before the failure, you can reconstruct the Exchange server. For details, see Recovering a failed storage system and server to a replicated environment, using your new environment as the replicated environment.
3	If...	Then...
	Your backup software backed up SnapDrive	Proceed to Step 4.
	Your backup software was not configured to back up SnapDrive	Reinstall the same version of SnapDrive used before the disaster occurred. For information about installing SnapDrive, see your SnapDrive documentation.
4	From the MMC on the Exchange server, use SnapDrive to connect to the LUNs in the active file system of the SnapMirror destination volume. Make sure that you use the same drive letters for the same LUNs as your original configuration. Note Do not mount the Exchange databases yet. The SnapManager Restore process mounts the databases. If you get an error when connecting, such as "Disk is in exclusive use," use FilerView to ensure that the LUN is unmapped from all igroups and online. For information about connecting LUNs, see your SnapDrive documentation. Result The mirror is broken and an SFSR is performed, restoring the LUNs from the most recent SnapManager or SnapDrive Snapshot copy. Another SFSR will be performed in a later step, during the SnapManager restore.
5	If...	Then...
	Your backup software backed up SnapManager	Proceed to Step 6.
	Your backup software was not configured to back up SnapManager	Reinstall the same version of SnapManager used before the disaster and run the Configuration Wizard to ensure that your configuration matches exactly the configuration used before the disaster. Note Because you are reconstructing your original configuration, no data is moved by the Configuration Wizard. However, running the Configuration Wizard is necessary for SnapManager to function correctly.
6	Restore the most recent backup using SnapManager Restore. For more information about using SnapManager Restore, see Restoring Databases with SnapManager.
7	Launch the Outlook client and verify that your data was properly restored and that the Exchange server is operating correctly.
8	Perform a SnapManager backup and verification to verify that your restored database is free of physical-level corruption.

Recovering both a failed storage system and Exchange server using archiving

To recover both the storage system and the Exchange server using archiving, complete the following steps.

Step	Action
1	Bring the failed storage system back online.
2	Perform a full restore of the Exchange server, without the Exchange data, using the backup application you used to create the backup. For more information about restoring your Exchange server, see the documentation for your backup software and the appropriate Microsoft disaster recovery document as described in Guides you should read and have at hand. Note If a backup of the Exchange server is not available and your Windows environment is an exact duplicate of the environment before the failure, you can reconstruct the Exchange server. For details, see Recovering a failed storage system and server to a replicated environment, using your new environment as the replicated environment.
3	If...	Then...
	Your backup software backed up SnapDrive	Proceed to Step 4.
	Your backup software was not configured to back up SnapDrive	Reinstall the same version of SnapDrive used before the disaster occurred. For information about installing SnapDrive, see your SnapDrive documentation.
4	Using the archive tool you used to create the archive, restore the archived database LUNs to the storage system volume.
5	If...	Then...
	You archived the LUNs containing the SnapInfo directory and the transaction logs	Restore these LUNs.
	You did not archive the LUNs containing the SnapInfo directory and the transaction logs	Create new LUNs using the same drive letters as your original configuration, in the same volumes as they were before.
6	Using SnapDrive on the Exchange server, connect to the LUNs you restored from archive with the same drive letters as your original configuration. Note Do not mount the Exchange databases yet. The SnapManager Restore process mounts the databases.
7	If...	Then...
	Your backup software backed up SnapManager	Proceed to Step 8.
	Your backup software was not configured to back up SnapManager	Reinstall the same version of SnapManager used before the disaster and run the Configuration Wizard to ensure that your configuration matches exactly the configuration used before the disaster. Note Because you are reconstructing your original configuration, no data is moved by the Configuration Wizard. However, running the Configuration Wizard is necessary for SnapManager to function correctly.
8	Perform the procedure for archive recovery described in Recovering Exchange data using archives, starting with Step 9.

Recovering a failed storage system and server to a replicated environment

To recover both the storage system and the Exchange server to a replicated environment, complete the following steps.

Note
This procedure assumes that you have your Windows environment replicated, as described in Replicating your Exchange environment. This includes a replicated Active Directory Domain Controller, so your supporting Windows environment matches your previous environment exactly.

For this configuration, the term "original Exchange server" refers to the Exchange server running in your original environment that has failed. The term "recovery Exchange server" refers to the Windows host that will run Exchange in the replicated environment after you complete this procedure.

Step	Action
1	Ensure that you have `rsh` access to the storage system hosting the SnapMirror destination volumes. For more information about managing access from administration hosts, see the System Administration Storage Management Guide for your version of Data ONTAP.
2	Ensure that the storage system hosting the SnapMirror destination volumes is online and that the volumes are available and shared through CIFS. For information about creating CIFS shares, see your Data ONTAP System Administration File Access Management Guide. For information about general storage system administration, see your Data ONTAP System Administration Storage Management Guide.
3	Follow the steps in the appropriate Microsoft Knowledge Base article to reset the computer account and rename the standby Exchange server in your new environment to the name of the original Exchange server: If your original Exchange server was running Exchange 2000, use article 297289. If your original Exchange server was running Exchange 2003, use article 822945. Attention Do not install Exchange yet. This is done in a later step. Make sure that you perform an account reset, rather than deleting the account and re-creating it.
4	Make sure that the same version of SnapDrive that was running on your original Exchange server is installed on your standby Exchange server.
5	From the MMC on the standby Exchange server, use SnapDrive to connect to the LUNs in the active file system of the SnapMirror destination volume. Make sure that you use the same drive letters for the same LUNs as your original configuration. For information about connecting LUNs, see your SnapDrive documentation. Note If you get an error when connecting, such as "Disk is in exclusive use," use FilerView to ensure that the LUN is unmapped from all igroups and online. Result The mirror is broken and then the LUN is restored using the most recent SnapDrive Snapshot copy.
6	If the LUN that stores the transaction logfiles resides on a different volume than the LUN that stores the SnapInfo directory and the volume containing the transaction logs LUN is not mirrored, you must create a new LUN--in the active file system of a SnapMirror destination volume that does not contain a LUN with Exchange databases--for the transaction logs. Note It is not a requirement to replicate the volume that contains the LUN that stores the Exchange transaction logs, and this LUN can reside on its own separate and un-mirrored volume. As a result, the LUN that stores the Exchange transaction logs LUN might not get replicated to the SnapMirror destination storage system. If you need to create a new LUN for the transaction logs, complete the following steps: On the destination storage system, create a volume of a size equal to or greater than that of the volume on the source storage system that contains the LUN for the transaction logs. Use SnapDrive to create a LUN of equal or greater size. The same drive letter must be used.
7	Using the Microsoft Knowledge Base article you used in Step 3, install Exchange and any required Exchange service packs in disaster recovery mode on your standby Exchange server. Result When you complete this step, your standby Exchange server should be running exactly the same version of Exchange, including service packs, as your original Exchange server.
8	On the standby Exchange server, install the same version of SnapManager as was running on your original Exchange server.
9	Launch SnapManager and run the SnapManager Configuration Wizard to ensure that the correct configuration is used. If necessary, modify the configuration so that it matches exactly the configuration before the failure.
10	Restore the most recent backup using SnapManager Restore. For more information about using SnapManager Restore, see Restoring Databases with SnapManager.
11	Launch the Outlook client and verify that your data was properly restored and that the standby Exchange server, which now becomes your primary Exchange server, is operating correctly.
12	After you repair or replace your primary site, you can return to your original configuration. For more information about returning to your original site replication configuration, see Returning to your original site replication configuration.

Returning to your original site replication configuration

If you needed to perform disaster recovery using a replicated site, you probably want to return to your original site replication configuration. Because Exchange is now running on the replicated site, you must perform this operation correctly to avoid data loss as you switch back over to the original site.

To return to using Exchange on your primary site after you perform disaster recovery using your replicated site, complete the following steps.

Note
In this procedure, your original primary site is called the primary site (although before you perform the procedure, it is not running Exchange), and the site and server you are currently running Exchange on are called the replicated site and the standby Exchange server.

This procedure references two Microsoft Knowledge Base articles. The article that you use depends on your version of Exchange. For Exchange 2000, use article 297289. For Exchange 2003, use article 822945.

Attention
Do not install any application software on the primary site until instructed to do so.

Step	Action
Prepare primary site
1	Repair or replace the storage system on your primary site. For more information about setting up your storage system, see the System Administration Storage Management Guide for your version of Data ONTAP.
2	Reconstruct the Windows environment, including the Active Directory Domain Controller, on your primary site by replicating the environment back from the replicated site.
Create temporary mirror
3	Using SnapMirror, create a mirror with the replicated site as the (temporary) source and the primary site as the (temporary) destination. Note Remember that a destination volume must be at least as large as its source volume. If your original destination volume was larger then your original source volume, you need to increase the size of the temporary destination volume to match the size of the temporary source volume. If your original primary storage system was not affected by the disaster, you can use the `snapmirror resync` command to perform this step more quickly. For more information about this command, see the System Administration Data Protection Guide for your version of Data ONTAP.
Capture Exchange data
4	On the standby Exchange server, perform a SnapManager backup and verification of all storage groups.
5	Block all user access to Exchange. Note This step is necessary because all changes to the Exchange data store made after the mirror is updated are lost when you switch over to the primary site.
6	Use SnapDrive to perform an update mirror operation using the following `sdcli` command once for every volume containing Exchange or SnapInfo data: `sdcli snap update_mirror -d` drive For more information about the SnapDrive command-line interface, see your SnapDrive documentation.
7	Shut down the standby Exchange server.
Reconstruct primary Exchange server
8	Using the appropriate Microsoft Knowledge Base article for your version of Exchange, reset the machine account in the domain. Attention Make sure that you perform the account reset, as specified in the Knowledge Base article, rather than deleting the account and re-creating it.
9	Install and configure Windows on the primary Exchange server. Attention If you repaired the original Exchange server, wipe its disks and reinstall the operating system. Do not attempt to bring the server back online with the original software.
10	Install any Windows service packs that were installed on the primary Exchange server.
11	Ensure that you have `rsh` access to the newly reconstructed or repaired storage system.
12	Install and configure SnapDrive on the primary Exchange server.
13	Using SnapDrive, connect to the LUNs in the active file system of the newly reconstructed or repaired storage system. Attention Be sure you use the same drive letters that were used in your original primary site, and as should be in use in your recovery site. Result The reverse direction mirror you created in Step 3 is broken and an SFSR is performed.
14	Using the appropriate Microsoft Knowledge Base article for your version of Exchange, install Exchange and any required Exchange service packs in disaster recovery mode on the primary Exchange server.
15	Install the same version of SnapManager for Microsoft Exchange that was installed on the primary Exchange server.
16	Launch SnapManager and run the SnapManager Configuration Wizard, making sure to keep all data on the same drives where it was before.
Restore and verify Exchange data
17	Use SnapManager Restore to restore the backup you created in Step 4.
18	Launch the Outlook client and verify that your data was properly restored and that the new primary Exchange server is operating correctly.
Re-create mirror
19	Delete the (reversed) mirror configuration you created in Step 3.
20	Re-create your original mirror, with your newly reconstructed storage system as the source, and the replicated site as the destination.
Reconfigure replicated site
21	Return your standby Exchange server to standby mode by performing these steps: Wipe the disks. Using a different name than the primary Exchange server, reinstall the correct version of the operating system and any required service packs. Place the standby Exchange server into a workgroup. (This step is optional.) Result: Your replicated site is ready once again in case of the loss of or damage to your primary site.

Restoring your Exchange environment

Overview

Exchange environment recovery processes

A SnapManager for Exchange restore from archive operation should be considered a "point-in-time" restore

Rules and guidelines for disaster recovery

Which recovery procedure to use

Recovering Exchange data using archives

Example

Result

Recovering Exchange data using SnapMirror

Result

Restoring a storage system volume using SnapManager backup archives

Recovering a failed Exchange server

Recovering a failed Exchange 2000 or 2003 server

About recovering both a failed storage system and a failed Exchange server

Which failed storage system and server recovery procedure to use

Recovering both a failed storage system and Exchange server using SnapMirror

Result

Recovering both a failed storage system and Exchange server using archiving

Recovering a failed storage system and server to a replicated environment

Result

Result

Returning to your original site replication configuration

Result

Result: