August 12, 2009 at 4:19 pm
Hi,
We are configuring log shipping for a production server which is in location A. The secondary server is in location B which is 1000 miles away.
Now we want to take a full backup of the databases on Primary and then directly copy to Secondary and then restore & configure Log shipping. Total size of all databases bakups (.bak) is around 15GB, which will take approximately 10hrs to copy.
Is this a good practice to copy backup files from Production server to a remote server?or take the full backup and copy to Tape and then send the Tape to Location B and then restore & configure log shipping ?
how you guys do?
please advice
setting up log shipping for prodution server
August 12, 2009 at 8:59 pm
it's a time and bandwidth issue.
If it takes 10 hours to copy, the secondary is then "backup time" + 10 hours + restore time = time behind primary when you start log shipping.
Now, you can start copying logs as soon as the first backup is finished, so I'd think that unless your logs are large, you'll catch up at some point.
The thing you need to do is look at the sizes of the log files. How long between backups (meaning minutes of data in each backup), and how long it takes to copy the file to the secondary. That will tell you how far behind your secondary will be and if it's feasible. If you can't copy and restore the logs, it doesn't matter about the full.
Assuming you can copy the logs in a reasonable time, then decide if it's quicker to send a full + a few backups through the post or through the network.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply