Daniel Carrera wrote:
> Hello,
>
> If BackupPC uses hard links, what exactly makes a full backup different
> from an incremental backup? Is it just the --checksum flag for rsync?
It depends on the xfer method. With smb and tar, a full actually
transfers everything, with rsync it sets the -i flag so the checksums
are compared. In all cases a full rebuilds a complete tree of
directories and pool links while an incremental does not.
> Suppose that a file has not changed since the last full backup. Will
> BackupPC re-transmit the file and create a new redundant file on the
> backup disk? I imagine not. I imagine that it just makes a hard link. In
> which case, the "full" backup now starts to look like a plain regular
> backup with --checksum added.
There are two steps here - the transfer (which smb/tar would do but
rsync will realize it can skip) and the pooling with hard links. Note
that for rsync to avoid the transfer, the same file with the same name
must appear in the reference backup of the same pc - but pooling with
hard links will happen if a file with the same content exists anywhere,
from the same pc or not.
--
Les Mikesell
[email protected]
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
