|
|
Posted by Greg D. Moore \(Strider\) on 06/08/05 15:20
"Jay" <jazemail@gmail.com> wrote in message
news:Hqepe.5753$U4.811596@news.xtra.co.nz...
> I've recently inherited a position where I am responsible for the
well-being
> of some DBs.
> 2 (much) more important than others.
> The current recovery model, from what I can tell, is to do a full db/log
> backup overnight.
> This .bak file is then written to tape as well as saved on the disk for 2
> days.
>
> Both these dbs are used fairly extensively 8-5pm and losing data would not
> be good.
> The db sizes are approx 5gb and 3gb.
> This doesn't seem like the ideal situation to me. Everything I read tells
> me... full backup periodically, differential nightly and transaction
hourly.
> Agreed?
> If so then I have 2 questions:
> 1. Is the best way to do this via a maintenance plan or by scripting and
> scheduling?
For this I'd use a simple maintenance plan to back up your logs every X
minutes.
> 2. What, if any, overhead can be expected with regular transaction backups
> during work hours?
>
VERY little.
We run our transaction log backups every 20 minutes and notice no impact.
(in fact, ironically in some cases, running them MORE often can be better
since they'll be smaller when you do run them.)
> A bit of a pointer to #1 would be appreciated also.
> Thanks.
>
>
Navigation:
[Reply to this message]
|