mirror of
https://github.com/holos-run/holos.git
synced 2026-03-21 17:55:01 +00:00
78cec76a96
A full backup was taken using: ``` kubectl annotate postgrescluster zitadel postgres-operator.crunchydata.com/pgbackrest-backup="$(date)" ``` And completed with: ``` ❯ k logs -f zitadel-backup-5r6v-v5jnm time="2024-03-10T21:52:15Z" level=info msg="crunchy-pgbackrest starts" time="2024-03-10T21:52:15Z" level=info msg="debug flag set to false" time="2024-03-10T21:52:15Z" level=info msg="backrest backup command requested" time="2024-03-10T21:52:15Z" level=info msg="command to execute is [pgbackrest backup --stanza=db --repo=2 --type=full]" time="2024-03-10T21:55:18Z" level=info msg="crunchy-pgbackrest ends" ``` This patch verifies the point in time backup is robust in the face of the following operations: 1. pg cluster zitadel was deleted (whole namespace emptied) 2. pg cluster zitadel was re-created _without_ a `dataSource` 3. pgo initailized a new database and backed up the blank database to S3. 4. pg cluster zitadel was deleted again. 5. pg cluster zitadel was re-created with `dataSource` `options: ["--type=time", "--target=\"2024-03-10 21:56:00+00\""]` (Just after the full backup completed) 6. Restore completed successfully. 7. Applied the holos zitadel component. 8. Zitadel came up successfully and user login worked as expected. - [x] Perform an in place [restore][restore] from [s3][bucket]. - [x] Set repo1-retention-full to clear warning [restore]: https://access.crunchydata.com/documentation/postgres-operator/latest/tutorials/backups-disaster-recovery/disaster-recovery#restore-properties [bucket]: https://access.crunchydata.com/documentation/postgres-operator/latest/tutorials/backups-disaster-recovery/disaster-recovery#cloud-based-data-source