ApsaraDB for OceanBase:Purchase an instance

Background information

You can use the OceanBase console to create and manage instances. By default, an OceanBase Database instance includes three zones. All zones provide read and write services. When you purchase a cluster instance, a backup and recovery order is generated. For more information, see Pricing of backup and recovery.

Prerequisites

You have an Alibaba Cloud account and are logged on.

For more information, see Sign up for an Alibaba Cloud account.

Procedure

1. Log on to the OceanBase console.

   If you are creating an instance for the first time, click Create Now when prompted.

2. In the navigation pane on the left, click Instance List.

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

4. Select a billing method: Subscription or Pay-as-you-go.

   • Subscription: This is an upfront billing method where you pay for an instance at the time of creation. This method is ideal for long-term needs and is more cost-effective than pay-as-you-go. Longer subscription durations offer greater discounts.

   • Pay-as-you-go: This is a postpaid billing method where you are charged by the hour. This method is ideal for short-term needs. You can release an instance at any time to save costs.

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

   Note

   If you select Tenant Instance as the instance type, you must also specify information about the tenant instance, such as the VPC ID, primary zone, vSwitch ID, service-linked role, character set, and time zone.

   Configuration parameters	Description
   Instance Type	The type of the cloud product instance 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 set Product Type to Subscription or Pay-as-you-go, the following instance types are available: Cluster Instance Tenant Instance (MySQL) Tenant Instance (Oracle)
   Series	Standard Edition (Cloud Disk): A recommended high availability instance series. It supports the widest range of specifications and deployment solutions and is applicable to many scenarios. Standard Edition (Local Disk): A high availability instance series that uses local solid-state drives (SSDs) for storage. It is designed for scenarios that require high stability. Standard Edition (Archive Database): A high availability instance series that uses hard disk drives (HDDs) for storage. It is designed for archive database scenarios where a large amount of data is infrequently read. Standard Edition (Key-Value): A product series that uses the OceanBase multi-model database model and supports NoSQL. Note If you set Instance Type to Tenant Instance, you can only purchase the Standard Edition (Cloud Disk) series. Standard Edition (Key-Value) is currently available only to users on the whitelist. To purchase this series, contact OceanBase Technical Support. OceanBase also supports the creation of information technology application innovation (ITAI) clusters. This feature is currently available only to users on the whitelist.
   Region	The geographic location of the instance. To improve access speed, select a region that is close to your users. You cannot change the region after you purchase the instance.
   Deployment Mode	Multi-zone deployment: Primary and secondary nodes are in different zones for cross-zone disaster recovery. This mode is free of charge. By default, three zones are selected. Dual-zone deployment: Two nodes are deployed in two zones, and a log-only node is deployed in a third zone for log synchronization. This node does not provide read or write services. Dual-zone deployment provides the same availability as multi-zone deployment but is more cost-effective. Single-zone deployment: All nodes are in the same zone. Note The available deployment modes vary by region. For more information, see Pricing. Standard Edition (Key-Value) supports only dual-zone and single-zone deployment. If the instance type is Tenant Instance, only single-zone deployment is supported.
   Zone	In multi-zone deployment mode, you can deploy three nodes in three different zones to achieve cross-zone disaster recovery at no extra charge. In dual-zone deployment mode, you can deploy two nodes in any two zones. In single-zone deployment mode, you can deploy all nodes in any one zone.
   CPU architecture	The CPU architecture of the instance to purchase. Note To purchase an instance that uses the ARM architecture, contact OceanBase Technical Support to activate it. If you plan to deploy server models that use the ARM architecture in regions such as Beijing, Hangzhou, Shanghai, Zhangjiakou, and Shenzhen, OceanBase currently supports only V4.x database systems in these regions. The ARM-based models currently support the following node specifications: 8-core 32 GB, 16-core 70 GB, and 32-core 180 GB. The ARM-based models currently support only ESSD PL1 disks. If the instance type is Tenant Instance, only x86-based models are supported.
   Specification type	You can select Dedicated or General-purpose. For more information about the specifications, see Pricing. Note The General-purpose specification type is a feature available only to users on the whitelist. To use this specification type, contact OceanBase Technical Support. Currently, only cluster instances of the Standard Edition (Cloud Disk) series support the General-purpose specification type.
   Node specifications	Nodes of a cluster instance include dedicated and shared nodes. Nodes of a tenant instance are shared nodes. Node specifications represent the CPU and memory allocated to the instance. The available specifications vary by series. For more information, see Available specifications.
   Number of nodes	An instance contains one primary node and two secondary nodes. The number of visible nodes varies by deployment mode. In multi-zone deployment mode, all three data nodes are visible. In dual-zone and single-zone deployment modes, there are two data nodes and one log node. The log node is not visible. Note Deleting a node may trigger data migration and a primary tenant switchover. This can increase request latency or cause transient disconnections. Perform this operation during off-peak hours.
   Storage type	ESSD PL1 and ESSD PL0 disks are supported. ESSD PL1 is the recommended storage type. ESSD PL0 is the default, cost-effective storage class. Note The PL0 feature is currently in invitational preview and is not fully available. Please wait for its official release.
   Storage size	The storage space range varies for nodes of different specifications. Select a proper size based on your business needs. For more information, see the Product specifications document.
   Resource group	A container that manages a group of related resources under a single Alibaba Cloud account. A resource can belong to only one resource group. You can map resource groups to concepts such as projects, applications, or organizations based on your business scenarios. For more information, see Classify resources into resource groups and grant permissions on the resource groups.
   Isolation optimization	Specifies whether to enable resource isolation optimization (cgroup) between tenants. Currently, only CPU resource isolation is supported. Disabled: Each tenant has an independent thread pool to isolate CPU resources between tenants. Enabled: The threads of a tenant are added to the corresponding cgroup directory. The cgroup system limits the CPU utilization of these threads to achieve CPU resource isolation. Note The isolation optimization feature is currently available only to users on the whitelist. To enable this feature, contact OceanBase Technical Support. The 4C and 8C specifications of the Standard Edition (Cloud Disk) series do not support the isolation optimization feature. The General-purpose specification type does not support the isolation optimization feature. OceanBase Database V3.2.4.1 and later support the isolation optimization feature. Enable cgroup for scenarios such as Software as a Service (SaaS), transactional processing (TP)/analytical processing (AP) isolation, or strong business isolation within a purchased cluster. Do not enable cgroup for scenarios such as single-tenant deployments, or where tenants have related or dependent businesses.
   VPC	The virtual private cloud (VPC) to which the business resources that access the database instance belong. You can have the system automatically create a VPC. To create a VPC, click Create VPC. For more information, see VPCs and vSwitches. This parameter is required if the instance type is Tenant Instance.
   Primary zone	The primary zone of the tenant instance. This parameter is required if the instance type is Tenant Instance.
   VPC vSwitch	The vSwitch to which the business resources that access the database service belong. You can have the system automatically create a VPC vSwitch. To create a vSwitch, click Create vSwitch. For more information, see Work with vSwitches. This parameter is required if the instance type is Tenant Instance.
   Service-linked role	The service-linked role for creating a tenant instance. Use this role to access your resources in the VPC to purchase an OceanBase tenant instance. For more information, see OceanBase service-linked roles. This parameter is required. This parameter is required if the instance type is Tenant Instance.
   Character set	The character set used by the tenant instance. This parameter is required if the instance type is Tenant Instance.
   Time zone	The time zone of the tenant instance. This parameter is required if the instance type is Tenant Instance.
   Version	The OceanBase Database version of the instance to purchase. The General-purpose specification type of the Standard Edition (Cloud Disk) series currently supports only version 4.2.1.4.
   Number of full-featured replicas	The number of full-featured replicas in the purchased instance. Note In multi-zone deployment mode, the number of full-featured replicas is three. The computing and storage resources are equally distributed across the three replicas. In dual-zone deployment mode, the number of full-featured replicas is two. There are two full-featured replicas and one log replica. The log replica uses fewer storage resources than a full-featured replica and is not displayed in the topology diagram. In single-zone deployment mode, the number of full-featured replicas is two. You can select three if the instance type is Cluster Instance.
   Automatic upgrade	Specifies whether to enable automatic upgrades for minor versions. Enable automatic upgrade of minor versions Disable automatic upgrade If enabled, the cloud platform will automatically upgrade the minor version without affecting your services.
   Backup policy for instance release	Specifies whether to retain full backup files when the instance is released. If you choose to retain the last full backup set and a recoverable time range exists, the instance is moved to the recycle bin after it is released. If no recoverable time range exists, or if the retention policy is not to retain backups, the instance is not moved to the recycle bin after it is released. You can modify the backup policy later. For more information, see Backup policies. Retaining full backups incurs fees. For more information, see Billing for backup and recovery.
   Quantity	The number of instances to purchase.
   Subscription duration	For subscription instances, select the subscription duration in months. You can also enable auto-renewal. The auto-renewal cycle is the same as the subscription duration.

6. Click Buy Now.

7. Select the Terms of Service checkbox and click Proceed to Pay.

8. After the payment is successful, you can view the newly created instance in the instance list.

What to do next

1. On the Instance List page, you can view information such as Instance Name/ID, Instance Type, Series, Zone, Specifications, Storage Space, Billing Method, Tags, and Status.

2. For a cluster instance, click More in the Actions column. You can create a secondary instance, perform a standard or temporary specification change, change the billing method, or renew or release the instance. The available operations vary depending on the instance type and billing method.