Restoring MySQL¶

When restoring MySQL, you select specific databases from a snapshot and then choose the method that best fits how you want to use the recovered data.

Available methods¶

Restore to disk as `.sql` files¶

Specify a restore path, and the system will export selected databases as .sql files.

Example:

If you set /tmp and restore database.sql, the file will be created as /tmp/database.sql.

Restore as archive¶

You can restore selected .sql files as an archive by setting the output path, filename, and format.

Supported formats:

tar
tar.gz
zip

Direct restore to a MySQL server¶

With this method, restore is executed directly into a MySQL instance. You need to provide:

username
password
server (host)
port

If the database already exists on the target server, it will be replaced with data from the backup. If it does not exist, it will be created.

Caution

Direct restore can modify or replace active production data. It is recommended to test first in a separate MySQL environment.

Best practices¶

Use a separate test instance before restoring in production.
Verify MySQL server version compatibility and charset/collation settings.
Validate critical tables and indexes after restore.
Review status and logs in Jobs.