Rebuilding a GaussDB Instance

Scenarios

When you delete an instance, the system automatically creates a full backup and stores it in the recycle bin. Within the retention period, you can restore (also known as rebuild in this context) this instance by creating a new instance using the backup file. However, note that the restored instance will have a different private IP address from the original one.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > GaussDB.
4. In the navigation pane on the left, choose Recycle Bin.
5. Locate the instance to be rebuilt and click Rebuild in the Operation column.
   Figure 1 Rebuilding an instance
   

6. On the displayed page, configure required parameters and submit the task.
   Figure 2 Billing mode and basic information
   

   Table 1 Basic information

   Parameter	Description
   Billing Mode	GaussDB provides yearly/monthly billing and pay-per-use billing. Yearly/Monthly: You pay upfront for the amount of time you expect to use the DB instance for. You will need to make sure you have a top-up account with a sufficient balance or have a valid payment method configured first. For distributed instances using the combined deployment model, yearly/monthly billing is only available to authorized users. To apply for the permissions needed, submit a service ticket. Pay-per-use: You can start using the DB instance first and then pay as you go. Pricing is listed on a per-hour basis, but bills are calculated based on the actual usage duration.
   DB Instance Name	The instance name is case-sensitive, must start with a letter, and can contain 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
   Failover Priority	This parameter is only available for distributed instances. This parameter is only available for authorized users. To apply for the permissions needed, submit a service ticket. The default value is Reliability. For details about how to change the failover priority for an existing instance, see Changing Failover Priority. Reliability: Data consistency is prioritized during a failover. This is recommended for applications whose highest priority is data consistency. Availability: Database availability is given priority during a failover. This is recommended for applications that require their databases to provide uninterrupted online services. If Availability is selected, exercise caution when modifying the following database parameters. For details about how to modify parameters, see Modifying Instance Parameters. recovery_time_target: If the value of this parameter is changed, the instance will experience frequent forced failovers. Contact technical support before modifying this parameter. audit_system_object: If the value of this parameter is changed, DDL audit logs will be lost. Contact technical support before modifying this parameter.
   AZ	An AZ is a physical region where resources have their own independent power supply and networks. AZs are physically isolated but interconnected through an internal network. A DB instance can be deployed in one AZ or three AZs. Three AZs are recommended. To deploy a GaussDB instance in Intelligent EdgeCloud (IEC), select an IEC HomeZones for AZ. For assistance with this setup, submit a service ticket to contact Huawei engineers.
   Time Zone	Select a time zone according to the region hosting your DB instance when you buy the instance.

   Figure 3 Specifications and storage
   

   Table 2 Specifications and storage

   Parameter	Description
   Instance Specifications	CPU and memory specifications of the instance. Different instance specifications support different numbers of database connections. For details, see Instance Specifications.
   Storage Space	The allocated storage space contains necessary file system overhead required for inodes, reserved blocks, and database operations. The storage for a single shard starts from 40 GB and can be increased at a step of 4 GB.
   Disk Encryption	Disable: Encryption is disabled. Enable: Encryption is enabled, which improves data security but affects system performance. Key Name: If disk encryption is enabled, you need to select or create a key. NOTE: When creating a pay-per-use instance with disk encryption enabled, ensure that your account has been granted the following action: kms:cmk:createGrant When you create a yearly/monthly instance with disk encryption enabled, if the KMS key shared by RAM is used for the first time, create an agency as prompted. When using the KMS key shared by RAM to create an instance, ensure that your account has also been granted the following actions: iam:agencies:listAgencies iam:agencies:createAgency iam:roles:listRoles iam:permissions:listRolesForAgency iam:permissions:grantRoleToAgency kms:cmk:createGrant If a shared KMS key is used, the corresponding CTS event is createGrant. Only the key owner can receive this event.

   Figure 4 Network and database configuration
   

   Table 3 Network and database configuration

   Parameter	Description
   VPC	A virtual network where your GaussDB instances are located. A VPC isolates networks for different workloads. You need to create or select the required VPC. If no VPC is available, GaussDB allocates a default VPC for you. After the GaussDB instance is created, the VPC cannot be changed. For details about how to create a VPC, see Creating a VPC. With VPC sharing, you can also use a VPC and subnet shared by another account. VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM). This allows for more efficient use of network resources and reduces O&M costs. For more information about VPC subnet sharing, see VPC Sharing in the Virtual Private Cloud User Guide.
   Subnet	A subnet provides dedicated network resources that are logically isolated from other networks for network security. Subnets take effect only within a specific AZ. Dynamic Host Configuration Protocol (DHCP) is enabled by default for subnets in which you plan to create GaussDB instances and cannot be disabled. GaussDB supports automatic IP address allocation during instance creation. If an IEC HomeZones is selected for AZ, create a subnet in that zone for this parameter. NOTE: By default, a subnet supports up to 256 IP addresses. A distributed instance can require up to 1,286 IP addresses. You are advised to use a subnet that can provide 2,048 IP addresses.
   Security Group	Controls access to and from an instance. When you buy an instance, the selected security group must meet the following requirements: When buying a distributed instance, ensure that the TCP ports in the inbound rule include the following: 40000-60480, 20050, 5000-5001, 2379-2380, 6000, 6001, 6500, and <database_port>-(<database_port> + 100). (For example, if the database port is 8000, the security group must contain ports 8000 to 8100.) Additionally, ensure that the outbound security group rules allow all outbound traffic. When buying a centralized instance, ensure that the TCP ports in the inbound rule include the following: 20050, 5000-5001, 2379-2380, 6000, 6500, and <database_port>-(<database_port> + 100). (For example, if the database port is 8000, the TCP ports for the security group must include 8000-8100.) The security group enhances security by controlling access to GaussDB from other services. Ensure that the security group you selected allows your client to access the instance. If you do not need to specify a security group when creating an instance, you can submit a service ticket. If no security group is available, GaussDB allocates a default security group for you.
   Database Port	The port is used by applications to access the database. Value range: 1024 to 39989. Default value: 8000. The following ports are used by the system and cannot be used: 2378 to 2380, 2400, 4999 to 5001, 5100, 5500, 5999 to 6001, 6009 to 6010, 6500, 8015, 8097, 8098, 8181, 9090, 9100, 9180, 9187, 9200, 12016, 12017, 20049, 20050, 21731, 21732, 32122 to 32126, and 39001.
   Single Private IP Address	Specifies whether to enable the single private IP address policy. If this policy is enabled, only one private IP address is assigned to an instance and is bound to the primary node. The private IP address does not change after a primary/standby switchover. If this policy is disabled, each node is bound to a private IP address, and the private IP address changes after a primary/standby switchover. The constraints on the single private IP address policy are as follows: This policy is only available for centralized instances of version V2.0-3.207 or later. This policy is configurable only at the time of instance creation and cannot be changed afterward.

   Figure 5 Database configuration
   

   Table 4 Database configuration

   Parameter	Description
   Administrator	Database administrator. The default username is root.
   Administrator Password	Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking. The password must contain: 8 to 32 characters. At least three types of the following: uppercase letters, lowercase letters, digits, and special characters. Supported special characters: ~!@#%^*-_=+?, Keep the password secure. Password retrieval is not supported.
   Confirm Password	Enter the administrator password again.
   Parameter Template	A template of parameters for creating an instance. The template contains engine configuration values that are applied to one or more instances. After creating an instance, you can modify the parameter template.
   Enterprise Project	If the instance has been associated with an enterprise project, select the target project from the Enterprise Project drop-down list. You can also go to the Enterprise Project Management console to create a project. For details, see Enterprise Management User Guide.
   Tag	This parameter is optional. Adding tags helps you better identify and manage your DB instances. Each instance can have up to 20 tags. If your organization has configured tag policies for GaussDB, add tags to instances based on the policies. If a tag does not comply with the policies, instance creation may fail. Contact your organization administrator to learn more about tag policies.

7. After the rebuilding task is submitted, check the instance status on the Instances page. The rebuild is complete when the status shows Available.