While that keeps the config from being lost, it doesn't totally remedy
the situation. For example, if we put a new drive into the rotation,
and somehow forget to include that symlink, every time that drive is
used the configuration will be wrong and it might go unnoticed. I know
a good solution is to "not forget," but we're thinking more long-term.
Several years from now when drives start going bad, we don't want to
have this cause data loss because we forgot a symlink and the data
wasn't backed up in the first place.
Unless there's you've got any more quick tricks up your sleeve, we can
probably manage with this one host by moving the important data into the
directory being backed up. But, like I said, I think it's a decent
feature to consider for future versions.
Ski Kacoroski wrote:
> Store the per config files in the main backuppc config directory and
> put links on the ../pc/ directories. We do this when we have several
> machines that share a local config.
> Justin Reed wrote:
>> First off, thanks for writing BackupPC. We've installed it on a
>> MacOS 10.3 G4 box, using external Firewire hard drives for rotating
>> backup storage. So far it's working great, with one minor exception.
>> I'd like to know if there is any way to store per-host configuration
>> files *not* in the pc directory. If not, I'd like to know if this
>> can be added to a future version. The reason is that, since our
>> storage drives are rotated in and out, it does not make sense to have
>> the configuration file (which dictates which files are to be backed
>> up) stored on the actual backup media. This would be particularly
>> disastrous if we later used new drives and forgot to copy the conf
>> files, thereby backing up the wrong data. Rather, it makes much more
>> sense to keep the configuration files in a central location where
>> they can't be forgotten.
>> Perhaps there is a workaround that can be coded into the main conf
>> file? That would be fine as well. To be precise, our main conf file
>> tells BackupPC to backup only the /home directory. However, we are
>> adding another client to the mix and it requires additional
>> directories to be backed up. So if there's a Perl one-liner that
>> would say "if the client is x then backup this directory, otherwise
>> backup /home" this would be perfect.
>> I realize our application of BackupPC might be out of the norm, but I
>> can see plenty of other folk eventually doing similar things and
>> being stuck in the same predicament. So if this isn't already part
>> of BackupPC, it might be a good thing to integrate in.
>> Thanks in advance for your help,
The Catalyst Group
University of Washington