2024-08-08
- Optimized the content in Backup Space and Billing.
Basic Concepts
-Understanding the following concepts helps you better use GaussDB(for MySQL):
-- Cluster: GaussDB(for MySQL) uses the cluster architecture, with one primary node and multiple read replicas.
- Region: A region is a physical data center. Generally, GaussDB(for MySQL) DB instances and ECSs must be located in the same region for high access performance.
- Availability zone (AZ): An AZ contains one or multiple physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple instances. An AZ is a geographic location with independent power supply and network facilities in a region.
AZs are physically isolated but interconnected over an intranet. Each AZ provides cost-effective and low-latency network connections that are unaffected by faults that may occur in other AZs. As a result, provisioning GaussDB(for MySQL) DB instances in separate AZs protects your applications against local faults that occur in a single location. AZs within the same region have no functional differences.
+Understanding the following concepts helps you better use GaussDB(for MySQL):
+- Cluster: GaussDB(for MySQL) uses the cluster architecture, with one primary node and multiple read replicas.
- Region: A region is a physical data center. Generally, GaussDB(for MySQL) instances and ECSs must be located in the same region for high access performance.
- Availability zone (AZ): An AZ contains one or multiple physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple instances. An AZ is a geographic location with independent power supply and network facilities in a region.
AZs are physically isolated but interconnected over an intranet. Each AZ provides cost-effective and low-latency network connections that are unaffected by faults that may occur in other AZs. As a result, provisioning GaussDB(for MySQL) instances in separate AZs protects your applications against local faults that occur in a single location. AZs within the same region have no functional differences.
- Instance class: resource configuration of each node, for example, 16 vCPUs and 64 GB.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_01_0002.html b/docs/gaussdb_mysql/umn/gaussdb_01_0002.html index cd80c219f..ff9e8f442 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_01_0002.html +++ b/docs/gaussdb_mysql/umn/gaussdb_01_0002.html @@ -1,9 +1,9 @@Product Benefits
-GaussDB(for MySQL) is an enterprise-class cloud database that uses a decoupled compute and storage architecture.
+GaussDB(for MySQL) is an enterprise-grade cloud database with decoupled compute and storage.
Requirements
-Table 1 Requirements Requirements
+Table 1 Requirements Requirement
Description
DB Instance Specifications
-GaussDB(for MySQL) instance specifications are listed in the following table and vary according to actual situations.
+GaussDB(for MySQL) instance specifications are listed in the following tables and vary according to actual situations.
-Table 1 x86 instance specifications Instance Specifications
+-Table 1 x86 instance specifications Instance Specifications
vCPUs
+vCPUs
Memory (GB)
Table 2 Kunpeng instance specifications Instance Specifications
+Table 2 Kunpeng instance specifications Instance Specifications
vCPUs
+vCPUs
Memory (GB)
DB Engines and Versions
-Table 1 lists the DB engines and versions supported by GaussDB(for MySQL).
+Table 1 lists the DB engines and versions supported by GaussDB(for MySQL).
Table 1 DB engines and versions DB Engine
Constraints
-Table 1 shows the constraints designed to ensure the stability and security of GaussDB(for MySQL).
+Table 1 shows the constraints designed to ensure the stability and security of GaussDB(for MySQL).
Table 1 Function constraints Function
GaussDB(for MySQL) access
+GaussDB(for MySQL) access
- If GaussDB(for MySQL) DB instances are not bound with EIPs, the DB instances must be in the same VPC subnet as the ECSs associated with these instances.
- Security group rules must be added to allow ECSs to access GaussDB(for MySQL) DB instances.
By default, a GaussDB(for MySQL) DB instance cannot be accessed by an ECS in a different security group. To allow it, you must add an inbound rule to the GaussDB(for MySQL) security group.
- - The default GaussDB(for MySQL) DB instance port is 3306. You can change it if you want to access GaussDB(for MySQL) through another port.
- If GaussDB(for MySQL) instances are not bound with EIPs, the instances must be in the same VPC subnet as the ECSs associated with these instances.
- Security group rules must be added to allow ECSs to access GaussDB(for MySQL) instances.
By default, a GaussDB(for MySQL) instance cannot be accessed by an ECS in a different security group. To allow it, you must add an inbound rule to the GaussDB(for MySQL) security group.
+ - The default GaussDB(for MySQL) instance port is 3306. You can change it if you want to access GaussDB(for MySQL) through another port.
Deployment
ECSs in which GaussDB(for MySQL) DB instances are deployed are not visible to users. You can access GaussDB(for MySQL) DB instances only over an IP address and a port.
+ECSs in which GaussDB(for MySQL) instances are deployed are not visible to users. You can access GaussDB(for MySQL) instances only over an IP address and a port.
Administrator root permission
@@ -27,22 +27,22 @@Database parameter modification
Most parameters can be modified on the GaussDB(for MySQL) console.
+Most parameters can be modified on the GaussDB(for MySQL) console.
Data migration
The mysqldump tool is used to migrate data to GaussDB(for MySQL).
+The mysqldump tool is used to migrate data to GaussDB(for MySQL).
GaussDB(for MySQL) instance reboot
+GaussDB(for MySQL) instance reboot
GaussDB(for MySQL) instances cannot be rebooted through commands. They must be rebooted on the GaussDB(for MySQL) console.
+GaussDB(for MySQL) instances cannot be rebooted through commands. They must be rebooted on the GaussDB(for MySQL) console.
GaussDB(for MySQL) backup files
+GaussDB(for MySQL) backup files
GaussDB(for MySQL) backup files are stored in OBS buckets and are not visible to users.
+GaussDB(for MySQL) backup files are stored in OBS buckets and are not visible to users.
Related Services
-The following figure shows the relationship between GaussDB(for MySQL) and other services.
+The following figure shows the relationship between GaussDB(for MySQL) and other services.
-Table 2 Specifications and storage Parameter
+-Table 2 Specifications and storage Parameter
Description
+Description
Nodes
GaussDB(for MySQL) supports one primary node and up to 15 read replicas. When you are creating a DB instance, a maximum of nine read replicas can be created at a time.
-After the DB instance is created, you can also create read replicas based on service requirements by referring to Creating a Read Replica.
+A GaussDB(for MySQL) instance supports one primary node and up to 15 read replicas. When you are creating a DB instance, a maximum of nine read replicas can be created at a time.
+After the DB instance is created, you can also create read replicas based on service requirements by referring to Creating Read Replicas.
Storage
@@ -74,16 +74,16 @@Table 3 Network Parameter
+-Table 3 Network Parameter
Description
+Description
VPC
A dedicated virtual network in which your DB instances are located. It isolates networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see "Creating a VPC" in the Virtual Private Cloud User Guide.
-If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.
+If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.
Subnet
@@ -94,15 +94,15 @@Security Group
Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.
-If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.
+Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.
+If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.
Table 4 Database configuration Parameter
+-Table 4 Database configuration Parameter
Description
Table 5 Parameter template Parameter
+Table 5 Parameter template Parameter
Description
+Description
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0005.html b/docs/gaussdb_mysql/umn/gaussdb_02_0005.html index 2d0e816ef..584666c09 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0005.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0005.html @@ -1,6 +1,6 @@ --Parent topic: Connecting to a DB instance Over a Private Network+Parent topic: Connecting to a DB Instance over a Private NetworkConnecting to a DB instance Over a Private Network
+Connecting to a DB Instance over a Private Network
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0006.html b/docs/gaussdb_mysql/umn/gaussdb_02_0006.html index 80e656076..e72b94f72 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0006.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0006.html @@ -6,14 +6,14 @@-
@@ -10,12 +10,12 @@
- Step 2: Configure Security Group Rules
- - Step 3: Connect to a DB Instance Over a Private Network
+ - Step 3: Connect to a DB Instance over a Private Network
-Parent topic: Getting Started with GaussDB(for MySQL)+Parent topic: Getting StartedProcess
Figure 1 illustrates the process of connecting to a DB instance over a private network.
-- Step 1: Create a DB instance. Confirm the specifications, storage, network, and database account configurations of the DB instance based on service requirements.
- Step 2: Configure security group rules.
- If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance Over a Private Network.
- If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
- DB instance: Configure an inbound rule for the security group to which the DB instance is associated.
- ECS: The default security group rule allows all outgoing data packets. In this scenario, you do not need to configure a security group rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.
- Step 1: Create a DB instance. Confirm the specifications, network, and database account configurations of the DB instance based on service requirements.
- Step 2: Configure security group rules.
- If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance over a Private Network.
- If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
- DB instance: Configure an inbound rule for the security group associated with the DB instance.
- ECS: The default security group rule allows all outgoing data packets. In this case, you do not need to configure a security group rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.
- Step 3: Connect to a DB instance over a private network. You can connect to the DB instance through a common connection, or an SSL connection for enhanced security. SSL connections are encrypted.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0008.html b/docs/gaussdb_mysql/umn/gaussdb_02_0008.html index f88a2fba1..5d558ccb4 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0008.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0008.html @@ -3,16 +3,16 @@-Parent topic: Connecting to a DB instance Over a Private Network+Parent topic: Connecting to a DB Instance over a Private NetworkStep 2: Configure Security Group Rules
Scenarios
A security group is a collection of access control rules for ECSs and DB instances that have the same security requirements and are mutually trusted in a VPC. To ensure database security and reliability, you need to configure security group rules to allow specific IP addresses and ports to access DB instances.
Check whether the ECS and DB instance are in the same security group.
-- If they are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance Over a Private Network.
- If they are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
- DB instance: Configure an inbound rule for the security group to which the DB instance is associated.
- ECS: The default security group rule allows all outgoing data packets. In this scenario, you do not need to configure a security rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.
- If they are in the same security group, they can communicate with each other by default. No security group rule needs to be configured. Go to Step 3: Connect to a DB Instance over a Private Network.
- If they are in different security groups, you need to configure security group rules for the ECS and DB instance, respectively.
- DB instance: Configure an inbound rule for the security group associated with the DB instance.
- ECS: The default security group rule allows all outgoing data packets. In this scenario, you do not need to configure a security rule for the ECS. If not all outbound traffic is allowed in the security group, you need to configure an outbound rule for the ECS.
-Precautions
The default security group rule allows all outgoing data packets. If an ECS and a DB instance are in the same security group, they can access each other. When a security group is created, you can configure security group rules to control access to and from DB instances in that security group.
- By default, you can create a maximum of 500 security group rules.
- To prevent high network latency for the first packet, you are advised to create a maximum of 50 rules for each security group.
- To access a DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the DB instance.
To ensure the security of your data and DB instances, you are advised to use the principle of least privilege for database access. Change the database port (default value: 3306), and set the IP address to the remote server's address or an IP address on the remote server's smallest subnet so that access to the remote server is limited.
-If you use 0.0.0.0/0, all IP addresses are enabled to access DB instances in the security group.
+The default value of Source is 0.0.0.0/0, indicating that GaussDB(for MySQL) instances in the security group can be accessed from any IP address.
Procedure
- Log in to the management console.
- Click
in the upper left corner and select a region and a project. - Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance.
- Configure security group rules.
In the Network Information area on the Basic Information page, click the security group.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the instance name to go to the Basic Information page.
- Configure security group rules.
In the Network Information area on the Basic Information page, click the security group.
- On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters and click OK.You can click + to add more inbound rules.
Table 1 Inbound rule parameter description Parameter
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0009.html b/docs/gaussdb_mysql/umn/gaussdb_02_0009.html index 99b9bc51a..59ee7d6e2 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0009.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0009.html @@ -1,7 +1,7 @@ --Parent topic: Connecting to a DB instance Over a Private Network+Parent topic: Connecting to a DB Instance over a Private NetworkStep 3: Connect to a DB Instance Over a Private Network
-GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection for enhanced security. SSL connections are encrypted.
+Step 3: Connect to a DB Instance over a Private Network
+GaussDB(for MySQL) is fully compatible with the MySQL protocol. You can connect to a DB instance through either a common connection or an SSL connection. SSL connections are encrypted.
Prerequisites
- Log in to the ECS.
For details on how to create and log in to an ECS, see "Creating an ECS" and "Logging In an ECS" in the Elastic Cloud Server User Guide.
- To connect to a DB instance through an ECS, you must ensure that:
- The ECS and DB instance are in the same VPC.
- The ECS must be allowed by the security group to access DB instances.
- If the security group with which the target DB instance associated is the default security group, you do not need to configure security group rules.
- If the security group with which the target DB instance associated is not the default security group, check whether the security group rules allow the ECS to connect to the DB instance. For details, see Step 2: Configure Security Group Rules.
If the security group rules allow the access from the ECS, the ECS can connect to the DB instance.
If the security group rules do not allow the access from the ECS, you need to add a security group rule. The ECS must be allowed by the security group to access DB instances.
@@ -9,7 +9,7 @@
- Use a database client to connect to the target DB instance.
You can use a database client to connect to the DB instance in the Linux or Windows OS.
-- In the Linux OS, install the MySQL client on the ECS or other device that can access the DB instance. It is recommended that you download a MySQL client running a version later than that of the DB instance.
For details about how to obtain and install the MySQL client, see How Can I Install the MySQL Client?
+- In the Linux OS, install the MySQL client on the device that can access GaussDB(for MySQL). It is recommended that you download a MySQL client running a version later than that of the DB instance.
For details about how to obtain and install the MySQL client, see How Can I Install the MySQL Client?
- In the Windows OS, you can use any common database client to connect to the DB instance in a similar way.
The database client MySQL-Front is used as an example in Using MySQL-Front to Connect to a DB Instance.
- In the Linux OS, install the MySQL client on the device that can access GaussDB(for MySQL). It is recommended that you download a MySQL client running a version later than that of the DB instance.
- In the Linux OS, install the MySQL client on the ECS or other device that can access the DB instance. It is recommended that you download a MySQL client running a version later than that of the DB instance.
Host
Private IP address for write of the target DB instance. To view the private address of the target DB instance, perform the following steps:- Log in to the GaussDB(for MySQL) console.
- Select the region in which the DB instance is located.
- Click the target DB instance to go to the Basic Information page.
- In the Network Information area, view the private IP address for write.
Private IP address for write of the target DB instance. To view the private address of the target DB instance, perform the following steps:- Log in to the GaussDB(for MySQL) console.
- Select the region in which the DB instance is located.
- Click the target DB instance to go to the Basic Information page.
- In the Network Information area, view the private IP address for write.
- In the displayed window, select the connection that you have created and click Open. If the connection information is correct, the DB instance is successfully connected.
-Figure 3 Opening a session
SSL Connection
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- In the DB Instance Information area on the Basic Information page, click
in the SSL field to download the root certificate or certificate bundle. - Import the root certificate to the Linux OS on the ECS.
For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
+SSL Connection
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- In the DB Instance Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
- Import the root certificate to the Linux OS on the ECS.
For details, see How Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?
- Connect to a DB instance. The Linux OS is assumed in this example.
mysql -h <hostName> -P <port> -u <userName> -p --ssl-ca=<caName>
-Table 2 Parameter description Parameter
@@ -79,7 +79,7 @@<userName>
Username of the GaussDB(for MySQL) administrator account. The default username is root.
+Username of the GaussDB(for MySQL) administrator account. The default username is root.
<caName>
@@ -99,7 +99,7 @@diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0010.html b/docs/gaussdb_mysql/umn/gaussdb_02_0010.html index f517c5344..c20073ad2 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0010.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0010.html @@ -1,6 +1,6 @@ --Parent topic: Connecting to a DB instance Over a Private Network+Parent topic: Connecting to a DB Instance over a Private NetworkConnecting to a DB Instance Over a Public Network
+Connecting to a DB Instance over a Public Network
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0012.html b/docs/gaussdb_mysql/umn/gaussdb_02_0012.html index 4670b3b31..e8d569418 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0012.html @@ -24,7 +24,7 @@-
@@ -12,12 +12,12 @@
- Step 3: Configure Security Group Rules
- - Step 4: Connect to a DB Instance Over a Public Network
+ - Step 4: Connect to a DB Instance over a Public Network
-Parent topic: Getting Started with GaussDB(for MySQL)+Parent topic: Getting StartedDB Engine
GaussDB(for MySQL)
+GaussDB(for MySQL)
DB Engine Version
@@ -47,9 +47,9 @@Table 2 Specifications and storage Parameter
+-Table 2 Specifications and storage Parameter
Description
+Description
Nodes
GaussDB(for MySQL) supports one primary node and up to 15 read replicas. When you are creating a DB instance, a maximum of nine read replicas can be created at a time.
-After the DB instance is created, you can also create read replicas based on service requirements by referring to Creating a Read Replica.
+A GaussDB(for MySQL) instance supports one primary node and up to 15 read replicas. When you are creating a DB instance, a maximum of nine read replicas can be created at a time.
+After the DB instance is created, you can also create read replicas based on service requirements by referring to Creating Read Replicas.
Storage
@@ -74,16 +74,16 @@Table 3 Network Parameter
+-Table 3 Network Parameter
Description
+Description
VPC
A dedicated virtual network in which your DB instances are located. It isolates networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see "Creating a VPC" in the Virtual Private Cloud User Guide.
-If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.
+If no VPC is available, GaussDB(for MySQL) allocates a VPC to you by default.
Subnet
@@ -94,15 +94,15 @@Security Group
Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.
-If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.
+Enhances security by controlling access to GaussDB(for MySQL) from other services. You need to add rules to a security group that enable you to connect to your DB instance.
+If no security group is available or has been created, GaussDB(for MySQL) allocates a security group to you by default.
Table 4 Database configuration Parameter
+-Table 4 Database configuration Parameter
Description
Table 5 Parameter template Parameter
+Table 5 Parameter template Parameter
Description
+Description
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0013.html b/docs/gaussdb_mysql/umn/gaussdb_02_0013.html index 18eaf48d5..252e1abb3 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0013.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0013.html @@ -8,10 +8,10 @@-Parent topic: Connecting to a DB Instance Over a Public Network+Parent topic: Connecting to a DB Instance over a Public Network-Precautions
The default security group rule allows all outgoing data packets. If an ECS and a DB instance are in the same security group, they can access each other. When a security group is created, you can configure security group rules to control access to and from DB instances in that security group.
- By default, you can create a maximum of 500 security group rules.
- To prevent high network latency for the first packet, you are advised to create a maximum of 50 rules for each security group.
- To access a DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the DB instance.
To ensure the security of your data and DB instances, you are advised to use the principle of least privilege for database access. Change the database port (default value: 3306), and set the IP address to the remote server's address or an IP address on the remote server's smallest subnet so that access to the remote server is limited.
-If you use 0.0.0.0/0, all IP addresses are enabled to access DB instances in the security group.
+The default value of Source is 0.0.0.0/0, indicating that GaussDB(for MySQL) instances in the security group can be accessed from any IP address.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instance Management page, click the target DB instance.
- Configure security group rules.
In the Network Information area on the Basic Information page, click the security group.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the instance name to go to the Basic Information page.
- Configure security group rules.
In the Network Information area on the Basic Information page, click the security group.
- On the Inbound Rules tab, click Add Rule. In the displayed dialog box, set required parameters and click OK.You can click + to add more inbound rules.
Table 1 Inbound rule parameter description Parameter
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0014.html b/docs/gaussdb_mysql/umn/gaussdb_02_0014.html index 78cabafbe..dc70d9f80 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0014.html @@ -1,7 +1,7 @@ --Parent topic: Connecting to a DB Instance Over a Public Network+Parent topic: Connecting to a DB Instance over a Public NetworkStep 4: Connect to a DB Instance Over a Public Network
-GaussDB(for MySQL) is fully compatible with the MySQL protocol. Therefore, you can connect to a DB instance through a common connection or an SSL connection. SSL connections are encrypted.
+Step 4: Connect to a DB Instance over a Public Network
+GaussDB(for MySQL) is fully compatible with the MySQL protocol. Therefore, you can connect to a DB instance through a common connection or an SSL connection. SSL connections are encrypted.
Prerequisites
- Bind an EIP to the target DB instance and configure security group rules.
- Bind an EIP to the target DB instance.
For details about how to bind an EIP, see Step 2: Bind an EIP.
- Obtain the IP address of the local device.
- Configure security group rules.
Add the IP address and port obtained in 1.b to the inbound rule of the security group.
For details about how to configure a security group rule, see Step 3: Configure Security Group Rules.
@@ -14,7 +14,7 @@
- Bind an EIP to the target DB instance.
Using MySQL-Front to Connect to a DB Instance
- Start MySQL-Front.
- In the displayed dialog box, click New.Figure 1 Connection management-
- Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2. +
- Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.
Table 1 Parameter description Parameter
Host
EIP bound to the target DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address (EIP) field in the Network Information area.
+EIP bound to the target DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address (EIP) field in the Network Information area.
Port
@@ -56,7 +56,7 @@ -Using SSL to Connect to a DB Instance
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- In the DB Instance Information area on the Basic Information page, click
in the SSL field to download the root certificate or certificate bundle. - Import the root certificate to the Linux OS on the ECS.
For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
+Using SSL to Connect to a DB Instance
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- In the DB Instance Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
- Import the root certificate to the Linux OS on the ECS.
For details, see How Do I Import the SSL Certificate of an RDS Instance to a Windows or Linux Server?
- Connect to a DB instance. The Linux OS is assumed in this example.mysql -h <hostName> -P <port> -u <userName> -p --ssl-ca=<caName>
Table 2 Parameter description Parameter
<hostName>
Host IP address of the target DB instance to be connected. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address (EIP) field in the Network Information area.
+Host IP address of the target DB instance to be connected. To obtain this parameter, go to the Basic Information page of the DB instance. The EIP can be found in the Public IP Address (EIP) field in the Network Information area.
<port>
@@ -76,7 +76,7 @@<userName>
Username of the GaussDB(for MySQL) database administrator account. The default username is root.
+Username of the GaussDB(for MySQL) administrator account. The default username is root.
<caName>
@@ -99,7 +99,7 @@diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html index 1fac6e8bb..a5810c51c 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0015.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0015.html @@ -3,9 +3,9 @@-Parent topic: Connecting to a DB Instance Over a Public Network+Parent topic: Connecting to a DB Instance over a Public NetworkStep 2: Bind an EIP
-Scenarios
You can bind an EIP to a DB instance for public access and can unbind the EIP from the DB instance if needed.
Precautions
- Public accessibility reduces the security of DB instances. Therefore, exercise caution when enabling this function. To achieve a higher transmission rate and security level, you are advised to migrate your applications to the ECS that is in the same region as the GaussDB(for MySQL) DB instance.
-Precautions
- Public accessibility reduces the security of DB instances. Therefore, exercise caution when enabling this function. To achieve a higher transmission rate and security level, you are advised to migrate your applications to the ECS that is in the same region as your DB instance.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance.
- In the Network Information area, click Bind in the Private IP Address field.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance. For details, see Step 3: Configure Security Group Rules.
+Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the instance name to go to the Basic Information page.
- In the Network Information area, click Bind next to Private IP Address.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance. For details, see Step 3: Configure Security Group Rules.
- On the EIPs page, view the EIP that has been bound to the DB instance.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_02_0016.html b/docs/gaussdb_mysql/umn/gaussdb_02_0016.html index 51cc849c0..e9a876d2d 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_02_0016.html +++ b/docs/gaussdb_mysql/umn/gaussdb_02_0016.html @@ -2,16 +2,16 @@-Parent topic: Connecting to a DB Instance Over a Public Network+Parent topic: Connecting to a DB Instance over a Public NetworkOverview
Scenarios
This section describes how to create a DB instance on the management console and bind an EIP to the DB instance to make the instance publicly accessible.
-If you are using GaussDB(for MySQL) for the first time, see Constraints.
+If you are using GaussDB(for MySQL) for the first time, see Constraints.
Process
Figure 1 illustrates the process of connecting to a DB instance over a public network.
-- Step 1: Create a DB instance. Confirm the specifications, storage, network, and database account configurations of the DB instance based on service requirements.
- Step 2: Bind an EIP. The Elastic IP service provides independent public IP addresses and bandwidth for public access. You can apply for an EIP on the VPC console and bind the EIP to the DB instance.
- Step 3: Configure security group rules. To access a DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the DB instance.
- Step 4: Connect to a DB instance over a public network. You can connect to a DB instance through a common connection, or an SSL connection for enhanced security. SSL connections are encrypted.
- Step 1: Create a DB instance. Confirm the specifications, network, and database account configurations of the DB instance based on service requirements.
- Step 2: Bind an EIP. The Elastic IP service provides independent public IP addresses and bandwidth for public access. You can apply for an EIP on the VPC console and bind the EIP to the DB instance.
- Step 3: Configure security group rules. To access a DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the DB instance.
- Step 4: Connect to a DB instance over a public network. You can connect to a DB instance through a common connection, or an SSL connection for enhanced security. SSL connections are encrypted.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0007.html b/docs/gaussdb_mysql/umn/gaussdb_03_0007.html index 4069c9d44..215725033 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0007.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0007.html @@ -1,19 +1,19 @@ --Parent topic: Connecting to a DB Instance Over a Public Network+Parent topic: Connecting to a DB Instance over a Public NetworkMigrating Data to GaussDB(for MySQL) Using mysqldump
-Preparing for Data Migration
GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through an ECS or EIP.
-- Prepare an ECS in the same VPC subnet as GaussDB(for MySQL) or prepare a device for accessing GaussDB(for MySQL) over a public network.
- To connect to a DB instance through an ECS, you must first create an ECS.
For details on how to create and log in to an ECS, see descriptions about creating an ECS and logging in an ECS in the Elastic Cloud Server User Guide.
+Migrating Data to GaussDB(for MySQL) Using mysqldump
+Preparing for Data Migration
GaussDB(for MySQL) supports public accessibility. You can access GaussDB(for MySQL) through an ECS or EIP.
+- Prepare an ECS in the same VPC subnet as the GaussDB(for MySQL) instance or bind an EIP to the GaussDB(for MySQL) instance.
- To connect to a DB instance through an ECS, you must first create an ECS.
For details on how to create and log in to an ECS, see descriptions about creating an ECS and logging in an ECS in the Elastic Cloud Server User Guide.
- To connect to a DB instance through an EIP, you must:
- Bind the EIP to the DB instance. For details, see Binding an EIP.
- Ensure that the local device can access the EIP that has been bound to the DB instance.
- To connect to a DB instance through an ECS, you must first create an ECS.
- Install the MySQL client on the prepared ECS or device.
For details, see How Can I Install the MySQL Client?
- -The version of the GaussDB(for MySQL) client must be the same as or later than that of the GaussDB(for MySQL) server. The MySQL database or client provides the mysqldump and mysql tools by default.
+ The version of the GaussDB(for MySQL) client must be the same as or later than that of the GaussDB(for MySQL) server. The MySQL database or client provides the mysqldump and mysql tools by default.
Exporting Data
Before migrating data to GaussDB(for MySQL), you need to export data first.
+Exporting Data
Before migrating data to GaussDB(for MySQL), you need to export data first.
- - The export tool must match the DB engine version.
- Database migration is performed offline. Before the migration, you must stop any applications using the source database.
- Log in to the prepared ECS or device that can access GaussDB(for MySQL) DB instances.
- Use the mysqldump tool to export metadata into an SQL file.
MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.
+- Log in to the prepared ECS or device that can access GaussDB(for MySQL) instances.
- Use the mysqldump tool to export metadata into an SQL file.
MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.
mysqldump --databases <DB_NAME> --single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF -u <DB_USER> -p -h <DB_ADDRESS> -P <DB_PORT> |sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' > <BACKUP_FILE>
- DB_NAME indicates the name of the database to be migrated.
- DB_USER indicates the database username.
- DB_ADDRESS indicates the database address.
- DB_PORT indicates the database port.
- BACKUP_FILE indicates the name of the file to which the data will be exported.
mysqldump --databases gaussdb --single-transaction --order-by-primary --hex-blob --no-data --routines --events --set-gtid-purged=OFF -u root -p -h 192.168.151.18 -P 3306 |sed -e 's/DEFINER[ ]*=[ ]*[^*]*\*/\*/' -e 's/DEFINER[ ]*=.*FUNCTION/FUNCTION/' -e 's/DEFINER[ ]*=.*PROCEDURE/PROCEDURE/' -e 's/DEFINER[ ]*=.*TRIGGER/TRIGGER/' -e 's/DEFINER[ ]*=.*EVENT/EVENT/' > dump-defs.sql
Enter password:
After this command is executed, the dump-defs.sql file will be generated.
- - Use the mysqldump tool to export data into an SQL file. -
MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.
+- Use the mysqldump tool to export data into an SQL file.
MySQL databases are required for GaussDB(for MySQL) management. When exporting metadata, do not specify --all-database. Otherwise, the databases will be unavailable.
mysqldump --databases <DB_NAME> --single-transaction --hex-blob --set-gtid-purged=OFF --no-create-info --skip-triggers -u <DB_USER> -p -h <DB_ADDRESS> -P <DB_PORT> -r <BACKUP_FILE>
For details on the parameters in the preceding command, see 2.
Enter the database password as prompted.
Example:
mysqldump --databases gaussdb --single-transaction --hex-blob --set-gtid-purged=OFF --no-create-info --skip-triggers -u root -p -h 192.168.151.18 -P 3306 -r dump-data.sql
-After this command is executed, the dump-data.sql file will be generated.
+After this command is executed, the dump-data.sql file will be generated.
Importing Data
You can use a client to connect to a GaussDB(for MySQL) DB instance through an ECS or a device and then import the exported SQL file into that DB instance.
+Importing Data
You can use a client to connect to a GaussDB(for MySQL) instance through an ECS or device and then import the exported SQL file into that instance.
- If the source database contains triggers, storage processes, functions, or event invocation, you must set log_bin_trust_function_creators to ON for the destination database before importing data.
- Import metadata into GaussDB(for MySQL).
Use the MySQL tool to connect to the GaussDB(for MySQL) DB instance, enter the password, and run the following command to import metadata:
+- Import metadata into GaussDB(for MySQL).
Use the MySQL tool to connect to the GaussDB(for MySQL) instance, enter the password, and run the following command to import metadata:
mysql -f -h <DB_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-defs.sql
-- DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) DB instance.
- DB_PORT indicates the GaussDB(for MySQL) DB instance port.
- BACKUP_DIR indicates the directory where dump-defs.sql is stored.
- DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) instance.
- DB_PORT indicates the GaussDB(for MySQL) instance port.
- BACKUP_DIR indicates the directory where dump-defs.sql is stored.
Example:
mysql -f -h 172.16.66.198 -P 3306 -u root -p < dump-defs.sql
Enter password:
- - Import data into GaussDB(for MySQL).
mysql -f -h <DB_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-data.sql
-- DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) DB instance.
- DB_PORT indicates the GaussDB(for MySQL) DB instance port.
- BACKUP_DIR indicates the directory where dump-data.sql is stored.
- Import data into GaussDB(for MySQL).
mysql -f -h <DB_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-data.sql
+- DB_ADDRESS indicates the IP address of the GaussDB(for MySQL) instance.
- DB_PORT indicates the GaussDB(for MySQL) instance port.
- BACKUP_DIR indicates the directory where dump-data.sql is stored.
Example:
mysql -f -h 172.16.66.198 -P 3306 -u root -p < dump-data.sql
Enter password:
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0009.html b/docs/gaussdb_mysql/umn/gaussdb_03_0009.html index ce047b944..d82bc8c4f 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0009.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0009.html @@ -6,7 +6,7 @@- Introducing Read Replicas
- - Creating a Read Replica
+ - Creating Read Replicas
- Managing a Read Replica
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0011.html b/docs/gaussdb_mysql/umn/gaussdb_03_0011.html
index 2befa1cfd..68a153414 100644
--- a/docs/gaussdb_mysql/umn/gaussdb_03_0011.html
+++ b/docs/gaussdb_mysql/umn/gaussdb_03_0011.html
@@ -1,13 +1,13 @@
- You have assigned an EIP on the VPC console.
- If a DB instance has already been bound with an EIP, you must unbind the EIP from the DB instance first before binding a new EIP to it.
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the Network Information area, click Bind in the Public IP Address (EIP) field.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance.
+Binding an EIP
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the instance name to go to the Basic Information page.
- In the Network Information area, click Bind in the Public IP Address (EIP) field.
- In the displayed dialog box, select an EIP and click OK.If no available EIPs are displayed, click View EIP and obtain an EIP.
You need to configure security group rules and enable specific IP addresses and ports to access the target DB instance.
- On the EIPs page, view the EIP that has been bound to the DB instance.
To unbind the EIP from the DB instance, see Unbinding an EIP.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html index 11d3064a5..106adbe96 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0012.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0012.html @@ -5,7 +5,7 @@
-Constraints
Changing the database port of a DB instance will only affect access through its IP address. If a DB instance is accessed through a proxy instance, the database port of the proxy instance cannot be changed, which defaults to 3306.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance to go to the Basic Information page.
- In the Network Information area, click
in the Database Port field.The GaussDB(for MySQL) database port ranges from 1025 to 65534, excluding 5342, 5343, 5344, 5345, 12017, 20000, 20201, and 20202, which are occupied by the system and cannot be used.- To submit the change, click
.- In the dialog box, click Yes.
- If you change the database port of a DB instance, the ports of the primary node and read replicas are also changed accordingly and all of them are rebooted.
- This process takes about 1–5 minutes.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the instance name to go to the Basic Information page.
- In the Network Information area, click in the Database Port field.The GaussDB(for MySQL) database port ranges from 1025 to 65534, excluding 5342, 5343, 5344, 5345, 12017, 20000, 20201, and 20202, which are reserved by the system.diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0014.html b/docs/gaussdb_mysql/umn/gaussdb_03_0014.html index 23b613869..c2c18904e 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0014.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0014.html @@ -1,9 +1,9 @@
- To submit the change, click .
- In the dialog box, click Yes.
- If you change the database port of a DB instance, the ports of the primary node and read replicas are also changed accordingly and all of them are rebooted.
- This process takes about 1–5 minutes.
- In the dialog box, click Yes.
- To cancel the change, click
.
Key Operations Supported by CTS
-Cloud Trace Service (CTS) records operations related to GaussDB(for MySQL) for further querying, auditing, and backtracking. Table 1 lists the supported operations.
+Cloud Trace Service (CTS) records operations related to GaussDB(for MySQL) for further querying, auditing, and backtracking. Table 1 lists the supported operations.
-Table 1 GaussDB(for MySQL) operations recorded by CTS Operation
+Table 1 GaussDB(for MySQL) operations recorded by CTS Operation
Resource Type
Viewing Logs
-You can view database logs on the GaussDB console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.
+You can view database logs on the GaussDB(for MySQL) console. For operation details, see Viewing Error Logs and Viewing Slow Query Logs.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0019.html b/docs/gaussdb_mysql/umn/gaussdb_03_0019.html index 594f680c7..78fe81180 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0019.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0019.html @@ -2,10 +2,10 @@Viewing Slow Query Logs
Scenarios
Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details and statistics to identify the statements that are executing slowly and optimize the statements.
-GaussDB(for MySQL) supports the following statement types:-- SELECT
- INSERT
- UPDATE
- DELETE
- CREATE
- ALTER
- DROP
GaussDB(for MySQL) supports the following statement types:- SELECT
- INSERT
- UPDATE
- DELETE
- CREATE
- ALTER
- DROP
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0032.html b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html index 051e879bb..cc72d1ba3 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0032.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0032.html @@ -1,7 +1,7 @@Viewing Log Details
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Logs.
- On the Slow Query Logs page, view the slow query log details.
You can view the slow query log records of a specified execution statement type or a specific time period.
+Viewing Log Details
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the navigation pane on the left, choose Logs.
- On the Slow Query Logs page, view the slow query log details.
You can view the slow query log records of a specified execution statement type or a specific time period.
Changing a DB Instance Name
-Scenarios
You can change the name of a GaussDB(for MySQL) DB instance.
+Scenarios
You can change the name of a GaussDB(for MySQL) instance.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, locate the instance name and click
in the Name/ID column to edit the instance name.- The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed.
- When changing the instance name, you can determine whether to select Change node names synchronously as required. If this option is selected, the names of the corresponding nodes are changed when the instance name is changed. If this option is not selected, only the instance name is changed, and the corresponding node names are not changed.
- If you want to submit the change, click OK. If you want to cancel the change, click Cancel.
- View the result of the change on the Basic Information page.
-Constraints
- DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are completed.
- If you delete a DB instance, its automated backups are also deleted and you are no longer charged for them. Manual backups are still retained and will incur additional costs.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, locate the DB instance to be deleted and click More > Delete in the Operation column.
- In the displayed dialog box, click Yes. Refresh the Instances page later to check that the deletion is successful.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, locate the DB instance to be deleted and click More > Delete in the Operation column.
- In the displayed dialog box, click Yes. Refresh the Instances page later to check that the deletion is successful.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html index 5c4520f77..910f214b1 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0051.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0051.html @@ -2,21 +2,21 @@Resetting the Administrator Password
Scenarios
You can reset the administrator password of a DB instance.
-You can also reset the password of your database account when using GaussDB(for MySQL).
+If you forget the password of your database account when using GaussDB(for MySQL), you can reset the password.
You cannot reset the administrator password under the following circumstances:
- The database port is being changed.
- The instance status is Creating, Restoring, Rebooting, Changing port, Changing instance class, Promoting to primary, or Abnormal.
-Precautions
- If you change the administrator password of a DB instance, the passwords of the read replicas associated with the DB instance are also changed accordingly.
- The length of time it takes for the new password to take effect depends on the amount of service data currently being processed by the primary node.
- To prevent brute force cracking and ensure system security, change your password periodically, such as every three or six months.
Method 1
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, locate the target DB instance and choose in the Operation column.
- Enter a new password and confirm the password.
Keep this password secure. The system cannot retrieve it.
+-Method 1
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, locate the instance for which you want to change the password and choose in the Operation column.
- Enter a new password and confirm the password.
Keep this password secure. The system cannot retrieve it.
The new password must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.
- To submit the new password, click OK.
- To cancel the reset, click Cancel.
Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance. The Basic Information page is displayed.
- In the DB Instance Information area, click Reset Password in the Administrator field. In the displayed dialog box, enter a new password and confirm the password.
Keep this password secure. The system cannot retrieve it.
+Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the instance name to go to the Basic Information page.
- In the DB Instance Information area, click Reset Password in the Administrator field. In the displayed dialog box, enter a new password and confirm the password.-
Keep this password secure. The system cannot retrieve it.
The new password must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0056.html b/docs/gaussdb_mysql/umn/gaussdb_03_0056.html index 21c71566a..3a59c5743 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0056.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0056.html @@ -2,7 +2,7 @@- To submit the new password, click OK.
- To cancel the reset, click Cancel.
The new password must consist of 8 to 32 characters and contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it to improve security, preventing security risks such as brute force cracking.- To submit the new password, click OK.
- To cancel the reset, click Cancel.
Working with Backups
GaussDB(for MySQL) supports backups and restorations to ensure data reliability.
-Automated Backups
Automated backups are created during the backup time window of your DB instances. GaussDB(for MySQL) saves automated backups based on the retention period you have specified. If necessary, you can restore to any point in time during your backup retention period.
+Automated Backups
Automated backups are created during the backup time window configured for your instances. GaussDB(for MySQL) saves automated backups based on the retention period you have specified. If necessary, you can restore to any point in time during your backup retention period.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html index ead577874..c3cce5be0 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0058.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0058.html @@ -7,8 +7,8 @@Manual Backups
Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually.
-Method 1
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, locate the target DB instance and choose in the Operation column.
- In the displayed dialog box, enter a backup name and description. Then, click OK. If you want to cancel the backup creation task, click Cancel.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
- The time required for creating a manual backup depends on the data volume of the DB instance.
- After a manual backup has been created, you can view and manage it on the Backups page.
Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the target DB instance.
- On the Backups page, click Create Backup. In the displayed dialog box, enter a backup name and a description, and click OK. If you want to cancel the backup creation task, click Cancel.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
- The time required for creating a manual backup depends on the data volume of the DB instance.
- After a manual backup has been created, you can view and manage it on the Backups page.
Method 2
- Log in to the management console.
- Click in the upper left corner and select a region and a project.
- Click Service List. Under Databases, click GaussDB(for MySQL).
- On the Instances page, click the instance name.
- On the Backups page, click Create Backup. In the displayed dialog box, enter a backup name and a description, and click OK. If you want to cancel the backup creation task, click Cancel.
- The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
- The description must consist of a maximum of 256 characters and cannot contain the carriage return character or the following special characters: !<"='>&
- The time required for creating a manual backup depends on the data volume of the DB instance.
- After a manual backup has been created, you can view and manage it on the Backups page.
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0069.html b/docs/gaussdb_mysql/umn/gaussdb_03_0069.html index b223413d7..af23b4926 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0069.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0069.html @@ -8,18 +8,18 @@Backup Space Calculation Methods
There is a default backup chain (where there are seven backups). The first automated backup is a full backup, and subsequent automated backups are differential backups.
In a backup chain, the backup space is released only after all full backups and differential backups are deleted.
The billed space is calculated as follows:
-- Logical space: Total size of the logical space – Logical size of the expired backup file
- Physical space: Size of the first full backup file + Total size of subsequent differential backup files
- Free space: There is free backup storage up to 100% of storage space.
Billed space = Min (Logical space, Physical space) – Free space = Min (Logical space, Physical space) – Storage space
+- Logical space: Total size of the logical space – Logical size of the expired backup file
- Physical space: Size of the first full backup file + Total size of subsequent differential backup files
Billed space = Min (Logical space, Physical space)
Example
A backup chain contains seven backups by default. There are 11 backups shown in the following figure. The 1st backup to the 7th belong to one backup chain and the 8th to the 11th belong to the other backup chain.
Figure 1 Backup example-
If there is 1,000 MB of backup space and the logical space is 1,000 MB each time, the physical space for the 1st backup is 1,000 MB. If the incremental data size is 100 MB each time, the physical space for the 2nd backup to 7th is 100 MB.
+If the logical space is 1,000 MB each time, the physical space for the 1st backup is 1,000 MB. If the incremental data size is 100 MB each time, the physical space for the 2nd backup to 7th is 100 MB.
A backup chain contains seven backups by default. The physical space for the 8th backup is 1,000 MB because it represents a new backup chain.
Billed space includes the space of the two chains in the example.
Suppose that after the 11th backup was created, and the 1st, 2nd and 3rd backups expired and were automatically deleted. The size of each space is calculated as follows:
- Total size of the logical space for the 11th backup = 1,000 MB x 11 – 3,000 MB = 8,000 MB
- Physical space: the amount of data backed up to OBS, that is, the sum of the physical space on the two chains.
Physical space = 1,000 MB + 100 MB x 6 + 1,000 MB + 100 MB x 3 = 2,900 MB
- - Total billed space = Min (8,000 MB, 2,900 MB) – 1,000 MB = 1,900 MB
- Total billed space = Min (8,000 MB, 2,900 MB) = 2,900 MB
diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0082.html b/docs/gaussdb_mysql/umn/gaussdb_03_0082.html index 7959b9423..f5dc7e901 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0082.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0082.html @@ -3,7 +3,7 @@Database Security
Password Strength Requirements
-GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:diff --git a/docs/gaussdb_mysql/umn/gaussdb_03_0085.html b/docs/gaussdb_mysql/umn/gaussdb_03_0085.html index 486042952..c3464583e 100644 --- a/docs/gaussdb_mysql/umn/gaussdb_03_0085.html +++ b/docs/gaussdb_mysql/umn/gaussdb_03_0085.html @@ -1,10 +1,10 @@- Consist of at least eight characters.
- Contain at least three types of the following: uppercase letters, lowercase letters, digits, and special characters.
GaussDB(for MySQL) has a password security policy for newly created database users. Passwords must:- Consist of at least eight characters.
- Contain at least three types of the following: uppercase letters, lowercase letters, digits, and special characters.
When you create DB instances, your password strength is checked. You can modify the password strength as user root. For security reasons, you are advised to use a password that is at least as strong as the default one.
Configuring Displayed Metrics
-Function
You can use Cloud Eye to monitor the running statuses of DB instances. This section describes namespaces, descriptions, and dimensions of monitoring metrics to be reported to Cloud Eye.
+-Function
You can use Cloud Eye to monitor the running statuses of DB instances. This section describes namespaces, descriptions, and dimensions of metrics to be reported to Cloud Eye.
DB Instance Monitoring Metrics
-
- To submit the change, click
- In the dialog box, click Yes.
- To submit the change, click
Binding and Unbinding an EIP
-Scenarios
By default, a GaussDB(for MySQL) DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to the DB instance for public accessibility and can unbind the EIP from the DB instance as required.
+Scenarios
By default, a GaussDB(for MySQL) instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to the instance for public accessibility and can unbind the EIP from the instance as required.
To ensure that the database can be accessed, the security group used by the database must have the permission to access the database port. For example, if the database port is 3306, ensure that the security group has the permission to access port 3306.
-Prerequisites
Binding an EIP
- Import metadata into GaussDB(for MySQL).
- Use the mysqldump tool to export data into an SQL file.
- Prepare an ECS in the same VPC subnet as the GaussDB(for MySQL) instance or bind an EIP to the GaussDB(for MySQL) instance.
- To connect to a DB instance through an ECS, you must first create an ECS.
- Bind an EIP to the target DB instance and configure security group rules.
- Step 3: Configure Security Group Rules
- Log in to the ECS.
