SQL Log shipping internet disconnection

Dears,

I have my SQL Transaction log shipping between My main site and DR site.

  • Jobs are running every 2 hours
  • I keep the history for 3 days

The connection between main and dr site will be down for 1 day, so:

  1. What shall I do as a a best practice?
  2. If I kept the servers up and running, so what will happen when connection is again online after 1 day? (is copy and restore job will work fine and restore all the data or there is chances that it will be not consistent or will not be able to restore)

Thanks

July 22nd, 2015 9:03am

Hi,

As you mentioned you retain log backup files for 3-days, your DR server should be able to copy these files & restore them on secondary replica without any issues once the connectivity is online.

Since DR site has to copy the pending files (24 hrs), your DR server might take some time to be in sync with primary, you need to monitor this.

Free Windows Admin Tool Kit Click here and download it now
July 22nd, 2015 10:00am

when your connection goes down logshipping will not happen. It does not mean your logshipping is broken.

your log backus job still runs as scheduled. copy job fails due to no connection. 

Once your connection is back all files will be shipped automatically and restored in order at your secondary. How ever you need to keep an eye it may fail for some other reasons.

if you want you can manually ship the files to the secondary servery. restore job will pick the right file as it know the sequence. 

July 26th, 2015 10:24pm

What shall I do as a a best practice?
  1. If I kept the servers up and running, so what will happen when connection is again online after 1 day? (is copy and restore job will work fine and restore all the data or there is chances that it will be not consistent or will not be able to restore)

Thanks

1. Nothing much just stop all jobs related to logshipping on both servers.

2. Since you stopped the jobs LS is there but since LS jobs are not working there would be no transaction log generated so no copy and no restore job will also come into picture.

But make sure you do not do big transactions on primary because when you start LS backup job it would produce BIG .trn file and it would take quite few amount of time to get copied and restored and in that case you might start getting delay alerts

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 12:31am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics