The primary and standby BYOC instances must use the same cloud provider. This topic describes the usage limitations and specific procedure for creating a standby instance.
Prerequisites
Before you create a standby instance, perform the following checks. You can proceed only if all conditions are met.
You have created a cluster instance. For more information, see Create a cluster instance.
The current cluster instance is billed on a pay-as-you-go basis.
The current cluster version is 4.2.1.7 or later.
The current cluster instance is in the Running state.
The role of the current 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, it does not synchronize the read-only replicas from the primary instance. If needed, you can create read-only replicas separately for the standby instance. For instructions, see Create a read-only replica.
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 up to two standby instances for a primary cluster instance.
On the order page, configure the purchase parameters for the standby instance.
ParameterDescriptionStorage Architecture Shared-nothing architecture: Compute resources and data storage are located on the same node. Data is processed locally on the compute node, reducing data transmission overhead and improving compute efficiency. It features a streamlined architecture and is easy to maintain and manage. Database Version Select the version of OceanBase Database. 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 availability zone. Supports single-IDC two-replica and single-IDC three-replica deployments. Contact OceanBase Technical Support if required.
- Dual-IDC Deployment: Deploys two full-featured replicas across two availability zones, and deploys an arbitration service dedicated only to log synchronization in a third availability zone. This service does not provide read/write services externally. Dual-IDC deployment offers the same availability as multi-IDC deployment but with significantly improved cost-effectiveness. Currently, versions 4.1.0.0 and later support the dual-IDC deployment solution.
- Multi-IDC Deployment: Primary and standby replicas are located in different availability zones, enabling cross-availability-zone disaster recovery without additional charges. By default, all three availability zones are selected.
Zone - Single-IDC Deployment: Select one availability zone, which provides two deployment methods: single-IDC two-replica and single-IDC three-replica.
- Dual-IDC Deployment: Select two availability zones.
- Multi-IDC Deployment: Select three availability zones.
Compute Different cloud vendors support different compute specifications. For details, see Cloud Service Providers and Deployment Regions. Storage Different node specifications correspond to different storage specifications. For details, see Billing Overview. Maximum IOPS for Single Replica The per-replica IOPS limit depends on the compute specification, storage type, and storage specifications. The console shows the available IOPS. On the Summary page, verify that your parameter configurations and quantities are correct. After verification, agree to the service agreement and click Confirm Order.
Note
- The billing rules for compute and storage resources of a standby instance are described in Instance Billing.
- Data backup is billed based on the backup space. For billing rules, see Backup and Recovery Fees.
- During the feature promotion phase, cross-region data transfer is temporarily free of charge.
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 data, and deployment relationship diagram of the primary and standby instances on their respective workspace pages. For more information, see Primary and standby instance workspaces.
Scale the compute, storage, and node specifications of the primary and standby instances. For more information, see Primary and Standby Instance Scaling.
View or modify the cluster parameters of the primary and standby instances on the Parameter Management page. For more information, see Parameter Management.
Stop and start the primary instance to automatically stop and start the standby instance. For more information, see Stop and start an instance.
After the primary instance is stopped, all associated standby instances are automatically stopped. You cannot stop 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 on the primary and standby instances. For more information, see Set Cluster Change Configuration.
Note
- The minimum node specification of a standby instance must be greater than or equal to 0.33 times the node specification of the primary instance.
- The storage specification of a standby instance must not be less than that of the primary instance.
Configure alert rules for the standby instance. For more information, see Create an Alert Rule.
View the performance metrics of the primary and standby instances on the Performance Monitoring page. For more information, see Cluster Host Performance Monitoring.
On the Backup and 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 more information, see Backup and Recovery.
Data backup is billed based on the backup space. For billing rules, see Backup and Recovery Fees.On the Historical Events page, you can view the historical event records of the primary and standby instances. For more information, see Historical Events.