I'm using the tar method for backups with the default tar command in the
config file. For each incremental backup, every file that has not
changed is reported as being an Xfer error. Is this the intended
behaviour? I'm getting ~ 250000 Xfer errors per share because of this.
eg output)
Running: /usr/bin/ssh -q -x -n -l root localhost /usr/bin/tar -c -v -f - -C /
--totals --newer=2005-10-21\ 01:00:05 --exclude=./dev --exclude=./initrd
--exclude=./proc --exclude=./tmp --exclude=./mnt --exclude=./home/ghm
--exclude=./home/backuppc --exclude=./sys --exclude=./var/tmp .
Xfer PIDs are now 6774,6772
/usr/bin/tar: ./bin/[: file is unchanged; not dumped
/usr/bin/tar: ./bin/bb: file is unchanged; not dumped
/usr/bin/tar: ./bin/dd: file is unchanged; not dumped
/usr/bin/tar: ./bin/cp: file is unchanged; not dumped
/usr/bin/tar: ./bin/df: file is unchanged; not dumped
/usr/bin/tar: ./bin/ed: file is unchanged; not dumped
/usr/bin/tar: ./bin/du: file is unchanged; not dumped
/usr/bin/tar: ./bin/id: file is unchanged; not dumped
Thanks,
Andrew
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
