Thus consuming double the CPU and disk resources and taking longer times for what is a single redundant backup. This works, but is not the best practice for two reasons:įirst, you are running the backup twice: once for the default storage and the second time for the offsite_storage storage. Therefore, when you want to backup to the new storage, you have to specifically select it when running backup as such: duplicacy backup -storage offsite_storage Now when you run the backup command, by default the backup will be stored to the default storage: duplicacy backup # add an additional storage named `offsite_storage`:ĭuplicacy add offsite_storage repository_id offsite_storage_url The first argument to add is the name of the new storage that can be used by other commands (instead of the normal default). You can add additional storage providers to this repository by running the add command. ) cd /path/to/repositoryĭuplicacy init repository_id onsite_storage_url ( Even though you are not told directly, this storage has the name default for easy access. When a repository is initialized you always provide the url to the default storage, which will be initialized if it hasn’t been.
Duplicacy provides a unique tool to make this backup redundancy solution super easy. It is therefore highly recommended to back up your data to at least two different storage providers.
There is always a danger of losing all your data if it is stored only in one storage.
0 kommentar(er)
