Documentation
- Getting Started Configuration Using CDM
- Clusters
- Fleet Configuration
- Capacity
- Metrics
- Servers, Pools and Services
- Logs
- Advisor
- Tasks and Audit
- S3 Multisite
- RBD Mirroring
- Support
Rollback
An older release does not start on a database migrated by a newer one. After starting the older tag, docker logs cdm lists the database copies it can use; pick the newest.
-
Stop CDM:
docker compose stop cdm -
Restore the copy. The current database is kept as
cdm.db.newer:BACKUP=cdm.db.007 # the copy from the log docker run --rm -v cdm-data:/data -e BACKUP="$BACKUP" alpine sh -c \ 'cp /data/cdm.db /data/cdm.db.newer && rm -f /data/cdm.db-wal /data/cdm.db-shm && cp "/data/$BACKUP" /data/cdm.db' -
Set
image:to the older tag and start it:docker compose up -d
Changes made since the update are lost.
