Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

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, while SingleStore 9.0 is recommended for production workloads.

Back Up and Restore Data

You can make a full backup or an incremental backup of a database. When you make a backup, you can target local file systems (only for full backups), network file systems, Azure, Google Cloud Storage, S3, and S3 Compatible Storage.

For backup destinations other than the local filesystem, all leaves must have access to write to the target destination.

Note

This topic applies to database backups made using the BACKUP DATABASE command or using the SingleStore Toolbox sdb-admin create-backup command.

Incremental backups cannot be made on unlimited storage databases.

Unlimited storage databases can be restored (attached) to any point in time using PITR, which is not discussed in this topic. See Local and Unlimited Database Storage Concepts for information on PITR.

Warning

SingleStore does not support restoring database backups from a newer version of SingleStore into an older version.

On account of how logs are now captured in SingleStore versions 8.9.19 and later, the following are not supported:

  • Downgrading from SingleStore versions 8.9.19 and later to SingleStore versions 8.9.18 and earlier

  • Restoring backups from SingleStore versions 8.9.19 and later to SingleStore versions 8.9.18 and earlier

Release 6.8 and earlier backups cannot be restored from release 7.8.

Note

When you restore a database from a backup , any pipelines included in that backup are also created in the restored database. These pipelines start automatically and immediately start consuming cluster resources, which can affect performance due to the additional pipelines.

You should review the pipelines in the restored database and stop or remove any pipelines that are not needed.

Databases on a secondary cluster to which the primary database is being replicated cannot be backed up with the BACKUP DATABASE command.

In this section

Last modified:

Was this article helpful?

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In