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 Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1761216 Title: Backup fails if backup destination is not mounted Status in Déjà Dup: Incomplete Status in deja-dup package in Ubuntu: Triaged Bug description: I have set my backup destination to a separate drive in the machine, but not at the default location. When the backup runs, it fails stating permission denied, as the destination drive is not mounted. When I enter the proper destination in the backup at the "storage location", the drive then mounts and is present on the desktop. Then the backup will run successfully. I then "unmount" the drive using the menu on the drive icon, and the mounted drive disappears from the desktop. I don't need a bunch of drives listed or shown on my desktop, as it detracts from the beauty of the screen. If I mount the drive before running the backup, it will succeed. My point with this is that I am not going to mount the drive every time I run backup, and when mounted, I don't need it listed or shown on my desktop. In unity, the drives appeared in the launcher or dock, and there was an option to "remove from launcher", which still left the drive mounted, but off the desktop and launcher. This was a nice way to fix this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1761216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
