Deja Dup will not allow nfs backup

[KeithG]

This works as expected on my Arch Linux machine. Does not work on either machine running Ubuntu 18.04

From the command line when I run duplicity, I ge tthis

$ duplicity .bashrc nfs://192.168.2.198/mnt/first_NAS/Backups/Kris
UnsupportedBackendScheme: scheme not supported in url: nfs://192.168.2.198/mnt/first_NAS/Backups/Kris

I do not know if this is the correct syntax or not form teh cli, but I thouught I'd try to see if there is any info which may help with diagnosis.

I want to use nfs as my repository. I can mount it, so it exists. I can have a non elevated user (does not have sudo capability) on the Arch machine also use an nfs directory on the server as his backup location.

It apears that there is a package which is not installed or some package is not yet configured. I am not aware of anything I did on the Arch machine to cause this to work.

$ lsb_release -d
Description: Ubuntu 18.04 LTS

$ dpkg-query -W deja-dup duplicity
deja-dup 37.1-2fakesync1
duplicity 0.7.17-0ubuntu1

$ cat /tmp/deja-dup.gsettings
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'remote'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check '2018-05-15T00:41:10.878761Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['/home/kmgrider/Documents', '/home/kmgrider/Downloads', '/home/kmgrider/eagle', '/home/kmgrider/Pictures', '/home/kmgrider/Videos']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'X550VX'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'X550VX'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'X550VX'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'X550VX'
org.gnome.DejaDup.Local folder 'X550VX'
org.gnome.DejaDup.Remote uri 'nfs://192.168.2.198/mnt/first_NAS/Backup'
org.gnome.DejaDup.Remote folder 'Kris'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.Drive folder '$HOSTNAME'
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'X550VX'
org.gnome.DejaDup.GOA type 'google'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []

$ cat /tmp/deja-dup.log
$ DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

** (org.gnome.DejaDup:13905): WARNING **: 20:16:27.467: BackendRemote.vala:86: The specified location is not supported

[KeithG (grider-4)]

Have done a bit of sleuthing. This problem is apparently due to a bug in gvfs. I also cannot mount and browse any nfs shares in Ubuntu in Nautilus (and have no issue doing do on Arch). I checked the libnfs and nfsidmap libraries and they appear to be similar, but nfsidmap is a bit behind Arch.

Arch:
libnfs.so.11
libnfsidmap.so.1.0

Ubuntu:
libnfs.so.11
libnfsidmap.so.0.3

This breaks all user mounts of nfs. It affects my backup and Nautilus. I am not aware of other programs, but guess it probably affects other programs as well.

[Oscar Carlberg (canhasspace)]

I have the exact same problem. A workaround I use for now is to mount the NFS share in fstab and point deja-dup to the local mount, not ideal though.

[KeithG (grider-4)]

I can perform that workaround, too, but the real culprit is gvfs and it
really should be fixed.

On Sat, Jun 2, 2018 at 3:15 AM, Oscar Carlberg <email address hidden>
wrote:

> I have the exact same problem. A workaround I use for now is to mount
> the NFS share in fstab and point deja-dup to the local mount, not ideal
> though.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1773717
>
> Title:
> Deja Dup will not allow nfs backup
>
> Status in Déjà Dup:
> New
>
> Bug description:
> This works as expected on my Arch Linux machine. Does not work on
> either machine running Ubuntu 18.04
>
> From the command line when I run duplicity, I ge tthis
>
> $ duplicity .bashrc nfs://192.168.2.198/mnt/first_NAS/Backups/Kris
> UnsupportedBackendScheme: scheme not supported in url: nfs://
> 192.168.2.198/mnt/first_NAS/Backups/Kris
>
> I do not know if this is the correct syntax or not form teh cli, but I
> thouught I'd try to see if there is any info which may help with
> diagnosis.
>
> I want to use nfs as my repository. I can mount it, so it exists. I
> can have a non elevated user (does not have sudo capability) on the
> Arch machine also use an nfs directory on the server as his backup
> location.
>
> It apears that there is a package which is not installed or some
> package is not yet configured. I am not aware of anything I did on the
> Arch machine to cause this to work.
>
> $ lsb_release -d
> Description: Ubuntu 18.04 LTS
>
> $ dpkg-query -W deja-dup duplicity
> deja-dup 37.1-2fakesync1
> duplicity 0.7.17-0ubuntu1
>
>
> $ cat /tmp/deja-dup.gsettings
> org.gnome.DejaDup last-restore ''
> org.gnome.DejaDup periodic true
> org.gnome.DejaDup periodic-period 7
> org.gnome.DejaDup full-backup-period 90
> org.gnome.DejaDup backend 'remote'
> org.gnome.DejaDup last-run ''
> org.gnome.DejaDup nag-check ''
> org.gnome.DejaDup prompt-check '2018-05-15T00:41:10.878761Z'
> org.gnome.DejaDup root-prompt true
> org.gnome.DejaDup include-list ['/home/kmgrider/Documents',
> '/home/kmgrider/Downloads', '/home/kmgrider/eagle',
> '/home/kmgrider/Pictures', '/home/kmgrider/Videos']
> org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
> org.gnome.DejaDup last-backup ''
> org.gnome.DejaDup allow-metered false
> org.gnome.DejaDup delete-after 0
> org.gnome.DejaDup.Rackspace username ''
> org.gnome.DejaDup.Rackspace container 'X550VX'
> org.gnome.DejaDup.S3 id ''
> org.gnome.DejaDup.S3 bucket ''
> org.gnome.DejaDup.S3 folder 'X550VX'
> org.gnome.DejaDup.OpenStack authurl ''
> org.gnome.DejaDup.OpenStack tenant ''
> org.gnome.DejaDup.OpenStack username ''
> org.gnome.DejaDup.OpenStack container 'X550VX'
> org.gnome.DejaDup.GCS id ''
> org.gnome.DejaDup.GCS bucket ''
> org.gnome.DejaDup.GCS folder 'X550VX'
> org.gnome.DejaDup.Local folder 'X550VX'
> org.gnome.DejaDup.Remote uri 'nfs://192.168.2.198/mnt/first_NAS/Backup'
> org.gnome.DejaDup.Remote folder 'Kris'
> org.gnome.DejaDup.Drive uuid ''
> org.gnome.DejaDup.Drive icon ''
> org.gnome.DejaDup.Drive folder '$HOSTNAME'
> ...

[Charlie Jordan (cj11363)]

manually mounting ( & unmounting ) the NFS share is not a great option for a laptop that moves around a lot...

[Vej (vej)]

Setting as confirmed as this bug affects multiple users.

[Sebastien Bacher (seb128)]

The gvfs nfs backend was not enabled in 18.04, see bug #1637988

If the feature is relying on that then it's normal it's not working. Could you try on a newer Ubuntu serie?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael Terry (mterry)]

I'm going to close this ticket, as it should be solved in Ubuntu 20.04 and on and it was never really something that deja-dup itself could fix.

The workaround of mounting via fstab should work for folks stuck on Ubuntu 18.04 and earlier though.