Collecting and providing databases to Broadcom support in certain scenario's will assist in faster resolution
The steps provided in the article will assist in collecting either the entire database or a specific database
cd /root; for db in cci-db postgres ebs-db provisioning-db abx-db approval-db catalog-db ccs-k3s-db cgs-db cmx-db codestream-db form-db hcmp-db idem-db identity-db lemans-resources-db migration-db project-db relocation-db repmgr-db tango-blueprint-db terraform-db userprofile-db assessment-db vco-db vro-gateway-db; do vracli db dump "$db" > "${db}-data.txt" 2>/dev/null; done; tar -czf "vra-db-backup-$(date +%Y%m%d_%H%M%S).tar.gz" *-data.txt 2>/dev/null && rm *-data.txt 2>/dev/null
cd /root
vracli db dump <database name> > <database name.txt>
e.g. vracli db dump identity-db > identity-db-data.txt
cd /root
vracli db dump > vra-db-dump.txt
vracli dev psql
\l (For a prettier output format, first run \x then run \l)
\q (To exit PSQL after getting the database name)
cd /root
vracli db dump <database name> > <database name.txt>
e.g. vracli db dump identity-db > identity-db-data.txt
Note: Database restore is not supported due to Kubernetes dependencies. The option of exporting DB should be used only for troubleshooting purpose with Broadcom support.