Moin,
ich möchte mit Duplicity (http://www.marcogabriel.com/blog/archives/586-Linux-Backup-mit-Duply,-Duplicity-und-Rdiff-Backup-auf-potentiell-unsichere-Online-Speicher-Teil-2.html) Sicherungen von meinem Home-Verzeichnis von einem Ubuntu-Server erstellen. Als Ziel für die Sicherung habe ich mein Google-Mail-Konto genommen.
Das ganze funktioniert auch wunderbar, jedoch muss ich jedes mal das IMAP-Kennwort erneut eingeben, obwohl dieses in der Konfiguration hinterlegt ist.
Sprich, wenn ich z. B.
duply ftpbackup status[/code] eingebe, erscheint folgendes: [code]heiko@vs:~$ duply ftpbackup status Start duply v1.5.1.4, time is 11/27/11 16:18:34. Using profile '/home/heiko/.duply/ftpbackup'. Using installed duplicity (0.6.08b) (please report, this is a bug), gpg 1.4.10 (Home: ~/.gnupg) Test - Encryption with key *** (OK) Test - Decryption with key *** (OK) Test - Compare Original w/ Decryption (OK) Cleanup - Delete '/tmp/duply.30688.1322407114_*'(OK) --- Start running command STATUS 16:18:35.066 --- Enter account password:
Und erst nach Eingabe des richtigen Kennworts geht es weiter.
Ich möchte das ganze per Cronjob automatisieren, doch die andauernde Kennwort-Abfrage stört da ja.
Meine Konfiguration sieht so aus:
# gpg key data (for symmetric encryption comment out GPG_KEY) GPG_KEY='***' GPG_PW='***' # gpg options passed from duplicity to gpg process (default='') # e.g. "--trust-model pgp|classic|direct|always" # or "--compress-algo=bzip2 --bzip2-compress-level=9" #GPG_OPTS='' # credentials & server address of the backup target (URL-Format) # syntax is # scheme://[user:password@]host[:port]/[/]path # probably one out of # file:///some_dir # ftp://user[:password]@other.host[:port]/some_dir # hsi://user[:password]@other.host/some_dir # cf+http://container_name # imap://user[:password]@host.com[/from_address_prefix] # imaps://user[:password]@host.com[/from_address_prefix] # rsync://user[:password]@other.host[:port]::/module/some_dir # rsync://user[:password]@other.host[:port]/relative_path # rsync://user[:password]@other.host[:port]//absolute_path # # for the s3 user/password are AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY # s3://[user:password]@host/bucket_name[/prefix] # s3+http://[user:password]@bucket_name[/prefix] # scp://user[:password]@other.host[:port]/some_dir # ssh://user[:password]@other.host[:port]/some_dir # tahoe://alias/directory # webdav://user[:password]@other.host/some_dir # webdavs://user[:password]@other.host/some_dir # ATTENTION: characters other than A-Za-z0-9.-_.~ in user,password,path have # to be replaced by their url encoded pendants, see # http://en.wikipedia.org/wiki/Url_encoding # if you define the credentials as TARGET_USER, TARGET_PASS below # duply will url_encode them for you TARGET='imaps://imap.googlemail.com/vServer' # optionally the username/password can be defined as extra variables # setting them here _and_ in TARGET results in an error TARGET_USER='***' TARGET_PASS='***' # base directory to backup SOURCE='/home/heiko' # Time frame for old backups to keep, Used for the "purge" command. # see duplicity man page, chapter TIME_FORMATS) # defaults to 1M, if not set #MAX_AGE=1M # Number of full backups to keep. Used for the "purge-full" command. # See duplicity man page, action "remove-all-but-n-full". # defaults to 1, if not set #MAX_FULL_BACKUPS=1 # verbosity of output (5 for gpg errors, 9 for bug fixing) # default is 4, if not set #VERBOSITY=5 # temporary file space. at least the size of the biggest file in backup # for a successful restoration process. (default is '/tmp', if not set) #TEMP_DIR=/tmp # sets duplicity --time-separator option (since v0.4.4.RC2) to allow users # to change the time separator from ':' to another character that will work # on their system. HINT: For Windows SMB shares, use --time-separator='_'. # NOTE: '-' is not valid as it conflicts with date separator. # ATTENTION: only use this with duplicity < 0.5.10, since then default file # naming is compatible and this option is pending depreciation #DUPL_PARAMS="$DUPL_PARAMS --time-separator _ " # activates duplicity --short-filenames option, when uploading to a file # system that can't have filenames longer than 30 characters (e.g. Mac OS 8) # or have problems with ':' as part of the filename (e.g. Microsoft Windows) # ATTENTION: only use this with duplicity < 0.5.10, later versions default file # naming is compatible and this option is pending depreciation #DUPL_PARAMS="$DUPL_PARAMS --short-filenames " # activates duplicity --full-if-older-than option (since duplicity v0.4.4.RC3) # forces a full backup if last full backup reaches a specified age, for the # format of MAX_FULLBKP_AGE see duplicity man page, chapter TIME_FORMATS # Uncomment the following two lines to enable this setting. #MAX_FULLBKP_AGE=1M #DUPL_PARAMS="$DUPL_PARAMS --full-if-older-than $MAX_FULLBKP_AGE " # sets duplicity --volsize option (available since v0.4.3.RC7) # set the size of backup chunks to VOLSIZE MB instead of the default 25MB. # VOLSIZE must be number of MB's to set the volume size to. # Uncomment the following two lines to enable this setting. VOLSIZE=10 DUPL_PARAMS="$DUPL_PARAMS --volsize $VOLSIZE " # more duplicity command line options can be added in the following way # don't forget to leave a separating space char at the end #DUPL_PARAMS="$DUPL_PARAMS --put_your_options_here "
Kann mir da jemand weiterhelfen?
Danke
Moderiert von redknight:
Klarer Fall fürs Backupforum.