eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/reference/storage/sifaka.md
Erich Blume 3c72f1d2ae 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 <noreply@anthropic.com>
2026-02-03 14:21:42 -08:00

1.9 KiB
Raw Blame History

title tags
Sifaka NAS
storage

Sifaka NAS

Synology NAS providing network storage and backup target.

Quick Reference

Property Value
Dashboard https://nas.ops.eblu.me
Model Synology
Storage 10.9TB RAID 5
Role Backup target, media storage

Network Shares

Share Path Purpose Consumers
backups /volume1/backups Borg backup repository [[services/borgmatic
torrents /volume1/torrents ZIM downloads [[services/kiwix
music /volume1/music Music library [[services/navidrome
allisonflix /volume1/allisonflix Video library [[services/jellyfin
photos /volume1/photos Photo library [[services/immich

NFS Exports

Export Allowed Clients Purpose
/volume1/torrents 192.168.1.0/24, 100.64.0.0/10 k8s pods via Docker NAT
/volume1/music 192.168.1.0/24, 100.64.0.0/10 k8s pods via Docker NAT

Monitoring

Node exporter running in Docker container, scraped by services/prometheus at sifaka:9100.

Tailscale

  • Tag: tag:nas
  • ACL: tag:homelab can access for backups

Backup

Sifaka is the target for operations/backup, not a backup source. services/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