Can cPanel users restore and download their own backups?
Yes. The BackupWall cPanel plugin gives each account owner a BackupWall tile under Files in the Jupiter theme, where they list their own backups, restore files, databases, email and DNS zones, and download backups. They can only ever act on their own account.
What users can do
In cPanel, Files → BackupWall opens the account owner's self-service pages: My backups, My restores and Downloads. Users can:
- List their own backup points.
- Restore Everything, Files, Databases, Email or DNS zones. End-user restores always write into the user's own account, and every overwrite takes a safety copy first.
- Download a backup as a
.tarfile (see below).
Download a backup
- In My backups, choose Download on a backup.
- Choose Files, Files + Databases or Databases only.
- The server builds the archive in the background. Open the Downloads page and wait until the status is Ready.
- Choose Download.
The result is an uncompressed .tar file that never includes mail. It is kept for 48 hours. On cPanel an interrupted download can normally be resumed, provided the /backupwall-download Apache proxy is in place. The link works until its 6-hour token expires, the file's 48-hour limit passes, the download is deleted, an administrator uses "revoke all links", or the admin password changes.
How users are kept apart
The plugin runs as the account owner and reaches BackupWall through cPanel's own user-to-root channel, which takes the account name from the authenticated cPanel session. A user cannot ask for another account's data.
Enable the plugin for users
- Install the WHM plugin, then the cPanel plugin. See Install the panel plugins.
- If the tile is missing for a user, open WHM → Feature Manager and make sure the feature
backupwallis on in that user's feature list. The installer registers it as available by default.
The cPanel plugin never shows the licence banner. Restores and downloads work in every licence state.
Limits
- Jupiter theme only.
- Downloads never include mail.
- A MongoDB job has no self-service restore.
- Restore always overwrites the live account; there is no dry run.