Dear Brothers,

I am facing an issue with the Central Site Backup, I seen details in smsbkup.log file such as

smsbkup.log (Log Details)

1.)  Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:17:54 PM 6912 (0x1B00)
2.) SQL Backup did not complete or abort. You must wait till the backup is completed or aborted before you can start off another backup. 8/18/2015 2:47:56 PM 6912 (0x1B00)
3.) Error: Failed to send start message to the SqlBackup. 8/18/2015 2:47:56 PM 6912 (0x1B00)
4.) SMS_SITE_BACKUP failed. Please see previous errors. 8/18/2015 2:47:56 PM 6912 (0x1B00)
5.) STATMSG: ID=5060 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM-CEN.microsoft.com.sg SITE=UNO PID=5404 TID=6912 GMTDATE=Tue Aug 18 11:47:56.448 2015 ISTR0="Error: Failed to send start message to the SqlBackup." ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 8/18/2015 2:47:56 PM 6912 (0x1B00)
6.) Raised backup task failure alert. 8/18/2015 2:47:56 PM 6912 (0x1B00)

smsbkup.log (start)

Registered connection to SQL server SCCM-DB.microsoft.com.sg and database SCCM\MS_UNO. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Registered connection to master database on SQL server SCCM-DB.microsoft.com.sg. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Initializing the status message reporting system... 8/18/2015 2:17:51 PM 6912 (0x1B00)
    The path to the "Status Manager" inbox is "F:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs". 8/18/2015 2:17:51 PM 6912 (0x1B00)
    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. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Registered this process as a source of "SMS Server" events. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Registered this process as a source of "SMS Client" events. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Registered this process as a source of "SMS Provider" events. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Status message reporting system initialized successfully. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Locale set to OS value (English_United States.1252). 8/18/2015 2:17:51 PM 6912 (0x1B00)
