Miscellaneous tips

It is recommended that you take a regular backup of the vital files and folders used in the IBM Verify Identity Governance - Container. In general, here are the artifacts that you should include in the backup process.

Database files

If you are using an external database, ensure that you take a regular backup on a periodic basis.

If you are using PostgreSQL, refer to pg_dump option in the PostgreSQL documentation.

If you are using the internal (that is, containerized) PostgreSQL, then the pg_dump option is already supported in the starter/bin/util/pgBackup.sh and the pgRestore.sh.

In addition, you can make a copy of the volume being used by the database.

LDAP data

If you are using an external ISVD, ensure that you take a regular backup on a periodic basis.

If you are using internal (containerized) ISVD, then it is recommended that you take a backup of the LDIF data and the schema directory. Alternatively, you can also backup the volume that is being used by them.

For more backup options, refer the ISVD technote.

Configuration data

You must take a backup of any changes or customization done to the starter host in the /data directory and turned into a configmap. IBM Verify Identity Governance - Container does maintain a copy of these files in the Kubernetes cluster, but it is a good practice to also save it from the starter area.

It is recommended that you should backup the entire starter area, or, at least the config, data, helm, and yaml directories.