![]() ![]() Relica’s installation is simplicity itself! For Mac OS, it’s as straightforward as downloading a. Once set up, you really don’t need to think about it unless you need to do a restore. All backups made with Relica can be restored using either Relica or plain restic. Also, the Relica software apparently updates itself when the time comes, with no user involvement needed. These would seem trivial to anyone versed in some bash scripting and systemd/supervisord knowledge (whip up some scripts!) but there are nuances that could be overlooked, with potentially damaging results. The backup has all of restic’s features and Relica additionally takes care of matters like scheduling the backups, missed schedules, reports, and backup pruning and maintenance. The replication to additional clouds is managed by Relica’s server side infrastructure. For the latter, your data will be transmitted from your computer only once. If you choose Relica’s cloud storage, it is a) Cheaper than most other cloud storage providers and b) Your backed up data can be transparently replicated across up to five independent cloud providers. That destination can be an external harddisk plugged into your computer, a NAS on your network, your own cloud storage provider, Relica’s cloud storage, or even your friends computer – or all or any of those mixed and matched as you please. Relica is a program that, at its essence, backs up the folders you specify on your computer to a destination. Additionally, it supplies everything I was missing in restic, and more! Relica Relica does not advertise itself as a front-end for restic – and it is admittedly a bit simplistic to describe it as a restic GUI – but the fact of the matter is that it does use restic under the hood. ![]() So I looked for comprehensive, cross-platform GUI wrappers for restic, but those don’t seem to exist. However, I did not want to get into writing custom scripts, scheduling script execution, managing situations where my laptops may be sleeping so scripts did not execute, pruning and maintaining backups, finding ways to get notified when the scripts ran successfully and when they failed etc. I chose to go with restic because of the variety of cloud storage backends it supports. Of these, borg and restic seemed the most promising contenders in terms of maturity, community, and actual usage – based roughly on the amount of articles, blog posts, reddit threads, and other forums.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |