SingleStore DB

Backup and Restore on Specific Systems
Backup and Restore on NFS (Network File System)

SingleStore DB makes BACKUP DATABASE and RESTORE DATABASE easy to use with a Network File System (NFS) by naming the .backup files so that that no two leaves will attempt to write to the same file even if they are all writing to the same NFS directory.

To back up SingleStore DB with NFS: - Ensure that the same NFS share is mounted in the same directory on all leaves (e.g. /mnt/backup_nfs/ - When running BACKUP DATABASE, simply select a backup_path that points to a directory on that NFS share (e.g. BACKUP DATABASE memsql_demo to '/mnt/backup_nfs/backup_2016_05_04/')

Backup and Restore without NFS

If your cluster is not on NFS and you are restoring a cluster with a different configuration or on different hardware than the original, you must manually distribute partitions across the cluster before running RESTORE DATABASE. If the cluster has redundancy level greater than one, you must group leaf nodes into replication pairs. Paired nodes must have the same set of partition backups in their local backup directories (specified by backup_path). SingleStore DB will automatically choose master and replica partitions when you run RESTORE DATABASE on the master aggregator.

Backup and Restore on S3 and Azure

Backup and restore can also specify an S3 bucket or Azure container. In this case, all the backup files across all the leaves (one per partition as described above) are put directly into the S3 bucket or Azure container. When restore is called, SingleStore DB will distribute the backup files appropriately and restore the data (similar to how restore from an NFS drive works).

Backup and Restore between S3 and a local system

You can restore a full backup taken in S3 to your local system and vice versa as discussed here.