Comments
Sort by recent activity
I don't know what happened, but since I added that step, the job took 6 days to encounter another failure, instead of the numerous times per day. Here's the data in that table:
status | count
4259848 | 745 / comments
I don't know what happened, but since I added that step, the job took 6 days to encounter another failure, instead of the numerous times per day. Here's the data in that table:
status | count
4259...
Correct, the status value didn't change, which supports why it didn't show in the SQL error log.
I've added the extra column. / comments
Correct, the status value didn't change, which supports why it didn't show in the SQL error log.
I've added the extra column.
Ok, we have an error again:
SQL Backup log file 5.2.0.2825
2/15/2008 2:15:00 PM: Backing up dbadmin (transaction log) to:
2/15/2008 2:15:00 PM: d:\MSSQL\Backup\dbadmin\LOG_dbadmin_20080215141500.sqb
2/15/2008 2:15:00 PM: BACKUP LOG [dbadmin] TO DISK = '<AUTO>' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', INIT, ERASEFILES = 5, MAILTO_ONERROR = '<<emailaddress>>', COPYTO = '\\<<servername>>\SQLBackup$\<SERVER>\<DATABASE>\', LOGTO = 'D:\MSSQL\Backup\\_LogFiles', FILEOPTIONS = 1, COMPRESSION = 1
2/15/2008 2:15:30 PM: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had elapsed.)
2/15/2008 2:15:30 PM: SQL error 3013: BACKUP LOG is terminating abnormally.
2/15/2008 2:15:30 PM: SQL error 4208: The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
And here are the most recent results from the debug table:
refdate status recoverymodel
2008-02-15 14:15:00.213 4259848 SIMPLE
2008-02-15 14:00:01.300 4259848 SIMPLE / comments
Ok, we have an error again:
SQL Backup log file 5.2.0.2825
2/15/2008 2:15:00 PM: Backing up dbadmin (transaction log) to:
2/15/2008 2:15:00 PM: d:\MSSQL\Backup\dbadmin\LOG_dbadmin_20080215141500....
I don't believe I didn't realize this until it happened :roll: ... that query won't work, since the table is automatically cleaned up after the job completes, since there's no longer a reference to it. I changed the code to create a permanent object, so now it will capture and remain. :P / comments
I don't believe I didn't realize this until it happened :roll: ... that query won't work, since the table is automatically cleaned up after the job completes, since there's no longer a reference to...
Ok, I've added the query as step 1. The next time it fails I'll pull the values from the temp table. / comments
Ok, I've added the query as step 1. The next time it fails I'll pull the values from the temp table.