This topic describes the usage notes and methods for deploying OceanBase Migration Service (OMS) of the current version.
Single-node deployment
OMS deployed on a single node can provide all OMS features. If you do not need to use a high-availability environment, you can deploy OMS on a single node. For more information, see Deploy OMS on a single node.
Deploy OMS on multiple nodes in a single region
You can deploy OMS on multiple nodes to achieve high availability. In the high-availability architecture, each OMS node provides all OMS features, and the backend task framework implements distributed scheduling based on the database. When an OMS node becomes unavailable, the framework automatically schedules tasks to other available OMS nodes.
OMS also supports deployment on multiple nodes in a single region. For more information, see Deploy OMS on multiple nodes in a single region.
Note
The high availability (HA) feature does not support automatic recovery of the Full-Import/Full-Verification component.
We recommend that you apply multi-node deployment in the production environment.
Deploy OMS on multiple nodes in multiple regions
OMS supports multi-region deployment. You can deploy OMS across multiple regions. For more information, see Deploy OMS on multiple nodes in multiple regions.
OAT-based deployment
If OceanBase Admin Toolkit (OAT) is installed in your environment, you can deploy OMS on the server by using OAT V3.2.0 or later. For more information, see the OAT documentation.
Usage notes
If you use OMS V2.1.0 or later to collect and display historical monitoring data, you must deploy an InfluxDB time-series database.
By default, HA is disabled in OMS. To enable HA, use one of the following methods:
If you use OMS earlier than V3.1.0, run the following command:
supervisorctl start oms_drc_haFor OMS V3.1.0 and later, log on to the OMS console and change the value of
enabletotrueinha.configto enable the HA feature. For more information, see Modify high availability configurations.