#BORG VS DUPLICACY PC#
But apparently something with the cronjob (not a real initd but systemd service cronjob thingy) went wrong and the PC of my parents did not get backed up for month without anyone realizing. After finally managing to do so, I thought I am all fine and settled. Even me using quite a lot of terminal in my daily work enabling Borg backup on all machines in my household and the cronjob for it was a tidies process. In order to enable this I want my backup system to give me easy access to different states of my file systemĪs I searched for a viable backup solution I stumbled upon Borg already about 2 years ago and thought it finally solves all my problems. My backup should help me in situation where I fucked up my files and give me the peace of mind to do faster experimenting. Sometimes it happens that I delete files from my work git directories or forget to commit. I don’t want to use the backup only for disaster recovery like my laptop breaking or going down in flames, but also for a daily “simon-fucked-up-his-files”-scenario. Differential backups for Time Machine like file version access With a closed source server I depend on the merchant not going away. The server-side being open source is a nice-to have for me as it guarantees that if my chosen provider is vanishing another could jump into that gap. To facilitate the client-side encryption and to give me confidence that the backup tool is not cheating on me, at least the client of the solution should be open source.
#BORG VS DUPLICACY HOW TO#
The requirement for a client side backup key comes with the new problem BackupInception: How to back up this backup-key? More on this at the end of this article. Only if my backups are encrypted on my machine before being transferred to the cloud storage I can assume (as long as the 5-eyes have no encryption breaking quantum-computers yet) no-one apart from me (not even the cloud provider) can access my data. Why would I have my laptops hard-drive encrypted, but my backup is stored in clear text in the cloud ?(yep looking at you iCloud Backups)
Storing all my backup data in a cloud storage comes with a negative privacy implication. Same for both devices being destroyed in a fire.
I figured, as long as the backup system doesn’t do its work on its own in the background it is of no use to me. They all lost important data at some point because of their last backup being too old.
#BORG VS DUPLICACY MANUAL#
And to be honest: I know no one in my circle for whom this manual strategy works. Like with New Year’s resolutions: After a short period I forget doing them or the time in between the single backups is too big to really call it an up-to-date backup. You might claim that your manual scheduled backup might be a good solution for you…for me it’s not. Some people go with the quote: “No backup, no mercy”, but I like to go even further “No automatic backup, no mercy”. RequirementsĪll the aforementioned solutions lacked either in one or the other of my following requirements. I tried various solutions, from gnomes Déjà Dup over various more or less maintained open source solutions up to manually file system backups with rsync. TLDR After years of searching around I finally found a Linux backup setup that fits my needs: Borg + Vorta + BorgBaseĪs long as I can think back, backing up my Linux system always was a problem for me.
0 kommentar(er)
