Yes, since 20.04, I have not had the problem, but I thought it was due to using a linux server and smbĀ which solved the problem.
The original problem was localized to my desktop machine and a local drive, which would fail after bootup because the dedicated backup drrive/partition was not mounted at bootup. Only after mounting the drive/partition would the backup run. This prevented the automated backup that should run shortly after the system booted up. To be clear, the backup partition and deja-dup were being run locally on a client machine. Since 20.04, I built a xigmanas server and moved the backup destination off the local machine to the server and started using smb to access the backup partition. This saved space on the local machine and further protected the backups as they are now stored on a remote server. Thanks for the reply, response and fix. On 8/2/20 4:13 PM, Michael Terry wrote: > OK, then yah, I suspect the change I recently made should fix this: > deja-dup now checks fstab and mounts the target location before a backup > starts. > > You should be able to test it by installing the latest edge snap: > snap install deja-dup --classic --edge > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761216 Title: Backup fails if backup destination is not mounted To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1761216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs