From 3c72f1d2ae6d00c8c3dfea4c3b6c63c0e9cd9e51 Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Tue, 3 Feb 2026 14:21:42 -0800 Subject: [PATCH] Add Backup section to sifaka card Clarifies that sifaka is the backup TARGET, not source. Notes RAID 5 for current protection, offsite planned for future. Co-Authored-By: Claude Opus 4.5 --- docs/reference/storage/sifaka.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/reference/storage/sifaka.md b/docs/reference/storage/sifaka.md index 73998d5..1481b88 100644 --- a/docs/reference/storage/sifaka.md +++ b/docs/reference/storage/sifaka.md @@ -43,6 +43,12 @@ Node exporter running in Docker container, scraped by [[services/prometheus|Prom - Tag: `tag:nas` - ACL: `tag:homelab` can access for backups +## Backup + +Sifaka is the **target** for [[operations/backup|backups]], not a backup source. [[services/borgmatic|Borgmatic]] sends backups TO sifaka, not OF sifaka. + +Data protection for sifaka itself currently relies on the Synology RAID 5 configuration, which provides single-disk fault tolerance. Future plans include offsite duplication for additional resiliency. + ## Related - [[storage/backups|Backups]] - Backup policy