In this video guide, we will be covering how to perform a backup and restore of a Configuration Manager site. This guide will include using the default “Backup Site Server” site maintenance task as well as how you can use a native SQL Backup as another option. We will also cover how to backup additional items not included in the “Backup Site Server” such as the SCCMContentLib, WSUS Database, Source Files, and the WSUS Content folder.
Create an AfterBackup.bat in “Inboxes\Smsbkup.box” folder to also copy the SCCMContentLib, WSUS Content, and Source Package folder – https://youtu.be/puQyt3aJsmY?t=650
Review content downloaded (ADK, SQL, .Etc) to allow faster re-install of a site server and how to document the current site server details – https://youtu.be/puQyt3aJsmY?t=1259
Review how to set up a SQL maintenance plan to back up the WSUS DB as well as how to back up the SCCM Database if you prefer using a SQL Backup plan instead of the “Backup Site Server” maintenance task – https://youtu.be/puQyt3aJsmY?t=1523
Use custom task scheduler for copying SCCM content like SCCMContentLib, WSUS Content, Sources, CD.Latest if you decide to use a backup task not using the site backup maintenance task – https://youtu.be/puQyt3aJsmY?t=1895
Since the MP, DP, and SUP was using HTTPS on the Site Server, we need to request a new Web Server Cert and bind it to the Default Web Site and WSUS Website – https://youtu.be/puQyt3aJsmY?t=3391
After core setup completes, review sitecomp.log to validate the site system roles install successfully – https://youtu.be/puQyt3aJsmY?t=3820
Review accounts that need to have the password manually re-entered after the restore from C:\ConfigMgrPostRecoveryActions.html – https://youtu.be/puQyt3aJsmY?t=3895
Hi Justin, many thanks, your videos are a great resource, I have one question, when you install SQL server you don’t show the SQL collation that sccm needs as part of the install, i.e. The collation should be set to SQL_Latin1_General_CP1_CI_AS otherwise it fails the install, just a small tip for others and it’s in the exam.
cheers Dene
Hi Justin,
Great post, and easy to follow. I have some questions for you. I see how you restored the server. if you completely format all drives, will the restore bring it right back to where it was from the backup (permissions, folders, etc)? I have the SCCM DB on a remote SQL server, along with the WSUS DB. If I reinstall WSUS services, will it reattach itself back to the SUSDB after post config? I see that the customrestore.bat file needs run before installing SCCM. Just want to make sure I’m doing this right in my test environment. On the site server and recovery window during install of SCCM, would I do a reinstall of site server, or use the maintenance task backup, then skip DB recovery, since the DB is on a remote server? I do have the reporting point role and application catalog roles installed on the remote SQL server. I have some issues on my prod server where it needs to be brought down and rebuilt. That’s why I’m doing this in a test environment first. Thanks.
Hi Justin,
The video is great. I ran through the process in a quick test environment I spun up, but when I ran the install from the cd.latest folder, my recover a site option was grayed out. I am using SCCM tech preview to play around with.
Here’s what I have:
1) Remote SQL server, 1 primary
2) Did all steps to backup server, using both methods of maintenance task, and SQL backup
3) Left SQL alone, deleted the VM out of Hyper-V and deleted the extra drive
4) created the extra drive where installs were, created new VM
5) Named the new VM with the same name, after deleting it out of AD, then put in proper groups for container, and all other current settings (IP, etc.), reattached the extra drive
6) Set server up with all the necessary prerequisites and copied data back
7) Ran SCCM install from cd.latest and only option available was to install a new site
What did I miss here? Is it b/c it’s tech preview and the recover option isn’t suppose to work? Thanks for your response.
Hello Justin. Now that’s public service 🙂
In my case, I’m going to migrate to a more recent OS and from SQL 2012 to SQL 2019. In the video, which dates back to 2018, you mentioned that you were migrating WSUS to a more recent database, which worked, but which did not was recommended or not documented by Microsoft. Is this premise still true at the moment? If so, tell me if this is the right procedure to migrate WSUS:
1. before the backup, uninstall the “software update point” role;
2. do not recover the SUSDB database because when creating the service a new one will be created;
3. do not copy/restore the “X:\WSUS” folder;
4. after everything is restored, install the “software update point” role again and force synchronization.
Is this it or do you have any other advice?
Thanks
I'm Justin Chalfant! I'm the founder of
Thank you for the great job Justin. Great job!
Thanks for watching
Hi Justin, many thanks, your videos are a great resource, I have one question, when you install SQL server you don’t show the SQL collation that sccm needs as part of the install, i.e. The collation should be set to SQL_Latin1_General_CP1_CI_AS otherwise it fails the install, just a small tip for others and it’s in the exam.
cheers Dene
Thanks for the update, yeah, if you use a non EN-US ISO for the SQL install it may default to something else.
Thank you so much!
Thanks for watching!
Hi Justin,
Great post, and easy to follow. I have some questions for you. I see how you restored the server. if you completely format all drives, will the restore bring it right back to where it was from the backup (permissions, folders, etc)? I have the SCCM DB on a remote SQL server, along with the WSUS DB. If I reinstall WSUS services, will it reattach itself back to the SUSDB after post config? I see that the customrestore.bat file needs run before installing SCCM. Just want to make sure I’m doing this right in my test environment. On the site server and recovery window during install of SCCM, would I do a reinstall of site server, or use the maintenance task backup, then skip DB recovery, since the DB is on a remote server? I do have the reporting point role and application catalog roles installed on the remote SQL server. I have some issues on my prod server where it needs to be brought down and rebuilt. That’s why I’m doing this in a test environment first. Thanks.
Sorry for the delay did you figure this out?
Hi Justin,
The video is great. I ran through the process in a quick test environment I spun up, but when I ran the install from the cd.latest folder, my recover a site option was grayed out. I am using SCCM tech preview to play around with.
Here’s what I have:
1) Remote SQL server, 1 primary
2) Did all steps to backup server, using both methods of maintenance task, and SQL backup
3) Left SQL alone, deleted the VM out of Hyper-V and deleted the extra drive
4) created the extra drive where installs were, created new VM
5) Named the new VM with the same name, after deleting it out of AD, then put in proper groups for container, and all other current settings (IP, etc.), reattached the extra drive
6) Set server up with all the necessary prerequisites and copied data back
7) Ran SCCM install from cd.latest and only option available was to install a new site
What did I miss here? Is it b/c it’s tech preview and the recover option isn’t suppose to work? Thanks for your response.
Was SCCM fully uninstalled on the server? This option usually happens if SCCM regkeys and such are still detected.
Hello Justin,
Thank you for your video! I didn’t see you create any firewall rules on your new Server 2019 VM. Are these created during the SQL install now?
Thanks Again!
I didn’t really need any since it’s all local. The SQL ports are probably what you may need.
Hello Justin,
thank you for you useful resource and video.
Thanks for watching!
do you have copies of the .bat files?
I don’t think so, are you all set for that?
Hello Justin. Now that’s public service 🙂
In my case, I’m going to migrate to a more recent OS and from SQL 2012 to SQL 2019. In the video, which dates back to 2018, you mentioned that you were migrating WSUS to a more recent database, which worked, but which did not was recommended or not documented by Microsoft. Is this premise still true at the moment? If so, tell me if this is the right procedure to migrate WSUS:
1. before the backup, uninstall the “software update point” role;
2. do not recover the SUSDB database because when creating the service a new one will be created;
3. do not copy/restore the “X:\WSUS” folder;
4. after everything is restored, install the “software update point” role again and force synchronization.
Is this it or do you have any other advice?
Thanks