Backup on NAS SSD via fritzbox

[danteffm]

Hi everyone,

today I would like to show you a small project around improving backups for an indi-allsky setup on a Raspberry Pi.
It started as a simple “this should really be backed up properly” exercise and evolved in two steps. Phase 1 covers the technical basics by backing up all critical configuration and database data. Phase 2 builds on that and adds a more opinionated approach to image backups and timelapses, focusing on keeping only nights that are actually worth keeping.

Phase 1 — Automatic indi-allsky Backup to External Drive (Fritz!Box NAS)

This is a small side project to improve the operational robustness of my indi-allsky setup.
The focus of Phase 1 was a reliable, fully automated backup of all critical system data.

https://allsky-rodgau.com/automatic-indi-allsky-backup-on-external-drive-fritzbox-nas-1653/

Task

The objective was to create a daily, unattended backup for an indi-allsky installation running on a Raspberry Pi. The backup should cover all relevant configuration and database components and be stored externally on an SSD connected to a Fritz!Box NAS.

Implementation

• Identified the critical indi-allsky components that need to be backed up, including the SQLite database, configuration files, and migrations.
• Connected and formatted an external SSD on the Fritz!Box and exposed it via SMB.
• Mounted the SMB share on the Raspberry Pi using CIFS with explicit mount options.
• Implemented a shell script that creates timestamped backups, verifies database integrity, applies retention rules, and sends email notifications only in case of failure.
• Scheduled the backup via cron for daily execution.

Hiccups and notes

• Fritz!Box SMB mounts require specific options such as noserverino to prevent file handle issues.
• Reliable email notifications require a properly configured SMTP client (e.g. msmtp).
• Image and video data are intentionally excluded in this phase and addressed in Phase 2.

---

Phase 2 — Quality-Aware Backup of Image Files

Phase 2 extends the backup strategy beyond system data and focuses on selectively backing up image data based on objective quality criteria rather than backing up everything.

https://allsky-rodgau.com/automatic-indi-allsky-backup-on-external-drive-fritzbox-nas-phase-2-files-1656/

Task

The goal was to back up indi-allsky image files and timelapses in a storage-efficient way by keeping only nights that provide meaningful astronomical value.

Implementation

• Used the indi-allsky database to assess night quality using metrics such as star counts and moon influence.
• Implemented logic to classify nights and selectively back up corresponding image directories.
• Generated manifest files explaining why a night was included in the backup.
• Added consistency checks comparing database entries with backed-up files.
• Integrated disk-usage-aware retention rules.
• Reused the existing cron-based execution model.

Hiccups and notes

• Defining meaningful quality thresholds required analysis of database and iteration.
• Image backups are significantly larger than database backups and required performance considerations.
• Manifest files proved essential for traceability and later debugging.