pub fn execute_backup_run(plan: &BackupRunPlan) -> Result<()>Expand description
Run a planned backup end-to-end.
online services (a live dump, or safe-to-copy flat data) run only their
own hooks around restic: pre_backup -> restic -> post_backup. The post
hook runs even when restic fails (it usually cleans up a dump), but its own
failure never masks restic’s error.
Cold services (the default) get the full lifecycle ryra derives from their
units + paths: stop the stack, make the data readable, optional pre_backup
prep, restic, then bring the service back (a post_backup hook if present,
else start the primary unit). The service is always brought back up, even
when restic fails, so a failed backup never leaves it down.