DPMBackup -db not working.

Morning,

Last week I upgraded to DPM 2012 R2. All went well; no problem; apart from taking  hours to run consistency checks on the replicas but I was expecting that.

Today when I tried to back up the database I was informed that I had to upgrade to SQL server 2012 SP1 before I could do that. Kinda wish that during the upgrade to DPM 2012R2 it would've told me that; but heyho.

So I've upgraded to SQL server 2012 SP1 this morning. Now when I run DPMBackup -db from the dpm management shell (The syntax that has worked for the last year or more) I get the error  Invalid command -db.

The help underneath the error suggests the syntax has changed to DpmBackup.exe; which returns the same error.

Anyone else experienced this yet? Am I missing something blindingly obvious?

DPM itself is working fine. Backups continuing normally; I just checked the latest synchronisations. Just db backup issue.

Any help much appreciated.

Richard

November 4th, 2013 1:13pm

I just ran into that 2 hours ago.

I fixed it with the additional parameters:

dpmbackup.exe -db -sqlServerName <hostname> -instanceName MSDPM2012 -dpmdbname DPMDB

Good luck!

  • Marked as answer by stafford7 Monday, November 04, 2013 4:04 PM
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2013 2:54pm

Brilliant! That did the trick.

Much easier typing all that rather than DPMBackup -db :-).

Thanks for your help Hans

Richard

November 4th, 2013 4:08pm

For me, this resulted in:

"Error: Failed to connect to server localhost\mssqlserver.
DpmBackup encountered an internal error. Check the Application Event Log for the cause of the failure."

In the case of DPM 2012R2 with SQL2012 installed on the same server (default MSSQLSERVER instance) I had to use this command-line:

 dpmbackup.exe -db -sqlServerName <dpmservername> -instanceName (Local) -dpmdbname <dpmDBname>

Replace the <dpmservername> and <dpmDBname> with your own values, but leave the (Local) exactly as it is.

Strangely, if you specify the literal instancename as MSSQLSERVER instead of (Local), it doesn't work.

Free Windows Admin Tool Kit Click here and download it now
January 6th, 2015 12:54pm

After Update Rollup 5, the above commandline doesn't work anymore. The parameter (local) now has to be put inside " quotation marks:  -instanceName "(local)"

The -? help text now seems to reflect this, but the version of dpmbackup.exe remains at 1.0.

February 26th, 2015 10:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics