Skip to content
Security Verified service · 5.0 rating

WHMCS Backup & Disaster Recovery

Encrypted offsite WHMCS backups of database, files and encryption key, a real test restore and a recovery runbook.

Fixed-price quote in 24h 14-day correction guarantee 1 year free support

WHMCS backup and disaster recovery setup gives your billing system copies you can actually restore from: the database, the files and the encryption key, sent off the server every day, encrypted, and proven by a real test restore. Setup for one install costs from $199 and comes with a written runbook for rebuilding WHMCS on a new server. It suits any self-hosted install where the honest answer to "when did we last restore a backup?" is "never".

Why the built-in backup is not enough by itself

WHMCS has automated backups at Configuration > System Settings > Database Backups, with three options: SFTP/FTP, cPanel Backups and Daily Email Backups. They are a useful extra layer, but each has limits:

  • The SFTP/FTP and email options cover the database only, not your theme, hooks, modules or attachments.
  • WHMCS says the email option may fail on large databases because of memory and time limits, and does not recommend it for large installs.
  • The cPanel option only asks cPanel to start a full backup; WHMCS will not detect completion, move the file or notify you.
  • The export runs during the daily cron and can be heavy on CPU, memory and disk at a busy hour.

Most importantly, none of them protect the one file a restore cannot do without.

The file that decides whether a restore works

configuration.php holds your install's encryption hash. WHMCS stores passwords, security answers and card data encrypted with it, and its restore documentation is blunt: without the original file, that data stays encrypted for good. We back it up with the rest, and also store a copy separately under restricted access, for example in your password manager, so losing the server never means losing the key.

What gets backed up

  • The database, exported with mysqldump using a single consistent transaction so InnoDB tables are not locked, or with mariadb-backup or Percona XtraBackup when the database is large
  • The WHMCS directory, including your custom theme, order forms, hooks, addons, modules and language overrides
  • Folders moved outside the web root, such as attachments, downloads and the crons directory
  • Remote storage, if Storage Settings already put attachments or downloads in an Amazon S3 bucket

Where the copies go

Backups are encrypted with restic or BorgBackup before they leave the server, then sent to storage with a different provider from the one hosting WHMCS: Amazon S3, Backblaze B2, Wasabi or a Hetzner Storage Box, for example. On cPanel servers that already run JetBackup, we can use it for the file side. Where the storage supports it, we turn on object lock or append-only access, so someone who breaks into the WHMCS server cannot delete the backups too. You choose how many daily, weekly and monthly copies to keep, and a failed or missing backup sends an alert instead of failing quietly.

Proving the restore

We restore the latest backup onto a separate test server, with the cron off and outgoing mail blocked so no customer receives anything. Then we log in to the admin area, open a record that holds encrypted data to confirm decryption works, and place a test order. We note how long the restore took, so the runbook can state it honestly.

The disaster recovery runbook

A short document written for a stressful day, covering:

  1. Who decides to invoke it, and how to reach them.
  2. Where the backups and the encryption key are, and who can access each.
  3. What a replacement server needs: Linux, Apache or LiteSpeed, PHP at the level your release expects (8.1 minimum on 8.13, 8.2 minimum on 9.x) and an ionCube Loader to match.
  4. The restore steps for the database, files and configuration.php.
  5. Reissuing the WHMCS license for the new server through WHMCS or your license reseller.
  6. DNS changes, the cron job, email piping forwarders and gateway callback checks.
  7. The test order and checks that confirm billing is back.

It also records two numbers in plain words: how much recent data you can afford to lose, and how long billing can be down.

What we need from you

  • SSH access, with root preferred, or control panel access
  • A storage account in your name, or permission to open one
  • A WHMCS admin login
  • A test server for the restore, or approval for us to use a temporary one at cost

Prices

ScopePrice
One install: encrypted offsite backups, alerts, one test restore and the runbookFrom $199
Several installs, or a separate database serverFixed quote
Further test restores or a recovery drill with your team$65/hour
StorageBilled by your storage provider

Not included

  • Backups of your customers' hosting accounts on the servers you sell from
  • Recovering an install that has already been compromised, which is hacked WHMCS cleanup
  • Monthly restore checks, which our monthly maintenance plan includes

For detection between backups, the WHMCS Security module watches for file changes, and a security audit checks the rest of the setup. On the call we begin with one question: if the WHMCS server disappeared tonight, where would you restore from?

What's included

Every WHMCS Backup & Disaster Recovery engagement ships with these.

  • Review of the built-in WHMCS database backup settings
  • Consistent database exports with mysqldump, mariadb-backup or XtraBackup
  • WHMCS files, custom theme, hooks, modules and moved folders included
  • configuration.php and encryption hash stored separately under restricted access
  • Encryption with restic or BorgBackup before upload
  • Offsite storage on S3, Backblaze B2, Wasabi or a Hetzner Storage Box
  • Object lock or append-only access where the storage supports it
  • Alerts when a backup fails or does not run
  • Test restore on a separate server with cron and mail disabled
  • Written disaster recovery runbook, including license reissue steps

Business outcomes

What hosting operators report after delivery.

  • You know, rather than hope, that a backup restores
  • Encrypted customer data stays readable after a restore because the key is safe
  • An intruder on the WHMCS server cannot wipe the backups as well
  • Anyone on your team can follow the runbook on a bad day
  • Backups stop competing with the daily cron for server resources

Ready to talk about WHMCS Backup & Disaster Recovery?

Quick scoping call, fixed-price quote within 24 hours, no commitment.

Related services

Other WHMCS work hosting operators ask us about.