add

SYNOPSIS:
   duplicacy add - Add an additional storage to be used for the existing repository

USAGE:
   duplicacy add [command options] <storage name> <snapshot id> <storage url>

OPTIONS:
   -encrypt, -e                    encrypt the storage with a password
   -chunk-size, -c <size> 	   the average size of chunks (defaults to 4M)
   -max-chunk-size, -max <size>    the maximum size of chunks (defaults to chunk-size*4)
   -min-chunk-size, -min <size>    the minimum size of chunks (defaults to chunk-size/4)
   -iterations <i>                 the number of iterations used in storage key deriviation (default is 16384)
   -copy <storage name>            make the new storage copy-compatible with an existing one
   -bit-identical                  (when using -copy) make the new storage bit-identical to also allow rsync etc.

The add command connects another storage to the current repository. Like the init command, if the storage has not been initialized before, a storage configuration file derived from the command line options will be uploaded, but those options will be ignored if the configuration file already exists in the storage.

A unique storage name must be given in order to distinguish it from other storages.

The -iterations option speicifies how many iterations are used to generate the key that encrypts the config file from the storage password.

The -copy option is required if later you want to copy snapshots between this storage and another storage. Two storages are copy-compatible if they have the same average chunk size, the same maximum chunk size, the same minimum chunk size, the same chunk seed (used in calculating the rolling hash in the variable-size chunks algorithm), and the same hash key. If the -copy option is specified, these parameters will be copied from the existing storage rather than from the command line.

The -bit-identical option is used along with the -copy option (usage: -copy default -bit-identical), and it also copies the IDKey, ChunkKey and FileKey to the new storage from the old one. In this case the names of the chunks generated by Duplicacy during backup will be identical in the source and new storage. This has the effect that you can rsync the chunks folder for example from local (source) to Google Drive (new storage), and then only do backups on Google Drive, and the existing chunks will be identical (same name, same size) as if the backup was run locally.

The -bit-identical option does not copy the encryption option. It is possible to have an encrypted source and an unencrypted new storage, or vice versa. The -e option of the add command determines whether or not the new storage will be encrypted.