August 14, 2013 at 10:56 pm
Hi,
I have Litespeed log shipping configured for SQL 2005. LS went out of sync, when I chked restore job, I saw below error:
RESTORE LOG is terminating abnormally.
MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file.
I found disk is out of space on secondary, we got disk space extended by storage team. I expected that LS would get in sync after that, but then job failed again with below error:
x.trn cannot be applied to database. More earlier transaction log file can be applied. Probably you need to reinitialize subscriber or manually restore database.
I thought some log backup is missing, I chked the backupset table to find the log backup sequence and nothing was missing. All log backups were in the LS folder.
When I tried restoring the next log file manually, I got below error:
LiteSpeed(R) for SQL Server Version 6.5.2.1042
Copyright 2011 Quest Software, Inc.
Msg 62301, Level 16, State 1, Line 0
SQL Server has returned a failure message to LiteSpeed for SQL Server which has prevented the operation from succeeding.
The following message is not a LiteSpeed for SQL Server message. Please refer to SQL Server books online or Microsoft technical support for a solution:
RESTORE LOG is terminating abnormally.
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
A previous restore operation was interrupted and did not complete processing on file 'file1'. Either restore the backup set that was interrupted or restart the restore sequence.
A previous restore operation was interrupted and did not complete processing on file 'file2'. Either restore the backup set that was interrupted or restart the restore sequence.
A previous restore operation was interrupted and did not complete processing on file 'file3'. Either restore the backup set that was interrupted or restart the restore sequence.
And then we gave up and reconfigured it using full backup. Now when I am looking at the error again and again I feel I should have tried restore with restart.
What can be the possibility of this LS failure? Partial tlog restore?Where (any system table) can I find info about partial restore?
Regards,
Sonali
September 4, 2013 at 11:52 am
Did you find any solution?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply