none
DPM 2016 recreate sql database if corrupt, lose protection group? RRS feed

  • Question

  • Im plagued with a sql error code 64 when using the console.

    I believe the db may be corrupt.

    I may have a backup but it dates back to april or before.  What do you lose by restoring one of those sql bak files?  Do you just run the sql restore routine from within sql then reload the console?

    If those backups are also corrupt, how do you recreate things and do you lose the PG?

    Thanks in advance


    Tech, the Universe, Everything: http://tech-stew.com Just Plane Crazy http://flight-stew.com

    Thursday, November 7, 2019 8:22 PM

All replies

  • Hi,

    There's a specific procedure for restoring the DPM database, basically if you restore it you will see the recovery points that existed from the time the backup was taken.

    Here's the procedure:
    Restore and synchronize the DPM database with DPMSync

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Proposed as answer by Leon Laude Friday, November 8, 2019 11:41 AM
    Thursday, November 7, 2019 8:25 PM
  • Hi,

    There's a specific procedure for restoring the DPM database, basically if you restore it you will see the recovery points that existed from the time the backup was taken.

    Here's the procedure:
    Restore and synchronize the DPM database with DPMSync

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    So far i've had no success with the commandline..

    i've tried several variations, with single quotes, without, with instance name without, each time i get error id 457 invalid command line arguments

    DpmSync –RestoreDB -DbLoc "D:\Program Files\Microsoft SQL
    Server\MSSQL13.BACKUP02\MSSQL\Backup\QFEDPMDB_BACKUP02.bak" -instancename Backup02


    Tech, the Universe, Everything: http://tech-stew.com Just Plane Crazy http://flight-stew.com

    Thursday, November 7, 2019 9:05 PM
  • DpmSync –RestoreDB -DbLoc "D:\Program Files\Microsoft SQL
    Server\MSSQL13.BACKUP02\MSSQL\Backup\QFEDPMDB_BACKUP02.bak" -instancename Backup02


    I can see that the first "dash" is wrong (located before RestoreDB), this can easily happen when commands are copied.

    Try writing down the command manually instead.



    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, November 7, 2019 9:09 PM
  • DpmSync –RestoreDB -DbLoc "D:\Program Files\Microsoft SQL
    Server\MSSQL13.BACKUP02\MSSQL\Backup\QFEDPMDB_BACKUP02.bak" -instancename Backup02


    I can see that the first "dash" is wrong (located before RestoreDB), this can easily happen when commands are copied.

    Try writing down the command manually instead.



    Blog: https://thesystemcenterblog.com LinkedIn:

    Ah ok, i see this.

    I made it a little further, except for some reason it fails with "the login failed" for my domain admin account.


    Tech, the Universe, Everything: http://tech-stew.com Just Plane Crazy http://flight-stew.com

    Thursday, November 7, 2019 9:15 PM
  • I used management studio and restored it.

    I'm now running the sync command.

    Do i need to do the reallocate replica command after that i assume?


    Tech, the Universe, Everything: http://tech-stew.com Just Plane Crazy http://flight-stew.com

    Thursday, November 7, 2019 9:21 PM
  • Yes you can also use the SQL Management Studio to restore the database.

    After running the DpmSync -Sync command, run the DpmSync -ReallocateReplica yes.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, November 7, 2019 9:33 PM
  • Hi,

    Just checking to see if you have any update on your issue?

    If your issue was resolved, may I ask you to mark all the answers that helped you? This way it will also help others in the future who face the same challenge. Many thanks in advance!


    Best regards,
    Leon

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, December 11, 2019 9:37 PM