6.4. Upgrading to PPEM 2.0 #
This section contains recommendations and an instruction for migrating to PPEM 2.0.
Important
Version 2.0 is not backward compatible with version 1.0. No tools for smooth data migration are currently available.
Migration Recommendations
When migrating to PPEM 2.0, note the following changes implemented in this version:
The manager and agent components are rewritten in Golang and implement the new API version. For this reason, some PPEM 2.0 components are incompatible with version 1.0 components:
The manager version 2.0 and agents version 1.0 are mutually incompatible.
The web application version 2.0 and the manager version 1.0 are mutually incompatible.
Configuration files of the manager version 1.0 and the manager version 2.0 are mutually incompatible.
Configuration files of agents version 1.0 and agents version 2.0 are mutually incompatible.
Agents version 2.0 no longer regularly collect metrics and logs of DBMS instances. PPEM now uses pgpro-otel-collector to work with metrics and logs.
Therefore, the following migration recommendations for PPEM 2.0 are provided:
It is recommended to install PPEM 2.0 on hardware separate from that used for PPEM 1.0, as well as to completely shut down all PPEM 1.0 components (including the manager and agents) before installing and starting the PPEM 2.0 manager and agents.
Important
Performing the same operations on the same DBMS instances simultaneously in two PPEM versions may lead to unpredictable consequences. Avoid using two PPEM versions simultaneously. Simultaneous operation of both versions was not tested and is not guaranteed.
To use advanced DBMS instance health monitoring features in PPEM, it is recommended to install and configure pgpro-otel-collector.
For more information, refer to the official Postgres Pro documentation on pgpro-otel-collector and integration with PPEM.
Migration
Completely shut down all PPEM 1.0 components.
On a separate server, install the manager version 2.0.
The manager 2.0 repository database can be located in the same DBMS instance as the manager 1.0 repository database.
Important
Do not use the same repository database for both versions, otherwise the manager version 2.0 will not start.
To verify that the manager version 2.0 is successfully installed, log in to the web application and get an API key for configuring the agent.
Install an agent version 2.0.
On all DBMS instance servers, delete agents first, and then delete the manager version 1.0.