Sunday 29 July 2012

Deploying System Center 2012 – Data Protection Manager

For the next stage of this lab build, I'm going to be looking at Data Protection Manager.  One of the key new pieces of functionality of the latest version is a centralized console.  In order to take a look at this functionality, I have decided to deploy two DPM servers.  As I will be growing the Exchange side of the lab quite significantly, I have decided to split the purpose for the two DPM servers into Exchange and non-Exchange.  I'll be assigning each of these two servers 500GB to use for backups which will leave half of the space on the 2TB for VM's.  The backup requirements will therefore not exceed 1TB from the SAS disk plus 240GB from the SSD.  However, as the SAS drive will also contain things that will not be backed up by DPM (such as OS images, templates etc), I'm not too worried about having given DPM less than 50% of the overall storage.  I'll be keeping the number of snapshots of any given object to a minimum, and for this lab environment, I expect any differences between snapshots to be extremely minimal anyway.

With the above in mind, I deployed two VM's from template.
With the VM's created, the 500GB volumes assigned, and the DPM install files downloaded, I logged onto the existing SQL server, and ran SQLPrepInstaller_x64.exe to install the SQL Pre-Requisites.
As DPM requires it's own SQL instance, I re-ran the SQL installer, selecting new installation or add shared features.
After accepting the license agreement and entering the product key I selected the Database Engine Services, SQL Server Replication, Full-Text search and reporting services. (The Management tools and SQL Client Connectivity SDK are also requirements, but these shared features were already installed for the Operations Manager instance.)
After some additional checks had run, I entered the name for the instance of INS02.
To keep things simple, I matched the Service accounts to those used for the Operations Manager instance.
I kept the default settings on the next 4 screens, after that, a summary is shown.
The install completed successfully.
To keep the network and firewall config simple for this second instance I loaded SQL server configuration manager and disabled dynamic port allocation, setting a static port of 1432.
I then copied the windows firewall rule I created earlier for the default instance and modified the name, program and port to match the second instance.
I then created a temporary rule in the Windows Firewall, to permit inbound UDP on port 1434 to the SQL browser service.  I should be able to disable this rule once setup completes.

After that, I restarted the Database Engine for INS02, and logged onto the first DPM server and launched the DPM installer.
For now, I'll just be installing DPM itself.  Clicking Data Protection Manager in the above window installs .NET framework 3.5.1 and then launches the DPM Setup Wizard.
I entered the Instance of SQL Server in the format SERVERNAME\INSTANCENAME.
Next, I entered the product key.
I'll be installing DPM to the local system drive.
I then entered a password for DPM to use for it's local user accounts.
I opted not to use Microsoft update.
Opted not to join the CEIP.
After that, you get a summary of options selected.
The install completed successfully.
I then computer Management, and initialized the 500GB volume.
Next, I loaded the DPM console, and went into administration and add disk.  Here I added the 500GB volume to the storage pool.
I then repeated the above process to install DPM on the second DPM server.  I'll cover additional configuration and agent deployment in a subsequent post.

No comments:

Post a Comment