I'll also assume you're talking about SQL Server backups. On my servers, I run complete database backups overnight to a backup file named with that day of the week. And then during the day, I run incremental transaction log backups every five minutes to backup files named by the day of the week as well. So, if I ever have to restore anything, I restore from "yesterday's" full backup, and then replay the current day's transaction log. I backup to a share on another server, and then at night, those .bak files go to tape. I like having seven days of data, because if something goes wrong, such as a user error that creates a domino effect that goes unnoticed for a couple of days, there is always the option to roll everything back to prior to that user error if it's totally necessary. Ray at work > -----Original Message----- > From: Chris Berry [mailto:compjma@xxxxxxxxxxx] > > I would like to minimize the possibility of this multi-day > rollback, but I > have very little budget to accomplish this. Less than a > thousand dollars up > front or two hundred a month (most likely). I'm considering > implementing > some sort of second backup system, possibly an online backup. > Does anyone > have any suggestions, recommendations, ideas, etc.? > > ********************************************************************************************************** The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. Distribution, publication, or retransmission of this message is strictly prohibited. This message may be a bank to client communication and as such is priviliged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. The sender of this e-mail specifically "opts-out" of the Electronic Signatures and Global and National Commerce Act (E-Sign) and any and all similar state and federal acts. Accordingly, but without limitation, any and all documents, contracts, and ageements must contain a handwritten signature of the sender to be legal, valid, and enforceable. ********************************************************************************************************** ******************************************************** This Weeks Sponsor Pearl Software Internet Monitoring, Filtering, and Control Solutions Enabling User & Group Level Oversight & Access Policies Fully Functional in a Thick or Thin Client Environment http://www.pearlsw.com ********************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm