If both the filer and the Exchange server fail, in most cases, you should recover the filer 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:
The procedure you use to recover both a failed filer and a failed Exchange server depends on whether you employed SnapMirror or archiving. Use the appropriate procedure, as follows.
|
Recovering both a failed filer and Exchange server using SnapMirror | |
|
Recovering both a failed filer and Exchange server using archiving |
To recover both the filer and the Exchange server using SnapMirror replication, complete the following steps.
| 1 |
Ensure that the filer 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 filer 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 |
|
| 3 | ||
|
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 | ||
|
Proceed to Step 5. | ||
|
Your backup software was not configured to back up NetApp VSS Hardware Provider |
Reinstall the same version of NetApp VSS Hardware Provider used before the disaster occurred. For information about installing NetApp VSS Hardware Provider, see the NetApp VSS Hardware Provider Installation and Administration Guide. | |
| 5 |
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 For information about connecting LUNs, see your SnapDrive documentation. ResultThe mirror is broken and an SFSR is performed, restoring the LUNs from the most recent SnapManager or SnapDrive snapshot. Another SFSR will be performed in a later step, during the SnapManager restore. |
|
| 6 | ||
|
Proceed to Step 7. | ||
|
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 | |
| 7 |
Restore the most recent backup using SnapManager Restore. For more information about using SnapManager Restore, see Restoring Databases with SnapManager Restore. |
|
| 8 |
Launch the Outlook client and verify that your data was properly restored and that the Exchange server is operating correctly. |
|
| 9 |
Perform a SnapManager backup and verification to verify that your restored database is free of physical-level corruption. |
|
To recover both the filer and the Exchange server using archiving, complete the following steps.
| 1 | ||
| 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 |
|
| 3 | ||
|
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 filer volume. |
|
| 5 | ||
|
You archived the LUNs containing the SnapInfo directory and the transaction logs | ||
|
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 |
|
| 7 | ||
|
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 | |
| 8 |
Perform the procedure for archive recovery described in Restoring databases from archive, starting with Step 9. |
|
Copyright © 1994-2004, Network Appliance, Inc. All rights
reserved.
Part No. 215-00858
File: recove10.htm
Last updated: Tue Jun 15 15:34:15 2004