neulab/tldr huggingface dataset:
--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.
--file-prefix, --file-prefix-manifest, --file-prefix-archive, --file- prefix-signature Adds a prefix to all files, manifest files, archive files, and/or 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
--file-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.
--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.
--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.
--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=parm" where the string is quoted and the only spaces allowed are between options.
--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.
--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.
--max-blocksize number determines the number of the blocks examined for changes during the diff process.  For files < 1MB the blocksize is a constant of 512.  For files over 1MB the size is given by:
file_blocksize = int((file_len / (2000 * 512)) * 512) return min(file_blocksize, config.max_blocksize)
where config.max_blocksize defaults to 2048.  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.
--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-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.
--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 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.
--do-not-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.
--old-filenames Use the old filename format (incompatible with Windows/Samba) rather than the new filename format.
--par2-options options Verbatim options to pass to par2.
--par2-redundancy percent Adjust the level of redundancy in percent for Par2 recovery files (default 10%).
--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
--s3-european-buckets When using the Amazon S3 backend, create buckets in Europe instead of the default (requires --s3-use-new-style ). Also see the EUROPEAN S3 BUCKETS section.
This option does not apply when using the newer boto3 backend, which does not create buckets.
See also A NOTE ON AMAZON S3 below.
--s3-unencrypted-connection Don't use SSL for connections to S3.
This may be much faster, at some cost to confidentiality.
With this option, anyone who can observe traffic between your computer and S3 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.
This option is not available when using the newer boto3 backend.
--s3-use-new-style When operating on Amazon S3 buckets, use new-style subdomain bucket addressing. This is now the preferred method to access Amazon S3, but is not backwards compatible if your bucket name contains upper-case characters or other characters that are not valid in a hostname.
This option has no effect when using the newer boto3 backend, which will always use new style subdomain bucket naming.
--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-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-glacier Store volumes using Glacier 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 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.  Notice: Duplicity will store the manifest.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-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. Notice: Duplicity will store the manifest.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.
Glacier Deep Archive is only available when using the newer boto3 backend.
--s3-use-multiprocessing Allow multipart volumne uploads to S3 through multiprocessing. This option requires Python 2.6 and can be used to make uploads to S3 more efficient.  If enabled, files duplicity uploads to S3 will be split into chunks and uploaded in parallel. Useful if you want to saturate your bandwidth or if large files are failing during upload.
This has no effect when using the newer boto3 backend.  Boto3 always attempts to multiprocessing when it is believed it will be more efficient.
--s3-use-server-side-encryption Allow use of server side encryption in S3
--s3-multipart-chunk-size Chunk size (in MB) used for S3 multipart uploads. Make this smaller than --volsize to maximize the use of your bandwidth. For example, a chunk size of 10MB with a volsize of 30MB will result in 3 chunks per volume upload.
--s3-multipart-max-procs Specify the maximum number of processes to spawn when performing a multipart upload to S3. By default, this will choose the number of processors detected on your system (e.g. 4 for a 4-core system). You can adjust this number as required to ensure you don't overload your system while maximizing the use of your bandwidth.
This has no effect when using the newer boto3 backend.
--s3-multipart-max-timeout You can control the maximum time (in seconds) a multipart upload can spend on uploading a single chunk to S3. This may be useful if you find your system hanging on multipart uploads or if you'd like to control the time variance when uploading to S3 to ensure you kill connections to slow S3 endpoints.
--s3-region-name Specifies the region of the S3 storage.
This is currently only used in the newer boto3 backend.
--s3-endpoint-url Specifies the endpoint URL of the S3 storage.
--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.
--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.
--short-filenames If this option is specified, the names of the files duplicity writes will be shorter (about 30 chars) but less understandable. This may be useful when backing up to MacOS or another OS or FS that doesn't support long filenames.
--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.
--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.
-ttime, --time time, --restore-time time Specify the time from which to restore or list files.
--time-separator char Use char as the time separator in filenames instead of colon (":").
--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.
TMPDIR, TEMP, TMP In decreasing order of importance, specifies the directory to use for temporary files (inherited from Python's tempfile module). Eventually the option --tempdir supercedes any of these.
FTP_PASSWORD Supported by most backends which are password capable. More secure than setting it in the backend url (which might be readable in the operating systems process listing to other users on the same machine).
PASSPHRASE This passphrase is passed to GnuPG. If this is not set, the user will be prompted for the passphrase.
SIGN_PASSPHRASE The passphrase to be used for --sign-key.  If ommitted and sign key is also one of the keys to encrypt against PASSPHRASE will be reused instead.  Otherwise, if passphrase is needed but not set the user will be prompted for it.
Other environment variables may be used to configure specific backends.  See the notes for the particular backend.
Duplicity uses the URL format (as standard as possible) to define data locations.  The generic format for a URL is:
scheme://[user[:password]@]host[:port]/[/]path
It is not recommended to expose the password on the command line since it could be revealed to anyone with permissions to do process listings, it is permitted however.  Consider setting the environment variable FTP_PASSWORD instead, which is used by most, if not all backends, regardless of it's name.
In protocols that support it, the path may be preceded by a single slash, '/path', to represent a relative path to the target home directory, or preceded by a double slash, '//path', to represent an absolute filesystem path.
Note: Scheme (protocol) access may be provided by more than one backend. In case the default backend is buggy or simply not working in a specific case it might be worth trying an alternative implementation.  Alternative backends can be selected by prefixing the scheme with the name of the alternative backend e.g. ncftp+ftp:// and are mentioned below the scheme's syntax summary.
Formats of each of the URL schemes follow:
Amazon Drive Backend
ad://some_dir
See also A NOTE ON AMAZON DRIVE
azure://container-name
See also A NOTE ON AZURE ACCESS
b2://account_id[:application_key]@bucket_name/[folder/]
box:///some_dir[?config=path_to_config]
See also A NOTE ON BOX ACCESS
Cloud Files (Rackspace)
cf+http://container_name
See also A NOTE ON CLOUD FILES ACCESS
dpbx:///some_dir
Make sure to read A NOTE ON DROPBOX ACCESS first!
Local file path
file://[relative|/absolute]/local/path
FISH (Files transferred over Shell protocol) over ssh
fish://user[:password]@other.host[:port]/[relative|/absolute]_path
ftp[s]://user[:password]@other.host[:port]/some_dir
NOTE: use lftp+, ncftp+ prefixes to enforce a specific backend, default is lftp+ftp://...
gdocs://user[:password]@other.host/some_dir
NOTE: use pydrive+, gdata+ prefixes to enforce a specific backend, default is pydrive+gdocs://...
gs://bucket[/prefix]
hsi://user[:password]@other.host/some_dir
hubiC
cf+hubic://container_name
See also A NOTE ON HUBIC
IMAP email storage
imap[s]://user[:password]@host.com[/from_address_prefix]
See also A NOTE ON IMAP
MEGA.nz cloud storage (only works for accounts created prior to November 2018, uses "megatools")
mega://user[:password]@mega.nz/some_dir
NOTE: if not given in the URL, relies on password being stored within $HOME/.megarc (as used by the "megatools" utilities)
MEGA.nz cloud storage (works for all MEGA accounts, uses "MEGAcmd" tools)
megav2://user[:password]@mega.nz/some_dir megav3://user[:password]@mega.nz/some_dir[?no_logout=1] (For latest MEGAcmd)
NOTE: despite "MEGAcmd" no longer uses a configuration file, for convenience storing the user password this backend searches it in the $HOME/.megav2rc file (same syntax as the old $HOME/.megarc) [Login] Username = MEGA_USERNAME Password = MEGA_PASSWORD
OneDrive Backend
onedrive://some_dir
Par2 Wrapper Backend
par2+scheme://[user[:password]@]host[:port]/[/]path
See also A NOTE ON PAR2 WRAPPER BACKEND
Rclone Backend
rclone://remote:/some_dir
See also A NOTE ON RCLONE BACKEND
Rsync via daemon
rsync://user[:password]@host.com[:port]::[/]module/some_dir
Rsync over ssh (only key auth)
rsync://user@host.com[:port]/[relative|/absolute]_path
S3 storage (Amazon)
s3://host[:port]/bucket_name[/prefix] s3+http://bucket_name[/prefix] defaults to the legacy boto backend based on boto v2 (last update 2018/07) alternatively try the newer boto3+s3://bucket_name[/prefix]
For details see A NOTE ON AMAZON S3 and see also A NOTE ON EUROPEAN S3 BUCKETS below.
SCP/SFTP access
scp://.. or sftp://user[:password]@other.host[:port]/[relative|/absolute]_path
defaults are paramiko+scp:// and paramiko+sftp:// alternatively try pexpect+scp://, pexpect+sftp://, lftp+sftp:// See also --ssh-askpass, --ssh-options and A NOTE ON SSH BACKENDS.
Swift (Openstack)
swift://container_name[/prefix]
See also A NOTE ON SWIFT (OPENSTACK OBJECT STORAGE) ACCESS
Public Cloud Archive (OVH)
pca://container_name[/prefix]
See also A NOTE ON PCA ACCESS
tahoe://alias/directory
webdav[s]://user[:password]@other.host[:port]/some_dir
alternatively try lftp+webdav[s]://
pydrive://<service account' email address>@developer.gserviceaccount.com/some_dir
See also A NOTE ON PYDRIVE BACKEND below.
gdrive://<service account' email address>@developer.gserviceaccount.com/some_dir
See also A NOTE ON GDRIVE BACKEND below.
multi:///path/to/config.json
See also A NOTE ON MULTI BACKEND below.
mf://user[:password]@mediafire.com/some_dir
See also A NOTE ON MEDIAFIRE BACKEND below.
duplicity uses time strings in two places.  Firstly, many of the files duplicity creates will have the time in their filenames in the w3 datetime format as described in a w3 note at http://www.w3.org/TR/NOTE- datetime.  Basically they look like "2001-07-15T04:09:38-07:00", which means what it looks like.  The "-07:00" section means the time zone is 7 hours behind UTC.
Secondly, the -t, --time, and --restore-time options take a time string, which can be given in any of several formats:
1.     the string "now" (refers to the current time)
2.     a sequences of digits, like "123456890" (indicating the time in seconds after the epoch)
3.     A string like "2002-01-25T07:00:00+02:00" in datetime format
4.     An interval, which is a number followed by one of the characters s, m, h, D, W, M, or Y (indicating seconds, minutes, hours, days, weeks, months, or years respectively), or a series of such pairs. In this case the string refers to the time that preceded the current time by the length of the interval.  For instance, "1h78m" indicates the time that was one hour and 78 minutes ago.  The calendar here is unsophisticated: a month is always 30 days, a year is always 365 days, and a day is always 86400 seconds.
5.     A date format of the form YYYY/MM/DD, YYYY-MM-DD, MM/DD/YYYY, or MM-DD-YYYY, which indicates midnight on the day in question, relative to the current time zone settings.  For instance, "2002/3/5", "03-05-2002", and "2002-3-05" all mean March 5th, 2002.
When duplicity is run, it searches through the given source directory and backs up all the files specified by the file selection system.  The file selection system comprises a number of file selection conditions, which are set using one of the following command line options: --exclude --exclude-device-files --exclude-if-present --exclude-filelist --exclude-regexp --include --include-filelist --include-regexp Each file selection condition either matches or doesn't match a given file.  A given file is excluded by the file selection system exactly when the first matching file selection condition specifies that the file be excluded; otherwise the file is included.
duplicity --include /usr --exclude /usr /usr scp://user@host/backup
duplicity /usr scp://user@host/backup
because the include and exclude directives match exactly the same files, and the --include comes first, giving it precedence.  Similarly,
duplicity --include /usr/local/bin --exclude /usr/local /usr scp://user@host/backup
would backup the /usr/local/bin directory (and its contents), but not /usr/local/doc.
The include, exclude, include-filelist, and exclude-filelist options accept some extended shell globbing patterns.  These patterns can contain *, **, ?, and [...]  (character ranges). As in a normal shell, * can be expanded to any string of characters not containing "/", ?  expands to any character except "/", and [...]  expands to a single character of those characters specified (ranges are acceptable).  The new special pattern, **, expands to any string of characters whether or not it contains "/".  Furthermore, if the pattern starts with "ignorecase:" (case insensitive), then this prefix will be removed and any character in the string can be replaced with an upper- or lowercase version of itself.
Remember that you may need to quote these characters when typing them into a shell, so the shell does not interpret the globbing patterns before duplicity sees them.
The --exclude pattern option matches a file if:
1.  pattern can be expanded into the file's filename, or 2.  the file is inside a directory matched by the option.
Conversely, the --include pattern matches a file if:
1.  pattern can be expanded into the file's filename, or 2.  the file is inside a directory matched by the option, or 3.  the file is a directory which contains a file matched by the option.
--exclude /usr/local
matches e.g. /usr/local, /usr/local/lib, and /usr/local/lib/netscape.  It is the same as --exclude /usr/local --exclude '/usr/local/**'.
On the other hand
--include /usr/local
specifies that /usr, /usr/local, /usr/local/lib, and /usr/local/lib/netscape (but not /usr/doc) all be backed up. Thus you don't have to worry about including parent directories to make sure that included subdirectories have somewhere to go.
--include ignorecase:'/usr/[a-z0-9]foo/*/**.py'
would match a file like /usR/5fOO/hello/there/world.py.  If it did match anything, it would also match /usr.  If there is no existing file that the given pattern can be expanded into, the option will not match /usr alone.
The --include-filelist, and --exclude-filelist, options also introduce file selection conditions.  They direct duplicity to read in a text file (either ASCII or UTF-8), each line of which is a file specification, and to include or exclude the matching files.  Lines are separated by newlines or nulls, depending on whether the --null-separator switch was given.  Each line in the filelist will be interpreted as a globbing pattern the way --include and --exclude options are interpreted, except that lines starting with "+ " are interpreted as include directives, even if found in a filelist referenced by --exclude-filelist.  Similarly, lines starting with "- " exclude files even if they are found within an include filelist.
For example, if file "list.txt" contains the lines:
/usr/local - /usr/local/doc /usr/local/bin + /var - /var
then --include-filelist list.txt would include /usr, /usr/local, and /usr/local/bin.  It would exclude /usr/local/doc, /usr/local/doc/python, etc.  It would also include /usr/local/man, as this is included within /user/local.  Finally, it is undefined what happens with /var.  A single file list should not contain conflicting file specifications.
Each line in the filelist will also be interpreted as a globbing pattern the way --include and --exclude options are interpreted.  For instance, if the file "list.txt" contains the lines:
dir/foo + dir/bar - **
Then --include-filelist list.txt would be exactly the same as specifying --include dir/foo --include dir/bar --exclude ** on the command line.
Finally, the --include-regexp and --exclude-regexp options allow files to be included and excluded if their filenames match a python regular expression.  Regular expression syntax is too complicated to explain here, but is covered in Python's library reference.  Unlike the --include and --exclude options, the regular expression options don't match files containing or contained in matched files.  So for instance
--include '[0-9]{7}(?!foo)'
matches any files whose full pathnames contain 7 consecutive digits which aren't followed by 'foo'.  However, it wouldn't match /home even if /home/ben/1234567 existed.
1.     The API Keys used for Amazon Drive have not been granted production limits.  Amazon do not say what the development limits are and are not replying to to requests to whitelist duplicity. A related tool, acd_cli, was demoted to development limits, but continues to work fine except for cases of excessive usage. If you experience throttling and similar issues with Amazon Drive using this backend, please report them to the mailing list.
2.     If you previously used the acd+acdcli backend, it is strongly recommended to update to the ad backend instead, since it interfaces directly with Amazon Drive. You will need to setup the OAuth once again, but can otherwise keep your backups and config.
A NOTE ON AMAZON S3 When backing up to Amazon S3, two backend implementations are available. The schemes "s3" and "s3+http" are implemented using the older boto library, which has been deprecated and is no longer supported.  The "boto3+s3" scheme is based on the newer boto3 library. This new backend fixes several known limitations in the older backend, which have crept in as Amazon S3 has evolved while the deprecated boto library has not kept up.
The boto3 backend should behave largely the same as the older S3 backend, but there are some differences in the handling of some of the "S3" options.  Additionally, there are some compatibility differences with the new backed.  Because of these reasons, both backends have been retained for the time being.  See the documentation for specific options regarding differences related to each backend.
The boto3 backend does not support bucket creation.  This is a deliberate choice which simplifies the code, and side steps problems related to region selection.  Additionally, it is probably not a good practice to give your backup role bucket creation rights.  In most cases the role used for backups should probably be limited to specific buckets.
The boto3 backend only supports newer domain style buckets.  Amazon is moving to deprecate the older bucket style, so migration is recommended. Use the older s3 backend for compatibility with backups stored in buckets using older naming conventions.
The boto3 backend does not currently support initiating restores from the glacier storage class.  When restoring a backup from glacier or glacier deep archive, the backup files must first be restored out of band.  There are multiple options when restoring backups from cold storage, which vary in both cost and speed.  See Amazon's documentation for details.
The Azure backend requires the Microsoft Azure Storage Blobs client library for Python to be installed on the system.  See REQUIREMENTS.
It uses the environment variable AZURE_CONNECTION_STRING (required). This string contains all necessary information such as Storage Account name and the key for authentication.  You can find it under Access Keys for the storage account.
Duplicity will take care to create the container when performing the backup.  Do not create it manually before.
A container name (as given as the backup url) must be a valid DNS name, conforming to the following naming rules:
1.     Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.
2.     Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted in container names.
3.     All letters in a container name must be lowercase.
4.     Container names must be from 3 through 63 characters long.
These rules come from Azure; see https://docs.microsoft.com/en- us/rest/api/storageservices/naming-and-referencing- containers--blobs--and-metadata
The box backend requires boxsdk with jwt support to be installed on the system.  See REQUIREMENTS.
It uses the environment variable BOX_CONFIG_PATH (optional).  This string contains the path to box custom app's config.json. Either this environment variable or the config query parameter in the url need to be specified, if both are specified, query paramter takes precedence.
Create a Box custom app In order to use box backend, user need to create a box custom app in the box developer console (https://app.box.com/developers/console).
After create a new custom app, please make sure it is configured as follow:
1.     Choose "App Access Only" for "App Access Level"
2.     Check "Write all files and folders stored in Box"
3.     Generate a Public/Private Keypair
The user also need to grant the created custom app permission in the admin console (https://app.box.com/master/custom-apps) by clicking the "+" button and enter the client_id which can be found on the custom app's configuration page.
Pyrax is Rackspace's next-generation Cloud management API, including Cloud Files access.  The cfpyrax backend requires the pyrax library to be installed on the system.  See REQUIREMENTS.
Cloudfiles is Rackspace's now deprecated implementation of OpenStack Object Storage protocol.  Users wishing to use Duplicity with Rackspace Cloud Files should migrate to the new Pyrax plugin to ensure support.
The backend requires python-cloudfiles to be installed on the system. See REQUIREMENTS.
It uses three environment variables for authentification: CLOUDFILES_USERNAME (required), CLOUDFILES_APIKEY (required), CLOUDFILES_AUTHURL (optional)
If CLOUDFILES_AUTHURL is unspecified it will default to the value provided by python-cloudfiles, which points to rackspace, hence this value must be set in order to use other cloud files providers.
1.     First of all Dropbox backend requires valid authentication token. It should be passed via DPBX_ACCESS_TOKEN environment variable. To obtain it please create 'Dropbox API' application at: https://www.dropbox.com/developers/apps/create Then visit app settings and just use 'Generated access token' under OAuth2 section. Alternatively you can let duplicity generate access token itself. In such case temporary export DPBX_APP_KEY , DPBX_APP_SECRET using values from app settings page and run duplicity interactively. It will print the URL that you need to open in the browser to obtain OAuth2 token for the application. Just follow on-screen instructions and then put generated token to DPBX_ACCESS_TOKEN variable. Once done, feel free to unset DPBX_APP_KEY and DPBX_APP_SECRET
2.     "some_dir" must already exist in the Dropbox folder. Depending on access token kind it may be: Full Dropbox: path is absolute and starts from 'Dropbox' root folder. App Folder: path is related to application folder. Dropbox client will show it in ~/Dropbox/Apps/<app-name>
3.     When using Dropbox for storage, be aware that all files, including the ones in the Apps folder, will be synced to all connected computers.  You may prefer to use a separate Dropbox account specially for the backups, and not connect any computers to that account. Alternatively you can configure selective sync on all computers to avoid syncing of backup files
A NOTE ON EUROPEAN S3 BUCKETS Amazon S3 provides the ability to choose the location of a bucket upon its creation. The purpose is to enable the user to choose a location which is better located network topologically relative to the user, because it may allow for faster data transfers.
duplicity will create a new bucket the first time a bucket access is attempted. At this point, the bucket will be created in Europe if --s3-european-buckets was given. For reasons having to do with how the Amazon S3 service works, this also requires the use of the --s3-use-new- style option. This option turns on subdomain based bucket addressing in S3. The details are beyond the scope of this man page, but it is important to know that your bucket must not contain upper case letters or any other characters that are not valid parts of a hostname. Consequently, for reasons of backwards compatibility, use of subdomain based bucket addressing is not enabled by default.
Note that you will need to use --s3-use-new-style for all operations on European buckets; not just upon initial creation.
You only need to use --s3-european-buckets upon initial creation, but you may may use it at all times for consistency.
Further note that when creating a new European bucket, it can take a while before the bucket is fully accessible. At the time of this writing it is unclear to what extent this is an expected feature of Amazon S3, but in practice you may experience timeouts, socket errors or HTTP errors when trying to upload files to your newly created bucket. Give it a few minutes and the bucket should function normally.
Filename prefixes can be used in multi backend with mirror mode to define affinity rules. They can also be used in conjunction with S3 lifecycle rules to transition archive files to Glacier, while keeping metadata (signature and manifest files) on S3.
Duplicity does not require access to archive files except when restoring from backup.
Support for Google Cloud Storage relies on its Interoperable Access, which must be enabled for your account.  Once enabled, you can generate Interoperable Storage Access Keys and pass them to duplicity via the GS_ACCESS_KEY_ID and GS_SECRET_ACCESS_KEY environment variables. Alternatively, you can run gsutil config -a to have the Google Cloud Storage utility populate the ~/.boto configuration file.
Enable Interoperable Access: https://code.google.com/apis/console#:storage Create Access Keys: https://code.google.com/apis/console#:storage:legacy
The hubic backend requires the pyrax library to be installed on the system. See REQUIREMENTS.  You will need to set your credentials for hubiC in a file called ~/.hubic_credentials, following this pattern:
[hubic] email = your_email password = your_password client_id = api_client_id client_secret = api_secret_key redirect_uri = http://localhost/
An IMAP account can be used as a target for the upload.  The userid may be specified and the password will be requested.
The from_address_prefix may be specified (and probably should be). The text will be used as the "From" address in the IMAP server.  Then on a restore (or list) command the from_address_prefix will distinguish between different backups.
The multi backend allows duplicity to combine the storage available in more than one backend store (e.g., you can store across a google drive account and a onedrive account to get effectively the combined storage available in both).  The URL path specifies a JSON formated config file containing a list of the backends it will use. The URL may also specify "query" parameters to configure overall behavior.  Each element of the list must have a "url" element, and may also contain an optional "description" and an optional "env" list of environment variables used to configure that backend.
Query Parameters Query parameters come after the file URL in standard HTTP format for example: multi:///path/to/config.json?mode=mirror&onfail=abort multi:///path/to/config.json?mode=stripe&onfail=continue multi:///path/to/config.json?onfail=abort&mode=stripe multi:///path/to/config.json?onfail=abort Order does not matter, however unrecognized parameters are considered an error.
mode=stripe This mode (the default) performs round-robin access to the list of backends. In this mode, all backends must be reliable as a loss of one means a loss of one of the archive files.
mode=mirror This mode accesses backends as a RAID1-store, storing every file in every backend and reading files from the first-successful backend.  A loss of any backend should result in no failure. Note that backends added later will only get new files and may require a manual sync with one of the other operating ones.
onfail=continue This setting (the default) continues all write operations in as best-effort. Any failure results in the next backend tried. Failure is reported only when all backends fail a given operation with the error result from the last failure.
onfail=abort This setting considers any backend write failure as a terminating condition and reports the error.  Data reading and listing operations are independent of this and will try with the next backend on failure.
JSON File Example [ { "description": "a comment about the backend" "url": "abackend://myuser@domain.com/backup", "env": [ { "name" : "MYENV", "value" : "xyz" }, { "name" : "FOO", "value" : "bar" } ], "prefixes": ["prefix1_", "prefix2_"] }, { "url": "file:///path/to/dir" } ]
A NOTE ON PAR2 WRAPPER BACKEND Par2 Wrapper Backend can be used in combination with all other backends to create recovery files. Just add par2+ before a regular scheme (e.g. par2+ftp://user@host/dir or par2+s3+http://bucket_name ). This will create par2 recovery files for each archive and upload them all to the wrapped backend.
Before restoring, archives will be verified. Corrupt archives will be repaired on the fly if there are enough recovery blocks available.
Use --par2-redundancy percent to adjust the size (and redundancy) of recovery files in percent.
The pydrive backend requires Python PyDrive package to be installed on the system. See REQUIREMENTS.
There are two ways to use PyDrive: with a regular account or with a "service account". With a service account, a separate account is created, that is only accessible with Google APIs and not a web login.  With a regular account, you can store backups in your normal Google Drive.
To use a service account, go to the Google developers console at https://console.developers.google.com. Create a project, and make sure Drive API is enabled for the project. Under "APIs and auth", click Create New Client ID, then select Service Account with P12 key.
Download the .p12 key file of the account and convert it to the .pem format: openssl pkcs12 -in XXX.p12  -nodes -nocerts > pydriveprivatekey.pem
The content of .pem file should be passed to GOOGLE_DRIVE_ACCOUNT_KEY environment variable for authentification.
The email address of the account will be used as part of URL. See URL FORMAT above.
The alternative is to use a regular account. To do this, start as above, but when creating a new Client ID, select "Installed application" of type "Other". Create a file with the following content, and pass its filename in the GOOGLE_DRIVE_SETTINGS environment variable: