Create a new protection group in DPM 2012 R2

Brief Description:

A protection group is a collection of data sources that share the same protection configuration. Data sources within a protection group are referred to as protection group members.

Steps to create a new protection group:

dpm1a

 

  • Double click the DPM icon to launch DPM.

dpm2

  • The console will open up and show the protection groups currently running.
  • To add a new protection group click the new button.

dpm3

  • We going to protect a server. Click Next.

dpm4

  • Step 1 -> Expand the server you want to backup.
  • Step 2 -> Click the checkbox for the folder you want to backup. Once that is done it will show on the right hand side of the screen.
  • Click Next.

dpm5

  • Step 1 -> Give your protection group a name.
  • Step 2 -> Select your option.
  • Step 3 -> Optional, you can enable online protection.
  • Click Next.

dpm6

  • Step 1 -> Select your retention range.
  • Step 2 -> Select the Synchronization.
  • Step 3 -> Click on the Modify button.

dpm7

  • Select the days of the week you want the backups to run, the default time is set, you can click the remove button and add in your times.
  • Click OK and it will return you to the previous screen. Click Next.

dpm8

  • I have a storage pool setup so it allocates the space, however if you want to modify this then click the modify button and select your storage. Don’t forget to format the drive within DPM.
  • Click Next.

dpm9

  • Select your option above. Click Next.

dpm10

  • Here you can select where you want to run a consistency chick if a replica becomes inconsistent and then you can also schedule it. Once you have made your selection click Next.

dpm11

  • Review the summary and then click “Create Group”.
  • Once it completes it will give you a success message. 
  • In the DPM you will now have the new protection

hope it helps.

DPM Console shutting down with error 917 constantly

Environment: DPM 2012 R2 SP1 with Rollup 3

I had a protection group that didn’t want to update and I went and remove the group but retained the data. Immediately after that I was presented with the following error:

“Connection to the DPM service has been lost

Review the application event log for information about a possible service shut-down.
Verify that the following services are not disabled:
DPM
DPM Replication Agent
SQLAgent$MSDPM2010
MSSQL$MSDPM2010
Virtual Disk Service
Volume Shadow Copy

ID: 917”

I attempted a restart which didn’t fix the problem. I ran a CHECKDB in SQL but it returned clean. Even after this I couldn’t open up the DPM Console.

Last attempt I ran the following: .\DPMSync.exe -sync

This command fixed the console crashing but all replicas from all protection groups were in an inconsistent state now. Didn’t take long to run consistency checks to have all backups back to normal again.

Hope it helps.

 

DPM 2012 R2 & SharePoint 2013 Backup

I wanted to modify my Sharepoint Protection Group on DPM to backup Sharepoint 2013 so I can do item level restore. When expanding the server and Sharepoint farm I got presented with the following error:

DPMSharepointSo the first thing I did was check my VSS writers, you can do so as follows:

  • VSSAdmin ListWriters

Everything seemed fine. Permissions were set on the SQL Server VSS writer service with a domain account. Restarted the service, no luck.

Only thing I found was that 1 of the SharePoint Databases was giving an error. It was the WSS_Usage DB. I removed this DB, created a new one and then checked. All the errors in event viewer were gone.

I now went back to DPM, edited my protection group and I was able to select my Sharepoint farm.

Hope it helps.

Upgrade DPM 2012 SP1 to DPM 2012 R2

Yesterday I downloaded System Center Data Protection Manager 2012 R2. I extracted the ISO file and started the splash screen.

Upon clicking the link to install DPM another screen similar to the earlier versions appears and you click next. With this install you have the option to install using SQL local or clustered.

If you choose local it defaults to the SQL instance created by DPM 2012 (unless you changed it)

When I clicked Check and Install the checks run through and then DPM 2012 R2 fails with an error that the SQL instance is not valid.

When I checked the logs I noticed it was complaining about the protocol TCP. I went to SQL Configuration Manager and I got the same WMI error saying it couldnt open. I then opened up and elevated prompt and ran the following:

mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”

After that I could open up SQL Configuration Manager, I enabled TCP for the SQL instance and then restarted all the services. I then went back to the DPM 2012 R2 install and clicked the Check Again button and voila, DPM 2012 R2 upgraded my existing DPM installation and completed successfully.

Hope it helps.