Skip to content

Revisions

  • Updated restore (markdown)

    @gilbertchen gilbertchen committed Jun 22, 2023
  • Updated restore (markdown)

    @gilbertchen gilbertchen committed Jul 21, 2020
  • Updated restore (markdown)

    @gilbertchen gilbertchen committed Mar 7, 2020
  • Update wiki to mirror the Guide from forum.duplicacy.com

    @gilbertchen gilbertchen committed Mar 7, 2020
  • Wiki was moved to forum.duplicacy.com

    @TheBestPessimist TheBestPessimist committed Sep 11, 2018
  • fixing -limit-rate incorrectly stating in the document that it limits upload instead of download for restore

    @leerspace leerspace committed Mar 29, 2018
  • Updated restore (markdown)

    @gilbertchen gilbertchen committed Nov 10, 2017
  • Updated restore (markdown)

    @gilbertchen gilbertchen committed Nov 10, 2017
  • Updated restore``` SYNOPSIS: duplicacy restore Restore the repository to a previously saved snapshot USAGE: duplicacy restore [command options] [ ] [pattern] ... OPTIONS: r revision the revision number of the snapshot (required) hash detect file differences by hash (rather than size and timestamp) overwrite overwrite existing files in the repository delete delete files not in the snapshot stats show statistics during and after restore threads n number of downloading threads limit rate kB s the maximum download rate (in kilobytes sec) storage storage name restore from the specified storage instead of the default one ``` The *restore* command restores the repository to a previous revision. By default the restore procedure will treat files that have the same sizes and timestamps as those in the snapshot as unchanged files, but with the hash option, every file will be fully scanned to make sure they are in fact unchanged. By default the restore procedure will not overwriting existing files, unless the ` overwrite` option is specified. The ` delete` option indicates that files not in the snapshot will be removed. If the ` stats` option is specified, statistical information such as transfer speed, and number of chunks will be displayed throughout the restore procedure. The ` threads` option can be used to specify more than one thread to download chunks. The ` limit rate` option sets a cap on the maximum upload rate. When the repository can have multiple storages (added by the *add* command), you can select the storage to restore from by specifying the storage name. Unlike the *backup* procedure that reading the include exclude patterns from a file, the *restore* procedure reads them from the command line. If the patterns can cause confusion to the command line argument parser, should be prepended to the patterns. Please refer to the [Include Exclude Patterns](#includeexclude patterns) section for how to specify patterns. (markdown)

    @gilbertchen gilbertchen committed Nov 10, 2017