July 2, 2010 at 2:50 pm
Hi,
At the time of running the sql server log backup job its giving the error message "BACKUP LOG cannot be performed because there is no current database backup.". But full backup of the database has been taken before running the the log backup job.
what could be reason for the log backup failure ?
so again i run the full backup of the database and rerun the log backup job then its running fine. can anyone explain reason behind this ?
Thanks in Advance.
July 2, 2010 at 3:26 pm
Sometime after the full backup was taken - the log chain was broken. Once that happens, no further transaction log backups can be taken until the log chain is re-established.
Two common reasons for this are:
BACKUP LOG ... WITH TRUNCATE_ONLY;
And,
ALTER DATABASE ... SET RECOVERY SIMPLE;
and then later,
ALTER DATABASE ... SET RECOVERY FULL;
You should review the Managing Transaction Logs article I link to in my signature.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 2, 2010 at 7:11 pm
If the reasons Jeff mentioned were the cause of your issue, you can find out when those actions were performed by checking the SQL Server log. Recovery model changes would be logged as follows:
Setting database option RECOVERY to SIMPLE for database ...
And backing up the log with the TRUNCATE_ONLY option would raise the following warning:
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
July 3, 2010 at 10:11 am
Hi,
Thanks for your reply.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply