logshipping-
-
HI,
we have a logshipping configured for a db and restore job is failing on the seconday server.Please see below error
012-03-11 10:54:01.28*** Error: The file '\\m2100\backup\cpe7\cpe7_20120309170001.trn' is too recent to apply to the secondary database 'cpe7'.(Microsoft.SqlServer.Management.LogShipping) ***
2012-03-11 10:54:01.28*** Error: The log in this backup set begins at LSN 1826128000000001600001, which is too recent to apply to the database. An earlier log backup that includes LSN 1753252000001009200001 can be restored.
RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***
2012-03-11 10:54:01.30Searching for an older log backup file. Secondary Database: 'cpe7'
2012-03-11 10:54:01.30*** Error: Could not find a log backup file that could be applied to secondary database 'cpe7'.(Microsoft.SqlServer.Management.LogShipping) ***
2012-03-11 10:54:01.30Deleting old log backup files. Primary Database: 'cpe7'
Please let me know how to resolve the error.
Thanks.
-
There's a log backup that was taken on the primary but not copied to the secondary. Probably from someone running an ad-hoc log backup or a second log backup job.
Find the missing log backup (look in MSDB at the backup tables for info on where it was written to) and apply those to the log shipping secondary.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
In case you don't find the missing backup, you can restore a full backup again and leave the secondary database in restoring state.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply