February 13, 2013 at 6:21 am
We have nightly backups configured for the Team Foundation Server TFS databases. Recently, the transaction log backup for the TFS_Warehouse database is failing with the following message:
'Backup detected log corruption in database Tfs_Warehouse'
We are doing a backup of the database and the transaction log for this database. The backup seems to complete successfully and a .bak file is created. A .trn file is not created however.
My question is How can the transaction log be repaired without getting the database out of sync from the other TFS databases or losing data?
The corruption occurred a week ago and there has been TFS checkins and data committed to the Tfs_Warehouse database since the corruption occurred. We keep backups for 14 days but if we go back pre-corruption, the last time the transaction log .trn backup succeeded, we would lose all data since.
What would be the best approach here?
Thanks in advance for any suggestions
February 14, 2013 at 9:28 am
Could be a section of the LDF file that is corrupt, does DBCC CHECKDB return any errors? Below is a link which could be of help to you.
http://www.sqlskills.com/blogs/paul/how-can-a-log-backup-fail-but-a-full-backup-succeed/
On another note I would also start checking the disk subsystem, corruption doesn't just happen.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply