http://golangnews.com Jobs, Code, Videos and News for Go hackers - everything about the go programming language Mon, 22 Jan 2018 17:34:00 +0000 <p>This is Part 4 of my series on building a <a href="https://restic.github.io/%22" style="color: rgb(0, 102, 0);">restic</a>-based system backup series. The rest of the articles can be found <a href="https://kula.tproa.net/lnt/computers/backups/restic-systems-backups/" style="color: rgb(0, 102, 0);">here</a>.</p> <h2>Replication</h2> <p>A goal from the start of this project has been replicating backup date to multiple locations. A long personal and professional history of dealing with backups leads me to the mantra that it isn't backed up until it's backed up to three different locations. Restic has several features which make this easy: backend storage (to a first approximation) is treated as append only — a blob, one stored, is never touched although may be deleted as part of expiring snapshots. Second, everything is encrypted, so you can feel as safe spreading your data to any number of cost-effective storage providers as you trust restic's encryption setup (which I generally trust).</p> 8 points posted by andythomas https://kula.tproa.net/lnt/computers/backups/restic-systems-backups/pt4.html 3128 Sat, 20 Jan 2018 11:35:00 +0000