On 10/19/07, Craig Barratt <[EMAIL PROTECTED]> wrote:
>
> Koen writes:
>
> > BackupPC_tarPCCopy /var/lib/backuppc/pc/mpi021 | (cd
> > /backups/backuppc/pc/mpi021 && tar xPf -)
> >
> > gives something like this:
> >
> > tar: ./mpi021/7/fC$/fDocuments and Settings/fAdministrator/fMijn
> > documenten/fHPLJ24x0/ftoolbox/attrib: Cannot hard link to
> > `../cpool/d/b/1/db10c689101ef0b373742b62b7b6f532': No such file or
> > directory
> >
> > backuppc has write rights as owner for the target directory:
> > drwxr-x--- 11 backuppc backuppc 4096 2007-10-18 14:31 mpi021
>
> Your extract is starting one directly too low. You should
> cd to /var/lib/backuppc/pc, not /var/lib/backuppc/pc/mpi021:
>
> BackupPC_tarPCCopy /var/lib/backuppc/pc/mpi021 | (cd
> /backups/backuppc/pc && tar xPf -)
>
> ^^^^^^^^^^^
>
> Craig
>
>
>
Perhaps this has been discussed, but how does backuppc_tarPCCopy compare to
using rsync (with hardlinks enabled)
Lets say i'm backing up 50 computers, and i want to get them off site (~3tb
of data)
Which is the best way to do this? backupPC_tar_PCCopy or rsync?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-devel
http://backuppc.sourceforge.net/
