In the present scenario, technology is a boom for every individual. It plays a vital role in every sector. With this evolution in technology, disasters also come. Thereby, to ensure that the resources are accessible during planned and unplanned outages, there is a dire need of a Business Continuity and Disaster Recovery<\/span>. This recovery approach helps during the odd scenarios when things go wrong by restoring normal working conditions.<\/p>\n The effective Business Continuity and Disaster Recovery strategy keeps the data secure and recoverable. Further, it also ensures that the business applications, workloads, and services are continuously available. One of the best Enterprise Backup and Recovery System that contributes to the BCDR strategy is Data Protection Manager<\/span>. This System Center DPM facilitates both recovery and backup of Enterprise Data.<\/span><\/p>\n If we talk about Exchange Server, then, we can easily say it includes native data protection. Although this built-in native data protection is capable, yet there are certain scenarios where traditional backup still is needed. At this stage, DPM 2012 works. The reason being, it has been designed specifically for offering protection to the Exchange Server as well as other Microsoft workloads.<\/p>\n Further, Native Data Protection works perfectly in Disaster Recovery, accidentally deleted items recovery, Point-in-time database snapshots, and long-term data storage. However, when we talk about corruptions, application errors, malware incidents, and security issues, it is not a right option. At these events, DPM is a sure-shot solution.<\/p>\n The Data Protection Manager uses several technologies to deliver continuous Data Protection for Exchange Server 2013, 2010, 2007<\/span>. It supports the following:<\/p>\n \u2022 Both active & passive databases in DAG Data Protection Manager for Exchange 2013<\/strong> <\/span><\/p>\n In Exchange 2013, DPM ensures backup and recovery for following:<\/p>\n \u2022 Under a database availability group, backup of Exchange mailbox databases Why Choose Data Protection Manager to Backup Exchange?<\/strong><\/p>\n \u2022 During backup with DPM protection, there is no reliance on DAGs Prior discussing how you can Recover Exchange Data using Data Protection Manager, let us first have a quick overlook at the certain deployment prerequisites and things that are to be considered prior beginning the process.<\/p>\n Deployment Prerequisites to be Verified Prior to Deploying DPM to Protection Exchange 2013<\/strong><\/p>\n \u2022 Examine Release Notes<\/strong> and what is supported, to check the Exchange issues<\/strong> Things to Consider:<\/strong><\/p>\n 1. DPM Deployment<\/strong><\/p>\n The first and the foremost step is to ensure that DPM is installed as well as deployed correctly.<\/p>\n 2. Storage Setup<\/strong><\/p>\n The backup data can be stored effortlessly on the tape, disk, and in the cloud along with Azure. Thus, set up the data storage.<\/p>\n 3. DPM protection agent Set up<\/strong><\/p>\n It is necessary to ensure that the agents are installed on the Exchange Server.<\/p>\n How to Recover Exchange Data?<\/strong><\/p>\n Recovery of an Exchange Data<\/span> using DPM includes Single Mailbox Recovery, Exchange database recovery<\/span> and entire Exchange Server recovery.<\/span><\/p>\n \u2022 Single Mailbox Recovery<\/strong><\/span><\/p>\n The steps to recover single mailbox are as follows:<\/strong><\/p>\n i. Ensure you have an existing recovery mailbox database<\/strong> on the protected Exchange Server<\/strong>. In case, if you don\u2019t have, just create the one using cmdlet\u2014 New-MailboxDatabase<\/strong> \u2022 Exchange Database Recovery<\/strong><\/span><\/p>\n The steps to recover Exchange Database are as follows:<\/p>\n i. Go to the DPM Administrator Console,<\/strong> select the Recovery<\/strong> view \u2022 Exchange Server Recovery<\/strong><\/span><\/p>\n The steps to recover Exchange Server are as follows:<\/p>\n i. Under the DPM Administrator Console<\/strong>, select the Recovery<\/strong> view Alternative solution<\/strong><\/p>\n No doubt, DPM for recovery is the best choice, but it has certain limitations associated with it. Such as it uses VSS snapshot that supports only up to 64 snapshots, limited flexibility i.e. no incremental, differential, or full backup, and same retention policies for the data that resides on the same volume. Further, being a manual process, it also has risk associated with it. On the other hand, the Third-Party Recovery solutions are easy, fast, and efficient and are far from being risky as they are free from manual intervention.<\/p>\n To overcome Exchange 2013 Recovery, there are multitudes of Third-party solutions available in the market. Out of these extensive options, some have marked a strong position in the market, whereas some are left behind. If a suggestion is to be given, then Stellar Repair for Exchange can be considered to be the ideal solution. This software is experimented upon, verified, as well as agreed to by skilled Professionals, who have years of experience in this particular niche.<\/p>\n
\n\u2022 Continuous replication
\n\u2022 Standalone mailbox databases backup<\/p>\n
\n\u2022 Backup of Exchange Server roles
\n\u2022 Configures Volumes protection
\n\u2022 Provides the protection of all Exchange data and configuration settings<\/p>\n
\n\u2022 DPM practices a simple as well as centralized Data Recovery
\n\u2022 DPM ensures constant backup of Microsoft workloads
\n\u2022 Unlike Native Protection, DPM offers a longer backed up data retention period in comparison<\/p>\n
\n\u2022 Ensure you own same Ese.dll<\/strong> and Eseutil.exe<\/strong> versions on DPM Servers<\/strong> as well as the Exchange<\/strong>
\n\u2022 Ensure for Visual Studio 2012 Update<\/strong>; you own the latest Visual C++ Redistributable<\/strong>
\n\u2022 Ensure DPM protection agent<\/strong> installation on the node for Exchange 2013 Database Availability Group (DAG)<\/strong> node protection.
\n\u2022 Ensure each day at least one full backup<\/strong> is being configured
\n\u2022 Ensure backup Copies<\/strong> do not truncate log files
\n\u2022 Ensure a minimal protection of two copies of every mailbox database, irrespective of the fact whether Exchange is implemented with numerous disks\/drives (JBOD)<\/strong> disks or Serial ATA<\/strong>
\n\u2022 Ensure that minimum frequency for mailbox synchronization is set greater than 15 minutes
\n\u2022 Ensure to create manifold protection groups and add Exchange Databases<\/strong> to every protection group for housing parallel Exchange database backups<\/strong><\/p>\n
\nii. Now, use cmdlet\u2014 Set-MailboxDatabase<\/strong> to configure the recovery database<\/strong>
\niii. Now, under DPM Administrator Console<\/strong>, select the Recovery view<\/strong> and direct to the mailbox database<\/strong> that is to be recovered.
\niv. Go to Recovery Time,<\/strong> select Recover,<\/strong> and choose Recovery points<\/strong> option. In the recovery points<\/strong> section, click on to a data and select a recovery point.
\nv. Now, under the Recovery Wizard<\/strong> examine your recovery selection
\nvi. Click on Next.<\/strong>
\nvii. State the recovery type<\/strong> you wish to execute.
\nviii. Click Next<\/strong>
\nix. Specify Recovery Options<\/strong> screen will pop. Here, specify whether you want to mount the databases, want to enable throttling, want to enable SAN-based recovery, or want to send an email notification on completion or not.<\/span>
\nx. Now, under Summary<\/strong> screen, just review the Recovery settings<\/strong>
\nxi. Click on Recover<\/strong>
\nxii. After successful completion<\/strong>, click on Close<\/strong>
\nxiii. By the end of this step, the Recovery process<\/strong> has completed; however, the Mailbox is not completely Restored<\/strong>. To reset the mailbox, run cmdlet: New-MailboxRestoreRequest -SourceDatabase ‘RDB-CONTROL’ -SourceStoreMailbox ‘mailbox name’ -TargetMailbox <name>@contoso.com -TargetRootFolder Recovery -SkipMerging StorageProviderForSource<\/strong>
\nxiv. After restoring, run the Windows PowerShell cmdlet<\/strong> to dismount as well as delete the Recovery Mailbox database: Remove-MailboxDatabase -Identity ‘RDB-CONTROL’<\/strong><\/p>\n
\nii. Under the Recovery view<\/strong>, select the mailbox database<\/strong> that you need to recover
\niii. Now, under the Recovery Points section<\/strong>, select a date, and choose Latest<\/strong> to get the recent backup
\niv. Click on to Recover.<\/strong>
\nv. Now, under the Recovery Wizard<\/strong> analyze the recovery selection
\nvi. Once you are done with it, click on to Next.<\/strong>
\nvii. Here, state the recovery type<\/strong> you want to execute.
\nviii. Click on Next<\/strong>
\nix. A Specify Recovery Options<\/strong> screen will pop up. In this screen, select Mount the databases after they are recovered and Network bandwidth usage throttling<\/strong> option. Further, if you wish to enable the SAN-based recovery<\/strong> option, do checking the appropriate boxes.
\nx. Under the Notification window<\/strong>, click on Send an e-mail when the recovery completes<\/strong> option by specifying the email address of the recipient.
\nxi. Now, Open Exchange Admin Center<\/strong> again
\nxii. Click on Servers<\/strong> and select Databases<\/strong>
\nxiii. Now, Select the Exchanger mailbox database<\/strong> that you need to overwrite
\nxiv. Click on Edit<\/strong>
\nxv. Now, click on Maintenance<\/strong>
\nxvi. Select This database can be overwritten by a restore<\/strong>
\nxvii. Click on Save<\/strong>
\nxviii. Click on to Summary<\/strong> screen to view your Recovery Settings<\/strong>
\nxix. Click on Recover<\/strong>
\nxx. Click on Finish<\/strong><\/p>\n
\nii. Now, select the Server<\/strong> that needs to recover
\niii. Click on to the Recovery Time<\/strong>, choose Recover<\/strong>, and click on to Recovery Points<\/strong> option
\niv. Under the Recovery Points<\/strong> option, select the data and recovery point<\/strong> from the list
\nv. Now, right-click on to BMR -> Recover<\/strong>
\nvi. Go to Recovery Wizard<\/strong> and examine the Recovery Selection<\/strong>
\nvii. Click on Next<\/strong>
\nviii. Under the Selective Recovery Type<\/strong> screen, choose Copy to a network folder<\/strong> or Copy to tape<\/strong> option as per preference.
\nix. Now, under the Specify Destination<\/strong> screen, choose the location where you need to store the database files.
\nx. Now, go to the Specify Recovery Options<\/strong> screen and perform the following actions\u2014 Mount the databases after they are recovered, Network bandwidth usage throttling, Enable SAN-based recovery using hardware snapshots, Notifications<\/strong> as per the convenience.
\nxi. Go to Monitoring Tab<\/strong> to view the process progress
\nxii. A Recovery Message<\/strong> will generate after successful recovery
\nxiii. Now, open the destination folder of recovery files and rename it
\nxiv. If you wish to execute the Bare Metal Recovery,<\/strong> simply insert the operating system ISO<\/strong> and select Repair<\/strong>. Under Advanced<\/strong> options, choose System Image Recovery.<\/strong>
\nxv. Now, under the Select a system image backup<\/strong> screen, choose Select a system image.<\/strong>
\nxvi. Here, go to the Advanced<\/strong> option and from a network share, choose recovery files.
\nxvii. Click on Search for a<\/strong> system image on the network<\/strong> and opt for Yes<\/strong>
\nxviii. Now, state the network folder, choose the backup,<\/strong> and specify the date as well as the time of the image that needs to be restored. You can also state the additional driver<\/strong> as well as the disk settings<\/strong>
\nxix. Click on Finish to restore.<\/p>\n