Does the backup role back up the full contents of the postgres database? Or does it just back up the configuration of the nodes and deployments of the AWX instance?
apiVersion: awx.ansible.com/v1beta1
kind: AWXBackup
What is the use case for a restore? I did a backup using this tool, then messed up my installation. So, I did a delete on the namespace/project in OpenShift, hoping to do a restore, but that was a disaster. The namespace would not delete, because the backup is a finalizer dependency. I ended up having to delete the backup in order to complete the deletion of the namespace. Obviously, I’m a complete rookie and this was a huge blunder. But what’s the right use case?
I’ve been doing nightly exports of my yaml state to an external file system and doing an import when things go badly. Is this recommended? Was it ever?
Hi Kevin,
When under normal circumstances the backup role does do what is basically a pgdump of the database, so yes, the contents would all be backed up.
That being said, deleting the namespace means that your backup is gone.
It sounds like you wanted to delete the deployment vs. the whole namespace, so the best use case here would be do a backup first, and then you would delete the AWX object, not the whole namespace. You can also delete the postgres PVC (persistent volume Claim) at this point.
We don’t have a doc for this at this time as far as we’re aware, but it would be good if we did, we’ll flag this as a to do item on our end.
We’ve all been rookies who make huge blunders before so we’d like to prevent something like this for other users if possible in the future.
Some useful docs:
restore docs - https://github.com/ansible/awx-operator/blob/devel/roles/restore/README.md
backup docs - https://github.com/ansible/awx-operator/blob/devel/roles/backup/README.md
Hope this helps,
AWX Team