- #BORG VS DUPLICACY UPDATE#
- #BORG VS DUPLICACY FULL#
- #BORG VS DUPLICACY CODE#
- #BORG VS DUPLICACY PASSWORD#
Windows VSS shado copies supported (DT seems to have better support) Linux LVM snapshots supported (DT seems to have better support) Lock-free deduplication (DC uses destination files names instead of a local database resulting in lower local storage needs)Ĭross-source de-duplication (possible with DC thanks to lock-free deduplication)
#BORG VS DUPLICACY CODE#
Source code available (*DC source code for CLI only) Borg sweeps 656 GB of data in 4.5 minutes, determines that there is only 13 MB of new data and sends only that over the network.Free (*DC command line free for individual users, else per user or computer fee) Original size Compressed size Deduplicated size Now I get the following report by email every morning: Duration: 4 minutes 22.54 seconds Borg then reads the passphrase from that environment variable, so no user input is necessary. borg-passphrase file contains my passphrase and has the permission set to 400 (read only by my user). usr/local/bin/borg create -stats -exclude "pattern_to_exclude*". #/bin/shĮxport BORG_PASSCOMMAND="cat ~/.borg-passphrase" I added command to a cron job (actually, the Synology Task Scheduler) to run it daily and now I have daily, efficient backups. The cool thing about Borg is that if a backup stops while in progress, it can easily resume at any time. Then you will be able to restore both archives, with BorgBackup doing the right thing in the background to show you only the items that were backed up in that archive. If the next day you rerun the command with archive_name2, it will compare all the chunks and transmit only the ones that have changed or which are new. The archive_name corresponds to one instance when you backed up everything. It will also generate a keyfile, which you should export and keep safe on other machines: > borg key export to start the actual backup process: > borg create -stats -progress -exclude "pattern_to_exclude*". First you have to initialize a repository, which will contain your backups: > borg init -e authenticated
#BORG VS DUPLICACY FULL#
It also does deduplication, compression and deltas, so after an initial full backup, it only backs up changes, so it's quite efficient.īorgBackup is quite simple to use. It has builtin encryption for the archive, so I don't need to muck around with full disk encryption. I looked around and there are several options. Now that I have a stable connection to the Pi, it was time to set up the actual backups. It has worked for two weeks, so that's pretty good.
#BORG VS DUPLICACY PASSWORD#
I added public key authentication through SSH, while restricting password based authentication to LAN networks only, in the /etc/ssh/sshd_config: PasswordAuthentication no I had to open a port on my parents router for this.
#BORG VS DUPLICACY UPDATE#
Then I tried another option: I set up a Dynamic DNS entry on a subdomain, with ddclient on the Raspberry Pi to update the IP address regularly. At first I thought I would set up a reverse SSH tunnel from the Raspberry Pi to my NAS, but I couldn't get autossh to work with systemd. The address usually changes only if the router is restarted, but it can still cause issues. It sits at my parent's home, which has a dynamic IP address. So I took one of the Pis, set it up at my parents place and after some fiddling, it works. Then it finally dawned on me: I have two Raspberry Pi 3s at home that are just collecting dust.
And Syncthing turned out to be finicky and sometimes didn't sync. Often the PC would not be turned on for days, so I couldn't even do the backups without asking them to turn it on. The PC ran Windows, I had trouble getting SSH to work reliably, I would often had to fix stuff through Teamviewer. Unfortunately, it didn't prove to be a very reliable solution. This was supposed to be my offline backup. More than a year ago I described how I used Syncthing to backup folders from my NAS to an external harddrive attached to my parents PC.
0 kommentar(er)
