First published on TECHNET on Aug 16, 2017
Authored by Danny Guillory
Now that we have gotten Configuration Manager 2012 R2 to a point where we can restore the backup to supported version of a higher Operating System and the same SQL version (2014) we can go through the next phase.
As stated before we will be restoring Configuration Manager 2012 R2 to the below specifications
Backup Configuration Manager 2012 R2 with the maintenance task built into Configuration Manager
2 Key Important things to take note of:
Now that the server is up and patched let's go through the restore process.
Make sure the server has the Correct Version of SQL 2014 (Remember from the last step we upgraded SQL Server 2008 R2 to SQL Server 2014).
SQL Server Versions
Copy the extracted & HOTFIXED media to the server and open the Splash Application.
When the Splash application opens click install.
Right after "Install" you should be presented with the next few screens throughout the restore process.
This is where your presented with the restore option.
In this step, I am referencing the backup location from my maintenance task. I copied the backup from the share and back to the new server that I will be restoring configuration manager to.
Select Recover Primary Site.
Yeap, in my case I am using the evaluation.
Accept the Licensing Terms.
I predownloaded the files. Here I am just pointing to the location. If you haven't downloaded the files then go ahead and chose the 1 st option and download the files to a location.
This section is prepopulated, though you could change the installed path if desired. in this scenario, I will not be changing anything.
Prepopulated with my database server, name, and Service Broker Port.
Prepopulated with SQL Server data file and transaction log path.
And the restore is complete. Now real world . I like to let this cook for a day are two. Check your site status and components, use the product, make sure it is fully functional before upgrading to Configuration Manager Current Branch. In some cases, after you restore, you might need to apply CU's, are other performance based tweaks, but your Configuration Manager 2012 R2 is restored to a Windows Server 2012 R2 with SQL Server 2014.
Don't forget the POST restore processes as documented here .
Key things to remember after the restore:
Thanks for your time and attentiveness.
That is it for Part 2. Job well Done. 1 more step to go.
In part 3 we will in place upgrade our Configuration Manager 2012 R2 to our final resting place of 1706
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.