AnalyticDB for PostgreSQL:Restore data

Usage notes

• The availability of restore points in time is determined by whether the mechanism of proactively discarding xlog archiving is triggered for instance nodes. For more information about the mechanism of proactively discarding xlog archiving, see the description of log backup in the "How it works" section of the "Overview" topic.

• Before you restore data, make sure that during the period from the end time of the previous full backup to the desired restore point in time, the mechanism of proactively discarding xlog archiving is not triggered for all nodes in the source instance.

  To confirm the availability of the desired restore point in time, submit a ticket.

• The source and destination instances must be in elastic storage mode.

• The source and destination instances must reside within the same region.

• The storage capacity of the destination instance must be greater than or equal to that of the source instance.

• The amount of time that is consumed by instance data restoration varies based on the volume of data that is stored in the source instance. In most cases, the data of an instance is restored within a few hours.

Procedure

1. Log on to the AnalyticDB for PostgreSQL console.
2. In the upper-left corner of the console, select a region.
3. Find the instance that you want to manage and click the instance ID.
4. In the left-side navigation pane, click Backup and Restoration.

5. Click the Data Backup tab. Find a backup that you want to use to restore data and click Restore in the Actions column.

   

6. On the Clone Instance page, configure the parameters. The following table describes the parameters.

   Parameter	Description
   Source Instance	The source instance whose data you want to restore.
   Restore Mode	The mode that is used to restore data. It is automatically set to Backup Set.
   Backup Set	The point in time to which you want to restore data.
   Region	The region in which you want to clone the instance. It is automatically set to the region in which the source instance resides.
   Zone	The zone in which you want to clone the instance.
   Network Type	The network type of the destination instance. It is automatically set to VPC.
   VPC.	The ID of the virtual private cloud (VPC).
   vSwitch	The vSwitch in the specified VPC.
   Instance Resource Type	The resource type of the destination instance. It is automatically set to Elastic Storage Mode.
   Edition	The edition of the destination instance. Set the edition to High Performance (Basic Edition) or High-availability based on your business requirements. Basic Edition is available only in specific regions and zones. For more information, see the "Scope" section of the "[Notice] AnalyticDB for PostgreSQL Basic Edition Released" topic. For more information about Basic Edition, see High-performance Edition.
   Engine Version	The engine version of the destination instance. It must be the same as the engine version of the source instance.
   Coordinator Node Resources	The coordinator node resources of the destination instance. The specifications of coordinator nodes must be greater than or equal to those of compute nodes. For more information, see Manage coordinator node resources.
   Compute Node Specifications	The specifications of compute nodes in the destination instance.
   Nodes	The number of compute nodes in the destination instance.
   Single Node Storage Capacity	The storage capacity per compute node in the destination instance. The total storage capacity of compute nodes in the destination instance must be greater than or equal to that in the source instance.
   Storage Disk Type	The disk type. Valid values: PL1 ESSD (Recommended) PL0 ESSD PL2 ESSD (High-throughput) For more information, see Change the disk storage type.
   Encryption Type	The encryption type. If you set the encryption type to Disk Encryption, you must also specify CMK.

7. Read and select the Terms of Service.

8. Click Buy Now.

   Note

   A new instance is created with the data of the source instance restored. The amount of time that is consumed by instance data restoration varies based on the volume of data that is stored in the source instance. In most cases, the data of an instance is restored within a few hours.