April 3, 2010 at 4:41 am
I do regular full backups of all our sql server databases of soze ranging from 200Gb - 1.5TB using Litespeed @ Compression level=5, most of the time the jobs fail but i am having trouble to find the reason. Here is one of the failed message i have in the sql job log
Executed as user: COMPANY\BkpDmnAct. ...SQLSTATE 01000] (Message 0)
LiteSpeed Version 4.8.3.00025 Copyright (C) 2004-2006, Quest Software Inc.
All Rights Reserved. Quest Software. Registered Name: COMPANY INC
Processed 593456 pages for database 'State_Revenue_Dev', file 'State_Revenue_Dev'
on file 1. Processed 1 pages for database 'State_Revenue_Dev',
file 'State_Revenue_Dev_log' on file 1. BACKUP DATABASE successfully
processed 593457 pages in 356.988 seconds (13.618 MB/sec). Backup added as file number: 1
Native Size: 4637.31 MB Backup Size: 1001.01 MB CPU Seconds: 165.02
Environment: Dual-Core AMD Opteron(tm) Processor 2218 CPUs: 4 logical, 4 core(s),
2 physical processors(s). [SQLSTATE 01000] (Message 1) database backup
in progress: State_Bud_dev [SQLSTATE 01000] (Message 0)
LiteSpeed Version 4.8.3.00025 Copyright (C) 2004-2006,
Quest Software Inc. All Rights Reserved. Quest Software.
Registered Name: COMPANY INC Processed 31138... The step failed.
this is in sql log for the same time
[highlight=""]Date4/2/2010 7:45:56 PM
LogSQL Server (Current - 4/3/2010 6:38:00 AM)
SourceBackup
Message
BACKUP failed to complete the command BACKUP DATABASE State_temp_Rev.
Check the backup application log for detailed messages.[/highlight]
Can someone interprest the reason.
April 3, 2010 at 5:26 am
You appear to be backing up multiple databases in one step...?
The first log entry shows State_Revenue_Dev being successfully backed up.
The second entry shows a failure for State_temp_Rev.
The log output generated by the operation is too long, so it is truncated after the first message.
Either break the backups into separate steps, or change the logging to capture more information.
One way to log more information is to tick the 'output to table' option on the job.
April 5, 2010 at 4:52 pm
I agree with Paul. Start with breaking out the DB backups to separate jobs.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply