Configuration Manager Backup and Recovery Forum

Urgent :Restoring after Central site and Primary site upgraded from SCCM SP1 to SP2

Wed, 25 Nov 2009 23:53:14 Z

Hi Guys

We took full backup of Primary sites before upgrade thinking we can restore it to SP1 if we encountered any major issues. In test environment, we replicated this situation, After upgrading to SP2 when I tried to restore SP1 again from backup using Config Mgr Site Repair Wizard. It instantly gives error message "Verify Backup Path" Failed. I read the post
http://social.technet.microsoft.com/Forums/en/configmgrbackup/thread/f6f7be22-deaf-4e9c-95be-87fb6240a6c8

It says: "Backup was taken on SP1 and we tried to restore it without SP1 and so failed"

If Primary servers are upgraded from SCCM SP1 to SP2 and we got backup when site server was SP1. If we have issue at that stage then we actually need to uninstall SP2, reinstall SP1 and then use Backup to restore it. Is that sound right? Its sound ridiculous to me, If i uninstall Central Site, all the year work on the infrastructure would be lost. Also there is no guarrenty, restoring from Backup will bring us back to same state.
Is there any way we can restore our state to SP1 being on SP2 at the same timewe can have our system intact?

Its really urgent.. Please advice

Thanks in Advance

Veday

Server Engineer

SCCM SP2 Upgrade MP installation issue

Fri, 20 Nov 2009 10:50:04 Z

Hi,
I've upgrade my site to SCCM sp2 but the upgrade fails to install the MP, the error message is:
MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.

Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.

Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties.

Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.

I've tried reinstalling IIS, my reporting site works fine.

Help!

Backup will not run

Tue, 24 Nov 2009 11:09:37 Z

Hi,

I am trying to create a backup. The weekly backup normally works ok. I got the backup to run once and now it will no longer run, though it looks like the backup service is stopping and starting. Any ideas would be most appreciated, permissions etc all look good.

The log file is as follows.Initializing the status message reporting system... SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
The path to the "Status Manager" inbox is "F:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs". SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Registered this process as a source of "SMS Server" events. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Registered this process as a source of "SMS Client" events. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Registered this process as a source of "SMS Provider" events. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Status message reporting system initialized successfully. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Locale set to OS value (English_United States.1252). SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
SMS site backup service 4.00 started. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=ASHSACCM01 SITE=ASH PID=9672 TID=3156 GMTDATE=Tue Nov 24 09:34:08.706 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
11/24/09 09:34:08 - starting backup. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
BackupDir = F:\DATA\BACKUP. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Installation RootDir = F:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Site SQL Dir = . SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
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 24/11/2009 09:34:08 3156 (0x0C54)
Sql Writer service is running. SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
SMS sql data files: C:\SMSData\SMSData_ASH.MDF, C:\SMSData\SMSLog_ASH.LDF SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
Site Backup Location = F:\Data\Backup SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
SQL Backup Location = F:\Data\Backup SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=ASHSACCM01 SITE=ASH PID=9672 TID=3156 GMTDATE=Tue Nov 24 09:34:08.956 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 24/11/2009 09:34:08 3156 (0x0C54)
LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879) SMS_SITE_BACKUP 24/11/2009 09:34:09 3156 (0x0C54)
Starting VSS initialization... SMS_SITE_BACKUP 24/11/2009 09:34:09 3156 (0x0C54)
Starting Asynchronous GatherWriterMetadata. SMS_SITE_BACKUP 24/11/2009 09:34:09 3156 (0x0C54)
Number of writers that responded: 10. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Reading SMS Writer metadata... SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Number of FileIncludes: 0. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Number of FileExcludes: 0. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Number of Components: 7. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Component 0 - ASHBackup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Component 1 - ASHBackup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Component 2 - ASHBackup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Component 3 - ASHBackup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Component 4 - ASHBackup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat [Recursive: no] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Component 5 - ASHBackup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Component 6 - ASHBackup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Dependency On SQL Writer , LogicalPath:ASHSACCM01\HRCMAPRD, ComponentName:SMS_ASH SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
SQL Server is on the same box as the Site Server. So, no need to communicate to the SQL backup agent. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATASMS_ASH.mdf [Recursive: no] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
FileGroupFile = F:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATASMS_ASH_log.LDF [Recursive: no] SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
After GatherWriterMetadata SQL Writer status = STABLE. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
After GatherWriterMetadata SMS Writer status = STABLE. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Starting to clean and prepare the backup location. SMS_SITE_BACKUP 24/11/2009 09:34:12 3156 (0x0C54)
Deleting F:\Data\Backup\ASHBackup, FAILED, Win32 Error = 32 SMS_SITE_BACKUP 24/11/2009 09:34:19 3156 (0x0C54)
Failed to delete the contents of the backup folder. Error Code = 0x0 SMS_SITE_BACKUP 24/11/2009 09:34:20 3156 (0x0C54)
Error: Deleting the existing files in the backup location failed... SMS_SITE_BACKUP 24/11/2009 09:34:20 3156 (0x0C54)
STATMSG: ID=5026 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=ASHSACCM01 SITE=ASH PID=9672 TID=3156 GMTDATE=Tue Nov 24 09:34:20.019 2009 ISTR0="F:\Data\Backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 24/11/2009 09:34:20 3156 (0x0C54)
SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP 24/11/2009 09:34:20 3156 (0x0C54)

MP error after running site repair

Thu, 23 Oct 2008 09:04:38 Z

Hello,

We are using SCCM 2007 R2 installed on Windows Server STD 32-bit

SQL server is remote ( SQL 2005 , Server 2008 STd 32-bit )

After testing the DRP plan I perfomed a site repair of the SCCM site.

However the MP is unable to install, I recieve the following error

