Copy the following PowerShell command into the clipboard ( Note: modify paths as needed to match your environment, should be one line) For Type: select Operating system (CmdExec)Ĭ. For the Job Step Properties, perform the following steps:ī. Using SQL Server Management Studio, expand the SQL Server Agent node. You will start by creating an SQL Server Agent task to back up the cd.latest folder.ġ. How to backup ConfigMgr using SQL Server Agent tasks Always test the restore process in a lab prior to actual use! Keep fingers out of the cage and do not feed the animals. (please see the references section for more information). I’ve assembled the following step by step guide to create a backup task for SQL Server to back up the core items you need for a successful recovery.Ĭaveat(s) : This guide will not cover other files that you will need for a complete recovery OSD images, source for packages/applications, drivers, etc. TIP : If you need to perform any of the above steps, you will need to copy the contents of CD.Latest to a path outside the Configuration Manager installation to get ALL of the available options. Expand an existing site – if you need to turn your primary site into a multi-site hierarch, you will need to use CD.Latest to install the CAS.Child primary site – if you need to re-install a child primary site in a hierarchy you must use the CD.Latest folder that matches the CAS version.If you need to recover a site and do not have the contents of CD.Latest folder – you cannot recover the site! Backup and Recovery – if you need to re-install a site and want it to be the same build number, the files contained will be an exact version match.
The source files for CD.Latest are used as follows: Why do I care about the CD.Latest folder?Īs updates are delivered to ConfigMgr, updates to the ConfigMgr binaries are updated in the CD.Latest folder as well. Since ConfigMgr (Current Branch) build 1511 was introduced, in addition to SQL databases, the CD.Latest folder (located in the installation path for Configuration Manager), also needs to be backed up.
– More granular control over scheduling of backup time – Can send email notifications on completion (or failure) – ConfigMgr services continue to run while backup is in motion
– Use database compression (the space savings can be huge) – Backup databases other than ConfigMgr (ReportServer, ReportServerTempdb and SUSDB) Here is my list of why native SQL Server backups are superior to the built-in ConfigMgr maintenance task: SQL backups are the preferred technique for backing up the ConfigMgr for a number of reasons. As previously documented, using native SQL Server backup for ConfigMgr recovery has been supported since CM 2012 Sp1 and later.
0 kommentar(er)
