Migration of ADB Control and ADBM metadata during ADB ES installation

Depending on which PostgreSQL target databases you plan to use in ADB ES, perform the following:

Migrate metadata from previously used internal databases to new ones (external or delivered in ADB ES). For this, you can use the pg_dump utility on the host where target databases are deployed. Example:

$ sudo -u postgres pg_dump -h <host> -p <port> --format=custom --no-owner --no-privileges -U <user> -f /tmp/<dump>.dump <database_name>

Restore data from each dump you created. For this, on the host where target databases are deployed, run the pg_restore utility:

$ sudo -u postgres pg_restore -p <target_port> -d <target_db> --clean --no-owner /tmp/<dump>.dump

Ensure that metadata is loaded to the target database. You can do this by comparing the number of rows in the key tables of the source and target databases:

SELECT count(*) FROM <schema>.<table>;

SELECT count(*) FROM adbm.adbm_restore_point;

Check that the correct owner is set for the adcc (in case of ADB Control) and adbm (in case of ADBM) schemas in target databases. If needed, change the owner manually. Example for adbm:

$ sudo -u postgres psql -p <target_port> -d <target_db> -c "ALTER SCHEMA adbm OWNER TO <target_owner>;"

For the quartz schema in ADBM, you should restore ownership for all its tables and sequences (if privileges were lost during migration).

DO $$ DECLARE r record;
BEGIN
    FOR r IN SELECT tablename FROM pg_tables WHERE schemaname = 'quartz' LOOP
        EXECUTE 'ALTER TABLE quartz.' || quote_ident(r.tablename) || ' OWNER TO <target_owner>;';
    END LOOP;
END $$;

DO $$ DECLARE r record;
BEGIN
    FOR r IN SELECT sequence_name FROM information_schema.sequences WHERE sequence_schema = 'quartz' LOOP
        EXECUTE 'ALTER SEQUENCE quartz.' || quote_ident(r.sequence_name) || ' OWNER TO <target_owner>;';
    END LOOP;
END $$;

Remove ADBM from ADB using the Uninstall service action. In the Erase data field, set false.

Remove ADB Control from ADB using the Uninstall service action. In the Erase data field, set false.

Perform ADB cluster upgrade to 6.30.0.1.

Add one Database service to ADB ES and map its components to hosts

On the Database service configuration page, select External postgres parameters in the Database type field and fill in all parameters in the list that opens. The assignment of parameters is described in the Configuration parameters → Database → External postgres parameters section.

Parameters for connecting to the external PostgreSQL DB

Click Save to save the Database configuration.

In the ADB Control database, to where you migrated metadata (external or internal), run the following query to delete data about the existing ADB cluster (needed to prevent conflicts in the future):

DELETE FROM adcc.system_user WHERE cluster_name = '<cluster_name>';

In ADB ES, add other services (except Database) and map their components to hosts.

Perform ADB ES installation using the Install cluster action.

Add the ADBC agents and ADBM agents services to all ADB clusters that were monitored in the previous version of ADB Control.

Import ADB ES configuration to ADB clusters.

Install ADBC agents and ADBM agents in ADB clusters.

In case of errors with GUC management in the ADB Control web interface after upgrade — on the host with ADB Control UI, add the following record to /etc/hosts:

<master_IP> <master_hostname>

On the ADB master host, run the following command to remove all existing configuration files of the pgbackrest utility:

$ gpssh -f arenadata_configs/arenadata_all_hosts.hosts -v -e 'rm -rf /home/gpadmin/arenadata_configs/pgbackrest/*'

Using the web interface of the ADBM service (installed in ADB ES), run the Verify action to recreate configuration files.

Using the web interface of the ADBM service (installed in ADB ES), run the Create configuration action to reapply the current backup configuration.