SMS_SITE_BACKUP service 2012 started. 8/18/2015 2:17:51 PM 6912 (0x1B00)
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM-CEN.microsoft.com.sg SITE=UNO PID=5404 TID=6912 GMTDATE=Tue Aug 18 11:17:51.725 2015 ISTR0="SMS_SITE_BACKUP" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 8/18/2015 2:17:51 PM 6912 (0x1B00)
Starting backup - Tue Aug 18 14:17:51 2015 8/18/2015 2:17:51 PM 6912 (0x1B00)
SMS installation root directory = F:\Program Files\Microsoft Configuration Manager. 8/18/2015 2:17:51 PM 6912 (0x1B00)
SQL installation root directory = \\SCCM-DB\C$\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Site server backup location = \\192.168.1.2\SCCM2012R2\SCCM2012-UNO\UNOBackup. 8/18/2015 2:17:51 PM 6912 (0x1B00)
SQL backup location = \\192.168.1.2\SCCM2012R2\SCCM2012-UNO\UNOBackup. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Verified that backup folder \\192.168.1.2\SCCM2012R2\SCCM2012-UNO\UNOBackup exists. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Successfully created the backup folder \\192.168.1.2\SCCM2012R2\SCCM2012-UNO\UNOBackup\UNOBackup. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Verified backup service has permission to access the backup folder \\192.168.1.2\SCCM2012R2\SCCM2012-UNO\UNOBackup 8/18/2015 2:17:51 PM 6912 (0x1B00)
STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM-CEN.microsoft.com.sg SITE=UNO PID=5404 TID=6912 GMTDATE=Tue Aug 18 11:17:51.799 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 8/18/2015 2:17:51 PM 6912 (0x1B00)
LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879) 8/18/2015 2:17:51 PM 6912 (0x1B00)
Starting VSS initialization... 8/18/2015 2:17:51 PM 6912 (0x1B00)
Starting Asynchronous GatherWriterMetadata. 8/18/2015 2:17:51 PM 6912 (0x1B00)
Number of writers that responded: 15. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Reading SMS Writer metadata... 8/18/2015 2:17:54 PM 6912 (0x1B00)
Number of FileIncludes: 0. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Number of FileExcludes: 0. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Number of Components: 7. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Component 0 - UNOBackup\SiteServer\SMSServer\inboxes. 8/18/2015 2:17:54 PM 6912 (0x1B00)
FileGroupFile = F:\Program Files\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes] 8/18/2015 2:17:54 PM 6912 (0x1B00)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Component 1 - UNOBackup\SiteServer\SMSServer\Logs. 8/18/2015 2:17:54 PM 6912 (0x1B00)
FileGroupFile = F:\Program Files\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes] 8/18/2015 2:17:54 PM 6912 (0x1B00)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Component 2 - UNOBackup\SiteServer\SMSServer\data. 8/18/2015 2:17:54 PM 6912 (0x1B00)
FileGroupFile = F:\Program Files\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes] 8/18/2015 2:17:54 PM 6912 (0x1B00)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Component 3 - UNOBackup\SiteServer\SMSServer\srvacct. 8/18/2015 2:17:54 PM 6912 (0x1B00)
FileGroupFile = F:\Program Files\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes] 8/18/2015 2:17:54 PM 6912 (0x1B00)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Component 4 - UNOBackup\SiteServer\SMSServer. 8/18/2015 2:17:54 PM 6912 (0x1B00)
FileGroupFile = F:\Program Files\Microsoft Configuration Manager\install.map [Recursive: no] 8/18/2015 2:17:54 PM 6912 (0x1B00)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Component 5 - UNOBackup\SiteServer\SMSbkSiteRegSMS.dat. 8/18/2015 2:17:54 PM 6912 (0x1B00)
FileGroupFile = F:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no] 8/18/2015 2:17:54 PM 6912 (0x1B00)
Volume F:\ (that contains the file(s)) is marked as a candidate for snapshot. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Component 6 - UNOBackup\SiteDBServer\SMSbkSQLSiteDB.dat. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Dependency On SQL Writer , LogicalPath:\\sccm-db\sccm-db\MS_UNO, ComponentName:MS_UNO 8/18/2015 2:17:54 PM 6912 (0x1B00)
After GatherWriterMetadata SMS Writer status = STABLE. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Info: Sending message to start the SQL Backup... 8/18/2015 2:17:54 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed yet. Waiting 30 minutes for it to abort before starting another backup. 8/18/2015 2:17:54 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:17:54 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:18:54 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:19:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:20:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:21:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:22:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:23:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:24:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:25:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:26:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:27:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:28:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:29:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:30:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:31:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:32:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:33:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:34:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:35:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:36:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:37:55 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:38:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:39:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:40:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:41:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:42:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:43:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:44:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:45:56 PM 6912 (0x1B00)
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... 8/18/2015 2:46:56 PM 6912 (0x1B00)
SQL Backup did not complete or abort. You must wait till the backup is completed or aborted before you can start off another backup. 8/18/2015 2:47:56 PM 6912 (0x1B00)
STATMSG: ID=5051 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM-CEN.microsoft.com.sg SITE=UNO PID=5404 TID=6912 GMTDATE=Tue Aug 18 11:47:56.407 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 8/18/2015 2:47:56 PM 6912 (0x1B00)
Error: Failed to send start message to the SqlBackup. 8/18/2015 2:47:56 PM 6912 (0x1B00)
SMS_SITE_BACKUP failed. Please see previous errors. 8/18/2015 2:47:56 PM 6912 (0x1B00)
STATMSG: ID=5060 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM-CEN.microsoft.com.sg SITE=UNO PID=5404 TID=6912 GMTDATE=Tue Aug 18 11:47:56.448 2015 ISTR0="Error: Failed to send start message to the SqlBackup." ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 8/18/2015 2:47:56 PM 6912 (0x1B00)
SMS_SITE_BACKUP service is stopping. 8/18/2015 2:47:56 PM 6912 (0x1B00)
STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM-CEN.microsoft.com.sg SITE=UNO PID=5404 TID=6912 GMTDATE=Tue Aug 18 11:47:56.456 2015 ISTR0="SMS_SITE_BACKUP" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 8/18/2015 2:47:56 PM 6912 (0x1B00)
Raised backup task failure alert. 8/18/2015 2:47:56 PM 6912 (0x1B00)
SMS_SITE_BACKUP service stopped. 8/18/2015 2:47:56 PM 6912 (0x1B00)
STATMSG: ID=501 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM-CEN.microsoft.com.sg SITE=UNO PID=5404 TID=6912 GMTDATE=Tue Aug 18 11:47:56.485 2015 ISTR0="SMS_SITE_BACKUP" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 8/18/2015 2:47:56 PM 6912 (0x1B00)

Setup Scenario:

1 CAS Server
1 Primary Site Server
2 Secondary Site Server
1 Site Database Server (Hosted in a Clustered SQL Environment)

Questions:
1. How to check Previous SQL backup operation whither it is stalled, looping etc?

2. How to terminate Previous SQL backup operation whither it is stalled, looping etc?

Regards,

• Edited by Arnel-101 Wednesday, August 19, 2015 9:10 AM Correction

Hi,

Is the SMS_SITE_SQL_BACKUP still running?

To answer your question; No, the SMS_SITE_BACKUP services is no longer running. I believed the SCCM Triggered the backup perfectly but as you can see below message from the log. Which I believed the backup trigger is on the loop or stalled and because of this another attempt has been rejected by SQL Server.

To add to the Picture:

This are the message from the SMS_Site_Backup log on the Component Status.

...Site Backup failed. The error reported by the service is Error: Failed to send start message to the SqlBackup.. Backup operation is not completed. Please see smsbkup.log for more information.

...Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the site database. It cannot start the new backup until the previous backup task is completed.

Which I believed the backup trigger is on the loop or stalled and because of this another attempt has been rejected by SQL Server.

• Edited by Arnel-101 22 hours 55 minutes ago Clarity

To answer your question; No, the SMS_SITE_BACKUP services is no longer running. I believed the SCCM Triggered the backup perfectly but as you can see below message from the log. Which I believed the backup trigger is on the loop or stalled and because of this another attempt has been rejected by SQL Server.

To add to the Picture:

This are the message from the SMS_Site_Backup log on the Component Status.

...Site Backup failed. The error reported by the service is Error: Failed to send start message to the SqlBackup.. Backup operation is not completed. Please see smsbkup.log for more information.

...Site Backup found that the SMS SQL Backup service on the SQL machine is currently backing up the site database. It cannot start the new backup until the previous backup task is completed.

Which I believed the backup trigger is on the loop or stalled and because of this another attempt has been rejected by SQL Server.

• Edited by Arnel-101 Thursday, August 20, 2015 8:57 AM Clarity

Hi ,

For the clustered SQL instance as the SCCM DB, during setup, you must enter the name of the virtual SQL Server cluster instance, and not the virtual Windows Server name created by the Windows Server cluster. Installing the site database using the Windows Server cluster virtual instance name will result in the site database being installed on the local hard drive of the active Windows Server cluster node, and it will prevent successful failover if that node fails.

http://technet.microsoft.com/en-us/library/bb680513.aspx

• Please check on all cluster nodes if the SMS_SERVER_BOOTSTRAP_<server> service is installed.
• Please failover the SQL instance to another node and see if the SQL service and SCCM still works fine.
• Pease perform a manual backup from the sql management console of the SQL DB. See how it works. Then failover the SQL DB to another node and back up the DB again.

Maybe the following link may give some clues.

1. Please backup the SQL DB and SCCM site server as well as the Registry before we do the following actions.

2. Please DO these actions in the test environment first before we apply it to the product one.

http://www.systemcenterblog.nl/2012/06/01/moving-a-configmgr-2012-database-to-a-sql-cluster/#more-1973
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Regarding how to setup the clustered sql for SCCM, please see:

https://technet.microsoft.com/en-us/library/hh427336.aspx#BKMK_SiteDB_SQLCluster

Thanks.

This is an interesting information, let me look at this brother hoping this may guide me with the issues I have, I will let you know the outcome.

Dear Sir,

I have the same problem and almost exactly the same scenario. Please help...