Everyone (hopefully) is aware that the SCCM database needs to be backed up. And, that there a number of other components that need to be backed up in order to have everything on hand in case there is a need to do a full recovery. Note: search my blog for native SQL backup steps.
Obviously, if you have a third party backup software product in place, you are probably OK.
Here are the key parts:
Report Server Databases
- ReportServer DB
- ReportServerTempDB DB
Reporting Services encryption keys using the SQL Server Reporting Services Configuration Manager.
Report Designer files – Report Definition (.RDL), Report Model (.SMDL), Shared Data Sources (.RDS), Data Views (.DV), Data Sources (.DS), Report Server Project (.RPTPROJ), and Report Solutions (.SLN)
Report Services Files located in [SQL Server Installation Direcotry]\MSRS14.MSSQLSERVER\Reporting Services\ReportServer
- Web.config for both the Report Server and Report Manager ASP.NET applications
- Machine.config for ASP.NET
WSUS – Backup folder containing WSUS data
- Current branch
Backup Content Files
Backup Package Source Files
The content library in Configuration Manager is the location where all content files are stored for software updates, applications, operating system deployment, and so on. The content library is located on the site server and each distribution point. The Backup Site Server maintenance task does not include a backup for the content library or the package source files. When a site server fails, the information about the content library files is restored to the site database, but you must restore the content library and package source files on the site server.
- Content library: The content library must be restored before you can redistribute content to distribution points. When you start content redistribution, Configuration Manager copies the files from the content library on the site server to the distribution points. The content library for the site server is in the SCCMContentLib folder, which is typically located on the drive with the most free disk space at the time that the site installed. For more information about the content library, see Introduction to Content Management in Configuration Manager.
- Package source files: The package source files must be restored before you can update content on distribution points. When you start a content update, Configuration Manager copies new or modified files from the package source to the content library, which in turn copies the files to associated distribution points. You can run the following query in SQL Server to find the package source location for all packages and applications:
SELECT * FROM v_Package
You can identify the package source site by looking at the first three characters of the package ID. For example, if the package ID is CEN00001, the site code for the source site is CEN. When you restore the package source files, they must be restored to the same location in which they were before the failure. For more information about updating content, see the Update Content on Distribution Points section in the Operations and Maintenance for Content Management in Configuration Manager topic.
Important: Verify that you include both the content library and package source locations in your file system backup for the site server.
Back Up Custom Software Updates
On the computer that runs Updates Publisher, browse the Updates Publisher 2011 database file (Scupdb.sdf) in %USERPROFILE%\AppData\Local\Microsoft\System Center Updates Publisher 2011\5.00.1727.0000\. There is a different database file for each user that runs Updates Publisher 2011.
Post Recovery Tasks
- The recovery report is saved to C:\ConfigMgrPostRecoveryActions.html
- Re-enter user account passwords
- Re-enter Sideloading Keys
- Recreate Microsoft Intune Subscription
- Configure SSL for Site System Roles that use IIS
- Reinstall hotfixes
- Recover Custom Reports
- Recover Content Files
- Recover Custom Software Updates (SCUP)
- Recover USMT
- Update Certificates for Cloud DP’s
- Reprovision Intel AMT-based computers
SCCM Secondary Site
- How to backup
- Step 1: No need!
- Recover Secondary Site
- Use the Recover Secondary Site action from the Sites node