OceanBase Cloud supports creating cross-cloud standby instances and standby instances within the same cloud. This topic describes the limitations on standby instances and the procedure for creating a standby instance.
Background information
In the multi-cloud architecture of OceanBase Cloud, independent "organizations" are created under one OceanBase account based on different cloud vendor channels (such as Alibaba Cloud marketplace, Huawei Cloud marketplace, and AWS Marketplace) or OceanBase Cloud official website. By default, resources are isolated across these organizations. Previously, users could not create primary and standby instances across organizations or projects, limiting cross-cloud disaster recovery capabilities. Now, primary and standby databases can be created across Alibaba Cloud, AWS, Google Cloud, and Azure.
Prerequisites
You have completed cross-project authorization. For more information, see Cross-project bidirectional authorization.
A primary instance has already been created. For more information, see Create an Instance.
The storage architecture of the current primary instance is Unified Storage & Compute, and the current instance is billed on a pay-as-you-go basis.
The current instance version is 4.x or later.
The current instance is in the running state.
The logged-in account has the role of Project Admin.
Procedure
Log in to the OceanBase Cloud console.
In the left-side navigation pane, click Instances.
On the Instances page, find the target instance and click Create Standby Instance in the Actions column.
Select the organization and project of the instance in the pop-up box.
On the order page, set the purchase parameters for the standby instance.
Parameter Description Storage Architecture Select Unified Storage & Compute: The computing resources and data storage are in the same node. Data is locally processed on the computing node. This reduces the overheads of data transmission and improves the computing efficiency. The architecture is simple and easy to maintain. Version Select the same version of OceanBase Database as the primary instance. Deployment Mode - Single-IDC Deployment: All nodes are located within the same zone. This deployment supports both two-node and three-node configurations within a single IDC. If you require this setup, please contact OceanBase technical support.
- Dual-IDC Deployment: Two nodes are deployed across two zones, with a third node deployed in a different zone solely for log synchronization. This node does not provide read/write services. Dual-IDC deployment offers the same availability as multi-IDC deployment but with significantly improved cost efficiency. The dual-IDC deployment option is supported in versions 4.1.0.0 and later.
- Multi-IDC Deployment: Primary and standby nodes are located in different zones, enabling disaster recovery across zones. This deployment comes at no additional cost and by default, all three zones are selected.
Zone - Single-IDC deployment: Select one zone to deploy either two or three nodes.
- Dual-IDC deployment: Select two zones to deploy two nodes.
- Multi-IDC deployment: Select three zones to deploy the primary and standby nodes.
Compute Select the compute specification as needed. Storage Disk Type EPL0 and EPL1 are supported. Storage The storage specifications vary by compute specifications. Select the storage specification as needed. Maximum IOPS per Node The maximum IOPS for each node is calculated based on the compute specification and storage type and specification. The actual available IOPS is subject to the result displayed on the OceanBase Cloud console. Note
At present, only instances purchased through Alibaba Cloud, Huawei Cloud, and AWS support viewing IOPS information.
In the Summary section, review your instance configurations and quantity, and then place the order.
Note
- For details on billing rules for the standby instance’s compute and storage resources, see Instance billing.
- Backup costs are based on the backup space used. For more details, see Backup billing.
- Cross-region traffic charges are free for a limited time during the feature promotion phase.
After the standby instance is created, you can view the standby instance’s basic information, such as type, region, storage, tags, and status, on the instance list page.
Prerequisites
Before creating a standby instance, ensure the following conditions are met:
A primary instance has already been created. For more information, see Create an Instance.
The current instance is billed on a pay-as-you-go basis.
The current instance version is 4.2.1.7 or later.
The current instance is in the running state.
The logged-in account has the role of 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 instance, and click Create Standby Instance in the Actions column.
Note
Each primary instance can have up to 2 standby instances.
On the order page, complete the purchase options for the standby instance.
Parameter Description Storage Architecture - Unified Storage & Compute: The computing resources and data storage are in the same node. Data is locally processed on the computing node. This reduces the overheads of data transmission and improves the computing efficiency. The architecture is simple and easy to maintain.
- Separated Storage & Compute: This cloud-native architecture separates storage and computing in a cluster by using multiple computing nodes and shared storage technology. The separated layers of computing and storage resources allow independent scaling and improve cost-effectiveness and flexibility.
Note
At present, only instances purchased through Alibaba Cloud and Huawei Cloud support separated storage and compute. The database version is V4.3.5.
Version The version of OceanBase Database. Different channels support various database versions, including V4.3.5, V4.2.5, V4.2.1, and V3.2.4. Deployment Mode - Single-IDC Deployment: All nodes are located within the same zone. This deployment supports both two-node and three-node configurations within a single IDC. If you require this setup, please contact OceanBase technical support.
- Dual-IDC Deployment: Two nodes are deployed across two zones, with a third node deployed in a different zone solely for log synchronization. This node does not provide read/write services. Dual-IDC deployment offers the same availability as multi-IDC deployment but with significantly improved cost efficiency. The dual-IDC deployment option is supported in versions 4.1.0.0 and later.
- Multi-IDC Deployment: Primary and standby nodes are located in different zones, enabling disaster recovery across zones. This deployment comes at no additional cost and by default, all three zones are selected.
Zone - Single-IDC deployment: Select one zone to deploy either two or three nodes.
- Dual-IDC deployment: Select two zones to deploy two nodes.
- Multi-IDC deployment: Select three zones to deploy the primary and standby nodes.
Compute Select the compute specification as needed. Storage Disk Type EPL0 and EPL1 are supported. Storage The storage specifications vary by compute specifications. Select the storage specification as needed. Maximum IOPS per Node The maximum IOPS for each node is calculated based on the compute specification and storage type and specification. The actual available IOPS is subject to the result displayed on the OceanBase Cloud console. Note
At present, only instances purchased through Alibaba Cloud, Huawei Cloud, and AWS support viewing IOPS information.
In the Summary section, review your instance configurations and quantity, and then place the order.
After the standby instance is created, you can view the standby instance’s basic information, such as type, region, storage, tags, and status, on the instance list page.
Note
- For details on billing rules for the standby instance’s compute and storage resources, see Instance billing.
- Backup costs are based on the backup space used. For more details, see Backup billing.
- Cross-region traffic charges are free for a limited time during the feature promotion phase.
Related operations
After creating a standby instance, you can perform the following operations:
View basic information, performance metrics, and deployment topology for both primary and standby instances on the Overview page of primary and standby instances. For details, refer to Primary and standby instances' overview page.
Modify compute specifications, storage specifications, and nodes for both primary and standby instances. For details, refer to Scale instances.
View or modify parameters for both primary and standby instances on the Parameters page. For details, refer to Manage parameters.
Stop or start the primary instance, which will also stop or start the associated standby instance. For details, refer to Stop and restart instances. When the primary instance is stopped, all related standby instances are automatically stopped. Independent pausing of standby instances is not supported. When the primary instance is started, all related standby instances are automatically started. Independent starting of standby instances is not supported.
Configure alert rules for the standby instance. For details, refer to Create alert rules.
View performance metrics for both primary and standby instances on the Performance Monitoring page. For details, refer to Performance monitoring overview.
Perform backup, restore, immediate backup, and modify backup strategies for both primary and standby instances on the Backup and Restore page. For details, refer to Backup and restore. Backup costs are based on the backup space used. For more details, refer to Backup billing.
View load and health status for primary and standby instance tenants on the Diagnostics page. For details, refer to Diagnostics Optimization.
View the history of events for primary and standby instances on the Events page. For details, refer to Historical Events.