I have a customer that runs log backups every hour. For some systems they can't loose more than 5 minutes of data. For those systems they implement clustering. Going with Marks idea can they afford to wait 10 hours for you to replay logs. In that time they can't backup the data because you are running a restore. If the real need is full time access to data without 0 potential for data loss then they shouldn't be relying solely on a backup application.
Luc Beaudoin <[EMAIL PROTECTED]> wrote: Hi Mark ... So with that setup ... worst case ... they will loose 4 hours of work ??? I'm working in a hospital ... so even 1 hours lost of lab result or patient appointment can be kind of hell anyway .. if there is no way of putting minutes ... I will put the minimum ... 1 hours ... thanks a lot Mark Luc "Stapleton, Mark" Sent by: "ADSM: Dist Stor Manager" 2004-09-21 04:28 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: schedule of SQL LOG backup From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Luc Beaudoin >I thought of doing Full backup every 8 hours and LOG backup >every 20 minutes ... >Is there a best pratice for SQL backup ?? What works best is whatever meets your business needs. Most of my customers do a full backup of databases once a day, and periodic log backups (every 4 hours, for example) throughout the day. YMMV. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 --------------------------------- Do you Yahoo!? vote.yahoo.com - Register online to vote today!
