UpdateErrorOne

From RdiffBackupWiki

al reason for this error is that the file changed during the backup. This is not unusual with log and database files which are constantly changing. There are a few ways around this problem.

One thing you could do is ignore the problem. On my systems, I'll rarely have this happen to the same logfile two days in a row, so I risk losing a day from any logfile it happens to. On the systems in question, this is acceptable.

A simple but perhaps incovenient way is to stop the logs from changing while the backup runs by stopping whatever process is making the affected files, such as by shutting down syslog, the email system, database or whatever.

Perhaps the best way for many people is to copy the log files someplace before the backup runs; you will still get the error message, but the unchanging copy of the log file will be backed up.

A more complex but very cool way is to mount a snapshot of the filesystem that is frozen in time and make the backup from that rather than from the live filesystem. I believe the linux volume manager allows for this, and I am sure that AdvFS in Tru64 Unix from DEC/Digital/Compaq/HP can do this.

[1] discusses this, stating "rdiff-backup will pretend that the file is the same as it is in the destination directory. For an incremental backup, this means that no new increment will be written, and the mirror copy will not be updated."