You are on page 1of 145

Exchange Server 2003 Disaster Recovery Operations Guide

Last Reviewed: Product Version: Reviewed By: Latest Content: Authors: May 2004 Exchange Server 2003 Exchange Product Development www.microsoft.com/exchange/library Tammy Treit, Chris Frediani

Exchange Server 2003 Disaster Recovery Operations Guide

Tammy Treit Chris Frediani

Published: May 2004 Applies to: Exchange Server 2003 running on Windows Server 2003

Copyright
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2004 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Outlook, Microsoft Press, MSDN, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Acknowledgments
Writers: Tammy Treit, Chris Frediani Project Editor: Cathy Anderson Editors: Cathy Anderson, Amy Groncznack, Tony and Lee Ross Technical Reviewers: Michael Lee, Ayla Kol Additional Reviewers: Vanessa Feliberti, Jon Hoerlein, Nick Britton, The Siemens Team, Jian Yan, Frank Castro, Stanley Yuan Artist: Kristie Smith Production: Joe Orzech, Sean Pohtilla

.................................................................34 Selecting the Advanced Options for a Restore.........................................................................................12 Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data............................................................28 Verifying Backed Up Data..................................i Introduction...............................................................................................................................................45 Backing Up Domain Controllers......................................Table of Contents Exchange Server 2003 Disaster Recovery Operations Guide.......7 Permissions Required......5 Who Should Read This Guide?.....27 Checking the Success of a Completed Backup....................................................................39 Data to Exclude from Windows Backup Sets or Full Computer Backup Sets39 Creating Windows Backup Sets...............................................................................................................................................................................20 Performing a Basic Backup................................32 Using Backup to Restore Your Data......................1 Exchange Server 2003 Disaster Recovery Operations Guide...........................37 Chapter 2.............................................................8 Chapter 1....................................................................................................................................................................................................................................4 What Can You Learn from This Guide?........12 Starting Backup............................................................................................................33 Performing a Basic Restore................5 How Is This Guide Structured?.....................................................................................25 Scheduling a Backup.................4 Overview............................................................................................23 Selecting Options for a Backup......................7 What Terminology Is Used in This Guide?....................................................................................................................................................................35 Checking the Success of a Completed Restore Job...........39 Backing Up Exchange Server 2003..................................................................................42 Creating Full Computer Backup Sets........................................13 Selecting the Default Settings for Backup.................2 Table of Contents.........45 Using Backup to Create Full Computer Backup Sets......20 Selecting the Destination for a Backup.........................................................................................................47 ..................................................................................................................................................................................................14 Using Backup to Back Up Your Data....................................33 Rebuilding a Catalog for a Restore...........

........................................................................60 Backing Up the Exchange Server 2003 Databases That Are Stored on Shared Disk Resources.........................................................................................................................................................................................................122 .......119 Restoring Shared Disk Resources........................................................................66 Reinstalling Windows Server 2003.............................................................................66 Using the Safe Mode Boot Options................................................................................114 Replacing Damaged Exchange Cluster Nodes................................108 Restoring the Certification Authority (CA)...64 Repairing Windows Server 2003.............................88 Recovering an Exchange Database....................................................................................108 Restoring the Microsoft Exchange Site Replication Service (MSExchangeSRS)........................................................................................................................................................................................................................ii Exchange Server 2003 Disaster Recovery Operations Guide Backing Up the System State Data of a Domain Controller.48 Backing Up Exchange Server 2003 Data........................81 Restoring Full Computer Backup Sets.....69 Repairing Exchange Databases.....................................................................................65 Running Windows System File Checker.......................65 Running the Windows Chkdsk Utility....................................66 Using the Windows Recovery Console...............67 Repairing Exchange Server 2003.......58 Backing Up Exchange Server 2003 Clusters ....................119 Recovering a Whole Exchange Cluster.............................................................................................................................................................112 Restoring Connector-Specific Data.............120 Exchange Member Server Recovery.................................84 Restoring a Full Computer Backup Set by Using Backup............72 Repairing Full-Text Indexing......................................................107 Restoring Exchange Databases to Another Server.................................57 Backing Up Connector-Specific Information...........................................................................................86 Restoring Individual Mailboxes...............................75 Restoring Windows Backup Sets.................................................63 Chapter 3..........................................115 Restoring or Rebuilding a Cluster Node from Backups...................................................................................................................................................67 Reinstalling Exchange Over a Damaged Installation.....................58 Backing Up an Exchange Server 2003 Cluster's Shared Disk Resources................................90 Resolving Exchange Database Restore Problems.....47 Recommendations for Backing Up a Domain Controller ...................87 Restoring Exchange Mailbox or Public Folder Stores.... 55 Backing Up the Certification Authority (CA)........121 Member Server Recovery Methods.......................................................................................................................................................64 Restoring Exchange Server 2003.....61 Maintaining Records About Your Server Clusters........................................................88 Overview of the Database Restore Process..................................................................66 Using the Last Known Good Configuration Boot Option......................................48 Backing Up Exchange Server 2003 Databases ............................114 Restoring Exchange Clusters.................................................................................................................................49 Backing Up the Microsoft Exchange Site Replication Service (MSExchangeSRS)........................................................85 Restoring Domain Controllers.................

...............................................................................................................134 Windows 2000 Server.............................................................................................................................................................................................................................................................141 Exchange Server 2003.................................................................................................................................................................138 Accessibility for People with Disabilities............................133 Resources............................136 Exchange Server 2003..........................................................................................134 Exchange Server 5..........................................................................................................................................................................................................133 Exchange 2000 Server.....................0..133 Resources Cited in This Book........................................134 Windows Server 2003.......................................................140 Customer Service....................................138 Accessibility in Microsoft Windows......................................132 Appendix A.......136 Windows Server 2003......Table of Contents iii Member Server Recovery Procedures.................................................................................141 ......................................138 Adjusting Microsoft Products for People with Accessibility Needs.....................135 Additional Resources..........5....................139 Free Step-by-Step Tutorials.....................................................124 Appendixes.....134 IIS 6.................................................138 Accessibility Files to Download.....................................................................136 Web Sites..............................................................................................................................................................................................139 Microsoft Documentation in Alternative Formats.....................................................................................................................136 Exchange 2000 Server..............................................................141 Getting More Accessibility Information................................133 Exchange Server 2003...................................................................................................................................141 Outlook Web Access...................................140 Technical Assistance...137 Appendix B..............................................139 Assistive Technology Products for Windows.................................137 Resource Kits..........................................................................................................................................................................................................................140 Microsoft Services for People Who Are Deaf or Hard-of-Hearing.....................................................................................................137 Windows 2000 Server......................

Use this guide to help you decide on your backup and recovery strategy before continuing with the procedures covered in the Disaster Recovery Operations Guide.microsoft. For information about recovery storage groups. are not covered in this guide. it explains how to use the backup utility (Backup) in Windows Server 2003 for both backup and recovery purposes.com/fwlink/?LinkId=6277). For information about how to back up and restore Microsoft Exchange 5. This guide is intended for information technology (IT) professionals who perform backup and restore procedures or who write customized backup and restore procedures for their organization. This guide explains how to perform backup and restore procedures so that you can prepare for (back up) and recover from (restore) a failure that causes some or all of your data to become unavailable. see Exchange Server 2003 Disaster Recovery Planning Guide (http://go. This guide does not cover third-party backup and restore solutions. For information about planning and selecting a backup and recovery strategy for your organization. This guide focuses on deployments of Exchange 2003 that are running on a Windows Server 2003 operating system. see that software's documentation.I N T R O D U C T I O N Overview This guide explains how to back up and restore the critical data in your Exchange organization.microsoft. see Microsoft Exchange 5. Understanding disaster recovery concepts.com/fwlink/?LinkId=30251). which are new in Exchange 2003. To learn more about strategies for maintaining a highly available Exchange 2003 messaging system see the Exchange Server 2003 High Availability Guide (http://go. see Using Exchange Server 2003 Recovery Storage Groups (http://go. It covers how to use the backup utility in Microsoft® Windows Server™ 2003 (Backup). see Disaster Recovery for Microsoft Exchange 2000 Server (http://go. Meeting service level agreements.com/fwlink/?LinkId=30251) .1 Disaster recovery documentation Guide Exchange Server 2003 Disaster Recovery Planning Guide (http://go. Instead.microsoft. how to back up Microsoft Exchange Server 2003.microsoft. Exchange Server 2003 High Availability Guide (http://go.5 Disaster Recovery (http://go.com/fwlink/? LinkId=21277).com/fwlink/?LinkId=21277) Material covered • • • • Planning your disaster recovery strategy.com/fwlink/?LinkId=18350). Recovery storage groups.microsoft. For information about how to use third-party software products for disaster recovery.microsoft.com/fwlink/?LinkId=23233).microsoft. Table I. and how to restore Exchange Server 2003. Maintaining a high level of uptime.5 servers. For information about how to back up and restore Microsoft Exchange 2000 Server deployments that are running on a Microsoft Windows® 2000 Server operating system.

com/fwlink/?LinkId=23233) Disaster Recovery for Microsoft Exchange 2000 Server (http://go.Introduction 5 Guide Exchange Server 2003 Disaster Recovery Operations Guide (http://go. How to recover data from a database in a recovery storage group. Using Exchange Server 2003 Recovery Storage Groups (http://go.5 Disaster Recovery (http://go. How to use Backup to back up and restore Exchange data and components.microsoft. How to use a Dial Tone database to recover a mailbox database without interrupting service to users. Concepts and procedures necessary to plan and implement backup and restore processes for Exchange 2000 and Windows 2000 Server.microsoft. Concepts and procedures necessary to plan and implement backup and restore processes for Exchange 5. .microsoft. "Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data" This chapter describes how to use Backup to both back up and restore your Exchange data. Procedures to help you protect and recover your Exchange organization.microsoft. How to use recovery storage groups to back up Exchange data. How Is This Guide Structured? This guide is divided into the following sections: Chapter 1. Explanation of recovery storage groups. Chapter 2. How to use Backup to back up and restore Windows Server 2003 network resources that Exchange 2003 depends on. How to back up and restore Exchange clusters.com/fwlink/?LinkId=30250) Material covered • • • • • • How to use the backup utility (Backup) in Windows Server 2003.5.com/fwlink/?LinkId=6277) • What Can You Learn from This Guide? This guide provides the following information: • • • • How to use the backup utility (Backup) in Windows Server 2003.com/fwlink/?LinkId=18350) • Microsoft Exchange 5. "Backing Up Exchange Server 2003" This chapter provides step-by-step instructions on how to back up your Exchange 2003 organization.

"Restoring Exchange Server 2003" This chapter provides step-by-step instructions on how to restore your Exchange 2003 organization after a failure.6 Exchange Server 2003 Disaster Recovery Operations Guide Chapter 3. .

you must have. you can use Run as to start applications or additional commands in a different security context without having to log off. • Performing recovery operations for your Exchange organization. Add your own. To create Exchange backups. Therefore. Instead. local backup operator rights. consider using this guide as a basis for that documentation. Permissions Required You must have the required permissions or rights assigned to the user account that you are logged into when you try to back up or restore files and folders. If you are responsible for creating internal documentation for your Exchange organization. Minimum permissions Domain backup operator Full Exchange administrator Local backup operator Local administrator rights . in addition to a list of additional resources that might help you back up and restore your Exchange 2003 data. Standard Edition online Help (http://go. at a minimum. Although this guide is intended for beginning through advanced information technology (IT) administrators.Introduction 7 Appendix A. To restore Exchange 2003 backups. "Accessibility for People with Disabilities" Who Should Read This Guide? This document is intended for Exchange administrators or backup operators who have one or more of the following responsibilities: • Creating detailed disaster recovery procedures for your Exchange organization. Appendix B. For more information. specific policies and procedures where necessary. To create backups of your Windows Server 2003 operating system. "Resources" This appendix provides a list of all references cited in Chapters 1 through 3. do not log on to a computer by using administrative credentials when you want to perform routine backup operations. you must have full Exchange administrator rights for the domain. as a security best practice. Run as prompts you to type different credentials before it allows you to run the application or command. this guide will show you how to perform them. you must have domain level backup operator rights.com/fwlink/?LinkId=28314).microsoft.2 Disaster recovery permissions Task Exchange backups Exchange restore operations Windows backups Windows restore operations Important Logging onto a computer by using administrative credentials might pose a security risk to the computer and network. see "Using Run as" in the Windows Server 2003. you must have local administrator rights. If you are responsible for performing the step-by-step backup or restore procedures for your Exchange organization. the technical explanations and procedures are written to benefit beginning administrators who might not have previous experience with disaster recovery processes. Table I. To restore a backup of a Windows Server 2003 operating system.

that stores files that have been backed up.com/fwlink/?LinkId=24625). Domain Administrators group Local Backup Operators group Domain Backup Operators group Any other domain or local group What Terminology Is Used in This Guide? To understand this guide. Standard Edition online Help (http://go. back up (verb) To create a duplicate copy of a database or other system component by preserving the actual files that make up that component. Can back up all files and folders that your account owns. If you are a local administrator on an Exchange member server.3 Accounts and their backup privileges Account is a member of Local Administrators group Backup privileges Can back up most files and folders on the computer where your account is a member of the Local Administrators group. Additional terms that are specific to Exchange are defined in the Exchange Server 2003 Glossary (http://go. backup job The act of backing up a set of files at the same time. typically compressed. you cannot back up Exchange database files unless you are also a member of the Backup Operator or Domain Administrator groups.com/fwlink/?LinkId=28312).microsoft. backup (noun) The file or other media. This partition contains files in the root directory such as NTLDR and BOOT. Can back up all files and folders on all computers in the domain.com/fwlink/?LinkId=21769) and "Permissions and user rights required to back up and restore" in the Windows Server 2003.8 Exchange Server 2003 Disaster Recovery Operations Guide For more information about permissions. or Full Control permissions. Modify. Table I. Read and Execute. Can back up files or folders for which your account has Read.microsoft. These files are typically stored in a different location. such as on specialized storage media. Can back up all files and folders on the computer where your account is a member of the Local Backup Operators group. Can back up all files and folders on all computers in the domain.microsoft. . make sure that you are familiar with the following terms. see "Managing an Exchange Organization" in the Exchange Server 2003 Administration Guide (http://go. boot partition The disk partition from which your computer starts.ini.

An Exchange database is composed of both information in memory and the database files on the disk. The hard recovery process uses a RESTORE. consistent state If your database is in a consistent state. The checkpoint file has a pointer to the oldest log file that contains data that has not yet been written to the database. ESE is a multiuser Indexed Sequential Access Method (ISAM) table manager with full data manipulation language (DML) and data definition language (DDL) capabilities. to determine how to restore the database files and what transaction log files must be replayed from the temp directory that the backup was restored to. full computer backup set You create a full computer backup set when you back up your Windows Server 2003 operating system files. . Changing a database from an inconsistent state to a consistent state generally entails two processes: Restoring the database from a backup that was completed while the database was online. the database can be remounted without requiring any type of transaction log replay. database In this document.env file that is generated during the recovery process. database is a generic term that refers to either a mailbox store or a public folder store. clean shutdown Whenever a database is shut down. Such a database can be mounted and attached again to the log stream without requiring additional transaction log replay. If the information in memory is lost before it is written to the database files on the disk. Applications such as Exchange 2003 use ESE to store records and create indexes. it is put into an inconsistent state. you select the Last Backup Set check box in Backup when you restore your last database. and the transaction log files from the temp directory are replayed into them. The database successfully detached from the log file stream when it was shut down. a flag in the database header keeps track of whether the database did the necessary maintenance to put the database in a consistent state. You cannot mount a database that was shut down in this state until the transaction logs have been replayed and the database has properly detached from the current log stream. including the System State data and all the applications that you have installed on your server. This type of shutdown is flagged as a dirty shutdown. The name of the checkpoint file is Enn. After the databases are copied to their original location. This means that some transaction log files must be replayed before the database can be considered consistent. and replaying the transaction log files into the restored database. or you can uses the eseutil /cc command. A database that was shut down in a consistent state is referred to as being shutdown clean. hard recovery continues to replay any additional transaction log files that it finds in the transaction log file path specified for the storage group of the restored database. where Enn is the log file prefix of the storage group. dirty shutdown When a database is shut down before you have performed necessary maintenance. You must back up these files as part of the same backup job. Extensible Storage Engine (ESE) The database engine that Exchange 2003 uses. hard recovery Hard recovery is the process that changes a restored database back to a consistent state by playing transactions into the database from transaction log files.chk. . it can be replayed from the transaction log files. To initiate hard recovery.Introduction 9 checkpoint file A file that tracks the progress of transaction logging. The soft recovery process also replays any additional transaction log files that it finds.

or to extend the size of a volume without having to re-create the volume on a larger disk. resource groups In a cluster. thereby bringing the database up-to-date. recovery means to replay transaction log files into a restored database. The soft recovery process only replays logs from the transaction log file path specified for the storage group containing the affected databases.stm file).stm files. these resources include the Microsoft Exchange System Attendant service (MSExchangeSA). When you perform an offline backup. A database in an inconsistent state has not been detached from the transaction log stream. the SMTP virtual server. There are two distinct forms of recovery: soft recovery and hard recovery. Although there are two files. the database is detached from the log stream. and the physical disk resource. users do not have access to their mailboxes.stm file.the Microsoft Exchange Information Store service (MSExchangeIS). online backup A backup made while the Exchange 2003 services are running.10 Exchange Server 2003 Disaster Recovery Operations Guide inconsistent state If your database is in an inconsistent state. public folder store The part of the Exchange store that maintains information in public folders. and also mailbox folders generated when a new mailbox is created for a user. think of them as the two halves of a single database. Soft recovery uses the checkpoint file to determine which transaction log file to start with when it sequentially replays transactions into databases. During failover. offline backup A backup made while the Exchange 2003 services are stopped. In an Exchange 2003 cluster. mounted drive A mounted drive is a drive that is mapped to an empty folder on a volume that uses the NTFS file system. Exchange mailbox stores contain data that is private to a user. the whole resource group is moved from the failed node to an available node. recovery When referring to Exchange databases. Affected databases are described as having been shut down in a dirty state. replay A process in which Exchange 2003 examines the transaction log files for a storage group to identify transactions that have been logged.edb file) and a streaming native Internet content (.edb and . A mailbox store is made up of a rich-text (. and can be mounted only after the appropriate transaction log replay has been done. soft recovery An automatic transaction log file replay process that occurs when a database is remounted after an unexpected stop. and left in a consistent and mountable state. This process. A public folder store is made up of a rich-text . but they are assigned drive paths instead of drive letters. brings the databases up-to-date with the transaction log files. also known as playing back log files. the . Mounted drives function the same way that other drives function.edb file. the Microsoft Search (MSSEARCH) service. it cannot be remounted. routing information. mailbox store A database for storing mailboxes in Exchange. instead of two distinct databases. but have not been incorporated into the databases of that storage group. restore To return the original files that were previously preserved in a backup to their location on a server. You can use a mounted drive to add another drive to a computer with all 26 possible drive letters already used. . and a streaming native Internet content . resource groups are collections of resources that are managed as a single unit. After the replay. This process makes the databases up-to-date with all recorded transactions.

This collection includes all the files and folders that Windows created in both the boot and system partitions. Windows backup set The most basic collection of files and folders that is required to preserve a backup of the Windows Server 2003 operating system. . The collection also includes the System State data that are preserved along with the Windows Server 2003 operating system files and folders in the same backup. This partition contains the %systemroot% folder and the %programfiles% folder. transaction log files Files that contain a record of the changes made to an Exchange 2003 database. unfinished transactions can be restored by replaying the transaction log files into the database. All changes to the database are recorded in the transaction log files before they are written into the database files.Introduction 11 system partition The hard disk partition where your Windows Server 2003 operating system is installed. If a database shuts down unexpectedly.

com/fwlink/? LinkId=28310). you can continue to Chapter 2 of this guide. online Help (http://go. Standard Edition. It is best to practice backup and restore procedures in a test environment before you back up or restore your organization's production servers. see the online Help in your Windows Server 2003 operating system. . selected files. see "Backing up and restoring data" in the Windows Server 2003. Backup helps you to back up directories." Chapter 1 of this guide explains the basics of using Backup. some of the information in this chapter will make more sense when you perform the backup and restore steps that appear in later chapters. and System State data. Chapter 1 contains the following sections about Backup: • Starting Backup • Selecting the Default Settings for Backup • Using Backup to Back Up Your Data • Using Backup to Restore Your Data For information not covered in this chapter.C H A P T E R Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 1 This guide explains how to use the backup utility (Backup) in Microsoft® Windows Server™ 2003 to back up and restore your Exchange Server 2003 organization. If you are already familiar with Backup. If you are new to backup and restore procedures.microsoft. The backup utility (Backup) in Windows Server 2003 is similar to earlier versions of the utility. You can also use Backup remotely over the network to back up Exchange databases and information about other computers. "Backing Up Exchange Server 2003. You can use Backup to back up and restore both Windows Server 2003 and Exchange 2003 data. including Windows Server 2003 operating system registry information. For complete details about Backup and how to troubleshoot it.

For this reason. This process opens the Backup or Restore Wizard (Figure 1. type NTBackup. you might need to use advanced settings that are not available in the basic Backup or Restore Wizard. . Always start in wizard mode. and then click OK. Figure 1. 2.1). Click the Advanced Mode link to open Backup in Advanced Mode (Figure 1.2).Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 13 Starting Backup The following procedure describes how to start Backup. To switch to Advanced Mode 1. To start Backup • Click Start.1 Note The Backup or Restore Wizard To back up and restore critical data in your Exchange 2003 organization. the procedures in this guide use Advanced Mode exclusively. click Run. Clear the check box.

2 Note Backup in Advanced Mode To switch back to the basic Backup or Restore Wizard. on the Tools menu.14 Exchange Server 2003 Disaster Recovery Operations Guide Figure 1. click Switch to wizard mode. For more information about these options. see the procedure "To switch to Advanced Mode" earlier in this chapter. Selecting the Default Settings for Backup You can specify the default settings used in Backup for every backup and restore that you perform. Start Backup in Advanced Mode. To specify the default settings for Backup 1. click Options. Table 1.1 provides detailed descriptions of the options available on the General tab. On the Tools menu.3). . On the General tab. For details. 2. either clear or select the check boxes to select the default settings that you want (Figure 1. see the online Help in your Windows Server 2003 operating system.

if you want to restore data from several tapes. This might take several hours if your backup set is very large. This is the fastest way to build an on-disk catalog. Backup will then scan your whole backup set (or as much of it as you have). Compute selection information before backup and restore operations.1 Option The General tab in the Options dialog box Explanation of the available General options Explanation Estimates the number of files and bytes that will be backed up or restored during the backup or restore operation. However. . and the tape with the on-media catalog is missing or you want to restore data from media that is damaged. do not select this option. Use the catalogs on the media to speed up building restore catalogs on disk.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 15 Figure 1.3 Table 1. and build an on-disk catalog. Specifies that you want to use the on-media catalog to build the on-disk catalog for restore selections. This information is calculated and displayed before the backup or restore begins.

and you save the file to a floppy disk. Displays a dialog box when new media is detected by Removable Storage. (This option does not verify Exchange databases. Displays a dialog box when you start Backup. and Removable Storage is not running. save the file to a floppy disk. Displays a dialog box when you start Backup. do not select this option. Show alert message when new media is inserted. only the path information for the mounted drive will be backed up. a hard disk. If you want all new media to be available to the Backup program only. Show alert message when I start the Backup Utility and Removable Storage is not running. .) Explanation Compares the backed-up data and the original data on your hard disk to make sure that they are the same. or any type of removable disk. or any type of removable disk. use different media or designate another file. If there are many verification errors. select this option. select this option. do not select this option.16 Exchange Server 2003 Disaster Recovery Operations Guide Option Verify data after the backup completes. and you prompting. a hard disk. If you primarily back up data to a tape or other media that is managed by Removable Storage. If you typically back up data to a file. If you primarily back up data to a tape or other media that is managed by Removable Storage. If you select this option. It is recommended that you only verify backups of data files System backups are difficult to verify because of the large number of changes that happen to system files on a continual basis. do not select this option. Back up the contents of mounted drives. the time it takes to perform an Exchange database backup increases substantially. there might be a problem with the media or the file you are using to back up data. and then you back up a mounted drive. Some data files that were in use during the backup might also cause verification errors. or any type of removable disk. and no one is using Removable Storage to manage new media. although this option helps you verify data integrity in some types of data backups (for example. and run the backup operation again. but you can generally ignore these errors. System State backups and full computer backups). the data that is on the mounted drive will be backed up. Show alert message when I start the Backup Utility and there is recognizable media available. Backs up the data that is on a mounted drive. If you do not select this option. Important Do not select this option when you back up Exchange databases. If you typically back up data to a file. If you primarily back up data to a file. and you save the file to a floppy disk. If you primarily back up data to a tape or other media that is managed by Removable Storage. If you select this option. a hard disk. do not select this option. select this option. If this behavior occurs. If you primarily back up data to a file. a hard disk. Backup will then start Removable Storage automatically. select this option. and then you back up a mounted drive. or any type of removable disk. and there is new media available. Always allow use of Automatically moves new media that is detected by Removable Storage recognizable media without to the Backup media pool. and you save the file to a floppy disk.

5). you make sure that all the restored operating system or Exchange files will match the file versions that were preserved in your Windows or full computer backup as closely as possible. You might receive an error message after you select the default setting. Selecting this option prevents file version conflicts when you restore a backup over a fresh installation of your Windows Server 2003 operating system. In contrast. • Always replace the file on my computer. such as MAPI32. . not to their original location. System State data always overwrites the existing operating system files. These files include the Exchange . • Replace the file on disk only if the file on disk is older. Then click one of the following options: • Do not replace the file on my computer (recommended). 4.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 17 3. If this behavior occurs. Figure 1. Click the Restore tab to display the options for restoring a file that already exists on your computer (Figure 1. When you restore an Exchange database. and will alert you to that fact before the restore process begins. Do not replace the file on my computer (recommended) when you restore your operating system.4). Click the Backup Type tab to select the default backup type (Figure 1. The files in your backup should be the most current versions if you keep the computer up-todate with service packs and other critical updates before you back up your Windows Server 2003 operating system or the Exchange folder.dll files. which exists in the %systemroot%/System32 folder. and ensures that the most current file versions that were preserved in your backup overwrite older versions that the Windows Server 2003 Setup program created. always replace the existing database files. when you restore your operating system. select the setting.DLL. Exchange log files that existed before the restore are not affected because Exchange log files are restored to a temporary directory. Select Always replace the file on my computer if you want to restore your operating system or the Exchange installation folder (or both) from a backup.4 The Restore tab in the Options dialog box Important The settings that you select on the Restore tab do not affect the Exchange database restore process. In this way. Always replace the file on my computer to force all the files in your backup to overwrite the existing files.

The Backup Type tab in the Options dialog box In the Default Backup Type list. • 6. (The archive attribute is cleared. you need only the most recent copy of the backup file or tape to restore all the files.) To back up files between normal and incremental backups. Important To restore from backup. • Incremental An incremental backup entails backing up only those files created or changed since the last normal or incremental backup. (The archive attribute is not cleared. you must have the most recent normal. • Normal A normal backup entails copying all the files that you selected.18 Exchange Server 2003 Disaster Recovery Operations Guide Figure 1. • Daily A daily backup entails copying all the files that you selected and that are also modified on the same day that you perform the daily backup. (The archive attribute is cleared. (The archive attribute is not cleared.5 5. perform a copy backup because it does not affect other backup operations. Copy A copy backup entails copying all the files that you select. differential. select one of the following backup types. you must have the last normal backup set and also the last differential backup set. but not marking files as having been backed up. When you select the Detailed option. all attempts to back up or restore a single file are logged. Normal backups are frequently referred to as full backups. you must have the last normal backup set and also all incremental backup sets to restore your data. The backed up files are not marked as having been backed up. This is a valuable troubleshooting tool if the backup or restore process completes with errors. Therefore. but not marking each file as having been backed up. and then marking files as having been backed up. although a backup is only a full backup when you choose to back up all files.6).) To perform a normal backup. you can search the backup log at the end of the backup or restore process for all failures that occurred when files were copied or restored. (The archive attribute is not cleared.) To perform a combination of normal and differential backups. and incremental backup files.) Click the Backup Log tab to display the options for setting the level of detail that you want to use when backup logs are created for backups and restores (Figure 1. • Differential A differential backup entails copying files created or changed since the last normal or incremental backup. and then marking each file as having been backed up. You usually perform a normal backup the first time that you create a backup set. .) If you use a combination of normal and incremental backups.

You do not have to exclude additional files during an Exchange backup.6 7.7). . The Backup Log tab in the Options dialog box Click the Exclude Files tab to exclude certain types of files from your backup job (Figure 1. Figure 1. it is best to exclude only the default files.7 Note The Exclude Files tab in the Options dialog box In the Files excluded for all users list box.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 19 Figure 1.

These procedures apply to a generic backup. domain controllers.20 Exchange Server 2003 Disaster Recovery Operations Guide Using Backup to Back Up Your Data Use Backup to preserve all the critical data in your Exchange organization.8 Using Backup to perform a basic backup One subtle difference between the backup utility in Windows Server 2003 compared to the backup utility in Microsoft Windows® 2000 is the way that files that are marked for backup and restore appear in the user . The following topics give you the general information you need to configure and create backups using the backup utility (Backup) in Windows Server 2003: • • • • • • Performing a basic backup Selecting the destination for a backup Selecting options for a backup Scheduling a backup Checking the success of a completed backup Verifying backed up data Performing a Basic Backup Use the procedures in this section to back up your data by using Backup. see Chapter 2. and so on. For information about backing up Exchange. "Backing Up Exchange Server 2003." Figure 1. and are not Exchange specific.

see the procedure "To switch to Advanced Mode" earlier in this chapter. and then on the Job menu. or the name of an attached tape drive. Note For detailed information about the Backup destination list and the Backup media or file name box. although the Program Files node in figure 1. For details. 8. or folder that you want. folder or file that you want to back up. and then in the Backup Job Information dialog box. To perform a basic backup 1. click Advanced if you want to set advanced backup options such as data verification or hardware compression. file. It is possible for a check mark that appears dimmed to indicate that no files are going to be backed up if nothing in the node is scheduled for backup. 2. select the check box next to the drive. see "Selecting Options for a Backup" later in this chapter. such as File if you want to back up to a disk. In the Backup media or file name box. see "Selecting the Destination for a Backup" later in this chapter. type the backup media or file name to use for your backup. In the Backup destination list. 3. verify that the settings for the backup are correct. Click Start Backup.8 is checked. expand the node. For example. 4. In Backup Job Information. see "Selecting the Default Settings for Backup" earlier in this chapter. To see which files will be backed up or restored. 7. Note For detailed information about the Options dialog box.9 Caution The Backup Job Information dialog box If the backup file name you use for this backup already exists in the backup media or file location. click New. Start Backup in Advanced Mode.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 21 interface (UI). Click the Backup tab. Then. 5. Under Click to select the check box for any drive. Select the appropriate backup options. click a destination device for your backup. confirm that the settings in Backup Job Information are correct to avoid overwriting a backup file that you might want to keep. A cleared check box means that nothing in its corresponding node will be backed up or restored. there are no files in that node scheduled for backup. A check mark that appears dimmed indicates that only a part of the files and folders in that node will be backed up or restored. On the Tools menu. Figure 1. Note For detailed information about the options in the Backup Job Information dialog box. 6. click OK. click Options. and then click OK. .

see "Scheduling a Backup" later in this chapter. Figure 1. If you want to schedule this backup to run automatically at a later time.10 Set Account Information dialog box 13. and then click OK. see "Permissions Required" in the Introduction. If you want to perform this backup immediately. If you choose to schedule a backup. 11.22 Exchange Server 2003 Disaster Recovery Operations Guide Note For detailed information about advanced backup options. enter the user name and password you want Backup to use when it runs the scheduled backup. and then click Save. in Scheduled Job Options. Make sure that the account you specify has the necessary permissions. If you want to schedule a backup. click Schedule. Click Properties to enter the date. type a name for the scheduled backup job. 10.11 Note Scheduled Job Options dialog box For general information about scheduling backups. and frequency parameters for the scheduled backup. see "Selecting Options for a Backup" later in this chapter. in the Job name box. 9. If you choose to schedule the backup job. . click Start Backup. in Backup Job Information. time. in Set Account Information. in Save Selections. 12. For more information. Figure 1. specify a name for the backup job you want to schedule.

select a destination for the files you want to back up. You can back up the files to a hard disk. a tape device. or a variety of other supported devices. .Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 23 Selecting the Destination for a Backup Before you proceed with a backup.

Backup creates a catalog of the files that are being backed up in each backup job. Click Browse to select a location and file name for your backup. archive the . CD-R. or DVD-R.24 Exchange Server 2003 Disaster Recovery Operations Guide To select a destination for a backup 1. and the backup utility (Backup) in Windows Server 2003 indicates that unused media is not available. If you do not have a tape device installed on your computer. Standard Edition online Help (http://go. • Select a tape device if you want to back up files and folders to a tape. this option is selected by default and cannot be changed. see "Removable Storage" in the Windows Server 2003.com/fwlink/?LinkId=28313). Figure 1. see "Rebuilding a Catalog for a Restore" later in this chapter. Next. perform one of the following steps: • Select File if you want to back up files and folders to a file. you must first back up the data to a file. You can use this catalog to select the files that you want to restore from the backup media. the catalog can be re-created from the backup media if you restore data on a different or rebuilt computer. you might have to use the Removable Storage Management console to add your tape device to the Backup media pool. 2.12 The Backup destination and Backup media fields 4. For more information about re-creating the catalog.bkf file to the CD. . see the procedure "To switch to Advanced Mode" earlier in this chapter. To back up your data to these devices. If you are performing a backup. The computer on which the backup occurs stores the catalog. During a backup. Backup will not back up to a CD device such as CD-RW. CD-RW.12). From this point onward. 3. or DVD-R drives. For details. you can restore your data from that CD-R. Start Backup in Advanced Mode. In the Backup destination list. However. For more information.microsoft. Click the Backup tab (Figure 1.

They should be backed up as online Exchange databases. The Backup Job Information dialog box appears after you click Start Backup from the Backup tab (Figure 1. Explanation You can type a unique name to describe each backup.2 and 1. Selecting this option does not affect any previous backup data stored on that media. see the online Help in your Windows Server 2003 operating system.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 25 Selecting Options for a Backup When you back up your data. .2 Backup options Backup options Backup description Append this backup to the media. Figure 1. you have the option to change the default settings for the backup set before the process begins. You can append the backup job to an existing backup file or tape.3 provide explanations of the available options. You should specifically exclude Exchange data directories from being backed up normally if you are performing online backups.13 Backup and advanced backup options Configure standard and advanced backup options in the Backup Job Information and the Advanced Backup Options dialog boxes (Figure 1. see Chapter 2. You can also configure advanced options. Tables 1.13). For more information about how to back up Exchange databases. "Backing Up Exchange Server 2003. Important Exchange databases should not be backed up in the same way you backup static data files.12). For more information about these options." Table 1.

You can verify that the backed up data matches the original data after the backup completes. Allow only the owner and the Administrator access to the backup data. you will lose all previous backup data currently stored on the destination media. (Do not use this option when you back up Exchange databases. If you do not select this option.26 Exchange Server 2003 Disaster Recovery Operations Guide Backup options Replace the data on the media with this backup. Additionally. you cannot select this option because ownership of the tape has already been established. You can specify that only the owner or members of the Administrator's group may access the data that is saved on the destination media. Explanation You can back up data that has been designated for Remote Storage. You can restore Remote Storage data only to an NTFS file system volume. System State backups and full computer backups). If you are backing up data to an existing tape or file that you want to overwrite. Explanation You can erase the backup file or all previous backup jobs stored on the destination media before the new backup job is saved. At the end of a successful backup. Table 1. Although this option helps you verify data integrity in some types of data backups (for example.3 Advanced backup options Advanced backup options Back up data that is in Remote Storage. The only added value that this option provides in this case is to verify that the media can still be read immediately after it was written to. If you are backing up data to an existing tape or file and you are appending the data to the tape or file. although the backed up Exchange database files were compared to the originals on disk after the backup. the verification would fail because the online databases are constantly changing during a backup. you can select this option. Remote Storage reparse points are not backed up. every file in the backup is read and compared to the checksums that are also stored in the backup to make sure that the file in the backup matches the checksum created at the time the file was backed up. This option secures the online tape or file. Selecting this option will substantially increase the time that the backup takes to complete. a subtle distinction to understand. Verify data after backup. This means that you are verifying the media instead of verifying that the file in the backup still matches the original at the end of the backup. and stores those checksums in the actual backup. Selecting this option backs up Remote Storage reparse points (placeholder files).) . Important Do not use this option when you back up Exchange databases. Caution If you select this option. do not use this option when you back up Exchange databases. Backup creates a checksum for every file as it is backed up.

You can schedule a backup job by using Backup to specify the times that you want your backups to run. you do not have a tape drive on your computer or your tape drive cannot manage compressed data. For a list of all the available backup switches. Note It is recommended that you do not disable this option. but disabling this option might cause nonExchange files that are open or in use during the backup to be skipped. Selecting this option does not affect Exchange online backups of the Exchange store. In most Exchange organizations. The IIS metabase contains information such as your Exchange Virtual Server (EVS) information. Backup Type. compress the backup data to save space. Important Make sure that the Task Scheduler service is running before you schedule a backup. If this option is disabled. You can use the Services snap-in to start. Although this option substantially increases the size of a normal backup job. You can back up all the system files that are in your systemroot directory in addition to the boot files that are included with the System State data. at a command prompt. view the command line parameters for Backup by typing ntbackup /? at a command prompt. Explanation You can compress the data that you plan to back up so that you can save more data on a tape. Note This option is enabled by default for a System State backup. For example. Scheduling a Backup If you configure Backup to run backup jobs automatically. (Do not disable this option. see "Selecting the Default Settings for Backup" earlier in this chapter. For more information about how to schedule a backup. It is recommended that you do not disable this option. see "Performing a Basic Backup" earlier in this chapter. You can disable the use of shadow copy to create the backup. it benefits Exchange backups because it backs up the Internet Information Services (IIS) metabase. type net start schedule. For a description of the different types of backups. stop.) skipped. you cannot perform an incremental backup of an Exchange store until you have performed a normal backup at least one time before the incremental backup. Exchange 2003 does not use the Volume Shadow Copy service in Backup when it backs up the Exchange store. You can also schedule a backup to run at a scheduled time by referencing the backup job in a batch file by using the command line switches for Backup (NTBackup. .) Disable volume shadow copy. Automatically backup System Protected Files with the System State.exe). To make sure that Task Scheduler is running. and view the status of services. If this option is disabled. You can specify how your data is backed up. you can save administrative time and provide a way to run unattended backup jobs during off-peak hours. some files that are open or in use during the backup might be (Do not disable this option.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 27 Advanced backup options If possible. it is best to perform the largest backup types (such as normal backups of the Exchange databases) when user access to servers is at a minimum.

After a backup job completes.28 Exchange Server 2003 Disaster Recovery Operations Guide Checking the Success of a Completed Backup Your ability to restore data and servers depends on the quality of your backups. see "Selecting the Default Settings for Backup" earlier in this chapter. it is important to verify that a backup is successful. If you receive error messages during a backup and want more detailed data about the failure. Figure 1. make sure that the Backup Progress dialog box displays Status: Completed (Figure 1. To verify that a backup completed without errors 1. For more information about enabling detailed logging. you can perform the backup again by using detailed logging. The following is an example of a backup log of a Windows backup.14 2. . the log file is set to record only a summary of the backup job that is performed. Then you can search the log file to find out exactly what happened. The Backup Progress dialog box Click Report to view the backup log file to determine whether any errors occurred during the backup. including the Exchange folder.14). Therefore. A successful backup is one that completes without errors. By default. which completed without errors: ---------------------Backup Status Operation: Backup Active backup destination: File Media name: "Windows Backup created 3/11/2004 at 5:28 PM" Backup (via shadow copy) of "C: BOOT" Backup set #1 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Media name: "Windows Backup created 3/11/2004 at 5:28 PM" Backup Type: Normal Backup started on 3/11/2004 at 5:31 PM.

988. Backup completed on 3/11/2004 at 5:56 PM.083. Backup completed on 3/11/2004 at 5:48 PM.436 Time: 5 minutes and 0 seconds Backup (via shadow copy) of "System State" Backup set #4 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Media name: "Windows Backup created 3/11/2004 at 5:28 PM" Backup Type: Copy Backup started on 3/11/2004 at 5:53 PM.025. Backup completed on 3/11/2004 at 5:53 PM. Directories: 257 Files: 3551 Bytes: 1.569 Time: 16 minutes and 55 seconds Backup (via shadow copy) of "F: Exchange" Backup set #3 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Media name: "Windows Backup created 3/11/2004 at 5:28 PM" Backup Type: Normal Backup started on 3/11/2004 at 5:48 PM.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 29 Backup completed on 3/11/2004 at 5:31 PM.597 Time: 2 minutes and 36 seconds ---------------------- .337 Time: 1 second Backup (via shadow copy) of "D: System" Backup set #2 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Media name: "Windows Backup created 3/11/2004 at 5:28 PM" Backup Type: Normal Backup started on 3/11/2004 at 5:31 PM.069.919. Directories: 1675 Files: 12925 Bytes: 1. Directories: 189 Files: 2624 Bytes: 461.675. Directories: 3 Files: 29 Bytes: 2.

Verify completed on 3/11/2004 at 5:58 PM.675. Directories: 1675 Files: 12925 Different: 0 Bytes: 1.569 Time: 1 minute and 18 seconds Verify of "F:" Backup set #3 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Verify started on 3/11/2004 at 5:57 PM.988.083.337 Time: 1 second Verify of "D:" Backup set #2 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Verify started on 3/11/2004 at 5:56 PM.bkf Verify of "C:" Backup set #1 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Verify started on 3/11/2004 at 5:56 PM. Verify completed on 3/11/2004 at 5:57 PM.436 Time: 34 seconds Verify of "System State" Backup set #4 on media #1 Backup description: "Windows Backup created 3/11/2004 at 5:28 PM" Verify started on 3/11/2004 at 5:58 PM.30 Exchange Server 2003 Disaster Recovery Operations Guide Verify Status Operation: Verify After Backup Active backup destination: File Active backup destination: H:\Windows Backup 3-11-04. Directories: 257 Files: 3551 Different: 0 Bytes: 1.919. Verify completed on 3/11/2004 at 5:56 PM. Verify completed on 3/11/2004 at 5:58 PM. Directories: 189 Files: 2624 .025. Directories: 3 Files: 29 Different: 0 Bytes: 2.

597 Time: 16 seconds ---------------------- .Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 31 Different: 0 Bytes: 461.069.

Close Event Viewer after you have looked for errors. you cannot test public folder backups this way. You might have to scroll to the bottom of the log file to find the information that relates to the most recent backup. and then click Event Viewer. You probably cannot verify all backups from all servers.microsoft. 8. make sure that there are no Error entries reported in the application event log that have "NTBackup" or "ESE" (the Extensible Storage Engine) as their source. Event 8000 indicates the start of the backup and Event 8019 indicates the end. .microsoft. Finally.com/fwlink/?LinkId=23233). If you enabled verification for this backup job. and storage location of your backup media are critical to the success of your disaster recovery strategy. Verifying Backed Up Data To verify data. see "Ensuring the Integrity of Your Backups" in the Exchange Server 2003 Disaster Recovery Planning Guide (http://go. see Using Exchange Server 2003 Recovery Storage Groups (http://go. 4. by rotating a simulated Exchange restore process in a test domain using backups from various production servers. These errors indicate that the backup has not been completely successful. Reviewing both the backup log and the application event log in Event Viewer helps you verify the success of a backup. In Event Viewer. you can use recovery storage groups to test restore procedures for an Exchange database. For more information about these important factors.com/fwlink/?LinkId=21277).32 Exchange Server 2003 Disaster Recovery Operations Guide 3. click Application. Note that some files change regularly. Verifying the data from a backup also helps you train administrators to perform restore procedures. However. Important This step is essential when you back up Exchange data. you can view the Verify Status section of the log file to see which files in the backup (if any) do not match the original files on disk by looking at the Different: line in the log file. Make sure that there are no errors in the backup log file. Click Start. Some errors that occur will only show up in the application event log. Do not rely only on the backup logs when you back up Exchange. This strategy helps you identify potential problems before a real disaster happens. point to Administrative Tools. 5. However. Check the backup log file for errors. quality. In the details pane. in the console tree. you restore the preserved data from your backup media to a test domain. you can test the reliability of your system. For more information about recovery storage groups. and a discrepancy between files does not always indicate a problem. look for events that indicate when the backup and verification processes started and completed. If you do not have a separate test domain. Then review any events that occurred in between. Note Each backup job adds information to this log file. remember that the condition. and then make sure that you can access the data. 6. point to All Programs. Close the log file and the Backup Progress dialog box. Note To speed up your search. 7. Training familiarizes administrators with the restore process so that they can respond quickly and appropriately to a real disaster. It is a good idea to research and resolve errors or inconsistencies in the logs as soon as possible. particularly in a large organization.

see "Rebuilding a Catalog for a Restore" later in this chapter. Figure 1. see "Performing a Basic Backup" earlier in this chapter. select the location where you want the files restored. you might have to rebuild the catalog. Rebuilding a catalog for a restore. Checking the success of a completed restore job. 3. 2. For more information. To perform a basic restore 1. Click the Restore and Manage Media tab. If the catalog for the backup that you want to restore does not appear. see the procedure "To switch to Advanced Mode" earlier in this chapter.15 The Restore and Manage Media tab Remember that the way that selected files appear in the UI of the Windows Server 2003 version of Backup differs slightly from earlier versions of Backup. and Exchange databases) that were previously backed up. The following topics provide the information you need to restore items using Backup: • • • • Performing a basic restore.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 33 Using Backup to Restore Your Data The backup utility (Backup) in Windows Server 2003 helps you restore items (including files. In the Restore files to list. folders. For details. the location specified is Original location. For details. . Start Backup in Advanced Mode. By default. Performing a Basic Restore Use the procedures in this section to restore your data by using Backup.15). Selecting the advanced options for a restore. the System State data. and then select the files that you want to restore (Figure 1.

In Confirm Restore. If the catalog is missing or if you are restoring the files to a different computer or to a clean installation of your Windows Server 2003 operating system. . if you store multiple backup jobs in the same backup file. 3. click Advanced to specify advanced restore options. When you select a check box with a question mark inside. To rebuild a catalog 1. 5.34 Exchange Server 2003 Disaster Recovery Operations Guide 4. The Restore and Manage Media tab displays the files available to be restored by reading this catalog. Click Start Restore. or click OK to start the restore. Note For more detailed information about advanced restore options. 4. Backup creates a catalog on the local computer that lists all the files in the backup set. On the Restore and Manage Media tab. You can delete any catalogs that you no longer want from the Restore and Manage Media tab. For details. and then click Catalog. see the procedure "To switch to Advanced Mode" earlier in this chapter. Start Backup in Advanced Mode. However this will leave question marks for any items contained in that node. and then click Delete Catalog. Click the Restore and Manage Media tab. you must rebuild the catalog. For example. and then click OK (Figure 1. cataloging the backup set will create the top node for each of the different backup jobs performed. 2. see "Selecting the Advanced Options for a Restore" later in this chapter. Rebuilding a Catalog for a Restore When you back up your data. type the path and the file name of the backup file that you want to catalog. In Open Backup File.16). you will be prompted again for the path and file name of the backup file you are cataloging. right-click the media that you want to restore files from. Sometimes this only creates the top node of the tree in the backup set. Right-click each catalog.

Note These options are not present in Exchange database restores. see "Performing a Basic Restore" earlier in this chapter. You configure advanced restore options while you restore data.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 35 Figure 1. you can configure advanced restore options before you start to restore the files you have selected.16 Rebuilding the catalog Selecting the Advanced Options for a Restore When you restore most types of data by using the backup utility (Backup) in Windows Server 2003. To view the complete procedure for restoring data.17 The Advanced Restore Options dialog box . Figure 1.

17). the junction points will be restored as common directories and the data that the junction points point to will not be accessible. For more information about these options. click Advanced to open the Advanced Restore Options dialog box (Figure 1. If you do not select this check box. For example. Explanation You can restore security settings for each file and folder.36 Exchange Server 2003 Disaster Recovery Operations Guide To configure advanced restore options. The whole server cluster will therefore be down during an authoritative restore of the data on the quorum disk resource. you must select this check box. mark the restored data as the primary data for all replicas. Restore junction points. Table 1. By doing this. If you do not select this check box. You can ensure that the quorum database is restored and replicated on all nodes in a server cluster. Select this option only when you restore the first replica set to the network. If you select this option. When restoring replicated data sets. audit entries. Security settings include permissions. select this option if you are restoring data to a replacement drive and you have already partitioned the drive. A primary restore ensures that restored File Replication Service (FRS) data is replicated to your other servers. you will only restore the folder containing the mounted drive. Do not use this option if one or more replica sets have already been restored. Preserve existing volume mount points. You can restore the junction points on your hard disk and also the data that the junction points point to. . If you are restoring a mounted drive and you want to restore the data that is on the mounted drive.4 provides explanations of the advanced options. This option is available only under two conditions: if you have backed up data from an NTFS file system volume used in the Windows Server 2003 operating system. Backup will stop the Cluster service on all the other nodes of the server cluster after the node that was restored is restarted. Do not select this option if you are restoring data to a partition or drive that you have recently reformatted. you ensure that your volume mount points are not restored. You can perform a primary restore. and restored its volume mount points. formatted it. Table 1. see the online Help in your Windows Server 2003 operating system.4 Advanced restore options Advanced restore options Restore security. and restore file and folder data under junction points to the original location. and ownership. and you are restoring that data to an NTFS volume used in a Windows Server 2003 operating system. Restore the Cluster Registry to the quorum disk and all other nodes. see the online Help in your Windows Server 2003 operating system. You can prevent the restore operation from overwriting any volume mount points that you have created on the partition or volume that you are restoring data to. This option is useful when you are restoring data to a whole drive or partition. in the Confirm Restore dialog box. For more information. and you want to restore the old volume mount points.

Unable to restore data to SERVER01\Microsoft Information Store\First Storage Group. the restore was not successful. which displays the errors that occurred. When the restore completes. or Status: Failed. Restore completed on 1/28/2004 at 11:01 PM. Note Each session of Backup adds information to this log file. make sure that the Restore Progress dialog box shows Status: Completed (Figure 1. You might have to scroll to the bottom of the log file to find the log information that relates to the most recent restore attempt. click Report to view the Report log file. If the status displays Status: Completed with Errors. The following is an example of a restore log with errors: ---------------------Restore Status Operation: Restore Backup of "SERVER01\Microsoft Information Store\First Storage Group" Backup set #1 on media #1 Backup description: "Set created 12/27/2003 at 3:12 PM" Restore started on 1/28/2004 at 11:01 PM. If errors exist.Chapter 1: Using the Backup Utility in Windows Server 2003 to Back Up and Restore Your Data 37 Checking the Success of a Completed Restore Job It is important to verify that the restore occurred without errors.18 Restore completed successfully If the restore failed or had errors.18). Figure 1. check the application event log for more information. Directories: 0 Files: 0 Bytes: 0 Time: 1 second ---------------------- . research the possible causes of the errors.

38 Exchange Server 2003 Disaster Recovery Operations Guide

By default, the Restore log file is set to record only a summary of the restore process. If you receive error messages during the restore and want more detailed data to troubleshoot the problem, you can perform the restore again using detailed logging, and then search the log to find out exactly what happened. For more information about enabling detailed logging, see "Selecting the Default Settings for Backup" earlier in this chapter. When you have finished checking the Restore log, make sure to also check the application event log for errors.

To check the application event log for errors
1. Open Event Viewer: Click Start, point to All Programs, point to Administrative Tools, and then click Event Viewer. 2. In Event Viewer, in the console tree, click Application. In the details pane, make sure that there are no errors reported in the application event log that indicate the restore was unsuccessful. 3. If you notice any events that disclose an error, double-click the event to open the Event Properties, and then read the description of the event. 4. Research and resolve errors or inconsistencies as soon as possible. For more information about the error, click the URL in the Description box, or search for relevant articles in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=18175). 5. After you have checked for errors, close Event Viewer. When the Status field in the Restore Progress dialog box is marked as Completed, it means that Backup has successfully finished copying files to their appropriate destinations. However, if you are restoring an Exchange database, transaction log file replay needs to finish before you mount the database. For more information about this issue, see "Make Sure That the Restore Process Was Successful" in Chapter 3.

C H A P T E R

Backing Up Exchange Server 2003

2

The Exchange Server 2003 Disaster Recovery Planning Guide (http://go.microsoft.com/fwlink/? LinkID=21277) will help you determine your disaster recovery strategy. After you have chosen your strategy, use the information in this chapter to perform the appropriate backup tasks by using the backup utility (Backup) in Microsoft® Windows Server™ 2003. This chapter covers the following backup-related tasks: • Data to exclude from Windows backup sets or full computer backup sets. • Creating Windows backup sets. • Creating full computer backup sets. • Backing up domain controllers. • Backing up Exchange Server 2003 data. • Backing up Exchange Server 2003 clusters. Several additional backup methods might suit your needs. For example, you can use Automated System Recovery, make shadow copies, and create drive images. For more information about these backup methods, see "Disaster Recovery" in the Windows Server 2003, Standard Edition online Help (http://go.microsoft.com/fwlink/?LinkId=28311). If you want to use third party software to back up and restore your Microsoft Exchange Server 2003 data and infrastructure, use this chapter to make sure that you back up the appropriate data. For specific procedures, see the documentation for the third party software. The procedures in this chapter apply only to the backup utility (Backup) in Windows Server 2003.

Data to Exclude from Windows Backup Sets or Full Computer Backup Sets
Do not back up the following directories and drives when you create either Windows backup sets or full computer backup sets. • Installable File System (IFS) drive By default, the IFS drive (frequently referred to as the M drive) is turned off in Exchange Server 2003. If you have enabled the IFS drive, make sure to clear the check box in the backup utility (Backup) in Windows Server 2003 before you back up your data. Important
If you back up the IFS drive, you might damage your Exchange databases. To avoid this type of damage, do not enable the IFS drive. Antivirus software and other programs that affect all drives might also damage or cause problems for Exchange. For more information, see Microsoft

40 Exchange Server 2003 Disaster Recovery Operations Guide

Knowledge Base article 298924, "XADM: Do Not Back Up or Scan Exchange 2000 Drive M" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=298924).

and clear the Microsoft Information Store check box (under the Microsoft Exchange Server node). see "Backing Up Exchange Server 2003 Databases" later in this chapter. it is recommended that you back them up by selecting the Microsoft Information Store option under Microsoft Exchange Server in Backup. back up your Exchange server's database and transaction log files as part of a separate backup. For this reason. . Any attempts to restore the backup might cause problems. the files that are in use at the time that the backup occurs are not backed up. Instead... drive M). Figure 2.1). When you create Windows or full computer backup sets.Chapter 2: Backing Up Exchange Server 2003 41 • Exchange databases and log files Because Exchange database and transaction log files are constantly changing. do not select the .\Exchsrvr\MDBDATA folder in Backup (Figure 2.\Exchsrvr\MDBDATA folder If your backup includes the drives or folders that contain your Exchange database and transaction log files or the Exchange IFS drive (by default. do not back up Exchange data when you create Windows or full computer backup sets. For information about how to back up Exchange databases and log files.1 Do not back up the . Selecting this option causes Backup to use the Extensible Storage Engine (ESE) to back up your database and transaction log files correctly.

including both the System State data and the operating system files. Because Windows backup sets are typically created with the expectation that you will reinstall applications such as Exchange. is referred to as a Windows backup set. including Exchange 2003. by default. You must include the following data in a Windows backup set. and CD-ROM drives) that are not a part of your disaster recovery strategy. To customize the backup set. your boot partition and system partition are the same. Windows backups that are older than the tombstoneLifetime attribute might reintroduce deleted Active Directory® directory service objects. but plan to reinstall all your applications. you can avoid problems and delays when you restore data. you must back up both the System State data and the operating system files. It is also best to test your backup sets in a test environment.) Note If you installed your Windows Server 2003 operating system to the hard disk partition that is used to start your computer. A backup of Windows Server 2003. omit unnecessary files from it. • Creating Windows Backup Sets Create Windows backup sets when you want to restore your System State data from a backup.) The system partition. you do not typically include the drives of the server cluster's shared disk resources (for example. see "Backing Up an Exchange Server 2003 Cluster's Shared Disk Resources" later in this chapter. Files restored from System State data will always overwrite the originals. You can customize the backup set to speed up both the backup and restore processes. The boot partition. Changes to your Windows Server 2003 operating system might include the installation of a service pack or other update. . (The disk partition where your Windows Server 2003 operating system is installed. This time limit exists because of the value of the tombstoneLifetime attribute of the organization. and you must include all this data in one backup: • • • The System State data. For more information about how to back up a server cluster's shared disk resources. By keeping your Windows backups up-to-date. Because of the dependencies among System State components. Operating system files include the boot partition and the system partition. In the backup utility (Backup) in Windows Server 2003. To completely back up the operating system of a server that is running Windows Server 2003. select the System State data option to back up your System State data along with these partitions. if you can—and whenever a change is made to your Windows Server 2003 operating system. the drive where you store your quorum disk resource or the drives where you store your Exchange database files and log files). Only omit files that you are certain are not part of your Windows Server 2003 operating system. you do not have to back up your applications when you create a Windows backup set.ini in the root directory. floppy drives. Create Windows backup sets frequently—weekly. or any process that makes a lot of registry changes. do not back up the removable storage media (such as removable disk drives. such as Microsoft Internet Explorer. Do not omit anything that was installed during Windows Server 2003 setup. For example. you cannot use Backup to back up or restore individual components of System State data.42 Exchange Server 2003 Disaster Recovery Operations Guide • The cluster shared disk resources (if you are running Exchange on a cluster) In a full computer backup set. You must back up these resources by using the System State option and the Microsoft Information Store option in Backup. Removable Drives To save disk space for your Windows or full computer backup set. This partition contains hidden files such as NTLDR and BOOT. and also the time required to create and restore backups. large media files such as training videos are likely candidates for omission. Windows backup sets are valid for a limited time only—60 days. If you are not sure about a file. (The disk partition from which your computer starts. back it up.

and click OK. Assume that any backup older than the tombstoneLifetime attribute is not valid.2). Figure 2. 2. Selecting a System State backup Clear the check boxes that are next to anything that you do not want to back up.com/fwlink/? LinkId=3052&kbid=216993). see Microsoft Knowledge Base article 216993. Start Backup in Advanced Mode: Click Start. Navigate to the Exchsrvr folder (by default. Then click the Advanced Mode link on the Welcome screen. <drive>:\Program Files\Exchsrvr). click Run. In the console tree.3). Remember that a Windows backup set should not include Exchange. type ntbackup. Select the Backup tab. .Chapter 2: Backing Up Exchange Server 2003 43 Therefore.microsoft. to your organization. and then select the check box next to System State (Figure 2. To create a Windows backup set 1.2 3. For related information. problems might arise if you try to introduce a member server. select the check box next to the drive letter (or letters) for your boot partition and system partition. whose System State data is older than the tombstoneLifetime attribute. "Backup of the Active Directory Has 60-Day Useful Life" (http://go. and then clear the check boxes under Exchsrvr and any other applications that you do not want to back up (Figure 2.

5. 7. . For more information about how to verify the success of a backup.44 Exchange Server 2003 Disaster Recovery Operations Guide Figure 2. To confirm that you will not back up any part of Exchange. Select Browse to select the location and file name for your backup.3. In the Backup destination list. 8. 6. perform one of the following steps: • Select File if you want to back up files and folders to a file. in the Backup description text box. In Backup Job Information. make sure that all check boxes under Exchsrvr are cleared as shown in Figure 2. 4. which indicates that some files in the Exchsrvr node will not be backed up. Caution Do not select the drives or folders that are listed as exceptions in the section "Data to Exclude from Windows Backup Sets or Full Computer Backup Sets" earlier in this chapter. • Select a tape device if you want to back up files and folders to a tape. For more information about how to set the options for the backup. set the appropriate options. see "Selecting Options for a Backup" in Chapter 1.3 Clear the check box that is next to Exchange The check box next to Exchsrvr appears dimmed. Click Start Backup. this option is selected by default and cannot be changed. After the backup completes. The check symbol remains in the check box although there is nothing selected for backup in that node. verify that it was successful. and then click Start Backup. type a backup description. see "Checking the Success of a Completed Backup" in Chapter 1. If a tape device is not installed on your computer.

Unlike Windows backup sets. such as swap files and temporary files. Windows Server 2003 must function sufficiently well after a disaster to allow you to restore your full computer backups. click Run. you do not have to repair or reinstall Windows Server 2003 if you can restore a disk image of the boot partition (which contains the files that start the operating system) and the system partition (which contains the remaining operating system files). 2. located on drive C). 3. If the disaster renders your Windows Server 2003 operating system unusable. Backup does not back up specific file sets. you must repair or reinstall the operating system.. and all of your applications. see the Exchange Server 2003 Disaster Recovery Planning Guide (http://go. Then click the Advanced Mode link on the Welcome screen.microsoft. Using Backup to Create Full Computer Backup Sets You can use the backup utility (Backup) in Windows Server 2003 to create full computer backup sets. Caution Do not select the drives or folders that are listed as exceptions in "Data to Exclude from Windows Backup Sets or Full Computer Backup Sets" earlier in this chapter. It is recommended that you do not include the . and your Exchsrvr directory (Exchange installation directory) as part of your full computer backup set.com/fwlink/?LinkID=21277). Therefore. the System State data. and click OK. see "Selecting the Default Settings for Backup" in Chapter 1. If you performed a full computer backup by using Backup. For more information about using disk images as part of your disaster recovery strategy. see your disk imaging software documentation. Select the check box next to each item that you want to back up. type ntbackup. Click the Backup tab. By default. Start Backup in Advanced Mode: Click Start. For information about how to exclude particular directories or file types from your full computer backup set.\Exchsrvr\MDBDATA folder in your backup set. the contents of your drives on a specific date). If a failure renders your Windows Server 2003 operating system unusable. Having a full computer backup set available is helpful if you want to make sure that you have a copy of all the data on your server (for example. this backup can be restored only by using Backup. Note Backup might not include all the files on a drive in a backup. For more information about how to restore disk images. full computer backup sets are typically created with the expectation that you will restore applications such as Exchange by restoring the full computer backup set instead of reinstalling them. and then restore your full computer backup. you must also include the System State data in this backup set. Important Although the drive contents of your computer make up the majority of the data in a full computer backup set.Chapter 2: Backing Up Exchange Server 2003 45 Creating Full Computer Backup Sets A full computer backup set includes all of the information in a Windows backup set plus most of the data on the hard drives of your computer. Important You must include the Windows boot partition and system partition (by default. . To create a full computer backup set by using Backup 1.

46 Exchange Server 2003 Disaster Recovery Operations Guide 4. Click Start Backup. 5. Next to the Backup media or file name box. . click Browse to select the media for your backup.

microsoft. After the backup completes. you also back up the Active Directory database. In addition to the System State data. For more information about how to verify the success of a backup. see the Exchange Server 2003 Disaster Recovery Planning Guide (http://go. in the Backup description text box.chk Edb*. 7. such as the Active Directory database and log files. Recommendations for backing up a domain controller. these files are located in the Active Directory folder in %SystemRoot%\Ntds.log and Res2.log Definition The Active Directory database. Backing Up the System State Data of a Domain Controller When you use Backup to back up the System State data of a domain controller. For more information about how to set the options for the backup. and all other files for the system components and services on which Active Directory depends. The following Active Directory files are part of a System State data backup of a domain controller. This section contains the following information about how to back up domain controllers: • • Backing up the System State data of a domain controller.1 Active Directory files to back up File type Ntds. The primary difference between backing up a domain controller and backing up an Exchange member server is that you do not have Exchange databases to consider when you back up a domain controller.Chapter 2: Backing Up Exchange Server 2003 47 6. type a backup description.com/fwlink/? LinkID=21277). see "Selecting Options for a Backup" in Chapter 1. For more information about domain controller availability and how to choose a disaster recovery strategy. If you lose all your domain controllers to a disaster and must restore a backup of Active Directory. Circular logging for Active Directory is enabled on domain controllers and cannot be turned off. set the appropriate options.dit Edb. Backing up a domain controller is like backing up an Exchange member server. you can use the same procedure as you would for a server that is not a domain controller. you will lose data that was . Backing Up Domain Controllers It is important to back up your domain controllers to ensure their availability. However. The method that you use to back up your domain controller depends on the disaster recovery strategy you choose. By default. In Backup Job Information.log Res1. you must also back up additional files. Table 2. The transaction log files. The reserved transaction log files. each file is 10 megabytes (MB). and then click Start Backup. see "Checking the Success of a Completed Backup" in Chapter 1. verify that it was successful. The checkpoint file. you must also back up the Windows boot partition and system partition when you perform either a Windows backup or a full computer backup of a domain controller. To back up the System State data of a domain controller that is running Active Directory.

see Active Directory Disaster Recovery (http://go. a large Active Directory database. Recommendations for Backing Up a Domain Controller Consider the following recommendations before you back up a domain controller: • Create a Windows backup set of at least one domain controller to preserve the Active Directory information which is vital to your Exchange servers. This section provides detailed descriptions and procedural information about the following types of backups: • • • • Backing up Exchange Server 2003 databases. For more information. For more information about authoritative restores.com/fwlink/?LinkId=6270).microsoft.com/fwlink/?LinkId=3052&kbid=216993). Backing Up the certification authority (CA).com/fwlink/? LinkId=3052&kbid=241594). If the date of your System State data backup exceeds the maximum age limit set in Active Directory.48 Exchange Server 2003 Disaster Recovery Operations Guide written to Active Directory after the backup set was made. • Perform a non-authoritative restore of Active Directory from backup. It is recommended that you back up one domain controller nightly.microsoft. see Microsoft Knowledge Base article 216993. moving users. Backing Up Exchange Server 2003 Data The Exchange 2003 data that you must back up depends on which components are installed on your Exchange 2003 server. • Create Windows backup sets frequently enough to make sure that they are valid backups. and then allow the other domain controllers on the network to update the restored domain controller. You can use the backup of a domain controller to restore the domain controller and the version of Active Directory that was on the domain controller at the time that it was backed up. make regular backups of Active Directory. you can choose whether this Active Directory information replicates to other domain controllers. the backup utility (Backup) in Windows Server 2003 performs nonauthoritative restores of Active Directory information. Therefore. Active Directory objects that are part of an authoritative restore replicate from the restored domain controller to the other domain controllers on the network. The Active Directory objects from the backup replace the Active Directory objects in the domain. instead of restoring your data from a backup. For more information about how to back up Active Directory information. . or adding new storage groups and databases. see Microsoft Knowledge Base article 241594. Backing up connector-specific information. regardless of the update sequence numbers (USNs). Additionally. This method is especially useful when you have a slow link over which to replicate data. and your Windows Server 2003 operating system prevents you from restoring Active Directory. "Backup of the Active Directory Has 60-Day Useful Life" (http://go. • Re-create the failed domain controller and populate its copy of Active Directory through replication from the unaffected domain controllers in your organization. "HOW TO: Perform an Authoritative Restore to a Domain Controller in Windows 2000" (http://go. it is highly recommended that you make a new backup of a domain controller to preserve these changes to Active Directory. the backups are not valid.microsoft. Backing Up the Microsoft Exchange Site Replication Service (MSExchangeSRS). If you make changes to your Exchange organization such as (but not limited to) adding new servers. By default. or both.

In the console tree.4 The Microsoft Information Store in Backup Backing Up Exchange Server 2003 Databases The mailbox store and public folder store data in your Exchange 2003 databases and transaction log files are the most important data to back up in your Exchange organization.) For information about . The Microsoft Exchange System Management Tools component has been successfully installed on the computer. and then expand Microsoft Information Store.Chapter 2: Backing Up Exchange Server 2003 49 Note To locate the Microsoft Information Store options that are mentioned in this section. You can also use Exchange database backups to restore your Exchange databases to a different server. Backing Up Remote Exchange Server 2003 Databases For the backup utility (Backup) in Windows Server 2003 to successfully back up the databases of an Exchange 2003 server. For more information about how to restore Exchange databases to a different server. open Windows Backup. expand the name of the server that you want. see "Restoring Exchange Databases to Another Server" in Chapter 3. expand Microsoft Exchange Server. You can use an Exchange database backup to restore damaged mailbox or public folder stores to a functioning server that is running Exchange 2003. Figure 2. (This is typically referred to as an admin only Exchange installation. you must run it on a computer that meets at least one of the following requirements: • • The Microsoft Exchange Messaging and Collaboration Services component has been successfully installed on the computer.

(In versions of Exchange earlier than Exchange 2000 Server Service Pack 2 (SP2). use the Remote Store option on the Tools menu to manually connect to an Exchange server that is on the network. "XADM: How to Use NTBackup from a Non-Exchange 2000 Computer" (http://go. To use the Remote Store option 1. If you still cannot connect to any Exchange servers or see any in the list. 4. . If you do not see this option on the Backup tab. but the checkpoint will not move again until the backup ends. an option named Microsoft Exchange Server appears on the Backup tab in Backup. Click Tools. Page changes made to the database during backup that cannot be reconstructed fully from the log files are not flushed to the disk during backup. • The computer must be manually configured to make remote backups of Exchange databases. 1.microsoft. 4. depending on the backup status of other databases in the storage group. In Backup.com/fwlink/?LinkId=3052&kbid=275676). Assuming that the account that you are logged into has the necessary permissions to back up the server. The first log that must be copied to tape with the backup is recorded in the database header in the Current Full Backup section. Type the name or IP address of an Exchange server in the organization that you want to back up. This option shows you all the Exchange servers in the forest that you are connected to. make sure that you have logged into an account that has the necessary permissions to back up the server.microsoft.pat file that is in 2. This is especially useful for a dedicated backup server that is used to back up databases in multiple Exchange organizations.) The checkpoint is frozen. see Microsoft Knowledge Base article 275876. see the information in Microsoft Knowledge Base article 275676.5. you can add servers from multiple Exchange organizations to the list of servers that you can back up. 5. Click Remote Store. Copying the database files to tape begins. New changes will still be accepted and written to the database files. Click OK. In this way.com/fwlink/?LinkId=21769). make sure that you are on the Backup tab. If the problem persists. 3. the backup was established with the Microsoft Exchange System Attendant (MSExchangeSA) service process. (In Exchange 5. these changes are stored in a . you will populate the Microsoft Exchange Server option on the Backup tab with all the servers in the Exchange organization. Note If there is a similar option named only Microsoft Exchange above the Microsoft Exchange Server option. The backup agent establishes communication and initializes a backup with the MSExchangeIS service on the target Exchange server. 2. This option is only for backing up Exchange databases on Exchange 5. 3. see "Preparing to Administer Exchange 2003" in the Exchange Server 2003 Administration Guide (http://go. Normal (or Full) Backups The following is a step-by-step description of the normal (or full) backup process. you can ignore it.50 Exchange Server 2003 Disaster Recovery Operations Guide installing the Exchange System Management Tools. For the manual configuration steps.com/fwlink/? LinkId=3052&kbid=275876).5 or earlier versions. This might not be the current checkpoint log. How Exchange Server 2003 Backup Works This section explains the online backup process step-by-step.microsoft. "XADM: Troubleshooting a Remote Online Backup of Exchange 2000" (http://go. If your computer meets at least one of these requirements.

the log is closed so that it can be appended to the tape. and then it is deleted. 5. . This means that if you never back up one particular database in a storage group. the logs from Thursday will be truncated. Only closed. there is no patch file. The range of logs needed to reliably recover the backup are copied to tape.pat file is copied to tape after the database files have finished being copied. If you then back up the Tuesday database on Friday. Note If all databases are mounted in the storage group and all databases have been selected for backup. and also which logs were required. no log files will be truncated.log in an online backup set. If you back up some databases but not others in a storage group. Copy (or Full Copy) Backups A copy backup is the same as a normal backup. It overrides the Log Required field in the database header. However. or not all the databases are being backed up. because it contains operations applicable to the databases that were just backed up. 8. but on which recovery has not yet run. The headers of all the databases in a storage group keep track of the last backup time for each database. its header will not be read and Exchange will make no calculations about which log files can be safely deleted. If any database in a storage group is dismounted. The . the Thursday backup will truncate logs only up to Tuesday.Chapter 2: Backing Up Exchange Server 2003 51 the same location as the database file. the range of logs copied to tape might start before the current checkpoint. 7. The current Enn. a single extra page is constructed and appended to the very end of the . except that the last two steps of truncating the logs and updating the Previous Full Backup section of the header are not done. you will see the mini header information displayed as the Patch Current Full Backup section. If you have two databases in a storage group. no transaction logs will ever be deleted. You will never see a log file called Enn. only the transaction logs not needed by the database least recently backed up will be truncated.edb file. This happens regardless of how full the log is. The log needs to be on tape. Exchange ensures that all logs needed for replay into the backed up databases will be present on the tape. if some databases are dismounted. This page is a mini header that contains information about the transaction log files needed to recover this database.) Note In Exchange 2000 Server SP2 and later. this range of logs will only be from the checkpoint log to the highest available numbered log. 6.log file is forced to roll over immediately after all database files have been copied to tape. If you run Eseutil /MH on a database that has been restored from an online backup. although it will often list the same log range. Log files that no database in the storage group needs to roll forward beyond the backup logs are truncated (deleted from disk). The Previous Full Backup section of the database header is updated to reflect the time and log range of the backup that just completed. There are two factors that affect which log files will be truncated after a backup: • Databases can be backed up individually. Therefore. and you back up one of them on Tuesday and the other on Thursday. Note If any database in a storage group is dismounted at the time of backup. • Not all databases in the storage group may be mounted at the time the backup occurs. These will include at least all the logs starting from the frozen checkpoint up through the log that was just forced to close. Instead. numbered log files are backed up. The reason that the log is forced to roll over is that log files cannot be backed up while they are open.

2. in the console tree.log in an online backup set.log file is forced to roll over regardless of how full the log is. Failed backups are not the only problem that will arise if you do not verify the success of your backups. type ntbackup.5. New changes will still be accepted and written into the database files. Only closed. Differential Backups A differential backup is similar to an incremental backup. Log files that no database in the storage group needs to roll forward are truncated (deleted from the disk).000 log files behind. and they did not notice it. .5 The Exchange 2003 backup process How to Back Up Exchange Server 2003 Databases The following is the procedure for backing up Exchange 2003 databases. 3. The backup agent establishes communication and initializes a backup with the MSExchangeIS service on the target Exchange server. 6. the backup was established with the MSExchangeSA service process.) The checkpoint is frozen. but the checkpoint will not move again till the backup ends. Figure 2. after the databases have all been copied to tape. Warning One of the most important daily tasks of an Exchange administrator is to examine the application event log and verify that backups have completed successfully. The reason that the log is forced to roll over is that log files cannot be backed up while they are open. 5. and click OK. Therefore. the dismount will occur at approximately 256 logs. except that the last two steps of truncating the logs and updating the Current Incremental Backup section of the header are not done. Then click the Advanced Mode link on the Welcome screen. (In Exchange 5. When you perform a normal or copy backup. if the checkpoint is more than 1. and then expand the server that contains the Exchange databases that you want to back up. All existing numbered log files are copied to tape. If any database in a storage group is dismounted at the time of backup. the log file is rolled over near the end of the backup. 4. A backup job that never completes leaves the checkpoint frozen. If a server crashes. For an incremental backup. In Exchange 2003. Microsoft Product Support Services frequently receives calls from customers who are experiencing problems because their backups have been failing for weeks. no log files will be truncated. 3. 2. expand Microsoft Exchange Server. the transaction log replay time after the crash can be extended up to several hours. the rollover happens at the very beginning. The Current Incremental Backup section of the database header is updated to reflect the time and log range of the backup that just completed. Click the Backup tab.52 Exchange Server 2003 Disaster Recovery Operations Guide Incremental Backups The following is a step-by-step description of the incremental backup process: 1. On the Backup tab. In previous versions of Exchange. 8. You will never see a log file named Enn. click Run. Exchange will automatically dismount the Exchange store. Start Backup in Advanced Mode: Click Start. 7. the log is closed so it can be appended to the tape. The current Enn. To back up Exchange 2003 databases 1. numbered log files are backed up.

see "Backing Up Remote Exchange Server 2003 Databases" earlier in this chapter. use the Remote Store option on the Tools menu to connect to a server in the organization that you want to back up. . For more information about using the Remote Store option.Chapter 2: Backing Up Exchange Server 2003 53 If you do not see the Exchange server whose databases you want to back up in the list of servers on the Backup tab.

in the Backup description text box. For more information about the options for the backup. Figure 2. see "Checking the Success of a Completed Backup" in Chapter 1. and then click Start Backup. After the backup completes. see Figure 2. expand Microsoft Information Store. expand Microsoft Information Store. Click Browse to select the location for your backup. verify that it was successful. select the check box next to Microsoft Information Store • If you want to back up specific storage groups in their entirety. in the details pane. set the appropriate options. For more information about how to verify the success of a backup.6 5. 6. such as "First Storage Group. Select the specific mailbox stores to back up 8. For more information. . To back up the Exchange databases. and then select the check boxes next to the storage groups that you want to back up. see "Selecting the Destination for a Backup" in Chapter 1. 7.6. (Select the label. select the check boxes next to the databases that you want to back up. For more information about how to select the media for your backup. • If you want to back up specific mailbox stores and public folder stores in a storage group. see "Selecting Options for a Backup" in Chapter 1.54 Exchange Server 2003 Disaster Recovery Operations Guide 4. select the storage group that contains the databases you want to back up. Click Start Backup. perform one of the following steps: • If you want to back up all the storage groups on the server. In Backup Job Information.) Then." in addition to the check box. type a backup description.

8). point to Microsoft Exchange.edb file) manually. To determine which Exchange server is running the MSExchangeSRS service 1. If an Exchange 5.com/fwlink/?LinkId=3052&kbid=822453). the server that is running the MSExchangeSRS service is the first Exchange 2000 or later server that was installed into an Exchange 5.) In Exchange System Manager. under Site Replication Services. you will see at least one entry named Microsoft Exchange Site Replication Service (computer name). expand Tools.microsoft. You can also rebuild the SRS database after a disaster by following the instructions in Microsoft Knowledge Base article 822453. Start Exchange System Manager. Figure 2. although you can create new instances of the MSExchangeSRS service to distribute the replication load. and then expand Site Replication Services to locate the server that is running the MSExchangeSRS service. (Click Start.Chapter 2: Backing Up Exchange Server 2003 55 Backing Up the Microsoft Exchange Site Replication Service (MSExchangeSRS) You will only have to back up the Microsoft Exchange Site Replication Service (MSExchangeSRS) if you have coexistence between Exchange 5.5 site. "How to Rebuild a Site Replication Service in Exchange 2003 When You Do Not Have a Backup of the SRS Database" (http://go. point to Programs. . and then select System Manager.5 site exists in your organization. 2.7 Determining which server is running the Microsoft Exchange Site Replication Service (MSExchangeSRS) Note You can also back up the MSExchangeSRS service database (Srs.edb file is located in the SRSData folder under the folder where you installed the first Exchange 2000 Server or later server (Figure 2.7). Use Exchange System Manager to determine which Exchange server is running the MSExchangeSRS service in your site. By default. where (computer name) is the name of the server that is running the MSExchangeSRS service (Figure 2.5 and Exchange 2000 or later servers. Use Backup to back up the MSExchangeSRS service on the server that is running it. The Srs.

point to Administrative Tools. (Click Start. On any computer in your Exchange organization. close the Services MMC snap-in. double-click Microsoft Exchange Site Replication Service. select Automatic. point to Programs. 4. 5. start Backup in Advanced Mode: Click Start. in the Startup Type list.56 Exchange Server 2003 Disaster Recovery Operations Guide Figure 2.8 Database. and click OK. click the Backup tab. . Then click the Advanced Mode link on the Welcome screen. type ntbackup. 6. 1. The Microsoft Exchange Site Replication Service (MSExchangeSRS) To back up the MSExchangeSRS service database On the server that is running the MSExchangeSRS service. In Backup. After the service starts. start the Services MMC snap-in. expand Microsoft Exchange Server. in the console tree. 2. In Microsoft Exchange Site Replication Service Properties.9).) In Services. and then select Services. On the Backup tab. and then select the check box next to Microsoft Site Replication Service (Figure 2. 3. click Start to start the MSExchangeSRS service. expand the server that is running the MSExchangeSRS service. click Run. If Service status is currently Stopped.

Click Browse to select the media for your backup. see "Creating Full Computer Backup Sets" and "Creating Windows Backup Sets" earlier in this chapter.Chapter 2: Backing Up Exchange Server 2003 57 Figure 2. you must first back up the computer that is the certification authority (CA). you can also back up the CA by creating a Windows backup set on the server that is running Certificate Services. it is better to run Certificate Services on a separate server to make sure that you meet your standards for reliability and performance. Backing Up the Certification Authority (CA) If you have to recover a server that is running Certificate Services. 10. In Backup Job Information. It is recommended that you back up the CA by creating a full computer backup set of your server that is running Certificate Services. set the appropriate options.9 Backing up the Microsoft Exchange Site Replication Service (MSExchangeSRS) 7. 9. Click Start Backup. see "Checking the Success of a Completed Backup" in Chapter 1. and then click Start Backup. (The System State data part of a Windows backup set includes the Certificate Services database. 8. in the Backup description text box. Although you can configure a computer to be both the CA and a server that is running Exchange 2003. type a description of the backup. For more information about how to set the options for the backup. After the backup completes. If you cannot create a full computer backup set of your server. verify that it was successful. For more information about how to verify the success of a backup. see "Selecting Options for a Backup" in Chapter 1. .) For more information about how to perform full computer and System State backups.

com/fwlink/?LinkId=25762). see Microsoft Knowledge Base article 328835. For more information about using CA and Windows Server 2003 public key infrastructure (PKI) with Exchange 2003.0 online product documentation (http://go. and also in Active Directory. Standard Edition online Help (http://go. To use the Backup or Restore Wizard in the Certification Authority MMC snap-in. Backing Up Exchange Server 2003 Clusters The disaster recovery processes for backing up and restoring Exchange 2003 server clusters are similar to the processes for backing up and restoring data on stand-alone Exchange 2003 servers. You back up the IIS metabase file when you create a Windows backup set.58 Exchange Server 2003 Disaster Recovery Operations Guide You can also use the Certification Authority Backup Wizard to back up keys.com/fwlink/?LinkId=28748). For more information about how to back up and restore connectors. You must have this password to restore data from the backup.microsoft.microsoft. You access this wizard from the Certification Authority MMC snap-in. For more information. you must manually back up and restore additional files. you must be a Backup Operator or a Certification Authority Administrator. • Windows Server 2003 PKI Operations Guide (http://go. such as the contents of the CONNDATA directory and subdirectories. private keys.microsoft. see the following resources: • "Backing up and restoring a certification authority" in the Windows Server 2003.microsoft. make sure to back up the Internet Information Services (IIS) metabase also. . • "Backing Up and Restoring the Metabase" in the IIS 6. for specific e-mail connectors. However. see "Implementing an Exchange 2003-Based Message Security System in a Test Environment" in the Exchange Server 2003 Message Security Guide (http://go. you must first determine which server recovery method you want to use for each node in the server cluster: • • Restore the node. This information is relevant to Exchange Server 2003. To successfully back up Exchange server clusters. (The System State data part of a Windows backup set includes the IIS metabase. such as Novell GroupWise or Lotus cc:Mail. If your disaster recovery strategy includes restoring either a Windows backup set or a full computer backup set.com/fwlink/?LinkId=3052&kbid=328835). contain connector-specific configuration data. Connector-specific configuration data is stored in the registry of the computer where the connector is installed.com/fwlink/? LinkId=23216). "XADM: How to Back Up and Restore Connectors on Exchange 2000" (http://go. certificates.microsoft. and the certificates database.) You can also use the IIS snap-in to back up the IIS metabase independently. or you must have local administrator permissions on the CA. The Backup or Restore Wizard requires you to supply a password when you back up public keys. Rebuild the node without using a standby recovery server. Backing Up Connector-Specific Information Exchange servers that include connectors to other messaging systems. the connectorspecific data is automatically restored to your server when you run the Exchange Setup program in disaster recovery mode.com/fwlink/?LinkID=17807). and CA certificates. If you use the Certification Authority MMC snap-in to back up the CA.

if a different type of disaster occurs (for example. However. you do not have to restore any backups. updating it whenever you update your production servers. see "Restoring Exchange Clusters" in Chapter 3. see the Technical Overview of Windows Server 2003 Clustering Services (http://go. If you are using the Majority Node Set. Table 2.) Insert a new node into the cluster • • • • • • • Full computer backup set. The ability to run the Exchange Setup program and reinstall all Exchange updates. For information about how to back up the quorum disk resource. see "Backing Up the Quorum Disk Resource" later in this chapter. each node maintains a copy of the cluster configuration data. For information about how to back up shared disk resources that contain your Exchange database files and log files. You keep the standby hardware available to replace any nodes in your server clusters in the event of a disaster. The shared disk resource that maintains the consistency of your server cluster is the quorum disk resource. a complete cluster failure. As long as the maximum number of nodes for the server cluster has not been exceeded.2 Disaster recovery methods for server clusters Recovery method Restore the node What you need • • • • • • Rebuild the node by using a standby recovery server (Prepare the node in advance. Exchange database backups for each EVS. and you do not have to back up the quorum. For detailed information about Exchange server cluster restore processes. Exchange database backups for each EVS. Exchange database backups for each EVS. . The ability to run the Exchange Setup program and reinstall all Exchange updates. you will do most of the work involved in recovering or inserting a new node before a disaster happens. unless you are using the Majority Node Set. For example. A Windows backup set. see "Backing Up the Exchange Server 2003 Databases That Are Stored on Shared Disk Resources" later in this chapter. Any dynamic data backups for each node.com/fwlink/?LinkId=16303). For an overview of Windows Server 2003 clustering support and troubleshooting. In this case. a damaged quorum disk resource. Any dynamic data backups for each node. it is relatively easy to replace that server by introducing a new node to the server cluster (either a newly rebuilt server cluster node or a standby cluster node).Chapter 2: Backing Up Exchange Server 2003 59 • Rebuild the node by using a standby recovery server. After you make sure that your backup strategy includes creating backups for each node in the server cluster. you can add new nodes to a cluster at any time. you must also make sure that your backup strategy includes backing up the data on your server cluster's shared disk resources. You do not have to restore the backups described in this section to solve every problem that might occur in your clustering environment. A Windows backup set. Any dynamic data backups for each node. Rebuild the node without using a standby recovery server If you choose to rebuild the node by using a standby recovery server.microsoft. The ability to install Windows Server 2003 and Exchange. or damaged Exchange databases) you might have to use one or more of your backups. if a single node in a server cluster fails because of a hardware problem. Exchange database backups of each Exchange Virtual Server (EVS) in the cluster.

open Windows Backup. If a cluster's shared disk fails.microsoft. any new node that joins that cluster will not be able to access the data that is stored on the failed shared disk. Important When you create backup sets of your cluster node that contains a server cluster's shared disk. . If you plan to use the "restore the server" method to recover your shared disk resources. This section provides detailed descriptions and procedural information about the following Exchange clustering topics: • • • Backing up an Exchange Server 2003 cluster's shared disk resources. The cluster database contains information about all physical and logical elements in a server cluster. Note Create a separate cluster group for your quorum disk resource.com/fwlink/?LinkID=21277). To back up your quorum disk resource. Note To locate the Microsoft Information Store options that are referred to in this section. Backing Up the Quorum Disk Resource If you are not using Majority Node Sets. Backing Up an Exchange Server 2003 Cluster's Shared Disk Resources The shared disks in an Exchange 2003 server cluster are a critical part of the cluster technology. For more recommendations about Exchange cluster groups.log). Each node in the cluster has access to the most recent database changes. In the console tree. back up specific information that is stored on each server in the server cluster. For more information about the "restore the server" method. including cluster resource object properties and configuration data. An Exchange server cluster's shared disk resources can include the quorum disk resource and the resource that contains the Exchange databases and transaction log files. The cluster registry for each node is located in the %systemroot%\Cluster\CLUSDB directory of each node.microsoft. back up any dynamic data that exists on that disk. Any node in a server cluster can access the shared disks while the cluster service is running. perform either a full computer backup or a Windows backup of the node that currently owns the quorum disk resource.60 Exchange Server 2003 Disaster Recovery Operations Guide To secure your Exchange server clusters. to make sure that the cluster registries on all nodes of the server cluster are consistent with each other. Backing up the Exchange Server 2003 databases that are stored on shared disk resources. and then expand Microsoft Information Store. see "Exchange Server Clusters" in the Exchange Server 2003 High Availability Guide (http://go. Make sure that you include the System State data together with the boot and Windows partitions of the node. Maintaining records about your server clusters. create a separate backup set by using the Microsoft Information Store option in Backup. and keep it on its own physical hard disk. the quorum disk resource maintains the consistency of your server cluster by recording the changes that have been made to the cluster database. expand Microsoft Exchange Server. expand the server that you want. and all the nodes rely on those disks to be intact. The quorum disk resource uses the quorum log file (Quolog. Quorum disk resource files are located in the /MSCS folder of the drive that contains the quorum disk resource. see "Restoring the Server" in the Exchange Server 2003 Disaster Recovery Planning Guide (http://go.com/fwlink/?LinkID=21277). To back up the Exchange databases and log files on your server cluster's shared disks. the following files are also backed up. do not include the drives for those resources in your full computer backup set. When you back up the quorum disk resource.

If you must rebuild a whole server cluster.com/fwlink/? LinkId=3052&kbid=286422). Backing Up the Exchange Server 2003 Databases That Are Stored on Shared Disk Resources Exchange 2003 database files and transaction log files are stored on one or more of a server cluster's shared disk resources. For more information about how to back up the quorum disk resource. see "Backing Up Remote Exchange Server 2003 Databases" earlier in this chapter. click Run.dat Definition The shadow copy files of the cluster registry. 2. and click OK.tmp Quolog. Under Microsoft Exchange Server is a list of the Exchange stand-alone servers and Exchange clustered virtual servers in the domain. Click the Backup tab. . see "Backing up Exchange Server 2003 Databases" earlier in this chapter. The quorum log file. The registry checkpoint files for the resource identified by the GUID. you can create either a full computer backup set or a Windows backup set for that node.log <GUID of resource>\*. Start Backup in Advanced mode on any computer that is configured to back up Exchange databases (clustered or not clustered). For a description. expand Microsoft Exchange Server. 0-byte file). It is recommended that you label the backup that contains the quorum disk resource.cpr Clusbackup.cpt <GUID of resource>\*. you ensure that the cluster resource objects in the cluster are restored before you reintroduce any other nodes to the cluster. quorum disk resource data is also backed up. to back up the quorum disk resource data. Therefore.Chapter 2: Backing Up Exchange Server 2003 61 Table 2. Both of these backup sets includes a backup of System State data. hidden. you can create and restore backups for all the nodes. Each instance supports multiple storage groups. "How to Back Up and Restore a Windows Server 2003 Cluster" (http://go. Each Exchange Virtual Server (EVS) in the cluster that uses these resources has its own set of databases and log files. Then click the Advanced Mode link on the Welcome screen. The crypto checkpoint files for the resource identified by the GUID. and then in the console tree. type ntbackup. in Advanced Mode: Click Start. For a full cluster recovery. you can insert new nodes into the cluster. To start Backup. After that node is running. see the Windows Server 2003 online Help and Microsoft Knowledge Base article 286422. When you make sure to first restore the node that owned the quorum disk resource. you must restore the node that owned the quorum disk resources before you restore or join any other node. Back up Exchange databases in your Exchange server clusters by using a method that is similar to that for backing up a stand-alone Exchange server. One instance of the MSExchangeIS service runs per node. To back up the Exchange 2003 databases that are stored on shared disk resources 1. The file that indicates that a backup is completed (a read-only. Whenever the System State data is backed up on the node in the server cluster that currently owns the quorum disk. If the server that you want to back up does not appear in this list. If you lose the whole cluster.3 Quorum disk resource files to back up File type chknnnn. You only have to back up the node in the server cluster that currently owns the quorum disk resource. you can recover the first node and the quorum disk resource that it controls.microsoft.

4. • If you want to back up specific mailbox stores and public folder stores in a storage group. After the backup completes. expand Microsoft Information Store. and then click the check boxes next to the storage groups that you want to back up. The Microsoft Exchange option is only for backing up Exchange 5. Expand the cluster's EVS that contains the Exchange databases that you want to back up. select the check boxes that are next to the databases that you want to back up. you can ignore it. Click Start Backup. Selecting the storage groups under Microsoft Information Store 8.10 5. Figure 2. For more information about how to verify the success of a backup. Select the Exchange databases that you want to back up by following one of these procedures: • If you want to back up all storage groups on the EVS. In Backup Job Information. For more information about how to select the media for your backup. set the options and the advanced options. • If you want to back up specific storage groups in their entirety. 7. Click Browse to select the location of your backup. verify that the backup was successful. Then. . click the check box next to Microsoft Information Store (Figure 2. see "Checking the Success of a Completed Backup" in Chapter 1. and then click Start Backup. in the details pane.62 Exchange Server 2003 Disaster Recovery Operations Guide Note If you see a similar option named "Microsoft Exchange" above the Microsoft Exchange Server option. 6.10).5 or earlier databases. in the Backup description text box. 3. type a backup description. For more information about how to set the options for the backup. see "Selecting the Destination for a Backup" in Chapter 1. and click the storage group that contains the Exchange databases that you want to back up. see "Selecting Options for a Backup" in Chapter 1. expand Microsoft Information Store.

Names of cluster resources. you might have to completely rebuild the cluster. type: Nbtstat –s On the Administrative Tools menu. Network names of each Exchange Virtual Server (EVS). click Cluster Administrator. On the Administrative Tools menu. On the Administrative Tools menu. At a command prompt. . Important If you do not keep a record of this information. maintain records of the following information about the cluster.Chapter 2: Backing Up Exchange Server 2003 63 Maintaining Records About Your Server Clusters Make sure to maintain records of the configuration information about your Exchange 2003 clusters. Names of virtual server storage groups. You might need this information to recover your Exchange organization from a major disaster. If you do not have full computer backup sets or Windows backup sets for each node. click Cluster Administrator.4 Cluster information to record Information to record Disk Signatures of a cluster's shared disks. For example. To view the properties of a virtual server. you might not be able to recover your Exchange server clusters. IP addresses of virtual servers. Use Exchange System Manager. type: cluster /cluster: clusterName resource sharedDisk /priv NetBIOS (network basic input/output system) names of each node. Use Exchange System Manager. On the Administrative Tools menu. How to obtain it At a command prompt. a record of configuration information for the cluster might help you to recover the cluster. click Cluster Administrator. Names of cluster groups. if all the servers in a cluster are damaged. Names of virtual server Exchange stores. click Cluster Administrator. Table 2. To help you recover an Exchange 2003 cluster. including its IP address. select its name.

• Repairing Exchange Server 2003. • Restoring full computer backup sets. • Restoring Exchange mailbox or public folder stores. • Restoring Exchange clusters. For example. The procedures in this chapter apply to Backup. which provide descriptions and procedural information for various recovery processes: • Repairing Windows Server 2003.com/fwlink/?LinkId=28311). Note For some problems that occur. use this chapter for general restoration practices. After you choose the restoration strategy that best suits your needs. • Restoring domain controllers.microsoft. you do not have to restore any backups. The types of backups that you have available.com/fwlink/? LinkId=21277) will help you determine your disaster recovery strategy.C H A P T E R Restoring Exchange Server 2003 3 The Exchange Server 2003 Disaster Recovery Planning Guide (http://go. • Restoring connector-specific data. • Restoring the Microsoft Exchange Site Replication Service (MSExchangeSRS). • Restoring Windows backup sets. • Restoring individual mailboxes. Chapter 3 contains the following sections. For more information about these methods. These methods include using Automated System Recovery (ASR). but see your backup software's documentation for specific procedures. see "Disaster Recovery" in the Windows Server 2003 online Help (http://go. Several additional restore methods might suit your needs. The recovery procedures you perform depend on the following three factors: • • • The type of disaster or failure that occurs. If you have chosen to use third party software to restore your Exchange data. . restoring from a shadow copy. • Exchange member server recovery. The time that you can spend performing the recovery.microsoft. and restoring from a drive image. you can use the information in this chapter to perform the appropriate tasks by using the backup utility (Backup) in Microsoft® Windows Server™ 2003. you can resolve some problems by repairing your Windows Server 2003 operating system or Microsoft Exchange Server 2003 installations.

consider the following possibilities before you use more complex troubleshooting techniques: • Recent changes to your Windows Server 2003 operating system installation.Chapter 3: Restoring Exchange Server 2003 65 Repairing Windows Server 2003 There are many troubleshooting techniques that you can use to resolve problems that arise in a Windows Server 2003 operating system installation. However.microsoft. Note If the Chkdsk utility cannot lock the drive. such as the installation of new software. it will offer to check the drive the next time the computer restarts. Navigate to a drive other than the drive that you want to check. PSS might have written a Microsoft Knowledge Base article describing how to resolve the issue. see the Windows Server 2003 documentation that is listed in Appendix A. Open a command prompt. Chkdsk also lists and corrects errors on the disk. For more information about repairing Windows Server 2003. The Chkdsk utility creates and displays a status report for a disk based on the file system used. you can use the Chkdsk disk repair utility included in the operating system to check the file system on each logical partition and check the disk surface for unreadable or corrupted sectors. if you run Chkdsk on a hard disk. Type chkdsk /f <drive letter> and press ENTER. Tip Some third-party diagnostic and repair software packages have advanced features for verifying the integrity of your hard disk. You can run Chkdsk from your Windows Server 2003 operating system." Running the Windows Chkdsk Utility If your Windows Server 2003 operating system experiences a problem. • Other users might have experienced a similar problem and contacted Microsoft Product Support Services (PSS) for help. you can run Chkdsk from the Windows Recovery Console in Windows Server 2003 Setup. use this section to familiarize yourself with the following basic troubleshooting techniques: • • • • • • Running the Windows Chkdsk utility Running Windows System File Checker Using the Safe Mode boot options Using the Last Known Good Configuration boot option Using the Windows Recovery Console Reinstalling Windows Server 2003 Note This section does not provide every possible troubleshooting technique for your Windows Server 2003 operating system.com/fwlink/? LinkId=18175) for an article that describes the problem. Navigate to the directory you want to check. To run chkdsk and have it repair errors 1. Also. or configuration changes. the file system. In turn. 3. If you cannot start your operating system because of the problem. you must be a member of the Administrators group. and the data contained therein. might cause or contribute to the problem. 4. new drivers. Search the Microsoft Knowledge Base (http://go. If you cannot resolve the problem using these suggestions. . 2. if a problem arises. "Resources.

com/fwlink/?LinkId=3052&kbid=325375). but you can still start Windows Server 2003. you can: .microsoft. the registry configuration reverts to the condition it was in before you made the changes that prevented the operating system from starting normally. Using the Safe Mode Boot Options If your Windows Server 2003 operating system experiences a problem. try using the following Safe Mode advanced startup options: • Safe Mode • Safe Mode with Networking • Safe Mode with Command Prompt The Safe Mode boot options are troubleshooting modes that load your Windows Server 2003 operating system with a minimal set of device drivers and services.exe)" (http://go. the Last Known Good Configuration option cannot roll back those changes.microsoft. see Microsoft Knowledge Base article 325375. you can use the System File Checker tool (Sfc. see Microsoft Knowledge Base article 310747. In Recovery Console.exe) to make sure that all the operating system files are the correct version and are still intact. For more information about the Safe Mode boot options and other advanced startup options.com/fwlink/?LinkId=3052&kbid=325375). Additionally.com/fwlink/?LinkId=3052&kbid=310747). "HOW TO: Troubleshoot Startup Problems in Windows Server 2003" (http://go. After you start Windows Server 2003 in Safe Mode. you can use troubleshooting techniques such as running System File Checker or restoring backups to resolve the problem. For more information about the System File Checker tool. System File Checker is a command-line tool that scans and verifies the versions of all protected system files. you can obtain limited access to NTFS file system volumes without starting the Windows graphical user interface (GUI). For more information about the Last Known Good Configuration options and other advanced startup options. at a command prompt.microsoft. it retrieves the correct version of the file from the %systemroot%\system32\dllcache folder. see Microsoft Knowledge Base article 325375. To run Windows System File Checker. you will lose all configuration changes that were made since you last successfully logged on to your system. "Description of Windows XP and Windows Server 2003 System File Checker (Sfc. you can use the Last Known Good Configuration advanced startup options. if you use this option. If System File Checker discovers that a protected file was overwritten. "HOW TO: Troubleshoot Startup Problems in Windows Server 2003" (http://go. If you use this boot option.66 Exchange Server 2003 Disaster Recovery Operations Guide Running Windows System File Checker If your Windows Server 2003 operating system experiences a problem. and then replaces the incorrect file. Using the Last Known Good Configuration Boot Option If you experience difficulty starting your Windows Server 2003 operating system after you install a new driver or change a driver configuration. When you successfully log on after you make changes that affect the registry. Using the Windows Recovery Console With the Windows Recovery Console. and you cannot start it normally. type sfc /scannow.

and then merging any additional data from your test server to your production server. rename. you can try to recover additional data from the failed database. but make sure to perform basic troubleshooting methods such as checking the event log files to determine the root cause of the problem that you are experiencing. some of the transaction log files were truncated (deleted) and you no longer have those transaction log files available. Repairing Exchange Server 2003 In most situations where you might consider repairing a database.microsoft. you can try to reinstall Exchange before you resort to restoring your database. You can start the Recovery Console from the Windows Server 2003 CD or at startup. from the Windows Server 2003 boot menu.Chapter 3: Restoring Exchange Server 2003 67 • Use. • Enable or disable services or devices from starting when you next start your computer. In these instances. Important After you perform an in-place upgrade. and then start to restore the most recent backup to your production server. Unfortunately. it is recommended instead that you restore the database from the backup. if the Recovery Console was previously installed to your computer. "HOW TO: Troubleshoot Startup Problems in Windows Server 2003" (http://go. or when your only backup is unusable. Sometimes you cannot make the database completely up-to-date. Note Restarting your server might fix your immediate problem. the tape that you used for the backup was bad. • Create and format partitions on drives. changes that were made to your system after the original Windows Server 2003 installation (such as service pack upgrades and system customizations) might be lost. There are situations where repairing your database might be your only option. and replay the transaction log files to make the database up-to-date. and you have to revert to an earlier backup. you are still missing data. You might experience problems with an Exchange server that might not necessarily require you to perform a database restore or a complete recovery of the server. • Repair the file system boot sector or the master boot record (MBR). Between the time that the two backups were made. . You copy the corrupted database to a test server. or replace operating system files and folders. The time that it takes to perform this in-place upgrade is equal to the time that it took to perform your original Windows Server 2003 installation. For this reason. see "Moving or Copying the Existing Versions of the Database Files That You Are Restoring (Optional)" later in this chapter. you can use the Windows Server 2003 Setup CD to perform an in-place upgrade over the existing installation. see Microsoft Knowledge Base article 325375. For more information about how to use Windows Recovery Console. make sure to do this with a copy of the damaged database in case your attempts to repair the database fail. copy. When you try to repair a backup. keep a copy of the failed database when you restore your backup to production hardware. Examples of these cases include times when you do not have a backup of your Exchange database. You still might be able to recover some of that missing data by trying to repair the database on your test server. When you have restored all the available database and log files. You cannot undo repair operations.com/fwlink/? LinkId=3052&kbid=325375). Try restarting your Exchange server first. Reinstall the most recent service pack and all previous hotfixes and software updates after you reinstall Windows Server 2003. For example: One of the databases in your Exchange organization experiences some type of corruption. For more information about keeping a copy of the failed database. Reinstalling Windows Server 2003 If the computer still does not operate normally. If that does not solve the problem.

68 Exchange Server 2003 Disaster Recovery Operations Guide .

The node where Exchange is to be installed cannot be running any Exchange services. Components that are not installed are not available. click Next. under Action. .exe) from <drive>:\setup\I386. Reinstalling Exchange and any service packs stops Exchange services from running on the Exchange server during the install processes. If the reinstall option does not appear. Note If you try to reinstall Exchange on a server that is running Exchange in a cluster. you must first move all Exchange Virtual Servers (EVSs) to another server node in the cluster." and then click Next (Figure 3. Reinstalling Exchange Over a Damaged Installation Reinstalling Exchange and any relevant service packs and hotfixes helps ensure that all Exchange files are intact and are the correct version. Repairing full-text indexing. To reinstall Exchange 2003 1. On the Welcome page. select the Reinstall option for the parent component "Microsoft Exchange.1). Insert the Exchange Installation CD. and then run the Setup program (Setup. users cannot access the Exchange server until after the installations are complete. For more information. you can try to run the Setup program in disaster recovery mode with the /disasterrecovery switch. 3. 2.Chapter 3: Restoring Exchange Server 2003 69 This section contains the following topics about Exchange repair processes: • • • Reinstalling Exchange over a damaged installation. Repairing Exchange databases. On the Component Selection page. see "Run Exchange Setup in Disaster Recovery Mode" later in this chapter. Therefore.

2).2 5. Reinstalling Exchange On the Installation Summary page. including recopying all files.1 4. Figure 3. click Next to start the reinstall process (Figure 3. The Installation Summary page Exchange stops all Exchange services and performs all the required steps to reinstall Exchange over the damaged installation.70 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. .

4). it is recommended that you do not overwrite these files. . prompting you to specify whether you want to overwrite certain files on your server that are newer than the files being copied from the Exchange Setup CD (Figure 3. Note For Exchange 2000 servers.Chapter 3: Restoring Exchange Server 2003 71 Figure 3. The Component Progress page As the Setup program tries to copy installation files to your computer. the Confirm File Replace dialog box might appear.3 6. Required updates are all updates that were applied to the server before the failure occurred. Because you are trying to repair files that are either damaged or the wrong version. apply all required updates immediately after you run the Setup program in disaster recovery mode. Instead. you must click Yes to overwrite these files.

see Using Exchange Server 2003 Recovery Storage Groups (http://go. Repairing Exchange Databases Try to repair an Exchange database only as a last resort. see "Install Exchange Service Packs in Disaster Recovery Mode" later in this chapter. 9.edb files) by using Eseutil. and then click Properties. For more information. You can repair Exchange database files (. because such an attempt can lead to loss of data.. the Setup program notifies you if there are errors and whether your installation of Exchange is successful.exe. If you ran setup with the /disasterrecovery switch. Click Finish to exit Setup.\exchsrvr\bin directory to your Windows Server 2003 system path 1. right-click My Computer.. For information about using recovery storage groups. You can also use recovery storage groups to salvage data from damaged databases.\exchsrvr\bin to your Windows Server 2003 system path. To run these tools globally on your server (from any command prompt).com/fwlink/? LinkId=23233). To add the .72 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3.. The Confirm File Replace dialog box After the wizard completes. 8. Running Exchange Tools Globally on a Server By default. some tools such as Eseutil and Isinteg are installed to the .microsoft. add the full path of . make sure to use the /disasterrecovery switch when you install service packs. . click Start.\exchsrvr\bin directory during Exchange setup. Open System Properties. To open System Properties.4 7.exe and Isinteg. Install any Exchange service packs and hotfixes that were installed to the server before the repair process.

Click the Advanced tab. 11. and then click OK to close System Properties... In the Variable Value box. 3. and also any other tools you keep in the . click OK to close Environment Variables. 4.\exchsrvr\bin. 10. . 8.Chapter 3: Restoring Exchange Server 2003 73 2. 6. After the semicolon (with no spaces) type the full path of . Open a new command shell. Add a semicolon at the end of the path variable. Editing the Path environment variable Click Path to select it. Click the Environment Variables button. and then click Edit. click Run. Editing the Path variable Click OK to close Edit System Variable. 7.\exchsrvr\bin directory. You should now be able to run Eseutil and Isinteg from any command prompt on your server.6 9.5 5. Figure 3.5).6). Click Start.) to the end of the string. and then click OK. In the System Variables box. The default path is C:\program files\exchsrvr\bin (Figure 3. scroll down to the variable "Path" (Figure 3. 12. Figure 3. Close any command shells that are open. add a semicolon (. type cmd.

If both utilities run successfully (for example. Typically. If it is possible.microsoft. b.com/fwlink/?LinkId=3052&kbid=182081). see Microsoft Knowledge Base articles 812357. While you can redirect the temp files to another drive as you can with the /P switch.) Because you cannot undo changes that were made to a database during the repair process. If you are running Eseutil /P you must have approximately 20 percent of the size of the database you are repairing on the same drive. After Eseutil /D is completed successfully. the database is generally considered to be repaired and ready to replace the damaged database. For this reason. (For information about how to copy your database files. copy the database files you are repairing before attempting the repair process.74 Exchange Server 2003 Disaster Recovery Operations Guide Using Eseutil and Isinteg to Repair an Exchange Database This section contains general information that you should know about if you use Eseutil or Isinteg to repair Exchange databases. only use Eseutil and Isinteg as a last resort. it will dramatically increase the time it takes to repair your database. After Eseutil /P completes successfully. If you do not have that much room.com/fwlink/?LinkId=3052&kbid=812357) and 182081. • • • . run Eseutil /D. you can use command-line switches to redirect the temp files to a different location. If you plan to put the repaired database back in production you must: a. if there are not any errors at the end of the last Isinteg run). If you are using Eseutil /D. For more information about using Eseutil or Isinteg.microsoft. see "Moving or Copying the Existing Versions of the Database Files That You Are Restoring (Optional)" later in this chapter. Consider the following information when repairing Exchange databases: • Repairing Exchange databases with Eseutil and Isinteg can cause lost data in the Exchange databases you repair. have ample free space when using the /D switch. Using the Eseutil and Isinteg utilities to repair a database file takes a substantial amount of time. run Isinteg –fix –test alltests. it takes much longer to repair a database than it does to restore a database from backup. If you use Eseutil to repair an Exchange database. As discussed earlier. Run Eseutil /P. you must have 110 percent of the size of the database. you must have sufficient free disk space for Eseutil to run. "Description of the Isinteg utility" (http://go. it is recommended that you recover a damaged database by restoring a backup set instead of repairing a database. c. "XADM: Maintain Your Exchange Database After You Repair By Using the Eseutil /p Tool" (http://go.

Skipping step b will save time in your recovery process but might cause the database to have indexing and space allocation errors. You can also use a recovery storage group on the same server to restore data from a damaged database.com/fwlink/?LinkId=23233). To restore Microsoft Search as part of your full-text indexing repair when Microsoft Search is damaged. see the procedure in "Restoring Microsoft Search" later in this chapter. Full-text indexing allows your users to perform full-text searches across documents and attachments in messages. it should report zero errors in the database. After Isinteg is completed. • If Eseutil and Isinteg cannot fix every error in the database. . For more information about recovery storage groups. and do not plan to put it back in production. Repairing Full-Text Indexing Exchange includes an optional feature that is referred to as full-text indexing (also known as content indexing). you can restore a damaged database to another server. do not leave the database in production. Full-text indexes are not stored with your Exchange databases. you can skip step b earlier in this section. it is best not to discard a repaired database. Figure 3. run Isinteg again until the count becomes zero or the count does not decrement on successive runs.7) and are managed by the Microsoft Search service. full-text indexes are located in the Program Files\Exchsrvr\ExchangeServer_<Server Name>\Projects folder (Figure 3. and then insert the data into a new database file. • You can restore data from a damaged database by using another server. These errors are not what you want in a production environment.microsoft. see Using Exchange Server 2003 Recovery Storage Groups (http://go. but are unlikely to affect your ability to salvage data from the database. For example. you must reindex the data on your Exchange databases.Chapter 3: Restoring Exchange Server 2003 75 If you only plan to salvage data from the disk. extract data from it using the Exmerge utility. By default.7 The default location for full-text indexes is the projects folder To repair full-text indexes that are corrupted or not synchronized with your Exchange databases. If the error count is greater than zero. If you cannot get the error count to zero. By default. Eseutil and Isinteg are both installed into the <drive>\Program Files\Exchsrvr\bin directory when Exchange is installed. Salvage data from it by merging or replicating folders to a new database or by moving mailboxes to a new database.

Before editing the registry. Open Exchange System Manager.9). locate the following key: HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Search\1. click ExchangeServer_<ServerName>. To remove full-text indexing information 1. 7. Close Exchange System Manager. 5. and then click OK. Navigating to a storage group Right-click the mailbox or public folder store that contains the full-text index that you want to remove and select Delete Full-Text Index. click Run.76 Exchange Server 2003 Disaster Recovery Operations Guide Re-Indexing the Data on Your Exchange Databases Re-indexing the data on your Exchange databases requires that you remove full-text indexing information and re-create full-text indexes.8 3. navigate to the storage group which contains the full-text index that you want to remove (Figure 3. Problems resulting from editing the registry incorrectly may not be able to be resolved. . where <ServerName> is the server from which you want to delete full-text indexes (Figure 3.8). Warning Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. 4. Open Registry Editor. 6. 2. follow these steps.0\Databases Under Databases. Click Start. back up any valuable data. Figure 3. point to All Programs. In Exchange System Manager. In Registry Editor. To delete the damaged indexes and re-create them. and then click System Manager. Click Start. point to Microsoft Exchange. type Regedit.

right-click each store again.9 8. 9. . and then click Create Full-Text Index. Open Exchange System Manager. 2. To re-create full-text indexes 1. it is <drive>:\Program Files\Exchsrvr\ExchangeServer_<ServerName>\ where <drive> is the drive where Exchange was installed and <ServerName> is the name of the server running Exchange. and then click System Manager. Do not delete the Projects and GatherLogs folders. navigate to the storage group where you want to create the full-text index (Figure 3. point to All Programs. 4. Right-click the mailbox or public folder store that you want to index. 10. Close Windows Explorer or the command prompt. find the folder that you recorded in the previous step. In Windows Explorer. 3. and then click Start Full Population. 11. or at a command prompt.8). View the contents of the Projects and GatherLogs folders to make sure that the folders are empty. Viewing the registry Record the value data for the key value LogPath.Chapter 3: Restoring Exchange Server 2003 77 Figure 3. Under the ExchangeServer_<ServerName> folder. By default. delete the contents of the Projects and GatherLogs subfolders. Caution Because you are going to delete files from this folder. consider copying the contents of this folder to a safe location to save the folder information in the event an error occurs while deleting the files. For each mailbox store or public folder store where you performed Step 3 of this procedure. Click Start. In Exchange System Manager. point to Microsoft Exchange.

If full-text indexing is not functioning correctly. see "Re-Indexing the Data on Your Exchange Databases" earlier in this chapter. Figure 3. make sure that full-text indexing is functioning correctly before performing this procedure.10). . if you are repairing an existing Exchange installation. and then re-create your full-text indexes. right-click the mailbox store or public folder store. click the Full-Text Indexing tab. you must restore it. Restoring Microsoft Search The Microsoft Search service (MSSearch) is a Windows Server 2003 service that is installed on your Exchange server that is required for full-text indexing. Before editing the registry. You cannot create full-text indexes for your Exchange databases if the Microsoft Search component is damaged or if its registry keys are incorrect. Enabling the indexes for searching Set the update interval by selecting one of the default options from the drop-down list or click Customize. you might be able to repair your full-text indexes by removing. and then select the This index is currently available for searching by clients check box (Figure 3. click Properties. or if you have restored your server from either a Windows backup set or full computer backup set). If you are in a recovery situation where Exchange is already installed on your server (for example. and then re-creating the full-text indexes. perform the following procedure.10 6. If problems occur with Microsoft Search. Warning Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. back up any valuable data. For each index that you want to make available for full-text index searching. Problems resulting from editing the registry incorrectly may not be able to be resolved. If you cannot remove. to customize the schedule. For more information about how to remove full-text indexes.78 Exchange Server 2003 Disaster Recovery Operations Guide 5.

On the File menu.0\ CatalogNames\ExchangeServer_<ServerName> HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1. click Delete. c. locate the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search Important As a cautionary measure. click Search. To back up the Search registry key branch: a.11).Chapter 3: Restoring Exchange Server 2003 79 To restore Microsoft Search 1.0\ Applications\ExchangeServer_<ServerName> HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1. under Export range. in the console tree. 3. click Export. right-click the key. and make sure that HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search appears in the corresponding text box.0\ Gather\ExchangeServer_<ServerName> HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\ Databases\ExchangeServer_<ServerName> HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1. and then click Yes (as shown in Figure 3.0\ Gathering Manager\Applications\ExchangeServer_<ServerName> HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1. e. In Registry Editor. click Selected branch.0\ Indexer\ExchangeServer_<ServerName> . type Regedit. b. 2. d. and then click Save. Name the file. Click Start. In Registry Editor. back up the registry keys in case any errors occur while deleting the registry keys. • • • • • • • HKEY_LOCAL_MACHINE\Software\Microsoft\Search\Install HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1. In the console tree. In Export Registry File. Select a location to save the file. click Run. and then click OK. delete the following registry keys (where <ServerName> is the name of the server running Exchange): To delete a key.

80 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3.exe /disasterrecovery where <drive> is the location of your Exchange CD. Deleting the Microsoft Search registry keys Close Registry Editor. set Microsoft Exchange to None.11 4. under Action.12). . Run Exchange Setup in Disaster Recovery mode. 5. On the Component Selection page of the Exchange Installation Wizard. Note Running Setup in Disaster Recovery mode installs the required Microsoft Search files to your computer. At a command prompt. and then reset Microsoft Exchange back to Disaster Recovery (Figure 3. To ensure that the Microsoft Search files are correctly reinstalled. under Component Name. 6. type <drive>:\setup\i386\setup. Disaster Recovery is automatically selected for all installed components.

Note During Setup.12 7. you should overwrite these files. For information about how to re-create full-text indexes.Chapter 3: Restoring Exchange Server 2003 81 Figure 3. Note For information about how to restore Exchange databases. Microsoft Search files are updated. To prevent the Setup program from mounting the databases after installation. Apply any Exchange service packs or hotfixes that were previously running on the server. you can retrieve the newer versions of these overwritten when you install Exchange service packs or hotfixes. 11. You typically restore this data using the "rebuild a server" recovery method. If you have to restore any Exchange database backups as part of this repair. However. you restore critical operating system files and registry information from the original server. you must install service packs and software updates in Disaster Recovery mode. During this time. Restoring Windows Backup Sets A Windows backup set contains a server's unique operating system data and configuration information. 9. the Confirm File Replace dialog box might appear. When you restore a Windows backup set to a server. Because you are trying to repair any Microsoft Search files. 10. Restart the computer. you also restore the original computer name and return the . see "Restoring Exchange Mailbox or Public Folder Stores" later in this chapter. see the procedure "To re-create full-text indexes" in "Re-Indexing the Data on Your Exchange Databases" earlier in this chapter. When you restore the original server's registry. 8. and then make sure that the Exchange databases are mounted. Re-create full-text indexes. Running Exchange Setup in Disaster Recovery mode Click Next to continue with the installation process. restore your Exchange databases now. The dialog box prompts you to specify whether you want to overwrite certain files on your computer that are newer than the files being copied from the Exchange Setup CD (Figure 3.4).

and so on).13). To restore a Windows backup set 1. it is recommended that you create Windows backup sets regularly. For Exchange Setup to complete successfully when run in Disaster Recovery mode. However. you will probably find that selecting Always replace the file on my computer provides the greatest stability and consistency among Windows Server 2003 files by ensuring all the file versions after the restore match exactly what they were when the backup was originally made. Start Backup in Advanced Mode: Click Start. the Internet Information Services (IIS) metabase. . and select the criteria for overwriting files. you cannot use Backup to back up or restore individual components comprising System State data. and click OK. and the COM+ Class registration database to another location. you can recover the following data individually after you restore the System State data from a Windows or full computer backup to another location: • • • • Windows Server 2003 registry files. For information about how to create a Windows backup set. see "Creating Windows Backup Sets" in Chapter 2. the Certificate Services database. Because of the dependencies among System State components. For more information. Click the Restore and Manage Media tab and Expand File in the console tree. Setup relies on some of the unique configuration information included in the Windows backup set (such as the registry. the older your Windows backup set is. and when you restore System State data. Note You cannot restore the Active Directory services database. Although the default setting is Do not replace the file on my computer. Expand the backup media that you want to restore (Figure 3. Note In general. click Options. Windows Server 2003 boot files.82 Exchange Server 2003 Disaster Recovery Operations Guide server to its original domain with a computer account that matches the System ID in Active Directory® directory service. click Run. Therefore. see "Creating Windows Backup Sets" in Chapter 2. Click Tools. Then click the Advanced Mode link on the Welcome screen. 4. any existing files in the destination will always be overwritten. select the Restore tab. 3. Cluster database information files. type ntbackup. SYSVOL directory files. 2. Set your file restoration preference. the more likely you are to experience problems that must be resolved before you can restore Exchange.

and must have been backed up as part of the same backup job. 5. and the system partition. see "Rebuilding a Catalog for a Restore" in Chapter 1. For information. you might have to rebuild the catalog.14). a Windows backup set must contain the System State data. Select the check boxes next to the drive letters for your boot partition and system partition (frequently the same drive). and then select the check box next to System State (Figure 3. Important To correctly restore all your Windows Server 2003 operating system components. the boot partition.13 Note Selecting the media to restore If the correct media does not display under File. Figure 3.14 data Selecting the boot and system partition. and also the System State .Chapter 3: Restoring Exchange Server 2003 83 Figure 3.

By default. For more information about how to check the success of a restore. and then click OK. In the Restore files to list. Click Yes to restart. This section provides information about how to restore a full computer backup set by using the backup utility (Backup) in Windows Server 2003. if you use a disk-imaging software utility to create your full computer backup sets. 10. 11. After the restore is completed. see "Restoring the Server" in the Exchange Server 2003 Disaster Recovery Planning Guide (http://go. if you use Backup to create your full computer backup sets. You will be notified that the current System State data will be overwritten unless you want to restore to a different location. Restoring a full computer backup set is the primary step in the "restore the server" recovery method. 8. select the location to where you want the files restored. Restoring a full computer backup set to a computer allows you to recover a server running Exchange without having to reinstall applications. You are then prompted to restart your computer to complete the restore. In Confirm Restore. Similarly. click OK. Restoring Full Computer Backup Sets A full computer backup set includes a backup of System State data and most of the data on your hard disks. 9.microsoft. 7. select the correct backup file name. click Close. see "Creating Full Computer Backup Sets" in Chapter 2. see "Creating Full Computer Backup Sets" in Chapter 2. After you verify that your Windows backup set is successfully restored. For more information about how to create full computer backup sets with Backup. see "Selecting the Advanced Options for a Restore" in Chapter 1. you would use that same utility to restore those backup sets. you use Backup to restore them. such as Exchange. These errors occur because when you restore the Windows backup set. see "Checking the Success of a Completed Restore Job" in Chapter 1. That registry might include entries that try to start services that are not yet reinstalled. make sure that it was successful. These errors should be resolved when you finish rebuilding the computer. after restarting your computer. For more information about the advanced restore options in Backup. For more information about full computer backup sets and the "restore the server" recovery method.84 Exchange Server 2003 Disaster Recovery Operations Guide 6.com/fwlink/? LinkId=21277). such as Simple Mail Transfer Protocol (SMTP). . click Advanced to specify advanced restore options. you might experience errors that indicate that one or more services cannot start. Click Start Restore. For detailed information about how to create full computer backup sets. the location specified is Original location. Ignore the errors. which were running on the server. the steps that you perform to restore your full computer backup set can vary. A full computer backup set must not include the Exchange Installable File System (IFS) drive and the drives or folders that contain your Exchange log files and database files. or click OK to start the restore. in the Restore Progress dialog box. For example. If Backup prompts you for the location of the backup file to use in the restore. To continue. Important If you perform this procedure as part of rebuilding a server. Depending on the backup and restore utility or program that you use. you also restore the original registry of the server that you are rebuilding.

To restore your Exchange databases. and cluster shared disk resources. make sure that Windows Server 2003 is functioning sufficiently well after the disaster to allow you to start the operating system and run Backup. To restore a full computer backup set 1. On the computer for which you want to restore your full computer backup set. restore the Exchange database backup that you performed by using the Microsoft Exchange Server option in Backup. 2.15). 4. Start Backup in Advanced Mode: Click Start. click Run. start your Windows Server 2003 operating system.Chapter 3: Restoring Exchange Server 2003 85 Restoring a Full Computer Backup Set by Using Backup If you used the backup utility (Backup) in Windows Server 2003 to create a full computer backup set. type ntbackup. For more information about how to rebuild the catalog. If the correct media does not appear under File. click the backup media that you want to restore. do not select those drives or folders. do not back up the IFS drive. Always include the System State data when you restore the drive partitions of your full computer backup set (Figure 3. For information about how to restore Exchange databases. or you might add duplicate and unwanted items to the database. Click the Restore and Manage Media tab. and then in the console tree. For more information about this issue. Exchange database files. . Then click the Advanced Mode link on the Welcome screen. Important When you create full computer backup sets. Because you must use Backup in this case. you must also use Backup to restore that backup set. see "Data to Exclude from Windows Backup Sets or Full Computer Backup Sets" in Chapter 2. you might overwrite newer copies of the database with older ones. you might have to rebuild the catalog. Exchange log files. and then click System State. see "Restoring Exchange Mailbox or Public Folder Stores" later in this chapter. your log files might be out of sync. If the full computer backup set that you are restoring includes the Exchange IFS drive or the drives or folders that contain the Exchange database files and transaction log files. If you restore those drives or folders. and click OK. see "Rebuilding a Catalog for a Restore" in Chapter 1. 3. Select the check boxes next to the drives that you want to restore.

Click Yes to restart. By default. 9. see "Checking the Success of a Completed Restore Job" in Chapter 1.86 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. and then click OK. click Close. select the correct backup file. click Advanced to specify advanced restore options. In Confirm Restore. make sure that it was successful. 6. . You are then prompted to restart your computer to complete the restore. Therefore. 10. the replicated Active Directory information is still available in the remaining domain controllers. select the location where you want the files to be restored.15 5. you must repair those domain controllers immediately. If you experience problems with the domain controllers in the Windows Server 2003 domain to which your Exchange server belongs. you might experience minor complications with your servers running Exchange. If these problems occur. You will be notified that the current System State data will be overwritten unless you want to restore to a different location. For more information about how to check the success of a restore. For more information about the advanced restore options in Backup. or click OK to start the restore. click OK. 7. the location specified is Original location. or your servers might stop functioning. To continue. make sure that you have more than one domain controller in each domain of your organization. if a single domain controller fails. Restoring a full computer backup set In the Restore files to list. If Backup prompts you for the location of the backup file to use in the restore. To secure the availability of the domain controllers in your Exchange organization. Restoring Domain Controllers Servers running Exchange rely on information stored in Active Directory to function correctly. Click Start Restore. in the Restore Progress dialog box. see "Selecting the Advanced Options for a Restore" in Chapter 1. After you verify that the full computer backup set is successfully restored. 8. After the restore is completed.

which helps you to back up and restore individual mailboxes. Restoring Individual Mailboxes Use recovery storage groups to recover individual mailboxes.com/fwlink/?LinkId=6270).microsoft. If all the domain controllers in your organization are affected or if you only have one domain controller. For more information. see Active Directory Disaster Recovery (http://go.Chapter 3: Restoring Exchange Server 2003 87 If you have multiple domain controllers and if the failure does not affect all the domain controllers in your organization. one of the simplest and most effective ways to deal with the situation is to build a new domain controller and join it to the existing domain. For detailed information about how to recover a Windows Server 2003 operating system domain controller. For more information.com/fwlink/?LinkId=23233). Some third party backup solutions allow brick level backup and restore.microsoft. see the documentation for your third-party software. For information about how to back up a domain controller. . see Using Exchange Server 2003 Recovery Storage Groups (http://go. The required Active Directory information will be replicated from the remaining domain controllers to the new one. you must restore your data from a backup. see "Backing Up Domain Controllers" in Chapter 2.

Resolving Exchange database restore problems. if you were to restore two normal backups to the same temporary folder the second Restore. In a disaster recovery scenario that involves rebuilding a server.env file does not exist. You can use Exchange database backups to restore one or more damaged mailbox or public folder stores.env file. Restoring a differential or incremental backup set only updates the Restore. which keeps track of the storage group that the database belongs to.env file. Note Installing Exchange (and any service packs that were running on your server before the disaster) in Disaster Recovery mode prevents the Setup program from mounting the databases after the Setup program is completed. and a separate instance of ESE is started to replay the transaction logs from their temporary location into the restored database. This section contains the following information about restoring Exchange databases: • • • • Overview of the database restore process.88 Exchange Server 2003 Disaster Recovery Operations Guide Restoring Exchange Mailbox or Public Folder Stores Note The term database is used in this guide to generically refer to Exchange mailbox stores and Exchange public folder stores. and other pertinent data. Therefore. make sure that the log files have completed replaying. use Backup to restore your Exchange databases after you run Exchange Setup and any Exchange service packs in Disaster Recovery mode. it does not create one. Always use different temporary folders for each full backup set that you are restoring. the path to the database when they were restored. When you use Backup to restore Exchange databases.env file. the range of log files that were restored. always specify a different temporary folder for each normal or copy backup set that you are restoring. You can then correctly restore and mount your Exchange database backups at the end of the setup process. The associated log files are copied to a temporary folder. If the Restore. Backup informs the ESE that the process has begun. as prompted by Exchange Setup. Overview of the Database Restore Process When a restore operation begins. The restore process creates the Restore.env file. causing ESE to enter restore mode. The database (made up of a pair of files: an .edb file and an . For example. the differential or incremental updates cannot restore. . You must restore a full backup set (either a normal or copy backup) before you can restore a differential or incremental backup set.stm file ) is then copied from the backup media directly to the database target path. the paths of the database files when they were backed up. Recovering an Exchange database.env file that would be created would overwrite the first Restore. Before you restart your server. application programming interface (API) calls are made to the Exchange Extensible Storage Engine (ESE) to restore Exchange database files and their associated log files. This is because restoring a full backup set creates the Restore. Restoring Exchange databases to another server.

env and transaction log files have been copied to the temporary folder. Restore. ESE initiates a hard recovery to replay log files into the database. the temporary instance of ESE is stopped. First. Then. so that they are paired with the correct Restore. additional transaction logs from the target storage group are also replayed. if it is possible. when you restore an incremental or differential backup.Chapter 3: Restoring Exchange Server 2003 89 However.16 illustrates the Exchange restore process. Figure 3. the newly restored database is automatically mounted in the target storage group. This brings the database up-to-date with the time that it was lost if all the log files since the backup was taken are available.env is used to determine which transaction logs will be played from the temporary folder. specify the same temporary folder you used for the full backup that the incremental or differential backup belongs with. . After the database files are copied back to their original locations and the Restore. Following hard recovery.env file. If you select the Mount Database After Restore check box in Backup.

Copy the current database files to another location (optional).90 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. Make sure that the mailbox and public folder store names in Exchange System Manager match your .16 The flow of the Exchange restore process Recovering an Exchange Database Exchange Database Recovery Checklist      Dismount the databases for each mailbox or public folder store that you are restoring. Determine the database and log file locations of the files that you are restoring (optional). Configure the databases so that the restore can overwrite them (optional).

Make sure that the restore process was successful. you must dismount only the databases that are being restored from your backup. consider using a recovery storage group instead of its original storage group. point to Programs.       Make sure that the Microsoft Exchange Information Store service (MSExchangeIS) is running. Open Exchange System Manager. 2. Typically. . Dismounting the Exchange Databases That You Are Restoring Before you perform the restore process. To dismount the mailbox and public folder stores that you are restoring 1. recovery storage groups are used only when you want to extract or merge specific data from the backup database to the original still running database. Replay the transaction log files (Eseutil /cc) (optional). Restore the selected files. In Exchange System Manager. you must dismount the Exchange databases that you want to restore. Mount the databases (stores). the restore process will fail. Select the backup files that you want to restore from your backup media. Note When mailboxes and public folders are dismounted. Because Exchange supports multiple storage groups and multiple mailbox and public folder stores. they are inaccessible to users. To restore a database without affecting e-mail users who have mailboxes on that database.Chapter 3: Restoring Exchange Server 2003 91 backup media. Click Start. point to Microsoft Exchange. Note You must dismount every database that you want to restore.17). If a database that you try to restore is still mounted. right-click the database. navigate to the database that you want to restore. and then click Dismount Store (Figure 3. and then click System Manager.

and then click Properties (Figure 3. It is only required when the databases that you restore have different GUIDs in Active Directory. For example. . A different GUID is also required if the Active Directory object for the database has been deleted. Unless you know that you must overwrite the database. right-click it. and then click System Manager. Open Exchange System Manager. 2. navigate to the database that you want to restore.92 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. a different GUID is required when you restore a database to another forest. or if you use recovery storage groups.17 Dismounting a mailbox store Configuring the Exchange Databases so That the Restore Process Overwrites Them (Optional) To ensure that the restore process overwrites Exchange databases. do not use this option. you do not have to configure the databases if you restore them to their original locations. such as a test forest. Click Start. To configure the Exchange databases so that the restore process overwrites them 1.18). point to Microsoft Exchange. However. you give each object a new GUID. point to Programs. you must configure the databases that are being restored. In Exchange System Manager. When you re-create deleted objects in Active Directory.

18 3.Chapter 3: Restoring Exchange Server 2003 93 Figure 3.19). select the This database can be overwritten by a restore check box (Figure 3. Mailbox store properties On the Database tab.19 Enabling the database to be overwritten during a restore . Figure 3.

The System path location is where other files critical to the storage group are kept. .94 Exchange Server 2003 Disaster Recovery Operations Guide Determining the Database and Log File Locations of the Files You Are Restoring (Optional) If you plan to make copies of the damaged database so that you can try to repair it later if necessary. You must do this for each database you want to move or copy.20). such as the storage group's checkpoint file. 2. navigate to the storage group that contains the database that you want to move or copy. The Transaction log location is the path where log files are written for the whole storage group. In the following procedure. Click Start. Storage group properties On the General tab. and then click OK (Figure 3. and then click System Manager. To determine the database and log file locations of the files you are restoring 1. and then click Properties (Figure 3.20 3. Open Exchange System Manager. Record these paths for each storage group that contains a database that you want to move or copy. Figure 3. you must record information from the properties dialog boxes from both the database and the storage group that contains the database.21). note the paths in the Transaction log location and System path location boxes. point to Microsoft Exchange. you determine the location of the database and log files so that you can move or copy them. point to Programs. In Exchange System Manager. right-click the storage group. These log files record every change made to a database in that storage group.

22 Exchange database file locations . 5. and then close the dialog box (Figure 3. Log file locations and system path locations In Exchange System Manager. right-click the database that you want to move or copy.22). Figure 3. and then click Properties.Chapter 3: Restoring Exchange Server 2003 95 Figure 3.21 4. note the paths of both the Exchange database file and the Exchange streaming database file. On the Database tab.

For example. Look for State: Clean Shutdown in the dumped information. For more information about how to dismount databases. remounting the database causes soft recovery to start so that the database can be shut down in a clean state. Use Eseutil /mh to dump the header information for the database. if your restore is unsuccessful. The disadvantage of copying the database files before the restore is that it might add significant time to the database recovery process. try to restore the database to a clean state before you repair it. In many cases. this will be much quicker than trying to copy the files. Moving or copying the database files to a different location over the network takes even more time. Make sure that the databases that you are moving or making a copy of are dismounted. If moving the files to another location on the same logical drive is an option. Remember that moving the file to another location on the same logical drive is the fastest way to preserve the damaged database. Create a folder to store the database files that you want to move or copy. and can use a lot of your network bandwidth. If the database is in a dirty state. This task entails playing any required transaction logs into the database. a copy of these files helps you to revert to the original versions. Make sure the destination location has sufficient room before you start the copy process. Make sure the databases you are copying have been shut down in a clean state. 3. To copy or move the existing versions of the database files you are restoring 1. The Log Required field in the dump file from Eseutil /mh will show you the logs that are required to restore the database to a clean state. you must convert these values to hexadecimal to find the appropriate transaction log files. . which might be repairable. Moving the files to a different logical disk (even if both drives share the same physical disk) or making a copy of them in any location takes much longer because each database file must be rewritten to the new location. Keeping a copy of the damaged database files allows for more recovery options. You can create the folder either on a local hard disk or on your network.96 Exchange Server 2003 Disaster Recovery Operations Guide Moving or Copying the Existing Versions of the Database Files That You Are Restoring (Optional) You can preserve the existing database files before they are overwritten by a restore in case the restore process is unsuccessful. see "Dismounting the Exchange Databases That You Are Restoring" earlier in this chapter. 2. Important Moving database files from their original location to a different folder on the same logical disk is almost instantaneous. This is just one reason why making full use of the 4 storage group and 20 database capabilities of Exchange Server 2003 (more databases of smaller sizes) is actually more manageable and can decrease the time that you spend on backup and restore-related tasks. The logs shown in this field are shown in decimal. as the only data that must be written to disk is an update to the NTFS Master File Table (MFT).

Then click the Advanced Mode link on the Welcome screen.24). you might have to rebuild the catalog. In your backup or restore device. To ensure that storage group and database display names match the names of the files you are restoring 1. it will read this data from Active Directory and display it so that the data can be verified against the names of the storage groups and databases as they appear in your backup. type ntbackup. if you delete a storage group and its databases before you try to restore them. click Run. . If Exchange System Manager is running on any Exchange server in the organization. Click the Restore and Manage Media tab.Chapter 3: Restoring Exchange Server 2003 97 Figure 3. If the names do not match. and then in the console tree. and click OK. Record the names of the storage groups and each mailbox store or public folder store that you want to restore (Figure 3. For more information about how to rebuild the catalog.23 Copying database files before the restore process Ensure That the Mailbox and Public Folder Store Names in Exchange System Manager Match Your Backup Media The names of the storage groups and databases (mailbox stores or public folder stores) that you restore from your backup media must match the names of the storage groups and databases as they exist as objects in Active Directory for the server to which they are being restored. insert the backup media that contains the backups that you want to restore. 5. the storage group and its database will not exist in Active Directory for that server. see "Rebuilding a Catalog for a Restore" in Chapter 1. and you must re-create a storage group and databases with names that exactly match the storage group and database names on your backup media. For example. 4. the restore process fails. 3. If the correct media does not display in the console tree. click the backup media that you want to restore. 2. Expand the tree structure of the media so that the name of each Exchange database that you are restoring appears. 6. Start Backup in Advanced Mode: Click Start.

98 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. . The names in Exchange System Manager must match those on the backup media or the restore process will fail. note the names of the storage group and databases (Figure 3. In the console tree and details pane. Storage group and mailbox store names in Backup Open Exchange System Manager. In Exchange System Manager. and then click System Manager. point to Programs.25). 8. navigate to the server that contains the database that you want to restore.24 7. point to Microsoft Exchange. Click Start. Compare these with the storage group and database names on your backup media. 9.

after you follow the procedures earlier in this chapter. In Exchange System Manager. you must create storage group and databases that match the names of the storage group and databases that you are restoring from backup. Type the name of the database or storage group that you are restoring. Click Rename (Figure 3. right-click the storage group or database that you want to rename. 2. you only have to rename the database or storage group. 3. you find that the names do not match. . or the database or storage group is missing. To rename a storage group or database 1. and then press ENTER. In situations where you are setting up a new server.26). Make sure that the name you type exactly matches the name on the backup media.25 Manager Storage group and mailbox store names in Exchange System Resolving Mismatched Names Between Exchange System Manager and Your Backup Media If.Chapter 3: Restoring Exchange Server 2003 99 Figure 3. In the case where a database or storage group name has changed. you have to create them.

Click New. right-click the server where you want to create the storage group.26 Renaming a database To create a storage group 1.27). 3.27 Creating a new storage group in Exchange System Manager . Figure 3. 2.100 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. Click Storage Group (Figure 3. In Exchange System Manager.

and then type services. In Exchange System Manager right-click the storage group where you want to create the database.28). To create a mailbox or public folder store 2.29).Chapter 3: Restoring Exchange Server 2003 101 4. . To start the Microsoft Exchange Information Store service (MSExchangeIS) 1. click Run. Locate the Microsoft Exchange Information Store service (MSExchangeIS) and make sure that the Status column displays Started (Figure 3. 3. Click the type of database that you are restoring (Figure 3. click No. Figure 3. It is best not to mount the store at this point. 2. Point to New. Start the Services snap-in: Click Start. Mounting the store can create log files that conflict with the log files on your backup media and therefore interfere with log file replay when you restore the database from backup. Click OK. 6. type the name of the mailbox or public folder store exactly as it appears on your backup media. Creating a new mailbox store in Exchange System Manager In the Name field. Make Sure That the Microsoft Exchange Information Store Service (MSExchangeIS) Is Running Perform the following procedure to start the Microsoft Exchange Information Store service (MSExchangeIS). Click OK.28 4. Note The structure that you see in the user interface (UI) should mirror the original structure on your backup media. 1. When prompted to mount the store. 5.msc. On the General tab of the Properties dialog box. type the name exactly as it appears on your backup media. 5.

you might have to rebuild the catalog. select the check box next to the storage group that you want to restore. Then click the Advanced Mode link on the Welcome screen.30). 3. right-click Microsoft Exchange Information Store. If you have to start the service. type ntbackup. To select the backup files to restore from your backup media 1. Click the Restore and Manage Media tab. In the console tree. 4. click the backup media that you want to restore. If you want to restore just one database in a storage group. click Run. Start Backup in Advanced Mode: Click Start.29 Locating the Microsoft Exchange Information Store service (MSExchangeIS) 3. if you want to restore a whole storage group. . Click the check boxes next to the storage groups or databases that you want to restore (Figure 3. Selecting the Backup Files to Restore from Your Backup Media Perform the following procedure to select the backup files to restore. For more information about how to rebuild the catalog. and then click Start. 2. If the correct media does not display in the console tree. see "Rebuilding a Catalog for a Restore" in Chapter 1.102 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. select only the check box next to the database you want to restore. For example. and click OK.

Figure 3. some transaction logs might not be replayed. and then restore any incremental or differential backups in chronological order. 3. To restore selected files 1. In the Restore To box. specify the Exchange server that you want the databases restored to (Figure 3. 2. Click Start Restore. If you restore backup sets out of order.Chapter 3: Restoring Exchange Server 2003 103 Note Selecting or clearing the Log Files check box in Backup does not affect the restore process. In the Restore files to list. Always restore the normal backup first.31). By default. the location specified is Original location. make sure to restore the backups in chronological order. select the location to where you want the files restored.30 Selecting the storage groups or databases that you want to restore Restore the Selected Files In cases where you are restoring differential and incremental backups. Exchange automatically detects whether log files are to be restored based on the type of backup that you are restoring. .

Because transaction logs are written per storage group. "The 'Last Backup Set' Check Box and Hard Recovery in Exchange" (http://go. 11. It is recommended that you do not select this check box. Select the Last Restore Set check box only if this is the last backup set that you have to restore before you remount your databases. leave this check box cleared until you restore the final incremental or differential backup in the series. . and you are sure that you are ready to mount the databases. and not per database. It is recommended that you create an empty temporary folder for this procedure. see.104 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. 6. For a step-by-step explanation of this process. 5. Only select the Mount Database After Restore check box if this is the last backup set that you plan to restore. there were problems with the restore process that must be resolved before you can continue restoring your Exchange database.com/fwlink/?LinkId=3052&kbid=232938). specify a directory to store log files during the restore process. you can use Eseutil to manually replay the transaction logs. If you do not select this check box when you restore the last backup set. If the status field reads Failed. Important The directory that you specify in the Temporary location for log and patch files box must not contain the original database or log files or the restore might fail. To perform the restore. using a temporary folder ensures that transaction log replay is isolated and will not interfere with undamaged databases that are still running in a storage group during recovery. The disk space requirement is about 10 MB more than the size of the transaction log files that are being restored. The restore process does not initiate hard recovery to play back the log files to the database that is being restored until this box is selected. The Restoring Database Store dialog box In the Temporary location for log and patch files box. select the correct backup name. Make Sure That the Restore Process Was Successful The Status field in the Restore Progress dialog box indicates where Backup is in the restore process. If Backup prompts you for the location of the backup file to use in the restore. If you are restoring a backup that is part of a series of normal. Click the Report button for more information about these errors. 10. Click OK when you are ready to start the restore process. For more information about hard recovery and transaction log replay. "Replay the Transaction Log Files Using Eseutil /CC (Optional)" later in this chapter. 12. or incremental backups.microsoft. and then click OK. 8. 7. differential. you must have sufficient space in the directory to store the files. see Microsoft Knowledge Base article 232938.31 4. 9.

Do not use any other parameters.Chapter 3: Restoring Exchange Server 2003 105 If the Status field reads Completed. the transaction logs must still be replayed for the whole recovery process to complete. Hard recovery is the process that brings a restored database back to a consistent state. When the transaction logs finish replaying successfully. To run Eseutil from any command prompt. follow the procedure in "Running Exchange Tools Globally on a Server" earlier in this chapter. However. it is in what is referred to as an inconsistent state where the database and log files are not synched together. and then click OK. 3. For more information about how to check the success of the restore process. you can select the Last Restore Set check box in Backup when you restore your last database or you can use the Eseutil /cc command. . Type eseutil /cc. Replay the Transaction Log Files Using Eseutil /CC (Optional) When a database is restored from backup media. It is recommended that you run only one instance of Eseutil /cc at a time. 2. After the last backup has been restored and you want to initiate a hard recovery. Find the folder where the Restore. click Run. "Operation completed successfully" appears (Figure 3. Transaction log replay can take several hours to complete. To fully recover your Exchange data after you restore the database. see "Checking the Success of a Completed Restore Job" in Chapter 1. To run Eseutil /cc 1. type cmd.env file is located. the message. Eseutil performs the same function as the Last Restore Set check box. To initiate hard recovery. open a Command Prompt window: Click Start. even if you restore multiple databases concurrently. Use all other Eseutil /cc switches with extreme caution.32). you must replay the transaction logs to bring the database up-to-date or make it consistent. Backup has successfully restored the database and the log files have been restored to the temporary directory. 4.

106 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3.32 Replaying transaction logs with Eseutil /cc .

Chapter 3: Restoring Exchange Server 2003 107

Mount the Databases (Stores)
Mounting the store is the last step in recovering an Exchange database. Before you mount the store, make sure that the hard recovery is completed. To make sure that the hard recovery is completed, check whether the Restore.env file has been deleted. Restore.env is not deleted until the hard recovery succeeds. Open the folder that you designated as the temporary location for log files, and then open the folder for the storage group that you are restoring. If the Restore.env file is still there, the hard recovery is not completed. Do not try to mount the store. Note
If you have performed hard recovery with the /k switch, which prevents deletion of Restore.env (Eseutil /cc /k), check the database header for a clean shutdown state by using Eseutil /mh.

After you are sure that the transaction log replay is completed, mount each store that you have recovered.

To mount the store (database)
1. 2. Open Exchange System Manager. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. In Exchange System Manager, navigate to the database that you want to mount, right-click the database, and then click Mount Store (Figure 3.33).

Figure 3.33

Mounting the store

Resolving Exchange Database Restore Problems
If the restore process fails, troubleshoot the problem as soon as possible. Sometimes, performing the restore process again corrects the problem. Other times, you might have to repair one or more Exchange databases. For information about how to repair Exchange databases, see "Repairing Exchange Databases" earlier in this chapter.

108 Exchange Server 2003 Disaster Recovery Operations Guide

For general information about how to search and troubleshoot restore errors, see "Checking the Success of a Completed Restore Job" in Chapter 1. If you experience problems with the databases that you tried to restore, check the application log for errors, and then search the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=18175) for specific solutions to those errors.

Troubleshooting Failed Restore Processes
If the restore process is not completed successfully, search for errors in the Backup status window, the Backup restore log, and the logs in Event Viewer. These errors might help you determine the cause of the failure. Because Exchange relies heavily on your Windows Server 2003 operating system, look for both Exchangespecific errors in the event logs and errors for non-Exchange components that Exchange relies on. Also consider hardware errors. For example, a bad page file on a hard disk drive can prevent Exchange from moving forward writing to the database. After you have identified errors in the event log that you suspect might be the cause of the failed restore, search the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=18175) for those specific errors. Note
If one or more Exchange database or log files are damaged or missing, the application log might include the following error: Error -1216 (JET_errAttachedDatabaseMismatch) For information about how to troubleshoot database restore issues that include the 1216 error, see Microsoft Knowledge Base article 296843, "XADM: Error -1216 Recovering an Exchange 2000 Database" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=296843).

