Sign inTry Free

Backup Data

On this page

Note

The process described below of raising Support tickets will remain valid till March 31, 2025. After that, it will be replaced with Continuous Backups

Only full backups can be created. Incremental backups are not available.

In SingleStore Helios backups cannot be created to local file systems.

Backups are not run within the workspaces themselves but on the Master Aggregator (MA) of the corresponding underlying cluster.

Backups happen for workspaces that have databases attached in R/W (read and write) mode. Workspaces with databases attached in R/O (read only) mode do not get backed up.

When you suspend a workspace you suspend any operations against it. Hence if you suspend a workspace around the time a backup is scheduled, then that day's backup gets skipped.

In addition to the scheduled backups, you can also create your own backups through SQL from a MySQL client. You can back up into your AWS S3 bucket, your Azure Blob storage, or GCS and then restore as needed.

Backup Schedule

SingleStore Helios automatically backs up data on a default schedule at 2 am daily in the local time for the deployment region. The data is stored in AWS S3.

Data Retention Period

The retention period is seven days. You can always request a restore from a particular day in the last seven days.

Altering the Scheduled Time for Your Backup

You can raise a Support ticket to alter the scheduled time for your backup.

In the support ticket you should provide the following information:

  • The name of the database for which you want to alter the scheduled backup time.

  • The name of the workspace on which the database is running.

  • The new scheduled backup time you want to be set for your database. Ensure you specify the time format clearly (12-hour or 24-hour) and include the time zone.

The support team will provide an ETA when they receive the support ticket and subsequently update the ticket with the confirmation of the changes made.

Last modified: January 24, 2025

Was this article helpful?

On this page

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