nssbackup-team team mailing list archive

[Jean-Peer Lorenz <peer.loz@xxxxxxx>]

A warning is logged stating that logarithmic purging is disabled and
that you should set an appropriate cutoff value in your configuration.
Existing backups are not removed until you change to cutoff purge. That
is, you can manually save your old backups and then enable cutoff purge.

Unfortunately, disabling the logarithmic purge was necessary since it
had some serious (performance) issues. The current implementation merges
existing snapshots during the purge process every time and this merge
takes several hours when applied to archives containing more than 10.000
files. Practically, this makes (Not So) Simple Backup unusable for daily
use. Therefore, I've decided to disable it and to provide only a working
choice (the cutoff purge) for the stable release.

For later versions, it is planned to re-enable this feature.

I'll slightly modify the title of this bug and set its status to
confirmed, so we can use it to track the progress on this issue.

Thanks for reporting and for using (Not So) Simple Backup.
Best, Jean-Peer.

** Summary changed:

- Logarithmic purge missing after upgrade to 0.2
+ Logarithmic purge disabled in final release 0.2

** Changed in: nssbackup
       Status: New => Confirmed

-- 
Logarithmic purge disabled in final release 0.2
https://bugs.launchpad.net/bugs/587911
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.