SCDPM Troubles: "The destination to store the backup cannot be one of the source volumes"

By YellowOnline on Friday 8 November 2013 16:49 - Comments (3)
Category: SCDPM, Views: 8.436

How great to work with SCDPM, a product almost no one uses. It's not a bad product, but it isn't mature yet, not wide-spread and not on Microsoft's list of high-priority products. I hope someday the application will break out of this vicious circle.

The problem with a little used application is that there isn't as much information around on the net to help you with your problems. Ironically, most of the "Click here for more information" links in the product itself forward to a 404 on the Microsoft site. Ugh.

Anyway: today I dived into a problem I should've solved a long time ago already and I actually managed to find a solution for it. One of my DPM servers couldn't get backed up by my Disaster Recovery DPM.

The problem has actually little to do with DPM itself but rather with Windows Backup, so this is SCDPM version independent.

Read more »

Removing DPM Recovery Points from Inactive Protection

By YellowOnline on Tuesday 22 January 2013 10:55 - Comments (6)
Category: SCDPM, Views: 13.539

Removing DPM Recovery Points from Inactive Protection

An annoying limit of SCDPM is its maximum of 9000 recovery points per server (which is a VSS limit it seems). Recently I did a migration of a bunch of protected servers to another DPM server without moving the protected data as well - because that's simply not possible as far as I know. If it is, please let me know.

So anyway: after moving the protected server to another DPM server, the problem is that I can't just throw away the old data. I have to guarantee 2 months of recovery so the data needs to stay on the old DPM server for two months, under a header Inactive protection for previously protected data.

When I wanted to add new protected servers to the DPM server that I moved other protected servers away from, I hit the 9000 recovery points. Blast.

Of course: I have the data of two drives on 22 servers as Inactive protection for previously protected data. That's 22x2x62 = 2728 recovery points. Yikes, these old snapshots are eating about a third of my snapshot capability.

That migration happened about three weeks ago. The problem is that inactive recovery points will not automatically prune just like a recovery point that is part of an active protection group. An idea would be to remove all recovery points that are older than 2 months, which would give me right now 924 available recovery points, enough to add the stuff I need to backup to that same DPM server.

So how do we remove recovery points? Not through the GUI in any case: it only offers the possibility of removing all recovery points for a given data source, not specific points in time. Also, removing 924 recovery points by hand would be quite a tedious job. Automation is the keyword.

Powershell to the rescue!

Read more »

SCDPM 2007 SQL Self Recovery with clusters

By YellowOnline on Friday 7 December 2012 09:47 - Comments (0)
Category: SCDPM, Views: 2.770

Gosh, it's been two months since I blogged. I'm spending too much time playing video games lately :)

The past week our MS SQL environment got a health check my Microsoft, comparable with ADRAP for AD. The downside of being a SCCM/SCOM/SCDPM administrator is that you get involved in whatever happens with other products in your company, because you deploy them, monitor them and back them up.

There are two things that make a DPM admin's life easier when it comes to recovery: enabling end-user recovery - which is a simple AD schema update if you're post-Vista (on XP you need to install an agent on the clients), and enabling SQL self recovery for SAs. The latter is slightly more complicated.

Read more »

SCDPM Scripting: Trouble with LastRecoveryPoint

By YellowOnline on Thursday 29 March 2012 14:22 - Comments (4)
Category: SCDPM, Views: 2.942

Many a DPM admin who scripts in Powershell will want to create a script at one point that asks from a specific data source its last recovery point. For this, a data source object has the property ($DataSource).LatestRecoveryPoint.

Many a DPM admin will have been utterly disappointed to find out that the value returned is 01/01/0001 00:00:00.

Read more »