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 description/documentation it was a bit challenge to guess what would be the real behaviour of the "Simple cut-off" option. Frustrated, I based my understanding on the explicit name of the option even though I understand it would leave us with those orphants. Also, I'd rather have it working in more smarter and safer way, which seems it does....except keeps disk full.
You're right, my expectation would put the whole backup in the risk, OTOH I would know what to expect.
I'll try to come up with some wordings for the documentation and tooltips, as the behaviour seems to be alright. So, hopefully everyone could configure Sbackup in the right way.
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 description/ documentation it was a bit challenge to guess what would be the real behaviour of the "Simple cut-off" option. Frustrated, I based my understanding on the explicit name of the option even though I understand it would leave us with those orphants. Also, I'd rather have it working in more smarter and safer way, which seems it does....except keeps disk full.
You're right, my expectation would put the whole backup in the risk, OTOH I would know what to expect.
I'll try to come up with some wordings for the documentation and tooltips, as the behaviour seems to be alright. So, hopefully everyone could configure Sbackup in the right way.
Cheers,
-d