I set up Restic or Borgbackup with encrypted, deduplicated backups to AWS S3 or Backblaze B2 — including scheduling, retention policies, restore testing, and failure alerting. Backups you haven't tested aren't backups; every engagement includes a verified restore.
Restic provides client-side encryption (AES-256), deduplication across snapshots, fast incremental backups, and point-in-time restore from any snapshot. I configure: cron schedule (daily/weekly); retention policy (keep N daily, M weekly, X monthly snapshots); repository initialization on your chosen remote; encryption key management documentation; and a Healthchecks.io ping or similar dead man's switch so you know immediately when a backup fails.
For database backup I add pre-backup dump hooks for PostgreSQL and MySQL — ensuring consistent, restorable database snapshots that are included in the encrypted repository.
Multi-server setups come with a centralized backup monitoring dashboard. Share your server OS, what needs backing up, backup destination, retention requirements, and alerting destination.