Back up notebooks and codespaces¶

Notebook and codespace data is automatically backed up by the notebooks-data-retention service. No manual backup steps are required. However, codespace file storage requires additional cluster configuration, and you should verify the retention window matches your recovery requirements.

Configure codespace file storage backup¶

Notebook metadata and content is backed up automatically. Codespace persistent file storage additionally requires Kubernetes Volume Snapshots to be configured in the cluster.

重要

Without Volume Snapshots, Codespace file storage cannot be backed up or restored. Classic notebooks and standalone notebooks are not affected.

Verify Volume Snapshots are available:

kubectl get volumesnapshotclass

Ensure persistent volumes for the notebooks filesystem use a storage class that supports snapshots:

notebooks:
  filesystems:
    configs:
      data:
        STORAGE_CLASS_NAME: <storage-class-with-snapshot-support>

Configure the retention window¶

The notebooks-data-retention service retains backed-up data for a configurable period before permanently deleting it. Ensure the retention window is long enough for your recovery needs.

Cluster-level¶

備考

You must fulfill the prerequisites before proceeding.

Set the default retention window for all notebooks and codespaces in the cluster:

notebooks:
  data-retention:
    configs:
      data:
        RETENTION_WINDOW: "30d"  # Default is 30 days

Valid values:

値	期間
`"30min"`	30分
`"6h"`	6時間
`"7d"`	7日
`"30d"`	30 days (default)
`"90d"`	90日

Per organization¶

Administrators can override the cluster default per organization in the DataRobot Admin UI:

Navigate to Organization settings.
Locate Notebooks soft-deletion retention period.
Set the desired retention period.

Verify the backup service¶

Confirm the notebooks-data-retention service is running:

kubectl get pods -n <namespace> | grep data-retention
kubectl logs -n <namespace> deployment/notebooks-data-retention