April 14, 2014 at 12:53 am
Hi,
I cant able to take the database full backup its says database log file is corrupted. Please find the attached screenshot for your ref.
Its very urgent. Please help on this.
Pradeep
April 14, 2014 at 12:59 am
Have you checked the error log? What information captured in it? Is this production server? Have you executed DBCC CHECKDB?
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 14, 2014 at 1:25 am
Yes its a production server and already executed DBCC CHECKDB command but there was no error found.
Pradeep
April 14, 2014 at 3:35 am
You haven't updated error from sql error log?
Can you restore with command line?
BACKUP DATABASE <DBNAME> TO DISK = '<PATH>'
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
April 14, 2014 at 3:53 am
Use backup log with TRUNCATE_ONLY option to truncate the log entries from .ldf file and run a full backup. It should work. But I would really recommend to have your I/O subsystem checked once with people who are responsible to manage this...
April 14, 2014 at 3:59 am
What does the error log say?
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
April 14, 2014 at 4:20 am
Error log is :
Backup detected log corruption in database Wss_Content. Context is Bad Middle Sector. LogFile: 2 'D:\Data\xxxx_log.ldf' VLF SeqNo: x280d VLFBase: x10df10000 LogBlockOffset: x10efa1000 SectorStatus: 2 LogBlock.StartLsn.SeqNo: x280d LogBlock.StartLsn.Blk: x8477 Size: xcc00 PrevSize: xec00
Pradeep
April 14, 2014 at 4:22 am
Oooh, a sharepoint content database...
Switch the database into simple recovery, checkpoint, checkpoint, checkpoint, (and a few more just to be sure), switch the DB back to full recovery and take a full backup, then you should be able to resume both full and log backups without error.
Then get the storage people to have a look at the IO subsystem for problems.
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 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply