SQL Server Performance Forum – Threads Archive

Point in time restore while LS in progress.

Hi all,
I have set up a log shipping pair using the database mainentance plan wizard, set full backup every day on primary, 15 mins interval for transaction shipping. My questions are :
1) Is it possible to perform a point in time restore on the primary database using the database backups/transaction logs generated by logshipping?
2) If so how?
3) Will the changes on the restored primary then be shipped across Many Thanks.

Then what is for secondary server, in case of disaster recovery you can setup secondary server as a primary server. Refer to the books online about invoking the process. All the changes on the primary database will be shipped accross the secondary server with the log shipping. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided Ã¯Â¿Â½AS ISÃ¯Â¿Â½ with no rights for the sake of knowledge sharing.

Thanks for the reply satya, I’ve actually sorted it out now to be honest. The secondary server is there as a fail-over so that we may continue to do business with up to the last 15 minutes transactions.
The point in time restore was in case a mistake made its way onto the primary database and was shipped to the secondary without us noticing.

Arg, back again <img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ /> Well I got everything working fine except when restoring the primary server to a previous point in time breaks the log shipping on the secondary server. The secondary server does NOT restore any logs after you restore the primary as the transaction log sequence is out of order. Is there a quick fix around this apart from either: 1. Restoring the secondary from same backups I used on the primary 2. Deleting the secondary database and running the entire Database Maintenance Task wizard to restart the process. Thanks again

Just to answer myself again as reference for anyone else trying this, you cannot simply restore the primary db, you must re-initialise any log shipping pairings afterwards.

Appreciate your feedback and thats what been referred in books online about role reversal in order to continue the log shipping. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided Ã¯Â¿Â½AS ISÃ¯Â¿Â½ with no rights for the sake of knowledge sharing.

]]>