August 23, 2013 at 11:39 am
GilaMonster (8/23/2013)
Once more with feeling...Full backups DO NOT break the log chain.
Therefore, to re-initialise the secondary after the drill, take a full backup of the primary, copy it, restore it, restart the log copying jobs. Done.
Would it help to add second emphasis??
I have done as Gail just said numerous times. Most recently just this morning.
If you are restoring the database "with recovery" you are putting the database into a state where more tlogs cannot be restored. Are you by chance doing the restore "with recovery."
When restoring the full backup to "re-initialize" log-shipping, you need to do it with "norecovery", then subsequent tlogs can be restored.
However, Gail also made another important point. That point being that if t3 was taken prior to f2, then t3 cannot be restored because the LSN is prior to that of the full backup. This is not a broken log chain because f2 has a more recent chain and the log backups from after f2 can still be applied.
To further support what Gail has said, I have clients with numerous logshipped databases. Most of these databases have a full nightly that is performed. This full backup has no impact on the log chain ever. Logshipping continues without blinking.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 24, 2013 at 1:04 am
GilaMonster (8/23/2013)
Once more with feeling...Full backups DO NOT break the log chain.
Therefore, to re-initialise the secondary after the drill, take a full backup of the primary, copy it, restore it, restart the log copying jobs. Done.
@Gail problem is there are 2 dr of a single primary and only is participating in DR drill so i cannot stop ls backup job at primary.i know full log bkps donot break lsn chain but then full bkps restore does .so i was asking whether t3 (backup which was taken to prior f2 backup), can it be restored after f2 full backup was restored (with standy,replace) at secondary
SQLRNNR (8/23/2013)
GilaMonster (8/23/2013)
Once more with feeling...Full backups DO NOT break the log chain.
Therefore, to re-initialise the secondary after the drill, take a full backup of the primary, copy it, restore it, restart the log copying jobs. Done.
Would it help to add second emphasis??
I have done as Gail just said numerous times. Most recently just this morning.
If you are restoring the database "with recovery" you are putting the database into a state where more tlogs cannot be restored. Are you by chance doing the restore "with recovery."
When restoring the full backup to "re-initialize" log-shipping, you need to do it with "norecovery", then subsequent tlogs can be restored.
However, Gail also made another important point. That point being that if t3 was taken prior to f2, then t3 cannot be restored because the LSN is prior to that of the full backup. This is not a broken log chain because f2 has a more recent chain and the log backups from after f2 can still be applied.
To further support what Gail has said, I have clients with numerous logshipped databases. Most of these databases have a full nightly that is performed. This full backup has no impact on the log chain ever. Logshipping continues without blinking.
I am restoring full bkps with standby option.I ma still struggling to find ans how to bring primary and secondary in sync after dr drill
Ok what i want to know now is can tlogs backup can be applied more then once on secondary server.once which had been previously restored
Thanks everybody for help
Regards
Anoop
August 24, 2013 at 3:12 am
anoop.mig29 (8/24/2013)
@Gail problem is there are 2 dr of a single primary and only is participating in DR drill so i cannot stop ls backup job at primary.
I never said stop the backup jobs at the primary.
i know full log bkps donot break lsn chain but then full bkps restore does .so i was asking whether t3 (backup which was taken to prior f2 backup), can it be restored after f2 full backup was restored (with standy,replace) at secondary
Only if you restore the primary, which there's no reason for you to do in this case.
Stop the copy jobs to the secondary that you're bringing online (not the backup jobs)
Bring that secondary online (restore with recovery)
Do your DR tests
Once complete, take a full backup of the primary
Restore that over the secondary that you brought online
Restart log shipping to that 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 recoverability
August 26, 2013 at 10:54 pm
GilaMonster (8/24/2013)
anoop.mig29 (8/24/2013)
@Gail problem is there are 2 dr of a single primary and only is participating in DR drill so i cannot stop ls backup job at primary.I never said stop the backup jobs at the primary.
i know full log bkps donot break lsn chain but then full bkps restore does .so i was asking whether t3 (backup which was taken to prior f2 backup), can it be restored after f2 full backup was restored (with standy,replace) at secondary
Only if you restore the primary, which there's no reason for you to do in this case.
Stop the copy jobs to the secondary that you're bringing online (not the backup jobs)
Bring that secondary online (restore with recovery)
Do your DR tests
Once complete, take a full backup of the primary
Restore that over the secondary that you brought online
Restart log shipping to that secondary.
@gail thanks for steps ,
Now can u tell me how to monitor logshiping pr-dr dervers
i mean when i used customized reports i have to visit both pr-dr server to know status.Same is case with proc sp_help_log_shipping_mointor.
IS THERE any way to get information at one place or i have to create some script which would query through link servers.
August 26, 2013 at 11:10 pm
anoop.mig29 (8/26/2013)
GilaMonster (8/24/2013)
anoop.mig29 (8/24/2013)
@Gail problem is there are 2 dr of a single primary and only is participating in DR drill so i cannot stop ls backup job at primary.I never said stop the backup jobs at the primary.
i know full log bkps donot break lsn chain but then full bkps restore does .so i was asking whether t3 (backup which was taken to prior f2 backup), can it be restored after f2 full backup was restored (with standy,replace) at secondary
Only if you restore the primary, which there's no reason for you to do in this case.
Stop the copy jobs to the secondary that you're bringing online (not the backup jobs)
Bring that secondary online (restore with recovery)
Do your DR tests
Once complete, take a full backup of the primary
Restore that over the secondary that you brought online
Restart log shipping to that secondary.
@gail thanks for steps ,
Now can u tell me how to monitor logshiping pr-dr dervers
i mean when i used customized reports i have to visit both pr-dr server to know status.Same is case with proc sp_help_log_shipping_mointor.
IS THERE any way to get information at one place or i have to create some script which would query through link servers.
You could create a script to monitor your servers through linked servers if you don't have a monitor server created for the logshipped databases.
If you create a monitor server for your logshipped databases, you can just run the reports from that server or you can run sp_help_log_shipping_monitor from the monitor server.
I have a client that has both the monitor server and we also use separate scripts to help monitor the primary and secondary servers in the logshipped databases.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply