Adding Databases to the Default Backup Task

I am using a Single Primary Site Server with WSUS, Reporting Services and Security Compliance Manager installed on it. Co-located SQL server as well. Each of these additional pieces of software has its own database.

I see the following in smsbkup.ctl:

# DO NOT MODIFY - Default SQL Data backup tasks - DO NOT MODIFY:#
#----------------------------------------------------------------------
sitedbdump  %SITE_DB_NAME%            %SITE_DB_SERVER_DEST%\SMSbkSQLSiteDB.dat

As this screams "DO NOT MODIFY" I am left thinking I cannot add the ReportServer, ReportServerTempDB, SUSDB, and XTrans databases to the list of databases being backed up by this facility.

Is there a way to add these databases to the default backup task in SCCM 2012?


  • Edited by SecOpsGuy 15 hours 12 minutes ago Formatting
March 27th, 2015 12:37pm

Check out the info here: https://technet.microsoft.com/en-us/library/gg712697.aspx#BKMK_BackupMaintenanceTask  It says you can modify that file, but I have never done it before.  I rely on SQL backups for backing up the other databases as well as the ConfigMgr DB.

Using standard SQL Backups for ConfigMgr works.  In fact, some prefer that method:

http://myitforum.com/myitforumwp/2013/06/07/sql-server-backup-recommendations-for-configuration-manager/

Jeff

Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 12:49pm

Thanks for the reply, Jeff.

I have tried altering smsbkup.ctl and adding databases to no avail. Shocking to find out after the file explicitly tells you not to edit the section containing the site database. ;)

Looking at the second link you provided points out the glaring hole in the default task. No compression. That's absolute weak-sauce.

As I have an all-in-one Primary Site Server, I may just implement file-system backups combined with the SQL databases following shortly after the file-system job has completed. This seems like it would catch everything on the list and then some.


  • Edited by SecOpsGuy 14 hours 47 minutes ago
March 27th, 2015 1:02pm

Using a pure SQL backup is what I recommend. The built-in backup site maintenance task does a lot of useless stuff as well as pause site services and (as you've pointed out) does not use compression. It also, by default, overwrites previous backups.
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2015 1:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics