Pausing Log Shipping Plans

We are doing an IP Restructuring on our DR site over the weekend due to some business and management requirements.I actually have 2 questions. I have implemented log shipping plans for our databases. Which means I will have to pause (disable) my log shipping plans while this is being done and resume (re-enable) after everything is comlete.

Any insights on what else I need to do apart from these?

My second question is this. I am generating transaction log backups every 15 minutes and is averaging at 350MB (this much data every 15 minutes - not to mention that I've got around 40+ databases, all configured for log shipping just for this instance alone). My alert threshold is 45 minutes. My log shipping plan for one database starts failing probably because 15 minutes is not enough to transfer 300+MB-sized backup file over a WAN locate across the globe on a not-so-high bandwidth and restore it to the destination. Any recommendations on this apart from increasing the threshold? Your assistance is highly appreciated

Log shipping should not be affected by changing the IP addresses unless you change ones targetted directly by the log shipping jobs. For the WAN case, you can consider adding a step to compress the transaction log backups prior to copying them over the network. This typically improves the end-toend throughput over a WAN.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||

Hi Matt,

Thanks for your reply. Actually, we will be changing the IPs of the destination servers You were mentioning compressing the transaction log backups prior to copying them over the network. I am using the Database maintenance plans to define my log shipping plans. The way I see it, the copy job does a "pull" method - the destination server is the one initiating the job. How do you insert a step to compress the transaction log backup files in the database maintenance plans? I am only allowed to use "Microsoft supported" procedures as per company policy

sql