MSI (s) (18!74) [10:55:51:419]: Product: SMS Management Point -- Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming
The error code is 800CC801

Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming
The error code is 800CC801

Any help would be appreciated ...

Setup was unable to create the Internet virtual directory CCM_Incoming. The error code is 8007000D

Sun, 22 Nov 2009 09:15:25 Z

Hi

At one of the secondary site, MPSETUP.log file is giving following error
Setup was unable to create the Internet virtual directory CCM_Incoming. The error code is 8007000D

Tried to remove and reinstall MP >>> Same Error

As per
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/7ce16575-474c-4a0e-8eca-be4f4fc7344c

Again Remove BITS and Reinstall BITS through ADD\Remove Windows Component. Same Error

Tried to install manually using mp.msi but returning same error

Please advice, any more ideas..

Your help would be much appreciated

Thanks & Regards

Veday

Server Engineer

Errors with nightly site backup

Mon, 17 Mar 2008 18:07:17 Z

Ever since I upgraded my SMS 2003 site I've been getting errors with my nightly site backup task. I'm backing up my site to the same drive (D that Config Mgr is installed on. The database is about 3 gb and the free space on D: is 60 gb.

The database file and log file appear to be getting backed up despite some SQL / VSS errors that appear in my smsbkup.log.

I'm getting this warning presumabley because my backup is on the same volume as my db / log files:

Warning: Backup location and the sms sql data/log files 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.

Further down I get this error:

After GatherWriterMetadata SQL Writer status = FAILED_AT_FREEZE.

Error: VSS_E_WRITERERROR_RETRYABLE. Error Code = 0x80,042,3f3.

After GatherWriterMetadata SMS Writer status = FAILED_AT_PREPARE_SNAPSHOT.

Error: VSS_E_WRITERERROR_RETRYABLE. Error Code = 0x80,042,3f3.

Things continue on until

After DoSnapshotSet SQL Writer status = FAILED_AT_FREEZE.

Error: VSS_E_WRITERERROR_NONRETRYABLE. Error Code = 0x80,042,3f4.

After DoSnapshotSet SMS Writer status = FAILED_AT_PREPARE_SNAPSHOT.

Now the backup continues and shows it has suceeded in backing up all the Components. Then I see

After BackupComplete SQL Writer status = FAILED_AT_FREEZE.

Error: VSS_E_WRITERERROR_NONRETRYABLE. Error Code = 0x80,042,3f4.

After BackupComplete SMS Writer status = FAILED_AT_PREPARE_SNAPSHOT.

03/17/08 04:54:31 - backup completed.

Backup task completed successfully with zero errors but there could be some warnings, AFTERBACKUP.BAT will be started if available in its predefined location

Looks like all went well despite the warnings! Should I be concerned?

Just SCCM Backup Task needed?

Fri, 20 Nov 2009 16:34:29 Z

Is there anything other than the built-in SCCM Site Backup task that should be done to ensure that a hierarchy with one primary central site server and 4 secondary site servers can be restored? Is anything else recommended such as IIS backups or any file directories?

Thanks

Moving SCCM Installation to New Drive

Tue, 17 Nov 2009 18:38:02 Z

I've come into a situation where a customer has SCCM installed on C:\ (not sure why??) and they are running out of space. There is ample space on E:\ (100+ GB free) if I can only figure out how to move the installation. I don't beleve the repair wizard will do this, will it?? My concern is the drive letters will be changing. I assume this will cause issues (registry, etc.). This is a rather small environment:
-1 Primary Site Server (local SQL)
-2 MP's
-2 SUP's
-20 DP's
-about 1500 clients

Has anyone done this before or have any ideas on what the procedure is for this?

Thanks!

xtiyu32n

SMS Application Backup Issue

Wed, 11 Nov 2009 06:11:48 Z

Hello,

we have couple of SMS Application servers in our environment. Recently we migrated from SQL 2000 to SQL 2005 and changed SQL Service from "Local System" to our "Service account". When SMS application takes backup from their consol we are getting following error messages and backups are failing.

We cahnged SQL Service account from "Service Account" to "Local System" then backups are running from SMS application console.

Backup Failing Observations:
1)Our Service Account is in Administrator Group
2)Granted permissions in Local Security Policyes
3) Builtin\ Administrator is Available
4) NTAuthority \ System is available
5) Granted Full rights to SQL Folders

*** backup database SMS_CHE to DISK = 'E:\_SMFFB.tmp' with INIT SMS_SITE_BACKUP 1/7/2009 6:32:02 PM 840 (0x0348)

*** [42000][3201][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'E:\_SMFFB.tmp'. Operating system error 5(Access is denied.). SMS_SITE_BACKUP 1/7/2009 6:32:02 PM 840 (0x0348)

*** backup database SMS_CHE to DISK = 'E:\_SMFFB.tmp' with INIT SMS_SITE_BACKUP 1/7/2009 6:32:02 PM 840 (0x0348)

*** [42000][3013][Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally. SMS_SITE_BACKUP 1/7/2009 6:32:02 PM 840 (0x0348)

Failed to backup site database SMS_CHE up to E:\mssql\data\sms_bak\CHEBackup\SiteDBServer\SMSbkSQLDBsite.dat: ~Error executing SQL backup command. SMS_SITE_BACKUP 1/7/2009 6:32:02 PM 840 (0x0348)

Trying database backup through temp file SMS_SITE_BACKUP 1/7/2009 7:04:29 PM 11900 (0x2E7C)

*** backup database SMS_HYD to DISK = 'F:\_SM128A.tmp' with INIT SMS_SITE_BACKUP 1/7/2009 7:04:30 PM 11900 (0x2E7C)

*** [42000][3201][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'F:\_SM128A.tmp'. Operating system error 5(Access is denied.). SMS_SITE_BACKUP 1/7/2009 7:04:30 PM 11900 (0x2E7C)

*** backup database SMS_HYD to DISK = 'F:\_SM128A.tmp' with INIT SMS_SITE_BACKUP 1/7/2009 7:04:30 PM 11900 (0x2E7C)

*** [42000][3013][Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally. SMS_SITE_BACKUP 1/7/2009 7:04:30 PM 11900 (0x2E7C)

Failed to backup site database SMS_HYD up to E:\mssql\MSSQL\BACKUP\HYDBackup\SiteDBServer\SMSbkSQLDBsite.dat: ~Error executing SQL backup command. SMS_SITE_BACKUP 1/7/2009 7:04:30 PM 11900 (0x2E7C)

kindly let us know if any other changes need to done.

Thanks

Srikanth.kls

Distribution Manager Isn't Distributing

Wed, 14 Oct 2009 21:09:06 Z

I'm using the SCCM Site Repair Wizard to create a copy of my production environment in my lab, but I'm having a problem with Distribution Manager.

I have 3 packages that have their source files on odd, one-off servers. I didn't bother to restore those in the lab, because they're not necessary for what I'm doing now. Currently Distribution Manager has fixated on one of these packages and keeps trying to distribute it, failing because the source files aren't there. I wouldn't care, but nothing else has been distributed to my distribution point.

In the lab I have created a VM that is acting as my SMS Primary Site server/SQL Server (just like in production), and another to act as the source for 99% of my packages, and my distribution point.

How can I get Distribution Manager to move on? I've deleted the package, but that didn't have any effect.

Disaster Recover / High Availabity

Mon, 05 Oct 2009 18:46:41 Z

Does anyone have any recommendation in regards to DR or HA for a primary? We have had 2 cases in the last few months in which drives went bad and primaries had to be restored from backup. It's a whole long story and if the region had the HW we suggested (Raid 10 vs Raid 5) it wouldn’t have been as issue. Taking HW out of the equation what / is their a best way to recover from a primary failure that won' take hours? In the case of the last primary, it took us about 8 hours to get back up and running:

1) Install SQL - 30 mins
2) Install SCCM - 1 hour
3) Run site repair wizard. We noticed the amount of adverts will impact how long this step takes to fnish. We had around 8k adverts and the repair would do around 1500 adverts and hour (you can see this is smsprov.log while the restore is going) - 6 hrs

The problem with the primary going down is that all of my secondaries below the primary (in this case 10) are also useless until the primary is restored. I think 8 hours is pretty good to get everything going again, but business doesn't agree.

Business keeps pushing us to go to SAN, since all our primaries have direct attached storage, but we believe SAN will impact performance. Does anyone have any input on SAN ?

Thank you.

Migrate Win2K3 x86 to Win2K8 x64

Fri, 06 Nov 2009 03:39:51 Z

We are wanting to upgrade our ConfigMgr Site Server from Win2K3 x86 to Win2K8 x64.

Is there a supported path to doing this? It seems that you need to install a new site and join the exiting site as a child... is this correct?

SCCM SITE RESET QUESTION

Sat, 07 Nov 2009 03:53:14 Z

After reading site reset on technet online, http://technet.microsoft.com/en-us/library/bb633159.aspx I want to confirm something:

1. If perform site reset, will the package,or advertiment be missing?

2. Will the site configuration be missing or back to original default setting?

3. What the impact after site reset? Will the security configuration be back to original?

Does anybody explain this process?

Thanks.

Cannot backup SCCM site getting error "Unable to find/start SQLWriter service". Nees Advice since I am not a SQL Admin

Fri, 11 Sep 2009 17:54:16 Z

Lately, my SCCM 2007 site is not getting backed up anymore. The backup is supposed to run every Sunday but the last time it ran successfully was about two months ago. The backup log says, " ERROR: SQL Backup task failed. Error message - Unable to find/start SQLWriter service. Cannot backup Sql database without this service." The SCCM database is on a remote SQL server that houses other databses. I do not have access to the SQL server as our SQL servers are managed by the SQL Admins (and they are very strict with access permissions and security). If the SQL Admin refuses to enable this service, is it possible to backup the SCCM site without backing up the database? The SQL Admins do back up on the databases on a regular basis so I they are gonna tell me not to do a database backup since they are already doing it.

We have SCCM1 SP1, 1 primary site, no child or secondary sites.

Unsafe removal of device error, when trying to backup in 2000 server...

Mon, 02 Nov 2009 18:45:36 Z

I'm using the windows 2000 server backup utility to save data to my WD external drive. When I schedule a backup, the backup never starts. I will get the error message that the drive has been removed and has not been shut down correctly. The drive hasn't been removed. It always sits in the closet with the server. If I do remove it, I do it correctly. When I look at the event viewer. I see the message: received a device interfacing removal notification for device...( the WD USB drive ). Then a few seconds later a arrival notification for the USB drive. This event occurs a few seconds after the backup is scheduled to start. Please help!

Move SCCM Site Server

Tue, 27 Oct 2009 15:37:48 Z

I'd like to replace my existing site server with new hardware. Is there a procedure for this? We can keep the same computer name. In addition to being the site server, it's also a distribution point, management point, and reporting point. The database is on another host and I'm not planning on moving that.

I don't expect anybody to write up instructions for me but pointing me to a known good procedure would be great. Thanks!

SQL DB does not seem to be backing up..

Tue, 18 Nov 2008 01:21:19 Z

Hello all,

I know theres numerous posts about various backup problems/configs but I couldn't find anything referencing my particular problem..

I have my backup task scheduled to run daily.

The sms part of it seems to back up fine, however when I check the directory on the SQL server there is only a single file called SQLBackupDocument.xml in there.

I am trying to do a test restore of sms but am running into some problems and I think I need to get it to spit out the mdb when it does the backup.

Also when I did the restore I ticked the 'do not restore db', restored, then restored a manual backup (*.bak) of the database into sql. This 'work' but when I load the console everything is empty, for example, under packages, all my folders are there, but no packages. No collections are present either..

The backup says it runs successfully so I am at a loss as to where to poke around.

Thankyou in advance,

-Dan

SCCM errors

Fri, 16 Oct 2009 20:54:26 Z

This is a re-install after the previous site was removed.
the SCCM is running on a 64 bit machine, WSUs and SQL are on two separate machines. Teh install went without any errors, however we see a load of critical errors in the component status:
SMS_CI_assignment _manager : SMS CI Assignment Manager failed to process CI Assignment changes. These changes will be retried on next processing cycle.
SMS_collection_evaluator : SMS Collection Evaluator failed to process Collection Settings changes. These changes will be retried on next processing cycle.
And list goes on.
SMS_database_notification
SMS_discovery_data_manager
SMS_hierarchy_manager
SMS_inventory-data_loader
SMS_MP_control_manager
SMS_object_replication_manager
SMS_policy_provider
SMS_software_metering_processor
SMS_state-system
SMS_WSUS_SYNC_manager
SMS_SRs_reporting_point
SMS_system_health_validator
SMS_MP_decive_manager

For many entries the severity level for the first few are information and the rest are errors. trying to apply hot fixes fails due to hardware platform error, so where would you start? this is a dedicated SCCM machine, so i was thinking, uninstall, wipe out, directory clean up and re-install from scratch. Or are those errors "easy" to fix.

Backup

Thu, 15 Oct 2009 16:52:36 Z

I am trying to install backups made before I did system recovery. I receive message that backup is unavailabe. I am using an external hard drive for backup.

Unble to backup Site System

Fri, 02 Oct 2009 12:54:33 Z

Hi all,

I configured the backup task to do a backup of SCCM but I got the following error:

SMS SQL Monitor could not start the SMS Backup service on server MTLSCCM1.

Possible cause: You changed the service setting for the SMS Backup service, but forgot to notify SMS.
Solution: Use SMS Setup to modify the installation of the site.

Possible cause: SMS SQL Monitor does not have sufficient access rights to administer the site server.
Solution: Verify that the server connection accounts are properly configured to allow the SMS SQL Monitor to administer the site server.

My Primary Site server and the SQL DB are on the same box.

Does anybody have any thoughts?

Thanks,

JesMat

Reinstalling SCOM 2007 again on the same server

Wed, 05 Aug 2009 19:32:14 Z

Hello. We Need to configure a SCOM 2007 server, before that, want to remove anythings from AD Infrastructure? Is there force to uninstalling agents on servers whole on the network? is there some check marks for reinstalling SCOM 2007 on the network? last installation was not useful after a half-healthy SCOM server and after hours on troubleshoot, we decided to Build a New Server, but agents are on the servers still, not communicating with SCOM server.
I'm wondering, I should erase things out there? or just build a new server and boom!
It would be better name this thread, installing scom 2007 after reinstalling a corrupted SCOM Server.
Thank you all.

Repair Site wizard fails to launch on Site Server Consoles SCCM 2007

Fri, 17 Apr 2009 23:51:08 Z

On two test site servers running SCCM 2007 with R2 update on both the "Repair Site" wizard fails to launch.

When I right-click and select repair site nothing happens.

The New Secondary site, Upgrade Secondary Site, Transfer Site Settings, and properties all work.

Just not the repair site.

This is happening on both the Central Site server and the child Primary site server.

This happens on both consoles.

Is there a log file for failed app launches?

Event Viewer does not show anything.

What gives?

Screenshots here:
http://picasaweb.google.com/BridgesCCS/SCCMScreenshots?feat=directlink

SCCM's SQL Database restore fails with "Could not connect or execute SQL query" error.

Thu, 01 Oct 2009 16:07:23 Z

Greetings,

I have SQL Server 2008 working in conjunction with SCCM. Recently, I have had to redo my DC and since then I have not been able to access the SQL Management Studio. Everything else is just fine and has been resolved, SCCM along with DNS, DHCP, IIS, etc. It comes up with an error of access denied no matter what I did or what username I typed in whether it was with SQl Authentication or Windows Authentication, "sa" account or AD account. I know we had an account specificly created for SCCM with all permissions and full control. That same account was added to the SQL DB and made part of sysadmin group. Even though I was not able to access the Management Studio, SQL services were starting by using the custom made account and SCCM was working fine with no errors or warning for SQL.

Since we need to access Management Studio and just the fact that access is denied, scares me. I therefore ended up reloading just the SQL Server and leaving SCCM alone how it was originally. The DB was named the same as it was before. After reloading it, I wanted to restore it through SCCM, since that is how it was backed up in the first place. I choose to run the ConfigMgr setup -> Perform site maintenance or reset the Site -> Modify SQL Server Configuration -> Type in the SQL instance and the server where it resides SERVER\SQLDB and ConfigMgr Site Db, which is SMS_XXX. After this step, I get an error saying:

"Could not connect or execute SQL query. If the Site's database has been restored, verify if this machine account and the user account have local administrator privileges on the selected SQL Server"

I made sure that the account that is trying to access the current database is in the database sysadmin group and part of the Domain admin group, who are also local admin on the server. Now, I am not sure if this error is coming from the old database that I am trying to recover and the since the SID is different in the DB from the SID in the AD, it does not allow access or is is trying to access the new database? Is there any other ways that I can restore my old SCCM database? As it is now, I cannot use SCCM since it is not connecting to its original DB? What can I do to get it working and get the DB in place for SCCM? Would I have to reload the SCCM completely?

Thanks in advance,

Kenzo

DPM 2007 setting up storage pools

Wed, 12 Aug 2009 19:56:58 Z

I have just installed a new DPM 2007 server on a VM machine. I have made available 150gb of storage via virtual hd. My problem is when I try to add it within the storage pool. It shows capacity of 150gb and only 3mb free. But there is nothing instaledl on the disk. Can someone please explain why this is showing up like that through the storage pool and how I can resolve this issue. This the first DPM 2007 I have had my hands on so I am learning as I go here. Any and all hel pwould be greatly appreciated.

Changing SQL Backup configuration after moving site database files

Fri, 18 Sep 2009 20:33:20 Z

Hi there,

I am using SCCM 2007 SP1. I have moved my database files which were on the system partition of my remote database server to another partition on the same remote database server using the detach, move files then attach method. My question is the the SMS_SITE_BACKUP task is still looking to the default location for the database files and obviously they are no longer there.

here is the log line showing that it is looking in the wrong place:

Site SQL Dir = \\SCCMDB1\C$\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL.1\MSSQL\.

Anyone know where abouts I can change this so it now points to the D: drive on that same server?

Thanks in advance

Best practice to perform backup&restore Secondary site?

Fri, 18 Sep 2009 12:28:08 Z

Hi,

SCCM R2 SP1 + SQL 2005 SP3 (same server)
Secondary Site server roles: DP, WSUS+SUP, Proxy MP, FSP

I have many questions on the backup&restore SS server:

1) Which folders need backup on Secondary Site (SS) server (SMSPKGD$, SMSPKGSIG, SMSSIG$ .....)?

2) How they must then correctly backup&restore? (permissions, share)

3) Who worked with PreloadPkgOnSite, for a package you can use one time?
(last paragraph: http://blogs.technet.com/configurationmgr/archive/2009/05/07/configmgr-2007-the-preload-package-tool-preloadpkgonsite-exe-explained.aspx)

4) What is pck-files and Is it possible to initiate the creation of these pck-files some utility ?
I do not have these pck-files, but there are pkg-files.

Thx.

MCSE

SMS_SITE_BACKUP component error every hour although set to run weekly

Wed, 16 Sep 2009 05:35:27 Z

Ive set the SCCM Site backup task to run on sunday between 3:30am and 4:30am but in the logs (which SCOM is reporting on for me) i have a hourly event showing the SMS_SITE_BACKUP failed :-

A new monitored SMS status message on machine BACVSSCCM01 from component SMS_SITE_BACKUP with message ID 5049 was found in the site BNE database.

Does anyone know why this is coming up hourly when its not set to run that way?

SCCM Backup - packages covered?

Tue, 08 Sep 2009 05:11:55 Z

Hi All

Ive got the SCCM backup task scheduled but its not run yet, want to ask a quick question, does this also backup all of our packages? or do i need to ensure this is covered in our regualr file backup?

Cheers

Stewart

Site Repair Wizard on a SCCM Secondary

Thu, 28 May 2009 19:30:46 Z

I am replacing our SCCM 2007 SP1 secondary sites with new hardware and Windows 2008 64 bit.
I have made a backup of the secondary. Shutdown the old server removed it from AD.
Added the new server to AD with the same server name.
Installed SCCM with the exact site names/information.
I then install the SCCM console on the secondary in order to use ConfigMgr Site Recovery Wizard.

This is where the problem is. The Wizard stops with the following error: "SCCM - Recoverywizard has stopped working"

It places this in the application event log

Fault bucket 253032840, type 5
Event Name: CLR20r3
Response: None
Cab Id: 0

Problem signature:
P1: repairwizard.exe
P2: 4.0.6221.1000
P3: 48339214
P4: RepairWizard
P5: 4.0.6000.0
P6: 48339214
P7: 47a
P8: a1
P9: System.NullReferenceException
P10:

Attached files:
C:\Users\*****\AppData\Local\Temp\2\WERAA72.tmp.version.txt

These files may be available here:
C:\Users\*****\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report13ecbb15

These files have no more information other than it stopped working.

The process worked perfectly on the Primaries.

I have many secondaries to replace and a short time to do so.

Any thoughts on how to get the repairwizard to run on the secondaries?

PnP problem code: 00000013

Wed, 09 Sep 2009 23:27:26 Z

Problem Event Name: PnPDeviceProblemCode

Architecture: x86

Hardware Id: IDE\CdRomTSSTcorp_CDDVDW_TS-L633A________________TO01____

Setup class GUID: {4d36e965-e325-11ce-bfc1-08002be10318}

PnP problem code: 00000013

Driver name: cdrom.sys

Driver version: 6.0.6002.18005

Driver date: 04-11-2009

OS Version: 6.0.6002.2.2.0.768.3

Locale ID: 2057

Restoring Records for Inadvertently Deleted Users

Wed, 09 Sep 2009 16:13:03 Z

A colleagues accidentally deleted a few user records from within the SCCM console, and after searching for a while, I'm unable to find how to get those users back in the database, and back in the All Users collection. I'm using AD User Discovery. If I simply force discovery to be run now, will those users reappear in the database after discovery has completed, or is the solution much more complicated than that? Thanks in advance!

SMS 2003 gets "broken" every time

Thu, 03 Sep 2009 07:17:12 Z

I'm running my lab test enviroment on VMware ESXi 4.0. I had this situation twice. When I install and configure SMS2003 server, everything works fine at first. I might restart the SMS server several times, and everything is fine. Then I shut down everything for the night (everything, I mean SMS, DC, VMware). At the morning SMS console won't expand any collections, queries or any other objects. I can't even get inside site status.

Is it like stone written rule, that SMS can't be used as virtual machine?

ps. sorry if I wrote this in a wrong forum directory

Best recovery strategy when hosting SCCM 2007 and the site database on the same virtual machine

Fri, 28 Aug 2009 19:11:47 Z

Hi,

we have a virtual machine running SCCM 2007 R2 as a primary site with SQL 2005 SP3.

The SCCM database is located on the same server and SQL is dedicated to SCCM.

The virtual machine also owns the Management Point, Reporting Point and Distribution Point roles. The remaining roles we configured; Software Update Point, State Migration Point and PXE Service Point are located on other servers.

The primary (and central) site is on top of a hierarchy consisting of 3 secondary sites under it.

We run a SCCM Backup task on a daily basis and moreover, a snapshot of the virtual machine is done everyday.

Let say we have to restore SCCM and the latest snapshot of the virtual machine is more recent than the SCCM backup, which way it should be restored:

1. Using the Site Repair Wizard with the latest SCCM backup, even if it is older than the virtual server snapshot.

2. Using the Site Repair Wizard, but without the SCCM backup, instead, we select the Repair or reconfigure a site option and then, when asked for the backup date, we enter the date the virtual server snapshot was taken.

Tnx for your help

Pat

Error communicating with (remote) SMS_SITE_SQL_BACKUP component

Mon, 18 Aug 2008 19:20:14 Z

I have an SCCM SP1 site server with a remote SQL server running SQL 2005 SP2 that houses the site database. The site server's computer account is a local admin on the SQL server. The components installed successfully, but when I query the SMS_SITE_SQL_BACKUP component that resides on the SQL server, I get the error "Error communicating with component". I verified the service is running on the SQL server under LocalSystem.

When running the ConfigMgr backup maintenance task, the site backs up successfully, but it can't backup the database (due to the above).

Any ideas?

SMS_SITE_SQL_BACKUP component failed to reinstall

Tue, 30 Jun 2009 12:27:03 Z

Hi,

I have a problem with SMS_SITE_SQL_BACKUP component on my SCCM SQL server. The SQL server is running on Windows Server 2003 x64 SP2 and site is in Native mode running SCCM SP1 R2 on Windows Server 2003 SP2 (separate servers)
I've enabled a Backup ConfigMgr Site Server maintance task 2 weeks ago and since then site backup was running fine.
Few days ago I've noticed that SMS_SITE_SQL_BACKUP component start to log following errors:

"SMS Site Component Manager failed to reinstall this component on this site system.

Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager."

Information in 'sitecomp.log'

    "Reinstalling component SMS_SITE_SQL_BACKUP...    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:08    2204 (0x089C)
STATMSG: ID=1018 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_SQL_BACKUP_SiteName" SYS=SiteName SITE=SiteCode PID=1808 TID=2204 GMTDATE=Fri Jun 26 14:56:08.956 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:08    2204 (0x089C)
      Starting bootstrap operations...    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
        Component file list item in the install map for component SMS_SITE_SQL_BACKUP does not contain srvboot.exe.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
      Bootstrap operations aborted.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
LogEvent(): Successfully logged Event to NT Event Log (4, 77, 1073742842, (null)).    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
      The server already contains some of the required files for this component. A disk space check will not be made.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
      Installed file \\SiteName\E$\SMS_SiteName\bin\x64\smssqlbkup.exe.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
      All files installed.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
      Starting bootstrap operations...    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
        Component file list item in the install map for component SMS_SITE_SQL_BACKUP does not contain srvboot.exe.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
      Bootstrap operations aborted.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
    Reinstallation failed and will be retried in the next polling cycle.    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)
LogEvent(): Successfully logged Event to NT Event Log (1, 77, -1073740804, (null)).    SMS_SITE_COMPONENT_MANAGER    26/06/2009 15:56:09    2204 (0x089C)"

Information in 'Application' log on SQL server:
"14:56:08, component SMS_SITE_COMPONENT_MANAGER on computer ServerName reported: , HRESULT=0x00000000."
"14:56:08, component SMS_SITE_COMPONENT_MANAGER on computer ServerName reported: , 60."

I've rechecked all the permissions and they're OK. Site server computer account is a local admin on the sql box (SQL and main SCCM server are separate servers). All other SCCM components are working fine.
When I tried to query this component I'm getting error: Error communicating with component I've applied patch specified here: http://support.microsoft.com/default.aspx/kb/957879 but it didn't resolve this issue.

Is there something I'm missing ? Is there any other log to be checked ?

Any help Appreciate

Exclude directories to backup / DB backup size

Wed, 12 Aug 2009 21:47:58 Z

I have 2 questions:

In SMS 2003 you were able to exclude certain directories that you didn't want to backup (ex: offersum.box) using the smsbkup.ctl file. Can you do the same thing in SCCM ? My assumption is no because of the way it does a snapshot using VSS.

SMS 2003 if your DB was 200GB's but the file only had 100GB's worth of data in it, the .dat file was 100GB's. If you have the same scenario in SCCM even though there is only 100GB of data the backup is 200GB's. SCCM doesn't create a .dat file anymore using SQL backup, it looks like it uses VSS and backs up the actual .mdf and .ldf, so my assumption to this is that I'm out of luck and my backup will be 200GB's.

I do like the fact that VSS allows the SMS Executive to kick right back off, but it also seems to have alot of shortcomings if my assumptions above are correct.

DPM 2007 Protected data location change issue

Mon, 24 Aug 2009 14:26:22 Z

Need your support in DPM server issue. Please find the complete details.

We have a DPM server and protected 2 TB of file server data. It was running fine so far.

Recently we have changed the location of the data (Cluster Group Name Changed) hence we required to add the changes also in the DPM server for that protected data.

Please let us know the procedure to add the changes without loosing the old recovery points.

Recovery Point Threshold

Wed, 26 Aug 2009 20:00:42 Z

Hello,

One of my protection groups is backing up a backup domain controller system state. All of a sudden starting this week, I am getting a Recovery Point Threshold exceeded message. I have modified the disk space to over 20 additional gigs this past week. The wierd thing is that BDC drive is not getting bigger. The total size of the drive is only 39 gigs with over 12 gigs free. Right now the recovery point volume on the DPM is set for 99.64 gigs. My issue is that I need to be very careful on drive space since my SAN is for now limited on space. Does anyone have suggestions on what could be taking up all the room on the recovery point volume, it does not make sense that all of sudden I am running out of space on the recovery point.

TIA.
DC

Unable to backup SCCM with SCCM SP1 R2 and SQL 2008 all on Server 2008 with SP2.

Tue, 25 Aug 2009 00:01:25 Z

I have two servers.
Server 1
    Server 2008 with SP2
    SCCM 2007 with SP1 and R2
    SCCM Updates Applied, KB956578, KB961105, KB969113, KB969529, KB970093

Server 2
    Server 2008 with SP2
    SQL 2008 (all patches applied)

I receive this message from my SMSBKUP.LOG

Initializing the status message reporting system... SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    The path to the "Status Manager" inbox is "D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs". SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
Registered this process as a source of "SMS Server" events. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
Registered this process as a source of "SMS Client" events. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
Registered this process as a source of "SMS Provider" events. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
Status message reporting system initialized successfully. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
Locale set to OS value (English_United States.1252). SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
SMS site backup service 4.00 started. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:10:14.737 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
08/24/09 18:10:14 - starting backup. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
BackupDir = E:\CONFIGMGRBACKUP. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
Installation RootDir = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
Site SQL Dir = \\SQL02\C$\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL10.MSSQLSERVER\MSSQL\. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
Site Backup Location = \\sccm01\configmgrbackup SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
SQL Backup Location = \\sccm01\configmgrbackup SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:10:15.284 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879) SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
Starting VSS initialization... SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
Starting Asynchronous GatherWriterMetadata. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
Number of writers that responded: 10. SMS_SITE_BACKUP 8/24/2009 6:10:18 PM 7828 (0x1E94)
Reading SMS Writer metadata... SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Number of FileIncludes: 0. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Number of FileExcludes: 0. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Number of Components: 7. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Component 0 - PC2Backup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Component 1 - PC2Backup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Component 2 - PC2Backup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Component 3 - PC2Backup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Component 4 - PC2Backup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
FileGroupFile = D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat [Recursive: no] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Component 5 - PC2Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
FileGroupFile = D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Component 6 - PC2Backup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Dependency On SQL Writer , LogicalPath:\\SQL02, ComponentName:SCCM_PC2 SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
After GatherWriterMetadata SMS Writer status = FAILED_AT_PREPARE_BACKUP. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Starting to clean and prepare the backup location. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Cleanup and/or preparation done. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Info: Sending message to start the SQL Backup... SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Starting to create the snapshot set. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Added volume containing D:\ to the snapshot set. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Info: Starting Asynchronous PrepareForBackup... SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
Info: Asynchronous PrepareForBackup finished... SMS_SITE_BACKUP 8/24/2009 6:10:20 PM 7828 (0x1E94)
Info: Waiting for SQL to PrepareForBackup. SMS_SITE_BACKUP 8/24/2009 6:10:20 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:20 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:25 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:30 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:35 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:40 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:45 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:50 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:55 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:00 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:05 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:10 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:15 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:20 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:25 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:30 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:35 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:40 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:45 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:50 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:55 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:00 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:05 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:10 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:15 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:20 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:25 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:30 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:35 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:41 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:46 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:51 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:56 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:01 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:06 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:11 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:16 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:21 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:26 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:31 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:36 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:41 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:46 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:51 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:56 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:01 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:06 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:11 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:16 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:21 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:26 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:31 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:36 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:41 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:46 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:51 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:56 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:01 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:06 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:11 PM 7828 (0x1E94)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:16 PM 7828 (0x1E94)
Error: Sql Server could not prepare for the Backup. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
Aborting the backup process. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
Error: CreateSnapshotSet failed... SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
STATMSG: ID=5047 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:15:21.615 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
SMS site backup service is stopping. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:15:21.647 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
SMS site backup service stopped. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
STATMSG: ID=501 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:15:21.647 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)

This is from my SMSWRITER.LOG

OnIdentify event triggerred. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
SMS Writer 08/24/09 18:10:17 - starting to build the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\INBOXES into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\LOGS into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\DATA into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\SRVACCT into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
Successfully included \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\NAL - D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat into the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
Successfully included \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS - D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat into the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
OnPrepareBackup event triggerred. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
The backup task has selected the components in the Sms Writer. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
ComponentName = PC2Backup\SiteServer\SMSServer\inboxes. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
ComponentName = PC2Backup\SiteServer\SMSServer\Logs. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
ComponentName = PC2Backup\SiteServer\SMSServer\data. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
ComponentName = PC2Backup\SiteServer\SMSServer\srvacct. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
ComponentName = PC2Backup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
ComponentName = PC2Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
ComponentName = PC2Backup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
Successfully exported the \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\NAL to D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:20 PM 1012 (0x03F4)
Successfully exported the \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS to D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:20 PM 1012 (0x03F4)

Site backup fails when database is hosted on a clustered SQL instance

Wed, 05 Aug 2009 02:38:59 Z

I know this post is similar to a few others, but after reading through them I am still experiencing issues. So..

Topology-
> Single Site server hosting all roles except database server role
>> SCCM01
> 2-node A/P SQL 2005 SP3 cluster hosting database server role (Server 2K8 failover cluster)
>> NODE1
>> NODE2
>> SCCMSQLCLU

Configuration-
> SCCM01 computer account is resident in local admin groups on both SQL cluster nodes
> SQL service account has local admin rights on both SQL cluster nodes
> SPN properly registered for SQL service account
> Kerberos is enabled on clustered resource and is has been validated via SQL query
> Backup ConfigMgr Site Server configured to backup to a share local to site server
>> Both SQL cluster nodes and virtual instance have FC rights (both share and NTFS)

Observations-
When running a site backup, the process quickly fails...
> The Application log only contains a single event (5055) indicating the start of the SMS_SITE_BACKUP component
> Migrating the database to a local SQL instance allows for a good backup
> The smsbkup.log from a clustered database backup attempt:

<START LOG>
Initializing the status message reporting system... SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
The path to the "Status Manager" inbox is "E:\SMS\inboxes\statmgr.box\statmsgs". SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
Registered this process as a source of "SMS Server" events. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
Registered this process as a source of "SMS Client" events. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
Registered this process as a source of "SMS Provider" events. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
Status message reporting system initialized successfully. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
Locale set to OS value (English_United States.1252). SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
SMS site backup service 4.00 started. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=JCS PID=4828 TID=6160 GMTDATE=Tue Aug 04 22:39:18.807 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
08/04/09 17:39:18 - starting backup. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
BackupDir = E:\SMSSITEBACKUP. SMS_SITE_BACKUP 8/4/2009 5:39:18 PM 6160 (0x1810)
Installation RootDir = E:\SMS. SMS_SITE_BACKUP 8/4/2009 5:39:19 PM 6160 (0x1810)
Site SQL Dir = . SMS_SITE_BACKUP 8/4/2009 5:39:19 PM 6160 (0x1810)
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 8/4/2009 5:39:19 PM 6160 (0x1810)
Site Backup Location = \\SCCM01\SMSSITEBACKUP$ SMS_SITE_BACKUP 8/4/2009 5:39:19 PM 6160 (0x1810)
SQL Backup Location = \\SCCM01\SMSSITEBACKUP$ SMS_SITE_BACKUP 8/4/2009 5:39:19 PM 6160 (0x1810)
STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=JCS PID=4828 TID=6160 GMTDATE=Tue Aug 04 22:39:19.354 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/4/2009 5:39:19 PM 6160 (0x1810)
LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879) SMS_SITE_BACKUP 8/4/2009 5:39:19 PM 6160 (0x1810)
Starting VSS initialization... SMS_SITE_BACKUP 8/4/2009 5:39:19 PM 6160 (0x1810)
Starting Asynchronous GatherWriterMetadata. SMS_SITE_BACKUP 8/4/2009 5:39:20 PM 6160 (0x1810)
Number of writers that responded: 10. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Reading SMS Writer metadata... SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Number of FileIncludes: 0. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Number of FileExcludes: 0. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Number of Components: 7. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Component 0 - JCSBackup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
FileGroupFile = E:\SMS\INBOXES\* [Recursive: yes] SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Component 1 - JCSBackup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
FileGroupFile = E:\SMS\LOGS\* [Recursive: yes] SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Component 2 - JCSBackup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
FileGroupFile = E:\SMS\DATA\* [Recursive: yes] SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Component 3 - JCSBackup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
FileGroupFile = E:\SMS\SRVACCT\* [Recursive: yes] SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Component 4 - JCSBackup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
FileGroupFile = E:\SMS\BackupTemp\SMSbkSiteRegNAL.dat [Recursive: no] SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Component 5 - JCSBackup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
FileGroupFile = E:\SMS\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no] SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Component 6 - JCSBackup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Dependency On SQL Writer , LogicalPath:\\SCCMSQLCLU, ComponentName:SMS_JCS SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
After GatherWriterMetadata SMS Writer status = FAILED_AT_PREPARE_BACKUP. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Starting to clean and prepare the backup location. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Cleanup and/or preparation done. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Info: Sending message to start the SQL Backup... SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Starting to create the snapshot set. SMS_SITE_BACKUP 8/4/2009 5:39:28 PM 6160 (0x1810)
Added volume containing E:\ to the snapshot set. SMS_SITE_BACKUP 8/4/2009 5:39:29 PM 6160 (0x1810)
Info: Starting Asynchronous PrepareForBackup... SMS_SITE_BACKUP 8/4/2009 5:39:29 PM 6160 (0x1810)
Info: Asynchronous PrepareForBackup finished... SMS_SITE_BACKUP 8/4/2009 5:39:29 PM 6160 (0x1810)
Info: Waiting for SQL to PrepareForBackup. SMS_SITE_BACKUP 8/4/2009 5:39:29 PM 6160 (0x1810)
Sleeping for 5 seconds... SMS_SITE_BACKUP 8/4/2009 5:39:30 PM 6160 (0x1810)
ERROR: SQL Backup task failed. Error message - SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
STATMSG: ID=5052 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=JCS PID=4828 TID=6160 GMTDATE=Tue Aug 04 22:39:35.057 2009 ISTR0="\\SCCMSQLCLU" ISTR1="SMS_JCS" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
Error: Sql Server could not prepare for the Backup. SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
Aborting the backup process. SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
Error: CreateSnapshotSet failed... SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
STATMSG: ID=5047 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=JCS PID=4828 TID=6160 GMTDATE=Tue Aug 04 22:39:35.260 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
SMS site backup service is stopping. SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=JCS PID=4828 TID=6160 GMTDATE=Tue Aug 04 22:39:35.276 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
SMS site backup service stopped. SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
STATMSG: ID=501 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=JCS PID=4828 TID=6160 GMTDATE=Tue Aug 04 22:39:35.291 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/4/2009 5:39:35 PM 6160 (0x1810)
<END LOG>

Advice?