$ duplicacy prune -keep 0:180 # Remove all backups older than 180 days $ duplicacy prune -keep 7:30 # Keep 1 backup every 7 days for backups older than 30 days $ duplicacy prune -keep 1:7 # Keep 1 backup per day for backups older than 7 days $ duplicacy prune -t quick # Remove all backups with the tag 'quick' The prune command removes backups by revisions, or tags, or retention policies: $ duplicacy prune -r 1 # Remove the backup with revision number 1 $ duplicacy history # Show how a file changes over time $ duplicacy cat # Print a file in a backup $ duplicacy diff # Compare two backups of the same repository, or the same file in two backups $ duplicacy check # Check integrity of backups $ duplicacy init mywork2 sftp:// /path/to/storage # different repository id but same storage urlĭuplicacy provides a set of commands, such as list, check, diff, cat history, to manage backups: $ duplicacy list # List all backups $ cd path/to/your/repository2 # this can be on the same or a different computer In fact, this is the recommended way, because this way you will take advantage of cross-computer deduplication - identical files from different repository will get deduplicated automatically. It is possible to back up two different repositories to the same storage. As long as the new repository has the same repository id, Duplicacy will treat it as a clone of the original repository: $ cd path/to/your/restore/dir # this can be on the same or a different computer Duplicacy is very flexible in this regard, as it allows you to create a new repository no matter where it is. Or you may want to run the restore operation from a different computer. Sometimes you may not want to run the restore operation directly from the original repository, as it may overwrite files that have not been backed up. The restore command rolls back the repository to a previous revision: $ duplicacy restore -r 1 Each backup is identified by the repository id and an increasing revision number starting from 1.

Subsequent backups will be much faster, as only new or modified files will be uploaded. The first backup may take a while depending on the size of the repository and the upload bandwidth. You can now create backups of the repository by invoking the backup command. This repository id is used to uniquely identify this repository if there are other repositories that also back up to the same storage. It also assigns the repository id mywork to the repository. It will initialize the remote storage if this has not been done before (create the required duplicacy config files and folders), but it requires that the folder already exists on the storage (duplicacy will not create it). This init command connects the repository with the remote storage at 192.168.1.100 via SFTP. $ duplicacy init mywork sftp:// /path/to/storage Once you have the Duplicacy executable on your path, you can change to the directory that you want to back up (called repository) and run the init command: $ cd path/to/your/repository

Github duplicacy