Mark writes:
> Using rsync between two linux servers, the full took 2.5 hours, the
> incremental backups are taking longer each day.
>
> 2008-10-21 23:00:01 full backup started for directory /
> 2008-10-22 02:32:55 full backup 0 complete, 294903 files, 203401100538
> bytes, 28 xferErrs (0 bad files, 0 bad shares, 28 other)
> 2008-10-22 23:00:00 incr backup started back to 2008-10-21 23:00:01
> (backup #0) for directory /
> 2008-10-23 04:59:40 incr backup 1 complete, 541 files, 170443233887
> bytes, 11 xferErrs (0 bad files, 0 bad shares, 11 other)
Each incremental is transferring 170GB. The full is 203GB. Do you
have, eg, a large sparse file below /var/log that you should exclude
from the backup?
Les Mikesell notes that:
In particular, many 64-bit linux versions have a /var/log/lastlog
file that appears to be 1.2 terabytes in size as an artifact of
indexing it by uid numbers and using -1 for the nfsnobody id. It's
generally not important to back this file up, so if that is the
problem you can just exclude
If there is a small change to such a file it is quite likely to be
more expensive than the original complete transfer. (It won't matter
whether it is a full or incr.)
Craig
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
