Files in repository not matching name convention will be deleted during clean-up

[Martin Schniewind]

Binary package hint: backup-manager

This concerns backup-manager 0.6.
The problem is fixed in stable release 0.6.2.

Problem:
Backup-manager (BM) is designed to clean the backup repository according to BM_ARCHIVE_TTL (time to live). But BM deletes every file not matching the BM naming convention for backup files (with eight digit date in the name). For this reason, the method "tarball-incremental" does not work properly, since BM deletes tar's timestamp file during clean-up.
This is mostly harmless as long as noone else than BM puts files into the repository directory, and as long as the "tarball-incremental" method is not used. But if so, in the first case the files will be lost on next BM execution; so if BM_REPOSITORY_ROOT is misconfigured to - let's take the worst case - "/", everything will be deleted on the system.
In the second case the repository size will grow huge since a full backup is made each time instead of an incremental one.

Reason:
There is a buggy procedure "clean_file()" in /usr/share/backup-manager/files.sh. This procedure decides whether any file residing in the backup repository is to be deleted or not during clean-up. The procedure has been re-designed in version 0.6.2.

Solution:
Use stable version 0.6.2 from www.backup-manager.org.

[Jeff Anderson (jander99)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Jeff Anderson (jander99)]

Reporter has stated problem is fixed in 0.62. Marking this as Fix Released.
Dapper is the only release to use 0.6.