#13 increase size of MAX_FULL

[undecidable]

Can I add something to your "nice to have" list?
Allow Max_Full to be bigger?

At the moment the max is 8,
but I would like to keep monthly full backups.

To keep monthly full backups, one needs max_full = 12
but when max_full is set to anything greater than 8, it just keeps creting new backups
without deleting old ones, eg:

Summary

Backup Date Time | Size | Skipped Files+D | New Obs. | Err.
------------------------------------------------------------------------------
t0.1 2008-05-24 11:36 | 2.5G | 0 28772 |28772 0 | 8
t0.10 2009-04-04 10:04 | 4.1G | 0 26719 |26719 0 | 7
t0.11 2009-05-03 09:21 | 3.0G | 0 24310 |24310 0 | 7
t0.12 2009-05-31 09:22 | 2.8G | 0 21210 |21210 0 | 6
t0.13 2009-06-28 08:53 | 2.6G | 0 21670 |21670 0 | 6
t0.2 2008-06-29 07:47 | 2.9G | 0 25385 |25385 0 | 8
t0.3 2008-08-01 06:08 | 3.4G | 0 24963 |24963 0 | 8
t0.4 2008-08-31 08:44 | 3.9G | 0 25706 |25706 0 | 8
t0.5 2008-09-30 10:10 | 4.0G | 0 25802 |25802 0 | 8
t0.6 2008-11-01 10:55 | 4.1G | 0 26265 |26265 0 | 7
t0.7 2008-11-30 09:54 | 4.2G | 0 27235 |27235 0 | 7
t0.8 2009-02-01 06:20 | 4.3G | 0 27472 |27472 0 | 7
t0.9 2009-02-25 14:33 | 4.3G | 0 27634 |27634 0 | 7

then when I wanted to add one, get t0.14

backup2l v1.4 by Gundolf Kiefer

Estimating full backup <t0.14>...
19570 / 19570 file(s), 2599 / 2599 dir(s), 3.4GB / 3.4GB (uncompressed)
skipping: 0 file(s), 0 dir(s), 0 B (uncompressed)

If I try to manually restrict to 12, eg by deleting t0.1 by hand
so that I now have:

Summary

Backup Date Time | Size | Skipped Files+D | New Obs. | Err.
------------------------------------------------------------------------------
t0.10 2009-04-04 10:04 | 4.1G | 0 26719 |26719 0 | 7
t0.11 2009-05-03 09:21 | 3.0G | 0 24310 |24310 0 | 7
t0.12 2009-05-31 09:22 | 2.8G | 0 21210 |21210 0 | 6
t0.13 2009-06-28 08:53 | 2.6G | 0 21670 |21670 0 | 6
t0.2 2008-06-29 07:47 | 2.9G | 0 25385 |25385 0 | 8
t0.3 2008-08-01 06:08 | 3.4G | 0 24963 |24963 0 | 8
t0.4 2008-08-31 08:44 | 3.9G | 0 25706 |25706 0 | 8
t0.5 2008-09-30 10:10 | 4.0G | 0 25802 |25802 0 | 8
t0.6 2008-11-01 10:55 | 4.1G | 0 26265 |26265 0 | 7
t0.7 2008-11-30 09:54 | 4.2G | 0 27235 |27235 0 | 7
t0.8 2009-02-01 06:20 | 4.3G | 0 27472 |27472 0 | 7
t0.9 2009-02-25 14:33 | 4.3G | 0 27634 |27634 0 | 7

then when I run again we run into a bug,
it creates a new t0.9

Removing old backups...
moving <t0.2> to <t0.1>
moving <t0.3> to <t0.2>
moving <t0.4> to <t0.3>
moving <t0.5> to <t0.4>
moving <t0.6> to <t0.5>
moving <t0.7> to <t0.6>
moving <t0.8> to <t0.7>
moving <t0.9> to <t0.8>

Preparing full backup <t0.9>...
19570 / 19570 file(s), 2599 / 2599 dir(s), 3.4GB / 3.4GB (uncompressed)
skipping: 0 file(s), 0 dir(s), 0 B (uncompressed)

so that now t0.10, t0.11, t0.12,.. are out of sequence:

Summary

Backup Date Time | Size | Skipped Files+D | New Obs. | Err.
------------------------------------------------------------------------------
t0.1 2008-06-29 07:47 | 2.9G | 0 25385 |25385 0 | 8
t0.10 2009-04-04 10:04 | 4.1G | 0 26719 |26719 0 | 7
t0.11 2009-05-03 09:21 | 3.0G | 0 24310 |24310 0 | 7
t0.12 2009-05-31 09:22 | 2.8G | 0 21210 |21210 0 | 6
t0.13 2009-06-28 08:53 | 2.6G | 0 21670 |21670 0 | 6
t0.2 2008-08-01 06:08 | 3.4G | 0 24963 |24963 0 | 8
t0.3 2008-08-31 08:44 | 3.9G | 0 25706 |25706 0 | 8
t0.4 2008-09-30 10:10 | 4.0G | 0 25802 |25802 0 | 8
t0.5 2008-11-01 10:55 | 4.1G | 0 26265 |26265 0 | 7
t0.6 2008-11-30 09:54 | 4.2G | 0 27235 |27235 0 | 7
t0.7 2009-02-01 06:20 | 4.3G | 0 27472 |27472 0 | 7
t0.8 2009-02-25 14:33 | 4.3G | 0 27634 |27634 0 | 7
t0.9 2009-08-01 10:42 | 2.8G | 0 22169 |22169 0 | 6

which now starts to get very messy,
so realy I need to stick with max last 8 months.

If there is a workaround pls let me knw,
otherwise let me add increasing max_full to the wishlist.

thanks
mc