What kind of database? MS SQL Server? What I do here is set the SQL agent to perform a backup to disk, then that directory is what gets copied to tape. It removes files older than two days when it finishes so I always have my least two backups on disk before I have to break out a tape. I do the same thing with a script for mysql. The script stops the service, runs xcopy to dump the data directories to a backup folder, the restarts the service. Takes about 30 seconds. This would be cheap to do. All you need is disk space. The tape is then your second line of defense, not your first. You could even go as far as getting a cheap NAS device like the one from iomega and just use it to hold backups. Run your tapes against that for a permanent archive. Sorry for the top post. I know you hate that. It's late. Greg -----Original Message----- From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx]On Behalf Of Chris Berry Sent: Wednesday, October 29, 2003 5:40 PM To: oclug@xxxxxxxxx; windows2000@xxxxxxxxxxxxx Subject: [windows2000] Backups Currently we use a 60gb Onstream Tape drive and Veritas Backup Exec to backup our data nightly to tape. The tape drives are not that great, and we're only getting about 6000 hours meantime between failure, in addition the restore success rate is only about 95% (As in it fails about one time in 20, so if I have a month of backups one of them is probably bad). Considering the low cost of the tape drives ($350) this isn't that surprising, but I don't have the budget available to buy a decent system ($5k-$12k). There is a small subset of our data (the database dat files) that is both mission critical and very time sensitive (currently about 2.3gb worth, but growing about a meg a day). Because of the way the databse works there cannot be any competing file access (a file locking issue) so I can't use any kind of hot backup system. So far while I've been working here there have been a number of times where we've had to restore from the previous day's backup which is bad enough but not my fault, however on three occassions, we had to go more than one day back because the data wouldn't restore properly. 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.? Chris Berry compjma@xxxxxxxxxxx Systems Administrator JM Associates "Live dangerously, overclock your servers." _________________________________________________________________ Add MSN 8 Internet Software to your current Internet access and enjoy patented spam control and more. Get two months FREE! http://join.msn.com/?page=dept/byoa ******************************************************** 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 ******************************************************** 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