Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have two instances of SQL Server 2005 STANDARD edition, Server A in New York and Server B in California.

Server A has a large database; for DR/BCP purposes, I would like to use Log Shipping to keep a warm backup on Server B.

Unfortunately, the transaction logs are too large (over 10GB across a WAN =( ). Before I invest in a third party product that deals with this issue, could I do something like this:

1) Disable the copy job on Server B. Backups are still created on Server A, but are not automatically moved to Server B.

2) Create a scheduled task to compress all backed up logs on Server A (using a tool like 7zip or WinZip), and dump them on Server B where the restore job expects them (and unzipping, of course).

3) Allow the restore job on Server B to work as normal.

Is this a naive or workable solution?

If we had enterprise edition, I would use asynchronous database mirroring; or if we had 2008 Enterprise edition I would look into the built in compression.

share|improve this question

2 Answers 2

up vote 0 down vote accepted

I believe this would work fine. Keep in mind that unless you are using 2008 you'd have to look into some kind of 3rd party tool for the compression anyways.

The only real downside I see is it's a bit more work for you to maintain as you'll be relying on more than just SQL server to do the work.

share|improve this answer

Don't create another scheduled task as the timing can get messed up. Modify the existing sql server generated log shipping jobs for backing up the log & copying the log.

There's a blog post here with a solution that you may want to borrow some or all parts from.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.