Backup Scripts Fail Due to Permission and Path Issues

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Backups report success in scheduler but archives are missing or incomplete.

Environment & Reproduction

Incorrect run user, missing execute permissions, relative paths, or failed mount targets.

Root Cause Analysis

Run the script with set -x under the same user as cron/service context.

Quick Triage

Correct ownership and permissions, then rerun backup with explicit absolute paths.

Step-by-Step Diagnosis

Use su -m -c ‘/path/backup.sh’ and verify output files and exit status.

Solution – Primary Fix

Review script config, cron entries, and destination mount options in /etc/fstab.

Solution – Alternative Approaches

Harden script error handling, validate destination free space, and test restore workflow.

Verification & Acceptance Criteria

Confirm new backup artifacts exist and checksum/restore tests pass.

Rollback Plan

Automate post-backup verification and alert on missing artifacts.

Prevention & Hardening

Re-enable prior backup routine while fixing the updated script.

Related Errors & Cross-Refs

Escalate if restore tests fail or backup destination integrity is in question.

Related tutorial: View the step-by-step tutorial for freebsd-15.

View all freebsd-15 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

chmod +x /path/backup.sh; chown : /path/backup.sh; df -h; zfs snapshot /@backup