none
Wiping DPM 2016 server to upgrade OS to 2019 and dpm 2019, recover protection groups? RRS feed

  • Question

  • I have an OS (2016 1607) that needs updated to 2019 server, but the in place upgrade fails with an error about second boot failure.

    I needed to get to 2019 OS to install dpm 2019 because the interim 2016 server cant upgrade, no pathway.

    Whats the method to just do a clean install and get to 2019 and recover the entire protection group, so it doesnt need to be recreated?

    And also, should i first go to 2016 DPM, recover things then upgrade to 2019, or just jump to 2019.

    I'm assuming i can just install dpm 2019, it puts the sql instance back on the server, once up bare bones, restore the db somehow then run a few commands to reallocate replica?

    Thanks in advance


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

    Tuesday, November 26, 2019 3:59 PM

Answers

  • Yes, I've outlined the steps for you below:

    1. Reinstall the DPM server with Windows Server 2019, keep the same name and IP address.

    2. Install SQL Server 2014.

    3. Install DPM 2016.

    4. Install the latest update rollup 8 for DPM 2016.

    5. Upgrade SQL Server 2014 to SQL Server 2016/2017.

    6. Upgrade DPM 2016 to DPM 2019.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by techfun89 Tuesday, November 26, 2019 9:34 PM
    Tuesday, November 26, 2019 9:19 PM

All replies

  • Hi,

    A clean install is the recommended approach anyways instead of an in-place upgrade.

    You can uninstall DPM with the retain database option, this means you will keep everything, make sure to backup the database if it's located on the same server as DPM 2016, then copy it to another server/share safely.

    Reinstall the server to Windows Server 2019 with the same name and IP address, then it's safest to reinstall the same DPM version (DPM 2016 in your case), and choose existing database.

    If you have the DPM database located on the same server, you'll need to reinstall SQL Server as well, install it to the same version as used previously to avoid any problems.

    You can use the procedure in the link below to restore the DPM database:
    Restore and synchronize the DPM database with DPMSync

    Install the latest Update Rollup (Update Rollup 8 as of writing this), then upgrade DPM 2016 to DPM 2019.

    If you're using an SQL Server version that is below SQL Server 2016, you will need to upgrade that as well to minimum SQL Server 2016 or 2017.


    I have written a step-by-step guide on how to upgrade to DPM 2019:
    DPM Step-By-Step: upgrading to v2019

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, November 26, 2019 4:19 PM
  • Hi,

    A clean install is the recommended approach anyways instead of an in-place upgrade.

    You can uninstall DPM with the retain database option, this means you will keep everything, make sure to backup the database if it's located on the same server as DPM 2016, then copy it to another server/share safely.

    Reinstall the server to Windows Server 2019 with the same name and IP address, then it's safest to reinstall the same DPM version (DPM 2016 in your case), and choose existing database.

    If you have the DPM database located on the same server, you'll need to reinstall SQL Server as well, install it to the same version as used previously to avoid any problems.

    You can use the procedure in the link below to restore the DPM database:
    Restore and synchronize the DPM database with DPMSync

    Install the latest Update Rollup (Update Rollup 8 as of writing this), then upgrade DPM 2016 to DPM 2019.

    If you're using an SQL Server version that is below SQL Server 2016, you will need to upgrade that as well to minimum SQL Server 2016 or 2017.


    I have written a step-by-step guide on how to upgrade to DPM 2019:
    DPM Step-By-Step: upgrading to v2019

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thanks for this.

    When i originally installed dpm 2016, i pointed it to D: for some of the install apparently.

    In there are folders like dpm\volumes\replica  or dpm\volumes\shadow copy  or dpm\datasources etc

    Are those going to be needed, or do i rename this folder and start clean with the fresh install of dpm 2016 only restoring the db and doing the reallocate?


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

    Tuesday, November 26, 2019 9:00 PM
  • You don't have to worry about those folders, everything you need to worry about is stored in the DPM database.

    To make things simple, try to reinstall your new Windows Server 2019 that will host your new DPM as identical as the old server.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, November 26, 2019 9:06 PM
  • You don't have to worry about those folders, everything you need to worry about is stored in the DPM database.

    To make things simple, try to reinstall your new Windows Server 2019 that will host your new DPM as identical as the old server.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Ok good to know. Thanks

    As far as sql install goes, i guess i have to install sql server 2014 for now to get dpm 2016 back and running (the one that was there)  I think it was standard not sql express, though i see 2016 and later are supported with the updated 2016.


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



    • Edited by techfun89 Tuesday, November 26, 2019 9:17 PM
    Tuesday, November 26, 2019 9:14 PM
  • Yes, I've outlined the steps for you below:

    1. Reinstall the DPM server with Windows Server 2019, keep the same name and IP address.

    2. Install SQL Server 2014.

    3. Install DPM 2016.

    4. Install the latest update rollup 8 for DPM 2016.

    5. Upgrade SQL Server 2014 to SQL Server 2016/2017.

    6. Upgrade DPM 2016 to DPM 2019.


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by techfun89 Tuesday, November 26, 2019 9:34 PM
    Tuesday, November 26, 2019 9:19 PM
  • Yes, I've outlined the steps for you below:

    1. Reinstall the DPM server with Windows Server 2019, keep the same name and IP address.

    2. Install SQL Server 2014.

    3. Install DPM 2016.

    4. Install the latest update rollup 8 for DPM 2016.

    5. Upgrade SQL Server 2014 to SQL Server 2016/2017.

    6. Upgrade DPM 2016 to DPM 2019.


    Blog: https://thesystemcenterblog.com LinkedIn:

    I went through 1-4.

    I didnt get to the restore db portion because the command was throwing a mismatch on version, 

    dpmsync -restoreDB -DbLoc d:\dpmdb.bak

    strangely this error: 

    Error ID: 455
    Failed to attach database [DPMDB_BACKUP02] at location [d:\dpmdb.bak] to SQL server. Make sure that the SQL server services are running and you are restoring a valid DPM database backup.

    Detailed Error: The database was backed up on a server running version 13.00.5492. That version is incompatible with this server, which is running version 12.00.6024. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
    RESTORE DATABASE is terminating abnormally.

    Thats what lead me to try to open the console (maybe since i didnt open it after the fresh install)

    But when i do that i get "unable to connect to backup02" verify the dpm service is running on this computer (it is)

    Any thoughts?

    Thanks


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

    Tuesday, November 26, 2019 10:53 PM
  • Actually, i think that error meant sql server 2016 was already on there, not that the dpm was 13.x

    Probably also why it wont launch


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

    Tuesday, November 26, 2019 10:58 PM
  • The error refers to the SQL Server version, it will not complain of the Windows Server version.

    Are you sure you were using SQL Server 2014 for your DPM 2016 environment? According to this log, the backup was done from SQL Server 2016 SP2.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, November 26, 2019 11:00 PM
  • The error refers to the SQL Server version, it will not complain of the Windows Server version.

    Are you sure you were using SQL Server 2014 for your DPM 2016 environment? According to this log, the backup was done from SQL Server 2016 SP2.


    Blog: https://thesystemcenterblog.com LinkedIn:

    I updated to sql sp2, but get this message on trying the command now:

    Detailed Error: Directory lookup for the file "D:\Program Files\Microsoft SQL Server\MSSQL13.BACKUP02\MSSQL\DATA\MSDPM2012$DPMDB_BACKUP02new.mdf" failed with the operating system error 3(The system cannot find the path specified.).

    File 'MSDPM2012$DPMDB_BACKUP02_dat' cannot be restored to 'D:\Program Files\Microsoft SQL Server\MSSQL13.BACKUP02\MSSQL\DATA\MSDPM2012$DPMDB_BACKUP02new.mdf'. Use WITH MOVE to identify a valid location for the file.

    Directory lookup for the file "D:\Program Files\Microsoft SQL Server\MSSQL13.BACKUP02\MSSQL\DATA\MSDPM2012$DPMDB_BACKUP02new_log.ldf" failed with the operating system error 3(The system cannot find the path specified.).
    File 'MSDPM2012$DPMDB_BACKUP02Log_dat' cannot be restored to 'D:\Program Files\Microsoft SQL Server\MSSQL13.BACKUP02\MSSQL\DATA\MSDPM2012$DPMDB_BACKUP02new_log.ldf'. Use WITH MOVE to identify a valid location for the file.
    Problems were identified while planning for the RESTORE statement. Previous messages provide details.
    RESTORE DATABASE is terminating abnormally.


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

    Wednesday, November 27, 2019 2:55 AM
  • The folder pathing of the new instance is slightly different, hence the error i believe.


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

    Wednesday, November 27, 2019 3:00 AM
  • I believe i got around this with some file trickery and using the sql management studio. 

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

    Wednesday, November 27, 2019 3:24 AM
  • i initiated the dpmsync command after restoring the database and received this error:

    Unhandled Exception: System.Runtime.InteropServices.COMException: Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CProxyUtils.HandleErrors(Int32 hr, tagSAFEARRAY* exceptionResult)
       at Microsoft.Internal.EnterpriseStorage.Dls.Engine.RestoreDbSyncServicesProxy.RestoreDbSynchronize(Boolean reallocateReplica, Boolean* isExternalVolumeMissing)
       at Microsoft.Internal.EnterpriseStorage.Dls.RestoreDbSync.RestoreDbSync.SyncFunction(Boolean reallocateReplica, Boolean& isExternalVolumeMissing)
       at Microsoft.Internal.EnterpriseStorage.Dls.RestoreDbSync.RestoreDbSync.Main(String[] args)


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

    Wednesday, November 27, 2019 3:29 AM
  • I decided to run the dpm sync command to restore the db, then ran -sync, this time i get this error:

    Error ID: 33507
    DPM could not execute a WMI query. The query either returned an error or an empty result. Retry the operation


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

    Wednesday, November 27, 2019 3:49 AM
  • It's difficult to say if you didn't follow the steps precisely, as any workaround or altering will most likely affect the process.

    It is important that you use the same SQL Server version with same Service Pack, the same DPM version with same Update Rollup.

    It is possible to restore the database by using the SQL Server Management Studio, and then run the DPMSync -Sync command.

    --------------------------------------------

    For the error ID 33507 you can try the following:

    1. Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TmFilter\Parameters" using the Windows Registry Editor.

    2. Add a DWORD (32 Bit) called BypassDPMfilter with a value of 1.

    3. Restart the affected machine.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, November 27, 2019 8:24 AM
  • It's difficult to say if you didn't follow the steps precisely, as any workaround or altering will most likely affect the process.

    It is important that you use the same SQL Server version with same Service Pack, the same DPM version with same Update Rollup.

    It is possible to restore the database by using the SQL Server Management Studio, and then run the DPMSync -Sync command.

    --------------------------------------------

    For the error ID 33507 you can try the following:

    1. Navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TmFilter\Parameters" using the Windows Registry Editor.

    2. Add a DWORD (32 Bit) called BypassDPMfilter with a value of 1.

    3. Restart the affected machine.


    Blog: https://thesystemcenterblog.com LinkedIn:

    I followed the steps pretty closely.  Strangely, after rerunning the restoredb command and sync etc and a reboot, all errors vanished and i'm back at least to where i was with the situation of 2016.  Now i can work on the upgrade to 2019 dpm

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

    Wednesday, November 27, 2019 3:18 PM
  • Great to hear that!

    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, November 27, 2019 3:23 PM