Script to remove all datasources in Inactive Protection

After I moved several protected servers from one DPM server to another, I had a LOT of exchange storage groups left in the Inactive Protection that I wanted to get rid of.  Doing this  manually was very time consuming, and lots of clicks.  So, after a quick search, I found a script on the Ctrl P blog that does exactly what I needed to do!

Usage:

Remove-InactiveDatasource.ps1 -DPMServerName [DPMServername] -RemoveOption [Remove Options]

Run ‘Remove-InactiveDatasource.ps1 -detailed’ for detailed help

Attachment: Remove-InactiveDatasource.ps1

DPM Install Issue: Error 3023 when installing

Error ID 3023:

DPM is unable to configure the Windows account because the password
you entered does not meet the Group Policy requirements. (ID: 3023)

I received this message right after selecting the DPM installer to install SQL, on the next screen, it asks for a password for the service account to use.  Note, that this creates a two local accounts, using the password provided in the installer.  Time after time, I kept getting this error ID 3023.  Strange thing, I was able to go to computer management, add a local account, using the exact same name and password that the DPM installer was trying to do, and it would work!?!?  But when the installer did it, it would fail.

This error was a HUGE problem, and caused me a great deal of stress, so, I wanted to pass on the solution, so nobody else needs to have this heartache! 

My first troubleshooting steps were to block all group policy to the OU the computer account was in, perform a gpupdate /force and restart the server.  This didn’t work.  Same error message.

Next, I created a local admin account, logged in with it, and tried to install DPM with it – no go, as the installer needs to communicate with Active Directory.

Then, I tried installing SQL 2005, and SQL 2005 SP2 manually.  The install when OK, albeit, the SQL install took an unusually long time to install.  I remembered something from a long time ago, that I was installing SQL, and it would hang for hours during the install, while setting permissions, and the trick was to unplug (or disable) the NIC during the install, and it goes right through without issues!  I did this, and the SQL install went through nice and quick!

So, Now I had SQL installed, back to the DPM installer.  So I choose the option for an existing SQL instance, and don’t you know, that only works if the SQL is NOT on the same box as you are installing DPM?  ARGH!!!

Uninstalled SQL….

Well, I had an idea – I had to disable the NIC for the SQL trick, maybe I can do this with DPM?  So, I disable the NIC, and start the installer.  Failed the pre-requisite check, saying it couldn’t communicate with Active Directory.  So, enabled the NIC, started the installer, got past the pre-requisite check, then disabled the NIC, selected for DPM to install SQL, clicked next, said a little prayer, and entered the password…. clicked next….. AND IT WORKED!  I was couldn’t believe it worked!  So, I enabled the NIC again, and let the installer go to work.

All was good, until the installer was done installing SQL, and SQL SP2, it started the DPM portion of the install, and it failed, with this error:

*** Error : Report configuration failed.

Verify that SQL Server Reporting Services is installed properly and that it is running.

ID: 812

Now oddly enough, this error references that SharePoint Services is installed on the same machine, and there are certain steps in order to make SQL for DPM and SharePoint Services to work correctly together.  Well, that’s great, except for the fact that I DIDN’T have SPS installed on the box!

Well, I ran through the installer again, disabling the NIC before the password, entered the password, enabled the NIC, and got to the DPM install portion again, and watched it fail on the section of setting security.   BINGO!  that’s the same place that SQL was messing up before!  So, start over, Disable the NIC for the password, enable it again, wait for the installer to get to setting security during the DPM install portion, and disabled it again….

Survey says!?  Success!!!!  After the security, the installer finished in a few minutes, and I enabled after the install was complete.  I enabled the NIC, restarted the box, and I was finally in business!

I hope this helps somebody else out there, I know it was a bear for me!  If you have any questions, please comment, and I’ll be glad to answer them if I can!  Good luck!

Move Protected Server Agent to another DPM server

If you work in a multiple DPM server environment, you will, at some point run into a situation that will require you to change protection from one DPM server to another. So, how do you do it? Simply two command lines. (queue up the Stapes “Easy” button…)

Scenario:

• DPMServer01 is protecting Exchange01
• You want DPMServer02 to protect Exchange01

This is a three step process:

1. On the DPM DPMServer01, stop protection of Exchange01
2. On Exchange01, Open a command prompt, and and navigate to where the DPM Agent is installed (default is %ProgramFiles%\Microsoft Data Protection Manager\DPM\bin\). Execute the following command:

SetDpmServer.exe -dpmServerName DPMServer02 

3. On DPMServer02, open DPM Management Shell (Powershell), and enter this command:

.\Attach-ProductionServer.ps1 -DPMServer DPMServer02 

You will also have to provide the following information (and can be added as additional switches in the command:

• -PSName (Protected Server Name)
• -UserName
• -Password
• -Domain

That’s it! (Time to press the “Easy” button!)I have noticed that it takes about 5 or so minutes for the agent to show up as available on the new DPM server.

Fix Error 3114 & Error 30216

Errors:

Recovery point creation jobs for Storage group Storage_Group_04 on Server1 have been failing. The number of failed recovery point creation jobs = 1. (ID 3114)

DPM has detected a discontinuity in the log chain for Storage group Storage_Group_04 on Server1 since the last synchronization. (ID 30216 Details: Unspecified error (0x80004005))

Fix:

Although DPM prompts you to Create a recovery point… it will not perform a Full Backup as needed to recover from this error.  Click the Protection tab, navigate to the Storage Group you are protecting, right click, and choose create recovery point.  Then choose to create an express full backup.  You can now inactivate this alert, as the Full backup will resolve the issue.