Skip to content

JetBackup destinations — local plus offsite, the right way

How to configure JetBackup with both a local destination for fast restores and an offsite destination for disaster recovery, without doubling your backup window.

Local-only JetBackup configurations are fast to restore from but useless if the server is unrecoverable. Offsite-only configurations protect against site loss but make a 50 GB account restore an hour-long affair. The defensible answer is both — and the trick is to configure them so the offsite stage starts from the local copy, not from a fresh scan of /home.

What’s happening

JetBackup 5 supports multiple destinations per backup job, executed in order. A typical layout: destination 1 is a local filesystem path on a separate volume (or an iSCSI LUN), destination 2 is an offsite object store (S3 / B2 / Wasabi / SFTP target). When destinations are chained, the second can copy from the local result rather than re-reading from /home, halving the IO impact.

How to verify

List current jobs and destinations:

jetbackup5api -F getBackupJobs
jetbackup5api -F getDestinations
jetbackup5api -F getDestination -D '{"_id":"<dest-id>"}'
df -h | grep -i backup

Confirm each destination’s last-success timestamp; an offsite destination that hasn’t succeeded in 14 days is effectively missing. Also confirm the offsite destination’s free space — running out of room on the remote side is the most common silent failure mode.

The fix

  1. Create the local destination first. A separate volume (not a path inside /home) — losing /home should not lose the backup. Mount under /backup/jb with the same filesystem options as /home.
  2. Create the offsite destination second. For S3/B2/Wasabi, use a bucket dedicated to this server, with versioning enabled and a lifecycle policy that matches your retention. SFTP to a Borg-style append-only target is also acceptable.
  3. In the backup job, list local first and offsite second. JetBackup’s “Mirror destination” option lets the second destination copy from the first — turn it on.
  4. Encrypt the offsite copy at rest. JetBackup supports GPG encryption per destination; configure it with a key whose private side is escrowed, not just stored on the cPanel server.
  5. Test restore from both. A backup you have never restored is a theoretical backup; pick one account quarterly and restore to a staging server.

Stack Harbor configures and supervises JetBackup as part of environment management for cPanel servers.