CPanelBackup helps you generate and restore CPanel backups. It was initially written as Bacula pre-job-run hook, but was quickly expanded to do more.

Usage

Use the CLI script provided, run cpb_runner --help to see all the options.

Now let’s go through the backup process.

Backing up stuff

• Bacula runs a job.
  • Bacula invokes pre-run hook on the client (cpb_runner)
  • Bacula backups /home & /backups/cpanelbackup/accounts dirs
  • /backups/cpanelbackup/accounts is deleted on successful job completion

The hook is invoked with the following options:

cpb_runner --action backup

The script now backups all cpanel accounts into /backups/cpanelbackup/accounts dir, where CPanel pkgacct ’s *.tar files are placed.

Restoring

• Something initiates backup restoral
  • Backup files are placed into:
    • CPanel backups (tar): /backups/cpanelbackup/backups/cpanelbackup/accounts
    • Home dir backups (plain): /backups/cpanelbackup/home
• User runs cpb_runner script

The script could be run as following:

cpb_runner --action restore --users theusername  --home-rsync --delete-source --smart-id

This will ask cpb to move theusername.tar file from /backups/cpanelbackup/backups/cpanelbackup/accounts/ to /backups/cpanelbackup/accounts/ dir, restore from it, rsync home dir from /backups/cpanelbackup/home/theusername/ to /home/theusername/ and delete all backup data for that user afterwards in case of success.

Notes

Logging

Log file is written into /var/log/cp-backup-runner.log by default.

Options

—smart-id

Sets proper ownership on files below user homedir after rsync, but only in case public_html has incorrect uid/gid. TODO: check how ACLs would behave.

—process-sql-grants

Stores mysql user access information (AKA grant data) into mysql.sql file and incorporates it into final tar archive. It mimics what pkgacct would’ve done, but skips dumping table data. Same applies during restoral – it tries to exec mysql statements from that file if it’s present.

@see Other various funny options obtainable via —help.

Misc

CPanel is a big nasty miserable mess in regards to general architecture and software design. It appears like tons of monkeys from different zoos were lured into one big purple cave where they were given a task of “getting API and CLI tools done immediately” without much thinking. ¹ This could probably be the reason for all the workarounds we have to implement here.

¹ Author’s personal opinion