Important
Self-managed SingleStore will soon transition from version 9.1 RC to version 10. This new semantic versioning scheme will provide SingleStore with finer control over engine and feature releases that were not possible with the current versioning scheme.
In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10 prior to its general availability. Ahead of this transition, SingleStore 9.0 is recommended for production workloads, which can later be upgraded to SingleStore 10.
Full Backups
On this page
A full backup contains a complete copy of a database.
Make a Full Backup
To make a full backup, run the BACKUP DATABASE command.test_ and stores it in the /test_ directory.
BACKUP DATABASE test_db to "/test_db_backups_week_1";
BACKUP DATABASE outputs one row containing the BACKUP_ column.
You can view the history all of the backups made in the cluster by querying information_.
SELECT backup_id, incr_backup_id, database_name, start_timestampFROM information_schema.mv_backup_historyORDER BY backup_id;
+-----------+----------------+-----------------+---------------------+
| backup_id | incr_backup_id | database_name | start_timestamp |
+-----------+----------------+-----------------+---------------------+
| 1 | NULL | test_db | 2019-08-04 00:00:00 |
+-----------+----------------+-----------------+---------------------+You cannot save a full backup to a directory that already contains a full backup.
Restore a Full Backup
Note
Release 6.
To restore a full backup, use the RESTORE DATABASE command and specify the database name along with the directory where the backup is stored.test_ from the test_ directory.
RESTORE DATABASE 'test_db' FROM "/test_db_backups_week_1";
Last modified: