Rich Duzenbury writes:
> I'm pretty new with backuppc, and I think I'm having some kind of
> trouble with one linux machine out of five or six that I've got running
> so far.
> It seems that way too many files are being transferred in the
> incremental backups. For the most part, this particular machine just
> adds a few database entries and a few files each day. However, if you
> look at the included table, you can see that the last incremental backed
> up about 285,000 files as 'new', if I read the table correctly. Looking
> at the logs, I saw many files that have dates from 3/4 years ago, where
> nothing has recently been done with them.
> The incremental takes some five or six hours to run, and I've got some
> other somewhat similar machines that are admittedly using less disk
> (perhpas 50%) that run their incrementals in a few minutes. The full
> backup takes eleven hours for about 11 gigs.
> When I first installed backuppc on this particular machine, I used the
> rsync over ssh method. I recently configured rsyncd on the client
> machine, and converted the config on the backuppc server, the backup got
> a bit slower.
I suspect that the path name being backed up changed between the
full backup and the incremental. That means the incremental will
backup all the files since they have different path names to the
original full backup. All the files will get pooled correctly,
but they will be re-transferred every incremental.
For example, if you started with rsync over ssh, then you were
probably backing up the "share" "/". When you switched to rsyncd,
the module you are backing up is probably not called "/", eg: cDrive.
So the full backup has paths like /etc/foo, while the incremental
backups have paths like cDrive/etc/foo. That makes every incremental
file look new, so each file will get transferred.
The solution is to manually run a full backup.