Bastian de Byl
0ab423ca55
The data-only rsync left no way to restore a working instance: mysql/ and config/ were never backed up, so a recovery would have files but no shares, users or metadata. Dump the database before syncing files (a DB older than the files is repairable with occ files:scan; a newer one references blobs that never made it into the backup) and ship config/ alongside it. Capture the --chmod=Du=rwx,Dgo=rx flag that had been hand-added to the deployed skudak-cloud script. It was outside git, so every deploy silently reverted it. It now lives in backup_rsync_extra_args. Add OnFailure= alerting. The units failed silently before, which is how an iDrive sync failure sat unnoticed since May. msmtp rather than the esmtp already installed: the OpenSRS relay is port 465 (implicit TLS) and libesmtp only speaks STARTTLS. Exclude nextcloud.log* from the sync and cap log_rotate_size. skudak-cloud was running at loglevel 0 and had written a 64 GB log that was being rsynced and pushed to S3; set it to 2 to match the home instance. Stagger the timers (04:00 / 04:30) so both finish before the 05:00 TrueNAS snapshot task, and bound TimeoutStartSec so a wedged rsync cannot leave the unit activating forever and skip every subsequent trigger. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
15 lines
471 B
Django/Jinja
15 lines
471 B
Django/Jinja
[Unit]
|
|
Description=Nextcloud {{ instance_name }} backup to TrueNAS
|
|
After=network-online.target
|
|
Wants=network-online.target
|
|
OnFailure=nextcloud-backup-failed@%n.service
|
|
|
|
[Service]
|
|
Type=oneshot
|
|
ExecStart={{ script_path }}
|
|
# Type=oneshot disables the start timeout by default, so a wedged rsync would
|
|
# leave the unit "activating" forever and every subsequent daily trigger would
|
|
# be silently skipped. Bound it.
|
|
TimeoutStartSec={{ backup_timeout | default('4h') }}
|
|
Nice=10
|