DB Backup Manager

Create backup

You can create a backup directly in the database overview by clicking on the «Create backup» icon next to the respective database, or you can click on in the DB Backup Manager.

All backup dumps are compressed with GZIP and are located in your hosting's ~/backups/ directory. You can either download the backup files directly via SSH/SFTP/FTPS, or simply here via download link.

As a customer, you do not need to worry about regular backups! We already back up all data on our backup server on a daily basis and store a large number of past generations of MySQL databases in particular. Backup restores are carried out upon request for a small fee. This backup manager is rather intended for cases where you are making a major change to your website and would like to back up the current status of your database beforehand.

Backup restore

To restore a database backup dump, click on «Restore backup ...». A backup can be restored to the previous database (which the backup was created from) or to a different/new target database.

All tables in the target database are overwritten with the data from the selected backup.

Restore strategies:

• Regular Restore (default) – Run a regular restore of the full database backup dump. This will only DROP existing tables prior to restoring the data, if they are also present in the backup. Any other tables will be left untouched.
• Radical Restore – Run a radical restore of the full database backup dump. This will first DROP your complete database and then repopulate it from scratch. Like this, you will get a clean copy of the database as it was at the time of the backup. But this may be risky and cause some downtime while loading the data. If your backup dump cannot be restored for some reason, the database will be blanked out.

ATTENTION

Tables (including the contained data) that exist in the target database but not in the backup are not overwritten with «Regular Restore (standard)» strategy! It is therefore not advisable to import a backup into an existing database that previously contained tables from a completely different web application. Technically speaking, with this backup restore strategy, only a DROP TABLE is executed before each CREATE TABLE. No DROP DATABASE is executed!

If you want to be sure that the target database really just contains the data from the backup, please select «Radical restore» instead.