diff --git a/docs/rds/umn/.placeholder b/docs/rds/umn/.placeholder deleted file mode 100644 index e69de29bb..000000000 diff --git a/docs/rds/umn/ALL_META.TXT.json b/docs/rds/umn/ALL_META.TXT.json new file mode 100644 index 000000000..3b2e0a8ca --- /dev/null +++ b/docs/rds/umn/ALL_META.TXT.json @@ -0,0 +1,3722 @@ +[ + { + "uri":"rds_01_0000.html", + "product_code":"rds", + "code":"1", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Introduction", + "title":"Introduction", + "githuburl":"" + }, + { + "uri":"en-us_topic_dashboard.html", + "product_code":"rds", + "code":"2", + "des":"RDS is a cloud-based web service that is reliable, scalable, and easy to manage. RDS supports the following DB engines:MySQLPostgreSQLMicrosoft SQL ServerRDS provides a c", + "doc_type":"usermanual", + "kw":"RDS,RDS,RDS,RDS,RDS for MySQL,MySQL,RDS for MySQL,PostgreSQL,RDS for PostgreSQL,RDS for PostgreSQL,R", + "title":"What Is RDS?", + "githuburl":"" + }, + { + "uri":"rds_01_0015.html", + "product_code":"rds", + "code":"3", + "des":"The smallest management unit of RDS is the DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance runs a DB engine. For details abo", + "doc_type":"usermanual", + "kw":"RDS,Basic Concepts,Introduction,User Guide", + "title":"Basic Concepts", + "githuburl":"" + }, + { + "uri":"rds_01_0001.html", + "product_code":"rds", + "code":"4", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Advantages", + "title":"Advantages", + "githuburl":"" + }, + { + "uri":"rds_01_0002.html", + "product_code":"rds", + "code":"5", + "des":"You can create a DB instance on the management console within minutes and access RDS from an ECS to reduce the application response time and avoid paying for the traffic ", + "doc_type":"usermanual", + "kw":"Easy Management,Advantages,User Guide", + "title":"Easy Management", + "githuburl":"" + }, + { + "uri":"rds_01_0004.html", + "product_code":"rds", + "code":"6", + "des":"RDS uses Virtual Private Cloud (VPC) and network security groups to isolate and secure your DB instances. VPCs allow you to define what IP address range can access RDS. Y", + "doc_type":"usermanual", + "kw":"High Security,Advantages,User Guide", + "title":"High Security", + "githuburl":"" + }, + { + "uri":"rds_01_0005.html", + "product_code":"rds", + "code":"7", + "des":"RDS uses the hot standby architecture, in which failover upon fault occurrence takes only some seconds.RDS automatically backs up data every day and transfers backup file", + "doc_type":"usermanual", + "kw":"High Reliability,Advantages,User Guide", + "title":"High Reliability", + "githuburl":"" + }, + { + "uri":"rds_01_0006.html", + "product_code":"rds", + "code":"8", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Comparison Between RDS and Self-Built Databases,Advantages,User Guide", + "title":"Comparison Between RDS and Self-Built Databases", + "githuburl":"" + }, + { + "uri":"rds_01_0009.html", + "product_code":"rds", + "code":"9", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Product Series", + "title":"Product Series", + "githuburl":"" + }, + { + "uri":"rds_01_0010.html", + "product_code":"rds", + "code":"10", + "des":"Currently, RDS DB instances are classified into the following types:SinglePrimary/StandbySinglePrimary/StandbyDifferent series support different DB engines and instance s", + "doc_type":"usermanual", + "kw":"RDS,DB Instance Introduction,Product Series,User Guide", + "title":"DB Instance Introduction", + "githuburl":"" + }, + { + "uri":"rds_00_0011.html", + "product_code":"rds", + "code":"11", + "des":"Single DB instances use a single-node architecture. Different from the primary/standby DB instances, a single DB instance contains only one node and has no slave node for", + "doc_type":"usermanual", + "kw":"Function Comparison,Product Series,User Guide", + "title":"Function Comparison", + "githuburl":"" + }, + { + "uri":"rds_01_0028.html", + "product_code":"rds", + "code":"12", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"DB Instance Description", + "title":"DB Instance Description", + "githuburl":"" + }, + { + "uri":"rds_01_0016.html", + "product_code":"rds", + "code":"13", + "des":"The smallest management unit of RDS is the DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance can contain multiple user-created", + "doc_type":"usermanual", + "kw":"DB Instance Types,DB Instance Description,User Guide", + "title":"DB Instance Types", + "githuburl":"" + }, + { + "uri":"rds_01_0029.html", + "product_code":"rds", + "code":"14", + "des":"General-enhanced and general-enhanced II instance classes provide robust and stable performance. They use latest-generation network acceleration engines and Data Plane De", + "doc_type":"usermanual", + "kw":"DB Instance Classes,DB Instance Description,User Guide", + "title":"DB Instance Classes", + "githuburl":"" + }, + { + "uri":"en-us_topic_0043898356.html", + "product_code":"rds", + "code":"15", + "des":"Table 1 lists the DB engines and versions supported by RDS.For new applications, you are advised to use the latest major version of the DB engine, for example, MySQL 8.0.", + "doc_type":"usermanual", + "kw":"DB Engines and Versions,DB Instance Description,User Guide", + "title":"DB Engines and Versions", + "githuburl":"" + }, + { + "uri":"rds_01_0023.html", + "product_code":"rds", + "code":"16", + "des":"The status of a DB instance indicates the health of the DB instance. You can use the management console or API to view the status of a DB instance.", + "doc_type":"usermanual", + "kw":"DB Instance Statuses,DB Instance Description,User Guide", + "title":"DB Instance Statuses", + "githuburl":"" + }, + { + "uri":"rds_01_0024.html", + "product_code":"rds", + "code":"17", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Typical Applications", + "title":"Typical Applications", + "githuburl":"" + }, + { + "uri":"rds_01_0012.html", + "product_code":"rds", + "code":"18", + "des":"RDS for MySQL, RDS for PostgreSQL, and RDS for SQL Server 2017 Enterprise Edition DB instances support read replicas to offload read traffic from primary DB instances.For", + "doc_type":"usermanual", + "kw":"Read/Write Splitting,Typical Applications,User Guide", + "title":"Read/Write Splitting", + "githuburl":"" + }, + { + "uri":"rds_01_0013.html", + "product_code":"rds", + "code":"19", + "des":"RDS supports diverse storage extension through Distributed Cache Service (DCS) for Memcached, DCS for Redis, and OBS.", + "doc_type":"usermanual", + "kw":"Diversified Data Storage,Typical Applications,User Guide", + "title":"Diversified Data Storage", + "githuburl":"" + }, + { + "uri":"rds_01_0025.html", + "product_code":"rds", + "code":"20", + "des":"RDS provides two types of user permissions by default: user management and resource management.User management permissions cover the management of users, user groups, and", + "doc_type":"usermanual", + "kw":"user management,resource management,User Permissions,Introduction,User Guide", + "title":"User Permissions", + "githuburl":"" + }, + { + "uri":"rds_01_0026.html", + "product_code":"rds", + "code":"21", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Constraints", + "title":"Constraints", + "githuburl":"" + }, + { + "uri":"rds_02_0002.html", + "product_code":"rds", + "code":"22", + "des":"Table 1 shows the constraints designed to ensure the stability and security of RDS for MySQL.", + "doc_type":"usermanual", + "kw":"MySQL Constraints,Constraints,User Guide", + "title":"MySQL Constraints", + "githuburl":"" + }, + { + "uri":"rds_02_0012.html", + "product_code":"rds", + "code":"23", + "des":"Table 1 shows the constraints designed to ensure the stability and security of RDS for PostgreSQL.", + "doc_type":"usermanual", + "kw":"PostgreSQL Constraints,Constraints,User Guide", + "title":"PostgreSQL Constraints", + "githuburl":"" + }, + { + "uri":"rds_03_0003.html", + "product_code":"rds", + "code":"24", + "des":"RDS for SQL Server only supports DB instances under the License Included model and does not support \"bring your own license\" (BYOL). After a DB instance is created, it co", + "doc_type":"usermanual", + "kw":"SQL Server,Microsoft SQL Server Constraints,Constraints,User Guide", + "title":"Microsoft SQL Server Constraints", + "githuburl":"" + }, + { + "uri":"rds_01_0031.html", + "product_code":"rds", + "code":"25", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"DB Engine", + "title":"DB Engine", + "githuburl":"" + }, + { + "uri":"rds_01_0018.html", + "product_code":"rds", + "code":"26", + "des":"This section describes function differences between single and primary/standby DB instances as well as function differences among Microsoft SQL Server editions.For detail", + "doc_type":"usermanual", + "kw":"differences of basic functions,DB instance types,differences of database migration functions,differe", + "title":"Function Differences of RDS for SQL Server Instances Types and Editions", + "githuburl":"" + }, + { + "uri":"rds_01_0027.html", + "product_code":"rds", + "code":"27", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Related Services,Introduction,User Guide", + "title":"Related Services", + "githuburl":"" + }, + { + "uri":"index.html", + "product_code":"rds", + "code":"28", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Getting Started with RDS for MySQL", + "title":"Getting Started with RDS for MySQL", + "githuburl":"" + }, + { + "uri":"en-us_topic_0046585334.html", + "product_code":"rds", + "code":"29", + "des":"You can create and connect to DB instances on the RDS console.", + "doc_type":"usermanual", + "kw":"Operation Guide,Getting Started with RDS for MySQL,User Guide", + "title":"Operation Guide", + "githuburl":"" + }, + { + "uri":"rds_02_0008.html", + "product_code":"rds", + "code":"30", + "des":"This section describes how to create a DB instance on the management console.The DB instance class and storage space you need depend on your processing power and memory r", + "doc_type":"usermanual", + "kw":"DB Engine,Step 1: Create a DB Instance,Getting Started with RDS for MySQL,User Guide", + "title":"Step 1: Create a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_02_0006.html", + "product_code":"rds", + "code":"31", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Step 2: Connect to a DB Instance", + "title":"Step 2: Connect to a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_02_0060.html", + "product_code":"rds", + "code":"32", + "des":"An RDS DB instance can be connected through a private network or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ", + "doc_type":"usermanual", + "kw":"RDS,Connecting to a DB Instance,Step 2: Connect to a DB Instance,User Guide", + "title":"Connecting to a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_02_0101.html", + "product_code":"rds", + "code":"33", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to an RDS for MySQL DB Instance Through a Private Network", + "title":"Connecting to an RDS for MySQL DB Instance Through a Private Network", + "githuburl":"" + }, + { + "uri":"en-us_topic_apply_for_rds.html", + "product_code":"rds", + "code":"34", + "des":"Figure 1 illustrates the process of connecting to a MySQL DB instance through a private network.", + "doc_type":"usermanual", + "kw":"Overview,Connecting to an RDS for MySQL DB Instance Through a Private Network,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"rds_02_0004.html", + "product_code":"rds", + "code":"35", + "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "doc_type":"usermanual", + "kw":"security group,Configuring Security Group Rules,Connecting to an RDS for MySQL DB Instance Through a", + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"rds_02_0047.html", + "product_code":"rds", + "code":"36", + "des":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.You have logged in to an ECS.To co", + "doc_type":"usermanual", + "kw":"SSL connection,encrypts data,Connecting to a DB Instance Through a Private Network,Connecting to an ", + "title":"Connecting to a DB Instance Through a Private Network", + "githuburl":"" + }, + { + "uri":"rds_02_0048.html", + "product_code":"rds", + "code":"37", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to an RDS for MySQL DB Instance Through a Public Network", + "title":"Connecting to an RDS for MySQL DB Instance Through a Public Network", + "githuburl":"" + }, + { + "uri":"rds_02_0099.html", + "product_code":"rds", + "code":"38", + "des":"Figure 1 illustrates the process of connecting to a MySQL DB instance through a public network.", + "doc_type":"usermanual", + "kw":"Overview,Connecting to an RDS for MySQL DB Instance Through a Public Network,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"rds_02_0025.html", + "product_code":"rds", + "code":"39", + "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can un", + "doc_type":"usermanual", + "kw":"configure security groups,Binding an EIP,Connecting to an RDS for MySQL DB Instance Through a Public", + "title":"Binding an EIP", + "githuburl":"" + }, + { + "uri":"rds_02_0009.html", + "product_code":"rds", + "code":"40", + "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "doc_type":"usermanual", + "kw":"security group,Configuring Security Group Rules,Connecting to an RDS for MySQL DB Instance Through a", + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"en-us_topic_connect_instance.html", + "product_code":"rds", + "code":"41", + "des":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.An EIP has been bound to the targe", + "doc_type":"usermanual", + "kw":"SSL connection,encrypts data,Connecting to a DB Instance Through a Public Network,Connecting to an R", + "title":"Connecting to a DB Instance Through a Public Network", + "githuburl":"" + }, + { + "uri":"rds_03_0063.html", + "product_code":"rds", + "code":"42", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Getting Started with RDS for PostgreSQL", + "title":"Getting Started with RDS for PostgreSQL", + "githuburl":"" + }, + { + "uri":"rds_02_0001.html", + "product_code":"rds", + "code":"43", + "des":"You can create and connect to DB instances on the RDS console.", + "doc_type":"usermanual", + "kw":"Operation Guide,Getting Started with RDS for PostgreSQL,User Guide", + "title":"Operation Guide", + "githuburl":"" + }, + { + "uri":"rds_03_0065.html", + "product_code":"rds", + "code":"44", + "des":"You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see \"Creating a DB Instance\" in the Relational Databas", + "doc_type":"usermanual", + "kw":"create DB instances,create a DB instance,Step 1: Create a DB Instance,Getting Started with RDS for P", + "title":"Step 1: Create a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_02_0017.html", + "product_code":"rds", + "code":"45", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Step 2: Connect to a DB Instance", + "title":"Step 2: Connect to a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_03_0060.html", + "product_code":"rds", + "code":"46", + "des":"An RDS DB instance can be connected through a private network or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ", + "doc_type":"usermanual", + "kw":"Connecting to a DB Instance,Step 2: Connect to a DB Instance,User Guide", + "title":"Connecting to a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_02_0013.html", + "product_code":"rds", + "code":"47", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a PostgreSQL DB Instance Through a Private Network", + "title":"Connecting to a PostgreSQL DB Instance Through a Private Network", + "githuburl":"" + }, + { + "uri":"rds_02_0010.html", + "product_code":"rds", + "code":"48", + "des":"Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a private network.", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a PostgreSQL DB Instance Through a Private Network,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"rds_02_0014.html", + "product_code":"rds", + "code":"49", + "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "doc_type":"usermanual", + "kw":"security group,Configuring Security Group Rules,Connecting to a PostgreSQL DB Instance Through a Pri", + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"rds_02_0016.html", + "product_code":"rds", + "code":"50", + "des":"You can use the PostgreSQL client psql to connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection is encrypted and therefore more s", + "doc_type":"usermanual", + "kw":"SSL connection,SSL Connection,Connecting to a DB Instance Through psql,Connecting to a PostgreSQL DB", + "title":"Connecting to a DB Instance Through psql", + "githuburl":"" + }, + { + "uri":"rds_02_0018.html", + "product_code":"rds", + "code":"51", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a PostgreSQL DB Instance Through a Public Network", + "title":"Connecting to a PostgreSQL DB Instance Through a Public Network", + "githuburl":"" + }, + { + "uri":"rds_02_0019.html", + "product_code":"rds", + "code":"52", + "des":"Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a public network.", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a PostgreSQL DB Instance Through a Public Network,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"rds_03_0064.html", + "product_code":"rds", + "code":"53", + "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can un", + "doc_type":"usermanual", + "kw":"configure security groups,Binding an EIP,Connecting to a PostgreSQL DB Instance Through a Public Net", + "title":"Binding an EIP", + "githuburl":"" + }, + { + "uri":"rds_02_0003.html", + "product_code":"rds", + "code":"54", + "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "doc_type":"usermanual", + "kw":"security group,Configuring Security Group Rules,Connecting to a PostgreSQL DB Instance Through a Pub", + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"rds_02_0051.html", + "product_code":"rds", + "code":"55", + "des":"You can use the PostgreSQL client psql to connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection is encrypted and therefore more s", + "doc_type":"usermanual", + "kw":"SSL connection,SSL Connection,Connecting to a DB Instance Through psql,Connecting to a PostgreSQL DB", + "title":"Connecting to a DB Instance Through psql", + "githuburl":"" + }, + { + "uri":"rds_03_0014.html", + "product_code":"rds", + "code":"56", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Getting Started with RDS for SQL Server", + "title":"Getting Started with RDS for SQL Server", + "githuburl":"" + }, + { + "uri":"rds_03_0010.html", + "product_code":"rds", + "code":"57", + "des":"You can create and connect to DB instances on the RDS console.", + "doc_type":"usermanual", + "kw":"Operation Guide,Getting Started with RDS for SQL Server,User Guide", + "title":"Operation Guide", + "githuburl":"" + }, + { + "uri":"rds_04_0061.html", + "product_code":"rds", + "code":"58", + "des":"You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see the \"Creating a DB Instance\" section in the Relati", + "doc_type":"usermanual", + "kw":"create a DB instance,Step 1: Create a DB Instance,Getting Started with RDS for SQL Server,User Guide", + "title":"Step 1: Create a DB Instance", + "githuburl":"" + }, + { + "uri":"en-us_topic_0053089697.html", + "product_code":"rds", + "code":"59", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Step 2: Connect to a DB Instance", + "title":"Step 2: Connect to a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_04_0060.html", + "product_code":"rds", + "code":"60", + "des":"An RDS DB instance can be connected through a private network or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ", + "doc_type":"usermanual", + "kw":"Connecting to a DB Instance,Step 2: Connect to a DB Instance,User Guide", + "title":"Connecting to a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_03_0008.html", + "product_code":"rds", + "code":"61", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a SQL Server DB Instance Through a Private Network", + "title":"Connecting to a SQL Server DB Instance Through a Private Network", + "githuburl":"" + }, + { + "uri":"rds_03_0001.html", + "product_code":"rds", + "code":"62", + "des":"Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a private network.", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a SQL Server DB Instance Through a Private Network,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"rds_03_0005.html", + "product_code":"rds", + "code":"63", + "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "doc_type":"usermanual", + "kw":"security group,Configuring Security Group Rules,Connecting to a SQL Server DB Instance Through a Pri", + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"rds_03_0013.html", + "product_code":"rds", + "code":"64", + "des":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.Prepare an ECS.To connect to a DB ", + "doc_type":"usermanual", + "kw":"SSL connection,encrypts data,Connecting to a DB Instance Through a Private Network,Connecting to a S", + "title":"Connecting to a DB Instance Through a Private Network", + "githuburl":"" + }, + { + "uri":"rds_03_0052.html", + "product_code":"rds", + "code":"65", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connecting to a SQL Server DB Instance Through a Public Network", + "title":"Connecting to a SQL Server DB Instance Through a Public Network", + "githuburl":"" + }, + { + "uri":"rds_03_0066.html", + "product_code":"rds", + "code":"66", + "des":"Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a public network.", + "doc_type":"usermanual", + "kw":"Overview,Connecting to a SQL Server DB Instance Through a Public Network,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"rds_03_0006.html", + "product_code":"rds", + "code":"67", + "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can un", + "doc_type":"usermanual", + "kw":"configure security groups,Binding an EIP,Connecting to a SQL Server DB Instance Through a Public Net", + "title":"Binding an EIP", + "githuburl":"" + }, + { + "uri":"rds_03_0051.html", + "product_code":"rds", + "code":"68", + "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "doc_type":"usermanual", + "kw":"security group,Configuring Security Group Rules,Connecting to a SQL Server DB Instance Through a Pub", + "title":"Configuring Security Group Rules", + "githuburl":"" + }, + { + "uri":"rds_03_0007.html", + "product_code":"rds", + "code":"69", + "des":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.Install the Microsoft SQL Server c", + "doc_type":"usermanual", + "kw":"SSL connection,encrypts data,Connecting to a DB Instance Through a Public Network,Connecting to a SQ", + "title":"Connecting to a DB Instance Through a Public Network", + "githuburl":"" + }, + { + "uri":"rds_08_0000.html", + "product_code":"rds", + "code":"70", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Working with RDS for MySQL", + "title":"Working with RDS for MySQL", + "githuburl":"" + }, + { + "uri":"rds_05_0001_02.html", + "product_code":"rds", + "code":"71", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Data Migration", + "title":"Data Migration", + "githuburl":"" + }, + { + "uri":"rds_migration_mysql.html", + "product_code":"rds", + "code":"72", + "des":"You can access RDS DB instances through an EIP or through an ECS.Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through a", + "doc_type":"usermanual", + "kw":"Migrating Data to RDS for MySQL Using mysqldump,Data Migration,User Guide", + "title":"Migrating Data to RDS for MySQL Using mysqldump", + "githuburl":"" + }, + { + "uri":"rds_08_00000.html", + "product_code":"rds", + "code":"73", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Parameter Tuning", + "title":"Parameter Tuning", + "githuburl":"" + }, + { + "uri":"rds_08_00001.html", + "product_code":"rds", + "code":"74", + "des":"Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some", + "doc_type":"usermanual", + "kw":"Suggestions on MySQL Parameter Tuning,Parameter Tuning,User Guide", + "title":"Suggestions on MySQL Parameter Tuning", + "githuburl":"" + }, + { + "uri":"rds_05_0000.html", + "product_code":"rds", + "code":"75", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Instance Lifecycle", + "title":"Instance Lifecycle", + "githuburl":"" + }, + { + "uri":"rds_05_0055.html", + "product_code":"rds", + "code":"76", + "des":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", + "doc_type":"usermanual", + "kw":"create a DB instance with the same configurations as the selected one,Creating a Same DB Instance as", + "title":"Creating a Same DB Instance as an Existing DB Instance", + "githuburl":"" + }, + { + "uri":"rds_05_0057.html", + "product_code":"rds", + "code":"77", + "des":"If you use DB instances only for routine development, you can temporarily stop pay-per-use DB instances to save money. You can stop a DB instance for up to seven days.If ", + "doc_type":"usermanual", + "kw":"Stopping a DB Instance,Instance Lifecycle,User Guide", + "title":"Stopping a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_05_0058.html", + "product_code":"rds", + "code":"78", + "des":"You can stop your DB instance temporarily to save money. After stopping your DB instance, you can restart it to begin using it again.If you start a primary DB instance, r", + "doc_type":"usermanual", + "kw":"Starting a DB Instance,Instance Lifecycle,User Guide", + "title":"Starting a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_08_0013.html", + "product_code":"rds", + "code":"79", + "des":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", + "doc_type":"usermanual", + "kw":"Rebooting DB Instances or Read Replicas,Instance Lifecycle,User Guide", + "title":"Rebooting DB Instances or Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_08_0022.html", + "product_code":"rds", + "code":"80", + "des":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", + "doc_type":"usermanual", + "kw":"instance items,edit columns,Selecting Displayed Items,Instance Lifecycle,User Guide", + "title":"Selecting Displayed Items", + "githuburl":"" + }, + { + "uri":"rds_05_0017.html", + "product_code":"rds", + "code":"81", + "des":"You can export information about all or selected DB instances to view and analyze DB instance information.", + "doc_type":"usermanual", + "kw":"Exporting DB Instance Information,Instance Lifecycle,User Guide", + "title":"Exporting DB Instance Information", + "githuburl":"" + }, + { + "uri":"rds_08_0002.html", + "product_code":"rds", + "code":"82", + "des":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", + "doc_type":"usermanual", + "kw":"Deleting a DB Instance,Deleting a Read Replica,Deleting a DB Instance or Read Replica,Instance Lifec", + "title":"Deleting a DB Instance or Read Replica", + "githuburl":"" + }, + { + "uri":"rds_mysql_recycle.html", + "product_code":"rds", + "code":"83", + "des":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", + "doc_type":"usermanual", + "kw":"Read replicas,Recycling a DB Instance,Instance Lifecycle,User Guide", + "title":"Recycling a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_05_0001.html", + "product_code":"rds", + "code":"84", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Instance Modifications", + "title":"Instance Modifications", + "githuburl":"" + }, + { + "uri":"rds_05_0003.html", + "product_code":"rds", + "code":"85", + "des":"RDS for MySQL supports minor version upgrades to improve performance, add new functions, and fix bugs.The upgrade will cause the DB instance to reboot and interrupt servi", + "doc_type":"usermanual", + "kw":"RDS for MySQL,MySQL,Upgrading a Minor Version,Instance Modifications,User Guide", + "title":"Upgrading a Minor Version", + "githuburl":"" + }, + { + "uri":"rds_modify_instance_name.html", + "product_code":"rds", + "code":"86", + "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", + "doc_type":"usermanual", + "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", + "title":"Changing a DB Instance Name", + "githuburl":"" + }, + { + "uri":"rds_modify_availability.html", + "product_code":"rds", + "code":"87", + "des":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", + "doc_type":"usermanual", + "kw":"failover priority,Changing the Failover Priority,Instance Modifications,User Guide", + "title":"Changing the Failover Priority", + "githuburl":"" + }, + { + "uri":"en-us_topic_scale_rds.html", + "product_code":"rds", + "code":"88", + "des":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "doc_type":"usermanual", + "kw":"CPU or memory,Changing a DB Instance Class,Instance Modifications,User Guide", + "title":"Changing a DB Instance Class", + "githuburl":"" + }, + { + "uri":"en-us_topic_scale_cluster.html", + "product_code":"rds", + "code":"89", + "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If your storage space usage reaches up to 95% for a disk l", + "doc_type":"usermanual", + "kw":"scale up storage space,scale up storage space,MySQL,Scaling up Storage Space,Instance Modifications,", + "title":"Scaling up Storage Space", + "githuburl":"" + }, + { + "uri":"rds_05_0038.html", + "product_code":"rds", + "code":"90", + "des":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", + "doc_type":"usermanual", + "kw":"Changing the Maintenance Window,Instance Modifications,User Guide", + "title":"Changing the Maintenance Window", + "githuburl":"" + }, + { + "uri":"rds_05_0023.html", + "product_code":"rds", + "code":"91", + "des":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability. This operation does not affect the services running on the ", + "doc_type":"usermanual", + "kw":"change single DB instances to primary/standby DB instances,Changing a DB Instance Type from Single t", + "title":"Changing a DB Instance Type from Single to Primary/Standby", + "githuburl":"" + }, + { + "uri":"rds_switch_ha.html", + "product_code":"rds", + "code":"92", + "des":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", + "doc_type":"usermanual", + "kw":"Manually Switching Between Primary and Standby DB Instances,Instance Modifications,User Guide", + "title":"Manually Switching Between Primary and Standby DB Instances", + "githuburl":"" + }, + { + "uri":"rds_11_0011.html", + "product_code":"rds", + "code":"93", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Read Replicas", + "title":"Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_11_0012.html", + "product_code":"rds", + "code":"94", + "des":"RDS for MySQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. ", + "doc_type":"usermanual", + "kw":"read replicas,MySQL,Introducing Read Replicas,Read Replicas,User Guide", + "title":"Introducing Read Replicas", + "githuburl":"" + }, + { + "uri":"en-us_topic_add_read_replica.html", + "product_code":"rds", + "code":"95", + "des":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After DB instances are created, you can create read replicas for them.", + "doc_type":"usermanual", + "kw":"create read replicas,create read replicas,Creating a Read Replica,Read Replicas,User Guide", + "title":"Creating a Read Replica", + "githuburl":"" + }, + { + "uri":"rds_11_0015.html", + "product_code":"rds", + "code":"96", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Managing a Read Replica,Read Replicas,User Guide", + "title":"Managing a Read Replica", + "githuburl":"" + }, + { + "uri":"rds_05_0034.html", + "product_code":"rds", + "code":"97", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Backups and Restorations", + "title":"Backups and Restorations", + "githuburl":"" + }, + { + "uri":"en-us_topic_backup_restore.html", + "product_code":"rds", + "code":"98", + "des":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", + "doc_type":"usermanual", + "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", + "title":"Working with Backups", + "githuburl":"" + }, + { + "uri":"rds_08_0004.html", + "product_code":"rds", + "code":"99", + "des":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", + "doc_type":"usermanual", + "kw":"Configuring an Automated Backup Policy,Backups and Restorations,User Guide", + "title":"Configuring an Automated Backup Policy", + "githuburl":"" + }, + { + "uri":"rds_08_0005.html", + "product_code":"rds", + "code":"100", + "des":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", + "doc_type":"usermanual", + "kw":"create manual backups,Creating a Manual Backup,Backups and Restorations,User Guide", + "title":"Creating a Manual Backup", + "githuburl":"" + }, + { + "uri":"rds_08_0006.html", + "product_code":"rds", + "code":"101", + "des":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for MySQL enables you to download ", + "doc_type":"usermanual", + "kw":"download a manual or an automated backup file,RDS for MySQL,full backup files,Downloading a Backup F", + "title":"Downloading a Backup File", + "githuburl":"" + }, + { + "uri":"rds_03_0100.html", + "product_code":"rds", + "code":"102", + "des":"RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary.You can also select the binlog backups ", + "doc_type":"usermanual", + "kw":"binlog backup files,Downloading a Binlog Backup File,Backups and Restorations,User Guide", + "title":"Downloading a Binlog Backup File", + "githuburl":"" + }, + { + "uri":"rds_08_0007.html", + "product_code":"rds", + "code":"103", + "des":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", + "doc_type":"usermanual", + "kw":"Restoring from Backup Files to DB Instances,Backups and Restorations,User Guide", + "title":"Restoring from Backup Files to DB Instances", + "githuburl":"" + }, + { + "uri":"rds_08_0044.html", + "product_code":"rds", + "code":"104", + "des":"You can download backup files by referring to Downloading a Backup File and restore data from them.Backup data cannot be restored to local databases that run the Windows ", + "doc_type":"usermanual", + "kw":"MySQL,MySQL,MySQL,Restoring from Backup Files to a Self-Built MySQL Database,Backups and Restoration", + "title":"Restoring from Backup Files to a Self-Built MySQL Database", + "githuburl":"" + }, + { + "uri":"rds_08_0008.html", + "product_code":"rds", + "code":"105", + "des":"You can restore from automated backups to a specified point in time.RDS for MySQL supports restoration to a new, the original, or an existing DB instance.When you enter t", + "doc_type":"usermanual", + "kw":"RDS for MySQL,restoration to a new, the original,,Restoring a DB Instance to a Point in Time,Backups", + "title":"Restoring a DB Instance to a Point in Time", + "githuburl":"" + }, + { + "uri":"rds_08_0009.html", + "product_code":"rds", + "code":"106", + "des":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", + "doc_type":"usermanual", + "kw":"replicate a manual or an automated backup,Replicating a Backup,Backups and Restorations,User Guide", + "title":"Replicating a Backup", + "githuburl":"" + }, + { + "uri":"rds_08_0010.html", + "product_code":"rds", + "code":"107", + "des":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", + "doc_type":"usermanual", + "kw":"Deleting a Manual Backup,Backups and Restorations,User Guide", + "title":"Deleting a Manual Backup", + "githuburl":"" + }, + { + "uri":"rds_08_0011.html", + "product_code":"rds", + "code":"108", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Parameter Template Management", + "title":"Parameter Template Management", + "githuburl":"" + }, + { + "uri":"en-us_topic_parameter_group.html", + "product_code":"rds", + "code":"109", + "des":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "doc_type":"usermanual", + "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", + "title":"Creating a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_configuration.html", + "product_code":"rds", + "code":"110", + "des":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", + "doc_type":"usermanual", + "kw":"Modifying Parameters,Parameter Template Management,User Guide", + "title":"Modifying Parameters", + "githuburl":"" + }, + { + "uri":"rds_08_0042.html", + "product_code":"rds", + "code":"111", + "des":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", + "doc_type":"usermanual", + "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", + "title":"Exporting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_08_0012.html", + "product_code":"rds", + "code":"112", + "des":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "doc_type":"usermanual", + "kw":"Compare,Comparing Parameter Templates,Parameter Template Management,User Guide", + "title":"Comparing Parameter Templates", + "githuburl":"" + }, + { + "uri":"rds_05_0099.html", + "product_code":"rds", + "code":"113", + "des":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", + "doc_type":"usermanual", + "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", + "title":"Viewing Parameter Change History", + "githuburl":"" + }, + { + "uri":"rds_08_0014.html", + "product_code":"rds", + "code":"114", + "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "doc_type":"usermanual", + "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", + "title":"Replicating a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_08_0015.html", + "product_code":"rds", + "code":"115", + "des":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", + "doc_type":"usermanual", + "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", + "title":"Resetting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_05_0018.html", + "product_code":"rds", + "code":"116", + "des":"You can apply parameter templates to DB instances as needed.The parameter innodb_buffer_pool_size is determined by the memory. DB instances of different specifications ha", + "doc_type":"usermanual", + "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", + "title":"Applying a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_05_0098.html", + "product_code":"rds", + "code":"117", + "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "doc_type":"usermanual", + "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", + "title":"Viewing Application Records of a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_08_0016.html", + "product_code":"rds", + "code":"118", + "des":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", + "doc_type":"usermanual", + "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", + "title":"Modifying a Parameter Template Description", + "githuburl":"" + }, + { + "uri":"rds_08_0017.html", + "product_code":"rds", + "code":"119", + "des":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "doc_type":"usermanual", + "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", + "title":"Deleting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_05_0005.html", + "product_code":"rds", + "code":"120", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connection Management", + "title":"Connection Management", + "githuburl":"" + }, + { + "uri":"rds_05_0024.html", + "product_code":"rds", + "code":"121", + "des":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", + "doc_type":"usermanual", + "kw":"change floating IP addresses,automatically-assigned IP address,change the floating IP address,Config", + "title":"Configuring and Changing a Floating IP Address", + "githuburl":"" + }, + { + "uri":"rds_public_accessibility.html", + "product_code":"rds", + "code":"122", + "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", + "doc_type":"usermanual", + "kw":"Binding and Unbinding an EIP,Connection Management,User Guide", + "title":"Binding and Unbinding an EIP", + "githuburl":"" + }, + { + "uri":"rds_change_database_port.html", + "product_code":"rds", + "code":"123", + "des":"This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the pri", + "doc_type":"usermanual", + "kw":"change the database port of a primary DB instance or a read replica,Changing a Database Port,Connect", + "title":"Changing a Database Port", + "githuburl":"" + }, + { + "uri":"rds_11_0009.html", + "product_code":"rds", + "code":"124", + "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "doc_type":"usermanual", + "kw":"security group,RDS,RDS,RDS,RDS,RDS,Configuring a Security Group Rule,Connection Management,User Guid", + "title":"Configuring a Security Group Rule", + "githuburl":"" + }, + { + "uri":"rds_05_0006.html", + "product_code":"rds", + "code":"125", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Data Security", + "title":"Data Security", + "githuburl":"" + }, + { + "uri":"rds_reset_password.html", + "product_code":"rds", + "code":"126", + "des":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", + "doc_type":"usermanual", + "kw":"reset the administrator password,RDS,Resetting the Administrator Password,Data Security,User Guide", + "title":"Resetting the Administrator Password", + "githuburl":"" + }, + { + "uri":"rds_08_0003.html", + "product_code":"rds", + "code":"127", + "des":"This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the pri", + "doc_type":"usermanual", + "kw":"Changing a Security Group,Data Security,User Guide", + "title":"Changing a Security Group", + "githuburl":"" + }, + { + "uri":"rds_08_0019.html", + "product_code":"rds", + "code":"128", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Metrics and Alarms", + "title":"Metrics and Alarms", + "githuburl":"" + }, + { + "uri":"rds_06_0001.html", + "product_code":"rds", + "code":"129", + "des":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the RDS metrics that can be monitored by Cloud Eye as well as their na", + "doc_type":"usermanual", + "kw":"Configuring Displayed Metrics,Metrics and Alarms,User Guide", + "title":"Configuring Displayed Metrics", + "githuburl":"" + }, + { + "uri":"rds_06_0002.html", + "product_code":"rds", + "code":"130", + "des":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", + "doc_type":"usermanual", + "kw":"Setting Alarm Rules,Metrics and Alarms,User Guide", + "title":"Setting Alarm Rules", + "githuburl":"" + }, + { + "uri":"rds_06_0003.html", + "product_code":"rds", + "code":"131", + "des":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", + "doc_type":"usermanual", + "kw":"Viewing Monitoring Metrics,Metrics and Alarms,User Guide", + "title":"Viewing Monitoring Metrics", + "githuburl":"" + }, + { + "uri":"rds_08_0020.html", + "product_code":"rds", + "code":"132", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Interconnection with CTS", + "title":"Interconnection with CTS", + "githuburl":"" + }, + { + "uri":"rds_06_0004.html", + "product_code":"rds", + "code":"133", + "des":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", + "doc_type":"usermanual", + "kw":"Cloud Trace Service (CTS),Key Operations Supported by CTS,Interconnection with CTS,User Guide", + "title":"Key Operations Supported by CTS", + "githuburl":"" + }, + { + "uri":"rds_06_0005.html", + "product_code":"rds", + "code":"134", + "des":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", + "doc_type":"usermanual", + "kw":"Viewing Tracing Events,Interconnection with CTS,User Guide", + "title":"Viewing Tracing Events", + "githuburl":"" + }, + { + "uri":"rds_08_0021.html", + "product_code":"rds", + "code":"135", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Management", + "title":"Log Management", + "githuburl":"" + }, + { + "uri":"rds_mysql_error_log.html", + "product_code":"rds", + "code":"136", + "des":"RDS log management allows you to view database-level logs, including error logs and slow SQL query logs.Error logs contain warning- and error-level logs generated during ", + "doc_type":"usermanual", + "kw":"Viewing Error Logs,Log Management,User Guide", + "title":"Viewing Error Logs", + "githuburl":"" + }, + { + "uri":"rds_mysql_slow_query_log.html", + "product_code":"rds", + "code":"137", + "des":"Slow query logs record statements that exceed long_query_time. You can use these logs to identify and optimize the statements that are executing slowly.RDS supports the f", + "doc_type":"usermanual", + "kw":"Viewing Slow Query Logs,Log Management,User Guide", + "title":"Viewing Slow Query Logs", + "githuburl":"" + }, + { + "uri":"rds_switch_log.html", + "product_code":"rds", + "code":"138", + "des":"You can view failover or switchover logs of MySQL DB instances to evaluate the impact on services.Only failover and switchover logs within 30 days are displayed.", + "doc_type":"usermanual", + "kw":"MySQL,Viewing Failover/Switchover Logs,Log Management,User Guide", + "title":"Viewing Failover/Switchover Logs", + "githuburl":"" + }, + { + "uri":"rds_sql_auditing_log.html", + "product_code":"rds", + "code":"139", + "des":"After you enable the SQL audit function, all SQL operations will be recorded in log files. You can download audit logs to view log details.By default, SQL audit is disabl", + "doc_type":"usermanual", + "kw":"Enabling the SQL Audit Function,Log Management,User Guide", + "title":"Enabling the SQL Audit Function", + "githuburl":"" + }, + { + "uri":"rds_download_sql_auditing_log.html", + "product_code":"rds", + "code":"140", + "des":"If you enable the SQL audit function, all SQL operations will be logged, and you can download audit logs to view details. By default, the SQL audit function is disabled. ", + "doc_type":"usermanual", + "kw":"Downloading SQL Audit Logs,Log Management,User Guide", + "title":"Downloading SQL Audit Logs", + "githuburl":"" + }, + { + "uri":"rds_05_0007.html", + "product_code":"rds", + "code":"141", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Task Center", + "title":"Task Center", + "githuburl":"" + }, + { + "uri":"rds_task_0001.html", + "product_code":"rds", + "code":"142", + "des":"You can view the progress and results of scheduled and instant tasks on the Task Center page.RDS allows you to view and manage the following instant tasks:Creating DB ins", + "doc_type":"usermanual", + "kw":"Viewing a Task,Task Center,User Guide", + "title":"Viewing a Task", + "githuburl":"" + }, + { + "uri":"rds_task_0002.html", + "product_code":"rds", + "code":"143", + "des":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", + "doc_type":"usermanual", + "kw":"Deleting a Task Record,Task Center,User Guide", + "title":"Deleting a Task Record", + "githuburl":"" + }, + { + "uri":"rds_tag.html", + "product_code":"rds", + "code":"144", + "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "doc_type":"usermanual", + "kw":"Tag Management Service (TMS),Managing Tags,Working with RDS for MySQL,User Guide", + "title":"Managing Tags", + "githuburl":"" + }, + { + "uri":"rds_09_0000.html", + "product_code":"rds", + "code":"145", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Working with RDS for PostgreSQL", + "title":"Working with RDS for PostgreSQL", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0001_02.html", + "product_code":"rds", + "code":"146", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Data Migration", + "title":"Data Migration", + "githuburl":"" + }, + { + "uri":"rds_09_0023.html", + "product_code":"rds", + "code":"147", + "des":"PostgreSQL supports logical backups. You can use the pg_dump logical backup function to export backup files and then import them to RDS using psql.You can access RDS DB i", + "doc_type":"usermanual", + "kw":"PostgreSQL,pg_dump,Migrating Data to RDS for PostgreSQL Using psql,Data Migration,User Guide", + "title":"Migrating Data to RDS for PostgreSQL Using psql", + "githuburl":"" + }, + { + "uri":"rds_pg_10_0000.html", + "product_code":"rds", + "code":"148", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Parameter Tuning", + "title":"Parameter Tuning", + "githuburl":"" + }, + { + "uri":"rds_pg_10_0001.html", + "product_code":"rds", + "code":"149", + "des":"Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some", + "doc_type":"usermanual", + "kw":"Suggestions on PostgreSQL Parameter Tuning,Parameter Tuning,User Guide", + "title":"Suggestions on PostgreSQL Parameter Tuning", + "githuburl":"" + }, + { + "uri":"rds_04_0001.html", + "product_code":"rds", + "code":"150", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"PostgreSQL Enhanced Edition", + "title":"PostgreSQL Enhanced Edition", + "githuburl":"" + }, + { + "uri":"rds_03_0018.html", + "product_code":"rds", + "code":"151", + "des":"PostgreSQL Enhanced Edition is developed from PostgreSQL 11. It retains all functions of the PostgreSQL databases. PostgreSQL Enhanced Edition supports system views, PL/S", + "doc_type":"usermanual", + "kw":"PostgreSQL Enhanced Edition,Introduction to PostgreSQL Enhanced Edition,PostgreSQL Enhanced Edition,", + "title":"Introduction to PostgreSQL Enhanced Edition", + "githuburl":"" + }, + { + "uri":"rds_04_0002.html", + "product_code":"rds", + "code":"152", + "des":"This section describes the built-in functions and advanced function packages added to PostgreSQL Enhanced Edition on the basis of PostgreSQL 11 open-source edition.", + "doc_type":"usermanual", + "kw":"Functions,PostgreSQL Enhanced Edition,User Guide", + "title":"Functions", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0000.html", + "product_code":"rds", + "code":"153", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Instance Lifecycle", + "title":"Instance Lifecycle", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0055.html", + "product_code":"rds", + "code":"154", + "des":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", + "doc_type":"usermanual", + "kw":"create a DB instance with the same configurations as the selected one,Creating a Same DB Instance as", + "title":"Creating a Same DB Instance as an Existing DB Instance", + "githuburl":"" + }, + { + "uri":"rds_pg_stop.html", + "product_code":"rds", + "code":"155", + "des":"If you use DB instances only for routine development, you can temporarily stop pay-per-use instances to save money. You can stop an instance for up to seven days.If you s", + "doc_type":"usermanual", + "kw":"Stopping an Instance,Instance Lifecycle,User Guide", + "title":"Stopping an Instance", + "githuburl":"" + }, + { + "uri":"rds_pg_start.html", + "product_code":"rds", + "code":"156", + "des":"You can stop your instance temporarily to save money. After stopping your instance, you can restart it to begin using it again.If you start a primary instance, read repli", + "doc_type":"usermanual", + "kw":"Starting an Instance,Instance Lifecycle,User Guide", + "title":"Starting an Instance", + "githuburl":"" + }, + { + "uri":"rds_09_0024.html", + "product_code":"rds", + "code":"157", + "des":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", + "doc_type":"usermanual", + "kw":"Rebooting DB Instances or Read Replicas,Instance Lifecycle,User Guide", + "title":"Rebooting DB Instances or Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_pg_06_0022.html", + "product_code":"rds", + "code":"158", + "des":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", + "doc_type":"usermanual", + "kw":"instance items,edit columns,Selecting Displayed Items,Instance Lifecycle,User Guide", + "title":"Selecting Displayed Items", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0017.html", + "product_code":"rds", + "code":"159", + "des":"You can export information about all or selected DB instances to view and analyze DB instance information.", + "doc_type":"usermanual", + "kw":"Exporting DB Instance Information,Instance Lifecycle,User Guide", + "title":"Exporting DB Instance Information", + "githuburl":"" + }, + { + "uri":"rds_09_0025.html", + "product_code":"rds", + "code":"160", + "des":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", + "doc_type":"usermanual", + "kw":"Deleting a DB Instance,Deleting a Read Replica,Deleting a DB Instance or Read Replica,Instance Lifec", + "title":"Deleting a DB Instance or Read Replica", + "githuburl":"" + }, + { + "uri":"rds_pg_recycle.html", + "product_code":"rds", + "code":"161", + "des":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", + "doc_type":"usermanual", + "kw":"Read replicas,Recycling a DB Instance,Instance Lifecycle,User Guide", + "title":"Recycling a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0001.html", + "product_code":"rds", + "code":"162", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Instance Modifications", + "title":"Instance Modifications", + "githuburl":"" + }, + { + "uri":"rds_pg_modify_instance_name.html", + "product_code":"rds", + "code":"163", + "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", + "doc_type":"usermanual", + "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", + "title":"Changing a DB Instance Name", + "githuburl":"" + }, + { + "uri":"rds_pg_modify_availability.html", + "product_code":"rds", + "code":"164", + "des":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", + "doc_type":"usermanual", + "kw":"failover priority,Changing the Failover Priority,Instance Modifications,User Guide", + "title":"Changing the Failover Priority", + "githuburl":"" + }, + { + "uri":"rds_pg_scale_rds.html", + "product_code":"rds", + "code":"165", + "des":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "doc_type":"usermanual", + "kw":"CPU or memory,Changing a DB Instance Class,Instance Modifications,User Guide", + "title":"Changing a DB Instance Class", + "githuburl":"" + }, + { + "uri":"rds_pg_scale_cluster.html", + "product_code":"rds", + "code":"166", + "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "doc_type":"usermanual", + "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", + "title":"Scaling up Storage Space", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0038.html", + "product_code":"rds", + "code":"167", + "des":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", + "doc_type":"usermanual", + "kw":"Changing the Maintenance Window,Instance Modifications,User Guide", + "title":"Changing the Maintenance Window", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0023.html", + "product_code":"rds", + "code":"168", + "des":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", + "doc_type":"usermanual", + "kw":"change single DB instances to primary/standby DB instances,Changing a DB Instance Type from Single t", + "title":"Changing a DB Instance Type from Single to Primary/Standby", + "githuburl":"" + }, + { + "uri":"rds_pg_switch_ha.html", + "product_code":"rds", + "code":"169", + "des":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", + "doc_type":"usermanual", + "kw":"Manually Switching Between Primary and Standby DB Instances,Instance Modifications,User Guide", + "title":"Manually Switching Between Primary and Standby DB Instances", + "githuburl":"" + }, + { + "uri":"rds_pg_11_0001.html", + "product_code":"rds", + "code":"170", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Read Replicas", + "title":"Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_pg_11_0002.html", + "product_code":"rds", + "code":"171", + "des":"RDS for PostgreSQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affec", + "doc_type":"usermanual", + "kw":"read replicas,Introducing Read Replicas,Read Replicas,User Guide", + "title":"Introducing Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_add_read_replica_pg.html", + "product_code":"rds", + "code":"172", + "des":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.You can create read replicas as needed.A maximum of five read replicas", + "doc_type":"usermanual", + "kw":"create read replicas,Creating a Read Replica,Read Replicas,User Guide", + "title":"Creating a Read Replica", + "githuburl":"" + }, + { + "uri":"rds_pg_11_0004.html", + "product_code":"rds", + "code":"173", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"read replica,Managing a Read Replica,Read Replicas,User Guide", + "title":"Managing a Read Replica", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0034.html", + "product_code":"rds", + "code":"174", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Backups and Restorations", + "title":"Backups and Restorations", + "githuburl":"" + }, + { + "uri":"rds_pg_backup_restore.html", + "product_code":"rds", + "code":"175", + "des":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", + "doc_type":"usermanual", + "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", + "title":"Working with Backups", + "githuburl":"" + }, + { + "uri":"rds_09_0027.html", + "product_code":"rds", + "code":"176", + "des":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", + "doc_type":"usermanual", + "kw":"Configuring an Automated Backup Policy,Backups and Restorations,User Guide", + "title":"Configuring an Automated Backup Policy", + "githuburl":"" + }, + { + "uri":"rds_09_0028.html", + "product_code":"rds", + "code":"177", + "des":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", + "doc_type":"usermanual", + "kw":"create manual backups,Creating a Manual Backup,Backups and Restorations,User Guide", + "title":"Creating a Manual Backup", + "githuburl":"" + }, + { + "uri":"rds_09_0031.html", + "product_code":"rds", + "code":"178", + "des":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", + "doc_type":"usermanual", + "kw":"download a manual or an automated backup file,full backup files,Downloading a Full Backup File,Backu", + "title":"Downloading a Full Backup File", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0138.html", + "product_code":"rds", + "code":"179", + "des":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", + "doc_type":"usermanual", + "kw":"automated backup,incremental backup files,Downloading an Incremental Backup File,Backups and Restora", + "title":"Downloading an Incremental Backup File", + "githuburl":"" + }, + { + "uri":"rds_09_0030.html", + "product_code":"rds", + "code":"180", + "des":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", + "doc_type":"usermanual", + "kw":"Restoring from Backup Files to RDS for PostgreSQL,Backups and Restorations,User Guide", + "title":"Restoring from Backup Files to RDS for PostgreSQL", + "githuburl":"" + }, + { + "uri":"rds_pg_08_0044.html", + "product_code":"rds", + "code":"181", + "des":"You can download backup files by referring to Downloading a Full Backup File and restore data from them.A tool for decompressing TAR files must be installed in a Unix-lik", + "doc_type":"usermanual", + "kw":"Restoring from Full Backup Files to a Self-Built PostgreSQL Database,Backups and Restorations,User G", + "title":"Restoring from Full Backup Files to a Self-Built PostgreSQL Database", + "githuburl":"" + }, + { + "uri":"rds_09_0029.html", + "product_code":"rds", + "code":"182", + "des":"You can restore from automated backups to a specified point in time.RDS for PostgreSQL supports restoration to a new, the original, or an existing DB instance.When you en", + "doc_type":"usermanual", + "kw":"to a specified point in time,RDS for PostgreSQL,restoration to a new, the original,,Restoring a DB I", + "title":"Restoring a DB Instance to a Point in Time", + "githuburl":"" + }, + { + "uri":"rds_09_0032.html", + "product_code":"rds", + "code":"183", + "des":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", + "doc_type":"usermanual", + "kw":"replicate a manual or an automated backup,Replicating a Backup,Backups and Restorations,User Guide", + "title":"Replicating a Backup", + "githuburl":"" + }, + { + "uri":"rds_09_0033.html", + "product_code":"rds", + "code":"184", + "des":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", + "doc_type":"usermanual", + "kw":"Deleting a Manual Backup,Backups and Restorations,User Guide", + "title":"Deleting a Manual Backup", + "githuburl":"" + }, + { + "uri":"rds_09_0034.html", + "product_code":"rds", + "code":"185", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Parameter Template Management", + "title":"Parameter Template Management", + "githuburl":"" + }, + { + "uri":"rds_pg_parameter_group.html", + "product_code":"rds", + "code":"186", + "des":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "doc_type":"usermanual", + "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", + "title":"Creating a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_pg_configuration.html", + "product_code":"rds", + "code":"187", + "des":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can change parameter values in custom parameter templates only and canno", + "doc_type":"usermanual", + "kw":"Modifying Instance Parameters,Parameter Template Management,User Guide", + "title":"Modifying Instance Parameters", + "githuburl":"" + }, + { + "uri":"rds_pg_08_0042.html", + "product_code":"rds", + "code":"188", + "des":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", + "doc_type":"usermanual", + "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", + "title":"Exporting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_09_0035.html", + "product_code":"rds", + "code":"189", + "des":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "doc_type":"usermanual", + "kw":"Compare,Comparing Parameter Templates,Parameter Template Management,User Guide", + "title":"Comparing Parameter Templates", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0099.html", + "product_code":"rds", + "code":"190", + "des":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", + "doc_type":"usermanual", + "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", + "title":"Viewing Parameter Change History", + "githuburl":"" + }, + { + "uri":"rds_09_0036.html", + "product_code":"rds", + "code":"191", + "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "doc_type":"usermanual", + "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", + "title":"Replicating a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_09_0037.html", + "product_code":"rds", + "code":"192", + "des":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", + "doc_type":"usermanual", + "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", + "title":"Resetting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0018.html", + "product_code":"rds", + "code":"193", + "des":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", + "doc_type":"usermanual", + "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", + "title":"Applying a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0098.html", + "product_code":"rds", + "code":"194", + "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "doc_type":"usermanual", + "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", + "title":"Viewing Application Records of a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_09_0038.html", + "product_code":"rds", + "code":"195", + "des":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", + "doc_type":"usermanual", + "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", + "title":"Modifying a Parameter Template Description", + "githuburl":"" + }, + { + "uri":"rds_09_0039.html", + "product_code":"rds", + "code":"196", + "des":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "doc_type":"usermanual", + "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", + "title":"Deleting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0005.html", + "product_code":"rds", + "code":"197", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connection Management", + "title":"Connection Management", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0024.html", + "product_code":"rds", + "code":"198", + "des":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", + "doc_type":"usermanual", + "kw":"change floating IP addresses,automatically-assigned IP address,change the floating IP address,Config", + "title":"Configuring and Changing a Floating IP Address", + "githuburl":"" + }, + { + "uri":"rds_pg_public_accessibility.html", + "product_code":"rds", + "code":"199", + "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", + "doc_type":"usermanual", + "kw":"Binding and Unbinding an EIP,Connection Management,User Guide", + "title":"Binding and Unbinding an EIP", + "githuburl":"" + }, + { + "uri":"rds_pg_change_database_port.html", + "product_code":"rds", + "code":"200", + "des":"This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the pri", + "doc_type":"usermanual", + "kw":"change the database port of a primary DB instance or a read replica,Changing a Database Port,Connect", + "title":"Changing a Database Port", + "githuburl":"" + }, + { + "uri":"rds_pg_11_0005.html", + "product_code":"rds", + "code":"201", + "des":"You can use the pgAdmin client to connect to an RDS DB instance.The pgAdmin version must be 4 or later.Prepare an ECS or a device that can access RDS DB instances.To conn", + "doc_type":"usermanual", + "kw":"pgAdmin,Connecting to a DB Instance Through pgAdmin,Connection Management,User Guide", + "title":"Connecting to a DB Instance Through pgAdmin", + "githuburl":"" + }, + { + "uri":"rds_09_0046.html", + "product_code":"rds", + "code":"202", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Plugin Management", + "title":"Plugin Management", + "githuburl":"" + }, + { + "uri":"rds_09_0043.html", + "product_code":"rds", + "code":"203", + "des":"RDS provides the PostgreSQL plugin management solution for user root. Except the following plugins, you need to manually create other plugins by referring to this section", + "doc_type":"usermanual", + "kw":"Creating or Deleting a Plugin,Plugin Management,User Guide", + "title":"Creating or Deleting a Plugin", + "githuburl":"" + }, + { + "uri":"rds_09_0045.html", + "product_code":"rds", + "code":"204", + "des":"The following table lists the plugins supported by the latest minor versions of RDS for PostgreSQL. You can use SELECT name FROM pg_available_extensions; to view the plug", + "doc_type":"usermanual", + "kw":"Supported Plugins,Plugin Management,User Guide", + "title":"Supported Plugins", + "githuburl":"" + }, + { + "uri":"rds_09_0044.html", + "product_code":"rds", + "code":"205", + "des":"RDS provides the PostgreSQL tablespace management solution based on user root.# psql --host=--port= --dbname=--username=root -c\"select cont", + "doc_type":"usermanual", + "kw":"PostgreSQL tablespace,Tablespace Management,Working with RDS for PostgreSQL,User Guide", + "title":"Tablespace Management", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0006.html", + "product_code":"rds", + "code":"206", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Data Security", + "title":"Data Security", + "githuburl":"" + }, + { + "uri":"rds_pg_reset_password.html", + "product_code":"rds", + "code":"207", + "des":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", + "doc_type":"usermanual", + "kw":"reset the administrator password,RDS,Resetting the Administrator Password,Data Security,User Guide", + "title":"Resetting the Administrator Password", + "githuburl":"" + }, + { + "uri":"rds_09_0026.html", + "product_code":"rds", + "code":"208", + "des":"This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the pri", + "doc_type":"usermanual", + "kw":"Changing a Security Group,Data Security,User Guide", + "title":"Changing a Security Group", + "githuburl":"" + }, + { + "uri":"rds_09_0041.html", + "product_code":"rds", + "code":"209", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Metrics and Alarms", + "title":"Metrics and Alarms", + "githuburl":"" + }, + { + "uri":"rds_pg_06_0001.html", + "product_code":"rds", + "code":"210", + "des":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", + "doc_type":"usermanual", + "kw":"Configuring Displayed Metrics,Metrics and Alarms,User Guide", + "title":"Configuring Displayed Metrics", + "githuburl":"" + }, + { + "uri":"rds_pg_06_0002.html", + "product_code":"rds", + "code":"211", + "des":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", + "doc_type":"usermanual", + "kw":"alarm rule,Setting Alarm Rules,Metrics and Alarms,User Guide", + "title":"Setting Alarm Rules", + "githuburl":"" + }, + { + "uri":"rds_pg_06_0003.html", + "product_code":"rds", + "code":"212", + "des":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", + "doc_type":"usermanual", + "kw":"Viewing Monitoring Metrics,Metrics and Alarms,User Guide", + "title":"Viewing Monitoring Metrics", + "githuburl":"" + }, + { + "uri":"rds_09_0042.html", + "product_code":"rds", + "code":"213", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Interconnection with CTS", + "title":"Interconnection with CTS", + "githuburl":"" + }, + { + "uri":"rds_pg_06_0004.html", + "product_code":"rds", + "code":"214", + "des":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", + "doc_type":"usermanual", + "kw":"Cloud Trace Service (CTS),Key Operations Supported by CTS,Interconnection with CTS,User Guide", + "title":"Key Operations Supported by CTS", + "githuburl":"" + }, + { + "uri":"rds_pg_06_0005.html", + "product_code":"rds", + "code":"215", + "des":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", + "doc_type":"usermanual", + "kw":"Viewing Tracing Events,Interconnection with CTS,User Guide", + "title":"Viewing Tracing Events", + "githuburl":"" + }, + { + "uri":"rds_08_001.html", + "product_code":"rds", + "code":"216", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Management", + "title":"Log Management", + "githuburl":"" + }, + { + "uri":"rds_recent_log.html", + "product_code":"rds", + "code":"217", + "des":"Error logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner ", + "doc_type":"usermanual", + "kw":"Viewing Error Logs,Log Management,User Guide", + "title":"Viewing Error Logs", + "githuburl":"" + }, + { + "uri":"slow_query_log-pg.html", + "product_code":"rds", + "code":"218", + "des":"Slow query logs record statements that exceed the log_min_duration_statement value. You can view log details to identify statements that are slowly executed and optimize ", + "doc_type":"usermanual", + "kw":"Viewing Slow Query Logs,Log Management,User Guide", + "title":"Viewing Slow Query Logs", + "githuburl":"" + }, + { + "uri":"rds_pg_05_0007.html", + "product_code":"rds", + "code":"219", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Task Center", + "title":"Task Center", + "githuburl":"" + }, + { + "uri":"rds_task_pg_0001.html", + "product_code":"rds", + "code":"220", + "des":"You can view the detailed progress and result of the task on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasC", + "doc_type":"usermanual", + "kw":"Viewing a Task,Task Center,User Guide", + "title":"Viewing a Task", + "githuburl":"" + }, + { + "uri":"rds_task_pg_0002.html", + "product_code":"rds", + "code":"221", + "des":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", + "doc_type":"usermanual", + "kw":"Deleting a Task Record,Task Center,User Guide", + "title":"Deleting a Task Record", + "githuburl":"" + }, + { + "uri":"rds_pg_tag.html", + "product_code":"rds", + "code":"222", + "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "doc_type":"usermanual", + "kw":"Tag Management Service (TMS),Managing Tags,Working with RDS for PostgreSQL,User Guide", + "title":"Managing Tags", + "githuburl":"" + }, + { + "uri":"rds_10_0000.html", + "product_code":"rds", + "code":"223", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Working with RDS for SQL Server", + "title":"Working with RDS for SQL Server", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0001_02.html", + "product_code":"rds", + "code":"224", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Data Migration", + "title":"Data Migration", + "githuburl":"" + }, + { + "uri":"rds_10_0035.html", + "product_code":"rds", + "code":"225", + "des":"You can access RDS DB instances through an EIP or ECS.Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through an EIP. To c", + "doc_type":"usermanual", + "kw":"Migrating Data to RDS for SQL Server Using SQL Server Management Studio,Data Migration,User Guide", + "title":"Migrating Data to RDS for SQL Server Using SQL Server Management Studio", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0000.html", + "product_code":"rds", + "code":"226", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Instance Lifecycle", + "title":"Instance Lifecycle", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0055.html", + "product_code":"rds", + "code":"227", + "des":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", + "doc_type":"usermanual", + "kw":"create a DB instance with the same configurations as the selected one,Creating a Same DB Instance as", + "title":"Creating a Same DB Instance as an Existing DB Instance", + "githuburl":"" + }, + { + "uri":"rds_11_0006.html", + "product_code":"rds", + "code":"228", + "des":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", + "doc_type":"usermanual", + "kw":"Rebooting DB Instances or Read Replicas,Instance Lifecycle,User Guide", + "title":"Rebooting DB Instances or Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_06_0022.html", + "product_code":"rds", + "code":"229", + "des":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", + "doc_type":"usermanual", + "kw":"instance items,edit columns,Selecting Displayed Items,Instance Lifecycle,User Guide", + "title":"Selecting Displayed Items", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0017.html", + "product_code":"rds", + "code":"230", + "des":"You can export information about all or selected DB instances to view and analyze DB instance information.", + "doc_type":"usermanual", + "kw":"Exporting DB Instance Information,Instance Lifecycle,User Guide", + "title":"Exporting DB Instance Information", + "githuburl":"" + }, + { + "uri":"rds_11_0030.html", + "product_code":"rds", + "code":"231", + "des":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", + "doc_type":"usermanual", + "kw":"Deleting a DB Instance,Deleting a Read Replica,Deleting a DB Instance or Read Replica,Instance Lifec", + "title":"Deleting a DB Instance or Read Replica", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_recycle.html", + "product_code":"rds", + "code":"232", + "des":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", + "doc_type":"usermanual", + "kw":"Read replicas,Recycling a DB Instance,Instance Lifecycle,User Guide", + "title":"Recycling a DB Instance", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0008.html", + "product_code":"rds", + "code":"233", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Instance Modifications", + "title":"Instance Modifications", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_modify_instance_name.html", + "product_code":"rds", + "code":"234", + "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", + "doc_type":"usermanual", + "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", + "title":"Changing a DB Instance Name", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_modify_availability.html", + "product_code":"rds", + "code":"235", + "des":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", + "doc_type":"usermanual", + "kw":"failover priority,Changing the Failover Priority,Instance Modifications,User Guide", + "title":"Changing the Failover Priority", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_scale_rds.html", + "product_code":"rds", + "code":"236", + "des":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "doc_type":"usermanual", + "kw":"CPU or memory,Changing a DB Instance Class,Instance Modifications,User Guide", + "title":"Changing a DB Instance Class", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_scale_cluster.html", + "product_code":"rds", + "code":"237", + "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "doc_type":"usermanual", + "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", + "title":"Scaling up Storage Space", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0023.html", + "product_code":"rds", + "code":"238", + "des":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", + "doc_type":"usermanual", + "kw":"change single DB instances to primary/standby DB instances,Changing a DB Instance Type from Single t", + "title":"Changing a DB Instance Type from Single to Primary/Standby", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_switch_ha.html", + "product_code":"rds", + "code":"239", + "des":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", + "doc_type":"usermanual", + "kw":"Manually Switching Between Primary and Standby DB Instances,Instance Modifications,User Guide", + "title":"Manually Switching Between Primary and Standby DB Instances", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_11_0001.html", + "product_code":"rds", + "code":"240", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Read Replicas", + "title":"Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_11_0002.html", + "product_code":"rds", + "code":"241", + "des":"Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and ser", + "doc_type":"usermanual", + "kw":"read replicas,Introducing Read Replicas,Read Replicas,User Guide", + "title":"Introducing Read Replicas", + "githuburl":"" + }, + { + "uri":"rds_03_0011.html", + "product_code":"rds", + "code":"242", + "des":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After a DB instance has been created, you can create read replicas for", + "doc_type":"usermanual", + "kw":"create read replicas,read replicas,Creating a Read Replica,Read Replicas,User Guide", + "title":"Creating a Read Replica", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_11_0004.html", + "product_code":"rds", + "code":"243", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"read replica,Managing a Read Replica,Read Replicas,User Guide", + "title":"Managing a Read Replica", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0034.html", + "product_code":"rds", + "code":"244", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Backups and Restorations", + "title":"Backups and Restorations", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_backup_restore.html", + "product_code":"rds", + "code":"245", + "des":"RDS supports DB instance backups and restorations to ensure data reliability.Automated backups are created during the backup period of your DB instances. RDS saves automa", + "doc_type":"usermanual", + "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", + "title":"Working with Backups", + "githuburl":"" + }, + { + "uri":"rds_11_0031.html", + "product_code":"rds", + "code":"246", + "des":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", + "doc_type":"usermanual", + "kw":"Configuring an Automated Backup Policy,Backups and Restorations,User Guide", + "title":"Configuring an Automated Backup Policy", + "githuburl":"" + }, + { + "uri":"rds_11_0010.html", + "product_code":"rds", + "code":"247", + "des":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", + "doc_type":"usermanual", + "kw":"create manual backups,Creating a Manual Backup,Backups and Restorations,User Guide", + "title":"Creating a Manual Backup", + "githuburl":"" + }, + { + "uri":"rds_11_0013.html", + "product_code":"rds", + "code":"248", + "des":"This section describes how to download a manual backup or an automated backup to a local device and restore data from the backup file.If the size of the backup data is gr", + "doc_type":"usermanual", + "kw":"automated backup,Downloading a Backup File,Backups and Restorations,User Guide", + "title":"Downloading a Backup File", + "githuburl":"" + }, + { + "uri":"rds_11_0023.html", + "product_code":"rds", + "code":"249", + "des":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created.Alternatively, click the target DB inst", + "doc_type":"usermanual", + "kw":"Restoring from Backup Files to RDS for SQL Server,Backups and Restorations,User Guide", + "title":"Restoring from Backup Files to RDS for SQL Server", + "githuburl":"" + }, + { + "uri":"rds_05_0044.html", + "product_code":"rds", + "code":"250", + "des":"You can download backup files by referring to section Downloading a Backup File and restore data from them. You can use SQL Server Management Studio (SSMS) to connect to ", + "doc_type":"usermanual", + "kw":"Restoring from Backup Files to a Self-Built SQL Server Database,Backups and Restorations,User Guide", + "title":"Restoring from Backup Files to a Self-Built SQL Server Database", + "githuburl":"" + }, + { + "uri":"rds_11_0022.html", + "product_code":"rds", + "code":"251", + "des":"You can restore from automated backups to a specified point in time.RDS for Microsoft SQL Server supports restoration to a new, the original, or an existing DB instance.I", + "doc_type":"usermanual", + "kw":"restoration to a new, the original,Restoring a DB Instance to a Point in Time,Backups and Restoratio", + "title":"Restoring a DB Instance to a Point in Time", + "githuburl":"" + }, + { + "uri":"rds_10_0055.html", + "product_code":"rds", + "code":"252", + "des":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", + "doc_type":"usermanual", + "kw":"replicate a manual or an automated backup,Replicating a Backup,Backups and Restorations,User Guide", + "title":"Replicating a Backup", + "githuburl":"" + }, + { + "uri":"rds_10_0101.html", + "product_code":"rds", + "code":"253", + "des":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", + "doc_type":"usermanual", + "kw":"Deleting a Manual Backup,Backups and Restorations,User Guide", + "title":"Deleting a Manual Backup", + "githuburl":"" + }, + { + "uri":"rds_10_0102.html", + "product_code":"rds", + "code":"254", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Parameter Template Management", + "title":"Parameter Template Management", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_parameter_group.html", + "product_code":"rds", + "code":"255", + "des":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "doc_type":"usermanual", + "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", + "title":"Creating a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_configuration.html", + "product_code":"rds", + "code":"256", + "des":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", + "doc_type":"usermanual", + "kw":"Modifying Parameters,Parameter Template Management,User Guide", + "title":"Modifying Parameters", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_08_0042.html", + "product_code":"rds", + "code":"257", + "des":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", + "doc_type":"usermanual", + "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", + "title":"Exporting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_10_0103.html", + "product_code":"rds", + "code":"258", + "des":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "doc_type":"usermanual", + "kw":"Compare,Comparing Parameter Templates,Parameter Template Management,User Guide", + "title":"Comparing Parameter Templates", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0099.html", + "product_code":"rds", + "code":"259", + "des":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", + "doc_type":"usermanual", + "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", + "title":"Viewing Parameter Change History", + "githuburl":"" + }, + { + "uri":"rds_10_0104.html", + "product_code":"rds", + "code":"260", + "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "doc_type":"usermanual", + "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", + "title":"Replicating a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_10_0105.html", + "product_code":"rds", + "code":"261", + "des":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", + "doc_type":"usermanual", + "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", + "title":"Resetting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0018.html", + "product_code":"rds", + "code":"262", + "des":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", + "doc_type":"usermanual", + "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", + "title":"Applying a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0098.html", + "product_code":"rds", + "code":"263", + "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "doc_type":"usermanual", + "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", + "title":"Viewing Application Records of a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_10_0106.html", + "product_code":"rds", + "code":"264", + "des":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", + "doc_type":"usermanual", + "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", + "title":"Modifying a Parameter Template Description", + "githuburl":"" + }, + { + "uri":"rds_10_0107.html", + "product_code":"rds", + "code":"265", + "des":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "doc_type":"usermanual", + "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", + "title":"Deleting a Parameter Template", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0005.html", + "product_code":"rds", + "code":"266", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Connection Management", + "title":"Connection Management", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0024.html", + "product_code":"rds", + "code":"267", + "des":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", + "doc_type":"usermanual", + "kw":"change floating IP addresses,self-configured floating IP address,Configuring and Changing a Floating", + "title":"Configuring and Changing a Floating IP Address", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_0025.html", + "product_code":"rds", + "code":"268", + "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", + "doc_type":"usermanual", + "kw":"Binding and Unbinding an EIP,Connection Management,User Guide", + "title":"Binding and Unbinding an EIP", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_change_database_port.html", + "product_code":"rds", + "code":"269", + "des":"This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the pri", + "doc_type":"usermanual", + "kw":"change the database port of a primary DB instance or a read replica,Changing a Database Port,Connect", + "title":"Changing a Database Port", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0006.html", + "product_code":"rds", + "code":"270", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Data Security", + "title":"Data Security", + "githuburl":"" + }, + { + "uri":"en-us_topic_sqlserver_reset_password.html", + "product_code":"rds", + "code":"271", + "des":"You can reset the administrator password only through the primary DB instance.You can also reset the password of your database account when using RDS.If you have changed ", + "doc_type":"usermanual", + "kw":"reset the administrator password,Resetting the Administrator Password,Data Security,User Guide", + "title":"Resetting the Administrator Password", + "githuburl":"" + }, + { + "uri":"rds_11_0032.html", + "product_code":"rds", + "code":"272", + "des":"This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the pri", + "doc_type":"usermanual", + "kw":"Changing a Security Group,Data Security,User Guide", + "title":"Changing a Security Group", + "githuburl":"" + }, + { + "uri":"rds_11_0004.html", + "product_code":"rds", + "code":"273", + "des":"Transparent Data Encryption (TDE) encrypts data files and backup files using certificates to implement real-time I/O encryption and decryption. This function effectively ", + "doc_type":"usermanual", + "kw":"Configuring the TDE Function,Data Security,User Guide", + "title":"Configuring the TDE Function", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_01_0001.html", + "product_code":"rds", + "code":"274", + "des":"The participator, transaction-supported server, resource server, and transaction manager of a distributed transaction are deployed on different nodes in a distributed sys", + "doc_type":"usermanual", + "kw":"Distributed Transactions,Working with RDS for SQL Server,User Guide", + "title":"Distributed Transactions", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_06_0000.html", + "product_code":"rds", + "code":"275", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Metrics and Alarms", + "title":"Metrics and Alarms", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_06_0001.html", + "product_code":"rds", + "code":"276", + "des":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", + "doc_type":"usermanual", + "kw":"Configuring Displayed Metrics,Metrics and Alarms,User Guide", + "title":"Configuring Displayed Metrics", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_06_0002.html", + "product_code":"rds", + "code":"277", + "des":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", + "doc_type":"usermanual", + "kw":"alarm rule,Setting Alarm Rules,Metrics and Alarms,User Guide", + "title":"Setting Alarm Rules", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_06_0003.html", + "product_code":"rds", + "code":"278", + "des":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", + "doc_type":"usermanual", + "kw":"Viewing Monitoring Metrics,Metrics and Alarms,User Guide", + "title":"Viewing Monitoring Metrics", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_01_0000.html", + "product_code":"rds", + "code":"279", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Interconnection with CTS", + "title":"Interconnection with CTS", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_06_0004.html", + "product_code":"rds", + "code":"280", + "des":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", + "doc_type":"usermanual", + "kw":"Cloud Trace Service (CTS),Key Operations Supported by CTS,Interconnection with CTS,User Guide", + "title":"Key Operations Supported by CTS", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_06_0005.html", + "product_code":"rds", + "code":"281", + "des":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", + "doc_type":"usermanual", + "kw":"Viewing Tracing Events,Interconnection with CTS,User Guide", + "title":"Viewing Tracing Events", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_log.html", + "product_code":"rds", + "code":"282", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Management", + "title":"Log Management", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_01_0002.html", + "product_code":"rds", + "code":"283", + "des":"System logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner", + "doc_type":"usermanual", + "kw":"Viewing System Logs,Log Management,User Guide", + "title":"Viewing System Logs", + "githuburl":"" + }, + { + "uri":"slow_query_log-sqlserver.html", + "product_code":"rds", + "code":"284", + "des":"Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details to identify statements that are executing slowly and optimiz", + "doc_type":"usermanual", + "kw":"Viewing and Downloading Slow Query Logs,Log Management,User Guide", + "title":"Viewing and Downloading Slow Query Logs", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_05_0007.html", + "product_code":"rds", + "code":"285", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Task Center", + "title":"Task Center", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_task_0001.html", + "product_code":"rds", + "code":"286", + "des":"You can view the progress and results of tasks on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasChanging sin", + "doc_type":"usermanual", + "kw":"Viewing a Task,Task Center,User Guide", + "title":"Viewing a Task", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_task_0002.html", + "product_code":"rds", + "code":"287", + "des":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", + "doc_type":"usermanual", + "kw":"Deleting a Task Record,Task Center,User Guide", + "title":"Deleting a Task Record", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_tag.html", + "product_code":"rds", + "code":"288", + "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "doc_type":"usermanual", + "kw":"Tag Management Service (TMS),Managing Tags,Working with RDS for SQL Server,User Guide", + "title":"Managing Tags", + "githuburl":"" + }, + { + "uri":"rds_faq_0000.html", + "product_code":"rds", + "code":"289", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"FAQs", + "title":"FAQs", + "githuburl":"" + }, + { + "uri":"rds_faq_0146.html", + "product_code":"rds", + "code":"290", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Product Consulting", + "title":"Product Consulting", + "githuburl":"" + }, + { + "uri":"rds_faq_0001.html", + "product_code":"rds", + "code":"291", + "des":"DB instance operating systems (OSs) are invisible to you. Your applications can access a database only through an IP address and a port.The backup files stored in Object ", + "doc_type":"usermanual", + "kw":"What Should I Pay Attention to When Using RDS?,Product Consulting,User Guide", + "title":"What Should I Pay Attention to When Using RDS?", + "githuburl":"" + }, + { + "uri":"rds_faq_0002.html", + "product_code":"rds", + "code":"292", + "des":"Calculation formula for RDS DB instance availability:DB instance availability = (1 – Failure duration/Total service duration) × 100%", + "doc_type":"usermanual", + "kw":"What Is the Availability of RDS DB Instances?,Product Consulting,User Guide", + "title":"What Is the Availability of RDS DB Instances?", + "githuburl":"" + }, + { + "uri":"rds_faq_0003.html", + "product_code":"rds", + "code":"293", + "des":"Currently, DB instance cannot be created using a template.", + "doc_type":"usermanual", + "kw":"Can I Use a Template to Create DB Instances?,Product Consulting,User Guide", + "title":"Can I Use a Template to Create DB Instances?", + "githuburl":"" + }, + { + "uri":"rds_faq_0004.html", + "product_code":"rds", + "code":"294", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"What Are the Differences Between RDS and Other Database Solutions?,Product Consulting,User Guide", + "title":"What Are the Differences Between RDS and Other Database Solutions?", + "githuburl":"" + }, + { + "uri":"rds_faq_0005.html", + "product_code":"rds", + "code":"295", + "des":"No. Your RDS DB instances and resources are isolated from other users' DB instances.", + "doc_type":"usermanual", + "kw":"Will My RDS DB Instances Be Affected by Other User Instances?,Product Consulting,User Guide", + "title":"Will My RDS DB Instances Be Affected by Other User Instances?", + "githuburl":"" + }, + { + "uri":"rds_faq_0073.html", + "product_code":"rds", + "code":"296", + "des":"Yes. RDS supports cross-AZ high availability. When you create primary/standby DB instances, you can select different AZs for them.", + "doc_type":"usermanual", + "kw":"Does RDS Support Cross-AZ High Availability?,Product Consulting,User Guide", + "title":"Does RDS Support Cross-AZ High Availability?", + "githuburl":"" + }, + { + "uri":"rds_faq_0104.html", + "product_code":"rds", + "code":"297", + "des":"No. RDS single DB instances can be changed to primary/standby DB instances, but not the other way around.", + "doc_type":"usermanual", + "kw":"Can RDS Primary/Standby DB Instances Be Changed to Single DB Instances?,Product Consulting,User Guid", + "title":"Can RDS Primary/Standby DB Instances Be Changed to Single DB Instances?", + "githuburl":"" + }, + { + "uri":"rds_faq_0110.html", + "product_code":"rds", + "code":"298", + "des":"The default code is utf8. You need to convert the default code to Unicode in the exported Excel file.", + "doc_type":"usermanual", + "kw":"What Should I Do If Garbled Characters Are Displayed After SQL Query Results Are Exported to an Exce", + "title":"What Should I Do If Garbled Characters Are Displayed After SQL Query Results Are Exported to an Excel File?", + "githuburl":"" + }, + { + "uri":"rds_faq_0008.html", + "product_code":"rds", + "code":"299", + "des":"To solve this problem:Check the performance of RDS DB instances on the RDS console.Compare the database connection status of local databases and RDS DB instances. This pr", + "doc_type":"usermanual", + "kw":"What Can I Do About Slow Respond of Websites When They Use RDS?,Product Consulting,User Guide", + "title":"What Can I Do About Slow Respond of Websites When They Use RDS?", + "githuburl":"" + }, + { + "uri":"rds_faq_0065.html", + "product_code":"rds", + "code":"300", + "des":"RDS provides the high availability. Select the primary/standby mode.Also called an unplanned handover. If the primary DB instance fails, the system will automatically swi", + "doc_type":"usermanual", + "kw":"How Does a Cloud Database Perform a Primary/Standby Switchover?,Product Consulting,User Guide", + "title":"How Does a Cloud Database Perform a Primary/Standby Switchover?", + "githuburl":"" + }, + { + "uri":"rds_faq_0013.html", + "product_code":"rds", + "code":"301", + "des":"Multiple ECSs can connect to the same RDS DB instance as long as the capability limits of a database are not exceeded.", + "doc_type":"usermanual", + "kw":"Can Multiple ECSs Connect to the Same RDS DB Instance?,Product Consulting,User Guide", + "title":"Can Multiple ECSs Connect to the Same RDS DB Instance?", + "githuburl":"" + }, + { + "uri":"rds_faq_0094.html", + "product_code":"rds", + "code":"302", + "des":"An error shown in Figure 1 is reported on SQL Server Management Studio when a database is being deleted from RDS SQL Server primary/standby DB instances.The database 'xxx", + "doc_type":"usermanual", + "kw":"Why Is an Error Reported When I Attempt to Delete a Database from RDS SQL Server Primary/Standby DB ", + "title":"Why Is an Error Reported When I Attempt to Delete a Database from RDS SQL Server Primary/Standby DB Instances?", + "githuburl":"" + }, + { + "uri":"rds_faq_0145.html", + "product_code":"rds", + "code":"303", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Resource and Disk Management", + "title":"Resource and Disk Management", + "githuburl":"" + }, + { + "uri":"rds_faq_0049.html", + "product_code":"rds", + "code":"304", + "des":"The following logs and files occupy RDS storage space.If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If d", + "doc_type":"usermanual", + "kw":"scale up storage space,Which Types of Logs and Files Occupy RDS Storage Space?,Resource and Disk Man", + "title":"Which Types of Logs and Files Occupy RDS Storage Space?", + "githuburl":"" + }, + { + "uri":"rds_faq_0047.html", + "product_code":"rds", + "code":"305", + "des":"Both your common data (excluding backup data) and the data required for the operation of your DB instances (such as system database data, rollback logs, redo logs, and in", + "doc_type":"usermanual", + "kw":"Which Items Occupy the Storage Space of My RDS DB Instances?,Resource and Disk Management,User Guide", + "title":"Which Items Occupy the Storage Space of My RDS DB Instances?", + "githuburl":"" + }, + { + "uri":"rds_faq_0048.html", + "product_code":"rds", + "code":"306", + "des":"The storage space you applied for will include space for the file system overhead required for inode, reserved block, and database operations.", + "doc_type":"usermanual", + "kw":"What Overhead Does the Storage Space Have After I Applied for an RDS DB Instance?,Resource and Disk ", + "title":"What Overhead Does the Storage Space Have After I Applied for an RDS DB Instance?", + "githuburl":"" + }, + { + "uri":"rds_faq_0082.html", + "product_code":"rds", + "code":"307", + "des":"Data Definition Language (DDL) operations may increase storage space usage sharply. To ensure that services are running properly, do not perform DDL operations during pea", + "doc_type":"usermanual", + "kw":"How Much Storage Space Is Required for DDL Operations?,Resource and Disk Management,User Guide", + "title":"How Much Storage Space Is Required for DDL Operations?", + "githuburl":"" + }, + { + "uri":"rds_faq_0006.html", + "product_code":"rds", + "code":"308", + "des":"There are no limitations on the number of DB instances running on RDS.", + "doc_type":"usermanual", + "kw":"How Many DB Instances Can Run on RDS?,Resource and Disk Management,User Guide", + "title":"How Many DB Instances Can Run on RDS?", + "githuburl":"" + }, + { + "uri":"rds_faq_0007.html", + "product_code":"rds", + "code":"309", + "des":"The maximum number of databases that can run on an RDS DB instance depends on the DB engine settings.If there are enough CPU, memory, and storage resources, there are no ", + "doc_type":"usermanual", + "kw":"How Many Databases Can Run on an RDS DB Instance?,Resource and Disk Management,User Guide", + "title":"How Many Databases Can Run on an RDS DB Instance?", + "githuburl":"" + }, + { + "uri":"rds_faq_0141.html", + "product_code":"rds", + "code":"310", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Connection", + "title":"Database Connection", + "githuburl":"" + }, + { + "uri":"rds_faq_0018.html", + "product_code":"rds", + "code":"311", + "des":"For a DB instance that has an EIP bound, you can access it through the EIP.Enable a VPN in a VPC and use the VPN to connect to the RDS DB instance.Create an RDS and an EC", + "doc_type":"usermanual", + "kw":"Can an External Server Access the RDS Database?,Database Connection,User Guide", + "title":"Can an External Server Access the RDS Database?", + "githuburl":"" + }, + { + "uri":"rds_faq_0019.html", + "product_code":"rds", + "code":"312", + "des":"The number of database connections indicates the number of applications that can be simultaneously connected to a database, and is irrelevant to the maximum number of use", + "doc_type":"usermanual", + "kw":"What Do I Do If the Number of RDS Database Connections Reaches the Upper Limit?,Database Connection,", + "title":"What Do I Do If the Number of RDS Database Connections Reaches the Upper Limit?", + "githuburl":"" + }, + { + "uri":"rds_faq_0055.html", + "product_code":"rds", + "code":"313", + "des":"RDS does not have constraints on the number of connections. This number is determined by the default value and value range of the DB engine. For example, you can set max_", + "doc_type":"usermanual", + "kw":"What Is the Maximum Number of Connections to an RDS DB Instance?,Database Connection,User Guide", + "title":"What Is the Maximum Number of Connections to an RDS DB Instance?", + "githuburl":"" + }, + { + "uri":"rds_faq_0057.html", + "product_code":"rds", + "code":"314", + "des":"For details about how to create an ECS, see the Elastic Cloud Server User Guide.If you connect to an RDS DB instance through a private network, ensure that the ECS and DB", + "doc_type":"usermanual", + "kw":"How Can I Create and Connect to an ECS?,Database Connection,User Guide", + "title":"How Can I Create and Connect to an ECS?", + "githuburl":"" + }, + { + "uri":"rds_faq_0020.html", + "product_code":"rds", + "code":"315", + "des":"Perform the following steps to identify the problem:If they are in the same VPC, go to 2.If they are in different VPCs, create an ECS in the VPC in which the RDS DB insta", + "doc_type":"usermanual", + "kw":"What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?,Database ", + "title":"What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?", + "githuburl":"" + }, + { + "uri":"rds_faq_0021.html", + "product_code":"rds", + "code":"316", + "des":"Troubleshoot RDS connection failures caused by a client problem by checking the following items:ECS Security PolicyIn Windows, check whether the RDS instance port is enab", + "doc_type":"usermanual", + "kw":"What Should I Do If a Database Client Problem Causes a Connection Failure?,Database Connection,User ", + "title":"What Should I Do If a Database Client Problem Causes a Connection Failure?", + "githuburl":"" + }, + { + "uri":"rds_faq_0022.html", + "product_code":"rds", + "code":"317", + "des":"Check whether any of the following problems occurred on the RDS DB instance.The RDS DB instance is not properly connected.Solution: Check the connection. If you connect t", + "doc_type":"usermanual", + "kw":"What Should I Do If an RDS Database Problem Causes a Connection Failure?,Database Connection,User Gu", + "title":"What Should I Do If an RDS Database Problem Causes a Connection Failure?", + "githuburl":"" + }, + { + "uri":"rds_faq_0023.html", + "product_code":"rds", + "code":"318", + "des":"Ensure that the ECS in which your applications are located is in the same VPC as the RDS DB instance. If the ECS and the RDS DB instance are in different VPCs, modify the", + "doc_type":"usermanual", + "kw":"How Do My Applications Access an RDS DB Instance in a VPC?,Database Connection,User Guide", + "title":"How Do My Applications Access an RDS DB Instance in a VPC?", + "githuburl":"" + }, + { + "uri":"rds_faq_0024.html", + "product_code":"rds", + "code":"319", + "des":"It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the d", + "doc_type":"usermanual", + "kw":"Do Applications Need to Support Reconnecting to the RDS DB Instance Automatically?,Database Connecti", + "title":"Do Applications Need to Support Reconnecting to the RDS DB Instance Automatically?", + "githuburl":"" + }, + { + "uri":"rds_faq_0050.html", + "product_code":"rds", + "code":"320", + "des":"Although the SSL certificate is optional if you choose to connect to a database through Java database connectivity (JDBC), download an SSL certificate to encrypt the conn", + "doc_type":"usermanual", + "kw":"How Can I Connect to a PostgreSQL Database Through JDBC?,Database Connection,User Guide", + "title":"How Can I Connect to a PostgreSQL Database Through JDBC?", + "githuburl":"" + }, + { + "uri":"rds_faq_0100.html", + "product_code":"rds", + "code":"321", + "des":"Check whether the ECS can connect to the RDS DB instance.If the ECS cannot connect to the RDS DB instance, check whether the ECS and RDS DB instance are located in the sa", + "doc_type":"usermanual", + "kw":"What Should I Do If an RDS Microsoft SQL Server DB Instance Failed to Be Connected?,Database Connect", + "title":"What Should I Do If an RDS Microsoft SQL Server DB Instance Failed to Be Connected?", + "githuburl":"" + }, + { + "uri":"rds_faq_0101.html", + "product_code":"rds", + "code":"322", + "des":"By default, RDS DB instances cannot be accessed over an intranet across regions. Cloud services in different regions cannot communicate with each other over an intranet. ", + "doc_type":"usermanual", + "kw":"Can I Access an RDS DB Instance Over an Intranet Connection Across Regions?,Database Connection,User", + "title":"Can I Access an RDS DB Instance Over an Intranet Connection Across Regions?", + "githuburl":"" + }, + { + "uri":"rds_faq_0111.html", + "product_code":"rds", + "code":"323", + "des":"For DB instances connected using SSL, a primary/standby switchover or failover does not interrupt the connection because the SSL certificate is still valid for both the p", + "doc_type":"usermanual", + "kw":"Is an SSL Connection to a DB Instance Interrupted After a Primary/Standby Switchover or Failover?,Da", + "title":"Is an SSL Connection to a DB Instance Interrupted After a Primary/Standby Switchover or Failover?", + "githuburl":"" + }, + { + "uri":"rds_faq_0070.html", + "product_code":"rds", + "code":"324", + "des":"MySQL supports SSL connections. Different from other vendors, RDS for MySQL enables the SSL connection on the database server by default. When you use a client to connect", + "doc_type":"usermanual", + "kw":"Does MySQL Support SSL Connections?,Database Connection,User Guide", + "title":"Does MySQL Support SSL Connections?", + "githuburl":"" + }, + { + "uri":"rds_faq_0034.html", + "product_code":"rds", + "code":"325", + "des":"You may have restored from a backup before you reset the administrator password.Check whether the DB instance was restored after you reset the administrator password.Log ", + "doc_type":"usermanual", + "kw":"Why Did the New Password Not Take Effect After I Reset the Administrator Password?,Database Connecti", + "title":"Why Did the New Password Not Take Effect After I Reset the Administrator Password?", + "githuburl":"" + }, + { + "uri":"rds_faq_0155.html", + "product_code":"rds", + "code":"326", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Migration", + "title":"Database Migration", + "githuburl":"" + }, + { + "uri":"rds_faq_0026.html", + "product_code":"rds", + "code":"327", + "des":"The mysqldump or pg_dump tool is easy to use for data migration. However, when you use this tool, the server is stopped for a long period of time during data migration. O", + "doc_type":"usermanual", + "kw":"Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?,Database Migration,User Guide", + "title":"Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?", + "githuburl":"" + }, + { + "uri":"rds_faq_0025.html", + "product_code":"rds", + "code":"328", + "des":"Exporting or importing data between DB engines of the same type is called homogeneous database export or import.Exporting or importing data between DB engines of differen", + "doc_type":"usermanual", + "kw":"What Types of DB Engines Does RDS Support for Importing Data?,Database Migration,User Guide", + "title":"What Types of DB Engines Does RDS Support for Importing Data?", + "githuburl":"" + }, + { + "uri":"rds_faq_0154.html", + "product_code":"rds", + "code":"329", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Permission", + "title":"Database Permission", + "githuburl":"" + }, + { + "uri":"rds_faq_0075.html", + "product_code":"rds", + "code":"330", + "des":"Most relational database cloud service platforms do not provide super permissions for the root user. The super permissions allow users to execute many management commands", + "doc_type":"usermanual", + "kw":"Why Does the Root User Not Have the Super Permissions?,Database Permission,User Guide", + "title":"Why Does the Root User Not Have the Super Permissions?", + "githuburl":"" + }, + { + "uri":"rds_faq_0144.html", + "product_code":"rds", + "code":"331", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Storage", + "title":"Database Storage", + "githuburl":"" + }, + { + "uri":"rds_faq_0041.html", + "product_code":"rds", + "code":"332", + "des":"The database storage engine is a core service for storing, processing, and protecting data. It can be used to control access permissions and rapidly process transactions ", + "doc_type":"usermanual", + "kw":"What Storage Engines Does the RDS for MySQL Support?,Database Storage,User Guide", + "title":"What Storage Engines Does the RDS for MySQL Support?", + "githuburl":"" + }, + { + "uri":"rds_faq_0045.html", + "product_code":"rds", + "code":"333", + "des":"RDS uses Elastic Volume Service (EVS) disks for storage. For details about EVS disks, see Elastic Volume Service Product Introduction.The RDS backup data is stored in OBS", + "doc_type":"usermanual", + "kw":"What Is the RDS DB Instance Storage Configuration?,Database Storage,User Guide", + "title":"What Is the RDS DB Instance Storage Configuration?", + "githuburl":"" + }, + { + "uri":"rds_faq_0076.html", + "product_code":"rds", + "code":"334", + "des":"No. After an RDS DB instance is created, the storage type cannot be changed.", + "doc_type":"usermanual", + "kw":"Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?,Database Stor", + "title":"Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?", + "githuburl":"" + }, + { + "uri":"rds_faq_0046.html", + "product_code":"rds", + "code":"335", + "des":"There is not enough storage available for an RDS DB instance and the DB instance has entered read-only status, or applications can no longer read from or write to the dat", + "doc_type":"usermanual", + "kw":"What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?,Database Storage,Us", + "title":"What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?", + "githuburl":"" + }, + { + "uri":"rds_faq_0152.html", + "product_code":"rds", + "code":"336", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Client Installation", + "title":"Client Installation", + "githuburl":"" + }, + { + "uri":"rds_faq_0027.html", + "product_code":"rds", + "code":"337", + "des":"MySQL provides client installation packages for different OSs on its official website. MySQL 5.6 is used as an example. Download the MySQL 5.6 client installation package", + "doc_type":"usermanual", + "kw":"How Can I Install the MySQL Client?,Client Installation,User Guide", + "title":"How Can I Install the MySQL Client?", + "githuburl":"" + }, + { + "uri":"rds_faq_0029.html", + "product_code":"rds", + "code":"338", + "des":"PostgreSQL provides client installation packages and the required dynamic shared library packages for different OSs on its official website.Ensure that the database clien", + "doc_type":"usermanual", + "kw":"How Can I Install the PostgreSQL Client?,Client Installation,User Guide", + "title":"How Can I Install the PostgreSQL Client?", + "githuburl":"" + }, + { + "uri":"rds_faq_0032.html", + "product_code":"rds", + "code":"339", + "des":"The Microsoft SQL Server official website provides the SQL Server Management Studio installation package. SQL Server Management Studio applications can run in the Windows", + "doc_type":"usermanual", + "kw":"How Can I Install SQL Server Management Studio?,Client Installation,User Guide", + "title":"How Can I Install SQL Server Management Studio?", + "githuburl":"" + }, + { + "uri":"rds_faq_0098.html", + "product_code":"rds", + "code":"340", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Backup and Restoration", + "title":"Backup and Restoration", + "githuburl":"" + }, + { + "uri":"rds_faq_0043.html", + "product_code":"rds", + "code":"341", + "des":"Automated backup data is kept based on the backup retention period you specified. There is no limit for the manual backup retention period. You can delete manual backups ", + "doc_type":"usermanual", + "kw":"How Long Does RDS Store Backup Data For?,Backup and Restoration,User Guide", + "title":"How Long Does RDS Store Backup Data For?", + "githuburl":"" + }, + { + "uri":"rds_faq_0044.html", + "product_code":"rds", + "code":"342", + "des":"A backup window is a user-specified time during which RDS DB instances are backed up. With these periodic data backups, RDS allows you to restore DB instances to the back", + "doc_type":"usermanual", + "kw":"Can My Database Be Used in the Backup Window?,Backup and Restoration,User Guide", + "title":"Can My Database Be Used in the Backup Window?", + "githuburl":"" + }, + { + "uri":"rds_faq_0042.html", + "product_code":"rds", + "code":"343", + "des":"You can back up data to an ECS the same way you export SQL statements. The ECS service does not have restrictions on the types of data to be backed up as long as the data", + "doc_type":"usermanual", + "kw":"How Can I Back Up an RDS Database to an ECS?,Backup and Restoration,User Guide", + "title":"How Can I Back Up an RDS Database to an ECS?", + "githuburl":"" + }, + { + "uri":"rds_faq_0053.html", + "product_code":"rds", + "code":"344", + "des":"Automated backups may fail for the following reasons:The network environment is unstable due to issues such as network delay or interruption. RDS will detect these proble", + "doc_type":"usermanual", + "kw":"Why Has My Automated Backup Failed?,Backup and Restoration,User Guide", + "title":"Why Has My Automated Backup Failed?", + "githuburl":"" + }, + { + "uri":"rds_faq_0014.html", + "product_code":"rds", + "code":"345", + "des":"When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.", + "doc_type":"usermanual", + "kw":"What Happens to Database Backups After an RDS DB Instance Is Deleted?,Backup and Restoration,User Gu", + "title":"What Happens to Database Backups After an RDS DB Instance Is Deleted?", + "githuburl":"" + }, + { + "uri":"rds_faq_0015.html", + "product_code":"rds", + "code":"346", + "des":"If your cloud account is deleted, both your automated and manual backups are deleted.", + "doc_type":"usermanual", + "kw":"Will My Backups Be Deleted If I Delete My Cloud Account?,Backup and Restoration,User Guide", + "title":"Will My Backups Be Deleted If I Delete My Cloud Account?", + "githuburl":"" + }, + { + "uri":"rds_faq_0012.html", + "product_code":"rds", + "code":"347", + "des":"RDS does not delete or perform any operations on any user data. If this problem occurs, check if there have been any misoperations and restore the data from backup files,", + "doc_type":"usermanual", + "kw":"Why Is a Table or Data Missing from My Database?,Backup and Restoration,User Guide", + "title":"Why Is a Table or Data Missing from My Database?", + "githuburl":"" + }, + { + "uri":"rds_faq_0151.html", + "product_code":"rds", + "code":"348", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Monitoring", + "title":"Database Monitoring", + "githuburl":"" + }, + { + "uri":"rds_faq_0036.html", + "product_code":"rds", + "code":"349", + "des":"You need to pay attention to CPU, memory, and storage space usage.You can configure the system to report alarms based on service requirements and take measures to handle ", + "doc_type":"usermanual", + "kw":"Which DB Instance Monitoring Metrics Do I Need to Pay Attention To?,Database Monitoring,User Guide", + "title":"Which DB Instance Monitoring Metrics Do I Need to Pay Attention To?", + "githuburl":"" + }, + { + "uri":"rds_faq_0150.html", + "product_code":"rds", + "code":"350", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Capacity Expansion and Specification Change", + "title":"Capacity Expansion and Specification Change", + "githuburl":"" + }, + { + "uri":"rds_faq_0016.html", + "product_code":"rds", + "code":"351", + "des":"Currently, you can scale up storage space and change the CPU or memory of a DB instance.When storage space is being scaled up, RDS DB instances are still available and se", + "doc_type":"usermanual", + "kw":"Are My RDS DB Instances Available When Scaling?,Capacity Expansion and Specification Change,User Gui", + "title":"Are My RDS DB Instances Available When Scaling?", + "githuburl":"" + }, + { + "uri":"rds_faq_0035.html", + "product_code":"rds", + "code":"352", + "des":"The DB instance is in Faulty state after the original database port is changed.The DB instance cannot be connected using the new database port.The submitted database port", + "doc_type":"usermanual", + "kw":"Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?,Capacity Expansi", + "title":"Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?", + "githuburl":"" + }, + { + "uri":"rds_faq_0142.html", + "product_code":"rds", + "code":"353", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Parameter Modification", + "title":"Database Parameter Modification", + "githuburl":"" + }, + { + "uri":"rds_faq_0031.html", + "product_code":"rds", + "code":"354", + "des":"In the following cases, inappropriate parameter settings cause the database to be unavailable:Parameter value ranges are related to DB instance specifications.The maximum", + "doc_type":"usermanual", + "kw":"What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?,Database Para", + "title":"What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?", + "githuburl":"" + }, + { + "uri":"rds_faq_0119.html", + "product_code":"rds", + "code":"355", + "des":"PostgreSQL 10, PostgreSQL 11, PostgreSQL 12 and PostgreSQL 13 support test_decoding. For more information about test_decoding, see test_decoding introduction.To use test_", + "doc_type":"usermanual", + "kw":"Does RDS for PostgreSQL Support the test_decoding Plugin?,Database Parameter Modification,User Guide", + "title":"Does RDS for PostgreSQL Support the test_decoding Plugin?", + "githuburl":"" + }, + { + "uri":"rds_faq_0092.html", + "product_code":"rds", + "code":"356", + "des":"When you add NDF files of the custom database and the tempdb database, do not place them in the C drive. If you place them in the C drive, the system disk space will be u", + "doc_type":"usermanual", + "kw":"Where Should I Store the NDF Files for Microsoft SQL Server?,Database Parameter Modification,User Gu", + "title":"Where Should I Store the NDF Files for Microsoft SQL Server?", + "githuburl":"" + }, + { + "uri":"rds_faq_0149.html", + "product_code":"rds", + "code":"357", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Log Management", + "title":"Log Management", + "githuburl":"" + }, + { + "uri":"rds_faq_0078.html", + "product_code":"rds", + "code":"358", + "des":"Generally, the delay is 5 minutes. If the size of slow query logs reaches 10 MB within 5 minutes, the logs will be uploaded to OBS.", + "doc_type":"usermanual", + "kw":"How Long Is the Delay for RDS MySQL Slow Query Logs?,Log Management,User Guide", + "title":"How Long Is the Delay for RDS MySQL Slow Query Logs?", + "githuburl":"" + }, + { + "uri":"rds_faq_0077.html", + "product_code":"rds", + "code":"359", + "des":"The slow query threshold is 5 seconds.", + "doc_type":"usermanual", + "kw":"What's the Slow Query Threshold for Microsoft SQL Server?,Log Management,User Guide", + "title":"What's the Slow Query Threshold for Microsoft SQL Server?", + "githuburl":"" + }, + { + "uri":"rds_faq_0059.html", + "product_code":"rds", + "code":"360", + "des":"EXECUTE master.dbo.rds_read_errorlogFileID,LogType,FilterText,FilterBeginTime,FilterEndTimeFileID: indicates the ID of an error log. The value 0 indicates the latest logs", + "doc_type":"usermanual", + "kw":"How Can I Obtain Microsoft SQL Server Error Logs Using Commands?,Log Management,User Guide", + "title":"How Can I Obtain Microsoft SQL Server Error Logs Using Commands?", + "githuburl":"" + }, + { + "uri":"rds_faq_0120.html", + "product_code":"rds", + "code":"361", + "des":"Sorry, statistics on RDS slow query logs cannot be exported.", + "doc_type":"usermanual", + "kw":"Can I Export Statistics on RDS Slow Query Logs?,Log Management,User Guide", + "title":"Can I Export Statistics on RDS Slow Query Logs?", + "githuburl":"" + }, + { + "uri":"rds_faq_0143.html", + "product_code":"rds", + "code":"362", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Network Security", + "title":"Network Security", + "githuburl":"" + }, + { + "uri":"rds_faq_0038.html", + "product_code":"rds", + "code":"363", + "des":"RDS runs your DB instances in a VPC, ensuring that the DB instances are isolated from other services.RDS uses security groups to ensure that only trusted sources can acce", + "doc_type":"usermanual", + "kw":"What Security Protection Policies Does RDS Have?,Network Security,User Guide", + "title":"What Security Protection Policies Does RDS Have?", + "githuburl":"" + }, + { + "uri":"rds_faq_0040.html", + "product_code":"rds", + "code":"364", + "des":"The VPC security group helps ensure the security of RDS in a VPC. In addition, an ACL can be used to allow or reject I/O network traffic for each subnet.", + "doc_type":"usermanual", + "kw":"How Can I Ensure the Security of RDS DB Instances in a VPC?,Network Security,User Guide", + "title":"How Can I Ensure the Security of RDS DB Instances in a VPC?", + "githuburl":"" + }, + { + "uri":"rds_faq_0039.html", + "product_code":"rds", + "code":"365", + "des":"When you access RDS through an EIP, service data will be transmitted on the public network. To prevent any potential data breaches, you are advised to use SSL to encrypt ", + "doc_type":"usermanual", + "kw":"How Can Data Security Be Ensured During Transmission When I Access RDS Through an EIP?,Network Secur", + "title":"How Can Data Security Be Ensured During Transmission When I Access RDS Through an EIP?", + "githuburl":"" + }, + { + "uri":"rds_faq_0056.html", + "product_code":"rds", + "code":"366", + "des":"If you enable public accessibility, your EIP DNS and database port may be vulnerable to hacking. To protect information such as your EIP, DNS, database port, database acc", + "doc_type":"usermanual", + "kw":"How Can I Prevent Untrusted Source IP Addresses from Accessing RDS?,Network Security,User Guide", + "title":"How Can I Prevent Untrusted Source IP Addresses from Accessing RDS?", + "githuburl":"" + }, + { + "uri":"rds_faq_0054.html", + "product_code":"rds", + "code":"367", + "des":"When you attempt to connect to a DB instance through a private network, check whether the ECS and RDS DB instance are in the same security group.If the ECS and RDS DB ins", + "doc_type":"usermanual", + "kw":"How Do I Configure a Security Group to Enable Access to RDS DB Instances?,Network Security,User Guid", + "title":"How Do I Configure a Security Group to Enable Access to RDS DB Instances?", + "githuburl":"" + }, + { + "uri":"rds_faq_0052.html", + "product_code":"rds", + "code":"368", + "des":"Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.On the displayed console, choose File > Add/Remove Snap-in.In the left Available sn", + "doc_type":"usermanual", + "kw":"How Can I Import the Root Certificate to a Windows or Linux OS?,Network Security,User Guide", + "title":"How Can I Import the Root Certificate to a Windows or Linux OS?", + "githuburl":"" + }, + { + "uri":"rds_faq_0051.html", + "product_code":"rds", + "code":"369", + "des":"When you connect to an RDS MySQL DB instance using an SSL connection, run the following command to check whether the certificate has expired:Update the root certificate t", + "doc_type":"usermanual", + "kw":"How Can I Identify the Validity Period of an SSL Root Certificate?,Network Security,User Guide", + "title":"How Can I Identify the Validity Period of an SSL Root Certificate?", + "githuburl":"" + }, + { + "uri":"rds_faq_0011.html", + "product_code":"rds", + "code":"370", + "des":"Data tamperingLots of security measures are provided to ensure that only authenticated users have permissions to perform operations on database table records. Database ta", + "doc_type":"usermanual", + "kw":"How Can I Identify Data Corruption?,Network Security,User Guide", + "title":"How Can I Identify Data Corruption?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0000001419863378.html", + "product_code":"rds", + "code":"371", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Change History,User Guide", + "title":"Change History", + "githuburl":"" + }, + { + "uri":"rds_glossary_0001.html", + "product_code":"rds", + "code":"372", + "des":"For details about the glossaries in this document, see Glossary.", + "doc_type":"usermanual", + "kw":"Glossary,User Guide", + "title":"Glossary", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/rds/umn/CLASS.TXT.json b/docs/rds/umn/CLASS.TXT.json new file mode 100644 index 000000000..f748c1c74 --- /dev/null +++ b/docs/rds/umn/CLASS.TXT.json @@ -0,0 +1,3350 @@ +[ + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Introduction", + "uri":"rds_01_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"RDS is a cloud-based web service that is reliable, scalable, and easy to manage. RDS supports the following DB engines:MySQLPostgreSQLMicrosoft SQL ServerRDS provides a c", + "product_code":"rds", + "title":"What Is RDS?", + "uri":"en-us_topic_dashboard.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"2" + }, + { + "desc":"The smallest management unit of RDS is the DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance runs a DB engine. For details abo", + "product_code":"rds", + "title":"Basic Concepts", + "uri":"rds_01_0015.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"3" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Advantages", + "uri":"rds_01_0001.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"4" + }, + { + "desc":"You can create a DB instance on the management console within minutes and access RDS from an ECS to reduce the application response time and avoid paying for the traffic ", + "product_code":"rds", + "title":"Easy Management", + "uri":"rds_01_0002.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"5" + }, + { + "desc":"RDS uses Virtual Private Cloud (VPC) and network security groups to isolate and secure your DB instances. VPCs allow you to define what IP address range can access RDS. Y", + "product_code":"rds", + "title":"High Security", + "uri":"rds_01_0004.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"6" + }, + { + "desc":"RDS uses the hot standby architecture, in which failover upon fault occurrence takes only some seconds.RDS automatically backs up data every day and transfers backup file", + "product_code":"rds", + "title":"High Reliability", + "uri":"rds_01_0005.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"7" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Comparison Between RDS and Self-Built Databases", + "uri":"rds_01_0006.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"8" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Product Series", + "uri":"rds_01_0009.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"9" + }, + { + "desc":"Currently, RDS DB instances are classified into the following types:SinglePrimary/StandbySinglePrimary/StandbyDifferent series support different DB engines and instance s", + "product_code":"rds", + "title":"DB Instance Introduction", + "uri":"rds_01_0010.html", + "doc_type":"usermanual", + "p_code":"9", + "code":"10" + }, + { + "desc":"Single DB instances use a single-node architecture. Different from the primary/standby DB instances, a single DB instance contains only one node and has no slave node for", + "product_code":"rds", + "title":"Function Comparison", + "uri":"rds_00_0011.html", + "doc_type":"usermanual", + "p_code":"9", + "code":"11" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"DB Instance Description", + "uri":"rds_01_0028.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"12" + }, + { + "desc":"The smallest management unit of RDS is the DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance can contain multiple user-created", + "product_code":"rds", + "title":"DB Instance Types", + "uri":"rds_01_0016.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"13" + }, + { + "desc":"General-enhanced and general-enhanced II instance classes provide robust and stable performance. They use latest-generation network acceleration engines and Data Plane De", + "product_code":"rds", + "title":"DB Instance Classes", + "uri":"rds_01_0029.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"14" + }, + { + "desc":"Table 1 lists the DB engines and versions supported by RDS.For new applications, you are advised to use the latest major version of the DB engine, for example, MySQL 8.0.", + "product_code":"rds", + "title":"DB Engines and Versions", + "uri":"en-us_topic_0043898356.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"15" + }, + { + "desc":"The status of a DB instance indicates the health of the DB instance. You can use the management console or API to view the status of a DB instance.", + "product_code":"rds", + "title":"DB Instance Statuses", + "uri":"rds_01_0023.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"16" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Typical Applications", + "uri":"rds_01_0024.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"17" + }, + { + "desc":"RDS for MySQL, RDS for PostgreSQL, and RDS for SQL Server 2017 Enterprise Edition DB instances support read replicas to offload read traffic from primary DB instances.For", + "product_code":"rds", + "title":"Read/Write Splitting", + "uri":"rds_01_0012.html", + "doc_type":"usermanual", + "p_code":"17", + "code":"18" + }, + { + "desc":"RDS supports diverse storage extension through Distributed Cache Service (DCS) for Memcached, DCS for Redis, and OBS.", + "product_code":"rds", + "title":"Diversified Data Storage", + "uri":"rds_01_0013.html", + "doc_type":"usermanual", + "p_code":"17", + "code":"19" + }, + { + "desc":"RDS provides two types of user permissions by default: user management and resource management.User management permissions cover the management of users, user groups, and", + "product_code":"rds", + "title":"User Permissions", + "uri":"rds_01_0025.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"20" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Constraints", + "uri":"rds_01_0026.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"21" + }, + { + "desc":"Table 1 shows the constraints designed to ensure the stability and security of RDS for MySQL.", + "product_code":"rds", + "title":"MySQL Constraints", + "uri":"rds_02_0002.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"22" + }, + { + "desc":"Table 1 shows the constraints designed to ensure the stability and security of RDS for PostgreSQL.", + "product_code":"rds", + "title":"PostgreSQL Constraints", + "uri":"rds_02_0012.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"23" + }, + { + "desc":"RDS for SQL Server only supports DB instances under the License Included model and does not support \"bring your own license\" (BYOL). After a DB instance is created, it co", + "product_code":"rds", + "title":"Microsoft SQL Server Constraints", + "uri":"rds_03_0003.html", + "doc_type":"usermanual", + "p_code":"21", + "code":"24" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"DB Engine", + "uri":"rds_01_0031.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"25" + }, + { + "desc":"This section describes function differences between single and primary/standby DB instances as well as function differences among Microsoft SQL Server editions.For detail", + "product_code":"rds", + "title":"Function Differences of RDS for SQL Server Instances Types and Editions", + "uri":"rds_01_0018.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"26" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Related Services", + "uri":"rds_01_0027.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"27" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Getting Started with RDS for MySQL", + "uri":"index.html", + "doc_type":"usermanual", + "p_code":"", + "code":"28" + }, + { + "desc":"You can create and connect to DB instances on the RDS console.", + "product_code":"rds", + "title":"Operation Guide", + "uri":"en-us_topic_0046585334.html", + "doc_type":"usermanual", + "p_code":"28", + "code":"29" + }, + { + "desc":"This section describes how to create a DB instance on the management console.The DB instance class and storage space you need depend on your processing power and memory r", + "product_code":"rds", + "title":"Step 1: Create a DB Instance", + "uri":"rds_02_0008.html", + "doc_type":"usermanual", + "p_code":"28", + "code":"30" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Step 2: Connect to a DB Instance", + "uri":"rds_02_0006.html", + "doc_type":"usermanual", + "p_code":"28", + "code":"31" + }, + { + "desc":"An RDS DB instance can be connected through a private network or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ", + "product_code":"rds", + "title":"Connecting to a DB Instance", + "uri":"rds_02_0060.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"32" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connecting to an RDS for MySQL DB Instance Through a Private Network", + "uri":"rds_02_0101.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"33" + }, + { + "desc":"Figure 1 illustrates the process of connecting to a MySQL DB instance through a private network.", + "product_code":"rds", + "title":"Overview", + "uri":"en-us_topic_apply_for_rds.html", + "doc_type":"usermanual", + "p_code":"33", + "code":"34" + }, + { + "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "product_code":"rds", + "title":"Configuring Security Group Rules", + "uri":"rds_02_0004.html", + "doc_type":"usermanual", + "p_code":"33", + "code":"35" + }, + { + "desc":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.You have logged in to an ECS.To co", + "product_code":"rds", + "title":"Connecting to a DB Instance Through a Private Network", + "uri":"rds_02_0047.html", + "doc_type":"usermanual", + "p_code":"33", + "code":"36" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connecting to an RDS for MySQL DB Instance Through a Public Network", + "uri":"rds_02_0048.html", + "doc_type":"usermanual", + "p_code":"31", + "code":"37" + }, + { + "desc":"Figure 1 illustrates the process of connecting to a MySQL DB instance through a public network.", + "product_code":"rds", + "title":"Overview", + "uri":"rds_02_0099.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"38" + }, + { + "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can un", + "product_code":"rds", + "title":"Binding an EIP", + "uri":"rds_02_0025.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"39" + }, + { + "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "product_code":"rds", + "title":"Configuring Security Group Rules", + "uri":"rds_02_0009.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"40" + }, + { + "desc":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.An EIP has been bound to the targe", + "product_code":"rds", + "title":"Connecting to a DB Instance Through a Public Network", + "uri":"en-us_topic_connect_instance.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"41" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Getting Started with RDS for PostgreSQL", + "uri":"rds_03_0063.html", + "doc_type":"usermanual", + "p_code":"", + "code":"42" + }, + { + "desc":"You can create and connect to DB instances on the RDS console.", + "product_code":"rds", + "title":"Operation Guide", + "uri":"rds_02_0001.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"43" + }, + { + "desc":"You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see \"Creating a DB Instance\" in the Relational Databas", + "product_code":"rds", + "title":"Step 1: Create a DB Instance", + "uri":"rds_03_0065.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"44" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Step 2: Connect to a DB Instance", + "uri":"rds_02_0017.html", + "doc_type":"usermanual", + "p_code":"42", + "code":"45" + }, + { + "desc":"An RDS DB instance can be connected through a private network or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ", + "product_code":"rds", + "title":"Connecting to a DB Instance", + "uri":"rds_03_0060.html", + "doc_type":"usermanual", + "p_code":"45", + "code":"46" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connecting to a PostgreSQL DB Instance Through a Private Network", + "uri":"rds_02_0013.html", + "doc_type":"usermanual", + "p_code":"45", + "code":"47" + }, + { + "desc":"Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a private network.", + "product_code":"rds", + "title":"Overview", + "uri":"rds_02_0010.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"48" + }, + { + "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "product_code":"rds", + "title":"Configuring Security Group Rules", + "uri":"rds_02_0014.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"49" + }, + { + "desc":"You can use the PostgreSQL client psql to connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection is encrypted and therefore more s", + "product_code":"rds", + "title":"Connecting to a DB Instance Through psql", + "uri":"rds_02_0016.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"50" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connecting to a PostgreSQL DB Instance Through a Public Network", + "uri":"rds_02_0018.html", + "doc_type":"usermanual", + "p_code":"45", + "code":"51" + }, + { + "desc":"Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a public network.", + "product_code":"rds", + "title":"Overview", + "uri":"rds_02_0019.html", + "doc_type":"usermanual", + "p_code":"51", + "code":"52" + }, + { + "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can un", + "product_code":"rds", + "title":"Binding an EIP", + "uri":"rds_03_0064.html", + "doc_type":"usermanual", + "p_code":"51", + "code":"53" + }, + { + "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "product_code":"rds", + "title":"Configuring Security Group Rules", + "uri":"rds_02_0003.html", + "doc_type":"usermanual", + "p_code":"51", + "code":"54" + }, + { + "desc":"You can use the PostgreSQL client psql to connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection is encrypted and therefore more s", + "product_code":"rds", + "title":"Connecting to a DB Instance Through psql", + "uri":"rds_02_0051.html", + "doc_type":"usermanual", + "p_code":"51", + "code":"55" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Getting Started with RDS for SQL Server", + "uri":"rds_03_0014.html", + "doc_type":"usermanual", + "p_code":"", + "code":"56" + }, + { + "desc":"You can create and connect to DB instances on the RDS console.", + "product_code":"rds", + "title":"Operation Guide", + "uri":"rds_03_0010.html", + "doc_type":"usermanual", + "p_code":"56", + "code":"57" + }, + { + "desc":"You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see the \"Creating a DB Instance\" section in the Relati", + "product_code":"rds", + "title":"Step 1: Create a DB Instance", + "uri":"rds_04_0061.html", + "doc_type":"usermanual", + "p_code":"56", + "code":"58" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Step 2: Connect to a DB Instance", + "uri":"en-us_topic_0053089697.html", + "doc_type":"usermanual", + "p_code":"56", + "code":"59" + }, + { + "desc":"An RDS DB instance can be connected through a private network or a public network.VPC: indicates the Virtual Private Cloud.ECS: indicates the Elastic Cloud Server.If the ", + "product_code":"rds", + "title":"Connecting to a DB Instance", + "uri":"rds_04_0060.html", + "doc_type":"usermanual", + "p_code":"59", + "code":"60" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connecting to a SQL Server DB Instance Through a Private Network", + "uri":"rds_03_0008.html", + "doc_type":"usermanual", + "p_code":"59", + "code":"61" + }, + { + "desc":"Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a private network.", + "product_code":"rds", + "title":"Overview", + "uri":"rds_03_0001.html", + "doc_type":"usermanual", + "p_code":"61", + "code":"62" + }, + { + "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "product_code":"rds", + "title":"Configuring Security Group Rules", + "uri":"rds_03_0005.html", + "doc_type":"usermanual", + "p_code":"61", + "code":"63" + }, + { + "desc":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.Prepare an ECS.To connect to a DB ", + "product_code":"rds", + "title":"Connecting to a DB Instance Through a Private Network", + "uri":"rds_03_0013.html", + "doc_type":"usermanual", + "p_code":"61", + "code":"64" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connecting to a SQL Server DB Instance Through a Public Network", + "uri":"rds_03_0052.html", + "doc_type":"usermanual", + "p_code":"59", + "code":"65" + }, + { + "desc":"Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a public network.", + "product_code":"rds", + "title":"Overview", + "uri":"rds_03_0066.html", + "doc_type":"usermanual", + "p_code":"65", + "code":"66" + }, + { + "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can un", + "product_code":"rds", + "title":"Binding an EIP", + "uri":"rds_03_0006.html", + "doc_type":"usermanual", + "p_code":"65", + "code":"67" + }, + { + "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "product_code":"rds", + "title":"Configuring Security Group Rules", + "uri":"rds_03_0051.html", + "doc_type":"usermanual", + "p_code":"65", + "code":"68" + }, + { + "desc":"You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.Install the Microsoft SQL Server c", + "product_code":"rds", + "title":"Connecting to a DB Instance Through a Public Network", + "uri":"rds_03_0007.html", + "doc_type":"usermanual", + "p_code":"65", + "code":"69" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Working with RDS for MySQL", + "uri":"rds_08_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"70" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Data Migration", + "uri":"rds_05_0001_02.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"71" + }, + { + "desc":"You can access RDS DB instances through an EIP or through an ECS.Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through a", + "product_code":"rds", + "title":"Migrating Data to RDS for MySQL Using mysqldump", + "uri":"rds_migration_mysql.html", + "doc_type":"usermanual", + "p_code":"71", + "code":"72" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Parameter Tuning", + "uri":"rds_08_00000.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"73" + }, + { + "desc":"Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some", + "product_code":"rds", + "title":"Suggestions on MySQL Parameter Tuning", + "uri":"rds_08_00001.html", + "doc_type":"usermanual", + "p_code":"73", + "code":"74" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Instance Lifecycle", + "uri":"rds_05_0000.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"75" + }, + { + "desc":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", + "product_code":"rds", + "title":"Creating a Same DB Instance as an Existing DB Instance", + "uri":"rds_05_0055.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"76" + }, + { + "desc":"If you use DB instances only for routine development, you can temporarily stop pay-per-use DB instances to save money. You can stop a DB instance for up to seven days.If ", + "product_code":"rds", + "title":"Stopping a DB Instance", + "uri":"rds_05_0057.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"77" + }, + { + "desc":"You can stop your DB instance temporarily to save money. After stopping your DB instance, you can restart it to begin using it again.If you start a primary DB instance, r", + "product_code":"rds", + "title":"Starting a DB Instance", + "uri":"rds_05_0058.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"78" + }, + { + "desc":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", + "product_code":"rds", + "title":"Rebooting DB Instances or Read Replicas", + "uri":"rds_08_0013.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"79" + }, + { + "desc":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", + "product_code":"rds", + "title":"Selecting Displayed Items", + "uri":"rds_08_0022.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"80" + }, + { + "desc":"You can export information about all or selected DB instances to view and analyze DB instance information.", + "product_code":"rds", + "title":"Exporting DB Instance Information", + "uri":"rds_05_0017.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"81" + }, + { + "desc":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", + "product_code":"rds", + "title":"Deleting a DB Instance or Read Replica", + "uri":"rds_08_0002.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"82" + }, + { + "desc":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", + "product_code":"rds", + "title":"Recycling a DB Instance", + "uri":"rds_mysql_recycle.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"83" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Instance Modifications", + "uri":"rds_05_0001.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"84" + }, + { + "desc":"RDS for MySQL supports minor version upgrades to improve performance, add new functions, and fix bugs.The upgrade will cause the DB instance to reboot and interrupt servi", + "product_code":"rds", + "title":"Upgrading a Minor Version", + "uri":"rds_05_0003.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"85" + }, + { + "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", + "product_code":"rds", + "title":"Changing a DB Instance Name", + "uri":"rds_modify_instance_name.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"86" + }, + { + "desc":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", + "product_code":"rds", + "title":"Changing the Failover Priority", + "uri":"rds_modify_availability.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"87" + }, + { + "desc":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "product_code":"rds", + "title":"Changing a DB Instance Class", + "uri":"en-us_topic_scale_rds.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"88" + }, + { + "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If your storage space usage reaches up to 95% for a disk l", + "product_code":"rds", + "title":"Scaling up Storage Space", + "uri":"en-us_topic_scale_cluster.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"89" + }, + { + "desc":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", + "product_code":"rds", + "title":"Changing the Maintenance Window", + "uri":"rds_05_0038.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"90" + }, + { + "desc":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability. This operation does not affect the services running on the ", + "product_code":"rds", + "title":"Changing a DB Instance Type from Single to Primary/Standby", + "uri":"rds_05_0023.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"91" + }, + { + "desc":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", + "product_code":"rds", + "title":"Manually Switching Between Primary and Standby DB Instances", + "uri":"rds_switch_ha.html", + "doc_type":"usermanual", + "p_code":"84", + "code":"92" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Read Replicas", + "uri":"rds_11_0011.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"93" + }, + { + "desc":"RDS for MySQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. ", + "product_code":"rds", + "title":"Introducing Read Replicas", + "uri":"rds_11_0012.html", + "doc_type":"usermanual", + "p_code":"93", + "code":"94" + }, + { + "desc":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After DB instances are created, you can create read replicas for them.", + "product_code":"rds", + "title":"Creating a Read Replica", + "uri":"en-us_topic_add_read_replica.html", + "doc_type":"usermanual", + "p_code":"93", + "code":"95" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Managing a Read Replica", + "uri":"rds_11_0015.html", + "doc_type":"usermanual", + "p_code":"93", + "code":"96" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Backups and Restorations", + "uri":"rds_05_0034.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"97" + }, + { + "desc":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", + "product_code":"rds", + "title":"Working with Backups", + "uri":"en-us_topic_backup_restore.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"98" + }, + { + "desc":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", + "product_code":"rds", + "title":"Configuring an Automated Backup Policy", + "uri":"rds_08_0004.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"99" + }, + { + "desc":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", + "product_code":"rds", + "title":"Creating a Manual Backup", + "uri":"rds_08_0005.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"100" + }, + { + "desc":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for MySQL enables you to download ", + "product_code":"rds", + "title":"Downloading a Backup File", + "uri":"rds_08_0006.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"101" + }, + { + "desc":"RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary.You can also select the binlog backups ", + "product_code":"rds", + "title":"Downloading a Binlog Backup File", + "uri":"rds_03_0100.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"102" + }, + { + "desc":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", + "product_code":"rds", + "title":"Restoring from Backup Files to DB Instances", + "uri":"rds_08_0007.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"103" + }, + { + "desc":"You can download backup files by referring to Downloading a Backup File and restore data from them.Backup data cannot be restored to local databases that run the Windows ", + "product_code":"rds", + "title":"Restoring from Backup Files to a Self-Built MySQL Database", + "uri":"rds_08_0044.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"104" + }, + { + "desc":"You can restore from automated backups to a specified point in time.RDS for MySQL supports restoration to a new, the original, or an existing DB instance.When you enter t", + "product_code":"rds", + "title":"Restoring a DB Instance to a Point in Time", + "uri":"rds_08_0008.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"105" + }, + { + "desc":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", + "product_code":"rds", + "title":"Replicating a Backup", + "uri":"rds_08_0009.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"106" + }, + { + "desc":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", + "product_code":"rds", + "title":"Deleting a Manual Backup", + "uri":"rds_08_0010.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"107" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Parameter Template Management", + "uri":"rds_08_0011.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"108" + }, + { + "desc":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "product_code":"rds", + "title":"Creating a Parameter Template", + "uri":"en-us_topic_parameter_group.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"109" + }, + { + "desc":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", + "product_code":"rds", + "title":"Modifying Parameters", + "uri":"rds_configuration.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"110" + }, + { + "desc":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", + "product_code":"rds", + "title":"Exporting a Parameter Template", + "uri":"rds_08_0042.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"111" + }, + { + "desc":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "product_code":"rds", + "title":"Comparing Parameter Templates", + "uri":"rds_08_0012.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"112" + }, + { + "desc":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", + "product_code":"rds", + "title":"Viewing Parameter Change History", + "uri":"rds_05_0099.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"113" + }, + { + "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "product_code":"rds", + "title":"Replicating a Parameter Template", + "uri":"rds_08_0014.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"114" + }, + { + "desc":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", + "product_code":"rds", + "title":"Resetting a Parameter Template", + "uri":"rds_08_0015.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"115" + }, + { + "desc":"You can apply parameter templates to DB instances as needed.The parameter innodb_buffer_pool_size is determined by the memory. DB instances of different specifications ha", + "product_code":"rds", + "title":"Applying a Parameter Template", + "uri":"rds_05_0018.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"116" + }, + { + "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "product_code":"rds", + "title":"Viewing Application Records of a Parameter Template", + "uri":"rds_05_0098.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"117" + }, + { + "desc":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", + "product_code":"rds", + "title":"Modifying a Parameter Template Description", + "uri":"rds_08_0016.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"118" + }, + { + "desc":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "product_code":"rds", + "title":"Deleting a Parameter Template", + "uri":"rds_08_0017.html", + "doc_type":"usermanual", + "p_code":"108", + "code":"119" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connection Management", + "uri":"rds_05_0005.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"120" + }, + { + "desc":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", + "product_code":"rds", + "title":"Configuring and Changing a Floating IP Address", + "uri":"rds_05_0024.html", + "doc_type":"usermanual", + "p_code":"120", + "code":"121" + }, + { + "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", + "product_code":"rds", + "title":"Binding and Unbinding an EIP", + "uri":"rds_public_accessibility.html", + "doc_type":"usermanual", + "p_code":"120", + "code":"122" + }, + { + "desc":"This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the pri", + "product_code":"rds", + "title":"Changing a Database Port", + "uri":"rds_change_database_port.html", + "doc_type":"usermanual", + "p_code":"120", + "code":"123" + }, + { + "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", + "product_code":"rds", + "title":"Configuring a Security Group Rule", + "uri":"rds_11_0009.html", + "doc_type":"usermanual", + "p_code":"120", + "code":"124" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Data Security", + "uri":"rds_05_0006.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"125" + }, + { + "desc":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", + "product_code":"rds", + "title":"Resetting the Administrator Password", + "uri":"rds_reset_password.html", + "doc_type":"usermanual", + "p_code":"125", + "code":"126" + }, + { + "desc":"This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the pri", + "product_code":"rds", + "title":"Changing a Security Group", + "uri":"rds_08_0003.html", + "doc_type":"usermanual", + "p_code":"125", + "code":"127" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Metrics and Alarms", + "uri":"rds_08_0019.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"128" + }, + { + "desc":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the RDS metrics that can be monitored by Cloud Eye as well as their na", + "product_code":"rds", + "title":"Configuring Displayed Metrics", + "uri":"rds_06_0001.html", + "doc_type":"usermanual", + "p_code":"128", + "code":"129" + }, + { + "desc":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", + "product_code":"rds", + "title":"Setting Alarm Rules", + "uri":"rds_06_0002.html", + "doc_type":"usermanual", + "p_code":"128", + "code":"130" + }, + { + "desc":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", + "product_code":"rds", + "title":"Viewing Monitoring Metrics", + "uri":"rds_06_0003.html", + "doc_type":"usermanual", + "p_code":"128", + "code":"131" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Interconnection with CTS", + "uri":"rds_08_0020.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"132" + }, + { + "desc":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", + "product_code":"rds", + "title":"Key Operations Supported by CTS", + "uri":"rds_06_0004.html", + "doc_type":"usermanual", + "p_code":"132", + "code":"133" + }, + { + "desc":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", + "product_code":"rds", + "title":"Viewing Tracing Events", + "uri":"rds_06_0005.html", + "doc_type":"usermanual", + "p_code":"132", + "code":"134" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Log Management", + "uri":"rds_08_0021.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"135" + }, + { + "desc":"RDS log management allows you to view database-level logs, including error logs and slow SQL query logs.Error logs contain warning- and error-level logs generated during ", + "product_code":"rds", + "title":"Viewing Error Logs", + "uri":"rds_mysql_error_log.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"136" + }, + { + "desc":"Slow query logs record statements that exceed long_query_time. You can use these logs to identify and optimize the statements that are executing slowly.RDS supports the f", + "product_code":"rds", + "title":"Viewing Slow Query Logs", + "uri":"rds_mysql_slow_query_log.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"137" + }, + { + "desc":"You can view failover or switchover logs of MySQL DB instances to evaluate the impact on services.Only failover and switchover logs within 30 days are displayed.", + "product_code":"rds", + "title":"Viewing Failover/Switchover Logs", + "uri":"rds_switch_log.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"138" + }, + { + "desc":"After you enable the SQL audit function, all SQL operations will be recorded in log files. You can download audit logs to view log details.By default, SQL audit is disabl", + "product_code":"rds", + "title":"Enabling the SQL Audit Function", + "uri":"rds_sql_auditing_log.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"139" + }, + { + "desc":"If you enable the SQL audit function, all SQL operations will be logged, and you can download audit logs to view details. By default, the SQL audit function is disabled. ", + "product_code":"rds", + "title":"Downloading SQL Audit Logs", + "uri":"rds_download_sql_auditing_log.html", + "doc_type":"usermanual", + "p_code":"135", + "code":"140" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Task Center", + "uri":"rds_05_0007.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"141" + }, + { + "desc":"You can view the progress and results of scheduled and instant tasks on the Task Center page.RDS allows you to view and manage the following instant tasks:Creating DB ins", + "product_code":"rds", + "title":"Viewing a Task", + "uri":"rds_task_0001.html", + "doc_type":"usermanual", + "p_code":"141", + "code":"142" + }, + { + "desc":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", + "product_code":"rds", + "title":"Deleting a Task Record", + "uri":"rds_task_0002.html", + "doc_type":"usermanual", + "p_code":"141", + "code":"143" + }, + { + "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "product_code":"rds", + "title":"Managing Tags", + "uri":"rds_tag.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"144" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Working with RDS for PostgreSQL", + "uri":"rds_09_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"145" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Data Migration", + "uri":"rds_pg_05_0001_02.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"146" + }, + { + "desc":"PostgreSQL supports logical backups. You can use the pg_dump logical backup function to export backup files and then import them to RDS using psql.You can access RDS DB i", + "product_code":"rds", + "title":"Migrating Data to RDS for PostgreSQL Using psql", + "uri":"rds_09_0023.html", + "doc_type":"usermanual", + "p_code":"146", + "code":"147" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Parameter Tuning", + "uri":"rds_pg_10_0000.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"148" + }, + { + "desc":"Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some", + "product_code":"rds", + "title":"Suggestions on PostgreSQL Parameter Tuning", + "uri":"rds_pg_10_0001.html", + "doc_type":"usermanual", + "p_code":"148", + "code":"149" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"PostgreSQL Enhanced Edition", + "uri":"rds_04_0001.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"150" + }, + { + "desc":"PostgreSQL Enhanced Edition is developed from PostgreSQL 11. It retains all functions of the PostgreSQL databases. PostgreSQL Enhanced Edition supports system views, PL/S", + "product_code":"rds", + "title":"Introduction to PostgreSQL Enhanced Edition", + "uri":"rds_03_0018.html", + "doc_type":"usermanual", + "p_code":"150", + "code":"151" + }, + { + "desc":"This section describes the built-in functions and advanced function packages added to PostgreSQL Enhanced Edition on the basis of PostgreSQL 11 open-source edition.", + "product_code":"rds", + "title":"Functions", + "uri":"rds_04_0002.html", + "doc_type":"usermanual", + "p_code":"150", + "code":"152" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Instance Lifecycle", + "uri":"rds_pg_05_0000.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"153" + }, + { + "desc":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", + "product_code":"rds", + "title":"Creating a Same DB Instance as an Existing DB Instance", + "uri":"rds_pg_05_0055.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"154" + }, + { + "desc":"If you use DB instances only for routine development, you can temporarily stop pay-per-use instances to save money. You can stop an instance for up to seven days.If you s", + "product_code":"rds", + "title":"Stopping an Instance", + "uri":"rds_pg_stop.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"155" + }, + { + "desc":"You can stop your instance temporarily to save money. After stopping your instance, you can restart it to begin using it again.If you start a primary instance, read repli", + "product_code":"rds", + "title":"Starting an Instance", + "uri":"rds_pg_start.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"156" + }, + { + "desc":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", + "product_code":"rds", + "title":"Rebooting DB Instances or Read Replicas", + "uri":"rds_09_0024.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"157" + }, + { + "desc":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", + "product_code":"rds", + "title":"Selecting Displayed Items", + "uri":"rds_pg_06_0022.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"158" + }, + { + "desc":"You can export information about all or selected DB instances to view and analyze DB instance information.", + "product_code":"rds", + "title":"Exporting DB Instance Information", + "uri":"rds_pg_05_0017.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"159" + }, + { + "desc":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", + "product_code":"rds", + "title":"Deleting a DB Instance or Read Replica", + "uri":"rds_09_0025.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"160" + }, + { + "desc":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", + "product_code":"rds", + "title":"Recycling a DB Instance", + "uri":"rds_pg_recycle.html", + "doc_type":"usermanual", + "p_code":"153", + "code":"161" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Instance Modifications", + "uri":"rds_pg_05_0001.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"162" + }, + { + "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", + "product_code":"rds", + "title":"Changing a DB Instance Name", + "uri":"rds_pg_modify_instance_name.html", + "doc_type":"usermanual", + "p_code":"162", + "code":"163" + }, + { + "desc":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", + "product_code":"rds", + "title":"Changing the Failover Priority", + "uri":"rds_pg_modify_availability.html", + "doc_type":"usermanual", + "p_code":"162", + "code":"164" + }, + { + "desc":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "product_code":"rds", + "title":"Changing a DB Instance Class", + "uri":"rds_pg_scale_rds.html", + "doc_type":"usermanual", + "p_code":"162", + "code":"165" + }, + { + "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "product_code":"rds", + "title":"Scaling up Storage Space", + "uri":"rds_pg_scale_cluster.html", + "doc_type":"usermanual", + "p_code":"162", + "code":"166" + }, + { + "desc":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", + "product_code":"rds", + "title":"Changing the Maintenance Window", + "uri":"rds_pg_05_0038.html", + "doc_type":"usermanual", + "p_code":"162", + "code":"167" + }, + { + "desc":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", + "product_code":"rds", + "title":"Changing a DB Instance Type from Single to Primary/Standby", + "uri":"rds_pg_05_0023.html", + "doc_type":"usermanual", + "p_code":"162", + "code":"168" + }, + { + "desc":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", + "product_code":"rds", + "title":"Manually Switching Between Primary and Standby DB Instances", + "uri":"rds_pg_switch_ha.html", + "doc_type":"usermanual", + "p_code":"162", + "code":"169" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Read Replicas", + "uri":"rds_pg_11_0001.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"170" + }, + { + "desc":"RDS for PostgreSQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affec", + "product_code":"rds", + "title":"Introducing Read Replicas", + "uri":"rds_pg_11_0002.html", + "doc_type":"usermanual", + "p_code":"170", + "code":"171" + }, + { + "desc":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.You can create read replicas as needed.A maximum of five read replicas", + "product_code":"rds", + "title":"Creating a Read Replica", + "uri":"rds_add_read_replica_pg.html", + "doc_type":"usermanual", + "p_code":"170", + "code":"172" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Managing a Read Replica", + "uri":"rds_pg_11_0004.html", + "doc_type":"usermanual", + "p_code":"170", + "code":"173" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Backups and Restorations", + "uri":"rds_pg_05_0034.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"174" + }, + { + "desc":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", + "product_code":"rds", + "title":"Working with Backups", + "uri":"rds_pg_backup_restore.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"175" + }, + { + "desc":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", + "product_code":"rds", + "title":"Configuring an Automated Backup Policy", + "uri":"rds_09_0027.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"176" + }, + { + "desc":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", + "product_code":"rds", + "title":"Creating a Manual Backup", + "uri":"rds_09_0028.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"177" + }, + { + "desc":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", + "product_code":"rds", + "title":"Downloading a Full Backup File", + "uri":"rds_09_0031.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"178" + }, + { + "desc":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", + "product_code":"rds", + "title":"Downloading an Incremental Backup File", + "uri":"rds_pg_05_0138.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"179" + }, + { + "desc":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", + "product_code":"rds", + "title":"Restoring from Backup Files to RDS for PostgreSQL", + "uri":"rds_09_0030.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"180" + }, + { + "desc":"You can download backup files by referring to Downloading a Full Backup File and restore data from them.A tool for decompressing TAR files must be installed in a Unix-lik", + "product_code":"rds", + "title":"Restoring from Full Backup Files to a Self-Built PostgreSQL Database", + "uri":"rds_pg_08_0044.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"181" + }, + { + "desc":"You can restore from automated backups to a specified point in time.RDS for PostgreSQL supports restoration to a new, the original, or an existing DB instance.When you en", + "product_code":"rds", + "title":"Restoring a DB Instance to a Point in Time", + "uri":"rds_09_0029.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"182" + }, + { + "desc":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", + "product_code":"rds", + "title":"Replicating a Backup", + "uri":"rds_09_0032.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"183" + }, + { + "desc":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", + "product_code":"rds", + "title":"Deleting a Manual Backup", + "uri":"rds_09_0033.html", + "doc_type":"usermanual", + "p_code":"174", + "code":"184" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Parameter Template Management", + "uri":"rds_09_0034.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"185" + }, + { + "desc":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "product_code":"rds", + "title":"Creating a Parameter Template", + "uri":"rds_pg_parameter_group.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"186" + }, + { + "desc":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can change parameter values in custom parameter templates only and canno", + "product_code":"rds", + "title":"Modifying Instance Parameters", + "uri":"rds_pg_configuration.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"187" + }, + { + "desc":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", + "product_code":"rds", + "title":"Exporting a Parameter Template", + "uri":"rds_pg_08_0042.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"188" + }, + { + "desc":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "product_code":"rds", + "title":"Comparing Parameter Templates", + "uri":"rds_09_0035.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"189" + }, + { + "desc":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", + "product_code":"rds", + "title":"Viewing Parameter Change History", + "uri":"rds_pg_05_0099.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"190" + }, + { + "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "product_code":"rds", + "title":"Replicating a Parameter Template", + "uri":"rds_09_0036.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"191" + }, + { + "desc":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", + "product_code":"rds", + "title":"Resetting a Parameter Template", + "uri":"rds_09_0037.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"192" + }, + { + "desc":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", + "product_code":"rds", + "title":"Applying a Parameter Template", + "uri":"rds_pg_05_0018.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"193" + }, + { + "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "product_code":"rds", + "title":"Viewing Application Records of a Parameter Template", + "uri":"rds_pg_05_0098.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"194" + }, + { + "desc":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", + "product_code":"rds", + "title":"Modifying a Parameter Template Description", + "uri":"rds_09_0038.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"195" + }, + { + "desc":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "product_code":"rds", + "title":"Deleting a Parameter Template", + "uri":"rds_09_0039.html", + "doc_type":"usermanual", + "p_code":"185", + "code":"196" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connection Management", + "uri":"rds_pg_05_0005.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"197" + }, + { + "desc":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", + "product_code":"rds", + "title":"Configuring and Changing a Floating IP Address", + "uri":"rds_pg_05_0024.html", + "doc_type":"usermanual", + "p_code":"197", + "code":"198" + }, + { + "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", + "product_code":"rds", + "title":"Binding and Unbinding an EIP", + "uri":"rds_pg_public_accessibility.html", + "doc_type":"usermanual", + "p_code":"197", + "code":"199" + }, + { + "desc":"This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the pri", + "product_code":"rds", + "title":"Changing a Database Port", + "uri":"rds_pg_change_database_port.html", + "doc_type":"usermanual", + "p_code":"197", + "code":"200" + }, + { + "desc":"You can use the pgAdmin client to connect to an RDS DB instance.The pgAdmin version must be 4 or later.Prepare an ECS or a device that can access RDS DB instances.To conn", + "product_code":"rds", + "title":"Connecting to a DB Instance Through pgAdmin", + "uri":"rds_pg_11_0005.html", + "doc_type":"usermanual", + "p_code":"197", + "code":"201" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Plugin Management", + "uri":"rds_09_0046.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"202" + }, + { + "desc":"RDS provides the PostgreSQL plugin management solution for user root. Except the following plugins, you need to manually create other plugins by referring to this section", + "product_code":"rds", + "title":"Creating or Deleting a Plugin", + "uri":"rds_09_0043.html", + "doc_type":"usermanual", + "p_code":"202", + "code":"203" + }, + { + "desc":"The following table lists the plugins supported by the latest minor versions of RDS for PostgreSQL. You can use SELECT name FROM pg_available_extensions; to view the plug", + "product_code":"rds", + "title":"Supported Plugins", + "uri":"rds_09_0045.html", + "doc_type":"usermanual", + "p_code":"202", + "code":"204" + }, + { + "desc":"RDS provides the PostgreSQL tablespace management solution based on user root.# psql --host=--port= --dbname=--username=root -c\"select cont", + "product_code":"rds", + "title":"Tablespace Management", + "uri":"rds_09_0044.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"205" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Data Security", + "uri":"rds_pg_05_0006.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"206" + }, + { + "desc":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", + "product_code":"rds", + "title":"Resetting the Administrator Password", + "uri":"rds_pg_reset_password.html", + "doc_type":"usermanual", + "p_code":"206", + "code":"207" + }, + { + "desc":"This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the pri", + "product_code":"rds", + "title":"Changing a Security Group", + "uri":"rds_09_0026.html", + "doc_type":"usermanual", + "p_code":"206", + "code":"208" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Metrics and Alarms", + "uri":"rds_09_0041.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"209" + }, + { + "desc":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", + "product_code":"rds", + "title":"Configuring Displayed Metrics", + "uri":"rds_pg_06_0001.html", + "doc_type":"usermanual", + "p_code":"209", + "code":"210" + }, + { + "desc":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", + "product_code":"rds", + "title":"Setting Alarm Rules", + "uri":"rds_pg_06_0002.html", + "doc_type":"usermanual", + "p_code":"209", + "code":"211" + }, + { + "desc":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", + "product_code":"rds", + "title":"Viewing Monitoring Metrics", + "uri":"rds_pg_06_0003.html", + "doc_type":"usermanual", + "p_code":"209", + "code":"212" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Interconnection with CTS", + "uri":"rds_09_0042.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"213" + }, + { + "desc":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", + "product_code":"rds", + "title":"Key Operations Supported by CTS", + "uri":"rds_pg_06_0004.html", + "doc_type":"usermanual", + "p_code":"213", + "code":"214" + }, + { + "desc":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", + "product_code":"rds", + "title":"Viewing Tracing Events", + "uri":"rds_pg_06_0005.html", + "doc_type":"usermanual", + "p_code":"213", + "code":"215" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Log Management", + "uri":"rds_08_001.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"216" + }, + { + "desc":"Error logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner ", + "product_code":"rds", + "title":"Viewing Error Logs", + "uri":"rds_recent_log.html", + "doc_type":"usermanual", + "p_code":"216", + "code":"217" + }, + { + "desc":"Slow query logs record statements that exceed the log_min_duration_statement value. You can view log details to identify statements that are slowly executed and optimize ", + "product_code":"rds", + "title":"Viewing Slow Query Logs", + "uri":"slow_query_log-pg.html", + "doc_type":"usermanual", + "p_code":"216", + "code":"218" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Task Center", + "uri":"rds_pg_05_0007.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"219" + }, + { + "desc":"You can view the detailed progress and result of the task on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasC", + "product_code":"rds", + "title":"Viewing a Task", + "uri":"rds_task_pg_0001.html", + "doc_type":"usermanual", + "p_code":"219", + "code":"220" + }, + { + "desc":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", + "product_code":"rds", + "title":"Deleting a Task Record", + "uri":"rds_task_pg_0002.html", + "doc_type":"usermanual", + "p_code":"219", + "code":"221" + }, + { + "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "product_code":"rds", + "title":"Managing Tags", + "uri":"rds_pg_tag.html", + "doc_type":"usermanual", + "p_code":"145", + "code":"222" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Working with RDS for SQL Server", + "uri":"rds_10_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"223" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Data Migration", + "uri":"rds_sqlserver_05_0001_02.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"224" + }, + { + "desc":"You can access RDS DB instances through an EIP or ECS.Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through an EIP. To c", + "product_code":"rds", + "title":"Migrating Data to RDS for SQL Server Using SQL Server Management Studio", + "uri":"rds_10_0035.html", + "doc_type":"usermanual", + "p_code":"224", + "code":"225" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Instance Lifecycle", + "uri":"rds_sqlserver_05_0000.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"226" + }, + { + "desc":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", + "product_code":"rds", + "title":"Creating a Same DB Instance as an Existing DB Instance", + "uri":"rds_sqlserver_05_0055.html", + "doc_type":"usermanual", + "p_code":"226", + "code":"227" + }, + { + "desc":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", + "product_code":"rds", + "title":"Rebooting DB Instances or Read Replicas", + "uri":"rds_11_0006.html", + "doc_type":"usermanual", + "p_code":"226", + "code":"228" + }, + { + "desc":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", + "product_code":"rds", + "title":"Selecting Displayed Items", + "uri":"rds_sqlserver_06_0022.html", + "doc_type":"usermanual", + "p_code":"226", + "code":"229" + }, + { + "desc":"You can export information about all or selected DB instances to view and analyze DB instance information.", + "product_code":"rds", + "title":"Exporting DB Instance Information", + "uri":"rds_sqlserver_05_0017.html", + "doc_type":"usermanual", + "p_code":"226", + "code":"230" + }, + { + "desc":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", + "product_code":"rds", + "title":"Deleting a DB Instance or Read Replica", + "uri":"rds_11_0030.html", + "doc_type":"usermanual", + "p_code":"226", + "code":"231" + }, + { + "desc":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", + "product_code":"rds", + "title":"Recycling a DB Instance", + "uri":"rds_sqlserver_recycle.html", + "doc_type":"usermanual", + "p_code":"226", + "code":"232" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Instance Modifications", + "uri":"rds_sqlserver_05_0008.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"233" + }, + { + "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", + "product_code":"rds", + "title":"Changing a DB Instance Name", + "uri":"rds_sqlserver_modify_instance_name.html", + "doc_type":"usermanual", + "p_code":"233", + "code":"234" + }, + { + "desc":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", + "product_code":"rds", + "title":"Changing the Failover Priority", + "uri":"rds_sqlserver_modify_availability.html", + "doc_type":"usermanual", + "p_code":"233", + "code":"235" + }, + { + "desc":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", + "product_code":"rds", + "title":"Changing a DB Instance Class", + "uri":"rds_sqlserver_scale_rds.html", + "doc_type":"usermanual", + "p_code":"233", + "code":"236" + }, + { + "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", + "product_code":"rds", + "title":"Scaling up Storage Space", + "uri":"rds_sqlserver_scale_cluster.html", + "doc_type":"usermanual", + "p_code":"233", + "code":"237" + }, + { + "desc":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", + "product_code":"rds", + "title":"Changing a DB Instance Type from Single to Primary/Standby", + "uri":"rds_sqlserver_05_0023.html", + "doc_type":"usermanual", + "p_code":"233", + "code":"238" + }, + { + "desc":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", + "product_code":"rds", + "title":"Manually Switching Between Primary and Standby DB Instances", + "uri":"rds_sqlserver_switch_ha.html", + "doc_type":"usermanual", + "p_code":"233", + "code":"239" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Read Replicas", + "uri":"rds_sqlserver_11_0001.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"240" + }, + { + "desc":"Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and ser", + "product_code":"rds", + "title":"Introducing Read Replicas", + "uri":"rds_sqlserver_11_0002.html", + "doc_type":"usermanual", + "p_code":"240", + "code":"241" + }, + { + "desc":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After a DB instance has been created, you can create read replicas for", + "product_code":"rds", + "title":"Creating a Read Replica", + "uri":"rds_03_0011.html", + "doc_type":"usermanual", + "p_code":"240", + "code":"242" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Managing a Read Replica", + "uri":"rds_sqlserver_11_0004.html", + "doc_type":"usermanual", + "p_code":"240", + "code":"243" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Backups and Restorations", + "uri":"rds_sqlserver_05_0034.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"244" + }, + { + "desc":"RDS supports DB instance backups and restorations to ensure data reliability.Automated backups are created during the backup period of your DB instances. RDS saves automa", + "product_code":"rds", + "title":"Working with Backups", + "uri":"rds_sqlserver_backup_restore.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"245" + }, + { + "desc":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", + "product_code":"rds", + "title":"Configuring an Automated Backup Policy", + "uri":"rds_11_0031.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"246" + }, + { + "desc":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", + "product_code":"rds", + "title":"Creating a Manual Backup", + "uri":"rds_11_0010.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"247" + }, + { + "desc":"This section describes how to download a manual backup or an automated backup to a local device and restore data from the backup file.If the size of the backup data is gr", + "product_code":"rds", + "title":"Downloading a Backup File", + "uri":"rds_11_0013.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"248" + }, + { + "desc":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created.Alternatively, click the target DB inst", + "product_code":"rds", + "title":"Restoring from Backup Files to RDS for SQL Server", + "uri":"rds_11_0023.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"249" + }, + { + "desc":"You can download backup files by referring to section Downloading a Backup File and restore data from them. You can use SQL Server Management Studio (SSMS) to connect to ", + "product_code":"rds", + "title":"Restoring from Backup Files to a Self-Built SQL Server Database", + "uri":"rds_05_0044.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"250" + }, + { + "desc":"You can restore from automated backups to a specified point in time.RDS for Microsoft SQL Server supports restoration to a new, the original, or an existing DB instance.I", + "product_code":"rds", + "title":"Restoring a DB Instance to a Point in Time", + "uri":"rds_11_0022.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"251" + }, + { + "desc":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", + "product_code":"rds", + "title":"Replicating a Backup", + "uri":"rds_10_0055.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"252" + }, + { + "desc":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", + "product_code":"rds", + "title":"Deleting a Manual Backup", + "uri":"rds_10_0101.html", + "doc_type":"usermanual", + "p_code":"244", + "code":"253" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Parameter Template Management", + "uri":"rds_10_0102.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"254" + }, + { + "desc":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", + "product_code":"rds", + "title":"Creating a Parameter Template", + "uri":"rds_sqlserver_parameter_group.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"255" + }, + { + "desc":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", + "product_code":"rds", + "title":"Modifying Parameters", + "uri":"rds_sqlserver_configuration.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"256" + }, + { + "desc":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", + "product_code":"rds", + "title":"Exporting a Parameter Template", + "uri":"rds_sqlserver_08_0042.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"257" + }, + { + "desc":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", + "product_code":"rds", + "title":"Comparing Parameter Templates", + "uri":"rds_10_0103.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"258" + }, + { + "desc":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", + "product_code":"rds", + "title":"Viewing Parameter Change History", + "uri":"rds_sqlserver_05_0099.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"259" + }, + { + "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", + "product_code":"rds", + "title":"Replicating a Parameter Template", + "uri":"rds_10_0104.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"260" + }, + { + "desc":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", + "product_code":"rds", + "title":"Resetting a Parameter Template", + "uri":"rds_10_0105.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"261" + }, + { + "desc":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", + "product_code":"rds", + "title":"Applying a Parameter Template", + "uri":"rds_sqlserver_05_0018.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"262" + }, + { + "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", + "product_code":"rds", + "title":"Viewing Application Records of a Parameter Template", + "uri":"rds_sqlserver_05_0098.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"263" + }, + { + "desc":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", + "product_code":"rds", + "title":"Modifying a Parameter Template Description", + "uri":"rds_10_0106.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"264" + }, + { + "desc":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", + "product_code":"rds", + "title":"Deleting a Parameter Template", + "uri":"rds_10_0107.html", + "doc_type":"usermanual", + "p_code":"254", + "code":"265" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Connection Management", + "uri":"rds_sqlserver_05_0005.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"266" + }, + { + "desc":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", + "product_code":"rds", + "title":"Configuring and Changing a Floating IP Address", + "uri":"rds_sqlserver_05_0024.html", + "doc_type":"usermanual", + "p_code":"266", + "code":"267" + }, + { + "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", + "product_code":"rds", + "title":"Binding and Unbinding an EIP", + "uri":"rds_sqlserver_0025.html", + "doc_type":"usermanual", + "p_code":"266", + "code":"268" + }, + { + "desc":"This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the pri", + "product_code":"rds", + "title":"Changing a Database Port", + "uri":"rds_sqlserver_change_database_port.html", + "doc_type":"usermanual", + "p_code":"266", + "code":"269" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Data Security", + "uri":"rds_sqlserver_05_0006.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"270" + }, + { + "desc":"You can reset the administrator password only through the primary DB instance.You can also reset the password of your database account when using RDS.If you have changed ", + "product_code":"rds", + "title":"Resetting the Administrator Password", + "uri":"en-us_topic_sqlserver_reset_password.html", + "doc_type":"usermanual", + "p_code":"270", + "code":"271" + }, + { + "desc":"This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the pri", + "product_code":"rds", + "title":"Changing a Security Group", + "uri":"rds_11_0032.html", + "doc_type":"usermanual", + "p_code":"270", + "code":"272" + }, + { + "desc":"Transparent Data Encryption (TDE) encrypts data files and backup files using certificates to implement real-time I/O encryption and decryption. This function effectively ", + "product_code":"rds", + "title":"Configuring the TDE Function", + "uri":"rds_11_0004.html", + "doc_type":"usermanual", + "p_code":"270", + "code":"273" + }, + { + "desc":"The participator, transaction-supported server, resource server, and transaction manager of a distributed transaction are deployed on different nodes in a distributed sys", + "product_code":"rds", + "title":"Distributed Transactions", + "uri":"rds_sqlserver_01_0001.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"274" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Metrics and Alarms", + "uri":"rds_sqlserver_06_0000.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"275" + }, + { + "desc":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", + "product_code":"rds", + "title":"Configuring Displayed Metrics", + "uri":"rds_sqlserver_06_0001.html", + "doc_type":"usermanual", + "p_code":"275", + "code":"276" + }, + { + "desc":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", + "product_code":"rds", + "title":"Setting Alarm Rules", + "uri":"rds_sqlserver_06_0002.html", + "doc_type":"usermanual", + "p_code":"275", + "code":"277" + }, + { + "desc":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", + "product_code":"rds", + "title":"Viewing Monitoring Metrics", + "uri":"rds_sqlserver_06_0003.html", + "doc_type":"usermanual", + "p_code":"275", + "code":"278" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Interconnection with CTS", + "uri":"rds_sqlserver_01_0000.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"279" + }, + { + "desc":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", + "product_code":"rds", + "title":"Key Operations Supported by CTS", + "uri":"rds_sqlserver_06_0004.html", + "doc_type":"usermanual", + "p_code":"279", + "code":"280" + }, + { + "desc":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", + "product_code":"rds", + "title":"Viewing Tracing Events", + "uri":"rds_sqlserver_06_0005.html", + "doc_type":"usermanual", + "p_code":"279", + "code":"281" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Log Management", + "uri":"rds_sqlserver_log.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"282" + }, + { + "desc":"System logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner", + "product_code":"rds", + "title":"Viewing System Logs", + "uri":"rds_sqlserver_01_0002.html", + "doc_type":"usermanual", + "p_code":"282", + "code":"283" + }, + { + "desc":"Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details to identify statements that are executing slowly and optimiz", + "product_code":"rds", + "title":"Viewing and Downloading Slow Query Logs", + "uri":"slow_query_log-sqlserver.html", + "doc_type":"usermanual", + "p_code":"282", + "code":"284" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Task Center", + "uri":"rds_sqlserver_05_0007.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"285" + }, + { + "desc":"You can view the progress and results of tasks on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasChanging sin", + "product_code":"rds", + "title":"Viewing a Task", + "uri":"rds_sqlserver_task_0001.html", + "doc_type":"usermanual", + "p_code":"285", + "code":"286" + }, + { + "desc":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", + "product_code":"rds", + "title":"Deleting a Task Record", + "uri":"rds_sqlserver_task_0002.html", + "doc_type":"usermanual", + "p_code":"285", + "code":"287" + }, + { + "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", + "product_code":"rds", + "title":"Managing Tags", + "uri":"rds_sqlserver_tag.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"288" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"FAQs", + "uri":"rds_faq_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"289" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Product Consulting", + "uri":"rds_faq_0146.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"290" + }, + { + "desc":"DB instance operating systems (OSs) are invisible to you. Your applications can access a database only through an IP address and a port.The backup files stored in Object ", + "product_code":"rds", + "title":"What Should I Pay Attention to When Using RDS?", + "uri":"rds_faq_0001.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"291" + }, + { + "desc":"Calculation formula for RDS DB instance availability:DB instance availability = (1 – Failure duration/Total service duration) × 100%", + "product_code":"rds", + "title":"What Is the Availability of RDS DB Instances?", + "uri":"rds_faq_0002.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"292" + }, + { + "desc":"Currently, DB instance cannot be created using a template.", + "product_code":"rds", + "title":"Can I Use a Template to Create DB Instances?", + "uri":"rds_faq_0003.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"293" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"What Are the Differences Between RDS and Other Database Solutions?", + "uri":"rds_faq_0004.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"294" + }, + { + "desc":"No. Your RDS DB instances and resources are isolated from other users' DB instances.", + "product_code":"rds", + "title":"Will My RDS DB Instances Be Affected by Other User Instances?", + "uri":"rds_faq_0005.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"295" + }, + { + "desc":"Yes. RDS supports cross-AZ high availability. When you create primary/standby DB instances, you can select different AZs for them.", + "product_code":"rds", + "title":"Does RDS Support Cross-AZ High Availability?", + "uri":"rds_faq_0073.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"296" + }, + { + "desc":"No. RDS single DB instances can be changed to primary/standby DB instances, but not the other way around.", + "product_code":"rds", + "title":"Can RDS Primary/Standby DB Instances Be Changed to Single DB Instances?", + "uri":"rds_faq_0104.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"297" + }, + { + "desc":"The default code is utf8. You need to convert the default code to Unicode in the exported Excel file.", + "product_code":"rds", + "title":"What Should I Do If Garbled Characters Are Displayed After SQL Query Results Are Exported to an Excel File?", + "uri":"rds_faq_0110.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"298" + }, + { + "desc":"To solve this problem:Check the performance of RDS DB instances on the RDS console.Compare the database connection status of local databases and RDS DB instances. This pr", + "product_code":"rds", + "title":"What Can I Do About Slow Respond of Websites When They Use RDS?", + "uri":"rds_faq_0008.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"299" + }, + { + "desc":"RDS provides the high availability. Select the primary/standby mode.Also called an unplanned handover. If the primary DB instance fails, the system will automatically swi", + "product_code":"rds", + "title":"How Does a Cloud Database Perform a Primary/Standby Switchover?", + "uri":"rds_faq_0065.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"300" + }, + { + "desc":"Multiple ECSs can connect to the same RDS DB instance as long as the capability limits of a database are not exceeded.", + "product_code":"rds", + "title":"Can Multiple ECSs Connect to the Same RDS DB Instance?", + "uri":"rds_faq_0013.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"301" + }, + { + "desc":"An error shown in Figure 1 is reported on SQL Server Management Studio when a database is being deleted from RDS SQL Server primary/standby DB instances.The database 'xxx", + "product_code":"rds", + "title":"Why Is an Error Reported When I Attempt to Delete a Database from RDS SQL Server Primary/Standby DB Instances?", + "uri":"rds_faq_0094.html", + "doc_type":"usermanual", + "p_code":"290", + "code":"302" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Resource and Disk Management", + "uri":"rds_faq_0145.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"303" + }, + { + "desc":"The following logs and files occupy RDS storage space.If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If d", + "product_code":"rds", + "title":"Which Types of Logs and Files Occupy RDS Storage Space?", + "uri":"rds_faq_0049.html", + "doc_type":"usermanual", + "p_code":"303", + "code":"304" + }, + { + "desc":"Both your common data (excluding backup data) and the data required for the operation of your DB instances (such as system database data, rollback logs, redo logs, and in", + "product_code":"rds", + "title":"Which Items Occupy the Storage Space of My RDS DB Instances?", + "uri":"rds_faq_0047.html", + "doc_type":"usermanual", + "p_code":"303", + "code":"305" + }, + { + "desc":"The storage space you applied for will include space for the file system overhead required for inode, reserved block, and database operations.", + "product_code":"rds", + "title":"What Overhead Does the Storage Space Have After I Applied for an RDS DB Instance?", + "uri":"rds_faq_0048.html", + "doc_type":"usermanual", + "p_code":"303", + "code":"306" + }, + { + "desc":"Data Definition Language (DDL) operations may increase storage space usage sharply. To ensure that services are running properly, do not perform DDL operations during pea", + "product_code":"rds", + "title":"How Much Storage Space Is Required for DDL Operations?", + "uri":"rds_faq_0082.html", + "doc_type":"usermanual", + "p_code":"303", + "code":"307" + }, + { + "desc":"There are no limitations on the number of DB instances running on RDS.", + "product_code":"rds", + "title":"How Many DB Instances Can Run on RDS?", + "uri":"rds_faq_0006.html", + "doc_type":"usermanual", + "p_code":"303", + "code":"308" + }, + { + "desc":"The maximum number of databases that can run on an RDS DB instance depends on the DB engine settings.If there are enough CPU, memory, and storage resources, there are no ", + "product_code":"rds", + "title":"How Many Databases Can Run on an RDS DB Instance?", + "uri":"rds_faq_0007.html", + "doc_type":"usermanual", + "p_code":"303", + "code":"309" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Database Connection", + "uri":"rds_faq_0141.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"310" + }, + { + "desc":"For a DB instance that has an EIP bound, you can access it through the EIP.Enable a VPN in a VPC and use the VPN to connect to the RDS DB instance.Create an RDS and an EC", + "product_code":"rds", + "title":"Can an External Server Access the RDS Database?", + "uri":"rds_faq_0018.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"311" + }, + { + "desc":"The number of database connections indicates the number of applications that can be simultaneously connected to a database, and is irrelevant to the maximum number of use", + "product_code":"rds", + "title":"What Do I Do If the Number of RDS Database Connections Reaches the Upper Limit?", + "uri":"rds_faq_0019.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"312" + }, + { + "desc":"RDS does not have constraints on the number of connections. This number is determined by the default value and value range of the DB engine. For example, you can set max_", + "product_code":"rds", + "title":"What Is the Maximum Number of Connections to an RDS DB Instance?", + "uri":"rds_faq_0055.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"313" + }, + { + "desc":"For details about how to create an ECS, see the Elastic Cloud Server User Guide.If you connect to an RDS DB instance through a private network, ensure that the ECS and DB", + "product_code":"rds", + "title":"How Can I Create and Connect to an ECS?", + "uri":"rds_faq_0057.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"314" + }, + { + "desc":"Perform the following steps to identify the problem:If they are in the same VPC, go to 2.If they are in different VPCs, create an ECS in the VPC in which the RDS DB insta", + "product_code":"rds", + "title":"What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?", + "uri":"rds_faq_0020.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"315" + }, + { + "desc":"Troubleshoot RDS connection failures caused by a client problem by checking the following items:ECS Security PolicyIn Windows, check whether the RDS instance port is enab", + "product_code":"rds", + "title":"What Should I Do If a Database Client Problem Causes a Connection Failure?", + "uri":"rds_faq_0021.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"316" + }, + { + "desc":"Check whether any of the following problems occurred on the RDS DB instance.The RDS DB instance is not properly connected.Solution: Check the connection. If you connect t", + "product_code":"rds", + "title":"What Should I Do If an RDS Database Problem Causes a Connection Failure?", + "uri":"rds_faq_0022.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"317" + }, + { + "desc":"Ensure that the ECS in which your applications are located is in the same VPC as the RDS DB instance. If the ECS and the RDS DB instance are in different VPCs, modify the", + "product_code":"rds", + "title":"How Do My Applications Access an RDS DB Instance in a VPC?", + "uri":"rds_faq_0023.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"318" + }, + { + "desc":"It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the d", + "product_code":"rds", + "title":"Do Applications Need to Support Reconnecting to the RDS DB Instance Automatically?", + "uri":"rds_faq_0024.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"319" + }, + { + "desc":"Although the SSL certificate is optional if you choose to connect to a database through Java database connectivity (JDBC), download an SSL certificate to encrypt the conn", + "product_code":"rds", + "title":"How Can I Connect to a PostgreSQL Database Through JDBC?", + "uri":"rds_faq_0050.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"320" + }, + { + "desc":"Check whether the ECS can connect to the RDS DB instance.If the ECS cannot connect to the RDS DB instance, check whether the ECS and RDS DB instance are located in the sa", + "product_code":"rds", + "title":"What Should I Do If an RDS Microsoft SQL Server DB Instance Failed to Be Connected?", + "uri":"rds_faq_0100.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"321" + }, + { + "desc":"By default, RDS DB instances cannot be accessed over an intranet across regions. Cloud services in different regions cannot communicate with each other over an intranet. ", + "product_code":"rds", + "title":"Can I Access an RDS DB Instance Over an Intranet Connection Across Regions?", + "uri":"rds_faq_0101.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"322" + }, + { + "desc":"For DB instances connected using SSL, a primary/standby switchover or failover does not interrupt the connection because the SSL certificate is still valid for both the p", + "product_code":"rds", + "title":"Is an SSL Connection to a DB Instance Interrupted After a Primary/Standby Switchover or Failover?", + "uri":"rds_faq_0111.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"323" + }, + { + "desc":"MySQL supports SSL connections. Different from other vendors, RDS for MySQL enables the SSL connection on the database server by default. When you use a client to connect", + "product_code":"rds", + "title":"Does MySQL Support SSL Connections?", + "uri":"rds_faq_0070.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"324" + }, + { + "desc":"You may have restored from a backup before you reset the administrator password.Check whether the DB instance was restored after you reset the administrator password.Log ", + "product_code":"rds", + "title":"Why Did the New Password Not Take Effect After I Reset the Administrator Password?", + "uri":"rds_faq_0034.html", + "doc_type":"usermanual", + "p_code":"310", + "code":"325" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Database Migration", + "uri":"rds_faq_0155.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"326" + }, + { + "desc":"The mysqldump or pg_dump tool is easy to use for data migration. However, when you use this tool, the server is stopped for a long period of time during data migration. O", + "product_code":"rds", + "title":"Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?", + "uri":"rds_faq_0026.html", + "doc_type":"usermanual", + "p_code":"326", + "code":"327" + }, + { + "desc":"Exporting or importing data between DB engines of the same type is called homogeneous database export or import.Exporting or importing data between DB engines of differen", + "product_code":"rds", + "title":"What Types of DB Engines Does RDS Support for Importing Data?", + "uri":"rds_faq_0025.html", + "doc_type":"usermanual", + "p_code":"326", + "code":"328" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Database Permission", + "uri":"rds_faq_0154.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"329" + }, + { + "desc":"Most relational database cloud service platforms do not provide super permissions for the root user. The super permissions allow users to execute many management commands", + "product_code":"rds", + "title":"Why Does the Root User Not Have the Super Permissions?", + "uri":"rds_faq_0075.html", + "doc_type":"usermanual", + "p_code":"329", + "code":"330" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Database Storage", + "uri":"rds_faq_0144.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"331" + }, + { + "desc":"The database storage engine is a core service for storing, processing, and protecting data. It can be used to control access permissions and rapidly process transactions ", + "product_code":"rds", + "title":"What Storage Engines Does the RDS for MySQL Support?", + "uri":"rds_faq_0041.html", + "doc_type":"usermanual", + "p_code":"331", + "code":"332" + }, + { + "desc":"RDS uses Elastic Volume Service (EVS) disks for storage. For details about EVS disks, see Elastic Volume Service Product Introduction.The RDS backup data is stored in OBS", + "product_code":"rds", + "title":"What Is the RDS DB Instance Storage Configuration?", + "uri":"rds_faq_0045.html", + "doc_type":"usermanual", + "p_code":"331", + "code":"333" + }, + { + "desc":"No. After an RDS DB instance is created, the storage type cannot be changed.", + "product_code":"rds", + "title":"Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?", + "uri":"rds_faq_0076.html", + "doc_type":"usermanual", + "p_code":"331", + "code":"334" + }, + { + "desc":"There is not enough storage available for an RDS DB instance and the DB instance has entered read-only status, or applications can no longer read from or write to the dat", + "product_code":"rds", + "title":"What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?", + "uri":"rds_faq_0046.html", + "doc_type":"usermanual", + "p_code":"331", + "code":"335" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Client Installation", + "uri":"rds_faq_0152.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"336" + }, + { + "desc":"MySQL provides client installation packages for different OSs on its official website. MySQL 5.6 is used as an example. Download the MySQL 5.6 client installation package", + "product_code":"rds", + "title":"How Can I Install the MySQL Client?", + "uri":"rds_faq_0027.html", + "doc_type":"usermanual", + "p_code":"336", + "code":"337" + }, + { + "desc":"PostgreSQL provides client installation packages and the required dynamic shared library packages for different OSs on its official website.Ensure that the database clien", + "product_code":"rds", + "title":"How Can I Install the PostgreSQL Client?", + "uri":"rds_faq_0029.html", + "doc_type":"usermanual", + "p_code":"336", + "code":"338" + }, + { + "desc":"The Microsoft SQL Server official website provides the SQL Server Management Studio installation package. SQL Server Management Studio applications can run in the Windows", + "product_code":"rds", + "title":"How Can I Install SQL Server Management Studio?", + "uri":"rds_faq_0032.html", + "doc_type":"usermanual", + "p_code":"336", + "code":"339" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Backup and Restoration", + "uri":"rds_faq_0098.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"340" + }, + { + "desc":"Automated backup data is kept based on the backup retention period you specified. There is no limit for the manual backup retention period. You can delete manual backups ", + "product_code":"rds", + "title":"How Long Does RDS Store Backup Data For?", + "uri":"rds_faq_0043.html", + "doc_type":"usermanual", + "p_code":"340", + "code":"341" + }, + { + "desc":"A backup window is a user-specified time during which RDS DB instances are backed up. With these periodic data backups, RDS allows you to restore DB instances to the back", + "product_code":"rds", + "title":"Can My Database Be Used in the Backup Window?", + "uri":"rds_faq_0044.html", + "doc_type":"usermanual", + "p_code":"340", + "code":"342" + }, + { + "desc":"You can back up data to an ECS the same way you export SQL statements. The ECS service does not have restrictions on the types of data to be backed up as long as the data", + "product_code":"rds", + "title":"How Can I Back Up an RDS Database to an ECS?", + "uri":"rds_faq_0042.html", + "doc_type":"usermanual", + "p_code":"340", + "code":"343" + }, + { + "desc":"Automated backups may fail for the following reasons:The network environment is unstable due to issues such as network delay or interruption. RDS will detect these proble", + "product_code":"rds", + "title":"Why Has My Automated Backup Failed?", + "uri":"rds_faq_0053.html", + "doc_type":"usermanual", + "p_code":"340", + "code":"344" + }, + { + "desc":"When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.", + "product_code":"rds", + "title":"What Happens to Database Backups After an RDS DB Instance Is Deleted?", + "uri":"rds_faq_0014.html", + "doc_type":"usermanual", + "p_code":"340", + "code":"345" + }, + { + "desc":"If your cloud account is deleted, both your automated and manual backups are deleted.", + "product_code":"rds", + "title":"Will My Backups Be Deleted If I Delete My Cloud Account?", + "uri":"rds_faq_0015.html", + "doc_type":"usermanual", + "p_code":"340", + "code":"346" + }, + { + "desc":"RDS does not delete or perform any operations on any user data. If this problem occurs, check if there have been any misoperations and restore the data from backup files,", + "product_code":"rds", + "title":"Why Is a Table or Data Missing from My Database?", + "uri":"rds_faq_0012.html", + "doc_type":"usermanual", + "p_code":"340", + "code":"347" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Database Monitoring", + "uri":"rds_faq_0151.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"348" + }, + { + "desc":"You need to pay attention to CPU, memory, and storage space usage.You can configure the system to report alarms based on service requirements and take measures to handle ", + "product_code":"rds", + "title":"Which DB Instance Monitoring Metrics Do I Need to Pay Attention To?", + "uri":"rds_faq_0036.html", + "doc_type":"usermanual", + "p_code":"348", + "code":"349" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Capacity Expansion and Specification Change", + "uri":"rds_faq_0150.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"350" + }, + { + "desc":"Currently, you can scale up storage space and change the CPU or memory of a DB instance.When storage space is being scaled up, RDS DB instances are still available and se", + "product_code":"rds", + "title":"Are My RDS DB Instances Available When Scaling?", + "uri":"rds_faq_0016.html", + "doc_type":"usermanual", + "p_code":"350", + "code":"351" + }, + { + "desc":"The DB instance is in Faulty state after the original database port is changed.The DB instance cannot be connected using the new database port.The submitted database port", + "product_code":"rds", + "title":"Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?", + "uri":"rds_faq_0035.html", + "doc_type":"usermanual", + "p_code":"350", + "code":"352" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Database Parameter Modification", + "uri":"rds_faq_0142.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"353" + }, + { + "desc":"In the following cases, inappropriate parameter settings cause the database to be unavailable:Parameter value ranges are related to DB instance specifications.The maximum", + "product_code":"rds", + "title":"What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?", + "uri":"rds_faq_0031.html", + "doc_type":"usermanual", + "p_code":"353", + "code":"354" + }, + { + "desc":"PostgreSQL 10, PostgreSQL 11, PostgreSQL 12 and PostgreSQL 13 support test_decoding. For more information about test_decoding, see test_decoding introduction.To use test_", + "product_code":"rds", + "title":"Does RDS for PostgreSQL Support the test_decoding Plugin?", + "uri":"rds_faq_0119.html", + "doc_type":"usermanual", + "p_code":"353", + "code":"355" + }, + { + "desc":"When you add NDF files of the custom database and the tempdb database, do not place them in the C drive. If you place them in the C drive, the system disk space will be u", + "product_code":"rds", + "title":"Where Should I Store the NDF Files for Microsoft SQL Server?", + "uri":"rds_faq_0092.html", + "doc_type":"usermanual", + "p_code":"353", + "code":"356" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Log Management", + "uri":"rds_faq_0149.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"357" + }, + { + "desc":"Generally, the delay is 5 minutes. If the size of slow query logs reaches 10 MB within 5 minutes, the logs will be uploaded to OBS.", + "product_code":"rds", + "title":"How Long Is the Delay for RDS MySQL Slow Query Logs?", + "uri":"rds_faq_0078.html", + "doc_type":"usermanual", + "p_code":"357", + "code":"358" + }, + { + "desc":"The slow query threshold is 5 seconds.", + "product_code":"rds", + "title":"What's the Slow Query Threshold for Microsoft SQL Server?", + "uri":"rds_faq_0077.html", + "doc_type":"usermanual", + "p_code":"357", + "code":"359" + }, + { + "desc":"EXECUTE master.dbo.rds_read_errorlogFileID,LogType,FilterText,FilterBeginTime,FilterEndTimeFileID: indicates the ID of an error log. The value 0 indicates the latest logs", + "product_code":"rds", + "title":"How Can I Obtain Microsoft SQL Server Error Logs Using Commands?", + "uri":"rds_faq_0059.html", + "doc_type":"usermanual", + "p_code":"357", + "code":"360" + }, + { + "desc":"Sorry, statistics on RDS slow query logs cannot be exported.", + "product_code":"rds", + "title":"Can I Export Statistics on RDS Slow Query Logs?", + "uri":"rds_faq_0120.html", + "doc_type":"usermanual", + "p_code":"357", + "code":"361" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Network Security", + "uri":"rds_faq_0143.html", + "doc_type":"usermanual", + "p_code":"289", + "code":"362" + }, + { + "desc":"RDS runs your DB instances in a VPC, ensuring that the DB instances are isolated from other services.RDS uses security groups to ensure that only trusted sources can acce", + "product_code":"rds", + "title":"What Security Protection Policies Does RDS Have?", + "uri":"rds_faq_0038.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"363" + }, + { + "desc":"The VPC security group helps ensure the security of RDS in a VPC. In addition, an ACL can be used to allow or reject I/O network traffic for each subnet.", + "product_code":"rds", + "title":"How Can I Ensure the Security of RDS DB Instances in a VPC?", + "uri":"rds_faq_0040.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"364" + }, + { + "desc":"When you access RDS through an EIP, service data will be transmitted on the public network. To prevent any potential data breaches, you are advised to use SSL to encrypt ", + "product_code":"rds", + "title":"How Can Data Security Be Ensured During Transmission When I Access RDS Through an EIP?", + "uri":"rds_faq_0039.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"365" + }, + { + "desc":"If you enable public accessibility, your EIP DNS and database port may be vulnerable to hacking. To protect information such as your EIP, DNS, database port, database acc", + "product_code":"rds", + "title":"How Can I Prevent Untrusted Source IP Addresses from Accessing RDS?", + "uri":"rds_faq_0056.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"366" + }, + { + "desc":"When you attempt to connect to a DB instance through a private network, check whether the ECS and RDS DB instance are in the same security group.If the ECS and RDS DB ins", + "product_code":"rds", + "title":"How Do I Configure a Security Group to Enable Access to RDS DB Instances?", + "uri":"rds_faq_0054.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"367" + }, + { + "desc":"Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.On the displayed console, choose File > Add/Remove Snap-in.In the left Available sn", + "product_code":"rds", + "title":"How Can I Import the Root Certificate to a Windows or Linux OS?", + "uri":"rds_faq_0052.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"368" + }, + { + "desc":"When you connect to an RDS MySQL DB instance using an SSL connection, run the following command to check whether the certificate has expired:Update the root certificate t", + "product_code":"rds", + "title":"How Can I Identify the Validity Period of an SSL Root Certificate?", + "uri":"rds_faq_0051.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"369" + }, + { + "desc":"Data tamperingLots of security measures are provided to ensure that only authenticated users have permissions to perform operations on database table records. Database ta", + "product_code":"rds", + "title":"How Can I Identify Data Corruption?", + "uri":"rds_faq_0011.html", + "doc_type":"usermanual", + "p_code":"362", + "code":"370" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Change History", + "uri":"en-us_topic_0000001419863378.html", + "doc_type":"usermanual", + "p_code":"", + "code":"371" + }, + { + "desc":"For details about the glossaries in this document, see Glossary.", + "product_code":"rds", + "title":"Glossary", + "uri":"rds_glossary_0001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"372" + } +] \ No newline at end of file diff --git a/docs/rds/umn/PARAMETERS.txt b/docs/rds/umn/PARAMETERS.txt new file mode 100644 index 000000000..6da8d5f07 --- /dev/null +++ b/docs/rds/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/rds/umn/en-us_image_0000001419863594.png b/docs/rds/umn/en-us_image_0000001419863594.png new file mode 100644 index 000000000..173bac7a7 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863594.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863630.jpg b/docs/rds/umn/en-us_image_0000001419863630.jpg new file mode 100644 index 000000000..d4af2f261 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863630.jpg differ diff --git a/docs/rds/umn/en-us_image_0000001419863674.png b/docs/rds/umn/en-us_image_0000001419863674.png new file mode 100644 index 000000000..d232ef1a9 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863674.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863698.png b/docs/rds/umn/en-us_image_0000001419863698.png new file mode 100644 index 000000000..821920592 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863698.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863714.jpg b/docs/rds/umn/en-us_image_0000001419863714.jpg new file mode 100644 index 000000000..d4af2f261 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863714.jpg differ diff --git a/docs/rds/umn/en-us_image_0000001419863730.png b/docs/rds/umn/en-us_image_0000001419863730.png new file mode 100644 index 000000000..1267615e3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863730.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863746.png b/docs/rds/umn/en-us_image_0000001419863746.png new file mode 100644 index 000000000..62ddb8e0f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863746.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863754.png b/docs/rds/umn/en-us_image_0000001419863754.png new file mode 100644 index 000000000..c27951e69 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863754.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863802.png b/docs/rds/umn/en-us_image_0000001419863802.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863802.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863814.png b/docs/rds/umn/en-us_image_0000001419863814.png new file mode 100644 index 000000000..ad79b27da Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863814.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863830.png b/docs/rds/umn/en-us_image_0000001419863830.png new file mode 100644 index 000000000..62ddb8e0f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863830.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863834.png b/docs/rds/umn/en-us_image_0000001419863834.png new file mode 100644 index 000000000..d232ef1a9 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863834.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863846.png b/docs/rds/umn/en-us_image_0000001419863846.png new file mode 100644 index 000000000..9767a5620 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863846.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863866.png b/docs/rds/umn/en-us_image_0000001419863866.png new file mode 100644 index 000000000..21acd3c8b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863866.png differ diff --git a/docs/rds/umn/en-us_image_0000001419863886.png b/docs/rds/umn/en-us_image_0000001419863886.png new file mode 100644 index 000000000..d5a396a32 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001419863886.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023530.png b/docs/rds/umn/en-us_image_0000001420023530.png new file mode 100644 index 000000000..f0934c462 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023530.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023546.png b/docs/rds/umn/en-us_image_0000001420023546.png new file mode 100644 index 000000000..4b159e167 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023546.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023606.png b/docs/rds/umn/en-us_image_0000001420023606.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023606.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023642.png b/docs/rds/umn/en-us_image_0000001420023642.png new file mode 100644 index 000000000..d232ef1a9 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023642.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023654.png b/docs/rds/umn/en-us_image_0000001420023654.png new file mode 100644 index 000000000..9a5be8d67 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023654.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023658.png b/docs/rds/umn/en-us_image_0000001420023658.png new file mode 100644 index 000000000..1267615e3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023658.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023666.png b/docs/rds/umn/en-us_image_0000001420023666.png new file mode 100644 index 000000000..378685d21 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023666.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023698.png b/docs/rds/umn/en-us_image_0000001420023698.png new file mode 100644 index 000000000..0610c163b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023698.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023730.png b/docs/rds/umn/en-us_image_0000001420023730.png new file mode 100644 index 000000000..916f934f7 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023730.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023746.png b/docs/rds/umn/en-us_image_0000001420023746.png new file mode 100644 index 000000000..284eb60d4 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023746.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023750.png b/docs/rds/umn/en-us_image_0000001420023750.png new file mode 100644 index 000000000..d232ef1a9 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023750.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023754.png b/docs/rds/umn/en-us_image_0000001420023754.png new file mode 100644 index 000000000..61dfbfaaa Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023754.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023786.png b/docs/rds/umn/en-us_image_0000001420023786.png new file mode 100644 index 000000000..bfb03c8a1 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023786.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023810.png b/docs/rds/umn/en-us_image_0000001420023810.png new file mode 100644 index 000000000..6385d0854 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023810.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023814.png b/docs/rds/umn/en-us_image_0000001420023814.png new file mode 100644 index 000000000..c4ab9077b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023814.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023818.png b/docs/rds/umn/en-us_image_0000001420023818.png new file mode 100644 index 000000000..2adf7d4df Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023818.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023822.png b/docs/rds/umn/en-us_image_0000001420023822.png new file mode 100644 index 000000000..f5da78672 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023822.png differ diff --git a/docs/rds/umn/en-us_image_0000001420023830.png b/docs/rds/umn/en-us_image_0000001420023830.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420023830.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181154.png b/docs/rds/umn/en-us_image_0000001420181154.png new file mode 100644 index 000000000..65f98b41b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181154.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181286.png b/docs/rds/umn/en-us_image_0000001420181286.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181286.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181290.png b/docs/rds/umn/en-us_image_0000001420181290.png new file mode 100644 index 000000000..c27951e69 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181290.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181302.png b/docs/rds/umn/en-us_image_0000001420181302.png new file mode 100644 index 000000000..1267615e3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181302.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181394.png b/docs/rds/umn/en-us_image_0000001420181394.png new file mode 100644 index 000000000..70a7eda6c Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181394.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181398.png b/docs/rds/umn/en-us_image_0000001420181398.png new file mode 100644 index 000000000..ad79b27da Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181398.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181410.png b/docs/rds/umn/en-us_image_0000001420181410.png new file mode 100644 index 000000000..bfec41545 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181410.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181422.png b/docs/rds/umn/en-us_image_0000001420181422.png new file mode 100644 index 000000000..48763e5cf Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181422.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181438.png b/docs/rds/umn/en-us_image_0000001420181438.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181438.png differ diff --git a/docs/rds/umn/en-us_image_0000001420181450.png b/docs/rds/umn/en-us_image_0000001420181450.png new file mode 100644 index 000000000..cf71491f3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420181450.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340466.png b/docs/rds/umn/en-us_image_0000001420340466.png new file mode 100644 index 000000000..1a22ffbf6 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340466.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340506.png b/docs/rds/umn/en-us_image_0000001420340506.png new file mode 100644 index 000000000..378685d21 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340506.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340574.png b/docs/rds/umn/en-us_image_0000001420340574.png new file mode 100644 index 000000000..62ddb8e0f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340574.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340582.png b/docs/rds/umn/en-us_image_0000001420340582.png new file mode 100644 index 000000000..3a06c59bf Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340582.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340598.png b/docs/rds/umn/en-us_image_0000001420340598.png new file mode 100644 index 000000000..90469ade7 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340598.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340614.png b/docs/rds/umn/en-us_image_0000001420340614.png new file mode 100644 index 000000000..bfec41545 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340614.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340634.png b/docs/rds/umn/en-us_image_0000001420340634.png new file mode 100644 index 000000000..c4ab9077b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340634.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340670.png b/docs/rds/umn/en-us_image_0000001420340670.png new file mode 100644 index 000000000..c4ab9077b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340670.png differ diff --git a/docs/rds/umn/en-us_image_0000001420340718.png b/docs/rds/umn/en-us_image_0000001420340718.png new file mode 100644 index 000000000..2e4d8d5be Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001420340718.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940549.png b/docs/rds/umn/en-us_image_0000001469940549.png new file mode 100644 index 000000000..06c5fbfbd Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940549.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940645.png b/docs/rds/umn/en-us_image_0000001469940645.png new file mode 100644 index 000000000..81fefa449 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940645.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940653.png b/docs/rds/umn/en-us_image_0000001469940653.png new file mode 100644 index 000000000..bfec41545 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940653.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940665.png b/docs/rds/umn/en-us_image_0000001469940665.png new file mode 100644 index 000000000..cc54e03a4 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940665.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940669.png b/docs/rds/umn/en-us_image_0000001469940669.png new file mode 100644 index 000000000..c4ab9077b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940669.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940677.png b/docs/rds/umn/en-us_image_0000001469940677.png new file mode 100644 index 000000000..cf9beddee Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940677.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940697.png b/docs/rds/umn/en-us_image_0000001469940697.png new file mode 100644 index 000000000..2aaabba0e Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940697.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940709.png b/docs/rds/umn/en-us_image_0000001469940709.png new file mode 100644 index 000000000..05ec8ce57 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940709.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940721.png b/docs/rds/umn/en-us_image_0000001469940721.png new file mode 100644 index 000000000..fe0485d83 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940721.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940729.png b/docs/rds/umn/en-us_image_0000001469940729.png new file mode 100644 index 000000000..fe0485d83 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940729.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940745.png b/docs/rds/umn/en-us_image_0000001469940745.png new file mode 100644 index 000000000..48e4002d8 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940745.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940765.png b/docs/rds/umn/en-us_image_0000001469940765.png new file mode 100644 index 000000000..7dfb0f9e2 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940765.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940773.png b/docs/rds/umn/en-us_image_0000001469940773.png new file mode 100644 index 000000000..57c6a81ca Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940773.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940781.png b/docs/rds/umn/en-us_image_0000001469940781.png new file mode 100644 index 000000000..ceebf4a0a Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940781.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940797.png b/docs/rds/umn/en-us_image_0000001469940797.png new file mode 100644 index 000000000..c1772796a Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940797.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940813.png b/docs/rds/umn/en-us_image_0000001469940813.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940813.png differ diff --git a/docs/rds/umn/en-us_image_0000001469940849.png b/docs/rds/umn/en-us_image_0000001469940849.png new file mode 100644 index 000000000..d5a396a32 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001469940849.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140289.png b/docs/rds/umn/en-us_image_0000001470140289.png new file mode 100644 index 000000000..378685d21 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140289.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140341.png b/docs/rds/umn/en-us_image_0000001470140341.png new file mode 100644 index 000000000..fe0485d83 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140341.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140357.png b/docs/rds/umn/en-us_image_0000001470140357.png new file mode 100644 index 000000000..3fb922114 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140357.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140361.png b/docs/rds/umn/en-us_image_0000001470140361.png new file mode 100644 index 000000000..bbc75ba41 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140361.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140373.png b/docs/rds/umn/en-us_image_0000001470140373.png new file mode 100644 index 000000000..378685d21 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140373.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140377.png b/docs/rds/umn/en-us_image_0000001470140377.png new file mode 100644 index 000000000..62ddb8e0f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140377.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140389.png b/docs/rds/umn/en-us_image_0000001470140389.png new file mode 100644 index 000000000..70a7eda6c Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140389.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140409.png b/docs/rds/umn/en-us_image_0000001470140409.png new file mode 100644 index 000000000..c4ab9077b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140409.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140445.png b/docs/rds/umn/en-us_image_0000001470140445.png new file mode 100644 index 000000000..c8ddcbebc Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140445.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140453.png b/docs/rds/umn/en-us_image_0000001470140453.png new file mode 100644 index 000000000..c27951e69 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140453.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140461.png b/docs/rds/umn/en-us_image_0000001470140461.png new file mode 100644 index 000000000..bfec41545 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140461.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140481.png b/docs/rds/umn/en-us_image_0000001470140481.png new file mode 100644 index 000000000..28b241487 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140481.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140493.png b/docs/rds/umn/en-us_image_0000001470140493.png new file mode 100644 index 000000000..c4ab9077b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140493.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140533.png b/docs/rds/umn/en-us_image_0000001470140533.png new file mode 100644 index 000000000..bfec41545 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140533.png differ diff --git a/docs/rds/umn/en-us_image_0000001470140545.png b/docs/rds/umn/en-us_image_0000001470140545.png new file mode 100644 index 000000000..2415f0436 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470140545.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260029.png b/docs/rds/umn/en-us_image_0000001470260029.png new file mode 100644 index 000000000..3a06c59bf Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260029.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260033.png b/docs/rds/umn/en-us_image_0000001470260033.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260033.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260045.png b/docs/rds/umn/en-us_image_0000001470260045.png new file mode 100644 index 000000000..09061607f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260045.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260077.png b/docs/rds/umn/en-us_image_0000001470260077.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260077.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260089.png b/docs/rds/umn/en-us_image_0000001470260089.png new file mode 100644 index 000000000..1267615e3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260089.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260141.png b/docs/rds/umn/en-us_image_0000001470260141.png new file mode 100644 index 000000000..1267615e3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260141.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260157.png b/docs/rds/umn/en-us_image_0000001470260157.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260157.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260185.png b/docs/rds/umn/en-us_image_0000001470260185.png new file mode 100644 index 000000000..1210f838f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260185.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260209.png b/docs/rds/umn/en-us_image_0000001470260209.png new file mode 100644 index 000000000..cf71491f3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260209.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260221.png b/docs/rds/umn/en-us_image_0000001470260221.png new file mode 100644 index 000000000..b0bcfa510 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260221.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260233.png b/docs/rds/umn/en-us_image_0000001470260233.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260233.png differ diff --git a/docs/rds/umn/en-us_image_0000001470260245.png b/docs/rds/umn/en-us_image_0000001470260245.png new file mode 100644 index 000000000..88a561a7b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470260245.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340005.png b/docs/rds/umn/en-us_image_0000001470340005.png new file mode 100644 index 000000000..90469ade7 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340005.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340109.png b/docs/rds/umn/en-us_image_0000001470340109.png new file mode 100644 index 000000000..62ddb8e0f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340109.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340125.png b/docs/rds/umn/en-us_image_0000001470340125.png new file mode 100644 index 000000000..90469ade7 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340125.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340153.png b/docs/rds/umn/en-us_image_0000001470340153.png new file mode 100644 index 000000000..97358745f Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340153.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340169.png b/docs/rds/umn/en-us_image_0000001470340169.png new file mode 100644 index 000000000..7dfb0f9e2 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340169.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340205.png b/docs/rds/umn/en-us_image_0000001470340205.png new file mode 100644 index 000000000..dec4adb0b Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340205.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340221.png b/docs/rds/umn/en-us_image_0000001470340221.png new file mode 100644 index 000000000..c8d49ac88 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340221.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340225.png b/docs/rds/umn/en-us_image_0000001470340225.png new file mode 100644 index 000000000..4ba2bdf47 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340225.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340229.png b/docs/rds/umn/en-us_image_0000001470340229.png new file mode 100644 index 000000000..2057d4ed4 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340229.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340233.png b/docs/rds/umn/en-us_image_0000001470340233.png new file mode 100644 index 000000000..bfec41545 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340233.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340241.png b/docs/rds/umn/en-us_image_0000001470340241.png new file mode 100644 index 000000000..ceebf4a0a Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340241.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340253.png b/docs/rds/umn/en-us_image_0000001470340253.png new file mode 100644 index 000000000..1267615e3 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340253.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340297.png b/docs/rds/umn/en-us_image_0000001470340297.png new file mode 100644 index 000000000..d3444b7f1 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340297.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340305.png b/docs/rds/umn/en-us_image_0000001470340305.png new file mode 100644 index 000000000..7cabd6199 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001470340305.png differ diff --git a/docs/rds/umn/en-us_image_0192954074.png b/docs/rds/umn/en-us_image_0192954074.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/rds/umn/en-us_image_0192954074.png differ diff --git a/docs/rds/umn/en-us_topic_0000001419863378.html b/docs/rds/umn/en-us_topic_0000001419863378.html new file mode 100644 index 000000000..3b63528a2 --- /dev/null +++ b/docs/rds/umn/en-us_topic_0000001419863378.html @@ -0,0 +1,370 @@ + + +

Change History

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Released On

+

Description

+

2022-10-30

+

Modified the following content:

+
  • Modified the description of the tag value in Editing a Tag.
  • Modified the description of the Administrator Password.
+

2022-07-22

+

Modified the following content:

+

Supported Table Name settings during MySQL 8.0 instance creation in Step 1: Create a DB Instance.

+

2022-03-22

+

Modified the following content:

+

Supported PostgreSQL 13.

+

2022-02-21

+

Modified the following content:

+ +

2022-01-28

+

Modified the following content:

+ +

2021-08-13

+

Modified the following content:

+ +

2021-05-25

+

Modified the following content:

+ +

2021-03-29

+

Modified the following content:

+ +

2021-02-01

+

Modified the following content:

+

Supported PostgreSQL 12.

+

2020-10-15

+

Modified the following content:

+
  • Supported PostgreSQL Enhanced Edition.
  • Supported Microsoft SQL Server 2017 EE.
  • Supported Microsoft SQL Server 2017 SE.
  • Supported creating read replicas for Microsoft SQL Server 2017 EE DB instances.
  • Added support for MySQL minor version upgrades in section Upgrading a Minor Version.
  • Supported primary/standby switchover or failover logs for RDS MySQL DB instances.
  • Changed "Parameter Group" to "Parameter Template".
+

2020-04-17

+

Modified the following content:

+

Supported MySQL 8.0.

+

2019-11-30

+

Added an FAQ Does RDS for PostgreSQL Support the test_decoding Plugin?

+

2019-10-30

+

Modified the following content:

+ +

2019-09-27

+

Accepted for RM-466, RM-525, RM-581, RM-583, RM-604, RM-650, RM-680, and RM-681.

+

2019-09-17

+

Modified the following content:

+ +

2019-09-12

+

Modified the following content:

+

Modified the content in the following sections: Comparison Between RDS and Self-Built Databases, Downloading a Backup File, Applying a Parameter Template, Key Operations Supported by CTS, Scaling up Storage Space, Rebooting DB Instances or Read Replicas, Restoring from Backup Files to RDS for PostgreSQL, Configuring Displayed Metrics, Key Operations Supported by CTS, Creating or Deleting a Plugin, Configuring Displayed Metrics, Key Operations Supported by CTS, Does RDS Support Cross-AZ High Availability?, and Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?

+

2019-08-15

+

Modified the following content:

+
  • Added the NOTE error log level for MySQL DB instances in section Viewing Error Logs.
  • Changed "Character Set" to "Server Collation" and modified its description for Microsoft SQL Server DB instances.
+

2019-06-30

+

Modified the following content:

+
  • Supported batch creation of DB instances.
  • Supported exporting DB instance lists.
  • Supported the task center.
  • Supported creating DB instances with the same specifications as the selected DB instance.
  • Supported selecting floating IP addresses during DB instance creation.
  • Supported restoration to existing DB instances.
  • Added the error log level WARNING for MySQL DB instances in section Viewing Error Logs.
  • Supported 16 vCPUs | 64 GB, 16 vCPUs | 128 GB, and 32 vCPUs | 256 GB for MySQL DB instances in section DB Instance Classes.
  • Supported modifying floating IP addresses of existing DB instances for MySQL and PostgreSQL.
  • Supported 16 vCPUs | 32 GB and 16 vCPUs | 64 GB for PostgreSQL DB instances in section DB Instance Classes.
  • Supported transparent data encryption for Microsoft SQL Server DB instances in Configuring the TDE Function.
  • Supported slow query logs for Microsoft SQL Server DB instances in Viewing and Downloading Slow Query Logs.
  • Based on the console modifications, updated the following procedure descriptions: creating DB instances, connecting DB instances, creating read replicas, scaling up storage space, changing instance classes, creating backups, restoring backups, changing database ports, changing administrator passwords, rebooting DB instances, deleting DB instances, and task center.
+

2019-04-03

+

Modified the following content:

+
  • Supported restoration to original DB instances for Microsoft SQL Server DB instances.
  • Supported database-level restoration for Microsoft SQL Server DB instances.
+

2019-03-28

+

Accepted in OTC-4.0.

+

2019-02-28

+

Modified the following content:

+
  • Modified the description in section Exporting a Parameter Template to the following: An exported parameter group has initially a blank change history.
  • Modified the description in the scenario in section Viewing Parameter Change History to the following: An exported or custom parameter group has initially a blank change history.
+

2019-02-25

+

Modified the following content:

+
  • Added the description in section Exporting a Parameter Template: An exported parameter group has initially a blank change history.
  • Supported the file name with a maximum of 81 characters when exporting a parameter group to a file in section Exporting a Parameter Template.
  • Added the description in the scenario in section Viewing Parameter Change History: An exported or custom parameter group has initially a blank change history.
  • Added the description in section Scaling up Storage Space: The DB instance is in Scaling up state when its storage space is being scaled up. For Microsoft SQL Server DB instances, backups cannot be created during the scale-up process. For MySQL and PostgreSQL DB instances, backup creation is not affected.
+

2019-02-15

+

Modified the following content:

+ +

2019-01-31

+

Modified the following content:

+
  • Added PostgreSQL 10 to the PostgreSQL engine in Table 1 in section Function Comparison.
  • Changed the maximum storage space to 4 TB in Function Comparison in section Function Comparison.
  • Supported adding tags during the DB instance creation.
  • Supported selecting parameter groups during the DB instance creation.
  • Optimized parameter group management: when you change certain parameter values in parameter groups in batches and save the changes, the changes will take effect only after you apply the parameter groups to DB instances.
+

2018-12-29

+

Modified the following content:

+
  • Supported PostgreSQL 10.
  • Supported Microsoft SQL Server 2016 EE.
  • Supported Microsoft SQL Server 2016 SE.
  • Supported selecting time zones during the DB instance creation.
  • Supported changing the DB instance type from single to primary/standby.
  • Supported DB instance storage space up to 4,000 GB.
+

2018-10-08

+

Accepted in OTC-3.2.

+

2018-09-26

+

Modified the following content:

+ +

2018-09-12

+

Modified the following content:

+
  • Deleted the release numbers and retained the release dates only in accordance with the unified style.
  • Added the hyperlink in 2 for ease of use.
  • Added the following description in section Creating a Parameter Template: RDS does not share parameter group quotas with DDS. All RDS DB engines share the parameter group quota.
  • Deleted [username@host] from the command in section Tablespace Management.
+

2018-08-31

+

Modified the following content:

+ +

2018-08-17

+

Modified the following content:

+
  • Changed PostGIS to postgis.
  • Added the following PostgreSQL plugins: auto_explain, pg_pathman, pg_stat_statements, and pg_hint_plan.
  • Changed "backups" to "automated backups".
  • Changed the quota of custom parameter groups to 1000. The quota is not shared by DDS.
  • Deleted [username@host] from the command.
  • Set the plugin name "postgis" in bold.
  • Adjusted the positions of constraints for earthdistance, timescaledb, and cube plugins.
+

2018-08-03

+

Modified the following content:

+
  • Enhanced password verification when a DB instance is created or the password of a database account is reset.
  • Added PostgreSQL plugins.
  • Optimized the disabling mechanism of the automated backup policy.
+

2018-07-03

+

Accepted in OTC-3.1.

+

2018-06-22

+

Modified the following content:

+

Added the impact of deleting keys after disk encryption is enabled.

+

2018-06-14

+

Modified the following content:

+
  • Added the change history of selecting a time zone when creating a Microsoft SQL Server DB instance.
  • Added the reference path for creating a key.
  • Added the maximum throughput of each storage type.
  • Optimized descriptions of subnets and security groups.
  • Optimized the public accessibility scenario.
  • Changed descriptions after successful DB instance creation from an ordered list to a nonsequential list.
  • Optimized the procedures of downloading backup files.
  • Added the description of the replication delay parameter.
  • Added an FAQ How Can I Obtain Microsoft SQL Server Error Logs Using Commands?
+

2018-06-08

+

Modified the following content:

+
  • Provided an option for enabling or disabling automated backups.
  • Optimized the procedures of downloading backup files from OBS.
  • Added the description of administrator password security.
+

2018-05-22

+

Modified the following content:

+

Optimized the description of disk encryption.

+

2018-05-17

+

Modified the following content:

+
  • Combined the content of "Access RDS" in restrictions.
  • Added the description of "Reboot an RDS DB instance" in restrictions.
  • Optimized the description of disk encryption.
  • Modified the DB instance specifications supported by Microsoft SQL Server.
+

2018-05-03

+

Modified the following content:

+
  • Supported disk encryption.
  • Supported Microsoft SQL Server instance with high specifications.
  • Supported multi-AZ deployment of Microsoft SQL Server HA DB instances.
  • Added information about product introduction.
  • Added the "Getting Started" sections for each DB engine.
  • Changed the minimum storage space of a disk to 40 GB when a DB instance is created.
  • Supported instance name modification when a DB instance is created.
  • Supported time zone selections when creating a Microsoft SQL Server DB instance.
+

2018-03-31

+

Accepted in OTC-3.0.

+

2018-03-20

+
  • Adjust HA Type sequence to show primary/standby first.
  • Add description of primary/standby at Scenarios and Step 1 of section 3.10.
+

2018-03-14

+

Optimized the automated backup policy description.

+

2018-03-05

+

Optimized the commands for exporting and importing data.

+

2018-02-23

+
  • Changed the MySQL version to 5.7.20.
  • Deleted the frozen status and description.
  • Updated the commands.
  • Added the description: If the retention period is 0 days (indicating that the automated backup is disabled) and you set it to one or more days, the backup policy is enabled and a full automated backup is triggered instantly.
  • Added a description.
  • Supported tag management.
+

2018-02-09

+

Modified the following content:

+
  • Based on the console modifications, updated the following procedure descriptions: creating DB instances, connecting DB instances, creating read replicas, scaling up storage space, changing instance classes, creating backups, restoring backups, changing database ports, changing administrator passwords, rebooting DB instances, and deleting DB instances.
  • Supported DB instance name modifications.
+

2018-01-31

+

Modified the following content:

+
  • Supported tag management.
  • Supported PostgreSQL plugins.
+

2017-10-31

+

Modified the following content:

+
  • Supported MySQL 5.7.20.
  • Supported PostgreSQL 9.6.5.
+

2017-10-13

+

Modified the following content:

+
  • Added the suffix description for the DB instance name.
  • Added the description of the EIPs displayed in the dialog box when enabling public accessibility.
+

2017-09-27

+

Modified the following content:

+
  • Modified the Microsoft SQL Server log loading method.
  • Added a description to the EIP binding and unbinding: A reboot is required after enabling public accessibility for Microsoft SQL Server DB instances.
+

2017-08-30

+

Modified the following content:

+ +

2017-07-30

+

Modified the following content:

+ +

2017-06-30

+

Modified the following content:

+

Supported changing the descriptions of custom parameter groups.

+

2017-06-14

+

Modified the following content:

+ +

2017-05-06

+

Modified the following content:

+

Supported MySQL 5.7.17.

+

2017-04-28

+

Modified the following content:

+
  • Supported Microsoft SQL Server 2014 SP2 SE.
  • Supported parameter groups.
+

2017-03-31

+

Modified the following content:

+
  • Supported resetting the administrator password.
  • Updated the SSL certificate.
+

2017-02-28

+

Modified the following content:

+
  • Supported MySQL 5.6.35.
  • Supported changing the database port.
+

2017-02-08

+

Modified the following content:

+
  • Adjusted the document structure.
  • Supported PostgreSQL 9.5.
  • Added section Glossary.
+

2016-11-24

+

Modified the following content:

+ +

2016-10-29

+

Modified the following content:

+
  • Modified description of snapshot management.
  • Supported MySQL 5.6.34.
+

2016-10-19

+

Modified the following content:

+
  • Supported MySQL 5.6.33.
  • Supported scaling up DB clusters.
  • Supported creating and managing snapshots.
  • Supported changing the DB instance CPU and memory.
  • Supported restoring a DB instance to a specified point in time.
+

2016-07-15

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/rds/umn/en-us_topic_0043898356.html b/docs/rds/umn/en-us_topic_0043898356.html new file mode 100644 index 000000000..a01f10c5f --- /dev/null +++ b/docs/rds/umn/en-us_topic_0043898356.html @@ -0,0 +1,53 @@ + + +

DB Engines and Versions

+

Table 1 lists the DB engines and versions supported by RDS.

+

For new applications, you are advised to use the latest major version of the DB engine, for example, MySQL 8.0. When you create a DB instance, you can select a major DB engine version only (such as MySQL 8.0). The system will automatically select an appropriate minor version (such as 8.0.17) for you. After the DB instance is created, you can view the minor version in the DB Engine Version column on the Instances page. The DB engine and version vary according to site requirements.

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 DB engines and versions

DB Engine

+

Single

+

Primary/Standby

+

Cluster

+

MySQL

+
  • 8.0
  • 5.7
  • 5.6
+
  • 8.0
  • 5.7
  • 5.6
+

Not supported

+

PostgreSQL

+		 + +

Not supported

+

Microsoft SQL Server

+
  • 2017 SE
  • 2016 EE
  • 2016 SE
  • 2014 SE
+
  • 2017 SE
  • 2016 EE
  • 2016 SE
  • 2014 SE
+
  • 2017 EE
+
+
+
+
+
+
Parent topic: DB Instance Description
+
+
+ diff --git a/docs/rds/umn/en-us_topic_0046585334.html b/docs/rds/umn/en-us_topic_0046585334.html new file mode 100644 index 000000000..b04a0b210 --- /dev/null +++ b/docs/rds/umn/en-us_topic_0046585334.html @@ -0,0 +1,34 @@ + + +

Operation Guide

+

You can create and connect to DB instances on the RDS console.

+

Flowchart

Figure 1 Flowchart
+
+

Procedure

+
+ + + + + + + + + + +
Table 1 Related operations and references

Operation

+

Reference

+

Creating an RDS DB instance

+

Step 1: Create a DB Instance

+

Connecting to an RDS DB Instance

+

Step 2: Connect to a DB Instance

+
+
+
+
+ + diff --git a/docs/rds/umn/en-us_topic_0053089697.html b/docs/rds/umn/en-us_topic_0053089697.html new file mode 100644 index 000000000..dbee47f7d --- /dev/null +++ b/docs/rds/umn/en-us_topic_0053089697.html @@ -0,0 +1,20 @@ + + +

Step 2: Connect to a DB Instance

+

+
+ + diff --git a/docs/rds/umn/en-us_topic_add_read_replica.html b/docs/rds/umn/en-us_topic_add_read_replica.html new file mode 100644 index 000000000..a97b3e853 --- /dev/null +++ b/docs/rds/umn/en-us_topic_add_read_replica.html @@ -0,0 +1,122 @@ + + +

Creating a Read Replica

+

Scenarios

Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.

+
+

After DB instances are created, you can create read replicas for them.

+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click Create Read Replica in the Operation column.

    Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

    +

  5. On the displayed page, configure information about the DB instance and click Next.

    +

    + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    By default, read replicas are in the same region as the primary DB instance.

    +

    DB Instance Name

    +

    Must start with a letter and consist of 4 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).

    +

    DB Engine

    +

    Same as the DB engine of the primary DB instance by default and cannot be changed.

    +

    DB Engine Version

    +

    Same as the DB engine version of the primary DB instance by default and cannot be changed.

    +

    AZ

    +

    RDS allows you to deploy primary DB instances and read replicas in a single AZ or across AZs to improve reliability.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Instance specifications

    Parameter

    +

    Description

    +

    Instance Class

    +

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and maximum IOPS.

    +

    For details about instance classes, see section DB Instance Classes.

    +

    +

    +

    +

    After a DB instance is created, you can change its instance class (CPU and memory). For details, see section Changing a DB Instance Class.

    +

    +

    Storage Type

    +

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    +
    • Common I/O: uses the SATA disk type that supports a maximum throughput of 90 MB/s.
    • Ultra-high I/O: uses the SSD disk type that supports a maximum throughput of 350 MB/s.
    +

    Storage Space

    +

    Contains the file system overhead required for inode, reserved block, and database operation.

    +

    By default, storage space of a read replica is the same as that of the primary DB instance.

    +

    Disk Encryption

    +
    • Disable: indicates the encryption function is disabled.
    • Enable: indicates the encryption function is enabled. Security is improved but system performance is affected.

      Key Name: indicates the tenant key. You can select an existing key or create a new one.

      +
      NOTE:
      • Once the DB instance is created, you cannot modify the disk encryption status or change the key. The backup data stored in OBS is not encrypted.
      • After an RDS DB instance is created, do not disable or delete a key that is currently in use. Otherwise, RDS will be unavailable and data cannot be restored.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      +
    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    Same as the primary DB instance's VPC.

    +

    Subnet

    +

    Same as the primary DB instance's subnet. A floating IP address is automatically assigned when you create a read replica. You can also enter an unused floating IP address in the subnet CIDR block. After the read replica is created, you can change the floating IP address.

    +

    Security Group

    +

    Same as the primary DB instance's VPC.

    +
    +
    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. After a read replica is created, you can view and manage it.

    For details about how to manage read replicas, see Managing a Read Replica.

    +

    You can view the detailed progress and result of the task on the Task Center page.

    +

+
+

Follow-up Operations

Managing a Read Replica

+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/en-us_topic_apply_for_rds.html b/docs/rds/umn/en-us_topic_apply_for_rds.html new file mode 100644 index 000000000..4d1676cb1 --- /dev/null +++ b/docs/rds/umn/en-us_topic_apply_for_rds.html @@ -0,0 +1,13 @@ + + +

Overview

+

Process

Figure 1 illustrates the process of connecting to a MySQL DB instance through a private network.

+
Figure 1 Connecting to a DB instance through a private network
+
+
+ + diff --git a/docs/rds/umn/en-us_topic_backup_restore.html b/docs/rds/umn/en-us_topic_backup_restore.html new file mode 100644 index 000000000..2a8bdde3d --- /dev/null +++ b/docs/rds/umn/en-us_topic_backup_restore.html @@ -0,0 +1,17 @@ + + +

Working with Backups

+

RDS supports backups and restorations to ensure data reliability.

+

Automated Backups

Automated backups are created during the backup time window for your DB instances. RDS saves automated backups based on a retention period you specify. If necessary, you can restore a DB instance to any point in time during your backup retention period. For details, see Configuring an Automated Backup Policy.

+
+

Manual Backups

Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually. For details, see Creating a Manual Backup.

+
+

Downloading a Backup File

You can download a full or an incremental backup file for local data backup or restoration. For details, see Downloading a Backup File and Downloading a Binlog Backup File.

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/en-us_topic_connect_instance.html b/docs/rds/umn/en-us_topic_connect_instance.html new file mode 100644 index 000000000..a9b77c90a --- /dev/null +++ b/docs/rds/umn/en-us_topic_connect_instance.html @@ -0,0 +1,107 @@ + + +

Connecting to a DB Instance Through a Public Network

+

You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.

+

Prerequisites

  1. An EIP has been bound to the target DB instance and security group rules have been configured.
    1. Bind an EIP to the target DB instance.

      For details about how to bind an EIP, see section Binding an EIP.

      +
    2. Obtain the IP address of the local device.
    3. Configure security group rules.

      Add the IP address obtained in 1.b and the instance port to the inbound rule of the security group.

      +

      For details about how to configure a security group rule, see section Configuring Security Group Rules.

      +
    4. Run the ping command to check the connectivity between the local device and the EIP that has been bound to the DB instance in 1.a.
    +
  2. You have installed a database client to connect to DB instances.

    You can use a database client to connect to the target DB instance in the Linux or Windows operating system (OS).

    +
    • In the Linux OS, you need to install a MySQL client on the ECS. 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 section How Can I Install the MySQL Client?

      +
    + +
+
+

Using MySQL-Front to Connect to a DB Instance

  1. Start MySQL-Front.
  2. In the displayed dialog box, click New.

    Figure 1 Connection management
    +

  3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

    Figure 2 Adding an account
    + +
    + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Name

    +

    Indicates the name of the database connection task. If you do not set this parameter, it will be the same as the Host value by default.

    +

    Host

    +

    Indicates the EIP of the DB instance to be connected.

    +

    Port

    +

    Indicates the private network port of the DB instance.

    +

    User

    +

    Indicates the name of the user who will access the DB instance. The default user is root.

    +

    Password

    +

    Indicates the password of the RDS database account.

    +
    +
    +

  4. In the displayed window, select the connection that you have created in Figure 3 and click Open.

    If the connection information is correct, the DB instance is successfully connected.
    Figure 3 Opening a session
    +
    +

    If the connection fails, ensure that preparations have been correctly made in Prerequisites and try again.

    +
    +

+
+

Using SSL to Connect to a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
  5. 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?

    • Since April 2017, RDS has offered a new root certificate that has a 20-year validation period. The new certificate takes effect after DB instances are rebooted. Replace the old certificate before it expires to improve system security.

      For details, see section How Can I Identify the Validity Period of an SSL Root Certificate?

      +
    • You can also download the certificate bundle, which contains both the new certificate provided since April 2017 and the old certificate.
    +
    +

  6. Connect to an RDS DB instance. The Linux OS is used as an example.

    mysql -h <host> -P <port> -u <userName> -p --ssl-ca=<caDIR> +
    + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    <host>

    +

    Indicates the EIP of the DB instance to be connected.

    +

    <port>

    +

    Indicates the port of the DB instance to be connected.

    +

    <userName>

    +

    Indicates the username of the RDS database account. The default administrator is root.

    +

    <caDIR>

    +

    Indicates the directory of the CA certificate. The certificate should be stored in the directory where the command is executed.

    +
    +
    +
    +

    For example, to connect to a DB instance through an SSL connection as user root, run the following command:

    +

    mysql -h 172.16.0.31 -P 3306 -u root -p --ssl-ca=ca.pem

    +

    Enter the password of the database account if the following information is displayed:

    +
    Enter password:
    +

    If the connection fails, ensure that preparations have been correctly made in Prerequisites and try again.

    +
    +

+
+
+ + diff --git a/docs/rds/umn/en-us_topic_dashboard.html b/docs/rds/umn/en-us_topic_dashboard.html new file mode 100644 index 000000000..9b7ea4f29 --- /dev/null +++ b/docs/rds/umn/en-us_topic_dashboard.html @@ -0,0 +1,25 @@ + + +

What Is RDS?

+

RDS is a cloud-based web service that is reliable, scalable, and easy to manage. RDS supports the following DB engines:

+ +

RDS provides a comprehensive performance monitoring system, multi-level security protection measures, and a professional database management platform, allowing you to easily set up and scale a relational database. On the RDS console, you can perform almost all necessary tasks and no programming is required. The console simplifies operations and reduces routine O&M workloads, so you can stay focused on application and service development.

+

RDS for MySQL

MySQL is one of the world's most popular open-source relational databases. It works with the Linux, Apache, and Perl/PHP/Python to establish a LAMP model to provide efficient web solutions. RDS for MySQL is reliable, secure, scalable, inexpensive, and easy to manage.

+
  • It supports various web applications and is cost-effective, preferred by small- and medium-sized enterprises.
  • A web-based console provides comprehensive monitoring information, making your operations easy and visual.
  • You can flexibly scale resources based on your service requirements and pay for only what you use.
+

For details about the versions supported by RDS for MySQL, see DB Engines and Versions.

+
+

RDS for PostgreSQL

PostgreSQL is an open-source object-relational database management system that focuses on extensibility and standards compliance. It is known as the most advanced open-source database available. RDS for PostgreSQL excels in processing complex online transaction processing (OLTP) transactions and supports NoSQL (JSON, XML, or hstore) and geographic information system (GIS) data types. It has earned a reputation for reliability and data integrity, and is widely used for websites, location-based applications, and complex data object processing.

+
  • RDS for PostgreSQL supports the postgis plugin and provides excellent spatial performance.
  • RDS for PostgreSQL is a good cost-effective solution for many different scenarios. You can flexibly scale resources based on your service requirements and pay for only what you use.
+

For details about the versions supported by RDS for PostgreSQL, see DB Engines and Versions.

+
+

RDS for SQL Server

Microsoft SQL Server is a well-established commercial database with a mature enterprise-class architecture. One-stop deployment simplifies key O&M services and greatly reduces labor costs. It is widely used in government, finance, medical care, education, and gaming.

+

RDS for SQL Server is reliable, scalable, inexpensive, and easy to manage. It uses a high availability (HA) architecture, guarantees data security, and recovers from faults within seconds.

+

For details about the versions supported by RDS for SQL Server, see DB Engines and Versions.

+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/rds/umn/en-us_topic_parameter_group.html b/docs/rds/umn/en-us_topic_parameter_group.html new file mode 100644 index 000000000..f7328dd87 --- /dev/null +++ b/docs/rds/umn/en-us_topic_parameter_group.html @@ -0,0 +1,24 @@ + + +

Creating a Parameter Template

+

You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

+

When you create a DB instance, RDS will automatically allocate a default database parameter template for you. This default template contains DB engine defaults and system defaults that are configured based on the engine, compute class, and allocated storage of the instance. Default parameter templates cannot be modified, but you can create your own parameter template to change parameter settings.

+

Not all of the DB engine parameters in a custom parameter template can be changed.

+
+

If you want to use a custom parameter template, you simply create a parameter template and select it when you create a DB instance or apply it to an existing DB instance following the instructions provided in section Applying a Parameter Template.

+

When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template following the instructions provided in section Replicating a Parameter Template.

+

The following are the key points you should know when using parameters in a parameter template:

+
  • When you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately. When you change a static parameter value in a parameter template and save the change, the change will take effect only after you manually reboot the DB instances that the parameter template applies to.
  • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
+

RDS does not share parameter template quotas with DDS.

+

You can create a maximum of 100 parameter templates for RDS DB instances. All RDS DB engines share the parameter template quota.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Create Parameter Template.
  5. In the displayed dialog box, configure required information and click OK.

    • Select a DB engine for the parameter template.
    • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
    • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/en-us_topic_scale_cluster.html b/docs/rds/umn/en-us_topic_scale_cluster.html new file mode 100644 index 000000000..aa01bb4ad --- /dev/null +++ b/docs/rds/umn/en-us_topic_scale_cluster.html @@ -0,0 +1,35 @@ + + +

Scaling up Storage Space

+

Scenarios

If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

+

If your storage space usage reaches up to 95% for a disk less than 1 TB or the remaining space becomes 50 GB for a disk no less than 1 TB, the DB instance status becomes Storage full and data cannot be written to databases. In this case, scale up storage space to make the DB instance preserve at least 15% of its capacity to work properly.

+

You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

+

For details about the causes and solutions of insufficient storage space, see section What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?

+

RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

+
+

Constraints

  • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
  • The DB instance is in Scaling up state when its storage space is being scaled up and the backup services are not affected.
  • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
  • You cannot reboot or delete a DB instance that is being scaled up.
  • Storage space can only be scaled up, not down.
  • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.
+
+

Scaling up a Primary DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Scale Storage Space in the Operation column.

    You can also perform the following operations to scale up storage space:

    +
    • Click the target DB instance to enter the Basic Information page. In the Storage Space area, click Scale.
    +

  5. On the displayed page, specify the new storage space and click Next.

    The minimum increment for each scaling is 10 GB.

    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. View the scale-up result.

    Scaling up storage space takes 3-5 minutes. During the time period, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Basic Information page to verify that the scale-up is successful.

    +

    If the DB instance is running the MySQL DB engine, you can view the detailed progress and result of the task on the Task Center page. For details, see section Task Center.

    +

+
+

Scaling up a Read Replica

Scaling up the storage space of a read replica does not affect that of the primary DB instance. Therefore, you can separately scale read replicas to meet service requirements. New storage space of read replicas after scaling up must be greater than or equal to that of the primary DB instance.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click in front of it. Locate a read replica to be scaled and choose More > Scale Storage Space in the Operation column.

    You can also perform the following operations to scale up storage space:

    +
    • Click the target DB instance to enter the Basic Information page. In the Storage Space area, click Scale.
    +

  5. On the displayed page, specify the new storage space and click Next.

    The minimum increment for each scaling is 10 GB.

    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. View the scale-up result.

    Scaling up storage space takes 3-5 minutes. During the time period, the status of the read replica on the Instances page will be Scaling up. Click the read replica and view the utilization on the displayed Basic Information page to verify that the scale-up is successful.

    +

    If the read replica is running the MySQL DB engine, you can view the detailed progress and result of the task on the Task Center page. For details, see section Task Center.

    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/en-us_topic_scale_rds.html b/docs/rds/umn/en-us_topic_scale_rds.html new file mode 100644 index 000000000..4815c3c39 --- /dev/null +++ b/docs/rds/umn/en-us_topic_scale_rds.html @@ -0,0 +1,21 @@ + + +

Changing a DB Instance Class

+

Scenarios

You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.

+
+

Constraints

  • A DB instance cannot be deleted when its instance class is being changed.
  • After you change instance classes, the DB instances will be rebooted and service will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

    Alternatively, click the target DB instance to go to the Basic Information page. In the DB Information area, click Change in the Instance Class field.

    +

  5. On the displayed page, specify the new instance class and click Next.

    +

  6. View the DB instance class change result.

    Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Basic Information page to check that the change is successful.

    +

    After you change a MySQL instance class, the values of the following parameters will also be changed accordingly: back_log, innodb_buffer_pool_size, innodb_log_buffer_size, innodb_log_files_in_group, max_connections, innodb_page_cleaners, innodb_buffer_pool_instances, threadpool_size, and slave_parallel_workers.

    +
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/en-us_topic_sqlserver_reset_password.html b/docs/rds/umn/en-us_topic_sqlserver_reset_password.html new file mode 100644 index 000000000..58b50398f --- /dev/null +++ b/docs/rds/umn/en-us_topic_sqlserver_reset_password.html @@ -0,0 +1,29 @@ + + +

Resetting the Administrator Password

+

Scenarios

You can reset the administrator password only through the primary DB instance.

+

You can also reset the password of your database account when using RDS.

+
+
  • If you have changed the administrator password of the primary DB instance, the administrator passwords of the standby DB instance and read replicas (if any) will also be changed accordingly.
  • The time required for the new password to take effect depends on the amount of service data currently being processed by the primary DB instance.
  • To protect against brute force hacking attempts and ensure system security, change your password periodically, such as every three or six months.
+
+

Method 1

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Reset Password in the Operation column.
  5. Enter and confirm a new 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 types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_+?). Enter a strong password and periodically change it for security reasons.

    +
    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
    • To submit the new password, click OK.
    • To cancel the reset operation, click Cancel.
    +
    +

+
+

Method 2

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field. In the displayed dialog box, enter and confirm a new 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 types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_+?). Enter a strong password and periodically change it for security reasons.

    +
    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
    • To submit the new password, click OK.
    • To cancel the reset operation, click Cancel.
    +
    +

+
+
+
+
+
Parent topic: Data Security
+
+
+ diff --git a/docs/rds/umn/index.html b/docs/rds/umn/index.html new file mode 100644 index 000000000..bb27070ec --- /dev/null +++ b/docs/rds/umn/index.html @@ -0,0 +1,15 @@ + + +

Getting Started with RDS for MySQL

+
+ + diff --git a/docs/rds/umn/public_sys-resources/ExpandCollapse.js b/docs/rds/umn/public_sys-resources/ExpandCollapse.js new file mode 100644 index 000000000..116ddaabf --- /dev/null +++ b/docs/rds/umn/public_sys-resources/ExpandCollapse.js @@ -0,0 +1 @@ +var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}}; \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/caution_3.0-en-us.png b/docs/rds/umn/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 000000000..60f607621 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/caution_3.0-en-us.png differ diff --git a/docs/rds/umn/public_sys-resources/commonltr.css b/docs/rds/umn/public_sys-resources/commonltr.css new file mode 100644 index 000000000..c5480b0ab --- /dev/null +++ b/docs/rds/umn/public_sys-resources/commonltr.css @@ -0,0 +1 @@ +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/commonltr_print.css b/docs/rds/umn/public_sys-resources/commonltr_print.css new file mode 100644 index 000000000..a59823141 --- /dev/null +++ b/docs/rds/umn/public_sys-resources/commonltr_print.css @@ -0,0 +1 @@ +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/commonrtl.css b/docs/rds/umn/public_sys-resources/commonrtl.css new file mode 100644 index 000000000..f261da752 --- /dev/null +++ b/docs/rds/umn/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +/*! Copyright (c) Huawei Technologies Co., Ltd. 2020-2022. All rights reserved. */.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/danger_3.0-en-us.png b/docs/rds/umn/public_sys-resources/danger_3.0-en-us.png new file mode 100644 index 000000000..47a9c7235 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/danger_3.0-en-us.png differ diff --git a/docs/rds/umn/public_sys-resources/delta.gif b/docs/rds/umn/public_sys-resources/delta.gif new file mode 100644 index 000000000..0d1b1f674 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/delta.gif differ diff --git a/docs/rds/umn/public_sys-resources/deltaend.gif b/docs/rds/umn/public_sys-resources/deltaend.gif new file mode 100644 index 000000000..cc7da0fc8 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/deltaend.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-arrowdn.gif b/docs/rds/umn/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 000000000..379428032 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-arrowrt.gif b/docs/rds/umn/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 000000000..6aaaa11c2 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-caution.gif b/docs/rds/umn/public_sys-resources/icon-caution.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-caution.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-danger.gif b/docs/rds/umn/public_sys-resources/icon-danger.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-danger.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-huawei.gif b/docs/rds/umn/public_sys-resources/icon-huawei.gif new file mode 100644 index 000000000..a31d60f89 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-huawei.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-note.gif b/docs/rds/umn/public_sys-resources/icon-note.gif new file mode 100644 index 000000000..31be2b039 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-note.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-notice.gif b/docs/rds/umn/public_sys-resources/icon-notice.gif new file mode 100644 index 000000000..409070650 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-notice.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-tip.gif b/docs/rds/umn/public_sys-resources/icon-tip.gif new file mode 100644 index 000000000..c47bae05c Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-tip.gif differ diff --git a/docs/rds/umn/public_sys-resources/icon-warning.gif b/docs/rds/umn/public_sys-resources/icon-warning.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/icon-warning.gif differ diff --git a/docs/rds/umn/public_sys-resources/note_3.0-en-us.png b/docs/rds/umn/public_sys-resources/note_3.0-en-us.png new file mode 100644 index 000000000..57a0e1f53 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/note_3.0-en-us.png differ diff --git a/docs/rds/umn/public_sys-resources/notice_3.0-en-us.png b/docs/rds/umn/public_sys-resources/notice_3.0-en-us.png new file mode 100644 index 000000000..fa4b64990 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/notice_3.0-en-us.png differ diff --git a/docs/rds/umn/public_sys-resources/popup.js b/docs/rds/umn/public_sys-resources/popup.js new file mode 100644 index 000000000..a550862ed --- /dev/null +++ b/docs/rds/umn/public_sys-resources/popup.js @@ -0,0 +1 @@ +var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/warning_3.0-en-us.png b/docs/rds/umn/public_sys-resources/warning_3.0-en-us.png new file mode 100644 index 000000000..def5c3565 Binary files /dev/null and b/docs/rds/umn/public_sys-resources/warning_3.0-en-us.png differ diff --git a/docs/rds/umn/rds_00_0011.html b/docs/rds/umn/rds_00_0011.html new file mode 100644 index 000000000..9e52af344 --- /dev/null +++ b/docs/rds/umn/rds_00_0011.html @@ -0,0 +1,120 @@ + + +

Function Comparison

+

Single DB instances use a single-node architecture. Different from the primary/standby DB instances, a single DB instance contains only one node and has no slave node for fault recovery.

+

Advantage Comparison

  • Single DB instances: support the creation of read replicas (except for Microsoft SQL Server) and support the queries of error logs and slow query logs. Different from primary/standby DB instances that have two database nodes, a single DB instance has only one node. If a node fails, the restoration will take a long time. Therefore, single DB instances are not recommended for sensitive services that have high requirements on database availability.
  • Primary/Standby DB instances: use the slave database node only for failover and restoration. The slave database node does not provide services. The performance of single DB instances is similar to or even higher than the primary/standby DB instances.
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Function comparisons

Function

+

Single

+

Primary/Standby

+

Number of nodes

+

1

+

2

+

Specifications

+

vCPUs: a maximum of 60

+

Memory: a maximum of 512 GB

+

Storage: a maximum of 4,000 GB

+

vCPUs: a maximum of 60

+

Memory: a maximum of 512 GB

+

Storage: a maximum of 4,000 GB

+

Monitoring and alarms

+

Supported

+

Supported

+

Security group

+

Supported

+

Supported

+

Backups and restorations

+

Supported

+

Supported

+

Recycle bin

+

Supported

+

Supported

+

Parameter settings

+

Supported

+

Supported

+

SSL

+

Supported

+

Supported

+

Log management

+

Supported

+

Supported

+

Read replicas (need to be created)

+

Supported

+

Supported

+

High-frequency monitoring

+

Supported

+

Supported

+

Primary/standby switchover or failover

+

Not supported

+

Supported

+

Standby DB instance migration

+

Not supported

+

Supported

+
+
+
+
+
+
Parent topic: Product Series
+
+
+ diff --git a/docs/rds/umn/rds_01_0000.html b/docs/rds/umn/rds_01_0000.html new file mode 100644 index 000000000..c9057a34f --- /dev/null +++ b/docs/rds/umn/rds_01_0000.html @@ -0,0 +1,29 @@ + + +

Introduction

+
+ + diff --git a/docs/rds/umn/rds_01_0001.html b/docs/rds/umn/rds_01_0001.html new file mode 100644 index 000000000..a051b9697 --- /dev/null +++ b/docs/rds/umn/rds_01_0001.html @@ -0,0 +1,21 @@ + + +

Advantages

+
+ + diff --git a/docs/rds/umn/rds_01_0002.html b/docs/rds/umn/rds_01_0002.html new file mode 100644 index 000000000..f8a5aba21 --- /dev/null +++ b/docs/rds/umn/rds_01_0002.html @@ -0,0 +1,18 @@ + + +

Easy Management

+

Quick Setup

You can create a DB instance on the management console within minutes and access RDS from an ECS to reduce the application response time and avoid paying for the traffic that would be generated by regular public access.

+
+

Elastic Scaling

Cloud Eye monitors changes in the load on your database and storage capacity. You can flexibly scale resources accordingly and pay for only what you use.

+
+

High Compatibility

You use RDS database engines (DB engines) the same way as you would use a native engine. RDS is compatible with existing programs and tools.

+
+

Easy O&M

Routine RDS maintenance and management operations, including hardware and software fault handling and database patch updates, are easy to perform. With the web-based console, you can reboot DB instances, reset passwords, modify parameters, view error or slow query logs, and restore data. Additionally, the system helps you monitor DB instances in real time and generates alarms if an error occurs. You can check DB instance information at any time, including CPU usage, IOPS, database connections, and storage space usage.

+
+
+
+
+
Parent topic: Advantages
+
+
+ diff --git a/docs/rds/umn/rds_01_0004.html b/docs/rds/umn/rds_01_0004.html new file mode 100644 index 000000000..fac4db6b0 --- /dev/null +++ b/docs/rds/umn/rds_01_0004.html @@ -0,0 +1,24 @@ + + +

High Security

+

Network Isolation

RDS uses Virtual Private Cloud (VPC) and network security groups to isolate and secure your DB instances. VPCs allow you to define what IP address range can access RDS. You can configure subnets and security groups to control access to DB instances.

+
+

Access Control

RDS controls access through the domain/IAM user and security groups. When you create an RDS DB instance, a domain is automatically created. To separate out specific permissions, you can create IAM users and assign permissions to them as needed. VPC security groups have rules that govern both inbound and outbound traffic for DB instances.

+
+

Transmission Encryption

RDS uses Transport Layer Security (TLS) and Secure Sockets Layer (SSL) to encrypt transmission. You can download a Certificate Agency (CA) certificate from the RDS console and upload it when connecting to a database for authentication.

+
+

Storage Encryption

RDS uses static encryption and tablespace encryption to encrypt the data to be stored. Encryption keys are managed by Key Management Service (KMS).

+
+

Data Deletion

When you delete an RDS DB instance, its attached disks, storage space its automated backups occupy, and all data it stores will be deleted. You can restore a deleted DB instance using a manual backup or rebuild the DB instance from the recycle bin within the retention period.

+
+

Anti-DDoS

When you connect to an RDS DB instance through a public network, there may be risks of a distributed denial-of-service (DDoS) attack. If the RDS security system detects a DDoS attack, it will enable the anti-DDoS function. If the function cannot defend against the attack or the attack reaches the black hole threshold, black hole processing is triggered to ensure availability of the RDS service.

+
+

Security Protection

RDS is protected by multiple layers of firewalls to defend against various malicious attacks, such as DDoS attacks and SQL injections. For security reasons, you are advised to access RDS through a private network.

+
+
+
+
+
Parent topic: Advantages
+
+
+ diff --git a/docs/rds/umn/rds_01_0005.html b/docs/rds/umn/rds_01_0005.html new file mode 100644 index 000000000..102d58773 --- /dev/null +++ b/docs/rds/umn/rds_01_0005.html @@ -0,0 +1,17 @@ + + +

High Reliability

+

Dual-Host Hot Standby

RDS uses the hot standby architecture, in which failover upon fault occurrence takes only some seconds.

+
+

Data Backup

RDS automatically backs up data every day and transfers backup files to Object Storage Service (OBS). The backup files can be stored for 732 days and can be restored with just a few clicks. You can set a custom backup policy and create manual backups at any time.

+
+

Data Restoration

You can restore data from backups to any point in time during the backup retention period. In most scenarios, you can use backup files to restore data to a new DB instance at any time point within 732 days. After the data is verified, data can be migrated back to the primary DB instance.

+

Deleted DB instances can be moved to the recycle bin. You can rebuild the DB instance that was deleted up to 7 days ago from the recycle bin.

+
+
+
+
+
Parent topic: Advantages
+
+
+ diff --git a/docs/rds/umn/rds_01_0006.html b/docs/rds/umn/rds_01_0006.html new file mode 100644 index 000000000..6b3ce8c4b --- /dev/null +++ b/docs/rds/umn/rds_01_0006.html @@ -0,0 +1,86 @@ + + +

Comparison Between RDS and Self-Built Databases

+

Performance

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item

+

Cloud Database RDS

+

Self-Built Database Service

+

Service availability

+

For details, see the Elastic Cloud Service User Guide.

+

Requires device procurement, primary/standby relationship setup, and RAID setup.

+

Data reliability

+

For more information, see the Elastic Volume Service User Guide.

+

Requires device procurement, primary/standby relationship setup, and RAID setup.

+

System security

+

Defends against Anti-DDoS attacks and promptly repairs database security vulnerabilities.

+

Requires procurement of expensive devices and software, as well as manual detection and repair of security vulnerabilities.

+

Database backup

+

Supports automated backups, manual backups, and custom backup retention periods.

+

Requires device procurement, setup, and maintenance.

+

Hardware and software investment

+

Supports on-demand pricing and scaling without requiring hardware and software investment.

+

Requires large investment in database servers. The Microsoft SQL Server license must be paid for separately.

+

System hosting

+

Not required.

+

Requires two servers for primary/standby DB instances.

+

Maintenance cost

+

Not required.

+

Requires large manpower investment and professional database administrator (DBA) for maintenance.

+

Deployment and scaling

+

Supports elastic scaling, fast upgrade, and on-demand enabling.

+

Requires procurement, deployment, and coordination of hardware that matches original devices.

+

Resource utilization

+

Bills users based on the resources actually used, resulting in 100% resource utilization.

+

Considers peak traffic, resulting in low resource utilization.

+
+
+
+
+
+
+
Parent topic: Advantages
+
+
+ diff --git a/docs/rds/umn/rds_01_0009.html b/docs/rds/umn/rds_01_0009.html new file mode 100644 index 000000000..d94880512 --- /dev/null +++ b/docs/rds/umn/rds_01_0009.html @@ -0,0 +1,17 @@ + + +

Product Series

+
+ + diff --git a/docs/rds/umn/rds_01_0010.html b/docs/rds/umn/rds_01_0010.html new file mode 100644 index 000000000..891b96861 --- /dev/null +++ b/docs/rds/umn/rds_01_0010.html @@ -0,0 +1,40 @@ + + +

DB Instance Introduction

+
Currently, RDS DB instances are classified into the following types:
  • Single
  • Primary/Standby
+
+

Different series support different DB engines and instance specifications.

+ +
+ + + + + + + + + + + + + +
Table 1 DB instance types

DB Instance Type

+

Description

+

Scenarios

+

Single

+

Uses a single-node architecture. More cost-effective than the mainstream primary/standby DB instances.

+
  • Personal learning
  • Microsites
  • Development and testing environment of small- and medium-sized enterprises
+

Primary/Standby

+

Uses an HA architecture with one master node and one slave node.

+

The primary and standby DB instances share the same IP address and can be deployed in different AZs.

+
  • Production databases of large- and medium-sized enterprises
  • Applications for the Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other industries
+
+
+
+
+
+
Parent topic: Product Series
+
+
+ diff --git a/docs/rds/umn/rds_01_0012.html b/docs/rds/umn/rds_01_0012.html new file mode 100644 index 000000000..cc1361ec5 --- /dev/null +++ b/docs/rds/umn/rds_01_0012.html @@ -0,0 +1,13 @@ + + +

Read/Write Splitting

+

RDS for MySQL, RDS for PostgreSQL, and RDS for SQL Server 2017 Enterprise Edition DB instances support read replicas to offload read traffic from primary DB instances.

+

For RDS for MySQL and RDS for PostgreSQL, the primary DB instances and read replicas have independent connection addresses. A maximum of five read replicas can be created for each RDS for MySQL or RDS for PostgreSQL DB instance. For details about how to create a read replica, see Creating a Read Replica (RDS for MySQL) and Creating a Read Replica (RDS for PostgreSQL).

+

To offload read pressure on the primary DB instance, you can create one or more read replicas in the same region as the primary instance. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses for the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.

+
+
+
+
Parent topic: Typical Applications
+
+
+ diff --git a/docs/rds/umn/rds_01_0013.html b/docs/rds/umn/rds_01_0013.html new file mode 100644 index 000000000..f3775404b --- /dev/null +++ b/docs/rds/umn/rds_01_0013.html @@ -0,0 +1,12 @@ + + +

Diversified Data Storage

+

RDS supports diverse storage extension through Distributed Cache Service (DCS) for Memcached, DCS for Redis, and OBS.

+
Figure 1 Diversified data storage
+
+
+
+
Parent topic: Typical Applications
+
+
+ diff --git a/docs/rds/umn/rds_01_0015.html b/docs/rds/umn/rds_01_0015.html new file mode 100644 index 000000000..7d31b9516 --- /dev/null +++ b/docs/rds/umn/rds_01_0015.html @@ -0,0 +1,33 @@ + + +

Basic Concepts

+

DB Instances

The smallest management unit of RDS is the DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance runs a DB engine. For details about DB instance types, specifications, engines, versions, and statuses, see DB Instance Description.

+
+

DB Engines

RDS supports the following DB engines:

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

For details about the supported versions, see DB Engines and Versions.

+
+

DB Instance Types

RDS DB instances are classified into the following types: single and primary/standby.

+

For details about DB instance types, see DB Instance Introduction and Function Comparison.

+
+

DB Instance Classes

The DB instance class determines the compute (vCPUs) and memory capacity (memory size) of a DB instance. For details, see DB Instance Classes.

+
+

Automated Backups

When you create a DB instance, an automated backup policy is enabled by default. After the DB instance is created, you can modify the policy. RDS will automatically create full backups for DB instances based on your settings.

+
+

Manual Backups

Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually.

+
+

Regions and AZs

A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

+
  • Regions are defined in terms of their geographical location and network latency. Each region is completely independent, improving fault tolerance and stability. After a resource is created, its region cannot be changed.
  • An AZ is a physical location using independent power supplies and networks. Faults in an AZ do not affect other AZs. A region can contain multiple AZs, which are physically isolated but interconnected through internal networks. This ensures the independence of AZs and provides low-cost and low-latency network connections.
+ +

Figure 1 shows the relationship between regions and AZs.

+
Figure 1 Regions and AZs
+
+

Projects

Projects are used to group and isolate OpenStack resources (compute, storage, and network resources). A project can be a department or a project team. Multiple projects can be created for a single account.

+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/rds/umn/rds_01_0016.html b/docs/rds/umn/rds_01_0016.html new file mode 100644 index 000000000..ad5e36070 --- /dev/null +++ b/docs/rds/umn/rds_01_0016.html @@ -0,0 +1,40 @@ + + +

DB Instance Types

+

The smallest management unit of RDS is the DB instance. A DB instance is an isolated database environment on the cloud. Each DB instance can contain multiple user-created databases, and you can access a DB instance using the same tools and applications that you use with a stand-alone DB instance. You can create and modify DB instances using the management console or APIs. RDS does not have limits on the number of running DB instances. Each DB instance has a DB instance identifier.

+

DB instances are classified into the following types.

+ +
+ + + + + + + + + + + + + +
Table 1 DB instance types

DB Instance Type

+

Description

+

Single

+

Uses a single-node architecture. More cost-effective than primary/standby DB instances.

+

Primary/Standby

+

Uses an HA architecture with one master node and one slave node. The instance classes of the nodes are the same.

+

Read replica

+

Uses a single-node architecture (without a standby node).

+
+
+

For RDS for SQL Server, only 2017 EE supports read replicas.

+

You can use RDS to create and manage DB instances running various DB engines.

+

For details about differences and function comparison between different instance types, see DB Instance Introduction and Function Comparison.

+
+
+
+
Parent topic: DB Instance Description
+
+
+ diff --git a/docs/rds/umn/rds_01_0018.html b/docs/rds/umn/rds_01_0018.html new file mode 100644 index 000000000..0e6815fbd --- /dev/null +++ b/docs/rds/umn/rds_01_0018.html @@ -0,0 +1,510 @@ + + +

Function Differences of RDS for SQL Server Instances Types and Editions

+

This section describes function differences between single and primary/standby DB instances as well as function differences among Microsoft SQL Server editions.

+
  • For details about differences of basic functions, see Table 1.
  • For details about differences of DB instance types, see Table 1.
  • For details about differences of database migration functions, see Table 2.
  • For details about differences of database security functions, see Table 3.
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Differences of basic functions

Module

+

Function Item

+

Primary/Standby

+

Single

+

Cluster

+

Life cycle

+

Create a DB instance

+

Supported

+

Supported

+

Supported

+

Reboot a DB instance

+

Supported

+

Supported

+

Supported

+

Auto-renewal

+

Supported

+

Supported

+

Supported

+

Change the instance class

+

Supported

+

Supported

+

Supported

+

Delete a DB instance

+

Supported

+

Supported

+

Supported

+

Upgrade the DB engine version

+

Not supported

+

Not supported

+

Not supported

+

Restore to a new DB instance

+

Supported

+

Supported

+

Supported

+

Create a read replica

+

Not supported

+

Not supported

+

Supported

+

Recycle bin

+

Supported

+

Supported

+

Supported

+

DB instance properties

+

View the DB instance list

+

Supported

+

Supported

+

Supported

+

View DB instance details

+

Supported

+

Supported

+

Supported

+

Modify the DB instance description

+

Supported

+

Supported

+

Supported

+

Change the maintenance window

+

Supported

+

Supported

+

Supported

+

Manage tags

+

Supported

+

Supported

+

Supported

+

Database connection

+

Internal access through a VPC

+

Supported

+

Supported

+

Supported

+

Public accessibility

+

Supported

+

Supported

+

Supported

+

Read/write splitting

+

Not supported

+

Not supported

+

Not supported

+

Backups and restorations

+

Full backup

+

Supported

+

Supported

+

Supported

+

Log backup

+

Supported

+

Supported

+

Supported

+

Customize a backup policy

+

Supported

+

Supported

+

Supported

+

Restore from automated backups

+

Supported

+

Supported

+

Supported

+

Point-in-time restore

+

Supported

+

Supported

+

Supported

+

Partial backup

+

Supported

+

Supported

+

Supported

+

Partial restore

+

Supported

+

Supported

+

Supported

+

Monitoring and alarms

+

Resource monitoring

+

Supported

+

Supported

+

Supported

+

DB engine monitoring

+

Not supported

+

Not supported

+

Not supported

+

Customize monitoring policies

+

Supported

+

Supported

+

Supported

+

Aggregate monitoring items

+

Supported

+

Supported

+

Supported

+

Parameter management

+

Parameter update

+

Supported

+

Supported

+

Supported

+

Parameter template

+

Supported

+

Supported

+

Supported

+

Log management

+

Error logs

+

Supported

+

Supported

+

Supported

+

System running logs

+

Supported

+

Supported

+

Supported

+
+
+ +
+ + + + + + + + + + + + + + + + + +
Table 2 Differences of database migration

Function Item

+

Primary/Standby

+

Single

+

Homogeneous data migration

+

Supported

+

Supported

+

Heterogeneous data migration

+

Not supported

+

Not supported

+

Data synchronization

+

Supported

+

Supported

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 Differences of database security

Function Item

+

Primary/Standby

+

Single

+

IP address whitelist

+

Not supported

+

Not supported

+

Management audit

+

Supported

+

Supported

+

Storage encryption

+

Supported

+

Supported

+

Network encryption

+

Supported

+

Supported

+

Security group management

+

Supported

+

Supported

+

Transparent Data Encryption (TDE) encryption

+

Supported (Enterprise Edition)

+

Supported (Enterprise Edition)

+
+
+

Table 4 lists the major differences of the official Microsoft SQL Server editions.

+

For more information about function differences among Microsoft SQL Server 2016 official editions, see official documents.

+

For more information about function differences among Microsoft SQL Server 2017 official editions, see official documents.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 Differences of Microsoft SQL Server editions

Function Item

+

Standard Edition

+

Enterprise Edition

+

High availability

+

Mirror HA

+

Mirror HA

+ +

Data compression

+

Supported

+

Supported

+

SQL Profiler

+

Supported

+

Supported

+

Column index

+

Supported

+

Supported

+

Table/index partitioning

+

Supported only by Microsoft SQL Server 2014.

+

Supported

+

Change Data Capture (CDC)

+

Not supported

+

Supported

+

Online DDL

+

Not supported

+

Supported

+

Parallel searches

+

Not supported

+

Supported

+

Adjustment of partitioned table parallelism

+

Not supported

+

Supported

+

TDE

+

Not supported

+

Supported

+

Advanced R integration

+

Not supported

+

Supported

+
+
+
+
+
+
Parent topic: DB Engine
+
+
+ diff --git a/docs/rds/umn/rds_01_0023.html b/docs/rds/umn/rds_01_0023.html new file mode 100644 index 000000000..3eae3a702 --- /dev/null +++ b/docs/rds/umn/rds_01_0023.html @@ -0,0 +1,102 @@ + + +

DB Instance Statuses

+

DB Instance Statuses

The status of a DB instance indicates the health of the DB instance. You can use the management console or API to view the status of a DB instance.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 DB instance statuses

Status

+

Description

+

Available

+

A DB instance is available.

+

Abnormal

+

A DB instance is abnormal.

+

Creating

+

A DB instance is being created.

+

Creation failed

+

A DB instance has failed to be created.

+

Switchover in progress

+

A standby DB instance is being switched over to the primary DB instance.

+

Changing type to primary/standby

+

A single DB instance is being changed to primary/standby DB instances.

+

Rebooting

+

A DB instance is being rebooted.

+

Changing port

+

A DB instance port is being changed.

+

Changing instance class

+

The CPU or memory of a DB instance is being modified.

+

Scaling up

+

Storage space of a DB instance is being scaled up.

+

Backing up

+

A DB instance is being backed up.

+

Restoring

+

A DB instance is in the process of being restored from a backup.

+

Restore failed

+

A DB instance fails to be restored.

+

Storage full

+

Storage space of a DB instance is full. Data cannot be written to databases.

+

Deleted

+

A DB instance has been deleted and will not be displayed in the instance list.

+

Parameter change. Pending reboot

+

A modification to a database parameter is waiting for an instance reboot before it can take effect.

+
+
+
+
+
+
+
Parent topic: DB Instance Description
+
+
+ diff --git a/docs/rds/umn/rds_01_0024.html b/docs/rds/umn/rds_01_0024.html new file mode 100644 index 000000000..e6b23802c --- /dev/null +++ b/docs/rds/umn/rds_01_0024.html @@ -0,0 +1,17 @@ + + +

Typical Applications

+
+ + diff --git a/docs/rds/umn/rds_01_0025.html b/docs/rds/umn/rds_01_0025.html new file mode 100644 index 000000000..fc44842ad --- /dev/null +++ b/docs/rds/umn/rds_01_0025.html @@ -0,0 +1,14 @@ + + +

User Permissions

+

RDS provides two types of user permissions by default: user management and resource management.

+
  • User management permissions cover the management of users, user groups, and user group permissions.
  • Resource management permissions cover the management of controlling operations on cloud service resources.
+

User management allows you to create, delete, and modify users, and allows you to grant permissions to users. Resource management refers to the management of operation permissions such as creating, deleting, modifying, and setting cloud resources. After resources and users are added to a user group, the users can inherit permissions assigned to their user group. User permissions management based on user groups is more organized and helps avoid confusions.

+

For details, see Permissions.

+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/rds/umn/rds_01_0026.html b/docs/rds/umn/rds_01_0026.html new file mode 100644 index 000000000..585cc9a19 --- /dev/null +++ b/docs/rds/umn/rds_01_0026.html @@ -0,0 +1,19 @@ + + +

Constraints

+
+ + diff --git a/docs/rds/umn/rds_01_0027.html b/docs/rds/umn/rds_01_0027.html new file mode 100644 index 000000000..ec2564f5f --- /dev/null +++ b/docs/rds/umn/rds_01_0027.html @@ -0,0 +1,45 @@ + + +

Related Services

+
+
+ + + + + + + + + + + + + + + + + + + +
Table 1 Related services

Service Name

+

Description

+

Elastic Cloud Service (ECS)

+

Enables you to access RDS DB instances through an internal network. You can then access applications faster and you do not need to pay for public network traffic.

+

Virtual Private Cloud (VPC)

+

Isolates your networks and controls access to your RDS DB instances.

+

Object Storage Service (OBS)

+

Stores automated and manual backups of your RDS DB instances.

+

Cloud Eye

+

Monitors RDS resources in real time and reports alarms and warnings promptly.

+

Cloud Trace Service (CTS)

+

Records operations on cloud service resources for query, audit, and backtrack.

+
+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/rds/umn/rds_01_0028.html b/docs/rds/umn/rds_01_0028.html new file mode 100644 index 000000000..fd8f90eb5 --- /dev/null +++ b/docs/rds/umn/rds_01_0028.html @@ -0,0 +1,21 @@ + + +

DB Instance Description

+
+ + diff --git a/docs/rds/umn/rds_01_0029.html b/docs/rds/umn/rds_01_0029.html new file mode 100644 index 000000000..491661659 --- /dev/null +++ b/docs/rds/umn/rds_01_0029.html @@ -0,0 +1,168 @@ + + +

DB Instance Classes

+
General-enhanced and general-enhanced II instance classes provide robust and stable performance. They use latest-generation network acceleration engines and Data Plane Development Kit (DPDK) to provide higher network performance, meeting requirements in different scenarios.
  • General-enhanced DB instances use Intel® Xeon® Scalable processors and feature high and stable computing performance. Working in high-performance networks, general-enhanced DB instances provide higher performance and stability, meeting enterprise-class application requirements.
  • General-enhanced II DB instances use second-generation Intel® Xeon® Scalable processors with technologies optimized and 25GE high-speed intelligent NICs to offer powerful and stable computing performance, including ultra-high network bandwidth and PPS.
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 DB instance classes

Instance Class

+

vCPUs

+

Memory (GB)

+

Supported DB Engine

+

General-enhanced

+

1

+

2

+
  • MySQL
  • PostgreSQL
+

1

+

4

+
  • MySQL
  • PostgreSQL
+

2

+

4

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

2

+

8

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

2

+

16

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

4

+

8

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

4

+

16

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

4

+

32

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

8

+

16

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

8

+

32

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

8

+

64

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

16

+

32

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

16

+

64

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

16

+

128

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

32

+

64

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

32

+

128

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

32

+

256

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

60

+

128

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

60

+

256

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+

60

+

512

+
  • MySQL
  • PostgreSQL
  • Microsoft SQL Server
+
+
+
+
+
+
Parent topic: DB Instance Description
+
+
+ diff --git a/docs/rds/umn/rds_01_0031.html b/docs/rds/umn/rds_01_0031.html new file mode 100644 index 000000000..9033b541d --- /dev/null +++ b/docs/rds/umn/rds_01_0031.html @@ -0,0 +1,16 @@ + + +

DB Engine

+

+
+ + diff --git a/docs/rds/umn/rds_02_0001.html b/docs/rds/umn/rds_02_0001.html new file mode 100644 index 000000000..66a2d65ba --- /dev/null +++ b/docs/rds/umn/rds_02_0001.html @@ -0,0 +1,34 @@ + + +

Operation Guide

+

You can create and connect to DB instances on the RDS console.

+

Flowchart

Figure 1 Flowchart
+
+

Procedure

+
+ + + + + + + + + + +
Table 1 Related operations and references

Operation

+

Reference

+

Creating an RDS DB instance

+

Step 1: Create a DB Instance

+

Connecting to an RDS DB Instance

+

Step 2: Connect to a DB Instance

+
+
+
+
+ + diff --git a/docs/rds/umn/rds_02_0002.html b/docs/rds/umn/rds_02_0002.html new file mode 100644 index 000000000..8c95d5d1b --- /dev/null +++ b/docs/rds/umn/rds_02_0002.html @@ -0,0 +1,73 @@ + + +

MySQL Constraints

+

Table 1 shows the constraints designed to ensure the stability and security of RDS for MySQL.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Function constraints

Function Item

+

Constraints

+

Database access

+
  • If public accessibility is not enabled, the RDS DB instance must be in the same VPC as the ECS.
  • RDS read replicas must be created in the same subnet as the primary DB instance.
  • The security group must allow access from the ECS.

    By default, RDS cannot be accessed through an ECS in a different security group. You need to add an inbound rule to the RDS security group.

    +
  • The default MySQL port is 3306. You can change it if you want to access MySQL through another port.
+

Deployment

+

ECSs in which DB instances are deployed are not visible to users. You can access the DB instances only through an IP address and a port number.

+

Database root permissions

+

Only the root user permissions are provided on the instance creation page.

+

Database parameter modification

+

Most parameters can be modified on the RDS console.

+

Data migration

+

Use MySQL CLI tools to migrate data by referring to Migrating Data to RDS for MySQL Using mysqldump.

+

MySQL storage engine

+

For details, see What Storage Engines Does the RDS for MySQL Support?

+

Database replication setup

+

RDS for MySQL uses a primary/standby dual-node replication cluster. You do not need to set up replication additionally. The standby DB instance is not visible to users and therefore you cannot access it directly.

+

Minor version upgrade

+

Currently, RDS for MySQL supports a maximum of 100,000 tables. If the number of tables is greater than 100,000, the minor version upgrade may fail.

+

DB instance reboot

+

RDS DB instances cannot be rebooted through commands. They must be rebooted through the RDS console.

+

RDS backup files

+

For details, see Downloading a Backup File.

+

You can rebuild a DB instance from the recycle bin to restore data.

+
+
+
+
+
+
Parent topic: Constraints
+
+
+ diff --git a/docs/rds/umn/rds_02_0003.html b/docs/rds/umn/rds_02_0003.html new file mode 100644 index 000000000..200fe9d20 --- /dev/null +++ b/docs/rds/umn/rds_02_0003.html @@ -0,0 +1,21 @@ + + +

Configuring Security Group Rules

+

Scenarios

A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a VPC.

+

This section describes how to create a security group to enable specific IP addresses and ports to access RDS.

+

When you attempt to connect to an RDS DB instance through an EIP, you need to configure an inbound rule for the security group associated with the DB instance.

+
+

Precautions

The default security group rule allows all outgoing data packets. ECSs and RDS DB instances can access each other if they are deployed in the same security group. After a security group is created, you can configure security group rules to control access from and to the DB instances in the security group.

+
  • By default, you can create a maximum of 500 security group rules.
  • One security group can be associated with only one RDS DB instance.
  • Too many security group rules will increase the first packet latency. You are advised to create no more than 50 rules for each security group.
  • To enable access to an RDS DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the RDS DB instance.
+

If you use 0.0.0.0/0, RDS DB instances in the security group can be accessed from any IP address.

+
+
+

Procedure

  1. Log in to the management console.
  2. Under Network, click Virtual Private Cloud.
  3. In the navigation pane on the left, choose Access Control > Security Groups.
  4. On the Security Groups page, locate the target security group and click Manage Rule in the Operation column.
  5. On the displayed page, click Add Rule.
  6. In the displayed dialog box, set required parameters to add an inbound rule.
  7. Click OK.
+
+
+ + diff --git a/docs/rds/umn/rds_02_0004.html b/docs/rds/umn/rds_02_0004.html new file mode 100644 index 000000000..07847ba59 --- /dev/null +++ b/docs/rds/umn/rds_02_0004.html @@ -0,0 +1,23 @@ + + +

Configuring Security Group Rules

+

Scenarios

A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a VPC.

+

This section describes how to create a security group to enable specific IP addresses and ports to access RDS.

+

First check whether the ECS and RDS DB instance are in the same security group.

+
  • If the ECS and RDS 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 Connecting to a DB Instance Through a Private Network.
  • If the ECS and RDS DB instance are in different security groups, you need to configure security group rules for them, separately.
    • RDS DB instance: Configure an inbound rule for the security group with which the RDS DB instance is associated.
    • ECS: The default security group rule allows all outgoing data packets. In this case, 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. ECSs and RDS DB instances can access each other if they are deployed in the same security group. After a security group is created, you can configure security group rules to control access from and to the DB instances in the security group.

+
  • By default, a tenant can create a maximum of 100 security groups.
  • By default, each security group can have a maximum of 50 security group rules.
  • One RDS instance can be associated only with one security group, but a security group can be associated with multiple RDS instances.
  • Too many security group rules will increase the first packet latency. You are advised to create no more than 50 rules for each security group.
  • To enable access to an RDS DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the RDS DB instance.
+

If you use 0.0.0.0/0, RDS DB instances in the security group can be accessed from any IP address.

+
+
+

Procedure

  1. Log in to the management console.
  2. Under Network, click Virtual Private Cloud.
  3. In the navigation pane on the left, choose Access Control > Security Groups.
  4. On the Security Groups page, locate the target security group and click Manage Rule in the Operation column.
  5. On the displayed page, click Add Rule.
  6. In the displayed dialog box, set required parameters to add an inbound rule.
  7. Click OK.
+
+
+ + diff --git a/docs/rds/umn/rds_02_0006.html b/docs/rds/umn/rds_02_0006.html new file mode 100644 index 000000000..2c5814f38 --- /dev/null +++ b/docs/rds/umn/rds_02_0006.html @@ -0,0 +1,20 @@ + + +

Step 2: Connect to a DB Instance

+

+
+ + diff --git a/docs/rds/umn/rds_02_0008.html b/docs/rds/umn/rds_02_0008.html new file mode 100644 index 000000000..05c491d49 --- /dev/null +++ b/docs/rds/umn/rds_02_0008.html @@ -0,0 +1,223 @@ + + +

Step 1: Create a DB Instance

+

Scenarios

This section describes how to create a DB instance on the management console.

+

The DB instance class and storage space you need depend on your processing power and memory requirements.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click Create DB Instance.
  5. On the displayed page, configure information about your DB instance. Then, click Create Now.

    +
    + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    The region where your RDS resources will be located. You can change it on the creation page, or go back to the Instances page and change it in the upper left corner.

    +
    NOTE:

    Products in different regions cannot communicate with each other through a private network. After a DB instance is created, the region cannot be changed. Therefore, exercise caution when selecting a region.

    +
    +

    DB Instance Name

    +

    Must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

    +

    DB Engine

    +

    Set to MySQL.

    +

    DB Engine Version

    +

    +

    +

    For details, see DB Engines and Versions.

    +

    Different DB engine versions are supported in different regions.

    +

    You are advised to select the latest available version because it is more stable, reliable, and secure.

    +

    DB Instance Type

    +
    • Primary/Standby: uses an HA architecture with a primary DB instance and a synchronous standby DB instance. It is suitable for production databases of large- and medium-sized enterprises in Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other sectors. The standby DB instance improves instance reliability and is invisible to you after being created.

      An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

      +

      You can deploy primary and standby DB instances in a single AZ or across AZs to achieve failover and high availability.

      +
    • Single: uses a single-node architecture, which is more cost-effective than primary/standby DB instances. It is suitable for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.
    +

    Time Zone

    +

    Select a time zone when you are creating a DB instance, and you can change it after the DB instance is created.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Instance specifications

    Parameter

    +

    Description

    +

    Instance Class

    +

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and different maximum IOPS.

    +

    +

    +

    For details about instance classes, see section DB Instance Classes.

    +

    After a DB instance is created, you can change its instance class. For details, see section Changing a DB Instance Class.

    +

    Storage Type

    +

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    +
    • Common I/O: uses the SATA disk type, with a maximum throughput of 90 MB/s.
    • Ultra-high I/O: uses the SSD disk type that supports a maximum throughput of 350 MB/s.
    +

    Storage Space (GB)

    +

    Contains the file system overhead required for inode, reserved block, and database operation.

    +

    +

    +

    After a DB instance is created, you can scale up its storage space. For details, see section Scaling up Storage Space.

    +
    NOTE:
    • Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.
    +
    +

    Disk Encryption

    +
    • Disable: indicates the encryption function is disabled.
    • Enable: indicates the encryption function is enabled, improving data security but affecting system performance.

      Key Name: indicates the tenant key. You can create or select a key.

      +
      NOTE:
      • Once the instance is created, you cannot modify the disk encryption status or change the key. The backup data stored in OBS is encrypted.
      • After an RDS DB instance is created, do not disable or delete the key that is being used. Otherwise, database will be unavailable.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      +
    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    A dedicated virtual network in which your RDS DB instances are located. A VPC can isolate networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.

    +

    If no VPC is available, RDS allocates a VPC to you by default.

    +
    NOTICE:

    After the DB instance is created, the VPC cannot be changed.

    +
    +

    Subnet

    +

    Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function is enabled by default for subnets in which you plan to create RDS DB instances and cannot be disabled.

    +

    A floating IP address is automatically assigned when you create a DB instance. You can also enter an unused floating IP address in the subnet CIDR block. After the DB instance is created, you can change the floating IP address.

    +

    Security Group

    +

    Enhances security by controlling access to RDS from other services. You need to add inbound rules to a security group so that you can connect to your DB instance.

    +

    If no security group is available or has been created, RDS allocates a security group to you by default.

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + +
    Table 4 Database configuration

    Parameter

    +

    Description

    +

    Administrator

    +

    The default login name for the database is root.

    +

    Administrator Password

    +

    Must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_=+?). Enter a strong password and periodically change it for security reasons.

    +

    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.

    +

    Keep this password secure. The system cannot retrieve it.

    +

    +

    After a DB instance is created, you can reset this password. For details, see section Resetting the Administrator Password.

    +

    Confirm Password

    +

    Must be the same as Administrator Password.

    +

    Parameter Template

    +

    Contains engine configuration values that can be applied to one or more DB instances. If you intend to create primary/standby DB instances, they use the same parameter template.

    +
    NOTICE:

    If you use a custom parameter template when creating a DB instance, the following specification-related parameters in the custom template are not delivered. Instead, the default values are used.

    +
    • back_log
    • innodb_io_capacity_max
    • max_connections
    • innodb_io_capacity
    • innodb_buffer_pool_size
    • innodb_buffer_pool_instances
    +
    +

    +

    +

    You can modify the instance parameters as required after the DB instance is created. For details, see section Modifying Parameters.

    +

    Table Name

    +

    Specifies whether table names are case sensitive.

    +

    The case sensitivity of table names for created RDS for MySQL 8.0 instances cannot be changed.

    +
    +
    + +
    + + + + + + + +
    Table 5 Tags

    Parameter

    +

    Description

    +

    Tag

    +

    Tags an RDS DB instance. This configuration is optional. Adding tags to RDS DB instances helps you better identify and manage the DB instances. A maximum of 20 tags can be added for each DB instance.

    +

    After a DB instance is created, you can click it and view its details on the Tags page. For details, see section Managing Tags.

    +
    +
    + +
    + + + + + + + +
    Table 6 Batch creation

    Parameter

    +

    Description

    +

    Quantity

    +

    RDS supports DB instance creation in batches. If you choose to create primary/standby DB instances and set Quantity to 1, a primary DB instance and a standby DB instance will be created synchronously.

    +

    If you create multiple DB instances at a time, they will be named with four digits appended to the DB instance name. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on.

    +
    +
    +
    +

    After the configuration, click Price Calculator to view the RDS configuration fee.

    +

    The performance of your DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.

    +
    +

  6. Confirm the specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. To view and manage the DB instance, go to the Instances page.

    • During the creation process, the DB instance status is Creating. When the creation process is complete, the instance status will change to Available. You can view the detailed progress and result of the task on the Task Center page.
    • The automated backup policy is enabled by default. After the DB instance is created, you can modify the automated backup policy. An automated full backup is immediately triggered after a DB instance is created.
    • The default database port is 3306. After a DB instance is created, you can change its port.

      +

      +

      For details, see section Changing a Database Port.

      +
    +

+
+
+ + diff --git a/docs/rds/umn/rds_02_0009.html b/docs/rds/umn/rds_02_0009.html new file mode 100644 index 000000000..7da87c649 --- /dev/null +++ b/docs/rds/umn/rds_02_0009.html @@ -0,0 +1,21 @@ + + +

Configuring Security Group Rules

+

Scenarios

A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a VPC.

+

This section describes how to create a security group to enable specific IP addresses and ports to access RDS.

+

When you attempt to connect to an RDS DB instance through an EIP, you need to configure an inbound rule for the security group associated with the DB instance.

+
+

Precautions

The default security group rule allows all outgoing data packets. ECSs and RDS DB instances can access each other if they are deployed in the same security group. After a security group is created, you can configure security group rules to control access from and to the DB instances in the security group.

+
  • By default, a tenant can create a maximum of 100 security groups.
  • By default, each security group can have a maximum of 50 security group rules.
  • One RDS instance can be associated only with one security group, but a security group can be associated with multiple RDS instances.
  • Too many security group rules will increase the first packet latency. You are advised to create no more than 50 rules for each security group.
  • To enable access to an RDS DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the RDS DB instance.
+

If you use 0.0.0.0/0, RDS DB instances in the security group can be accessed from any IP address.

+
+
+

Procedure

  1. Log in to the management console.
  2. Under Network, click Virtual Private Cloud.
  3. In the navigation pane on the left, choose Access Control > Security Groups.
  4. On the Security Groups page, locate the target security group and click Manage Rule in the Operation column.
  5. On the displayed page, click Add Rule.
  6. In the displayed dialog box, set required parameters to add an inbound rule.
  7. Click OK.
+
+
+ + diff --git a/docs/rds/umn/rds_02_0010.html b/docs/rds/umn/rds_02_0010.html new file mode 100644 index 000000000..70aa00ec0 --- /dev/null +++ b/docs/rds/umn/rds_02_0010.html @@ -0,0 +1,13 @@ + + +

Overview

+

Process

Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a private network.

+
Figure 1 Connecting to a DB instance through a private network
+
+
+ + diff --git a/docs/rds/umn/rds_02_0012.html b/docs/rds/umn/rds_02_0012.html new file mode 100644 index 000000000..972215a78 --- /dev/null +++ b/docs/rds/umn/rds_02_0012.html @@ -0,0 +1,67 @@ + + +

PostgreSQL Constraints

+

Table 1 shows the constraints designed to ensure the stability and security of RDS for PostgreSQL.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Function constraints

Function Item

+

Constraints

+

Database access

+
  • If public accessibility is not enabled, the RDS DB instance must be in the same VPC as the ECS.
  • RDS read replicas must be created in the same subnet as the primary DB instance.
+
  • The security group must allow access from the ECS.

    By default, RDS cannot be accessed through an ECS in a different security group. You need to add an inbound rule to the RDS security group.

    +
  • The default RDS port is 5432. You can change it if you want to access RDS through another port.
+

Deployment

+

ECSs in which DB instances are deployed are not visible to users. You can access the DB instances only through an IP address and a port number.

+

Database root permissions

+

Only the root user permissions are provided on the instance creation page.

+
NOTE:

The root user has the following permissions: Create role, Create DB, and Replication.

+

+
+

Database parameter modification

+

Most parameters can be modified on the RDS console.

+

Data migration

+

Use psql to import data by referring to Migrating Data to RDS for PostgreSQL Using psql.

+

Database replication setup

+

RDS for PostgreSQL uses a primary/standby dual-node replication cluster. You do not need to set up replication additionally. The standby DB instance is not visible to users and therefore you cannot access it directly.

+

DB instance reboot

+

DB instances cannot be rebooted through commands. They must be rebooted through the RDS console.

+

RDS backup files

+

For details, see Downloading a Full Backup File.

+

You can rebuild a DB instance from the recycle bin to restore data.

+
+
+
+
+
+
Parent topic: Constraints
+
+
+ diff --git a/docs/rds/umn/rds_02_0013.html b/docs/rds/umn/rds_02_0013.html new file mode 100644 index 000000000..fee5e4636 --- /dev/null +++ b/docs/rds/umn/rds_02_0013.html @@ -0,0 +1,19 @@ + + +

Connecting to a PostgreSQL DB Instance Through a Private Network

+
+ + diff --git a/docs/rds/umn/rds_02_0014.html b/docs/rds/umn/rds_02_0014.html new file mode 100644 index 000000000..74719aa03 --- /dev/null +++ b/docs/rds/umn/rds_02_0014.html @@ -0,0 +1,23 @@ + + +

Configuring Security Group Rules

+

Scenarios

A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a VPC.

+

This section describes how to create a security group to enable specific IP addresses and ports to access RDS.

+

First check whether the ECS and RDS DB instance are in the same security group.

+
  • If the ECS and RDS 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 Connecting to a DB Instance Through psql.
  • If the ECS and RDS DB instance are in different security groups, you need to configure security group rules for them, separately.
    • RDS DB instance: Configure an inbound rule for the security group with which the RDS DB instance is associated.
    • ECS: The default security group rule allows all outgoing data packets. In this case, 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. ECSs and RDS DB instances can access each other if they are deployed in the same security group. After a security group is created, you can configure security group rules to control access from and to the DB instances in the security group.

+
  • By default, a tenant can create a maximum of 100 security groups.
  • By default, each security group can have a maximum of 50 security group rules.
  • One security group can be associated with only one RDS DB instance.
  • Too many security group rules will increase the first packet latency. You are advised to create no more than 50 rules for each security group.
  • To enable access to an RDS DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the RDS DB instance.
+

If you use 0.0.0.0/0, RDS DB instances in the security group can be accessed from any IP address.

+
+
+

Procedure

  1. Log in to the management console.
  2. Under Network, click Virtual Private Cloud.
  3. In the navigation pane on the left, choose Access Control > Security Groups.
  4. On the displayed page, locate the target security group and click Manage Rule in the Operation column.
  5. On the displayed page, click Add Rule.
  6. In the displayed dialog box, set required parameters to add an inbound rule.
  7. Click OK.
+
+
+ + diff --git a/docs/rds/umn/rds_02_0016.html b/docs/rds/umn/rds_02_0016.html new file mode 100644 index 000000000..b8c155349 --- /dev/null +++ b/docs/rds/umn/rds_02_0016.html @@ -0,0 +1,106 @@ + + +

Connecting to a DB Instance Through psql

+

You can use the PostgreSQL client psql to connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection is encrypted and therefore more secure.

+

Prerequisites

  1. You have logged in to the ECS.
    • To connect to a DB instance through an ECS, make sure that:
      • The ECS and DB instance must be in the same VPC.
      • The ECS must be allowed by the security group to access RDS DB instances.
        • If the security group with which the target DB instance is 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 is 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 Configuring 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.

          +
        +
      +
    +
  2. You have installed a database client to connect to DB instances.

    For details, see How Can I Install the PostgreSQL Client?

    +
+
+

Non-SSL Connection

  1. Log in to the ECS or the device that can access RDS.
  2. Run the following command to connect to the DB instance:

    psql --no-readline -U <user> -h <host> -p <port> -d <datastore> -W

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    <user>

    +

    Indicates the username of the RDS database account. The default administrator is root.

    +

    <host>

    +

    Indicates the IP address of the primary DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. If the DB instance is accessed through the ECS, the IP address can be found in the Floating IP Address field in the Connection Information area.

    +

    <port>

    +

    Indicates the database port in use. The default value is 5432. To obtain this parameter, go to the Basic Information page of the DB instance. The port number can be found in the Database Port field in the Connection Information area.

    +

    <datastore>

    +

    Indicates the name of the database (the default database name is postgres).

    +
    +
    +

    The parameter -W indicates that a password must be entered for the connection. After running this command, you will be prompted to enter a password.

    +

    Example:

    +

    Run the following command as user root to connect to a DB instance:

    +

    psql --no-readline -U root -h 192.168.0.44 -p 5432 -d postgres -W

    +

+
+

SSL Connection

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
  5. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.

    For details about how to import the root certificate to the Linux OS on the ECS, see How Can I Import the Root Certificate to a Windows or Linux OS?

    +

  6. Connect to an RDS DB instance. The Linux OS is used as an example.

    psql --no-readline -h <host> -p <port> "dbname=<database> user=<user> sslmode=verify-ca sslrootcert=<ca-file-directory>"

    + +
    + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    <host>

    +

    IP address of the primary DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. If the DB instance is accessed through the ECS, the IP address can be found in the Floating IP Address field in the Connection Information area.

    +

    <port>

    +

    Database port in use. The default value is 5432. To obtain this parameter, go to the Basic Information page of the DB instance. The port number can be found in the Database Port field in the Connection Information area.

    +

    <database>

    +

    Name of the database (the default database name is postgres).

    +

    <user>

    +

    Username of the RDS database account. The default administrator is root.

    +

    <ca-file-directory>

    +

    Directory of the CA certificate for the SSL connection. The certificate should be stored in the directory where the command is executed.

    +

    sslmode

    +

    SSL connection mode. Set it to verify-ca to use a CA to check whether the service is trusted.

    +
    +
    +

    Enter the password of the database account if the following information is displayed:

    +

    Password:

    +

    For example, to connect to a DB instance through an SSL connection as user root, run the following command:

    +

    psql --no-readline -h 192.168.0.44 -p 5432 "dbname=postgres user=root sslmode=verify-ca sslrootcert=/root/ca.pem"

    +

    Password:

    +

  7. The SSL connection is established if information similar to the following is displayed after you log in to the database:

    SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)
    +

+
+
+ + diff --git a/docs/rds/umn/rds_02_0017.html b/docs/rds/umn/rds_02_0017.html new file mode 100644 index 000000000..8aeae8f8e --- /dev/null +++ b/docs/rds/umn/rds_02_0017.html @@ -0,0 +1,20 @@ + + +

Step 2: Connect to a DB Instance

+

+
+ + diff --git a/docs/rds/umn/rds_02_0018.html b/docs/rds/umn/rds_02_0018.html new file mode 100644 index 000000000..005e5f808 --- /dev/null +++ b/docs/rds/umn/rds_02_0018.html @@ -0,0 +1,21 @@ + + +

Connecting to a PostgreSQL DB Instance Through a Public Network

+
+ + diff --git a/docs/rds/umn/rds_02_0019.html b/docs/rds/umn/rds_02_0019.html new file mode 100644 index 000000000..43db07c60 --- /dev/null +++ b/docs/rds/umn/rds_02_0019.html @@ -0,0 +1,13 @@ + + +

Overview

+

Process

Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a public network.

+
Figure 1 Connecting to a DB instance through a public network
+
+
+ + diff --git a/docs/rds/umn/rds_02_0025.html b/docs/rds/umn/rds_02_0025.html new file mode 100644 index 000000000..53df17644 --- /dev/null +++ b/docs/rds/umn/rds_02_0025.html @@ -0,0 +1,18 @@ + + +

Binding an EIP

+

Scenarios

By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can unbind the EIP from the DB instance as required.

+
+

Precautions

  • You need to configure security groups and enable specific IP addresses and ports to access the target DB instance. Before accessing the DB instance, you need to add an individual IP address or an IP address range that will access the DB instance to the inbound rule. For details, see section Configuring Security Group Rules.
  • 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 RDS.
+
+

Binding an EIP

  1. On the Instances page, click the target DB instance.
  2. In the navigation pane on the left, choose EIPs. On the displayed page, click Bind EIP.
  3. In the displayed dialog box, select an EIP and click OK.

    If no available EIPs are displayed, click View EIP to obtain an EIP.

    +

  4. On the EIPs page, view the EIP that has been bound to the DB instance.

    You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

    +

+
+
+ + diff --git a/docs/rds/umn/rds_02_0047.html b/docs/rds/umn/rds_02_0047.html new file mode 100644 index 000000000..20436ab74 --- /dev/null +++ b/docs/rds/umn/rds_02_0047.html @@ -0,0 +1,110 @@ + + +

Connecting to a DB Instance Through a Private Network

+

You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.

+

Prerequisites

  1. You have logged in to an ECS.
    • To connect to a DB instance through an ECS, you must ensure that:
      • The ECS and DB instance must be in the same VPC.
      • The ECS must be allowed by the security group to access the DB instance.
        • If the security group with which the target DB instance is 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 is 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 section Configuring 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 the DB instance.

          +
        +
      +
    +
  2. You have installed a database client to connect to DB instances.

    You can use a database client to connect to the target DB instance in the Linux or Windows OS.

    +
    • In the Linux OS, install the MySQL client on the device that can access RDS. 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 section How Can I Install the MySQL Client?

      +
    + +
+
+

Using MySQL-Front to Connect to a DB Instance

  1. Start MySQL-Front.
  2. In the displayed dialog box, click New.

    Figure 1 Connection management
    +

  3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

    Figure 2 Adding an account
    + +
    + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Name

    +

    Indicates the name of the database connection task. If you do not set this parameter, it will be the same as the Host value by default.

    +

    Host

    +
    Indicates the floating IP address of the DB instance to be connected. To view the floating IP address and port of the DB instance, perform the following steps:
    1. Log in to the RDS console.
    2. Select the region in which the DB instance is located.
    3. Click the target DB instance to enter the Basic Information page.
    4. In the Connection Information area, view the floating IP address.
    +
    +

    Port

    +

    Indicates the private network port of the DB instance.

    +

    User

    +

    Indicates the name of the user who will access the DB instance. The default user is root.

    +

    Password

    +

    Indicates the password of the RDS database account.

    +
    +
    +

  4. In the displayed window, select the connection that you have created in 3 and click Open. If the connection information is correct, the DB instance is successfully connected.

    Figure 3 Opening a session
    +

    If the connection fails, see What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?

    +
    +

+
+

SSL Connection

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
  5. 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?

    • Since April 2017, RDS has offered a new root certificate that has a 20-year validation period. The new certificate takes effect after DB instances are rebooted. Replace the old certificate before it expires to improve system security.

      +

      +

      For details, see section How Can I Identify the Validity Period of an SSL Root Certificate?

      +
    • You can also download the certificate bundle, which contains both the new certificate provided since April 2017 and the old certificate.
    +
    +

  6. Connect to the RDS DB instance. The Linux OS is used as an example.

    mysql -h <host> -P <port> -u <userName> -p --ssl-ca=<caDIR>

    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    <host>

    +

    Floating IP address. To obtain this parameter, go to the Basic Information page of the DB instance and view the floating IP address in the Connection Information area.

    +

    <port>

    +

    Database port. By default, the value is 3306. To obtain this parameter, go to the Basic Information page of the DB instance and view the database port in the Connection Information area.

    +

    <userName>

    +

    Username of the RDS database account. The default administrator is root.

    +

    <caDIR>

    +

    Directory of the CA certificate. The certificate should be stored in the directory where the command is executed.

    +
    +
    +

    For example, to connect to a DB instance through an SSL connection as user root, run the following command:

    +

    mysql -h 172.16.0.31 -P 3306 -u root -p --ssl-ca=ca.pem

    +

    Enter the password of the database account if the following information is displayed:

    +
    Enter password:
    +

    If the connection fails, see What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?

    +
    +

+
+
+ + diff --git a/docs/rds/umn/rds_02_0048.html b/docs/rds/umn/rds_02_0048.html new file mode 100644 index 000000000..7e4cc71e5 --- /dev/null +++ b/docs/rds/umn/rds_02_0048.html @@ -0,0 +1,21 @@ + + +

Connecting to an RDS for MySQL DB Instance Through a Public Network

+
+ + diff --git a/docs/rds/umn/rds_02_0051.html b/docs/rds/umn/rds_02_0051.html new file mode 100644 index 000000000..76a5fa968 --- /dev/null +++ b/docs/rds/umn/rds_02_0051.html @@ -0,0 +1,105 @@ + + +

Connecting to a DB Instance Through psql

+

You can use the PostgreSQL client psql to connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection is encrypted and therefore more secure.

+

Prerequisites

  1. An EIP has been bound to the target DB instance and security group rules have been configured.
    1. Bind an EIP to the target DB instance.

      For details about how to bind an EIP, see Binding an EIP.

      +
    2. Obtain the IP address of a local device.
    3. Configure security group rules.

      Add the IP address obtained in 1.b and the instance port to the inbound rule of the security group.

      +

      For details about how to configure security group rules, see Configuring Security Group Rules.

      +
    4. Run the ping command to ping the EIP bound in 1.a.
    +
  2. You have installed a database client to connect to DB instances.

    For details, see How Can I Install the PostgreSQL Client?

    +
+
+

Non-SSL Connection

  1. Log in to the ECS or the device that can access RDS.
  2. Run the following command to connect to the DB instance:

    psql --no-readline -U <user> -h <host> -p <port> -d <datastore> -W

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    <user>

    +

    Indicates the username of the RDS database account. The default administrator is root.

    +

    <host>

    +

    Indicates the IP address of the primary DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. The IP address can be found on the EIPs page.

    +

    <port>

    +

    Indicates the database port in use. The default value is 5432. To obtain this parameter, go to the Basic Information page of the DB instance. The port number can be found in the Database Port field in the Connection Information area.

    +

    <datastore>

    +

    Indicates the name of the database (the default database name is postgres).

    +
    +
    +

    The parameter -W indicates that a password must be entered for the connection. After running this command, you will be prompted to enter a password.

    +

    Example:

    +

    Run the following command as user root to connect to a DB instance:

    +

    psql --no-readline -U root -h 192.168.0.44 -p 5432 -d postgres -W

    +

+
+

SSL Connection

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
  5. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.

    For details about how to import the root certificate to the Linux OS on the ECS, see How Can I Import the Root Certificate to a Windows or Linux OS?

    +

  6. Connect to an RDS DB instance. The Linux OS is used as an example.

    psql --no-readline -h <host> -p <port> "dbname=<database> user=<user> sslmode=verify-ca sslrootcert=<ca-file-directory>"

    + +
    + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    <host>

    +

    IP address of the primary DB instance. To obtain this parameter, go to the Basic Information page of the DB instance. The IP address can be found on the EIPs page.

    +

    <port>

    +

    Database port in use. The default value is 5432. To obtain this parameter, go to the Basic Information page of the DB instance. The port number can be found in the Database Port field in the Connection Information area.

    +

    <database>

    +

    Name of the database (the default database name is postgres).

    +

    <user>

    +

    Username of the RDS database account. The default administrator is root.

    +

    <ca-file-directory>

    +

    Directory of the CA certificate for the SSL connection. The certificate should be stored in the directory where the command is executed.

    +

    sslmode

    +

    SSL connection mode. Set it to verify-ca to use a CA to check whether the service is trusted.

    +
    +
    +

    Enter the password of the database account if the following information is displayed:

    +

    Password:

    +

    For example, to connect to a DB instance through an SSL connection as user root, run the following command:

    +

    psql --no-readline -h 192.168.0.44 -p 5432 "dbname=postgres user=root sslmode=verify-ca sslrootcert=/root/ca.pem"

    +

    Password:

    +

  7. The SSL connection is established if information similar to the following is displayed after you log in to the database:

    SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off)
    +

+
+
+ + diff --git a/docs/rds/umn/rds_02_0060.html b/docs/rds/umn/rds_02_0060.html new file mode 100644 index 000000000..7896e5d54 --- /dev/null +++ b/docs/rds/umn/rds_02_0060.html @@ -0,0 +1,48 @@ + + +

Connecting to a DB Instance

+

An RDS DB instance can be connected through a private network or a public network.

+ +
+ + + + + + + + + + + + + + + + +
Table 1 RDS connection methods

Connect Through

+

IP Address

+

Scenarios

+

Description

+

Private network

+

Floating IP

+

RDS provides a floating IP address by default.

+

When your applications are deployed on an ECS that is in the same region and VPC as RDS, you are advised to use a floating IP address to connect to the RDS DB instance through the ECS.

+
  • Secure and excellent performance
  • Recommended
+

Public network

+

EIP

+

If you cannot access an RDS DB instance through a floating IP address, bind an EIP to the DB instance and connect the DB instance to the ECS through the EIP.

+
  • A relatively lower level of security compared to other connection methods
  • To achieve a higher transmission rate and security level, you are advised to migrate your applications to an ECS that is in the same VPC as your RDS DB instance and use a floating IP address to access the DB instance.
+
+
+
  • VPC: indicates the Virtual Private Cloud.
  • ECS: indicates the Elastic Cloud Server.
  • If the ECS is in the same VPC as your RDS DB instance, you do not need to apply for an EIP.
+
+

Figure 1 illustrates the connection over a private network or a public network.

+
Figure 1 DB instance connection
+
+
+
+
Parent topic: Step 2: Connect to a DB Instance
+
+
+ diff --git a/docs/rds/umn/rds_02_0099.html b/docs/rds/umn/rds_02_0099.html new file mode 100644 index 000000000..73b58c196 --- /dev/null +++ b/docs/rds/umn/rds_02_0099.html @@ -0,0 +1,13 @@ + + +

Overview

+

Process

Figure 1 illustrates the process of connecting to a MySQL DB instance through a public network.

+
Figure 1 Connecting to a DB instance through a public network
+
+
+ + diff --git a/docs/rds/umn/rds_02_0101.html b/docs/rds/umn/rds_02_0101.html new file mode 100644 index 000000000..e1845d019 --- /dev/null +++ b/docs/rds/umn/rds_02_0101.html @@ -0,0 +1,19 @@ + + +

Connecting to an RDS for MySQL DB Instance Through a Private Network

+
+ + diff --git a/docs/rds/umn/rds_03_0001.html b/docs/rds/umn/rds_03_0001.html new file mode 100644 index 000000000..9b2a932d3 --- /dev/null +++ b/docs/rds/umn/rds_03_0001.html @@ -0,0 +1,13 @@ + + +

Overview

+

Process

Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a private network.

+
Figure 1 Connecting to a DB instance through a private network
+
+
+ + diff --git a/docs/rds/umn/rds_03_0003.html b/docs/rds/umn/rds_03_0003.html new file mode 100644 index 000000000..8a38240f1 --- /dev/null +++ b/docs/rds/umn/rds_03_0003.html @@ -0,0 +1,172 @@ + + +

Microsoft SQL Server Constraints

+

RDS for SQL Server only supports DB instances under the License Included model and does not support "bring your own license" (BYOL). After a DB instance is created, it contains the Microsoft SQL Server software license.

+

Table 1 shows the constraints designed to ensure the stability and security of RDS for SQL Server.

+

Microsoft SQL Server DB instances are classified into three types: single, primary/standby, and cluster. Different types support different functions. For details, see Function Comparison.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Function constraints

Function Item

+

Single

+

Primary/Standby

+

Maximum number of databases

+

100

+

100

+

Number of database accounts

+

Unlimited

+

Unlimited

+

Creation of user, LOGIN, or database

+

Supported

+

Supported

+

Database-level DDL trigger

+

Supported

+

Supported

+

Database permission authorization

+

Supported

+

Supported

+

KILL permission

+

Supported

+

Supported

+

Distributed transaction

+

Supported

+

Supported

+

SQL Profiler

+

Supported

+

Supported

+

Tuning Adviser

+

Supported

+

Supported

+

Change Data Capture (CDC)

+

Supported

+

Supported

+

Change tracking

+

Supported

+

Supported

+

Windows domain account login

+

Supported

+

Supported

+

Email

+

Not supported

+

Not supported

+

SQL Server Integration Services (SSIS)

+

Not supported

+

Not supported

+

SQL Server Analysis Services (SSAS)

+

Not supported

+

Not supported

+

SQL Server Reporting Services (SSRS)

+

Not supported

+

Not supported

+

R Services

+

Not supported

+

Not supported

+

Common Language Runtime (CLR)

+

Not supported

+

Not supported

+

Asynchronous communication

+

Not supported

+

Not supported

+

Replication subscription

+

Not supported

+

Not supported

+

Policy management

+

Not supported

+

Not supported

+
+
+
+
+
+
Parent topic: Constraints
+
+
+ diff --git a/docs/rds/umn/rds_03_0005.html b/docs/rds/umn/rds_03_0005.html new file mode 100644 index 000000000..2f94badbe --- /dev/null +++ b/docs/rds/umn/rds_03_0005.html @@ -0,0 +1,23 @@ + + +

Configuring Security Group Rules

+

Scenarios

A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a VPC.

+

This section describes how to create a security group to enable specific IP addresses and ports to access RDS.

+

First check whether the ECS and RDS DB instance are in the same security group.

+
  • If the ECS and RDS 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 Connecting to a DB Instance Through a Private Network.
  • If the ECS and RDS DB instance are in different security groups, you need to configure security group rules for them, separately.
    • RDS DB instance: Configure an inbound rule for the security group with which the RDS DB instance is associated.
    • ECS: The default security group rule allows all outgoing data packets. In this case, 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. ECSs and RDS DB instances can access each other if they are deployed in the same security group. After a security group is created, you can configure security group rules to control access from and to the DB instances in the security group.

+
  • By default, a tenant can create a maximum of 100 security groups.
  • By default, each security group can have a maximum of 50 security group rules.
  • One security group can be associated with only one RDS DB instance.
  • Too many security group rules will increase the first packet latency. You are advised to create no more than 50 rules for each security group.
  • To enable access to an RDS DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the RDS DB instance.
+

If you use 0.0.0.0/0, RDS DB instances in the security group can be accessed from any IP address.

+
+
+

Procedure

  1. Log in to the management console.
  2. Under Network, click Virtual Private Cloud.
  3. In the navigation pane on the left, choose Access Control > Security Groups.
  4. On the Security Groups page, locate the target security group and click Manage Rule in the Operation column.
  5. On the displayed page, click Add Rule.
  6. In the displayed dialog box, set required parameters to add an inbound rule.
  7. Click OK.
+
+
+ + diff --git a/docs/rds/umn/rds_03_0006.html b/docs/rds/umn/rds_03_0006.html new file mode 100644 index 000000000..2f783dcee --- /dev/null +++ b/docs/rds/umn/rds_03_0006.html @@ -0,0 +1,18 @@ + + +

Binding an EIP

+

Scenarios

By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can unbind the EIP from the DB instance as required.

+
+

Precautions

  • You need to configure security groups and enable specific IP addresses and ports to access the target DB instance. Before accessing the DB instance, you need to add an individual IP address or an IP address range that will access the DB instance to the inbound rule. For details, see section Configuring Security Group Rules.
  • Public accessibility reduces the security of DB instances. Therefore, exercise caution when deciding to connect to DB instances through a public network. 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 RDS.
+
+

Binding an EIP

  1. On the Instances page, click the target DB instance.
  2. In the navigation pane on the left, choose EIPs. On the displayed page, click Bind EIP.
  3. In the displayed dialog box, select an EIP and click OK.

    If no available EIPs are displayed, click View EIP and obtain an EIP.

    +

  4. On the EIPs page of the RDS console, view the EIP that has been bound to the DB instance.

    You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

    +

+
+
+ + diff --git a/docs/rds/umn/rds_03_0007.html b/docs/rds/umn/rds_03_0007.html new file mode 100644 index 000000000..72d1764a1 --- /dev/null +++ b/docs/rds/umn/rds_03_0007.html @@ -0,0 +1,36 @@ + + +

Connecting to a DB Instance Through a Public Network

+

You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.

+

Preparations

  1. Install the Microsoft SQL Server client.

    For details, see section How Can I Install SQL Server Management Studio?

    +
  2. Bind an EIP to the target DB instance and configure security group rules.
    1. Bind an EIP to the target DB instance.

      For details about how to bind an EIP, see section Binding an EIP.

      +
    2. Obtain the IP address of the local device.
    3. Configure security group rules.

      Add the IP address obtained in 2.b and the instance port to the inbound rule of the security group.

      +

      For details about how to configure a security group rule, see section Configuring Security Group Rules.

      +
    4. Run the ping command to connect the EIP that has been bound to the target DB instance in 2.a to check that the local device can connect to the EIP.
    +
+
+

Non-SSL Connection

  1. Start SQL Server Management Studio.
  2. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

    Figure 1 Connecting to the server
    +
    • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
      • The IP address is the EIP that has been bound to the DB instance.
      • The port is the database port in the Connection Information area on the Basic Information page of the DB instance.
      +
    • Authentication: indicates the authentication mode. Select SQL Server Authentication.
    • Login: indicates the RDS database username. The default administrator is rdsuser.
    • Password: indicates the password of the RDS database username.
    +

  3. Click Connect to connect to the DB instance.

    If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

    +
    +

+
+

SSL Connection

  1. Download the SSL root certificate and then upload it.

    1. In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
    2. Upload the root certificate to the ECS to be connected to the DB instance.
    3. Import the root certificate to the Windows OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
      • Replace the old certificate before it expires to improve system security.
      • After you bind an EIP to a DB instance, you must reboot the instance for the SSL connection to take effect.
      +
      +
    +

  2. Start SQL Server Management Studio.
  3. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

    Figure 2 Connecting to the server
    +
    • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
      • The IP address is the EIP that has been bound to the DB instance.
      • The port is the database port in the Connection Information area on the Basic Information page of the DB instance.
      +
    • Authentication: indicates the authentication mode. Select SQL Server Authentication.
    • Login: indicates the RDS database username. The default administrator is rdsuser.
    • Password: indicates the password of the RDS database username.
    +

  4. On the Connection Properties page, enter related parameters and select Encrypt connection to enable SSL encryption. (By default, Encrypt connection is not selected. You need to select it manually.)

    Figure 3 Connection properties
    +

  5. Click Connect to connect to the DB instance.

    If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

    +
    +

+
+
+ + diff --git a/docs/rds/umn/rds_03_0008.html b/docs/rds/umn/rds_03_0008.html new file mode 100644 index 000000000..6e3261b5c --- /dev/null +++ b/docs/rds/umn/rds_03_0008.html @@ -0,0 +1,19 @@ + + +

Connecting to a SQL Server DB Instance Through a Private Network

+
+ + diff --git a/docs/rds/umn/rds_03_0010.html b/docs/rds/umn/rds_03_0010.html new file mode 100644 index 000000000..9774536f1 --- /dev/null +++ b/docs/rds/umn/rds_03_0010.html @@ -0,0 +1,34 @@ + + +

Operation Guide

+

You can create and connect to DB instances on the RDS console.

+

Flowchart

Figure 1 Flowchart
+
+

Procedure

+
+ + + + + + + + + + +
Table 1 Related operations and references

Operation

+

Reference

+

Creating an RDS DB instance

+

Step 1: Create a DB Instance

+

Connecting to an RDS DB Instance

+

Step 2: Connect to a DB Instance

+
+
+
+
+ + diff --git a/docs/rds/umn/rds_03_0011.html b/docs/rds/umn/rds_03_0011.html new file mode 100644 index 000000000..bb104924c --- /dev/null +++ b/docs/rds/umn/rds_03_0011.html @@ -0,0 +1,125 @@ + + +

Creating a Read Replica

+

Scenarios

Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.

+
+

After a DB instance has been created, you can create read replicas for it.

+

A maximum of five read replicas can be created for a primary DB instance.

+

Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Create Read Replica in the Operation column.

    Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

    +

  5. On the displayed page, configure information about the DB instance and click Next.

    +

    + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    By default, read replicas are in the same region as the primary DB instance.

    +

    DB Instance Name

    +

    Must start with a letter and consist of 4 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).

    +

    DB Engine

    +

    Same as the DB engine of the primary DB instance by default and cannot be changed.

    +

    DB Engine Version

    +

    Same as the DB engine version of the primary DB instance by default and cannot be changed.

    +

    AZ

    +

    RDS allows you to deploy primary DB instances and read replicas in a single AZ or across AZs to improve reliability.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Instance specifications

    Parameter

    +

    Description

    +

    Instance Class

    +

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and maximum IOPS.

    +

    For details about instance classes, see DB Instance Classes.

    +

    +

    +

    +

    After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

    +

    +

    Storage Type

    +

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    +
    • Common I/O: uses the SATA disk type that supports a maximum throughput of 90 MB/s.
    • Ultra-high I/O: uses the SSD disk type that supports a maximum throughput of 350 MB/s.
    +

    Storage Space

    +

    Contains the file system overhead required for inode, reserved block, and database operation.

    +

    By default, storage space of a read replica is the same as that of the primary DB instance.

    +

    Disk Encryption

    +
    • Disable: indicates the encryption function is disabled.
    • Enable: indicates the encryption function is enabled, improving data security but affecting system performance.

      Key Name: indicates the tenant key. You can select an existing key or create a new one.

      +
      NOTE:
      • Once the DB instance is created, you cannot modify the disk encryption status or change the key. The backup data stored in OBS is not encrypted.
      • After an RDS DB instance is created, do not disable or delete a key that is currently in use. Otherwise, RDS will be unavailable and data cannot be restored.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      +
    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    Same as the primary DB instance's VPC.

    +

    Subnet

    +

    Same as the primary DB instance's subnet. A floating IP address is automatically assigned when you create a read replica. You can also enter an unused floating IP address in the subnet CIDR block. After the read replica is created, the floating IP address cannot be changed.

    +

    Security Group

    +

    Same as the primary DB instance's VPC.

    +
    +
    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • Otherwise, click Submit.
    +

  7. After a read replica has been created, you can view and manage it on the Instances page by clicking on the left of the DB instance to which it belongs.

    Alternatively, click the target DB instance. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.

    +

    +

+
+

Follow-up Operations

Managing a Read Replica

+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_03_0013.html b/docs/rds/umn/rds_03_0013.html new file mode 100644 index 000000000..4d8c8d0e3 --- /dev/null +++ b/docs/rds/umn/rds_03_0013.html @@ -0,0 +1,40 @@ + + +

Connecting to a DB Instance Through a Private Network

+

You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.

+

Preparations

  1. Prepare an ECS.

    To connect to a DB instance through a private network, you must first create an ECS.

    +

    For details about how to create an ECS, see section How Can I Create and Connect to an ECS?

    +
    • The ECS and RDS DB instance must be in the same VPC.
    • The ECS must be allowed by the security group to access RDS DB instances.
      • If the security group with which the target DB instance is 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 is associated is not the default security group, check whether the security group rules allow the ECS to connect to the DB instance.
        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
        4. On the Instances page, click the target DB instance.
        5. In the Connection Information area, click the security group to view its 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. For details, see section Configuring Security Group Rules.

          +
        +
      +
    +
  2. Install the Microsoft SQL Server client.

    Install the Microsoft SQL Server client on the ECS or device that was prepared in 1.

    +

    For details, see section How Can I Install SQL Server Management Studio?

    +
+
+

Non-SSL Connection

  1. Log in to the ECS or device that can access RDS.
  2. Start SQL Server Management Studio.
  3. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

    Figure 1 Connecting to the server
    +
    • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
      • The IP address is the floating IP address in the Connection Information area on the Basic Information page of the DB instance.
      • The port is the database port in the Connection Information area on the Basic Information page of the DB instance.
      +
    • Authentication: indicates the authentication mode. Select SQL Server Authentication.
    • Login: indicates the RDS database username. The default administrator is rdsuser.
    • Password: indicates the password of the RDS database username.
    +

  4. Click Connect to connect to the DB instance.

    If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

    +
    +

+
+

SSL Connection

  1. Download the SSL root certificate and then upload it.

    1. In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
    2. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.
    3. Import the root certificate into the Windows OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
      • Replace the old certificate before it expires to improve system security.
      • After you bind an EIP to a DB instance, you must reboot the instance for the SSL connection to take effect.
      +
      +
    +

  2. Start SQL Server Management Studio.
  3. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

    Figure 2 Connecting to the server
    +
    • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
      • The IP address is the floating IP address in the Connection Information area on the Basic Information page of the DB instance.
      • The port is the database port in the Connection Information area on the Basic Information page of the DB instance.
      +
    • Authentication: indicates the authentication mode. Select SQL Server Authentication.
    • Login: indicates the RDS database username. The default administrator is rdsuser.
    • Password: indicates the password of the RDS database username.
    +

  4. On the Connection Properties page, enter related parameters and select Encrypt connection to enable SSL encryption. (By default, Encrypt connection is not selected. You need to select it manually.)

    Figure 3 Connection properties
    +

  5. Click Connect to connect to the DB instance.

    If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

    +
    +

+
+
+ + diff --git a/docs/rds/umn/rds_03_0014.html b/docs/rds/umn/rds_03_0014.html new file mode 100644 index 000000000..74f3057e0 --- /dev/null +++ b/docs/rds/umn/rds_03_0014.html @@ -0,0 +1,15 @@ + + +

Getting Started with RDS for SQL Server

+
+ + diff --git a/docs/rds/umn/rds_03_0018.html b/docs/rds/umn/rds_03_0018.html new file mode 100644 index 000000000..0cb8dfafe --- /dev/null +++ b/docs/rds/umn/rds_03_0018.html @@ -0,0 +1,11 @@ + + +

Introduction to PostgreSQL Enhanced Edition

+

PostgreSQL Enhanced Edition is developed from PostgreSQL 11. It retains all functions of the PostgreSQL databases. PostgreSQL Enhanced Edition supports system views, PL/SQL, data types, advanced functions, SQL syntax, and null value processing. It helps you reduce costs for migration to the cloud and provides a comprehensive solution with high security, high availability, and high performance.

+
+
+
+
Parent topic: PostgreSQL Enhanced Edition
+
+
+ diff --git a/docs/rds/umn/rds_03_0051.html b/docs/rds/umn/rds_03_0051.html new file mode 100644 index 000000000..9fcc783d2 --- /dev/null +++ b/docs/rds/umn/rds_03_0051.html @@ -0,0 +1,21 @@ + + +

Configuring Security Group Rules

+

Scenarios

A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a VPC.

+

This section describes how to create a security group to enable specific IP addresses and ports to access RDS.

+

When you attempt to connect to an RDS DB instance through an EIP, you need to configure an inbound rule for the security group associated with the DB instance.

+
+

Precautions

The default security group rule allows all outgoing data packets. ECSs and RDS DB instances can access each other if they are deployed in the same security group. After a security group is created, you can configure security group rules to control access from and to the DB instances in the security group.

+
  • By default, you can create a maximum of 500 security group rules.
  • Too many security group rules will increase the first packet latency. You are advised to create no more than 50 rules for each security group.
  • To enable access to an RDS DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the RDS DB instance.
+

If you use 0.0.0.0/0, RDS DB instances in the security group can be accessed from any IP address.

+
+
+

Procedure

  1. Log in to the management console.
  2. Under Network, click Virtual Private Cloud.
  3. In the navigation pane on the left, choose Access Control > Security Groups.
  4. On the Security Groups page, locate the target security group and click Manage Rule in the Operation column.
  5. On the displayed page, click Add Rule.
  6. In the displayed dialog box, set required parameters to add an inbound rule.
  7. Click OK.
+
+
+ + diff --git a/docs/rds/umn/rds_03_0052.html b/docs/rds/umn/rds_03_0052.html new file mode 100644 index 000000000..11d89a571 --- /dev/null +++ b/docs/rds/umn/rds_03_0052.html @@ -0,0 +1,22 @@ + + +

Connecting to a SQL Server DB Instance Through a Public Network

+

+
+ + diff --git a/docs/rds/umn/rds_03_0060.html b/docs/rds/umn/rds_03_0060.html new file mode 100644 index 000000000..acb2204e0 --- /dev/null +++ b/docs/rds/umn/rds_03_0060.html @@ -0,0 +1,48 @@ + + +

Connecting to a DB Instance

+

An RDS DB instance can be connected through a private network or a public network.

+ +
+ + + + + + + + + + + + + + + + +
Table 1 RDS connection methods

Connect Through

+

IP Address

+

Scenarios

+

Description

+

Private network

+

Floating IP

+

RDS provides a floating IP address by default.

+

When your applications are deployed on an ECS that is in the same region and VPC as RDS, you are advised to use a floating IP address to connect to the RDS DB instance through the ECS.

+
  • Secure and excellent performance
  • Recommended
+

Public network

+

EIP

+

If you cannot access an RDS DB instance through a floating IP address, bind an EIP to the DB instance and connect the DB instance to the ECS through the EIP.

+
  • A relatively lower level of security compared to other connection methods
  • To achieve a higher transmission rate and security level, you are advised to migrate your applications to an ECS that is in the same VPC as your RDS DB instance and use a floating IP address to access the DB instance.
+
+
+
  • VPC: indicates the Virtual Private Cloud.
  • ECS: indicates the Elastic Cloud Server.
  • If the ECS is in the same VPC as your RDS DB instance, you do not need to apply for an EIP.
+
+

Figure 1 illustrates the connection over a private network or a public network.

+
Figure 1 DB instance connection
+
+
+
+
Parent topic: Step 2: Connect to a DB Instance
+
+
+ diff --git a/docs/rds/umn/rds_03_0063.html b/docs/rds/umn/rds_03_0063.html new file mode 100644 index 000000000..0052c09b0 --- /dev/null +++ b/docs/rds/umn/rds_03_0063.html @@ -0,0 +1,15 @@ + + +

Getting Started with RDS for PostgreSQL

+
+ + diff --git a/docs/rds/umn/rds_03_0064.html b/docs/rds/umn/rds_03_0064.html new file mode 100644 index 000000000..e5563fe34 --- /dev/null +++ b/docs/rds/umn/rds_03_0064.html @@ -0,0 +1,18 @@ + + +

Binding an EIP

+

Scenarios

By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility and can unbind the EIP from the DB instance as required.

+
+

Precautions

  • You need to configure security groups and enable specific IP addresses and ports to access the target DB instance. Before accessing the DB instance, you need to add an individual IP address or an IP address range that will access the DB instance to the inbound rule. For details, see section Configuring Security Group Rules.
  • Public accessibility reduces the security of DB instances. Therefore, exercise caution when deciding to connect to DB instances through a public network. 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 RDS.
+
+

Binding an EIP

  1. On the Instances page, click the target DB instance.
  2. In the navigation pane on the left, choose EIPs. On the displayed page, click Bind EIP.
  3. In the displayed dialog box, select an EIP and click OK.

    If no available EIPs are displayed, click View EIP to obtain an EIP.

    +

  4. On the EIPs page, view the EIP that has been bound to the DB instance.

    You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

    +

+
+
+ + diff --git a/docs/rds/umn/rds_03_0065.html b/docs/rds/umn/rds_03_0065.html new file mode 100644 index 000000000..c0f3b9e5f --- /dev/null +++ b/docs/rds/umn/rds_03_0065.html @@ -0,0 +1,220 @@ + + +

Step 1: Create a DB Instance

+

Scenarios

You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see "Creating a DB Instance" in the Relational Database Service API Reference. This section describes how to create a DB instance on the RDS console.

+

RDS allows you to tailor your computing resources and storage space to your business needs.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click Create DB Instance.
  5. On the displayed page, configure information about your DB instance. Then, click Create Now.

    +

    + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    The region where your RDS resources will be located. You can change it on the creation page, or go back to the Instances page and change it in the upper left corner.

    +
    NOTE:

    Products in different regions cannot communicate with each other through a private network and you cannot change the region of a DB instance after creating the instance. Therefore, exercise caution when selecting a region.

    +
    +

    DB Instance Name

    +

    Must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

    +

    DB Engine

    +

    Set to PostgreSQL.

    +

    DB Engine Version

    +

    +

    +

    For details, see DB Engines and Versions.

    +

    Different DB engine versions are supported in different regions.

    +

    You are advised to select the latest available version because it is more stable, reliable, and secure.

    +

    DB Instance Type

    +
    • Primary/Standby: uses an HA architecture with a primary DB instance and a synchronous standby DB instance. It is suitable for production databases of large- and medium-sized enterprises in Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other sectors. The standby DB instance improves instance reliability and is invisible to you after being created.

      An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

      +

      You can deploy primary and standby DB instances in a single AZ or across AZs to achieve failover and high availability.

      +
    • Single: uses a single-node architecture, which is more cost-effective than primary/standby DB instances. It is suitable for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.
    +

    Time Zone

    +

    Select a time zone when you are creating a DB instance, and you can change it after the DB instance is created.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Instance specifications

    Parameter

    +

    Description

    +

    Instance Class

    +

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and different maximum IOPS.

    +

    For details about instance classes, see DB Instance Classes.

    +

    +

    +

    +

    After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

    +

    +

    Storage Type

    +

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    +
    • Common I/O: uses the SATA disk type, with a maximum throughput of 90 MB/s.
    • Ultra-high I/O: uses the SSD disk type that supports a maximum throughput of 350 MB/s.
    +

    Storage Space (GB)

    +

    Contains the file system overhead required for inode, reserved block, and database operation. Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.

    +

    +

    +

    After a DB instance is created, you can scale up its storage space. For details, see Scaling up Storage Space.

    +

    +

    Disk Encryption

    +
    • Disable: indicates the encryption function is disabled.
    • Enable: indicates the encryption function is enabled, improving data security but affecting system performance.

      Key Name: indicates the tenant key. You can create or select a key.

      +
      NOTE:
      • Once the DB instance is created, you cannot modify the disk encryption status or change the key.
      • After an RDS DB instance is created, do not disable or delete the key that is being used. Otherwise, database will be unavailable.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      +
    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    A dedicated virtual network in which your RDS DB instances are located. A VPC can isolate networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.

    +

    If no VPC is available, RDS allocates a VPC to you by default.

    +
    NOTICE:

    After the DB instance is created, the VPC cannot be changed.

    +
    +

    Subnet

    +

    Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function is enabled by default for subnets in which you plan to create RDS DB instances and cannot be disabled.

    +

    A floating IP address is automatically assigned when you create a DB instance. You can also enter an unused floating IP address in the subnet CIDR block. After the DB instance is created, you can change the floating IP address.

    +

    Security Group

    +

    Controls the access that traffic has in and out of a DB instance. By default, the security group associated with the DB instance is authorized.

    +

    Enhances security by controlling access to RDS from other services. You need to add inbound rules to a security group so that you can connect to your DB instance.

    +

    If no security group is available, RDS allocates a security group to you by default.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 4 Database configuration

    Parameter

    +

    Description

    +

    Administrator

    +

    The default login name for the database is root.

    +

    Administrator Password

    +

    Must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it for security reasons.

    +

    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.

    +

    Keep this password secure. The system cannot retrieve it.

    +

    +

    After a DB instance is created, you can reset this password. For details, see section Resetting the Administrator Password.

    +

    Confirm Password

    +

    Must be the same as Administrator Password.

    +

    Parameter Template

    +

    Contains engine configuration values that can be applied to one or more DB instances. If you intend to create primary/standby DB instances, they use the same parameter template.

    +
    NOTICE:

    If you use a custom parameter template when creating a DB instance, the following specification-related parameters in the custom template are not delivered. Instead, the default values are used.

    +
    • maintenance_work_mem
    • shared_buffers
    • max_connections
    • effective_cache_size
    +
    +

    +

    +

    You can modify the instance parameters as required after the DB instance is created. For details, see Modifying Instance Parameters.

    +

    +
    +
    + +
    + + + + + + + +
    Table 5 Tags

    Parameter

    +

    Description

    +

    Tag

    +

    Tags an RDS DB instance. This configuration is optional. Adding tags to RDS DB instances helps you better identify and manage the DB instances. A maximum of 20 tags can be added for each DB instance.

    +

    After a DB instance is created, you can view its tag details on the Tags page. For details, see section Managing Tags.

    +
    +
    + +
    + + + + + + + +
    Table 6 Batch creation

    Parameter

    +

    Description

    +

    Quantity

    +

    RDS supports DB instance creation in batches. If you choose to create primary/standby DB instances and set Quantity to 1, a primary DB instance and a standby DB instance will be created synchronously.

    +

    If you create multiple DB instances at a time, they will be named with four digits appended to the DB instance name. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on.

    +
    +
    +

    After the configuration, click Price Calculator to view the RDS configuration fee.

    +

    The performance of your DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.

    +
    +

  6. Confirm the specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. To view and manage the DB instance, go to the Instances page.

    • During the creation process, the DB instance status is Creating. When the creation process is complete, the instance status will change to Available.
    • The automated backup policy is enabled by default. After the DB instance is created, you can modify the policy as needed. An automated full backup is immediately triggered after a DB instance is created.
    • The default database port is 5432. After a DB instance is created, you can change the database port.

      +

      +

      For details, see Changing a Database Port.

      +

      +
    +

+
+
+ + diff --git a/docs/rds/umn/rds_03_0066.html b/docs/rds/umn/rds_03_0066.html new file mode 100644 index 000000000..d4df5ca49 --- /dev/null +++ b/docs/rds/umn/rds_03_0066.html @@ -0,0 +1,13 @@ + + +

Overview

+

Process

Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a public network.

+
Figure 1 Connecting to a DB instance through a public network
+
+
+ + diff --git a/docs/rds/umn/rds_03_0100.html b/docs/rds/umn/rds_03_0100.html new file mode 100644 index 000000000..8403a63d3 --- /dev/null +++ b/docs/rds/umn/rds_03_0100.html @@ -0,0 +1,15 @@ + + +

Downloading a Binlog Backup File

+

Scenarios

RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary.

+
+

Downloading a Binlog Backup File

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. The Basic Information page is displayed.
  5. In the navigation pane on the left, choose Backups & Restorations. On the Binlog Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    You can also select the binlog backups to be downloaded and click Download above the list.

    +

  6. After the download is complete, you can view the binlog backups locally.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_04_0001.html b/docs/rds/umn/rds_04_0001.html new file mode 100644 index 000000000..78b285e0b --- /dev/null +++ b/docs/rds/umn/rds_04_0001.html @@ -0,0 +1,17 @@ + + +

PostgreSQL Enhanced Edition

+
+ + diff --git a/docs/rds/umn/rds_04_0002.html b/docs/rds/umn/rds_04_0002.html new file mode 100644 index 000000000..0dc2305be --- /dev/null +++ b/docs/rds/umn/rds_04_0002.html @@ -0,0 +1,386 @@ + + +

Functions

+

This section describes the built-in functions and advanced function packages added to PostgreSQL Enhanced Edition on the basis of PostgreSQL 11 open-source edition.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Built-in functions

Built-in Function

+

Description

+

add_months(date,integer)

+

Returns the date plus integer months. The return type is DATE.

+

appendchildxml(XMLType_instance, XPath_string, value_expr[, namespace_string])

+

Appends the value_expr node onto XPath_string specified by XMLType_instance. The namespace_string provides namespace information for the XPath_string.

+

asciistr(string)

+

Returns an ASCII version of the string in the database character set. Non-ASCII characters are not supported.

+

bin_to_num(expr_list)

+

Converts a binary string in expr_list to its equivalent decimal number. The return type is NUMBER.

+

bitand(number1,number2)

+

Returns the bitwise 'AND' for two supplied integers number1 and number2. The return type is BIT.

+

convert(char, dest_char_set[, source_char_set])

+

Converts char in the source_char_set to the dest_char_set encoding format. This function takes effect only on the server.

+

cosh(n)

+

Returns the hyperbolic cosine of argument n.

+

decode(expr,search1, result1[[,search2, result2],......][, default])

+

Compares expr to each search value (search1, search2, etc). If expr is equal to a search, then Oracle Database returns the corresponding result. If no match is found, then Oracle returns default. If default is omitted, then Oracle returns null.

+

empty_blob()

+

Returns an empty BLOB.

+

hextoraw(char)

+

Converts a hexadecimal string to a raw value.

+

instrb(string, substring[, position[, occurrence]])

+

Searches a string for a substring using characters and return the position in the string that is the first character of a specified occurrence of the substring. The functions vary in how they determine the position of the substring to return.

+

last_day(date)

+

Returns the date of the last day of the month that contains date.

+

lengthb(char)

+

Returns the length of char. Char can be any of the data types (CHAR, VARCHAR2, NCHAR, or NVARCHAR2), or types (such as integer) that can be implicitly converted into character strings.

+

listagg(measure_expr[, 'delimiter']) within group(order_by_clause) [over query_partition_clause]

+

Sorts the values of the column expression measure_expr in the query_partition_clause group based on the order_by_clause rule and aggregates them into one row. Values are separated by delimiter.

+

lnnvl(condition)

+

Returns a value of condition expression. The return type is BOOLEAN.

+

mod(n2, n1)

+

Returns the remainder of n2 divided by n1. Returns n2 if n1 is 0.

+

months_between(date1, date2)

+

Returns the number of months between dates date1 and date2. If date1 is earlier than date2, then the result is negative.

+

nanvl(n2, n1)

+

Returns n1 if the single- or double-precision floating point number input value n2 is NAN. If the input value n2 is not NAN, n2 is returned.

+

nchr(number)

+

Returns the character having the binary equivalent to number in the national character set.

+

new_time(date, timezone1, timezone2)

+

Returns the date and time in time zone timezone2 when date and time in time zone timezone1 are date. The return type is DATE.

+

next_day(date, char)

+

Returns the date of the first weekday named by char that is later than the date (including workdays, weekends, and holidays). The return type is DATE.

+

numtodsinterval(n, interval_unit)

+

Converts n to an INTERVAL DAY TO SECOND literal. The value for interval_unit specifies the unit of n and must resolve to 'DAY', 'HOUR', 'MINUTE', and 'SECOND'.

+

numtoyminterval(n, 'interval_unit')

+

Converts n to an INTERVAL YEAR TO MONTH literal. The value for interval_unit can be YEAR or MONTH.

+

nlssort(char[, nlsparam])

+

Sorts the char string according to the sorting character set specified by nlsparam. By default, char is used for sorting.

+

nls_upper(char[, nlsparam])

+

Converts all alphabetic characters in the character string char to uppercase letters based on the sort sequence specified by nlsparam. The character string type is CHAR, VARCHAR2, NCHAR, NVARCHAR2, CLOB, or NCLOB, and nlsparam is in the form of NLS_SORT = sort.

+

nls_lower(char[, nlsparam])

+

Converts all alphabetic characters in the character string char to lowercase letters based on the sort sequence specified by nlsparam. The character string type is CHAR, VARCHAR2, NCHAR, NVARCHAR2, CLOB, or NCLOB, and nlsparam is in the form of NLS_SORT = sort.

+

nvl(expr1, expr2)

+

Returns the first non-null value in expr1 and expr2.

+

rawtohex(raw)

+

Converts raw to a character value containing its hexadecimal representation.

+

regexp_count(source_char, pattern, position, match_param)

+

Returns the number of times a pattern occurs in a source string starting from the position that indicates the source_char character where the database begins the search. The match_param parameter is a text literal that lets you change the default matching behavior of the function. For example, match_param='i' specifies case-insensitive matching.

+

regexp_instr(source_char, pattern[, position[, occurrence[, return_opt[, match_param[, subexpr]]]]])

+

Extends the INSTR function and allows regular expression matching. The return type is INTEGER.

+
  • position: indicates the start position of the search.
  • occurrence: indicates the sequence number of the pattern in source_char.
  • return_opt:
    • The value 0 indicates the start position of the return mode.
    • The value 1 indicates the end position of the return mode.
    +
  • match_param: indicates the control parameter of the regular expression, such as case sensitive.
  • subexpr: indicates the group number of the regular expression group.
+

regexp_like(source_char, pattern[,match_param])

+

source_char is a character expression. Pattern is the regular expression. The match_param parameter is a text literal that lets you change the default matching behavior of the function.

+

regexp_substr(source_char, pattern[,position[,occurrence[,match_param[,subexpr]]]])

+

Matches the character string in the source_char string based on the regular expression.

+
  • source_char is the text expression that is searched. Supports all character strings, including CHAR, VARCHAR2, NCHAR, or NVARCHAR2, or types (such as integer) that can be implicitly converted into character strings.
  • pattern is the text expression to search for.
  • position is a nonzero integer indicating the character of source_char where the function begins the search.
  • occurrence is an integer indicating which occurrence of pattern the function should search for.
  • match_parameter is a text expression that lets you change the default matching behavior of the function.
  • subexpr is a nonnegative integer from 0 to 9 indicating which subexpression in pattern is to be returned by the function.
+

raise_application_error(errnum, errmsg)

+

Sends the error code errnum and error message errmsg to the client.

+

remainder(n2, n1)

+

Returns the remainder of n2 divided by n1. The remainder function is similar to mod except that mod uses floor in its formula, whereas reminder uses ROUND. The return type is NUMERIC or double-precision floating-point number (determined by the input parameter type).

+

round(n,precision)

+

Returns n rounded to integer places to the right of the decimal point. The precision is the number of digits in a number.

+

scn_to_timestamp(number)

+

Returns the approximate timestamp associated with a system change number (SCN).

+

sinh(n)

+

Returns the hyperbolic sine of n. If n is BINARY_FLOAT, the return type is BINARY_DOUBLE. Otherwise, the return type is NUMERIC.

+

substr(char,position[,substring_length])

+

Returns a portion of string, beginning at a specified position in the string. The functions vary in how they calculate the length of the substring to return. If substring_length is not specified, the function returns all characters to the end of string.

+

substrb(char, position[, substring_length])

+

Returns a portion of char, beginning at a specified position in the string. The functions vary in how they calculate the length of the substring to return. If substring_length is not specified, the function returns all characters to the end of string.

+

sys_context(namespace, parameter)

+

Returns the value of parameter associated with the context namespace. The return type is VARCHAR2.

+

sys_guid()

+

Returns a globally unique identifier (RAW value).

+

sys_connect_by_path(column, char)

+

Is valid only in CONNECT BY queries and returns the path of a column value from root to node.

+

tanh(n)

+

Returns the hyperbolic tangent of argument n.

+

to_blob(char)

+

Converts char strings to BLOB values. Char can be any of the data types (CHAR, VARCHAR2, NCHAR, or NVARCHAR2), or types (such as integer) that can be implicitly converted into character strings.

+

to_binary_float(expr)

+

Converts expr to the single-precision float type.

+

to_binary_double(expr)

+

Converts expr to the double-precision float type.

+

to_clob(char)

+

Converts char to the CLOB data type.

+

to_char(char)

+

Supports char types: char, character, and varchar.

+

to_date(char[,fmt])

+

Converts char of the CHAR, VARCHAR2, NCHAR, NVARCHAR2, or TIMESTAMP data type to a value of the DATE data type according to the fmt format. If fmt is omitted, char must use the default format of the DATE data type.

+

to_dsinterval('sql_format' | 'ds_iso_format')

+

Converts the time character string of the SQL standard (such as '100 00:00:00') or ISO standard (such as 'P100DT05H') to the INTERVAL DAY TO SECOND data type.

+

to_multi_byte(char)

+

Converts a single-byte character char into a multi-byte character.

+

to_number(expr)

+

Converts expr to a value of NUMBER data type.

+

to_number(expr, fmt, 'nlsparam')

+

+

Converts expr to a value of NUMBER data type in the format specified by fmt. The nlsparam is an international language parameter and supports the following parameters: NLS_NUMERIC_CHARACTERS, NLS_CURRENCY, and NLS_ISO_CURRENCY.

+

to_timestamp(char[,fmt])

+

Converts char of the CHAR, VARCHAR2, NCHAR, NVARCHAR2, or TIMESTAMP data type to a value of the timestamp data type according to the fmt format. If fmt is omitted, char must use the default format of the TIMESTAMP data type.

+

to_single_byte(char)

+

Converts multibyte characters to their corresponding single-byte characters.

+

to_yminterval('sql_format' | 'ym_iso_format')

+

Converts the time character string of the SQL standard (such as '01-02') or ISO standard (such as 'P1Y2M') to the INTERVAL MONTH TO YEAR data type.

+

timestamp_to_scn(timestamp)

+

Returns the approximate system change number (SCN) associated with a timestamp.

+

trunc(date[, fmt])

+

Truncates date according to the date format specified by fmt. The return type is DATE. If fmt is omitted, the default date format is 'DDD'.

+

tz_offset({time_zone_name | '{+|-}hh:mi'})

+

Returns the specified time zone offset. The return type is VARCHAR2. The parameter is a character string in the time_zone_name or '{+|-}hh:mi' format.

+

value(correlation_variable)

+

Returns the recorded row associated with correlation_variable in object table mode. The return type is the object table associated with correlation_variable.

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Advanced function packages

Advanced Function Package

+

Description

+

DBMS_OUTPUT.PUT(item)

+

Places the item string in the local buffer. Item indicates all types that can be converted into character strings.

+

DBMS_OUTPUT.PUT_LINE(item)

+

Places the item string in the local buffer and outputs all the content in the local buffer. Item indicates all types that can be converted into character strings.

+

DBMS_RANDOM.SEED(val)

+

Val is the seed number used to generate a random number. It can be a character string or a digit.

+

DBMS_RANDOM.VALUE([low,high])

+

Returns a 16-digit random number between low and high. If the range of low and high is not specified, the default value range is 0-1.

+

dbms_lob.getlength(lob_loc {clob|blob})

+

Returns the LOB length specified by lob_loc.

+

dbms_lob.read(lob_loc, amount, offset, buffer)

+

Returns the specified amount into the buffer parameter, starting from an absolute offset from the beginning of the LOB.

+

dbms_lob.write(lob_loc, amount, offset, buffer)

+

Writes the buffer content to the large object lob_loc buffer (the referenced large object is not affected) starting at offset. The amount represents the size.

+

utl_raw.cast_to_raw(char)

+

Converts char of the VARCHAR2 data type to RAW. The return type is RAW.

+

utl_raw.length(raw)

+

Returns the length of the raw data type. The return type is NUMBER.

+

utl_raw.cast_from_binary_integer(n, endianess)

+

Converts the integer n to the RAW type based on the memory alignment mode specified by endianess. The values of endianess are as follows:

+
  • 1: big_endian
  • 2: little_endian
  • 3: machine_endian
+
+
+
+
+
+
Parent topic: PostgreSQL Enhanced Edition
+
+
+ diff --git a/docs/rds/umn/rds_04_0060.html b/docs/rds/umn/rds_04_0060.html new file mode 100644 index 000000000..0d166a2ad --- /dev/null +++ b/docs/rds/umn/rds_04_0060.html @@ -0,0 +1,48 @@ + + +

Connecting to a DB Instance

+

An RDS DB instance can be connected through a private network or a public network.

+ +
+ + + + + + + + + + + + + + + + +
Table 1 RDS connection methods

Connect Through

+

IP Address

+

Scenarios

+

Description

+

Private network

+

Floating IP

+

RDS provides a floating IP address by default.

+

When your applications are deployed on an ECS that is in the same region and VPC as RDS, you are advised to use a floating IP address to connect to the RDS DB instance through the ECS.

+
  • Secure and excellent performance
  • Recommended
+

Public network

+

EIP

+

If you cannot access an RDS DB instance through a floating IP address, bind an EIP to the DB instance and connect the DB instance to the ECS through the EIP.

+
  • A relatively lower level of security compared to other connection methods
  • To achieve a higher transmission rate and security level, you are advised to migrate your applications to an ECS that is in the same VPC as your RDS DB instance and use a floating IP address to access the DB instance.
+
+
+
  • VPC: indicates the Virtual Private Cloud.
  • ECS: indicates the Elastic Cloud Server.
  • If the ECS is in the same VPC as the RDS DB instance, you do not need to apply for an EIP.
+
+

Figure 1 illustrates the connection over a private network or a public network.

+
Figure 1 DB instance connection
+
+
+
+
Parent topic: Step 2: Connect to a DB Instance
+
+
+ diff --git a/docs/rds/umn/rds_04_0061.html b/docs/rds/umn/rds_04_0061.html new file mode 100644 index 000000000..5452be9d0 --- /dev/null +++ b/docs/rds/umn/rds_04_0061.html @@ -0,0 +1,226 @@ + + +

Step 1: Create a DB Instance

+

Scenarios

You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see the "Creating a DB Instance" section in the Relational Database Service API Reference. This section describes how to create a DB instance on the RDS console.

+

The DB instance class and storage space you need depend on your processing power and memory requirements.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click Create DB Instance.
  5. On the displayed page, configure information about your DB instance. Then, click Create Now.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    The region where your RDS resources will be located. You can change it on the creation page, or go back to the Instances page and change it in the upper left corner.

    +
    NOTE:

    Products in different regions cannot communicate with each other through a private network and you cannot change the region of a DB instance after creating the instance. Therefore, exercise caution when selecting a region.

    +
    +

    DB Instance Name

    +

    Must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

    +

    DB Engine

    +

    Set to Microsoft SQL Server.

    +

    DB Engine Version

    +

    +

    +

    For details, see DB Engines and Versions.

    +

    +

    Different DB engine versions are supported in different regions.

    +

    You are advised to select the latest available version because it is more stable, reliable, and secure.

    +

    DB Instance Type

    +
    • Primary/Standby: uses an HA architecture with a primary DB instance and a synchronous standby DB instance. It is suitable for production databases of large- and medium-sized enterprises in Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other sectors. The standby DB instance improves instance reliability and is invisible to you after being created.

      An AZ is a physical region where resources use independent power supply and networks. AZs are physically isolated but interconnected through an internal network.

      +

      You can deploy primary and standby DB instances in a single AZ or across AZs to achieve failover and high availability.

      +
    • Single: uses a single-node architecture, which is more cost-effective than primary/standby DB instances. It is suitable for development and testing of microsites, and small- and medium-sized enterprises, or for learning about RDS.
    +

    Time Zone

    +

    Select your time zone when you are creating a DB instance. After the DB instance is created, the time zone cannot be modified.

    +

    Server Collation

    +

    Defines a collation of a database or table column, or a collation cast operation when applied to character string expression. It acts as the default collation for the DB instance.

    +
    NOTE:

    The SQL_Latin1_General_CP850_BIN2 collation is supported.

    +
    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Instance specifications

    Parameter

    +

    Description

    +

    Instance Class

    +

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and different maximum IOPS.

    +

    For details about instance classes, see DB Instance Classes.

    +

    +

    +

    +

    After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class.

    +

    +

    Storage Type

    +

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    +
    • Common I/O: uses the SATA disk type, with a maximum throughput of 90 MB/s.
    • Ultra-high I/O: uses the SSD disk type that supports a maximum throughput of 350 MB/s.
    +

    Storage Space (GB)

    +

    Contains the file system overhead required for inode, reserved block, and database operation. Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.

    +

    +

    +

    After a DB instance is created, you can scale up its storage space. For details, see section Scaling up Storage Space.

    +

    +

    Disk Encryption

    +
    • Disable: indicates the encryption function is disabled.
    • Enable: indicates the encryption function is enabled, improving data security but affecting system performance.

      Key Name: indicates the tenant key. You can create or select a key.

      +
      NOTE:
      • Once the DB instance is created, you cannot modify the disk encryption status or change the key. The backup data stored in OBS is not encrypted.
      • After an RDS DB instance is created, do not disable or delete the key that is being used. Otherwise, database will be unavailable.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      +
    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    A dedicated virtual network in which your RDS DB instances are located. A VPC can isolate networks for different services. You can select an existing VPC or create a VPC. For details on how to create a VPC, see the "Creating a VPC" section in the Virtual Private Cloud User Guide.

    +

    If no VPC is available, RDS allocates a VPC to you by default.

    +
    NOTICE:

    After the DB instance is created, the VPC cannot be changed.

    +
    +

    Subnet

    +

    Improves network security by providing dedicated network resources that are logically isolated from other networks. Subnets take effect only within an AZ. The Dynamic Host Configuration Protocol (DHCP) function is enabled by default for subnets in which you plan to create RDS DB instances and cannot be disabled.

    +

    A floating IP address is automatically assigned when you create a DB instance. You can also enter an unused floating IP address in the subnet CIDR block. After the DB instance is created, the floating IP address cannot be changed.

    +

    Security Group

    +

    Enhances security by controlling access to RDS from other services. You need to add inbound rules to a security group so that you can connect to your DB instance.

    +

    If no security group is available, RDS allocates a security group to you by default.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 4 Database configuration

    Parameter

    +

    Description

    +

    Administrator

    +

    The default login name for the database is rdsuser.

    +

    Administrator Password

    +

    Must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_+?). Enter a strong password and periodically change it for security reasons.

    +

    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.

    +

    Keep this password secure. The system cannot retrieve it.

    +

    +

    After a DB instance is created, you can reset this password. For details, see section Resetting the Administrator Password.

    +

    Confirm Password

    +

    Must be the same as Administrator Password.

    +

    Parameter Template

    +

    Contains engine configuration values that can be applied to one or more DB instances. If you intend to create primary/standby DB instances, they use the same parameter template.

    +
    NOTICE:

    If you use a custom parameter template when creating a DB instance, the specification-related parameter max server memory (MB) in the custom template is not delivered. Instead, the default value is used.

    +
    +

    +

    +

    You can modify the instance parameters as required after the DB instance is created. For details, see Modifying Parameters.

    +

    +
    +
    + +
    + + + + + + + +
    Table 5 Tags

    Parameter

    +

    Description

    +

    Tag

    +

    Tags an RDS DB instance. This configuration is optional. Adding tags to RDS DB instances helps you better identify and manage the DB instances. A maximum of 20 tags can be added for each DB instance.

    +

    After a DB instance is created, you can view its tag details on the Tags page. For details, see section Managing Tags.

    +
    +
    + +
    + + + + + + + +
    Table 6 Batch creation

    Parameter

    +

    Description

    +

    Quantity

    +

    RDS supports DB instance creation in batches. If you choose to create primary/standby DB instances and set Quantity to 1, a primary DB instance and a standby DB instance will be created synchronously.

    +

    If you create multiple DB instances at a time, they will be named with four digits appended to the DB instance name. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on.

    +
    +
    +

    After the configuration, click Price Calculator to view the RDS configuration fee.

    +

    The performance of your DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.

    +
    +

  6. Confirm the specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. To view and manage the DB instance, go to the Instances page.

    • During the creation process, the DB instance status is Creating. When the creation process is complete, the instance status will change to Available.
    • The automated backup policy is enabled by default. An automated full backup is immediately triggered after a DB instance is created.
    • The default database port number is 1433. After a DB instance is created, you can change its port number.

      +

      +

      For details, see Changing a Database Port.

      +

      +
    +

+
+
+ + diff --git a/docs/rds/umn/rds_05_0000.html b/docs/rds/umn/rds_05_0000.html new file mode 100644 index 000000000..f70b56939 --- /dev/null +++ b/docs/rds/umn/rds_05_0000.html @@ -0,0 +1,29 @@ + + +

Instance Lifecycle

+
+ + diff --git a/docs/rds/umn/rds_05_0001.html b/docs/rds/umn/rds_05_0001.html new file mode 100644 index 000000000..4ac037698 --- /dev/null +++ b/docs/rds/umn/rds_05_0001.html @@ -0,0 +1,33 @@ + + + +

Instance Modifications

+ +

+
+ + + diff --git a/docs/rds/umn/rds_05_0001_02.html b/docs/rds/umn/rds_05_0001_02.html new file mode 100644 index 000000000..7b746e396 --- /dev/null +++ b/docs/rds/umn/rds_05_0001_02.html @@ -0,0 +1,16 @@ + + +

Data Migration

+

+
+ + diff --git a/docs/rds/umn/rds_05_0003.html b/docs/rds/umn/rds_05_0003.html new file mode 100644 index 000000000..26cbcb193 --- /dev/null +++ b/docs/rds/umn/rds_05_0003.html @@ -0,0 +1,18 @@ + + +

Upgrading a Minor Version

+

Scenarios

RDS for MySQL supports minor version upgrades to improve performance, add new functions, and fix bugs.

+
+

Precautions

  • The upgrade will cause the DB instance to reboot and interrupt services intermittently. To limit the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your applications support automatic reconnection.
  • If primary and standby DB instances are deployed in the same AZ, a minor version upgrade will trigger a failover. If primary and standby DB instances are deployed in different AZs, a minor version upgrade will trigger two failovers.
  • When you upgrade a minor version of a primary DB instance, minor versions of read replicas (if any) will also be upgraded automatically (they cannot be upgraded separately). Perform the upgrade during off-peak hours because the DB instance will be rebooted after the upgrade is complete.
  • A minor version upgrade cannot be rolled back after the upgrade is complete. If the upgrade fails, the DB instance will be automatically rolled back to the source version.
  • DDL operations, such as create event, drop event, and alter event, are not allowed during a minor version upgrade.
+
+

Constraints

  • If the replication delay between primary and standby DB instances is longer than 300 seconds, the minor version cannot be upgraded.
  • Minor versions cannot be upgraded for DB instances with abnormal nodes.
  • Currently, RDS for MySQL supports a maximum of 100,000 tables. If there are more than 100,000 tables, the minor version upgrade may fail.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary/standby DB instances.
  5. In the DB Information area on the Basic Information page, click Upgrade in the DB Engine Version field.
  6. In the displayed dialog box, select a scheduled time and click OK.
+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_05_0005.html b/docs/rds/umn/rds_05_0005.html new file mode 100644 index 000000000..91856017e --- /dev/null +++ b/docs/rds/umn/rds_05_0005.html @@ -0,0 +1,21 @@ + + +

Connection Management

+
+ + diff --git a/docs/rds/umn/rds_05_0006.html b/docs/rds/umn/rds_05_0006.html new file mode 100644 index 000000000..777f24504 --- /dev/null +++ b/docs/rds/umn/rds_05_0006.html @@ -0,0 +1,17 @@ + + +

Data Security

+
+ + diff --git a/docs/rds/umn/rds_05_0007.html b/docs/rds/umn/rds_05_0007.html new file mode 100644 index 000000000..1fee7e573 --- /dev/null +++ b/docs/rds/umn/rds_05_0007.html @@ -0,0 +1,17 @@ + + +

Task Center

+
+ + diff --git a/docs/rds/umn/rds_05_0017.html b/docs/rds/umn/rds_05_0017.html new file mode 100644 index 000000000..a8817b86b --- /dev/null +++ b/docs/rds/umn/rds_05_0017.html @@ -0,0 +1,16 @@ + + +

Exporting DB Instance Information

+

Scenarios

You can export information about all or selected DB instances to view and analyze DB instance information.

+
+

Exporting Information About All DB Instances

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
  5. Find a .csv file locally after the export task is completed.
+
+

Exporting Information About Selected DB Instances

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
  5. Find a .csv file locally after the export task is completed.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_05_0018.html b/docs/rds/umn/rds_05_0018.html new file mode 100644 index 000000000..eeb37dd85 --- /dev/null +++ b/docs/rds/umn/rds_05_0018.html @@ -0,0 +1,18 @@ + + +

Applying a Parameter Template

+

Scenarios

You can apply parameter templates to DB instances as needed.

+
  • The parameter innodb_buffer_pool_size is determined by the memory. DB instances of different specifications have different value ranges. If this parameter value is out of range of the DB instance that the parameter template applies to, the maximum value within the range is used.
  • A parameter template can be applied only to DB instances of the same DB engine version.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

    • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
    • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.
    +

    A parameter template can be applied to one or more DB instances.

    +

  5. In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.

    After the parameter template is successfully applied, you can view the application records by referring to section Viewing Application Records of a Parameter Template.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_05_0023.html b/docs/rds/umn/rds_05_0023.html new file mode 100644 index 000000000..699fce2ba --- /dev/null +++ b/docs/rds/umn/rds_05_0023.html @@ -0,0 +1,16 @@ + + +

Changing a DB Instance Type from Single to Primary/Standby

+

Scenarios

  • RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability. This operation does not affect the services running on the primary DB instance.
  • Primary/standby DB instances support automatic failover. If the primary DB instance fails, the standby DB instance takes over services quickly. You are advised to deploy primary and standby DB instances in different AZs for high availability and disaster recovery.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate a single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

    Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

    +

  5. Select a standby AZ. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
  6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

    • The DB instance is in the Changing type to primary/standby status. You can view the progress on the Task Center page. For details, see section Task Center.
    • In the upper right corner of the DB instance list, click to refresh the list. After the DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_05_0024.html b/docs/rds/umn/rds_05_0024.html new file mode 100644 index 000000000..898e3a05d --- /dev/null +++ b/docs/rds/umn/rds_05_0024.html @@ -0,0 +1,20 @@ + + +

Configuring and Changing a Floating IP Address

+

Scenarios

You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.

+
+

Constraints

After a floating IP address is changed, the domain name needs to be resolved again. This operation takes several minutes and may interrupt database connections. Therefore, you are advised to change a floating IP address during off-peak hours.

+
+

Configuring a Floating IP Address

You can use an automatically-assigned IP address when creating a DB instance.

+
+

Changing a Floating IP Address

You can change the floating IP address of an existing DB instance.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
  6. In the displayed dialog box, enter a new floating IP address and click OK.

    An in-use IP address cannot be used as the new floating IP address of the DB instance.

    +

+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_05_0034.html b/docs/rds/umn/rds_05_0034.html new file mode 100644 index 000000000..1056814c9 --- /dev/null +++ b/docs/rds/umn/rds_05_0034.html @@ -0,0 +1,33 @@ + + +

Backups and Restorations

+
+ + diff --git a/docs/rds/umn/rds_05_0038.html b/docs/rds/umn/rds_05_0038.html new file mode 100644 index 000000000..4165eaebb --- /dev/null +++ b/docs/rds/umn/rds_05_0038.html @@ -0,0 +1,18 @@ + + +

Changing the Maintenance Window

+

Scenarios

The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off-peak hours.

+
+

Precautions

  • During the maintenance window, the DB instance will be intermittently disconnected for one or two times. Ensure that your applications support automatic reconnection.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. In the DB Information area on the Basic Information page, click Change in the Maintenance Window field.
  5. In the displayed dialog box, select a maintenance window and click OK.

    Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

    +
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_05_0044.html b/docs/rds/umn/rds_05_0044.html new file mode 100644 index 000000000..703fcb5df --- /dev/null +++ b/docs/rds/umn/rds_05_0044.html @@ -0,0 +1,23 @@ + + +

Restoring from Backup Files to a Self-Built SQL Server Database

+

You can download backup files by referring to section Downloading a Backup File and restore data from them. You can use SQL Server Management Studio (SSMS) to connect to a self-built ECS database or local database to restore data. The following uses SSMS as an example to show how to restore data from a backup file on a local database.

+
  • Before restoring data, ensure that the ECS has been installed with the SQL Server database service running a same or later version than the SQL Server databases.
+
+

Procedure

  1. Download SSMS and upload it to the ECS for installation.

    Download SSMS 18.0 (GA) from the website and upload it to the ECS.

    +

  2. On the ECS, decompress the RDS full backup file that has been downloaded.
  3. Start the SSMS client.
  4. Log in to the local database service through the SSMS client.
  5. In the SSMS client, right-click Databases and choose Restore Database.

    +

  6. In the displayed Restore Database dialog box, select Device in the Source pane. In the displayed Select backup devices dialog box, specify the backup media and its location and click OK.

    1. Set Backup media type to File.

      +
    2. Click Add to add the decompressed backup file (in the .bak format) and configure required information on the Options page.
      Figure 1 Adding a backup file
      +
      Figure 2 Configuring required options
      +
    +

    3. Click OK to add the backup file to the backup media list and click OK again to restore the backup file to a self-built database.

    +

    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_05_0055.html b/docs/rds/umn/rds_05_0055.html new file mode 100644 index 000000000..c23030fb0 --- /dev/null +++ b/docs/rds/umn/rds_05_0055.html @@ -0,0 +1,19 @@ + + +

Creating a Same DB Instance as an Existing DB Instance

+

Scenarios

This section describes how to quickly create a DB instance with the same configurations as the selected one.

+
  • You can create DB instances with the same configurations numerous times.
  • This function is unavailable for read replicas.
+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Create Same DB Instance in the Operation column.
  5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Create Now.

    For details about MySQL DB instance configurations, see section Step 1: Create a DB Instance.

    +

  6. Confirm the instance specifications.

    +

  7. Refresh the DB instance list and view the status of the DB instance. If the status is Available, it has been created successfully.

    You can manage the DB instance on the Instances page.

    +

+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_05_0057.html b/docs/rds/umn/rds_05_0057.html new file mode 100644 index 000000000..15534379a --- /dev/null +++ b/docs/rds/umn/rds_05_0057.html @@ -0,0 +1,17 @@ + + +

Stopping a DB Instance

+

Scenarios

If you use DB instances only for routine development, you can temporarily stop pay-per-use DB instances to save money. You can stop a DB instance for up to seven days.

+
+

Constraints

  • If you stop a primary DB instance, read replicas (if there are any) will also be stopped. They are stopped for up to seven days. You cannot stop a read replica without stopping the primary DB instance.
  • A stopped DB instance will not be moved to the recycle bin after being deleted.
  • If you do not manually start your stopped DB instance after seven days, your DB instance is automatically started during the next maintenance window. For details about the maintenance window, see Changing the Maintenance Window. To start a DB instance, see Starting a DB Instance.
  • After a DB instance is stopped, billing for instance usage duration will stop.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the primary DB instance that you want to stop and choose More > Stop in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the DB instance list and view the status of the DB instance. If the status is Stopped, the DB instance is stopped successfully.
+
+

+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_05_0058.html b/docs/rds/umn/rds_05_0058.html new file mode 100644 index 000000000..52b80cb21 --- /dev/null +++ b/docs/rds/umn/rds_05_0058.html @@ -0,0 +1,17 @@ + + +

Starting a DB Instance

+

Scenarios

You can stop your DB instance temporarily to save money. After stopping your DB instance, you can restart it to begin using it again.

+
+

Constraints

  • If you start a primary DB instance, read replicas (if there are any) will also be started.
  • Only DB instances in Stopped state can be started. After this function is enabled, billing for instance usage duration will start.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the primary DB instance that you want to start and choose More > Start in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the DB instance list and view the status of the DB instance. If the status is Available, the DB instance is started successfully.
+
+

+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_05_0098.html b/docs/rds/umn/rds_05_0098.html new file mode 100644 index 000000000..224f0da6b --- /dev/null +++ b/docs/rds/umn/rds_05_0098.html @@ -0,0 +1,15 @@ + + +

Viewing Application Records of a Parameter Template

+

Scenarios

You can view the application records of a parameter template.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left.
  5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

    You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_05_0099.html b/docs/rds/umn/rds_05_0099.html new file mode 100644 index 000000000..abae859d2 --- /dev/null +++ b/docs/rds/umn/rds_05_0099.html @@ -0,0 +1,21 @@ + + +

Viewing Parameter Change History

+

Scenarios

You can view the change history of DB instance parameters or custom parameter templates.

+

An exported or custom parameter template has initially a blank change history.

+
+
+

Viewing Change History of a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

    You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

    +

    You can apply the parameter template to DB instances as required by referring to Applying a Parameter Template.

    +

+
+

Viewing Change History of a Parameter Template

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  5. On the displayed page, choose Change History in the navigation pane on the left.

    You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_06_0001.html b/docs/rds/umn/rds_06_0001.html new file mode 100644 index 000000000..8f8e7f8ea --- /dev/null +++ b/docs/rds/umn/rds_06_0001.html @@ -0,0 +1,654 @@ + + +

Configuring Displayed Metrics

+

The RDS Agent monitors RDS DB instances and collects monitoring metrics only.

+

Description

This section describes the RDS metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the monitoring metrics and alarms generated for RDS.

+
+

Namespace

SYS.RDS

+
+

DB Instance Monitoring Metrics

Table 1 lists the performance metrics of MySQL databases. +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Database performance metrics

Metric

+

Name

+

Description

+

Value Range

+

Monitored Object

+

Monitoring Interval (Raw Data)

+

rds001_cpu_util

+

CPU Usage

+

CPU usage of the monitored object

+

0-100%

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds002_mem_util

+

Memory Usage

+

Memory usage of the monitored object

+

0-100%

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds003_iops

+

IOPS

+

Average number of I/O requests processed by the system in a specified period

+

≥ 0 counts/s

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds004_bytes_in

+

Network Input Throughput

+

Incoming traffic in bytes per second

+

≥ 0 bytes/s

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds005_bytes_out

+

Network Output Throughput

+

Outgoing traffic in bytes per second

+

≥ 0 bytes/s

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds006_conn_count

+

Total Connections

+

Total number of connections that attempt to connect to the MySQL server

+

≥ 0 counts

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds007_conn_active_count

+

Current Active Connections

+

Number of current active connections

+

≥ 0 counts

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds008_qps

+

QPS

+

Query times of SQL statements (including stored procedures) per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds009_tps

+

TPS

+

Execution times of submitted and rollback transactions per second

+

≥ 0 transactions/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds010_innodb_buf_usage

+

Buffer Pool Usage

+

Ratio of idle pages to the total number of buffer pool pages in the InnoDB buffer

+

0–1

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds011_innodb_buf_hit

+

Buffer Pool Hit Ratio

+

Ratio of read hits to read requests in the InnoDB buffer

+

0–1

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds012_innodb_buf_dirty

+

Buffer Pool Dirty Block Ratio

+

Ratio of dirty data to used pages in the InnoDB buffer

+

0–1

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds013_innodb_reads

+

InnoDB Read Throughput

+

Number of read bytes per second in the InnoDB buffer

+

≥ 0 bytes/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds014_innodb_writes

+

InnoDB Write Throughput

+

Number of write bytes per second in the InnoDB buffer

+

≥ 0 bytes/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds015_innodb_read_count

+

InnoDB File Read Frequency

+

Number of times that InnoDB reads data from files per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds016_innodb_write_count

+

InnoDB File Write Frequency

+

Number of times that InnoDB writes data to files per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds017_innodb_log_write_req_count

+

InnoDB Log Write Requests per Second

+

Number of InnoDB log write requests per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds018_innodb_log_write_count

+

InnoDB Log Physical Write Frequency

+

Number of InnoDB physical write times to log files per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds019_innodb_log_fsync_count

+

InnoDB Log fsync() Write Frequency

+

Number of completed fsync() write times to InnoDB log files per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds020_temp_tbl_count

+

Temporary Tables

+

Number of temporary tables automatically created on hard disks when MySQL statements are executed

+

≥ 0 tables

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds021_myisam_buf_usage

+

Key Buffer Usage

+

MyISAM key buffer usage

+

0–1

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds022_myisam_buf_write_hit

+

Key Buffer Write Hit Ratio

+

MyISAM key buffer write hit ratio

+

0–1

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds023_myisam_buf_read_hit

+

Key Buffer Read Hit Ratio

+

MyISAM key buffer read hit ratio

+

0–1

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds024_myisam_disk_write_count

+

MyISAM Disk Write Frequency

+

Number of times that indexes are written to disks per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds025_myisam_disk_read_count

+

MyISAM Disk Read Frequency

+

Number of times that indexes are read from disks per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds026_myisam_buf_write_count

+

MyISAM Buffer Pool Write Requests per Second

+

Number of requests for writing indexes into the MyISAM buffer pool per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds027_myisam_buf_read_count

+

MyISAM Buffer Pool Read Requests per Second

+

Number of requests for reading indexes from the MyISAM buffer pool per second

+

≥ 0 counts/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds028_comdml_del_count

+

DELETE Statements per Second

+

Number of DELETE statements executed per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds029_comdml_ins_count

+

INSERT Statements per Second

+

Number of INSERT statements executed per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds030_comdml_ins_sel_count

+

INSERT_SELECT Statements per Second

+

Number of INSERT_SELECT statements executed per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds031_comdml_rep_count

+

REPLACE Statements per Second

+

Number of REPLACE statements executed per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds032_comdml_rep_sel_count

+

REPLACE_SELECTION Statements per Second

+

Number of REPLACE_SELECTION statements executed per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds033_comdml_sel_count

+

SELECT Statements per Second

+

Number of SELECT statements executed per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds034_comdml_upd_count

+

UPDATE Statements per Second

+

Number of UPDATE statements executed per second

+

≥ 0 queries/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds035_innodb_del_row_count

+

Row Delete Frequency

+

Number of rows deleted from the InnoDB table per second

+

≥ 0 rows/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds036_innodb_ins_row_count

+

Row Insert Frequency

+

Number of rows inserted into the InnoDB table per second

+

≥ 0 rows/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds037_innodb_read_row_count

+

Row Read Frequency

+

Number of rows read from the InnoDB table per second

+

≥ 0 rows/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds038_innodb_upd_row_count

+

Row Update Frequency

+

Number of rows updated into the InnoDB table per second

+

≥ 0 rows/s

+

Monitored object: database

+

Monitored instance type: MySQL instance

+

1 minute

+

rds039_disk_util

+

Storage Space Usage

+

Storage space usage of the monitored object

+

0-100%

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds047_disk_total_size

+

Total Storage Space

+

Total storage space of the monitored object

+

40–4,000 GB

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds048_disk_used_size

+

Used Storage Space

+

Used storage space of the monitored object

+

0–4,000 GB

+

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds049_disk_read_throughput

+

Disk Read Throughput

+

Number of bytes read from the disk per second

+

≥ 0 bytes/s

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+

rds050_disk_write_throughput

+

Disk Write Throughput

+

Number of bytes written into the disk per second

+

≥ 0 bytes/s

+

Monitored object: ECS

+

Monitored instance type: MySQL instance

+

1 minute

+
+
+
+
+

Dimension

+
+ + + + + + + +

Key

+

Value

+

rds_instance_id

+

MySQL DB instance ID

+
+
+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_06_0002.html b/docs/rds/umn/rds_06_0002.html new file mode 100644 index 000000000..e030fd009 --- /dev/null +++ b/docs/rds/umn/rds_06_0002.html @@ -0,0 +1,16 @@ + + +

Setting Alarm Rules

+

Scenarios

  • You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.

    The RDS alarm rules include alarm rule names, resource types, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

    +
+
+

Setting Alarm Rules

  1. Log in to the management console.
  2. Click Service List and choose Management & Governance > Cloud Eye.
  3. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
  4. On the displayed Alarm Rules page, click Create Alarm Rule.

    For details about how to create alarm rules, see Using Alarm Templates to Create an Alarm Rule in the Cloud Eye User Guide.

    +

+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_06_0003.html b/docs/rds/umn/rds_06_0003.html new file mode 100644 index 000000000..a273ab7ff --- /dev/null +++ b/docs/rds/umn/rds_06_0003.html @@ -0,0 +1,24 @@ + + +

Viewing Monitoring Metrics

+

Scenarios

Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.

+

Monitored data takes some time before it can be displayed. The RDS status displayed on the Cloud Eye console is about 5 to 10 minutes delayed. When you create a new RDS DB instance, it takes 5 to 10 minutes before monitoring data is displayed on Cloud Eye.

+
+

Prerequisites

  • RDS is running properly.

    Monitoring metrics of the RDS DB instances that are faulty or have been deleted are not displayed on the Cloud Eye console. You can view their monitoring metrics after they are rebooted or restored to normal.

    +
+

If an RDS DB instance has been faulty for 24 hours, Cloud Eye considers it to no longer exist and deletes it from the monitoring object list. You need to manually clear the alarm rules created for the DB instance.

+
+
  • RDS has been running properly for about 10 minutes.

    For a newly created RDS DB instance, you need to wait a bit before you can view the metrics.

    +
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

    Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

    +

  5. On the Cloud Eye console, view monitoring metrics of the primary DB instance.

    Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 30 days, and 7 days.

    +

+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_06_0004.html b/docs/rds/umn/rds_06_0004.html new file mode 100644 index 000000000..d4d7b50f9 --- /dev/null +++ b/docs/rds/umn/rds_06_0004.html @@ -0,0 +1,275 @@ + + +

Key Operations Supported by CTS

+

Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 RDS operations that can be recorded by CTS

Operation

+

Resource Type

+

Trace Name

+

Creating a DB instance or a read replica, or restoring data to a new DB instance

+

instance

+

createInstance

+

Scaling up storage space and changing instance class

+

instance

+

instanceAction

+

Rebooting a DB instance

+

instance

+

instanceRestart

+

Restoring data to the original DB instance

+

instance

+

instanceRestore

+

Renaming a DB instance

+

instance

+

instanceRename

+

Resetting a password

+

instance

+

resetPassword

+

Setting database version parameters

+

instance

+

setDBParameters

+

Resetting database version parameters

+

instance

+

resetDBParameters

+

Enabling, modifying, or disabling a backup policy

+

instance

+

setBackupPolicy

+

Changing a database port

+

instance

+

changeInstancePort

+

Binding or unbinding an EIP

+

instance

+

setOrResetPublicIP

+

Modifying a security group

+

instance

+

modifySecurityGroup

+

Adding a tag

+

instance

+

createTag

+

Deleting a tag

+

instance

+

deleteTag

+

Editing a tag

+

instance

+

modifyTag

+

Deleting a DB instance

+

instance

+

deleteInstance

+

Performing a primary/standby switchover

+

instance

+

instanceFailOver

+

Changing a synchronize model

+

instance

+

instanceFailOverMode

+

Changing a failover priority

+

instance

+

instanceFailOverStrategy

+

Changing a DB instance type from single to primary/standby

+

instance

+

modifySingleToHaInstance

+

Creating a backup

+

backup

+

createManualSnapshot

+

Replicating a backup

+

backup

+

copySnapshot

+

Downloading a backup (using OBS)

+

backup

+

downLoadSnapshot

+

Downloading a backup (using a browser)

+

backup

+

backupsDownLoad

+

Deleting a backup

+

backup

+

deleteManualSnapshot

+

Downloading a merged backup

+

backup

+

packBackupsDownLoad

+

Creating a parameter template

+

parameterGroup

+

createParameterGroup

+

Modifying parameters in a parameter template

+

parameterGroup

+

updateParameterGroup

+

Deleting a parameter template

+

parameterGroup

+

deleteParameterGroup

+

Replicating a parameter template

+

parameterGroup

+

copyParameterGroup

+

Resetting a parameter template

+

parameterGroup

+

resetParameterGroup

+

Comparing parameter templates

+

parameterGroup

+

compareParameterGroup

+

Applying a parameter template

+

parameterGroup

+

applyParameterGroup

+

Saving parameters in a parameter template

+

parameterGroup

+

saveParameterGroup

+

Deleting a frozen DB instance

+

all

+

rdsUnsubscribeInstance

+

Freezing a DB instance

+

all

+

rdsfreezeInstance

+
+
+
+
+
+
Parent topic: Interconnection with CTS
+
+
+ diff --git a/docs/rds/umn/rds_06_0005.html b/docs/rds/umn/rds_06_0005.html new file mode 100644 index 000000000..97f31e1cd --- /dev/null +++ b/docs/rds/umn/rds_06_0005.html @@ -0,0 +1,18 @@ + + +

Viewing Tracing Events

+

Scenarios

After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.

+

This section describes how to query the operation records of last 7 days on the CTS console.

+
+

Procedure

  1. Log in to the management console.
  2. Choose Management & Governance > Cloud Trace Service.
  3. Choose Trace List in the navigation pane on the left.
  4. Filter conditions to query traces. The details are described as follows:

    • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

      When you select Resource ID for Search By, you also need to select or enter a resource ID.

      +
    • Operator: Select a specific operator from the drop-down list.
    • Trace Status: Available options include All trace statuses, Normal, Warning, and Incident. You can only select one of them.
    • In the upper right corner of the page, you can specify a time range for querying traces.
    +

  5. Select the search criteria, and click Query.
  6. Click on the left of the required trace to expand its details.
  7. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
  8. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

    For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

    +

+
+
+
+
+
Parent topic: Interconnection with CTS
+
+
+ diff --git a/docs/rds/umn/rds_08_0000.html b/docs/rds/umn/rds_08_0000.html new file mode 100644 index 000000000..1e609828d --- /dev/null +++ b/docs/rds/umn/rds_08_0000.html @@ -0,0 +1,37 @@ + + +

Working with RDS for MySQL

+
+ + diff --git a/docs/rds/umn/rds_08_00000.html b/docs/rds/umn/rds_08_00000.html new file mode 100644 index 000000000..07b81cdc9 --- /dev/null +++ b/docs/rds/umn/rds_08_00000.html @@ -0,0 +1,16 @@ + + +

Parameter Tuning

+

+
+ + diff --git a/docs/rds/umn/rds_08_00001.html b/docs/rds/umn/rds_08_00001.html new file mode 100644 index 000000000..c13dce004 --- /dev/null +++ b/docs/rds/umn/rds_08_00001.html @@ -0,0 +1,36 @@ + + +

Suggestions on MySQL Parameter Tuning

+

Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some important parameters for your reference. For details, visit the MySQL official website.

+

For details on how to modify MySQL parameters on the console, see Modifying Parameters.

+

Sensitive Parameters

The following parameters can result in system security and stability issues if set improperly:

+
  • lower_case_table_names

    Default value: 1

    +

    Function: Controls whether database and tables stored on disks are case sensitive. The value 1 indicates that database and table names are case-insensitive and are lowercase by default.

    +

    MySQL 8.0 does not support this parameter.

    +
    +

    Impact: Changing this parameter value may cause primary/standby replication exceptions. Exercise caution when performing this operation.

    +
    • If you want to change this parameter value from 1 to 0, change it on read replicas and reboot them first, and then repeat the operations on the primary DB instance.
    • If you want to change this parameter value from 0 to 1, change it on the primary DB instance and reboot it first, and then run SELECT @@GLOBAL.GTID_EXECUTED on read replicas. Wait until the result set is at least the same as the primary DB instance and then change this parameter value on read replicas and reboot them.
    +
  • innodb_flush_log_at_trx_commit

    Default value: 1

    +

    Function: Controls the balance between strict ACID compliance for commit operations and higher performance. The default setting of 1 is required for full ACID compliance. Logs are written and flushed to disks at each transaction commit. If the value is set to 0, logs are written and flushed to disks once per second. If the value is set to 2, logs are written at each transaction commit and flushed to disks every two seconds.

    +

    Impact: If this parameter is not set to 1, data security is not guaranteed. If the system fails, data may be lost.

    +
  • sync_binlog

    Default value: 1

    +

    Function: Controls how often the MySQL server synchronizes binary logs to the disk. The default setting of 1 requires synchronization of the binary log to the disk at each transaction commit. If the value is set to 0, synchronization of the binary log to the disk is not controlled by the MySQL server but relies on the OS to flush the binary log to the disk. This setting provides the best performance, but in the event of a power failure or OS crash, all binary log information in binlog_cache is lost.

    +

    Impact: If this parameter is not set to 1, data security is not guaranteed. If the system fails, data may be lost.

    +
  • innodb_large_prefix

    Default value: OFF

    +

    Function: Specifies the maximum length of a single-column index in an InnoDB table.

    +

    This parameter is available only for MySQL 5.6.

    +
    +

    Impact: Changing this parameter value during DDL execution may cause primary/standby replication exceptions. Exercise caution when performing this operation.

    +
    • If you want to change this parameter value from OFF to ON, change it on read replicas first and then on the primary DB instance.
    • If you want to change this parameter value from ON to OFF, change it on the primary DB instance first and then on read replicas.
    +
+
+

Performance Parameters

The following parameters can affect database performance:

+
  • The values of innodb_spin_wait_delay and query_alloc_block_size are determined by the DB instance specifications. If you increase their values, database performance may be affected.
  • If key_buffer_size is set to a value smaller than 4096, the parameter modification will fail.
  • If max_connections is set to a small value, database access will be affected.
  • The default values of the following parameters are determined by the DB instance specifications: innodb_buffer_pool_size, max_connections, and back_log. These parameter values are default before being specified.
  • The values of innodb_io_capacity_max and innodb_io_capacity are determined by the storage type. These parameter values are default before being specified.
+
+
+
+
+
Parent topic: Parameter Tuning
+
+
+ diff --git a/docs/rds/umn/rds_08_0002.html b/docs/rds/umn/rds_08_0002.html new file mode 100644 index 000000000..eee6f5850 --- /dev/null +++ b/docs/rds/umn/rds_08_0002.html @@ -0,0 +1,20 @@ + + +

Deleting a DB Instance or Read Replica

+

Scenarios

To release resources, you can delete DB instances or read replicas as required on the Instances page.

+
+

Constraints

  • DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are complete.
  • If you delete a DB instance, its automated backups are also deleted and you are no longer billed for them. Manual backups, however, are still retained and will generate additional costs.
+
  • If you delete a primary DB instance, its standby DB instance and read replicas (if any) are also deleted automatically. Exercise caution when performing this operation.
  • Deleted DB instances cannot be recovered and resources are released. Exercise caution when performing this operation. If you want to retain data, create a manual backup first before deleting the DB instance.
  • You can restore a DB instance that was deleted up to 7 days ago from the recycle bin. For details, see Recycling a DB Instance.
  • You can use a manual backup to restore a DB instance. For details, see Restoring from Backup Files to DB Instances.
+
+
+

Deleting a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the DB instance list later to confirm that the deletion was successful.
+
+

Deleting a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
  5. Locate the read replica to be deleted and click More > Delete in the Operation column.
  6. In the displayed dialog box, click Yes.
  7. Refresh the DB instance list later to check that the deletion is successful.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_08_0003.html b/docs/rds/umn/rds_08_0003.html new file mode 100644 index 000000000..fa0ca2b92 --- /dev/null +++ b/docs/rds/umn/rds_08_0003.html @@ -0,0 +1,15 @@ + + +

Changing a Security Group

+

Scenarios

This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the primary DB instance will cause the security group of the standby DB instance to also be changed accordingly.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary DB instance or read replica.
  5. In the Connection Information area on the Basic Information page, click in the Security Group field.

    • To submit the change, click .
    • To cancel the change, click .
    +

  6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information page to view the results.
+
+
+
+
+
Parent topic: Data Security
+
+
+ diff --git a/docs/rds/umn/rds_08_0004.html b/docs/rds/umn/rds_08_0004.html new file mode 100644 index 000000000..d03fcd014 --- /dev/null +++ b/docs/rds/umn/rds_08_0004.html @@ -0,0 +1,21 @@ + + +

Configuring an Automated Backup Policy

+

Scenarios

When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB instance is created, you can customize the automated backup policy as required and then RDS backs up data based on the automated backup policy you configure.

+

RDS backs up data at the DB instance level, rather than the database level. If a database is faulty or data is damaged, you can restore it from backups. Backups are saved as packages in OBS buckets to ensure data confidentiality and durability. Since backing up data affects database read and write performance, the automated backup time window should be set to off-peak hours.

+
The automated backup policy is enabled by default as follows:
  • Retention period: 7 days
  • Time window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is configured based on UTC time and is adjusted for daylight saving time, which changes at different times depending on the time zone.
  • Backup cycle: Each day of the week by default
+
+
+

Constraints

  • The number of tables in a DB instance affects the backup speed. The maximum number of tables is 500,000.
  • The system verifies the connection to the DB instance when starting a full backup task. If either of the following conditions is met, the verification fails and a retry is automatically performed. If the retry fails, the backup will fail.
    • DDL operations are being performed on the DB instance.
    • The backup lock failed to be obtained from the DB instance.
    +
+
+

Modifying an Automated Backup Policy

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Backups & Restorations page, click Modify Backup Policy.

    • Retention Period is the number of days that your automated backups are saved for. Increasing the retention period will improve data reliability.
    • If you shorten the retention period, the new backup policy takes effect for all backup files. Any backup files that have expired, based on a newly configured retention period, will be deleted.
    • The backup retention period is the number of days you want automated full backups and binlog backups of your DB instance to be saved for. It ranges from 1–732 days. The backup time window is one hour. You are advised to select an off-peak time window for automated backups. By default, each day of the week is selected for Backup Cycle and you can change it. At least one day must be selected.
    +

  6. Click OK.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_08_0005.html b/docs/rds/umn/rds_08_0005.html new file mode 100644 index 000000000..8170652f7 --- /dev/null +++ b/docs/rds/umn/rds_08_0005.html @@ -0,0 +1,25 @@ + + +

Creating a Manual Backup

+

Scenarios

RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.

+

When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.

+
+
+

Constraints

  • The number of tables in a DB instance affects the backup speed. The maximum number of tables is 500,000.
  • The system verifies the connection to the DB instance when starting a full backup task. If either of the following conditions is met, the verification fails and a retry is automatically performed. If the retry fails, the backup will fail.
    • DDL operations are being performed on the DB instance.
    • The backup lock failed to be obtained from the DB instance.
    +
+
+

Method 1

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Create Backup in the Operation column.
  5. 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 consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    • The time required for creating a manual backup depends on the amount of data.
    +

  6. After a manual backup has been created, you can view and manage it on the Backup Management page.

    Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

    +

+
+

Method 2

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name and 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 consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    • The time required for creating a manual backup depends on the amount of data.
    +

  6. After a manual backup has been created, you can view and manage it on the Backup Management page.

    Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_08_0006.html b/docs/rds/umn/rds_08_0006.html new file mode 100644 index 000000000..824c2cbaf --- /dev/null +++ b/docs/rds/umn/rds_08_0006.html @@ -0,0 +1,38 @@ + + +

Downloading a Backup File

+

Scenarios

This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.

+

RDS for MySQL enables you to download full backup files.

+
+

Constraints

  • If the size of the backup data is greater than 400 MB, you are advised to use OBS Browser+ to download the backup data.
+
+

Method 1: Using OBS Browser+

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select Use OBS Browser+ for Download Method and click OK.

    1. Download OBS Browser+
    2. Decompress and install OBS Browser+.
    3. Log in to OBS Browser+.

      For details about how to log in to OBS Browser+, see Logging In to OBS Browser+ in the OBS Browser+ Operation Guide.

      +
    4. Disable certificate verification on OBS Browser+.

      For details on how to configure OBS Browser+, see Configuring the System in the OBS Browser+ Operation Guide.

      +

      The OBS bucket name displayed in the Download Backup File pane on the RDS console does not support certificate verification. OBS Browser+ certificate verification needs to be disabled before the external bucket can be added, and then it must be enabled again after the backup is downloaded.

      +
      +
    5. Add an external bucket.

      In the Add Bucket dialog box of OBS Browser+, select Add external bucket and enter the bucket name provided in step 2 "Add an External Bucket" on the RDS console.

      +

      For details about how to add external buckets, see Adding External Buckets in the OBS Browser+ Operation Guide.

      +
    6. Download the backup file.

      On the OBS Browser+ page, click the bucket that you added. In the search box on the right of OBS Browser+, enter the backup file name provided in step 3 "Download the Backup File" on the RDS console. In the search result, locate the target backup and download it.

      +
    7. After the backup is downloaded, enable OBS Browser+ certificate verification.
    +

  6. Follow the instructions provided in Restoring from Backup Files to a Self-Built MySQL Database to restore data locally as required.
+
+

Method 2: Using Current Browser

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select Use Current Browser for Download Method and click OK.
  6. Follow the instructions provided in Restoring from Backup Files to a Self-Built MySQL Database to restore data locally as required.
+
+

Method 3: Using Download URL

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

    A valid URL for downloading the backup data is displayed.

    +
    • You can use various download tools to download backup files.
    • You can also run the following command to download backup files:

      wget -O FILE_NAME --no-check-certificate "DOWNLOAD_URL"

      +

      The parameters in the command are as follows:

      +

      FILE_NAME: indicates the new backup file name after the download is successful. The original backup file name may be too long and exceed the maximum characters allowed by the client file system. You are advised to use the -O argument with wget to rename the backup file.

      +

      DOWNLOAD_URL: indicates the location of the backup file to be downloaded. If the location contains special characters, escape is required.

      +
    +

  6. Follow the instructions provided in Restoring from Backup Files to a Self-Built MySQL Database to restore data locally as required.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_08_0007.html b/docs/rds/umn/rds_08_0007.html new file mode 100644 index 000000000..3611ec319 --- /dev/null +++ b/docs/rds/umn/rds_08_0007.html @@ -0,0 +1,33 @@ + + +

Restoring from Backup Files to DB Instances

+

Scenarios

This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance level.

+

When you restore a DB instance from a backup file, a full backup file is downloaded from OBS and then restored to the DB instance at an average speed of 40 MB/s.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, select the backup to be restored and click Restore in the Operation column.

    Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

    +

  5. Select a restoration method and click OK.

    • Create New Instance

      The Create New Instance page is displayed.

      +
      • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
      • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
      • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
      +
    • Restore to Original
      1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +
      • If the DB instance for which the backup is created has been deleted, data cannot be restored to the original DB instance.
      • Restoring to the original DB instance will overwrite all existing data and the DB instance will be unavailable during the restoration process.
      +
      +
    • Restore to Existing
      1. Select "I acknowledge that restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +
      • If the target existing DB instance has been deleted, data cannot be restored to it.
      • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable.
      • To restore backup data to an existing DB instance, the selected DB instance must use the same DB engine and the same or a later version than the original DB instance.
      • Ensure that the storage space of the selected existing DB instance is greater than or equal to the storage space of the original DB instance. Otherwise, data will not be restored.
      +
      +
    +

  6. View the restoration result. The result depends on which restoration method was selected:

    • Create New Instance

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      +

      The new DB instance is independent from the original one. If you need read replicas to offload read pressure, create one or more for the new DB instance.

      +

      After the new instance is created, a full backup will be automatically triggered.

      +
    • Restore to Original

      On the Instances page, the status of the original DB instance changes from Restoring to Available. If the original DB instance contains read replicas, the read replica status is the same as the original DB instance status.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    • Restore to Existing

      On the Instances page, the status of the target existing DB instance changes from Restoring to Available. If the target existing DB instance contains read replicas, the read replica status is the same as the target existing DB instance status.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_08_0008.html b/docs/rds/umn/rds_08_0008.html new file mode 100644 index 000000000..c7d16044d --- /dev/null +++ b/docs/rds/umn/rds_08_0008.html @@ -0,0 +1,34 @@ + + +

Restoring a DB Instance to a Point in Time

+

Scenarios

You can restore from automated backups to a specified point in time.

+

RDS for MySQL supports restoration to a new, the original, or an existing DB instance.

+

When you enter the time point that you want to restore the DB instance to, RDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

+
+

Restoring a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
  6. Select the restoration date and time range, enter a time point within the selected time range, and select a restoration method. Then, click OK.

    • Create New Instance

      The Create New Instance page is displayed.

      +
      • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
      • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
      +
    • Restore to Original
      1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +

      Restoring to the original DB instance will overwrite all existing data and the DB instance will be unavailable during the restoration process.

      +
      +
    • Restore to Existing
      1. Select "I acknowledge that restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +
      • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable.
      • To restore backup data to an existing DB instance, the selected DB instance must use the same DB engine and the same or a later version than the original DB instance.
      • Ensure that the storage space of the selected DB instance is greater than or equal to the storage space of the original DB instance. Otherwise, data will not be restored.
      +
      +
    +

  7. View the restoration result. The result depends on which restoration method was selected:

    • Create New Instance

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      +

      The new DB instance is independent from the original one. If you need read replicas to offload read pressure, create one or more for the new DB instance.

      +

      After the new DB instance is created, a full backup will be automatically triggered.

      +
    • Restore to Original

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      +

      A new restoration time range is available. There will be a difference between the new and original time ranges. This difference reflects the duration of the restoration.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    • Restore to Existing

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_08_0009.html b/docs/rds/umn/rds_08_0009.html new file mode 100644 index 000000000..60d2f6b8e --- /dev/null +++ b/docs/rds/umn/rds_08_0009.html @@ -0,0 +1,20 @@ + + +

Replicating a Backup

+

Scenarios

This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.

+
+

Constraints

You can replicate backups and use them only within the same region.

+
+

Backup Retention Policy

  • RDS will delete automated backups when they expire or the DB instance for which the backups are created is deleted.
  • If you want to retain the automated backups for a long time, you can replicate them to generate manual backups, which will be always retained until you delete them.
  • If the storage occupied by manual backups exceeds the provisioned free backup storage, additional storage costs may incur.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

    Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

    +

  5. In the displayed dialog box, enter a new backup name and description and click OK.

    • 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 consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
    +

  6. After the new backup has been created, you can view and manage it on the Backup Management page.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_08_001.html b/docs/rds/umn/rds_08_001.html new file mode 100644 index 000000000..1a08f736e --- /dev/null +++ b/docs/rds/umn/rds_08_001.html @@ -0,0 +1,17 @@ + + +

Log Management

+
+ + diff --git a/docs/rds/umn/rds_08_0010.html b/docs/rds/umn/rds_08_0010.html new file mode 100644 index 000000000..633ae6def --- /dev/null +++ b/docs/rds/umn/rds_08_0010.html @@ -0,0 +1,18 @@ + + +

Deleting a Manual Backup

+

Scenarios

You can delete manual backups to free up backup storage.

+
+

Deleted manual backups cannot be recovered. Exercise caution when performing this operation.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

    The following backups cannot be deleted:

    +
    • Automated backups
    • Backups that are being restored
    • Backups that are being replicated
    +

  5. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_08_0011.html b/docs/rds/umn/rds_08_0011.html new file mode 100644 index 000000000..e92e8c495 --- /dev/null +++ b/docs/rds/umn/rds_08_0011.html @@ -0,0 +1,35 @@ + + +

Parameter Template Management

+
+ + diff --git a/docs/rds/umn/rds_08_0012.html b/docs/rds/umn/rds_08_0012.html new file mode 100644 index 000000000..10c4cd25d --- /dev/null +++ b/docs/rds/umn/rds_08_0012.html @@ -0,0 +1,19 @@ + + +

Comparing Parameter Templates

+

Scenarios

You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.

+

You can also compare default parameter templates that use the same DB engine to understand the differences of parameter settings.

+
+

Comparing Instance Parameters with a Parameter Template

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Compare above the parameter list.
  6. In the displayed dialog box, select a parameter template to be compared and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+

Comparing Parameter Templates

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
  5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_08_0013.html b/docs/rds/umn/rds_08_0013.html new file mode 100644 index 000000000..8b2540ddb --- /dev/null +++ b/docs/rds/umn/rds_08_0013.html @@ -0,0 +1,18 @@ + + +

Rebooting DB Instances or Read Replicas

+

Scenarios

You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can reboot a primary DB instance or a read replica on the management console.

+
+

Constraints

  • If the DB instance status is Abnormal, the reboot may fail.
  • Rebooting DB instances will cause service interruptions. During the reboot process, the DB instance status is Rebooting.
  • Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance, or click and then locate the target read replica. Choose More > Reboot in the Operation column.

    Alternatively, click the target DB instance on the Instances page to go to the Basic Information page. In the upper right corner, click Reboot.

    +

    For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.

    +

  5. In the displayed dialog box, click Yes.
  6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_08_0014.html b/docs/rds/umn/rds_08_0014.html new file mode 100644 index 000000000..ec78bfd38 --- /dev/null +++ b/docs/rds/umn/rds_08_0014.html @@ -0,0 +1,19 @@ + + +

Replicating a Parameter Template

+

Scenarios

You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template.

+

After a parameter template is replicated, it takes about 5 minutes before the new template is displayed.

+

Default parameter templates cannot be replicated, but you can create parameter templates based on the default ones.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

    Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

    +

  5. In the displayed dialog box, configure required information and click OK.

    • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
    • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    +

    After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_08_0015.html b/docs/rds/umn/rds_08_0015.html new file mode 100644 index 000000000..7b6120833 --- /dev/null +++ b/docs/rds/umn/rds_08_0015.html @@ -0,0 +1,16 @@ + + +

Resetting a Parameter Template

+

Scenarios

You can reset all parameters in a custom parameter template to their default settings.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
  5. Click Yes.
  6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
  7. View the status of the DB instance to which the parameter template is applied.

    If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.

    +
    • The DB instance reboot caused by instance class changes will not make parameter modifications take effect.
    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_08_0016.html b/docs/rds/umn/rds_08_0016.html new file mode 100644 index 000000000..4818d5f19 --- /dev/null +++ b/docs/rds/umn/rds_08_0016.html @@ -0,0 +1,17 @@ + + +

Modifying a Parameter Template Description

+

Scenarios

You can modify the description of a parameter template you have created.

+

You cannot modify the description of a default parameter template.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
  5. Enter a new description. You can click to submit or to cancel the modification.

    • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
    • After the modification is successful, you can view the new description in the Description column of the parameter template list.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_08_0017.html b/docs/rds/umn/rds_08_0017.html new file mode 100644 index 000000000..1c2b51bed --- /dev/null +++ b/docs/rds/umn/rds_08_0017.html @@ -0,0 +1,16 @@ + + +

Deleting a Parameter Template

+

Scenarios

You can delete a custom parameter template that is no longer in use.

+
+
  • Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
  • Default parameter templates cannot be deleted.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
  5. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_08_0019.html b/docs/rds/umn/rds_08_0019.html new file mode 100644 index 000000000..2e12fe835 --- /dev/null +++ b/docs/rds/umn/rds_08_0019.html @@ -0,0 +1,19 @@ + + +

Metrics and Alarms

+
+ + diff --git a/docs/rds/umn/rds_08_0020.html b/docs/rds/umn/rds_08_0020.html new file mode 100644 index 000000000..beb1daa67 --- /dev/null +++ b/docs/rds/umn/rds_08_0020.html @@ -0,0 +1,17 @@ + + +

Interconnection with CTS

+
+ + diff --git a/docs/rds/umn/rds_08_0021.html b/docs/rds/umn/rds_08_0021.html new file mode 100644 index 000000000..290e481cb --- /dev/null +++ b/docs/rds/umn/rds_08_0021.html @@ -0,0 +1,23 @@ + + +

Log Management

+
+ + diff --git a/docs/rds/umn/rds_08_0022.html b/docs/rds/umn/rds_08_0022.html new file mode 100644 index 000000000..2cc8766ed --- /dev/null +++ b/docs/rds/umn/rds_08_0022.html @@ -0,0 +1,16 @@ + + +

Selecting Displayed Items

+

Scenarios

You can customize which instance items are displayed on the Instances page.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click to edit columns displayed in the DB instance list.

    • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

      These default items cannot be deselected.

      +
    • In a single project, you can select up to 9 items: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, creation time, database port, storage type, and operation.
    +

+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_08_0042.html b/docs/rds/umn/rds_08_0042.html new file mode 100644 index 000000000..399608fcf --- /dev/null +++ b/docs/rds/umn/rds_08_0042.html @@ -0,0 +1,22 @@ + + +

Exporting a Parameter Template

+

Scenarios

  • You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Parameter Template.
  • You can export the parameter template information (parameter names, values, and descriptions) of a DB instance to a CSV file for viewing and analysis.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

    • Exporting to a custom template
      In the displayed dialog box, configure required information and click OK.
      • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
      • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
      +
      +
      +

      After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

      +
    • Exporting to a file
      The parameter template information (parameter names, values, and descriptions) of a DB instance is exported to a CSV file. In the displayed dialog box, enter the file name and click OK.

      The file name must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

      +
      +
      +
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_08_0044.html b/docs/rds/umn/rds_08_0044.html new file mode 100644 index 000000000..6ee6febf3 --- /dev/null +++ b/docs/rds/umn/rds_08_0044.html @@ -0,0 +1,51 @@ + + +

Restoring from Backup Files to a Self-Built MySQL Database

+

Scenarios

You can download backup files by referring to Downloading a Backup File and restore data from them.

+

Backup data cannot be restored to local databases that run the Windows operating system.

+

Only x86 packages of the open-source backup tool XtraBackup are supported. Therefore, you are advised to restore backup data to self-built databases on Arm-based ECSs by migrating data with DRS or exporting and importing data. For details, see Data Migration.

+
+
+

Prerequisites

When you restore data from backup files to self-built MySQL databases, ensure that the target MySQL version is later than or equal to the original MySQL version.

+

During data restoration, run the following command to view the restoration process:

+

ps -ef | grep mysql

+
+

Procedure

  1. Download the qpress RPM file qpress-11-1.el7.x86_64.rpm. Enterprise Linux 7 (CentOS 7, RHEL 7, Rocky Linux 7, and AlmaLinux 7) is used as an example.

    For details about RPM files of other OSs, see https://repo.percona.com/yum/release/.

    +

  2. Upload the qpress RPM file to the ECS.
  3. Install qpress on the ECS.

    rpm -ivh qpress-11-1.el7.x86_64.rpm

    +

  4. Download XtraBackup from the website, for example, percona-xtrabackup-24-2.4.9-1.el7.x86_64.rpm.

    +
    +

  5. Upload XtraBackup to the ECS.
  6. Install XtraBackup on the ECS.

    rpm -ivh percona-xtrabackup-24-2.4.9-1.el7.x86_64.rpm --nodeps --force

    +

  7. On the ECS, decompress the full backup file that has been downloaded.

    1. Create a temporary directory backupdir.

      mkdir backupdir

      +
    2. Decompress the package.

      xbstream -x -p 4 < ./Full backup file.qp -C ./backupdir/

      +
      • For MySQL 5.6 and 5.7, run innobackupex --parallel 4 --decompress ./backupdir.
      • For MySQL 8.0, run xtrabackup --parallel 4 --decompress --target-dir=./backupdir.
      +

      find ./backupdir/ -name '*.qp' | xargs rm -f

      +
    +

  8. Apply the log.

    • For MySQL 5.6 and 5.7, run innobackupex --apply-log ./backupdir.
    • For MySQL 8.0, run xtrabackup --prepare --target-dir=./backupdir.
    +

  9. Back up data.

    1. Stop MySQL database services.

      service mysql stop

      +

      For MySQL 5.7, run the following command to stop MySQL database services:

      +

      /bin/systemctl stop mysqld.service

      +
      +
    2. Back up the original database directory.

      mv /var/lib/mysql/data /var/lib/mysql/data_bak

      +
    3. Create a new database directory and change the permissions.

      mkdir /var/lib/mysql/data

      +

      chown mysql:mysql /var/lib/mysql/data

      +
    +

  10. Copy the full backup file and modify the directory permissions.

    • For MySQL 5.6 and 5.7, run innobackupex --defaults-file=/etc/my.cnf --copy-back ./backupdir.
    • For MySQL 8.0, run xtrabackup --defaults-file=/etc/my.cnf --copy-back --target-dir=./backupdir.
    +

    chown -R mysql:mysql /var/lib/mysql/data

    +

    Clear the content in the var/lib/mysql/data directory in advance.

    +
    +

  11. Start the database.

    service mysql start

    +

    For MySQL 5.7, run the following command to start the database:

    +

    /bin/systemctl start mysqld.service

    +
    +

  12. Log in to the database and view the restoration result.

    mysql -u -root

    +

    show databases

    +
    Figure 1 Viewing the restoration result
    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0000.html b/docs/rds/umn/rds_09_0000.html new file mode 100644 index 000000000..4d7a68b9b --- /dev/null +++ b/docs/rds/umn/rds_09_0000.html @@ -0,0 +1,43 @@ + + +

Working with RDS for PostgreSQL

+
+ + diff --git a/docs/rds/umn/rds_09_0023.html b/docs/rds/umn/rds_09_0023.html new file mode 100644 index 000000000..12a0b977a --- /dev/null +++ b/docs/rds/umn/rds_09_0023.html @@ -0,0 +1,54 @@ + + +

Migrating Data to RDS for PostgreSQL Using psql

+

Preparing for Data Migration

PostgreSQL supports logical backups. You can use the pg_dump logical backup function to export backup files and then import them to RDS using psql.

+

You can access RDS DB instances through an EIP or through an ECS.

+
+

Preparations

  1. Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through an EIP.
    • To connect to a DB instance through an ECS, you need to create an ECS first.

      For details about how to create and connect to an ECS, see section How Can I Create and Connect to an ECS?

      +
    • To connect to a DB instance through an EIP, you must:
      1. Bind an EIP to a DB instance. For details, see Binding an EIP.
      2. Ensure that the local device can access the EIP that has been bound to the DB instance.
      +
    +
  2. Install the PostgreSQL client on the prepared ECS or device.

    For details, see How Can I Install the PostgreSQL Client?

    +

    The PostgreSQL client version must be the same as the version of RDS for PostgreSQL. The PostgreSQL database or client will provide pg_dump and psql.

    +
    +
+
+

Exporting Data

Before migrating an existing PostgreSQL database to RDS, you need to export the PostgreSQL database.

+
  • 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.
+
+
  1. Log in to the ECS or the device that can access RDS.
  2. Use the pg_dump tool to export the source database into an SQL file.

    pg_dump --username=<DB_USER> --host=<DB_ADDRESS> --port=<DB_PORT> --format=plain --file=<BACKUP_FILE> <DB_NAME>

    +
    • 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.
    • DB_NAME indicates the name of the database to be migrated.
    +

    Enter the database password when prompted.

    +

    Example:

    +

    $ pg_dump --username=root --host=192.168.151.18 --port=5432 --format=plain --file=backup.sql my_db

    +

    Password for user root:

    +

    After this command is executed, a backup.sql file will be generated as follows:

    +

    [rds@localhost ~]$ ll backup.sql

    +
    -rw-r-----. 1 rds rds 2714 Sep 21 08:23 backup.sql
    +

+
+

Importing Data

  1. Log in to the ECS or the device that can access RDS.
  2. Ensure that the destination database to which data is to be imported exists.

    If the destination database does not exist, run the following command to create a database:

    +
    # psql --host=<RDS_ADDRESS> --port=<DB_PORT> --username=root --dbname=postgres -c "create database <DB_NAME>;"
    • RDS_ADDRESS indicates the IP address of the RDS DB instance.
    • DB_PORT indicates the RDS DB instance port.
    • DB_NAME indicates the name of the database to be imported.
    +
    +

  3. Import the exported file to RDS.

    # psql --host=<RDS_ADDRESS> --port=<DB_PORT> --username=root --dbname=<DB_NAME> --file=<BACKUP_DIR>/backup.sql

    +
    • RDS_ADDRESS indicates the IP address of the RDS DB instance.
    • DB_PORT indicates the RDS DB instance port.
    • DB_NAME indicates the name of the database to which data is to be imported. Ensure that the database exists.
    • BACKUP_DIR indicates the directory where the backup.sql file is stored.
    +

    Enter the password for the RDS DB instance when prompted.

    +

    Example:

    +

    # psql --host=172.16.66.198 --port=5432 --username=root --dbname=my_db --file=backup.sql

    +

    Password for user root:

    +

  4. View the import result.

    my_db=> \l my_db

    +

    In this example, the database named my_db has been imported.

    +
    my_db=> \l my_db
+List of databases
+Name  | Owner | Encoding | Collate     | Ctype       | Access privileges
+------+-------+----------+-------------+-------------+-----------
+my_db | root  | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
+(1 row)
    +

+
+
+
+
+
Parent topic: Data Migration
+
+
+ diff --git a/docs/rds/umn/rds_09_0024.html b/docs/rds/umn/rds_09_0024.html new file mode 100644 index 000000000..f5621601b --- /dev/null +++ b/docs/rds/umn/rds_09_0024.html @@ -0,0 +1,18 @@ + + +

Rebooting DB Instances or Read Replicas

+

Scenarios

You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can reboot a primary DB instance or a read replica on the management console.

+
+

Constraints

  • If the DB instance status is Abnormal, the reboot may fail.
  • Rebooting a DB instance will cause service interruptions. During this period, the DB instance status is Rebooting.
  • Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance, or click in the front of a DB instance and then locate the target read replica. Choose More > Reboot in the Operation column.

    Alternatively, click the target DB instance on the Instances page to go to the Basic Information page. In the upper right corner, click Reboot.

    +

    For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.

    +

  5. In the displayed dialog box, select a scheduled time, and click Yes.
  6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_09_0025.html b/docs/rds/umn/rds_09_0025.html new file mode 100644 index 000000000..3495928be --- /dev/null +++ b/docs/rds/umn/rds_09_0025.html @@ -0,0 +1,20 @@ + + +

Deleting a DB Instance or Read Replica

+

Scenarios

To release resources, you can delete DB instances or read replicas as required on the Instances page.

+
+

Constraints

  • DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are complete.
  • If you delete a DB instance, its automated backups are also deleted and you are no longer billed for them. Manual backups, however, are still retained and will generate additional costs.
+
  • If you delete a primary DB instance, its standby DB instance and read replicas (if any) are also deleted automatically. Exercise caution when performing this operation.
  • Deleted DB instances cannot be recovered and resources are released. Exercise caution when performing this operation. If you want to retain data, create a manual backup first before deleting the DB instance.
  • You can restore a DB instance that was deleted up to 7 days ago from the recycle bin. For details, see Recycling a DB Instance.
  • You can use a manual backup to restore a DB instance. For details, see Restoring from Backup Files to DB Instances.
+
+
+

Deleting a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the DB instance list later to confirm that the deletion was successful.
+
+

Deleting a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
  5. Locate the read replica to be deleted and click More > Delete in the Operation column.
  6. In the displayed dialog box, click Yes.
  7. Refresh the DB instance list later to check that the deletion is successful.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_09_0026.html b/docs/rds/umn/rds_09_0026.html new file mode 100644 index 000000000..e63f1d6bd --- /dev/null +++ b/docs/rds/umn/rds_09_0026.html @@ -0,0 +1,15 @@ + + +

Changing a Security Group

+

Scenarios

This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the primary DB instance will cause the security group of the standby DB instance to also be changed accordingly.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary DB instance or read replica.
  5. In the Connection Information area on the Basic Information page, click in the Security Group field.

    • To submit the change, click .
    • To cancel the change, click .
    +

  6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information page to view the results.
+
+
+
+
+
Parent topic: Data Security
+
+
+ diff --git a/docs/rds/umn/rds_09_0027.html b/docs/rds/umn/rds_09_0027.html new file mode 100644 index 000000000..879bbf21e --- /dev/null +++ b/docs/rds/umn/rds_09_0027.html @@ -0,0 +1,18 @@ + + +

Configuring an Automated Backup Policy

+

Scenarios

When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB instance is created, you can customize the automated backup policy as required and then RDS backs up data based on the automated backup policy you configure.

+

RDS backs up data at the DB instance level, rather than the database level. If a database is faulty or data is damaged, you can restore it from backups. Backups are saved as packages in OBS buckets to ensure data confidentiality and durability. Since backing up data affects database read and write performance, the automated backup time window should be set to off-peak hours.

+
The automated backup policy is enabled by default as follows:
  • Retention period: 7 days. Backup files that exceed the retention period will be deleted and cannot be restored.
  • Time window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is configured based on UTC time and is adjusted for daylight saving time, which changes at different times depending on the time zone.
  • Backup cycle: Each day of the week
+
+
+

Modifying an Automated Backup Policy

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Backups & Restorations page, click Modify Backup Policy.

    • Retention Period is the number of days that your automated backups are saved for. Increasing the retention period will improve data reliability.
    • If you shorten the retention period, the new backup policy takes effect for all backup files. The backup files that have expired will be deleted.
    • The backup retention period is the number of days you want automated full and incremental backups of your DB instance to be saved for. It ranges from 1–732 days. The backup time window is one hour. You are advised to select an off-peak time window for automated backups. By default, each day of the week is selected for Backup Cycle and you can change it. At least one day must be selected.
    +

  6. Click OK.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0028.html b/docs/rds/umn/rds_09_0028.html new file mode 100644 index 000000000..afce421ba --- /dev/null +++ b/docs/rds/umn/rds_09_0028.html @@ -0,0 +1,22 @@ + + +

Creating a Manual Backup

+

Scenarios

RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.

+

When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.

+
+
+

Method 1

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Create Backup in the Operation column.
  5. 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 consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    • The time required for creating a manual backup depends on the amount of data.
    +

  6. After a manual backup has been created, you can view and manage it on the Backup Management page.

    Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

    +

+
+

Method 2

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name and 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 consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    • The time required for creating a manual backup depends on the amount of data.
    +

  6. After a manual backup has been created, you can view and manage it on the Backup Management page.

    Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0029.html b/docs/rds/umn/rds_09_0029.html new file mode 100644 index 000000000..7a43ef059 --- /dev/null +++ b/docs/rds/umn/rds_09_0029.html @@ -0,0 +1,36 @@ + + +

Restoring a DB Instance to a Point in Time

+

Scenarios

You can restore from automated backups to a specified point in time.

+

RDS for PostgreSQL supports restoration to a new, the original, or an existing DB instance.

+

When you enter the time point that you want to restore the DB instance to, RDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
  6. Select the restoration date and time range, enter a time point within the selected time range, and select a restoration method. Then, click OK.

    • Create New Instance
      The Create New Instance page is displayed.
      • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
      • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
      • Other settings are the same as those of the original DB instance by default and can be modified. For details, see section Step 1: Create a DB Instance.
      +
      +
    +
    • Restore to Original
      1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +

      Restoring to the original DB instance will overwrite all existing data and the DB instance will be unavailable during the restoration process.

      +
      +
    • Restore to Existing
      1. Select "I acknowledge that restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +
      • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable.
      • To restore backup data to an existing DB instance, the selected DB instance must be in the same VPC as the original DB instance and must have the same DB engine and the same or later version than the original DB instance.
      • Ensure that the storage space of the selected DB instance is greater than or equal to the storage space of the original DB instance. Otherwise, data will not be restored.
      +
      +
    +

  7. View the restoration result. The result depends on which restoration method was selected:

    • Create New Instance

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      +

      The new DB instance is independent from the original one. If you need read replicas to offload read pressure, create one or more for the new DB instance.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    +
    • Restore to Original

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      +

      A new restoration time range is available. There will be a difference between the new and original time ranges. This difference reflects the duration of the restoration.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    • Restore to Existing

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0030.html b/docs/rds/umn/rds_09_0030.html new file mode 100644 index 000000000..2856d6b7f --- /dev/null +++ b/docs/rds/umn/rds_09_0030.html @@ -0,0 +1,31 @@ + + +

Restoring from Backup Files to RDS for PostgreSQL

+

Scenarios

This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance level.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, select the backup to be restored and click Restore in the Operation column.

    Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

    +

  5. Select a restoration method and click OK.

    • Create New Instance
      The Create New Instance page is displayed.
      • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
      • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
      • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
      +
      +
    • Restore to Original
      1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +
      • If the DB instance for which the backup is created has been deleted, data cannot be restored to the original DB instance.
      • Restoring to the original DB instance will overwrite all existing data and the DB instance will be unavailable during the restoration process.
      +
      +
    • Restore to Existing
      1. Select "I acknowledge that restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable during the restoration." and click Next.
      2. Confirm the information and click OK.
      +
      • If the target existing DB instance has been deleted, data cannot be restored to it.
      • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable.
      • To restore backup data to an existing DB instance, the selected DB instance must be in the same VPC as the original DB instance and must have the same DB engine and the same or later version than the original DB instance.
      • Ensure that the storage space of the selected DB instance is greater than or equal to the storage space of the original DB instance. Otherwise, data will not be restored.
      +
      +
    +

  6. View the restoration result. The result depends on which restoration method was selected:

    • Create New Instance

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      +

      The new DB instance is independent from the original one. If you need read replicas to offload read pressure, create one or more for the new DB instance.

      +

      After the new instance is created, a full backup will be automatically triggered.

      +
    +
    • Restore to Original

      On the Instances page, the status of the target existing DB instance changes from Restoring to Available. If the original existing DB instance contains read replicas, the read replica status is the same as the original DB instance status.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0031.html b/docs/rds/umn/rds_09_0031.html new file mode 100644 index 000000000..f72a77fb4 --- /dev/null +++ b/docs/rds/umn/rds_09_0031.html @@ -0,0 +1,38 @@ + + +

Downloading a Full Backup File

+

Scenarios

This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.

+

RDS for PostgreSQL enables you to download full backup files.

+
+

Constraints

  • If the size of the backup data is greater than 400 MB, you are advised to use OBS Browser+ to download the backup data.
+
+

Method 1: Using OBS Browser+

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select Use OBS Browser+ for Download Method and click OK.

    1. Download OBS Browser+
    2. Decompress and install OBS Browser+.
    3. Log in to OBS Browser+.

      For details about how to log in to OBS Browser+, see Logging In to OBS Browser+ in the OBS Browser+ Operation Guide.

      +
    4. Disable certificate verification on OBS Browser+.

      For details on how to configure OBS Browser+, see Configuring the System in the OBS Browser+ Operation Guide.

      +

      The OBS bucket name displayed in the Download Backup File pane on the RDS console does not support certificate verification. OBS Browser+ certificate verification needs to be disabled before the external bucket can be added, and then it must be enabled again after the backup is downloaded.

      +
      +
    5. Add an external bucket.

      In the Add Bucket dialog box of OBS Browser+, select Add external bucket and enter the bucket name provided in step 2 "Add an External Bucket" on the RDS console.

      +

      For details about how to add external buckets, see Adding External Buckets in the OBS Browser+ Operation Guide.

      +
    6. Download the backup file.

      On the OBS Browser+ page, click the bucket that you added. In the search box on the right of OBS Browser+, enter the backup file name provided in step 3 "Download the Backup File" of the RDS console. In the search result, locate the target backup and download it.

      +
    7. After the backup is downloaded, enable OBS Browser+ certificate verification.
    +

  6. Restore data locally as required. For details, see Restoring from Full Backup Files to a Self-Built PostgreSQL Database.
+
+

Method 2: Using Current Browser

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select Use Current Browser for Download Method and click OK.
  6. Restore data locally as required. For details, see Restoring from Full Backup Files to a Self-Built PostgreSQL Database.
+
+

Method 3: Using Download URL

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

    A valid URL for downloading the backup data is displayed.

    +
    • You can use various download tools to download backup files.
    • You can also run the following command to download backup files:

      wget -O FILE_NAME --no-check-certificate "DOWNLOAD_URL"

      +

      The parameters in the command are as follows:

      +

      FILE_NAME: indicates the new backup file name after the download is successful. The original backup file name may be too long and exceed the maximum characters allowed by the client file system. You are advised to use the -O argument with wget to rename the backup file.

      +

      DOWNLOAD_URL: indicates the location of the backup file to be downloaded. If the location contains special characters, escape is required.

      +
    +

  6. Restore data locally as required. For details, see Restoring from Full Backup Files to a Self-Built PostgreSQL Database.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0032.html b/docs/rds/umn/rds_09_0032.html new file mode 100644 index 000000000..13e93ba70 --- /dev/null +++ b/docs/rds/umn/rds_09_0032.html @@ -0,0 +1,20 @@ + + +

Replicating a Backup

+

Scenarios

This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.

+
+

Constraints

You can replicate backups and use them only within the same region.

+
+

Backup Retention Policy

  • RDS will delete automated backups when they expire or the DB instance for which the backups are created is deleted.
  • If you want to retain the automated backups for a long time, you can replicate them to generate manual backups, which will be always retained until you delete them.
  • If the storage occupied by manual backups exceeds the provisioned free backup storage, additional storage costs may incur.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

    Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

    +

  5. In the displayed dialog box, enter a new backup name and description and click OK.

    • 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 consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
    +

  6. After the new backup has been created, you can view and manage it on the Backup Management page.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0033.html b/docs/rds/umn/rds_09_0033.html new file mode 100644 index 000000000..69985d8bb --- /dev/null +++ b/docs/rds/umn/rds_09_0033.html @@ -0,0 +1,18 @@ + + +

Deleting a Manual Backup

+

Scenarios

You can delete manual backups to free up backup storage.

+
+

Deleted manual backups cannot be recovered. Exercise caution when performing this operation.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

    The following backups cannot be deleted:

    +
    • Automated backups
    • Backups that are being restored
    • Backups that are being replicated
    +

  5. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_09_0034.html b/docs/rds/umn/rds_09_0034.html new file mode 100644 index 000000000..e160c5cdb --- /dev/null +++ b/docs/rds/umn/rds_09_0034.html @@ -0,0 +1,35 @@ + + +

Parameter Template Management

+
+ + diff --git a/docs/rds/umn/rds_09_0035.html b/docs/rds/umn/rds_09_0035.html new file mode 100644 index 000000000..91c411d4f --- /dev/null +++ b/docs/rds/umn/rds_09_0035.html @@ -0,0 +1,19 @@ + + +

Comparing Parameter Templates

+

Scenarios

You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.

+

You can also compare default parameter templates that use the same DB engine to understand the differences of parameter settings.

+
+

Comparing Instance Parameters with a Parameter Template

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Compare above the parameter list.
  6. In the displayed dialog box, select a parameter template to be compared and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+

Comparing Parameter Templates

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
  5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_09_0036.html b/docs/rds/umn/rds_09_0036.html new file mode 100644 index 000000000..a4ac767ec --- /dev/null +++ b/docs/rds/umn/rds_09_0036.html @@ -0,0 +1,19 @@ + + +

Replicating a Parameter Template

+

Scenarios

You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template.

+

After a parameter template is replicated, it takes about 5 minutes before the new template is displayed.

+

Default parameter templates cannot be replicated, but you can create parameter templates based on the default ones.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

    Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

    +

  5. In the displayed dialog box, configure required information and click OK.

    • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
    • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    +

    After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_09_0037.html b/docs/rds/umn/rds_09_0037.html new file mode 100644 index 000000000..e322ba627 --- /dev/null +++ b/docs/rds/umn/rds_09_0037.html @@ -0,0 +1,16 @@ + + +

Resetting a Parameter Template

+

Scenarios

You can reset all parameters in a custom parameter template to their default settings.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
  5. Click Yes.
  6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
  7. View the status of the DB instance to which the parameter template is applied.

    If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.

    +
    • The DB instance reboot caused by instance class changes will not make parameter modifications take effect.
    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_09_0038.html b/docs/rds/umn/rds_09_0038.html new file mode 100644 index 000000000..a865566db --- /dev/null +++ b/docs/rds/umn/rds_09_0038.html @@ -0,0 +1,17 @@ + + +

Modifying a Parameter Template Description

+

Scenarios

You can modify the description of a parameter template you have created.

+

You cannot modify the description of a default parameter template.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
  5. Enter a new description. You can click to submit or to cancel the modification.

    • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
    • After the modification is successful, you can view the new description in the Description column of the parameter template list.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_09_0039.html b/docs/rds/umn/rds_09_0039.html new file mode 100644 index 000000000..dccada06d --- /dev/null +++ b/docs/rds/umn/rds_09_0039.html @@ -0,0 +1,16 @@ + + +

Deleting a Parameter Template

+

Scenarios

You can delete a custom parameter template that is no longer in use.

+
+
  • Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
  • Default parameter templates cannot be deleted.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
  5. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_09_0041.html b/docs/rds/umn/rds_09_0041.html new file mode 100644 index 000000000..08721a190 --- /dev/null +++ b/docs/rds/umn/rds_09_0041.html @@ -0,0 +1,19 @@ + + +

Metrics and Alarms

+
+ + diff --git a/docs/rds/umn/rds_09_0042.html b/docs/rds/umn/rds_09_0042.html new file mode 100644 index 000000000..dc4b6ec4d --- /dev/null +++ b/docs/rds/umn/rds_09_0042.html @@ -0,0 +1,17 @@ + + +

Interconnection with CTS

+
+ + diff --git a/docs/rds/umn/rds_09_0043.html b/docs/rds/umn/rds_09_0043.html new file mode 100644 index 000000000..c19f908b9 --- /dev/null +++ b/docs/rds/umn/rds_09_0043.html @@ -0,0 +1,48 @@ + + +

Creating or Deleting a Plugin

+

RDS provides the PostgreSQL plugin management solution for user root. Except the following plugins, you need to manually create other plugins by referring to this section.

+
  • auto_explain
  • passwordcheck
  • pg_profile_pro
  • pg_sql_history
  • wal2json
  • test_decoding
+

The PostgreSQL plugin takes effect at the database level, not globally. You need to manually create it on corresponding databases.

+

The latest minor versions of PostgreSQL 11, 12, 13, and Enhanced Edition allow the root user to create plugins (create extension) or delete plugins (drop extension).

+
+

Creating a Plugin

  1. Connect to the database database1 as user root and use template1 to create a database that can support the plugin.

    # psql --host=<RDS_ADDRESS> --port=<DB_PORT> --dbname=database1 --username=root -c "create database <DB_NAME> template template1;"

    +
    • RDS_ADDRESS indicates the IP address of the RDS DB instance.
    • DB_PORT indicates the RDS DB instance port.
    • DB_NAME indicates the name of the database to be created.
    +

    Enter the password of user root when prompted.

    +

    Create a database named my_extension_db that can support the plugin. Example:

    +

    # psql --host=192.168.6.141 --port=5432 --dbname=database1 --username=root -c "create database my_extension_db template template1;"

    +
    Password for user root:
+CREATE DATABASE
    +

    Note: If you are creating a database as a common user, log in to the created database as the common user and run the following command to grant all rights to user root:

    +

    GRANT ALL ON DATABASE db1 TO root;

    +

  2. Connect to the created database as user root and create a plugin.

    # psql --host=<RDS_ADDRESS> --port=<DB_PORT> --dbname=<DB_NAME> --username=root -c "select control_extension('create','<EXTENSION_NAME>');"

    +
    • RDS_ADDRESS indicates the IP address of the RDS DB instance.
    • DB_PORT indicates the RDS DB instance port.
    • DB_NAME indicates the name of the database to be created.
    • EXTENSION_NAME indicates the plugin name. For more information, see Supported Plugins.
    +

    Enter the password of user root when prompted.

    +

    Create the postgis plugin in the database my_extension_db. Example:

    +

    # psql --host=192.168.6.141 --port=5432 --dbname=my_extension_db --username=root -c "select control_extension('create','postgis');"

    +
    Password for user root: 
+      control_extension       
+------------------------------
+ create postgis successfully.
+(1 row)
    +

+
+

Deleting a Plugin

Connect to the database with a plugin created as user root and delete the plugin.

+

# psql --host=<RDS_ADDRESS> --port=<DB_PORT> --username=root --dbname=<DB_NAME> -c "select control_extension ('drop','<EXTENSION_NAME>');"

+
  • RDS_ADDRESS indicates the IP address of the RDS DB instance.
  • DB_PORT indicates the RDS DB instance port.
  • DB_NAME indicates the name of the database to be created.
  • EXTENSION_NAME indicates the plugin name. For more information, see Supported Plugins.
+

Enter the password of user root when prompted.

+

Example:

+

# psql --host=192.168.6.141 --port=5432 --dbname=my_extension_db --username=root -c "select control_extension('drop','postgis');"

+
Password for user root: 
+     control_extension      
+----------------------------
+ drop postgis successfully.
+(1 row)
+
+
+
+
+
Parent topic: Plugin Management
+
+
+ diff --git a/docs/rds/umn/rds_09_0044.html b/docs/rds/umn/rds_09_0044.html new file mode 100644 index 000000000..3de02c5be --- /dev/null +++ b/docs/rds/umn/rds_09_0044.html @@ -0,0 +1,96 @@ + + +

Tablespace Management

+

Scenarios

RDS provides the PostgreSQL tablespace management solution based on user root.

+
+

Creating a Tablespace

  1. Connect to the database as user root and create a tablespace.

    # psql --host=<RDS_ADDRESS> --port=<DB_PORT> --dbname=<DB_NAME> --username=root -c "select control_tablespace ('create', '<TABLESPACE_NAME>');"

    + +
    + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    RDS_ADDRESS

    +

    Indicates the IP address of the RDS DB instance.

    +

    DB_PORT

    +

    Indicates the port of the RDS DB instance.

    +

    DB_NAME

    +

    Indicates the database name.

    +

    TABLESPACE_NAME

    +

    Indicates the tablespace name.

    +
    +
    +

  2. Enter the password of user root when prompted.

    Log in to the my_db database and create the tbspc1 tablespace. Example:

    +

    # psql --host=192.168.6.141 --port=5432 --dbname=my_db --username=root -c "select control_tablespace('create', 'tbspc1');"

    +
    Password for user root:
+          control_tablespace          
+------------------------------    
+create tablespace tbspc1 successfully.   
+(1 row)
    +

    If the creation fails, view error logs of the DB instance.

    +

    To ensure performance, a maximum of 20 tablespaces can be created.

    +
    +

+
+

Deleting a Tablespace

  1. Connect to a database as user root and delete a tablespace.

    # psql --host=<RDS_ADDRESS> --port=<DB_PORT> --username=root --dbname=<DB_NAME> -c "select control_tablespace('drop', '<TABLESPACE _NAME>');"

    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    RDS_ADDRESS

    +

    Indicates the IP address of the RDS DB instance.

    +

    DB_PORT

    +

    Indicates the port of the RDS DB instance.

    +

    DB_NAME

    +

    Indicates the database name.

    +

    TABLESPACE_NAME

    +

    Indicates the tablespace name.

    +
    +
    +

  2. Enter the password of user root when prompted.

    Example:

    +

    # psql --host=192.168.6.141 --port=8635 --dbname=my_db --username=root -c "select control_tablespace('drop', 'tbspc1');"

    +
    Password for user root:
+         control_tablespace         
+----------------------------    
+drop tablespace tbspc1 successfully.   
+(1 row)
    +

    Before deleting the tablespace, ensure that it is empty. If the deletion fails, view error logs of the DB instance.

    +

+
+
+
+
+
Parent topic: Working with RDS for PostgreSQL
+
+
+ diff --git a/docs/rds/umn/rds_09_0045.html b/docs/rds/umn/rds_09_0045.html new file mode 100644 index 000000000..382e03139 --- /dev/null +++ b/docs/rds/umn/rds_09_0045.html @@ -0,0 +1,786 @@ + + +

Supported Plugins

+

The following table lists the plugins supported by the latest minor versions of RDS for PostgreSQL. You can use SELECT name FROM pg_available_extensions; to view the plugins supported by your DB instance.

+

Before using the mysql_fdw, oracle_fdw, pgsql-ogr-fdw, postgres_fdw, and tds_fdw plugins, ensure that the server IP addresses of the two PostgreSQL DB instances are in the same VPC and subnet.

+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Supported plugins

Plugin Name

+

PostgreSQL 9.5

+

PostgreSQL 9.6

+

PostgreSQL 10

+

PostgreSQL 11

+

PostgreSQL Enhanced Edition (1.0)

+

PostgreSQL 12

+

PostgreSQL 13

+

address_standardizer

+

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

3.0.0

+

3.1.0

+

address_standardizer_data_us

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

3.0.0

+

3.1.0

+

btree_gin

+

1.0

+

1.0

+

1.2

+

1.3

+

1.3

+

1.3

+

1.3

+

btree_gist

+

1.1

+

1.2

+

1.5

+

1.5

+

1.5

+

1.5

+

1.5

+

citext

+

1.1

+

1.3

+

1.4

+

1.5

+

1.5

+

1.6

+

1.6

+

cube

+

For details, see cube.

+

1.0

+

1.2

+

1.2

+

1.4

+

1.4

+

1.4

+

1.4

+

dblink

+

1.1

+

1.2

+

1.2

+

1.2

+

1.2

+

1.2

+

1.2

+

dict_int

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

dict_xsyn

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

earthdistance

+

For details, see earthdistance.

+

1.0

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

fuzzystrmatch

+

1.0

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

hll

+

2.12

+

2.12

+

2.12

+

2.12

+

2.12

+

2.14

+

2.15.1

+

hstore

+

1.3

+

1.4

+

1.4

+

1.5

+

1.5

+

1.6

+

1.7

+

intagg

+

1.0

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

intarray

+

1.0

+

1.2

+

1.2

+

1.2

+

1.2

+

1.2

+

1.3

+

isn

+

1.0

+

1.1

+

1.1

+

1.2

+

1.2

+

1.2

+

1.2

+

ltree

+

1.0

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

1.2

+

oracle_fdw

+

-

+

-

+

2.1.0

+

2.1.0

+

2.1.0

+

2.2.0

+

2.3.0

+

orafce

+

3.8.0

+

3.8.0

+

3.8.0

+

3.8.0

+

0

+

3.8.0

+

3.14.0

+

pg_cron

+

-

+

-

+

-

+

-

+

-

+

1.2.0

+

1.3.0

+

pg_hint_plan

+

1.1.5

+

1.2.0

+

1.3.0

+

1.3.5

+

1.3.5

+

1.3.7

+

1.3.7

+

pg_jieba

+

1.1.0

+

1.1.0

+

1.1.0

+

1.1.0

+

1.1.0

+

1.1.0

+

2.0.1

+

pg_pathman

+

1.5.8

+

1.5.8

+

1.5.8

+

1.5.8

+

1.5.8

+

1.5.12

+

1.5.12

+

pg_repack

+

1.4.6

+

1.4.6

+

1.4.6

+

1.4.6

+

1.4.6

+

1.4.6

+

1.4.6

+

pgrouting

+

-

+

-

+

-

+

3.1.0

+

3.1.0

+

3.1.0

+

3.1.3

+

pg_stat_statements

+

1.3

+

1.4

+

1.6

+

1.6

+

1.6

+

1.7

+

1.8

+

pg_trgm

+

1.1

+

1.3

+

1.3

+

1.4

+

1.4

+

1.4

+

1.5

+

pgcrypto

+

1.2

+

1.3

+

1.3

+

1.3

+

1.3

+

1.3

+

1.3

+

pgstattuple

+

-

+

-

+

1.5

+

1.5

+

1.5

+

1.5

+

1.5

+

plpgsql

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

postgis

+

For details, see postgis.

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

3.0.0

+

3.1.0

+

postgres_fdw

+

-

+

-

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

postgis_raster

+

Integrated to postgis

+

Integrated to postgis

+

Integrated to postgis

+

Integrated to postgis

+

Integrated to postgis

+

3.0.0

+

3.1.0

+

postgis_sfcgal

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

3.0.0

+

3.1.0

+

postgis_tiger_geocoder

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

3.0.0

+

3.1.0

+

postgis_topology

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

2.5.1

+

3.0.0

+

3.1.0

+

tablefunc

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

tds_fdw

+

-

+

-

+

-

+

2.0.1

+

2.0.1

+

2.0.1

+

2.0.2

+

timescaledb

+

For details, see timescaledb.

+

-

+

1.3.2

+

1.3.2

+

1.3.2

+

1.3.2

+

1.7.0

+

2.1.0

+

unaccent

+

1.0

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

uuid-ossp

+

1.0

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

1.1

+

wal2json

+

-

+

-

+

-

+

2.3

+

2.3

+

2.3

+

2.3

+

zhparser

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+

1.0

+
+
+

Plugin Description

  • postgis
    • When postgis is created, the following plugins are created at the same time:

      postgis

      +

      postgis_topology

      +

      fuzzystrmatch

      +

      postgis_tiger_geocoder

      +

      address_standardizer

      +

      address_standardizer_data_us

      +
    • After the postgis plugin is created on the primary DB instance, you need to disconnect the connection from the standby DB instance first and re-establish a connection to update the search_path setting.
    • For PostgreSQL Enhanced Edition DB instances, you need to set empty_is_null to OFF on the console before creating the postgis plugin.
    +
  • earthdistance

    To install the earthdistance plugin, you must install the cube plugin first.

    +
  • cube

    If the earthdistance plugin has been installed, deleting the cube plugin will cause the earthdistance plugin to be unavailable.

    +
  • timescaledb

    The timescaledb plugin does not support the TSL protocol. For more information, see APIs Not Supported by the timescaledb Plugin.

    +
  • wal2json

    This plugin is a logical replication plugin. You can directly use it without installing it through control_extension.

    +
+
+

APIs Not Supported by the timescaledb Plugin

  • add_compress_chunks_policy
  • add_drop_chunks_policy
  • add_reorder_policy
  • alter_job_schedule
  • compress_chunk
  • decompress_chunk
  • drop_chunks
  • interpolate
  • locf
  • move_chunk
  • remove_compress_chunks_policy
  • remove_drop_chunks_policy
  • remove_reorder_policy
  • reorder_chunk
  • set_integer_now_func
  • time_bucket_gapfill
+
+
+
+
+
Parent topic: Plugin Management
+
+
+ diff --git a/docs/rds/umn/rds_09_0046.html b/docs/rds/umn/rds_09_0046.html new file mode 100644 index 000000000..c9d272126 --- /dev/null +++ b/docs/rds/umn/rds_09_0046.html @@ -0,0 +1,17 @@ + + +

Plugin Management

+
+ + diff --git a/docs/rds/umn/rds_10_0000.html b/docs/rds/umn/rds_10_0000.html new file mode 100644 index 000000000..c8a2928bb --- /dev/null +++ b/docs/rds/umn/rds_10_0000.html @@ -0,0 +1,37 @@ + + +

Working with RDS for SQL Server

+
+ + diff --git a/docs/rds/umn/rds_10_0035.html b/docs/rds/umn/rds_10_0035.html new file mode 100644 index 000000000..ad5dc9034 --- /dev/null +++ b/docs/rds/umn/rds_10_0035.html @@ -0,0 +1,62 @@ + + +

Migrating Data to RDS for SQL Server Using SQL Server Management Studio

+

Preparing for Data Migration

You can access RDS DB instances through an EIP or ECS.

+
  1. Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through an EIP.
    • To connect to a DB instance through an ECS, you must first create an ECS.

      For details about how to create and connect to an ECS, see section How Can I Create and Connect to an ECS?

      +
    • To connect to a DB instance through an EIP, you must:
      1. Bind the EIP to the DB instance. For details, see Binding an EIP.
      2. Ensure that the local device can access the EIP that has been bound to the DB instance.
      +
    +
  2. Install the Microsoft SQL Server client on the ECS or the device.

    For details, see How Can I Install SQL Server Management Studio?

    +

    The SQL Server Management Studio version must be equal to or later than the Microsoft SQL Server DB engine version.

    +
    +
+
+

Exporting Data

Before migrating an existing Microsoft SQL Server database to RDS, you need to export the Microsoft SQL Server database.

+
  • 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.
+
+
  1. Log in to the ECS or device that can access RDS.
  2. Use SQL Server Management Studio to generate database object scripts such as tables and views.

    1. Use SQL Server Management Studio to connect to the Microsoft SQL Server database.
    2. On Object Explorer, expand Databases, right-click the database to be exported, and choose Tasks > Generate Scripts. The Generate and Publish Scripts window is displayed.
    3. Choose Choose Objects in the navigation pane on the left, select database objects to be exported, and click Next.
    4. Choose Set Scripting Options in the navigation pane on the left, click Save script to a specific location, and select a path for storing exported files from the File name drop-down list, and click Next.
      • If you select Single file, all objects will be stored in the same file.
      • If you select Single file per object, each object will be stored in its own file.
      +
      +
    5. Click Next.
    6. Click Finish.
    7. Use SQL Server Management Studio to open the exported SQL file or SQL files.
    8. Change USE [DATABASE] in the first line to USE [RDS database name] and save the change.
    +

    For details on generating scripts, see Generate and Publish Scripts Wizard.

    +
    +

  3. Use bcp to export data from the source database to a .txt file.

    Download and install the bcp first. The command for exporting data is as follows:

    +

    >bcp dbname.schema_name.table_name out C:\test\table_name.txt -n -S localhost -U username -b 2000

    +
    • out indicates the directory from which the data is imported.
    • -n indicates that the native (database) data types are used for performing bulk-copy operations.
    • -S indicates the address to be used by the bcp tool to connect to the Microsoft SQL Server DB instance.
    • -U indicates the database username.
    • -b indicates the lines of data imported in a batch.
    +

    Enter the database password when prompted.

    +

    Example:

    +
    C:\test>bcp test.dbo.t1 out c:\test\t1.txt -n -S localhost -U rdsuser -b 2000
+Enter password:
    +

    After this command is executed, a t1.txt file will be generated as follows:

    +
    C:\test>$ dir t1.txt
+2017/03/27  11:51         22 t1.txt
    +

    Repeat the preceding steps to export data from the other tables in the database.

    +

+
+

Importing Data

This section describes how to use an ECS or a device that can access RDS to connect to a DB instance and import the exported SQL file into RDS.

+

If the source database contains the full-text index, you need to create one on RDS.

+
+
  1. Import data through tools.

    Method 1: Use sqlcmd to import database objects.

    +

    The Microsoft SQL Server database or client provides sqlcmd.

    +

    >sqlcmd -S "server" -d database -U login_id -i inputfile

    +
    • -S indicates the IP address and port of the RDS DB instance.
    • -d indicates the name of the database to be imported.
    • -U indicates the username used to log in to the database.
    • -i indicates the SQL file to be executed.
    +

    Enter the database password when prompted.

    +

    Example:

    +
    >sqlcmd -S "10.65.60.79,8636" -d test -U rdsuser -i C:\test\objects.sql
+Enter password:
    +

    Method 2: Use bcp to import data.

    +

    >bcp dbname.schema_name.table_name in C:\test\table_name.txt -n -S Server -U username -b 2000

    +
    • in indicates the directory which the data is imported to.
    • -n indicates that the native (database) data types are used for performing bulk-copy operations.
    • -S indicates the address to be used by the bcp tool to connect to the Microsoft SQL Server DB instance.
    • -U indicates the database username.
    • -b indicates the lines of data imported in a batch.
    +

    Enter the database password when prompted.

    +

    Example:

    +
    C:\test>bcp test.dbo.t1 in c:\test\t1.txt -n -S "10.65.60.79,8636" -U rdsuser -b 2000
+Enter password:
    +

  2. Check the data import result.

    select * from sys.databases;
    +
    Figure 1 Data import result
    +

+
+
+
+
+
Parent topic: Data Migration
+
+
+ diff --git a/docs/rds/umn/rds_10_0055.html b/docs/rds/umn/rds_10_0055.html new file mode 100644 index 000000000..a4d177b68 --- /dev/null +++ b/docs/rds/umn/rds_10_0055.html @@ -0,0 +1,20 @@ + + +

Replicating a Backup

+

Scenarios

This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.

+
+

Constraints

You can replicate backups and use them only within the same region.

+
+

Backup Retention Policy

  • RDS will delete automated backups when they expire or the DB instance for which the backups are created is deleted.
  • If you want to retain the automated backups for a long time, you can replicate them to generate manual backups, which will be always retained until you delete them.
  • If the storage occupied by manual backups exceeds the provisioned free backup storage, additional storage costs may incur.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

    Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

    +

  5. In the displayed dialog box, enter a new backup name and description and click OK.

    • 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 consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
    +

  6. After the new backup has been created, you can view and manage it on the Backup Management page.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_10_0101.html b/docs/rds/umn/rds_10_0101.html new file mode 100644 index 000000000..797145a1a --- /dev/null +++ b/docs/rds/umn/rds_10_0101.html @@ -0,0 +1,18 @@ + + +

Deleting a Manual Backup

+

Scenarios

You can delete manual backups to free up backup storage.

+
+

Deleted manual backups cannot be recovered. Exercise caution when performing this operation.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

    The following backups cannot be deleted:

    +
    • Automated backups
    • Backups that are being restored
    • Backups that are being replicated
    +

  5. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_10_0102.html b/docs/rds/umn/rds_10_0102.html new file mode 100644 index 000000000..a57c80484 --- /dev/null +++ b/docs/rds/umn/rds_10_0102.html @@ -0,0 +1,35 @@ + + +

Parameter Template Management

+
+ + diff --git a/docs/rds/umn/rds_10_0103.html b/docs/rds/umn/rds_10_0103.html new file mode 100644 index 000000000..f503664e5 --- /dev/null +++ b/docs/rds/umn/rds_10_0103.html @@ -0,0 +1,19 @@ + + +

Comparing Parameter Templates

+

Scenarios

You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.

+

You can also compare default parameter templates that use the same DB engine to understand the differences of parameter settings.

+
+

Comparing Instance Parameters with a Parameter Template

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Compare above the parameter list.
  6. In the displayed dialog box, select a parameter template to be compared and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+

Comparing Parameter Templates

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
  5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

    • If their settings are different, the parameter names and values of both parameter templates are displayed.
    • If their settings are the same, no data is displayed.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_10_0104.html b/docs/rds/umn/rds_10_0104.html new file mode 100644 index 000000000..9e9f2ccde --- /dev/null +++ b/docs/rds/umn/rds_10_0104.html @@ -0,0 +1,19 @@ + + +

Replicating a Parameter Template

+

Scenarios

You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template.

+

After a parameter template is replicated, it takes about 5 minutes before the new template is displayed.

+

Default parameter templates cannot be replicated, but you can create parameter templates based on the default ones.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

    Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

    +

  5. In the displayed dialog box, configure required information and click OK.

    • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
    • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    +

    After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_10_0105.html b/docs/rds/umn/rds_10_0105.html new file mode 100644 index 000000000..c06959866 --- /dev/null +++ b/docs/rds/umn/rds_10_0105.html @@ -0,0 +1,16 @@ + + +

Resetting a Parameter Template

+

Scenarios

You can reset all parameters in a custom parameter template to their default settings.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
  5. Click Yes.
  6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
  7. View the status of the DB instance to which the parameter template is applied.

    If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.

    +
    • The DB instance reboot caused by instance class changes will not make parameter modifications take effect.
    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_10_0106.html b/docs/rds/umn/rds_10_0106.html new file mode 100644 index 000000000..3e8fbc2a5 --- /dev/null +++ b/docs/rds/umn/rds_10_0106.html @@ -0,0 +1,17 @@ + + +

Modifying a Parameter Template Description

+

Scenarios

You can modify the description of a parameter template you have created.

+

You cannot modify the description of a default parameter template.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
  5. Enter a new description. You can click to submit or to cancel the modification.

    • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
    • After the modification is successful, you can view the new description in the Description column of the parameter template list.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_10_0107.html b/docs/rds/umn/rds_10_0107.html new file mode 100644 index 000000000..270d7f338 --- /dev/null +++ b/docs/rds/umn/rds_10_0107.html @@ -0,0 +1,16 @@ + + +

Deleting a Parameter Template

+

Scenarios

You can delete a custom parameter template that is no longer in use.

+
+
  • Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
  • Default parameter templates cannot be deleted.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
  5. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_11_0004.html b/docs/rds/umn/rds_11_0004.html new file mode 100644 index 000000000..cddfdf8e9 --- /dev/null +++ b/docs/rds/umn/rds_11_0004.html @@ -0,0 +1,62 @@ + + +

Configuring the TDE Function

+

Transparent Data Encryption (TDE) encrypts data files and backup files using certificates to implement real-time I/O encryption and decryption. This function effectively protects the security of databases and data files.

+

Currently, the TDE function supports single and primary/standby DB instances of the Microsoft SQL Server editions listed in Table 1.

+ +
+ + + + + + + + + + + + + +
Table 1 SQL Server editions that support the TDE function

DB Instance Type

+

Editions Support for TDE

+

Primary/Standby (1/1)

+		 +
  • 2016 EE
  • 2017 SE
+

Single DB instances

+
  • 2016 EE
  • 2017 SE
+

Cluster

+
  • 2017 EE
+
+
+

Constraints

  1. If TDE has been enabled for a single DB instance, the instance cannot be changed to primary/standby DB instances.
  2. RDS for SQL Server currently does not support TDE certificate download. To restore data offline using the encrypted .bak file, perform the following operations:
    1. Disable TDE for the database. For details, see Configuring Database-Level TDE.
    2. Create a manual backup for the database.
    3. Restore data from the manual backup.
    4. Enable TDE for the database as required.
    +
  3. Enabling TDE improves data security but affects read and write performance of encrypted databases. Exercise caution when enabling TDE.
  4. To migrate on-premises encrypted databases to RDS SQL Server DB instances, you need to disable database-level TDE first.
  5. DB instances with the instance-level TDE function enabled cannot be restored from backups to existing DB instances.
  6. When enabling the instance-level TDE function or using the stored procedure rds_tde to enable or disable database-level TDE, you are advised not to perform the following operations:
    • Delete files from file groups in databases.
    • Delete databases.
    • Take databases offline
    • Split databases.
    • Convert databases or file groups to the READ ONLY state.
    • Run the ALTER DATABASE command.
    • Create backups.
    • Start backup for databases or database files.
    • Start restoration for databases or database files.
    +
+
+

Enabling Instance-Level TDE

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the DB Information area, click in the TDE field to enable TDE.
+
+

Configuring Database-Level TDE

Before enabling the database-level TDE function, ensure that the instance-level TDE function has been enabled.

+
+
  1. Connect to the target DB instance.
  2. Use the stored procedure rds_tde to enable, disable, or query the database-level TDE status.

    exec master.dbo.rds_tde DatabaseName,TDE_Action

    +
    • DatabaseName: indicates the target database name, which can be null.
    • TDE_Action:
      • The value -1 indicates that the database encryption status is queried.

        If DatabaseName is null, the encryption status of all databases is returned.

        +
      • The value 0 indicates that the TDE function is disabled.
      • The value 1 indicates that the TDE function is enabled.
      +
    +
    1. Enable TDE for database db1.

      exec master.dbo.rds_tde db1, 1

      +
      Figure 1 Enabling TDE
      +
    2. Disable TDE for database db1.

      exec master.dbo.rds_tde db1, 0

      +
      Figure 2 Disabling TDE
      +
    3. Query the TDE status of database db1.

      exec master.dbo.rds_tde db1, -1

      +
      Figure 3 Querying the TDE status (Enabled)
      +
      Figure 4 Querying the TDE status (Disabled)
      +
    4. Query the TDE status of all databases.

      exec master.dbo.rds_tde null, -1

      +
      Figure 5 Querying the TDE status of all databases
      +
    +

+
+
+
+
+
Parent topic: Data Security
+
+
+ diff --git a/docs/rds/umn/rds_11_0006.html b/docs/rds/umn/rds_11_0006.html new file mode 100644 index 000000000..79164d0e2 --- /dev/null +++ b/docs/rds/umn/rds_11_0006.html @@ -0,0 +1,18 @@ + + +

Rebooting DB Instances or Read Replicas

+

Scenarios

You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can reboot a primary DB instance or a read replica on the management console.

+
+

Constraints

  • If the database service status is abnormal, you can forcibly reboot the DB instance, but this will interrupt uncommitted transactions.
  • Rebooting DB instances will cause service interruptions. During the reboot process, the DB instance status is Rebooting.
  • Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance, or click and then locate the target read replica. Choose More > Reboot in the Operation column.

    Alternatively, click the target DB instance on the Instances page to go to the Basic Information page. In the upper right corner, click Reboot.

    +

    For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.

    +

  5. In the displayed dialog box, select a reboot mode. If you select Forceful, select the checkbox before Confirm forcible reboot and click Yes.
  6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_11_0009.html b/docs/rds/umn/rds_11_0009.html new file mode 100644 index 000000000..e16f09238 --- /dev/null +++ b/docs/rds/umn/rds_11_0009.html @@ -0,0 +1,24 @@ + + +

Configuring a Security Group Rule

+

Scenarios

A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a VPC.

+

This section describes how to create a security group to enable specific IP addresses and ports to access RDS.

+
  • When you attempt to connect to an RDS DB instance through an EIP, you need to configure an inbound rule for the security group associated with the DB instance.
  • Check whether the ECS and RDS DB instance are in the same security group.
    • If the ECS and RDS DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured.
    • If the ECS and RDS DB instance are in different security groups, you need to configure security group rules for them, separately.
      • RDS DB instance: Configure an inbound rule for the security group with which the RDS DB instance is associated.
      • ECS: The default security group rule allows all outgoing data packets. In this case, 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. ECSs and RDS DB instances can access each other if they are deployed in the same security group. After a security group is created, you can configure security group rules to control access from and to the DB instances in the security group.

+
  • By default, a tenant can create a maximum of 100 security groups.
  • By default, each security group can have a maximum of 50 security group rules.
  • One RDS instance can be associated only with one security group, but a security group can be associated with multiple RDS instances.
  • Too many security group rules will increase the first packet latency. You are advised to create no more than 50 rules for each security group.
  • To enable access to an RDS DB instance from resources outside the security group, you need to configure an inbound rule for the security group associated with the RDS DB instance.
+

If you use 0.0.0.0/0, RDS DB instances in the security group can be accessed from any IP address.

+
+
+

Procedure

  1. Log in to the management console.
  2. Under Network, click Virtual Private Cloud.
  3. In the navigation pane on the left, choose Access Control > Security Groups.
  4. On the Security Groups page, locate the target security group and click Manage Rule in the Operation column.
  5. On the displayed page, click Add Rule.
  6. In the displayed dialog box, set required parameters to add an inbound rule.
  7. Click OK.
+
+

+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_11_0010.html b/docs/rds/umn/rds_11_0010.html new file mode 100644 index 000000000..faec522b2 --- /dev/null +++ b/docs/rds/umn/rds_11_0010.html @@ -0,0 +1,26 @@ + + +

Creating a Manual Backup

+

Scenarios

RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.

+

When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.

+
+
+

Method 1

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Create Backup in the Operation column.
  5. In the displayed dialog box, enter a backup name, select a target database for which to create the backup, and enter a 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 consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    • The time required for creating a manual backup depends on the amount of data.
    +

    System databases are backed up by default.

    +
    +

  6. After a manual backup has been created, you can view and manage it on the Backup Management page.

    Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

    +

+
+

Method 2

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name, select a target database for which to create the backup, and enter a description. Then, click OK.

    • 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 consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    • The time required for creating a manual backup depends on the amount of data.
    +

    System databases are backed up by default.

    +
    +

  6. After a manual backup has been created, you can view and manage it on the Backup Management page.

    Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_11_0011.html b/docs/rds/umn/rds_11_0011.html new file mode 100644 index 000000000..571850788 --- /dev/null +++ b/docs/rds/umn/rds_11_0011.html @@ -0,0 +1,19 @@ + + +

Read Replicas

+
+ + diff --git a/docs/rds/umn/rds_11_0012.html b/docs/rds/umn/rds_11_0012.html new file mode 100644 index 000000000..903046870 --- /dev/null +++ b/docs/rds/umn/rds_11_0012.html @@ -0,0 +1,22 @@ + + +

Introducing Read Replicas

+

Introduction

RDS for MySQL supports read replicas.

+

In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To expand the DB instance read ability to offload read pressure on the database, you can create read replicas in a region. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses for the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.

+

A read replica uses a single-node architecture (without a slave node). Changes to the primary DB instance are also automatically synchronized to all associated read replicas through the native MySQL replication function. The synchronization is not affected by network latency. Read replicas and the primary DB instance must be in the same region but can be in different AZs.

+
+

Functions

  • Read replica specifications can be different from primary DB instance specifications. It is recommended that the read replica specifications be greater than or equal to the primary DB instance specifications to prevent long delay and high load.
  • Read replicas support system performance monitoring.

    RDS provides up to 20 monitoring metrics, including storage space, IOPS, the number of database connections, CPU usage, and network traffic. You can view these metrics to learn about the load on DB instances.

    +
  • Read replicas do not support automated backups or manual backups.
  • Read replicas do not support restoration from backups to new, existing, or original read replicas.
  • Data cannot be migrated to read replicas.
  • Read replicas do not support database creation and deletion.
  • Read replicas do not support database account creation.
+
+

Constraints

A maximum of five read replicas can be created for each primary DB instance.

+ +
+

Creating and Managing a Read Replica

+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_11_0013.html b/docs/rds/umn/rds_11_0013.html new file mode 100644 index 000000000..850c30f13 --- /dev/null +++ b/docs/rds/umn/rds_11_0013.html @@ -0,0 +1,36 @@ + + +

Downloading a Backup File

+

Scenarios

This section describes how to download a manual backup or an automated backup to a local device and restore data from the backup file.

+
+

Constraints

  • If the size of the backup data is greater than 400 MB, you are advised to use OBS Browser+ to download the backup data.
+
+

Method 1: Using OBS Browser+

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select Use OBS Browser+ for Download Method and click OK.

    1. Download OBS Browser+
    2. Decompress and install OBS Browser+.
    3. Log in to OBS Browser+.

      For details about how to log in to OBS Browser+, see Logging In to OBS Browser+ in the OBS Browser+ Operation Guide.

      +
    4. Disable certificate verification on OBS Browser+.

      For details on how to configure OBS Browser+, see Configuring the System in the OBS Browser+ Operation Guide.

      +

      The OBS bucket name displayed in the Download Backup File pane on the RDS console does not support certificate verification. OBS Browser+ certificate verification needs to be disabled before the external bucket can be added, then it must be enabled again after the backup is downloaded.

      +
      +
    5. Add an external bucket.

      In the Add Bucket dialog box of OBS Browser+, select Add external bucket and enter the bucket name provided in step 2 "Add an External Bucket" of the RDS console.

      +

      For details about how to add external buckets, see Adding External Buckets in the OBS Browser+ Operation Guide.

      +
    6. Download the backup file.

      On the OBS Browser+ page, click the bucket that you added. In the search box on the right of OBS Browser+, enter the backup file name displayed on Download the Backup File of the RDS console. In the search result, locate the target backup and download it.

      +

      Microsoft SQL Server allows you to download backup files of a specific database.

      +
    7. After the backup is downloaded, enable OBS Browser+ certificate verification.
    +

  6. Follow the instructions provided in Restoring from Backup Files to a Self-Built SQL Server Database to restore data locally as required.
+
+

Method 2: Using Download URL

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, locate the target backup to be downloaded and click Download in the Operation column.

    +

  5. In the displayed dialog box, select a method to download backup data.

    In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

    +

    For Microsoft SQL Server DB instances, the URLs of all the backup files are displayed. You can download the backup files of a specific database.

    +
    • You can use other download tools to download backup files.
    • You can also run the following command to download backup files:

      wget -O FILE_NAME --no-check-certificate "DOWNLOAD_URL"

      +

      Variables in the commands are as follows:

      +

      FILE_NAME: indicates the new backup file name after the download is successful. The original backup file name may be too long and exceed the maximum characters allowed by the client file system. You are advised to use the -O argument with wget to rename the backup file.

      +

      DOWNLOAD_URL: indicates the path of the backup file to be downloaded. If the path contains special characters, escape is required.

      +
    +

  6. Follow the instructions provided in Restoring from Backup Files to a Self-Built SQL Server Database to restore data locally as required.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_11_0015.html b/docs/rds/umn/rds_11_0015.html new file mode 100644 index 000000000..e83c40b87 --- /dev/null +++ b/docs/rds/umn/rds_11_0015.html @@ -0,0 +1,16 @@ + + +

Managing a Read Replica

+

Entering the Management Interface Through a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Basic Information page.
+
+

Entering the Management Interface Through a Primary DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
  5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
+
+

Deleting a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the DB instance list, click in front of a DB instance, locate the read replica to be deleted, and choose More > Delete in the Operation column.
+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_11_0022.html b/docs/rds/umn/rds_11_0022.html new file mode 100644 index 000000000..9d0f2bc2a --- /dev/null +++ b/docs/rds/umn/rds_11_0022.html @@ -0,0 +1,34 @@ + + +

Restoring a DB Instance to a Point in Time

+

Scenarios

You can restore from automated backups to a specified point in time.

+

RDS for Microsoft SQL Server supports restoration to a new, the original, or an existing DB instance.

+

If you delete a database or modify some records in a database at a specified time, you only need to restore the database instead of restoring the whole DB instance. You can also restore databases to a point in time as required.

+

When you enter the time point that you want to restore the DB instance to, RDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
  6. In the displayed dialog box, configure required information and click OK.

    1. Select the time range, select or enter a time point within the acceptable range.
    2. Select a restoration method.
      • Create New Instance

        The Create New Instance page is displayed.

        +
        • The DB engine of the new DB instance is the same as that of the original DB instance and cannot be changed.
        • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
        • Other settings are the same as those of the original DB instance by default and can be modified. For details, see section Step 1: Create a DB Instance.
        +
      • Restore to Original
        • Restoring to the original DB instance will overwrite data on it and cause the original DB instance to be unavailable during the restoration.
        +
        +
      • Restore to Existing
        • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable.
        • To restore backup data to an existing DB instance, the selected DB instance must be in the same VPC as the original DB instance and must have the same DB engine and the same or later version than the original DB instance.
        • Ensure that the storage space of the selected DB instance is greater than or equal to the storage space of the original DB instance. Otherwise, data will not be restored.
        • DB instances with the TDE function enabled cannot be restored from backups to existing DB instances.
        +
        +

        Select an existing DB instance and click Next.

        +
      +
    3. Select the databases to be restored. You can rename these databases as required. If you do not enter a new name, the original database name will be used.
      • The new database names must be different from each other and must be different from the original database names.
      • The new database names cannot contain the following fields (case-insensitive): rdsadmin, master, msdb, tempdb, model, and resource.
      • Each database name consists of 1 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
      +
      +
    +

  7. View the restoration result. The result depends on which restoration method was selected:

    • Create New Instance

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      +

      The new DB instance is independent from the original one.

      +
    • Restore to Original

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      +

      A new restoration time range is available. There will be a difference between the new and original time ranges. This difference reflects the duration of the restoration.

      +
    • Restore to Existing

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      +
    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_11_0023.html b/docs/rds/umn/rds_11_0023.html new file mode 100644 index 000000000..3e70cc0b8 --- /dev/null +++ b/docs/rds/umn/rds_11_0023.html @@ -0,0 +1,32 @@ + + +

Restoring from Backup Files to RDS for SQL Server

+

Scenarios

This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Backups & Restorations page, locate the target backup and click Restore in the Operation column.

    Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

    +

  5. In the displayed dialog box, configure required information and click OK.

    1. Select a restoration method and click OK.
      • Create New Instance
        The Create New Instance page is displayed.
        • The DB engine of the new DB instance is the same as that of the original DB instance and cannot be changed.
        • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
        • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
        +
        +
      • Restore to Original
        • If the DB instance for which the backup is created has been deleted, data cannot be restored to the original DB instance.
        • Restoring to the original DB instance will overwrite data on it and cause the original DB instance to be unavailable during the restoration.
        +
        +
      • Restore to Existing
        • Restoring to an existing DB instance will overwrite data on it and cause the existing DB instance to be unavailable.
        • To restore backup data to an existing DB instance, the selected DB instance must be in the same VPC as the original DB instance and must have the same DB engine and the same or later version than the original DB instance.
        • Ensure that the storage space of the selected DB instance is greater than or equal to the storage space of the original DB instance. Otherwise, data will not be restored.
        • DB instances with the TDE function enabled cannot be restored from backups to existing DB instances.
        +
        +

        Select an existing DB instance and click Next.

        +
      +
    2. Select the databases to be restored. You can rename these databases as required. If you do not enter a new name, the original database name will be used.
      • The new database names must be different from each other and must be different from the original database names.
      • The new database names cannot contain the following fields (case-insensitive): rdsadmin, master, msdb, tempdb, model, and resource.
      • Each database name consists of 1 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
      +
      +
    +

  6. View the restoration result. The result depends on which restoration method was selected:

    • Create New Instance

      A new DB instance is created using the backup data. The status of the DB instance changes from Creating to Available.

      +

      The new DB instance is independent from the original one. If you need read replicas to offload read pressure, create one or more for the new DB instance.

      +
    • Restore to Original

      On the Instances page, the status of the target existing DB instance changes from Restoring to Available. If the target existing DB instance contains read replicas, the read replica status is the same as the target existing DB instance status.

      +

      After the restoration is complete, a full backup will be automatically triggered.

      +
    • Restore to Existing

      On the Instances page, the status of the DB instance changes from Restoring to Available.

      +
    +

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_11_0030.html b/docs/rds/umn/rds_11_0030.html new file mode 100644 index 000000000..fe501a212 --- /dev/null +++ b/docs/rds/umn/rds_11_0030.html @@ -0,0 +1,20 @@ + + +

Deleting a DB Instance or Read Replica

+

Scenarios

To release resources, you can delete DB instances or read replicas as required on the Instances page.

+
+

Constraints

  • DB instances cannot be deleted when operations are being performed on them. They can be deleted only after the operations are complete.
  • If you delete a DB instance, its automated backups are also deleted and you are no longer billed for them. Manual backups, however, are still retained and will generate additional costs.
+
  • If you delete a primary DB instance, its standby DB instance and read replicas (if any) are also deleted automatically. Exercise caution when performing this operation.
  • Deleted DB instances cannot be recovered and resources are released. Exercise caution when performing this operation. If you want to retain data, create a manual backup first before deleting the DB instance.
  • You can restore a DB instance that was deleted up to 7 days ago from the recycle bin. For details, see Recycling a DB Instance.
  • You can use a manual backup to restore a DB instance. For details, see Restoring from Backup Files to DB Instances.
+
+
+

Deleting a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the DB instance list later to confirm that the deletion was successful.
+
+

Deleting a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
  5. Locate the read replica to be deleted and click More > Delete in the Operation column.
  6. In the displayed dialog box, click Yes.
  7. Refresh the DB instance list later to check that the deletion is successful.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_11_0031.html b/docs/rds/umn/rds_11_0031.html new file mode 100644 index 000000000..2f7cb5585 --- /dev/null +++ b/docs/rds/umn/rds_11_0031.html @@ -0,0 +1,18 @@ + + +

Configuring an Automated Backup Policy

+

Scenarios

When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB instance is created, you can customize the automated backup policy as required and then RDS backs up data based on the automated backup policy you have set.

+

RDS automatically backs up data at the DB instance level. If a database is faulty or data is damaged, you can restore it from backups to ensure data reliability. Backups are saved as packages in OBS buckets to ensure data confidentiality and durability. Since backing up data affects the database read and write performance, you are advised to set the automated backup time window to off-peak hours.

+
The default automated backup policy is as follows:
  • Retention period: 7 days
  • Time window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is configured based on UTC time and is adjusted for daylight saving time, which changes at different times depending on the time zone.
  • Backup cycle: Each day of the week
+
+
+

Modifying an Automated Backup Policy

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Backups & Restorations page, click Modify Backup Policy.

    • Retention Period refers to the number of days that your automated backups can be retained. Increasing the retention period will improve data reliability.
    • If you shorten the retention period, the new backup policy takes effect for all backup files. The backup files that have expired will be deleted.
    • The backup retention period indicates the number of days you want automated full and incremental backups of your DB instance to be retained. It ranges from 1–732 days. The backup time window is one hour. You are advised to select an off-peak time window for automated backups. By default, each day of the week is selected for Backup Cycle and you can change it. At least one day must be selected.
    +

  6. Click OK.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_11_0032.html b/docs/rds/umn/rds_11_0032.html new file mode 100644 index 000000000..93e9b8472 --- /dev/null +++ b/docs/rds/umn/rds_11_0032.html @@ -0,0 +1,15 @@ + + +

Changing a Security Group

+

Scenarios

This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the primary DB instance will cause the security group of the standby DB instance to also be changed accordingly.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary DB instance or read replica.
  5. In the Connection Information area on the Basic Information page, click in the Security Group field.

    • To submit the change, click .
    • To cancel the change, click .
    +

  6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information page to view the results.
+
+
+
+
+
Parent topic: Data Security
+
+
+ diff --git a/docs/rds/umn/rds_add_read_replica_pg.html b/docs/rds/umn/rds_add_read_replica_pg.html new file mode 100644 index 000000000..1399417e5 --- /dev/null +++ b/docs/rds/umn/rds_add_read_replica_pg.html @@ -0,0 +1,125 @@ + + +

Creating a Read Replica

+

Scenarios

Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.

+
+

You can create read replicas as needed.

+

A maximum of five read replicas can be created for a primary DB instance.

+

The specifications of read replicas must be greater than or equal to the specifications of the current primary DB instance.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click Create Read Replica in the Operation column.

    Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

    +

  5. On the displayed page, configure information about the DB instance and click Next.

    +

    + + + + + + + + + + + + + + + + + + + +
    Table 1 Basic information

    Parameter

    +

    Description

    +

    Region

    +

    By default, read replicas are in the same region as the primary DB instance.

    +

    DB Instance Name

    +

    Must start with a letter and consist of 4 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).

    +

    DB Engine

    +

    Same as the DB engine of the primary DB instance by default and cannot be changed.

    +

    DB Engine Version

    +

    Same as the DB engine version of the primary DB instance by default and cannot be changed.

    +

    AZ

    +

    RDS allows you to deploy primary DB instances and read replicas in a single AZ or across AZs to improve reliability.

    +
    +
    + +
    + + + + + + + + + + + + + + + + +
    Table 2 Instance specifications

    Parameter

    +

    Description

    +

    Instance Class

    +

    Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and maximum IOPS.

    +

    For details about instance classes, see section DB Instance Classes.

    +

    +

    +

    +

    After a DB instance is created, you can change its CPU and memory. For details, see section Changing a DB Instance Class.

    +

    +

    Storage Type

    +

    Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

    +
    • Common I/O: uses the SATA disk type that supports a maximum throughput of 90 MB/s.
    • Ultra-high I/O: uses the SSD disk type that supports a maximum throughput of 350 MB/s.
    +

    Storage Space

    +

    Contains the file system overhead required for inode, reserved block, and database operation.

    +

    By default, storage space of a read replica is the same as that of the primary DB instance.

    +

    Disk Encryption

    +
    • Disable: indicates the encryption function is disabled.
    • Enable: indicates the encryption function is enabled. Security is improved but system performance is affected.

      Key Name: indicates the tenant key. You can select an existing key or create a new one.

      +
      NOTE:
      • Once the DB instance is created, you cannot modify the disk encryption status or change the key. The backup data stored in OBS is not encrypted.
      • After an RDS DB instance is created, do not disable or delete a key that is currently in use. Otherwise, RDS will be unavailable and data cannot be restored.
      • For details about how to create a key, see the "Creating a CMK" section in the Key Management Service User Guide.
      +
      +
    +
    +
    + +
    + + + + + + + + + + + + + +
    Table 3 Network

    Parameter

    +

    Description

    +

    VPC

    +

    Same as the primary DB instance's VPC.

    +

    Subnet

    +

    Same as the primary DB instance's subnet. A floating IP address is automatically assigned when you create a read replica. You can also enter an unused floating IP address in the subnet CIDR block. After the read replica is created, you can change the floating IP address.

    +

    Security Group

    +

    Same as the primary DB instance's VPC.

    +
    +
    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. After a read replica has been created, you can view and manage it on the Instances page by clicking on the left of the DB instance to which it belongs.

    Alternatively, click the target DB instance. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.

    +

    +

+
+

Follow-up Operations

Managing a Read Replica

+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_change_database_port.html b/docs/rds/umn/rds_change_database_port.html new file mode 100644 index 000000000..b908f8186 --- /dev/null +++ b/docs/rds/umn/rds_change_database_port.html @@ -0,0 +1,23 @@ + + +

Changing a Database Port

+

Scenarios

This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the primary DB instance will cause the database port of the standby DB instance to also be changed accordingly.

+
+

Constraints

When the database port of a DB instance is being changed, you cannot:

+
  • Bind an EIP to the DB instance.
  • Delete the DB instance.
  • Create a backup for the DB instance.
  • Restore from backup data or from a specific point in time to the original DB instance.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance or click first and then click the target read replica.
  5. In the Connection Information area on the Basic Information page, click in the Database Port field.

    A MySQL database can use ports 2100 to 9500.

    +

    +
    +
    • To submit the change, click .
      • In the dialog box, click Yes.
        1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
        2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will be rebooted.
        3. This process takes 1-5 minutes.
        +
      • In the dialog box, click No to cancel the modification.
      +
    • To cancel the change, click .
    +

  6. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_configuration.html b/docs/rds/umn/rds_configuration.html new file mode 100644 index 000000000..7420b0b77 --- /dev/null +++ b/docs/rds/umn/rds_configuration.html @@ -0,0 +1,31 @@ + + +

Modifying Parameters

+

You can modify parameters in a custom parameter template to optimize RDS database performance.

+

You can only change parameter values in custom parameter templates. You cannot change the parameter values in default parameter templates. When you change parameter values in a custom parameter template, the changes take effect for all DB instances that the parameter template applies to.

+

When you modify a parameter, the time when the modification takes effect depends on the type of the parameter.

+

The RDS console displays the statuses of DB instances that the parameter template applies to. For example, if the DB instance has not yet used the latest modifications made to its parameter template, its status is Parameter change. Pending reboot. Manually reboot the DB instance for the latest modifications to take effect for that DB instance.

+

RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly, the database startup may fail. If this happens, you can re-configure the custom parameter template based on the settings of the default parameter template.

+
+

Modifying Parameter Template Parameters

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  5. On the Parameters page, modify parameters as required.

    For parameter description details, see Suggestions on MySQL Parameter Tuning.

    +

    Available operations are as follows:

    +
    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +

  6. After the parameter values are modified, you can click View Change History to view the details.
  7. The modifications do not take effect until you apply the parameter template to your DB instances. For details, see Applying a Parameter Template.
  8. View the status of the DB instance to which the parameter template was applied.

    If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.

    +
    • The DB instance reboot caused by instance class changes will not make parameter modifications take effect.
    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
    +

+
+

Modifying Instance Parameters

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

    Check the value in the Effective upon Reboot column.
    • If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.
      • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
      • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
      +
    • If the value is No, the modifications take effect immediately.
    +
    +
    +
    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +

    After parameters are modified, you can click Change History to view parameter modification details.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_download_sql_auditing_log.html b/docs/rds/umn/rds_download_sql_auditing_log.html new file mode 100644 index 000000000..6627cdd4b --- /dev/null +++ b/docs/rds/umn/rds_download_sql_auditing_log.html @@ -0,0 +1,85 @@ + + +

Downloading SQL Audit Logs

+

If you enable the SQL audit function, all SQL operations will be logged, and you can download audit logs to view details. By default, the SQL audit function is disabled. Enabling this function may affect performance.

+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose SQL Audits.
  6. On the displayed page, select a time range in the upper right corner, select SQL audit logs to be downloaded in the list, and click Download above the list to download SQL audit logs in batches.

    Alternatively, select an audit log and click Download in the Operation column to download an individual SQL audit log.

    +

  7. The following figure shows the SQL audit log content. For field descriptions, see Table 1.

    Figure 1 MySQL audit logs
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Audit log field description

    Parameter

    +

    Description

    +

    record_id

    +

    ID of a single audit log record.

    +

    connection_id

    +

    ID of the session executed by the record, which is the same as the ID in the show processlist command output.

    +

    connection_status

    +

    Session status, which is usually the returned error code of a statement. If a statement is successfully executed, the value 0 is returned.

    +

    name

    +

    Recorded type name. Generally, DML and DDL operations are QUERY, connection and disconnection operations are CONNECT and QUIT, respectively.

    +

    timestamp

    +

    Recorded UTC time.

    +

    command_class

    +

    SQL command type. The value is the parsed SQL type, for example, select or update. (This field does not exist if the connection is disconnected.)

    +

    sqltext

    +

    Executed SQL statement content. (This field does not exist if the audit connection is disconnected.)

    +

    user

    +

    Login account.

    +

    host

    +

    Login host. The value is localhost for local login and is empty for remote login.

    +

    external_user

    +

    External username.

    +

    ip

    +

    IP address of the remotely-connected client. The local IP address is empty.

    +

    default_db

    +

    Default database on which SQL statements are executed.

    +
    +
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0000.html b/docs/rds/umn/rds_faq_0000.html new file mode 100644 index 000000000..e134dec13 --- /dev/null +++ b/docs/rds/umn/rds_faq_0000.html @@ -0,0 +1,35 @@ + + +

FAQs

+
+ + diff --git a/docs/rds/umn/rds_faq_0001.html b/docs/rds/umn/rds_faq_0001.html new file mode 100644 index 000000000..10f987a46 --- /dev/null +++ b/docs/rds/umn/rds_faq_0001.html @@ -0,0 +1,13 @@ + + +

What Should I Pay Attention to When Using RDS?

+
  1. DB instance operating systems (OSs) are invisible to you. Your applications can access a database only through an IP address and a port.
  2. The backup files stored in Object Storage Service (OBS) and the Elastic Cloud Server (ECS) used by RDS are invisible to you. They are visible only to the RDS instance management system.
  3. Before viewing the DB instance list, ensure that the region is the same as the region where the DB instance is purchased.
  4. Precautions after purchasing RDS:

    After purchasing RDS DB instances, you do not need to perform basic database O&M operations, such as applying HA and security patches. However, you must still pay attention to:

    +
    1. Whether the CPU, input/output operations per second (IOPS), and space of the RDS DB instance are sufficient. If any of these becomes insufficient, change the CPU/Memory or scale up the DB instance.
    2. Whether the performance of the RDS DB instances is adequate, a large number of slow query SQL statements exist, SQL statements need to be optimized, or any indexes are redundant or missing.
    +
+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0002.html b/docs/rds/umn/rds_faq_0002.html new file mode 100644 index 000000000..cea13451f --- /dev/null +++ b/docs/rds/umn/rds_faq_0002.html @@ -0,0 +1,12 @@ + + +

What Is the Availability of RDS DB Instances?

+

Calculation formula for RDS DB instance availability:

+

DB instance availability = (1 – Failure duration/Total service duration) × 100%

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0003.html b/docs/rds/umn/rds_faq_0003.html new file mode 100644 index 000000000..4aefb4e08 --- /dev/null +++ b/docs/rds/umn/rds_faq_0003.html @@ -0,0 +1,11 @@ + + +

Can I Use a Template to Create DB Instances?

+

Currently, DB instance cannot be created using a template.

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0004.html b/docs/rds/umn/rds_faq_0004.html new file mode 100644 index 000000000..59ca486b9 --- /dev/null +++ b/docs/rds/umn/rds_faq_0004.html @@ -0,0 +1,85 @@ + + +

What Are the Differences Between RDS and Other Database Solutions?

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Differences between RDS and other database solutions

Function

+

RDS

+

Self-Built Database Service

+

Service availability

+

For details, see Elastic Cloud Service User Guide.

+

Requires self-guarantee, primary/standby relationship setup, and RAID setup.

+

Data reliability

+

For details, see Elastic Volume Service User Guide.

+

Requires self-guarantee, primary/standby relationship setup, and RAID setup.

+

System security

+

Defends against Anti-DDoS attacks and promptly repairs database security vulnerabilities.

+

Requires procurement of expensive devices and software, as well as manual detection and repair of security vulnerabilities.

+

Database backup

+

Automated backup

+

You need to find backup storage space by yourself and periodically check whether backup data can be restored.

+

Hardware and software investment

+

Supports on-demand pricing without hardware and software investment.

+

Requires large investment in database servers.

+

System hosting

+

Not required.

+

The hosting cost is high.

+

Maintenance cost

+

Not required.

+

Full-time Database Administrators (DBAs) are required for maintenance, leading to high manpower costs.

+

Deployment and scaling

+

Supports elastic scaling, fast deployment, and on-demand enabling.

+

Requires procurement, deployment, and coordination of hardware.

+

Resource utilization

+

Bills users based on the resources actually used, resulting in high resource utilization.

+

Peak resource utilization is considered, leading to low resource usage.

+
+
+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0005.html b/docs/rds/umn/rds_faq_0005.html new file mode 100644 index 000000000..c181697d1 --- /dev/null +++ b/docs/rds/umn/rds_faq_0005.html @@ -0,0 +1,11 @@ + + +

Will My RDS DB Instances Be Affected by Other User Instances?

+

No. Your RDS DB instances and resources are isolated from other users' DB instances.

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0006.html b/docs/rds/umn/rds_faq_0006.html new file mode 100644 index 000000000..6e5c8b364 --- /dev/null +++ b/docs/rds/umn/rds_faq_0006.html @@ -0,0 +1,11 @@ + + +

How Many DB Instances Can Run on RDS?

+

There are no limitations on the number of DB instances running on RDS.

+
+
+
+
Parent topic: Resource and Disk Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0007.html b/docs/rds/umn/rds_faq_0007.html new file mode 100644 index 000000000..61f7d6a18 --- /dev/null +++ b/docs/rds/umn/rds_faq_0007.html @@ -0,0 +1,13 @@ + + +

How Many Databases Can Run on an RDS DB Instance?

+

The maximum number of databases that can run on an RDS DB instance depends on the DB engine settings.

+

If there are enough CPU, memory, and storage resources, there are no limitations to the number of databases running on a DB instance. However, the number of tables in the databases affects the backup speed. If the number of tables exceeds 500,000, the backup will fail.

+
  • MySQL allows you to create numerous databases and tables. For details, see the official MySQL documentation.
  • PostgreSQL allows you to create numerous databases and database accounts.
  • Microsoft SQL Server allows you to create a maximum of 100 databases and numerous database accounts.
+
+
+
+
Parent topic: Resource and Disk Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0008.html b/docs/rds/umn/rds_faq_0008.html new file mode 100644 index 000000000..856a6bb3e --- /dev/null +++ b/docs/rds/umn/rds_faq_0008.html @@ -0,0 +1,12 @@ + + +

What Can I Do About Slow Respond of Websites When They Use RDS?

+

To solve this problem:

+
  • Check the performance of RDS DB instances on the RDS console.
  • Compare the database connection status of local databases and RDS DB instances. This problem depends on web applications.
+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0011.html b/docs/rds/umn/rds_faq_0011.html new file mode 100644 index 000000000..b113a8c43 --- /dev/null +++ b/docs/rds/umn/rds_faq_0011.html @@ -0,0 +1,14 @@ + + +

How Can I Identify Data Corruption?

+
  • Data tampering

    Lots of security measures are provided to ensure that only authenticated users have permissions to perform operations on database table records. Database tables can be accessed only through specific database ports.

    +

    Verifying package during primary/standby synchronization can prevent data tampering. MySQL uses the InnoDB storage engine to prevent data from being damaged.

    +
  • DB instance servers may be powered off suddenly, causing database page corruption and database rebooting failures.

    If a primary DB instance becomes faulty, RDS switches to the standby DB instance within 1 to 5 minutes to provide services for you. Databases cannot be accessed during a failover. You must configure automatic reconnection between your applications and RDS to make sure that your applications are available after the failover.

    +
+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0012.html b/docs/rds/umn/rds_faq_0012.html new file mode 100644 index 000000000..84827ad3e --- /dev/null +++ b/docs/rds/umn/rds_faq_0012.html @@ -0,0 +1,14 @@ + + +

Why Is a Table or Data Missing from My Database?

+

RDS does not delete or perform any operations on any user data. If this problem occurs, check if there have been any misoperations and restore the data from backup files, if necessary.

+

Check for misoperations: If the SQL audit function has been enabled, you can view data execution records in audit logs.

+

Restore data using backup files:

+
  • Use the RDS restoration function.
  • Import the backup data to RDS through an ECS.
+
+
+
+
Parent topic: Backup and Restoration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0013.html b/docs/rds/umn/rds_faq_0013.html new file mode 100644 index 000000000..2d93d05c0 --- /dev/null +++ b/docs/rds/umn/rds_faq_0013.html @@ -0,0 +1,11 @@ + + +

Can Multiple ECSs Connect to the Same RDS DB Instance?

+

Multiple ECSs can connect to the same RDS DB instance as long as the capability limits of a database are not exceeded.

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0014.html b/docs/rds/umn/rds_faq_0014.html new file mode 100644 index 000000000..79b17fe33 --- /dev/null +++ b/docs/rds/umn/rds_faq_0014.html @@ -0,0 +1,11 @@ + + +

What Happens to Database Backups After an RDS DB Instance Is Deleted?

+

When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.

+
+
+
+
Parent topic: Backup and Restoration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0015.html b/docs/rds/umn/rds_faq_0015.html new file mode 100644 index 000000000..579f33537 --- /dev/null +++ b/docs/rds/umn/rds_faq_0015.html @@ -0,0 +1,11 @@ + + +

Will My Backups Be Deleted If I Delete My Cloud Account?

+

If your cloud account is deleted, both your automated and manual backups are deleted.

+
+
+
+
Parent topic: Backup and Restoration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0016.html b/docs/rds/umn/rds_faq_0016.html new file mode 100644 index 000000000..13e771bcb --- /dev/null +++ b/docs/rds/umn/rds_faq_0016.html @@ -0,0 +1,13 @@ + + +

Are My RDS DB Instances Available When Scaling?

+

Currently, you can scale up storage space and change the CPU or memory of a DB instance.

+
  • When storage space is being scaled up, RDS DB instances are still available and services are not affected. However, you cannot delete or reboot DB instances that are being scaled.
  • When the CPU or memory of DB instances is being changed, the network is intermittently disconnected once or twice within a few seconds. (For Microsoft SQL Server 2017 Enterprise Edition, you need to stop services first and then change the CPU or memory of DB instances.) For primary/standby DB instances, a failover may occur and services may be briefly interrupted. Changing the CPU or memory takes 5 to 15 minutes.

    After you change the CPU or memory, the DB instances will reboot and services will be interrupted. Therefore, select off-peak hours to perform this operation. Rebooting a DB instance will clear the cached memory in it. You are advised to reboot it during off-peak hours.

    +
+
+ + diff --git a/docs/rds/umn/rds_faq_0018.html b/docs/rds/umn/rds_faq_0018.html new file mode 100644 index 000000000..5546b1d35 --- /dev/null +++ b/docs/rds/umn/rds_faq_0018.html @@ -0,0 +1,14 @@ + + +

Can an External Server Access the RDS Database?

+

DB Instance Bound with an EIP

For a DB instance that has an EIP bound, you can access it through the EIP.

+
+

DB Instance Not Bound with an EIP

  • Enable a VPN in a VPC and use the VPN to connect to the RDS DB instance.
  • Create an RDS and an ECS in the same VPC and access RDS through the ECS.
+
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0019.html b/docs/rds/umn/rds_faq_0019.html new file mode 100644 index 000000000..fd2a1fcdb --- /dev/null +++ b/docs/rds/umn/rds_faq_0019.html @@ -0,0 +1,14 @@ + + +

What Do I Do If the Number of RDS Database Connections Reaches the Upper Limit?

+

The number of database connections indicates the number of applications that can be simultaneously connected to a database, and is irrelevant to the maximum number of users allowed by your applications or websites.

+

If there is an excessive number of database connections, applications may fail to be connected, and the full and incremental backups may fail, affecting services.

+

Fault Locating

  1. Check whether applications are connected, optimize the connections, and release unnecessary connections.
  2. Check the specifications and scale them up if needed.
  3. Check whether any metrics are abnormal and whether any alarms are generated on the Cloud Eye console. Cloud Eye monitors database metrics, such as the CPU usage, memory usage, storage space usage, and database connections, and allows you to set alarm policies to identify risks in advance if any alarms are generated. For details, see the Cloud Eye User Guide.
+
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0020.html b/docs/rds/umn/rds_faq_0020.html new file mode 100644 index 000000000..aafa8bcf3 --- /dev/null +++ b/docs/rds/umn/rds_faq_0020.html @@ -0,0 +1,22 @@ + + +

What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?

+

Perform the following steps to identify the problem:

+
  1. Check whether the ECS and RDS DB instances are located in the same VPC.

    • If they are in the same VPC, go to 2.
    • If they are in different VPCs, create an ECS in the VPC in which the RDS DB instance is located.
    +

  2. Check whether a security group has been added to the ECS.

    • If a security group has been added, check whether the rules are configured correctly.

      For MySQL DB instances, see the security group description in Step 1: Create a DB Instance. Then, go to 3.

      +

      For PostgreSQL DB instances, see the security group description in Step 1: Create a DB Instance. Then, go to 3.

      +

      For Microsoft SQL Server DB instances, see the security group description in Step 1: Create a DB Instance. Then, go to 3.

      +
    • If no security group has been added, go to the VPC console from the ECS details page and click Security Groups to add a security group.
    +

  3. On the ECS, check whether the RDS DB instance port can be connected.

    The default port of RDS for MySQL is 3306.

    +

    The default port of RDS for PostgreSQL is 5432.

    +

    The default RDS for Microsoft SQL Server port number is 1433.

    +
    telnet <IP address> {port number}
    +
    • If the ECS can connect to the RDS DB instance port, the network between the ECS and the RDS DB instance is normal and no further action is required.
    • If the ECS still cannot connect to the port, contact technical support.
    +

+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0021.html b/docs/rds/umn/rds_faq_0021.html new file mode 100644 index 000000000..05b4b6b08 --- /dev/null +++ b/docs/rds/umn/rds_faq_0021.html @@ -0,0 +1,18 @@ + + +

What Should I Do If a Database Client Problem Causes a Connection Failure?

+

Troubleshoot RDS connection failures caused by a client problem by checking the following items:

+
  1. ECS Security Policy

    In Windows, check whether the RDS instance port is enabled in the Windows security policy. In Linux, run iptables to check whether the RDS DB instance port is enabled in firewall settings.

    +
  2. Application Configuration

    Check whether the connection address, port parameter configuration, and JDBC connection parameter configuration are correct.

    +
  3. Username or Password

    Check whether the username or password is correct if an error similar to the following occurs during RDS DB connection:

    +
    • [Warning] Access denied for user 'username'@'yourIp' (using password: NO)
    • [Warning] Access denied for user 'username'@'yourIp' (using password: YES)
    • Login failed for user 'username'
    +
+

If the problem persists, contact post-sales technical support.

+
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0022.html b/docs/rds/umn/rds_faq_0022.html new file mode 100644 index 000000000..0e9c01ea1 --- /dev/null +++ b/docs/rds/umn/rds_faq_0022.html @@ -0,0 +1,15 @@ + + +

What Should I Do If an RDS Database Problem Causes a Connection Failure?

+

Check whether any of the following problems occurred on the RDS DB instance.

+
  1. The RDS DB instance is not properly connected.

    Solution: Check the connection. If you connect to the RDS DB instance through a private network, the ECS and DB instance must be in the same VPC and the DB instance can be accessed only through an ECS in the same VPC. If you connect to the RDS DB instance through a public network, the ECS and DB instance can be in different VPCs.

    +
  2. The maximum number of connections has been reached.

    Solution: Use RDS resource monitoring to check if the CPU usage and the number of current connections are abnormal. If either of them has reached the maximum, reboot, disconnect, or scale up the class of the RDS DB instance.

    +
  3. The DB instance is abnormal. For example, the RDS DB instance fails to be rebooted, the system is faulty, or the instance or table is locked.

    Solution: Reboot the RDS DB instance to see if the problem is resolved. If the problem persists, contact post-sales technical support.

    +
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0023.html b/docs/rds/umn/rds_faq_0023.html new file mode 100644 index 000000000..04832d5e8 --- /dev/null +++ b/docs/rds/umn/rds_faq_0023.html @@ -0,0 +1,11 @@ + + +

How Do My Applications Access an RDS DB Instance in a VPC?

+

Ensure that the ECS in which your applications are located is in the same VPC as the RDS DB instance. If the ECS and the RDS DB instance are in different VPCs, modify the VPC route table and network access control list (ACL) to ensure that the ECS can access the RDS DB instance.

+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0024.html b/docs/rds/umn/rds_faq_0024.html new file mode 100644 index 000000000..4a54668c9 --- /dev/null +++ b/docs/rds/umn/rds_faq_0024.html @@ -0,0 +1,12 @@ + + +

Do Applications Need to Support Reconnecting to the RDS DB Instance Automatically?

+

It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the database to increase service availability and continuity.

+

To reduce resource consumption and improve performance, configure your applications to connect to the database using a persistent connection.

+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0025.html b/docs/rds/umn/rds_faq_0025.html new file mode 100644 index 000000000..89541f40e --- /dev/null +++ b/docs/rds/umn/rds_faq_0025.html @@ -0,0 +1,13 @@ + + +

What Types of DB Engines Does RDS Support for Importing Data?

+
  • Exporting or importing data between DB engines of the same type is called homogeneous database export or import.
  • Exporting or importing data between DB engines of different types is called heterogeneous database export or import. For example, import data from Oracle to DB engines supported by RDS.

    Generally, data cannot be exported or imported between heterogeneous databases due to the different data formats involved. However, if the data formats are compatible, table data can, in theory, be migrated between them.

    +

    Third-party software is usually required for data replication to export and import between heterogeneous databases. For example, you can use a third-party tool to export table records from Oracle into a .txt file. Then, you can use LOAD statements to import the exported table records to a DB engine supported by RDS.

    +
+
+
+
+
Parent topic: Database Migration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0026.html b/docs/rds/umn/rds_faq_0026.html new file mode 100644 index 000000000..5f63282b7 --- /dev/null +++ b/docs/rds/umn/rds_faq_0026.html @@ -0,0 +1,12 @@ + + +

Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?

+

The mysqldump or pg_dump tool is easy to use for data migration. However, when you use this tool, the server is stopped for a long period of time during data migration. Only use these tools when there is not much data to migrate or if stopping the server for a long period of time is not an issue.

+

RDS is compatible with source database services. The procedure for migrating data from your database to RDS is similar to the procedure for migrating data from one database server to another.

+
+
+
+
Parent topic: Database Migration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0027.html b/docs/rds/umn/rds_faq_0027.html new file mode 100644 index 000000000..ed882992e --- /dev/null +++ b/docs/rds/umn/rds_faq_0027.html @@ -0,0 +1,25 @@ + + +

How Can I Install the MySQL Client?

+

MySQL provides client installation packages for different OSs on its official website. MySQL 5.6 is used as an example. Download the MySQL 5.6 client installation package or other versions of the packages. The following procedure illustrates how to obtain the required installation package and install the MySQL client into a Red Hat Linux system.

+

Procedure

  1. Obtain the installation package.

    Find the link to the required version on the download page. MySQL-client-5.6.31-1.el6.x86_64.rpm is used as an example in the following figure.

    +
    Figure 1 Procedure
    +

    Click URL to download the installation package.

    +
    +
    +

  2. Upload the installation package to the ECS.

    1. When you create an ECS, select an OS, such as Red Hat 6.6, and bind an EIP to it.
    2. Use a remote connection tool to connect to the ECS through the bound EIP and upload the installation package to the ECS.
    +

  3. Run the following command to install the MySQL client:

    Sudo rpm -ivh MySQL-client-5.6.31-1.el6.x86_64.rpm
    +
    • If there are any conflicts during the installation, add the replacefiles parameter to the command and try to install the client again. Example:
      rpm -ivh --replacefiles MySQL-client-5.6.31-1.el6.x86_64.rpm
      +
    +
    • If a message is displayed prompting you to install a dependency package, you can add the nodeps parameter to the command and install the client again. Example:
      rpm -ivh --nodeps MySQL-client-5.6.31-1.el6.x86_64.rpm
      +
    +
    +

+
+
+
+
+
Parent topic: Client Installation
+
+
+ diff --git a/docs/rds/umn/rds_faq_0029.html b/docs/rds/umn/rds_faq_0029.html new file mode 100644 index 000000000..6d1a38bd6 --- /dev/null +++ b/docs/rds/umn/rds_faq_0029.html @@ -0,0 +1,26 @@ + + +

How Can I Install the PostgreSQL Client?

+

PostgreSQL provides client installation packages and the required dynamic shared library packages for different OSs on its official website.

+

Ensure that the database client matches the DB engine version of your RDS PostgreSQL DB instances.

+
+

This following uses PostgreSQL 9.5 in Red Hat Linux 6 as an example to describe how to obtain the required installation package and complete the installation.

+

Procedure

  1. Obtain the PostgreSQL client installation package.

    Find the link to the required version on the download page. postgresql95 is used as an example in the following figure.

    +
    Figure 1 Downloading the PostgreSQL client installation package
    +

  2. Obtain the dynamic shared library package required for the PostgreSQL client.

    Find the link to the required version on the download page. postgresql95-libs is used as an example in the following figure.

    +
    Figure 2 Downloading the dynamic shared library package
    +

  3. Upload the installation and dynamic shared library packages to the ECS.

    1. When you create an ECS, select an OS, such as Red Hat 6.6, and bind an EIP to it.
    2. Use a remote connection tool to connect to the ECS through the bound EIP and upload the installation package and dynamic dependency package to the ECS.
    +

  4. Run the following command to install the PostgreSQL client:

    sudo rpm -ivh postgresql95-9.5.7-1PGDG.rhel6.x86_64.rpm postgresql95-libs-9.5.7-1PGDG.rhel6.x86_64.rpm
    +
    • If there are any conflicts during the installation, add the replacefiles parameter to the command and try to install the client again. Example:
      rpm -ivh --replacefiles postgresql95-9.5.7-1PGDG.rhel6.x86_64.rpm postgresql95-libs-9.5.7-1PGDG.rhel6.x86_64.rpm
      +
    • If a message is displayed prompting you to install a dependency package, you can add the nodeps parameter to the command and install the client again. Example:
      rpm -ivh --nodeps postgresql95-9.5.7-1PGDG.rhel6.x86_64.rpm postgresql95-libs-9.5.7-1PGDG.rhel6.x86_64.rpm
      +
    +
    +

+
+
+
+
+
Parent topic: Client Installation
+
+
+ diff --git a/docs/rds/umn/rds_faq_0031.html b/docs/rds/umn/rds_faq_0031.html new file mode 100644 index 000000000..16af13569 --- /dev/null +++ b/docs/rds/umn/rds_faq_0031.html @@ -0,0 +1,19 @@ + + +

What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?

+

In the following cases, inappropriate parameter settings cause the database to be unavailable:

+
  • Parameter value ranges are related to DB instance specifications.

    The maximum values of shared_buffers and max_connections are related to the DB instance physical memory. If you set these parameters inappropriately, the database will be unavailable.

    +
  • Parameter association is incorrect.
    • If log_parser_stats, log_planner_stats, or log_executor_stats is enabled, you must disable log_statement_stats. Otherwise, the database is unavailable.
    • max_connections, autovacuum_max_workers, and max_worker_processes must meet the following requirements. Otherwise, the database is unavailable.

      max_connections value + autovacuum_max_workers value + max_worker_processes value + 1 < 8388607

      +
    +
+

For additional details, visit the PostgreSQL official website.

+
+

Solution:

+
  1. Log in to the RDS console and query the logs to locate the incorrectly configured parameters.
  2. On the Configuration page, change parameters to default values and reboot the database.
  3. Configure the incorrect parameter values and restore other parameters to their original default values.
+
+
+
+
Parent topic: Database Parameter Modification
+
+
+ diff --git a/docs/rds/umn/rds_faq_0032.html b/docs/rds/umn/rds_faq_0032.html new file mode 100644 index 000000000..670a7ff48 --- /dev/null +++ b/docs/rds/umn/rds_faq_0032.html @@ -0,0 +1,13 @@ + + +

How Can I Install SQL Server Management Studio?

+

Procedure

  1. Obtain the SQL Server Management Studio installation package.

    Visit the Microsoft website and download the installation package, for example, SQL Server Management Studio 18.0.

    +

  2. Upload the installation package to the ECS.
  3. Double-click the installation package and complete the installation as instructed.
+
+
+
+
+
Parent topic: Client Installation
+
+
+ diff --git a/docs/rds/umn/rds_faq_0034.html b/docs/rds/umn/rds_faq_0034.html new file mode 100644 index 000000000..31ff8017b --- /dev/null +++ b/docs/rds/umn/rds_faq_0034.html @@ -0,0 +1,16 @@ + + +

Why Did the New Password Not Take Effect After I Reset the Administrator Password?

+

Possible Causes

You may have restored from a backup before you reset the administrator password.

+
+

Locating Method

Check whether the DB instance was restored after you reset the administrator password.

+
+

Solution

Log in to the RDS console and reset the administrator password again. For details, see section Resetting the Administrator Password.

+
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0035.html b/docs/rds/umn/rds_faq_0035.html new file mode 100644 index 000000000..b4755b83f --- /dev/null +++ b/docs/rds/umn/rds_faq_0035.html @@ -0,0 +1,17 @@ + + +

Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?

+

Symptom

  • The DB instance is in Faulty state after the original database port is changed.
  • The DB instance cannot be connected using the new database port.
+
+

Possible Causes

The submitted database port is occupied.

+
+

Procedure

Change the database port to the new port again. For details, see Changing a Database Port.
  • If the database port is changed successfully, the previous change failed because the submitted database port was occupied.
  • If the original database port still fails to be changed, contact technical support.
+
+
+
+ + diff --git a/docs/rds/umn/rds_faq_0036.html b/docs/rds/umn/rds_faq_0036.html new file mode 100644 index 000000000..1ea3c31e2 --- /dev/null +++ b/docs/rds/umn/rds_faq_0036.html @@ -0,0 +1,21 @@ + + +

Which DB Instance Monitoring Metrics Do I Need to Pay Attention To?

+

You need to pay attention to CPU, memory, and storage space usage.

+

You can configure the system to report alarms based on service requirements and take measures to handle any reported alarms.

+

Configuration examples:

+
  • Configure RDS to report alarms to Cloud Eye if its CPU utilization reaches or exceeds a specific value (for example, 90%) multiple times (for example, 3 times) within a set period (for example, 5 minutes).
  • Configure RDS to report alarms to Cloud Eye if its memory utilization reaches or exceeds a specific value (for example, 90%) multiple times (for example, 4 times) within a set period (for example, 5 minutes).
  • Configure RDS to report alarms to Cloud Eye if its storage utilization reaches or exceeds a specific value (for example, 85%) multiple times (for example, 5 times) within a set period (for example, 5 minutes).
+

For details on Cloud Eye alarm configuration, see "Creating an Alarm Rule" in the Cloud Eye User Guide.

+
+

Measures:

+
  • If a CPU or memory alarm is reported, you can scale up the vCPUs or memory by changing the DB instance class.

    For details, see Changing a DB Instance Class.

    +
  • If a storage space usage alarm is reported, you can:
    • Check the storage space consumption to see if any space can be freed up by deleting data from DB instances or by dumping the data to another system.
    • Scale up the storage space.

      For details, see Scaling up Storage Space.

      +
    +
+
+
+
+
Parent topic: Database Monitoring
+
+
+ diff --git a/docs/rds/umn/rds_faq_0038.html b/docs/rds/umn/rds_faq_0038.html new file mode 100644 index 000000000..66b588287 --- /dev/null +++ b/docs/rds/umn/rds_faq_0038.html @@ -0,0 +1,14 @@ + + +

What Security Protection Policies Does RDS Have?

+

Network

  • RDS runs your DB instances in a VPC, ensuring that the DB instances are isolated from other services.
  • RDS uses security groups to ensure that only trusted sources can access your DB instances.
  • RDS supports SSL connections to encrypt data during transmission.
+
+

Management

You can use the Identity and Access Management (IAM) service to manage RDS permissions.

+
+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0039.html b/docs/rds/umn/rds_faq_0039.html new file mode 100644 index 000000000..c50048a73 --- /dev/null +++ b/docs/rds/umn/rds_faq_0039.html @@ -0,0 +1,11 @@ + + +

How Can Data Security Be Ensured During Transmission When I Access RDS Through an EIP?

+

When you access RDS through an EIP, service data will be transmitted on the public network. To prevent any potential data breaches, you are advised to use SSL to encrypt data transmitted on a public network. You can also use the Direct Connect or VPN services to encrypt data transmission.

+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0040.html b/docs/rds/umn/rds_faq_0040.html new file mode 100644 index 000000000..eeddd039b --- /dev/null +++ b/docs/rds/umn/rds_faq_0040.html @@ -0,0 +1,11 @@ + + +

How Can I Ensure the Security of RDS DB Instances in a VPC?

+

The VPC security group helps ensure the security of RDS in a VPC. In addition, an ACL can be used to allow or reject I/O network traffic for each subnet.

+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0041.html b/docs/rds/umn/rds_faq_0041.html new file mode 100644 index 000000000..ca49270f4 --- /dev/null +++ b/docs/rds/umn/rds_faq_0041.html @@ -0,0 +1,19 @@ + + +

What Storage Engines Does the RDS for MySQL Support?

+

The database storage engine is a core service for storing, processing, and protecting data. It can be used to control access permissions and rapidly process transactions to meet enterprise requirements.

+

For MySQL databases, only InnoDB supports backup and restoration functions and is therefore recommended.

+

For versions later than MySQL 5.6.40 and 5.7.22, some storage engines are no longer supported.

+

RDS for MySQL does not currently support MyISAM because:

+
  • MyISAM engine tables do not support transactions and support only table-level locks. As a result, read and write operations conflict with each other.
  • MyISAM has a defect in protecting data integrity, which may cause database data damage or even data loss.
  • If data is damaged, MyISAM does not support data restoration provided by RDS for MySQL and requires manual restoration.
  • Data can be transparently migrated from MyISAM to InnoDB, which does not require code modification for tables.
+

RDS for MySQL does not currently support FEDERATED, because:

+
  • If the primary/standby DB instances support FEDERATED, the same DML operations are repeatedly executed on remote databases, resulting in data disorder.
  • During the PITR restoration, data on remote databases is not restored to the status when the full backup is performed after the full restoration is complete. Applying data during the incremental restoration will disorder FEDERATED table data.
+

RDS for MySQL does not currently support MEMORY for the following reasons:

+
  • If a memory table becomes empty after a restart, the database generates a DELETE event to the binlog when the table is opened. If primary/standby DB instances use memory tables and the standby database (or read-only database) is restarted, a GTID is generated, which is inconsistent with that of the primary database. As a result, the standby database is rebuilt.
  • Using memory tables may cause out-of-memory (OOM) errors and even service terminations.
+
+
+
+
Parent topic: Database Storage
+
+
+ diff --git a/docs/rds/umn/rds_faq_0042.html b/docs/rds/umn/rds_faq_0042.html new file mode 100644 index 000000000..50fe2bbb7 --- /dev/null +++ b/docs/rds/umn/rds_faq_0042.html @@ -0,0 +1,11 @@ + + +

How Can I Back Up an RDS Database to an ECS?

+

You can back up data to an ECS the same way you export SQL statements. The ECS service does not have restrictions on the types of data to be backed up as long as the data complies with local laws and regulations. You can store RDS backup data on an ECS, but using an ECS is not recommended. You are advised to store RDS backup data to OBS for higher data reliability and service assurance.

+
+
+
+
Parent topic: Backup and Restoration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0043.html b/docs/rds/umn/rds_faq_0043.html new file mode 100644 index 000000000..075d1586c --- /dev/null +++ b/docs/rds/umn/rds_faq_0043.html @@ -0,0 +1,12 @@ + + +

How Long Does RDS Store Backup Data For?

+

Automated backup data is kept based on the backup retention period you specified. There is no limit for the manual backup retention period. You can delete manual backups as needed.

+

The backup data is stored in OBS and does not occupy the database storage space.

+
+
+
+
Parent topic: Backup and Restoration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0044.html b/docs/rds/umn/rds_faq_0044.html new file mode 100644 index 000000000..9fd57e85c --- /dev/null +++ b/docs/rds/umn/rds_faq_0044.html @@ -0,0 +1,11 @@ + + +

Can My Database Be Used in the Backup Window?

+

A backup window is a user-specified time during which RDS DB instances are backed up. With these periodic data backups, RDS allows you to restore DB instances to the backups during a retention period. This backup process does not affect services. However, you cannot reboot these DB instances on the RDS console.

+
+
+
+
Parent topic: Backup and Restoration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0045.html b/docs/rds/umn/rds_faq_0045.html new file mode 100644 index 000000000..6b1d00ff7 --- /dev/null +++ b/docs/rds/umn/rds_faq_0045.html @@ -0,0 +1,12 @@ + + +

What Is the RDS DB Instance Storage Configuration?

+

RDS uses Elastic Volume Service (EVS) disks for storage. For details about EVS disks, see Elastic Volume Service Product Introduction.

+

The RDS backup data is stored in OBS and does not occupy the database storage space. For details on the RDS DB instance storage configuration, see the Object Storage Service User Guide.

+
+
+
+
Parent topic: Database Storage
+
+
+ diff --git a/docs/rds/umn/rds_faq_0046.html b/docs/rds/umn/rds_faq_0046.html new file mode 100644 index 000000000..4e477b168 --- /dev/null +++ b/docs/rds/umn/rds_faq_0046.html @@ -0,0 +1,17 @@ + + +

What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?

+

Scenario

There is not enough storage available for an RDS DB instance and the DB instance has entered read-only status, or applications can no longer read from or write to the databases, interrupting services.

+
+

Causes

Possible causes include:

+
  • Too much data being stored.
  • Too many MySQL binlog files being generated due to a large number of transactions and write operations.
  • A large number of temporary files being generated due to a large number of sorting queries executed by applications.
+
+

Solution

  1. If your DB instance becomes read-only because there is too much data, contact technical support to cancel the read-only status and run statements to delete useless historical table data to free up space. To delete data of an entire table, run DROP or TRUNCATE. To delete part of table data, run DELETE and OPTIMIZE TABLE. If the instance still supports read and write operations, directly delete unless historical table data. If no historical data can be deleted, scale up your storage space.
  2. If MySQL binlog files are taking up too much space, contact technical support to delete local binlog files to free up storage space.
  3. If temporary files generated by sorting queries are taking up too much space, optimize your SQL query statements.
  4. If none of these solutions work, use database and table sharding.
+
+
+
+
+
Parent topic: Database Storage
+
+
+ diff --git a/docs/rds/umn/rds_faq_0047.html b/docs/rds/umn/rds_faq_0047.html new file mode 100644 index 000000000..73164f6fc --- /dev/null +++ b/docs/rds/umn/rds_faq_0047.html @@ -0,0 +1,13 @@ + + +

Which Items Occupy the Storage Space of My RDS DB Instances?

+

Both your common data (excluding backup data) and the data required for the operation of your DB instances (such as system database data, rollback logs, redo logs, and indexes) occupies storage space on your purchased RDS DB instances. The following RDS log files also occupy storage space:

+
  • Binlog files generated by MySQL databases
  • Logs files generated by PostgreSQL database servers
  • Log files, including Microsoft SQL Server logs, default Microsoft SQL Server Trace logs, and Microsoft SQL Server Agent logs, generated by Microsoft SQL Server databases.
+

These files ensure the stability of RDS DB instances.

+
+
+
+
Parent topic: Resource and Disk Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0048.html b/docs/rds/umn/rds_faq_0048.html new file mode 100644 index 000000000..c53fd85f0 --- /dev/null +++ b/docs/rds/umn/rds_faq_0048.html @@ -0,0 +1,11 @@ + + +

What Overhead Does the Storage Space Have After I Applied for an RDS DB Instance?

+

The storage space you applied for will include space for the file system overhead required for inode, reserved block, and database operations.

+
+
+
+
Parent topic: Resource and Disk Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0049.html b/docs/rds/umn/rds_faq_0049.html new file mode 100644 index 000000000..c11ec9477 --- /dev/null +++ b/docs/rds/umn/rds_faq_0049.html @@ -0,0 +1,74 @@ + + +

Which Types of Logs and Files Occupy RDS Storage Space?

+

The following logs and files occupy RDS storage space.

+ +
+ + + + + + + + + + + +
Table 1 MySQL database file types

DB Engine

+

File Type

+

MySQL

+

Log files: database undo-log, redo-log, and binlog files

+

Data files: database content files and index files

+

Other files: ibdata, ib_logfile0, and temporary files

+
+
+ +
+ + + + + + + + + + + +
Table 2 PostgreSQL database file types

DB Engine

+

File Type

+

PostgreSQL

+

Log files: database error log and transaction log files

+

Data files: database content, index, replication slot data, transaction status data, and database configuration files

+

Other files: temporary files

+
+
+ +
+ + + + + + + + + +
Table 3 Microsoft SQL Server database file types

DB Engine

+

File Type

+

Microsoft SQL Server

+

Log files: database error log, transaction log, and trace files

+

Data files: database content files

+
+
+

Solution

  1. If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.
  2. If data occupies too much storage space, run DROP, TRUNCATE, or DELETE+OPTIMIZE TABLE to delete useless historical table data to release storage space. If no historical data can be deleted, scale up your storage space.
  3. If temporary files generated by sorting queries occupy too much storage space, optimize your SQL query statements.
    1. A large number of temporary files are generated if there are a large number of sorting queries executed by applications.
    2. A large number of binlog files are generated and occupy space if there are large amounts of insert, delete, and update operations in a short period.
    3. A large number of binlog files are generated if there are a large number of transactions and write operations.
    +
  4. Use Cloud Eye to monitor the size, usage, and utilization of storage space of your DB instance and set alarm policies.
+
+
+
+
+
Parent topic: Resource and Disk Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0050.html b/docs/rds/umn/rds_faq_0050.html new file mode 100644 index 000000000..47eca861c --- /dev/null +++ b/docs/rds/umn/rds_faq_0050.html @@ -0,0 +1,166 @@ + + +

How Can I Connect to a PostgreSQL Database Through JDBC?

+

Although the SSL certificate is optional if you choose to connect to a database through Java database connectivity (JDBC), download an SSL certificate to encrypt the connections for security.

+

Prerequisites

Familiarize yourself with:

+
  • Computer basics.
  • Java programming language.
  • JDBC knowledge.
+
+

Obtaining and Using JDBC

+
+

Connection with the SSL Certificate

Download the SSL certificate and verify the certificate before connecting to databases.

+

In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.

+
+
  1. Connect to the RDS PostgreSQL DB instance through JDBC.

    jdbc:postgresql://<instance_ip>:<instance_port>/<database_name>?sslmode=verify-full&sslrootcert=<ca.pem>
    + +
    + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    <instance_ip>

    +

    If you attempt to access the RDS DB instance through an ECS, set instance_ip to the floating IP address displayed on the Basic Information page of the DB instance to which you intend to connect.

    +

    If you attempt to access the RDS DB instance through an EIP, set instance_ip to the EIP that has been bound to the DB instance.

    +

    <instance_port>

    +

    Enter the database port displayed on the Basic Information page. Default value: 5432

    +

    <database_name>

    +

    Enter the name of the database to which you intend to connect. Default value: postgres

    +

    sslmode

    +

    Enter the SSL connection mode. Default value: verify-full

    +

    sslrootcert

    +

    Enter the directory of the CA certificate for the SSL connection. The certificate should be stored in the directory where the command is executed.

    +
    +
    +

    Example script in Java:

    +
    import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.ResultSet;
+import java.sql.Statement;
+
+public class MyConnTest {
+	final public static void main(String[] args) {
+		Connection conn = null;
+		// set sslmode here.
+		// with ssl certificate and path.
+		String url = "jdbc:postgresql://192.168.0.225:5432/my_db_test?sslmode=verify-full&sslrootcert=/home/Ruby/ca.pem";
+
+		try {
+			Class.forName("org.postgresql.Driver");
+			conn = DriverManager.getConnection(url, "root", "password");
+			System.out.println("Database connected");
+
+			Statement stmt = conn.createStatement();
+			ResultSet rs = stmt.executeQuery("SELECT * FROM mytable WHERE columnfoo = 500");
+			while (rs.next()) {
+				System.out.println(rs.getString(1));
+			}
+
+			rs.close();
+			stmt.close();
+			conn.close();
+		} catch (Exception e) {
+			e.printStackTrace();
+			System.out.println("Test failed");
+		} finally {
+			// release resource ....
+		}
+	}
+}
    +

+
+

Connection Without the SSL Certificate

You do not need to download the SSL certificate because the certificate verification on the server is not required.

+
+
  1. Connect to the RDS PostgreSQL DB instance through JDBC.

    jdbc:postgresql://<instance_ip>:<instance_port>/<database_name>?sslmode=disable
    + +
    + + + + + + + + + + + + + + + + + + +
    Table 2 Parameter description

    Parameter

    +

    Description

    +

    <instance_ip>

    +

    If you attempt to access the RDS DB instance through an ECS, set instance_ip to the floating IP address displayed on the Basic Information page of the DB instance to which you intend to connect.

    +

    If you attempt to access the RDS DB instance through an EIP, set instance_ip to the EIP that has been bound to the DB instance.

    +

    <instance_port>

    +

    Enter the database port displayed on the Basic Information page. Default value: 5432

    +

    <database_name>

    +

    Enter the name of the database to which you intend to connect. Default value: postgres

    +

    sslmode

    +

    Enter the SSL connection mode. disable means data is not encrypted.

    +
    +
    +

    Example script in Java:

    +
    import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.ResultSet;
+import java.sql.Statement;
+
+public class MyConnTest {
+	final public static void main(String[] args) {
+		Connection conn = null;
+		// set sslmode here.
+		// no ssl certificate, so do not specify path.
+		String url = "jdbc:postgresql://192.168.0.225:5432/my_db_test?sslmode=disable";
+		try {
+			Class.forName("org.postgresql.Driver");
+			conn = DriverManager.getConnection(url, "root", "password");
+			System.out.println("Database connected");
+
+			Statement stmt = conn.createStatement();
+			ResultSet rs = stmt.executeQuery("SELECT * FROM mytable WHERE columnfoo = 500");
+			while (rs.next()) {
+				System.out.println(rs.getString(1));
+			}
+			rs.close();
+			stmt.close();
+			conn.close();
+		} catch (Exception e) {
+			e.printStackTrace();
+			System.out.println("Test failed");
+		} finally {
+			// release resource ....
+		}
+	}
+}
    +

+
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0051.html b/docs/rds/umn/rds_faq_0051.html new file mode 100644 index 000000000..712fda013 --- /dev/null +++ b/docs/rds/umn/rds_faq_0051.html @@ -0,0 +1,17 @@ + + +

How Can I Identify the Validity Period of an SSL Root Certificate?

+

When you connect to an RDS MySQL DB instance using an SSL connection, run the following command to check whether the certificate has expired:

+
show status like '%ssl_server%';
+

Update the root certificate to the latest version before it expires:

+
  1. In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.
  2. Reboot the DB instance for the new certificate to take effect.
  3. Connect to the DB instance using the new certificate or certificate bundle. +

    If a certificate is about to expire, replace it with an officially issued certificate to improve system security.

    +
    +
+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0052.html b/docs/rds/umn/rds_faq_0052.html new file mode 100644 index 000000000..616ae35d4 --- /dev/null +++ b/docs/rds/umn/rds_faq_0052.html @@ -0,0 +1,16 @@ + + +

How Can I Import the Root Certificate to a Windows or Linux OS?

+

Importing the Root Certificate to the Windows OS

  1. Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.
  2. On the displayed console, choose File > Add/Remove Snap-in.
  3. In the left Available snap-ins pane of the displayed Add or Remove Snap-ins dialog box, select Certificates and click Add.
  4. In the displayed Certificates snap-in dialog box, select Computer account and click Next.
  5. In the displayed Select Computer dialog box, click Finish.
  6. In the Add or Remove Snap-ins dialog box, click OK.
  7. On the console, double-click Certificates.
  8. Right-click Trusted Root Certification Authorities and choose All Tasks > Import.
  9. In the displayed Certificate Import Wizard dialog box, click Next.
  10. Click Browse to change the file type to All Files (*.*).
  11. Locate the downloaded root certificate ca.pem file and click Open. Then, click Next.

    You must change the file type to All Files (*.*) because .pem is not a standard certificate extension name.

    +
    +
  12. Click Next.
  13. Click Finish.
  14. Click OK to complete the import of the root certificate.
+
+

Importing the Root Certificate to the Linux OS

You can use a connection tool (such as WinSCP or PuTTY) to upload the certificate to any directory on a Linux OS.

+
+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0053.html b/docs/rds/umn/rds_faq_0053.html new file mode 100644 index 000000000..81380d3da --- /dev/null +++ b/docs/rds/umn/rds_faq_0053.html @@ -0,0 +1,16 @@ + + +

Why Has My Automated Backup Failed?

+

Automated backups may fail for the following reasons:

+
  1. The network environment is unstable due to issues such as network delay or interruption. RDS will detect these problems and trigger another automated backup half an hour later. You can also perform a manual backup before then.
  2. Multi-task executions are complicated, resulting in problems such as task waiting or interruptions. RDS will detect these problems and trigger another automated backup half an hour later. You can also perform a manual backup.
  3. A DB instance status is unavailable, possibly because the DB instance is faulty or being modified. RDS will trigger an automated backup when the DB instance status becomes available. You can also perform a manual backup before then.
  4. The backup speed depends on how many tables there are in the databases. If the number of tables exceeds 500,000, the backup will fail.
  5. A parameter change was incorrect. For example, a DB instance may become faulty after a parameter template containing incorrect parameters was applied to it. You can check whether original and current values are correct, check whether any related parameters also need to be changed, reset the parameter template, or reboot the DB instance.
  6. An error occurred during data import.

    For example, system table records get lost due to inappropriate data import.

    +

    For MySQL, you can import data again by referring to section Migrating Data to RDS for MySQL Using mysqldump.

    +

    For PostgreSQL, you can import data again by referring to section Migrating Data to RDS for PostgreSQL Using psql.

    +

    For Microsoft SQL Server, you can import data again by referring to section Migrating Data to RDS for SQL Server Using SQL Server Management Studio.

    +
  7. If the problem persists, contact technical support.
+
+
+
+
Parent topic: Backup and Restoration
+
+
+ diff --git a/docs/rds/umn/rds_faq_0054.html b/docs/rds/umn/rds_faq_0054.html new file mode 100644 index 000000000..e1c2fafca --- /dev/null +++ b/docs/rds/umn/rds_faq_0054.html @@ -0,0 +1,13 @@ + + +

How Do I Configure a Security Group to Enable Access to RDS DB Instances?

+
  • When you attempt to connect to a DB instance through a private network, check whether the ECS and RDS DB instance are in the same security group.
    • If the ECS and RDS DB instance are in the same security group, they can communicate with each other by default. No security group rules need to be configured.
    • If the ECS and RDS DB instance are in different security groups, you need to configure security group rules for them, separately.
      • RDS DB instance: Configure an inbound rule for the security group with which the DB instance is associated.
      • ECS: The default security group rule allows all outgoing data packets. In this case, 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.
      +
    +
  • When you attempt to connect to a DB instance through an EIP, you need to configure an inbound rule for the security group associated with the DB instance.
+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0055.html b/docs/rds/umn/rds_faq_0055.html new file mode 100644 index 000000000..cd46dcf61 --- /dev/null +++ b/docs/rds/umn/rds_faq_0055.html @@ -0,0 +1,93 @@ + + +

What Is the Maximum Number of Connections to an RDS DB Instance?

+

RDS does not have constraints on the number of connections. This number is determined by the default value and value range of the DB engine. For example, you can set max_connections and max_user_connections in a parameter template to configure the maximum number of connections for an RDS for MySQL DB instance.

+

Changing the Maximum Number of Connections

.

+

You can change the maximum number of connections using commands.

+
  1. Query the maximum number of connections.

    show global variables like 'max_connections';

    +
  2. Change the value of max_connections under mysqld in the my.cnf file.

    [mysqld]

    +

    max_connections = 1000

    +
+
+

Setting the Maximum Number of RDS for MySQL Connections to an Appropriate Value

  • In addition to the value of max_connections, the maximum number of concurrent client connections allowed by MySQL is also limited by the maximum number of files that can be opened by a single process in the operating system. For example, if the maximum number of files that can be opened by each process is set to 100 in the operating system, the max_connections parameter does not take effect even if it is set to 200.

    Check the maximum number of files that can be opened by a single process in the operating system. The default value is 1024.

    +

    ulimit -n

    +

    The parameter open_files_limit indicates the maximum number of files that can be opened by a single process, which is read from the operating system during MySQL startup.

    +

    Check the value of open_files_limit.

    +

    show variables like 'open_files_limit';

    +
  • Suggestions

    The maximum number of MySQL connections can be customized provided that it is allowed by your instance specifications. The maximum number of connections is closely related to the instance memory. For details, see About max_connections.

    +

    In actual scenarios, set the maximum number of connections to an appropriate value because more connections lead to large resource consumption.

    +
+
+

About max_connections

max_connections: maximum number of clients that can be connected at the same time. If this parameter is set to default, it is related to the memory (unit: GB) of the DB instance. The calculation formula is as follows:

+

Estimated value of max_connections = Available node memory/Estimated memory occupied by a single connection

+
  • Available node memory = Total memory – Memory occupied by the buffer pool – 1 GB (mysqld process/OS/monitoring program)
  • Estimated memory usage of a single connection (single_thread_memory) = thread_stack (256 KB) + binlog_cache_size (32 KB) + join_buffer_size (256 KB) + sort_buffer_size (256 KB) + read_buffer_size (128 KB) + read_rnd_buffer_size (256 KB) ≈ 1 MB
+
+
+

The following table lists the default values of max_connections for different memory specifications.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Max_connections for different memory specifications

Memory (GB)

+

Connections

+

512

+

100,000

+

384

+

80,000

+

256

+

60,000

+

128

+

30,000

+

64

+

18,000

+

32

+

10,000

+

16

+

5,000

+

8

+

2,500

+

4

+

1,500

+

2

+

800

+
+
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0056.html b/docs/rds/umn/rds_faq_0056.html new file mode 100644 index 000000000..86ce141fe --- /dev/null +++ b/docs/rds/umn/rds_faq_0056.html @@ -0,0 +1,14 @@ + + +

How Can I Prevent Untrusted Source IP Addresses from Accessing RDS?

+
  • If you enable public accessibility, your EIP DNS and database port may be vulnerable to hacking. To protect information such as your EIP, DNS, database port, database account, and password, you are advised to set the range of source IP addresses in the RDS security group to ensure that only trusted source IP addresses can access your DB instances.
  • To prevent your database password from being cracked, set a strong password and periodically change it.
  • RDS for SQL Server includes defense against brute force cracking. If malicious individuals have obtained your EIP DNS, database port, or database login information and attempt a brute force attack, your service connections may be delayed. In this case, you can restrict the source connections and change the database username and password to prevent further damage.

    RDS for MySQL and RDS for PostgreSQL do not include defense against brute force attacks.

    +

    For RDS for Microsoft SQL Server, defense against brute force attacks is enabled by default and cannot be disabled.

    +
    +
+
+
+
+
Parent topic: Network Security
+
+
+ diff --git a/docs/rds/umn/rds_faq_0057.html b/docs/rds/umn/rds_faq_0057.html new file mode 100644 index 000000000..39348a20c --- /dev/null +++ b/docs/rds/umn/rds_faq_0057.html @@ -0,0 +1,12 @@ + + +

How Can I Create and Connect to an ECS?

+
  1. For details about how to create an ECS, see the Elastic Cloud Server User Guide.
    • If you connect to an RDS DB instance through a private network, ensure that the ECS and DB instance are in the same VPC. If you connect to an RDS DB instance through a public network, the ECS and DB instance can be in different VPCs.
    • Configure a security group to allow the ECS to access the RDS DB instance through the IP address.
    +
  2. For details on how to connect to the ECS, see section "Logging In to an ECS" in the Elastic Cloud Server User Guide.
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0059.html b/docs/rds/umn/rds_faq_0059.html new file mode 100644 index 000000000..29edacaa7 --- /dev/null +++ b/docs/rds/umn/rds_faq_0059.html @@ -0,0 +1,17 @@ + + +

How Can I Obtain Microsoft SQL Server Error Logs Using Commands?

+
  1. Log in to the Microsoft SQL Server client as user rdsuser.
  2. Run the following statement to query error logs:

    EXECUTE master.dbo.rds_read_errorlog FileID,LogType,FilterText,FilterBeginTime,FilterEndTime

    +
    • FileID: indicates the ID of an error log. The value 0 indicates the latest logs.
    • LogType: indicates the log type. The value 1 indicates error logs and value 2 indicates agent logs.
    • FilterText: indicates a keyword, which can be NULL.
    • FilterBeginTime: indicates the start time in queries, which can be NULL.
    • FilterEndTime: indicates the completion time in queries, which can be NULL.
    +

    Example:

    +

    EXEC master.dbo.rds_read_errorlog 0,1,'FZYUN','2018-06-14 14:30','2018-06-14 14:31'

    +

    Figure 1 shows the query results.

    +
    Figure 1 Example query results
    +

+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0065.html b/docs/rds/umn/rds_faq_0065.html new file mode 100644 index 000000000..c110d19e4 --- /dev/null +++ b/docs/rds/umn/rds_faq_0065.html @@ -0,0 +1,21 @@ + + +

How Does a Cloud Database Perform a Primary/Standby Switchover?

+

RDS provides the high availability. Select the primary/standby mode.

+

Failover

Also called an unplanned handover. If the primary DB instance fails, the system will automatically switch to the standby DB instance within 5 minutes. No human intervention is required. The connection IP address remains unchanged. DB instances cannot be accessed during the failover. You need to configure automatic reconnections between applications and RDS DB instances to ensure near-continuous availability.

+
+

Switchover (Manual)

Also called a planned handover. When a DB instance is running properly, you can manually perform a primary/standby switchover if it is needed.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

    Alternatively, click in the DB instance topology on the Basic Information page to manually trigger a primary/standby switchover.

    +

    A primary/standby switchover may cause service interruption for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, perform a switchover during off-peak hours.

    +
    +

  6. In the Switch Primary/Standby Instances dialog box, click Yes to switch between the primary and standby DB instances.

    If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

    +

  7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

    • During the switchover process, the DB instance status is Switchover in progress.
    • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is complete, the DB instance status will become Available
    +

+
+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0070.html b/docs/rds/umn/rds_faq_0070.html new file mode 100644 index 000000000..6f55d1e17 --- /dev/null +++ b/docs/rds/umn/rds_faq_0070.html @@ -0,0 +1,12 @@ + + +

Does MySQL Support SSL Connections?

+

MySQL supports SSL connections. Different from other vendors, RDS for MySQL enables the SSL connection on the database server by default. When you use a client to connect to MySQL DB instances, you can determine whether to enable SSL as required.

+

For details about SSL, see section Connecting to an RDS for MySQL DB Instance Through a Public Network.

+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0073.html b/docs/rds/umn/rds_faq_0073.html new file mode 100644 index 000000000..790622266 --- /dev/null +++ b/docs/rds/umn/rds_faq_0073.html @@ -0,0 +1,11 @@ + + +

Does RDS Support Cross-AZ High Availability?

+

Yes. RDS supports cross-AZ high availability. When you create primary/standby DB instances, you can select different AZs for them.

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0075.html b/docs/rds/umn/rds_faq_0075.html new file mode 100644 index 000000000..050deb825 --- /dev/null +++ b/docs/rds/umn/rds_faq_0075.html @@ -0,0 +1,18 @@ + + +

Why Does the Root User Not Have the Super Permissions?

+

Most relational database cloud service platforms do not provide super permissions for the root user. The super permissions allow users to execute many management commands, such as reset master, set global, kill, and reset slave. These operations may cause primary/standby replication errors. This is a major difference between public cloud databases and on-premises MySQL databases. To ensure stable running of DB instances, RDS does not provide the super permission for the root user.

+

If you need to perform actions that normally require super permissions, RDS provides alternative methods.

+

For example:

+
  1. You can modify parameter values only on the RDS console. You cannot run the following command on an RDS DB database to modify parameter values.

    set global parameter name=Parameter value;

    +

    If the script contains the set global command, delete the set global command and modify parameter values through the RDS console.

    +
  2. An error is reported after you run the following command because the root user does not have super permissions. You can delete definer='root' from the command to solve the problem.

    create definer='root'@'%' trigger(procedure)...

    +

    You can import data using mysqldump. For operation details, see Migrating Data to RDS for MySQL Using mysqldump.

    +
  3. You can create PostgreSQL plugins by referring to Creating or Deleting a Plugin.
+
+
+
+
Parent topic: Database Permission
+
+
+ diff --git a/docs/rds/umn/rds_faq_0076.html b/docs/rds/umn/rds_faq_0076.html new file mode 100644 index 000000000..8cf1b616d --- /dev/null +++ b/docs/rds/umn/rds_faq_0076.html @@ -0,0 +1,11 @@ + + +

Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?

+

No. After an RDS DB instance is created, the storage type cannot be changed.

+
+
+
+
Parent topic: Database Storage
+
+
+ diff --git a/docs/rds/umn/rds_faq_0077.html b/docs/rds/umn/rds_faq_0077.html new file mode 100644 index 000000000..c93824186 --- /dev/null +++ b/docs/rds/umn/rds_faq_0077.html @@ -0,0 +1,11 @@ + + +

What's the Slow Query Threshold for Microsoft SQL Server?

+

The slow query threshold is 5 seconds.

+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0078.html b/docs/rds/umn/rds_faq_0078.html new file mode 100644 index 000000000..9abf09bcb --- /dev/null +++ b/docs/rds/umn/rds_faq_0078.html @@ -0,0 +1,11 @@ + + +

How Long Is the Delay for RDS MySQL Slow Query Logs?

+

Generally, the delay is 5 minutes. If the size of slow query logs reaches 10 MB within 5 minutes, the logs will be uploaded to OBS.

+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0082.html b/docs/rds/umn/rds_faq_0082.html new file mode 100644 index 000000000..01e4e3088 --- /dev/null +++ b/docs/rds/umn/rds_faq_0082.html @@ -0,0 +1,11 @@ + + +

How Much Storage Space Is Required for DDL Operations?

+

Data Definition Language (DDL) operations may increase storage space usage sharply. To ensure that services are running properly, do not perform DDL operations during peak hours. If DDL operations are required, ensure that storage space is 10 GB greater than or equal to twice the size of the tablespace. For example, if your tablespace is 500 GB, ensure that storage space is greater than or equal to 1,010 GB (500 GB x 2 + 10 GB).

+
+
+
+
Parent topic: Resource and Disk Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0092.html b/docs/rds/umn/rds_faq_0092.html new file mode 100644 index 000000000..ad8aebd01 --- /dev/null +++ b/docs/rds/umn/rds_faq_0092.html @@ -0,0 +1,11 @@ + + +

Where Should I Store the NDF Files for Microsoft SQL Server?

+

When you add NDF files of the custom database and the tempdb database, do not place them in the C drive. If you place them in the C drive, the system disk space will be used up and services may be interrupted. You need to store the NDF auxiliary file of the custom database in D:\RDSDBDATA\DATA and the NDF auxiliary file of the tempdb database in D:\RDSDBDATA\Temp.

+
+
+
+
Parent topic: Database Parameter Modification
+
+
+ diff --git a/docs/rds/umn/rds_faq_0094.html b/docs/rds/umn/rds_faq_0094.html new file mode 100644 index 000000000..023d73608 --- /dev/null +++ b/docs/rds/umn/rds_faq_0094.html @@ -0,0 +1,23 @@ + + +

Why Is an Error Reported When I Attempt to Delete a Database from RDS SQL Server Primary/Standby DB Instances?

+

Symptom

An error shown in Figure 1 is reported on SQL Server Management Studio when a database is being deleted from RDS SQL Server primary/standby DB instances.

+

The database 'xxxx' is enabled for database mirroring. Database mirroring must be removed before you drop the database. Error: 3743

+
+
Figure 1 Error information
+

Possible Causes

The error details indicate that the SQL Server DB instance type is primary/standby and database mirroring is enabled for the standby DB instance. As a result, the database cannot be deleted.

+
+

Solution

Before deleting the database, run the following commands to disable the mirroring:

+
+

Use master

+

go

+

ALTER DATABASE [Database_Name] SET PARTNER OFF;

+

GO

+

Once database mirroring is disabled, the database can be deleted.

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0098.html b/docs/rds/umn/rds_faq_0098.html new file mode 100644 index 000000000..abb668f23 --- /dev/null +++ b/docs/rds/umn/rds_faq_0098.html @@ -0,0 +1,27 @@ + + +

Backup and Restoration

+
+ + diff --git a/docs/rds/umn/rds_faq_0100.html b/docs/rds/umn/rds_faq_0100.html new file mode 100644 index 000000000..609b9647c --- /dev/null +++ b/docs/rds/umn/rds_faq_0100.html @@ -0,0 +1,18 @@ + + +

What Should I Do If an RDS Microsoft SQL Server DB Instance Failed to Be Connected?

+

Fault Location

  • Check whether the ECS can connect to the RDS DB instance.

    If the ECS cannot connect to the RDS DB instance, check whether the ECS and RDS DB instance are located in the same VPC and security group.

    +

    In private network connection mode, the ECS and RDS DB instance must be in the same VPC and the DB instance can be accessed only through an ECS in the same VPC. In public network connection mode, the ECS and DB instance can be in different VPCs.

    +
+
  • Check whether the IP address and port are correct.

    Use a colon to separate the IP address and port.

    +
  • Check whether the RDS service is running properly.
  • Check whether the username and password are correct. You can reset the password.
  • Reboot the RDS DB instance and check whether it can be connected through an ECS.
+
+

Solution

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. On the Basic Information and Backups & Restorations pages, check connection and backup information.
  5. On the Basic Information page, check the administrator.
  6. Download an SQL Server Management Studio installation package and install it on an ECS.
  7. Connect to the RDS DB instance through an ECS.
+
+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0101.html b/docs/rds/umn/rds_faq_0101.html new file mode 100644 index 000000000..2bb1245ba --- /dev/null +++ b/docs/rds/umn/rds_faq_0101.html @@ -0,0 +1,11 @@ + + +

Can I Access an RDS DB Instance Over an Intranet Connection Across Regions?

+

By default, RDS DB instances cannot be accessed over an intranet across regions. Cloud services in different regions cannot communicate with each other over an intranet. You can use Cloud Connect (CC) or Virtual Private Network (VPN) to connect to RDS DB instances across regions.

+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0104.html b/docs/rds/umn/rds_faq_0104.html new file mode 100644 index 000000000..a7a7c5d57 --- /dev/null +++ b/docs/rds/umn/rds_faq_0104.html @@ -0,0 +1,11 @@ + + +

Can RDS Primary/Standby DB Instances Be Changed to Single DB Instances?

+

No. RDS single DB instances can be changed to primary/standby DB instances, but not the other way around.

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0110.html b/docs/rds/umn/rds_faq_0110.html new file mode 100644 index 000000000..06e44ec8c --- /dev/null +++ b/docs/rds/umn/rds_faq_0110.html @@ -0,0 +1,11 @@ + + +

What Should I Do If Garbled Characters Are Displayed After SQL Query Results Are Exported to an Excel File?

+

The default code is utf8. You need to convert the default code to Unicode in the exported Excel file.

+
+
+
+
Parent topic: Product Consulting
+
+
+ diff --git a/docs/rds/umn/rds_faq_0111.html b/docs/rds/umn/rds_faq_0111.html new file mode 100644 index 000000000..38fee770a --- /dev/null +++ b/docs/rds/umn/rds_faq_0111.html @@ -0,0 +1,11 @@ + + +

Is an SSL Connection to a DB Instance Interrupted After a Primary/Standby Switchover or Failover?

+

For DB instances connected using SSL, a primary/standby switchover or failover does not interrupt the connection because the SSL certificate is still valid for both the primary and standby DB instances.

+
+
+
+
Parent topic: Database Connection
+
+
+ diff --git a/docs/rds/umn/rds_faq_0119.html b/docs/rds/umn/rds_faq_0119.html new file mode 100644 index 000000000..6db1a5724 --- /dev/null +++ b/docs/rds/umn/rds_faq_0119.html @@ -0,0 +1,13 @@ + + +

Does RDS for PostgreSQL Support the test_decoding Plugin?

+

PostgreSQL 10, PostgreSQL 11, PostgreSQL 12 and PostgreSQL 13 support test_decoding. For more information about test_decoding, see test_decoding introduction.

+

To use test_decoding, set wal_level to logical.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the Parameters tab page, locate wal_level and change its value to logical.
  6. Click Save. In the displayed dialog box, click Yes.
+
+
+
+
Parent topic: Database Parameter Modification
+
+
+ diff --git a/docs/rds/umn/rds_faq_0120.html b/docs/rds/umn/rds_faq_0120.html new file mode 100644 index 000000000..9966becb5 --- /dev/null +++ b/docs/rds/umn/rds_faq_0120.html @@ -0,0 +1,11 @@ + + +

Can I Export Statistics on RDS Slow Query Logs?

+

Sorry, statistics on RDS slow query logs cannot be exported.

+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_faq_0141.html b/docs/rds/umn/rds_faq_0141.html new file mode 100644 index 000000000..78e00a462 --- /dev/null +++ b/docs/rds/umn/rds_faq_0141.html @@ -0,0 +1,43 @@ + + +

Database Connection

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/rds/umn/rds_faq_0142.html b/docs/rds/umn/rds_faq_0142.html new file mode 100644 index 000000000..ff65d035c --- /dev/null +++ b/docs/rds/umn/rds_faq_0142.html @@ -0,0 +1,19 @@ + + +

Database Parameter Modification

+
+ + diff --git a/docs/rds/umn/rds_faq_0143.html b/docs/rds/umn/rds_faq_0143.html new file mode 100644 index 000000000..b8f4606ed --- /dev/null +++ b/docs/rds/umn/rds_faq_0143.html @@ -0,0 +1,29 @@ + + +

Network Security

+
+ + diff --git a/docs/rds/umn/rds_faq_0144.html b/docs/rds/umn/rds_faq_0144.html new file mode 100644 index 000000000..c66b5cf71 --- /dev/null +++ b/docs/rds/umn/rds_faq_0144.html @@ -0,0 +1,21 @@ + + +

Database Storage

+
+ + diff --git a/docs/rds/umn/rds_faq_0145.html b/docs/rds/umn/rds_faq_0145.html new file mode 100644 index 000000000..6c0277f21 --- /dev/null +++ b/docs/rds/umn/rds_faq_0145.html @@ -0,0 +1,25 @@ + + +

Resource and Disk Management

+
+ + diff --git a/docs/rds/umn/rds_faq_0146.html b/docs/rds/umn/rds_faq_0146.html new file mode 100644 index 000000000..88637ba12 --- /dev/null +++ b/docs/rds/umn/rds_faq_0146.html @@ -0,0 +1,37 @@ + + +

Product Consulting

+
+
+ + +
+
Parent topic: FAQs
+
+
+ diff --git a/docs/rds/umn/rds_faq_0149.html b/docs/rds/umn/rds_faq_0149.html new file mode 100644 index 000000000..b6e864d1d --- /dev/null +++ b/docs/rds/umn/rds_faq_0149.html @@ -0,0 +1,21 @@ + + +

Log Management

+
+ + diff --git a/docs/rds/umn/rds_faq_0150.html b/docs/rds/umn/rds_faq_0150.html new file mode 100644 index 000000000..40b11a7dc --- /dev/null +++ b/docs/rds/umn/rds_faq_0150.html @@ -0,0 +1,21 @@ + + + +

Capacity Expansion and Specification Change

+ +

+
+ + + diff --git a/docs/rds/umn/rds_faq_0151.html b/docs/rds/umn/rds_faq_0151.html new file mode 100644 index 000000000..4b3316b75 --- /dev/null +++ b/docs/rds/umn/rds_faq_0151.html @@ -0,0 +1,19 @@ + + + +

Database Monitoring

+ +

+
+ + + diff --git a/docs/rds/umn/rds_faq_0152.html b/docs/rds/umn/rds_faq_0152.html new file mode 100644 index 000000000..8faede802 --- /dev/null +++ b/docs/rds/umn/rds_faq_0152.html @@ -0,0 +1,19 @@ + + +

Client Installation

+
+ + diff --git a/docs/rds/umn/rds_faq_0154.html b/docs/rds/umn/rds_faq_0154.html new file mode 100644 index 000000000..a51eb40b2 --- /dev/null +++ b/docs/rds/umn/rds_faq_0154.html @@ -0,0 +1,15 @@ + + +

Database Permission

+
+ + diff --git a/docs/rds/umn/rds_faq_0155.html b/docs/rds/umn/rds_faq_0155.html new file mode 100644 index 000000000..6e659fba7 --- /dev/null +++ b/docs/rds/umn/rds_faq_0155.html @@ -0,0 +1,21 @@ + + + +

Database Migration

+ +

+
+ + + diff --git a/docs/rds/umn/rds_glossary_0001.html b/docs/rds/umn/rds_glossary_0001.html new file mode 100644 index 000000000..482b365a2 --- /dev/null +++ b/docs/rds/umn/rds_glossary_0001.html @@ -0,0 +1,7 @@ + + +

Glossary

+

For details about the glossaries in this document, see Glossary.

+
+
+ diff --git a/docs/rds/umn/rds_migration_mysql.html b/docs/rds/umn/rds_migration_mysql.html new file mode 100644 index 000000000..0b9d3337e --- /dev/null +++ b/docs/rds/umn/rds_migration_mysql.html @@ -0,0 +1,85 @@ + + +

Migrating Data to RDS for MySQL Using mysqldump

+

Preparing for Data Migration

You can access RDS DB instances through an EIP or through an ECS.

+
  1. Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through an EIP.
    • To connect to a DB instance through an ECS, you need to create an ECS first.

      For details about how to create and connect to an ECS, see How Can I Create and Connect to an ECS?

      +
    • To connect to a DB instance through an EIP, you must:
      1. Bind an EIP to a DB instance. For details, see Binding an EIP.
      2. Ensure that the local device can access the EIP.
      +
    +
  2. Install the MySQL client on the prepared ECS or device.

    For details, see How Can I Install the MySQL Client?

    +

    The MySQL client version must be the same as the version of RDS for MySQL. The MySQL database or client will provide mysqldump and mysql.

    +

    After data is migrated to RDS, you may need to change the IP address. For details, see Configuring and Changing a Floating IP Address.

    +
    +
+
+

Exporting Data

Before migrating data to RDS, 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.
+
+
  1. Log in to the ECS or the device that can access RDS.
  2. Use the mysqldump tool to export metadata into an SQL file.

    The MySQL database is required for RDS management. When exporting metadata, do not specify --all-database. Otherwise, the MySQL database 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.
    +

    Enter the database password when prompted.

    +

    Example:

    +

    mysqldump --databases rdsdb --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:

    +

    If you use mysqldump with a version earlier than 5.6, remove --set-gtid-purged=OFF before running this command.

    +
    +

    After this command is executed, a dump-defs.sql file will be generated as follows:

    +
    [rds@localhost ~]$ ll dump-defs.sql
+-rw-r-----. 1 rds rds 2714 Sep 21 08:23 dump-defs.sql
    +

  3. Use the mysqldump tool to export data into an SQL file.

    The MySQL database is required for RDS management. When exporting metadata, do not specify --all-database. Otherwise, the MySQL database 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 when prompted.

    +

    Example:

    +

    mysqldump --databases rdsdb --single-transaction --hex-blob --set-gtid-purged=OFF --no-create-info --skip-triggers -u root -p -h 192.168.151.18 -P 8635 -r dump-data.sql

    +

    If you use mysqldump with a version earlier than 5.6, remove --set-gtid-purged=OFF before running this command.

    +
    +

    After this command is executed, a dump-data.sql file will be generated as follows:

    +
    [rds@localhost ~]$ ll dump-data.sql
+-rw-r-----. 1 rds rds 2714 Sep 21 08:23 dump-data.sql
    +

+
+

Importing Data

You can connect your client to RDS and import exported SQL files into RDS.

+

If the source database calls triggers, stored procedures, functions, or events, you must set log_bin_trust_function_creators to ON on the destination database before importing data.

+
+
  1. Log in to the ECS or the device that can access RDS.
  2. Import metadata into RDS.

    # mysql -f -h <RDS_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-defs.sql

    +
    • RDS_ADDRESS: indicates the IP address of the RDS DB instance.
    • DB_PORT indicates the RDS DB 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:

    +

    If you intend to import SQL statements of a table to RDS, you are advised to specify a database. Otherwise, the error message "No database selected" may be displayed. For example, if you intend to import SQL statements of a table to database mydb, run the following command:

    +

    # mysql -f -h 172.16.66.198 -P 3306 -u root -p mydb < dump-defs.sql

    +

    Enter password:

    +
    +

  3. Import data into RDS.

    # mysql -f -h <RDS_ADDRESS> -P <DB_PORT> -u root -p < <BACKUP_DIR>/dump-data.sql

    +
    • RDS_ADDRESS: indicates the IP address of the RDS DB instance.
    • DB_PORT indicates the RDS DB 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:

    +

    If you intend to import SQL statements of a table to RDS, you are advised to specify a database. Otherwise, the error message "No database selected" may be displayed. For example, if you intend to import SQL statements of a table to database mydb, run the following command:

    +

    # mysql -f -h 172.16.66.198 -P 3306 -u root -p mydb < dump-defs.sql

    +

    Enter password:

    +
    +

  4. View the import result.

    mysql> show databases;

    +

    The following result indicates that database rdsdb has been imported.

    +
    mysql> show databases;
++--------------------+
+| Database           |
++--------------------+
+| information_schema |
+| rdsdb              |
+| mysql              |
+| performance_schema |
++--------------------+
+4 rows in set (0.00 sec)
    +

+
+
+
+
+
Parent topic: Data Migration
+
+
+ diff --git a/docs/rds/umn/rds_modify_availability.html b/docs/rds/umn/rds_modify_availability.html new file mode 100644 index 000000000..4cf00c2e5 --- /dev/null +++ b/docs/rds/umn/rds_modify_availability.html @@ -0,0 +1,15 @@ + + +

Changing the Failover Priority

+

Scenarios

You can configure the failover priority for reliability or for availability, depending on your service requirements.

+
  • Reliability: This option is selected by default. Data consistency is preferentially ensured during a primary/standby failover. This is recommended for users whose highest priority is data consistency.
  • Availability: Database availability is preferentially ensured during a primary/standby failover. This is recommended for users who require their databases to provide uninterrupted online services.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary/standby DB instances.
  5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
  6. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_modify_instance_name.html b/docs/rds/umn/rds_modify_instance_name.html new file mode 100644 index 000000000..731824b88 --- /dev/null +++ b/docs/rds/umn/rds_modify_instance_name.html @@ -0,0 +1,17 @@ + + +

Changing a DB Instance Name

+

Scenarios

You can change the name of a primary DB instance or read replica.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

    Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name field in the DB Information area, click to edit the DB 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.

    +
    • To submit the change, click .
    • To cancel the change, click .
    +

  5. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_mysql_error_log.html b/docs/rds/umn/rds_mysql_error_log.html new file mode 100644 index 000000000..044d29bb2 --- /dev/null +++ b/docs/rds/umn/rds_mysql_error_log.html @@ -0,0 +1,18 @@ + + +

Viewing Error Logs

+

RDS log management allows you to view database-level logs, including error logs and slow SQL query logs.

+

Error logs contain warning- and error-level logs generated during the database running. These can help you analyze problems with the database.

+

Viewing Log Details

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the Error Logs page, view details about error logs.

    • You can select a log level in the upper right corner to view logs of the selected level.

      For MySQL DB instances, the following levels of logs are displayed:

      +
      • ERROR
      • WARNING
      • NOTE
      +
      +
    • You can click in the upper right corner to view error logs generated in different time segments.
    • If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_mysql_recycle.html b/docs/rds/umn/rds_mysql_recycle.html new file mode 100644 index 000000000..f4b0c7a00 --- /dev/null +++ b/docs/rds/umn/rds_mysql_recycle.html @@ -0,0 +1,21 @@ + + +

Recycling a DB Instance

+

Scenarios

Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB instance are the same as those of the original DB instance. Other parameters can be reconfigured. DB instances that were deleted up to 7 days ago can be restored.

+
+

Constraints

  • Read replicas cannot be moved to the recycle bin.
  • The recycle bin is enabled by default and cannot be disabled.
+
+

Modifying Recycling Policy

A new recycling policy only applies to DB instances that were put in the recycle bin after the new policy was put into effect. For DB instances that were in the recycle bin before the modification, the original recycling policy takes effect.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Recycling Management.
  5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
  6. Then, click OK.
+
+

Rebuilding a DB Instance

You can rebuild the primary DB instances in the recycle bin within the retention period.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Recycling Management.
  5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
  6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_mysql_slow_query_log.html b/docs/rds/umn/rds_mysql_slow_query_log.html new file mode 100644 index 000000000..43e51be43 --- /dev/null +++ b/docs/rds/umn/rds_mysql_slow_query_log.html @@ -0,0 +1,17 @@ + + +

Viewing Slow Query Logs

+

Scenarios

Slow query logs record statements that exceed long_query_time. You can use these logs to identify and optimize the statements that are executing slowly.

+
RDS supports the following statement types:
  • SELECT
  • INSERT
  • UPDATE
  • DELETE
  • CREATE
+
+
+

Viewing Log Details

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the Slow Query Logs page, view details about slow query logs.

    • You can view the slow query log records of a specified execution statement type or a specific time period.
    • The long_query_time parameter determines when a slow query log is recorded. However, changes to this parameter do not affect already recorded logs. If long_query_time is changed from 1s to 0.1s, none of the previously recorded logs that do not meet the new threshold are deleted. For example, a 1.5s SQL statement that was recorded when the threshold was 1s will not be deleted now that the new threshold is 2s.
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0000.html b/docs/rds/umn/rds_pg_05_0000.html new file mode 100644 index 000000000..dc3261502 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0000.html @@ -0,0 +1,29 @@ + + +

Instance Lifecycle

+
+ + diff --git a/docs/rds/umn/rds_pg_05_0001.html b/docs/rds/umn/rds_pg_05_0001.html new file mode 100644 index 000000000..855972b78 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0001.html @@ -0,0 +1,31 @@ + + + +

Instance Modifications

+ +

+
+ + + diff --git a/docs/rds/umn/rds_pg_05_0001_02.html b/docs/rds/umn/rds_pg_05_0001_02.html new file mode 100644 index 000000000..7b6497480 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0001_02.html @@ -0,0 +1,16 @@ + + +

Data Migration

+

+
+ + diff --git a/docs/rds/umn/rds_pg_05_0005.html b/docs/rds/umn/rds_pg_05_0005.html new file mode 100644 index 000000000..28797ec1f --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0005.html @@ -0,0 +1,21 @@ + + +

Connection Management

+
+ + diff --git a/docs/rds/umn/rds_pg_05_0006.html b/docs/rds/umn/rds_pg_05_0006.html new file mode 100644 index 000000000..9d0d91e84 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0006.html @@ -0,0 +1,17 @@ + + +

Data Security

+
+ + diff --git a/docs/rds/umn/rds_pg_05_0007.html b/docs/rds/umn/rds_pg_05_0007.html new file mode 100644 index 000000000..f96fd52c9 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0007.html @@ -0,0 +1,17 @@ + + +

Task Center

+
+ + diff --git a/docs/rds/umn/rds_pg_05_0017.html b/docs/rds/umn/rds_pg_05_0017.html new file mode 100644 index 000000000..7c74f1320 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0017.html @@ -0,0 +1,16 @@ + + +

Exporting DB Instance Information

+

Scenarios

You can export information about all or selected DB instances to view and analyze DB instance information.

+
+

Exporting Information About All DB Instances

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
  5. Find a .csv file locally after the export task is completed.
+
+

Exporting Information About Selected DB Instances

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
  5. Find a .csv file locally after the export task is completed.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0018.html b/docs/rds/umn/rds_pg_05_0018.html new file mode 100644 index 000000000..86ce548fc --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0018.html @@ -0,0 +1,17 @@ + + +

Applying a Parameter Template

+

Scenarios

You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

    • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
    • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.
    +

    A parameter template can be applied to one or more DB instances.

    +

  5. In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.

    After the parameter template is successfully applied, you can view the application records by referring to section Viewing Application Records of a Parameter Template.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0023.html b/docs/rds/umn/rds_pg_05_0023.html new file mode 100644 index 000000000..4c76f2812 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0023.html @@ -0,0 +1,16 @@ + + +

Changing a DB Instance Type from Single to Primary/Standby

+

Scenarios

  • RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.
  • Primary/standby DB instances support automatic failover. If the primary DB instance fails, the standby DB instance takes over services quickly. You are advised to deploy primary and standby DB instances in different AZs for high availability and disaster recovery.
  • Anti-affinity deployment is supported for primary/standby DB instances to prevent the entire instance unavailability due to the failure of a single host.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate a single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

    Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

    +

  5. Select a standby AZ. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
  6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

    • The DB instance is in the Changing type to primary/standby status. You can view the progress on the Task Center page. For details, see Task Center.
    • In the upper right corner of the DB instance list, click to refresh the list. After the DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0024.html b/docs/rds/umn/rds_pg_05_0024.html new file mode 100644 index 000000000..996fd1acb --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0024.html @@ -0,0 +1,20 @@ + + +

Configuring and Changing a Floating IP Address

+

Scenarios

You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.

+
+

Constraints

After a floating IP address is changed, the domain name needs to be resolved again. This operation takes several minutes and may interrupt database connections. Therefore, you are advised to change a floating IP address during off-peak hours.

+
+

Configuring a Floating IP Address

You can use an automatically-assigned IP address when creating a DB instance.

+
+

Changing a Floating IP Address

You can change the floating IP address of an existing DB instance.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
  6. In the displayed dialog box, enter a new floating IP address and click OK.

    In the in-use IP address list, the IP addresses whose statuses are To be used are occupied and cannot be used.

    +

+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0034.html b/docs/rds/umn/rds_pg_05_0034.html new file mode 100644 index 000000000..2c2b9ad31 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0034.html @@ -0,0 +1,33 @@ + + +

Backups and Restorations

+
+ + diff --git a/docs/rds/umn/rds_pg_05_0038.html b/docs/rds/umn/rds_pg_05_0038.html new file mode 100644 index 000000000..129c2fa21 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0038.html @@ -0,0 +1,18 @@ + + +

Changing the Maintenance Window

+

Scenarios

The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off-peak hours.

+
+

Precautions

  • During the maintenance window, the DB instance will be intermittently disconnected for one or two times. Ensure that your applications support automatic reconnection.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. In the DB Information area on the Basic Information page, click Change in the Maintenance Window field.
  5. In the displayed dialog box, select a maintenance window and click OK.

    Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

    +
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0055.html b/docs/rds/umn/rds_pg_05_0055.html new file mode 100644 index 000000000..7205d2c98 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0055.html @@ -0,0 +1,19 @@ + + +

Creating a Same DB Instance as an Existing DB Instance

+

Scenarios

This section describes how to quickly create a DB instance with the same configurations as the selected one.

+
  • You can create DB instances with the same configurations numerous times.
  • This function is unavailable for read replicas.
+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Create Same DB Instance in the Operation column.
  5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Next.

    For details about PostgreSQL DB instance configurations, see section Step 1: Create a DB Instance.

    +

  6. Confirm the instance specifications.

    +

  7. Refresh the DB instance list and view the status of the DB instance. If the status is Available, it has been created successfully.

    You can manage the DB instance on the Instances page.

    +

+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0098.html b/docs/rds/umn/rds_pg_05_0098.html new file mode 100644 index 000000000..8b13a6f61 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0098.html @@ -0,0 +1,15 @@ + + +

Viewing Application Records of a Parameter Template

+

Scenarios

You can view the application records of a parameter template.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left.
  5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

    You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0099.html b/docs/rds/umn/rds_pg_05_0099.html new file mode 100644 index 000000000..d48357d7e --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0099.html @@ -0,0 +1,21 @@ + + +

Viewing Parameter Change History

+

Scenarios

You can view the change history of DB instance parameters or custom parameter templates.

+

An exported or custom parameter template has initially a blank change history.

+
+
+

Viewing Change History of a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

    You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

    +

    You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.

    +

+
+

Viewing Change History of a Parameter Template

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  5. On the displayed page, choose Change History in the navigation pane on the left.

    You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_05_0138.html b/docs/rds/umn/rds_pg_05_0138.html new file mode 100644 index 000000000..51003fc63 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0138.html @@ -0,0 +1,16 @@ + + +

Downloading an Incremental Backup File

+

Scenarios

This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.

+

RDS for PostgreSQL enables you to download incremental backup files.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. Choose Backups & Restorations in the navigation pane on the left. On the Incremental Backups page, locate the target backup to be downloaded and click Download in the Operation column.

    You can also select the incremental backups to be downloaded and click Download above the list.

    +

  5. After the download is complete, you can view the incremental backups locally.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_pg_06_0001.html b/docs/rds/umn/rds_pg_06_0001.html new file mode 100644 index 000000000..c481c70ff --- /dev/null +++ b/docs/rds/umn/rds_pg_06_0001.html @@ -0,0 +1,291 @@ + + +

Configuring Displayed Metrics

+

The RDS Agent monitors RDS DB instances and collects monitoring metrics only.

+

Description

This section describes the metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the monitoring metrics and alarms generated for RDS.

+
+

Namespace

SYS.RDS

+
+

DB Instance Monitoring Metrics

  • Table 1 lists the performance metrics of PostgreSQL databases. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Database performance metrics

    Metric

    +

    Name

    +

    Description

    +

    Value Range

    +

    Monitored Object

    +

    Monitoring Interval (Raw Data)

    +

    rds001_cpu_util

    +

    CPU Usage

    +

    CPU usage of the monitored object

    +

    0-100%

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds002_mem_util

    +

    Memory Usage

    +

    Memory usage of the monitored object

    +

    0-100%

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds003_iops

    +

    IOPS

    +

    Average number of I/O requests processed by the system in a specified period

    +

    ≥ 0 counts/s

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds004_bytes_in

    +

    Network Input Throughput

    +

    Incoming traffic in bytes per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds005_bytes_out

    +

    Network Output Throughput

    +

    Outgoing traffic in bytes per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds039_disk_util

    +

    Storage Space Usage

    +

    Storage space usage of the monitored object

    +

    0-100%

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds040_transaction_logs_usage

    +

    Transaction Logs Usage

    +

    Storage space usage of transaction logs

    +

    ≥ 0 MB

    +

    Monitored object: database

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds041_replication_slot_usage

    +

    Replication Slot Usage

    +

    Storage space usage of replication slot files

    +

    ≥ 0 MB

    +

    Monitored object: database

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds042_database_connections

    +

    Database Connections in Use

    +

    Number of database connections in use

    +

    ≥ 0 counts

    +

    Monitored object: database

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds043_maximum_used_transaction_ids

    +

    Maximum Used Transaction IDs

    +

    Maximum number of transaction IDs that have been used

    +

    ≥ 0 counts

    +

    Monitored object: database

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds044_transaction_logs_generations

    +

    Transaction Logs Generation

    +

    Size of transaction logs generated per second

    +

    ≥ 0 MB/s

    +

    Monitored object: database

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds045_oldest_replication_slot_lag

    +

    Oldest Replication Slot Lag

    +

    Lagging size of the most lagging replica in terms of WAL data received

    +

    ≥ 0 MB

    +

    Monitored object: database

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds046_replication_lag

    +

    Replication Lag

    +

    Replication lag

    +

    ≥ 0 ms

    +

    Monitored object: database

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds047_disk_total_size

    +

    Total Storage Space

    +

    Total storage space of the monitored object

    +

    40–4,000 GB

    +

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds048_disk_used_size

    +

    Used Storage Space

    +

    Used storage space of the monitored object

    +

    0–4,000 GB

    +

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds049_disk_read_throughput

    +

    Disk Read Throughput

    +

    Number of bytes read from the disk per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +

    rds050_disk_write_throughput

    +

    Disk Write Throughput

    +

    Number of bytes written into the disk per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: PostgreSQL instance

    +

    1 minute

    +
    +
    +
+
+

Dimension

+
+ + + + + + + +

Key

+

Value

+

postgresql_instance_id

+

PostgreSQL DB instance ID

+
+
+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_pg_06_0002.html b/docs/rds/umn/rds_pg_06_0002.html new file mode 100644 index 000000000..ef3ed3dc5 --- /dev/null +++ b/docs/rds/umn/rds_pg_06_0002.html @@ -0,0 +1,16 @@ + + +

Setting Alarm Rules

+

Scenarios

You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.

+

The RDS alarm rules include alarm rule names, services, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

+
+

Setting Alarm Rules

  1. Log in to the management console.
  2. Click Service List and choose Management & Governance > Cloud Eye.
  3. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
  4. On the displayed Alarm Rules page, click Create Alarm Rule.

    For details about how to create alarm rules, see Using Alarm Templates to Create an Alarm Rule in the Cloud Eye User Guide.

    +

+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_pg_06_0003.html b/docs/rds/umn/rds_pg_06_0003.html new file mode 100644 index 000000000..80c3a5b6f --- /dev/null +++ b/docs/rds/umn/rds_pg_06_0003.html @@ -0,0 +1,24 @@ + + +

Viewing Monitoring Metrics

+

Scenarios

Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.

+

Monitored data takes some time before it can be displayed. The RDS status displayed on the Cloud Eye console is about 5 to 10 minutes delayed. When you create a new RDS DB instance, it takes 5 to 10 minutes before monitoring data is displayed on Cloud Eye.

+
+

Prerequisites

  • RDS is running properly.

    Monitoring metrics of the RDS DB instances that are faulty or have been deleted are not displayed on the Cloud Eye console. You can view their monitoring metrics after they are rebooted or restored to normal.

    +
+

If an RDS DB instance has been faulty for 24 hours, Cloud Eye considers it to no longer exist and deletes it from the monitoring object list. You need to manually clear the alarm rules created for the DB instance.

+
+
  • RDS has been running properly for about 10 minutes.

    For a newly created RDS DB instance, you need to wait a bit before you can view the metrics.

    +
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

    Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

    +

  5. On the Cloud Eye console, view monitoring metrics of the primary DB instance.

    Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 30 days, and 7 days.

    +

+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_pg_06_0004.html b/docs/rds/umn/rds_pg_06_0004.html new file mode 100644 index 000000000..33ff89e7e --- /dev/null +++ b/docs/rds/umn/rds_pg_06_0004.html @@ -0,0 +1,275 @@ + + +

Key Operations Supported by CTS

+

Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 RDS operations that can be recorded by CTS

Operation

+

Resource Type

+

Trace Name

+

Creating a DB instance or a read replica, or restoring data to a new DB instance

+

instance

+

createInstance

+

Scaling up storage space and changing instance class

+

instance

+

instanceAction

+

Rebooting a DB instance

+

instance

+

instanceRestart

+

Restoring data to the original DB instance

+

instance

+

instanceRestore

+

Renaming a DB instance

+

instance

+

instanceRename

+

Resetting a password

+

instance

+

resetPassword

+

Setting database version parameters

+

instance

+

setDBParameters

+

Resetting database version parameters

+

instance

+

resetDBParameters

+

Enabling, modifying, or disabling a backup policy

+

instance

+

setBackupPolicy

+

Changing a database port

+

instance

+

changeInstancePort

+

Binding or unbinding an EIP

+

instance

+

setOrResetPublicIP

+

Modifying a security group

+

instance

+

modifySecurityGroup

+

Adding a tag

+

instance

+

createTag

+

Deleting a tag

+

instance

+

deleteTag

+

Editing a tag

+

instance

+

modifyTag

+

Deleting a DB instance

+

instance

+

deleteInstance

+

Performing a primary/standby switchover

+

instance

+

instanceFailOver

+

Changing a synchronize model

+

instance

+

instanceFailOverMode

+

Changing a failover priority

+

instance

+

instanceFailOverStrategy

+

Changing a DB instance type from single to primary/standby

+

instance

+

modifySingleToHaInstance

+

Creating a backup

+

backup

+

createManualSnapshot

+

Replicating a backup

+

backup

+

copySnapshot

+

Downloading a backup (using OBS)

+

backup

+

downLoadSnapshot

+

Downloading a backup (using a browser)

+

backup

+

backupsDownLoad

+

Deleting a backup

+

backup

+

deleteManualSnapshot

+

Downloading a merged backup

+

backup

+

packBackupsDownLoad

+

Creating a parameter template

+

parameterGroup

+

createParameterGroup

+

Modifying parameters in a parameter template

+

parameterGroup

+

updateParameterGroup

+

Deleting a parameter template

+

parameterGroup

+

deleteParameterGroup

+

Replicating a parameter template

+

parameterGroup

+

copyParameterGroup

+

Resetting a parameter template

+

parameterGroup

+

resetParameterGroup

+

Comparing parameter templates

+

parameterGroup

+

compareParameterGroup

+

Applying a parameter template

+

parameterGroup

+

applyParameterGroup

+

Saving parameters in a parameter template

+

parameterGroup

+

saveParameterGroup

+

Deleting a frozen DB instance

+

all

+

rdsUnsubscribeInstance

+

Freezing a DB instance

+

all

+

rdsfreezeInstance

+
+
+
+
+
+
Parent topic: Interconnection with CTS
+
+
+ diff --git a/docs/rds/umn/rds_pg_06_0005.html b/docs/rds/umn/rds_pg_06_0005.html new file mode 100644 index 000000000..ccc62bf87 --- /dev/null +++ b/docs/rds/umn/rds_pg_06_0005.html @@ -0,0 +1,18 @@ + + +

Viewing Tracing Events

+

Scenarios

After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.

+

This section describes how to query the operation records of last 7 days on the CTS console.

+
+

Procedure

  1. Log in to the management console.
  2. Choose Management & Governance > Cloud Trace Service.
  3. Choose Trace List in the navigation pane on the left.
  4. Filter conditions to query traces. The details are described as follows:

    • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

      When you select Resource ID for Search By, you also need to select or enter a resource ID.

      +
    • Operator: Select a specific operator from the drop-down list.
    • Trace Status: Available options include All trace statuses, Normal, Warning, and Incident. You can only select one of them.
    • In the upper right corner of the page, you can specify a time range for querying traces.
    +

  5. Select the search criteria, and click Query.
  6. Click on the left of the required trace to expand its details.
  7. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
  8. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

    For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

    +

+
+
+
+
+
Parent topic: Interconnection with CTS
+
+
+ diff --git a/docs/rds/umn/rds_pg_06_0022.html b/docs/rds/umn/rds_pg_06_0022.html new file mode 100644 index 000000000..e0c064e15 --- /dev/null +++ b/docs/rds/umn/rds_pg_06_0022.html @@ -0,0 +1,16 @@ + + +

Selecting Displayed Items

+

Scenarios

You can customize which instance items are displayed on the Instances page.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click to edit columns displayed in the DB instance list.

    • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

      These default items cannot be deselected.

      +
    • In a single project, you can select up to 9 items: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, creation time, database port, storage type, and operation.
    +

+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_pg_08_0042.html b/docs/rds/umn/rds_pg_08_0042.html new file mode 100644 index 000000000..156ab0c26 --- /dev/null +++ b/docs/rds/umn/rds_pg_08_0042.html @@ -0,0 +1,22 @@ + + +

Exporting a Parameter Template

+

Scenarios

  • You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Parameter Template.
  • You can export the parameter template information (parameter names, values, and descriptions) of a DB instance to a CSV file for viewing and analysis.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

    • Exporting to a custom template
      In the displayed dialog box, configure required information and click OK.
      • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
      • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
      +
      +
      +

      After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

      +
    • Exporting to a file
      The parameter template information (parameter names, values, and descriptions) of a DB instance is exported to a CSV file. In the displayed dialog box, enter the file name and click OK.

      The file name must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

      +
      +
      +
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_08_0044.html b/docs/rds/umn/rds_pg_08_0044.html new file mode 100644 index 000000000..16a44eb95 --- /dev/null +++ b/docs/rds/umn/rds_pg_08_0044.html @@ -0,0 +1,23 @@ + + +

Restoring from Full Backup Files to a Self-Built PostgreSQL Database

+

You can download backup files by referring to Downloading a Full Backup File and restore data from them.

+

Prerequisites

  1. A tool for decompressing TAR files must be installed in a Unix-like system.
  2. Either python2.7 or python3 can be used.
  3. The following third-party packages need to be installed: lz4, gzip, and shutil.
  4. The version of the local database must be the same as that of the cloud database.
  5. Plugins of the same version as the cloud database are installed in the local database.
+
+

Procedure

  1. Prepare a local directory for storing tablespaces.
  2. Stop the local database server.
  3. Store the following configuration files in the data directory of the local database to another directory: postgresql.conf, pg_hba.conf, and recovery.done.
  4. Clear the data directory of the local database.
  5. Download the decompression tool.
  6. Run the following command to decompress backup files to the directory prepared in Step 1:

    python restore_obs_file.py src_file target_dir

    +

    Variables in the command are described as follows:

    +

    src_file: indicates the directory where PostgreSQL full backup files are stored.

    +

    target_dir: indicates the directory to which data is restored. The directory has been prepared in 1. The directory must be empty. If the directory does not exist, the system automatically creates it.

    +

    The following directories are generated after the decompression:

    +
    • data: stores full backup data. The recovery.done file has been deleted.
    • xlog: stores incremental backup data.
    • tblspc: stores tablespace directory files (if the original backup contains tablespace files).
    +

  7. Copy the files in 6 to the specified directory of the local database.

    1. Copy all the decompressed files in the data directory to the data directory of the local database, and then replace the three files in the data directory of the local database with the configuration files saved in step 3.
    2. Copy the decompressed files in the xlog directory to the pg_xlog or pg_wal folder in the data directory of the local database. (The folder names vary according to database versions.)
    3. Move the decompressed tablespace folder (if any) in the tblspc directory to the tablespace directory created in step 1 and modify the soft link of the corresponding tablespace in data\tablespace_map.

      +
    +

  8. Reboot the database and wait until the database restoration is complete.
+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_pg_10_0000.html b/docs/rds/umn/rds_pg_10_0000.html new file mode 100644 index 000000000..1ade99444 --- /dev/null +++ b/docs/rds/umn/rds_pg_10_0000.html @@ -0,0 +1,16 @@ + + +

Parameter Tuning

+

+
+ + diff --git a/docs/rds/umn/rds_pg_10_0001.html b/docs/rds/umn/rds_pg_10_0001.html new file mode 100644 index 000000000..65e0ad84e --- /dev/null +++ b/docs/rds/umn/rds_pg_10_0001.html @@ -0,0 +1,20 @@ + + +

Suggestions on PostgreSQL Parameter Tuning

+

Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some important parameters for your reference. For details, visit the PostgreSQL official website.

+

For details on how to modify PostgreSQL parameters on the console, see Modifying Instance Parameters.

+

Sensitive Parameters

The following parameters can result in system security and stability issues if set improperly:

+
  • The search_path parameter must be set to a schema sequence where schemas are separated by commas (,). Ensure that the schemas exist. Otherwise, the database performance will be affected.
  • If you enable the parameter log_duration, SQL statements containing sensitive information may be recorded in logs. You are advised to disable this parameter.
  • log_min_duration_statement specifies how many milliseconds a query has to run before it has to be logged. The unit is millisecond. Setting this parameter to 0 means that all statements are recorded. Setting this parameter to -1 means that no statement is recorded. For details, see Viewing Slow Query Logs.
  • The parameters nls_timestamp_format and nls_date_format control the input and output formats of timestamp and date. They are available only for PostgreSQL Enhanced Edition.
    • The nls_timestamp_format parameter defines the timestamp format. The nls_date_format defines the date format.
    +
  • The temp_file_limit parameter specifies the maximum amount of disk space (in KB) that a session can use for temporary files. It supports PostgreSQL 11, 12, and 13 only. Changing this parameter value is a high-risk operation. Exercise caution when deciding to perform this operation.
    • If the parameter value exceeds the threshold, the DB instance will become unavailable.
    • If the parameter value is changed to a larger value for temporary use but is not changed to the original value after the use, the disk space will be continuously used to store temporary files. If the disk space is used up, services will be interrupted and the DB instance will become unavailable.
    +
+
+

Performance Parameters

The following parameters can affect database performance:

+
  • If log_statement is set to ddl, mod, or all, the operations for creating and deleting database users (including passwords and other sensitive information) are recorded. This operation affects database performance. Exercise caution when setting this parameter.
  • Enabling the following parameters will affect the database performance: log_hostname, log_duration, log_connections, and log_disconnections. Exercise caution when enabling these parameters.
+
+
+
+
+
Parent topic: Parameter Tuning
+
+
+ diff --git a/docs/rds/umn/rds_pg_11_0001.html b/docs/rds/umn/rds_pg_11_0001.html new file mode 100644 index 000000000..256662744 --- /dev/null +++ b/docs/rds/umn/rds_pg_11_0001.html @@ -0,0 +1,19 @@ + + +

Read Replicas

+
+ + diff --git a/docs/rds/umn/rds_pg_11_0002.html b/docs/rds/umn/rds_pg_11_0002.html new file mode 100644 index 000000000..f6d77aea3 --- /dev/null +++ b/docs/rds/umn/rds_pg_11_0002.html @@ -0,0 +1,20 @@ + + +

Introducing Read Replicas

+

Introduction

RDS for PostgreSQL supports read replicas.

+

In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To expand the DB instance read ability to offload read pressure on the database, you can create one or more read replicas in a region. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses of the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.

+

A read replica uses a single-node architecture (without a slave node). Changes to the primary DB instance are also automatically synchronized to all associated read replicas through the native PostgreSQL replication function. The synchronization is not affected by network latency. Read replicas and the primary DB instance must be in the same region but can be in different AZs.

+
+

Functions

  • Read replica specifications can be different from primary DB instance specifications. It is recommended that the read replica specifications be greater than or equal to the primary DB instance specifications to prevent long delay and high load.
  • You do not need to maintain separate database accounts or databases. They are synchronized from the primary DB instance.
  • Read replicas support system performance monitoring. RDS provides up to 20 monitoring metrics, including storage space, IOPS, the number of database connections, CPU usage, and network traffic. You can view these metrics to learn about the load on DB instances.
  • Read replicas do not support automated backups or manual backups.
  • Read replicas do not support restoration from backups to new, existing, or original read replicas.
  • Data cannot be migrated to read replicas.
  • Read replicas do not support database creation and deletion.
  • Read replicas do not support database account creation.
  • The specifications of read replicas must be greater than or equal to the specifications of the current primary DB instance.
+
+

Constraints

  • A maximum of five read replicas can be created for each primary DB instance.
+
+

Creating and Managing a Read Replica

+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_pg_11_0004.html b/docs/rds/umn/rds_pg_11_0004.html new file mode 100644 index 000000000..2000a19fb --- /dev/null +++ b/docs/rds/umn/rds_pg_11_0004.html @@ -0,0 +1,16 @@ + + +

Managing a Read Replica

+

Entering the Management Interface Through a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Basic Information page.
+
+

Entering the Management Interface Through a Primary DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
  5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
+
+

Deleting a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the DB instance list, click in front of a DB instance, locate the read replica to be deleted, and choose More > Delete in the Operation column.
+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_pg_11_0005.html b/docs/rds/umn/rds_pg_11_0005.html new file mode 100644 index 000000000..63fcfc6e1 --- /dev/null +++ b/docs/rds/umn/rds_pg_11_0005.html @@ -0,0 +1,28 @@ + + +

Connecting to a DB Instance Through pgAdmin

+

You can use the pgAdmin client to connect to an RDS DB instance.

+

The pgAdmin version must be 4 or later.

+
+

Preparations

  1. Prepare an ECS or a device that can access RDS DB instances.

    To connect to a DB instance through a floating IP address, you must:

    +
    • Ensure that the ECS and DB instance must be in the same VPC.
    • Ensure that the ECS must be allowed by the security group to access RDS DB instances.
    +
    To connect to a DB instance through an EIP, you must:
    1. Bind the EIP to the DB instance. For details, see Binding an EIP.
    2. Ensure that the local device can access the EIP that has been bound to the DB instance.
    +
    +
  2. Install the pgAdmin client on the prepared ECS or device.
+
+

Procedure

  1. Start pgAdmin.
  2. In the displayed login window, choose Servers > Create > Server.

    Figure 1 Creation
    +

    +

  3. On the General page, specify Name. On the Connection page, specify information about the DB instance to be connected. Then, click Save.

    Figure 2 General page
    +

    +
    Figure 3 Connection page
    +

    Parameter description:

    +
    • Host name/address: indicates the IP address of the DB instance you want to connect to. If you connect to a DB instance through a floating IP address, enter the floating IP address displayed in the Connection Information area on the Basic Information page of your DB instance. If you connect to a DB instance through an EIP, enter the EIP of your DB instance.
    • Port: indicates the database port. By default, the value is 5432.
    • User name: indicates the username. By default, the value is root.
    • Password: indicates the password of the target database username.
    +

  4. In the login window, check that the connection information is correct. The target DB instance is successfully connected.
+
+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_backup_restore.html b/docs/rds/umn/rds_pg_backup_restore.html new file mode 100644 index 000000000..cfb09dea0 --- /dev/null +++ b/docs/rds/umn/rds_pg_backup_restore.html @@ -0,0 +1,17 @@ + + +

Working with Backups

+

RDS supports backups and restorations to ensure data reliability.

+

Automated Backups

Automated backups are created during the backup time window for your DB instances. RDS saves automated backups based on a retention period you specify. If necessary, you can restore to any point in time during your backup retention period. For details, see Configuring an Automated Backup Policy.

+
+

Manual Backups

Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually. For details, see Creating a Manual Backup.

+
+

Downloading a Backup File

You can download a full or an incremental backup file for local data backup or restoration. For details, see Downloading a Full Backup File and Downloading an Incremental Backup File.

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_pg_change_database_port.html b/docs/rds/umn/rds_pg_change_database_port.html new file mode 100644 index 000000000..86c669281 --- /dev/null +++ b/docs/rds/umn/rds_pg_change_database_port.html @@ -0,0 +1,19 @@ + + +

Changing a Database Port

+

Scenarios

This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the primary DB instance will cause the database port of the standby DB instance to also be changed accordingly.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance or click first and then click the target read replica.
  5. In the Connection Information area on the Basic Information page, click in the Database Port field.

    A PostgreSQL database can use ports 2100 to 9500.

    +
    +
    • To submit the change, click .
      • In the dialog box, click Yes.
        1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
        2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will be rebooted.
        3. This process takes 1-5 minutes.
        +
      • In the dialog box, click No to cancel the modification.
      +
    • To cancel the change, click .
    +

  6. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_configuration.html b/docs/rds/umn/rds_pg_configuration.html new file mode 100644 index 000000000..0159ef542 --- /dev/null +++ b/docs/rds/umn/rds_pg_configuration.html @@ -0,0 +1,31 @@ + + +

Modifying Instance Parameters

+

You can modify parameters in a custom parameter template to optimize RDS database performance.

+

You can change parameter values in custom parameter templates only and cannot change parameter values in default parameter templates. When you change parameter values in a custom parameter template, the changes take effect for all DB instances that the parameter template applies to.

+

When you modify a parameter, the time when the modification takes effect is determined by the type of the parameter.

+

The RDS console displays the statuses of DB instances that the parameter template applies to. For example, if the DB instance has not yet used the latest modifications made to its parameter template, its status is Parameter change. Pending reboot. Manually reboot the DB instance for the latest modifications to take effect for that DB instance.

+

RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly, the database startup may fail. If this happens, you can re-configure the custom parameter template based on the settings of the default parameter template.

+
+

Modifying Parameters of a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

    Available operations are Save, Cancel, and Preview:

    +
    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +
    In the Effective upon Reboot column:
    • If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.
      • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
      • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
      +
    • If the value is No, the modifications take effect immediately.
    +
    +
    +

    After parameters are modified, you can view parameter change history by referring to section Viewing Parameter Change History.

    +

+
+

Modifying Parameter Template Parameters

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  5. On the Parameters page, modify parameters as required.

    Available operations are Save, Cancel, and Preview:

    +
    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +

  6. After the parameter values are modified, you can click View Change History to view the modification details.
  7. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
  8. View the status of the DB instance to which the parameter template was applied.

    If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.

    +
    • A DB instance reboot caused by instance class changes will not make parameter modifications take effect.
    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_modify_availability.html b/docs/rds/umn/rds_pg_modify_availability.html new file mode 100644 index 000000000..645a41619 --- /dev/null +++ b/docs/rds/umn/rds_pg_modify_availability.html @@ -0,0 +1,15 @@ + + +

Changing the Failover Priority

+

Scenarios

You can configure the failover priority for reliability or for availability, depending on your service requirements.

+
  • Reliability: This option is selected by default. Data consistency is preferentially ensured during a primary/standby failover. This is recommended for users whose highest priority is data consistency.
  • Availability: Database availability is preferentially ensured during a primary/standby failover. This is recommended for users who require their databases to provide uninterrupted online services.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary/standby DB instances.
  5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
  6. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_pg_modify_instance_name.html b/docs/rds/umn/rds_pg_modify_instance_name.html new file mode 100644 index 000000000..f86decadf --- /dev/null +++ b/docs/rds/umn/rds_pg_modify_instance_name.html @@ -0,0 +1,17 @@ + + +

Changing a DB Instance Name

+

Scenarios

You can change the name of a primary DB instance or read replica.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

    Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name field in the DB Information area, click to edit the DB 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.

    +
    • To submit the change, click .
    • To cancel the change, click .
    +

  5. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_pg_parameter_group.html b/docs/rds/umn/rds_pg_parameter_group.html new file mode 100644 index 000000000..3d57a43ec --- /dev/null +++ b/docs/rds/umn/rds_pg_parameter_group.html @@ -0,0 +1,24 @@ + + +

Creating a Parameter Template

+

You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

+

When you create a DB instance, RDS will automatically allocate a default database parameter template for you. This default template contains DB engine defaults and system defaults that are configured based on the engine, compute class, and allocated storage of the instance. Default parameter templates cannot be modified, but you can create your own parameter template to change parameter settings.

+

Not all of the DB engine parameters in a custom parameter template can be changed.

+
+

If you want to use a custom parameter template, you simply create a parameter template and select it when you create a DB instance or apply it to an existing DB instance following the instructions provided in section Applying a Parameter Template.

+

When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template following the instructions provided in section Replicating a Parameter Template.

+

The following are the key points you should know when using parameters in a parameter template:

+
  • When you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately. When you change a static parameter value in a parameter template and save the change, the change will take effect only after you manually reboot the DB instances that the parameter template applies to.
  • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
+

RDS does not share parameter template quotas with DDS.

+

You can create a maximum of 100 parameter templates for RDS DB instances. All RDS DB engines share the parameter template quota.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Create Parameter Template.
  5. In the displayed dialog box, configure required information and click OK.

    • Select a DB engine for the parameter template.
    • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
    • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_public_accessibility.html b/docs/rds/umn/rds_pg_public_accessibility.html new file mode 100644 index 000000000..1eec51bb3 --- /dev/null +++ b/docs/rds/umn/rds_pg_public_accessibility.html @@ -0,0 +1,24 @@ + + +

Binding and Unbinding an EIP

+

Scenarios

By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you can unbind the EIP from the DB instance later if needed.

+

To ensure that the DB instance is accessible, the security group associated with the instance must allow access over the database port. For example, if the database port is 5432, ensure that the security group allows access over the 5432 port.

+
+
+

Prerequisites

  • You have assigned an EIP on the VPC console.
  • You can bind an EIP to a primary DB instance or a read replica only.
  • 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.
+
+

Binding an EIP

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the EIPs page, click Bind EIP.
  6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP and obtain an EIP.
  7. On the EIPs page of the RDS console, view the EIP that has been bound to the DB instance.

    You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

    +

    To unbind the EIP from the DB instance, see Unbinding an EIP.

    +

+
+

Unbinding an EIP

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the DB instance that has an EIP bound.
  5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
  6. On the EIPs page, view the unbinding result.

    You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

    +

    To bind an EIP to the DB instance again, see Binding an EIP.

    +

+
+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_pg_recycle.html b/docs/rds/umn/rds_pg_recycle.html new file mode 100644 index 000000000..282f7a197 --- /dev/null +++ b/docs/rds/umn/rds_pg_recycle.html @@ -0,0 +1,21 @@ + + +

Recycling a DB Instance

+

Scenarios

Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB instance are the same as those of the original DB instance. Other parameters can be reconfigured. DB instances that were deleted up to 7 days ago can be restored.

+
+

Constraints

  • Read replicas cannot be moved to the recycle bin.
  • The recycle bin is enabled by default and cannot be disabled.
+
+

Modifying Recycling Policy

A new recycling policy only applies to DB instances that were put in the recycle bin after the new policy was put into effect. For DB instances that were in the recycle bin before the modification, the original recycling policy takes effect.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Recycling Management.
  5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
  6. Then, click OK.
+
+

Rebuilding a DB Instance

You can rebuild the primary DB instances in the recycle bin within the retention period.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Recycling Management.
  5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
  6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_pg_reset_password.html b/docs/rds/umn/rds_pg_reset_password.html new file mode 100644 index 000000000..38e917130 --- /dev/null +++ b/docs/rds/umn/rds_pg_reset_password.html @@ -0,0 +1,29 @@ + + +

Resetting the Administrator Password

+

Scenarios

You can reset the administrator password of a primary instance.

+

You can also reset the password of your database account when using RDS.

+
+
  • If you have changed the administrator password of the primary DB instance, the administrator passwords of the standby DB instance and read replicas (if any) will also be changed accordingly.
  • The time required for the new password to take effect depends on the amount of service data currently being processed by the primary DB instance.
  • To protect against brute force hacking attempts and ensure system security, change your password periodically, such as every three or six months.
+
+

Method 1

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Reset Password in the Operation column.
  5. Enter and confirm a new 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 types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it for security reasons.

    +
    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
    • To submit the new password, click OK.
    • To cancel the reset operation, click Cancel.
    +
    +

+
+

Method 2

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field.
  6. Enter and confirm a new 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 types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#%^*-_=+?). Enter a strong password and periodically change it for security reasons.

    +
    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
    • To submit the new password, click OK.
    • To cancel the reset operation, click Cancel.
    +
    +

+
+
+
+
+
Parent topic: Data Security
+
+
+ diff --git a/docs/rds/umn/rds_pg_scale_cluster.html b/docs/rds/umn/rds_pg_scale_cluster.html new file mode 100644 index 000000000..2b6cbf3ac --- /dev/null +++ b/docs/rds/umn/rds_pg_scale_cluster.html @@ -0,0 +1,32 @@ + + +

Scaling up Storage Space

+

Scenarios

If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

+

The DB instance needs to preserve at least 15% of its capacity to work properly. The new minimum storage space required to make this instance available has been automatically calculated for you. You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

+

For details about the causes and solutions of insufficient storage space, see What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?

+

RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

+
+

Constraints

  • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
  • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
  • You cannot reboot or delete a DB instance that is being scaled up.
  • Storage space can only be scaled up.
  • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.
+
+

Scaling up a Primary DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Scale Storage Space in the Operation column.

    You can also perform the following operations to scale up storage space:

    +
    • Click the target DB instance to enter the Basic Information page. In the Storage Space area, click Scale.
    +

  5. On the displayed page, specify the new storage space and click Next.

    The minimum start value of each scaling is 10 GB. A DB instance can be scaled up only by a multiple of 10 GB. The allowed maximum storage space is 4,000 GB.

    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. View the scale-up result.

    Scaling up storage space takes 3-5 minutes. During the time period, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Basic Information page to verify that the scale-up is successful.

    +

+
+

Scaling up a Read Replica

Scaling up the storage space of a read replica does not affect that of the primary DB instance. Therefore, you can separately scale read replicas to meet service requirements. New storage space of read replicas after scaling up must be greater than or equal to that of the primary DB instance.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click in front of it. Locate a read replica to be scaled and choose More > Scale Storage Space in the Operation column.

    You can also perform the following operations to scale up storage space:

    +
    • Click the target DB instance to enter the Basic Information page. In the Storage Space area, click Scale.
    +

  5. On the displayed page, specify the new storage space and click Next.

    The minimum start value of each scaling is 10 GB. A read replica can be scaled up only by a multiple of 10 GB. The allowed maximum storage space is 4,000 GB.

    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. View the scale-up result.

    Scaling up storage space takes 3-5 minutes. During this time, the status of the read replica on the Instances page will be Scaling up. Click the read replica and view the utilization on the displayed Basic Information page to verify that the scale-up is successful.

    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_pg_scale_rds.html b/docs/rds/umn/rds_pg_scale_rds.html new file mode 100644 index 000000000..a351c06fd --- /dev/null +++ b/docs/rds/umn/rds_pg_scale_rds.html @@ -0,0 +1,22 @@ + + +

Changing a DB Instance Class

+

Scenarios

You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.

+
+

Constraints

  • A DB instance cannot be deleted when its instance class is being changed.
  • If the primary DB instance has a read replica, the new DB instance class must be less than or equal to the read replica class. When changing the read replica class, ensure that the selected class is greater than or equal to the current primary instance class.
+
  • After you change instance classes, the DB instances will be rebooted and service will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

    Alternatively, click the target DB instance to go to the Basic Information page. In the DB Information area, click Change in the Instance Class field.

    +

  5. On the displayed page, specify the new instance class and click Next.
  6. View the DB instance class change result.

    Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Basic Information page to check that the change is successful.

    +

    After the CPU or memory of a PostgreSQL DB instance is changed, the system will change the values of the following parameters accordingly:

    +
    • shared_buffers
    • max_connections
    • maintenance_work_mem
    • effective_cache_size
    +
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_pg_start.html b/docs/rds/umn/rds_pg_start.html new file mode 100644 index 000000000..07157fd30 --- /dev/null +++ b/docs/rds/umn/rds_pg_start.html @@ -0,0 +1,16 @@ + + +

Starting an Instance

+

Scenarios

You can stop your instance temporarily to save money. After stopping your instance, you can restart it to begin using it again.

+
+

Constraints

  • If you start a primary instance, read replicas (if there are any) will also be started.
  • Only instances in Stopped state can be started. After this function is enabled, billing for instance usage duration will start.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the primary instance that you want to start and choose More > Start in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the instance list and view the status of the instance. If the status is Available, the instance is started successfully.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_pg_stop.html b/docs/rds/umn/rds_pg_stop.html new file mode 100644 index 000000000..8832f1325 --- /dev/null +++ b/docs/rds/umn/rds_pg_stop.html @@ -0,0 +1,16 @@ + + +

Stopping an Instance

+

Scenarios

If you use DB instances only for routine development, you can temporarily stop pay-per-use instances to save money. You can stop an instance for up to seven days.

+
+

Constraints

  • If you stop a primary instance, read replicas (if there are any) will also be stopped. They are stopped for up to seven days. You cannot stop a read replica without stopping the primary instance.
  • A stopped instance will not be moved to the recycle bin after being deleted.
  • If you do not manually start your stopped DB instance after seven days, your DB instance is automatically started during the next maintenance window. For details about the maintenance window, see Changing the Maintenance Window. To start a DB instance, see Starting an Instance.
  • After a DB instance is stopped, billing for instance usage duration will stop.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the primary instance that you want to stop and choose More > Stop in the Operation column.
  5. In the displayed dialog box, click Yes.
  6. Refresh the instance list and view the status of the instance. If the status is Stopped, the instance is stopped successfully.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_pg_switch_ha.html b/docs/rds/umn/rds_pg_switch_ha.html new file mode 100644 index 000000000..9c6cb567b --- /dev/null +++ b/docs/rds/umn/rds_pg_switch_ha.html @@ -0,0 +1,21 @@ + + +

Manually Switching Between Primary and Standby DB Instances

+

Scenarios

If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the primary DB instance only. The standby instance serves as a backup. You can manually promote the standby DB instance to the new primary instance for failover support.

+
+

Constraints

  • A DB instance is running properly.
  • The replication between the primary and standby instances is normal.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary/standby DB instance.
  5. In the DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

    Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

    +

    A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

    +
    +

  6. In the Switch Primary/Standby Instances dialog box, click Yes to switch between the primary and standby DB instances.

    If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

    +

  7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

    • During the switchover process, the DB instance status is Switchover in progress.
    • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is successful, the DB instance status will become Available.
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_pg_tag.html b/docs/rds/umn/rds_pg_tag.html new file mode 100644 index 000000000..df5730359 --- /dev/null +++ b/docs/rds/umn/rds_pg_tag.html @@ -0,0 +1,21 @@ + + +

Managing Tags

+

Scenarios

Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally. Other cloud services manage only their own tags.

+
  • You are advised to set predefined tags on the TMS console.
  • A tag consists of a key and value. You can add only one value for each key.
  • Up to 20 tags can be added for each DB instance.
+
+

Adding a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

    • The tag key must be unique. It can consist of up to 36 characters. Only letters, digits, hyphens (-), underscores (_), and at signs (@) are allowed.
    • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
    +

  6. After a tag has been added, you can view and manage it on the Tags page.
+
+

Editing a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

    • Only the tag value can be edited.
    • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
    +

  6. After a tag has been edited, you can view and manage it on the Tags page.
+
+

Deleting a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
  6. After a tag has been deleted, it will no longer be displayed on the Tags page.
+
+
+
+
+
Parent topic: Working with RDS for PostgreSQL
+
+
+ diff --git a/docs/rds/umn/rds_public_accessibility.html b/docs/rds/umn/rds_public_accessibility.html new file mode 100644 index 000000000..d8f0c69d2 --- /dev/null +++ b/docs/rds/umn/rds_public_accessibility.html @@ -0,0 +1,24 @@ + + +

Binding and Unbinding an EIP

+

Scenarios

By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you can unbind the EIP from the DB instance later if needed.

+

To ensure that the DB instance is accessible, the security group associated with the instance must allow access over the database port. For example, if the database port is 8635, ensure that the security group allows access over the 8635 port.

+
+
+

Prerequisites

  • You have assigned an EIP on the VPC console.
  • You can bind an EIP to a primary DB instance or a read replica only.
  • 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.
+
+

Binding an EIP

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose EIPs. On the displayed page, click Bind EIP.
  6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP to obtain one.
  7. On the EIPs page, view the EIP that has been bound to the DB instance.

    You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

    +

    To unbind the EIP from the DB instance, see Unbinding an EIP.

    +

+
+

Unbinding an EIP

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the DB instance that has an EIP bound.
  5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
  6. On the EIPs page, view the unbinding result.

    You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

    +

    To bind an EIP to the DB instance again, see Binding an EIP.

    +

+
+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_recent_log.html b/docs/rds/umn/rds_recent_log.html new file mode 100644 index 000000000..1926a3418 --- /dev/null +++ b/docs/rds/umn/rds_recent_log.html @@ -0,0 +1,18 @@ + + +

Viewing Error Logs

+

Scenarios

Error logs contain logs generated during the database running. These can help you analyze problems with the database.

+
+

Viewing Log Details

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the Error Logs page, view details about error logs.

    • You can select a log level in the upper right corner of the log list.

      For PostgreSQL DB instances, the following levels of logs are displayed:

      +
      • ERROR
      • FATAL
      • PANIC
      +
      +
    • You can click in the upper right corner to view error logs generated in different time segments.
    • If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_reset_password.html b/docs/rds/umn/rds_reset_password.html new file mode 100644 index 000000000..67e275793 --- /dev/null +++ b/docs/rds/umn/rds_reset_password.html @@ -0,0 +1,29 @@ + + +

Resetting the Administrator Password

+

Scenarios

You can reset the administrator password of a primary instance.

+

You can also reset the password of your database account when using RDS.

+
+

Precautions

  • If you have changed the administrator password of the primary DB instance, the administrator passwords of the standby DB instance and read replicas (if any) will also be changed accordingly.
  • The time required for the new password to take effect depends on the amount of service data currently being processed by the primary DB instance.
  • To protect against brute force hacking attempts and ensure system security, change your password periodically.
+
+

Method 1

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Reset Password in the Operation column.
  5. Enter and confirm a new 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 types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@$#%^*-_=+?). Enter a strong password and periodically change it for security reasons.

    +
    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
    • To submit the new password, click OK.
    • To cancel the reset operation, click Cancel.
    +
    +

+
+

Method 2

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field.
  6. Enter and confirm a new 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 types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@$#%^*-_=+?). Enter a strong password and periodically change it for security reasons.

    +
    If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
    • To submit the new password, click OK.
    • To cancel the reset operation, click Cancel.
    +
    +

+
+
+
+
+
Parent topic: Data Security
+
+
+ diff --git a/docs/rds/umn/rds_sql_auditing_log.html b/docs/rds/umn/rds_sql_auditing_log.html new file mode 100644 index 000000000..4ec2bc209 --- /dev/null +++ b/docs/rds/umn/rds_sql_auditing_log.html @@ -0,0 +1,26 @@ + + +

Enabling the SQL Audit Function

+

After you enable the SQL audit function, all SQL operations will be recorded in log files. You can download audit logs to view log details.

+

By default, SQL audit is disabled because enabling this function may affect database performance. This section describes how to enable, modify, or disable SQL audit.

+
  • After you enable the SQL audit function, the system records all SQL operations and uploads logs every half an hour or when the size is accumulated to 100 MB.
  • After SQL audit is enabled, log files will occupy your backup space.
+
+

Constraints

Only the versions listed below support SQL audit. .
  • MySQL 5.6.43 and later versions for DB instances using cloud disks, MySQL 5.6.47.3 and later versions for DB instances using local disks
  • MySQL 5.7.23 and later versions for DB instances using cloud disks, MySQL 5.7.29.3 and later versions for DB instances using local disks
  • MySQL 8.0
+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose SQL Audits. On the displayed page, click Set SQL Audit above the list. In the displayed dialog box, configure information as required and click OK.

    Enabling or setting SQL audit
    • To retain SQL audit logs, set (disabled) to (enabled).
    • Audit logs are retained for 7 days by default but can be retained from anywhere from 1 to 732 days if needed.
    +
    +

    Disabling SQL audit

    +

    To disable SQL audit, toggle (enabled) to (disabled).

    +
    • If you select the check box "I acknowledge that after audit log is disabled, all audit logs are deleted.", all audit logs will be deleted.

      Deleted audit logs cannot be recovered. Exercise caution when performing this operation.

      +
      +
    • If you do not select the check box "I acknowledge that after audit log is disabled, all audit logs are deleted.", the audit logs will be retained.
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_0025.html b/docs/rds/umn/rds_sqlserver_0025.html new file mode 100644 index 000000000..9c9e8c93f --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_0025.html @@ -0,0 +1,24 @@ + + +

Binding and Unbinding an EIP

+

Scenarios

By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you can unbind the EIP from the DB instance later if needed.

+

To ensure that the DB instance is accessible, the security group associated with the instance must allow access over the database port. For example, if the database port is 8635, ensure that the security group allows access over the 8635 port.

+
+
+

Prerequisites

  • You have assigned an EIP on the VPC console.
  • You can bind an EIP to a primary DB instance or a read replica only.
  • 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.
+
+

Binding an EIP

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the EIPs page, click Bind EIP.
  6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP and obtain an EIP.
  7. On the EIPs page of the RDS console, view the EIP that has been bound to the DB instance.

    You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

    +

    To unbind the EIP from the DB instance, see Unbinding an EIP.

    +

+
+

Unbinding an EIP

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the DB instance that has an EIP bound.
  5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
  6. On the EIPs page, view the unbinding result.

    You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

    +

    To bind an EIP to the DB instance again, see Binding an EIP.

    +

+
+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_01_0000.html b/docs/rds/umn/rds_sqlserver_01_0000.html new file mode 100644 index 000000000..aa995866a --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_01_0000.html @@ -0,0 +1,17 @@ + + +

Interconnection with CTS

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_01_0001.html b/docs/rds/umn/rds_sqlserver_01_0001.html new file mode 100644 index 000000000..9835b51bc --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_01_0001.html @@ -0,0 +1,31 @@ + + +

Distributed Transactions

+

Scenarios

The participator, transaction-supported server, resource server, and transaction manager of a distributed transaction are deployed on different nodes in a distributed system. Operations contained in a transaction are considered as a logical unit, and they either succeed completely, or fail completely. Distributed transactions are used to ensure data consistency among different databases.

+

The Microsoft Distributed Transaction Coordinator (MSDTC) service is a component of modern versions of Microsoft Windows that is responsible for coordinating transactions that span multiple resource managers. To use distributed transactions on databases, you must enable MSDTC on each participating server. MSDTC has been enabled when you enable distributed transactions on RDS for SQL Server databases. To enable MSDTC on remote servers, see Configuring MSDTC on a Remote Server.

+

For more information, see MS DTC Distributed Transactions.

+
+

Constraints

  • Distributed transactions are enabled for newly created DB instances by default.
  • Read replicas do not support distributed transactions.
  • Once enabled, distributed transactions cannot be disabled.
  • Enabling distributed transactions will cause DB instance to reboot. Exercise caution when you perform this operation.
  • After a database link is created for a Microsoft SQL Server DB instance, if a primary/standby switchover or failover occurs, the database link will not be automatically synchronized to the new primary DB instance. You need to create a database link on the new primary DB instance again.
+
+

Enabling Distributed Transactions

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Distributed Transactions. On the displayed page, click in the Distributed Transaction field.
  6. In the displayed dialog box, click Yes to enable the distributed transaction function. The DB instance will be rebooted during this process.
+
+

Adding Hosts

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Distributed Transactions. On the displayed page, click Add Host.
  6. In the displayed dialog box, enter host names and IP addresses, and click Test Connection. After all host connection tests are successful, click OK.

    • Host IP name: Enter the names of the hosts for which you want to create distributed transactions with the RDS DB instance. Each host name must be unique and contains 1 to 64 characters, including only letters, digits, and hyphens (-).
    • Host IP address: Enter the IP addresses of the hosts for which you want to create distributed transactions with the RDS DB instance. You need to configure the inbound and outbound rules in the security group for the host IP addresses first.
      • If the hosts to be added are ECSs that are in the same VPC as your RDS DB instance, enter the private IP address of the ECS. You can obtain the ECS's private IP address on the ECS details page.
      • If the hosts to be added are ECSs that are in different VPCs from the RDS DB instance, enter the public IP addresses of the ECSs. You need to bind an EIP to the RDS DB instance by referring to Binding and Unbinding an EIP.
      +
      +
    +

+
+

Resolving Names on Remote Servers (ECSs)

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Distributed Transactions. On the displayed page, obtain information about the RDS DB instance.
  5. Add the RDS DB instance information to the hosts file in C:\Windows\System32\drivers\etc\hosts.
+
+

Configuring MSDTC on a Remote Server

  1. Click Start and choose Control Panel > Administrative Tools > Component Services.
  2. Expand the nodes in the Console pane Choose Computers > My Computer > Distributed Transaction Coordinator.
  3. Right-click Local DTC and choose Properties.
  4. In the displayed dialog box, click the Security tab. Configure information as required as shown in Figure 1 and click OK.

    Figure 1 Local DTC properties
    +

+
+

Deleting Hosts

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Distributed Transactions. In the host list, locate the host to be deleted and click Delete in the Operation column.

    Alternatively, select one or more hosts to be deleted and click Delete above the list to delete hosts in batches.

    +

  6. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Working with RDS for SQL Server
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_01_0002.html b/docs/rds/umn/rds_sqlserver_01_0002.html new file mode 100644 index 000000000..16cd7c606 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_01_0002.html @@ -0,0 +1,17 @@ + + +

Viewing System Logs

+

Scenarios

System logs contain logs generated during the database running. These can help you analyze problems with the database.

+
+

Viewing Log Details

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the System Logs page, view details about system logs.

    • You can select a log level in the upper right corner to view logs of the selected level.

      For Microsoft SQL Server DB instances, only info-level logs are displayed currently.

      +
      +
    • You can click in the upper right corner to view logs generated in different time segments.
    • If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_05_0000.html b/docs/rds/umn/rds_sqlserver_05_0000.html new file mode 100644 index 000000000..ed5249c75 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0000.html @@ -0,0 +1,25 @@ + + +

Instance Lifecycle

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_05_0001_02.html b/docs/rds/umn/rds_sqlserver_05_0001_02.html new file mode 100644 index 000000000..805fe3532 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0001_02.html @@ -0,0 +1,16 @@ + + +

Data Migration

+

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_05_0005.html b/docs/rds/umn/rds_sqlserver_05_0005.html new file mode 100644 index 000000000..cb0f2dff8 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0005.html @@ -0,0 +1,19 @@ + + +

Connection Management

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_05_0006.html b/docs/rds/umn/rds_sqlserver_05_0006.html new file mode 100644 index 000000000..ba60ae9a6 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0006.html @@ -0,0 +1,19 @@ + + +

Data Security

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_05_0007.html b/docs/rds/umn/rds_sqlserver_05_0007.html new file mode 100644 index 000000000..b9dedb6bb --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0007.html @@ -0,0 +1,17 @@ + + +

Task Center

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_05_0008.html b/docs/rds/umn/rds_sqlserver_05_0008.html new file mode 100644 index 000000000..b1eb5104e --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0008.html @@ -0,0 +1,29 @@ + + + +

Instance Modifications

+ +

+
+ + + diff --git a/docs/rds/umn/rds_sqlserver_05_0017.html b/docs/rds/umn/rds_sqlserver_05_0017.html new file mode 100644 index 000000000..db4acb41b --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0017.html @@ -0,0 +1,16 @@ + + +

Exporting DB Instance Information

+

Scenarios

You can export information about all or selected DB instances to view and analyze DB instance information.

+
+

Exporting Information About All DB Instances

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
  5. Find a .csv file locally after the export task is completed.
+
+

Exporting Information About Selected DB Instances

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
  5. Find a .csv file locally after the export task is completed.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_05_0018.html b/docs/rds/umn/rds_sqlserver_05_0018.html new file mode 100644 index 000000000..2666f75b0 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0018.html @@ -0,0 +1,17 @@ + + +

Applying a Parameter Template

+

Scenarios

You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

    • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
    • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.
    +

    A parameter template can be applied to one or more DB instances.

    +

  5. In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.

    After the parameter template is successfully applied, you can view the application records by referring to section Viewing Application Records of a Parameter Template.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_05_0023.html b/docs/rds/umn/rds_sqlserver_05_0023.html new file mode 100644 index 000000000..5aa6a4915 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0023.html @@ -0,0 +1,16 @@ + + +

Changing a DB Instance Type from Single to Primary/Standby

+

Scenarios

  • RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.
  • Primary/standby DB instances support automatic failover. If the primary DB instance fails, the standby DB instance takes over services quickly. You are advised to deploy primary and standby DB instances in different AZs for high availability and disaster recovery.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate a single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

    Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

    +

  5. Select a standby AZ and enter the original administrator password. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
  6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

    • The DB instance is in the Changing type to primary/standby status. You can view the progress on the Task Center page. For details, see Task Center.
    • In the upper right corner of the DB instance list, click to refresh the list. After the DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_05_0024.html b/docs/rds/umn/rds_sqlserver_05_0024.html new file mode 100644 index 000000000..78a9245d3 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0024.html @@ -0,0 +1,20 @@ + + +

Configuring and Changing a Floating IP Address

+

Scenarios

You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.

+
+

Constraints

After a floating IP address is changed, the domain name needs to be resolved again. This operation takes several minutes and may interrupt database connections. Therefore, you are advised to change a floating IP address during off-peak hours.

+
+

Configuring a Floating IP Address

You can use a self-configured floating IP address when creating a DB instance.

+
+

Changing a Floating IP Address

You can change the floating IP address of an existing DB instance.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
  6. In the displayed dialog box, enter a new floating IP address. Click OK.

    In the in-use IP address list, the IP addresses whose statuses are To be used are occupied and cannot be used.

    +

+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_05_0034.html b/docs/rds/umn/rds_sqlserver_05_0034.html new file mode 100644 index 000000000..bf7807b99 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0034.html @@ -0,0 +1,31 @@ + + +

Backups and Restorations

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_05_0055.html b/docs/rds/umn/rds_sqlserver_05_0055.html new file mode 100644 index 000000000..f3c24d8f8 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0055.html @@ -0,0 +1,19 @@ + + +

Creating a Same DB Instance as an Existing DB Instance

+

Scenarios

This section describes how to quickly create a DB instance with the same configurations as the selected one.

+
  • You can create DB instances with the same configurations numerous times.
  • This function is unavailable for read replicas.
+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Create Same DB Instance in the Operation column.
  5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Next.

    For details about Microsoft SQL Server DB instance configurations, see section Step 1: Create a DB Instance.

    +

  6. Confirm the instance specifications.

    +

  7. Refresh the DB instance list and view the status of the DB instance. If the status is Available, it has been created successfully.

    You can manage the DB instance on the Instances page.

    +

+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_05_0098.html b/docs/rds/umn/rds_sqlserver_05_0098.html new file mode 100644 index 000000000..8d0e30851 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0098.html @@ -0,0 +1,15 @@ + + +

Viewing Application Records of a Parameter Template

+

Scenarios

You can view the application records of a parameter template.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left.
  5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

    You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_05_0099.html b/docs/rds/umn/rds_sqlserver_05_0099.html new file mode 100644 index 000000000..67b63e8a1 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_05_0099.html @@ -0,0 +1,21 @@ + + +

Viewing Parameter Change History

+

Scenarios

You can view the change history of DB instance parameters or custom parameter templates.

+

An exported or custom parameter template has initially a blank change history.

+
+
+

Viewing Change History of a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

    You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

    +

    You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.

    +

+
+

Viewing Change History of a Parameter Template

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  5. On the displayed page, choose Change History in the navigation pane on the left.

    You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_06_0000.html b/docs/rds/umn/rds_sqlserver_06_0000.html new file mode 100644 index 000000000..48c1f3c48 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_06_0000.html @@ -0,0 +1,19 @@ + + +

Metrics and Alarms

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_06_0001.html b/docs/rds/umn/rds_sqlserver_06_0001.html new file mode 100644 index 000000000..a66e8a196 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_06_0001.html @@ -0,0 +1,407 @@ + + +

Configuring Displayed Metrics

+

The RDS Agent monitors RDS DB instances and collects monitoring metrics only.

+

Description

This section describes the metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the monitoring metrics and alarms generated for RDS.

+
+

Namespace

SYS.RDS

+
+

DB Instance Monitoring Metrics

  • Table 1 lists details about ECS metrics. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 ECS performance metrics

    Metric ID

    +

    Name

    +

    Description

    +

    Value Range

    +

    Monitored Object

    +

    Monitoring Interval (Raw Data)

    +

    rds001_cpu_util

    +

    CPU Usage

    +

    CPU usage of the monitored object

    +

    0%–100%

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds003_iops

    +

    IOPS

    +

    Average number of I/O requests processed by the system in a specified period

    +

    ≥ 0 counts/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds039_disk_util

    +

    Storage Space Usage

    +

    Storage space usage of the monitored object

    +

    0%–100%

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds002_mem_util

    +

    Memory Usage

    +

    Memory usage of the monitored object

    +

    0%–100%

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds004_bytes_in

    +

    Network Input Throughput

    +

    Incoming traffic in bytes per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds005_bytes_out

    +

    Network Output Throughput

    +

    Outgoing traffic in bytes per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds049_disk_read_throughput

    +

    Disk Read Throughput

    +

    Number of bytes read from the disk per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds050_disk_write_throughput

    +

    Disk Write Throughput

    +

    Number of bytes written into the disk per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds047_disk_total_size

    +

    Total Storage Space

    +

    Total storage space of the monitored object

    +

    40–4,000 GB

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds048_disk_used_size

    +

    Used Storage Space

    +

    Used storage space of the monitored object

    +

    0–4,000 GB

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds053_avg_disk_queue_length

    +

    Average Disk Queue Length

    +

    Number of processes to be written into the monitored object

    +

    ≥ 0

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds054_db_connections_in_use

    +

    Database Connections in Use

    +

    Number of database connections in use

    +

    ≥0 counts

    +

    Monitored object: database

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +
    +
    +
  • Table 2 lists the performance metrics of Microsoft SQL Server databases. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Database performance metrics

    Metric ID

    +

    Name

    +

    Description

    +

    Value Range

    +

    Monitored Object

    +

    Monitoring Interval (Raw Data)

    +

    rds001_cpu_util

    +

    CPU Usage

    +

    CPU usage of the monitored object

    +

    0-100%

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds002_mem_util

    +

    Memory Usage

    +

    Memory usage of the monitored object

    +

    0–1

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds003_iops

    +

    IOPS

    +

    Average number of I/O requests processed by the system in a specified period

    +

    ≥ 0 counts/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds004_bytes_in

    +

    Network Input Throughput

    +

    Incoming traffic in bytes per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds005_bytes_out

    +

    Network Output Throughput

    +

    Outgoing traffic in bytes per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds039_disk_util

    +

    Storage Space Usage

    +

    Storage space usage of the monitored object

    +

    0–1

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds047_disk_total_size

    +

    Total Storage Space

    +

    Total storage space of the monitored object

    +

    40–4,000 GB

    +

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds048_disk_used_size

    +

    Used Storage Space

    +

    Used storage space of the monitored object

    +

    0–4,000 GB

    +

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds049_disk_read_throughput

    +

    Disk Read Throughput

    +

    Number of bytes read from the disk per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds050_disk_write_throughput

    +

    Disk Write Throughput

    +

    Number of bytes written into the disk per second

    +

    ≥ 0 bytes/s

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds053_avg_disk_queue_length

    +

    Average Disk Queue Length

    +

    Number of processes to be written into the monitored object

    +

    ≥ 0

    +

    Monitored object: ECS

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +

    rds054_db_connections_in_use

    +

    Database Connections in Use

    +

    Number of database connections in use

    +

    ≥ 0 counts

    +

    Monitored object: database

    +

    Monitored instance type: Microsoft SQL Server instance

    +

    1 minute

    +
    +
    +
+
+

Dimension

+
+ + + + + + + +

Key

+

Value

+

rds_instance_sqlserver_id

+

Microsoft SQL Server DB instance node ID

+
+
+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_06_0002.html b/docs/rds/umn/rds_sqlserver_06_0002.html new file mode 100644 index 000000000..3093c1a6a --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_06_0002.html @@ -0,0 +1,16 @@ + + +

Setting Alarm Rules

+

Scenarios

You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.

+

The RDS alarm rules include alarm rule names, services, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

+
+

Setting Alarm Rules

  1. Log in to the management console.
  2. Click Service List and choose Management & Governance > Cloud Eye.
  3. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
  4. On the displayed Alarm Rules page, click Create Alarm Rule.

    For details about how to create alarm rules, see Using Alarm Templates to Create an Alarm Rule in the Cloud Eye User Guide.

    +

+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_06_0003.html b/docs/rds/umn/rds_sqlserver_06_0003.html new file mode 100644 index 000000000..4c5ceb5ae --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_06_0003.html @@ -0,0 +1,24 @@ + + +

Viewing Monitoring Metrics

+

Scenarios

Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.

+

Monitored data takes some time before it can be displayed. The RDS status displayed on the Cloud Eye console is about 5 to 10 minutes delayed. When you create a new RDS DB instance, it takes 5 to 10 minutes before monitoring data is displayed on Cloud Eye.

+
+

Prerequisites

  • RDS is running properly.

    Monitoring metrics of the RDS DB instances that are faulty or have been deleted are not displayed on the Cloud Eye console. You can view their monitoring metrics after they are rebooted or restored to normal.

    +
+

If an RDS DB instance has been faulty for 24 hours, Cloud Eye considers it to no longer exist and deletes it from the monitoring object list. You need to manually clear the alarm rules created for the DB instance.

+
+
  • RDS has been running properly for about 10 minutes.

    For a newly created RDS DB instance, you need to wait a bit before you can view the metrics.

    +
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

    Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

    +

  5. On the Cloud Eye console, view monitoring metrics of the primary DB instance.

    Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 30 days, and 7 days.

    +

+
+
+
+
+
Parent topic: Metrics and Alarms
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_06_0004.html b/docs/rds/umn/rds_sqlserver_06_0004.html new file mode 100644 index 000000000..40de2ec5d --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_06_0004.html @@ -0,0 +1,268 @@ + + +

Key Operations Supported by CTS

+

Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 RDS operations that can be recorded by CTS

Operation

+

Resource Type

+

Trace Name

+

Creating a DB instance or a read replica, or restoring data to a new DB instance (using the console, Trove APIs, or open APIs)

+

instance

+

createInstance

+

Scaling up storage space and changing instance class (using the console, Trove APIs, or open APIs)

+

instance

+

instanceAction

+

Rebooting a DB instance (using the console, Trove APIs, or open APIs)

+

instance

+

instanceRestart

+

Restoring to the original DB instance (using the console, Trove APIs, or open APIs)

+

instance

+

instanceRestore

+

Renaming a DB instance (using the console)

+

instance

+

instanceRename

+

Resetting the password (using the console)

+

instance

+

resetPassword

+

Setting the database version parameters (using open APIs)

+

instance

+

setDBParameters

+

Resetting the database version parameters (using open APIs)

+

instance

+

resetDBParameters

+

Enabling, modifying, or disabling the backup policy (using the console or open APIs)

+

instance

+

setBackupPolicy

+

Changing a database port (using the console)

+

instance

+

changeInstancePort

+

Binding and unbinding an EIP (using the console)

+

instance

+

setOrResetPublicIP

+

Modifying a security group (using the console)

+

instance

+

modifySecurityGroup

+

Adding a tag (using the console or open APIs)

+

instance

+

createTag

+

Deleting a tag (using the console or open APIs)

+

instance

+

deleteTag

+

Modifying a tag (using the console or open APIs)

+

instance

+

modifyTag

+

Deleting a DB instance (using the console, Trove APIs, or open APIs)

+

instance

+

deleteInstance

+

Enabling TDE for a Microsoft SQL Server DB instance (using the console)

+

instance

+

sqlserverOpenTDE

+

Performing a primary/standby switchover (using the console)

+

instance

+

instanceFailOver

+

Changing the synchronize model (using the console)

+

instance

+

instanceFailOverMode

+

Changing the failover priority (using the console)

+

instance

+

instanceFailOverStrategy

+

Changing a DB instance type from single to primary/standby (using the console, Trove APIs, or open APIs)

+

instance

+

modifySingleToHaInstance

+

Creating a backup (using the console or open APIs)

+

backup

+

createManualSnapshot

+

Replicating a backup (using the console)

+

backup

+

copySnapshot

+

Download a backup (using the console or open APIs)

+

backup

+

downLoadSnapshot

+

Deleting a backup (using the console or open APIs)

+

backup

+

deleteManualSnapshot

+

Creating a parameter template (using the console or Trove APIs)

+

parameterGroup

+

createParameterGroup

+

Modifying parameters in a parameter template (using the console or Trove APIs)

+

parameterGroup

+

updateParameterGroup

+

Deleting a parameter template (using the console or Trove APIs)

+

parameterGroup

+

deleteParameterGroup

+

Replicating a parameter template (using the console)

+

parameterGroup

+

copyParameterGroup

+

Resetting a parameter template (using the console)

+

parameterGroup

+

resetParameterGroup

+

Comparing parameter templates (using the console)

+

parameterGroup

+

compareParameterGroup

+

Applying a parameter template (using the console)

+

parameterGroup

+

applyParameterGroup

+

Saving parameters in a parameter template (using the console)

+

parameterGroup

+

saveParameterGroup

+

Deleting a frozen DB instance (using the console)

+

all

+

rdsUnsubscribeInstance

+

Freezing a DB instance (using the console)

+

all

+

rdsunfreezeInstance

+
+
+
+
+
+
Parent topic: Interconnection with CTS
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_06_0005.html b/docs/rds/umn/rds_sqlserver_06_0005.html new file mode 100644 index 000000000..1e4c01897 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_06_0005.html @@ -0,0 +1,18 @@ + + +

Viewing Tracing Events

+

Scenarios

After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.

+

This section describes how to query the operation records of last 7 days on the CTS console.

+
+

Procedure

  1. Log in to the management console.
  2. Choose Management & Governance > Cloud Trace Service.
  3. Choose Trace List in the navigation pane on the left.
  4. Filter conditions to query traces. The details are described as follows:

    • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

      When you select Resource ID for Search By, you also need to select or enter a resource ID.

      +
    • Operator: Select a specific operator from the drop-down list.
    • Trace Status: Available options include All trace statuses, Normal, Warning, and Incident. You can only select one of them.
    • In the upper right corner of the page, you can specify a time range for querying traces.
    +

  5. Select the search criteria, and click Query.
  6. Click on the left of the required trace to expand its details.
  7. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
  8. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

    For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

    +

+
+
+
+
+
Parent topic: Interconnection with CTS
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_06_0022.html b/docs/rds/umn/rds_sqlserver_06_0022.html new file mode 100644 index 000000000..ea5df0bef --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_06_0022.html @@ -0,0 +1,16 @@ + + +

Selecting Displayed Items

+

Scenarios

You can customize which instance items are displayed on the Instances page.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click to edit columns displayed in the DB instance list.

    • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

      These default items cannot be deselected.

      +
    • In a single project, you can select up to 9 items: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, creation time, database port, storage type, and operation.
    +

+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_08_0042.html b/docs/rds/umn/rds_sqlserver_08_0042.html new file mode 100644 index 000000000..0d9d0a620 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_08_0042.html @@ -0,0 +1,22 @@ + + +

Exporting a Parameter Template

+

Scenarios

  • You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Parameter Template.
  • You can export the parameter template information (parameter names, values, and descriptions) of a DB instance to a CSV file for viewing and analysis.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

    • Exporting to a custom template
      In the displayed dialog box, configure required information and click OK.
      • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
      • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
      +
      +
      +

      After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

      +
    • Exporting to a file
      The parameter template information (parameter names, values, and descriptions) of a DB instance is exported to a CSV file. In the displayed dialog box, enter the file name and click OK.

      The file name must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

      +
      +
      +
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_11_0001.html b/docs/rds/umn/rds_sqlserver_11_0001.html new file mode 100644 index 000000000..1586d0fb6 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_11_0001.html @@ -0,0 +1,19 @@ + + +

Read Replicas

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_11_0002.html b/docs/rds/umn/rds_sqlserver_11_0002.html new file mode 100644 index 000000000..8ab845c21 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_11_0002.html @@ -0,0 +1,22 @@ + + +

Introducing Read Replicas

+

Introduction

Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.

+

In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To expand the DB instance read ability to offload read pressure on the database, you can create one or more read replicas in a region. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses of the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.

+

A read replica uses a single-node architecture (without a slave node). Changes to the primary DB instance are also automatically synchronized to all associated read replicas through the native SQL Server replication function. The synchronization is not affected by network latency. Read replicas and the primary DB instance must be in the same region but can be in different AZs.

+
+

Functions

  • Specifications of read replicas can be different from those of the primary DB instance, and can be changed at any time.
  • You do not need to maintain separate database accounts or databases. They are synchronized from the primary DB instance.
  • Read replicas support system performance monitoring.

    RDS provides up to 20 monitoring metrics, including storage space, IOPS, the number of database connections, CPU usage, and network traffic. You can view these metrics to learn about the load on DB instances.

    +
  • Read replicas do not support automated backups or manual backups.
  • Read replicas do not support restoration from backups to new, existing, or original read replicas.
  • Data cannot be migrated to read replicas.
+
+

Constraints

+

A maximum of five read replicas can be created for each primary DB instance.

+
+

Creating and Managing a Read Replica

+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_11_0004.html b/docs/rds/umn/rds_sqlserver_11_0004.html new file mode 100644 index 000000000..dd8036985 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_11_0004.html @@ -0,0 +1,16 @@ + + +

Managing a Read Replica

+

Entering the Management Interface Through a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Basic Information page.
+
+

Entering the Management Interface Through a Primary DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
  5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
+
+

Deleting a Read Replica

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the DB instance list, click in front of a DB instance, locate the read replica to be deleted, and choose More > Delete in the Operation column.
+
+
+
+
+
Parent topic: Read Replicas
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_backup_restore.html b/docs/rds/umn/rds_sqlserver_backup_restore.html new file mode 100644 index 000000000..b4a1df50d --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_backup_restore.html @@ -0,0 +1,17 @@ + + +

Working with Backups

+

RDS supports DB instance backups and restorations to ensure data reliability.

+

Automated Backups

Automated backups are created during the backup period of your DB instances. RDS saves automated backups based on the retention period you specified. If necessary, you can restore to any point in time during your backup retention period. For details, see Configuring an Automated Backup Policy.

+
+

Manual Backups

Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually. For details, see Creating a Manual Backup.

+
+

Downloading a Backup File

You can download a full backup file for local data backup or restoration. For details, see Downloading a Backup File.

+
+
+
+
+
Parent topic: Backups and Restorations
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_change_database_port.html b/docs/rds/umn/rds_sqlserver_change_database_port.html new file mode 100644 index 000000000..1236eaa3f --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_change_database_port.html @@ -0,0 +1,21 @@ + + +

Changing a Database Port

+

Scenarios

This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the primary DB instance will cause the database port of the standby DB instance to also be changed accordingly.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance or click first and then click the target read replica.
  5. In the Connection Information area on the Basic Information page, click in the Database Port field.

    The DB instance port is 1433 by default or it can be set to a value from 2100 to 9500, excluding 5355 and 5985.

    +
    +
    • To submit the change, click .
      • In the dialog box, click Yes.
        1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
        2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will reboot.

          For RDS for SQL Server, only 2017 Enterprise Edition supports read replicas.

          +
          +
        3. This process takes 1-5 minutes.
        +
      • In the dialog box, click No to cancel the modification.
      +
    • To cancel the change, click .
    +

  6. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Connection Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_configuration.html b/docs/rds/umn/rds_sqlserver_configuration.html new file mode 100644 index 000000000..21074b9ab --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_configuration.html @@ -0,0 +1,35 @@ + + +

Modifying Parameters

+

You can modify parameters in a custom parameter template to optimize RDS database performance.

+

You can only change parameter values in custom parameter templates. You cannot change the parameter values in default parameter templates. When you change parameter values in a custom parameter template, the changes take effect for all DB instances that the parameter template applies to.

+

When you modify a parameter, the time when the modification takes effect depends on the type of the parameter.

+

The RDS console displays the statuses of DB instances that the parameter template applies to. For example, if the DB instance has not yet used the latest modifications made to its parameter template, its status is Parameter change. Pending reboot. Manually reboot the DB instance for the latest modifications to take effect for that DB instance.

+

RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly, the database startup may fail. If this happens, you can re-configure the custom parameter template based on the settings of the default parameter template.

+
+

Modifying Parameter Template Parameters

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  5. On the Parameters page, modify parameters as required.

    Relevant parameters are as follows:

    +
    • Set remote access to 0 (default value) to prevent locally stored procedures from running on a remote server and remotely stored procedures from running on a local server.
    • The max server memory (MB) parameter indicates the server memory. The default value equals to the OS memory (MB) minus 520 (MB). Its minimum value is 1024 MB.
    +

    Available operations are as follows:

    +
    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +

  6. After the parameter values are modified, you can click View Change History to view the modification details.
  7. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
  8. View the status of the DB instance to which the parameter template was applied.

    If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.

    +
    • A DB instance reboot caused by instance class changes will not make parameter modifications take effect.
    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
    +

+
+

Modifying Instance Parameters

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

    Relevant parameters are as follows:
    • Set remote access to 0 (default value) to prevent locally stored procedures from running on a remote server and remotely stored procedures from running on a local server.
    • The max server memory (MB) parameter indicates the server memory. The default value equals to the OS memory (MB) minus 520 (MB). Its minimum value is 1024 MB.
    +
    +

    Available operations are Save, Cancel, and Preview.

    +
    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    +
    In the Effective upon Reboot column:
    • If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required the modifications to take effect.
      • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
      • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
      +
    • If the value is No, the modifications take effect immediately.
    +
    +
    +

    After parameters are modified, you can view parameter change history by referring to section Viewing Parameter Change History.

    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_log.html b/docs/rds/umn/rds_sqlserver_log.html new file mode 100644 index 000000000..99e38ff79 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_log.html @@ -0,0 +1,17 @@ + + +

Log Management

+
+ + diff --git a/docs/rds/umn/rds_sqlserver_modify_availability.html b/docs/rds/umn/rds_sqlserver_modify_availability.html new file mode 100644 index 000000000..e3640c089 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_modify_availability.html @@ -0,0 +1,15 @@ + + +

Changing the Failover Priority

+

Scenarios

You can configure the failover priority for reliability or for availability, depending on your service requirements.

+
  • Reliability: This option is selected by default. Data consistency is preferentially ensured during a primary/standby failover. This is recommended for users whose highest priority is data consistency.
  • Availability: Database availability is preferentially ensured during a primary/standby failover. This is recommended for users who require their databases to provide uninterrupted online services.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary/standby DB instances.
  5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
  6. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_modify_instance_name.html b/docs/rds/umn/rds_sqlserver_modify_instance_name.html new file mode 100644 index 000000000..f6b3d7e33 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_modify_instance_name.html @@ -0,0 +1,17 @@ + + +

Changing a DB Instance Name

+

Scenarios

You can change the name of a primary DB instance or read replica.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

    Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name field in the DB Information area, click to edit the DB 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.

    +
    • To submit the change, click .
    • To cancel the change, click .
    +

  5. View the results on the Basic Information page.
+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_parameter_group.html b/docs/rds/umn/rds_sqlserver_parameter_group.html new file mode 100644 index 000000000..7e9367884 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_parameter_group.html @@ -0,0 +1,24 @@ + + +

Creating a Parameter Template

+

You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can be applied to one or more DB instances.

+

When you create a DB instance, RDS will automatically allocate a default database parameter template for you. This default template contains DB engine defaults and system defaults that are configured based on the engine, compute class, and allocated storage of the instance. Default parameter templates cannot be modified, but you can create your own parameter template to change parameter settings.

+

Not all of the DB engine parameters in a custom parameter template can be changed.

+
+

If you want to use a custom parameter template, you simply create a parameter template and select it when you create a DB instance or apply it to an existing DB instance following the instructions provided in section Applying a Parameter Template.

+

When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template following the instructions provided in section Replicating a Parameter Template.

+

The following are the key points you should know when using parameters in a parameter template:

+
  • When you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately. When you change a static parameter value in a parameter template and save the change, the change will take effect only after you manually reboot the DB instances that the parameter template applies to.
  • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
+

RDS does not share parameter template quotas with DDS.

+

You can create a maximum of 100 parameter templates for RDS DB instances. All RDS DB engines share the parameter template quota.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Parameter Template Management page, click Create Parameter Template.
  5. In the displayed dialog box, configure required information and click OK.

    • Select a DB engine for the parameter template.
    • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
    • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
    +

+
+
+
+
+
Parent topic: Parameter Template Management
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_recycle.html b/docs/rds/umn/rds_sqlserver_recycle.html new file mode 100644 index 000000000..d62b8ffd5 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_recycle.html @@ -0,0 +1,21 @@ + + +

Recycling a DB Instance

+

Scenarios

Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB instance are the same as those of the original DB instance. Other parameters can be reconfigured. DB instances that were deleted up to 7 days ago can be restored.

+
+

Constraints

  • Read replicas cannot be moved to the recycle bin.
  • The recycle bin is enabled by default and cannot be disabled.
+
+

Modifying Recycling Policy

A new recycling policy only applies to DB instances that were put in the recycle bin after the new policy was put into effect. For DB instances that were in the recycle bin before the modification, the original recycling policy takes effect.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Recycling Management.
  5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
  6. Then, click OK.
+
+

Rebuilding a DB Instance

You can rebuild the primary DB instances in the recycle bin within the retention period.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. In the navigation pane on the left, choose Recycling Management.
  5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
  6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
+
+
+
+
+
Parent topic: Instance Lifecycle
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_scale_cluster.html b/docs/rds/umn/rds_sqlserver_scale_cluster.html new file mode 100644 index 000000000..3b08129ec --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_scale_cluster.html @@ -0,0 +1,24 @@ + + +

Scaling up Storage Space

+

Scenarios

If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

+

The DB instance needs to preserve at least 15% of its capacity to work properly. The new minimum storage space required to make this instance available has been automatically calculated for you. You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

+

For details about the causes and solutions of insufficient storage space, see What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?

+

RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

+
+

Constraints

  • DB instances can be scaled up numerous times.
  • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
  • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
  • You cannot reboot or delete a DB instance that is being scaled up.
  • Storage space can only be scaled up.
  • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Scale Storage Space in the Operation column.

    You can also perform the following operations to scale up storage space:

    +
    • Click the target DB instance to enter the Basic Information page. In the Storage Space area, click Scale.
    +

  5. On the displayed page, specify the new storage space and click Next.

    The minimum start value of each scaling is 10 GB. A DB instance can be scaled up only by a multiple of 10 GB. The allowed maximum storage space is 4,000 GB.

    +

  6. Confirm specifications.

    • If you need to modify your settings, click Previous.
    • If you do not need to modify your settings, click Submit.
    +

  7. View the scale-up result.

    Scaling up storage space takes 3-5 minutes. During this time, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Basic Information page to verify that the scale-up is successful.

    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_scale_rds.html b/docs/rds/umn/rds_sqlserver_scale_rds.html new file mode 100644 index 000000000..fcecf1b34 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_scale_rds.html @@ -0,0 +1,21 @@ + + +

Changing a DB Instance Class

+

Scenarios

You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the change is successful.

+
+

Constraints

  • A DB instance cannot be deleted when its instance class is being changed.
+
  • After you change instance classes, the DB instances will be rebooted and service will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

    Alternatively, click the target DB instance to go to the Basic Information page. In the DB Information area, click Change in the Instance Class field.

    +

  5. On the displayed page, specify the new instance class and click Next.
  6. View the DB instance class change result.

    Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Basic Information page to check that the change is successful.

    +

    After you change a Microsoft SQL Server DB instance class, the value of max server memory will also be changed accordingly. You are advised to set it to a size equal to the memory size minus 520 MB. For example, if there is 1 GB of memory (1,024 MB), you are advised to set max server memory to 504 MB (1,024 MB – 520 MB).

    +
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_switch_ha.html b/docs/rds/umn/rds_sqlserver_switch_ha.html new file mode 100644 index 000000000..a6b990179 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_switch_ha.html @@ -0,0 +1,21 @@ + + +

Manually Switching Between Primary and Standby DB Instances

+

Scenarios

If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the primary DB instance only. The standby instance serves as a backup. You can manually promote the standby DB instance to the new primary instance for failover support.

+
+

Constraints

  • A DB instance is running properly.
  • The replication between the primary and standby instances is normal.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary/standby DB instance.
  5. In the DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

    Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

    +

    A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

    +
    +

  6. In the Switch Primary/Standby Instances dialog box, click Yes to switch between the primary and standby DB instances.

    If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

    +

  7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

    • During the switchover process, the DB instance status is Switchover in progress.
    • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is successful, the DB instance status will become Available.
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_tag.html b/docs/rds/umn/rds_sqlserver_tag.html new file mode 100644 index 000000000..bf57724bf --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_tag.html @@ -0,0 +1,21 @@ + + +

Managing Tags

+

Scenarios

Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally. Other cloud services manage only their own tags.

+
  • You are advised to set predefined tags on the TMS console.
  • A tag consists of a key and value. You can add only one value for each key.
  • Up to 20 tags can be added for each DB instance.
+
+

Adding a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

    • The tag key must be unique. It can consist of up to 36 characters. Only letters, digits, hyphens (-), underscores (_), and at signs (@) are allowed.
    • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
    +

  6. After a tag has been added, you can view and manage it on the Tags page.
+
+

Editing a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

    • Only the tag value can be edited.
    • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
    +

  6. After a tag has been edited, you can view and manage it on the Tags page.
+
+

Deleting a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
  6. After a tag has been deleted, it will no longer be displayed on the Tags page.
+
+
+
+
+
Parent topic: Working with RDS for SQL Server
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_task_0001.html b/docs/rds/umn/rds_sqlserver_task_0001.html new file mode 100644 index 000000000..e80738ade --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_task_0001.html @@ -0,0 +1,19 @@ + + +

Viewing a Task

+

You can view the progress and results of tasks on the Task Center page.

+

You can view and manage the following tasks:

+
  • Creating DB instances
  • Creating read replicas
  • Changing single DB instances to primary/standby
  • Scaling up storage space
  • Binding EIPs to DB instances
  • Unbinding EIPs from DB instances
  • Switching primary/standby DB instances
  • Rebooting DB instances
  • Restoring data to new DB instances
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. Locate the target task and view its details.

    • To identify the target task, you can use the task name and DB instance name/ID or enter the target task name in the search box in the upper right corner.
    • You can click in the upper right corner to view the progress and status of tasks in a specific period.

      The retention duration of failed tasks is 7 days, and of completed tasks is 1 days by default. It is controlled by two parameters on background. The retention duration cannot exceed 30 days. To set the retention duration contact O&M personnel.

      +
    • You can view instant tasks in the following statuses:
      • Running
      • Completed
      • Failed
      +
    • View the task creation and completion time.
    +

+
+
+
+
+
Parent topic: Task Center
+
+
+ diff --git a/docs/rds/umn/rds_sqlserver_task_0002.html b/docs/rds/umn/rds_sqlserver_task_0002.html new file mode 100644 index 000000000..cf0edf411 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_task_0002.html @@ -0,0 +1,22 @@ + + +

Deleting a Task Record

+

You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or terminate the tasks that are being executed.

+

Deleted task records cannot be recovered. Exercise caution when performing this operation.

+
+

Deleting an Instant Task Record

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. On the displayed Instant Tasks page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

    You can delete the records of instant tasks in any of the following statuses:

    +
    • Running
    • Completed
    • Failed
    +

+
+

Deleting a Scheduled Task Record

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, locate the target task record to be deleted and check whether the task status is To be executed or To be authorized.

    • If yes, go to 5.
    • If no, go to 6.
    +

  5. Click Cancel in the Operation column. In the displayed dialog box, click Yes to cancel the task. Then, click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.
  6. Click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.

    You can delete the records of scheduled tasks in any of the following statuses:

    +
    • Running
    • Completed
    • Failed
    • Canceled
    • To be executed
    • To be authorized
    +

+
+
+
+
+
Parent topic: Task Center
+
+
+ diff --git a/docs/rds/umn/rds_switch_ha.html b/docs/rds/umn/rds_switch_ha.html new file mode 100644 index 000000000..eba6d41b7 --- /dev/null +++ b/docs/rds/umn/rds_switch_ha.html @@ -0,0 +1,21 @@ + + +

Manually Switching Between Primary and Standby DB Instances

+

Scenarios

If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the primary DB instance only. The standby instance serves as a backup. You can manually promote the standby DB instance to the new primary instance for failover support.

+
+

Constraints

  • A DB instance is running properly.
  • The replication between the primary and standby instances is normal.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target primary/standby DB instance.
  5. In the DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

    Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

    +

    A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

    +
    +

  6. In the Switch Primary/Standby Instances dialog box, click Yes to switch between the primary and standby DB instances.

    If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

    +

  7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

    • During the switchover process, the DB instance status is Switchover in progress.
    • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is successful, the DB instance status will become Available.
    +

+
+
+
+
+
Parent topic: Instance Modifications
+
+
+ diff --git a/docs/rds/umn/rds_switch_log.html b/docs/rds/umn/rds_switch_log.html new file mode 100644 index 000000000..0f336214c --- /dev/null +++ b/docs/rds/umn/rds_switch_log.html @@ -0,0 +1,15 @@ + + +

Viewing Failover/Switchover Logs

+

You can view failover or switchover logs of MySQL DB instances to evaluate the impact on services.

+

Only failover and switchover logs within 30 days are displayed.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the displayed page, click Failover/Switchover Logs to view log details.
+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/rds_tag.html b/docs/rds/umn/rds_tag.html new file mode 100644 index 000000000..7659ad96a --- /dev/null +++ b/docs/rds/umn/rds_tag.html @@ -0,0 +1,21 @@ + + +

Managing Tags

+

Scenarios

Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally. Other cloud services manage only their own tags.

+
  • You are advised to set predefined tags on the TMS console.
  • A tag consists of a key and value. You can add only one value for each key.
  • Up to 20 tags can be added for each DB instance.
+
+

Adding a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

    • The tag key must be unique. It can consist of up to 36 characters. Only letters, digits, hyphens (-), underscores (_), and at signs (@) are allowed.
    • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
    +

  6. After a tag has been added, you can view and manage it on the Tags page.
+
+

Editing a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

    • Only the tag value can be edited.
    • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
    +

  6. After a tag has been edited, you can view and manage it on the Tags page.
+
+

Deleting a Tag

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
  6. After a tag has been deleted, it will no longer be displayed on the Tags page.
+
+
+
+
+
Parent topic: Working with RDS for MySQL
+
+
+ diff --git a/docs/rds/umn/rds_task_0001.html b/docs/rds/umn/rds_task_0001.html new file mode 100644 index 000000000..57b3f456e --- /dev/null +++ b/docs/rds/umn/rds_task_0001.html @@ -0,0 +1,25 @@ + + +

Viewing a Task

+

You can view the progress and results of scheduled and instant tasks on the Task Center page.

+

RDS allows you to view and manage the following instant tasks:

+
  • Creating DB instances
  • Creating read replicas
  • Scaling up storage space
  • Changing single DB instances to primary/standby
  • Switching primary/standby DB instances
  • Rebooting DB instances
  • Binding EIPs to DB instances
  • Unbinding EIPs from DB instances
  • Restoring data to new DB instances
  • Migrating a standby MySQL DB instance
  • Upgrading minor versions of MySQL DB instances
  • Restoring MySQL data to existing DB instances
+

RDS allows you to view and manage the following scheduled tasks:

+
  • Changing MySQL DB instance classes
  • Upgrading minor versions of MySQL DB instances
+
+

Viewing an Instant Task

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. Locate the target task and view its details on the displayed Instant Tasks page.

    • To identify the target task, you can use the task name, order ID, or DB instance name/ID, or simply enter the target task name in the search box in the upper right corner.
    • You can view the progress and status of tasks in a specific period.

      The retention duration of failed tasks is 7 days, and of completed tasks is 1 days by default. It is controlled by two parameters on background. The retention duration cannot exceed 30 days. To set the retention duration contact O&M personnel.

      +
    • You can view instant tasks in the following statuses:
      • Running
      • Completed
      • Failed
      +
    • You can view the task creation and completion time.
    +

+
+

Viewing a Scheduled Task

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, view the task progress and results.

    • To identify the target task, you can use the DB instance name/ID or enter the target DB instance ID in the search box in the upper right corner.
    • You can view the scheduled tasks in the following statuses:
      • Running
      • Completed
      • Failed
      • Canceled
      • To be executed
      • To be authorized
      +
    +

+
+
+
+
+
Parent topic: Task Center
+
+
+ diff --git a/docs/rds/umn/rds_task_0002.html b/docs/rds/umn/rds_task_0002.html new file mode 100644 index 000000000..ce2d5e9d4 --- /dev/null +++ b/docs/rds/umn/rds_task_0002.html @@ -0,0 +1,22 @@ + + +

Deleting a Task Record

+

You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or terminate the tasks that are being executed.

+

Deleted task records cannot be recovered. Exercise caution when performing this operation.

+
+

Deleting an Instant Task Record

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. On the displayed Instant Tasks page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

    You can delete the records of instant tasks in any of the following statuses:

    +
    • Running
    • Completed
    • Failed
    +

+
+

Deleting a Scheduled Task Record

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, locate the target task record to be deleted and check whether the task status is To be executed or To be authorized.

    • If yes, go to 5.
    • If no, go to 6.
    +

  5. Click Cancel in the Operation column. In the displayed dialog box, click Yes to cancel the task. Then, click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.
  6. Click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.

    You can delete the records of scheduled tasks in any of the following statuses:

    +
    • Running
    • Completed
    • Failed
    • Canceled
    • To be executed
    • To be authorized
    +

+
+
+
+
+
Parent topic: Task Center
+
+
+ diff --git a/docs/rds/umn/rds_task_pg_0001.html b/docs/rds/umn/rds_task_pg_0001.html new file mode 100644 index 000000000..e85fdae41 --- /dev/null +++ b/docs/rds/umn/rds_task_pg_0001.html @@ -0,0 +1,19 @@ + + +

Viewing a Task

+

You can view the detailed progress and result of the task on the Task Center page.

+

You can view and manage the following tasks:

+
  • Creating DB instances
  • Creating read replicas
  • Changing single DB instances to primary/standby
  • Scaling up storage space
  • Binding EIPs to DB instances
  • Unbinding EIPs from DB instances
  • Switching primary/standby DB instances
  • Rebooting DB instances
  • Restoring data to new DB instances
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Task Center page, locate the target task and view its details.

    • To identify the target task, you can use the task name and DB instance name/ID or enter the target task name in the search box in the upper right corner.
    • You can view the progress and status of tasks in a specific period.

      The retention duration of failed tasks is 7 days, and of completed tasks is 1 days by default. It is controlled by two parameters on background. The retention duration cannot exceed 30 days. To set the retention duration contact O&M personnel.

      +
    • You can view instant tasks in the following statuses:
      • Running
      • Completed
      • Failed
      +
    • View the task creation and completion time.
    +

+
+
+
+
+
Parent topic: Task Center
+
+
+ diff --git a/docs/rds/umn/rds_task_pg_0002.html b/docs/rds/umn/rds_task_pg_0002.html new file mode 100644 index 000000000..c739b4942 --- /dev/null +++ b/docs/rds/umn/rds_task_pg_0002.html @@ -0,0 +1,17 @@ + + +

Deleting a Task Record

+

You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or terminate the tasks that are being executed.

+

Deleted task records cannot be recovered. Exercise caution when performing this operation.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. Choose Task Center in the navigation pane on the left. On the displayed page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

    You can delete the records of instant tasks in any of the following statuses:

    +
    • Running
    • Completed
    • Failed
    +

+
+
+
+
+
Parent topic: Task Center
+
+
+ diff --git a/docs/rds/umn/slow_query_log-pg.html b/docs/rds/umn/slow_query_log-pg.html new file mode 100644 index 000000000..6cbf3846e --- /dev/null +++ b/docs/rds/umn/slow_query_log-pg.html @@ -0,0 +1,39 @@ + + +

Viewing Slow Query Logs

+

Scenarios

Slow query logs record statements that exceed the log_min_duration_statement value. You can view log details to identify statements that are slowly executed and optimize the statements.

+
RDS supports the following statement types:
  • SELECT
  • INSERT
  • UPDATE
  • DELETE
  • CREATE
  • DROP
  • ALTER
  • DO
  • CALL
  • COPY
+
+
+

Parameter Description

+
+ + + + + + + + + + +
Table 1 Parameters related to PostgreSQL slow queries

Parameter

+

Description

+

log_min_duration_statement

+

Specifies how many milliseconds a query has to run before it has to be logged.

+

log_statement

+

Specifies the statement type. The value can be none, ddl, mod, or all.

+

The default value is none. If you change the value to all, the database log format changes and slow query logs fail to be parsed.

+
+
+
+

Viewing Log Details

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the Slow Query Logs page, view details about slow query logs.

    • You can view the slow query log records of a specified execution statement type or a specific time period.
    • The log_min_duration_statement parameter determines when a slow query log is recorded. However, changes to this parameter do not affect already recorded logs. If log_min_duration_statement is changed from 1s to 0.1s, none of the previously recorded logs that do not meet the new threshold are deleted. For example, a 1.5s SQL statement that was recorded when the threshold was 1s will not be deleted now that the new threshold is 2s.
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+ diff --git a/docs/rds/umn/slow_query_log-sqlserver.html b/docs/rds/umn/slow_query_log-sqlserver.html new file mode 100644 index 000000000..842603919 --- /dev/null +++ b/docs/rds/umn/slow_query_log-sqlserver.html @@ -0,0 +1,55 @@ + + +

Viewing and Downloading Slow Query Logs

+

Scenarios

Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details to identify statements that are executing slowly and optimize the statements. You can also download slow query logs for service analysis.

+
+

Parameter Description

+
+ + + + + + + +
Table 1 Parameters related to Microsoft SQL Server slow queries

Parameter

+

Description

+

long_query_time

+

Specifies how many microseconds a SQL query has to take to be defined as a slow query log. The default value is 1s. When the execution time of an SQL statement exceeds the value of this parameter, the SQL statement is recorded in slow query logs.

+

You can modify the slow log threshold as required.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the Slow Query Logs page, click in the Threshold of Slow Query Log (long_query_time) field to change the threshold.
    • To submit the change, click .
    • To cancel the change, click .
    +
    NOTE:

    The recommended value is 1s. The lock wait time is not calculated into the query time.

    +
    +
+
+
+
+

Viewing Slow Query Logs

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the Slow Query Logs page, click to enable the slow query log function.
  6. The generated slow query logs are displayed.

    Enabling slow query log slightly affects DB instance performance.

    +
    +

  7. Connect to the DB instance through the Microsoft SQL Server client.
  8. After the DB instance is connected, run the following command to view slow query log details:

    select * from ::fn_trace_gettable('D:\SQLTrace\audit\XXX', default)

    +

    XXX indicates the name of the slow query log recorded in 6.

    +
    +

    Example:

    +

    select * from ::fn_trace_gettable('D:\SQLTrace\audit\SQLTrace.trc', default)

    +

    The result is shown in Figure 1.

    +
    Figure 1 Slow query log details
    +

+
+

Downloading a Log

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance.
  5. In the navigation pane on the left, choose Logs. On the Slow Query Logs page, click to enable the slow query log function.

    Enabling slow query log slightly affects DB instance performance.

    +
    +

  6. Locate a log to be downloaded and click Download in the Operation column.

    1. The system automatically loads the downloading preparation tasks. The loading duration is determined by the log file size and network environment.
      • When the log is being prepared for download, the log status is Preparing.
      • When the log is ready for download, the log status is Preparation completed.
      • If the preparation for download fails, the log status is Abnormal.
      +
    2. In the displayed dialog box, click OK to download the log whose status is Preparation completed. If you click Cancel, the system does not download the log.

      The download link is valid for 5 minutes. After the download link expires, a message is displayed indicating that the download link has expired. You can close the window and repeat the procedure 6 to try to download a log again.

      +

      After downloading slow query logs to a local PC, you can use SSMS to connect to the local database and run the following SQL statement to view the slow query log details:

      +

      select * from ::fn_trace_gettable('XXX', default)

      +

      In the preceding command, XXX indicates the local path for storing slow query logs.

      +
      +
    +

+
+
+
+
+
Parent topic: Log Management
+
+
+