Closed giohappy closed 6 years ago
Fixed with https://github.com/geosolutions-it/geonode-restore-docker/pull/1
Restore proc described in https://github.com/cezio/geonode-restore-docker/blob/master/README.md
Image: https://hub.docker.com/r/geosolutionsit/geonode-restore/
Restore procedure tested with both catalog entries.
Note, that 1.0 of geonode-generic stack backup won't work with 1.1 restore (and vice versa). Also, 1.0 won't upgrade properly to 1.1 due to change in db name.
Currently geonode-generic includes scheduled backups (geosolutionsit/geonode-backup:latest image) but we need to implement a restore procedure for disaster recovery scenarios.
Assuming external volume has been configured for backups storage we need to have the following procedure implemented and tested:
The goal is to have a recovery procedure that guarantees stack restoration in the worst scenario, that can be simulated restoring a stack in a brand new host.
For this task a new "geonode-restore" image should be defined. It will use the same configuration (env vars) fro Rancher / Docker as the other containers in the stack.
Recovery procedure steps:
For the moment this will be documented and executed manually. In the future an automated mechanis, under orchestration, will be implemented.