Date: Wed, 18 Apr 2001 08:51:15 -0700 (PDT) From: Rick Duvall <maillist@coastsight.com> To: Mike Meyer <mwm@mired.org> Cc: questions@freebsd.org Subject: Re: Backup and Verify Message-ID: <Pine.BSF.4.21.0104180844530.60328-100000@ns1.coastsight.com> In-Reply-To: <15069.13630.549850.806893@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This box is actually a web server, and the only files that change is when our web developer uploads files to the box, and email coming in. Don't care so much about the email as much as I do the configuration files. Same goes for the web server. Don't care much about the content as much as I do about the config files because my web developer has a copy of the entire site on her PC at work, and at home. In this sense, It would be possible to do a hot backup rather than shutting the system down to single user mode and taking down the entire site. As far as the verify, maybe I am thinking compare.... It would be nice if I could have a Bootable CD, though that one could put in the CD drive, the CD boot and it will ask to put the last backup in the tape drive, and it will restore the last backup. It needs to be as user friendly as possible because I am the only person in this company capable of operating this box, and if for some reason I leave (quit more likely than getting hit by a Mac truck) the average ordinary layman will need to be able to restore everything by following a checklist of procedures. I don't think that they will be able to do a fresh install of FreeBSD, however, and restore over the top. These are bank tellers we are talking about. On Wed, 18 Apr 2001, Mike Meyer wrote: > Rick Duvall <maillist@coastsight.com> types: > > What is the best way to back up a FreeBSD system to tape and verify the > > backup. I have been trying with dump, but I don't know of any way to > > verify that. Then, I tried tar with the -W option, and that didn't work > > (guess my tape drive doesn't support it). Amanda won't work for us > > because I find it isn't really designed for a single box, but rather for > > backing up and restoring multiple boxes, AND it's too difficult for the > > average ordinary layman to do a disaster recovery with Amanda on a totally > > dead system. > > > > Here are my requirements: > > Your requirements are incomplete, and I'm not sure they can be met as > stated. > > > * Backups must be done on the live system (single machine with a tape > > drive) > > This is a bad idea. Not "you must be out of your gourd" bad, but > "you're asking for trouble" bad. Backups of a live filesystem mean > that you can miss files, or dump bad copies of a file. For > incrementals, this is a minor problem - you've got one or two files > that will need be updated tomorrow. For level 0s, this is a bit of a > problem. If some regularly scheduled activity is causing the file to > be missed, it may never get backed up, which is bad. For instance, if > your backups happen in the midst of updating the financial database, > that database will probably never be backed up. > > > * Backups must be level 0 every time, and must be verified. > > You forgot to specify what happens when the verify fails. > > I'd also be interested to know whether the case where a file is backed > up, then changed before the backup is verified. Does the verify fail? > If not, how is the verification done? Can it fail for just one file, > which needs to be backed up again? > > > * Backups must be logged, especially the verify > > > > * After the verify, the tape must eject. > > These are both pretty trivial. > > > * Must have a disaster recovery solution so that if I get hit by a Mac > > Truck, the average joe blow can do the disaster recovery. I prefer a > > bootable cd they can put in which will boot, and ask for the last tape, > > and will do the restore on a new hard drive, partition it and everything. > > virtually no user input for disaster recovery. > > This seems to imply that you want to back the file system up in a > consistent state. That rules out any solution I know could be made to > work. > > You might be able to use vinum to do this for you. The idea is to > mirror your file system, then when you want a backup, take one mirror > offline, backup that mirror, then put it back and let vinum resync the > two drives. You could still catch the file system in the middle of a > transaction, which might or might not be acceptable. > > <mike > -- > Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ > Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0104180844530.60328-100000>