Skip to content

Database Backups

Database Backups let you create, restore, and delete on-demand dumps of a database directly from the client panel. Like Filesystem Backups, they are created by the bolt-agent on the server and require no external backup software.

Database Backups

Overview

Opened from the Databases page - this is not a standalone sidebar item. Open /client/databases (Databases → Databases), click Edit next to a database, and scroll to the Backups section of the dialog.

Each backup is a compressed SQL dump (.sql.gz) of a single database, produced with mysqldump. The dump contains the table structure and data along with stored routines, triggers, and events. The section shows how many backups exist for the database and lists them in a table:

ColumnDescription
FilenameDump name in the form <database>-<timestamp>.sql.gz
SizeDump size
Created AtDate and time the backup was created
ActionsRestore and Delete

Backups are stored in the backups folder of your home directory on the server, next to filesystem backup archives, so they count toward your disk quota. The Disk Usage page reports them under the Backups category.

Create a backup

  1. Open Databases → Databases (/client/databases) and click Edit next to the database.
  2. In the Backups section, click Create Backup and confirm.

The panel waits while the server dumps the database; for large databases this can take a while. When it finishes, a Backup Created notification appears and the new dump shows up in the list.

Download a backup

The backup list has no download action. To download a dump, open the File Manager, enter the backups folder in your home directory, select the .sql.gz file, and use Download.

Restore a backup

  1. In the Backups section, click Restore next to the dump and confirm.
  2. The server first dumps the current state of the database as a safety copy named <database>-before-restore-<timestamp>.sql.gz, then imports the backup into the database.

The safety copy appears in the backup list afterwards, so you can return to the pre-restore state if needed.

Warning: Restoring overwrites the current contents of the database with the contents of the dump. Changes made after the backup was created are removed (they remain available in the before-restore safety copy).

Delete a backup

Click Delete next to the dump and confirm. The file is removed from the server and the freed space no longer counts toward your quota.

Limits and availability

  • Backups are created on demand; there is no scheduling option in the client panel. Ask your administrator about server-side backup schedules or JetBackup.
  • Each hosting account can only see and manage its own backups.
  • The feature is available where the administrator's hosting plan enables the Databases pages.

Database Backups and JetBackup

Database and Filesystem Backups are AdminBolt's built-in, per-account backup tools. JetBackup is a separate, optional module with its own interface that adds scheduled, incremental, multi-destination backups. Both can coexist on one server; if JetBackup is installed, clients reach it through the JetBackup launcher.