Skip to content

Seamoth backup to Leviathon (rsync interim)

Status

Active on Seamoth (Ubuntu 26.04) until Synology Active Backup for Business supports 26.04.

Why

ABB agent targets 24.04 on Prawn; Seamoth on 26.04 uses scheduled rsync over SSH to the seamoth-backup share on Leviathon. See projects/Homelab-Mac-Mini-Hosts.

Leviathon

  • Shared folder seamoth-backup (backup lands under /volume1/seamoth-backup/ — e.g. docker/, etc/ at share root).
  • DSM user subarctic (or your backup user): read/write on the share; rsync service enabled (Control Panel → File Services → rsync).
  • SSH key in that user’s authorized_keys for /root/.ssh/seamoth_backup_ed25519 on Seamoth.
  • Do not enable “rsync account” (unencrypted daemon) for this workflow — backups use SSH + rsync.

Seamoth

Piece Path / name
Script /usr/local/bin/seamoth-backup-to-leviathon.sh
Timer seamoth-backup.timer → seamoth-backup.service
SSH key /root/.ssh/seamoth_backup_ed25519

What is backed up: /home/kiefermenard/docker/, /etc/, plus copies of the backup script and systemd units under host/ on the share when present.

Excludes (typical): cache/transcode/temp paths inside docker trees (per script).

Verify

sudo systemctl status seamoth-backup.timer
sudo systemctl start seamoth-backup.service
ssh [email protected] 'du -sh /volume1/seamoth-backup/docker /volume1/seamoth-backup/etc'

Restore (outline)

Reinstall Ubuntu → restore docker and /etc from the share → remount NFS /mnt/media → docker compose up -d per stack. Not a one-click bare-metal image like ABB.