Create a cross-cloud standby instance

This topic describes how to create a cross-cloud standby instance.

Limitations

• The primary and standby instances are deployed in the Shared Nothing Architecture.

• The standby instance must be of the same instance type, billing method, database version, and deployment mode as the primary instance.

• The standby instance can have a different compute specification. 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 must be at least the same as that of the primary instance.

• The database version must be V4.2.5.4 or later to create multiple standby instances (up to 3) for a primary instance. For V4.x or later, you can create a single cross-cloud standby instance.

• You have the project owner or project admin role in the current OceanBase Cloud account.

Procedure

1. Log in to the OceanBase Cloud console.

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

3. In the instance list, find the target instance, click the "..." icon next to the instance name, and select Create Standby Instance.

4. In the dialog box that appears, select the project that the standby instance belongs to and click Create Standby Instance.

5. On the order page, select the instance specifications:

   Parameter	Description
   Instance Type	Transactional
   Cloud Vendor	Select the cloud vendor.
   Region	To reduce network latency and improve access speed, we recommend that you select a region close to your business.
   Instance Name	You can customize the name of the standby instance. The name must be 2 to 64 characters in length and can contain letters, digits, Chinese characters, underscores, and hyphens.
   Version	The database version must be V4.x or later to create a cross-cloud standby instance. If you want to create multiple standby instances (up to 3) for a primary instance, the database version must be V4.2.5.4 or later.
   Deployment Mode	The same as that of the primary instance.
   Zone	You can click View Network Latency to view the network latency in different regions and select a suitable zone.
   Compute	The same as that of the primary instance.
   Storage	The same as that of the primary instance.
   Primary-Standby Instance Network Sync Method	You can select one of the following synchronization methods: Direct Network Connection: The primary instance transmits transaction logs (Redo logs) to the standby instance in real time over the network through the Log Transport Service. The standby instance applies the logs in real time through the Log Replay Service to synchronize data with the primary instance. This method has strong real-time synchronization capabilities and low latency, making it suitable for scenarios with high data synchronization requirements. It requires good network connectivity between the primary and standby instances. Log Archiving: The primary instance archives transaction logs to an object storage service (such as OSS). The standby instance reads the archived logs from the object storage service and applies them to synchronize data with the primary instance. This method uses an object storage service as a relay, making it less sensitive to network stability. It is suitable for scenarios with unstable cross-cloud networks or where you want to reduce network transmission costs. Compared to direct network connections, this method has slightly higher latency but lower costs. This method incurs primary-standby log synchronization traffic fees, which you can view on the billing page. If a standby instance already exists in the current cloud vendor, select the same synchronization method as the existing standby instance.

6. Specify the number of instances you want to create in the Quantity section.

7. In the Summary section, review the configurations and click Create Instance to complete the purchase.

After the creation is completed, you can navigate back to the Instances page to view the creation progress.