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 (354MiB, 768KiB/s) 2018-05-13 16:45:25,351 - INFO: TAR has been finished successfully. 2018-05-13 16:45:30,078 - INFO: Corrupt snapshot `2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped. 2018-05-13 16:45:30,082 - INFO: Simple purge - remove freestanding snapshots older than 10 days. 2018-05-13 16:45:30,177 - INFO: Corrupt snapshot `2018-05-09_22.00.07.699726.mcs-Ubuntu.corrupt` found. Skipped. 2018-05-13 16:45:30,181 - INFO: Backup process finished. 2018-05-13 16:45:30,186 - INFO: Terminating GIO File Access Manager. 2018-05-13 16:45:30,186 - INFO: Processing of profile successfully finished (no errors) I was also wondering what is the definition of the "freestanding" snapshot... -- 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
