CDM backup and restore
This page describes the CDM’s legacy backup and restore implementation, which is now deprecated. We strongly recommend that you transition to the current CDM backup and restore implementation as soon as possible.
- CDM directory architecture
Five DS instances are deployed using Kubernetes stateful sets (two
- Backup architecture
Before you can back up CDM data, you must set up a cloud storage container, and then configure a Kubernetes secret with the container’s location and credentials in the CDM deployment.
DS data backups are stored in Google Cloud Service, Amazon S3, or Azure Blob Storage.
All backups are incremental from the previous backup. The first backup created is a full backup.
DS server instances use cryptographic keys to sign and verify the integrity of backup files, and to encrypt data. Server instances protect these keys in a deployment by encrypting them with the shared master key. For portability, servers store the encrypted keys in the backup files.
- Backup scheduling
Backups must be scheduled using the schedule-backups.sh script in the /path/to/forgeops/bin path on your local computer.
By default, CTS and identity repository directory instances are backed up every hour.
The backup schedule can be customized separately for CTS and identity repository DS instances based on your recovery objectives.
By default, the backups are scheduled from the first (or
-0) pod of each DS instance. You can customize and schedule backups from any pod of a DS instance. You can also schedule backups from multiple pods.
You can initialize new DS instances with data from a backup when you deploy CDM.
You can restore existing
idrepoDS instances from a backup.
Creating or restoring a DS instance from a backup requires that the instance being created or restored has the same master key pair as the instance that you backed up. Make sure that you save the original directory’s master key pair when you deploy the CDM.