Log Shipping
-
Hi,
I am seeing the following error message "Error: The log in this backup set begins at LSN 28000000019500001, which is too recent to apply to the database. An earlier log backup that includes LSN 28000000014500001 can be restored." in Restore agent history. when i verify this issue i found that there are two log files are missing in the both backup & copy folder which need to be restored to continue the restore process successfully.
Pls let me know how to resolve this issue.
Thanks in advance.
-
you will have to try and find those missing log backups and manually copy them over and restore them. If you cannot find them or someone has truncated to log of the primary you will have to restore a full backup and restart log shipping process. (you don't need to remove logshipping, just re-initialise it)
Look in the errorlog for the primary server it will list out all transaction log backups taken.
---------------------------------------------------------------------
-
george sibbald (1/10/2010)
you will have to try and find those missing log backups and manually copy them over and restore them. If you cannot find them or someone has truncated to log of the primary you will have to restore a full backup and restart log shipping process. (you don't need to remove logshipping, just re-initialise it)Look in the errorlog for the primary server it will list out all transaction log backups taken.
Thanks for your reply ...
i could not find out the missing log backups so i have to restore the full backup of the database in the secondary database so kindly let me know the steps which i need to follow to resolve this issue.
-
disable all logshipping jobs
on primary move log backups out of logshipping directory to another directory
on secondary delete log backups from log shipping directory
on primary take full backup (ensure db in full or bulk-logged mode)
copy to secondary
restore on secondary with options replace,norecovery
manual run of log backup, copy, restore to ensure all ok
enable log shipping jobs
---------------------------------------------------------------------
-
How can you be missing two log backups? You should check what happened to the two log backups as it may ocuur again.
-
george sibbald (1/10/2010)
disable all logshipping jobson primary move log backups out of logshipping directory to another directory
on secondary delete log backups from log shipping directory
on primary take full backup (ensure db in full or bulk-logged mode)
copy to secondary
restore on secondary with options replace,norecovery
manual run of log backup, copy, restore to ensure all ok
enable log shipping jobs
Thanks for your help .. i have resolved the issues and its working fine.
-
Hi Sudhakara, did you findout what happened to the transaction log backups?
-
sudhakara (1/11/2010)
george sibbald (1/10/2010)
disable all logshipping jobson primary move log backups out of logshipping directory to another directory
on secondary delete log backups from log shipping directory
on primary take full backup (ensure db in full or bulk-logged mode)
copy to secondary
restore on secondary with options replace,norecovery
manual run of log backup, copy, restore to ensure all ok
enable log shipping jobs
Thanks for your help .. i have resolved the issues and its working fine.
good. no probs.
---------------------------------------------------------------------
-
Guys one more thing.. if I restore differential backup on secondry in place of full backup will it work???
Sudhakara it's always a good practice to post the solution also once you've got it on your own.. Might help someone else.....
Cheers...!!!!
-
Ramji-480085 (1/11/2010)
Guys one more thing.. if I restore differential backup on secondry in place of full backup will it work???Sudhakara it's always a good practice to post the solution also once you've got it on your own.. Might help someone else.....
Cheers...!!!!
the resolution sudhakara used is contained in his last post.
it wouldn't work as would not match to same starting full backup (unless you only recently set up log shipping.
edited - my original reply was rubbish!
---------------------------------------------------------------------
-
George, I know that the solution you gave helped to solve the problem, but I found it far more important to figure out what happened to the two transaction log backups he lost.
-
Ramji29 (1/11/2010)
Guys one more thing.. if I restore differential backup on secondry in place of full backup will it work???Sudhakara it's always a good practice to post the solution also once you've got it on your own.. Might help someone else.....
Cheers...!!!!
you can restore from a differential backup that was taken after you applied the most recent full backup..to ensure continuity of data recovery...
HTH..
The_SQL_DBA
MCTS"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
-
Ignacio A. Salom Rangel (1/11/2010)
George, I know that the solution you gave helped to solve the problem, but I found it far more important to figure out what happened to the two transaction log backups he lost.I share the same thoughts Salom. What happened to the two log backups and what if it happens again?...:w00t:
The_SQL_DBA
MCTS"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
-
Ignacio A. Salom Rangel (1/11/2010)
George, I know that the solution you gave helped to solve the problem, but I found it far more important to figure out what happened to the two transaction log backups he lost.fair enough but its important he has his logshipping and therefore DR solution working until he can track down the cause.
---------------------------------------------------------------------
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply