Back up validation fails due to PostGis Extension

[rstens]

Describe the Bug
We have a PostgreSQL database with PostGIS installed.
The back up validation fails with:

[!!ERROR!!] - Backup verification failed; /backups/daily/2020-07-29/invasivesbc-api-postgresql-test-InvasivesBC_2020-07-29_16-50-15.sql.gz

The following issues were encountered during backup verification;
ERROR:  could not open extension control file "/opt/rh/rh-postgresql10/root/usr/share/pgsql/extension/postgis.control": No such file or directory

Elapsed time: 0h:0m:40s - Status Code: 3

Other psql extensions might suffer from this as well.

Expected Behaviour
The backup validation works

** Steps To Reproduce**
Steps to reproduce the behaviour:

1. Open the back up pod (tested on test)
2. run./backup.sh -v all
3. See error

[rstens]

Also reported at: BCDevOps/backup-container#58
Wade's comment is that this needs to be enhancement for the backup solution.

[rstens]

Running into some issues related to combining two docker definitions and making it work in the same way. COntinuing

[rstens]

To run a restore:

Scale pods down:

• Metabase (only in Prod)
• API (remove autoscale first and then restore that afterwards)
• Schema Spy
• Prod Database (and then bring up again to sever all connections)
• The app can be left, but users will see an error msg

In Backup pod run:
./backup.sh -r invasivesbc-api-postgresql-test/InvasivesBC
Check ./backup.sh -h for options if you want a specific file.

Verification of successful restore:

oc rsh <database pod>
pqsql
\c InvasivesBC
SET search_path = invasivesbc;
select * from watercraft_risk_assessment;

Check Count of entries

[rstens]

We will close the issue for now. We'll have a technical debt to figure out how to get the validate to work.