duplicity

DUPLICITY(1) User Manuals DUPLICITY(1)

NAME

   duplicity - Encrypted incremental backup to local or remote storage.

SYNOPSIS

   For detailed descriptions for each action see chapter ACTIONS.

   duplicity [backup|full|incremental] [options] source_directory target_url

   duplicity verify [options] [--compare-data] [--path-to-restore <relpath>] [--time time] source_url target_directory

   duplicity collection-status [options] [--file-changed <relpath>] [--show-changes-in-set <index>] [--jsonstat]] target_url

   duplicity list-current-files [options] [--time time] target_url

   duplicity [restore] [options] [--path-to-restore <relpath>] [--time time] source_url target_directory

   duplicity remove-older-than <time> [options] [--force] target_url

   duplicity remove-all-but-n-full <count> [options] [--force] target_url

   duplicity remove-all-inc-of-but-n-full <count> [options] [--force] target_url

   duplicity cleanup [options] [--force] target_url

DESCRIPTION

   Duplicity incrementally backs up files and folders into tar-format volumes encrypted with GnuPG and places them to a remote (or local) storage backend.  See chapter URL FORMAT for a
   list of all supported backends and how to address them.  Because duplicity uses librsync, incremental backups are space efficient and only record the parts of files that have changed
   since the last backup.  Currently duplicity supports deleted files, full Unix permissions, uid/gid, directories, symbolic links, fifos, etc., but not hard links.

   If you are backing up the root directory /, remember to --exclude /proc, or else duplicity will probably crash on the weird stuff in there.

EXAMPLES

   Here is an example of a backup, using sftp to back up /home/me to some_dir on the other.host machine:

          duplicity /home/me sftp://uid@other.host/some_dir

   If the above is run repeatedly, the first will be a full backup, and subsequent ones will be incremental. To force a full backup, use the full action:

          duplicity full /home/me sftp://uid@other.host/some_dir

   or enforcing a full every other time via --full-if-older-than <time> , e.g. a full every month:

          duplicity --full-if-older-than 1M /home/me sftp://uid@other.host/some_dir

   Now suppose we accidentally delete /home/me and want to restore it the way it was at the time of last backup:

          duplicity sftp://uid@other.host/some_dir /home/me

   Duplicity enters restore mode because the URL comes before the local directory.  If we wanted to restore just the file "Mail/article" in /home/me as it was three days ago into
   /home/me/restored_file:

          duplicity -t 3D --path-to-restore Mail/article sftp://uid@other.host/some_dir /home/me/restored_file

   The following action compares the latest backup with the current files:

          duplicity verify sftp://uid@other.host/some_dir /home/me

   Finally, duplicity recognizes several include/exclude options.  For instance, the following will backup the root directory, but exclude /mnt, /tmp, and /proc:

          duplicity --exclude /mnt --exclude /tmp --exclude /proc / file:///usr/local/backup

   Note that in this case the destination is the local directory /usr/local/backup.  The following will backup only the /home and /etc directories under root:

          duplicity --include /home --include /etc --exclude '**' / file:///usr/local/backup

   Duplicity can also access a repository via ftp.  If a user name is given, the environment variable FTP_PASSWORD is read to determine the password:

          FTP_PASSWORD=mypassword duplicity /local/dir ftp://user@other.host/some_dir

ACTIONS

   Duplicity uses actions, which can be given in long or in short form and finetuned with options.
   The actions 'backup' or 'restore' can be implied from the order local path and remote url are given. Other actions need to be given explicitly.  For the rare case that the local path
   may be a valid duplicity action name you may append a '/' to the local path name so it can no longer be mistaken for an action.

   NOTE: The following explanations explain some but not all options that can be used in connection with that action.  Consult the OPTIONS section for more detailed descriptions.

   backup, bu <folder> <url>
          Perform a backup. Duplicity automatically performs an incremental backup if old signatures can be found. Else a new backup chain is started.

   full, fb <folder> <url>
          Perform a full backup. A new backup chain is started even if signatures are available for an incremental backup.

   incremental, ib <folder> <url>
          If this is requested an incremental backup will be performed.  Duplicity will abort if no old signatures can be found.

   verify, vb [--compare-data] [--time <time>] [--path-to-restore <rel_path>] <url> <local_path>
          Verify  tests  the integrity of the backup archives at the remote location by downloading each file and checking both that it can restore the archive and that the restored file
          matches the signature of that file stored in the backup, i.e. compares the archived file with its hash value from archival time. Verify does not actually restore and  will  not
          overwrite  any local files. Duplicity will exit with a non-zero error level if any files do not match the signature stored in the archive for that file. On verbosity level 4 or
          higher, it will log a message for each file that differs from the stored signature. Files must be downloaded to the local machine in order to compare  them.   Verify  does  not
          compare the backed-up version of the file to the current local copy of the files unless the --compare-data option is used (see below).
          The  --path-to-restore  option  restricts  verify  to  that  file or folder.  The --time option allows one to select a backup to verify.  The --compare-data option enables data
          comparison (see below).

   collection-status, st [--file-changed <relpath>] [--show-changes-in-set <index>] <url>
          Summarize the status of the backup repository by printing the chains and sets found, and the number of volumes in each.
          The --file-changed option summarizes the changes to the file (in the most recent backup chain).  The --show-changes-in-set  option  summarizes  all  the  file  changes  in  the
          index:th backup set (where index 0 means the latest set, 1 means the next to latest, etc.).  --jsonstat prints the changes in json format and statistics from the jsonstat files
          if the backups were created with --jsonstat. If <index> is set to -1 statistics for the whole backup chain printed

   list-current-files, ls [--time <time>] <url>
          Lists the files contained in the most current backup or backup at time.  The information will be extracted from the signature files, not the archive data itself. Thus the whole
          archive does not have to be downloaded, but on the other hand if the archive has been deleted or corrupted, this action will not detect it.

   restore, rb [--path-to-restore <relpath>] [--time <time>] <url> <target_folder>
          You  can  restore the full monty or selected folders/files from a specific time.  Use the relative path as it is printed by list-current-files.  Usually not needed as duplicity
          enters restore mode when it detects that the URL comes before the local folder.

   remove-older-than, ro <time> [--force] <url>
          Delete all backup sets older than the given time.  Old backup sets will not be deleted if backup sets newer than time depend on them.  See the TIME  FORMATS  section  for  more
          information.   Note,  this  action  cannot be combined with backup or other actions, such as cleanup.  Note also that --force will be needed to delete the files instead of just
          listing them.

   remove-all-but-n-full, ra <count> [--force] <url>
          Delete all backups sets that are older than the count:th last full backup (in other words, keep the last count full backups and associated incremental  sets).   count  must  be
          larger  than  zero. A value of 1 means that only the single most recent backup chain will be kept.  Note that --force will be needed to delete the files instead of just listing
          them.

   remove-all-inc-of-but-n-full, ri <count> [--force] <url>
          Delete incremental sets of all backups sets that are older than the count:th last full backup (in other words, keep only old full backups and not their increments).  count must
          be larger than zero. A value of 1 means that only the single most recent backup chain will be kept intact.  Note that --force will be needed to delete the files instead of just
          listing them.

   cleanup, cl [--force] <url>
          Delete the extraneous duplicity files on the given backend.  Non-duplicity files, or files in complete data sets will not be deleted.  This should only  be  necessary  after  a
          duplicity session fails or is aborted prematurely.  Note that --force will be needed to delete the files instead of just listing them.

OPTIONS

   --allow-source-mismatch
          Do not abort on attempts to use the same archive dir or remote backend to back up different directories. duplicity will tell you if you need this switch.

   --archive-dir path
          The archive directory.

          NOTE:  This  option  changed  in 0.6.0.  The archive directory is now necessary in order to manage persistence for current and future enhancements.  As such, this option is now
          used only to change the location of the archive directory.  The archive directory should not be deleted, or duplicity will have to recreate it from the remote repository (which
          may require decrypting the backup contents).

          When backing up or restoring, this option specifies that the local archive directory is to be created in path.  If the archive directory is not specified, the default  will  be
          to create the archive directory in ~/.cache/duplicity/.

          The archive directory can be shared between backups to multiple targets, because a subdirectory of the archive dir is used for individual backups (see --name ).

          The combination of archive directory and backup name must be unique in order to separate the data of different backups.

          The interaction between the --archive-dir and the --name options allows for four possible combinations for the location of the archive dir:

          1.     neither specified (default)
                  ~/.cache/duplicity/hash-of-url

          2.     --archive-dir=/arch, no --name
                  /arch/hash-of-url

          3.     no --archive-dir, --name=foo
                  ~/.cache/duplicity/foo

          4.     --archive-dir=/arch, --name=foo
                  /arch/foo

   --asynchronous-upload
          (DISCONTINUED) This option is discontinued because of instability.  `--concurrency` is the new replacement.

   --azure-blob-tier
          Standard storage tier used for backup files (Hot|Cool|Archive).

   --azure-max-single-put-size
          Specify  the  number  of  the largest supported upload size where the Azure library makes only one put call. If the content size is known and below this value the Azure library
          will only perform one put request to upload one block.  The number is expected to be in bytes.

   --azure-max-block-size
          Specify the number for the block size used by the Azure library to upload blobs if it is split into multiple blocks.  The maximum block size the service supports  is  104857600
          (100MiB) and the default is 4194304 (4MiB)

   --azure-max-connections
          Specify the number of maximum connections to transfer one blob to Azure blob size exceeds 64MB. The default values is 2.

   --b2-hide-files
          Causes Duplicity to hide files in B2 instead of deleting them. Useful in combination with B2's lifecycle rules.

   --backend-retry-delay number
          Specifies the number of seconds that duplicity waits after an error has occurred before attempting to repeat the operation.

   --cf-backend backend
          Allows the explicit selection of a cloudfiles backend. Defaults to pyrax.  Alternatively you might choose cloudfiles.

   --concurrency number
          Give  the  number  of  background  process  that  should  be  use  to run concurrent backend task. This decouples local operations like de/encrption, volume creation etc.  from
          transfering to/from backends.  The intended end-result is a faster backup, because the local CPU and your bandwidth can be  more  consistently  utilized.  Use  of  this  option
          implies  additional need for disk space in the temporary storage location; rather than needing to store only one volume at a time, enough storage space is required to store n+1
          volumes.  Depending on the backend and network parallel operations can speed up things.  A good starting point for concurrency is  1-4.  Check  duplicity  statistics  for  fine
          tuning.  In most cases this should not extend the number of CPUs minus one of your system.

   --config-dir path
          Allows selection of duplicity's configuratin dir.  Defaults to ~/.config/duplicity.

   --copy-blocksize kilos
          Allows selection of blocksize in kilobytes to use in copying.  Increasing this may speed copying of large files.  Defaults to 128.

   --no-check-remote
          Turn  off validation of the remote manifest.  Checking is the default.  No checking will allow you to backup without the private key, but will mean that the remote manifest may
          exist and be corrupted, leading to the possibility that the backup might not be recoverable.

   --compare-data
          Enable data comparison of regular files on action verify. This conducts a verify as described above to verify the integrity of the backup archives,  but  additionally  compares
          restored  files  to  those  in  target_directory.  Duplicity will not replace any files in target_directory. Duplicity will exit with a non-zero error level if the files do not
          correctly verify or if any files from the archive differ from those in target_directory. On verbosity level 4 or higher, it will log a message for each file that  differs  from
          its equivalent in target_directory.

   --copy-links
          Resolve  symlinks  during  backup.   Enabling  this  will resolve & back up the symlink's file/folder data instead of the symlink itself, potentially increasing the size of the
          backup.

   --dry-run
          Calculate what would be done, but do not perform any backend actions

   --encrypt-key key-id
          When backing up, encrypt to the given public key, instead of using symmetric (traditional) encryption.  Can be specified multiple times.  The key-id can be given in any of  the
          formats supported by GnuPG; see gpg(1), section "HOW TO SPECIFY A USER ID" for details.

   --encrypt-secret-keyring filename
          This  option can only be used with --encrypt-key, and changes the path to the secret keyring for the encrypt key to filename This keyring is not used when creating a backup. If
          not specified, the default secret keyring is used which is usually located at .gnupg/secring.gpg

   --encrypt-sign-key key-id
          Convenience parameter. Same as --encrypt-key key-id --sign-key key-id.

   --exclude shell_pattern
          Exclude the file or files matched by shell_pattern.  If a directory is matched, then files under that directory will also be matched.  See the FILE SELECTION section  for  more
          information.

   --exclude-device-files
          Exclude all device files.  This can be useful for security/permissions reasons or if duplicity is not handling device files correctly.

   --exclude-filelist filename
          Excludes  the  files  listed in filename, with each line of the filelist interpreted according to the same rules as --include and --exclude.  See the FILE SELECTION section for
          more information.

   --exclude-if-present filename
          Exclude directories if filename is present. Allows the user to specify folders that they do not wish to backup  by  adding  a  specified  file  (e.g.  ".nobackup")  instead  of
          maintaining a comprehensive exclude/include list.

   --exclude-older-than time
          Exclude  any  files whose modification date is earlier than the specified time.  This can be used to produce a partial backup that contains only recently changed files. See the
          TIME FORMATS section for more information.

   --exclude-other-filesystems
          Exclude files on file systems (identified by device number) other than the file system the root of the source directory is on.

   --exclude-regexp regexp
          Exclude files matching the given regexp.  Unlike the --exclude option, this option does not match files in a directory it matches.  See the  FILE  SELECTION  section  for  more
          information.

   --files-from filename
          Read a list of files to backup from filename rather than searching the entire backup source directory. Operation is otherwise normal, just on the specified subset of the backup
          source directory.

          Files must be specified one per line and relative to the backup source directory. Any absolute paths will raise an error. All characters per line are significant and treated as
          part of the path, including leading and trailing whitespace. Lines are separated by newlines or nulls, depending on whether the --null-separator switch was given.

          It  is  not necessary to include the parent directory of listed files, their inclusion is implied. However, the content of any explicitly listed directories is not implied. All
          required files must be listed when this option is used.

   --file-prefix prefix
   --file-prefix-manifest prefix
   --file-prefix-archive prefix
   --file-prefix-signature prefix
          Adds a prefix to either all files or only manifest, archive, signature files.  The same set of prefixes must be passed in on backup and restore.
          If both global and type-specific prefixes are set, global prefix will go before type-specific prefixes.

          See also A NOTE ON FILENAME PREFIXES

   --path-to-restore path
          This option may be given in restore mode, causing only path to be restored instead of the entire contents of the backup archive.  path should be given relative to the  root  of
          the directory backed up.

   --filter-globbing
   --filter-ignorecase
   --filter-literal
   --filter-regexp
   --filter-strictcase
          Change  the  interpretation  of  patterns  passed to the file selection condition option arguments --exclude and --include (and variations thereof, including file lists). These
          options can appear multiple times to switch between shell globbing (default), literal strings,  and  regular  expressions,  case  sensitive  (default)  or  not.  The  specified
          interpretation applies for all subsequent selection conditions up until the next --filter option.

          See the FILE SELECTION section for more information.

   --full-if-older-than time
          Perform  a  full backup if an incremental backup is requested, but the latest full backup in the collection is older than the given time.  See the TIME FORMATS section for more
          information.

   --force
          Proceed even if data loss might result.  Duplicity will let the user know when this option is required.

   --ftp-passive
          Use passive (PASV) data connections.  The default is to use passive, but to fallback to regular if the passive connection fails or times out.

   --ftp-regular
          Use regular (PORT) data connections.

   --gio  Use the GIO backend and interpret any URLs as GIO would.

   --gpg-binary file_path
          Allows you to force duplicity to use file_path as gpg command line binary. Can be an absolute or relative file path or a file name.  Default value is 'gpg'. The binary will  be
          localized via the PATH environment variable.

   --gpg-options='options'

          Allows  you  to  pass  options to gpg encryption. The options list should be of the form '--opt1 --opt2=val2' where the string is quoted and the only spaces allowed are between
          options.

          NOTE: This options value should be bound with '=' as in

          --gpg-options='--gpg-option=value'

          See ARGPARSE PROBLEM for more detail.

   --hidden-encrypt-key key-id
          Same as --encrypt-key, but it hides user's key id from encrypted file. It uses the gpg's --hidden-recipient command to obfuscate the owner of the backup. On restore,  gpg  will
          automatically try all available secret keys in order to decrypt the backup. See gpg(1) for more details.

   --ignore-errors
          Try  to  ignore  certain errors if they happen. This option is only intended to allow the restoration of a backup in the face of certain problems that would otherwise cause the
          backup to fail. It is not ever recommended to use this option unless you have a situation where you are trying to restore from backup and it is  failing  because  of  an  issue
          which you want duplicity to ignore. Even then, depending on the issue, this option may not have an effect.

          Please  note  that  while  ignored  errors  will  be logged, there will be no summary at the end of the operation to tell you what was ignored, if anything. If this is used for
          emergency restoration of data, it is recommended that you run the backup in such a way that you can revisit the backup log (look for lines containing the string IGNORED_ERROR).

          If you ever have to use this option for reasons that are not understood or understood but not your own responsibility, please contact duplicity maintainers.  The  need  to  use
          this option under production circumstances would normally be considered a bug.

   --imap-full-address email_address
          The full email address of the user name when logging into an imap server.  If not supplied just the user name part of the email address is used.

   --imap-mailbox option
          Allows you to specify a different mailbox.  The default is "INBOX".  Other languages may require a different mailbox than the default.

   --idr-fakeroot
          idrived  uses the concept of a "fakeroot" directory, defined via the --idr-fakeroot=... switch. This can be an existing directory, or the directory is created at runtime on the
          root of the (host) files system. (caveat: you have to have write access to the root!). Directories created at runtime are auto-removed on exit!
          So, in the above scheme, we could do:
              duplicity --idr-fakeroot=nicepath idrived://DUPLICITY
          our files end-up at
              <MYBUCKET>/DUPLICITY/nicepath

   --idr-fakeroot
          idrived uses the concept of a "fakeroot" directory, defined via the --idr-fakeroot=... switch. This can be an existing directory, or the directory is created at runtime on  the
          root of the (host) files system. (caveat: you have to have write access to the root!). Directories created at runtime are auto-removed on exit!
          So, in the above scheme, we could do:
              duplicity --idr-fakeroot=nicepath idrived://DUPLICITY
          our files end-up at
              <MYBUCKET>/DUPLICITY/nicepath

   --include shell_pattern
          Similar  to  --exclude  but  include  matched  files instead.  Unlike --exclude, this option will also match parent directories of matched files (although not necessarily their
          contents).  See the FILE SELECTION section for more information.

   --include-filelist filename
          Like --exclude-filelist, but include the listed files instead.  See the FILE SELECTION section for more information.

   --include-regexp regexp
          Include files matching the regular expression regexp.  Only files explicitly matched by regexp will be included by this  option.   See  the  FILE  SELECTION  section  for  more
          information.

   --jsonstat
          Record statistic data similar to the default stats printed at the end of a backup job, addtional it includes some meta data about the backup chain e.g. when the full backup was
          created  and  how  many  incremental  backups were made before.  Output format is json. It written to stdout at notice level (as classic stats) and the statistics are kept as a
          separte file next to the manifest but with "jsonstat" as extension.  collection-status --show-changes-in-set <index> --jsonstat adds data collected in the backup job and switch
          the output format to json.  If <index> is set to -1 statistics for the whole backup chain are printed.

   --log-fd number
          Write specially-formatted versions of output messages to the specified file descriptor.  The format used is designed to be easily consumable by other programs.

   --log-file filename
          Write specially-formatted versions of output messages to the specified file.  The format used is designed to be easily consumable by other programs.

   --log-timestamp
          Write the log with timestamp and log level before the message, similar to syslog.

   --max-blocksize number
          limits the maximum size of the blocks examined for changes during the diff process.

          By default the integer square root of file length is used as the librsync block size.  Minimum being 512 byte with no maximum unless --max-blocksize is supplied.  Block size is
          rounded up to the nearest 512 byte boundary.

          If you specify a larger max_blocksize, your difftar files will be larger, but your sigtar files will be smaller.  If you specify a smaller max_blocksize, the reverse occurs.

          The --max-blocksize option should be in multiples of 512.

          Max blocksize defaults to not supplied.

   --mf-purge
          Option for mediafire to purge files on delete instead of sending to trash.

   --mp-segment-size megs
          Swift backend segment size in megabytes

   --name symbolicname
          Set the symbolic name of the backup being operated on. The intent is to use a separate name for each logically distinct backup. For example, someone may use "home_daily_s3" for
          the daily backup of a home directory to Amazon S3. The structure of the name is up to the user, it is only important that the names be distinct. The symbolic name is  currently
          only  used  to  affect the expansion of --archive-dir , but may be used for additional features in the future. Users running more than one distinct backup are encouraged to use
          this option.

          If not specified, the default value is a hash of the backend URL.

   --no-check-remote
          Turn off validation of the remote manifest.  Checking is the default.  No checking will allow you to backup without the private key, but will mean that the remote manifest  may
          exist and be corrupted, leading to the possibility that the backup might not be recoverable.

   --no-compression
          Do not use GZip to compress files on remote system.

   --no-encryption
          Do not use GnuPG to encrypt files on remote system.

   --no-print-statistics
          By default duplicity will print statistics about the current session after a successful backup.  This switch disables that behavior.

   --no-files-changed
          By  default duplicity will collect file names and change action in memory (add, del, chg) during backup.  This can be quite expensive in memory use, especially with millions of
          small files.  This flag turns off that collection.  This means that the --file-changed option for collection-status will return nothing.

   --null-separator
          Use nulls (\0) instead of newlines (\n) as line separators, which may help when dealing with filenames containing newlines.  This affects  the  expected  format  of  the  files
          specified by the --{include|exclude}-filelist switches and the --{files-from} option, as well as the format of the directory statistics file.

   --numeric-owner
          On restore always use the numeric uid/gid from the archive and not the archived user/group names, which is the default behaviour.  Recommended for restoring from live cds which
          might have the users with identical names but different uids/gids.

   --no-restore-ownership
          Ignores  the  uid/gid  from the archive and keeps the current user's one.  Recommended for restoring data to mounted filesystem which do not support Unix ownership or when root
          privileges are not available.

   --num-retries number
          Number of retries to make on errors before giving up.

   --par2-options='options'
          Verbatim options to pass to par2.

          NOTE: This options value should be bound with '=' as in

          --par2-options='-a -b'

          See ARGPARSE PROBLEM for more detail.

   --par2-redundancy percent
          Adjust the level of redundancy in percent for Par2 recovery files (default 10%).

   --par2-volumes number
          Number of Par2 volumes to create (default 1).

   --progress
          When selected, duplicity will output the current upload progress and estimated upload time. To annotate changes, it will perform a first dry-run before a full  or  incremental,
          and then runs the real operation estimating the real upload progress.

   --progress-rate number
          Sets the update rate at which duplicity will output the upload progress messages (requires --progress option). Default is to print the status each 3 seconds.

   --rename <original path> <new path>
          Treats the path orig in the backup as if it were the path new.  Can be passed multiple times. An example:

          duplicity restore --rename Documents/metal Music/metal sftp://uid@other.host/some_dir /home/me

   --rsync-options='options'
          Allows  you  to pass options to the rsync backend.  The options list should be of the form "opt1=parm1 opt2=parm2" where the option string is quoted and the only spaces allowed
          are between options. The option string will be passed verbatim to rsync, after any internally generated option designating the remote port to use. Here  is  a  possibly  useful
          example:

          duplicity --rsync-options="--partial-dir=.rsync-partial" /home/me rsync://uid@other.host/some_dir

          NOTE: This options value should be bound with '=' as in

          --rsync-options='--partial-dir=.rsync-partial'

          See ARGPARSE PROBLEM for more detail.

   --s3-endpoint-url url
          Specifies the endpoint URL of the S3 storage.

   --s3-multipart-chunk-size
          Chunk  size  (in  MB,  default  is  20MB) used for S3 multipart uploads. Adjust this to maximize bandwidth usage. For example, a chunk size of 10MB and a volsize of 100MB would
          result in 10 chunks per volume upload.

          NOTE: This value should optimally be an even multiple of your --volsize for optimal performance.

          See also A NOTE ON AMAZON S3 below.

   --s3-multipart-max-procs
          Maximum number of concurrent uploads when performing a multipart upload.  The default is 4. You can adjust this number to maximizing bandwidth and CPU utilization.

          NOTE: Too many concurrent uploads may have diminishing returns.

          See also A NOTE ON AMAZON S3 below.

   --s3-region-name
          Specifies the region of the S3 storage. Usually mandatory if the bucket is created in a specific region.

   --s3-unencrypted-connection
          Disable SSL for connections to S3. This may be much faster, at some cost to confidentiality.

          With this option set, anyone between your computer and S3 can observe the traffic and will be able to tell: that you are using Duplicity, the  name  of  the  bucket,  your  AWS
          Access Key ID, the increment dates and the amount of data in each increment.

          This  option  affects  only the connection, not the GPG encryption of the backup increment files. Unless that is disabled, an observer will not be able to see the file names or
          contents.

          See also A NOTE ON AMAZON S3 below.

   --s3-use-deep-archive
          Store volumes using Glacier Deep Archive S3 when uploading to Amazon S3. This storage class has a lower cost of storage but a higher per-request cost along with delays of up to
          48 hours from the time of retrieval request. This storage cost is calculated against a 180-day storage minimum. According to Amazon this storage is ideal for data archiving and
          long-term backup offering 99.999999999% durability.  To restore a backup you will have to manually migrate all data stored on AWS Glacier Deep Archive back to Standard  S3  and
          wait for AWS to complete the migration.

          NOTE:  Duplicity  will  store  the manifest.gpg and sigtar.gpg files from full and incremental backups on AWS S3 standard storage to allow quick retrieval for later incremental
          backups, all other data is stored in S3 Glacier Deep Archive.

   --s3-use-glacier
          Store volumes using Glacier Flexible Storage when uploading to Amazon S3. This storage class has a lower cost of storage but a higher per-request cost along with delays  of  up
          to  12  hours from the time of retrieval request. This storage cost is calculated against a 90-day storage minimum. According to Amazon this storage is ideal for data archiving
          and long-term backup offering 99.999999999% durability.  To restore a backup you will have to manually migrate all data stored on AWS Glacier back to Standard S3 and  wait  for
          AWS to complete the migration.

          NOTE:  Duplicity  will  store  the manifest.gpg and sigtar.gpg files from full and incremental backups on AWS S3 standard storage to allow quick retrieval for later incremental
          backups, all other data is stored in S3 Glacier.

   --s3-use-glacier-ir
          Store volumes using Glacier Instant Retrieval when uploading to Amazon S3. This storage class is similar to Glacier Flexible Storage but offers instant  retrieval  at  standard
          speeds.

          NOTE:  Duplicity  will  store  the manifest.gpg and sigtar.gpg files from full and incremental backups on AWS S3 standard storage to allow quick retrieval for later incremental
          backups, all other data is stored in S3 Glacier.

   --s3-use-ia
          Store volumes using Standard - Infrequent Access when uploading to Amazon S3.  This storage class has a lower storage cost but a higher per-request cost, and the  storage  cost
          is calculated against a 30-day storage minimum. According to Amazon, this storage is ideal for long-term file storage, backups, and disaster recovery.

   --s3-use-onezone-ia
          Store  volumes  using  One  Zone  -  Infrequent Access when uploading to Amazon S3.  This storage is similar to Standard - Infrequent Access, but only stores object data in one
          Availability Zone.

   --s3-use-rrs
          Store volumes using Reduced Redundancy Storage when uploading to Amazon S3.  This will lower the cost of storage but also lower the  durability  of  stored  volumes  to  99.99%
          instead the 99.999999999% durability offered by Standard Storage on S3.

   --s3-use-server-side-kms-encryption
   --s3-kms-key-id key_id
   --s3-kms-grant grant
          Enable server-side encryption using key management service.

   --skip-if-no-change command
          By  default  an  empty incremental backup is created if no files have changed.  Setting this option will skip creating a backup if no data has changed.  Nothing will be sent to
          the target nor information be cached.

   --scp-command command
          (only ssh pexpect backend with --use-scp enabled)
          The command will be used instead of "scp" to send or receive files.  To list and delete existing files, the sftp command is used.
          See also A NOTE ON SSH BACKENDS section SSH pexpect backend.

   --sftp-command command
          (only ssh pexpect backend)
          The command will be used instead of "sftp".
          See also A NOTE ON SSH BACKENDS section SSH pexpect backend.

   --sign-key key-id
          This option can be used when backing up, restoring or verifying.  When backing up, all backup files will be signed with keyid key.  When restoring,  duplicity  will  signal  an
          error  if  any remote file is not signed with the given key-id. The key-id can be given in any of the formats supported by GnuPG; see gpg(1), section "HOW TO SPECIFY A USER ID"
          for details.  Should be specified only once because currently only one signing key is supported. Last entry overrides all other entries.
          See also A NOTE ON SYMMETRIC ENCRYPTION AND SIGNING

   --ssh-askpass
          Tells the ssh backend to prompt the user for the remote system password, if it was not defined in target url and no FTP_PASSWORD env var is set.  This password is also used for
          passphrase-protected ssh keys.

   --ssh-options='options'
          Allows you to pass options to the ssh backend.  Can be specified multiple times or as a space separated options list.  The options list should be of  the  form  "-oOpt1='parm1'
          -oOpt2='parm2'" where the option string is quoted and the only spaces allowed are between options. The option string will be passed verbatim to both scp and sftp, whose command
          line syntax differs slightly hence the options should therefore be given in the long option format described in ssh_config(5).
          example of a list:
                 duplicity --ssh-options="-oProtocol=2 -oIdentityFile='/my/backup/id'" /home/me scp://user@host/some_dir
          example with multiple parameters:
                 duplicity --ssh-options="-oProtocol=2" --ssh-options="-oIdentityFile='/my/backup/id'" /home/me scp://user@host/some_dir

          NOTE: The ssh paramiko backend currently supports only the -i or -oIdentityFile or -oUserKnownHostsFile or -oGlobalKnownHostsFile settings. If needed provide more host specific
          options via ssh_config file.

          NOTE2: This options value should be bound with '=' as in

          --ssh-options='-oProtocol=2 -oIdentityFile=/my/backup/id'

          See ARGPARSE PROBLEM for more detail.

   --ssl-cacert-file file
          (only webdav & lftp backend) Provide a cacert file for ssl certificate verification.

          See also A NOTE ON SSL CERTIFICATE VERIFICATION.

   --ssl-cacert-path path/to/certs/
          (only webdav backend and python 2.7.9+ OR lftp+webdavs and a recent lftp) Provide a path to a folder containing cacert files for ssl certificate verification.

          See also A NOTE ON SSL CERTIFICATE VERIFICATION.

   --ssl-no-check-certificate
          (only webdav & lftp backend) Disable ssl certificate verification.

          See also A NOTE ON SSL CERTIFICATE VERIFICATION.

   --swift-storage-policy
          Use this storage policy when operating on Swift containers.

          See also A NOTE ON SWIFT (OPENSTACK OBJECT STORAGE) ACCESS.

   --metadata-sync-mode mode
          This option defaults to 'partial', but you can set it to 'full'

          Use  'partial' to avoid syncing metadata for backup chains that you are not going to use.  This saves time when restoring for the first time, and lets you restore an old backup
          that was encrypted with a different passphrase by supplying only the target passphrase.

          Use 'full' to sync metadata for all backup chains on the remote.

   --tempdir directory
          Use this existing directory for duplicity temporary files instead of the system default, which is usually the /tmp directory. This option supersedes any environment variable.

          See also ENVIRONMENT VARIABLES.

   -t time, --time time, --restore-time time
          Specify the time from which to restore or list files.

          See section TIME FORMATS for details.

   --time-separator char
          Use char as the time separator in filenames instead of colon (":").

          NOTE: This option only applies to recovery and status style actions.  We no longer create or write filenames with time separators, but will read older  backups  that  may  need
          this option.

   --timeout seconds
          Use seconds as the socket timeout value if duplicity begins to timeout during network operations.  The default is 30 seconds.

   --use-agent
          If  this  option is specified, then --use-agent is passed to the GnuPG encryption process and it will try to connect to gpg-agent before it asks for a passphrase for --encrypt-
          key or --sign-key if needed.

          NOTE: Contrary to previous versions of duplicity, this option will also be honored by GnuPG 2 and newer versions. If GnuPG 2 is in use, duplicity passes the option  --pinentry-
          mode=loopback  to  the  the  gpg  process  unless --use-agent is specified on the duplicity command line. This has the effect that GnuPG 2 uses the agent only if --use-agent is
          given, just like GnuPG 1.

   --verbosity level, -vlevel
          Specify output verbosity level (log level).  Named levels and corresponding values are 0 Error, 2 Warning, 4 Notice (default), 8 Info, 9 Debug (noisiest).
          level may also be
                 a character: e, w, n, i, d
                 a word: error, warning, notice, info, debug

   The options -v4, -vn and -vnotice are functionally equivalent, as are the mixed/upper-case versions -vN, -vNotice and -vNOTICE.

   --version
          Print duplicity's version and quit.

   --volsize number
          Change the volume size to number MB. Default is 200MB.

   --webdav-headers csv formatted key,value pairs
          The input format is comma separated list of key,value pairs. Standard CSV encoding may be used.

          For example to set a Cookie use 'Cookie,name=value', or '"Cookie","name=value"'.

          You can set multiple headers, e.g. '"Cookie","name=value","Authorization","xxx"'.