summaryrefslogtreecommitdiff
path: root/gemfeed
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2024-11-17 10:14:54 +0200
committerPaul Buetow <paul@buetow.org>2024-11-17 10:14:54 +0200
commitdf122c0a5baa1ee96859aea05035e56ef06d8641 (patch)
tree5788c7abfcab691f4e8e89423f5ce13b4f9fd3e6 /gemfeed
parent2ce3cbf2db018108f75faadef4967692c5a3b965 (diff)
Update content for md
Diffstat (limited to 'gemfeed')
-rw-r--r--gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md
index 00257786..581e730c 100644
--- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md
+++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.md
@@ -106,6 +106,8 @@ Let's face it, backups are non-negotiable.
On the HAST master node, incremental and encrypted ZFS snapshots are created daily and automatically backed up to AWS S3 Glacier Deep Archive via CRON. I have a bunch of scripts already available, which I currently use for a similar purpose on my FreeBSD Home NAS server (an old ThinkPad T440 with an external USB drive enclosure, which I will eventually retire when the HAST setup is ready). I will copy them and slightly modify them to fit the purpose.
+There's also `zfstools` in the ports, which helps set up an automatic snapshot regime:
+
[https://www.freshports.org/sysutils/zfstools](https://www.freshports.org/sysutils/zfstools)
The backup scripts also perform some zpool scrubbing now and then. A scrub once in a while keeps the trouble away.