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 written: 
372029440 (355MiB, 723KiB/s)
2018-05-16 22:30:00,509 - INFO: TAR has been finished successfully.
2018-05-16 22:30:05,150 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:05,155 - INFO: Simple purge - remove freestanding snapshots 
older than 7 days.
2018-05-16 22:30:05,497 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:05,644 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:05,914 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:06,084 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:06,195 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:06,346 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:09,212 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:09,222 - INFO: Corrupt snapshot 
`2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped.
2018-05-16 22:30:09,227 - INFO: Backup process finished.
2018-05-16 22:30:09,235 - INFO: Terminating GIO File Access Manager.
2018-05-16 22:30:09,235 - INFO: Processing of profile successfully finished (no 
errors)


But the most interesting stuff is that it deleted some of the old backups.
Before this backup was executed there were:
#of ALL backups:15 #of CORRUPTED:1 #of FUL:2 #of INC:12
After this backup finished we have ended up with:
#of ALL backups:9 #of CORRUPTED:1 #of FULL:1 #of INC:7

Tha last scheduled backup created another INC backup, and then the purge 
triggered. It seems that there is some hidden fuzzy undescribed/undocumented 
logic for what that purge number means.
Definitely not the straightforward as it declares "erase all older than " $n 
"days".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770528

Title:
  Purging of old backup - Simple cut-off is not happening

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sbackup/+bug/1770528/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to