Considerations of Backward Compatibility in PPEM 2.2

In the PPEM 2.2, packaged API commands can now be sent by the manager. Typically, these are API commands required for executing various operations.

If the manager and agents operate on different PPEM versions, you cannot create instances and perform any actions with databases and their objects, such as schemas.

To avoid backward compatibility issues, select the date and time when no operations with databases and their objects are scheduled, and then upgrade both the manager and agents to version 2.2.

Upgrading the Manager to Version 2.2

To upgrade the manager:

1. Upgrade the repository and package manager metadata.

   The upgrade procedure depends on the version of the used distributive and package manager.

2. Stop the manager 2.1 service:

   systemctl stop ppem
   

3. Install the manager 2.2.

   The installation procedure is performed using the package manager.

4. Upgrade the configuration files in the /etc catalog.

   Place the parameters into a new configuration file if required.

5. Start the manager 2.2 service:

   systemctl start ppem
   

6. Ensure that the manager service started successfully and is available:

   systemctl status ppem
   

Upgrading Agents to Version 2.2

1. Upgrade the repository and package manager metadata.

   The upgrade procedure depends on the version of the used distributive and package manager.

2. Stop the agent 2.1 service:

   systemctl stop ppem-agent
   

3. Install the version 2.2 agent.

   The installation procedure is performed using the package manager.

4. Upgrade the configuration files in the /etc catalog.

   Place the parameters into a new configuration file if required.

5. Start the agent 2.2 service:

   systemctl start ppem-agent
   

6. Ensure that the agent service started successfully:

   systemctl status ppem-agent