summaryrefslogtreecommitdiff
path: root/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2021-12-28 21:17:57 +0000
committerPaul Buetow <paul@buetow.org>2021-12-28 21:17:57 +0000
commit805a516f18222504612a90ff5e4b5630d1047fb1 (patch)
tree664fcf726611fef5357717a17df45f0e5921b1c8 /gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
parentb2009191699a2a31b38fd2baea9ff2cabc38efdc (diff)
Publishing new version
Diffstat (limited to 'gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html')
-rw-r--r--gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html1
1 files changed, 1 insertions, 0 deletions
diff --git a/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html b/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
index ec1183a9..8d50d627 100644
--- a/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
+++ b/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
@@ -29,5 +29,6 @@
<p>Furthermore, I added scrubbing ("zpool scrub...") to the script. It ensures that the file system is consistent and that there are no bad blocks on the disk and the file system. To increase the reliability, I also run a "zfs set copies=2 zroot". That setting is also synchronized to the offsite ZFS pool. ZFS stores every data block to disk twice now. Yes, it consumes twice as much disk space, making it better fault-tolerant against hardware errors (e.g. only individual disk sectors going bad). </p>
<p>E-Mail me your thoughts at comments@mx.buetow.org!</p>
<a class="textlink" href="../">Go back to the main site</a><br />
+<p class="quote"><i>Generated with <a href="https://codeberg.org/snonux/gemtexter">Gemtexter</a>, served by <a href="https://www.OpenBSD.org">OpenBSD</a>/<a href="https://man.openbsd.org/httpd.8">httpd(8)</a></i></p>
</body>
</html>