Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Log Shipping Woes 1

Status
Not open for further replies.

peterlyttle

Technical User
Nov 6, 2006
139
GB
Having already raised 3 support calls with MS taking weeks to conclude I finally thought I had cracked it... until yesterday morning that was.

DB1 that is log shipped SQL1 to SQL2 on a 15min interval.

This was working for 6 days until Monday morning when I see the following messages in the ERRORLOG file.

2009-09-13 00:01:00.48 Backup BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.
2009-09-13 00:01:00.56 Backup BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.
2009-09-13 00:05:00.81 Backup Error: 3041, Severity: 16, State: 1.
2009-09-13 00:05:00.81 Backup BACKUP failed to complete the command BACKUP LOG DB1. Check the backup application log for detailed messages.

Anyone have any ideas?
Cheers,
Peter
 
Well, the BACKUP LOG WITH TRUNCATE_ONLY command has been deprecated.

Why is someone running that command?

I'm not quite sure what your question is.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Nobody is running the command, at the time is 00:01 and nobody is in the office.

My question is, are there any specific things I can look at as to why this command might be issued or happening?
 
Check for a SQL Job that runs it, or that calls a stored procedure that runs it. The database won't be running it by it self without someone telling it to.

You may want to setup a SQL Profiler trace and see what it says about who is running the command, and from what machine.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Having read through far too many SQL jobs, there was one with a line at the bottom truncating the TRN log!! Cheers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top