OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Best Practices

All Versions
  • Deploy
    • Configuration guide for read-write splitting in AP scenarios
    • Best practices for read-write splitting
  • Migrate
    • Data transfer solutions in OceanBase Database
    • Overview on data migration
    • Best practices for importing data files to OceanBase Database
    • Best practice for migrating data from other databases to OceanBase Database
    • Massive data migration strategy
    • Best practices for migrating data from MyCat to OceanBase Database
    • Best practices for migrating PostgreSQL to OceanBase MySQL-compatible mode
  • Route
    • ODP routing best practices
  • Table Design
    • Best practices for table design and index optimization
    • Best practices for creating indexes on large tables
    • Best practices for database development
  • Develop
    • Best practices for connecting Java applications to OceanBase Database
    • Best practices for integrating Spark Catalog with OceanBase Database
    • Best practices for achieving optimal performance in batch DML using JDBC and OBServer
    • Best practices for bulk data cleanup in OceanBase Database
    • Best practices for PDML processing in OceanBase Database
    • Best practices for hot tables in OceanBase Database
    • Best practices for auto-increment columns and sequences in OceanBase Database
  • Manage
    • Best practices for resource throttling
    • Best practices for data load balancing
    • Best practices for security certification
    • Best practices for access control
    • Best practices for data encryption
  • Diagnose
    • Best practices for log interpretation in common scenarios
    • Best practices for end-to-end tracing
    • Best practices for using obdiag to collect performance information
    • Best practices for using obdiag to collect diagnostic information of parallel and slow SQL statements
    • Best practices for troubleshooting OceanBase Database performance issues
  • Performance Tuning
    • Best practices for handling slow queries
    • Best practices for collecting statistics to generate an efficient execution plan
    • Best practices for updating hotspot rows
    • Best practices for large object storage performance
    • Best practices for semi-structured storage performance
    • Best practices for OceanBase materialized views
  • Cloud Database
    • Best practices for achieving high availability through cross-cloud active-active deployment
    • High availability through primary and standby databases across clouds
    • High host CPU usage
    • Best practices for read/write splitting in OceanBase Cloud

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Best Practices
  3. master

High availability through primary and standby databases across clouds

Last Updated:2026-10-13 12:45:10

Overview
Scenarios
Prerequisites
Procedure

OceanBase Cloud supports creating primary instances on Alibaba Cloud and standby instances on Huawei Cloud to implement primary and standby databases across clouds. This ensures that businesses can quickly switch to other cloud environments when a single cloud service provider or region fails, thereby ensuring high reliability and business continuity.

Overview

A cross-cloud primary-standby database allows you to create a standby instance of a database instance (primary database) in another cloud service provider and synchronize data to the standby instance.

A cross-cloud primary-standby database has the following characteristics:

  • Strong disaster recovery capability: Deploying the primary and standby databases in geographically separated regions can effectively mitigate regional disasters (such as natural disasters and data center failures). Even if the primary instance deployed in one cloud service provider fails, the standby instance deployed in another cloud service provider can quickly take over, reducing the impact on business continuity.

  • High service availability: Cross-cloud deployment reduces the risk of service interruptions caused by internal issues within a single cloud service provider, ensuring that you can quickly switch to a standby database in another cloud platform when a failure occurs, maintaining business continuity.

  • Compliance and data governance: For enterprises with specific regulatory requirements, cross-cloud deployment offers greater flexibility, helping them meet data sovereignty and compliance requirements in different countries or regions.

  • Cost-effectiveness: While cross-cloud deployment may increase management complexity and data synchronization costs, you can flexibly allocate resources across cloud service providers, achieving a better balance between cost and service quality.

Scenarios

A company is an internet retailer whose core business systems are based on databases, such as order management, customer management, and product inventory. To ensure high availability of business and address risks such as downtime and network failures on a single cloud platform, the company plans to build a cross-cloud primary-standby database architecture to meet high-reliability and low-latency business requirements. It also needs to support fast switching and strong data consistency to ensure that business operations can continue uninterrupted after a failure.

Prerequisites

  • At present, only instances purchased on the Alibaba Cloud console can be primary instances, and instances on Huawei Cloud can be standby instances.

  • At present, only transactional instances support cross-cloud primary-standby databases.

  • Only one standby instance can be created for a primary instance.

  • You have the project admin and instance admin permissions.

Procedure

  1. Create an Alibaba Cloud instance on the Alibaba Cloud console. For more information, see Purchase an instance.

    1. Log in to the OceanBase Cloud console. If you are creating an instance for the first time, click Go To Create.

    2. In the left-side navigation pane, click Instances.

    3. In the upper-right corner of the page, click Create Database Instance.

    4. Select the required information, such as the service type and instance type, and click Buy Now. Then, select Service Agreement and click Proceed to Checkout. After the payment is successful, view the instance in the instance list.

  2. Grant access permissions to the Alibaba Cloud account.

    1. Log in to the OceanBase Cloud console, and click the icon in the pop-up window to grant access permissions to the Alibaba Cloud account.

    2. Click Log in to Alibaba Cloud console to obtain the main account ID.

    3. Log in to the RAM console, and use an existing or newly created AccessKey. Save your AccessKey ID and AccessKey Secret, and enter them in the corresponding fields on the OceanBase Cloud console.

    4. Enter the AccessKey ID and AccessKey Secret in the pop-up window of the OceanBase Cloud console, and click OK.

  3. Create a Huawei Cloud standby instance. You can create a standby instance in the OceanBase Cloud console or through Huawei Cloud Market. This topic describes how to create a standby instance in the OceanBase Cloud console. For more information, see Create a standby instance for an Alibaba Cloud primary instance.

    1. Click Create Alibaba Cloud Standby Instance. In the pop-up window, select the primary instance for which you want to create a standby instance.

    2. Click Create Standby Instance. The Create Instance page appears. The system automatically selects the same database version, deployment mode, and computing specification for the standby instance as for the primary instance.

      • The standby instance must have the same instance type, payment method, database version, and deployment mode as the primary instance.

      • The standby instance can have a different computing specification from the primary instance. The minimum node specification for the standby instance cannot be less than 0.33 times the node specification of the primary instance.

      • The storage specification for the standby instance cannot be less than that of the primary instance.

    3. Check whether your parameter configurations and purchase quantity are correct. After the check, select the service agreement and click Confirm Order. The instance list page appears, where you can view your instance.

  4. After the primary and standby instances are created, create a tenant in the primary instance and import data into the tenant. The standby instance automatically synchronizes data from the primary instance.

Previous topic

Best practices for achieving high availability through cross-cloud active-active deployment
Last

Next topic

High host CPU usage
Next
on this page
Overview
Scenarios
Prerequisites
Procedure