1. Planning and Implementing Disaster Recovery
20341B
7: Planning and Implementing Disaster Recovery
Presentation: 75 minutes
Lab: 75 minutes
After completing this module, the students will be able to:
Plan for disaster mitigation.
Plan and implement backup for Microsoft® Exchange Server 2013.
Plan and implement Exchange Server 2013 recovery.
Required materials
To teach this module, you need the Microsoft® Office PowerPoint® file 20341B_07.pptx.
Important: We recommend that you use Office PowerPoint® 2007 or a newer version to display the slides for this course. If you use PowerPoint Viewer or an earlier version of Office PowerPoint, all of the features of the slides might not display correctly.
Preparation tasks
To prepare for this module:
Read all of the materials for this module.
Practice performing the demonstrations.
Practice performing the labs.
Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on-the-job performance.
As you prepare for this class, it is imperative that you complete the labs yourself so that you understand how they work and the concepts that are covered in each. This will allow you to provide meaningful hints to students who may experience difficulties in a lab. It also will help guide your lecture to ensure that you cover the concepts that the labs cover.
Module 7
Planning and Implementing Disaster Recovery

2. Planning and Implementing Exchange Server 2013 Recovery
20341B
Module Overview
7: Planning and Implementing Disaster Recovery
Planning and Implementing Exchange Server Recovery

3. Lesson 1: Planning for Disaster Mitigation
20341B
Lesson 1: Planning for Disaster Mitigation
7: Planning and Implementing Disaster Recovery
Scenarios Requiring Backup and Restore

4. Identifying Data-Loss Scenarios
20341B
Identifying Data-Loss Scenarios
7: Planning and Implementing Disaster Recovery
Data loss scenarios
Lost item
Lost mailbox
Lost database
Lost server

5. Data-Loss Mitigation Features
20341B
Data-Loss Mitigation Features
7: Planning and Implementing Disaster Recovery
Mitigating data loss avoids the need to recover from backup
Data-loss mitigation features include:
Deleted item recovery
Single item recovery
In-place hold
Deleted mailbox retention
DAGs
Shadow redundancy

6. Planning a Disaster Mitigation Strategy
20341B
Planning a Disaster Mitigation Strategy
7: Planning and Implementing Disaster Recovery
Considerations include:
Increase Deleted Item Retention increases database size
Increase Deleted Mailbox Retention increases database size
DAGs may prevent service outages due to lost databases and lost servers
Replay lag time may prevent data corruption on a passive copy in a DAG

7. What do you achieve if you are using fault- tolerant hardware?
20341B
Discussion: What Is the Relationship Between Disaster Recovery and High Availability?
7: Planning and Implementing Disaster Recovery
What high-availability features can be used as a first line against a disaster?
What do you achieve if you are using fault- tolerant hardware?
Use the following discussion questions to help the students understand the relationship between disaster recovery and high availability.
Question
What high-availability features can you use as a first line against a disaster?
Answer
The first line against disaster is to use DAGs with multiple database copies distributed over multiple data centers.
Would your organization accept using only high availability features and not use backups?
Answer may vary from customer to customer.

8. Exchange Server Native Data Protection
20341B
Exchange Server Native Data Protection
7: Planning and Implementing Disaster Recovery
Exchange Native Data Protection includes the following Exchange Server 2013 features:
High availability that minimizes downtime and data loss
Single-item recovery and In-Place hold policies for recovering deleted messages
Point-in-time database recovery with lagged copies of mailbox databases
Archive mailboxes, retention and archive policies, In-place eDiscovery for managing large mailboxes
Exchange Native Data Protection reduces costs by:
Simplifying management
Requiring no backup software or hardware
Requiring no RAID

9. 20341B
Discussion: When Is Exchange Server Native Data Protection Appropriate?
7: Planning and Implementing Disaster Recovery
Does your organization work with Exchange Server 2010 or and that uses only Exchange Server Native Data Protection? Why?
Does your organization use traditional backups? Why?
Does your organization use combination of Exchange Server Native Data Protection and traditional backups? Why?
Which features of Exchange Server Native Data Protection do you use in your organization?
In which situation is it appropriate to use only Exchange Server Native Data Protection?
The answers may vary for the first four questions, depending on the individual organization’s requirements.
For the last question, explain to the students that recovery point objective (RPO) and recovery time objective (RTO) goals are clearly defined, and that the combination of Exchange Native Data Protection features enables you to meet specific goals.

10. What Are the Timelines for Disaster Recovery?
20341B
What Are the Timelines for Disaster Recovery?
7: Planning and Implementing Disaster Recovery
The RTO determines:
How quickly the service is restored
The RPO determines:
From what point in time is the disaster recovery performed
Based on the RTO and RPO, you might choose to:
Keep databases small to shorten restore times
Keep transaction logs on separate drives to ensure they can be replayed after a restore
Backup up every few hours to ensure minimal data is lost

11. Scenarios Requiring Backup and Restore
7: Planning and Implementing Disaster Recovery
Scenarios:
Recover a message when single-item recovery is not enabled
Recover a mailbox after the mailbox retention period has passed
Recover a public folder item after the item retention has passed
Recover from a failed database when a DAG is not in use
Recover from a failed server when a DAG is not in use
Backups may be used to meet compliance requirements

12. Lesson 2: Planning and Implementing Exchange Server 2013 Backup
7: Planning and Implementing Disaster Recovery
Demonstration: How to Back Up Exchange Server 2013
Question
Do you plan to use Windows Server Backup as your primary Exchange Server backup solution?
Answer
The answer depends on the requirements of your organization, and whether it is sufficient to use Windows Server Backup as the backup solution.

13. Backup Requirements for Exchange 2013
7: Planning and Implementing Disaster Recovery
Exchange Server Role
Backed-Up Data
All roles
System State of server and Active Directory database on domain controllers
Mailbox server
Databases and transaction logs
Message tracking logs
Unified Messaging custom audio prompts
Client Access server
Server certificates used for SSL
Specific Internet IIS configuration

14. Choosing Exchange Server Backup Software
7: Planning and Implementing Disaster Recovery
Windows Server Backup:
Runs locally on the computer running Exchange Server
Cannot back up to tape
Restore only full databases
Cannot backup passive DAG copies
DPM:
Uses agents on the computer running Exchange Server
Typically backs up to disk and then archives to tape
Can restore databases or mailboxes
Can back up passive DAG copies
Non-Microsoft backup software may be able to:
The backup software must support VSS
Restore individual items
Perform brick-level backups
Brick-level has to open and close each mail item individually. This overhead can be enormous, multiplying the backup time many times over. In addition, restoring from a brick-level backup is slow.

15. Choosing Exchange Server Backup Media
7: Planning and Implementing Disaster Recovery
Media
Description
Tape
Is physically easy to transport and very durable
Disk
Increases backup performance
SAN-based
Backs up the traffic of the main network and keeps it on the SAN

16. How Does a VSS Backup Work?
7: Planning and Implementing Disaster Recovery
Exchange 2013 and VSS backup
The VSS writer inside Microsoft Exchange Information Store is moved to the Microsoft Exchange Replication service
Referred now as the Microsoft Exchange Writer
Used by Exchange-aware VSS-based applications to backup and restore active and passive database copies
For backup and restore, the Microsoft Exchange Information Store and the Microsoft Exchange Replication service are required and need to be running

17. Demonstration: How to Back Up Exchange Server 2013
7: Planning and Implementing Disaster Recovery
In this demonstration, you will see how to:
Install the Windows Server Backup program
Use Windows Server Backup to back up Exchange 2013
When starting the backup, it makes sense to take a short break, because the backup takes approximately 20 minutes.
When you have completed the demonstration, leave the virtual machines running.
Preparation Steps
Before performing the steps, you must have the 20341B-LON-DC1, 20341B-LON-MBX1, and 20341B- LON-CAS1 virtual machines running for this demonstration. Start each machine and sign in to it before starting the next virtual machine. Sign into all virtual machines using the Adatum\Administrator account with the password Pa$$w0rd.
Important: Ensure that you start your virtual machines at least ten minutes prior to conducting the demonstration.
Demonstration Steps
On LON-MBX1, on the Start screen, click Server Manager.
In the Dashboard, click Add roles and features. The Add Roles and Features Wizard opens.
On the Before you begin page, click Next.
On the Installation Type page, select Role-based or feature-based installation, and click Next.
On the Server Selection page, select Select a server from the server pool, click LON-MBX1.Adatum.com in the Server Pool and click Next.
On the Server Roles page, click Next.
On the Features page, scroll down in the Features list, select Windows Server Backup, and click Next.
On the Confirmation page, do not select the Restart the destination server automatically if required option, and then click Install.
On the Results page, click Close.
On LON-CAS1, click the Desktop tile.
(More notes on the next slide)

18. 7: Planning and Implementing Disaster Recovery
20341B
7: Planning and Implementing Disaster Recovery
From the task bar, click File Explorer, and then create a folder named Backup on drive C:\.
Right-click the Backup folder, select Share with, and select Specific people.
Check that the Administrator account has Read/Write permissions, and click Share. Click Done.
Close File Explorer.
On LON-MBX1, click to the Start screen, and then click Administrative Tools.
Scroll down the tools list and double-click Windows Server Backup.
In the left navigation pane, select Local Backup.
In the Actions pane on the right side, click Backup Once.
In the Backup Once Wizard on the Backup Options page, select Different options, and click Next.
On the Select Backup Configuration page, select Full server (recommended), and click Next.
On the Specify Destination Type page, select Remote shared folder, and click Next.
On the Specify Remote Folder page, under Location type \\LON-CAS1\Backup, under Access control, select Do not inherit, and click Next.
In the Windows Security popup window, enter Administrator as the name and Pa$$w0rd as the password, and click OK.
On the Confirmation page, click Backup. Wait for the backup to finish.
On the Backup Progress page, click Close.
Close Windows Server Backup.
From Administrative Tools, double-click Event Viewer.
In Event Viewer, expand Windows Logs, and then click Application.
In Event Viewer, on the Application log, locate the event items labeled Source MSExchangeRepl with EventID and 2021.

19. Lesson 3: Planning and Implementing Exchange Server 2013 Recovery
20341B
Lesson 3: Planning and Implementing Exchange Server 2013 Recovery
7: Planning and Implementing Disaster Recovery
Process for Implementing Dial-Tone Recovery

20. Options for Recovering Exchange Server Functionality
20341B
Options for Recovering Exchange Server Functionality
7: Planning and Implementing Disaster Recovery
To replace lost server roles:
Build a new server with equivalent functionality
Add roles to an existing Exchange server
To restore a lost server:
Build a new server
Restore system state (optional)
Install Exchange Server with Recovery mode
Restore any necessary data

21. Options for Recovering Mailbox Data and Databases
7: Planning and Implementing Disaster Recovery
When a database or server fails, you have several options for recovery, including:
Options
Description
Database restore
Replaces an existing database
Recovery database
Restores database to an alternate location for data recovery
Database portability
Restores database without having to recover a specific server
Dial-tone recovery
Restores server functionality rapidly before historical mailbox contents are restored
DAG recovery
Mounts a database copy on a different Exchange server with the mailbox role installed

22. Planning the Recovery of Mailbox Data and Databases
7: Planning and Implementing Disaster Recovery
Considerations:
Use DAGs to avoid the need to recover
Separate transaction logs and databases
Use a dial-tone database to speed up recovery
Allocate disk space for a recovery database
Use mailbox databases with a smaller size

23. Planning the Recovery of Client Access Servers
20341B
Planning the Recovery of Client Access Servers
7: Planning and Implementing Disaster Recovery
The basic functions of Client Access servers can be recovered without backup up existing servers
Replace a failed Client Access server by:
Adding the server role to an existing Exchange server
Deploying a new server with the same server role
Replacing and deploying a new server can result in some applications requiring reconfiguration

24. Repairing Exchange Server Database Corruption
7: Planning and Implementing Disaster Recovery
The following cmdlet to repair database corruption is available:
New-MailboxRepairRequest
The cmdlet provides the following benefit over isinteg.exe:
No need to take the database offline
Runs on Windows PowerShell, enabling you to automate the process

25. Process for Recovering Data Using the Recovery Database
7: Planning and Implementing Disaster Recovery
A recovery database allows you to:
Restore the database from backup
Mount the database and extract data
Recovery database scenarios include:
Dial-tone recovery
Individual mailbox recovery
Specific item recovery

26. Demonstration: How to Recover Data by Using the Recovery Database
7: Planning and Implementing Disaster Recovery
In this demonstration, you will see how to:
Create the recovery database
Restore data to the recovery database
Create a new MailboxRestoreRequest
Revert all virtual machines on completion of this demonstration.
Preparation Steps
Before performing the steps, you must have the 20341B-LON-DC1, 20341B-LON-CAS1, and 20341B- LON-MBX1 virtual machines running for this demonstration. Sign in to all virtual machines as Adatum\Administrator with the password of Pa$$w0rd.
Demonstration Steps
On LON-MBX1, from Administrative Tools, double-click Windows Server Backup.
Note: The backup activity from the previous demonstration must be completed before you can proceed.
In Windows Server Backup, in the Actions pane, click Recover.
In the Recovery Wizard, on the Getting Started page, select This Server (LON-MBX1), and then click Next.
On the Select Backup Date page, click Next.
On the Select Recovery Type page, select Applications, and then click Next.
On the Select Application page, select Exchange, and then click Next.
On the Specify Recovery Options page, click Recover to another location. Click Browse, expand Computer, click Local Disk (C:), click Make New Folder, enter Restore, click OK, and then click Next.
On the Confirmation page, click Recover.
On the Recovery Progress page, wait until the recovery process is finished, then click Close. Close Windows Server Backup.
On LON-MBX1, click to the Start screen, and then click Exchange Management Shell.
In the Exchange Management Shell, execute the following command. This command identifies the Mailbox Database 1 GUID, as well as the locations for the database and transaction log files.
Get-MailboxDatabase –ID “Mailbox Database 1” | fl name, guid, edbfilepath, logfolderpath
(More notes on the next slide)

27. 7: Planning and Implementing Disaster Recovery
20341B
7: Planning and Implementing Disaster Recovery
In the Exchange Management Shell, type the following command to create the Recovery database, and press Enter. Verify that the GUID, database and transaction log names match the output from the previous command.
New-MailboxDatabase –Recovery –Name RecoveryDB –EdbFilePath “C:\Restore\ 3c32c739-a0ce-43bc-a299-2f56f2bcb20c\C_\Program Files\Microsoft\Exchange Server\ V15\Mailbox\Mailbox Database \Mailbox Database edb” – LogFolderPath “C:\Restore\GUID\C_\Program Files\Microsoft\Exchange Server\ V15\Mailbox\Mailbox Database ” –Server LON-MBX1
At the Exchange Management Shell prompt, type the following command, and then press Enter.
Restart-service msexchangeis
CD “C:\Restore\3c32c739-a0ce-43bc-a299-2f56f2bcb20c\C_\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database ”
Eseutil /r E00 /i /d
At the Exchange Management Shell prompt, type the following command, and press Enter.
Mount-Database RecoveryDB
Get-MailboxStatistics -Database RecoveryDB
This cmdlet displays all mailboxes within the recovery database.
New-MailboxRestoreRequest –SourceDatabase RecoveryDB –SourceStor box “Tony Smith” –TargetMailbox -SkipMerging StorageProviderForSource
(More notes on the next slide)

28. 7: Planning and Implementing Disaster Recovery
20341B
7: Planning and Implementing Disaster Recovery
At the Exchange Management Shell prompt, type the following command, and press Enter. This command reports on the status of the mailbox restore request.
Get-MailboxRestoreRequest

29. What Is Dial-Tone Recovery?
20341B
What Is Dial-Tone Recovery?
7: Planning and Implementing Disaster Recovery
Dial-tone recovery is the process of implementing access to services without restoring data to user mailbox
Dial-tone recovery benefits:
Enables users to send and receive as soon as possible after the loss of a database or server
Dial-tone database can be merged with the recovered database into a single up-to-date mailbox database

30. Process for Implementing Dial-Tone Recovery
20341B
Process for Implementing Dial-Tone Recovery
7: Planning and Implementing Disaster Recovery
Process for implementing dial-tone recovery:
Create the dial-tone database
If necessary, configure the mailboxes that were on the database to use the new dial-tone database
Restore the database and log files that you want to recover into the Recovery Database
Swap the dial-tone database with the database that you have recovered in the step before
Export and import the content from the dial-tone database into the recovered original database

31. Lab: Implementing Disaster Recovery for Exchange Server 2013
7: Planning and Implementing Disaster Recovery
Exercise 3: Exchange Server 2013 Disaster Recovery (Optional)
Exercise 1: Backing Up Exchange 2013
You create a backup of your Exchange Server 2013 mailbox database to ensure that you can restore it when necessary.
Exercise 2: Restoring Exchange Server 2013 Data
Some of your users complain that they are missing messages from their mailboxes. You now need to use the backup you created to recover their messages.
Exercise 3: Exchange Server 2013 Disaster Recovery (Optional)
After a hard-disk malfunction, the Exchange Server 2013 Client Access server LON-CAS2 is no longer operational. You have to restore the server with the /RecoverServer mode in the setup.
Instructor Note: As discussed in this module, there are several options available for recovering Exchange server functionality without performing a server restore. This makes it unlikely that students will have to recover a server as described in this lab very often. For this reason, ask students to perform this lab only if you have sufficient time and there is student interest. The virtual machine 20341B-LON-CAS2 must be off before you start the task. Students do not have to start this virtual machine during this lab.
Logon Information
Virtual Machines B-LON-DC1
20341B-LON-CAS1
20341B-LON-MBX1
User name Adatum\Administrator
Password Pa$$w0rd
Estimated Time: 75 minutes

32. 20341B
Lab Scenario
7: Planning and Implementing Disaster Recovery
You are a messaging administrator for A. Datum Corporation. Your organization has deployed Exchange Server You now want to ensure that all Exchange server-related data is backed up and that you can restore not only the full server or database, but also a mailbox or mailbox folder.

33. 20341B
Lab Review
7: Planning and Implementing Disaster Recovery
Which tool do you need to create a Recovery Database in Exchange Server 2013?
Question
Which feature do you need before you can run a local backup on an Exchange Server 2013 with the Mailbox role installed?
Answer
The backup feature needs to be installed on the Exchange Server 2013 server.
Which tool do you need to create a Recovery Database in Exchange Server 2013?
You need the Exchange Management Shell to create a Recovery Database in Exchange Server 2013.

34. Module Review and Takeaways
20341B
Module Review and Takeaways
7: Planning and Implementing Disaster Recovery
Best Practice
Review Questions
Question
What are possible data-loss scenarios?
Answer
Possible loss scenarios include lost items, lost mailboxes, lost databases, and lost servers.
What steps are required in the process of recovering data using the Recovery Database?
The steps to Restore the database that you want to recover are:
Create a new recovery database, and configure it to use the restored files before.
Put the database into a clean shutdown state.
Mount the recovery database, and merge or extract the data from the recovery database into their destination.
Which cmdlet do you use to repair database corruption?
To repair database corruption, use the New-MailboxRepairRequest cmdlet.
Which options do you have to recover mailbox data?
These options are available to recover mailbox data:
Recovery database
Database portability
Dial-tone recovery
DAG recovery
(More notes on the next slide)

35. 7: Planning and Implementing Disaster Recovery
20341B
7: Planning and Implementing Disaster Recovery
Tools
Exchange Administration Center
Exchange Management Shell
Windows Server Backup
Best Practice
Supplement or modify the following best practices for your own work situations:
Whenever possible, use a DAG to protect mailbox databases. DAG recovery is faster and easier than backup recovery.
When you lose a database, use a dial-tone database to quickly recover basic messaging functionality.
Use a recovery database to retrieve specific items from a backup.
Allocate disk space for a recovery database when you are designing server storage.
Use single-item recovery to prevent users from purging messages before the messages reach the item-retention limit.
Instructor Note: Ensure that you cover the common issues and the corresponding troubleshooting tips listed in this section. Encourage the students to share tips from their own work environments.