diff options
| author | Paul Buetow <git@mx.buetow.org> | 2021-05-02 16:41:28 +0100 |
|---|---|---|
| committer | Paul Buetow <git@mx.buetow.org> | 2021-05-21 05:11:04 +0100 |
| commit | 7bcd33dba38209753e441217536cc9bde1929f9a (patch) | |
| tree | 195257c723124e41539d6222a11b6184b431ed0a /content/gemtext/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.gmi | |
| parent | 8c2fce29739692816ad67eaa315e30db9316c129 (diff) | |
Use an AI to correct some of the grammar
Diffstat (limited to 'content/gemtext/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.gmi')
| -rw-r--r-- | content/gemtext/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.gmi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/content/gemtext/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.gmi b/content/gemtext/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.gmi index e1b0d5f5..b91e7727 100644 --- a/content/gemtext/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.gmi +++ b/content/gemtext/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.gmi @@ -23,8 +23,8 @@ I enhanced the procedure a bit. From now on I am having two external 2TB USB hard drives. Both are setup exactly the same way. To decrease the probability that they will not fail at about the same time both drives are of different brands. One drive is kept at the secret location. The other one is kept at home right next to my HP MicroServer. -Whenever I am updating offsite backup I am doing it to the drive which is kept locally. Afterwards I bring it to the secret location and swap the drives and bring the other one back home. This ensures that I will always have an offiste backup available at a different location than my home - even while updating one copy of it. +Whenever I am updating offsite backup, I am doing it to the drive which is kept locally. Afterwards I bring it to the secret location and swap the drives and bring the other one back home. This ensures that I will always have an offiste backup available at a different location than my home - even while updating one copy of it. 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 but it makes it better fault tolerant against hardware errors (e.g. only individual disk sectors going bad). -E-Mail me your throughts at comments@mx.buetow.org! +E-Mail me your thoughts at comments@mx.buetow.org! |