Online Point-in-Time Recovery (PITR)

Note

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

You can open a Support ticket, for an online PITR.

The support ticket you open should include the following information:

  • The name of the database for which you want to do online PITR.

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

  • The name of the workspace on which you want it restored.

  • The name you want for the new restored database.

The workspace must be in the same region.

The support team will provide an ETA when they receive your ticket. Once your restored database is ready, the support team will update the support ticket with details.

Support will copy an online database to a new database name, and the new database will have all the PITR history of the original. The database will be attached at the latest time available. The last few minutes of data may not be available in the copy. Then, you have to detach the new copy and re-attach it at whatever point in time you want.

When you find the data you need, you can, for example, copy it back to the original database using INSERT INTO … SELECT FROM… commands.

This allows you to recover accidentally removed or corrupted data into the original online database while keeping the original data online.

For example, you accidentally deleted all the rows for one customer from a large Sales table. If you have thousands of customers, you may not want to take the whole database offline to recover these rows. Online PITR allows you to recover the rows while the database stays online.

Last modified: January 24, 2025

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