March 29, 2012 at 5:57 am
I have transaction log shipping set up for a large database with no problems for the last 6 months. A transaction log backup incurred an I/O error with all subsequent backups successful. The restore process is now failing as the 1 file can not be verified and all other files are out of sequence. Any options for repairing or bypassing the file in question? I am making alternate plans to reinitialize the database but due to its size it is a lengthy and tedious process.
March 29, 2012 at 7:28 am
If you have a log backup damaged and no copy of it, then you'll either have to reinitialise or use a differential backup to bridge the gap in the log chain.
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 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply