Backup Exec Disaster Recovery for Exchange 2000 or 2003

Embed Size (px)

Citation preview

  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    1/9

    Document ID: 235756http://support.veritas.com/docs/235756 E-Mail this document to a colleague

    Disaster Recovery Procedure for Exchange 2000 or 2003Details:The Windows 2000 or 2003 server must be recovered first. For more information, see theDisaster Recovery chapter in the Backup Exec Administrator's Guide . If a hard copy of theBackup Exec Administrator's Guide is unavailable, the complete manual in PDF format canfound on the Backup Exec CD at this location:

    %CDROM Drive Letter%:\WINNT\INSTALL\del *.log

    NOTE - If the Exchange 2000 or 2003 sever was configured with additional storage groups,delete the log files from the other transaction log directories as well.

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 1 of 9 Revised: 8/20/2006

    http://support.veritas.com/docs/235756http://opensubwin%28%27http//seer.support.veritas.com/email_forms/tnote_sndml.asp?docID=http://seer.support.veritas.com/docs/235756%27,%20475,%20500)http://opensubwin%28%27http//seer.support.veritas.com/email_forms/tnote_sndml.asp?docID=http://seer.support.veritas.com/docs/235756%27,%20475,%20500)http://support.veritas.com/docs/235756
  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    2/9

  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    3/9

    Figure 3

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 3 of 9 Revised: 8/20/2006

  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    4/9

    4. Start Backup Exec

    5. Catalog the media that contains the latest Full, Incremental, and Differential backups of theMicrosoft Exchange 2000 or 2003 storage groups that are to be recovered

    6. Select the latest full backups of the storage groups for restore

    Note : If the Exchange 2000 server being recovered contains the Site Replication Service(SRS) or Key Management Service (KMS), then select those databases for restore as well.

    7. Select all subsequent incremental storage group backups. If differential backups are to berestored, only the most recent differential storage group backups need to be selected.

    8. Click the Exchange tab, and clear the No Loss Restore selection (Figure 3)

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 4 of 9 Revised: 8/20/2006

  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    5/9

    Figure 4

    Explanation of No Loss Restore: (Do not delete existing log files): When the No loss Restoreoption is selected, the existing transaction logs on the Exchange 2000 server are preserved.Transaction logs from the storage media are then restored and added to the existing set of transaction logs on the Exchange 2000 server. When the restore operation finishes, Exchange2000 automatically updates its databases with the uncommitted transactions found in theexisting and newly-restored transaction logs. This option is selected by default. If No LossRestore is cleared, only the restored log files will be applied to the database.

    Caution : If restoring individual databases into a storage group, the No loss Restore optionshould be selected. If this option is not selected, log files for the entire storage group will bedeleted.

    9. Enter a location where the associated log and patch files are to be kept until the database isrestored in the field Temporary location for log and patch files (Figure 4). After thedatabase is restored, the log and patch files in the temporary location are applied to thedatabase. After the restore is complete, the log and patch files are automatically deleted fromthe temporary location (including any sub-directories).

    Note : Make sure the temporary location for log and patch files is empty before starting arestore job. If a restore job fails, check the temporary location (including any sub-directories) to

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 5 of 9 Revised: 8/20/2006

  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    6/9

    make sure any previous log and patch files from a previous restore job were deleted.

    Figure 5

    10. If the selection contains the last backup set to be restored, select Commit after restorecompletes (Figure 5). Do not select this option if backup sets still exist to restore. If the optionCommit after restore completes is selected when an intermediate backup is being applied,the job cannot continue to restore backups and it must restart the restore operation from thebeginning.

    Figure 6

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 6 of 9 Revised: 8/20/2006

  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    7/9

    11. If the database is to be immediately available to users after the recovery, select Mountdatabase after restore (Figure 6). This option is only available if Commit after restorecompletes is selected.

    Figure 7

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 7 of 9 Revised: 8/20/2006

  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    8/9

    12. Click OK , then click Run Now . The recovery procedure is complete.

    13. After completing the restore, it is recommended that a full backup of the restoreddatabases be performed.

    Related Documents:

    233420 : VERITAS Backup Exec (tm) 8.5 for Windows NT and Windows 2000 Administrator'sGuide (English) http://support.veritas.com/docs/233420

    234628 : When attempting to restore the Microsoft Exchange 2000/2003 Information Store, therestore job fails with the error: "Connection to the restore target lost. Operation aborted." http://support.veritas.com/docs/234628

    237738 : The error message "Access denied to database Applications Store" is reported in the job log when attempting to restore the Exchange 2000 Information store http://support.veritas.com/docs/237738

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 8 of 9 Revised: 8/20/2006

    http://support.veritas.com/docs/233420http://support.veritas.com/docs/233420http://support.veritas.com/docs/234628http://support.veritas.com/docs/234628http://support.veritas.com/docs/237738http://support.veritas.com/docs/237738http://support.veritas.com/docs/233420http://support.veritas.com/docs/233420http://support.veritas.com/docs/234628http://support.veritas.com/docs/234628http://support.veritas.com/docs/237738http://support.veritas.com/docs/237738
  • 8/9/2019 Backup Exec Disaster Recovery for Exchange 2000 or 2003

    9/9

    240870 : VERITAS Backup Exec (tm) 8.6 for Windows NT and Windows 2000 Administrator'sManual (English) http://support.veritas.com/docs/240870

    246973 : Backup server reboots during a remote Exchange 2000 Information Store backup andan Event ID 215 is logged on the Exchange 2000 server in the System Log of the EventViewer. http://support.veritas.com/docs/246973

    252165 : How to troubleshoot the "Connection to Restore Target has been lost" error during anExchange restore http://support.veritas.com/docs/252165

    257192 : During the disaster recovery of an Exchange 2000 server, the Exchange 2000

    Information Store restore fails with the error "Connection to the restore target has been lost.Operation canceled" when the option "Commit after restore completes" is selected. http://support.veritas.com/docs/257192

    262430 : How to determine the original site and organization names of an Exchange 5.x or Exchange 2000 or Exchange 2003 server from an Outlook .pst file http://support.veritas.com/docs/262430

    Acknowledgements VERITAS Backup Exec For Windows NT and Windows 2000 v8.x Administrators Guide

    Products Applied: Backup Exec for Windows Servers 10.0, 10d (10.1), 8.5, 8.6, 9.0, 9.1

    Last Updated: July 27 2006 07:08 PM GMTExpires on: 365 days from publish date

    Subscribe to this document

    Disaster Recovery Procedure for Exchange 2000 or 2003 Page 9 of 9 Revised: 8/20/2006

    http://support.veritas.com/docs/240870http://support.veritas.com/docs/240870http://support.veritas.com/docs/246973http://support.veritas.com/docs/246973http://support.veritas.com/docs/252165http://support.veritas.com/docs/252165http://support.veritas.com/docs/257192http://support.veritas.com/docs/257192http://support.veritas.com/docs/262430http://support.veritas.com/docs/262430http://maillist.support.veritas.com/notification.asp?doc=235756http://support.veritas.com/docs/240870http://support.veritas.com/docs/240870http://support.veritas.com/docs/246973http://support.veritas.com/docs/246973http://support.veritas.com/docs/252165http://support.veritas.com/docs/252165http://support.veritas.com/docs/257192http://support.veritas.com/docs/257192http://support.veritas.com/docs/262430http://support.veritas.com/docs/262430http://maillist.support.veritas.com/notification.asp?doc=235756