Menu

#33 Support for duplicity Azure backend

closed
nobody
None
5
2015-08-08
2015-01-14
No

Please add support for duplicity Azure backend.

1 Attachments

Related

Feature Requests: #33

Discussion

  • ede

    ede - 2015-01-29

    saw it ;)

    just busy currently.. will have a look at it when time allows it. thx ede

     
  • ede

    ede - 2015-07-24

    ok,

    instead of using your patch i opted to remove this backend specific part of duply for the sake of maintainability. with version 1.10 you will be able to place export declarations in the conf file for the env vars needed. there will be a hint in there as well just below the old auth section in new generated profile's conf files.

    please try the current development version from
    http://duply.net/tmp/duply.sh
    and tell me how that works out for you.

    regards.. ede

     

    Last edit: ede 2015-07-24
  • Scott McKenzie

    Scott McKenzie - 2015-07-29

    Thanks for looking in to this. I finally got around to testing... I commented out TARGET_USER and TARGET_PASS and exported AZURE_ACCOUNT_NAME and AZURE_ACCOUNT_KEY. This caused an error:

    Start duply.sh v1.9.3dev, time is 2015-07-29 21:54:53.
    Using profile '/home/scott/.duply/photos'.

    Sorry. A fatal ERROR occured:

    Backup target credentials needed but not set in conf file
    '/home/scott/.duply/photos/conf'.
    Setting TARGET_USER or TARGET_PASS or the corresponding values in TARGET url
    are missing. Some protocols only might need it for write access to the backup
    repository (commands: bkp,backup,full,incr,purge) but not for read only access
    (e.g. verify,list,restore,fetch).

    Hints:
    Add the credentials (user,password) to the conf file.
    To force an empty password set TARGET_PASS='' or >TARGET='prot://user:@host..'.

    I then tried it with TARGET_USER and TARGET_PASS populated, and the AZURE specific variables still exported, and it caused a problem for the backend by passing TARGET_USER in the URL. The backend tried to create a container called username@containername which is not a valid container name.

    Once I added Azure to the list of protocols that do not need passwords (line 1765) it started working.

    Regards
    Scott

     
  • ede

    ede - 2015-08-08
    • status: open --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB