ApsaraDB for OceanBase:Purchase an instance

Background information

You can create and manage instances in the ApsaraDB for OceanBase console. By default, an instance consists of three zones, all of which provide read and write services. When you purchase a cluster instance, a backup and restore order is generated. For more information, see Billing for backup and restore.

Prerequisites

You have registered an Alibaba Cloud account.

For more information, see Create an account.

Procedure

1. Log on to the ApsaraDB for OceanBase console.

   If this is your first time creating an instance, click Create Now as prompted.

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

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

4. Select a billing method. You can select Subscription or Pay-as-you-go as needed.

   • Subscription: You must pay for an instance when you create it. This billing method is more favorable than the pay-as-you-go billing method and therefore applies to long-term requirements. A longer term indicates a higher discount.

   • Pay-as-you-go: The fees are charged on an hourly basis and are postpaid. This billing method applies to short-term requirements. To reduce costs, you can release the instance immediately when the instance is no longer needed.

5. After you select a billing method, specify other parameters such as Instance Type, Series, Region, Deployment Method, Zone, CPU Architecture, Node Specifications, Nodes, Storage Type, Storage Size, Isolation Optimization, Resource Group, OceanBase Version, Quantity, and Duration.

   Note

   If you select Tenant Instance for Instance Type, you must also specify information about the tenant instance, such as the virtual private cloud (VPC) ID, primary zone, vSwitch ID, service-linked role, character set, and time zone.

   Parameter	Description
   Instance Type	The type of the ApsaraDB for OceanBase instance that you want to purchase. The service level agreement (SLA) for a cluster instance is different from that for a tenant instance. For more information about the differences, see Pricing. If you select Billing Method as Subscription or Pay-as-you-go, the available instance types are as follows: Cluster Instance Tenant Instance (MySQL) Tenant Instance (Oracle)
   Series	Standard Edition (Cloud Disk): We recommend that you use this high-availability instance series. It supports the widest range of specifications and deployment solutions and is applicable to more scenarios. Standard Edition (Local Disk): This instance series is much the same as the high-availability instance series, except that local SSDs are used for storage. It applies to scenarios that require high stability. Standard Edition (History Database): This instance series is much the same as the high-availability instance series, except that HDDs are used for storage. It applies to scenarios where a large amount of archived data is infrequently accessed. Standard Edition (Key-Value): This series adopts the multi-model architecture of OceanBase Database and supports No-SQL. Note If you select Tenant Instance for Instance Type, you can purchase only the Standard Edition (Cloud Disk) series. At present, the Standard Edition (Key-Value) series is available only for customers on the allowlist. To purchase this series, contact ApsaraDB for OceanBase Technical Support. ApsaraDB for OceanBase also allows you to create information technology application innovation industry (ITAI) clusters. This feature is available only for customers on the allowlist.
   Region	The geographical location where the instance resides. To accelerate the access, we recommend that you select a region that is geographically close to your location. You cannot change the region after you confirm your order.
   Deployment Method	Multi-IDC Deployment: It is a multi-zone deployment plan in which the primary and standby nodes are located in different zones for disaster recovery. This does not incur additional charges. By default, three zones are selected. Dual-IDC Deployment: Two nodes are deployed in two zones. A log node is deployed in a third zone. This node is used only for log synchronization and does not provide read or write services. Dual-IDC deployment provides the same availability as multi-IDC deployment, and is more cost-effective. Single-IDC Deployment: All nodes are deployed in the same zone. Note The available deployment solutions vary with the region. For more information, see Pricing. Standard Edition (Key-Value) supports dual-IDC deployment and single-IDC deployment. If you select Tenant Instance for Instance Type, only single-IDC deployment is supported.
   Zone	If you choose the multi-IDC deployment solution, you can deploy three nodes in three different zones to achieve zone-level disaster recovery. This does not incur additional charges. If you choose the dual-IDC deployment solution, you can deploy two nodes in any two zones. If you choose the single-IDC deployment solution, you can deploy all nodes in any single zone.
   CPU Architecture	The CPU architecture of the instance to purchase. Note If you need to purchase instances of the Arm architecture, contact ApsaraDB for OceanBase Technical Support. If you plan to deploy Arm architecture-based server models in Beijing, Hangzhou, Shanghai, Zhangjiakou, and Shenzhen, the version of OceanBase Database must be V4.x. At present, the node specifications supported by the Arm architecture are 8C32G, 16C70G, and 32C180G. The Arm architecture supports only the ESSD PL1 storage type. For tenant instances, only the x86 architecture is supported.
   Specification Type	Two specification types are supported: Exclusive and General. For more information about specifications, see Pricing. Note The general specification type is a allowlist feature. If you need to use this specification type, contact ApsaraDB for OceanBase Technical Support. At present, only cluster instances of the Standard Edition (Cloud Disk) series support the general specification type.
   Node Specifications	Nodes in a cluster instance use exclusive resources or share resources, and nodes in a tenant instance share resources. The node specifications specify the CPU and memory resources allocated to the instance. The specifications for sale vary based on the series. For more information, see Specifications for sale.
   Nodes	An instance contains one primary node and two standby nodes. The number of visible nodes varies according to the deployment solution. The multi-IDC deployment solution provides three data nodes, which are all visible. The dual-IDC or single-IDC deployment solution provides two data nodes and one log node, of which the log node is invisible. Note The deletion of a node will trigger data migration and primary zone switching of the tenant, thereby extending the response time of requests and causing connection interruptions. Therefore, we recommend that you delete a node during off-peak hours.
   Storage Type	Two storage types, ESSD PL1 and ESSD PL0, are supported. The ESSD PL1 storage type is recommended and used by default. The ESSD PL0 storage type is a cost-effective option. Note At present, the ESSD PL0 cloud disk is being tested by invited users and is not publicly available.
   Storage Size	The maximum storage capacity varies based on the node specifications. To increase the capacity, submit a ticket.
   Resource Group	A resource group is a container that manages all resources under an Alibaba Cloud account. A resource can only be managed in one resource group. You can map a resource group to a project, application, or organization in different business scenarios. For more information, see Classify resources into resource groups and grant permissions on the resource groups.
   Isolation Optimization	Choose whether to enable inter-tenant resource isolation (cgroup). At present, only CPU resource isolation is supported. If resource isolation is disabled, each tenant has an independent thread pool to isolate CPU resources. If resource isolation is enabled, the threads of a tenant are added to the corresponding cgroup directory. The cgroup system will restrict the CPU utilization of these threads, thereby implementing CPU resource isolation. Note At present, the resource isolation feature is available only for customers on the allowlist. To enable this feature, contact ApsaraDB for OceanBase Technical Support. The 4C and 8C specifications of Standard Edition (Cloud Disk) do not support this feature. The general specification type does not support this feature. OceanBase Database V3.2.4.1 and later support this feature. We recommend that you enable this feature in the case of SaaS or TP/AP isolation, or if the cluster demands business isolation. We recommend that you do not enable this feature if only one tenant exists, or the business of different tenants is associated or depends on each other.
   VPC ID	The ID of the VPC that is used to access the business resources of the instance. You can select a VPC automatically created by the system. You can also manually create a VPC. To do so, click Create VPC. For more information, see related Overview of VPCs and vSwitches. This parameter is required if Tenant Instance is selected for Instance Type.
   Primary Zone	The ID of the primary zone to which the instance belongs. This parameter is required if Tenant Instance is selected for Instance Type.
   vSwitch	The ID of the vSwitch that is used to access the business resources of the instance. You can select a vSwitch automatically created by the system. You can also manually create a vSwitch. To do so, click Create vSwitch. For more information, see related Create and manage a vSwitch. This parameter is required if Tenant Instance is selected for Instance Type.
   AliyunServiceRoleForOceanBaseEncryption	The role that you use to create the tenant instance. You must also use this role to access your resources in the VPC and purchase an ApsaraDB for OceanBase tenant instance. For more information, see AliyunServiceRoleForOceanBaseEncryption. This parameter is required if Tenant Instance is selected for Instance Type.
   Character Set	The character set used by the tenant instance. This parameter is required if Tenant Instance is selected for Instance Type.
   Time Zone	The time zone of the tenant instance. This parameter is required if Tenant Instance is selected for Instance Type.
   OceanBase Version	The OceanBase Database version of the instance. At present, the general specification type of the Standard Edition (Cloud Disk) series only supports OceanBase Database 4.2.1.4.
   Full-featured Replicas	The number of full-featured replicas in the purchased instance. Note In the multi-IDC deployment solution, three full-featured replicas are used. The computing and storage resources are equally distributed across the three replicas. In the dual-IDC deployment solution, two full-featured replicas and one log replica are used. The log replica is not displayed in the topology. In the single-IDC deployment solution, two full-featured replicas are used for a tenant instance and three or two, depending on your choice, full-featured replicas are used for a cluster instance.
   Automatic Upgrade	Specifies whether to enable automatic upgrade of minor versions. Enable Automatic Upgrade of Minor Versions Disable Automatic Upgrade After this feature is enabled, the system will provide you with automatic upgrade of minor versions without affecting your business.
   Backup Strategy for Releasing Instance	Specifies whether to retain full backups when the instance is released. If you choose to retain the last full backup set and a restorable period exists, the instance will be moved to the instance recycle bin after being released. If you choose not to retain backups or no restorable period exists, the instance will not be moved to the instance recycle bin after being released. You can modify this parameter later in the backup strategy. For more information, see Backup strategies. If you choose to retain full backups, fees will be incurred. For more information, see Billing for backup and restore.
   Quantity	The number of instances to purchase.
   Duration	The validity period of the instance, in months. This parameter is required for a subscription instance. You can enable automatic renewal. The renewed term is the same as the subscription term.

6. Click Buy Now.

7. Select I have read and agree to the OceanBase subscription service agreement and click Pay Now.

8. After you have made the payment, you can view the created instance in the instance list.

What to do next

1. In the instance list, you can view information such as the instance name or ID, instance type, series, zone, specifications, storage space, billing mode, tags, and status.

2. For a cluster instance, you can click More in the Actions column to create a standby instance, perform standard or temporary configuration modification, change the billing mode, or renew or release the instance. The operations supported vary based on the instance type and billing mode.