exchnage restore11.pdf

(http://www.msexchange.org)

Tweet 0ShareShare 1 5

Home Articles & Tutorials Exchange 2013 Articles Management & Administration

by Anderson Patricio [Published on 21 April 2015 / Last Updated on 21 April 2015]

Bringing the data from the dial tone database to the users and sharing some tips to help in the dial tone recovery process.

If you would like to read the other parts in this article series please go to:

Exchange Server 2013 Backup and Restore 101 - Recovering individual items (Part 1) (http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-server-2013-backup-and-restore-101-part1.html)


Exchange Server 2013 Backup and Restore 101 - Disabled mailboxes (Part 3) (http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-server-2013-backup-and-restore-101-part3.html)




Exchange Server 2013 Backup and Restore 101 (Part 7) (http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-server-2013-backup-and-restore-101-part7.html)




At this point, our clients are accessing the information before the crash and all new messages are arriving in their mailboxes, however we have a gap of messages that were delivered inthe dial tone database that are not accessible yet.

The first step is to clean the folder where we have the recovery database (RDB01), move the temporary database (TDB01 – Temp DB.edb) file to that location, and then rename it torDB01.edb, which is the name expected on the Recovery Database. The process to move and rename the file is shown in Figure 01.

Figure 01

Then, we need to mount the recovery database, the entire process including the validation in Figure 02.

Figure 02

We can list all the mailboxes that are available in the Recovery Database (which is our Temporary Database). In the output of the cmdlet we can see that the Number6 mailbox is there

Exchange Server 2013 Backup and Restore 101 (Part 11)

7LikeLike

Home Articles & Tutorials KBase Tips Products Reviews Free Tools Blogs Tech Topics Forums White Papers Contact Us

Exchange Server 2013 Backup and Restore 101 (... http://www.msexchange.org/articles-tutorials/exc...

1 of 5 12/09/2015 03:27 PM

and it has five items (Figure 03). The cmdlet below is important because we list the MailboxGuid attribute and we need that information to perform the restore of the information.

Get-MailboxStatistics –Database RDB01 | ft DisplayName,MailboxGuid,ItemCount -AutoSize

Figure 03

In order to restore the information from a single user, we can use the cmdlet shown below (Figure 04). The New-MailboxRestoreRequest requires 2 pieces of information to find out thesource (source database and the sourcestoremailbox which is the MailboxGUID) and just the target mailbox and that is it.

New-MailboxRestoreRequest –SourceStoreMailbox <MailboxGUID> -SourceDatabase RDB01 –TargetMailbox Number6

Figure 04

We can track the status of the process using Get-MailboxRestoreRequest cmdlet, and after it finishes, we can check the OWA (Figure 05) of the user and all messages will be available(before the crash and messages from the period of the dial tone database).

Figure 05

Now that the users have all their data back on their mailboxes and the service is completely restored, we can work on removing the databases that were used during the dial tonerecovery process. The first step in our scenario is to check which databases are mounted, and we can do that by running Get-MailboxDatabaseCopyStatus cmdlet (Figure 06).

Figure 06

In the last article, we mounted the restored database in the TDB01 Mailbox Database, and then we moved all data from the Recovery Database (RDB01) to the TDB01 and that becameour master copy with all old data, and the data from the dial tone which is receiving the new messages.

For all other databases, including the original database that had a problem (DB01) and the Recovery Database (RDB01), will need to be removed from Exchange Server and mostimportant, remove the files from the file system to save disk space.

Removing unnecessary databases…


2 of 5 12/09/2015 03:27 PM

In order to remove a database, first we need to dismount it using the Dismount-Database <DBName> cmdlet, as shown in Figure 07. A confirmation will be required.

Figure 07

Before removing the Mailbox Database, we need to know where the Database and its log files are located. Using the cmdlet below (Figure 08), a list of all Mailbox Databases, theirnames, Database file location and log files will be listed.

Get-MailboxDatabase | Select Name,EDB*,LogFolder* | fl

Note:In this example we are listing all Mailbox Databases of our organization (because we have a single server). If your environment has more than one server, then you should use –Server<ServerName> in the Get-MailboxDatabase cmdlet to narrow down your results.

Figure 08

The next step is to remove the Mailbox Database from Exchange, and afterwards the removal of the files on the file system. A list of three cmdlets which list the mailbox databases andtheir location, and to remove the database and log folder is listed below, we can also see those three cmdlets in action on Figure 09.

Remove-MailboxDatabase <DBName>

Remove-Item <EDB-Location-with-file-name.edb>

Remove-Item <Log Location-Path> -Force -Recurse

Figure 09

The last step is to remove the folder that was used during the swap of the Mailbox Databases. There is also the old folder that was used to move the log files in the remaining databases.

Advertisement

First, there is no such thing as a complete guide for disaster recovery that will have all steps to restore your environment, and the reason is simple, each environment is unique in acertain way. The best thing that an administrator can do is to make sure that he is prepared and has enough practice in a lab ot the process to restore.

Nowadays, it is easy to have a lab to test the procedures. If the company has virtualization, you can create your own Active Directory/Exchange Organization to test it without affectingproduction. If you do not have resources in house, then use Azure to spin your test environment.

There are several limitations on a Recovery Database, the most important is that we can have only one per server mounted on a server.

A good thing is that the Recovery Databases do not count towards the number of Mailboxes on a server, especially when the Standard edition is used since the limit is only five mounteddatabases at any given time.

Some hints when working with dial tone recovery…

Hint #01 – Exchange Recovery Databases limitation


3 of 5 12/09/2015 03:27 PM

Anderson Patricio is a consultant for Microsofttechnologies. He works with Exchange Server, ISASever and Active Directory deployments at a MicrosoftGold Partner in Toronto, Canada. In the Technet Brasilcommunity, he contributes news, articles andwebcasts.

The location used to store the temporary database at the beginning was the same that we used to restore the original database. Keep that in mind when starting the dial tone recoveryprocess, it is better to create the Temporary on the final location, which will contain enough space for the restored database.

Before starting the dial tone recovery process, it may be a best practice to document the distribution of the mailboxes and their mailbox databases. That is not a requirement, but nice tohave in cases where we have several databases being affected and we move all mailboxes to a single temporary database. Having this report handy makes it easy to find the users torestore the information afterwards. The following cmdlet can be used to generate this report (Figure 10).

Get-Mailbox | Select Name,DisplayName, Database

Figure 10

If you want to generate a csv report that you can use later in Excel where you can filter data, then we need to add | Export-CSV <file> -NoTypeInformation and the results will be similarto Figure 11.

Figure 11

In this article, we restored information from the Recovery Database to the production database that is the last step in the dial tone recovery process. After completing the restore of theservice, we validated the steps required to remove the databases and files no longer in use in the Exchange Server.

If you would like to read the other parts in this article series please go to:











Hint #02 – Location of the Temporary Databases

Hint #03 – Document the Mailbox and their Mailbox Databases

Conclusion

See Also

Exchange Server 2013 Backup and Restore 101 (Part 9)(http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-server-2013-backup-and-restore-101-part9.html)

Exchange Server 2013 Backup and Restore 101 (Part 10)(http://www.msexchange.org/articles-tutorials/exchange-

The Author — Anderson Patricio


4 of 5 12/09/2015 03:27 PM

TechGenix Ltd is an online mediacompany which sets the standardfor providing free high qualitytechnical content to ITprofessionals.(http://www.techgenix.com)

Windows Server 2012 / 2008 / 2003 &Windows 8 / 7 networking resource site(http://www.windowsnetworking.com/)

Network Security & Information Securityresource for IT administrators(http://www.windowsecurity.com/)

The essential Virtualization resource site foradministrators(http://www.virtualizationadmin.com/)

The No.1 Forefront TMG / UAG and ISAServer resource site(http://www.isaserver.org/)

Cloud Computing Resource Site for IT Pros(http://www.cloudcomputingadmin.com/)

An independent Amazon Web Servicesresource site(http://www.insideaws.com/)

World's largest weekly newsletter onWindows Server and cloud technologies(http://www.wservernews.com/)

About Us Advertise With Us Contact Us

MSExchange.org is in no way affiliated with Microsoft Corp.Copyright © 2015, TechGenix Ltd (http://www.techgenix.com/). All rights reserved. Please read our Privacy Policy (/pages/privacy.html) and Terms & Conditions (/pages/terms.html).

server-2013/management-administration/exchange-server-2013-backup-and-restore-101-part10.html)




Exchange Server 2013 Backup and Restore 101 - Disabledmailboxes (Part 5) (http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-server-2013-backup-and-restore-101-part5.html)



RestoreADmin (http://www.msexchange.org/software/Backup-Recovery/RestoreADmin-32386.html)

Exchange Server 2013 Backup and Restore 101 -Recovering individual items (Part 2)(http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/exchange-server-2013-backup-and-restore-101-part2.html)

Latest Contributions

Integrating Exchange Server 2013 and Skype for BusinessServer 2015 (Part 6) (/articles-tutorials/exchange-server-2013/migration-deployment/integrating-exchange-server-2013-and-skype-business-server-2015-part6.html)on 8 Dec. 2015 (2015-12-08 12:22)

Integrating Exchange Server 2013 and Skype for BusinessServer 2015 (Part 5) (/articles-tutorials/exchange-server-2013/migration-deployment/integrating-exchange-server-2013-and-skype-business-server-2015-part5.html)on 26 Nov. 2015 (2015-11-26 12:00)

Deploying Exchange Server 2016 (Part 2) (/articles-tutorials/exchange-2016-articles/migration-deployment/deploying-exchange-server-2016-part2.html)on 17 Nov. 2015 (2015-11-17 11:30)

Deploying Exchange Server 2016 (Part 1) (/articles-tutorials/exchange-2016-articles/migration-deployment/deploying-exchange-server-2016-part1.html)on 3 Nov. 2015 (2015-11-03 10:59)

Integrating Exchange Server 2013 and Skype for BusinessServer 2015 (Part 4) (/articles-tutorials/exchange-server-2013/migration-deployment/integrating-exchange-server-2013-and-skype-business-server-2015-part4.html)on 22 Oct. 2015 (2015-10-22 11:58)


5 of 5 12/09/2015 03:27 PM

exchnage restore11.pdf

Documents