DPM 2007: Protecting Exchange 2003/2007
by
rastix
on Sun 03 Jun 2007 04:56 PM CEST
Yesterday, I installed DPM 2007 in our lab environment. Today, it is time to try out the protection features for Exchange 2003 and 2007.
Obviously, I don't have access to a tape library in our virtual environment so I configured DPM with one disk for the storage pool. I created a 30GB disk and added it to the storage pool. That is done in the Management section of the management console (click to enlarge):
When you add a disk, it is wiped clean and cannot be used for anything else. Make sure that you provide an empty disk to DPM. At first, I provided a disk formatted with NTFS thinking that DPM would wipe it. On that disk however, there was no space for protection.
After that, I deployed agents to an Exchange 2003 virtual machine and an Exchange 2007 virtual machine (click to enlarge):
A reboot is required because the agent includes a storage filter driver. The storage filter driver is used to create a bitmap of changed blocks on disk. That information is then used during the creation of express full backups. More about that later.
You don't have to deploy the agent from the console. You can deploy the agent with Group Policy, SMS, script or put it in your unattended server installation.
To protect Exchange (or anything else for that matter), you need to create a protection group. You just click Create Protection Group... in the Protection section of the management console. In the wizard that follows you first select the group members. Depending on the role of the server, you will be able to select what to backup. In the case of Exchange 2003/2007, the screen looks like this (click to enlarge):
Next, you have to select the kind of protection you want (to disk, to tape, to disk/to tape):
Because I protect Exchange servers, an Exchange specific question is asked: "Run Eseutil to check data integrity?". When you do that, eseutil will be run on the DPM server to verify the backups. You need to copy the required binaries to the DPM server if you want to do that.
Next, you need to set short-term objectives:
In this example, I retain backups for 21 days. Every 15 minutes, a synchronization will occur. For Exchange, this results in copying the transaction logs to the DPM server. If you observe the screenshot, you can see that an express full backup is also created every day at 0:00. An express full is a full backup in the sense that you have all the data but it is not a real full because not all data is copied accross every time you take a backup. Instead, only the changes are sent from the source server to DPM. With an express full every day and recovery points (transaction logs) every 15 minutes you have a lot of recovery points to revert to in case something goes wrong.
Based on the number of recovery points, the wizard will propose disk allocation for protection:
You need an initial copy of the protected data. You can let DPM do this for you or you can make a copy yourself and transfer the data using removable media. That last option is useful if you have a slow link. I let DPM make the copy and finished the wizard. In the protection section, you can now see what you are protecting:
After a while, the replica creation will finish and the protection status should be set to OK. In the Monitoring section, you get a nice overview of the jobs past, running and scheduled:
In a next post, I will talk a bit about recovering Exchange data.
