• n00bDBA (8/30/2012)


    Hi Perry thanks!

    Can i just confirm im understanding it right.

    CASE 1 - logs retained on Primary and secondary for 24 hours - 1 hour LINK down

    10:00 - Log backup of Primary

    10:01 - Copy log to Secondary

    10:05 - restore log to Secondary

    10:10 --- WAN LINK DIES...

    10:30 - Log backup of Primary

    11:00 - Log backup of Primary

    11:10 --- WAN LINK RESTORED --

    11:30 Log backup Primary

    11:31 - copy of 10:30, 11:00 and 11:30 to Secondary

    11:35 - Restore of 10:30, 11:00 and 11:30 to Secondary

    CASE 2 - logs retained on Primary and secondary for 24 hours - Multi day LINK down

    Fri 10:00 - Log backup of Primary

    Fri 10:01 - Copy log to Secondary

    Fri 10:05 - restore log to Secondary

    Fri 10:10 --- WAN LINK DIES ---

    Tue 9:00 ---- WAN LINK RESTORED ---

    Tue 9:01 - Disable all Log Shipping Jobs

    Tue 9:05 - Differential Backup of Primary

    Tue 9:10 - Restore Differential backup to Secondary

    Tue 9:15 - Move all Log files from Primary backup location and Secondary

    Tue 9:20 - Enable all Log shipping Jobs

    Tue 9:30 - Log backup of Primary

    Tue 9:31 - Copy log to Secondary

    Tue 9:35 - Restore log to Secondary

    Tue 9:40 - Return log file to backup locations for Primary and Secondary

    Thanks for the help!

    72 hours, so

    in case 1 the copy and restore jobs would not have any affect as the copy job would not be able to access the primary backup share (you'd probably get an error). After an hour when the link is back up, the copy job would see the new files on the primary backup share and copy them across to the secondary. The restore job will restore any new backups that it finds.

    in case 2 the same thing would happen in that the copy job would not be able to access the primary backup share. Now, if it's a failure that you are aware of you would stop the 2 jobs on the secondary or just leave them to run expecting no action and manually retain the log backups by adjusting the purge threshold. If you're not aware then the jobs will just run as usual and do nothing anyway.

    Assuming you aren't aware of the failure do this

    Tue 9:00 ---- WAN LINK RESTORED ---

    Tue 9:01 - Disable all Log Shipping Jobs

    Tue 9:05 - Differential Backup of Primary

    Tue 9:10 - Restore Differential backup to Secondary

    Tue 9:15 - Move all Log backup files from Primary backup location and Secondary

    Tue 9:20 - Enable all Log shipping Jobs

    Tue 9:30 - execute LS Log backup job on Primary

    Tue 9:31 - execute LS Copy job on Secondary

    Tue 9:35 - execute LS Restore job on Secondary

    LS should carry on as usual

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