70 284 MCSE Guide to Microsoft Exchange Server

70 -284 MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter 11 Backup and Recovery of Exchange Server 2003 70 -284 MCSE Guide to Microsoft Exchange 2003 Server

Objectives • • Mitigate the risk of Exchange Server 2003 disasters Plan for disaster recovery Back up Exchange Server 2003 Restore a failed Exchange 2003 server 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 2

Objectives (continued) • Restore a corrupted Exchange Server 2003 store • Restore an Exchange mailbox or message • Understand how to replace a clustered Exchange 2003 server that has failed 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 3

Backup and Recovery of Exchange Server 2003 • First step in disaster recovery is performing a backup • Restore needed information after the backup • Three learning objectives: – Proper backup of Exchange Server 2003 – Restore failed server, Information Store, deleted mailboxes or messages – Replace a clustered Exchange 2003 server that has failed 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 4

Preventing Disasters • Three types of computing disasters: – Hardware fails – Software becomes unstable – Data is corrupted • Three preventive measures: – Implement redundant hardware – Implement redundant services – Use clustering 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 5

Redundant Hardware • RAID: multiple disks forming one logical unit • RAID-1 uses two disks – Each disk is a copy (mirror) of the other – Server continues to operate with one failed disk • RAID-5 uses three or more disks – Information saved is spread evenly among disks – Parity information (checksum) stored on disks – Checksum allows system to tolerate single disk failure • Other redundant components – Power supplies and network cards 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 6

Redundant Services • Exchange Server relies on DNS and Active Directory – DNS is used to deliver mail – DNS finds domain controllers for authentication – Active Directory availability is needed to authenticate • Making DNS fault tolerant – Have at least two DNS servers on the network – Configure Exchange server to use both DNS servers • Ensuring Active Directory is fault tolerant – Have at least two domain controllers for each domain 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 7

Clustering • Clustering is a high-availability solution – Multiple servers collaborate to provide services – All clustered servers are connected to external storage • Two types of clustering: active/active, active/passive • Active/active clustering – Installed and running on two servers – Each server (node) responds to requests – One disk takes over in the event of a failure • Active/passive clustering – Installed on up to eight servers, runs on up to seven – Inactive server takes over duties of failed server 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 8

Planning for Disaster Recovery • Planning is essential to successful disaster recovery • Six tasks that are part of disaster recovery planning – – – Document existing Exchange server configuration Choose a logging method Separate log files and databases Have a consistent backup schedule Ensure enough free disk space Prepare detailed written instructions on recovery 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 9

Documentation • Document configuration to enable server replication • Ensure documentation remains timely, up to date • Seven elements to document: – Server operating system version and service packs – Server network configuration • Include IP address and DNS servers – – – Exchange Server 2003 service packs Name of the Exchange organization Name of administrative group in which server is located Names of storage groups on the server Names of logical databases in server storage groups 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 10

Logging • Log files track partially completed transactions – Set of log files is maintained for each storage group – Database changes are written to the log files before the update – Transactions are kept in log files until the backup is performed • Log files + last backup allow message recovery to point of failure • Circular logging removes data from the log file after it is committed to the database – Reduces disk space requirements – Drawback: system can only be restored to point of last backup 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 11

Log File Location • Impact of storing logs and database on same drive – If failure occurs, recoverable to most recent backup • Store log files on different drives from databases – Enables recovery to point just before failure • Scenario demonstrating benefit of separate storage: – Drive storing database fails – Recent copy of database restored to another drive – Transaction logs replayed for restoration to point before failure 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 12

Backup Scheduling • • • Consistent, frequent backup speeds up recovery Backups should be automated, not manual Administrators should log and monitor backups Backup logs should also be checked Test backups on a monthly basis 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 13

Available Disk Space • Required disk space for repairs on database – Free disk space equivalent to database – 10 percent extra for working space on drive • Required disk space for recovery storage group – Free disk space equivalent to storage group • Rule of thumb for meeting space requirements – Keep free disk space equivalent to largest storage group 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 14

Written Instructions • List of objects to be restored: – – Servers Storage groups Databases Mailboxes • Write down instructions for performing restoration • Written instructions save time during restoration • Test written instructions before they are used 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 15

Backing Up Exchange Server 2003 • Good backup is the basis of recovery • Five elements of backup: – – – How database backups differ from file backups Differences in backup software What needs to be backed up Offline backups Full-text indexes 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 16

Database Backups • Database backup differs from file system backup • Elements of file system backup: – Use archive attribute to track files – Perform different backup types • Full, differential, incremental • Elements of database backup: – Composed of a few files that constantly change – Log files must be taken into account – Terms full, differential, incremental still used 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 17

Full Backup • Full backup of Exchange: – Takes copy of database and transaction logs – Clears transaction logs off hard drive • Conserves disk space • Restore database and storage groups with full backup – No other backups required 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 18

Differential Backup • Differential backup of Exchange: – Does not take a copy of database files – Only takes a copy of transaction logs – Does not remove transaction logs from hard drive • Benefits of differential backup: – Smaller and faster than full backup – Perform backups with greater frequency (during day) • Differential backups conjoined to full backups • Restore Exchange with most recent differential and full backup 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 19

Incremental Backup • Incremental backup of Exchange: – Does not take a copy of database files – Only takes a copy of transaction logs – Removes transaction logs from hard drive • Benefits of incremental backup: – Smaller and faster than full backup – Perform backups with greater frequency (during day) • Incremental backups conjoined to full backups • Restore Exchange with full backup and all recent incremental backups 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 20

Backup Software • Updated version of NT Backup – – – Installed with Exchange Administrative Tools Backs up Exchange databases and transaction logs Uses Exchange backup API Allows on-line backups while Exchange is running Checks for database errors • Major benefit of using NT Backup is price (no cost) • Limitation of NT Backup: cannot perform backup across network 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 21

Backup Software (continued) • Options for backing up Exchange across network: – Attach backup device (tape drive) to Exchange server – One central backup and third-party software for backup across network – Simulate network backup by saving Exchange to file • Backup file can then be backed up across network 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 22

Backup Software (continued) • Brick-level backup and restore (third-party solution) – Backs up and restores individual messages – Does not replace need for storage group backups • Using Volume Shadow Copy for backup – Volume Shadow Copy takes snapshot of database – Backup is performed on snapshot 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 23

Activity 11 -1: Backing Up Exchange Server 2003 • Time Required: 10 to 20 minutes • Objective: Perform a full backup of an Exchange Server 2003 store • Description: Learn how to perform a full backup of an Exchange Server 2003 store, the First Storage Group. To ensure there is data to back up, you first create a new user, log on to OWA (Outlook Web Access) as that user, and then create a new message. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 24

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 25

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 26

What to Backup • Elements to backup for a successful recovery: – – – Operating system directories System state Exchange Server folders (except databases, log files) Exchange databases and log files Cluster quorum (if in a cluster) Cluster disk signatures (if in a cluster) • System state: data set distributed among components – Components vary with server configuration 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 27

Offline Backups • Offline backup: – Takes a copy of Exchange database and transaction logs – Does not remove transaction logs – Performs operations when Exchange services are stopped • Use offline backups in two circumstances: – Third-party does not support Exchange backup API – Database errors prevent online backup • Perform repairs with Eseutil command utility 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 28

Full-Text Indexes • Full-text indexes improve searches of Information Store • Not necessary to backup indexes (redundant data) • Not possible to restore full-text indexes • Recover full-text indexes by re-creating them 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 29

Activity 11 -2: Recovering from a Lost Full-Text Index • Time Required: 5 to 10 minutes • Objective: Re-create a full-text index • Description: Full-text indexes are not backed up as part of an Exchange backup because they easily can be re-created. In this activity, you learn how to re-create the full-text index created in Chapter 9. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 30

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 31

Restoring a Failed Exchange 2003 Server • Restore entire server after a catastrophic failure • Failure may be hardware or software related – Examples: disk or operating system failures • Server need not be restored with identical hardware – NT Backup understands which drivers to restore • Requirements for restoring a server – Same drive letters must exist – OS on replacement server patched to same level as original 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 32

Restoring a Failed Exchange 2003 Server (continued) • Six step recovery process: – Install same version of Windows on new hardware • Temporary server name differs from the failed server • Temporary server is not joined to the domain in Active Directory – – – Install Windows service packs to match failed server Restore last OS backup from old server Install Exchange Server 2003 in disaster recovery mode Install service packs for Exchange Server 2003 Restore latest version of database and log files 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 33

Activity 11 -3: Recovering from a Failed Server • Time Required: 10 to 20 minutes • Objective: Research the detailed steps for recovering from a failed Exchange 2003 server • Description: Go to the Microsoft Web site and download a book about Exchange Server 2003 disaster recovery. Read the section about recovering from a failed server. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 34

Restoring a Corrupted Exchange 2003 Store • Restoring inaccessible Exchange 2003 store: – Information Store service must be running – Store being restored must be dismounted – Current transaction logs are replayed after the databases are restored 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 35

Restoring a Corrupted Exchange 2003 Store (continued) • Six steps to recovery process: – Database files from backup are copied back to disk – Log files from backup are copied to a temporary directory – A restore. env file is created in the same temporary directory as log files – A hard recovery is performed – A soft recovery is performed – Temporary directory with transaction logs is removed 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 36

Restoring a Corrupted Exchange 2003 Store (continued) • Multiple stores can be restored before a hard recovery – Restore each store individually in a separate temporary directory – Last Restore Set checkbox must be unchecked – Run eseutil /cc command to trigger a hard recovery 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 37

Activity 11 -4: Restoring an Exchange Server 2003 Store • Time Required: 20 to 30 minutes • Objective: Restore an Exchange Server 2003 store from backup • Description: Restoring a corrupted store is often the fastest way to get it up and running again. In this activity, you restore the First Storage Group on your back-end server using the Backup utility and the backup file created in Activity 11 -1. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 38

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 39

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 40

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 41

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 42

Restoring an Exchange Mailbox or Message • Three reasons for recovering a mailbox or message: – Reviewing deleted messages as part of a legal action – Retrieving accidentally deleted messages – Allowing manager to review mail of terminated employee • Four methods to restore missing messages/mailboxes: – – Recover deleted items in Outlook or OWA Reattach a mailbox to a user Use an alternate recovery forest Use the recovery storage group 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 43

Recovering Deleted Items in Outlook or OWA • Stages of deletion: – Deleted message placed in Deleted Items folder – Message deleted from Deleted Items no longer visible • Messages may be restored using Recover Deleted Items Option • Length of time deleted items retained configured by administrator 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 44

Activity 11 -5: Modifying the Deleted Item Retention Time • Time Required: 5 to 10 minutes • Objective: Modify the deleted item retention time • Description: By default, deleted messages are recoverable for seven days. In this activity, you extend the deleted item retention time to 14 days and ensure that no items are purged until they have been backed up at least once. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 45

Activity 11 -6: Recovering Deleted Items in Outlook Web Access • Time Required: 10 to 20 minutes • Objective: Recover a deleted item in Outlook. Web Access • Description: Exchange Server 2003 allows deleted items to be recovered in Outlook. Web Access. In this activity, you delete a message in Outlook Web Access and then recover it. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 46

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 47

Reattaching Mailboxes • Deleting a user account is a serious mistake • Fixing erroneous deletion of a user account: – Restore user object in Active Directory – Re-create user account • Deleted mailboxes are retained for 30 days before being purged • Fixing erroneous deletion of mailbox: – Reattach deleted mailbox not purged to a new account • Use Exchange System Manager • Mailbox may be attached to a different account – Action often used to review employees mail 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 48

Activity 11 -7: Modifying the Deleted Mailbox Retention Time • Time Required: 5 to 10 minutes • Objective: Increase the mailbox retention period to reduce the risk of deleted mailboxes being purged before they can be reattached • Description: By default, deleted mailboxes are recoverable for 30 days. In this activity, you extend the deleted mailbox retention time to 60 days. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 49

Activity 11 -8: Reattaching a Deleted Mailbox • Time Required: 20 to 40 minutes • Objective: Reattach a deleted mailbox to a new user • Description: After a user is deleted, the mailbox is still recoverable. In this activity, you attach the mailbox of a deleted user to a new user. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 50

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 51

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 52

Using an Alternate Recovery Forest • Alternate recovery forest: – Single server (at minimum) – Contains copy of Exchange organization • Advantages of an alternate recovery forest: – Provides the ability to perform restores of public folders – Allows testing of backup integrity outside a production environment – Allows mailbox recovery (after retention period has expired) – Acts as a testing environment for service packs and third-party add-ons • Major disadvantages of alternate recovery forest: – Cost and hassle of maintaining separate hardware 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 53

Preparing the Recovery Server • Relation of recovery server to Exchange Server – Same organization name, administrative group name, storage group name, and database name • Importance of Legacy. Exchange. DN attribute: – Value in recovery server should match source server – Enables Information Store to be mounted • legacydn. exe utility changes value of Legacy. Exchange. DN on all necessary objects 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 54

Recovering a Mailbox from the Recovery Server • Actions following setup of recovery server: – Create store with same name as store to be restored – Restore source store from backup over the empty new store – Copy messages in mailboxes to. pst files • Detailed procedure for recovering messages: – – – Create a user object in Active Directory Connect the user object to a recovered mailbox Copy the mailbox to a. pst file (use Outlook or Exmerge) Log on to the original mailbox Copy messages from. pst file to original mailbox 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 55

Using the Storage Recovery Group • Recovery storage groups: – Allow Exchange store to be restored on existing server – Eliminate need to create an alternate recovery forest • Recovery storage group limits by Exchange edition: – Enterprise: four storage groups on single server – Standard: one storage group on single server 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 56

Using the Storage Recovery Group (continued) • Four steps for using storage recovery groups: – – Create a recovery storage group Add mailbox store to recovery storage group Restore mailbox store to recovery storage group Use exmerge. exe to extract mailboxes 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 57

Using the Storage Recovery Group (continued) • Main advantage of recovery storage groups is simplicity • Limitations of recovery storage groups: – – – Must be in same administrative group as backup server User account for mailbox must exist in Active Directory Mailbox must not have been purged from the store Public folders cannot be restored Need to use exmerge. exe with Exchange Server 2003 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 58

Activity 11 -9: Using the Recovery Storage Group • Time Required: 20 to 40 minutes • Objective: Use the recovery storage group to restore a mailbox • Description: Create a recovery storage group; restore the First Storage Group backup, created in Activity 11 -1, to the new recovery storage group; and then recover Demitri Santos’s messages to a. pst file using Ex. Merge. 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 59

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 60

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 61

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 62

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 63

70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 64

Restoring Clustered Exchange Servers • Restoring corrupted database in cluster – Follow the same procedure used with nonclustered server • Fixing failed server in a cluster – Storage groups and services start on another server • Fixing server failure due to hardware or OS problem – Remove failed server from cluster – Add new server to replace failed one 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 65

Summary • Prevent disasters using redundant hardware, redundant services, clustering • Plan properly for disaster recovery • Transaction logs are kept until full backup is performed • Circular logging deletes logs after data is committed • Full backup copies databases and transaction logs 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 66

Summary (continued) • Differential backup only copies transaction logs • Incremental backup copies logs and deletes logs from disk • Updated NT Backup backs up Exchange store while services run • Third-party software performs brick-level and Volume Shadow Copy backups • Backups include OS directories, system state, folders, and stores 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 67

Summary (continued) • Offline backup is a copy of the Exchange databases taken when the services are stopped • Reinstall Windows and Exchange Server to restore failed server • Corrupted store may be restored with NT Backup • Four techniques for restoring messages and mailboxes • Clustered Exchange servers are restored by rebuilding them as a new cluster server 70 -284 MCSE Guide to Microsoft Exchange 2003 Server Administration 68