I use back-in-time to backup my Linux installation. It serves as an advanced wrapper for the
Today I tried to add /var/log to the list of folders to be backed up and it caused some serious performance problems. The job seems to stuck on a particular file and the CPU usage of the
rsync parent process reaches 100%. I then used
lsof to see which file caused the problem and it seems to be the
I did some googling and some experiments with the different
rsync options and found
--checksum to be the offender. Without the parameter, an incremental backup finishes properly in minutes. With it, the process will stuck when
rsync tries to sync a constantly changing log file. This kind of make sense, but it still seems to be a bug to me.
Am I using the option correctly? Is there a workaround for this?