Although not required in Data Protection Manager (DPM), it’s best to back up the Active Directory server, along with the Exchange Server. This is because Exchange Server relies heavily on the Active Directory Schema and restoring an object in Exchange Server would also need to restore the Active Directory object associated with it. It’s always best to separate the Active Directory and Exchange Server in Data Protection Manager (DPM) Protection Groups.<\/p>
Here’s the process to set up the DPM backup.<\/strong><\/h3>Once you open the System Center 2019 DPM Administrator Console<\/strong>, click on New<\/strong> and then click on Create Protection Group wizard<\/strong>. Now, you need to click on Next<\/strong> to proceed.<\/p>![\"the](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/the-System-Center-2019-DPM-Administrator-Console.png\")
Image Source – 4sysops<\/figcaption><\/figure>Then, select the Servers<\/strong> option and click Next<\/strong> to proceed to select the servers.<\/p>![\"select](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/select-the-Servers.png\")
<\/figure>\nNote:<\/strong> Here, we will be choosing Active Directory Server from the list of servers. If you don’t see the Server, it means you might not have installed the agent on the server, there is some issue with the service, or the service of the agent is not stated.<\/em><\/p>\n<\/blockquote>Once selected, you will be presented with a prompt showing the things that the Data Protection Manager (DPM) cannot back up. Such things include:<\/p>
\n- Recycle Bin<\/li>\n\n\n\n
- Non-NTFS volumes<\/li>\n\n\n\n
- DFS Links<\/li>\n\n\n\n
- CDs<\/li>\n\n\n\n
- Quorum Disks in case of Clusters<\/li>\n<\/ul>
The important thing in an Active Directory Server is the System Protection area.<\/p>![\"system](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/system-protection-area.png\")
<\/figure>In the next screen, give the group a name and select the protection method. In this example, we will use the Disk method. However, you can also use the cloud or tape drive option, depending on your business needs.<\/p>![\"give](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/give-the-group-a-name-and-select-the-protection-method.png\")
<\/figure>Before going ahead with the configuration of the backup retention, you need to check that you have enough resources to hold your data, depending on the retention. It is always recommended to plan your backup and the resources needed for your backup. Data Protection Manager (DPM) does not calculate the needed disk space accurately. So, it’s always best to first run a test backup job and from there you would get a rough idea about the space needed.<\/p>![\"confirm](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/confirm-the-first-seeding.png\")
<\/figure>Once you have the storage and the retention period confirmed, the next step is to confirm the first seeding. There are two options: synchronization over the network or transferring the data manually. Then, see the changes.<\/p>
If you are familiar with clusters and availability groups, the above falls into the same work needed for the initial copy. In the next screen, the progress will start and eventually, it will be updated as success.<\/p>![\"progress](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/progress-will-start-and-eventually.png\")
<\/figure>Once you have the Active Directory group done, the next step is to create the Exchange Server. You need to follow the same process of the Active Directory, until the selection of the Exchange Server. In the server selection, select the Exchange Server if it is a standalone server or select the Database Availability Group from the structure.<\/p>
Once you come to the destination of the backup, if you have a Database Availability Group<\/a>, you will need to run the integrity check (see below) on both databases and transaction logs or transaction logs only. If you run it on both, it will take a considerate amount of time depending on the size of the databases.<\/p>![\"run](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/run-the-integrity-check.png\")
<\/figure>At this stage, you will get an error, since ESEUtil<\/a> is an executable on the Exchange Server. All you need to do is copy the eseutil.exe<\/strong> and ese.dll <\/strong>from your Exchange Server to the server hosting the Data Protection Manager (DPM).<\/p>![\"error](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/error-message.png\")
<\/figure>The next step is to specify the source server in case you have a Database Availability Group (DAG). The last step is to set up the retention.<\/p>
Restoring from Data Protection Manager (DPM)<\/strong><\/strong><\/h3>To restore to an Exchange Server, you need to first create a recovery mailbox database in Exchange. This can be created from PowerShell using the below command:<\/p>
New-MailboxDatabase -Server <ServerName> -Name <database name> -Recovery -EdbFilePath <EDB file location> -LogFolderPath <logs location><\/code><\/pre>![\"New-MailboxDatabase](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/New-MailboxDatabase-Server.png\")
<\/figure>Once it is created, you need to mount it.<\/p>
Mount-Database <Database Name><\/code><\/pre>![\"Mount-Database\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/Mount-Database.png\")
<\/figure>Then, you need to allow the overwrite using the below command:<\/p>
Set-MailboxDatabase <Database Name> -AllowFileRestore $true<\/code><\/pre>![\"Set-MailboxDatabase\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/Set-MailboxDatabase.png\")
<\/figure>In the Data Protection Manager (DPM), click on the restore job and select from the available recovery points associated with the Exchange Server protection group. Once this is selected, select the Recover mailbox to an Exchange Server database<\/strong>.<\/p>![\"Recover](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/Recover-mailbox-to-an-Exchange-Server-database..png\")
<\/figure>Next, you will need to select the server in case of DAG and the recovery database.<\/p>![\"select](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/02\/select-the-server-in-case-of-DAG-.jpg\")
<\/figure>Now, verify the restore job and click on Restore to start the restore job.<\/p>
\nNote:<\/strong> After this, you will either need to move the mailbox to the live database in case you need to restore the whole mailbox or extract it to PST in case you need specific folder\/s or email\/s.<\/em><\/p>\n<\/blockquote>Conclusion<\/strong><\/h2>The above procedure works when everything goes well. Restoring from the Data Protection Manager (DPM) can be an administrative burden as you will need to restore to a separately created Recovery Database in your Exchange Server. Then, you will need to move or export to PST to restore email\/s or folder\/s. This will take time and resources. Also, you need to have a fully functional Exchange Server. What if your Exchange Server is not working well or you cannot restore from yesterday’s backup? Data Protection Manager (DPM) will not be able to restore and you cannot granularly restore specific emails or folders.<\/p>
In such cases, it would be best to use applications, like Stellar Repair for Exchange<\/a>. By using this application, you can open and browse through corrupted EDB files, from any version of the Exchange Server. You can granularly export to PST and other file formats. You can also export directly to a live Exchange Server database with no need to create recovery databases and with little administrative effort. You can also export directly to an Office 365 tenant.<\/p>\n","protected":false},"excerpt":{"rendered":"
Then, select the Servers<\/strong> option and click Next<\/strong> to proceed to select the servers.<\/p> Note:<\/strong> Here, we will be choosing Active Directory Server from the list of servers. If you don’t see the Server, it means you might not have installed the agent on the server, there is some issue with the service, or the service of the agent is not stated.<\/em><\/p>\n<\/blockquote> Once selected, you will be presented with a prompt showing the things that the Data Protection Manager (DPM) cannot back up. Such things include:<\/p> The important thing in an Active Directory Server is the System Protection area.<\/p> In the next screen, give the group a name and select the protection method. In this example, we will use the Disk method. However, you can also use the cloud or tape drive option, depending on your business needs.<\/p> Before going ahead with the configuration of the backup retention, you need to check that you have enough resources to hold your data, depending on the retention. It is always recommended to plan your backup and the resources needed for your backup. Data Protection Manager (DPM) does not calculate the needed disk space accurately. So, it’s always best to first run a test backup job and from there you would get a rough idea about the space needed.<\/p> Once you have the storage and the retention period confirmed, the next step is to confirm the first seeding. There are two options: synchronization over the network or transferring the data manually. Then, see the changes.<\/p> If you are familiar with clusters and availability groups, the above falls into the same work needed for the initial copy. In the next screen, the progress will start and eventually, it will be updated as success.<\/p> Once you have the Active Directory group done, the next step is to create the Exchange Server. You need to follow the same process of the Active Directory, until the selection of the Exchange Server. In the server selection, select the Exchange Server if it is a standalone server or select the Database Availability Group from the structure.<\/p> Once you come to the destination of the backup, if you have a Database Availability Group<\/a>, you will need to run the integrity check (see below) on both databases and transaction logs or transaction logs only. If you run it on both, it will take a considerate amount of time depending on the size of the databases.<\/p> At this stage, you will get an error, since ESEUtil<\/a> is an executable on the Exchange Server. All you need to do is copy the eseutil.exe<\/strong> and ese.dll <\/strong>from your Exchange Server to the server hosting the Data Protection Manager (DPM).<\/p> The next step is to specify the source server in case you have a Database Availability Group (DAG). The last step is to set up the retention.<\/p> To restore to an Exchange Server, you need to first create a recovery mailbox database in Exchange. This can be created from PowerShell using the below command:<\/p> Once it is created, you need to mount it.<\/p> Then, you need to allow the overwrite using the below command:<\/p> In the Data Protection Manager (DPM), click on the restore job and select from the available recovery points associated with the Exchange Server protection group. Once this is selected, select the Recover mailbox to an Exchange Server database<\/strong>.<\/p> Next, you will need to select the server in case of DAG and the recovery database.<\/p> Now, verify the restore job and click on Restore to start the restore job.<\/p> Note:<\/strong> After this, you will either need to move the mailbox to the live database in case you need to restore the whole mailbox or extract it to PST in case you need specific folder\/s or email\/s.<\/em><\/p>\n<\/blockquote> The above procedure works when everything goes well. Restoring from the Data Protection Manager (DPM) can be an administrative burden as you will need to restore to a separately created Recovery Database in your Exchange Server. Then, you will need to move or export to PST to restore email\/s or folder\/s. This will take time and resources. Also, you need to have a fully functional Exchange Server. What if your Exchange Server is not working well or you cannot restore from yesterday’s backup? Data Protection Manager (DPM) will not be able to restore and you cannot granularly restore specific emails or folders.<\/p> In such cases, it would be best to use applications, like Stellar Repair for Exchange<\/a>. By using this application, you can open and browse through corrupted EDB files, from any version of the Exchange Server. You can granularly export to PST and other file formats. You can also export directly to a live Exchange Server database with no need to create recovery databases and with little administrative effort. You can also export directly to an Office 365 tenant.<\/p>\n","protected":false},"excerpt":{"rendered":"<\/figure>\n
\n
<\/figure><\/figure><\/figure><\/figure><\/figure><\/figure>Restoring from Data Protection Manager (DPM)<\/strong><\/strong><\/h3>
New-MailboxDatabase -Server <ServerName> -Name <database name> -Recovery -EdbFilePath <EDB file location> -LogFolderPath <logs location><\/code><\/pre><\/figure>Mount-Database <Database Name><\/code><\/pre><\/figure>Set-MailboxDatabase <Database Name> -AllowFileRestore $true<\/code><\/pre><\/figure><\/figure><\/figure>\n
Conclusion<\/strong><\/h2>