Geoffrey McRae writes:
> Last night I was playing around with BackupPC and a have found quite a
> large bug in the smb Xfer method. I have found that NEW files do not get
> backed up on in incremental backup with a modified date older than the
> last backup. Now you may be wondering how you could end up with the
> modified date older than the creation date, it happens when you have more
> than one partiton on a windows box and you copy or move an old file to the
> c:\ from say the d:\. This may not cause any problems for most of you,
> but, this is a major flaw in functionality.
Right near the top of the documentation you will see:
An incremental backup is a backup of files that have changed
(based on their modification time) since the last successful
full backup. For SMB and tar, BackupPC backs up all files that
have changed since one hour prior to the start of the last
successful full backup. Rsync is more clever: any files whose
attributes have changed (ie: uid, gid, mtime, modes, size)
since the last full are backed up. Deleted and new files are
also detected by Rsync incrementals (SMB and tar are not able
to detect deleted files or new files whose modification time
is prior to the last full dump).
Look in the todo list for various suggestions for improving
incremental backups (eg: search for FileSys::SmbClient).
> This may be a possible solution to this problem:
> Before I found BackupPC I was investigating using rsync to backup the
> macines with samba. I did this by mounting the remote machine to a
> directory (mount -t smb //example/c$ /mnt/backuppc) and then running rsync
> on the mount point, this worked quite well.
More directly, you can also run rsync directly on the WinXX client.
That will generate a lot less network traffic than using mount and
running rsync on another machine.