All Products
Search
Document Center

ApsaraDB for OceanBase:Create a standby instance

Last Updated:Aug 29, 2023

This topic describes how to create and purchase a standby instance, and the limits of using the standby instance.

Prerequisites

You have created a cluster instance. For more information, see Purchase an instance.

Procedure

  1. Log on to the ApsaraDB for OceanBase console.

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

Instances
  1. Find the target cluster instance in the Instances list, click More in the Actions column, and then select Create Standby Instance to go to the purchase page.

    Note

    • At present, the standby instance is available only to whitelisted customers. To purchase standby instance, contact ApsaraDB for OceanBase Technical Support.

    • You can add a standby instance only for a cluster instance in the Running state. In addition, you cannot add standby instances to a standby instance in cascading mode. At present, you can add up to two standby instances for a primary cluster instance. To add more standby instances, submit a ticket to OceanBase Technical Support.

  2. By default, the Billing Method of the standby instance is the same as that of the primary instance. You must specify the following parameters for the standby instance: Instance Type, Series, Region, Deployment Method, Zone, Node Specifications, Nodes, Storage Type, Storage Size, OceanBase Version, Quantity, and Duration.

    Parameter

    Description

    Instance Type

    The standby instance must be a cluster instance.

    Series

    The value must be the same as that of the primary instance. Valid values: Standard Edition (Cloud Disk) and Standard Edition (Local Disk).

    Region

    The region of the standby instance can be different from that of the primary instance.

    • Valid values: China (Hangzhou), China (Shanghai), China (Zhangjiakou), and China (Shenzhen).

    • You cannot change the region after you confirm your order.

    Deployment Method

    The value must be the same as that of the primary instance.

    Zone

    The value can be different from that of the primary instance.

    Node Specifications

    The node specifications of the standby instance cannot be smaller than that of the primary instance.

    Nodes

    Default value: 3.

    Storage Type

    The value can be different from that of the primary instance.

    Storage Size

    The storage size of the standby instance cannot be smaller than that of the primary instance.

    OceanBase Version

    The value must be the same as that of the primary instance. Only OceanBase Database V3.x is supported.

    Quantity

    Default value: 1.

    Duration

    You can set the duration based on your business needs. We recommend that you set it in such a manner that the backup instance expires on a date that is close to the expiration date of the primary instance.

  3. Click Buy Now.

  4. Agree to the Terms of Service and click Pay.

  5. After you make the payment, you can view the created standby instance in the instances list.

    Note

    You must separately maintain the instance specifications and tenant specifications of the primary and standby instances. We recommend that you keep the instance specifications and tenant specifications of the standby instance the same as those of the primary instance to prevent high latency of data replication.

    After you create the standby instance, the standby instance automatically synchronizes the DDL operations on the primary instance and creates the tenants, tables, partitions, and accounts. You cannot perform DDL operations on a standby instance.

Follow-up steps

  1. On the Instances page, you can view details of the standby instance, such as its type, series, zone, specifications, storage space, billing method, tag, and status.

  2. Click the name of the standby instance. In the standby cluster instance workspace, you can click the More icon in the upper-right corner to perform operations such as switching the standby instance to the primary instance, adding nodes to or removing nodes from the standby instance, and increasing the capacity of the standby instance.

    Note

    You can perform the preceding operations only when the standby instance is in the Running state.

    Create a standby instance
  3. You must manually add the primary address for each tenant in the standby cluster instance. For more information, see Add the primary address for a tenant in a standby instance. By default, the primary address of a standby instance only supports data reads. Before the primary address is created, data reads are not supported.

Limits

You cannot perform the following operations on a standby cluster instance:

  • Create or delete a tenant. The data of the primary cluster instance is synchronized to the standby cluster instance.

  • Create or delete a database or account, or log on to a database. The data of the primary cluster instance is synchronized to the standby cluster instance.

  • Modify parameters. The data of the primary cluster instance is synchronized to the standby cluster instance. However, when a standby instance is created, the modified parameters of the primary instance are not synchronized. Parameter modifications made after the primary and standby instances are associated are automatically synchronized to the standby instance.

  • Enable the transaction log service.

  • Backup and recovery operations.