October 12, 2011 at 7:11 am
Hi All,
Restore job is keep on failing due to the below error.
Message
2011-10-12 04:01:16.11*** Error: The log backup file '\\xxxx\x$\MSSQL2K\MSSQL\Backup\WSB\xxxx_20111012064500.trn' was verified but could not be applied to secondary database 'xxxx'.(Microsoft.SqlServer.Management.LogShipping) ***
2011-10-12 04:01:16.12Deleting old log backup files. Primary Database: 'xxxx'
and in tlog-report i found the last restored backup that is
xxxx_20111012054501.trn with this i tried to restore in between backups but i am recieving the following errors
Msg 3203, Level 16, State 1, Line 1
Read on "\\xxxx\x$\MSSQL2K\MSSQL\Backup\WSB\\xxxx_20111012060000.trn" failed: 38(Reached the end of the file.)
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
Can any one suggest me to come out of this problem?
Regards,
Harish
October 12, 2011 at 7:48 am
do you have any log backups happening outside of the log shipping plan?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 12, 2011 at 7:56 am
That log backup file is damaged and hence not restorable.
You're going to have to take a full or diff backup of the source, restore over the secondary and then delete log backups prior to that.
Also look at your IO subsystem and network. Something truncated that file.
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 12, 2011 at 7:56 am
Perry Whittle (10/12/2011)
do you have any log backups happening outside of the log shipping plan?
If there was, the error would be that the log backup is too new to apply to the database.
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 12, 2011 at 8:40 am
GilaMonster (10/12/2011)
Perry Whittle (10/12/2011)
do you have any log backups happening outside of the log shipping plan?If there was, the error would be that the log backup is too new to apply to the database.
yep, goofed up there, only concentrated on the "couldnt be applied to the secondary" message.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
October 12, 2011 at 8:47 am
no other place tlogs are taking place
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply