You are browsing the archive for backup.

Configmgr 2007 / 2012 : Using AfterBackup.bat to Daily Archive a Backup Snapshot

8:23 am in backup, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr 2012, ConfigMgr 2012 SP1, ConfigMgr SP2, configmgr2007, ConfigMgr2007 R3, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, SCCM 2012, SCCM 2012 SP1, sccm2007 by Kenny Buntinx [MVP]


To ensure that a recent backup snapshot is always available, it is recommended that you archive the backup snapshot every time the SMS backup task completes a backup cycle. The standard backup task overwrites the previous created backup by default .

To accomplish that, you can use the AfterBackup.bat file to run a third-party tool (7Zip) that automatically archives the backup snapshot every time you back up your site. After successfully backing up the site, the SMS backup task runs the AfterBackup.bat batch file. The AfterBackup.bat file integrates the archive and the backup operations, thus ensuring that every new backup snapshot is archived.

All this script does is move the backup folder to a folder named the day of the week. If the destination already exists, then it is deleted first. Resulting in 7 days of backup or more

To use the AfterBackup.bat file

  1. Prepare an ASCII file with commands that archive your backup snapshot, or that perform any other post-backup tasks your site requires.
  2. Name the file "AfterBackup.bat" and save it in the SMS\inboxes\ folder. Now, every time the backup task runs successfully, it will run the AfterBackup.bat file.
  3. Every time after the AfterBackup.bat file archives the site’s backup snapshot, store that archive in a secure location.

Here is an Afterbackup.bat file that will make a daily backup of ConfigMgr Backup, so that you have a full week of backups.

  1. Place the file in the following location :


  1. Make sure you copy the 7zip (command line executable) in the root of the directory . When backup is daily ran , you should see this .



Hope it Helps ,

Kenny Buntinx

DPM 2012 : Sharepoint 2010 en ILM (Item Level Recovery) Running on SQL Cluster fails with :”DPM was unable to attach the database to the SQL Instance SERVER\INSTANCE”

1:47 pm in backup, dpm, DPM 2012 by Kenny Buntinx [MVP]


At my customer today , we were upon the first tests on our DPM 2012 platform protecting a SP 2010 farm. The protection groups are working perfectly , however, when trying to recover a Sharepoint item (a jpg file) we are facing some problems. here is a sample recovery session:

  • start the recovery wizard on the document
  • specify the SQL cluster instance as the staging SQL server
  • specify a temporary folder on the SQL cluster, which is already included in the cluster dependencies
  • specify a temporary folder on the WFE.

The recovery process ends with failure, displaying this warning on the DPM console: "DPM was unable to attach the database to the SQL Instance SERVER\INSTANCE. Cannot use file \\DPMSERVER\WSSILRShare_{guid}\local-replica-path-to-mdf for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the sql server does not have a dependency on it (ID 32000 Details :Unknown)"


Solution :

******************The answer below is not right for the error code – I am still investigating why this is not fixed *******************************

******************I will update when the right solution is fixed *******************************

There is a known limitation when using optimized item level recovery (ILR) for Sharepoint 2010 that uses clustered SQL Servers. The workaround is to perform a non-optimized recovery.  Please add the following registry key and try a new recovery.

To disable Optimized ILR completely, use the following registry key on the DPM 2012 server:

Key HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\SharePoint
Value: DisableOptimizedILR

******************The answer below is not right for the error code – I am still investigating why this is not fixed *******************************

Hope it Helps,

Kenny Buntinx