Thanks for the response Craig.
I noticed that pool and cpool were getting updated over at
/var/lib/backuppc also (don't understand why I wasn't getting these link
errors before ?!)
So I moved the var/lib/backuppc versions of the pool, cpool, and log
directories over to the raid volume and remount
dan wrote:
> you can make root own it and give everyone wrx access. the script
> will put the appropriate permissions in place for the installed
> folders. then after the install you can match the /var/lib/backuppc
> permissions with that of the subfolders.
Just to report backup and close this
I have no experience with DAT72; I do have some experience with DDS4 and
quite a bit of experience with older 4mm-format (DDS) tapes. I personally
like the VXA series of tapes; or if you can afford it, AIT. Based on
anecdotal evidence of myself and some others, the 8mm-format drives seem
more reli
can you setup sudo?
if so, you can put an /etc/sudoers file that allows the backuppc user to
sudo rsync without a password. then it would have permission to read the
files. security concern: now the backuppc user could rsync FROM somewhere
else to the DNS server, which means that if someone got
I have newly installed BackupPC using rsync. ssh via root is not permitted so I
used backuppc user to ssh to my dns server. My first server to backup is my dns
server. Its setup is chrooted. So it means backuppc user has no read/write
permission. BackupPC cannot fetch the file in my dns server.
