ent external location or secrets manager provider.To configure a backup secrets store in the Helm chart, use the same approach and instructions documented for the primary secrets store, but using the backupSecretsStore configuration section instead of secretsStore, e.g.:

zenml:

# ...

# Backup secrets store settings. This is used as a backup for the primary

# secrets store.

backupSecretsStore:

# Set to true to enable the backup secrets store.

enabled: true

# The type of the backup secrets store

type: aws

# Configuration for the AWS Secrets Manager backup secrets store

aws:

# The AWS Service Connector authentication method to use.

authMethod: secret-key

# The AWS Service Connector configuration.

authConfig:

# The AWS region to use. This must be set to the region where the AWS

# Secrets Manager service that you want to use is located.

region: us-east-1

# The AWS credentials to use to authenticate with the AWS Secrets

aws_access_key_id: <your AWS access key ID>

aws_secret_access_key: <your AWS secret access key>

Database backup and recovery

An automated database backup and recovery feature is enabled by default for all Helm deployments. The ZenML server will automatically back up the database before every upgrade and restore it if the upgrade fails in a way that affects the database.

The database backup automatically created by the ZenML server is only temporary and only used as an immediate recovery in case of database migration failures. It is not meant to be used as a long-term backup solution. If you need to back up your database for long-term storage, you should use a dedicated backup solution.

Several database backup strategies are supported, depending on where and how the backup is stored. The strategy can be configured by means of the zenml.database.backupStrategy Helm value:

disabled - no backup is performed