Backup operation not supported by backend

Bug #1105132 reported by Loren41
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Trying to run Deja Dup backup but operation fails. Message is "Backup Failed. Operation not supported by backend." Directing output via Samba to a server on my home network. Backups were working earlier but I must have changed something. Need help.
Prefer GUI solutions when possible.

Revision history for this message
Michael Terry (mterry) wrote :

Can you please provide some information:

1. The distribution of Linux you're using:
    lsb_release -d

2. The version of deja-dup and duplicity:
    (if on Ubuntu or Debian:)
    dpkg-query -W deja-dup duplicity

    (if on Fedora or other RPM-based systems:)
    rpm -q deja-dup duplicity

3. The file /tmp/deja-dup.gsettings after running the following line (you may want to scrub the file of any incriminating file names or details):
    gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

4. The file /tmp/deja-dup.log after running the appropriate line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):

 * If you're having problems backing up:
    DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

 * If you're having problems restoring:
    DEJA_DUP_DEBUG=1 deja-dup --restore | tail -n 1000 > /tmp/deja-dup.log

Changed in deja-dup (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]

Changed in deja-dup (Ubuntu):
status: Incomplete → Expired
Revision history for this message
LaunchpadAccount (unfo) wrote :

I seem to run into a similar situation. I have managed to create 4 automated back-ups last month and this month it simply stopped working. I have gone over my FTP settings but I can't find the problem, FTP works fine otherwise.

I keep receiving the error "Operation unsupported". Will include output as requested.

Changed in deja-dup (Ubuntu):
status: Expired → Incomplete
Revision history for this message
LaunchpadAccount (unfo) wrote :

Last bit of the log where the errors start.

I upload from Ubuntu 13.04 to a Zyxel nsa310 NAS.

Revision history for this message
LaunchpadAccount (unfo) wrote :

deja-dup 26.0-0ubuntu1
duplicity 0.6.21-0ubuntu1.1

org.gnome.DejaDup backend 'file'
org.gnome.DejaDup delete-after 365
org.gnome.DejaDup exclude-list @as []
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup include-list ['/home/REMOVED/Documents/REMOVED_REMOVED', '/home/REMOVED/Documents/REMOVED_REMOVED']
org.gnome.DejaDup last-backup '2013-07-11T19:00:31.234596Z'
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run '2013-07-11T19:00:31.234596Z'
org.gnome.DejaDup nag-check '2013-06-06T20:23:31.124074Z'
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup prompt-check '2013-05-21T15:30:25.258820Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path 'ftp://backup@REMOVED/backup/'
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.Rackspace container 'REMOVED'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'REMOVED'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.U1 folder '/deja-dup/REMOVED'

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]

Changed in deja-dup (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Milos Sramek (milos-sramek) wrote :

Hi, I get this with backap of ftp server, too. The bad thing is that there is no reason given, just "Operation unsupported".
Milos

lsb_release -d
Ubuntu 13.10
deja-dup 27.3.1-0ubuntu1
duplicity 0.6.21-0ubuntu4.1gsettings list-recursively org.gnome.DejaDup
org.gnome.DejaDup backend 'file'
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup exclude-list ['/home/milos/.local/share/Trash']
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup include-list ['/home/milos/Dokumenty', '/home/milos/Plocha', '/home/milos/Obrázky', '/home/milos/doc', '/home/milos/oldHDD', '/home/milos/FBooks', '/home/milos/Papers']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup periodic false
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup prompt-check '2014-03-05T06:28:34.166875Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path 'ftp://milos@192.168.1.1/tmp/mnt/IceSamsung1TB/milos/backup'
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.Rackspace container 'trigan'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'trigan'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.U1 folder 'deja-dup/trigan'

DEJA_DUP_DEBUG=1 deja-dup --backup
No output

Revision history for this message
Kurt Agius (kurteknikk) wrote :

I'm trying to backup to an internal FTP server and i'm getting the same error:

DUPLICITY: ERROR 50 put '/home/kurt/.cache/deja-dup/tmp/duplicity-1e0Q9B-tempdir/mktemp-40rClA-2' 'ftp://admin@192.168.178.11/admin/Documents/AcerAspireS7Backup/duplicity-full.20140419T215707Z.vol1.difftar.gpg'
DUPLICITY: . Operation unsupported

Debug trace:

DUPLICITY: DEBUG 1
DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 318, in iterate
DUPLICITY: . return fn(*args, **kwargs)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", line 137, in copy_file
DUPLICITY: . target.get_parse_name())
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", line 112, in handle_error
DUPLICITY: . raise e
DUPLICITY: . GError: Operation unsupported
DUPLICITY: .

Any ideas about this issue ?

Revision history for this message
GrzesiekC (grzesiekc) wrote :

Hi all,

I've just switched to 14.04 from 12.04.
In the previous version I was doing backups to my FTP server.

Now I've got the same problem as other users:

DUPLICITY: INFO 11
DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity disabled)

DUPLICITY: INFO 1
DUPLICITY: . Writing ftp://<user_name>@192.168.x.x /<folder name>/duplicity-full.20140425T203823Z.vol1.difftar.gpg

DUPLICITY: WARNING 1
DUPLICITY: . Attempt 1 failed: GError: Operation unsupported

DUPLICITY: DEBUG 1
DUPLICITY: . Backtrace of previous error: Traceback (innermost last):
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 318, in iterate
DUPLICITY: . return fn(*args, **kwargs)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", line 137, in copy_file
DUPLICITY: . target.get_parse_name())
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/backends/giobackend.py", line 112, in handle_error
DUPLICITY: . raise e
DUPLICITY: . GError: Operation unsupported
DUPLICITY: .

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.