Configure the Retention Period for an Unlimited Storage Database

Use the Workspace Groups path (/v1/workspaceGroups/{workspaceGroupID}/storage/retentionPeriod endpoint) in the Management API to specify the retention period (in minutes) for an unlimited storage database. The retention period specifies how long the historical information used to enable point-in-time recovery (PITR) is retained. By default, the retention period is set to 10080 minutes.

For example, the following API request sets the retention period to 7200 minutes for the workspace group with ID 058e2ed1-3000-4000-a000-512d334df903:

curl -X 'PATCH' \
'https://api.singlestore.com/v1/workspaceGroups/058e2ed1-3000-4000-a000-512d334df903/storage/retentionPeriod' \
-H 'accept: */*' \
-H 'Content-Type: application/json' \
-d '{
"retentionPeriod": 7200
}'

Refer to Management API Reference for more information.

Once a milestone reaches the retention period, it is no longer available and does not appear in the MV_MILESTONES information schema view.

You cannot attach an unlimited storage database at a milestone or time that is not within the retention period. For example, consider that the retention period is 1440 minutes (1 day) and you create a milestone for a database dbExample on June 1. On June 3, you will not be able to attach dbExample at the milestone created on June 1 or at a point in time that occurred on June 1.

Last modified: September 18, 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