Description On 25 February I noticed that backintime (root) had not done any backups since 18 February so I attempted to do manual snapshots using both options all I got was "Done No backup needed.". I even set the logging option to All - there was no data. That was with version 1.4.1 so I manually installed version 1.4.3. the problem persisted. I am running Ubuntu 22.04 LTS.
The problem was resolved by doing a reboot - I went to check bactintime (root) and it was working - it took 30 minutes. The have been no problems with the non root backintime backups. My suspicion is that a reboot occurred during a backintime (root) backup . The reboot may have been requested a Ubuntu update, I rarely reboot the cystem. I have the configuration option set so that only one backup job at a time can be active. Is backintime (root) capable of handling interruptions caused by a reboot? Is there a lock file that is only cleared after a reboot or completion of a backup? I am willing to do some testing by disabling root backups for a while and then manually start a snapshot and reboot the system while snapshot is running or before the root backup starts - the non root job seems to run first. Thanks to all Stephen Carr _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-le...@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: arch...@mail-archive.com
