From: Les M. <le...@fu...> - 2005-03-29 14:45:33
|
> However, in my experience, no one sets up the BackupPC pool on its own > partition the first time they install it. (I've seen at least 3 > installations of it by people I know, after showing it to them; and none of > them set up a separate partition for /var/lib/backuppc.. and these were > people with 5-20 yrs Unix experience). Yes, people often do things wrong the first time and learn only from experience. How many keep it that way after outgrowing their initial setup or having to switch to a faster box? The difficulty of copying the archive makes this a special case. > also, in many cases it doesn't matter. If the OS drive in my backup server > becomes corrupt/dies, the plan is: > - put a new drive in place > - install Debian > - install backuppc > - restore /etc/backuppc from the backups. But the archive files are the point here... What if the rest of your office is also gone at this point and you need to put it back. > If I had the backuppc data pool on a separate drive that I took home, and > the office burned down, the recovery plan would be something like: > - install backuppc on laptop > - plug drive into laptop > - start doing recovery > - worry about /etc/backuppc when I get around to restoring the backup server > itself. > So I don't consider it to be in any serious way a hindrance to put the > config files in /etc. Try it. You need stuff from the configs to restore, more or less, depending on the restore methods. > As for a symlink from one place to another... it doesn't meet my > backup-of-etc needs. What we need would be something like a hardlink that > can cross filesystem boundaries. (Anyone have experience with HURD's > 'firmlinks'?) How do you deal with ones that just plain won't work if they aren't in their real location - like grub.conf if /boot is a separate partition? I'd consider this a similar situation since the configuration isn't worth much without the data archive and vice versa. -- Les Mikesell le...@fu... |