All Products
Search
Document Center

ApsaraDB for ClickHouse:Data restoration

Last Updated:Jan 30, 2026

You can restore data from a backup of an ApsaraDB for ClickHouse instance to a new ApsaraDB for ClickHouse instance.

Feature description

ApsaraDB for ClickHouse supports instance-level data restoration. Database-level and table-level restoration are not supported. When you restore data, all data from the source cluster's backup set is restored to a new instance, which is also called a cloned instance.

Prerequisites

  • For Community-compatible clusters:

    • The kernel version is 21.8 or later.

    • The storage type is PL0 ESSD, PL1 ESSD, PL2 ESSD, or PL3 ESSD.

    • The Tiered Storage of Hot and Cold Data feature is disabled for the cluster.

  • For Enterprise Edition clusters, the cluster version must be 24.10 or later.

Billing

You are charged for the new instance when you restore data to it.

Note

The new instance must be in the same region and have the same edition as the source cluster. For Community-compatible instances, the deployment mode and replica configuration must also be the same as those of the source cluster.

Procedure

  1. Log on to the ApsaraDB for ClickHouse console. In the upper-left corner of the page, select the region where your cluster is located.

  2. On the Clusters page, in the cluster list for the correct edition, click the ID of the destination cluster.

  3. In the navigation pane on the left, click Backup and Restoration.

  4. On the Backup and Restoration page, find the backup that you want to restore. In the Actions column, click Data Recovery.

  5. On the Clone Instance page, review the configuration of the source cluster and configure the cloned instance.

    Community Edition

    Parameter

    Description

    Cluster Type

    The type of the source cluster.

    Source Cluster for Cloning

    The ID of the source instance.

    Source Type for Cloning

    The data source type for the cloned cluster.

    Source Backup Set for Cloning

    The start time of the backup.

    Note

    This parameter is available only if the following conditions are met:

    • The Clone Source Type is set to backup set.

    • The Current Instance Kernel Version is not the latest version.

    Region

    The region where the cloned instance is located. By default, this is the same as the source cluster and cannot be changed.

    Zone

    The zone where the cloned instance is located.

    Network Type

    Only virtual private cloud (VPC) is supported. A VPC is an isolated network environment that provides high security.

    Virtual Private Cloud (VPC)

    The VPC where the cloned instance is located.

    vSwitch

    The vSwitch for the cloned instance.

    Current Instance Kernel Version

    If you set the Clone Source Type parameter to Backup Set, the value of this parameter is the Milvus version of the clone instance. By default, the Milvus version of the clone instance is the same as that of the source instance and cannot be changed.

    If you set Clone Source Type to Real-time Replica, the value is the kernel version of the source instance and cannot be changed.

    Destination Instance Kernel Version

    The kernel version of the cloned instance.

    Note

    This option is available only when Clone Source Type is set to Clone from real-time replica.

    Replica Configuration

    The number of replicas for the cloned instance. By default, this is the same as the source cluster and cannot be changed.

    • Dual-replica edition: Each node has two replicas. If one replica becomes unavailable, the other replica in the same shard can continue to provide service.

    • Single-replica edition: Each node has only one replica. If the replica becomes unavailable, the entire cluster becomes unavailable. The cluster can provide stable service only after the replica is fully recovered.

    Node Specifications

    The node specifications for the cloned instance.

    Number of Nodes

    The number of nodes for the cloned instance. By default, this is the same as the source cluster and cannot be changed.

    Storage Type

    The storage type for the cloned instance.

    • Enterprise SSD (ESSD): A high-performance disk based on the next-generation distributed block storage architecture. It provides high access efficiency. In terms of performance: PL3 ESSD > PL2 ESSD > PL1 ESSD > PL0 ESSD.

    • Ultra disk: A cost-effective disk that provides medium random read and write performance and high reliability.

    Encryption Type

    The encryption type for the cloned instance.

    • No encryption: Disks are not encrypted.

    • Disk encryption: The entire data disk is encrypted based on block storage. If you select disk encryption, you must also select an encryption key.

    Storage Space

    The storage space for the cloned instance. By default, this is the same as the source cluster and cannot be changed.

    Enterprise Edition

    Parameter

    Description

    Cluster Type

    The type of the source cluster.

    Source Cluster for Cloning

    The ID of the source instance.

    Source Type for Cloning

    The default value is Restore from Backup Set.

    Source Backup Set for Cloning

    The start time of the backup.

    Deployment Plan

    The deployment plan for the cloned cluster.

    Region

    The region where the cloned instance is located. By default, this is the same as the source cluster and cannot be changed.

    Zone

    The zone where the cloned instance is located.

    If the deployment plan is multi-zone, you must select three zones to deploy the cluster.

    Network Type

    Only virtual private cloud (VPC) is supported. A VPC is an isolated network environment that provides high security.

    Virtual Private Cloud (VPC)

    The VPC where the cloned instance is located.

    vSwitch

    The vSwitch for the cloned instance.

    Maximum CCUs

    The maximum number of ClickHouse Compute Units (CCUs) for the cloned instance.

    Minimum CCUs

    The minimum number of CPUs for the cloned instance.

  6. Click Buy Now.

After the instance is purchased, you can view the cloned instance on the Clusters page.

Note

The time required to create the cloned cluster is proportional to the data volume.