in-place upgrade of RR server's OS - 2012 to 2016

So, I made a mistake of making one of my exchange DB's live on an ReFS drive.   RR server is on 2012r2 which can't complete Mountability checks because it can't mount the filesystem!!    So, can I in-place upgrade the server to 2016?  I'm guessing I probably can.  something like, stop/disable RR service... and maybe more services, then run upgrade OS?

edit; I WON'T go to Server 2019, and my Exchange is on Server 2016, so looks like I'm good to backup ReFS.    (ReFS still not supported on 2019)

Parents
  • I assume by RR server you mean the Core, if yes the next question is this an appliance or a regular server? if the latter, then you can proceed to upgrade the core by just stopping the core service and upgrading the OS. If on the other hand this is an appliance and the core version is 6.2.1 or lower then I recommend you to upgrade the core first to 6.4 this will help to remove the Appliance OS-specific limitations and then proceed to upgrade the OS. 

    Hope that helps.

  • I'm getting a Failed to start some services after upgrade.    It's the MongoDB connection.   I suspect something with changed .net version.   

    https://support.quest.com/rapid-recovery/kb/313752/mongodb-service-is-disconnected

    pretty sure it's a direct match to the link above.  I will update .net and report back.

    EDIT:  installed .net 4.8 standalone after upgrade to Server 2016.   all good!    

    EDIT: upgraded both target and source OS. (2012 to 2016),  key was to install .net 4.8 after upgrade finishes. (then run updates)  updates failed a few times... but eventually worked.  probably a normal Server OS upgrading issue.  

    now on to see if I can mount check that ReFS exchange DB.

Reply
  • I'm getting a Failed to start some services after upgrade.    It's the MongoDB connection.   I suspect something with changed .net version.   

    https://support.quest.com/rapid-recovery/kb/313752/mongodb-service-is-disconnected

    pretty sure it's a direct match to the link above.  I will update .net and report back.

    EDIT:  installed .net 4.8 standalone after upgrade to Server 2016.   all good!    

    EDIT: upgraded both target and source OS. (2012 to 2016),  key was to install .net 4.8 after upgrade finishes. (then run updates)  updates failed a few times... but eventually worked.  probably a normal Server OS upgrading issue.  

    now on to see if I can mount check that ReFS exchange DB.

Children
No Data