Exampleĭuplicacy add -copy default -bit-identical -repository This means of course, that the added storage can have a different password from the source. The -e option determines whether or not the new storage will be encrypted. It is possible to have an encrypted source and an unencrypted new storage, or vice versa. The -bit-identical option does not copy the encryption option. This has the effect that you can rclone 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. In this case the names of the chunks generated by Duplicacy during backup will be identical in the source and new storage. The -bit-identical option is used along with the -copy option and will copy the IDKey, ChunkKey and FileKey to the new storage from the old one. If the -copy option is specified, these parameters will be copied from the existing storage rather than from the command line. Two different storage are copy-compatible if they have the same 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. The -copy option is required if later you want to copy snapshots between this storage and another storage. The -iterations option specifies how many iterations are used to generate the key that encrypts the config file from the storage password. ![]() Example duplicacy add -min 1M # the minimumchunk size is 1MB Example duplicacy add -max 16M # the maximum chunk size is 16MB Example duplicacy add -c 4M # the average chunk size is 4MB key the RSA public key to encrypt file chunksĭuplicacy add ExampleĪdd an encrypted webdav storage with the name webdav-storage, the path the snapshot name my-documents-snap and copy all settings from the existing default storage.ĭuplicacy add -e -copy default -bit-identical webdav-storage my-documents-snap Options -chunk-size, -c repository specify the path of the repository (instead of the current working directory) bit-identical (when using -copy) make the new storage bit-identical to also allow rsync etc. copy make the new storage compatible with an existing one to allow for copy operations iterations the number of iterations used in storage key derivation (default is 16384) min-chunk-size, -min the minimum size of chunks (default is chunk-size/4) max-chunk-size, -max the maximum size of chunks (default is chunk-size*4) chunk-size, -c the average size of chunks (default is 4M) encrypt, -e encrypt the storage with a password Quick overview SYNOPSIS:ĭuplicacy add - Add an additional storage to be used for the existing repository If the add-ed storage has already been initialised before, then the command line options will be ignored and existing options are used.Ĭlick here for a list of related forum topics. Like the init command, if the storage has not been initialized before, a storage configuration file derived from the command line options will be created. The sections that follow provide information on the options for building a hash table.The add command connects another storage to the current repository. ![]() Contains all lines from the input bed file that are not comment lines, lines that describe empty intervals, or lines with contig names that were not found in the input FASTA.ĭragen -build-hash-table true -ht-reference -output-directory A tab delimeted bed file that describes the masked regions. This table is for information purposes and is not used by other tools. This file provides key information about the reference genome and hash table.Ī binary version of hash_table.cfg used to configure DRAGEN.Ī text file listing extensive internal statistics on the constructed hash including the hash table occupancy percentages. This is encoded in 1,526,285,312 bytes = 1.46 GB, where 1 GB means 1 GiB or 2 30 bytes.Ĭompressed hash table. The hash table is decompressed and used by the DRAGEN mapper to look up primary seeds with length specified by the -ht-seed-len option and extended seeds of various lengths.Ī list of parameters and attributes for the generated hash table in a text format. In between reference sequences, N are trimmed and padding is automatically inserted. For example, hg19 has 3,137,161,264 bases in 93 sequences. Four-bit codes are used, so the size in bytes is roughly half the reference genome size. The reference sequences, encoded in 4 bits per base. ![]() DRAGEN generates the following set of files: ![]() The option takes as input a FASTA file with multiple reference sequences being concatenated and a preexisting output directory. Use the -build-hash-table option to transform a reference FASTA into the hash table for DRAGEN mapping.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |