EverydayNerd | DPM Style

Oops, found the answer myself. I need to run the c...

2010-02-02T06:53:06.087-05:00

Oops, found the answer myself. I need to run the command from the right place. I saved it to the C: drive and use this command to launch it:

C:\Windows\system32\windowspowershell\v1.0\powershell.exe -PSConsoleFile "C:\Program Files\Microsoft DPM\DPM\bin\dpmshell.psc1" -command ".'C:\createrecoverypoints.ps1'"

Hi there Would like to use your script,but when I ...

2010-02-02T06:42:22.988-05:00

Hi there
Would like to use your script,but when I run it I get an error that "get-protectiongroup" is not a recognised cmdlet.

Thanks

Hello, thanks for your advice. I ran into a simil...

2010-01-08T13:22:14.062-05:00

Hello, thanks for your advice. I ran into a similiar issue installing MS09-062 (KB970892) on our 2 node SQL Server 2005 SP3 UAT cluster. On this cluster we have both SQL 2000 and 2005 engines. I'm posting my comment to possibly help out my follow DBA. I spent many hours on this and finally opened a ticket with MS. Turns out, that having the J: drive offline for one of my SQL 2000 engines (used for a POC migration)was the issue. Even though this was a SQL 2000 engine, the patch was probably trying to scan all availble disk resources, even though that resource group was not selected or couldn't be selected in the patch startup GUI. WTH

Hang in there fellow Microsoft DBA's.

@ Richard: Unfortunately, no. I am currently fac...

2009-12-07T16:13:53.565-05:00

@ Richard: Unfortunately, no. I am currently facing this issue now - with SAN frames up for lease, I'm having to migrate to a new SAN. NOT an easy feat at all!

Can you move the Replica and Recovery points that ...

2009-12-07T15:46:51.558-05:00

Can you move the Replica and Recovery points that are on DPMServer01 to DPMServer02?

Great Info!!!!

2009-11-02T16:17:01.959-05:00

Great Info!!!!

Thanks for info. It actually was helpful to me a l...

2009-10-21T19:24:23.842-04:00

Thanks for info. It actually was helpful to me a lot.

When i went to do the standard install of SQL Serv...

2009-08-04T08:04:18.523-04:00

When i went to do the standard install of SQL Server 2005 (to name the default database what DPM wants it to be, I got a message part of the way thru that I had ASP.net 32-bit installed on Windows x64 and that this config would affect Reporting Services... I fixed ASP.net and continued the install; will update if anything else occurs.

Great post, Did you just configure task schedular ...

2009-07-10T09:00:17.079-04:00

Great post, Did you just configure task schedular to run the script?

I am also getting this error repeatedly on just on...

2009-06-16T11:05:12.333-04:00

I am also getting this error repeatedly on just one VM on one host. This VM has SQL 2005 installed.

For what its worth, we are also on Exchange 2007 C...

2008-12-10T12:35:21.136-05:00

For what its worth, we are also on Exchange 2007 CCR (rollup 3). On DPM I have the feature release and the 949779 release/featurepack/whatever. Every express full backup of our storage groups completes with no issues. Every recovery point sync fails with the retryable VSS error.If I recreate the recoverypoint it tells me its inconsistent. If I then run the consistency check, its reporting that all is well. This still sucks, but beats rebooting the passive node for each backup. Not sure if its the 949... fix that is making this slightly less painful or if there is something different in our environment.

I'm experiencing the same error but with just one ...

2008-12-03T10:29:58.975-05:00

I'm experiencing the same error but with just one Virtual Machine. The other virtual machines on that host are backing up fine.

A reboot of the host seems to get everything back in sync but that is not a viable solution. I have tried just about every sequence of service restarts possible. Talk about frustrating.

Thanks,

John

Did Update Rollup 4 fix the issue with DPM? We ar...

2008-11-07T12:07:17.401-05:00

Did Update Rollup 4 fix the issue with DPM? We are using TSM copy Services with TDP Exchange and are also working with Microsoft on this. As far as I can tell the issue was not fixed with Update Rollup 4 (at least not for TSM backup).

I'm assuming that you are protecting a CCR? If so...

2008-11-07T09:29:07.030-05:00

I'm assuming that you are protecting a CCR? If so, re-seed your CCR for the storage group that is failing.

HiyaHas anyone come up with a resolution for this ...

2008-11-07T09:18:11.538-05:00

Hiya

Has anyone come up with a resolution for this as i am experiencing the same issue as brian?

Thanks

So I took your advice (uninstalling, then reinstal...

2008-10-30T16:47:15.195-04:00

So I took your advice (uninstalling, then reinstalling SQL with the special named instance) and was midway through the SQL install when there was another Ah ha! moment... I had neglected to follow the directions to customize each individual SQL Service logon account to be—as applicable—Local System, Network Service, or Local Service. So we have MS recomending a non-Best Practices installation of SQL. Ahem! Everyone is running their SQL servers with a least privlige domain user account right? ;)

Hmmm, oh well...continuing on... X__X

So, SP2 and post SP2 security fixes went on fine and then DPM setup gets through all preReq checks. So then I specify existing SQL and enter in localhost\MS$DPM2007$ and administrator account info. Interesting msg pops up...I can't use the special DPM named instance on the local machine BUT go back and have it install dedicated instance and it will detect the already installed SQL and use that (and its Reporting Services).

Voila! I did so and it did indeed detect the already installed SQL Enterprise Ed.! It does change the service logon user account to Microsot$DPM$Acct for both SQL Server Agent and SQL Server Services. Strangely, there is now two instances of SQL Server Reporting Services, one linked to the named instance starting as Network Service and one to the (non-existant) default MSSQLSERVER. Hmm, hopefully I can get rid of that one w/o hosing the whole thing!

So Install looks good with the exception of some error messages needing to be policed in event viewer.

I would stick with MS@DMP$2007 as the instance nam...

2008-10-29T15:40:35.894-04:00

I would stick with MS@DMP$2007 as the instance name - DPM is fragile enough as it is, so why mix things up? :) I did try installing SQL manually, as well as SP2 from the TechNet documentation, but when the DPM installer runs, it has to touch SQL, and that is when I had to unplug the NIC.

Hope this helps!

WRT the existing SQL install...According to the do...

2008-10-29T15:32:05.120-04:00

WRT the existing SQL install...

According to the docs it sure seems like you should be able to pre-install a default instance of SQL 2005 apply SP2 and then get on with it.

From http://technet.microsoft.com/en-us/library/bb808868.aspx

"If you do not want to use the dedicated instance for DPM, you can use another instance name or you can install SQL Server on a different computer."

But then further down in Step 11.:

"On the Instance Name page, select Named instance, type MS$DPM2007$, and then click Next."

Grrr so which one is it Microsoft, MS$DPM2007$ or "another instance name"?

BTW, I'm doing this on Server 2008 and my point of failure is at that same SQL selection screen and I get the error:

Setup has detected that the installation of Reporting Services is not correctly configured or no instance of Reporting Services is linked to MS$DPM2007$ of SQL Server.1)To use the local dedicated MS$DPM2007$ instance with DPM, uninstall SQL Server and run setup again.
2)To use the option of installing DPM with an existing instance of SQL Server, make sure that the Reporting Services instance is also installed and linked correctly. For details, refer to DPM Setup Help.

I'm keeping up the fight... ;)

Glad I could help! I am still working with Micros...

2008-10-23T08:19:25.370-04:00

Glad I could help! I am still working with Microsoft on this issue, so once I get a resolution, I'll post it... grab the RSS feed, so you won't miss it! :)

Thanks Heaps. We use TSM copy Services and we were...

2008-10-22T20:51:16.868-04:00

Thanks Heaps. We use TSM copy Services and we were getting this same Retryable Errors after 3 weeks of successful VSS replica Backups. We have switched back to performing Legacy Backups using TSM TDP on the active server.

i've done everything suggested here and still get ...

2008-10-16T11:57:29.446-04:00

i've done everything suggested here and still get the error
"DPM has detected a discontinuity in the log chain for Storage group First Storage Group on morgan03.MI2K3.local since the last synchronization. (ID 30216 Details: Unspecified error (0x80004005))"

Any other ideas?
Thanks for your site.

Got to love typos! Thanks, and corrected!

2008-10-07T09:33:31.748-04:00

Got to love typos! Thanks, and corrected!

shouldn't it be SetDpmServer.exe -dpmServerName DP...

2008-10-07T08:45:18.634-04:00

shouldn't it be SetDpmServer.exe -dpmServerName DPMServer02 instead of DPMServer01?

Since it is the entire point of going from 1 to 2...

Best Regards
Wim Boudin

When the replica is showing inconsistent, there ar...

2008-10-01T14:12:11.270-04:00

When the replica is showing inconsistent, there are two different types of Consistency Checks:

1: Consistency Check
2: Consistency Check with Synchronization

They are COMPLETELY different. The first is a normal Consistency Check - run from right clicking the Protection Group, and choosing Run Consistency Check.

The second is Consistency Check with Synchronization. This can ONLY be done from the monitoring tab. Select the alert for the inconsistent storage group. In the details section, you will see the link to run ac Synchronization with a Consistency Check.

I know this sounds stupid, but I actually spoke with one of the developers that wrote DPM 2007, and he confirmed that they are indeed two types of Consistency Checks.

So, to answer your question, you need to run the second one - the Synchronization with Consistency Check.

Hope this helps!

When I try this fix I get another error back sayin...

2008-10-01T14:03:40.246-04:00

When I try this fix I get another error back saying that the state is inconsistent so it will not let me create a recovery point. Any ideas why this is happening?

Thanks!

Ken