Backup and Restore on Specific Systems
On this page
BACKUP DATABASE and
RESTORE DATABASE easy to use with a Network File System (NFS) by naming the
. files so that that no two leaf nodes will attempt to write to the same file even if they are all writing to the same NFS directory.
To back up SingleStore with NFS: - Ensure that the same NFS share is mounted in the same directory on the master aggregator and all the leaf nodes (e.
BACKUP DATABASE, simply select a
backup_ that points to a directory on that NFS share (e.
BACKUP DATABASE memsql_)
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
Backup and restore works best if the topology of the source and target clusters are the same.
The same directory path must exist on all the leaf nodes and the master aggregator for both backup and restore.
If you are running HA, make sure the nodes are paired.
RESTORE DATABASE on the master aggregator.
Backup and restore can specify an S3 bucket or Azure container or Google Cloud Storage (GCS).
When taking a database backup to an Azure bucket [blob container] ensure that your service account has all required privileges, including the
blob feed privilege.
Last modified: April 24, 2021