SCCM Backup procedure
Below procedure helps to understand steps involved in SCCM backup (Site server and SQL database on the same server), how many status message gets generated? How many components get backed up?
Step-1 SMS site backup service 4.00 gets started.
Step-2 Status message 500 gets generated
Step-3 Locate the Backupdir, Installation RootDir and Site SQL directories. If backup location and installation directory on same location it through below warning @smsbkup.log
Warning: Backup location and the sms data (installation directory) are on the same volume. Sms Backup creates snapshot of the volume using VSS services and then copies the data to the backup location. It is advisable to have the backup location on a different volume (different than the one that has SMS data and SMS database files), so that the writes to the volume is minimal when the volume snapshot is active.
Step-4 Checks the status of SQL writer service, Locate the SQL data file location Site and SQL Backup Location
Step-5 Status message 5055 gets generated
Step-6 VSS gets initialized
Step-7 Below are the components which gets backed up during backup process
*<ConfigMgr Installation Directory>\*INBOXES
<ConfigMgr Installation Directory>\LOGS\
<ConfigMgr Installation Directory>\DATA\
<ConfigMgr Installation Directory>\SRVACCT\
<ConfigMgr Installation Directory>\BackupTemp\SMSbkSiteRegNAL.dat
<ConfigMgr Installation Directory>\BackupTemp\SMSbkSiteRegSMS.dat
*<sitecode>*Backup\SiteDBServer\SMSbkSQLDBsite.dat
<MSSQL Installation Directory>\DATASMS_<Sitecode>.mdf
<MSSQL Installation Directory>\DATASMS_<Sitecode>_log.LDF
Step-8 Starts cleaning and preparing the backup location.
Step-9 Starts to create the snapshot set and finished it.
Step-10 Status message 5056 gets generated
Step-11 Copies all above mentioned components from \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy288\ to <sitecode>Backup\Siteserver and <Sitecode>Backup\SiteDBServer
Step-12 Successfully creates the backup metadata file in backup directory.
Step-13 Status message 5057 gets generated
Step-14 AFTERBACKUP.BAT will be started if available in its predefined location (if it configured to take back up other things)
Step-15 Status message 5035, 5042, 502 and 501 gets generated.
Note: All above things will get logged on SMSBkup.log
Message ID |
Description |
500 |
This component started. |
5055 |
SMS Site Backup task is starting. This task will interact with the windows VSS services and the appropriate writers to create a volume snapshot and then back up the required files to the specified destination. |
5056 |
SMS Site Backup is starting to copy the files from the snapshot. |
5057 |
SMS Site Backup has successfully completed copying the files from the snapshot. |
5035 |
SMS Site Backup completed successfully with zero errors but still there could be some warnings. |
5042 |
SMS Site Backup did not find command file "afterbackup.bat" at its predefined location. Command file "afterbackup.bat" not launched. |
502 |
This component stopped. |
501 |
This component was signalled to stop by an administrator or the operating system. The component will complete any processing it is doing and stop at a safe point in time. If the component or this computer is very busy, it may take several minutes for the component to stop. |
You can check the successful backup status by running below query on SCCM database
select stat.machinename,stat.sitecode,max(stat.time) as "Latest Successful Backup"
from v_StatusMessage stat
join v_site sites on sites.servername=stat.machinename
where stat.messageid ='5035' and sites.type=2
group by stat.sitecode,stat.machinename
order by "Latest Successful Backup" desc