October 15, 2010 at 6:43 am
hello experts,
i checked the history of backup job on primary, and found issue, want to know hw can it suddenly come? BACKUP LOG cannot be performed because there is no current database backup. BACKUP LOG is terminating abnormally.
pls help
October 15, 2010 at 6:51 am
sounds like someone truncated your database log. Take another full backup and restart logshipping from the next log after that full backup.
---------------------------------------------------------------------
October 15, 2010 at 7:06 am
george sibbald (10/15/2010)
sounds like someone truncated your database log.
If this is a SQL 2008 server (it's posted in the SQL 2008 forum), someone switched the DB to simple recovery and back to full without thinking about the implications.
If this is a SQL 2005 server, someone either switched the DB to simple recovery and back to full or ran Backup Log ... with truncate_only without thinking about the implications.
Evidence of that will be in the SQL error log. I suggest you examine the logs, identify the culprit and have words with him/her about proper log management.
Take a full or differential backup to restart the log chain. You will have to re-do the log shipping secondary with latest full backup, differential if applicable then logs before the log shipping will start working again.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 15, 2010 at 7:40 am
u r right, i checked the sql server log, i found that "BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log."
bt rest of this msg m nt able to see anythng, can u suggest how can i get all the detail of this activity like who done this and what command exactly used
October 15, 2010 at 7:51 am
sachinsoni84 (10/15/2010)
u r right, i checked the sql server log, i found that "BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log."
Please post SQL 2005 questions in the SQL 2005 forums in future.
bt rest of this msg m nt able to see anythng, can u suggest how can i get all the detail of this activity like who done this and what command exactly used
Please don't use shortened SMS-type speech here. It's hard enough to understand stuff normally.
The command would have been BACKUP LOG <Database Name> WITH TRUNCATE_ONLY. It's no more than that. Very hard to tell from just the error log who ran it unless you keep an audit trace of logins. Ask the DBAs, it needs fairly high permissions to run. Might be in the default trace, but I will not guarantee that.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply