4. Install a9s-pg

a9s-pg is the central PostgreSQL database cluster used by the a9s Data Services Framework to store the state of every component, each of them in its own dedicated database.

4.1. Deploy a9s-pg

The deployment is created by executing:

bosh -d a9s-pg deploy a9s-pg/a9s-pg.yml \
  -l config/iaas-config.yml

Major Upgrades

Starting with anynines-deployment v60.0.0, a9s-pg uses a9s PostgreSQL 15 by default, and it is not possible to continue using a9s-pg running on a9s PostgreSQL 11. Therefore, a9s-pg must be manually upgraded to use a9s PostgreSQL 15 before executing the update to anynines-deployment v60.0.0. Otherwise, a forced upgrade of a9s-pg could be triggered that could lead to data loss and misbehavior.

4.2. Backup Integration

info

Backup integration for a9s-pg is mandatory. The a9s Data Services Framework requires a9s-pg to be connected to the a9s Backup Service. a9s-pg cannot be operated without backups enabled.

a9s-pg integrates with the a9s Backup Service to provide automated backups of the framework's state store. Backups are enabled by default when the a9s Backup Service is deployed and configured with a9s-pg support. For instructions on deploying the a9s Backup Service, see Install the a9s Backup Service.

4.3. Post-Deployment Process

In order to perform an a9s-pg disaster recovery, the Platform Operator must retrieve and save the backup encryption key and the a9s Backup Manager Service Instance ID. In case the disaster recovery happens and this information is unknown, it is not possible to recover a9s-pg.

Further information can be found in the a9s-pg Manual Logical Backup Recovery section.

4.4. Set Up a9s-pg Monitoring

Monitoring should be enabled in order to detect issues in a9s-pg, and to stop them from spreading and/or escalating. It is possible to add monitoring to a9s-pg by following a9s-pg setting up metrics manual. This provides better insight into the cluster's health and performance.