It's a bit tricky to come up with simple description. IMHO examples are
the best way how to demonstrate the functionality, so, please find below
what I would include in the documentation/help for the Simple Backup
Suite.
~~~
Purging
Is the instrument to keep
Hi wattazoum,
Thank you so much for looking into this issue and explaining how the
Sbackup works.
Well, I've slowly arrived to similar conclusion and yes, you're right
about our configuration was kind of clashing.
(Just inherited how it was setup and my aim is to improve it). With no
Hi,
I was one of the main developers of Sbackup.
I have devoted myself to other projects for quite some time now (leaving
sbackup to others).
Developers interested in this project come and go depending on their free time.
This explains the time it took for you to have and answer to your
Interesting observation:
The last night I've change the value of *Simple cut-off:* from 10 to 7, so now
it looks like:
Simple cut-off: Erase all backup older than 7 days.
The output of the sbackup in the log is also interesting:
2018-05-16 22:30:00,509 - INFO: TAR returned a message: Total bytes
To workaround this issue, I wrote a simple shell script located at:
https://gist.github.com/delphym/62e99ef7ba936879580c66c6a9685ef3#file-clean_old_backups-sh
Someone might find it helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
At the end of a sbackup.log there is a record that "Simple purge" has
been attempted (without any status what it actually did):
2018-05-13 16:45:25,339 - INFO: Leading '/' from member names were removed.
2018-05-13 16:45:25,350 - INFO: TAR returned a message: Total bytes written:
370298880
