Backing up DataRobot configuration¶

This operation can be executed from any macOS or GNU/Linux machine that has enough space to store the backup files.

Typically, all DataRobot configuration is managed through the values.yaml files that you use to install DataRobot from the Helm charts. To move or restore your configuration to a new cluster, you would generally use these original values.yaml files during the installation on the new cluster.

Alternatively, you can export the currently applied values from your running Helm releases. This section describes exporting the running Helm release values.

Exporting current Helm release values¶

To export the configuration values being used on your running DataRobot Helm releases, follow these steps.

Prerequisites:

Helm: Version 1.23 or later must be installed on the host where the backup will be created.
- See Helm Installation Guide.
- helm must be configured to access the Kubernetes cluster where the DataRobot application is running. Verify this configuration with a command like helm status dr -n <your-datarobot-namespace>, replacing <your-datarobot-namespace> with your actual DataRobot namespace.

Steps:

Define a backup location on the host where the configuration will be saved. This example uses ~/datarobot-backups/, but you can choose a different path. Replace ${BACKUP_LOCATION} with your chosen path if it's different, or set the variable.
```
export BACKUP_LOCATION=~/datarobot-backups/
mkdir -p ${BACKUP_LOCATION} 
```
Export the current Helm release values for the DataRobot application (typically named dr) and Persistent Critical Services (typically named pcs). Replace <your-datarobot-namespace> with the namespace where DataRobot is installed.
```
helm get values dr -n <your-datarobot-namespace> > ${BACKUP_LOCATION}/dr_values.yaml
helm get values pcs -n <your-datarobot-namespace> > ${BACKUP_LOCATION}/pcs_values.yaml 
```
These commands save the current values into dr_values.yaml and pcs_values.yaml inside your specified ${BACKUP_LOCATION}.