Hello and good day!
I'm having an issue with my SCCM backups. Here's the long and short of it...
-Backup fails after "Cleanup of backup location done" message in SMSBKUP.LOG.
-Backup location is now empty.
-If I run a follow-up backup, it is successful.
-This behavior repeats. My analysis is that the cleanup is taking too long, and once done, the backup has already given up waiting and it fails. A follow-up backup works because it doesn't have to wait on the cleanup (as the folder is empty).
The SMSBKUP.LOG log shows the start of the clean was at 6:31pm and completed at 9:14pm. It's taking almost 3 hours to clean up and then I get the following error immediately after the "cleanup done" message.
-Cleanup of backup location done. (9:14:58pm)
-Info: Sending message to SQL Backup to DoSnapshot... (9:14:58pm)
-ERROR: SQL Backup task failed. Error message - Did not receive dosnapshot message in the last 30 minutes. Aborting backup. (9:14:58pm)
Over on the SQL server, in SMSSQLBKUP.LOG, it shows the following:
-Did not receive the dosnapshot message in the last 30 minutes. Aborting backup. (7:00:09)
-Aborting the backup process. (7:00:09)
-Sql backup failed. Please see previous errors. (7:00:09)
then...
-We received a message... (9:14:18pm)
-Message received = Abort (9:14:18pm)
-Abort message received for Sql backup... (9:14:18pm)
-Aborting SQL backup not needed as SQL backup was not running... (9:14:18pm)
So my question is, is a 3 hour cleanup just too long for SCCM? I'm fairly new to SCCM and not sure what is typical. If it's too long, is there a way to find out WHY it's taking so long? Or is there a way to make sure it waits on the cleanup to finish?
I can add full logs is necessary. Thanks very much in advance.
I'm having an issue with my SCCM backups. Here's the long and short of it...
-Backup fails after "Cleanup of backup location done" message in SMSBKUP.LOG.
-Backup location is now empty.
-If I run a follow-up backup, it is successful.
-This behavior repeats. My analysis is that the cleanup is taking too long, and once done, the backup has already given up waiting and it fails. A follow-up backup works because it doesn't have to wait on the cleanup (as the folder is empty).
The SMSBKUP.LOG log shows the start of the clean was at 6:31pm and completed at 9:14pm. It's taking almost 3 hours to clean up and then I get the following error immediately after the "cleanup done" message.
-Cleanup of backup location done. (9:14:58pm)
-Info: Sending message to SQL Backup to DoSnapshot... (9:14:58pm)
-ERROR: SQL Backup task failed. Error message - Did not receive dosnapshot message in the last 30 minutes. Aborting backup. (9:14:58pm)
Over on the SQL server, in SMSSQLBKUP.LOG, it shows the following:
-Did not receive the dosnapshot message in the last 30 minutes. Aborting backup. (7:00:09)
-Aborting the backup process. (7:00:09)
-Sql backup failed. Please see previous errors. (7:00:09)
then...
-We received a message... (9:14:18pm)
-Message received = Abort (9:14:18pm)
-Abort message received for Sql backup... (9:14:18pm)
-Aborting SQL backup not needed as SQL backup was not running... (9:14:18pm)
So my question is, is a 3 hour cleanup just too long for SCCM? I'm fairly new to SCCM and not sure what is typical. If it's too long, is there a way to find out WHY it's taking so long? Or is there a way to make sure it waits on the cleanup to finish?
I can add full logs is necessary. Thanks very much in advance.
