The issue is that since you're using an NFS mount instead of SSH, the
network transfer benefits of rdiff-backup are lost. Really, if you want
to get reasonable performance, you need to install rdiff-backup on the
NAS and enable SSH access.
JoshN
Scott Schappell wrote:
Hello,
I was wondering if the use of NFS mounts is contraindicated for
rdiff-backup? The documentation on the site alludes to some errors, but
then release notes seem to indicate that bug fixes were put into place
for those errors. I am running rdiff-backup version 1.2.8 installed
via FreeBSD 7.2 ports. The system is an older P4 2.8 with 2 GiB of RAM
and 100 Mbps network speeds.
It took rdiff-backup 1 hour 49 minutes and 7.88 seconds according to
the log. The log stated it backed up 6634675372 bytes in 6547.88
seconds.
6634675372 bytes = 53077402976 bits
53077402976 / 6547.88 seconds = 8106044 bits per second or 8.11 Mbps
The NAS device I'm backing up to (ReadyNAS NV) does not allow inbound
SSH (well, they blocked it and as of yet I haven't gotten around to
breaking into it) so I need to do my backups via NFS over TCP and is
direct connected by crossover cable.
Also, as an interesting note when I'm copying files from the server to
the NAS directly, my MRTG graphs show outbound traffic approaching 80
Mbps, but when rdiff-backup is running, it shows traffic inbound AND
outbound (see http://archon.silvertree.org/rdiff.png).
This has me somewhat flummoxed as I like the way rdiff-backup seems to
work, but I definitely need more speed. I know that subsequent backups
should be quicker, but this is a pretty serious performance hit.
Thanks for any pointers,
Scott
_______________________________________________
rdiff-backup-users mailing list at address@hidden
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
|
