November 22, 2011 at 6:00 pm
One of our backups is failing with the following message. I ran dbcc checkdb and dbcc checkdb with Physical_only. These did not bring up any errors.
What else should I try:
Processed 53312 pages for database 'MED_PROD', file 'Primary' on file 1. Processed 2971120 pages for database 'MED_PROD', file 'DATA_1' on file 1. Processed 2678288 pages for database 'MED_PROD', file 'DATA_2' on file 1. Processed 2763624 pages for database 'MED_PROD', file 'DATA_3' on file 1. Processed 2803336 pages for database 'MED_PROD', file 'DATA_4' on file 1. Processed 2941152 pages for database 'MED_PROD', file 'DATA_5' on file 1. Processed 16 pages for ... The step failed.
November 22, 2011 at 10:16 pm
Very limited information for any one to answer.
Please submit your DBCC checkdb output and the complete error log of the backup.
November 23, 2011 at 6:48 am
dbcc checkdb did not find any errors. It came back saying 0 erorrs found.
Log only shows the error that I posted earlier.
November 23, 2011 at 7:26 am
check out the SQL errorlog at the time the backup runs for any further info.
If this is a maintenance plan job check the txt output file in the log directory, or add an output file via the advanced tab in the job step.
---------------------------------------------------------------------
November 23, 2011 at 12:47 pm
dbcc checkdb with NO_INFOMSGS did not bring any errors at all.
Job History log viewer does not show any error other than the one I posted. What else should I try?
Software, Inc. Processed 53312 pages for database 'MED_PROD', file 'Primary' on file 1. Processed 2971120 pages for database 'MED_PROD', file 'DATA_1' on file 1. Processed 2678288 pages for database 'MED_PROD', file 'DATA_2' on file 1. Processed 2763624 pages for database 'MED_PROD', file 'DATA_3' on file 1. Processed 2803336 pages for database 'MED_PROD', file 'DATA_4' on file 1. Processed 2941152 pages for database 'MED_PROD', file 'DATA_5' on file 1. Processed 16 pages for ... The step failed.
November 23, 2011 at 12:55 pm
As was already suggested, look at the SQL Server Error Log and post the entries from the log when the backup failed. You can also review the eventvwr in the application log.
November 23, 2011 at 1:39 pm
...not the job history, the .txt file found in the install path\mssql.1\mssql\log directory.
If there isn't one update the job step advanced tab to write to an output file for more information.
---------------------------------------------------------------------
November 23, 2011 at 2:08 pm
SQLServer error.log did not show any relevant info:
2011-11-22 17:49:26.66 Backup Database backed up. Database: MED_PROD, creation date(time): 2011/09/15(13:37:38), pages dumped: 14213712, first LSN: 523142:20326:56, last LSN: 523142:20580:1, number of dump devices: 3, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VDI_08A16498-F8CC-412E-92C5-0FE8BE7E0FF3_0', 'VDI_08A16498-F8CC-412E-92C5-0FE8BE7E0FF3_1', 'VDI_08A16498-F8CC-412E-92C5-0FE8BE7E0FF3_2'}). This is an informational message only. No user action is required.[/color]
November 23, 2011 at 2:20 pm
Output from Job Steps -> Advanced -> output to a file:
Msg 1, Sev 16, State 1: LiteSpeed(R) for SQL Server Version 6.5.1.1018 Copyright 2011 Quest Software, Inc. Processed 53312 pages for database 'MED_PROD', file 'Primary' on file 1. Processed 2971120 pages for database 'MED_PROD', file 'FILE_1' on file 1. Processed 2678288 pages for database 'MED_PROD', file 'FILE_2' on file 1. Processed 2763624 pages for database 'MED_PROD', file 'FILE_3' on file 1. Processed 2803336 pages for database 'MED_PROD', file 'FILE_4' on file 1. Processed 2941152 pages for database 'MED_PROD', file 'DFMsg 0, Sev 16, State 1, Line 249 : [SQLSTATE 01000]
Msg 0, Sev 16, State 1, Line 250 : ------------------------------------------------------------------ [SQLSTATE 01000]
Msg 0, Sev 16, State 1, Line 251 : [SQLSTATE 01000]
November 23, 2011 at 3:05 pm
third party software which makes it a bit more difficult. Looks like the backup may have completed but perhaps the cleanup afterwards failed. Was a backup file produced
What is the latest backup_finish_date for the database returned by this query, does it suggest the backup ran?
select * from msdb..backupset where database_name = 'yourdb' and type = 'D'
---------------------------------------------------------------------
November 24, 2011 at 4:35 am
do you not have an active maintenance contract with Quest?
6.5.1 is pretty recent, so you must have either expired on maintenance somtime after March or purchased 6.5.1 this year in which case you will be covered
November 24, 2011 at 4:45 am
from what I remember as I had the VDI issue with LiteSpeed is that it was down to memory pressure.
try restarting the LiteSpeed service, if that fails restart SQL and LiteSpeed
that was my specific problem, might not be the same for you
November 27, 2011 at 8:10 pm
I ran the query and it returned backup_finish_date with three rows - last night, night before and the night before that.
Does it mean that my backup ran fine? Is there a way I can find the status?
November 28, 2011 at 3:27 am
it says what it looks like, backup has completed for the last three nights.
Are you purging backup history older than 3 days?
---------------------------------------------------------------------
November 28, 2011 at 3:29 am
Seems like the backup was taken by litespeed and during the backup job, there was some problem of disk/network failure.
Can you run the job again by first looking everything in place?
----------
Ashish
Viewing 15 posts - 1 through 15 (of 18 total)
You must be logged in to reply to this topic. Login to reply