I can hardly believe how well TKLBAM does it's incremental backups but I did a restore and sure enough everything is there. What really amazes me is how small the incremental is and how fast it is completed.
When I do a manual mysqldump of all my databases I get an uncompressed file that is about 300MB in about 15 seconds. An entire TKLBAM incremental backup of my 12GB server including the MySQL databases takes about 30 seconds. I know that the incremental will only backup changes since the last backup but *still* combining the time to calculate the differences *and* backup the databases *seems* like it should take longer.
Isn't the MySQL backup done with mysqldump? If so is TKLBAM just looking at the changes from the previous mysqldump to the current mysqldump?
No matter how you've coded TKLBAM I'm impressed. It's very satisfying to have such a simple but complete backup solution. I can hardly wait to see LVM incorporated so we can get point-in-time consistent backups. My guess is that LVM will be a difficult thing to incorporate so good luck with the work.
Here is the tklbam-backup log entry from my most recent incremental backup. If I'm reading it correctly then it took only 34 seconds to find 8.29MB of changed content and compress it to 2.50MB and save it on the backup server.
ElapsedTime 34.41 (34.41 seconds)
SourceFileSize 8288062089 (7.72 GB)
NewFileSize 10106497 (9.64 MB)
ChangedFileSize 333924770 (318 MB)
ChangedDeltaSize 0 (0 bytes)
RawDeltaSize 8689094 (8.29 MB)
TotalDestinationSizeChange 2623269 (2.50 MB)