August 5, 2004 at 9:00 am
I have a db that I will be transfering to a reporting server hourly and also hourly to an offsite over a T1. On the SAN, doing a weekly backup and applying logs and differentials accordingly works fine. I can't apply this same logic because a 100GB backup obviously doesn't move quickly over a T1 and thats of course if its not interupted. Getting a faster line isn't an option. Constantly shipping logs out there would cause my reporting routine to fail once my full backup kicks in. Any ideas? Even if Isent the logs to tape for preservation, in event of recovering, I would have to apply 24 logs per day for every day since my last backup which would be very time consuming.
August 5, 2004 at 9:26 am
Perhaps I'm missing something. Why would your log shipping fail when your full b/u kicks in? The log backups will still be in sequence, as a full backup does not truncate the log. If you are concerned about recovering if you lose your standby database, you can restore your most recent full backup, then apply your logs and keep going. Not sure if I answered your question.
Steve
August 5, 2004 at 10:24 am
what about a differential backup? would that cause a problem?
August 5, 2004 at 10:41 am
No, the only backup that truncates the transaction log is a transaction log backup. You'll be ok doing fulls and diffs.
Steve
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply