OceanBase Cloud supports creating cross-cloud and same-cloud standby instances. This topic describes the limitations on standby instances and provides the specific procedure.
Background information
In the multi-cloud architecture of OceanBase Cloud, independent "organizations" are created under an OceanBase account based on different cloud vendor Marketplace channels (such as Alibaba Cloud Marketplace and AWS Marketplace, etc.) or self-operated channels. Resources between these organizations are isolated by default. Previously, users could not create primary and standby instances across different organizations/projects, which limited cross-cloud disaster recovery capabilities. Currently, you can create primary and standby databases on Alibaba Cloud, AWS, GCP, and Azure.
Prerequisites
You have completed authorization between different organization projects. For specific procedures, refer to Cross-project mutual authorization.
You have completed the creation of the primary instance. For specific procedures, refer to Create a cluster instance.
The current cluster instance uses the Shared Nothing architecture and is billed on a pay-as-you-go basis.
The current cluster version is 4.x or later.
The current cluster instance is in the Running state.
The role of the currently logged-in account is Project Admin.
Procedure
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Instances.
In the instance list, find the target cluster and click Create Standby Instance in the Actions column.
In the dialog box that appears, select the organization and project for the standby instance.
On the order page, configure the purchase parameters for the standby instance.
ParameterDescriptionStorage Architecture Select Shared Nothing. Compute resources and data are stored on the same node, and data is processed locally on compute nodes. This reduces data transfer overhead, improves compute efficiency, and simplifies maintenance. Database Version Select the same database version as the primary instance. Deployment Mode - Single-IDC Deployment: All full-featured replicas are located in the same zone. Single-IDC two-replica and single-IDC three-replica deployments are supported. Contact OceanBase Technical Support if required.
- Dual-IDC Deployment: Two full-featured replicas are deployed in two zones, and an arbitration service used only for log synchronization is deployed in a third zone. The arbitration service does not provide read or write services. Dual-IDC deployment provides the same availability as multi-IDC deployment at a lower cost. OceanBase Database V4.1.0.0 and later support this deployment mode.
- Multi-IDC Deployment: Primary and standby replicas are deployed in different zones to provide cross-zone disaster recovery at no additional cost. All three zones are selected by default.
Zone - Single-IDC Deployment: Select one zone. Single-IDC two-replica and single-IDC three-replica deployments are supported.
- Dual-IDC Deployment: Select two zones.
- Multi-IDC Deployment: Select three zones.
Compute Different cloud vendors support different compute specifications. For more information, refer to Cloud service provider and deployment region. Storage Disk Type Only instances on Alibaba Cloud Marketplace support selecting ESSD PL0 or ESSD PL1. Storage Different node specifications correspond to different storage specifications. For more information, refer to Billing overview. Maximum IOPS for Single Replica Calculated based on the compute specification, storage type, and specification. The actual available IOPS is subject to the result displayed on the interface. Note
The current version supports viewing IOPS only for instances on Alibaba Cloud, Huawei Cloud, and AWS marketplaces.
In the Summary section, check whether your parameter configurations and purchase quantity are correct. After verification, agree to the service agreement and click Confirm Order.
Note
- Billing rules for compute and storage resources of the standby instance. For more information, refer to Instance billing description.
- Data backup fees are charged based on the backup space. For more information, refer to Backup and restore fees.
- During the feature promotion phase, cross-region traffic fees are temporarily free.
After the payment is successful, you can view the basic information of the standby instance on the instance list page, such as its type, series, availability zone, storage space, payment method, tags, and status.
Prerequisites
Before creating a standby instance, perform the following checks. The modification can be performed only if all conditions are met.
You have completed the creation of the cluster instance. For specific procedures, refer to Create a cluster instance.
The current cluster instance is paid by the pay-as-you-go method.
The current cluster version is 4.2.1.7 or later.
The current cluster instance is in the Running state.
The role of the currently logged-in account is Project Admin.
Note
You can create a standby instance for an instance that already has read-only replicas. After the standby instance is created, the read-only replicas from the primary instance are not synchronized. If necessary, you can create read-only replicas separately for the standby instance. For specific procedures, refer to Create a read-only replica for a cluster or Create a read-only replica for a tenant.
Procedure
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Instances.
In the instance list, find the target cluster, and click Create Standby Instance in the Actions column.
Note
You can create at most two standby instances for a primary cluster instance.
On the order page, configure the purchase parameters for the standby instance.
ParameterDescriptionStorage Architecture - Shared Nothing: Compute resources and data are stored on the same node, and data is processed locally on compute nodes. This reduces data transfer overhead, improves compute efficiency, and simplifies maintenance.
- Shared Storage: Multiple compute nodes in a cluster use shared storage to decouple compute from storage. Compute and storage can be independently scaled for greater flexibility and elasticity.
Note
The Shared Storage architecture is currently unavailable and will be supported in the future.
Database Version Select the OceanBase database version. Different channels support various database versions, including V4.3.5, V4.2.5, V4.2.1, V3.2.4, and others. The drop-down window displays the main features of different versions for your reference. Deployment Mode - Single-IDC Deployment: All full-featured replicas are located in the same zone. Single-IDC two-replica and single-IDC three-replica deployments are supported. Contact OceanBase Technical Support if required.
- Dual-IDC Deployment: Two full-featured replicas are deployed in two zones, and an arbitration service used only for log synchronization is deployed in a third zone. The arbitration service does not provide read or write services. Dual-IDC deployment provides the same availability as multi-IDC deployment at a lower cost. OceanBase Database V4.1.0.0 and later support this deployment mode.
- Multi-IDC Deployment: Primary and standby replicas are deployed in different zones to provide cross-zone disaster recovery at no additional cost. All three zones are selected by default.
Zone - Single-IDC Deployment: Select one zone. Single-IDC two-replica and single-IDC three-replica deployments are supported.
- Dual-IDC Deployment: Select two zones.
- Multi-IDC Deployment: Select three zones.
Compute Different cloud vendors support different compute specifications. For more information, refer to Cloud service providers and deployment regions. Storage Disk Type Supports EPL0 and EPL1. Storage Different node specifications correspond to different storage specifications. For more information, refer to Billing overview. Maximum IOPS for a Single Replica Calculated based on the compute specification, storage type, and specification. The actual available IOPS are subject to the results displayed on the interface. Note
The current version supports viewing IOPS only for instances on Alibaba Cloud, Huawei Cloud, and AWS channels.
In the Summary section, check whether your parameter configurations and quantities are correct. After verification, agree to the service agreement and click Confirm Order.
Note
- Billing rules for compute and storage resources of the standby instance. For more information, refer to Instance billing description.
- Data backup fees are charged based on the backup space. For more information, refer to Backup and restore fees.
- During the feature promotion phase, cross-region traffic fees are temporarily waived.
After successful payment, you can view the basic information of the standby instance, such as its type, series, availability zone, storage space, payment method, tags, and status, on the instance list page.
Related operations
After the standby instance is created, you can perform the following operations:
View the basic information, performance monitoring, and deployment relationship diagram of the primary and standby instances on their respective workbench pages. For more information, refer to Primary and standby instance workbench.
Upgrade the compute specification, storage specification, and number of nodes for the primary and standby instances. For specific procedures, refer to Upgrade primary and standby instances.
View or modify the cluster parameters of the primary and standby instances on the Parameter Management page. For specific procedures, refer to Manage parameters.
Suspend and start the primary instance to automatically synchronize the standby instance. For specific procedures, refer to Suspend/Start an instance.
After the primary instance is suspended, all associated standby instances are automatically suspended. You cannot suspend a standby instance separately.
After the primary instance is started, all associated standby instances are automatically started. You cannot start a standby instance separately.Perform configuration changes for the primary and standby instances. For specific procedures, refer to Set cluster change configurations.
Note
- The minimum node specification of the standby instance must be at least 0.33 times that of the primary instance.
- The storage specification of the standby instance cannot be less than that of the primary instance.
Configure alert rules for the standby instance. For specific procedures, refer to Create an alert rule.
View the performance metrics of the primary and standby instances on the Performance Monitoring page. For more information, refer to Monitor the performance of hosts in a cluster.
On the Backup Recovery page, you can perform operations such as initiating recovery, performing immediate backup, and modifying the backup strategy for the primary and standby instances. For specific procedures, refer to Backup and recovery.
Data backup is billed based on the backup space. For more information, refer to Backup and recovery billing.On the Historical Events page, you can view the historical event records of the primary and standby instances. For more information, refer to Historical events.