-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Restore of geonode backup is not working #156
Comments
@mwallschlaeger have you already used this feature in the case of GeoNode K8s? |
@AlexGacon hey no i havent tried this approach. We're about to use https://github.com/zalando/postgres-operator/blob/master/docs/administrator.md#wal-archiving-and-physical-basebackups to backup and restore geonode databases together with a flat copy of the volume |
This could be part of a list in the docs listing geonode features currently not functional in geonode-k8s |
@AlexGacon is this maybe related to the latest fixes in geonode v4.2.3 |
@AlexGacon have you tested this since the changes in geonode regarding geonode-backup? If so maybe you could add a small readme of howto deal with backups in a geonode-k8s environment? |
Sorry @mwallschlaeger I didn't get the opportunity to do so. One of my customer will soon have to do a migration so it would be the occasion to test. |
Bug Description
In order to migrate a GeoNode instance to GeoNode K8s, we tried to dump and restore the environment using the geonode commands.
The restore is not working, because the backup_restore folder is not available on the geoserver pod.
I am not sure if mounting the PVC on the pod is enough because of the ReadWrite access mode
Reproduction Steps
best to provide your values.yaml, a brief description of your cluster and version of geonode-k8s here.
Behavior
A description of what you expected to happen and what actually happened.
Additional Information
Any additional information or context that may be helpful in resolving the bug.
The text was updated successfully, but these errors were encountered: