none
Restore and Sync DPM 1807 RRS feed

  • Question

  • On a Windows 2012 R2 server I have DPM 2012 R2 and DPMDB also on same server with SQL 2012 R2 standard. 

    I upgraded both components  : 

    SQL 2012 R2 >  to SQL 2014 SP 3

    DPM 2012 R2 > to DPM 1801 and then DPM 1807.

    Now DPM 1807 is running fine without any issue. I am trying to upgrade OS from Windows 2012 to 2016 but there's some issue with current installed servicing image of Windows 2012 which isn't letting me to perform in-place upgrade up to 2016 (Microsoft also tried to fix but no luck)

    After taking backup of current DPMDB (which holds config for DPM1807) I am planning to install fresh 2016 on this same physical server and install fresh SQL 2017 along with fresh DPM 1807. Then to restore DPMDB in SQL instance via SSMS.

    I am doing this task in this way first time, just curious if DPMSync work correctly in this way !




    • Edited by V Jay Rana Friday, March 15, 2019 4:38 PM
    Friday, March 15, 2019 4:27 PM

Answers

  • Restoring directly to Windows Server 2016 should be ok, but as far as I know you need to restore on the same SQL Server version that you are currently using (SQL 2014 SP3) and later upgrade to SQL 2017. 

    You need to use DPMSYNC to restore DPM database

    https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/hh757907(v=sc.12)


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    • Marked as answer by V Jay Rana Friday, March 15, 2019 7:32 PM
    Friday, March 15, 2019 6:23 PM
  • Hi!

    There shouldn't be any issues running the DPMSync, so the to 


    1. Create a backup of the DPM database.

    2. Copy the DPM database backup to the new server.

    3. Shut down the old DPM server.

    4. In the Active Directory (AD) go and reset the computer account of the DPM server.

    5. Rename the new server to have the exact same name as the old DPM server.

    6. Install SQL Server (if it isn't already) on the new DPM server.

    7. Install DPM 1807 on the new DPM server.

    8. Restore the DPM database from the backup on the new server.

    9. Present the previous DPM disks to the new DPM server.

    10. Run the DPMSync.exe -Sync command on the new DPM server.

    11. Perform consistency checks on all the protected computers.

    12. Check status.

    By the way what errors did you receive when trying an in-place upgrade from Windows Server 2012 -> Windows Server 2016?

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Friday, March 15, 2019 7:32 PM
    Friday, March 15, 2019 6:24 PM

All replies

  • Restoring directly to Windows Server 2016 should be ok, but as far as I know you need to restore on the same SQL Server version that you are currently using (SQL 2014 SP3) and later upgrade to SQL 2017. 

    You need to use DPMSYNC to restore DPM database

    https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/hh757907(v=sc.12)


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    • Marked as answer by V Jay Rana Friday, March 15, 2019 7:32 PM
    Friday, March 15, 2019 6:23 PM
  • Hi!

    There shouldn't be any issues running the DPMSync, so the to 


    1. Create a backup of the DPM database.

    2. Copy the DPM database backup to the new server.

    3. Shut down the old DPM server.

    4. In the Active Directory (AD) go and reset the computer account of the DPM server.

    5. Rename the new server to have the exact same name as the old DPM server.

    6. Install SQL Server (if it isn't already) on the new DPM server.

    7. Install DPM 1807 on the new DPM server.

    8. Restore the DPM database from the backup on the new server.

    9. Present the previous DPM disks to the new DPM server.

    10. Run the DPMSync.exe -Sync command on the new DPM server.

    11. Perform consistency checks on all the protected computers.

    12. Check status.

    By the way what errors did you receive when trying an in-place upgrade from Windows Server 2012 -> Windows Server 2016?

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by V Jay Rana Friday, March 15, 2019 7:32 PM
    Friday, March 15, 2019 6:24 PM
  • It's the Embedded storage controller driver which is windows showing 'Not digitally signed' in device manager. Though it's working fine with current setup but I guess windows upgrade check those things during upgrade or install so it's not allowing to proceed with upgrade. 

    I worked with HP as well, they provided updated driver but no luck with that. The boot partition drives are connected this controller and it doesn't allow me to go with upgrade until this above error is fixed. 

    Friday, March 15, 2019 8:51 PM
  • Yes , correct Matej. 

    I got it wrongly written SQL 2017, I will be restoring this on 2014 only :)

    Friday, March 15, 2019 9:38 PM
  • Okay, seems to be some kind of driver issue, is the Hardware/Storage Array card fully compatible/certified for Windows Server 2016? Check here: https://www.windowsservercatalog.com


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, March 15, 2019 9:42 PM
  • Hi Leon 

    DPMSync is throwing error and then DPM Console is crashing. 

    8. Restore the DPM database from the backup on the new server.

    >> you meant to say restore DPMDB from SQL Management studio console, and then run 'DPMSync.exe -Sync'

    from DPM Shell ?

    Monday, March 18, 2019 4:20 PM
  • Restore/attach in the SQL Server Management studio, then run the DPMSync.exe -Sync

    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, March 18, 2019 4:23 PM
  • Ok. Trying with that option. 
    Monday, March 18, 2019 4:46 PM
  • 'DPMSync.exe -restoreDB' command went well and then DpmSync.exe -Sync encountering following error


    I am suspecting 2 things can caused this issue (not sure)

    1. On the old server we had DPMDB in instance 'DPMSERVER\MSDPM2012' but now we are restoring to default instance 'DPMSERVER\MSSQLSERVER' Does it require instance with same name?

    2. So when I upgraded from DPM from 2012 R2 to DPM 1801 and then 1807 and took backup of DPMDB of 1807 (Which is I am restoring now). The application directory for DPM 1807 remained same which was used for DPM 2012 R2 because this was an upgrade and not fresh install. C:\Program Files\Microsoft System Center 2012 R2\DPM but now  with fresh install of DPM 1807 the default is changed to C:\Program Files\Microsoft System Center\DPM

    Probably that could lead DPMSync to fail !

    • Edited by V Jay Rana Monday, March 18, 2019 7:48 PM
    Monday, March 18, 2019 6:12 PM
  • Don't think the issue is related to SQL Instance. You got an error ID 453 DPM Failed to start, before you ran DPMSYNC -SYNC. I would say the issues is with the database name. Try the steps mentioned in this article under Resolution

    https://support.microsoft.com/en-us/help/2968666/error-id-470-when-you-run-the-dpmsync-restoredb-command-in-dpm


    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered"Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]


    Tuesday, March 19, 2019 6:51 AM
  • Agree with Matej, it sounds like the issue is related to the database name.

    Follow the link provided above and share the results here.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, March 19, 2019 7:01 AM
  • Thanks for this. I had already went through this link and commands in above screenshot were executed keeping instructions in mind which are provided in this support link. 

    DPM is back now but we lost too much data as after sync we saw many volumes were missing from disk. 

    Tuesday, March 19, 2019 9:18 PM