Jump to content




anyweb

how can I backup my SCCM server



Recommended Posts

This guide assumes you are backing up an SCCM Primary Site Server, backing up a Secondary Site Server is not supported.

 

You should always refer to Technet for best practise advise for troubleshooting, setup and maintenance of your SCCM server(s). this guide is provided as-is to help you understand the backup functionality within SCCM better and to get it working in your LAB environment, for proper guidance, refer to Technet.

 

 

 

Create a folder for storing the data

 

In Windows Explorer create a folder (or share on another computer *recommended) for storing our backup data

 

eg: D:\sources\backup or \\server\someshare

 

 

 

 

Create a scheduled backup task

 

To create a scheduled backup task, expand the Site Settings node and expand the Site Maintenance node, click on Tasks.

 

backup.JPG

 

Right click on the Backup ConfigMgr Site Server task and choose properties. Set your schedule values and enable the task.

 

schedule.JPG

 

 

 

What Gets Backed up ?

 

According to Microsoft the following gets backed up:

 

What Gets Backed Up

In order to completely back up a Configuration Manager 2007 site server, the following data needs to be included in the backup:

 

* The Configuration Manager site database (SQL Server database)

* Configuration Manager installation directory on the site server

* Master site control file (.\Inboxes\Sitectrl.box\Sitectrl.ct0)

* SMS and NAL registry keys on the site server

 

 

 

What Does Not Get Backed Up

 

Some Configuration Manager 2007 site systems contain site data that is easily recreated if the site fails and are not backed up during the site backup process. For example, there is no need to backup data from site systems such as standard and branch distribution points, management points, reporting points, and server locator points. These site systems can easily be reinstalled by the site server if they fail.The Backup ConfigMgr Site Server maintenance task backs up logs located in the Configuration Manager logs directory, but some Configuration Manager 2007 site systems write logs in other locations and are not backed up by the Backup ConfigMgr Site Server maintenance task. You should plan an alternative method to back up these logs if required.It is not necessary to back up the SQL Server master database when backing up the Configuration Manager site database. The Backup ConfigMgr Site Server maintenance task backs up all of the required information for restoring the site from the SQL Server hosting the site database as part of the backup process. The original SQL Server master database is not required for restoring the site database on a new SQL database server.Backing up Configuration Manager 2007 clients are not backed up as part of the site backup process for the following reasons:

 

* To properly back up a Configuration Manager client, the client services must be stopped. However, there is no reliable way to stop and start the client services. Stopping and starting the client services can potentially corrupt the data on the client�s disk or in the backup snapshot.

* Clients are too numerous. It is neither practical nor beneficial to backup and restore the clients assigned to a site.

* The effect of losing client data is relatively small.

 

 

What the above doesn't tell you is that you need to backup the following (using whatever other traditional backup method you have).

 

Using traditional backup routines (like DPM), backup the Following folders (assuming you have all your packages on D:\ if not, backup the corresponding folders on C:\ etc:-

 

SMSSIG$

SMSPKGSIG

SMSPKGD$

 

In other words, if you want everything backed up, you will need to backup ALL packages on ALL distribution Points you have setup, including the Package source folders using traditional backup methods (DPM etc).

 

 

How can I Restore my site Backup

 

You can restore your site backup using the Site Repair wizard, either by running splash.hta from the SCCM 2007 DVD or by selecting it from the Start Menu.

 

site repair.JPG

 

How can I Restore Packages

 

To restore packages you can use preloadpkgonsite.exe

 

 

 

How can I manually start a backup ?

 

Open up Administrative tools/Services and locate a service called SMS_SITE_BACKUP, select the service, right click and choose Start.

 

start manual backup.jpg

 

At this point the SMS site backup should start, refer to the smsbkup.log file (located in D:\Program Files (x86)\Microsoft Configuration Manager\Logs) for details such as

 

SMS site backup service 4.00 started.

 

and

 

04/30/09 17:52:28 - starting backup.

 

and of course you'll want to see that it completed successfully

 

04/30/09 18:02:56 - backup completed.

 

 

 

Some Backup related reading

 

3 Things I learnt about SCCM backups

 

http://myitforum.com...cm-backups.aspx

 

Site Restore Step by Step

 

http://myitforum.com/myitforumwp/2012/06/07/configmgr-sccm-recovery-restore-site-repair-wizard-step-by-step-guide/

 

Volume shadow copy service

 

If you want to find out how ConfigMgr uses the Volume shadow copy service see here

  • Like 1

Share this post


Link to post
Share on other sites


This guide assumes you are backing up an SCCM Primary Site Server, backing up a Secondary Site Server is not supported.

 

You should always refer to Technet for best practise advise for troubleshooting, setup and maintenance of your SCCM server(s). this guide is provided as-is to help you understand the backup functionality within SCCM better and to get it working in your LAB environment, for proper guidance, refer to Technet.

 

 

 

Create a folder for storing the data

 

In Windows Explorer create a folder for storing our backup data

 

eg: D:\sources\backup

 

 

 

Create a scheduled backup task

 

To create a scheduled backup task, expand the Site Settings node and expand the Site Maintenance node, click on Tasks.

 

post-1-1237467498_thumb.jpg

 

Right click on the Backup ConfigMgr Site Server task and choose properties. Set your schedule values and enable the task.

 

post-1-1237467599_thumb.jpg

 

 

 

What Gets Backed up ?

 

According to Microsoft the following gets backed up:

 

 

 

 

 

What Does Not Get Backed Up

 

 

 

 

What the above doesn't tell you is that you need to backup the following (using whatever other traditional backup method you have).

 

Using traditional backup routines (like DPM), backup the Following folders (assuming you have all your packages on D:\ if not, backup the corresponding folders on C:\ etc:-

 

SMSSIG$

SMSPKGSIG

SMSPKGD$

 

In other words, if you want everything backed up, you will need to backup ALL packages on ALL distribution Points you have setup, including the Package source folders using traditional backup methods (DPM etc).

 

 

How can I Restore my site Backup

 

You can restore your site backup using the Site Repair wizard, either by running splash.hta from the SCCM 2007 DVD or by selecting it from the Start Menu.

 

post-1-12730601579837_thumb.jpg

 

How can I Restore Packages

 

To restore packages you can use preloadpkgonsite.exe

 

 

 

How can I manually start a backup ?

 

Open up Administrative tools/Services and locate a service called SMS_SITE_BACKUP, select the service, right click and choose Start.

 

post-1-12726509827719_thumb.jpg

 

At this point the SMS site backup should start, refer to the smsbkup.log file (located in D:\Program Files (x86)\Microsoft Configuration Manager\Logs) for details such as

 

 

 

and

 

 

 

and of course you'll want to see that it completed successfully

 

 

 

 

 

Some Backup related reading

 

3 Things I learnt about SCCM backups

 

http://myitforum.com/cs2/blogs/scassells/archive/2009/11/16/three-things-i-learned-about-sccm-backups.aspx

 

Volume shadow copy service

 

If you want to find out how ConfigMgr uses the Volume shadow copy service see here

 

Hello,

 

After setting this up it seems the Task: "Backup Configmgr Site Server" does not start by itself.

Site Status > Component Status > SMS_SITE_BACKUP is in Manual Statup Type

The SMS_SITE_BACKUP service is not running and it is set to "Manual"

 

Should it be automatically changed to Scheduled and the service Started or should it be done manually?

 

Thanks,

DOm

  • Like 1

Share this post


Link to post
Share on other sites

it will remain set to Manual, but your scheduled backup will take place, verify by looking at the backup logs and check the location of where you told it to backup to

Share this post


Link to post
Share on other sites

How I can restore a backup of site server to new hardware, on my network I have:

01 Site Server

01 Reporting Server y Fallback Status Point.

03 Distribution Point.

01 Site Database.

 

Please i need a step by step procedure.

Share this post


Link to post
Share on other sites

I am recieving some type of SQL error when attempting a site backup on our primary site, i dont understand why this is not working. Any help would be appreciated. I have posted the log below:

 

10/16/11 00:12:24 - starting backup. SMS_SITE_BACKUP 10/16/2011 12:12:24 AM 2936 (0x0B78)

BackupDir = E:\SCCM_SITE_BACKUP. SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

Installation RootDir = E:\MICROSOFT CONFIGURATION MANAGER. SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

Site SQL Dir = \\HZSD-SQL-B\C$\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL10.MSSQLSERVER\MSSQL\. SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

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. SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

Site Backup Location = \\hzsd-sccm-a\SCCM_Site_Backup SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

SQL Backup Location = \\hzsd-sccm-a\SCCM_Site_Backup SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=HZSD-SCCM-A SITE=548 PID=4472 TID=2936 GMTDATE=Sun Oct 16 06:12:25.011 2011 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879) SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

Starting VSS initialization... SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

Starting Asynchronous GatherWriterMetadata. SMS_SITE_BACKUP 10/16/2011 12:12:25 AM 2936 (0x0B78)

Number of writers that responded: 19. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Reading SMS Writer metadata... SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Number of FileIncludes: 0. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Number of FileExcludes: 0. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Number of Components: 7. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Component 0 - 548Backup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

FileGroupFile = E:\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes] SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Component 1 - 548Backup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

FileGroupFile = E:\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes] SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Component 2 - 548Backup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

FileGroupFile = E:\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes] SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Component 3 - 548Backup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

FileGroupFile = E:\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes] SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Component 4 - 548Backup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

FileGroupFile = E:\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat [Recursive: no] SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Component 5 - 548Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

FileGroupFile = E:\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no] SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Component 6 - 548Backup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Dependency On SQL Writer , LogicalPath:\\HZSD-SQL-B\SCCM, ComponentName:SMS_548 SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

After GatherWriterMetadata SMS Writer status = STABLE. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Starting to clean and prepare the backup location. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Cleanup and/or preparation done. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Info: Sending message to start the SQL Backup... SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Starting to create the snapshot set. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

The System Provider VSS ID is 0,000,000,000,391,828 SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Added volume containing E:\ to the snapshot set. SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Info: Starting Asynchronous PrepareForBackup... SMS_SITE_BACKUP 10/16/2011 12:12:26 AM 2936 (0x0B78)

Info: Asynchronous PrepareForBackup finished... SMS_SITE_BACKUP 10/16/2011 12:12:27 AM 2936 (0x0B78)

Info: Waiting for SQL to PrepareForBackup. SMS_SITE_BACKUP 10/16/2011 12:12:27 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:12:27 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:12:32 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:12:37 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:12:42 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:12:47 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:12:52 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:12:57 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:02 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:07 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:12 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:17 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:22 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:27 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:32 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:37 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:42 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:47 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:52 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:13:57 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:02 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:07 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:12 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:17 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:22 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:27 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:32 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:37 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:42 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:47 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:52 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:14:57 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:02 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:07 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:12 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:17 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:22 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:27 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:32 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:37 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:42 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:47 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:52 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:15:57 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:02 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:07 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:12 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:17 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:22 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:27 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:32 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:37 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:42 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:47 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:52 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:16:57 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:17:02 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:17:07 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:17:12 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:17:17 AM 2936 (0x0B78)

Sleeping for 5 seconds... SMS_SITE_BACKUP 10/16/2011 12:17:22 AM 2936 (0x0B78)

Error: Sql Server could not prepare for the Backup. SMS_SITE_BACKUP 10/16/2011 12:17:27 AM 2936 (0x0B78)

Aborting the backup process. SMS_SITE_BACKUP 10/16/2011 12:17:27 AM 2936 (0x0B78)

SMS_SITE_BACKUP 10/16/2011 12:17:27 AM 2936 (0x0B78)

Error: CreateSnapshotSet failed... SMS_SITE_BACKUP 10/16/2011 12:17:27 AM 2936 (0x0B78)

STATMSG: ID=5047 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=HZSD-SCCM-A SITE=548 PID=4472 TID=2936 GMTDATE=Sun Oct 16 06:17:27.350 2011 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 10/16/2011 12:17:27 AM 2936 (0x0B78)

SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP 10/16/2011 12:17:27 AM 2936 (0x0B78)

Share this post


Link to post
Share on other sites

Well i managed to figure out my problem after hours of sifting through mounds of articles on line and the sccm logs on my primary site server. Turns out my STATUS_SUMMARIZE, SITE_COMPONENT_MANAGER, and SCCM_SITE_BACKUP componenets were corrupt and not installed properly...not sure how this happened, regardless i did the following, i ran a repair install from my configmgrsp2 sourcefiles and voaila, every component installed correctly. This has also fixed an issue i was having with my sms_executive not creating a crashdump every time it stopped.

  • Like 1

Share this post


Link to post
Share on other sites

With this configured do you still need normal SQL Maintenaince Plans running each night on the Primary Site's Database server or do they become redundant?

 

I notice I have a 5 gig SCCM back up done by SQL and a 7 gig backup done by SCCM each night...

Share this post


Link to post
Share on other sites

The ConfigMgr Backup Task is the only supported way to restore a Site. Also this task makes a backup of more then just SQL, see also: http://technet.microsoft.com/en-us/library/bb633229.aspx

 

Back to your question, no you don't have to make a separate SQL backup (even though it might look smaller).

Share this post


Link to post
Share on other sites

Well i managed to figure out my problem after hours of sifting through mounds of articles on line and the sccm logs on my primary site server. Turns out my STATUS_SUMMARIZE, SITE_COMPONENT_MANAGER, and SCCM_SITE_BACKUP componenets were corrupt and not installed properly...not sure how this happened, regardless i did the following, i ran a repair install from my configmgrsp2 sourcefiles and voaila, every component installed correctly. This has also fixed an issue i was having with my sms_executive not creating a crashdump every time it stopped.

 

binarymime, am in the same situation please help understanding the part where you ran a repair install from my configmgrsp2 sourcefiles, how did you do that?

Thanks in advance.

Share this post


Link to post
Share on other sites

Currently, we are backing up our sccm site to the C: drive on the site server and our sccm database to the C: drive on the remote database server. The database server is running low on disk space and the server administrator wants to change the backup location to a network storage system. Besides changing the backup location in the management console (Site Settings>Site Maintenance>Tasks>Backup ConfigMgr Site Server) using a network share (\\server\share), are there any other tasks that need to be performed to ensure the database backs up as it should?

Share this post


Link to post
Share on other sites

binarymime, am in the same situation please help understanding the part where you ran a repair install from my configmgrsp2 sourcefiles, how did you do that?

Thanks in advance.

 

I would be happy to assist :)

 

1. First things first. Make sure you have a backup of your site server and SQL site database.

 

2. On your site server browse to your ConfigMgrSP2 Install files. Depends where you have them stored...in my case we have all of our instllation media stored on a file server in ISO format so we mount them with Virtual drive software.

 

3. Run "splash.hta", when it loads click "Configuration Manager 2007 SP2"

 

4. Select "Perform site maintenance or reset this Site" and click "Next", ensure all data in the following screens is correct and follow the onscreen instructions.

 

Let me know if you have questions

 

{Edit}

 

I forgot to mention that following this procedure i had to uninstall my head end management point role, and pxe role, and then re-add / re-install them to get my PXE Service point to work again...in case you are getting a "Failed to download policy" message on any client you try to roll out. This entry will appear in the SMSTS.log file

 

Thanks

Share this post


Link to post
Share on other sites

Thanks binarymime. I appreciate the response. I was keeping my fingers crossed for not having to do more than change the backup location at Site Settings>Site Maintenance>Tasks>Backup ConfigMgr Site Server. I'm not quite clear on why I would need to run the Perform site maintenance or reset this site option. We would not be relocating the database. We'd just be changing the location for the backup. Thanks for your input.

Share this post


Link to post
Share on other sites

Thanks binarymime. I appreciate the response. I was keeping my fingers crossed for not having to do more than change the backup location at Site Settings>Site Maintenance>Tasks>Backup ConfigMgr Site Server. I'm not quite clear on why I would need to run the Perform site maintenance or reset this site option. We would not be relocating the database. We'd just be changing the location for the backup. Thanks for your input.

 

Hi jmac,

 

My apologies i should have quoted the post i was responding to, my solution was intended for saulw's inquiry. However to answer your question; all you should have to do is change the backup location. The only other thing i would make sure of is that you have a domain administrator account with permissions to the site database and the folder on the remote location to which you will be backing up.

 

Thanks

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×