#Duplicacy vs borg archive#
#Duplicacy vs borg password#
#Duplicacy vs borg download#

borg list repo::Monday allows you to list the existing files in an archive, and borg extract repo::Monday allows you to extract it into a directory. borg list repo allows to list the existing archives (dates). The manipulation of the data is relatively simple. Of course, in the case of a script that automates the backup, for example on a daily basis, it is easiest to enter the date as the name of the archive: DATE=$(date +%Y-%m-%d) Thanks to deduplication, Borg will only store new data: files that have not been modified are not added a second time, which greatly limits the size of the archive.

#Duplicacy vs borg archive#

The next day, you can create a new “Tuesday” archive with the same files: borg create /path/to/repo::Tuesday ~/folder1 ~/folder2 Since the files stored by Borg are compressed, the archive will be smaller than the original files. Let’s imagine that we want to create a “Monday” archive containing two folders: borg create /path/to/repo::Monday ~/folder1 ~/folder2 To avoid having to type it (to be used in a script for example), it is possible to store it in a ~/.borg-passphrase file and pass it as an environment variable: export BORG_PASSCOMMAND='cat $HOME/.borg-passphrase'

#Duplicacy vs borg password#

To do this, we use the following command: borg init -encryption=repokey /path/to/repoĪ password is required to encrypt the archive. Initialize the archiveįirst, a Borg directory must be initialized. After several tries, I ended up preferring it for its simplicity and performance over its many competitors, such as Restic, Duplicacy or Duplicati. encrypt the backup, so that the data cannot be decoded by someone and store it safely in the cloud.īorg is a deduplicating backup program which supports compression and authenticated encryption.compress the files, to limit the space taken up as well.store only the changes from one date to another (but have the possibility to extract the complete backup from any date) so as not to take up a considerable amount of space My goal is to create a script to automatically back up the files of several folders in an archive, and to synchronize it on a remote server. So it was time to use a much more serious backup method. Lastly, the hard disk was stored at my place, which ran the risk of losing everything in case of theft or fire. Moreover, they were done by hand, which was not only painful, but also risked forgetting files or making mistakes. Of course, this raised a lot of problems: the backups were irregular and rare (up to six months between two backups, so it was not unusual for me to lose the previous day’s work because of a mistake).

#Duplicacy vs borg download#

A few times a year, I would manually copy the files I wanted to download to an external hard drive. Remote backups with Borg and Rclone – Sylvain Durand sylvain durand Remote backups with Borg and Rclone įor a long time, my backup methods were very… questionable.