February 8, 2006 at 9:16 am
We are trying to come up with a good backup/replication plan for our Servers.
We have a database that is now 1.5GB (After a year) and need to create a backup server in case of an emergency.
I'm playing with the idea of replicating the data to our backup (standy server) and then using log shipping to create backups during the day in the event that we need to restore to a point in time.
I've evaluated Sonasafe, but it appears to be a glorified log shipping tool (with some cool features) and the backup server doesn't appear to keep within the 1 minute latency that replication offers.
Does anyone know an easier way to do this, or if there are any reasons this is a bad idea.
Our primary server has a peak of 10% utitilization, so I'm not worried about too many resources on the primary, but the secondary will be taxed if it has to be used by the clients directly. Thank you in advance for your help.
February 8, 2006 at 10:48 pm
if you have a server + backup setup and up to doing the log shipping yourself, this will be the better approach compared to replication (since you do not need to retrieve the data online from the backup)
HTH
February 9, 2006 at 9:27 am
For log shipping, I think many people here would agree that rolling your own is the best way to go. I wouldn't think that a 1 minute latency is required for a backup server. If the primary fails, grab the last transaction log from there, if it's recoverable, and use it to bring the backup online.
I'm sure searching the scripts will bring up a couple hits on log shipping, as I got a log shipping system built using a script from here.
So long, and thanks for all the fish,
Russell Shilling, MCDBA, MCSA 2K3, MCSE 2K3
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply