This topic describes the background information and limitations of upgrading OceanBase Migration Service (OMS) Community Edition to V4.2.6.
Background information
OMS Community Edition supports rollbacks during upgrades. We recommend that you use a backup tool to back up the existing database, such as db_oms, to an SQL file, such as db_oms_bak.sql, before starting an upgrade. The new image of OMS Community Edition will run on the original db_oms database, and the database backup file, such as db_oms_bak.sql, can be used for a rollback.
Note
If you do not have a handy backup tool, contact OMS Community Edition Technical Support for the documentation related to backup operations. In general, you can use mysqldump to export backup files.
Perform the following operations to upgrade OMS:
If high availability (HA) is enabled, disable it first.
Back up the databases.
Start a new container for OMS Community Edition V4.2.6.
The name of the MetaDB for the container of OMS Community Edition V4.2.6 must be the same as that of the MetaDB before the upgrade. In addition, the three disk mounting paths must be the same as those before the upgrade.
On the System Parameters page, enable HA and configure the related parameters.
(Optional) Perform the rollback operation as needed.
After the upgrade is complete, clear the browser cache before you log on to OMS Community Edition.
Limitations
Currently, it is only supported to upgrade from OMS Community Edition V4.2.4 to Community Edition V4.2.6. Upgrading from versions lower than Community Edition V4.2.4 to Community Edition V4.2.6 is not supported.
Before you start the upgrade, make sure that data is synchronized in quasi-real-time between the source and destination in data migration or synchronization tasks created by using the earlier version of OMS, and that the forward switchover process of the tasks is completed. We recommend that you do not use the new version of OMS Community Edition to perform the forward switchover process.