If you cannot resolve the problems that are preventing you from restoring your Exchange databases, contact Microsoft Help and Support (http://go.microsoft.com/fwlink/?LinkId=14898).

Restoring Exchange Databases to Another Server
If you experience problems when you restore Exchange databases to the original server, or to the server to which you have restored the original server's configuration, you can restore Exchange databases to a different Exchange server. However, restore Exchange databases to a different server only as a last resort. The Exchange server to which you restore Exchange databases must meet specific criteria. For example, Exchange service packs and hotfixes that you install on the server must match those of the server whose Exchange databases you backed up. For more information about how to restore Exchange databases to a different server, see Exchange 2000 Server Database Recovery (http://go.microsoft.com/fwlink/?LinkId=6273).

Restoring the Microsoft Exchange Site Replication Service (MSExchangeSRS)
Recovering the Microsoft Exchange Site Replication Service (MSExchangeSRS) involves restoring the MSExchangeSRS service database. You can use Backup to restore the MSExchangeSRS service database.

Chapter 3: Restoring Exchange Server 2003 109

Note
Alternatively, you can manually restore the MSExchangeSRS database (Srs.edb file) if you have a backup of that file. The Srs.edb file is located in the SRSData folder under the folder where you installed Exchange.

If you are restoring the MSExchangeSRS service database as part of recovering a server running Exchange, complete the required steps to restore or rebuild your server before you perform the following procedure. For example, if you are rebuilding an Exchange server that was running the MSExchangeSRS service, restore the local MSExchangeSRS service database after running Exchange Setup in disaster recovery mode. For information about when to restore the MSExchangeSRS service, see "Exchange Member Server Recovery" later in this chapter. For information about how to back up the MSExchangeSRS service database, see "Backing Up the Microsoft Exchange Site Replication Service (MSExchangeSRS)" in Chapter 2.

To restore the MSExchangeSRS service database
1. 2. 3. Open Exchange System Manager. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. In Exchange System Manager, in the console tree, expand Tools, and then expand Site Replication Services to locate the server that is running the MSExchangeSRS service. Under Site Replication Services, there is at least one entry named Microsoft Exchange Site Replication Service <computer name>, where <computer name> is the name of the server that is running the MSExchangeSRS service (Figure 3.34).

Figure 3.34 4. 5. 6. 7. 8.

Locate the server that is running SRS

On the server that is running the MSExchangeSRS service, click Start, click Run, type services.msc, and then click OK. In Services, in the details pane, double-click Microsoft Exchange Site Replication Service. Click the General tab in Microsoft Exchange Site Replication Service Properties. In the Startup Type box, select Automatic. Stop the MSExchangeSRS service if it is running. On the General tab, click the Stop button to stop the service, and then click Apply.

where <drive> is the location where you installed Exchange Server.chk files from the srsdata folder and move them to the temporary folder that you created (Figure 3.35). 10. point to All Programs. make sure that the Hide extensions for known file types check box is cleared. the location for this folder is <drive>:\Program Files\Exchsrvr\srsdata. click Folder Options. To move the current MSExchangeSRS service files: a. If this restore process fails. under Advanced Settings. you might be able to use the existing files to restore your MSExchangeSRS service data.35 Selecting the MSExchangeSRS service data to move to a temporary folder Note Although you can choose to delete the files instead of moving them to a temporary location. Do not close Microsoft Exchange Site Replication Service Properties. Figure 3. click Start. b. . 11. and then click Windows Explorer. point to Accessories. By default. c. Move any files that exist in the srsdata folder on the server running the MSExchangeSRS service to a temporary location. The original MSExchangeSRS service database files cannot be restored if these files are present. or .log.110 Exchange Server 2003 Disaster Recovery Operations Guide 9. it is a good idea to keep them. Navigate to the srsdata folder. d. On the server that is running the MSExchangeSRS service. On the View tab. Create a temporary folder to hold the files that you want to move. f. . and then click OK. Select all existing . On the Tools menu.edb. e.

point to Accessories. Important This server must be the server that is running the MSExchangeSRS service. click the backup media that you want to restore. Open Backup in Advanced Mode: Click Start. under Service status. point to All Programs.37). Figure 3. 18. The MSExchangeSRS databases will be restored to this server (Figure 3. Select the <computer name>\Microsoft Site Replication Service\SRS Storage check box. specify the server that is running the MSExchangeSRS service.36 Restoring Exchange SRS data 16. the location specified is Original Location. If the correct media does not display under File. point to System Tools.36). in the Restore to box. 14. . Click Start Restore. see "Rebuilding a Catalog for a Restore" in Chapter 1. and then in the console tree. 13. In Restoring Database Store. By default. 17. where <computer name> is the name of your Exchange server that is running the MSExchangeSRS service (Figure 3. For more information about how to rebuild the catalog. click Start. Start the MSExchangeSRS service: In Microsoft Exchange Site Replication Service Properties. select the location to where you want the file to be restored. In the Restore files to list.Chapter 3: Restoring Exchange Server 2003 111 12. and then click Backup. you might have to rebuild the catalog. 15. Click the Restore and Manage Media tab.

if you did not create a full computer backup set of the computer that is running the CA. Important The directory that you specify in the Temporary location for log and patch files box must not contain the original database or log files or the restore will fail. Select the Last Restore Set check box only if this is the last backup set that you have to restore. 21. You are then prompted to restart your computer to complete the restore. Note The Mount Database After Restore check box does not affect your MSExchangeSRS service database restore. leave this check box cleared until you restore the final incremental or differential backup in the series. It is recommended that you create an empty temporary folder for this procedure. If Backup prompts you for the location of the backup file to use in the restore. It is recommended that you restore the CA by restoring the full computer backup set that was created on the computer that is running the CA service. see "Backing Up the Certification Authority (CA)" in Chapter 2. click Close. For information about the different methods of backing up the CA.37 The Restoring Database Store dialog box 19. If you want to restore a backup that is part of a series of normal. Restoring the Certification Authority (CA) The restore method that you use for the certification authority (CA) depends on the type of backups that you performed. Perform any additional steps that your disaster recovery process requires. 22. After the restore is completed. 23. select the correct backup name. or incremental backups. see "Checking the Success of a Completed Restore Job" in Chapter 1. Make sure that the restore was successful. differential. After you verify that the MSExchangeSRS service database backups are successfully restored.112 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. That control is applicable only to mailbox and public folder store restoration procedures. the Restore Progress dialog box appears. 25. you can restore the CA by restoring the Windows backup set of the computer . However. specify a directory to store log files during the restore process. In the Temporary location for log and patch files box. For more information about how to check the success of a restore. and then click OK. in the Restore Progress dialog box. 20. 24. such as installing Exchange service packs. Click Yes to restart.

certificates. Note If the IIS metabase is not intact. You access this wizard from the Certification Authority MMC snap-in. If you use the Certification Authority MMC snap-in to restore the CA. IIS will not start. and the certificates database. you must also restore the IIS metabase if it has been damaged or lost. . see "Restoring Full Computer Backup Sets" and "Restoring Windows Backup Sets" earlier in this chapter. For information about how to restore full computer backup sets and Windows backup sets. and Certificate Services Web pages will not load. You can also use the Certification Authority Restore Wizard to restore keys.Chapter 3: Restoring Exchange Server 2003 113 that is running Certificate Services (the System State data part of a Windows backup set includes the Certificate Services database).

A possible owner node tries to start all the resources for that EVS.microsoft. if one of the resources in an Exchange Virtual Server (EVS) fails.com/fwlink/?LinkId=6273).com/fwlink/? LinkId=3052&kbid=328835). An important difference in disaster recovery processes for Exchange clusters is the task of identifying what caused a particular resource to fail. first determine whether the failure is on a single node (which indicates that there are problems with the node's files) or on every node (which indicates that there are problems with the cluster's objects or the shared cluster resources). If the resources cannot come online for the new node. If all nodes cannot bring the EVS resources online. Important The Certification Authority Restore Wizard in the Certification Authority MMC snap-in requests that you supply a password when you back up public keys.114 Exchange Server 2003 Disaster Recovery Operations Guide You restore the IIS metabase file when you restore a Windows backup set (the System State data part of a Windows backup set includes the IIS metabase).microsoft. If you cannot repair the node or the whole cluster. If you still cannot determine the cause of the failure. that node continues to perform the tasks that were previously performed by the damaged node. see Exchange 2000 Server Database Recovery (http://go. the EVS goes offline. This information applies to Exchange Server 2003. search the event logs in Event Viewer. see Microsoft Knowledge Base article 313272. "HOW TO: Back Up and Restore a Certificate Authority in Windows 2000" (http://go. For more information about how to preserve the root certificate. that new node fails over to the next possible owner node. you can perform the repair options listed in "Repairing Windows Server 2003" or "Repairing Exchange Server 2003" earlier in this chapter. Restoring Connector-Specific Data The process that you use to restore connector-specific data (for example Novell GroupWise connector configuration data) depends on the type of connector you are using. see Microsoft Knowledge Base article 328835. For more information about how to back up and restore connectors. Similarly. Restoring Exchange Clusters The disaster recovery processes for restoring Exchange clusters are similar to the processes for restoring data on stand-alone Exchange servers.microsoft. it is helpful to understand how Exchange cluster resources can continue to remain online. If the resources cannot come online for the new node. If a problem occurs. one of the possible owner nodes for the resource group tries to take control of that group. cluster. private keys.com/fwlink/?LinkId=3052&kbid=313272). Following the failover. the Cluster service takes control of the cluster. However. and CA certificates. even if one of the nodes experiences a failure. For information about how to restore the CA from the Certification Authority MMC snap-in and how to back up IIS metabase from the IIS MMC snap-in. You can also search for solutions in the Microsoft Knowledge Base (http://go. before you start to perform recovery processes on your clusters. This process continues until all possible owner nodes for that group cannot come online.com/fwlink/?LinkId=18175). . that node will fail over to the next node.microsoft. "XADM: How to Back Up and Restore Connectors on Exchange 2000" (http://go. You can also restore the IIS metabase independently by using the IIS snap-in. If one of the nodes in a cluster fails (known as a failover event). the resources on that virtual server will be unavailable to Exchange clients until the problem is resolved. or resources (such as the quorum disk resource or mailbox and public folder stores). consider replacing the node or recovering the node. To determine the cause of the failure. If all the resources can come online for the new node.

although the replacement node must belong to the same domain. b. provided there is at least one functioning node in the cluster. Install Exchange on the replacement node. Restoring or rebuilding a cluster node from backups. Node Creation Checklist      Evict the damaged node from the cluster. restore the full computer backup or the Windows backup. Use one of the following methods to replace a failed node: • Replace any damaged hardware on the failed node. and then click Open Connection. Choose one of the following methods for connecting to the cluster: a. point to All Programs. Important For fault tolerance purposes. Replacing Damaged Exchange Cluster Nodes If one node of a cluster is not functioning correctly. The replacement node must have as much RAM and at least as fast a processor as the node it is replacing.Chapter 3: Restoring Exchange Server 2003 115 This section provides the following procedural information about restoring Exchange clusters: • • • • Replacing damaged Exchange cluster nodes. Then join the node to the cluster. and additional software (such as service packs). • Create a new node by installing your Windows Server 2003 operating system. Evict the Damaged Node from the Cluster Use the following procedure to evict the damaged node from the cluster. click the cluster that you want to administer in the drop-down list (Figure 3. In Open Connection to Cluster. and then click Cluster Administrator). Exchange. Make sure that the hardware in a replacement node is as good or better quality than the hardware in the other nodes of the cluster. Restoring shared disk resources. Recovering a whole Exchange cluster. 2. repair or replace damaged nodes as soon as possible.38). The computer NetBIOS (network input/output system) name of the replacement node can be different from the computer name of the failed node. . Add the replacement node to the cluster. you can replace the damaged node with a new node. Open Cluster Administrator (click Start. Connect the new node to the shared disk resource. To evict a node from the cluster 1. point to Administrative Tools. Install your Windows Server 2003 operating system and join the new node to the domain. and then rejoin the node to the cluster. Make sure to install the same versions of Exchange and your Windows Server 2003 operating system on the new node as that of the rest of the cluster. Click File.

– or – 3.39). Note After you stop the Cluster service on the node. In Services. you can no longer make changes to the cluster. In Cluster Administrator. double-click Cluster Service.38 – or – • Opening a connection to a cluster In Open Connection to Cluster click Browse. click OK. point to All Programs. right-click the node that you want to evict and select Evict Node (Figure 3. and then click Services. and in the Cluster box. and then click Stop. point to Administrative Tools. If you are running Cluster Administrator on the node that you want to evict. click Start. To stop the Cluster service. . • Open Cluster Administrator on a cluster node and type a period (.) in Cluster or server name. switch to a different computer to evict the node. Stop the Cluster service on the node that you want to evict. When the Cluster service has stopped successfully. 4.116 Exchange Server 2003 Disaster Recovery Operations Guide Figure 3. type the NetBIOS name of an active node in the cluster.

Connect the New Node to the Shared Disk Resource After you have successfully joined the replacement node to the domain. Do not install Exchange on the new node yet.39 5. including the service packs. Install Windows Server 2003 and Join the New Node to the Domain Install Windows Server 2003.Chapter 3: Restoring Exchange Server 2003 117 Figure 3. You can use any computer name that is not on the network for the new node. . make sure that the computer has physical access to the cluster's disk resources. After the new node is running and connected to the shared disk resource. software updates. join the replacement node to the same domain as the other nodes in the cluster. add the replacement node to the cluster. Evicting a node from a cluster Remove the node from the cluster's shared disk resource. Then restart the replacement node. Shut down the replacement node and connect the computer to the cluster's disk resource. After the operating system is installed and patched. and other software for your Exchange cluster nodes (such as antivirus software) that matches the versions running on the cluster.

3. Adding a new cluster node Click OK to continue. Open Cluster Administrator: click Start. The server information is kept in the quorum for each EVS.40).) After the Exchange Setup program is completed. .40 4. In Open Connection to Cluster. Install Exchange on the Replacement Node Install Exchange Server on the replacement node.microsoft. When the Add Nodes Wizard is completed. The Add Nodes Wizard appears. 2. select Add nodes to cluster from the Action list. Click File. Exchange automatically notifies you that the cluster-aware version of Exchange is being installed. uninstall. 5. either type the name of an existing cluster. see "Deploying Exchange 2003 in a Cluster" in the Exchange Server 2003 Deployment Guide (http://go.118 Exchange Server 2003 Disaster Recovery Operations Guide Add the Replacement Node to the Cluster Use the following procedure to add the replacement node to the cluster. and reinstall. Then in Cluster or server name. Disaster Recovery mode is not available when the Setup program is running on cluster nodes. To add the replacement node to the cluster 1. you do not run Exchange Setup with the /disasterrecovery switch. point to All Programs. point to Administrative Tools. The Setup modes available for Exchange clusters are install. Therefore. or click Browse to search for an available cluster (Figure 3. click Finish. Figure 3. a specific server's Active Directory data does not have to be recovered and pushed down to the metabase for that node. Important When you run Exchange Setup as part of rebuilding a cluster node. select a name from the drop-down list box. and then click Cluster Administrator. (Applications that support the Cluster API are defined as clusteraware. change. The purpose of running the Exchange Setup program on the cluster node is to install the required Exchange binaries on the node.com/fwlink/?LinkId=21768). For detailed information about how to set up an Exchange cluster. Click Next to continue. 6. The reason that you do not use the /disasterrecovery switch is that you do not know which Exchange Virtual Server (EVS) that node might be hosting in the future. install any Exchange service packs that are running on the other nodes in the cluster. and then click Open Connection.

you might have to replace the failed hard disk and restore the contents of the lost disk from backups. Restoring an Exchange Database to a Cluster If any drives containing database files or transaction log files are lost. you use the Network Name resource of the Exchange Virtual Server (EVS) computer instead of the Windows computer name of the cluster node. or from any computer in the domain that is configured to perform Exchange backup and restore procedures. all cluster nodes have access to the most recent database changes. To restore a backup of the Exchange cluster node databases. you must perform steps that are similar to the steps for restoring Exchange databases to a stand-alone member server. when you restore the cluster node databases. "Recovering from an Event ID 1034 on a Server Cluster" (http://go. If the drive that contains the quorum disk resource is damaged. A cluster server relies on disk signatures to identify and mount volumes. The procedures for restoring or rebuilding a node are the same as the procedures for restoring or rebuilding a stand-alone server. if one node fails over to another. you must use your Exchange database backups to recover those drives. For more information. The quorum disk resource is accessible to other cluster resources. it might prevent the Cluster service from starting. The only difference between these processes is that. "How to Back Up and Restore a Windows Server 2003 Cluster" (http://go. you can back up and restore the Exchange databases of an EVS from any node in the cluster. If the disk signature for a shared disk resource changes.Chapter 3: Restoring Exchange Server 2003 119 Restoring or Rebuilding a Cluster Node from Backups Another recovery method for replacing a failed node with a new node is restoring or rebuilding a failed node from backup.microsoft.com/fwlink/? LinkId=3052&kbid=280425). For more information about how to resolve this problem. You would want to restore a node with either a Windows backup or full computer backup if you had special configuration information or dynamic or static data that you wanted to replace from backup to the node instead of having to re-create or reinstall it. you can use several methods to restore it. Consider a strategy that involves restoring a node from backup if it seems easier and makes more sense than creating a new node from scratch. It might be a lot of work to prepare a new node for the cluster depending on how your cluster nodes are set up and what applications are installed to them.microsoft. see "Restoring Exchange Mailbox or Public Folder Stores" earlier in this chapter. Additionally. you must have the required backup sets. If you have the correct permissions. to restore or rebuild a failed node. see Microsoft Knowledge Base article 280425. Restoring a Quorum Disk Resource The quorum disk resource is a shared disk resource that contains details of all the changes that have been applied to the cluster database. Restoring Shared Disk Resources If the shared disk resources that are used by the groups in the cluster are damaged. The Network Name of the virtual server is the same name that users use to connect to their EVS that is running in the cluster. You must type the Network Name of the EVS in the Restore text box of the backup utility (Backup) in Windows Server 2003. Therefore. . see the Windows Server 2003 online Help and Microsoft Knowledge Base article 286422.com/fwlink/? LinkId=3052&kbid=286422). For detailed information about how to restore Exchange databases.

For detailed information about how to restore a member server. you must recover the whole cluster. see "Exchange Member Server Recovery" later in this chapter.microsoft. The process for recovering a whole cluster includes many of the same procedures used for recovering stand-alone Exchange member servers.120 Exchange Server 2003 Disaster Recovery Operations Guide Recovering a Whole Exchange Cluster If you lose all the nodes of an Exchange cluster at the same time.com/fwlink/? LinkId=21277). For more information about stand-alone server recovery methods. . see the Exchange Server 2003 Disaster Recovery Planning Guide (http://go.

see "Restoring Shared Disk Resources" and "Restoring a Quorum Disk Resource" earlier in this chapter. The methods section provides a brief overview and checklist of the recovery method that you want to use to restore your member servers. the first node that you recover (also known as the first node) must be the node that owned the quorum disk resource at the time that you created the backup sets for your nodes. restore your Exchange database backups (if applicable). or continue to restore nodes from your full computer backup sets. Rebuilding the Server If you use the "rebuild the server" method to recover the first node. you can still recover your whole cluster. After you ensure that the first node in the cluster can bring all the cluster resources online. • Exchange Member Server Recovery The methods for recovering Exchange member servers are detailed in "Member Server Recovery Methods" later in this chapter. you must recover the quorum disk resource (if necessary) after you restore the Windows backup set. To attempt this type of recovery. not in Disaster Recovery mode. Additionally. For more information about how to restore these shared disk resources. you must run Exchange Setup normally. the procedures are detailed in "Member Server Recovery Procedures" later in this chapter. and the objects in your cluster should appear as they did before the disaster. After you recover the first node. To view your cluster information. you can insert new nodes. or continue to restore or rebuild additional failed nodes. After your cluster resources are online. insert standby recovery nodes. use Cluster Administrator. Because many of the specific procedures are common among the three recovery methods. • Restoring the Server If you use the "restore the server" method to recover the first node. After you ensure that the first node in your cluster can bring all the cluster resources online. see "Maintaining Records About Your Server Clusters" in Chapter 2. You must also have sufficient informational records about your cluster configuration. contact Microsoft Help and Support (http://go. The following information provides more explanation about using the "restore the server" and the "rebuild the server" methods to recover the first node of your cluster. Important When you install Exchange to a cluster node as part of a cluster node recovery. you must have backups of your Exchange databases (or your Exchange database files and transaction log files must be intact on one of your cluster's shared disk resources). . the Cluster service starts. After you install Exchange (do not use the /disasterrecovery switch. The procedures required in this type of recovery are for advanced-level administrators only.Chapter 3: Restoring Exchange Server 2003 121 If you do not have the required full computer backups or Windows backups of the nodes in your cluster. insert standby recovery nodes. After you restore your Windows backup set. insert standby recovery nodes. When implementing a recovery strategy for a whole cluster. see the procedures section. make sure that all your cluster resources come online. If you need specific help on one of the procedures in the checklist. the quorum disk resource or Exchange databases) after you restore the full computer backup set. advancedlevel administrators should only consider this cluster recovery method if there is no alternative method available. you can insert new nodes. you might have to restore one or more of the cluster's shared disk resources (for example. For information about how to record cluster information. perform a normal install). you can insert new nodes.microsoft.com/fwlink/?LinkId=14898). Important To rebuild a whole cluster using your cluster's information records instead of restoring the quorum. or continue to rebuild nodes from your backup sets.

Try to repair the server again if the restore fails. Try to repair the damaged member server (optional). It takes more time to rebuild a server. • Rebuilding an Exchange member server. Install service packs and software updates. However. Re-create your full-text indexes.122 Exchange Server 2003 Disaster Recovery Operations Guide For general information about these recovery methods. Restore the Exchange databases from backup media.microsoft. • Restore the System State data. Member Server Recovery Methods This section discusses the following methods you can use to recover a damaged server running Exchange: • Restoring an Exchange member server. Restore the full computer backup set. Restoring an Exchange Member Server Restoring an Exchange member server involves restoring a full computer backup set made from a server running Exchange.com/fwlink/?LinkId=21277). Restoring an Exchange member server requires fewer steps than other server recovery methods. including the advantages and disadvantages of each. Follow these steps if necessary:    Rebuilding an Exchange Member Server To rebuild an Exchange member server. Restoring Checklist      Move or copy the Exchange database and log files (optional). see the Exchange Server 2003 Disaster Recovery Planning Guide (http://go. see the Exchange Server 2003 Disaster Recovery Planning Guide (http://go. Replace any damaged hardware. .microsoft. you must: • Reinstall your Windows Server 2003 operating system (if you cannot start the server) and other software applications. A full computer backup set includes a backup of System State data and most of the data on your hard disks. For general information about the "restore the server" recovery method. • Run Exchange Setup in disaster recovery mode.com/fwlink/? LinkId=21277). the resulting operating environment is cleaner than if you were to restore a server from a full computer backup set. • Restore the Exchange databases. see "Member Server Recovery Procedures" later in this chapter. For detailed information about how to perform the procedures that are listed for each method. • Using an Exchange standby recovery server.

Restore any additional non-Exchange data from backup. Restore Site Replication Service (SRS).com/fwlink/?LinkId=21277). Follow these steps if necessary:       Using an Exchange Standby Recovery Server To recover from a disaster using a standby recovery server. configure the same drive letter and drive space configurations as the server that is running Exchange and that you intend to replace. Install Exchange hotfixes. If a disaster occurs. Restore MSSearch. Install service packs and software updates Install any other applications (not Exchange). Software and firmware updates that existed on the damaged server. Replace any damaged hardware. Restore the Exchange databases from backup media. Because servers running Exchange include various types of dynamic data. . Install Exchange service packs in disaster recovery mode. Note Install your Windows Server 2003 operating system to a workgroup. The spare servers must have hardware and firmware that is the same as the hardware of the server that you are replacing. Restore the Windows backup set. Operating system service packs or product updates. using the standby server recovery method is not as simple as disconnecting the damaged server and connecting the standby recovery server in its place. including both the SMTP and Network News Transfer Protocol (NNTP) IIS components as part of your installation. Additionally. you must have one or more spare servers available to replace the damaged server. Software applications (not including Microsoft Exchange Server). For general information about implementing the standby server recovery method.microsoft. Restore the certification authority (CA). prepare your standby recovery servers by installing the following: • • • • The correct version of your Windows Server 2003 operating system. see the Exchange Server 2003 Disaster Recovery Planning Guide (http://go. Install your Windows Server 2003 operating system if you cannot start the server in its current state. For this reason. Try to repair the server again if the restore fails. Re-create your full-text indexes.Chapter 3: Restoring Exchange Server 2003 123 Rebuilding Checklist            Move or copy the Exchange database and log files (optional). Try to repair the damaged member server (optional). Run Exchange setup in disaster recovery mode. using standby recovery servers minimizes the downtime that your Exchange organization experiences.

124 Exchange Server 2003 Disaster Recovery Operations Guide

Standby Checklist            Move or copy the Exchange database and log files (optional). Try to repair the damaged member server (optional). Shut down the damaged server and remove it from the network. Move the physical hard drives from the damaged server to the standby server. Connect the standby server to the network. Restore the Windows backup set. Install service packs and software updates. Install any other applications (not Exchange). Run Exchange Setup in disaster recovery mode. Install Exchange service packs in disaster recovery mode. Install Exchange hotfixes. Restore the Exchange databases from backup media. Re-create your full-text indexes. Restore Site Replication Service (SRS). Restore the certification authority (CA).

Follow these steps if necessary:    

Member Server Recovery Procedures
This section explains the details for each procedure listed in "Member Server Recovery Methods" earlier in this chapter.

Move or Copy the Exchange Database and Log Files (Optional)
This procedure applies to the following recovery methods: • Restoring an Exchange member server. • Rebuilding an Exchange member server. • Using an Exchange standby recovery server. If you can still access the hard disks of the damaged server, and if you have sufficient time, move or copy the Exchange database and transaction log files from that server to a folder on a network share or to a removable storage device. Even if the files are damaged, archive these files as a safety precaution. If the restore process is unsuccessful, you can revert to the original versions, which might be repairable. Moving the files to a folder on the same logical drive is much faster than using the copy command. If you plan to put the damaged database in a location on the same logical drive, use move instead of copy.

To move or copy the Exchange database and log files
1. Determine where on the server the database and log files resided before the disaster. For more information about how to locate these files, see "Determining the Database and Log File Locations of the Files You Are Restoring (Optional)" earlier in this chapter.

Chapter 3: Restoring Exchange Server 2003 125

2.

Move or copy these files to another location. For more information about how to move or copy database files, see "Moving or Copying the Existing Versions of the Database Files That You Are Restoring (Optional)" earlier in this chapter.

Repair the Damaged Member Server (Optional)
This procedure applies to the following recovery methods: • Restoring an Exchange member server. • Rebuilding an Exchange member server. • Using an Exchange standby recovery server. Before trying to recover a member server, consider repairing it instead. You can try to repair your operating system, your Exchange installation, and your Exchange databases.

To repair your member server
1. Search the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=18175) for a solution to the problem you are experiencing. Make sure to check the application logs in Event Viewer for any errors that might provide clues as to the cause of the problem. Repair your Windows Server 2003 operating system. For more information about how to repair your operating system, see "Repairing Windows Server 2003" earlier in this chapter. Repair your Exchange installation. For more information about how to repair your Exchange installation, see "Repairing Exchange Server 2003" earlier in this chapter. Repair your Exchange databases. Do this only as a last resort. Attempting to repair a damaged database can cause data loss. For more information about how to repair Exchange databases, see "Repairing Exchange Databases" earlier in this chapter.

2. 3. 4.

Replace Any Damaged Hardware
This procedure applies to the following recovery methods: • Restoring an Exchange member server. • Rebuilding an Exchange member server. Replace damaged hardware. If you can, make sure that all the replacement hardware in the server that you are rebuilding is the same as hardware that existed in the server that experienced the disaster.

Restore the Full Computer Backup Set
This procedure applies to the following recovery method: • Restoring an Exchange member server. Restore the full computer backup set that was performed on the damaged server to the server that you are restoring. To restore these backups, you must be able to start your Windows Server 2003 operating system on the server to which you are restoring your full computer backup set. Use one of the following methods to restore your full computer backup set: • Use the backup utility (Backup) in Windows Server 2003 to restore your full computer backup set. For more information about how to restore a full computer backup set, see "Restoring a Full Computer Backup Set by Using Backup" earlier in this chapter. Use a Windows disk image to restore your full computer backup set. If you have a Windows disk image of the server that experienced the disaster, restore the disk image of your Windows Server 2003 operating system, and then start the operating system. For more information about using disk images as part of your disaster recovery strategy, see the Exchange Server 2003 Disaster Recovery Planning Guide (http://go.microsoft.com/fwlink/?LinkId=21277).

126 Exchange Server 2003 Disaster Recovery Operations Guide

Restore the Exchange Database from Backup Media if Necessary
This procedure applies to the following recovery methods: • Restoring an Exchange member server. • Rebuilding an Exchange member server. • Using an Exchange standby recovery server. If the drives that contain the Exchange database files and log files were also lost in the disaster, restore the Exchange database backups that were performed on the damaged server to the server that you are restoring. For information about how to restore Exchange databases, see "Recovering an Exchange Database" earlier in this chapter. Important
If you were able to move or copy the log files from the damaged server as explained in "Move or Copy the Exchange Database and Log Files (Optional)" earlier in this chapter, and these files are not stored on a Storage Area Network (SAN), copy these files to the correct location on the recovery server. If you do not copy the most recent log files to the correct locations on the recovery server, changes that were made to Exchange databases up to the time the disaster occurred are lost.

Re-Create Your Full-Text Indexes
This procedure applies to the following recovery methods: • Restoring an Exchange member server. • Rebuilding an Exchange member server. • Using an Exchange standby recovery server. If the server that experienced the disaster included any Exchange full-text indexes, you might have to re-create the full-text indexes on the server that you want to restore. For information about how to re-create full-text indexing, see "Repairing Full-Text Indexing" earlier in this chapter.

Try to Repair the Server Again if the Restore Fails
This procedure applies to the following recovery methods: • Restoring an Exchange member server. • Rebuilding an Exchange member server. If the Exchange databases on the restored server cannot mount, try to repair the server again. To repair the server again, use the repair techniques in "Repair the Damaged Member Server (Optional)" earlier in this chapter.

Install Windows Server 2003
This procedure applies to the following recovery method: • Rebuilding an Exchange member server. Install Windows Server 2003 on the server that you are rebuilding.

restore that image. These updates include updates to your Windows Server 2003 operating system. Exchange updates. "Restore the Windows Backup Set" in the Rebuilding Checklist in "Rebuilding an Exchange Member Server" earlier in this chapter. • Using an Exchange standby recovery server. Reinstall any software applications or updates that were installed after you created your backup set. • Restore the Windows Backup Set This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. • Using an Exchange standby recovery server. • Restoring an Exchange member server. Restoring the Windows backup set restores the Windows Server 2003 system files (including the registry database and IIS metabase files). For more information about how to restore the System State data. During Windows Server 2003 Setup. .Chapter 3: Restoring Exchange Server 2003 127 To install Windows Server 2003 • Install Windows Server 2003 on the server that you are rebuilding. • Using an Exchange standby recovery server. you cannot correctly run the Setup program in Disaster Recovery mode. If you do not perform this step. Include any required service packs or updates. Note Install the applications to the same locations and with the same configurations as the applications that were installed on the damaged server. Install Any Other Applications That Were Installed on the Damaged Server (Except Exchange) This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. and then start the operating system. – or – If you have a Windows Server 2003 disk image of the damaged server. install the operating system with the NNTP and SMTP components. and allow Setup to create a random computer name (NetBIOS) instead of manually specifying a name. This process also provides the server you are rebuilding with its original NetBIOS name. Restore the Windows backup set that was performed on the damaged server to the server you are rebuilding. install the computer into a temporary workgroup instead of a domain. see "Restoring Windows Backup Sets" earlier in this chapter. and returns it to the correct domain. or any other software updates or patches. skip the step. Install Service Packs and Software Updates This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. Install any other applications (other than Exchange) that run on the server. If the disk image included every Windows Server 2003 service pack and software update that was on the damaged server.

Click Start. click Run. On the Welcome page. You can use Exchange System Manager on another Exchange server in the same organization to determine what paths were used for storage group files and database files on the server being recovered.exe /disasterrecovery. make sure that Disaster Recovery is selected for all components that were originally installed (Figure 3. On the server you are rebuilding. 3. always use the /disasterrecovery switch. the Setup program correctly selects this information if you restored a Windows backup set first. 2. When you run Exchange in Disaster Recovery mode. you must manually select them. and so on. Important When recovering an Exchange server. The configuration information that is reclaimed includes the Exchange storage group names.41). Setup runs in Reinstall mode and automatically mounts the mailbox stores and public folder stores after the Setup process is completed. Install Exchange to the same drive and directory as it was installed on the damaged server. On the Components Selection page.128 Exchange Server 2003 Disaster Recovery Operations Guide Restore Any Additional Non-Exchange Data from Backup This procedure applies to the following recovery method: • Rebuilding an Exchange member server. and then type <drive>:\SETUP\I386\Setup. Run Exchange Setup in Disaster Recovery Mode This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. This process also uses the configuration information that is stored on the Exchange Server object in Active Directory to reclaim the configuration of the original server. • Using an Exchange standby recovery server. If you run the Setup program without using the /disasterrecovery switch. restore any additional dynamic data backups that were performed on the damaged server. public folder store names. you can cause problems that include the potential loss of data. 4. On the server you are rebuilding. . This process installs Exchange applications and any required Exchange files to the server that you are rebuilding. To run Exchange in Disaster Recovery mode 1. virtual server configuration settings. mailbox store names. under Action. make sure that all the drive letters on which databases and log files were kept are available. where <drive> is the CD-ROM drive. If you mount mailbox stores and public folder stores before you restore your Exchange databases. run Exchange Setup in disaster recovery mode. If any component that was originally installed does not have Disaster Recovery selected. click Next. Insert the Microsoft Exchange CD. Also. make sure that all the components that existed on the damaged server are selected. You also must know which administrative group the server was originally a part of. By default.

Install Exchange Service Packs in Disaster Recovery Mode This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. To install a service pack in disaster recovery mode • At a command prompt on the computer that you are updating type [path] update. click Next to reinstall Exchange in Disaster Recovery mode. Install Exchange Software Updates This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. Make sure to install the service pack in disaster recovery mode.exe /disasterrecovery where [path] is the location of the service pack you are installing. • Using an Exchange standby recovery server. . Running Exchange setup in disaster recovery mode On the Components Summary page. Install the Exchange service pack that was running on the damaged server to the new server. using the /disasterrecovery switch. Installing Exchange service packs in Disaster Recovery mode prevents the Exchange databases from being mounted at the end of the service pack installation process. you can continue directly to restoring the Exchange databases from a backup. Therefore.41 5.Chapter 3: Restoring Exchange Server 2003 129 Figure 3. Install any Exchange software updates that were running on the damaged server to the new server. • Using an Exchange standby recovery server.

If the damaged server was running the MSExchangeSRS service. For example. Replace the hard disks in the standby recovery server with the hard drives from the damaged server. Note In a SAN environment. if the Microsoft Search registry keys on the server you are rebuilding are different from the keys that existed on the server at the time that the full-text index was built. Move the Physical Hard Drives from the Damaged Server to the Standby Server This procedure applies to the following recovery method: • Using an Exchange standby recovery server. If the physical hard disks of the damaged production server appear to be undamaged. • Using an Exchange standby recovery server. For more information about how to restore the CA. Shut down the server that experienced the disaster. you must restore the MSExchangeSRS service database to the server you are rebuilding. Make sure to restore MSSearch before you try to build your full-text index. you can experience problems with Microsoft Search (required for fulltext indexing).130 Exchange Server 2003 Disaster Recovery Operations Guide Restore MSSearch This procedure applies to the following recovery method: • Rebuilding an Exchange member server. see "Restoring the Certification Authority (CA)" earlier in this chapter. For information about restoring Microsoft Search. • Using an Exchange standby recovery server. see "Restoring Microsoft Search" earlier in this chapter. the registry keys will point to locations that do not exist on the server you have rebuilt). Restore the Certification Authority This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. you must also restore the CA to the server you are rebuilding. Restore Site Replication Services This procedure applies to the following recovery methods: • Rebuilding an Exchange member server. The registry keys that specify the locations for the full-text indexes will be out of sync (specifically. Microsoft Search will not function correctly. 2. . this procedure is unnecessary. 3. To remove the hard disks from the damaged server and install them into the standby recovery server 1. When rebuilding an Exchange server. see "Restoring the Microsoft Exchange Site Replication Service (MSExchangeSRS)" earlier in this chapter. For more information about how to restore the MSExchangeSRS service database. you can remove the disks from the damaged server and install them into the standby recovery server. Remove the hard disks from the damaged production server. If the damaged server was running the certification authority (CA).

Start the standby recovery server and run Chkdsk on all disk partitions to ensure that there are no problems with the file system. • Installed the computer into a temporary workgroup instead of a domain during Setup. reinstall the standby recovery server's original hard disks.Chapter 3: Restoring Exchange Server 2003 131 4. To ensure that your standby recovery server was correctly prepared. • Specified that the Setup program create a random computer (NetBIOS) name instead of manually specifying the name of the damaged server. Windows Server 2003 was installed with the following specifications: • Installed the optional NNTP and SMTP components of Windows Server 2003. verify that the following procedures were performed: • • Hardware was installed that is the same as the original hardware on the damaged server. For information about how to run Chkdsk. . and then start that computer. see "Running the Windows Chkdsk Utility" earlier in this chapter. Connect the Standby Server to the Network This procedure applies to the following recovery method: • Using an Exchange standby recovery server. Note If you verify that the hard disks from the damaged server are not functioning correctly in the standby recovery server. Connect the standby recovery server to the network.

Appendixes .

microsoft.com/fwlink/?LinkId=3052&kbid=822453) • 298901 "Restoring a Database in a Storage Group Without Replaying Subsequent Log Files" (http://go.microsoft.microsoft.com/fwlink/?LinkId=21769) • Exchange Server 2003 Deployment Guide (http://go.com/fwlink/?LinkId=23216) • Exchange Server 2003 Disaster Recovery Planning Guide (http://go.microsoft.microsoft.microsoft.com/fwlink/?LinkId=14898.A P P E N D I X Resources A Resources Cited in This Book Exchange Server 2003 Exchange Server 2003 Guides • Exchange Server 2003 Administration Guide (http://go. • 822453 "How to Rebuild a Site Replication Service in Exchange Server 2003 When You Do Not Have a Backup of the SRS Database" (http://go.microsoft.com/fwlink/?LinkId=24625) Microsoft Knowledge Base Articles The following Microsoft® Knowledge Base articles are available on the Web at http://go.com/fwlink/?LinkId=30251) • Exchange Server 2003 Glossary (http://go.microsoft.com/fwlink/?LinkId=21768) • Exchange Server 2003 Message Security Guide (http://go.microsoft.microsoft.com/fwlink/?LinkId=3052&kbid=298901) • 232938 "The 'Last Backup Set' Check Box and Hard Recovery in Exchange" (http://go.com/fwlink/?LinkId=3052&kbid=232938) .com/fwlink/?LinkId=21277) • Using Exchange Server 2003 Recovery Storage Groups (http://go.microsoft.com/fwlink/?LinkId=23233) • Exchange Server 2003 High Availability Guide (http://go.

com/fwlink/?LinkId=18350) • Exchange 2000 Server Database Recovery (http://go.com/fwlink/?LinkId=6277) Microsoft Knowledge Base Article • 182081 "Description of the Isinteg utility" (http://go.com/fwlink/?LinkId=3052&kbid=275676) Exchange Server 5.com/fwlink/?LinkId=14898.microsoft.microsoft.microsoft.microsoft.microsoft.microsoft.microsoft.com/fwlink/?LinkId=3052&kbid=812357) • 275676 "XADM: Troubleshooting a Remote Online Backup of Exchange 2000" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=182081) IIS 6.com/fwlink/?LinkId=3052&kbid=275876) • 812357 "XADM: Maintain Your Exchange Database After You Repair By Using the Eseutil /p Tool" (http://go.5 Disaster Recovery (http://go.com/fwlink/?LinkId=3052&kbid=182081) • 298901 "Restoring a Database in a Storage Group Without Replaying Subsequent Log Files" (http://go.microsoft.microsoft.microsoft.com/fwlink/?LinkId=6273) Microsoft Knowledge Base Articles The following Microsoft Knowledge Base articles are available on the Web at http://go.com/fwlink/?LinkId=28748) Windows Server 2003 .0 online product documentation (http://go.0 Online Product Documentation • "Backing Up and Restoring the Metabase" in the IIS 6.5 Technical Paper • Microsoft Exchange 5.com/fwlink/?LinkId=3052&kbid=298901) • 232938 "The 'Last Backup Set' Check Box and Hard Recovery in Exchange" (http://go.microsoft. • 182081 "Description of the Isinteg utility" (http://go.com/fwlink/?LinkId=3052&kbid=232938) • 298924 "XADM: Do Not Back Up or Scan Exchange 2000 Drive M" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=328835) • 275876 "XADM: How to Use NTBackup from a Non-Exchange 2000 Computer" (http://go.com/fwlink/?LinkId=3052&kbid=298924) • 296843 "XADM: Error -1216 Recovering an Exchange 2000 Database" (http://go.134 Exchange Server 2003 Disaster Recovery Operations Guide Exchange 2000 Server Technical Papers • Disaster Recovery for Microsoft Exchange 2000 Server (http://go.microsoft.microsoft.com/fwlink/?LinkId=3052&kbid=296843) • 328835 "XADM: How to Back Up and Restore Connectors on Exchange 2000" (http://go.

com/fwlink/?LinkId=3052&kbid=310747) • 286422 "How to Back Up and Restore a Windows Server 2003 Cluster" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=313272) . • 216993 "Backup of the Active Directory Has 60-Day Useful Life" (http://go.com/fwlink/?LinkId=28310) • "Disaster Recovery" (http://go.exe)" (http://go.com/fwlink/?LinkId=28314) Windows 2000 Server Technical Papers • Active Directory Disaster Recovery (http://go.microsoft.com/fwlink/?LinkId=14898.com/fwlink/?LinkId=28313) • "Using Run as" (http://go.microsoft.microsoft.com/fwlink/?LinkId=6270) Microsoft Knowledge Base Articles The following Microsoft Knowledge Base articles are available on the Web at http://go.com/fwlink/?LinkId=28311) • "Permissions and user rights required to back up and restore" (http://go.microsoft.Appendix A: Resources 135 Technical Papers • Windows Server 2003 PKI Operations Guide (http://go.com/fwlink/?LinkId=16303) Microsoft Knowledge Base Articles The following Microsoft Knowledge Base articles are available on the Web at http://go.microsoft.com/fwlink/?LinkId=3052&kbid=286422) • 325375 "HOW TO: Troubleshoot Startup Problems in Windows Server 2003" (http://go.com/fwlink/?LinkID=17807) • Technical Overview of Windows Server 2003 Clustering Services (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=325375) • 280425 "Recovering from an Event ID 1034 on a Server Cluster" (http://go.com/fwlink/?LinkId=14898 • 310747 "Description of Windows XP and Windows Server 2003 System File Checker (Sfc.microsoft.microsoft.microsoft.com/fwlink/?LinkId=25762) • "Backing up and restoring data" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=280425) Online Help • "Backing up and restoring a certification authority" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=216993) • 313272 "HOW TO: Back Up and Restore a Certificate Authority in Windows 2000" (http://go.microsoft.com/fwlink/?LinkId=28312) • "Removable Storage" (http://go.microsoft.microsoft.microsoft.microsoft.

microsoft. you may find the following resources useful in your implementation of Microsoft Exchange Server 2003.microsoft.microsoft.com/fwlink/?LinkID=18918) ISA Server 2000 Feature Pack 1 (http://go.com/fwlink/?LinkId=21766) What's New in Exchange Server 2003 (http://go.microsoft.com/fwlink/?LinkId=21277) Exchange Server 2003 Tools and Updates (http://go.com/fwlink/?LinkId=21574) ISA Server 2000 Service Pack 1 (http://go.microsoft.microsoft.microsoft.com/fwlink/?LinkId=21633) TechNet security Web site (http://go.microsoft.com/fwlink/?LinkId=25097) Microsoft Developer Network (MSDN®) (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=305145) 296788 "Offline Backup and Restoration Procedures for Exchange" (http://go.microsoft.136 Exchange Server 2003 Disaster Recovery Operations Guide • • 241594 "HOW TO: Perform an Authoritative Restore to a Domain Controller in Windows 2000" (http://go.microsoft. Web Sites • • • • • • • • Exchange Server 2003 Technical Library (http://go.com/fwlink/?LinkId=3052&kbid=296788) Planning an Exchange Server 2003 Messaging System (http://go.com/fwlink/?LinkId=21765) Exchange 2000 Server • • 305145 "HOW TO: Remove the IFS Mapping for Drive M in Exchange 2000 Server" (http://go.microsoft.com/fwlink/?LinkID=18919) Microsoft security Web site (http://go.com/fwlink/?LinkID=18917) ISA Server 2000 downloads Web site (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=280425) Additional Resources Besides the resources cited in this book.com/fwlink/?LinkId=3052&kbid=296788) .microsoft.com/fwlink/?LinkID=5936) Exchange Server 2003 • • • 296788 "Offline Backup and Restoration Procedures for Exchange" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=241594) 280425 "Recovering from an Event ID 1034 on a Server Cluster" (http://go.

microsoft.com/fwlink/?LinkId=6544 • Microsoft Windows 2000 Server Resource Kit (http://go.microsoft.microsoft.microsoft.com/fwlink/?LinkId=3052&kbid=275876) 275676 "XADM: Troubleshooting a Remote Online Backup of Exchange 2000" (http://go. .com/fwlink/?LinkId=3052&kbid=275676) Windows Server 2003 • • "Backing up and restoring data" (http://go.com/fwlink/?LinkId=3052&kbid=245762) Resource Kits • Microsoft Exchange 2000 Server Resource Kit (http://go.com/fwlink/?LinkId=6543) Note You can order a copy of Microsoft Exchange 2000 Server Resource Kit from Microsoft Press® at http://go.com/fwlink/?LinkId=28750) Windows 2000 Server • • 263532 "How to perform a disaster recovery restoration of Active Directory on a computer with a different hardware configuration" (http://go.microsoft.com/fwlink/?LinkId=6546.Appendix A: Resources 137 • • 275876 "XADM: How to Use NTBackup from a Non-Exchange 2000 Computer" (http://go.microsoft.microsoft.microsoft.com/fwlink/?LinkId=28749) "Windows 2003 Server Troubleshooting & Disaster Recovery" (http://go.com/fwlink/?LinkId=3052&kbid=263532) 245762 "Recovering from a Lost or Corrupted Quorum Log" (http://go.com/fwlink/?LinkId=6545) Note You can order a copy of Microsoft Windows 2000 Server Resource Kit from Microsoft Press at http://go.microsoft.microsoft.

microsoft. This appendix provides information about features. For more information about the accessibility features of the various Windows operating systems. you can download accessibility files from the following network services: • The Microsoft Accessibility Web site at http://go.com/fwlink/?LinkId=22008) for information available in the following languages: Chinese. Microsoft Exchange Server 2003. Japanese. The features can be installed during setup. and Spanish (Spain). and services that make the Microsoft Windows Server™ 2003 family. Accessibility in Microsoft Windows Many accessibility features have been built into the Windows operating system. products. The following topics are covered: • • • • • • Accessibility in Microsoft Windows Adjusting Microsoft products for people with accessibility needs Microsoft product documentation in alternative formats Microsoft services for people who are deaf or hard-of-hearing Specific information about Exchange 2003 and Outlook Web Access 2003 Other information resources for people with disabilities Note The information in this appendix applies only if you acquired Microsoft products in the United States. starting with the introduction of Windows 95.com/fwlink/?LinkId=21487. or who are deaf or hard-of-hearing. are blind or have low vision. . and Microsoft Office Outlook Web Access® 2003 more accessible for people with disabilities. French. See the International Microsoft Accessibility Site (http://go. English.microsoft. the Windows® 2000 Server family. Contact your subsidiary to find out whether the type of products and services described in this appendix are available in your area. Portuguese.microsoft.A P P E N D I X Accessibility for People with Disabilities B Microsoft is committed to making its products and services easy for everyone to use.com/fwlink/?LinkId=22010). If you acquired Windows outside the United States. your package contains a subsidiary information card listing Microsoft support services telephone numbers and addresses. go to the Microsoft Products Accessibility Web site (http://go. These features are useful for individuals who have difficulty typing or using a mouse. Italian. Accessibility Files to Download If you have a modem or another type of network connection. Spanish (Latin America).

or 14. Visit the Microsoft Accessibility Step by Step Tutorials Overview Web site (http://go. Accessibility options and features are useful for individuals who have difficulty typing or using a mouse. 9600.com/fwlink/?LinkId=14899) to find the latest step-by-step tutorials. contact your local Microsoft subsidiary for information.microsoft. For other accessibility articles. and then click the arrow. As an example. in softlib/MSLFILES. which you can reach by dialing (425) 936-6735 in the United States or (905) 507-3022 in Canada.microsoft. and settings to meet your accessibility needs. from the Microsoft Help and Support Web site. including the Windows operating system. Windows. Direct modem access to MSDL is available 24 hours a day. The search displays the Knowledge Base article. select the Search the Knowledge Base option. are blind or have low vision. . or a combination of both is presented in a side-by-side format to help you learn.400 baud data transmission with no parity. features. "Customizing Windows for Individuals with Disabilities. products available for the MS-DOS®. 8 data bits. MSDL does not support 28.com/fwlink/? LinkId=14901). and then click Go. type kbenable. Information related to the use of the mouse. 2400. Free Step-by-Step Tutorials Microsoft offers a series of step-by-step tutorials to help you learn how to adjust the accessibility options and settings on your computer. and in Search for. or who are deaf or hard-of-hearing.microsoft. Microsoft provides a searchable catalog of assistive technology products that run on the Windows operating systems at the Microsoft Overview of Assistive Technology page (http://go. Assistive Technology Products for Windows A wide variety of assistive technology products are available to make computers easier to use for people with disabilities.Appendix B: Accessibility for People with Disabilities 139 • The Microsoft Help and Support Web site at http://go. Microsoft Internet server at ftp://ftp. or that provide synthesized speech for people who are blind or have difficulty reading. select All Microsoft Products. or Integrated Digital Network (ISDN) connections. Microsoft Download Service (MSDL).com/fwlink/?LinkId=14898. and Windows NT operating systems are: • • Programs that describe information on the screen in Braille. Note MSDL supports 1200. Outside the United States and Canada. • • Adjusting Microsoft Products for People with Accessibility Needs Accessibility options and features are built into many Microsoft products. Hardware and software tools that modify the behavior of the mouse and keyboard. type 165486.8 Kbps. and 1 stop bit.com/." which includes links to documents about customizing various versions of Microsoft Windows. Select the Knowledge Base Article ID Number Search option. 365 days a year. The free tutorials provide detailed procedures on how to adjust options.microsoft. 56K. the keyboard.

Customer Service Contact the Microsoft Sales Information Center on a TTY/TTD by dialing (800) 892-5234 between 06:30 and 17:30 Pacific Time [UTC-8. RFB&D distributes these documents to registered. including Microsoft product documentation and books from Microsoft Press®. Your assistive technology vendor can also help you learn how to adjust your settings to optimize compatibility with your version of Windows or other Microsoft products.140 Exchange Server 2003 Disaster Recovery Operations Guide • • • Programs that enable people to type by using a mouse or their voice. you can obtain many Microsoft publications from Recording for the Blind & Dyslexic. including audiocassettes and CDs. (RFB&D). Monday through Friday. excluding holidays.com/fwlink/?LinkId=21573.com/fwlink/?LinkId=22007).000 titles. NJ 08540 Phone from within the United States: (866) 732-3585 Phone from outside the United States and Canada: (609) 452-0606 Fax: (609) 987-8116 Web: http://www.org/ Microsoft Services for People Who Are Deaf or Hard-of-Hearing If you are deaf or hard-of-hearing. . contact RFB&D at the following address or contact information: Recording for the Blind & Dyslexic 20 Roszel Road Princeton. Coordinated Universal Time (Greenwich Mean Time)]. Microsoft Documentation in Alternative Formats Documentation for many Microsoft products is available in several formats to make it more accessible. You can download many of the Microsoft books from the Accessible Documentation for Microsoft Products Web site (http://go. complete access to Microsoft product and customer services is available through a teletype/telecommunication device for the deaf (TTY/TDD) service. be sure to contact your assistive technology vendor to check compatibility with products on your computer before upgrading. such as single switch or puff-and-sip devices. Alternative input devices.rfbd. If you have difficulty reading or handling printed documentation.microsoft. Word or phrase prediction software that people can use to type more quickly and with fewer keystrokes. Exchange 2003 documents are available as Help on the CD included with the product and on the Exchange Web site at http://go. Upgrading an Assistive Technology Product If you use an assistive technology product. The RFB&D collection contains more than 90. eligible members of their distribution service in a variety of formats.microsoft. for people who cannot use a mouse or a keyboard. Inc. For more information.

In Canada. the Basic client renders in all browsers except Microsoft Internet Explorer 5. see the Microsoft Knowledge Base Article 296232.01 to 6. see the Exchange Server 2003 Administration Guide (http://go. terms. procured. excluding holidays. contact Microsoft Product Support Services on a TTY/TDD at (800) 892-5234 between 06:00 and 18:00 Pacific Time (UTC-8). To view the Exchange 2003 VPAT (Voluntary Product Accessibility Template). To do this.com/fwlink/?LinkId=21487) provides information for people with disabilities. However.microsoft.x with the option to choose the Basic client when logging on to Outlook Web Access. .com/fwlink/? LinkId=3052&kbid=296232). Exchange Server 2003 Section 508 of the Rehabilitation Act regulates how United States government agencies purchase electronic and information technology. Getting More Accessibility Information The Microsoft Accessibility Web site (http://go. Outlook Web Access For customers who require assistive technology devices to interact with software applications. "XCCC: Empty Inbox When Using Internet Explorer 5 and Later to Gain Access to OWA" (http://go. By default. Monday through Friday. which describes the accessibility features that address the Section 508 standards. For details on enabling forms-based authentication. excluding holidays. the administrator must use Exchange System Manager to enable forms-based authentication for Outlook Web Access. people in outreach organizations. educators. including employees and members of the public. maintained.microsoft. Section 508 states that any "electronic and information technology" developed.com/fwlink/?LinkId=14920). A free monthly electronic newsletter is available to help you keep up-to-date with accessibility topics about Microsoft products. go to http://go. unless an undue burden would be imposed on the agency. Administrators also have the option of setting the Basic client as the default client for all browsers. and conditions in place at the time the service is used.microsoft. Microsoft support services are subject to the prices.Appendix B: Accessibility for People with Disabilities 141 Technical Assistance For technical assistance in the United States. It requires procurement officials to purchase only electronic and information technologies that are accessible to people with disabilities. it is recommended that they use the Basic Outlook Web Access client. or used by federal agencies must be accessible to people with disabilities. dial (905) 568-9641 between 8:00 and 20:00 Eastern Time (UTC-5). and advocates. visit the Accessibility Update subscription page (http://go. For more information about this approach.microsoft. To subscribe. their friends and family members.microsoft.com/fwlink/?LinkId=21769).x. Monday through Friday.com/fwlink/? LinkId=22011.01 to 6. an Exchange administrator can provide users of Internet Explorer 5.

microsoft.microsoft.com.Does this book help you? Give us your feedback. On a scale of 1 (poor) to 5 (excellent). see the following Web sites: • • • Exchange Product Team technical articles and books http://go. how do you rate this book? Mail feedback to exchdocs@microsoft.com/fwlink/?LinkId=14927 .com/fwlink/?LinkId=21277 Exchange Tools and Updates http://go. For the latest information about Exchange.com/fwlink/?linkid=25097 Exchange Server Community http://go.microsoft.