From 0110b557aa09e8af8559549d0f32cef2afd3d328 Mon Sep 17 00:00:00 2001 From: wangdengke2 Date: Thu, 14 Aug 2025 14:05:39 +0000 Subject: [PATCH] drs_umn MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reviewed-by: Székely, Ond Co-authored-by: wangdengke2 Co-committed-by: wangdengke2 --- docs/drs/umn/ALL_META.TXT.json | 1006 +++++++++---- docs/drs/umn/CLASS.TXT.json | 1270 ++++++++++------- docs/drs/umn/drs_01_0001.html | 2 + docs/drs/umn/drs_01_0002.html | 2 +- docs/drs/umn/drs_01_0004.html | 4 +- docs/drs/umn/drs_01_0005.html | 4 +- docs/drs/umn/drs_01_0201.html | 8 +- docs/drs/umn/drs_01_0301.html | 55 +- docs/drs/umn/drs_01_0302.html | 208 +-- docs/drs/umn/drs_01_0303.html | 12 +- docs/drs/umn/drs_01_0305.html | 14 +- docs/drs/umn/drs_01_0313.html | 15 + docs/drs/umn/drs_01_0314.html | 169 +++ docs/drs/umn/drs_01_0326.html | 2 +- docs/drs/umn/drs_02_0002.html | 10 +- docs/drs/umn/drs_02_0005.html | 4 +- docs/drs/umn/drs_02_0006.html | 6 +- docs/drs/umn/drs_02_0007.html | 8 +- docs/drs/umn/drs_02_0009.html | 2 +- docs/drs/umn/drs_02_0010.html | 4 +- docs/drs/umn/drs_02_0017.html | 2 + docs/drs/umn/drs_02_0024.html | 2 +- docs/drs/umn/drs_02_0025.html | 2 +- docs/drs/umn/drs_02_0027.html | 12 +- docs/drs/umn/drs_02_0028.html | 2 +- docs/drs/umn/drs_03_0001.html | 2 +- docs/drs/umn/drs_03_0002.html | 4 +- docs/drs/umn/drs_03_0026.html | 4 +- docs/drs/umn/drs_03_0035.html | 10 +- docs/drs/umn/drs_03_0046.html | 2 +- docs/drs/umn/drs_03_0047.html | 4 +- docs/drs/umn/drs_03_0100.html | 4 +- docs/drs/umn/drs_03_0105.html | 15 + docs/drs/umn/drs_03_0108.html | 19 + docs/drs/umn/drs_03_0109.html | 2 +- docs/drs/umn/drs_03_1113.html | 2 +- docs/drs/umn/drs_03_1117.html | 6 +- docs/drs/umn/drs_03_1118.html | 331 ----- docs/drs/umn/drs_03_1124.html | 30 +- docs/drs/umn/drs_03_1131.html | 8 +- docs/drs/umn/drs_03_1134.html | 2 +- docs/drs/umn/drs_04_0002.html | 2 +- docs/drs/umn/drs_04_0005.html | 2 +- docs/drs/umn/drs_04_0006.html | 4 +- docs/drs/umn/drs_04_0008.html | 2 +- docs/drs/umn/drs_04_0030.html | 353 ++--- docs/drs/umn/drs_04_0088.html | 32 +- docs/drs/umn/drs_04_0089.html | 48 +- docs/drs/umn/drs_04_0090.html | 32 +- docs/drs/umn/drs_04_0095.html | 33 +- docs/drs/umn/drs_04_0100.html | 30 +- docs/drs/umn/drs_04_0101.html | 28 +- docs/drs/umn/drs_04_0102.html | 81 +- docs/drs/umn/drs_04_0104.html | 51 +- docs/drs/umn/drs_04_0107.html | 43 +- docs/drs/umn/drs_04_0115.html | 15 +- docs/drs/umn/drs_04_0117.html | 58 +- docs/drs/umn/drs_04_0118.html | 182 +-- docs/drs/umn/drs_04_0121.html | 316 ---- docs/drs/umn/drs_04_0122.html | 38 +- docs/drs/umn/drs_04_0123.html | 40 +- docs/drs/umn/drs_04_0128.html | 41 +- docs/drs/umn/drs_04_0446.html | 15 +- docs/drs/umn/drs_04_0451.html | 10 +- docs/drs/umn/drs_04_0452.html | 2 - docs/drs/umn/drs_04_0453.html | 237 ++- docs/drs/umn/drs_04_0464.html | 285 ++++ docs/drs/umn/drs_04_0465.html | 49 +- docs/drs/umn/drs_04_0508.html | 428 ++++++ docs/drs/umn/drs_05_0006.html | 6 + docs/drs/umn/drs_05_0007.html | 2 +- docs/drs/umn/drs_05_0011.html | 19 + docs/drs/umn/drs_05_0012.html | 319 +++++ docs/drs/umn/drs_05_0013.html | 16 + docs/drs/umn/drs_05_0014.html | 19 + docs/drs/umn/drs_06_0003.html | 2 +- docs/drs/umn/drs_06_0004.html | 2 +- docs/drs/umn/drs_06_0005.html | 53 +- docs/drs/umn/drs_06_0010.html | 15 + docs/drs/umn/drs_08_0012.html | 4 +- docs/drs/umn/drs_08_0088.html | 6 +- docs/drs/umn/drs_09_0101.html | 4 +- docs/drs/umn/drs_10_0002.html | 2 + docs/drs/umn/drs_10_0003.html | 4 +- docs/drs/umn/drs_10_0004.html | 2 +- docs/drs/umn/drs_10_0007.html | 2 +- docs/drs/umn/drs_10_0009.html | 2 +- docs/drs/umn/drs_10_0012.html | 6 +- docs/drs/umn/drs_10_0015.html | 11 +- docs/drs/umn/drs_10_0401.html | 2 +- docs/drs/umn/drs_10_0402.html | 4 +- docs/drs/umn/drs_10_0409.html | 21 + docs/drs/umn/drs_10_0410.html | 401 ++++++ docs/drs/umn/drs_10_0411.html | 15 + docs/drs/umn/drs_10_0412.html | 18 + docs/drs/umn/drs_11_0005.html | 12 +- docs/drs/umn/drs_11_0006.html | 4 +- docs/drs/umn/drs_11_0007.html | 2 +- docs/drs/umn/drs_11_0008.html | 4 +- docs/drs/umn/drs_11_0009.html | 59 +- docs/drs/umn/drs_11_0010.html | 2 +- docs/drs/umn/drs_11_0226.html | 35 + docs/drs/umn/drs_11_0228.html | 2 +- docs/drs/umn/drs_11_0436.html | 417 ++++++ docs/drs/umn/drs_11_0442.html | 423 ++++++ docs/drs/umn/drs_11_0454.html | 321 +++++ docs/drs/umn/drs_11_0462.html | 22 + docs/drs/umn/drs_12_0008.html | 2 + docs/drs/umn/drs_12_0009.html | 2 +- docs/drs/umn/drs_15_0100.html | 2 +- docs/drs/umn/drs_16_0001.html | 2 +- docs/drs/umn/drs_16_1148.html | 8 +- docs/drs/umn/drs_16_1155.html | 10 +- docs/drs/umn/drs_TaskMangement.html | 2 + docs/drs/umn/drs_backup_tag.html | 5 +- docs/drs/umn/drs_change_history.html | 58 +- docs/drs/umn/drs_disaster_tag.html | 5 +- docs/drs/umn/drs_offline_migration.html | 10 +- docs/drs/umn/drs_online_migration.html | 2 +- docs/drs/umn/drs_online_tag.html | 9 +- docs/drs/umn/drs_synchronization_tag.html | 5 +- docs/drs/umn/en-us_image_0000001320979513.png | Bin 0 -> 444 bytes docs/drs/umn/en-us_image_0000001710470528.png | Bin 0 -> 490 bytes docs/drs/umn/en-us_image_0000001710470540.png | Bin 0 -> 490 bytes docs/drs/umn/en-us_image_0000001710470864.png | Bin 234 -> 0 bytes docs/drs/umn/en-us_image_0000001710471068.png | Bin 0 -> 1004 bytes docs/drs/umn/en-us_image_0000001710471120.png | Bin 0 -> 27150 bytes docs/drs/umn/en-us_image_0000001710630592.png | Bin 0 -> 42406 bytes docs/drs/umn/en-us_image_0000001710631156.png | Bin 234 -> 0 bytes docs/drs/umn/en-us_image_0000001758430081.png | Bin 0 -> 490 bytes docs/drs/umn/en-us_image_0000001758430181.png | Bin 0 -> 490 bytes docs/drs/umn/en-us_image_0000001758550585.png | Bin 234 -> 0 bytes docs/drs/umn/en-us_image_0000001815857830.png | Bin 0 -> 51463 bytes docs/drs/umn/en-us_image_0000001862537477.png | Bin 123525 -> 0 bytes docs/drs/umn/en-us_image_0000001918683154.png | Bin 0 -> 547 bytes docs/drs/umn/en-us_image_0000002199576769.png | Bin 0 -> 444 bytes docs/drs/umn/en-us_image_0000002199662333.png | Bin 0 -> 444 bytes 137 files changed, 5703 insertions(+), 2406 deletions(-) create mode 100644 docs/drs/umn/drs_01_0313.html create mode 100644 docs/drs/umn/drs_01_0314.html create mode 100644 docs/drs/umn/drs_03_0105.html create mode 100644 docs/drs/umn/drs_03_0108.html delete mode 100644 docs/drs/umn/drs_03_1118.html delete mode 100644 docs/drs/umn/drs_04_0121.html create mode 100644 docs/drs/umn/drs_04_0464.html create mode 100644 docs/drs/umn/drs_04_0508.html create mode 100644 docs/drs/umn/drs_05_0011.html create mode 100644 docs/drs/umn/drs_05_0012.html create mode 100644 docs/drs/umn/drs_05_0013.html create mode 100644 docs/drs/umn/drs_05_0014.html create mode 100644 docs/drs/umn/drs_06_0010.html create mode 100644 docs/drs/umn/drs_10_0409.html create mode 100644 docs/drs/umn/drs_10_0410.html create mode 100644 docs/drs/umn/drs_10_0411.html create mode 100644 docs/drs/umn/drs_10_0412.html create mode 100644 docs/drs/umn/drs_11_0226.html create mode 100644 docs/drs/umn/drs_11_0436.html create mode 100644 docs/drs/umn/drs_11_0442.html create mode 100644 docs/drs/umn/drs_11_0454.html create mode 100644 docs/drs/umn/drs_11_0462.html create mode 100644 docs/drs/umn/en-us_image_0000001320979513.png create mode 100644 docs/drs/umn/en-us_image_0000001710470528.png create mode 100644 docs/drs/umn/en-us_image_0000001710470540.png delete mode 100644 docs/drs/umn/en-us_image_0000001710470864.png create mode 100644 docs/drs/umn/en-us_image_0000001710471068.png create mode 100644 docs/drs/umn/en-us_image_0000001710471120.png create mode 100644 docs/drs/umn/en-us_image_0000001710630592.png delete mode 100644 docs/drs/umn/en-us_image_0000001710631156.png create mode 100644 docs/drs/umn/en-us_image_0000001758430081.png create mode 100644 docs/drs/umn/en-us_image_0000001758430181.png delete mode 100644 docs/drs/umn/en-us_image_0000001758550585.png create mode 100644 docs/drs/umn/en-us_image_0000001815857830.png delete mode 100644 docs/drs/umn/en-us_image_0000001862537477.png create mode 100644 docs/drs/umn/en-us_image_0000001918683154.png create mode 100644 docs/drs/umn/en-us_image_0000002199576769.png create mode 100644 docs/drs/umn/en-us_image_0000002199662333.png diff --git a/docs/drs/umn/ALL_META.TXT.json b/docs/drs/umn/ALL_META.TXT.json index 9033233fe..1c426101c 100644 --- a/docs/drs/umn/ALL_META.TXT.json +++ b/docs/drs/umn/ALL_META.TXT.json @@ -254,11 +254,53 @@ "title":"GaussDB->MySQL", "githuburl":"" }, + { + "uri":"drs_01_0313.html", + "node_id":"drs_01_0313.xml", + "product_code":"drs", + "code":"13", + "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":"Specification Description", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Specification Description", + "githuburl":"" + }, + { + "uri":"drs_01_0314.html", + "node_id":"drs_01_0314.xml", + "product_code":"drs", + "code":"14", + "des":"The performance indicators provided in this section are for reference only. The actual environment is affected by factors such as the performance of the source or destina", + "doc_type":"usermanual", + "kw":"Real-Time Synchronization,Specification Description,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Real-Time Synchronization", + "githuburl":"" + }, { "uri":"drs_01_0005.html", "node_id":"drs_01_0005.xml", "product_code":"drs", - "code":"13", + "code":"15", "des":"VPC-based migration refers to a real-time migration that the source and destination databases are in the same VPC or two VPCs that can communicate with each other. No add", "doc_type":"usermanual", "kw":"entrust your account to the administrator,DRS,Basic Concepts,Service Overview,User Guide", @@ -279,7 +321,7 @@ "uri":"drs_01_0012.html", "node_id":"drs_01_0012.xml", "product_code":"drs", - "code":"14", + "code":"16", "des":"You can encrypt data and database connections and increase database account security.Before saving sensitive information and private data in a database, encrypt data to r", "doc_type":"usermanual", "kw":"Security Suggestions,Service Overview,User Guide", @@ -300,7 +342,7 @@ "uri":"drs_01_0021.html", "node_id":"drs_01_0021.xml", "product_code":"drs", - "code":"15", + "code":"17", "des":"To begin using DRS, register an account on the official website. When the registration is successful, you can access all cloud services, including DRS and RDS.If you have", "doc_type":"usermanual", "kw":"Accessing DRS,Service Overview,User Guide", @@ -321,7 +363,7 @@ "uri":"drs_01_0200.html", "node_id":"drs_01_0200.xml", "product_code":"drs", - "code":"16", + "code":"18", "des":"To improve your experience with DRS, add the Security Administrator permission using IAM in case some functions become unavailable, such as scheduled task startup, automa", "doc_type":"usermanual", "kw":"Instructions,Service Overview,User Guide", @@ -342,7 +384,7 @@ "uri":"drs_01_0201.html", "node_id":"drs_01_0201.xml", "product_code":"drs", - "code":"17", + "code":"19", "des":"If you need to assign different permissions to employees in your enterprise to access your DRS resources, IAM is a good choice for fine-grained permissions management. IA", "doc_type":"usermanual", "kw":"Permissions Management,Service Overview,User Guide", @@ -363,7 +405,7 @@ "uri":"drs_01_0318.html", "node_id":"drs_01_0318.xml", "product_code":"drs", - "code":"18", + "code":"20", "des":"You understand and agree that your use of this service complies with laws and regulations, including but not limited to legal compliance requirements on data content, dat", "doc_type":"usermanual", "kw":"Compliance Description,Service Overview,User Guide", @@ -384,7 +426,7 @@ "uri":"drs_01_0004.html", "node_id":"drs_01_0004.xml", "product_code":"drs", - "code":"19", + "code":"21", "des":"DRS can migrate data from your databases to the RDS databases in the cloud. For more information about RDS, see Relational Database Service User Guide.Supported network t", "doc_type":"usermanual", "kw":"MongoDB databases,Related Services,Service Overview,User Guide", @@ -405,7 +447,7 @@ "uri":"drs_02_0470.html", "node_id":"drs_02_0470.xml", "product_code":"drs", - "code":"20", + "code":"22", "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":"Preparations", @@ -426,7 +468,7 @@ "uri":"drs_02_0471.html", "node_id":"drs_02_0471.xml", "product_code":"drs", - "code":"21", + "code":"23", "des":"Before creating a DRS task, make preparations given in the following table to meet the environment requirements.", "doc_type":"usermanual", "kw":"Overview,Preparations,User Guide", @@ -447,7 +489,7 @@ "uri":"drs_08_0010.html", "node_id":"drs_08_0010.xml", "product_code":"drs", - "code":"22", + "code":"24", "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":"Permissions Management", @@ -468,7 +510,7 @@ "uri":"drs_08_0012.html", "node_id":"drs_08_0012.xml", "product_code":"drs", - "code":"23", + "code":"25", "des":"This section describes IAM's fine-grained permissions management for DRS.With IAM, you can:Create IAM users for employees based on the organizational structure of your en", "doc_type":"usermanual", "kw":"Creating a User and Granting Permissions,Permissions Management,User Guide", @@ -489,7 +531,7 @@ "uri":"drs_08_0088.html", "node_id":"drs_08_0088.xml", "product_code":"drs", - "code":"24", + "code":"26", "des":"Custom policies can be created to supplement the system-defined policies of DRS.You can create custom policies in either of the following ways:Visual editor: Select cloud", "doc_type":"usermanual", "kw":"Creating a Custom Policy,Permissions Management,User Guide", @@ -510,7 +552,7 @@ "uri":"drs_02_0017.html", "node_id":"drs_02_0017.xml", "product_code":"drs", - "code":"25", + "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":"Real-Time Migration", @@ -531,7 +573,7 @@ "uri":"drs_online_migration.html", "node_id":"drs_online_migration.xml", "product_code":"drs", - "code":"26", + "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":"To the Cloud", @@ -552,7 +594,7 @@ "uri":"drs_04_0088.html", "node_id":"drs_04_0088.xml", "product_code":"drs", - "code":"27", + "code":"29", "des":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", "doc_type":"usermanual", "kw":"migration,From MySQL to MySQL,To the Cloud,User Guide", @@ -573,7 +615,7 @@ "uri":"drs_04_0089.html", "node_id":"drs_04_0089.xml", "product_code":"drs", - "code":"28", + "code":"30", "des":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", "doc_type":"usermanual", "kw":"From MySQL to DDM,To the Cloud,User Guide", @@ -594,10 +636,10 @@ "uri":"drs_04_0090.html", "node_id":"drs_04_0090.xml", "product_code":"drs", - "code":"29", + "code":"31", "des":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", "doc_type":"usermanual", - "kw":"From MySQL to GaussDB(for MySQL) Primary/Standby,To the Cloud,User Guide", + "kw":"From MySQL to TaurusDB Cluster,To the Cloud,User Guide", "search_title":"", "metedata":[ { @@ -608,14 +650,14 @@ "opensource":"true" } ], - "title":"From MySQL to GaussDB(for MySQL) Primary/Standby", + "title":"From MySQL to TaurusDB Cluster", "githuburl":"" }, { "uri":"drs_04_0095.html", "node_id":"drs_04_0095.xml", "product_code":"drs", - "code":"30", + "code":"32", "des":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", "doc_type":"usermanual", "kw":"From MongoDB to DDS,To the Cloud,User Guide", @@ -636,7 +678,7 @@ "uri":"drs_02_0031.html", "node_id":"drs_02_0031.xml", "product_code":"drs", - "code":"31", + "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":"Out of the Cloud", @@ -657,7 +699,7 @@ "uri":"drs_04_0100.html", "node_id":"drs_04_0100.xml", "product_code":"drs", - "code":"32", + "code":"34", "des":"To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require diffe", "doc_type":"usermanual", "kw":"migration,From MySQL to MySQL,Out of the Cloud,User Guide", @@ -678,7 +720,7 @@ "uri":"drs_04_0101.html", "node_id":"drs_04_0101.xml", "product_code":"drs", - "code":"33", + "code":"35", "des":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", "doc_type":"usermanual", "kw":"From DDS to MongoDB,Out of the Cloud,User Guide", @@ -699,7 +741,7 @@ "uri":"drs_02_0490.html", "node_id":"drs_02_0490.xml", "product_code":"drs", - "code":"34", + "code":"36", "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":"Between Self-built Databases", @@ -720,7 +762,7 @@ "uri":"drs_03_1117.html", "node_id":"drs_03_1117.xml", "product_code":"drs", - "code":"35", + "code":"37", "des":"When a task is being started or in the full migration phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.To maintain data co", "doc_type":"usermanual", "kw":"migration,From MySQL to MySQL,Between Self-built Databases,User Guide", @@ -741,7 +783,7 @@ "uri":"drs_04_0010.html", "node_id":"drs_04_0010.xml", "product_code":"drs", - "code":"36", + "code":"38", "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 Management", @@ -762,7 +804,7 @@ "uri":"drs_02_0002.html", "node_id":"drs_02_0002.xml", "product_code":"drs", - "code":"37", + "code":"39", "des":"A complete real-time migration consists of creating a migration task, tracking task progress, analyzing migration logs, and comparing data consistency. By comparing multi", "doc_type":"usermanual", "kw":"migration,Step 1: Create a Migration Task,Task Management,User Guide", @@ -783,7 +825,7 @@ "uri":"drs_02_0006.html", "node_id":"drs_02_0006.xml", "product_code":"drs", - "code":"38", + "code":"40", "des":"The migration progress of a real-time migration task helps you keep track of the status of the migration task.DRS shows the migration progress using a progress bar, helpi", "doc_type":"usermanual", "kw":"migration,Step 2: Query the Migration Progress,Task Management,User Guide", @@ -804,7 +846,7 @@ "uri":"drs_02_0005.html", "node_id":"drs_02_0005.xml", "product_code":"drs", - "code":"39", + "code":"41", "des":"Migration logs refer to the warning-, error-, and info-level logs generated during the migration process. This section describes how to view migration logs to locate and ", "doc_type":"usermanual", "kw":"view migration logs,Step 3: View Migration Logs,Task Management,User Guide", @@ -825,7 +867,7 @@ "uri":"drs_02_0007.html", "node_id":"drs_02_0007.xml", "product_code":"drs", - "code":"40", + "code":"42", "des":"This section describes how to compare migration items to check if there are any differences between source and destination databases. By comparing migration objects, you ", "doc_type":"usermanual", "kw":"compare migration items,Step 4: Compare Migration Items,Task Management,User Guide", @@ -846,7 +888,7 @@ "uri":"drs_03_0007.html", "node_id":"drs_03_0007.xml", "product_code":"drs", - "code":"41", + "code":"43", "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 Objects", @@ -867,7 +909,7 @@ "uri":"drs_09_0017.html", "node_id":"drs_09_0017.xml", "product_code":"drs", - "code":"42", + "code":"44", "des":"During a database migration, accounts need to be migrated separately.During the migration of MySQL databases, there are accounts that can be migrated completely, accounts", "doc_type":"usermanual", "kw":"Migrating Accounts,Managing Objects,User Guide", @@ -888,7 +930,7 @@ "uri":"drs_08_0001.html", "node_id":"drs_08_0001.xml", "product_code":"drs", - "code":"43", + "code":"45", "des":"Parameter comparison helps you check consistency between the source and destination database data to ensure your services will not be affected after being migrated.This s", "doc_type":"usermanual", "kw":"Parameters for Comparison,Managing Objects,User Guide", @@ -909,7 +951,7 @@ "uri":"drs_03_0008.html", "node_id":"drs_03_0008.xml", "product_code":"drs", - "code":"44", + "code":"46", "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 Life Cycle", @@ -930,7 +972,7 @@ "uri":"drs_04_0005.html", "node_id":"drs_04_0005.xml", "product_code":"drs", - "code":"45", + "code":"47", "des":"This section describes how to view details about a migration task, including information about the task, replication instance, and migration.You have logged in to the DRS", "doc_type":"usermanual", "kw":"Viewing Task Details,Task Life Cycle,User Guide", @@ -951,7 +993,7 @@ "uri":"drs_04_0006.html", "node_id":"drs_04_0006.xml", "product_code":"drs", - "code":"46", + "code":"48", "des":"After a migration task is created, you can modify task information to identify different tasks.The following task information can be edited:Task nameDescriptionTask start", "doc_type":"usermanual", "kw":"Editing Migration Task Information,Task Life Cycle,User Guide", @@ -972,7 +1014,7 @@ "uri":"drs_03_1135.html", "node_id":"drs_03_1135.xml", "product_code":"drs", - "code":"47", + "code":"49", "des":"During the migration, you may change the password of the source or destination database. As a result, the migration task fails. In this case, you need to change the passw", "doc_type":"usermanual", "kw":"modify,Modifying Connection Information,Task Life Cycle,User Guide", @@ -993,7 +1035,7 @@ "uri":"drs_03_0046.html", "node_id":"drs_03_0046.xml", "product_code":"drs", - "code":"48", + "code":"50", "des":"You can choose whether to control the flow. DRS allows you to change the flow control mode after a task is created. Currently, only the following real-time migration type", "doc_type":"usermanual", "kw":"Modifying the Flow Control Mode,Task Life Cycle,User Guide", @@ -1014,7 +1056,7 @@ "uri":"drs_03_0002.html", "node_id":"drs_03_0002.xml", "product_code":"drs", - "code":"49", + "code":"51", "des":"For a migration task that has been created but not started, DRS allows you to edit the configuration information of the task, including the task information, replication ", "doc_type":"usermanual", "kw":"edit,Editing a Migration Task,Task Life Cycle,User Guide", @@ -1035,7 +1077,7 @@ "uri":"drs_09_0100.html", "node_id":"drs_09_0100.xml", "product_code":"drs", - "code":"50", + "code":"52", "des":"A fault may occur during the migration due to external factors, such as insufficient storage space. After the fault is rectified based on the migration log information, y", "doc_type":"usermanual", "kw":"Resuming a Migration Task,Task Life Cycle,User Guide", @@ -1056,7 +1098,7 @@ "uri":"drs_03_0100.html", "node_id":"drs_03_0100.xml", "product_code":"drs", - "code":"51", + "code":"53", "des":"During the migration, if a migration task fails due to uncertain causes, the background will resume the task several times. However, the task may fail to be recovered in ", "doc_type":"usermanual", "kw":"reset failed migration tasks,Resetting a Migration Task,Task Life Cycle,User Guide", @@ -1077,7 +1119,7 @@ "uri":"drs_03_0109.html", "node_id":"drs_03_0109.xml", "product_code":"drs", - "code":"52", + "code":"54", "des":"During migration, if the flow control mode cannot meet the requirements during peak hours, you can pause the migration task.You can pause the following migration tasks:To", "doc_type":"usermanual", "kw":"Pausing a Migration Task,Task Life Cycle,User Guide", @@ -1098,7 +1140,7 @@ "uri":"drs_03_0004.html", "node_id":"drs_03_0004.xml", "product_code":"drs", - "code":"53", + "code":"55", "des":"After the source database and services are migrated to the destination database, you can stop the migration task. To prevent data from being overwritten after the source ", "doc_type":"usermanual", "kw":"stop the migration task,Stopping a Migration Task,Task Life Cycle,User Guide", @@ -1119,7 +1161,7 @@ "uri":"drs_03_0005.html", "node_id":"drs_03_0005.xml", "product_code":"drs", - "code":"54", + "code":"56", "des":"This section describes how to delete a migration task that has been completed or has failed. Deleted tasks will no longer be displayed in the task list. Exercise caution ", "doc_type":"usermanual", "kw":"delete a migration task,Deleting a Migration Task,Task Life Cycle,User Guide", @@ -1140,7 +1182,7 @@ "uri":"drs_03_0001.html", "node_id":"drs_03_0001.xml", "product_code":"drs", - "code":"55", + "code":"57", "des":"Migration statuses indicate different migration phases.Table 1 lists statuses and descriptions of online migration tasks.If a task fails to be created, DRS retains the ta", "doc_type":"usermanual", "kw":"migration,Task Statuses,Task Life Cycle,User Guide", @@ -1161,7 +1203,7 @@ "uri":"drs_online_tag.html", "node_id":"drs_online_tag.xml", "product_code":"drs", - "code":"56", + "code":"58", "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),Tag Management,Real-Time Migration,User Guide", @@ -1178,11 +1220,53 @@ "title":"Tag Management", "githuburl":"" }, + { + "uri":"drs_03_0105.html", + "node_id":"drs_03_0105.xml", + "product_code":"drs", + "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":"Interconnecting with Cloud Eye", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Interconnecting with Cloud Eye", + "githuburl":"" + }, + { + "uri":"drs_03_0108.html", + "node_id":"drs_03_0108.xml", + "product_code":"drs", + "code":"60", + "des":"Cloud Eye monitors the running statuses of replication, synchronization, and DR instances. You can obtain the monitoring metrics on the management console. Monitored data", + "doc_type":"usermanual", + "kw":"Viewing Monitoring Metrics,Interconnecting with Cloud Eye,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Viewing Monitoring Metrics", + "githuburl":"" + }, { "uri":"drs_04_0001.html", "node_id":"drs_04_0001.xml", "product_code":"drs", - "code":"57", + "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":"Backup Migration", @@ -1203,7 +1287,7 @@ "uri":"drs_offline_migration.html", "node_id":"drs_offline_migration.xml", "product_code":"drs", - "code":"58", + "code":"62", "des":"It often becomes necessary to hide the real IP address of your database for the sake of security. Migrating data through direct connections is an option, but costly. DRS ", "doc_type":"usermanual", "kw":"Migration Overview,Backup Migration,User Guide", @@ -1224,7 +1308,7 @@ "uri":"drs_02_0010.html", "node_id":"drs_02_0010.xml", "product_code":"drs", - "code":"59", + "code":"63", "des":"You have logged in to the DRS console.For details about the supported DB types and versions, see Backup Migration.This section describes constraints on backup migrations ", "doc_type":"usermanual", "kw":"backup migrations of Microsoft SQL Server databases,Creating an RDS Backup Migration Task,Backup Mig", @@ -1245,7 +1329,7 @@ "uri":"drs_02_0009.html", "node_id":"drs_02_0009.xml", "product_code":"drs", - "code":"60", + "code":"64", "des":"You have logged in to the DRS console.For details about the supported DB types and versions, see Backup Migration.This section describes constraints on backup migrations ", "doc_type":"usermanual", "kw":"Creating a Backup Using OBS Buckets,Backup Migration,User Guide", @@ -1266,7 +1350,7 @@ "uri":"drs_04_0007.html", "node_id":"drs_04_0007.xml", "product_code":"drs", - "code":"61", + "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":"Task Management", @@ -1287,7 +1371,7 @@ "uri":"drs_04_0002.html", "node_id":"drs_04_0002.xml", "product_code":"drs", - "code":"62", + "code":"66", "des":"The Basic Information page of a backup migration task displays information about the task, backup files, and databases. This section describes how to view details about c", "doc_type":"usermanual", "kw":"Viewing Task Details,Task Management,User Guide", @@ -1308,7 +1392,7 @@ "uri":"drs_04_0008.html", "node_id":"drs_04_0008.xml", "product_code":"drs", - "code":"63", + "code":"67", "des":"After a backup migration task is created, you can modify basic information about the task to identify different tasks.The following task information can be edited:Task na", "doc_type":"usermanual", "kw":"Editing Migration Task Information,Task Management,User Guide", @@ -1329,7 +1413,7 @@ "uri":"drs_04_0003.html", "node_id":"drs_04_0003.xml", "product_code":"drs", - "code":"64", + "code":"68", "des":"Migration logs refer to the warning-, error-, and info-level logs generated during the migration process. This section describes how to view migration logs to locate and ", "doc_type":"usermanual", "kw":"view migration logs,Viewing Migration Logs,Task Management,User Guide", @@ -1350,7 +1434,7 @@ "uri":"drs_04_0004.html", "node_id":"drs_04_0004.xml", "product_code":"drs", - "code":"65", + "code":"69", "des":"This section describes how to delete a migration task. Deleted tasks will no longer be displayed in the task list. Exercise caution when performing this operation.You hav", "doc_type":"usermanual", "kw":"delete a migration task,Deleting a Migration Task,Task Management,User Guide", @@ -1371,7 +1455,7 @@ "uri":"drs_03_0010.html", "node_id":"drs_03_0010.xml", "product_code":"drs", - "code":"66", + "code":"70", "des":"Migration statuses indicate different migration phases.Table 1 lists statuses and descriptions of backup migration tasks.Deleted migration tasks are not displayed in the ", "doc_type":"usermanual", "kw":"statuses and descriptions of backup migration tasks,Task Statuses,Task Management,User Guide", @@ -1392,7 +1476,7 @@ "uri":"drs_backup_tag.html", "node_id":"drs_backup_tag.xml", "product_code":"drs", - "code":"67", + "code":"71", "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),Tag Management,Backup Migration,User Guide", @@ -1413,7 +1497,7 @@ "uri":"drs_10_0002.html", "node_id":"drs_10_0002.xml", "product_code":"drs", - "code":"68", + "code":"72", "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":"Real-Time Synchronization", @@ -1434,7 +1518,7 @@ "uri":"drs_11_0457.html", "node_id":"drs_11_0457.xml", "product_code":"drs", - "code":"69", + "code":"73", "des":"DRS real-time synchronization supports multiple topology types. You can plan the topology types as required. For details, see the following content.To ensure data consist", "doc_type":"usermanual", "kw":"Data Synchronization Topologies,Real-Time Synchronization,User Guide", @@ -1455,7 +1539,7 @@ "uri":"drs_06_0003.html", "node_id":"drs_06_0003.xml", "product_code":"drs", - "code":"70", + "code":"74", "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":"To the Cloud", @@ -1476,7 +1560,7 @@ "uri":"drs_04_0102.html", "node_id":"drs_04_0102.xml", "product_code":"drs", - "code":"71", + "code":"75", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "doc_type":"usermanual", "kw":"From MySQL to MySQL,To the Cloud,User Guide", @@ -1497,7 +1581,7 @@ "uri":"drs_04_0104.html", "node_id":"drs_04_0104.xml", "product_code":"drs", - "code":"72", + "code":"76", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "doc_type":"usermanual", "kw":"From MySQL to GaussDB Distributed,To the Cloud,User Guide", @@ -1518,10 +1602,10 @@ "uri":"drs_03_1124.html", "node_id":"drs_03_1124.xml", "product_code":"drs", - "code":"73", + "code":"77", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "doc_type":"usermanual", - "kw":"From MySQL to GaussDB(for MySQL) Primary/Standby,To the Cloud,User Guide", + "kw":"From MySQL to TaurusDB Cluster,To the Cloud,User Guide", "search_title":"", "metedata":[ { @@ -1532,14 +1616,14 @@ "opensource":"true" } ], - "title":"From MySQL to GaussDB(for MySQL) Primary/Standby", + "title":"From MySQL to TaurusDB Cluster", "githuburl":"" }, { "uri":"drs_04_0107.html", "node_id":"drs_04_0107.xml", "product_code":"drs", - "code":"74", + "code":"78", "des":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.To start a syn", "doc_type":"usermanual", "kw":"From PostgreSQL to PostgreSQL,To the Cloud,User Guide", @@ -1560,7 +1644,7 @@ "uri":"drs_04_0446.html", "node_id":"drs_04_0446.xml", "product_code":"drs", - "code":"75", + "code":"79", "des":"When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.To keep data ", "doc_type":"usermanual", "kw":"From Oracle to PostgreSQL,To the Cloud,User Guide", @@ -1581,7 +1665,7 @@ "uri":"drs_04_0115.html", "node_id":"drs_04_0115.xml", "product_code":"drs", - "code":"76", + "code":"80", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "doc_type":"usermanual", "kw":"From DDM to MySQL,To the Cloud,User Guide", @@ -1602,7 +1686,7 @@ "uri":"drs_04_0465.html", "node_id":"drs_04_0465.xml", "product_code":"drs", - "code":"77", + "code":"81", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "doc_type":"usermanual", "kw":"From DDM to DDM,To the Cloud,User Guide", @@ -1623,7 +1707,7 @@ "uri":"drs_04_0451.html", "node_id":"drs_04_0451.xml", "product_code":"drs", - "code":"78", + "code":"82", "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":"Out of the Cloud", @@ -1644,7 +1728,7 @@ "uri":"drs_04_0117.html", "node_id":"drs_04_0117.xml", "product_code":"drs", - "code":"79", + "code":"83", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "doc_type":"usermanual", "kw":"From MySQL to MySQL,Out of the Cloud,User Guide", @@ -1665,8 +1749,8 @@ "uri":"drs_04_0118.html", "node_id":"drs_04_0118.xml", "product_code":"drs", - "code":"80", - "des":"DMS for KafkaYou have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The s", + "code":"84", + "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The success of dat", "doc_type":"usermanual", "kw":"From MySQL to Kafka,Out of the Cloud,User Guide", "search_title":"", @@ -1686,7 +1770,7 @@ "uri":"drs_04_0453.html", "node_id":"drs_04_0453.xml", "product_code":"drs", - "code":"81", + "code":"85", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "doc_type":"usermanual", "kw":"From DDM to MySQL,Out of the Cloud,User Guide", @@ -1704,13 +1788,13 @@ "githuburl":"" }, { - "uri":"drs_04_0121.html", - "node_id":"drs_04_0121.xml", + "uri":"drs_04_0464.html", + "node_id":"drs_04_0464.xml", "product_code":"drs", - "code":"82", - "des":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.Before you sta", + "code":"86", + "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The success of dat", "doc_type":"usermanual", - "kw":"From GaussDB Distributed to MySQL,Out of the Cloud,User Guide", + "kw":"From DDS to MongoDB,Out of the Cloud,User Guide", "search_title":"", "metedata":[ { @@ -1721,14 +1805,98 @@ "opensource":"true" } ], - "title":"From GaussDB Distributed to MySQL", + "title":"From DDS to MongoDB", + "githuburl":"" + }, + { + "uri":"drs_04_0508.html", + "node_id":"drs_04_0508.xml", + "product_code":"drs", + "code":"87", + "des":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.To start a syn", + "doc_type":"usermanual", + "kw":"From PostgreSQL to PostgreSQL,Out of the Cloud,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"From PostgreSQL to PostgreSQL", + "githuburl":"" + }, + { + "uri":"drs_11_0436.html", + "node_id":"drs_11_0436.xml", + "product_code":"drs", + "code":"88", + "des":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.Before you sta", + "doc_type":"usermanual", + "kw":"From GaussDB Distributed to Oracle,Out of the Cloud,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"From GaussDB Distributed to Oracle", + "githuburl":"" + }, + { + "uri":"drs_11_0454.html", + "node_id":"drs_11_0454.xml", + "product_code":"drs", + "code":"89", + "des":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.Before you sta", + "doc_type":"usermanual", + "kw":"From GaussDB Distributed to Kafka,Out of the Cloud,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"From GaussDB Distributed to Kafka", + "githuburl":"" + }, + { + "uri":"drs_11_0442.html", + "node_id":"drs_11_0442.xml", + "product_code":"drs", + "code":"90", + "des":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.Before you sta", + "doc_type":"usermanual", + "kw":"From GaussDB Distributed to GaussDB Distributed,Out of the Cloud,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"From GaussDB Distributed to GaussDB Distributed", "githuburl":"" }, { "uri":"drs_04_0452.html", "node_id":"drs_04_0452.xml", "product_code":"drs", - "code":"83", + "code":"91", "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":"Between Self-built Databases", @@ -1745,32 +1913,11 @@ "title":"Between Self-built Databases", "githuburl":"" }, - { - "uri":"drs_03_1118.html", - "node_id":"drs_03_1118.xml", - "product_code":"drs", - "code":"84", - "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", - "doc_type":"usermanual", - "kw":"From MySQL to MySQL,Between Self-built Databases,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"drs", - "documenttype":"usermanual", - "IsBot":"No;Yes", - "IsMulti":"No;Yes", - "opensource":"true" - } - ], - "title":"From MySQL to MySQL", - "githuburl":"" - }, { "uri":"drs_04_0128.html", "node_id":"drs_04_0128.xml", "product_code":"drs", - "code":"85", + "code":"92", "des":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The success of dat", "doc_type":"usermanual", "kw":"From MySQL to Kafka,Between Self-built Databases,User Guide", @@ -1791,7 +1938,7 @@ "uri":"drs_TaskMangement.html", "node_id":"drs_taskmangement.xml", "product_code":"drs", - "code":"86", + "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":"Task Management", @@ -1812,7 +1959,7 @@ "uri":"drs_06_0005.html", "node_id":"drs_06_0005.xml", "product_code":"drs", - "code":"87", + "code":"94", "des":"A complete real-time synchronization consists of creating a synchronization task, tracking task progress, analyzing synchronization logs, and comparing data consistency. ", "doc_type":"usermanual", "kw":"Step 1: Create a Synchronization Task,Task Management,User Guide", @@ -1833,7 +1980,7 @@ "uri":"drs_10_0007.html", "node_id":"drs_10_0007.xml", "product_code":"drs", - "code":"88", + "code":"95", "des":"This section describes how to check the synchronization progress.During a full synchronization, DRS displays the progress overview. You can view the structure, data, and ", "doc_type":"usermanual", "kw":"synchronization,view table synchronization progress,Step 2: Query the Synchronization Progress,Task ", @@ -1854,7 +2001,7 @@ "uri":"drs_10_0008.html", "node_id":"drs_10_0008.xml", "product_code":"drs", - "code":"89", + "code":"96", "des":"Synchronization logs refer to the warning-, error-, and info-level logs generated during the synchronization process. This section describes how to view synchronization l", "doc_type":"usermanual", "kw":"view synchronization logs,Step 3: View Synchronization Logs,Task Management,User Guide", @@ -1875,7 +2022,7 @@ "uri":"drs_10_0012.html", "node_id":"drs_10_0012.xml", "product_code":"drs", - "code":"90", + "code":"97", "des":"This section describes how to compare synchronization items to check if there are any differences between source and destination databases. To minimize the impact on serv", "doc_type":"usermanual", "kw":"compare synchronization items,Step 4: Compare Synchronization Items,Task Management,User Guide", @@ -1896,7 +2043,7 @@ "uri":"drs_05_0007.html", "node_id":"drs_05_0007.xml", "product_code":"drs", - "code":"91", + "code":"98", "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 Objects", @@ -1917,7 +2064,7 @@ "uri":"drs_10_0009.html", "node_id":"drs_10_0009.xml", "product_code":"drs", - "code":"92", + "code":"99", "des":"This section describes how to change synchronization objects in a synchronization task. After a data synchronization task is created, you can change synchronization objec", "doc_type":"usermanual", "kw":"Editing Synchronization Objects,Managing Objects,User Guide", @@ -1938,7 +2085,7 @@ "uri":"drs_10_0402.html", "node_id":"drs_10_0402.xml", "product_code":"drs", - "code":"93", + "code":"100", "des":"Real-time synchronization supports the import of objects through files. After a task is created, you can import object files on the Set Synchronization Task page.Only Win", "doc_type":"usermanual", "kw":"Importing Synchronization Objects,Managing Objects,User Guide", @@ -1959,10 +2106,10 @@ "uri":"drs_10_0015.html", "node_id":"drs_10_0015.xml", "product_code":"drs", - "code":"94", + "code":"101", "des":"Data synchronization allows you to synchronize objects (including databases, schemas and tables) in a sources database to the corresponding objects in a destination datab", "doc_type":"usermanual", - "kw":"Mapping Object Names,Managing Objects,User Guide", + "kw":"Changing Object Names (Mapping Object Names),Managing Objects,User Guide", "search_title":"", "metedata":[ { @@ -1973,14 +2120,14 @@ "opensource":"true" } ], - "title":"Mapping Object Names", + "title":"Changing Object Names (Mapping Object Names)", "githuburl":"" }, { "uri":"drs_10_0100.html", "node_id":"drs_10_0100.xml", "product_code":"drs", - "code":"95", + "code":"102", "des":"During real-time synchronization, the objects that can be mapped to the destination include databases, schemas, tables, and columns (in data processing). After a mapping ", "doc_type":"usermanual", "kw":"Viewing Synchronization Mapping Information,Managing Objects,User Guide", @@ -2001,7 +2148,7 @@ "uri":"drs_03_0035.html", "node_id":"drs_03_0035.xml", "product_code":"drs", - "code":"96", + "code":"103", "des":"DRS processes synchronized objects and allows you to add rules for selected objects.After a data filtering rule is added, update the source database to ensure data consis", "doc_type":"usermanual", "kw":"Processing Data,Managing Objects,User Guide", @@ -2018,11 +2165,74 @@ "title":"Processing Data", "githuburl":"" }, + { + "uri":"drs_10_0409.html", + "node_id":"drs_10_0409.xml", + "product_code":"drs", + "code":"104", + "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 Parameters", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Managing Parameters", + "githuburl":"" + }, + { + "uri":"drs_10_0410.html", + "node_id":"drs_10_0410.xml", + "product_code":"drs", + "code":"105", + "des":"DRS allows you to change task parameters based on service requirements.You can change parameters of a synchronization task in the Configuration, Full, Full synchronizatio", + "doc_type":"usermanual", + "kw":"Changing Task Parameters,Managing Parameters,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Changing Task Parameters", + "githuburl":"" + }, + { + "uri":"drs_10_0411.html", + "node_id":"drs_10_0411.xml", + "product_code":"drs", + "code":"106", + "des":"DRS allows you to view the change history of task parameters to meet service requirements.By default, the parameter change history of the last seven days can be queried.", + "doc_type":"usermanual", + "kw":"Viewing Parameter Change History,Managing Parameters,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Viewing Parameter Change History", + "githuburl":"" + }, { "uri":"drs_05_0006.html", "node_id":"drs_05_0006.xml", "product_code":"drs", - "code":"97", + "code":"107", "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 Life Cycle", @@ -2043,7 +2253,7 @@ "uri":"drs_10_0003.html", "node_id":"drs_10_0003.xml", "product_code":"drs", - "code":"98", + "code":"108", "des":"View the information about the synchronization tasks and synchronization instances. This section describes how to view details about a synchronization task you have creat", "doc_type":"usermanual", "kw":"Viewing Task Details,Task Life Cycle,User Guide", @@ -2064,7 +2274,7 @@ "uri":"drs_10_0004.html", "node_id":"drs_10_0004.xml", "product_code":"drs", - "code":"99", + "code":"109", "des":"After a synchronization task is created, you can modify task information to identify different tasks.The following task information can be edited:Task nameDescriptionTask", "doc_type":"usermanual", "kw":"Modifying Task Information,Task Life Cycle,User Guide", @@ -2085,7 +2295,7 @@ "uri":"drs_10_0016.html", "node_id":"drs_10_0016.xml", "product_code":"drs", - "code":"100", + "code":"110", "des":"A data synchronization task may fail due to the change of the password of the source or destination database. You need to update the information and then retry the synchr", "doc_type":"usermanual", "kw":"modify,Modifying Connection Information,Task Life Cycle,User Guide", @@ -2106,7 +2316,7 @@ "uri":"drs_10_0401.html", "node_id":"drs_10_0401.xml", "product_code":"drs", - "code":"101", + "code":"111", "des":"You can choose whether to control the flow. DRS allows you to change the flow control mode after a task is created. Currently, only the following real-time migration type", "doc_type":"usermanual", "kw":"Modifying the Flow Control Mode,Task Life Cycle,User Guide", @@ -2127,7 +2337,7 @@ "uri":"drs_10_0010.html", "node_id":"drs_10_0010.xml", "product_code":"drs", - "code":"102", + "code":"112", "des":"For a synchronization task that has been created but not started, DRS allows you to edit the configuration information of the task, including the source and destination d", "doc_type":"usermanual", "kw":"edit,Editing a Synchronization Task,Task Life Cycle,User Guide", @@ -2148,7 +2358,7 @@ "uri":"drs_10_0400.html", "node_id":"drs_10_0400.xml", "product_code":"drs", - "code":"103", + "code":"113", "des":"A fault may occur during the synchronization due to external factors, such as insufficient storage space. After the fault is rectified based on the synchronization log in", "doc_type":"usermanual", "kw":"Resuming a Synchronization Task,Task Life Cycle,User Guide", @@ -2169,7 +2379,7 @@ "uri":"drs_03_0110.html", "node_id":"drs_03_0110.xml", "product_code":"drs", - "code":"104", + "code":"114", "des":"DRS allows you to pause real-time synchronization tasks.The following tasks can be paused during incremental synchronization:To the cloudMySQL->MySQLPostgreSQL->PostgreSQ", "doc_type":"usermanual", "kw":"Pausing a Synchronization Task,Task Life Cycle,User Guide", @@ -2190,7 +2400,7 @@ "uri":"drs_10_0300.html", "node_id":"drs_10_0300.xml", "product_code":"drs", - "code":"105", + "code":"115", "des":"During real-time synchronization, you can reset the synchronization tasks in one of the following statuses so that you do not need to configure the tasks again.PausedIncr", "doc_type":"usermanual", "kw":"Resetting a Synchronization Task,Task Life Cycle,User Guide", @@ -2207,11 +2417,74 @@ "title":"Resetting a Synchronization Task", "githuburl":"" }, + { + "uri":"drs_10_0412.html", + "node_id":"drs_10_0412.xml", + "product_code":"drs", + "code":"116", + "des":"DRS allows you to restart a synchronization task after task parameters are changed in Changing Task Parameters.Tasks in the Full, Full synchronization failed, Incremental", + "doc_type":"usermanual", + "kw":"Restarting a Synchronization Task,Task Life Cycle,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true", + "documenttype":"usermanual" + } + ], + "title":"Restarting a Synchronization Task", + "githuburl":"" + }, + { + "uri":"drs_06_0010.html", + "node_id":"drs_06_0010.xml", + "product_code":"drs", + "code":"117", + "des":"DRS allows you to change a single-AZ task to a dual-AZ task, improving task reliability while remaining the original task.A dual-AZ task cannot be changed to a single-AZ ", + "doc_type":"usermanual", + "kw":"Changing a Single-AZ Task to a Dual-AZ Task,Task Life Cycle,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true", + "documenttype":"usermanual" + } + ], + "title":"Changing a Single-AZ Task to a Dual-AZ Task", + "githuburl":"" + }, + { + "uri":"drs_11_0462.html", + "node_id":"drs_11_0462.xml", + "product_code":"drs", + "code":"118", + "des":"DRS allows you to clone the configuration of existing synchronization tasks. However, tasks in the following status cannot be cloned:CreatingCreation failedConfigurationP", + "doc_type":"usermanual", + "kw":"Cloning a Synchronization Task,Task Life Cycle,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Cloning a Synchronization Task", + "githuburl":"" + }, { "uri":"drs_10_0013.html", "node_id":"drs_10_0013.xml", "product_code":"drs", - "code":"106", + "code":"119", "des":"After the source database and services are migrated to the destination database, you can stop the synchronization task. To prevent data from being overwritten after the s", "doc_type":"usermanual", "kw":"stop the synchronization task,Stopping a Synchronization Task,Task Life Cycle,User Guide", @@ -2232,7 +2505,7 @@ "uri":"drs_10_0014.html", "node_id":"drs_10_0014.xml", "product_code":"drs", - "code":"107", + "code":"120", "des":"This section describes how to delete a synchronization task that has been completed or has failed. Deleted tasks will no longer be displayed in the task list. Exercise ca", "doc_type":"usermanual", "kw":"delete a synchronization task,Deleting a Synchronization Task,Task Life Cycle,User Guide", @@ -2253,7 +2526,7 @@ "uri":"drs_06_0004.html", "node_id":"drs_06_0004.xml", "product_code":"drs", - "code":"108", + "code":"121", "des":"Synchronization statuses indicate different synchronization phases.", "doc_type":"usermanual", "kw":"Task Statuses,Task Life Cycle,User Guide", @@ -2274,7 +2547,7 @@ "uri":"drs_synchronization_tag.html", "node_id":"drs_synchronization_tag.xml", "product_code":"drs", - "code":"109", + "code":"122", "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),Tag Management,Real-Time Synchronization,User Guide", @@ -2291,11 +2564,95 @@ "title":"Tag Management", "githuburl":"" }, + { + "uri":"drs_05_0011.html", + "node_id":"drs_05_0011.xml", + "product_code":"drs", + "code":"123", + "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":"Interconnecting with Cloud Eye", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Interconnecting with Cloud Eye", + "githuburl":"" + }, + { + "uri":"drs_05_0012.html", + "node_id":"drs_05_0012.xml", + "product_code":"drs", + "code":"124", + "des":"This section describes metrics reported by the Data Replication Service (DRS) to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud ", + "doc_type":"usermanual", + "kw":"Supported Metrics,Interconnecting with Cloud Eye,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Supported Metrics", + "githuburl":"" + }, + { + "uri":"drs_05_0013.html", + "node_id":"drs_05_0013.xml", + "product_code":"drs", + "code":"125", + "des":"You can configure DRS alarm rules to customize the monitored objects and notification policies and learn the DRS running status in a timely manner.This section describes ", + "doc_type":"usermanual", + "kw":"Configuring Alarm Rules,Interconnecting with Cloud Eye,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Configuring Alarm Rules", + "githuburl":"" + }, + { + "uri":"drs_05_0014.html", + "node_id":"drs_05_0014.xml", + "product_code":"drs", + "code":"126", + "des":"Cloud Eye monitors the running statuses of replication, synchronization, and DR instances. You can obtain the monitoring metrics on the management console. Monitored data", + "doc_type":"usermanual", + "kw":"Viewing Monitoring Metrics,Interconnecting with Cloud Eye,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Viewing Monitoring Metrics", + "githuburl":"" + }, { "uri":"drs_03_1113.html", "node_id":"drs_03_1113.xml", "product_code":"drs", - "code":"110", + "code":"127", "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":"Operation Reference in Synchronization Scenarios", @@ -2316,7 +2673,7 @@ "uri":"drs_03_0052.html", "node_id":"drs_03_0052.xml", "product_code":"drs", - "code":"111", + "code":"128", "des":"Data synchronized to the Kafka cluster is stored in JSON, and JSON-C formats.For details about the JSON format from MySQL to Kafka, see Table 1. Parameters for synchroniz", "doc_type":"usermanual", "kw":"Kafka Message Format,Operation Reference in Synchronization Scenarios,User Guide", @@ -2337,7 +2694,7 @@ "uri":"drs_05_0018.html", "node_id":"drs_05_0018.xml", "product_code":"drs", - "code":"112", + "code":"129", "des":"No security authentication mode is available. You only need to enter the IP address and port for connection.The SASL mechanism is used to connect to Kafka, and you need t", "doc_type":"usermanual", "kw":"Kafka Authentication,Operation Reference in Synchronization Scenarios,User Guide", @@ -2358,10 +2715,10 @@ "uri":"drs_03_1131.html", "node_id":"drs_03_1131.xml", "product_code":"drs", - "code":"113", - "des":"This section describes how to clear the streaming replication slots of the source GaussDB distributed database after the incremental or full+incremental synchronization t", + "code":"130", + "des":"This section describes how to delete streaming replication slots of the source distributed GaussDB database after an incremental or a full+incremental synchronization tas", "doc_type":"usermanual", - "kw":"Forcibly Stopping Synchronization of GaussDB Distributed,Operation Reference in Synchronization Scen", + "kw":"Forcibly Stopping Synchronization from GaussDB Distributed,Operation Reference in Synchronization Sc", "search_title":"", "metedata":[ { @@ -2372,14 +2729,14 @@ "opensource":"true" } ], - "title":"Forcibly Stopping Synchronization of GaussDB Distributed", + "title":"Forcibly Stopping Synchronization from GaussDB Distributed", "githuburl":"" }, { "uri":"drs_12_0009.html", "node_id":"drs_12_0009.xml", "product_code":"drs", - "code":"114", + "code":"131", "des":"This section describes how to clear the logical replication slot of the source database, how to synchronize sequence values, and how to reset the sequence values in the d", "doc_type":"usermanual", "kw":"Forcibly Stopping Synchronization of PostgreSQL,Operation Reference in Synchronization Scenarios,Use", @@ -2400,7 +2757,7 @@ "uri":"drs_03_0088.html", "node_id":"drs_03_0088.xml", "product_code":"drs", - "code":"115", + "code":"132", "des":"This section describes how to perform real-time synchronization from PostgreSQL to RDS PostgreSQL. You can create triggers and functions in the source database to obtain ", "doc_type":"usermanual", "kw":"Creating Triggers and Functions to Implement Incremental DDL Synchronization for PostgreSQL,Operatio", @@ -2421,7 +2778,7 @@ "uri":"drs_03_0023.html", "node_id":"drs_03_0023.xml", "product_code":"drs", - "code":"116", + "code":"133", "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":"Real-Time Disaster Recovery", @@ -2442,7 +2799,7 @@ "uri":"drs_02_0024.html", "node_id":"drs_02_0024.xml", "product_code":"drs", - "code":"117", + "code":"134", "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":"DR Scenarios", @@ -2463,7 +2820,7 @@ "uri":"drs_04_0122.html", "node_id":"drs_04_0122.xml", "product_code":"drs", - "code":"118", + "code":"135", "des":"You have logged in to the DRS console.For details about the supported DB types and versions, see Real-Time Disaster Recovery.During the DR initialization, do not perform ", "doc_type":"usermanual", "kw":"From MySQL to MySQL,DR Scenarios,User Guide", @@ -2484,10 +2841,10 @@ "uri":"drs_04_0123.html", "node_id":"drs_04_0123.xml", "product_code":"drs", - "code":"119", + "code":"136", "des":"You have logged in to the DRS console.For details about the supported DB types and versions, see Real-Time Disaster Recovery.During the DR initialization, do not perform ", "doc_type":"usermanual", - "kw":"From MySQL to GaussDB(for MySQL) Primary/Standby,DR Scenarios,User Guide", + "kw":"From MySQL to TaurusDB Cluster,DR Scenarios,User Guide", "search_title":"", "metedata":[ { @@ -2498,14 +2855,14 @@ "opensource":"true" } ], - "title":"From MySQL to GaussDB(for MySQL) Primary/Standby", + "title":"From MySQL to TaurusDB Cluster", "githuburl":"" }, { "uri":"drs_04_0125.html", "node_id":"drs_04_0125.xml", "product_code":"drs", - "code":"120", + "code":"137", "des":"You have logged in to the DRS console.For details about the supported DB types and versions, see Real-Time Disaster Recovery.During the DR initialization, do not perform ", "doc_type":"usermanual", "kw":"From Cassandra to Cassandra,DR Scenarios,User Guide", @@ -2526,7 +2883,7 @@ "uri":"drs_07_0007.html", "node_id":"drs_07_0007.xml", "product_code":"drs", - "code":"121", + "code":"138", "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 Management", @@ -2547,7 +2904,7 @@ "uri":"drs_02_0027.html", "node_id":"drs_02_0027.xml", "product_code":"drs", - "code":"122", + "code":"139", "des":"To prevent service unavailability caused by regional faults, DRS provides disaster recovery to ensure service continuity. If the region where the primary instance is loca", "doc_type":"usermanual", "kw":"DR instance,Step 1: Create a DR Task,Task Management,User Guide", @@ -2568,7 +2925,7 @@ "uri":"drs_02_0028.html", "node_id":"drs_02_0028.xml", "product_code":"drs", - "code":"123", + "code":"140", "des":"After a DR task starts, you can check the DR progress.You have logged in to the DRS console.A DR task has been created and started.On the Disaster Recovery Progress tab, ", "doc_type":"usermanual", "kw":"view the DR progress,Step 2: Query the DR Progress,Task Management,User Guide", @@ -2589,7 +2946,7 @@ "uri":"drs_02_0029.html", "node_id":"drs_02_0029.xml", "product_code":"drs", - "code":"124", + "code":"141", "des":"DR logs refer to the warning-, error-, and info-level logs generated during the DR process. This section describes how to view DR logs to locate and analyze database prob", "doc_type":"usermanual", "kw":"view DR logs,Step 3: View DR Logs,Task Management,User Guide", @@ -2610,7 +2967,7 @@ "uri":"drs_02_0033.html", "node_id":"drs_02_0033.xml", "product_code":"drs", - "code":"125", + "code":"142", "des":"DR item comparison: You can compare DR items to check data consistency between the service database and DR database. Currently, you can compare the following items during", "doc_type":"usermanual", "kw":"Step 4: Compare DR Items,Task Management,User Guide", @@ -2631,7 +2988,7 @@ "uri":"drs_07_0008.html", "node_id":"drs_07_0008.xml", "product_code":"drs", - "code":"126", + "code":"143", "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 Life Cycle", @@ -2652,7 +3009,7 @@ "uri":"drs_03_1134.html", "node_id":"drs_03_1134.xml", "product_code":"drs", - "code":"127", + "code":"144", "des":"After a DR task is created, you can modify task information to identify different tasks.The following task information can be edited:Task nameDescriptionTask start timeYo", "doc_type":"usermanual", "kw":"Editing Subscription Task Information,Task Life Cycle,User Guide", @@ -2673,7 +3030,7 @@ "uri":"drs_03_1138.html", "node_id":"drs_03_1138.xml", "product_code":"drs", - "code":"128", + "code":"145", "des":"A data DR task may fail due to the password change of the service or DR database. You need to update the information and then retry the DR task on the DRS console.You can", "doc_type":"usermanual", "kw":"Modifying Connection Information,Task Life Cycle,User Guide", @@ -2694,8 +3051,8 @@ "uri":"drs_03_0047.html", "node_id":"drs_03_0047.xml", "product_code":"drs", - "code":"129", - "des":"DRS allows you to change the flow control mode for a task. Currently, only the following DR tasks support this function.MySQL->MySQLMySQL -> GaussDB(for MySQL) primary/st", + "code":"146", + "des":"DRS allows you to change the flow control mode for a task. Currently, only the following DR tasks support this function.MySQL->MySQLMySQL -> TaurusDB ClusterYou have logg", "doc_type":"usermanual", "kw":"Modifying the Flow Control Mode,Task Life Cycle,User Guide", "search_title":"", @@ -2715,7 +3072,7 @@ "uri":"drs_03_0026.html", "node_id":"drs_03_0026.xml", "product_code":"drs", - "code":"130", + "code":"147", "des":"For a DR task that has been created but not started, DRS allows you to edit the configuration information of the task, including the source and destination database detai", "doc_type":"usermanual", "kw":"edit,Editing a DR Task,Task Life Cycle,User Guide", @@ -2736,7 +3093,7 @@ "uri":"drs_03_0027.html", "node_id":"drs_03_0027.xml", "product_code":"drs", - "code":"131", + "code":"148", "des":"A fault may occur during DR due to external factors, such as insufficient storage space.If a DR task fails due to non-network problems, the system will automatically resu", "doc_type":"usermanual", "kw":"Resuming a DR Task,Task Life Cycle,User Guide", @@ -2757,7 +3114,7 @@ "uri":"drs_03_0024.html", "node_id":"drs_03_0024.xml", "product_code":"drs", - "code":"132", + "code":"149", "des":"DRS monitors the DB instance performance and the migration progress. With the monitoring information, you can determine the data flow health status, data integrity, and d", "doc_type":"usermanual", "kw":"Viewing DR Metrics,Task Life Cycle,User Guide", @@ -2778,7 +3135,7 @@ "uri":"drs_03_1116.html", "node_id":"drs_03_1116.xml", "product_code":"drs", - "code":"133", + "code":"150", "des":"DRS supports primary/standby switchover for DR tasks. If both RPO and RTO are 0, data has been completely migrated to the DR database. Then, you can determine whether to ", "doc_type":"usermanual", "kw":"Performing a Primary/Standby Switchover for DR Tasks,Task Life Cycle,User Guide", @@ -2799,7 +3156,7 @@ "uri":"drs_03_0029.html", "node_id":"drs_03_0029.xml", "product_code":"drs", - "code":"134", + "code":"151", "des":"When the DR task is complete or no longer needed, you can stop the DR task. You can stop a task in any of the following statuses:CreatingConfigurationInitializingDisaster", "doc_type":"usermanual", "kw":"stop the DR task,Stopping a DR Task,Task Life Cycle,User Guide", @@ -2820,7 +3177,7 @@ "uri":"drs_03_0030.html", "node_id":"drs_03_0030.xml", "product_code":"drs", - "code":"135", + "code":"152", "des":"You can delete a DR task, when it is no longer needed Deleted tasks will no longer be displayed in the task list. Exercise caution when performing this operation.You have", "doc_type":"usermanual", "kw":"delete a DR task,Deleting a DR Task,Task Life Cycle,User Guide", @@ -2841,7 +3198,7 @@ "uri":"drs_02_0025.html", "node_id":"drs_02_0025.xml", "product_code":"drs", - "code":"136", + "code":"153", "des":"DR statuses indicate different DR phases.Table 1 lists DR task statuses and descriptions.If a task fails to be created, DRS retains the task for three days by default. Af", "doc_type":"usermanual", "kw":"DR task statuses,Task Statuses,Task Life Cycle,User Guide", @@ -2862,7 +3219,7 @@ "uri":"drs_disaster_tag.html", "node_id":"drs_disaster_tag.xml", "product_code":"drs", - "code":"137", + "code":"154", "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),Tag Management,Real-Time Disaster Recovery,User Guide", @@ -2883,7 +3240,7 @@ "uri":"drs_01_0099.html", "node_id":"drs_01_0099.xml", "product_code":"drs", - "code":"138", + "code":"155", "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", @@ -2904,7 +3261,7 @@ "uri":"drs_01_0103.html", "node_id":"drs_01_0103.xml", "product_code":"drs", - "code":"139", + "code":"156", "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", @@ -2925,7 +3282,7 @@ "uri":"drs_16_0103.html", "node_id":"drs_16_0103.xml", "product_code":"drs", - "code":"140", + "code":"157", "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center. Each ", "doc_type":"usermanual", "kw":"What Are Regions and AZs?,Product Consulting,User Guide", @@ -2946,7 +3303,7 @@ "uri":"drs_01_0100.html", "node_id":"drs_01_0100.xml", "product_code":"drs", - "code":"141", + "code":"158", "des":"DRS is a stable, efficient, and easy-to-use cloud service for database migration and synchronization in real time.It simplifies data migration processes and reduces migra", "doc_type":"usermanual", "kw":"DRS,What Is DRS?,Product Consulting,User Guide", @@ -2967,7 +3324,7 @@ "uri":"drs_01_0105.html", "node_id":"drs_01_0105.xml", "product_code":"drs", - "code":"142", + "code":"159", "des":"Yes. DRS provides high availability and can migrate a single RDS instance or RDS primary/standby instances. DRS can automatically rebuild the databases connection after a", "doc_type":"usermanual", "kw":"migrate a single RDS instance or RDS primary/standby instances,Can DRS Migrate RDS Primary/Standby I", @@ -2988,7 +3345,7 @@ "uri":"drs_04_0031.html", "node_id":"drs_04_0031.xml", "product_code":"drs", - "code":"143", + "code":"160", "des":"In database migration scenarios, if a migration task fails due to unavoidable problems (such as network fluctuation), DRS records the current parsing and replay point (wh", "doc_type":"usermanual", "kw":"Does DRS Support Resumable Uploads?,Product Consulting,User Guide", @@ -3009,7 +3366,7 @@ "uri":"drs_04_0087.html", "node_id":"drs_04_0087.xml", "product_code":"drs", - "code":"144", + "code":"161", "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 Real-Time Migration, Real-Time DR, and Real-Time Synchronization?,P", @@ -3030,7 +3387,7 @@ "uri":"drs_16_1133.html", "node_id":"drs_16_1133.xml", "product_code":"drs", - "code":"145", + "code":"162", "des":"In the full migration phase, DRS uses the row-level parallel migration mode to ensure migration performance and transmission stability. If the source database data is com", "doc_type":"usermanual", "kw":"How Do I Solve the Table Bloat Issue?,Product Consulting,User Guide", @@ -3051,7 +3408,7 @@ "uri":"drs_16_1142.html", "node_id":"drs_16_1142.xml", "product_code":"drs", - "code":"146", + "code":"163", "des":"RDS read replicas cannot be selected on the DRS console. You can select Self-built on ECS and enter the read replica IP address and port number to connect to the instance", "doc_type":"usermanual", "kw":"Why Cannot I Select RDS Read Replicas on the DRS Console?,Product Consulting,User Guide", @@ -3072,7 +3429,7 @@ "uri":"drs_16_1145.html", "node_id":"drs_16_1145.xml", "product_code":"drs", - "code":"147", + "code":"164", "des":"During the initialization of a full migration or synchronization task, DRS needs to query all inventory data in the source database. DRS uses simple SQL statements to que", "doc_type":"usermanual", "kw":"How Does DRS Affect the Source and Destination Databases?,Product Consulting,User Guide", @@ -3093,7 +3450,7 @@ "uri":"drs_01_0108.html", "node_id":"drs_01_0108.xml", "product_code":"drs", - "code":"148", + "code":"165", "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 and Security", @@ -3114,7 +3471,7 @@ "uri":"drs_01_0109.html", "node_id":"drs_01_0109.xml", "product_code":"drs", - "code":"149", + "code":"166", "des":"Uses security groups to ensure that the sources of access are trusted.Uses SSL channels to encrypt data during transmission.", "doc_type":"usermanual", "kw":"What Security Protection Policies Does DRS Have?,Network and Security,User Guide", @@ -3135,7 +3492,7 @@ "uri":"drs_01_0110.html", "node_id":"drs_01_0110.xml", "product_code":"drs", - "code":"150", + "code":"167", "des":"If the network is disconnected during the migration, you can view the task status first. If a full or incremental task fails, click Resume in the Operation column.Full mi", "doc_type":"usermanual", "kw":"What Can I Do If the Network Is Disconnected During the Migration?,Network and Security,User Guide", @@ -3156,7 +3513,7 @@ "uri":"drs_01_0112.html", "node_id":"drs_01_0112.xml", "product_code":"drs", - "code":"151", + "code":"168", "des":"By default, a VPC on the current cloud is isolated from external networks for security reasons. You cannot use an EIP outside a VPC (for example, an EIP of another cloud ", "doc_type":"usermanual", "kw":"How Can I Configure a VPC Security Group to Allow Traffic from an EIP?,Network and Security,User Gui", @@ -3177,7 +3534,7 @@ "uri":"drs_02_0100.html", "node_id":"drs_02_0100.xml", "product_code":"drs", - "code":"152", + "code":"169", "des":"Before data migration, ensure that network preparations and security rule settings are complete. If the connection is abnormal, check whether the network configuration is", "doc_type":"usermanual", "kw":"What Can I Do If the Network Connection Between the Replication Instance and Database Is Abnormal?,N", @@ -3198,7 +3555,7 @@ "uri":"drs_04_0040.html", "node_id":"drs_04_0040.xml", "product_code":"drs", - "code":"153", + "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":"Permissions Management", @@ -3219,7 +3576,7 @@ "uri":"drs_04_0034.html", "node_id":"drs_04_0034.xml", "product_code":"drs", - "code":"154", + "code":"171", "des":"DRS has certain permission requirements on accounts during migration, synchronization, and DR. This section describes the permission requirements on the MySQL engine.You ", "doc_type":"usermanual", "kw":"Which MySQL Permissions Are Required for DRS?,Permissions Management,User Guide", @@ -3240,7 +3597,7 @@ "uri":"drs_12_0001.html", "node_id":"drs_12_0001.xml", "product_code":"drs", - "code":"155", + "code":"172", "des":"mysql -h 'host' -u 'user' -p-N $@ -e \"SELECT CONCAT('SHOW GRANTS FOR ''', user, '''@''', host, ''';') AS query FROM mysql.user\" > /tmp/users.sqlhost indicates the IP add", "doc_type":"usermanual", "kw":"How Can I Import Users and Permissions from the Source to the Destination Database?,Permissions Mana", @@ -3261,7 +3618,7 @@ "uri":"drs_04_0025.html", "node_id":"drs_04_0025.xml", "product_code":"drs", - "code":"156", + "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":"Real-Time Migration", @@ -3282,7 +3639,7 @@ "uri":"drs_01_0104.html", "node_id":"drs_01_0104.xml", "product_code":"drs", - "code":"157", + "code":"174", "des":"You can refer to the following methods to check whether the task can be stopped. Before stopping the task, ensure that:At least one complete data comparison is performed ", "doc_type":"usermanual", "kw":"When Can I Stop a Migration Task?,Real-Time Migration,User Guide", @@ -3303,7 +3660,7 @@ "uri":"drs_16_0003.html", "node_id":"drs_16_0003.xml", "product_code":"drs", - "code":"158", + "code":"175", "des":"Definer is used in views, stored procedures, triggers, and events. Definer does not restrict the permission to invoke objects, instead the permission to access the databa", "doc_type":"usermanual", "kw":"How Do I Maintain the Original Service User Permission System After Definer Is Forcibly Converted Du", @@ -3324,7 +3681,7 @@ "uri":"drs_16_0121.html", "node_id":"drs_16_0121.xml", "product_code":"drs", - "code":"159", + "code":"176", "des":"After the MySQL stored procedure is migrated to the cloud, an error may occur when the stored procedure or function is invoked due to permission problems.The method varie", "doc_type":"usermanual", "kw":"What Can I Do If the Invoking Permission Problem Occurs After the MySQL Stored Procedure Is Migrated", @@ -3345,7 +3702,7 @@ "uri":"drs_04_0020.html", "node_id":"drs_04_0020.xml", "product_code":"drs", - "code":"160", + "code":"177", "des":"To ensure that all services on the database are stopped, perform the following steps:", "doc_type":"usermanual", "kw":"How Do I Ensure that All Services on the Database Are Stopped?,Real-Time Migration,User Guide", @@ -3366,7 +3723,7 @@ "uri":"drs_16_0123.html", "node_id":"drs_16_0123.xml", "product_code":"drs", - "code":"161", + "code":"178", "des":"When you use a subaccount to use scheduled task startup function, the account entrustment function must be used. Otherwise, the scheduled task fails to be started, leavin", "doc_type":"usermanual", "kw":"Security Administrator,What Can I Do When Scheduled Task Failed to Start Leaving Message \"can not ge", @@ -3387,7 +3744,7 @@ "uri":"drs_04_0032.html", "node_id":"drs_04_0032.xml", "product_code":"drs", - "code":"162", + "code":"179", "des":"Currently, RDS for MySQL does not support the MyISAM engine due to the following reasons.MyISAM engine tables do not support transactions and support only table-level loc", "doc_type":"usermanual", "kw":"What Can I Do If MyISAM Tables Are Not Supported by RDS for MySQL?,Real-Time Migration,User Guide", @@ -3408,7 +3765,7 @@ "uri":"drs_04_0030.html", "node_id":"drs_04_0030.xml", "product_code":"drs", - "code":"163", + "code":"180", "des":"Based on MySQL 5.7, some new features have been added to MySQL 8.0. There are performance differences between the two versions. Before migration, you need to analyze comp", "doc_type":"usermanual", "kw":"What Are the Precautions for Migrating Data from an Earlier Version MySQL to MySQL 8.0?,Real-Time Mi", @@ -3429,7 +3786,7 @@ "uri":"drs_15_0100.html", "node_id":"drs_15_0100.xml", "product_code":"drs", - "code":"164", + "code":"181", "des":"Out of memory (OOM) occurs during the migration from MongoDB to DDS, causing migration failures.The possible causes are as follows:If the mongod service of the source dat", "doc_type":"usermanual", "kw":"What Can I Do When OOM Occurs During the Migration from MongoDB to DDS?,Real-Time Migration,User Gui", @@ -3450,7 +3807,7 @@ "uri":"drs_16_0001.html", "node_id":"drs_16_0001.xml", "product_code":"drs", - "code":"165", + "code":"182", "des":"Before using the DRS service to migrate collections between sharded clusters, you must disable the balancer of the collections to be migrated.After the migration is compl", "doc_type":"usermanual", "kw":"How Do I Disable the Balancer?,Real-Time Migration,User Guide", @@ -3471,7 +3828,7 @@ "uri":"drs_14_0006.html", "node_id":"drs_14_0006.xml", "product_code":"drs", - "code":"166", + "code":"183", "des":"During the MySQL to MySQL migration, if the migration log indicates that the migration of events and triggers fails after the migration task is complete, you can manually", "doc_type":"usermanual", "kw":"How Do I Export and Import Events and Triggers in Batches?,Real-Time Migration,User Guide", @@ -3492,7 +3849,7 @@ "uri":"drs_14_0002.html", "node_id":"drs_14_0002.xml", "product_code":"drs", - "code":"167", + "code":"184", "des":"When the value of source database parameter lower_case_table_names is set to 1, the databases or tables whose names contain uppercase letters cannot be migrated.When the ", "doc_type":"usermanual", "kw":"How Can I Migrate Databases or Tables Whose Names Contain Uppercase Letters?,Real-Time Migration,Use", @@ -3513,7 +3870,7 @@ "uri":"drs_09_0101.html", "node_id":"drs_09_0101.xml", "product_code":"drs", - "code":"168", + "code":"185", "des":"In a sharded cluster, orphaned documents are those documents on a shard that also exist in chunks on other shards as a result of failed migrations or incomplete migration", "doc_type":"usermanual", "kw":"How Do I Delete Orphaned Documents in MongoDB Sharded Clusters?,Real-Time Migration,User Guide", @@ -3534,7 +3891,7 @@ "uri":"drs_04_0457.html", "node_id":"drs_04_0457.xml", "product_code":"drs", - "code":"169", + "code":"186", "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 Migration", @@ -3555,7 +3912,7 @@ "uri":"drs_04_0041.html", "node_id":"drs_04_0041.xml", "product_code":"drs", - "code":"170", + "code":"187", "des":"During the backup migration, If Last Backup File is selected by mistake, perform either of the following operations:If you select Yes by mistake, the database receives a ", "doc_type":"usermanual", "kw":"What Should I Do If the Last Backup File Is Incorrectly Selected in the Backup Migration Scenario?,B", @@ -3576,7 +3933,7 @@ "uri":"drs_04_0458.html", "node_id":"drs_04_0458.xml", "product_code":"drs", - "code":"171", + "code":"188", "des":"After data is migrated from the local host or VMs to the RDS SQL Server DB instance on the current cloud through DRS, the Login accounts, DBLink, AgentJobs, and key confi", "doc_type":"usermanual", "kw":"Manual Configuration,Backup Migration,User Guide", @@ -3597,7 +3954,7 @@ "uri":"drs_04_0026.html", "node_id":"drs_04_0026.xml", "product_code":"drs", - "code":"172", + "code":"189", "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":"Real-Time Synchronization", @@ -3618,7 +3975,7 @@ "uri":"drs_16_0101.html", "node_id":"drs_16_0101.xml", "product_code":"drs", - "code":"173", + "code":"190", "des":"DRS can directly synchronize tables of different schemas to those of the same schema if the tables do not conflict with each other.", "doc_type":"usermanual", "kw":"Can DRS Sync Tables of Different Schemas to the Same Schema?,Real-Time Synchronization,User Guide", @@ -3639,7 +3996,7 @@ "uri":"drs_16_1124.html", "node_id":"drs_16_1124.xml", "product_code":"drs", - "code":"174", + "code":"191", "des":"During table-level incremental synchronization from MySQL to MySQL, you can use Online DDL tools to add or delete columns. Pay attention to the following when using Onlin", "doc_type":"usermanual", "kw":"Can Online DDL Tools Be Used for Real-time Synchronization?,Real-Time Synchronization,User Guide", @@ -3660,7 +4017,7 @@ "uri":"drs_16_1151.html", "node_id":"drs_16_1151.xml", "product_code":"drs", - "code":"175", + "code":"192", "des":"If the source Oracle database is an RAC cluster, you are advised to use SCAN IP+SERVICE_NAMES to create a task because SCAN IP has stronger fault tolerance, better load b", "doc_type":"usermanual", "kw":"Why Do I Use the SCAN IP Address to Connect to an Oracle RAC Cluster?,Real-Time Synchronization,User", @@ -3681,7 +4038,7 @@ "uri":"drs_16_1155.html", "node_id":"drs_16_1155.xml", "product_code":"drs", - "code":"176", + "code":"193", "des":"In physical standby mode, the Oracle database directly replicates logs from the primary database and does not generate any logs. If the source is an Oracle database, you ", "doc_type":"usermanual", "kw":"How Do I Check Supplemental Logging of the Source Oracle Database?,Real-Time Synchronization,User Gu", @@ -3702,7 +4059,7 @@ "uri":"drs_04_0028.html", "node_id":"drs_04_0028.xml", "product_code":"drs", - "code":"177", + "code":"194", "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":"Real-Time Disaster Recovery", @@ -3723,7 +4080,7 @@ "uri":"drs_04_0033.html", "node_id":"drs_04_0033.xml", "product_code":"drs", - "code":"178", + "code":"195", "des":"Recovery Point Objective (RPO) refers to the difference between the time when a transaction in the current service database is submitted and the time when the transaction", "doc_type":"usermanual", "kw":"What Are RPO and RTO of DRS Disaster Recovery?,Real-Time Disaster Recovery,User Guide", @@ -3744,7 +4101,7 @@ "uri":"drs_16_1125.html", "node_id":"drs_16_1125.xml", "product_code":"drs", - "code":"179", + "code":"196", "des":"For real-time DR tasks, if the service database is faulty, manually perform a primary/standby switchover. For details, see Performing a Primary/Standby Switchover for DR ", "doc_type":"usermanual", "kw":"Is a Primary/Standby Switchover Triggered Automatically or Manually for DR Tasks?,Real-Time Disaster", @@ -3765,7 +4122,7 @@ "uri":"drs_16_1126.html", "node_id":"drs_16_1126.xml", "product_code":"drs", - "code":"180", + "code":"197", "des":"Real-time DR is performed by instance. You cannot select a specified database, but you can select tables or databases for real-time migration and synchronization task.", "doc_type":"usermanual", "kw":"Can Real-Time DR Be Performed for Specified Databases?,Real-Time Disaster Recovery,User Guide", @@ -3786,7 +4143,7 @@ "uri":"drs_14_0001.html", "node_id":"drs_14_0001.xml", "product_code":"drs", - "code":"181", + "code":"198", "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-Level Comparison", @@ -3807,7 +4164,7 @@ "uri":"drs_16_1130.html", "node_id":"drs_16_1130.xml", "product_code":"drs", - "code":"182", + "code":"199", "des":"DRS's data comparison allows you to check whether the data in the source database is the same as that in the destination database.DRS does not support value comparison fo", "doc_type":"usermanual", "kw":"Which of the Following Data Types Are Not Supported By Value Comparison?,Data-Level Comparison,User ", @@ -3828,7 +4185,7 @@ "uri":"drs_16_1161.html", "node_id":"drs_16_1161.xml", "product_code":"drs", - "code":"183", + "code":"200", "des":"Object comparison: System tables of the source and destination databases are queried, occupying about 10 sessions. The database is not affected. However, if there are a l", "doc_type":"usermanual", "kw":"What Impact Does a DRS Comparison Task Have on Databases?,Data-Level Comparison,User Guide", @@ -3849,7 +4206,7 @@ "uri":"drs_16_1162.html", "node_id":"drs_16_1162.xml", "product_code":"drs", - "code":"184", + "code":"201", "des":"Object comparison: Generally, the comparison results are returned within several minutes based on the query performance of the source database. If the amount of data is l", "doc_type":"usermanual", "kw":"How Long Does a DRS Comparison Task Take?,Data-Level Comparison,User Guide", @@ -3870,7 +4227,7 @@ "uri":"drs_04_0029.html", "node_id":"drs_04_0029.xml", "product_code":"drs", - "code":"185", + "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":"General Operations", @@ -3891,7 +4248,7 @@ "uri":"drs_15_0120.html", "node_id":"drs_15_0120.xml", "product_code":"drs", - "code":"186", + "code":"203", "des":"Information often overlaps when you decrease the size of the page. You are advised to set the page scale at 100%.", "doc_type":"usermanual", "kw":"What Can I Do When Information Overlaps on the DRS Console?,General Operations,User Guide", @@ -3912,7 +4269,7 @@ "uri":"drs_04_0021.html", "node_id":"drs_04_0021.xml", "product_code":"drs", - "code":"187", + "code":"204", "des":"During the migration, the destination instance can be set to read-only or read/write.Read-only: During the migration, the destination instance is read-only. After the mig", "doc_type":"usermanual", "kw":"Is the Destination Instance Set to Read-only or Read/Write?,General Operations,User Guide", @@ -3933,7 +4290,7 @@ "uri":"drs_16_0002.html", "node_id":"drs_16_0002.xml", "product_code":"drs", - "code":"188", + "code":"205", "des":"During migration for MySQL databases, the source database binlog must be in the ROW format. Otherwise, the task fails. After binlog_format=ROW at the global level is set ", "doc_type":"usermanual", "kw":"How Do I Set Global binlog_format=ROW to Take Effect Immediately?,General Operations,User Guide", @@ -3954,7 +4311,7 @@ "uri":"drs_16_0010.html", "node_id":"drs_16_0010.xml", "product_code":"drs", - "code":"189", + "code":"206", "des":"When migrating MySQL databases, ensure that the binlog_row_image parameter of the source database is set to FULL. Otherwise, the migration task will fail. After binlog_ro", "doc_type":"usermanual", "kw":"How Do I Set binlog_row_image=FULL to Take Effect Immediately?,General Operations,User Guide", @@ -3975,7 +4332,7 @@ "uri":"drs_14_0004.html", "node_id":"drs_14_0004.xml", "product_code":"drs", - "code":"190", + "code":"207", "des":"When you set the password for the migration account in the destination database, you need to set the password based on the password strength requirements of the destinati", "doc_type":"usermanual", "kw":"How Do I Change the Destination Database Password to Meet the Password Policy?,General Operations,Us", @@ -3996,7 +4353,7 @@ "uri":"drs_14_0003.html", "node_id":"drs_14_0003.xml", "product_code":"drs", - "code":"191", + "code":"208", "des":"MongoDB shards data at the collection level, distributing the collection data using shard keys.You choose the shard key when sharding a collection. Each record contains a", "doc_type":"usermanual", "kw":"How Do I Configure the Shard Key for a MongoDB Sharded Cluster?,General Operations,User Guide", @@ -4017,7 +4374,7 @@ "uri":"drs_16_0102.html", "node_id":"drs_16_0102.xml", "product_code":"drs", - "code":"192", + "code":"209", "des":"When the cloud connection bandwidth is expanded, the bandwidth link needs to be re-established and the network is disconnected. Whether the network disconnection affects ", "doc_type":"usermanual", "kw":"Does Bandwidth Expansion Affect the Running DRS Tasks?,General Operations,User Guide", @@ -4038,7 +4395,7 @@ "uri":"drs_16_0122.html", "node_id":"drs_16_0122.xml", "product_code":"drs", - "code":"193", + "code":"210", "des":"In some MariaDB versions, the SysDB database is used as a system database (similar to the sys database of MySQL 5.7). Therefore, DRS considers the SysDB database as the s", "doc_type":"usermanual", "kw":"Why Data in MariaDB and SysDB Cannot Be Migrated?,General Operations,User Guide", @@ -4059,7 +4416,7 @@ "uri":"drs_16_0120.html", "node_id":"drs_16_0120.xml", "product_code":"drs", - "code":"194", + "code":"211", "des":"DRS supports many-to-one scenarios during migration of different types of instances and tables to suit your service requirements.To ensure that there is sufficient space ", "doc_type":"usermanual", "kw":"Constraints and Operation Suggestions on Many-to-One Scenario,General Operations,User Guide", @@ -4080,7 +4437,7 @@ "uri":"drs_01_0101.html", "node_id":"drs_01_0101.xml", "product_code":"drs", - "code":"195", + "code":"212", "des":"You can view DRS operation logs on the Cloud Trace Service (CTS) console.Click the username in the upper right corner and select Operation Log from the drop-down list.", "doc_type":"usermanual", "kw":"DRS,Where Can I View DRS Operation Logs?,General Operations,User Guide", @@ -4101,7 +4458,7 @@ "uri":"drs_16_1140.html", "node_id":"drs_16_1140.xml", "product_code":"drs", - "code":"196", + "code":"213", "des":"No. DRS cannot restart a completed task.", "doc_type":"usermanual", "kw":"Can a Completed Task Be Restarted?,General Operations,User Guide", @@ -4122,7 +4479,7 @@ "uri":"drs_16_1143.html", "node_id":"drs_16_1143.xml", "product_code":"drs", - "code":"197", + "code":"214", "des":"You can reset a task when the task is suspended or fails. Resetting a task does not clear the destination database. You can determine whether to clear the destination dat", "doc_type":"usermanual", "kw":"What Are the Differences Between Resetting a Task and Recreating a Task?,General Operations,User Gui", @@ -4143,7 +4500,7 @@ "uri":"drs_16_1156.html", "node_id":"drs_16_1156.xml", "product_code":"drs", - "code":"198", + "code":"215", "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":"Delay", @@ -4164,7 +4521,7 @@ "uri":"drs_16_1148.html", "node_id":"drs_16_1148.xml", "product_code":"drs", - "code":"199", + "code":"216", "des":"Recovery Time Objective (RTO) is duration of time within which transactions on the DRS instance are transmitted and replayed to the destination database during incrementa", "doc_type":"usermanual", "kw":"Why Does the Delay of DR Tasks Increase?,Delay,User Guide", @@ -4185,7 +4542,7 @@ "uri":"drs_16_1157.html", "node_id":"drs_16_1157.xml", "product_code":"drs", - "code":"200", + "code":"217", "des":"Migration from MongoDB to DDSMigration from DDS to MongoDBTo ensure the performance of migration, synchronization, or disaster recovery, DRS performs concurrent replay at", "doc_type":"usermanual", "kw":"Why Is the Delay High In Migration from MongoDB to DDS?,Delay,User Guide", @@ -4206,7 +4563,7 @@ "uri":"drs_13_0001.html", "node_id":"drs_13_0001.xml", "product_code":"drs", - "code":"201", + "code":"218", "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":"Troubleshooting", @@ -4227,7 +4584,7 @@ "uri":"drs_11_0001.html", "node_id":"drs_11_0001.xml", "product_code":"drs", - "code":"202", + "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":"Solutions to Failed Check Items", @@ -4248,7 +4605,7 @@ "uri":"drs_12_0005.html", "node_id":"drs_12_0005.xml", "product_code":"drs", - "code":"203", + "code":"220", "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":"Disk Space", @@ -4269,7 +4626,7 @@ "uri":"drs_11_0010.html", "node_id":"drs_11_0010.xml", "product_code":"drs", - "code":"204", + "code":"221", "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":"Checking Whether the Destination Database Has Sufficient Storage Space,Disk Space,User Guide", @@ -4290,7 +4647,7 @@ "uri":"drs_11_0076.html", "node_id":"drs_11_0076.xml", "product_code":"drs", - "code":"205", + "code":"222", "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":"Checking Whether the Destination Server Has Sufficient Storage Space,Disk Space,User Guide", @@ -4311,7 +4668,7 @@ "uri":"drs_12_0008.html", "node_id":"drs_12_0008.xml", "product_code":"drs", - "code":"206", + "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":"Database Parameters", @@ -4332,7 +4689,7 @@ "uri":"drs_11_0014.html", "node_id":"drs_11_0014.xml", "product_code":"drs", - "code":"207", + "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":"source database binlog,Checking Whether the Source Database Binlog Is Enabled,Database Parameters,Us", @@ -4353,7 +4710,7 @@ "uri":"drs_11_0015.html", "node_id":"drs_11_0015.xml", "product_code":"drs", - "code":"208", + "code":"225", "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":"source database binlog,Checking Whether the Source Database Binlog Is Row-Based,Database Parameters,", @@ -4374,7 +4731,7 @@ "uri":"drs_11_0016.html", "node_id":"drs_11_0016.xml", "product_code":"drs", - "code":"209", + "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":"binlog retention period,Checking Whether the Binlog Retention Period Is Set on the Source Database,D", @@ -4395,7 +4752,7 @@ "uri":"drs_11_0013.html", "node_id":"drs_11_0013.xml", "product_code":"drs", - "code":"210", + "code":"227", "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":"Checking Whether the Source and Destination Database Character Sets Are Consistent,Database Paramete", @@ -4416,7 +4773,7 @@ "uri":"drs_11_0018.html", "node_id":"drs_11_0018.xml", "product_code":"drs", - "code":"211", + "code":"228", "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":"Checking Whether the Source Database server_id Meets the Incremental Migration Requirements,Database", @@ -4437,7 +4794,7 @@ "uri":"drs_11_0019.html", "node_id":"drs_11_0019.xml", "product_code":"drs", - "code":"212", + "code":"229", "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":"case sensitivity,Checking Whether the Source and Destination Database Table Names Are Consistent in ", @@ -4458,7 +4815,7 @@ "uri":"drs_11_0022.html", "node_id":"drs_11_0022.xml", "product_code":"drs", - "code":"213", + "code":"230", "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":"Checking Whether the Source Database Contains Object Names with Non-ASCII Characters,Database Parame", @@ -4479,7 +4836,7 @@ "uri":"drs_11_0023.html", "node_id":"drs_11_0023.xml", "product_code":"drs", - "code":"214", + "code":"231", "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":"Checking Whether the TIME_ZONE Values of the Source and Destination Databases Are the Same,Database ", @@ -4500,7 +4857,7 @@ "uri":"drs_11_0024.html", "node_id":"drs_11_0024.xml", "product_code":"drs", - "code":"215", + "code":"232", "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":"Checking Whether the COLLATION_SERVER Values of the Source and Destination Databases Are the Same,Da", @@ -4521,7 +4878,7 @@ "uri":"drs_11_0025.html", "node_id":"drs_11_0025.xml", "product_code":"drs", - "code":"216", + "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":"Checking Whether the SERVER_UUID Values of the Source and Destination Databases Are the Same,Databas", @@ -4542,7 +4899,7 @@ "uri":"drs_11_0044.html", "node_id":"drs_11_0044.xml", "product_code":"drs", - "code":"217", + "code":"234", "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":"Checking Whether the SERVER_ID Values of the Source and Destination Databases Are Different,Database", @@ -4563,7 +4920,7 @@ "uri":"drs_11_0049.html", "node_id":"drs_11_0049.xml", "product_code":"drs", - "code":"218", + "code":"235", "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":"Checking Whether the Source Database Contains Invalid sql_mode Values,Database Parameters,User Guide", @@ -4584,7 +4941,7 @@ "uri":"drs_11_0059.html", "node_id":"drs_11_0059.xml", "product_code":"drs", - "code":"219", + "code":"236", "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":"Checking Whether the SQL_MODE Values of the Source and Destination Databases Are the Same,Database P", @@ -4605,7 +4962,7 @@ "uri":"drs_11_0228.html", "node_id":"drs_11_0228.xml", "product_code":"drs", - "code":"220", + "code":"237", "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":"Checking Whether the sql_mode Value in the Destination Database Is Not NO_ENGINE_SUBSTITUTION,Databa", @@ -4626,7 +4983,7 @@ "uri":"drs_11_0060.html", "node_id":"drs_11_0060.xml", "product_code":"drs", - "code":"221", + "code":"238", "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":"Checking Whether the innodb_strict_mode Values of the Source and Destination Databases Are the Same,", @@ -4647,7 +5004,7 @@ "uri":"drs_11_0053.html", "node_id":"drs_11_0053.xml", "product_code":"drs", - "code":"222", + "code":"239", "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":"Checking Whether the max_wal_senders Value of the Source Database Is Correctly Configured,Database P", @@ -4668,7 +5025,7 @@ "uri":"drs_11_0054.html", "node_id":"drs_11_0054.xml", "product_code":"drs", - "code":"223", + "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":"Checking Whether the WAL_LEVEL Value in the Source Database Is Correct,Database Parameters,User Guid", @@ -4689,7 +5046,7 @@ "uri":"drs_11_0055.html", "node_id":"drs_11_0055.xml", "product_code":"drs", - "code":"224", + "code":"241", "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":"Checking Whether the MAX_REPLICATION_SLOTS Value in the Source Database Is Correct,Database Paramete", @@ -4710,7 +5067,7 @@ "uri":"drs_11_0056.html", "node_id":"drs_11_0056.xml", "product_code":"drs", - "code":"225", + "code":"242", "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":"Checking Whether the Source Database Is on Standby,Database Parameters,User Guide", @@ -4731,7 +5088,7 @@ "uri":"drs_11_0061.html", "node_id":"drs_11_0061.xml", "product_code":"drs", - "code":"226", + "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":"Checking Whether the log_slave_updates Value of the Source Database Is Correctly Configured,Database", @@ -4752,7 +5109,7 @@ "uri":"drs_11_0063.html", "node_id":"drs_11_0063.xml", "product_code":"drs", - "code":"227", + "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":"Checking Whether the BLOCK_SIZE Value of the Source Database Is the Same as That of the Destination ", @@ -4773,7 +5130,7 @@ "uri":"drs_11_0064.html", "node_id":"drs_11_0064.xml", "product_code":"drs", - "code":"228", + "code":"245", "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":"Checking Whether the binlog_row_image Value is FULL,Database Parameters,User Guide", @@ -4794,7 +5151,7 @@ "uri":"drs_11_0453.html", "node_id":"drs_11_0453.xml", "product_code":"drs", - "code":"229", + "code":"246", "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":"Checking Whether the Transaction Isolation Levels are Consistent,Database Parameters,User Guide", @@ -4815,7 +5172,7 @@ "uri":"drs_11_0038.html", "node_id":"drs_11_0038.xml", "product_code":"drs", - "code":"230", + "code":"247", "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":"Checking Whether the lc_monetary Values of the Source and Destination Databases Are the Same,Databas", @@ -4836,7 +5193,7 @@ "uri":"drs_11_0073.html", "node_id":"drs_11_0073.xml", "product_code":"drs", - "code":"231", + "code":"248", "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":"Checking Whether the Source Database Contains Trigger Names with Non-ASCII Characters,Database Param", @@ -4857,7 +5214,7 @@ "uri":"drs_11_0200.html", "node_id":"drs_11_0200.xml", "product_code":"drs", - "code":"232", + "code":"249", "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":"Checking Whether the Source Database Collections Contain More Than 10 Indexes,Database Parameters,Us", @@ -4878,7 +5235,7 @@ "uri":"drs_11_0227.html", "node_id":"drs_11_0227.xml", "product_code":"drs", - "code":"233", + "code":"250", "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":"Checking Whether log_bin_trust_function_creators Is Set to On in Both the Source and Destination Dat", @@ -4895,11 +5252,32 @@ "title":"Checking Whether log_bin_trust_function_creators Is Set to On in Both the Source and Destination Databases", "githuburl":"" }, + { + "uri":"drs_11_0226.html", + "node_id":"drs_11_0226.xml", + "product_code":"drs", + "code":"251", + "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":"Checking Whether GTID Is Enabled for the Source Database,Database Parameters,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"drs", + "documenttype":"usermanual", + "IsBot":"No;Yes", + "IsMulti":"No;Yes", + "opensource":"true" + } + ], + "title":"Checking Whether GTID Is Enabled for the Source Database", + "githuburl":"" + }, { "uri":"drs_11_0225.html", "node_id":"drs_11_0225.xml", "product_code":"drs", - "code":"234", + "code":"252", "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":"Checking Whether log_bin_trust_function_creators Is Set to On in the Destination Database,Database P", @@ -4920,7 +5298,7 @@ "uri":"drs_15_0017.html", "node_id":"drs_15_0017.xml", "product_code":"drs", - "code":"235", + "code":"253", "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":"Checking Whether the max_allowed_packet Value of the Destination Database Is too Small,Database Para", @@ -4941,7 +5319,7 @@ "uri":"drs_03_043.html", "node_id":"drs_03_043.xml", "product_code":"drs", - "code":"236", + "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":"Checking Whether the Source Database Character Set Is Supported,Database Parameters,User Guide", @@ -4962,7 +5340,7 @@ "uri":"drs_03_045.html", "node_id":"drs_03_045.xml", "product_code":"drs", - "code":"237", + "code":"255", "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":"Checking Whether the Databases and Tables Exist,Database Parameters,User Guide", @@ -4983,7 +5361,7 @@ "uri":"drs_03_1130.html", "node_id":"drs_03_1130.xml", "product_code":"drs", - "code":"238", + "code":"256", "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":"Checking Whether session_replication_role of the Destination Database Is correctly Set,Database Para", @@ -5004,7 +5382,7 @@ "uri":"drs_11_0066.html", "node_id":"drs_11_0066.xml", "product_code":"drs", - "code":"239", + "code":"257", "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":"Checking Whether the MongoDB Instance Type Matches the Migration Mode,Database Parameters,User Guide", @@ -5025,7 +5403,7 @@ "uri":"drs_11_0465.html", "node_id":"drs_11_0465.xml", "product_code":"drs", - "code":"240", + "code":"258", "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":"Checking the Physical Standby Database,Database Parameters,User Guide", @@ -5046,7 +5424,7 @@ "uri":"drs_11_0469.html", "node_id":"drs_11_0469.xml", "product_code":"drs", - "code":"241", + "code":"259", "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":"Checking Whether the Values of group_concat_max_len Are Consistent,Database Parameters,User Guide", @@ -5067,7 +5445,7 @@ "uri":"drs_11_0471.html", "node_id":"drs_11_0471.xml", "product_code":"drs", - "code":"242", + "code":"260", "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":"Checking Whether the Character Sets Are Compatible,Database Parameters,User Guide", @@ -5088,7 +5466,7 @@ "uri":"drs_11_0481.html", "node_id":"drs_11_0481.xml", "product_code":"drs", - "code":"243", + "code":"261", "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":"Checking Whether the Source Database Contains Unsupported Table Field Types,Database Parameters,User", @@ -5109,7 +5487,7 @@ "uri":"drs_11_0482.html", "node_id":"drs_11_0482.xml", "product_code":"drs", - "code":"244", + "code":"262", "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":"Checking Replication Attribute of Primary Key Columns,Database Parameters,User Guide", @@ -5130,7 +5508,7 @@ "uri":"drs_11_0464.html", "node_id":"drs_11_0464.xml", "product_code":"drs", - "code":"245", + "code":"263", "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":"Source DB Instance Statuses", @@ -5151,7 +5529,7 @@ "uri":"drs_11_0046.html", "node_id":"drs_11_0046.xml", "product_code":"drs", - "code":"246", + "code":"264", "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":"Checking Whether the Source and Destination Databases Are of the Same Type,Source DB Instance Status", @@ -5172,7 +5550,7 @@ "uri":"drs_11_0463.html", "node_id":"drs_11_0463.xml", "product_code":"drs", - "code":"247", + "code":"265", "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":"Checking Whether the ChangeStream API of the source DB instance is available,Source DB Instance Stat", @@ -5193,7 +5571,7 @@ "uri":"drs_12_0006.html", "node_id":"drs_12_0006.xml", "product_code":"drs", - "code":"248", + "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":"Destination DB Instance Statuses", @@ -5214,7 +5592,7 @@ "uri":"drs_11_0011.html", "node_id":"drs_11_0011.xml", "product_code":"drs", - "code":"249", + "code":"267", "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":"Checking Whether the Destination Database Is Involved in Another Migration Task,Destination DB Insta", @@ -5235,7 +5613,7 @@ "uri":"drs_11_0050.html", "node_id":"drs_11_0050.xml", "product_code":"drs", - "code":"250", + "code":"268", "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":"Checking Whether the Destination Database Has a Read Replica,Destination DB Instance Statuses,User G", @@ -5256,7 +5634,7 @@ "uri":"drs_11_0041.html", "node_id":"drs_11_0041.xml", "product_code":"drs", - "code":"251", + "code":"269", "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":"Checking Whether the Extensions Are Supported,Destination DB Instance Statuses,User Guide", @@ -5277,7 +5655,7 @@ "uri":"drs_11_0075.html", "node_id":"drs_11_0075.xml", "product_code":"drs", - "code":"252", + "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":"Checking Whether Destination Contains the Configured Database,Destination DB Instance Statuses,User ", @@ -5298,7 +5676,7 @@ "uri":"drs_11_0230.html", "node_id":"drs_11_0230.xml", "product_code":"drs", - "code":"253", + "code":"271", "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":"Checking Whether the Destination DB Instance Is Available,Destination DB Instance Statuses,User Guid", @@ -5319,7 +5697,7 @@ "uri":"drs_12_0007.html", "node_id":"drs_12_0007.xml", "product_code":"drs", - "code":"254", + "code":"272", "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 User Permissions", @@ -5340,7 +5718,7 @@ "uri":"drs_11_0009.html", "node_id":"drs_11_0009.xml", "product_code":"drs", - "code":"255", + "code":"273", "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":"source database user,Checking Whether the Source Database User Has Sufficient Permissions,Database U", @@ -5361,7 +5739,7 @@ "uri":"drs_11_0008.html", "node_id":"drs_11_0008.xml", "product_code":"drs", - "code":"256", + "code":"274", "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":"destination database user,Checking Whether the Destination Database User Has Sufficient Permissions,", @@ -5382,7 +5760,7 @@ "uri":"drs_12_0004.html", "node_id":"drs_12_0004.xml", "product_code":"drs", - "code":"257", + "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":"Database Versions", @@ -5403,7 +5781,7 @@ "uri":"drs_11_0005.html", "node_id":"drs_11_0005.xml", "product_code":"drs", - "code":"258", + "code":"276", "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":"source database version,Checking Whether the Source Database Version Is Supported,Database Versions,", @@ -5424,7 +5802,7 @@ "uri":"drs_11_0006.html", "node_id":"drs_11_0006.xml", "product_code":"drs", - "code":"259", + "code":"277", "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":"destination database version,Checking Whether the Destination Database Version Is Supported,Database", @@ -5445,7 +5823,7 @@ "uri":"drs_11_0007.html", "node_id":"drs_11_0007.xml", "product_code":"drs", - "code":"260", + "code":"278", "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":"Checking Whether the Migration Is from an Earlier Database Version to the Same or a Later Version,Da", @@ -5466,7 +5844,7 @@ "uri":"drs_12_0003.html", "node_id":"drs_12_0003.xml", "product_code":"drs", - "code":"261", + "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":"Networks", @@ -5487,7 +5865,7 @@ "uri":"drs_precheck.html", "node_id":"drs_precheck.xml", "product_code":"drs", - "code":"262", + "code":"280", "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":"Checking Whether the Source Database Is Connected,Networks,User Guide", @@ -5508,7 +5886,7 @@ "uri":"drs_11_0002.html", "node_id":"drs_11_0002.xml", "product_code":"drs", - "code":"263", + "code":"281", "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":"Checking Whether the Destination Database Is Connected,Networks,User Guide", @@ -5529,7 +5907,7 @@ "uri":"drs_11_0003.html", "node_id":"drs_11_0003.xml", "product_code":"drs", - "code":"264", + "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":"Checking Whether the Destination Database Can Connect to the Source Database,Networks,User Guide", @@ -5550,7 +5928,7 @@ "uri":"drs_11_0067.html", "node_id":"drs_11_0067.xml", "product_code":"drs", - "code":"265", + "code":"283", "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 Objects", @@ -5571,7 +5949,7 @@ "uri":"drs_11_0048.html", "node_id":"drs_11_0048.xml", "product_code":"drs", - "code":"266", + "code":"284", "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":"Checking Whether the Source Database Contains a MyISAM Table,Database Objects,User Guide", @@ -5592,7 +5970,7 @@ "uri":"drs_11_0080.html", "node_id":"drs_11_0080.xml", "product_code":"drs", - "code":"267", + "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":"Checking Whether the Source Database Contains the Functions or Stored Procedures that the Source Dat", @@ -5613,7 +5991,7 @@ "uri":"drs_11_0117.html", "node_id":"drs_11_0117.xml", "product_code":"drs", - "code":"268", + "code":"286", "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":"Checking Whether the Source Database Tables Use Storage Engines Not Supported by the Destination Dat", @@ -5634,7 +6012,7 @@ "uri":"drs_15_0020.html", "node_id":"drs_15_0020.xml", "product_code":"drs", - "code":"269", + "code":"287", "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":"Checking Whether the Source Database Tables Contain Primary Keys,Database Objects,User Guide", @@ -5655,7 +6033,7 @@ "uri":"drs_15_0021.html", "node_id":"drs_15_0021.xml", "product_code":"drs", - "code":"270", + "code":"288", "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":"Checking Whether the Source Database Contains Triggers or Events,Database Objects,User Guide", @@ -5676,7 +6054,7 @@ "uri":"drs_11_0068.html", "node_id":"drs_11_0068.xml", "product_code":"drs", - "code":"271", + "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":"Database Configuration Items", @@ -5697,7 +6075,7 @@ "uri":"drs_11_0045.html", "node_id":"drs_11_0045.xml", "product_code":"drs", - "code":"272", + "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":"Checking Whether the Source Database Name Is Valid,Database Configuration Items,User Guide", @@ -5718,7 +6096,7 @@ "uri":"drs_11_0105.html", "node_id":"drs_11_0105.xml", "product_code":"drs", - "code":"273", + "code":"291", "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":"Checking Whether the Source Database Table Name Is Valid,Database Configuration Items,User Guide", @@ -5739,7 +6117,7 @@ "uri":"drs_11_0072.html", "node_id":"drs_11_0072.xml", "product_code":"drs", - "code":"274", + "code":"292", "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":"Checking Whether the Source Database View Name Is Valid,Database Configuration Items,User Guide", @@ -5760,7 +6138,7 @@ "uri":"drs_11_0069.html", "node_id":"drs_11_0069.xml", "product_code":"drs", - "code":"275", + "code":"293", "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":"Checking Whether the Shard Key Can Be Obtained from the Source Database,Database Configuration Items", @@ -5781,7 +6159,7 @@ "uri":"drs_11_0070.html", "node_id":"drs_11_0070.xml", "product_code":"drs", - "code":"276", + "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":"Conflicts", @@ -5802,7 +6180,7 @@ "uri":"drs_11_0004.html", "node_id":"drs_11_0004.xml", "product_code":"drs", - "code":"277", + "code":"295", "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":"Checking Whether the Names of the Source and Destination Databases Are the Same,Conflicts,User Guide", @@ -5823,7 +6201,7 @@ "uri":"drs_11_0043.html", "node_id":"drs_11_0043.xml", "product_code":"drs", - "code":"278", + "code":"296", "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":"non-empty collection with the same name as the source database,Checking Whether the Destination Data", @@ -5844,7 +6222,7 @@ "uri":"drs_11_0071.html", "node_id":"drs_11_0071.xml", "product_code":"drs", - "code":"279", + "code":"297", "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":"SSL Connections", @@ -5865,7 +6243,7 @@ "uri":"drs_11_0017.html", "node_id":"drs_11_0017.xml", "product_code":"drs", - "code":"280", + "code":"298", "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":"Checking Whether the SSL Connection Is Correctly Configured,SSL Connections,User Guide", @@ -5886,7 +6264,7 @@ "uri":"drs_11_0042.html", "node_id":"drs_11_0042.xml", "product_code":"drs", - "code":"281", + "code":"299", "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":"SSL connection,Checking Whether the SSL Connection Is Enabled for the Source Database,SSL Connection", @@ -5907,7 +6285,7 @@ "uri":"drs_11_0107.html", "node_id":"drs_11_0107.xml", "product_code":"drs", - "code":"282", + "code":"300", "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":"Checking Whether the SSL Certificate of the Destination Database Exists,SSL Connections,User Guide", @@ -5928,7 +6306,7 @@ "uri":"drs_11_0220.html", "node_id":"drs_11_0220.xml", "product_code":"drs", - "code":"283", + "code":"301", "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":"Object Dependencies", @@ -5949,7 +6327,7 @@ "uri":"drs_11_0222.html", "node_id":"drs_11_0222.xml", "product_code":"drs", - "code":"284", + "code":"302", "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":"Checking Whether Referenced Tables Are Selected for Migration,Object Dependencies,User Guide", @@ -5970,7 +6348,7 @@ "uri":"drs_02_0488.html", "node_id":"drs_02_0488.xml", "product_code":"drs", - "code":"285", + "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":"Failure Cases", @@ -5991,7 +6369,7 @@ "uri":"drs_13_0002.html", "node_id":"drs_13_0002.xml", "product_code":"drs", - "code":"286", + "code":"304", "des":"When you migrate full backups from self-built OBS buckets to clouds, the following error message is displayed: restore:null.The possible causes are as follows:Backup file", "doc_type":"usermanual", "kw":"migration,Backup Migration Failed Because Backup Files Cannot Be Found,Failure Cases,User Guide", @@ -6012,7 +6390,7 @@ "uri":"drs_13_0005.html", "node_id":"drs_13_0005.xml", "product_code":"drs", - "code":"287", + "code":"305", "des":"When you migrate full backups from self-built OBS buckets to clouds, the system displays an error message indicating that the migration failed because the source database", "doc_type":"usermanual", "kw":"the source database cannot be found in the backup files,Backup Migration Failed Because a Backup Dat", @@ -6033,7 +6411,7 @@ "uri":"drs_change_history.html", "node_id":"drs_change_history.xml", "product_code":"drs", - "code":"288", + "code":"306", "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", diff --git a/docs/drs/umn/CLASS.TXT.json b/docs/drs/umn/CLASS.TXT.json index 2bb8e7ec8..47eecd409 100644 --- a/docs/drs/umn/CLASS.TXT.json +++ b/docs/drs/umn/CLASS.TXT.json @@ -107,6 +107,24 @@ "p_code":"9", "code":"12" }, + { + "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":"drs", + "title":"Specification Description", + "uri":"drs_01_0313.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"13" + }, + { + "desc":"The performance indicators provided in this section are for reference only. The actual environment is affected by factors such as the performance of the source or destina", + "product_code":"drs", + "title":"Real-Time Synchronization", + "uri":"drs_01_0314.html", + "doc_type":"usermanual", + "p_code":"13", + "code":"14" + }, { "desc":"VPC-based migration refers to a real-time migration that the source and destination databases are in the same VPC or two VPCs that can communicate with each other. No add", "product_code":"drs", @@ -114,7 +132,7 @@ "uri":"drs_01_0005.html", "doc_type":"usermanual", "p_code":"1", - "code":"13" + "code":"15" }, { "desc":"You can encrypt data and database connections and increase database account security.Before saving sensitive information and private data in a database, encrypt data to r", @@ -123,7 +141,7 @@ "uri":"drs_01_0012.html", "doc_type":"usermanual", "p_code":"1", - "code":"14" + "code":"16" }, { "desc":"To begin using DRS, register an account on the official website. When the registration is successful, you can access all cloud services, including DRS and RDS.If you have", @@ -132,7 +150,7 @@ "uri":"drs_01_0021.html", "doc_type":"usermanual", "p_code":"1", - "code":"15" + "code":"17" }, { "desc":"To improve your experience with DRS, add the Security Administrator permission using IAM in case some functions become unavailable, such as scheduled task startup, automa", @@ -141,7 +159,7 @@ "uri":"drs_01_0200.html", "doc_type":"usermanual", "p_code":"1", - "code":"16" + "code":"18" }, { "desc":"If you need to assign different permissions to employees in your enterprise to access your DRS resources, IAM is a good choice for fine-grained permissions management. IA", @@ -150,7 +168,7 @@ "uri":"drs_01_0201.html", "doc_type":"usermanual", "p_code":"1", - "code":"17" + "code":"19" }, { "desc":"You understand and agree that your use of this service complies with laws and regulations, including but not limited to legal compliance requirements on data content, dat", @@ -159,7 +177,7 @@ "uri":"drs_01_0318.html", "doc_type":"usermanual", "p_code":"1", - "code":"18" + "code":"20" }, { "desc":"DRS can migrate data from your databases to the RDS databases in the cloud. For more information about RDS, see Relational Database Service User Guide.Supported network t", @@ -168,7 +186,7 @@ "uri":"drs_01_0004.html", "doc_type":"usermanual", "p_code":"1", - "code":"19" + "code":"21" }, { "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.", @@ -177,7 +195,7 @@ "uri":"drs_02_0470.html", "doc_type":"usermanual", "p_code":"", - "code":"20" + "code":"22" }, { "desc":"Before creating a DRS task, make preparations given in the following table to meet the environment requirements.", @@ -185,8 +203,8 @@ "title":"Overview", "uri":"drs_02_0471.html", "doc_type":"usermanual", - "p_code":"20", - "code":"21" + "p_code":"22", + "code":"23" }, { "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.", @@ -194,8 +212,8 @@ "title":"Permissions Management", "uri":"drs_08_0010.html", "doc_type":"usermanual", - "p_code":"20", - "code":"22" + "p_code":"22", + "code":"24" }, { "desc":"This section describes IAM's fine-grained permissions management for DRS.With IAM, you can:Create IAM users for employees based on the organizational structure of your en", @@ -203,8 +221,8 @@ "title":"Creating a User and Granting Permissions", "uri":"drs_08_0012.html", "doc_type":"usermanual", - "p_code":"22", - "code":"23" + "p_code":"24", + "code":"25" }, { "desc":"Custom policies can be created to supplement the system-defined policies of DRS.You can create custom policies in either of the following ways:Visual editor: Select cloud", @@ -212,8 +230,8 @@ "title":"Creating a Custom Policy", "uri":"drs_08_0088.html", "doc_type":"usermanual", - "p_code":"22", - "code":"24" + "p_code":"24", + "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.", @@ -222,7 +240,7 @@ "uri":"drs_02_0017.html", "doc_type":"usermanual", "p_code":"", - "code":"25" + "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.", @@ -230,8 +248,8 @@ "title":"To the Cloud", "uri":"drs_online_migration.html", "doc_type":"usermanual", - "p_code":"25", - "code":"26" + "p_code":"27", + "code":"28" }, { "desc":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", @@ -239,8 +257,8 @@ "title":"From MySQL to MySQL", "uri":"drs_04_0088.html", "doc_type":"usermanual", - "p_code":"26", - "code":"27" + "p_code":"28", + "code":"29" }, { "desc":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", @@ -248,17 +266,17 @@ "title":"From MySQL to DDM", "uri":"drs_04_0089.html", "doc_type":"usermanual", - "p_code":"26", - "code":"28" + "p_code":"28", + "code":"30" }, { "desc":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", "product_code":"drs", - "title":"From MySQL to GaussDB(for MySQL) Primary/Standby", + "title":"From MySQL to TaurusDB Cluster", "uri":"drs_04_0090.html", "doc_type":"usermanual", - "p_code":"26", - "code":"29" + "p_code":"28", + "code":"31" }, { "desc":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", @@ -266,8 +284,8 @@ "title":"From MongoDB to DDS", "uri":"drs_04_0095.html", "doc_type":"usermanual", - "p_code":"26", - "code":"30" + "p_code":"28", + "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.", @@ -275,8 +293,8 @@ "title":"Out of the Cloud", "uri":"drs_02_0031.html", "doc_type":"usermanual", - "p_code":"25", - "code":"31" + "p_code":"27", + "code":"33" }, { "desc":"To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require diffe", @@ -284,8 +302,8 @@ "title":"From MySQL to MySQL", "uri":"drs_04_0100.html", "doc_type":"usermanual", - "p_code":"31", - "code":"32" + "p_code":"33", + "code":"34" }, { "desc":"Different types of migration tasks support different migration objects. For details, see Table 2. DRS will automatically check the objects you selected before the migrati", @@ -293,8 +311,8 @@ "title":"From DDS to MongoDB", "uri":"drs_04_0101.html", "doc_type":"usermanual", - "p_code":"31", - "code":"33" + "p_code":"33", + "code":"35" }, { "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.", @@ -302,8 +320,8 @@ "title":"Between Self-built Databases", "uri":"drs_02_0490.html", "doc_type":"usermanual", - "p_code":"25", - "code":"34" + "p_code":"27", + "code":"36" }, { "desc":"When a task is being started or in the full migration phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.To maintain data co", @@ -311,8 +329,8 @@ "title":"From MySQL to MySQL", "uri":"drs_03_1117.html", "doc_type":"usermanual", - "p_code":"34", - "code":"35" + "p_code":"36", + "code":"37" }, { "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.", @@ -320,8 +338,8 @@ "title":"Task Management", "uri":"drs_04_0010.html", "doc_type":"usermanual", - "p_code":"25", - "code":"36" + "p_code":"27", + "code":"38" }, { "desc":"A complete real-time migration consists of creating a migration task, tracking task progress, analyzing migration logs, and comparing data consistency. By comparing multi", @@ -329,8 +347,8 @@ "title":"Step 1: Create a Migration Task", "uri":"drs_02_0002.html", "doc_type":"usermanual", - "p_code":"36", - "code":"37" + "p_code":"38", + "code":"39" }, { "desc":"The migration progress of a real-time migration task helps you keep track of the status of the migration task.DRS shows the migration progress using a progress bar, helpi", @@ -338,8 +356,8 @@ "title":"Step 2: Query the Migration Progress", "uri":"drs_02_0006.html", "doc_type":"usermanual", - "p_code":"36", - "code":"38" + "p_code":"38", + "code":"40" }, { "desc":"Migration logs refer to the warning-, error-, and info-level logs generated during the migration process. This section describes how to view migration logs to locate and ", @@ -347,8 +365,8 @@ "title":"Step 3: View Migration Logs", "uri":"drs_02_0005.html", "doc_type":"usermanual", - "p_code":"36", - "code":"39" + "p_code":"38", + "code":"41" }, { "desc":"This section describes how to compare migration items to check if there are any differences between source and destination databases. By comparing migration objects, you ", @@ -356,8 +374,8 @@ "title":"Step 4: Compare Migration Items", "uri":"drs_02_0007.html", "doc_type":"usermanual", - "p_code":"36", - "code":"40" + "p_code":"38", + "code":"42" }, { "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.", @@ -365,8 +383,8 @@ "title":"Managing Objects", "uri":"drs_03_0007.html", "doc_type":"usermanual", - "p_code":"36", - "code":"41" + "p_code":"38", + "code":"43" }, { "desc":"During a database migration, accounts need to be migrated separately.During the migration of MySQL databases, there are accounts that can be migrated completely, accounts", @@ -374,8 +392,8 @@ "title":"Migrating Accounts", "uri":"drs_09_0017.html", "doc_type":"usermanual", - "p_code":"41", - "code":"42" + "p_code":"43", + "code":"44" }, { "desc":"Parameter comparison helps you check consistency between the source and destination database data to ensure your services will not be affected after being migrated.This s", @@ -383,8 +401,8 @@ "title":"Parameters for Comparison", "uri":"drs_08_0001.html", "doc_type":"usermanual", - "p_code":"41", - "code":"43" + "p_code":"43", + "code":"45" }, { "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.", @@ -392,8 +410,8 @@ "title":"Task Life Cycle", "uri":"drs_03_0008.html", "doc_type":"usermanual", - "p_code":"36", - "code":"44" + "p_code":"38", + "code":"46" }, { "desc":"This section describes how to view details about a migration task, including information about the task, replication instance, and migration.You have logged in to the DRS", @@ -401,8 +419,8 @@ "title":"Viewing Task Details", "uri":"drs_04_0005.html", "doc_type":"usermanual", - "p_code":"44", - "code":"45" + "p_code":"46", + "code":"47" }, { "desc":"After a migration task is created, you can modify task information to identify different tasks.The following task information can be edited:Task nameDescriptionTask start", @@ -410,8 +428,8 @@ "title":"Editing Migration Task Information", "uri":"drs_04_0006.html", "doc_type":"usermanual", - "p_code":"44", - "code":"46" + "p_code":"46", + "code":"48" }, { "desc":"During the migration, you may change the password of the source or destination database. As a result, the migration task fails. In this case, you need to change the passw", @@ -419,8 +437,8 @@ "title":"Modifying Connection Information", "uri":"drs_03_1135.html", "doc_type":"usermanual", - "p_code":"44", - "code":"47" + "p_code":"46", + "code":"49" }, { "desc":"You can choose whether to control the flow. DRS allows you to change the flow control mode after a task is created. Currently, only the following real-time migration type", @@ -428,8 +446,8 @@ "title":"Modifying the Flow Control Mode", "uri":"drs_03_0046.html", "doc_type":"usermanual", - "p_code":"44", - "code":"48" + "p_code":"46", + "code":"50" }, { "desc":"For a migration task that has been created but not started, DRS allows you to edit the configuration information of the task, including the task information, replication ", @@ -437,8 +455,8 @@ "title":"Editing a Migration Task", "uri":"drs_03_0002.html", "doc_type":"usermanual", - "p_code":"44", - "code":"49" + "p_code":"46", + "code":"51" }, { "desc":"A fault may occur during the migration due to external factors, such as insufficient storage space. After the fault is rectified based on the migration log information, y", @@ -446,8 +464,8 @@ "title":"Resuming a Migration Task", "uri":"drs_09_0100.html", "doc_type":"usermanual", - "p_code":"44", - "code":"50" + "p_code":"46", + "code":"52" }, { "desc":"During the migration, if a migration task fails due to uncertain causes, the background will resume the task several times. However, the task may fail to be recovered in ", @@ -455,8 +473,8 @@ "title":"Resetting a Migration Task", "uri":"drs_03_0100.html", "doc_type":"usermanual", - "p_code":"44", - "code":"51" + "p_code":"46", + "code":"53" }, { "desc":"During migration, if the flow control mode cannot meet the requirements during peak hours, you can pause the migration task.You can pause the following migration tasks:To", @@ -464,8 +482,8 @@ "title":"Pausing a Migration Task", "uri":"drs_03_0109.html", "doc_type":"usermanual", - "p_code":"44", - "code":"52" + "p_code":"46", + "code":"54" }, { "desc":"After the source database and services are migrated to the destination database, you can stop the migration task. To prevent data from being overwritten after the source ", @@ -473,8 +491,8 @@ "title":"Stopping a Migration Task", "uri":"drs_03_0004.html", "doc_type":"usermanual", - "p_code":"44", - "code":"53" + "p_code":"46", + "code":"55" }, { "desc":"This section describes how to delete a migration task that has been completed or has failed. Deleted tasks will no longer be displayed in the task list. Exercise caution ", @@ -482,8 +500,8 @@ "title":"Deleting a Migration Task", "uri":"drs_03_0005.html", "doc_type":"usermanual", - "p_code":"44", - "code":"54" + "p_code":"46", + "code":"56" }, { "desc":"Migration statuses indicate different migration phases.Table 1 lists statuses and descriptions of online migration tasks.If a task fails to be created, DRS retains the ta", @@ -491,8 +509,8 @@ "title":"Task Statuses", "uri":"drs_03_0001.html", "doc_type":"usermanual", - "p_code":"44", - "code":"55" + "p_code":"46", + "code":"57" }, { "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", @@ -500,8 +518,26 @@ "title":"Tag Management", "uri":"drs_online_tag.html", "doc_type":"usermanual", - "p_code":"25", - "code":"56" + "p_code":"27", + "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":"drs", + "title":"Interconnecting with Cloud Eye", + "uri":"drs_03_0105.html", + "doc_type":"usermanual", + "p_code":"27", + "code":"59" + }, + { + "desc":"Cloud Eye monitors the running statuses of replication, synchronization, and DR instances. You can obtain the monitoring metrics on the management console. Monitored data", + "product_code":"drs", + "title":"Viewing Monitoring Metrics", + "uri":"drs_03_0108.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.", @@ -510,7 +546,7 @@ "uri":"drs_04_0001.html", "doc_type":"usermanual", "p_code":"", - "code":"57" + "code":"61" }, { "desc":"It often becomes necessary to hide the real IP address of your database for the sake of security. Migrating data through direct connections is an option, but costly. DRS ", @@ -518,8 +554,8 @@ "title":"Migration Overview", "uri":"drs_offline_migration.html", "doc_type":"usermanual", - "p_code":"57", - "code":"58" + "p_code":"61", + "code":"62" }, { "desc":"You have logged in to the DRS console.For details about the supported DB types and versions, see Backup Migration.This section describes constraints on backup migrations ", @@ -527,8 +563,8 @@ "title":"Creating an RDS Backup Migration Task", "uri":"drs_02_0010.html", "doc_type":"usermanual", - "p_code":"57", - "code":"59" + "p_code":"61", + "code":"63" }, { "desc":"You have logged in to the DRS console.For details about the supported DB types and versions, see Backup Migration.This section describes constraints on backup migrations ", @@ -536,8 +572,8 @@ "title":"Creating a Backup Using OBS Buckets", "uri":"drs_02_0009.html", "doc_type":"usermanual", - "p_code":"57", - "code":"60" + "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.", @@ -545,8 +581,8 @@ "title":"Task Management", "uri":"drs_04_0007.html", "doc_type":"usermanual", - "p_code":"57", - "code":"61" + "p_code":"61", + "code":"65" }, { "desc":"The Basic Information page of a backup migration task displays information about the task, backup files, and databases. This section describes how to view details about c", @@ -554,8 +590,8 @@ "title":"Viewing Task Details", "uri":"drs_04_0002.html", "doc_type":"usermanual", - "p_code":"61", - "code":"62" + "p_code":"65", + "code":"66" }, { "desc":"After a backup migration task is created, you can modify basic information about the task to identify different tasks.The following task information can be edited:Task na", @@ -563,8 +599,8 @@ "title":"Editing Migration Task Information", "uri":"drs_04_0008.html", "doc_type":"usermanual", - "p_code":"61", - "code":"63" + "p_code":"65", + "code":"67" }, { "desc":"Migration logs refer to the warning-, error-, and info-level logs generated during the migration process. This section describes how to view migration logs to locate and ", @@ -572,8 +608,8 @@ "title":"Viewing Migration Logs", "uri":"drs_04_0003.html", "doc_type":"usermanual", - "p_code":"61", - "code":"64" + "p_code":"65", + "code":"68" }, { "desc":"This section describes how to delete a migration task. Deleted tasks will no longer be displayed in the task list. Exercise caution when performing this operation.You hav", @@ -581,8 +617,8 @@ "title":"Deleting a Migration Task", "uri":"drs_04_0004.html", "doc_type":"usermanual", - "p_code":"61", - "code":"65" + "p_code":"65", + "code":"69" }, { "desc":"Migration statuses indicate different migration phases.Table 1 lists statuses and descriptions of backup migration tasks.Deleted migration tasks are not displayed in the ", @@ -590,8 +626,8 @@ "title":"Task Statuses", "uri":"drs_03_0010.html", "doc_type":"usermanual", - "p_code":"61", - "code":"66" + "p_code":"65", + "code":"70" }, { "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", @@ -599,8 +635,8 @@ "title":"Tag Management", "uri":"drs_backup_tag.html", "doc_type":"usermanual", - "p_code":"57", - "code":"67" + "p_code":"61", + "code":"71" }, { "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.", @@ -609,7 +645,7 @@ "uri":"drs_10_0002.html", "doc_type":"usermanual", "p_code":"", - "code":"68" + "code":"72" }, { "desc":"DRS real-time synchronization supports multiple topology types. You can plan the topology types as required. For details, see the following content.To ensure data consist", @@ -617,8 +653,8 @@ "title":"Data Synchronization Topologies", "uri":"drs_11_0457.html", "doc_type":"usermanual", - "p_code":"68", - "code":"69" + "p_code":"72", + "code":"73" }, { "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.", @@ -626,8 +662,8 @@ "title":"To the Cloud", "uri":"drs_06_0003.html", "doc_type":"usermanual", - "p_code":"68", - "code":"70" + "p_code":"72", + "code":"74" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", @@ -635,8 +671,8 @@ "title":"From MySQL to MySQL", "uri":"drs_04_0102.html", "doc_type":"usermanual", - "p_code":"70", - "code":"71" + "p_code":"74", + "code":"75" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", @@ -644,17 +680,17 @@ "title":"From MySQL to GaussDB Distributed", "uri":"drs_04_0104.html", "doc_type":"usermanual", - "p_code":"70", - "code":"72" + "p_code":"74", + "code":"76" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", "product_code":"drs", - "title":"From MySQL to GaussDB(for MySQL) Primary/Standby", + "title":"From MySQL to TaurusDB Cluster", "uri":"drs_03_1124.html", "doc_type":"usermanual", - "p_code":"70", - "code":"73" + "p_code":"74", + "code":"77" }, { "desc":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.To start a syn", @@ -662,8 +698,8 @@ "title":"From PostgreSQL to PostgreSQL", "uri":"drs_04_0107.html", "doc_type":"usermanual", - "p_code":"70", - "code":"74" + "p_code":"74", + "code":"78" }, { "desc":"When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.To keep data ", @@ -671,8 +707,8 @@ "title":"From Oracle to PostgreSQL", "uri":"drs_04_0446.html", "doc_type":"usermanual", - "p_code":"70", - "code":"75" + "p_code":"74", + "code":"79" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", @@ -680,8 +716,8 @@ "title":"From DDM to MySQL", "uri":"drs_04_0115.html", "doc_type":"usermanual", - "p_code":"70", - "code":"76" + "p_code":"74", + "code":"80" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", @@ -689,8 +725,8 @@ "title":"From DDM to DDM", "uri":"drs_04_0465.html", "doc_type":"usermanual", - "p_code":"70", - "code":"77" + "p_code":"74", + "code":"81" }, { "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.", @@ -698,8 +734,8 @@ "title":"Out of the Cloud", "uri":"drs_04_0451.html", "doc_type":"usermanual", - "p_code":"68", - "code":"78" + "p_code":"72", + "code":"82" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", @@ -707,17 +743,17 @@ "title":"From MySQL to MySQL", "uri":"drs_04_0117.html", "doc_type":"usermanual", - "p_code":"78", - "code":"79" + "p_code":"82", + "code":"83" }, { - "desc":"DMS for KafkaYou have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The s", + "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The success of dat", "product_code":"drs", "title":"From MySQL to Kafka", "uri":"drs_04_0118.html", "doc_type":"usermanual", - "p_code":"78", - "code":"80" + "p_code":"82", + "code":"84" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", @@ -725,17 +761,53 @@ "title":"From DDM to MySQL", "uri":"drs_04_0453.html", "doc_type":"usermanual", - "p_code":"78", - "code":"81" + "p_code":"82", + "code":"85" + }, + { + "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The success of dat", + "product_code":"drs", + "title":"From DDS to MongoDB", + "uri":"drs_04_0464.html", + "doc_type":"usermanual", + "p_code":"82", + "code":"86" + }, + { + "desc":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.To start a syn", + "product_code":"drs", + "title":"From PostgreSQL to PostgreSQL", + "uri":"drs_04_0508.html", + "doc_type":"usermanual", + "p_code":"82", + "code":"87" }, { "desc":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.Before you sta", "product_code":"drs", - "title":"From GaussDB Distributed to MySQL", - "uri":"drs_04_0121.html", + "title":"From GaussDB Distributed to Oracle", + "uri":"drs_11_0436.html", "doc_type":"usermanual", - "p_code":"78", - "code":"82" + "p_code":"82", + "code":"88" + }, + { + "desc":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.Before you sta", + "product_code":"drs", + "title":"From GaussDB Distributed to Kafka", + "uri":"drs_11_0454.html", + "doc_type":"usermanual", + "p_code":"82", + "code":"89" + }, + { + "desc":"Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.Before you sta", + "product_code":"drs", + "title":"From GaussDB Distributed to GaussDB Distributed", + "uri":"drs_11_0442.html", + "doc_type":"usermanual", + "p_code":"82", + "code":"90" }, { "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.", @@ -743,17 +815,8 @@ "title":"Between Self-built Databases", "uri":"drs_04_0452.html", "doc_type":"usermanual", - "p_code":"68", - "code":"83" - }, - { - "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.When a task is bei", - "product_code":"drs", - "title":"From MySQL to MySQL", - "uri":"drs_03_1118.html", - "doc_type":"usermanual", - "p_code":"83", - "code":"84" + "p_code":"72", + "code":"91" }, { "desc":"You have logged in to the DRS console.For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.The success of dat", @@ -761,8 +824,8 @@ "title":"From MySQL to Kafka", "uri":"drs_04_0128.html", "doc_type":"usermanual", - "p_code":"83", - "code":"85" + "p_code":"91", + "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.", @@ -770,8 +833,8 @@ "title":"Task Management", "uri":"drs_TaskMangement.html", "doc_type":"usermanual", - "p_code":"68", - "code":"86" + "p_code":"72", + "code":"93" }, { "desc":"A complete real-time synchronization consists of creating a synchronization task, tracking task progress, analyzing synchronization logs, and comparing data consistency. ", @@ -779,8 +842,8 @@ "title":"Step 1: Create a Synchronization Task", "uri":"drs_06_0005.html", "doc_type":"usermanual", - "p_code":"86", - "code":"87" + "p_code":"93", + "code":"94" }, { "desc":"This section describes how to check the synchronization progress.During a full synchronization, DRS displays the progress overview. You can view the structure, data, and ", @@ -788,8 +851,8 @@ "title":"Step 2: Query the Synchronization Progress", "uri":"drs_10_0007.html", "doc_type":"usermanual", - "p_code":"86", - "code":"88" + "p_code":"93", + "code":"95" }, { "desc":"Synchronization logs refer to the warning-, error-, and info-level logs generated during the synchronization process. This section describes how to view synchronization l", @@ -797,8 +860,8 @@ "title":"Step 3: View Synchronization Logs", "uri":"drs_10_0008.html", "doc_type":"usermanual", - "p_code":"86", - "code":"89" + "p_code":"93", + "code":"96" }, { "desc":"This section describes how to compare synchronization items to check if there are any differences between source and destination databases. To minimize the impact on serv", @@ -806,8 +869,8 @@ "title":"Step 4: Compare Synchronization Items", "uri":"drs_10_0012.html", "doc_type":"usermanual", - "p_code":"86", - "code":"90" + "p_code":"93", + "code":"97" }, { "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.", @@ -815,8 +878,8 @@ "title":"Managing Objects", "uri":"drs_05_0007.html", "doc_type":"usermanual", - "p_code":"86", - "code":"91" + "p_code":"93", + "code":"98" }, { "desc":"This section describes how to change synchronization objects in a synchronization task. After a data synchronization task is created, you can change synchronization objec", @@ -824,8 +887,8 @@ "title":"Editing Synchronization Objects", "uri":"drs_10_0009.html", "doc_type":"usermanual", - "p_code":"91", - "code":"92" + "p_code":"98", + "code":"99" }, { "desc":"Real-time synchronization supports the import of objects through files. After a task is created, you can import object files on the Set Synchronization Task page.Only Win", @@ -833,17 +896,17 @@ "title":"Importing Synchronization Objects", "uri":"drs_10_0402.html", "doc_type":"usermanual", - "p_code":"91", - "code":"93" + "p_code":"98", + "code":"100" }, { "desc":"Data synchronization allows you to synchronize objects (including databases, schemas and tables) in a sources database to the corresponding objects in a destination datab", "product_code":"drs", - "title":"Mapping Object Names", + "title":"Changing Object Names (Mapping Object Names)", "uri":"drs_10_0015.html", "doc_type":"usermanual", - "p_code":"91", - "code":"94" + "p_code":"98", + "code":"101" }, { "desc":"During real-time synchronization, the objects that can be mapped to the destination include databases, schemas, tables, and columns (in data processing). After a mapping ", @@ -851,8 +914,8 @@ "title":"Viewing Synchronization Mapping Information", "uri":"drs_10_0100.html", "doc_type":"usermanual", - "p_code":"91", - "code":"95" + "p_code":"98", + "code":"102" }, { "desc":"DRS processes synchronized objects and allows you to add rules for selected objects.After a data filtering rule is added, update the source database to ensure data consis", @@ -860,8 +923,35 @@ "title":"Processing Data", "uri":"drs_03_0035.html", "doc_type":"usermanual", - "p_code":"91", - "code":"96" + "p_code":"98", + "code":"103" + }, + { + "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":"drs", + "title":"Managing Parameters", + "uri":"drs_10_0409.html", + "doc_type":"usermanual", + "p_code":"93", + "code":"104" + }, + { + "desc":"DRS allows you to change task parameters based on service requirements.You can change parameters of a synchronization task in the Configuration, Full, Full synchronizatio", + "product_code":"drs", + "title":"Changing Task Parameters", + "uri":"drs_10_0410.html", + "doc_type":"usermanual", + "p_code":"104", + "code":"105" + }, + { + "desc":"DRS allows you to view the change history of task parameters to meet service requirements.By default, the parameter change history of the last seven days can be queried.", + "product_code":"drs", + "title":"Viewing Parameter Change History", + "uri":"drs_10_0411.html", + "doc_type":"usermanual", + "p_code":"104", + "code":"106" }, { "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.", @@ -869,8 +959,8 @@ "title":"Task Life Cycle", "uri":"drs_05_0006.html", "doc_type":"usermanual", - "p_code":"86", - "code":"97" + "p_code":"93", + "code":"107" }, { "desc":"View the information about the synchronization tasks and synchronization instances. This section describes how to view details about a synchronization task you have creat", @@ -878,8 +968,8 @@ "title":"Viewing Task Details", "uri":"drs_10_0003.html", "doc_type":"usermanual", - "p_code":"97", - "code":"98" + "p_code":"107", + "code":"108" }, { "desc":"After a synchronization task is created, you can modify task information to identify different tasks.The following task information can be edited:Task nameDescriptionTask", @@ -887,8 +977,8 @@ "title":"Modifying Task Information", "uri":"drs_10_0004.html", "doc_type":"usermanual", - "p_code":"97", - "code":"99" + "p_code":"107", + "code":"109" }, { "desc":"A data synchronization task may fail due to the change of the password of the source or destination database. You need to update the information and then retry the synchr", @@ -896,8 +986,8 @@ "title":"Modifying Connection Information", "uri":"drs_10_0016.html", "doc_type":"usermanual", - "p_code":"97", - "code":"100" + "p_code":"107", + "code":"110" }, { "desc":"You can choose whether to control the flow. DRS allows you to change the flow control mode after a task is created. Currently, only the following real-time migration type", @@ -905,8 +995,8 @@ "title":"Modifying the Flow Control Mode", "uri":"drs_10_0401.html", "doc_type":"usermanual", - "p_code":"97", - "code":"101" + "p_code":"107", + "code":"111" }, { "desc":"For a synchronization task that has been created but not started, DRS allows you to edit the configuration information of the task, including the source and destination d", @@ -914,8 +1004,8 @@ "title":"Editing a Synchronization Task", "uri":"drs_10_0010.html", "doc_type":"usermanual", - "p_code":"97", - "code":"102" + "p_code":"107", + "code":"112" }, { "desc":"A fault may occur during the synchronization due to external factors, such as insufficient storage space. After the fault is rectified based on the synchronization log in", @@ -923,8 +1013,8 @@ "title":"Resuming a Synchronization Task", "uri":"drs_10_0400.html", "doc_type":"usermanual", - "p_code":"97", - "code":"103" + "p_code":"107", + "code":"113" }, { "desc":"DRS allows you to pause real-time synchronization tasks.The following tasks can be paused during incremental synchronization:To the cloudMySQL->MySQLPostgreSQL->PostgreSQ", @@ -932,8 +1022,8 @@ "title":"Pausing a Synchronization Task", "uri":"drs_03_0110.html", "doc_type":"usermanual", - "p_code":"97", - "code":"104" + "p_code":"107", + "code":"114" }, { "desc":"During real-time synchronization, you can reset the synchronization tasks in one of the following statuses so that you do not need to configure the tasks again.PausedIncr", @@ -941,8 +1031,35 @@ "title":"Resetting a Synchronization Task", "uri":"drs_10_0300.html", "doc_type":"usermanual", - "p_code":"97", - "code":"105" + "p_code":"107", + "code":"115" + }, + { + "desc":"DRS allows you to restart a synchronization task after task parameters are changed in Changing Task Parameters.Tasks in the Full, Full synchronization failed, Incremental", + "product_code":"drs", + "title":"Restarting a Synchronization Task", + "uri":"drs_10_0412.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"116" + }, + { + "desc":"DRS allows you to change a single-AZ task to a dual-AZ task, improving task reliability while remaining the original task.A dual-AZ task cannot be changed to a single-AZ ", + "product_code":"drs", + "title":"Changing a Single-AZ Task to a Dual-AZ Task", + "uri":"drs_06_0010.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"117" + }, + { + "desc":"DRS allows you to clone the configuration of existing synchronization tasks. However, tasks in the following status cannot be cloned:CreatingCreation failedConfigurationP", + "product_code":"drs", + "title":"Cloning a Synchronization Task", + "uri":"drs_11_0462.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"118" }, { "desc":"After the source database and services are migrated to the destination database, you can stop the synchronization task. To prevent data from being overwritten after the s", @@ -950,8 +1067,8 @@ "title":"Stopping a Synchronization Task", "uri":"drs_10_0013.html", "doc_type":"usermanual", - "p_code":"97", - "code":"106" + "p_code":"107", + "code":"119" }, { "desc":"This section describes how to delete a synchronization task that has been completed or has failed. Deleted tasks will no longer be displayed in the task list. Exercise ca", @@ -959,8 +1076,8 @@ "title":"Deleting a Synchronization Task", "uri":"drs_10_0014.html", "doc_type":"usermanual", - "p_code":"97", - "code":"107" + "p_code":"107", + "code":"120" }, { "desc":"Synchronization statuses indicate different synchronization phases.", @@ -968,8 +1085,8 @@ "title":"Task Statuses", "uri":"drs_06_0004.html", "doc_type":"usermanual", - "p_code":"97", - "code":"108" + "p_code":"107", + "code":"121" }, { "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", @@ -977,8 +1094,44 @@ "title":"Tag Management", "uri":"drs_synchronization_tag.html", "doc_type":"usermanual", - "p_code":"68", - "code":"109" + "p_code":"72", + "code":"122" + }, + { + "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":"drs", + "title":"Interconnecting with Cloud Eye", + "uri":"drs_05_0011.html", + "doc_type":"usermanual", + "p_code":"72", + "code":"123" + }, + { + "desc":"This section describes metrics reported by the Data Replication Service (DRS) to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud ", + "product_code":"drs", + "title":"Supported Metrics", + "uri":"drs_05_0012.html", + "doc_type":"usermanual", + "p_code":"123", + "code":"124" + }, + { + "desc":"You can configure DRS alarm rules to customize the monitored objects and notification policies and learn the DRS running status in a timely manner.This section describes ", + "product_code":"drs", + "title":"Configuring Alarm Rules", + "uri":"drs_05_0013.html", + "doc_type":"usermanual", + "p_code":"123", + "code":"125" + }, + { + "desc":"Cloud Eye monitors the running statuses of replication, synchronization, and DR instances. You can obtain the monitoring metrics on the management console. Monitored data", + "product_code":"drs", + "title":"Viewing Monitoring Metrics", + "uri":"drs_05_0014.html", + "doc_type":"usermanual", + "p_code":"123", + "code":"126" }, { "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.", @@ -986,8 +1139,8 @@ "title":"Operation Reference in Synchronization Scenarios", "uri":"drs_03_1113.html", "doc_type":"usermanual", - "p_code":"68", - "code":"110" + "p_code":"72", + "code":"127" }, { "desc":"Data synchronized to the Kafka cluster is stored in JSON, and JSON-C formats.For details about the JSON format from MySQL to Kafka, see Table 1. Parameters for synchroniz", @@ -995,8 +1148,8 @@ "title":"Kafka Message Format", "uri":"drs_03_0052.html", "doc_type":"usermanual", - "p_code":"110", - "code":"111" + "p_code":"127", + "code":"128" }, { "desc":"No security authentication mode is available. You only need to enter the IP address and port for connection.The SASL mechanism is used to connect to Kafka, and you need t", @@ -1004,17 +1157,17 @@ "title":"Kafka Authentication", "uri":"drs_05_0018.html", "doc_type":"usermanual", - "p_code":"110", - "code":"112" + "p_code":"127", + "code":"129" }, { - "desc":"This section describes how to clear the streaming replication slots of the source GaussDB distributed database after the incremental or full+incremental synchronization t", + "desc":"This section describes how to delete streaming replication slots of the source distributed GaussDB database after an incremental or a full+incremental synchronization tas", "product_code":"drs", - "title":"Forcibly Stopping Synchronization of GaussDB Distributed", + "title":"Forcibly Stopping Synchronization from GaussDB Distributed", "uri":"drs_03_1131.html", "doc_type":"usermanual", - "p_code":"110", - "code":"113" + "p_code":"127", + "code":"130" }, { "desc":"This section describes how to clear the logical replication slot of the source database, how to synchronize sequence values, and how to reset the sequence values in the d", @@ -1022,8 +1175,8 @@ "title":"Forcibly Stopping Synchronization of PostgreSQL", "uri":"drs_12_0009.html", "doc_type":"usermanual", - "p_code":"110", - "code":"114" + "p_code":"127", + "code":"131" }, { "desc":"This section describes how to perform real-time synchronization from PostgreSQL to RDS PostgreSQL. You can create triggers and functions in the source database to obtain ", @@ -1031,8 +1184,8 @@ "title":"Creating Triggers and Functions to Implement Incremental DDL Synchronization for PostgreSQL", "uri":"drs_03_0088.html", "doc_type":"usermanual", - "p_code":"110", - "code":"115" + "p_code":"127", + "code":"132" }, { "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.", @@ -1041,7 +1194,7 @@ "uri":"drs_03_0023.html", "doc_type":"usermanual", "p_code":"", - "code":"116" + "code":"133" }, { "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.", @@ -1049,8 +1202,8 @@ "title":"DR Scenarios", "uri":"drs_02_0024.html", "doc_type":"usermanual", - "p_code":"116", - "code":"117" + "p_code":"133", + "code":"134" }, { "desc":"You have logged in to the DRS console.For details about the supported DB types and versions, see Real-Time Disaster Recovery.During the DR initialization, do not perform ", @@ -1058,17 +1211,17 @@ "title":"From MySQL to MySQL", "uri":"drs_04_0122.html", "doc_type":"usermanual", - "p_code":"117", - "code":"118" + "p_code":"134", + "code":"135" }, { "desc":"You have logged in to the DRS console.For details about the supported DB types and versions, see Real-Time Disaster Recovery.During the DR initialization, do not perform ", "product_code":"drs", - "title":"From MySQL to GaussDB(for MySQL) Primary/Standby", + "title":"From MySQL to TaurusDB Cluster", "uri":"drs_04_0123.html", "doc_type":"usermanual", - "p_code":"117", - "code":"119" + "p_code":"134", + "code":"136" }, { "desc":"You have logged in to the DRS console.For details about the supported DB types and versions, see Real-Time Disaster Recovery.During the DR initialization, do not perform ", @@ -1076,8 +1229,8 @@ "title":"From Cassandra to Cassandra", "uri":"drs_04_0125.html", "doc_type":"usermanual", - "p_code":"117", - "code":"120" + "p_code":"134", + "code":"137" }, { "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.", @@ -1085,8 +1238,8 @@ "title":"Task Management", "uri":"drs_07_0007.html", "doc_type":"usermanual", - "p_code":"116", - "code":"121" + "p_code":"133", + "code":"138" }, { "desc":"To prevent service unavailability caused by regional faults, DRS provides disaster recovery to ensure service continuity. If the region where the primary instance is loca", @@ -1094,8 +1247,8 @@ "title":"Step 1: Create a DR Task", "uri":"drs_02_0027.html", "doc_type":"usermanual", - "p_code":"121", - "code":"122" + "p_code":"138", + "code":"139" }, { "desc":"After a DR task starts, you can check the DR progress.You have logged in to the DRS console.A DR task has been created and started.On the Disaster Recovery Progress tab, ", @@ -1103,8 +1256,8 @@ "title":"Step 2: Query the DR Progress", "uri":"drs_02_0028.html", "doc_type":"usermanual", - "p_code":"121", - "code":"123" + "p_code":"138", + "code":"140" }, { "desc":"DR logs refer to the warning-, error-, and info-level logs generated during the DR process. This section describes how to view DR logs to locate and analyze database prob", @@ -1112,8 +1265,8 @@ "title":"Step 3: View DR Logs", "uri":"drs_02_0029.html", "doc_type":"usermanual", - "p_code":"121", - "code":"124" + "p_code":"138", + "code":"141" }, { "desc":"DR item comparison: You can compare DR items to check data consistency between the service database and DR database. Currently, you can compare the following items during", @@ -1121,8 +1274,8 @@ "title":"Step 4: Compare DR Items", "uri":"drs_02_0033.html", "doc_type":"usermanual", - "p_code":"121", - "code":"125" + "p_code":"138", + "code":"142" }, { "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.", @@ -1130,8 +1283,8 @@ "title":"Task Life Cycle", "uri":"drs_07_0008.html", "doc_type":"usermanual", - "p_code":"121", - "code":"126" + "p_code":"138", + "code":"143" }, { "desc":"After a DR task is created, you can modify task information to identify different tasks.The following task information can be edited:Task nameDescriptionTask start timeYo", @@ -1139,8 +1292,8 @@ "title":"Editing Subscription Task Information", "uri":"drs_03_1134.html", "doc_type":"usermanual", - "p_code":"126", - "code":"127" + "p_code":"143", + "code":"144" }, { "desc":"A data DR task may fail due to the password change of the service or DR database. You need to update the information and then retry the DR task on the DRS console.You can", @@ -1148,17 +1301,17 @@ "title":"Modifying Connection Information", "uri":"drs_03_1138.html", "doc_type":"usermanual", - "p_code":"126", - "code":"128" + "p_code":"143", + "code":"145" }, { - "desc":"DRS allows you to change the flow control mode for a task. Currently, only the following DR tasks support this function.MySQL->MySQLMySQL -> GaussDB(for MySQL) primary/st", + "desc":"DRS allows you to change the flow control mode for a task. Currently, only the following DR tasks support this function.MySQL->MySQLMySQL -> TaurusDB ClusterYou have logg", "product_code":"drs", "title":"Modifying the Flow Control Mode", "uri":"drs_03_0047.html", "doc_type":"usermanual", - "p_code":"126", - "code":"129" + "p_code":"143", + "code":"146" }, { "desc":"For a DR task that has been created but not started, DRS allows you to edit the configuration information of the task, including the source and destination database detai", @@ -1166,8 +1319,8 @@ "title":"Editing a DR Task", "uri":"drs_03_0026.html", "doc_type":"usermanual", - "p_code":"126", - "code":"130" + "p_code":"143", + "code":"147" }, { "desc":"A fault may occur during DR due to external factors, such as insufficient storage space.If a DR task fails due to non-network problems, the system will automatically resu", @@ -1175,8 +1328,8 @@ "title":"Resuming a DR Task", "uri":"drs_03_0027.html", "doc_type":"usermanual", - "p_code":"126", - "code":"131" + "p_code":"143", + "code":"148" }, { "desc":"DRS monitors the DB instance performance and the migration progress. With the monitoring information, you can determine the data flow health status, data integrity, and d", @@ -1184,8 +1337,8 @@ "title":"Viewing DR Metrics", "uri":"drs_03_0024.html", "doc_type":"usermanual", - "p_code":"126", - "code":"132" + "p_code":"143", + "code":"149" }, { "desc":"DRS supports primary/standby switchover for DR tasks. If both RPO and RTO are 0, data has been completely migrated to the DR database. Then, you can determine whether to ", @@ -1193,8 +1346,8 @@ "title":"Performing a Primary/Standby Switchover for DR Tasks", "uri":"drs_03_1116.html", "doc_type":"usermanual", - "p_code":"126", - "code":"133" + "p_code":"143", + "code":"150" }, { "desc":"When the DR task is complete or no longer needed, you can stop the DR task. You can stop a task in any of the following statuses:CreatingConfigurationInitializingDisaster", @@ -1202,8 +1355,8 @@ "title":"Stopping a DR Task", "uri":"drs_03_0029.html", "doc_type":"usermanual", - "p_code":"126", - "code":"134" + "p_code":"143", + "code":"151" }, { "desc":"You can delete a DR task, when it is no longer needed Deleted tasks will no longer be displayed in the task list. Exercise caution when performing this operation.You have", @@ -1211,8 +1364,8 @@ "title":"Deleting a DR Task", "uri":"drs_03_0030.html", "doc_type":"usermanual", - "p_code":"126", - "code":"135" + "p_code":"143", + "code":"152" }, { "desc":"DR statuses indicate different DR phases.Table 1 lists DR task statuses and descriptions.If a task fails to be created, DRS retains the task for three days by default. Af", @@ -1220,8 +1373,8 @@ "title":"Task Statuses", "uri":"drs_02_0025.html", "doc_type":"usermanual", - "p_code":"126", - "code":"136" + "p_code":"143", + "code":"153" }, { "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", @@ -1229,8 +1382,8 @@ "title":"Tag Management", "uri":"drs_disaster_tag.html", "doc_type":"usermanual", - "p_code":"116", - "code":"137" + "p_code":"133", + "code":"154" }, { "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.", @@ -1239,7 +1392,7 @@ "uri":"drs_01_0099.html", "doc_type":"usermanual", "p_code":"", - "code":"138" + "code":"155" }, { "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.", @@ -1247,8 +1400,8 @@ "title":"Product Consulting", "uri":"drs_01_0103.html", "doc_type":"usermanual", - "p_code":"138", - "code":"139" + "p_code":"155", + "code":"156" }, { "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center. Each ", @@ -1256,8 +1409,8 @@ "title":"What Are Regions and AZs?", "uri":"drs_16_0103.html", "doc_type":"usermanual", - "p_code":"139", - "code":"140" + "p_code":"156", + "code":"157" }, { "desc":"DRS is a stable, efficient, and easy-to-use cloud service for database migration and synchronization in real time.It simplifies data migration processes and reduces migra", @@ -1265,8 +1418,8 @@ "title":"What Is DRS?", "uri":"drs_01_0100.html", "doc_type":"usermanual", - "p_code":"139", - "code":"141" + "p_code":"156", + "code":"158" }, { "desc":"Yes. DRS provides high availability and can migrate a single RDS instance or RDS primary/standby instances. DRS can automatically rebuild the databases connection after a", @@ -1274,8 +1427,8 @@ "title":"Can DRS Migrate RDS Primary/Standby Instances?", "uri":"drs_01_0105.html", "doc_type":"usermanual", - "p_code":"139", - "code":"142" + "p_code":"156", + "code":"159" }, { "desc":"In database migration scenarios, if a migration task fails due to unavoidable problems (such as network fluctuation), DRS records the current parsing and replay point (wh", @@ -1283,8 +1436,8 @@ "title":"Does DRS Support Resumable Uploads?", "uri":"drs_04_0031.html", "doc_type":"usermanual", - "p_code":"139", - "code":"143" + "p_code":"156", + "code":"160" }, { "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.", @@ -1292,8 +1445,8 @@ "title":"What Are the Differences Between Real-Time Migration, Real-Time DR, and Real-Time Synchronization?", "uri":"drs_04_0087.html", "doc_type":"usermanual", - "p_code":"139", - "code":"144" + "p_code":"156", + "code":"161" }, { "desc":"In the full migration phase, DRS uses the row-level parallel migration mode to ensure migration performance and transmission stability. If the source database data is com", @@ -1301,8 +1454,8 @@ "title":"How Do I Solve the Table Bloat Issue?", "uri":"drs_16_1133.html", "doc_type":"usermanual", - "p_code":"139", - "code":"145" + "p_code":"156", + "code":"162" }, { "desc":"RDS read replicas cannot be selected on the DRS console. You can select Self-built on ECS and enter the read replica IP address and port number to connect to the instance", @@ -1310,8 +1463,8 @@ "title":"Why Cannot I Select RDS Read Replicas on the DRS Console?", "uri":"drs_16_1142.html", "doc_type":"usermanual", - "p_code":"139", - "code":"146" + "p_code":"156", + "code":"163" }, { "desc":"During the initialization of a full migration or synchronization task, DRS needs to query all inventory data in the source database. DRS uses simple SQL statements to que", @@ -1319,8 +1472,8 @@ "title":"How Does DRS Affect the Source and Destination Databases?", "uri":"drs_16_1145.html", "doc_type":"usermanual", - "p_code":"139", - "code":"147" + "p_code":"156", + "code":"164" }, { "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.", @@ -1328,8 +1481,8 @@ "title":"Network and Security", "uri":"drs_01_0108.html", "doc_type":"usermanual", - "p_code":"138", - "code":"148" + "p_code":"155", + "code":"165" }, { "desc":"Uses security groups to ensure that the sources of access are trusted.Uses SSL channels to encrypt data during transmission.", @@ -1337,8 +1490,8 @@ "title":"What Security Protection Policies Does DRS Have?", "uri":"drs_01_0109.html", "doc_type":"usermanual", - "p_code":"148", - "code":"149" + "p_code":"165", + "code":"166" }, { "desc":"If the network is disconnected during the migration, you can view the task status first. If a full or incremental task fails, click Resume in the Operation column.Full mi", @@ -1346,8 +1499,8 @@ "title":"What Can I Do If the Network Is Disconnected During the Migration?", "uri":"drs_01_0110.html", "doc_type":"usermanual", - "p_code":"148", - "code":"150" + "p_code":"165", + "code":"167" }, { "desc":"By default, a VPC on the current cloud is isolated from external networks for security reasons. You cannot use an EIP outside a VPC (for example, an EIP of another cloud ", @@ -1355,8 +1508,8 @@ "title":"How Can I Configure a VPC Security Group to Allow Traffic from an EIP?", "uri":"drs_01_0112.html", "doc_type":"usermanual", - "p_code":"148", - "code":"151" + "p_code":"165", + "code":"168" }, { "desc":"Before data migration, ensure that network preparations and security rule settings are complete. If the connection is abnormal, check whether the network configuration is", @@ -1364,8 +1517,8 @@ "title":"What Can I Do If the Network Connection Between the Replication Instance and Database Is Abnormal?", "uri":"drs_02_0100.html", "doc_type":"usermanual", - "p_code":"148", - "code":"152" + "p_code":"165", + "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.", @@ -1373,8 +1526,8 @@ "title":"Permissions Management", "uri":"drs_04_0040.html", "doc_type":"usermanual", - "p_code":"138", - "code":"153" + "p_code":"155", + "code":"170" }, { "desc":"DRS has certain permission requirements on accounts during migration, synchronization, and DR. This section describes the permission requirements on the MySQL engine.You ", @@ -1382,8 +1535,8 @@ "title":"Which MySQL Permissions Are Required for DRS?", "uri":"drs_04_0034.html", "doc_type":"usermanual", - "p_code":"153", - "code":"154" + "p_code":"170", + "code":"171" }, { "desc":"mysql -h 'host' -u 'user' -p-N $@ -e \"SELECT CONCAT('SHOW GRANTS FOR ''', user, '''@''', host, ''';') AS query FROM mysql.user\" > /tmp/users.sqlhost indicates the IP add", @@ -1391,8 +1544,8 @@ "title":"How Can I Import Users and Permissions from the Source to the Destination Database?", "uri":"drs_12_0001.html", "doc_type":"usermanual", - "p_code":"153", - "code":"155" + "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.", @@ -1400,8 +1553,8 @@ "title":"Real-Time Migration", "uri":"drs_04_0025.html", "doc_type":"usermanual", - "p_code":"138", - "code":"156" + "p_code":"155", + "code":"173" }, { "desc":"You can refer to the following methods to check whether the task can be stopped. Before stopping the task, ensure that:At least one complete data comparison is performed ", @@ -1409,8 +1562,8 @@ "title":"When Can I Stop a Migration Task?", "uri":"drs_01_0104.html", "doc_type":"usermanual", - "p_code":"156", - "code":"157" + "p_code":"173", + "code":"174" }, { "desc":"Definer is used in views, stored procedures, triggers, and events. Definer does not restrict the permission to invoke objects, instead the permission to access the databa", @@ -1418,8 +1571,8 @@ "title":"How Do I Maintain the Original Service User Permission System After Definer Is Forcibly Converted During MySQL Migration?", "uri":"drs_16_0003.html", "doc_type":"usermanual", - "p_code":"156", - "code":"158" + "p_code":"173", + "code":"175" }, { "desc":"After the MySQL stored procedure is migrated to the cloud, an error may occur when the stored procedure or function is invoked due to permission problems.The method varie", @@ -1427,8 +1580,8 @@ "title":"What Can I Do If the Invoking Permission Problem Occurs After the MySQL Stored Procedure Is Migrated to the Cloud?", "uri":"drs_16_0121.html", "doc_type":"usermanual", - "p_code":"156", - "code":"159" + "p_code":"173", + "code":"176" }, { "desc":"To ensure that all services on the database are stopped, perform the following steps:", @@ -1436,8 +1589,8 @@ "title":"How Do I Ensure that All Services on the Database Are Stopped?", "uri":"drs_04_0020.html", "doc_type":"usermanual", - "p_code":"156", - "code":"160" + "p_code":"173", + "code":"177" }, { "desc":"When you use a subaccount to use scheduled task startup function, the account entrustment function must be used. Otherwise, the scheduled task fails to be started, leavin", @@ -1445,8 +1598,8 @@ "title":"What Can I Do When Scheduled Task Failed to Start Leaving Message \"can not get agency token\"", "uri":"drs_16_0123.html", "doc_type":"usermanual", - "p_code":"156", - "code":"161" + "p_code":"173", + "code":"178" }, { "desc":"Currently, RDS for MySQL does not support the MyISAM engine due to the following reasons.MyISAM engine tables do not support transactions and support only table-level loc", @@ -1454,8 +1607,8 @@ "title":"What Can I Do If MyISAM Tables Are Not Supported by RDS for MySQL?", "uri":"drs_04_0032.html", "doc_type":"usermanual", - "p_code":"156", - "code":"162" + "p_code":"173", + "code":"179" }, { "desc":"Based on MySQL 5.7, some new features have been added to MySQL 8.0. There are performance differences between the two versions. Before migration, you need to analyze comp", @@ -1463,8 +1616,8 @@ "title":"What Are the Precautions for Migrating Data from an Earlier Version MySQL to MySQL 8.0?", "uri":"drs_04_0030.html", "doc_type":"usermanual", - "p_code":"156", - "code":"163" + "p_code":"173", + "code":"180" }, { "desc":"Out of memory (OOM) occurs during the migration from MongoDB to DDS, causing migration failures.The possible causes are as follows:If the mongod service of the source dat", @@ -1472,8 +1625,8 @@ "title":"What Can I Do When OOM Occurs During the Migration from MongoDB to DDS?", "uri":"drs_15_0100.html", "doc_type":"usermanual", - "p_code":"156", - "code":"164" + "p_code":"173", + "code":"181" }, { "desc":"Before using the DRS service to migrate collections between sharded clusters, you must disable the balancer of the collections to be migrated.After the migration is compl", @@ -1481,8 +1634,8 @@ "title":"How Do I Disable the Balancer?", "uri":"drs_16_0001.html", "doc_type":"usermanual", - "p_code":"156", - "code":"165" + "p_code":"173", + "code":"182" }, { "desc":"During the MySQL to MySQL migration, if the migration log indicates that the migration of events and triggers fails after the migration task is complete, you can manually", @@ -1490,8 +1643,8 @@ "title":"How Do I Export and Import Events and Triggers in Batches?", "uri":"drs_14_0006.html", "doc_type":"usermanual", - "p_code":"156", - "code":"166" + "p_code":"173", + "code":"183" }, { "desc":"When the value of source database parameter lower_case_table_names is set to 1, the databases or tables whose names contain uppercase letters cannot be migrated.When the ", @@ -1499,8 +1652,8 @@ "title":"How Can I Migrate Databases or Tables Whose Names Contain Uppercase Letters?", "uri":"drs_14_0002.html", "doc_type":"usermanual", - "p_code":"156", - "code":"167" + "p_code":"173", + "code":"184" }, { "desc":"In a sharded cluster, orphaned documents are those documents on a shard that also exist in chunks on other shards as a result of failed migrations or incomplete migration", @@ -1508,8 +1661,8 @@ "title":"How Do I Delete Orphaned Documents in MongoDB Sharded Clusters?", "uri":"drs_09_0101.html", "doc_type":"usermanual", - "p_code":"156", - "code":"168" + "p_code":"173", + "code":"185" }, { "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.", @@ -1517,8 +1670,8 @@ "title":"Backup Migration", "uri":"drs_04_0457.html", "doc_type":"usermanual", - "p_code":"138", - "code":"169" + "p_code":"155", + "code":"186" }, { "desc":"During the backup migration, If Last Backup File is selected by mistake, perform either of the following operations:If you select Yes by mistake, the database receives a ", @@ -1526,8 +1679,8 @@ "title":"What Should I Do If the Last Backup File Is Incorrectly Selected in the Backup Migration Scenario?", "uri":"drs_04_0041.html", "doc_type":"usermanual", - "p_code":"169", - "code":"170" + "p_code":"186", + "code":"187" }, { "desc":"After data is migrated from the local host or VMs to the RDS SQL Server DB instance on the current cloud through DRS, the Login accounts, DBLink, AgentJobs, and key confi", @@ -1535,8 +1688,8 @@ "title":"Manual Configuration", "uri":"drs_04_0458.html", "doc_type":"usermanual", - "p_code":"169", - "code":"171" + "p_code":"186", + "code":"188" }, { "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.", @@ -1544,8 +1697,8 @@ "title":"Real-Time Synchronization", "uri":"drs_04_0026.html", "doc_type":"usermanual", - "p_code":"138", - "code":"172" + "p_code":"155", + "code":"189" }, { "desc":"DRS can directly synchronize tables of different schemas to those of the same schema if the tables do not conflict with each other.", @@ -1553,8 +1706,8 @@ "title":"Can DRS Sync Tables of Different Schemas to the Same Schema?", "uri":"drs_16_0101.html", "doc_type":"usermanual", - "p_code":"172", - "code":"173" + "p_code":"189", + "code":"190" }, { "desc":"During table-level incremental synchronization from MySQL to MySQL, you can use Online DDL tools to add or delete columns. Pay attention to the following when using Onlin", @@ -1562,8 +1715,8 @@ "title":"Can Online DDL Tools Be Used for Real-time Synchronization?", "uri":"drs_16_1124.html", "doc_type":"usermanual", - "p_code":"172", - "code":"174" + "p_code":"189", + "code":"191" }, { "desc":"If the source Oracle database is an RAC cluster, you are advised to use SCAN IP+SERVICE_NAMES to create a task because SCAN IP has stronger fault tolerance, better load b", @@ -1571,8 +1724,8 @@ "title":"Why Do I Use the SCAN IP Address to Connect to an Oracle RAC Cluster?", "uri":"drs_16_1151.html", "doc_type":"usermanual", - "p_code":"172", - "code":"175" + "p_code":"189", + "code":"192" }, { "desc":"In physical standby mode, the Oracle database directly replicates logs from the primary database and does not generate any logs. If the source is an Oracle database, you ", @@ -1580,8 +1733,8 @@ "title":"How Do I Check Supplemental Logging of the Source Oracle Database?", "uri":"drs_16_1155.html", "doc_type":"usermanual", - "p_code":"172", - "code":"176" + "p_code":"189", + "code":"193" }, { "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.", @@ -1589,8 +1742,8 @@ "title":"Real-Time Disaster Recovery", "uri":"drs_04_0028.html", "doc_type":"usermanual", - "p_code":"138", - "code":"177" + "p_code":"155", + "code":"194" }, { "desc":"Recovery Point Objective (RPO) refers to the difference between the time when a transaction in the current service database is submitted and the time when the transaction", @@ -1598,8 +1751,8 @@ "title":"What Are RPO and RTO of DRS Disaster Recovery?", "uri":"drs_04_0033.html", "doc_type":"usermanual", - "p_code":"177", - "code":"178" + "p_code":"194", + "code":"195" }, { "desc":"For real-time DR tasks, if the service database is faulty, manually perform a primary/standby switchover. For details, see Performing a Primary/Standby Switchover for DR ", @@ -1607,8 +1760,8 @@ "title":"Is a Primary/Standby Switchover Triggered Automatically or Manually for DR Tasks?", "uri":"drs_16_1125.html", "doc_type":"usermanual", - "p_code":"177", - "code":"179" + "p_code":"194", + "code":"196" }, { "desc":"Real-time DR is performed by instance. You cannot select a specified database, but you can select tables or databases for real-time migration and synchronization task.", @@ -1616,8 +1769,8 @@ "title":"Can Real-Time DR Be Performed for Specified Databases?", "uri":"drs_16_1126.html", "doc_type":"usermanual", - "p_code":"177", - "code":"180" + "p_code":"194", + "code":"197" }, { "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.", @@ -1625,8 +1778,8 @@ "title":"Data-Level Comparison", "uri":"drs_14_0001.html", "doc_type":"usermanual", - "p_code":"138", - "code":"181" + "p_code":"155", + "code":"198" }, { "desc":"DRS's data comparison allows you to check whether the data in the source database is the same as that in the destination database.DRS does not support value comparison fo", @@ -1634,8 +1787,8 @@ "title":"Which of the Following Data Types Are Not Supported By Value Comparison?", "uri":"drs_16_1130.html", "doc_type":"usermanual", - "p_code":"181", - "code":"182" + "p_code":"198", + "code":"199" }, { "desc":"Object comparison: System tables of the source and destination databases are queried, occupying about 10 sessions. The database is not affected. However, if there are a l", @@ -1643,8 +1796,8 @@ "title":"What Impact Does a DRS Comparison Task Have on Databases?", "uri":"drs_16_1161.html", "doc_type":"usermanual", - "p_code":"181", - "code":"183" + "p_code":"198", + "code":"200" }, { "desc":"Object comparison: Generally, the comparison results are returned within several minutes based on the query performance of the source database. If the amount of data is l", @@ -1652,8 +1805,8 @@ "title":"How Long Does a DRS Comparison Task Take?", "uri":"drs_16_1162.html", "doc_type":"usermanual", - "p_code":"181", - "code":"184" + "p_code":"198", + "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.", @@ -1661,8 +1814,8 @@ "title":"General Operations", "uri":"drs_04_0029.html", "doc_type":"usermanual", - "p_code":"138", - "code":"185" + "p_code":"155", + "code":"202" }, { "desc":"Information often overlaps when you decrease the size of the page. You are advised to set the page scale at 100%.", @@ -1670,8 +1823,8 @@ "title":"What Can I Do When Information Overlaps on the DRS Console?", "uri":"drs_15_0120.html", "doc_type":"usermanual", - "p_code":"185", - "code":"186" + "p_code":"202", + "code":"203" }, { "desc":"During the migration, the destination instance can be set to read-only or read/write.Read-only: During the migration, the destination instance is read-only. After the mig", @@ -1679,8 +1832,8 @@ "title":"Is the Destination Instance Set to Read-only or Read/Write?", "uri":"drs_04_0021.html", "doc_type":"usermanual", - "p_code":"185", - "code":"187" + "p_code":"202", + "code":"204" }, { "desc":"During migration for MySQL databases, the source database binlog must be in the ROW format. Otherwise, the task fails. After binlog_format=ROW at the global level is set ", @@ -1688,8 +1841,8 @@ "title":"How Do I Set Global binlog_format=ROW to Take Effect Immediately?", "uri":"drs_16_0002.html", "doc_type":"usermanual", - "p_code":"185", - "code":"188" + "p_code":"202", + "code":"205" }, { "desc":"When migrating MySQL databases, ensure that the binlog_row_image parameter of the source database is set to FULL. Otherwise, the migration task will fail. After binlog_ro", @@ -1697,8 +1850,8 @@ "title":"How Do I Set binlog_row_image=FULL to Take Effect Immediately?", "uri":"drs_16_0010.html", "doc_type":"usermanual", - "p_code":"185", - "code":"189" + "p_code":"202", + "code":"206" }, { "desc":"When you set the password for the migration account in the destination database, you need to set the password based on the password strength requirements of the destinati", @@ -1706,8 +1859,8 @@ "title":"How Do I Change the Destination Database Password to Meet the Password Policy?", "uri":"drs_14_0004.html", "doc_type":"usermanual", - "p_code":"185", - "code":"190" + "p_code":"202", + "code":"207" }, { "desc":"MongoDB shards data at the collection level, distributing the collection data using shard keys.You choose the shard key when sharding a collection. Each record contains a", @@ -1715,8 +1868,8 @@ "title":"How Do I Configure the Shard Key for a MongoDB Sharded Cluster?", "uri":"drs_14_0003.html", "doc_type":"usermanual", - "p_code":"185", - "code":"191" + "p_code":"202", + "code":"208" }, { "desc":"When the cloud connection bandwidth is expanded, the bandwidth link needs to be re-established and the network is disconnected. Whether the network disconnection affects ", @@ -1724,8 +1877,8 @@ "title":"Does Bandwidth Expansion Affect the Running DRS Tasks?", "uri":"drs_16_0102.html", "doc_type":"usermanual", - "p_code":"185", - "code":"192" + "p_code":"202", + "code":"209" }, { "desc":"In some MariaDB versions, the SysDB database is used as a system database (similar to the sys database of MySQL 5.7). Therefore, DRS considers the SysDB database as the s", @@ -1733,8 +1886,8 @@ "title":"Why Data in MariaDB and SysDB Cannot Be Migrated?", "uri":"drs_16_0122.html", "doc_type":"usermanual", - "p_code":"185", - "code":"193" + "p_code":"202", + "code":"210" }, { "desc":"DRS supports many-to-one scenarios during migration of different types of instances and tables to suit your service requirements.To ensure that there is sufficient space ", @@ -1742,8 +1895,8 @@ "title":"Constraints and Operation Suggestions on Many-to-One Scenario", "uri":"drs_16_0120.html", "doc_type":"usermanual", - "p_code":"185", - "code":"194" + "p_code":"202", + "code":"211" }, { "desc":"You can view DRS operation logs on the Cloud Trace Service (CTS) console.Click the username in the upper right corner and select Operation Log from the drop-down list.", @@ -1751,8 +1904,8 @@ "title":"Where Can I View DRS Operation Logs?", "uri":"drs_01_0101.html", "doc_type":"usermanual", - "p_code":"185", - "code":"195" + "p_code":"202", + "code":"212" }, { "desc":"No. DRS cannot restart a completed task.", @@ -1760,8 +1913,8 @@ "title":"Can a Completed Task Be Restarted?", "uri":"drs_16_1140.html", "doc_type":"usermanual", - "p_code":"185", - "code":"196" + "p_code":"202", + "code":"213" }, { "desc":"You can reset a task when the task is suspended or fails. Resetting a task does not clear the destination database. You can determine whether to clear the destination dat", @@ -1769,8 +1922,8 @@ "title":"What Are the Differences Between Resetting a Task and Recreating a Task?", "uri":"drs_16_1143.html", "doc_type":"usermanual", - "p_code":"185", - "code":"197" + "p_code":"202", + "code":"214" }, { "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.", @@ -1778,8 +1931,8 @@ "title":"Delay", "uri":"drs_16_1156.html", "doc_type":"usermanual", - "p_code":"138", - "code":"198" + "p_code":"155", + "code":"215" }, { "desc":"Recovery Time Objective (RTO) is duration of time within which transactions on the DRS instance are transmitted and replayed to the destination database during incrementa", @@ -1787,8 +1940,8 @@ "title":"Why Does the Delay of DR Tasks Increase?", "uri":"drs_16_1148.html", "doc_type":"usermanual", - "p_code":"198", - "code":"199" + "p_code":"215", + "code":"216" }, { "desc":"Migration from MongoDB to DDSMigration from DDS to MongoDBTo ensure the performance of migration, synchronization, or disaster recovery, DRS performs concurrent replay at", @@ -1796,8 +1949,8 @@ "title":"Why Is the Delay High In Migration from MongoDB to DDS?", "uri":"drs_16_1157.html", "doc_type":"usermanual", - "p_code":"198", - "code":"200" + "p_code":"215", + "code":"217" }, { "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.", @@ -1806,7 +1959,7 @@ "uri":"drs_13_0001.html", "doc_type":"usermanual", "p_code":"", - "code":"201" + "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.", @@ -1814,8 +1967,8 @@ "title":"Solutions to Failed Check Items", "uri":"drs_11_0001.html", "doc_type":"usermanual", - "p_code":"201", - "code":"202" + "p_code":"218", + "code":"219" }, { "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.", @@ -1823,8 +1976,8 @@ "title":"Disk Space", "uri":"drs_12_0005.html", "doc_type":"usermanual", - "p_code":"202", - "code":"203" + "p_code":"219", + "code":"220" }, { "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.", @@ -1832,8 +1985,8 @@ "title":"Checking Whether the Destination Database Has Sufficient Storage Space", "uri":"drs_11_0010.html", "doc_type":"usermanual", - "p_code":"203", - "code":"204" + "p_code":"220", + "code":"221" }, { "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.", @@ -1841,8 +1994,8 @@ "title":"Checking Whether the Destination Server Has Sufficient Storage Space", "uri":"drs_11_0076.html", "doc_type":"usermanual", - "p_code":"203", - "code":"205" + "p_code":"220", + "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.", @@ -1850,8 +2003,8 @@ "title":"Database Parameters", "uri":"drs_12_0008.html", "doc_type":"usermanual", - "p_code":"202", - "code":"206" + "p_code":"219", + "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.", @@ -1859,8 +2012,8 @@ "title":"Checking Whether the Source Database Binlog Is Enabled", "uri":"drs_11_0014.html", "doc_type":"usermanual", - "p_code":"206", - "code":"207" + "p_code":"223", + "code":"224" }, { "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.", @@ -1868,8 +2021,8 @@ "title":"Checking Whether the Source Database Binlog Is Row-Based", "uri":"drs_11_0015.html", "doc_type":"usermanual", - "p_code":"206", - "code":"208" + "p_code":"223", + "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.", @@ -1877,8 +2030,8 @@ "title":"Checking Whether the Binlog Retention Period Is Set on the Source Database", "uri":"drs_11_0016.html", "doc_type":"usermanual", - "p_code":"206", - "code":"209" + "p_code":"223", + "code":"226" }, { "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.", @@ -1886,8 +2039,8 @@ "title":"Checking Whether the Source and Destination Database Character Sets Are Consistent", "uri":"drs_11_0013.html", "doc_type":"usermanual", - "p_code":"206", - "code":"210" + "p_code":"223", + "code":"227" }, { "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.", @@ -1895,8 +2048,8 @@ "title":"Checking Whether the Source Database server_id Meets the Incremental Migration Requirements", "uri":"drs_11_0018.html", "doc_type":"usermanual", - "p_code":"206", - "code":"211" + "p_code":"223", + "code":"228" }, { "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.", @@ -1904,8 +2057,8 @@ "title":"Checking Whether the Source and Destination Database Table Names Are Consistent in Case Sensitivity", "uri":"drs_11_0019.html", "doc_type":"usermanual", - "p_code":"206", - "code":"212" + "p_code":"223", + "code":"229" }, { "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.", @@ -1913,8 +2066,8 @@ "title":"Checking Whether the Source Database Contains Object Names with Non-ASCII Characters", "uri":"drs_11_0022.html", "doc_type":"usermanual", - "p_code":"206", - "code":"213" + "p_code":"223", + "code":"230" }, { "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.", @@ -1922,8 +2075,8 @@ "title":"Checking Whether the TIME_ZONE Values of the Source and Destination Databases Are the Same", "uri":"drs_11_0023.html", "doc_type":"usermanual", - "p_code":"206", - "code":"214" + "p_code":"223", + "code":"231" }, { "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.", @@ -1931,8 +2084,8 @@ "title":"Checking Whether the COLLATION_SERVER Values of the Source and Destination Databases Are the Same", "uri":"drs_11_0024.html", "doc_type":"usermanual", - "p_code":"206", - "code":"215" + "p_code":"223", + "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.", @@ -1940,8 +2093,8 @@ "title":"Checking Whether the SERVER_UUID Values of the Source and Destination Databases Are the Same", "uri":"drs_11_0025.html", "doc_type":"usermanual", - "p_code":"206", - "code":"216" + "p_code":"223", + "code":"233" }, { "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.", @@ -1949,8 +2102,8 @@ "title":"Checking Whether the SERVER_ID Values of the Source and Destination Databases Are Different", "uri":"drs_11_0044.html", "doc_type":"usermanual", - "p_code":"206", - "code":"217" + "p_code":"223", + "code":"234" }, { "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.", @@ -1958,8 +2111,8 @@ "title":"Checking Whether the Source Database Contains Invalid sql_mode Values", "uri":"drs_11_0049.html", "doc_type":"usermanual", - "p_code":"206", - "code":"218" + "p_code":"223", + "code":"235" }, { "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.", @@ -1967,8 +2120,8 @@ "title":"Checking Whether the SQL_MODE Values of the Source and Destination Databases Are the Same", "uri":"drs_11_0059.html", "doc_type":"usermanual", - "p_code":"206", - "code":"219" + "p_code":"223", + "code":"236" }, { "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.", @@ -1976,8 +2129,8 @@ "title":"Checking Whether the sql_mode Value in the Destination Database Is Not NO_ENGINE_SUBSTITUTION", "uri":"drs_11_0228.html", "doc_type":"usermanual", - "p_code":"206", - "code":"220" + "p_code":"223", + "code":"237" }, { "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.", @@ -1985,8 +2138,8 @@ "title":"Checking Whether the innodb_strict_mode Values of the Source and Destination Databases Are the Same", "uri":"drs_11_0060.html", "doc_type":"usermanual", - "p_code":"206", - "code":"221" + "p_code":"223", + "code":"238" }, { "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.", @@ -1994,8 +2147,8 @@ "title":"Checking Whether the max_wal_senders Value of the Source Database Is Correctly Configured", "uri":"drs_11_0053.html", "doc_type":"usermanual", - "p_code":"206", - "code":"222" + "p_code":"223", + "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.", @@ -2003,8 +2156,8 @@ "title":"Checking Whether the WAL_LEVEL Value in the Source Database Is Correct", "uri":"drs_11_0054.html", "doc_type":"usermanual", - "p_code":"206", - "code":"223" + "p_code":"223", + "code":"240" }, { "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.", @@ -2012,8 +2165,8 @@ "title":"Checking Whether the MAX_REPLICATION_SLOTS Value in the Source Database Is Correct", "uri":"drs_11_0055.html", "doc_type":"usermanual", - "p_code":"206", - "code":"224" + "p_code":"223", + "code":"241" }, { "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.", @@ -2021,8 +2174,8 @@ "title":"Checking Whether the Source Database Is on Standby", "uri":"drs_11_0056.html", "doc_type":"usermanual", - "p_code":"206", - "code":"225" + "p_code":"223", + "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.", @@ -2030,8 +2183,8 @@ "title":"Checking Whether the log_slave_updates Value of the Source Database Is Correctly Configured", "uri":"drs_11_0061.html", "doc_type":"usermanual", - "p_code":"206", - "code":"226" + "p_code":"223", + "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.", @@ -2039,8 +2192,8 @@ "title":"Checking Whether the BLOCK_SIZE Value of the Source Database Is the Same as That of the Destination Database", "uri":"drs_11_0063.html", "doc_type":"usermanual", - "p_code":"206", - "code":"227" + "p_code":"223", + "code":"244" }, { "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.", @@ -2048,8 +2201,8 @@ "title":"Checking Whether the binlog_row_image Value is FULL", "uri":"drs_11_0064.html", "doc_type":"usermanual", - "p_code":"206", - "code":"228" + "p_code":"223", + "code":"245" }, { "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.", @@ -2057,8 +2210,8 @@ "title":"Checking Whether the Transaction Isolation Levels are Consistent", "uri":"drs_11_0453.html", "doc_type":"usermanual", - "p_code":"206", - "code":"229" + "p_code":"223", + "code":"246" }, { "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.", @@ -2066,8 +2219,8 @@ "title":"Checking Whether the lc_monetary Values of the Source and Destination Databases Are the Same", "uri":"drs_11_0038.html", "doc_type":"usermanual", - "p_code":"206", - "code":"230" + "p_code":"223", + "code":"247" }, { "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.", @@ -2075,8 +2228,8 @@ "title":"Checking Whether the Source Database Contains Trigger Names with Non-ASCII Characters", "uri":"drs_11_0073.html", "doc_type":"usermanual", - "p_code":"206", - "code":"231" + "p_code":"223", + "code":"248" }, { "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.", @@ -2084,8 +2237,8 @@ "title":"Checking Whether the Source Database Collections Contain More Than 10 Indexes", "uri":"drs_11_0200.html", "doc_type":"usermanual", - "p_code":"206", - "code":"232" + "p_code":"223", + "code":"249" }, { "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.", @@ -2093,8 +2246,17 @@ "title":"Checking Whether log_bin_trust_function_creators Is Set to On in Both the Source and Destination Databases", "uri":"drs_11_0227.html", "doc_type":"usermanual", - "p_code":"206", - "code":"233" + "p_code":"223", + "code":"250" + }, + { + "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":"drs", + "title":"Checking Whether GTID Is Enabled for the Source Database", + "uri":"drs_11_0226.html", + "doc_type":"usermanual", + "p_code":"223", + "code":"251" }, { "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.", @@ -2102,8 +2264,8 @@ "title":"Checking Whether log_bin_trust_function_creators Is Set to On in the Destination Database", "uri":"drs_11_0225.html", "doc_type":"usermanual", - "p_code":"206", - "code":"234" + "p_code":"223", + "code":"252" }, { "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.", @@ -2111,8 +2273,8 @@ "title":"Checking Whether the max_allowed_packet Value of the Destination Database Is too Small", "uri":"drs_15_0017.html", "doc_type":"usermanual", - "p_code":"206", - "code":"235" + "p_code":"223", + "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.", @@ -2120,8 +2282,8 @@ "title":"Checking Whether the Source Database Character Set Is Supported", "uri":"drs_03_043.html", "doc_type":"usermanual", - "p_code":"206", - "code":"236" + "p_code":"223", + "code":"254" }, { "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.", @@ -2129,8 +2291,8 @@ "title":"Checking Whether the Databases and Tables Exist", "uri":"drs_03_045.html", "doc_type":"usermanual", - "p_code":"206", - "code":"237" + "p_code":"223", + "code":"255" }, { "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.", @@ -2138,8 +2300,8 @@ "title":"Checking Whether session_replication_role of the Destination Database Is correctly Set", "uri":"drs_03_1130.html", "doc_type":"usermanual", - "p_code":"206", - "code":"238" + "p_code":"223", + "code":"256" }, { "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.", @@ -2147,8 +2309,8 @@ "title":"Checking Whether the MongoDB Instance Type Matches the Migration Mode", "uri":"drs_11_0066.html", "doc_type":"usermanual", - "p_code":"206", - "code":"239" + "p_code":"223", + "code":"257" }, { "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.", @@ -2156,8 +2318,8 @@ "title":"Checking the Physical Standby Database", "uri":"drs_11_0465.html", "doc_type":"usermanual", - "p_code":"206", - "code":"240" + "p_code":"223", + "code":"258" }, { "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.", @@ -2165,8 +2327,8 @@ "title":"Checking Whether the Values of group_concat_max_len Are Consistent", "uri":"drs_11_0469.html", "doc_type":"usermanual", - "p_code":"206", - "code":"241" + "p_code":"223", + "code":"259" }, { "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.", @@ -2174,8 +2336,8 @@ "title":"Checking Whether the Character Sets Are Compatible", "uri":"drs_11_0471.html", "doc_type":"usermanual", - "p_code":"206", - "code":"242" + "p_code":"223", + "code":"260" }, { "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.", @@ -2183,8 +2345,8 @@ "title":"Checking Whether the Source Database Contains Unsupported Table Field Types", "uri":"drs_11_0481.html", "doc_type":"usermanual", - "p_code":"206", - "code":"243" + "p_code":"223", + "code":"261" }, { "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.", @@ -2192,8 +2354,8 @@ "title":"Checking Replication Attribute of Primary Key Columns", "uri":"drs_11_0482.html", "doc_type":"usermanual", - "p_code":"206", - "code":"244" + "p_code":"223", + "code":"262" }, { "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.", @@ -2201,8 +2363,8 @@ "title":"Source DB Instance Statuses", "uri":"drs_11_0464.html", "doc_type":"usermanual", - "p_code":"202", - "code":"245" + "p_code":"219", + "code":"263" }, { "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.", @@ -2210,8 +2372,8 @@ "title":"Checking Whether the Source and Destination Databases Are of the Same Type", "uri":"drs_11_0046.html", "doc_type":"usermanual", - "p_code":"245", - "code":"246" + "p_code":"263", + "code":"264" }, { "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.", @@ -2219,8 +2381,8 @@ "title":"Checking Whether the ChangeStream API of the source DB instance is available", "uri":"drs_11_0463.html", "doc_type":"usermanual", - "p_code":"245", - "code":"247" + "p_code":"263", + "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.", @@ -2228,8 +2390,8 @@ "title":"Destination DB Instance Statuses", "uri":"drs_12_0006.html", "doc_type":"usermanual", - "p_code":"202", - "code":"248" + "p_code":"219", + "code":"266" }, { "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.", @@ -2237,8 +2399,8 @@ "title":"Checking Whether the Destination Database Is Involved in Another Migration Task", "uri":"drs_11_0011.html", "doc_type":"usermanual", - "p_code":"248", - "code":"249" + "p_code":"266", + "code":"267" }, { "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.", @@ -2246,8 +2408,8 @@ "title":"Checking Whether the Destination Database Has a Read Replica", "uri":"drs_11_0050.html", "doc_type":"usermanual", - "p_code":"248", - "code":"250" + "p_code":"266", + "code":"268" }, { "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.", @@ -2255,8 +2417,8 @@ "title":"Checking Whether the Extensions Are Supported", "uri":"drs_11_0041.html", "doc_type":"usermanual", - "p_code":"248", - "code":"251" + "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.", @@ -2264,8 +2426,8 @@ "title":"Checking Whether Destination Contains the Configured Database", "uri":"drs_11_0075.html", "doc_type":"usermanual", - "p_code":"248", - "code":"252" + "p_code":"266", + "code":"270" }, { "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.", @@ -2273,8 +2435,8 @@ "title":"Checking Whether the Destination DB Instance Is Available", "uri":"drs_11_0230.html", "doc_type":"usermanual", - "p_code":"248", - "code":"253" + "p_code":"266", + "code":"271" }, { "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.", @@ -2282,8 +2444,8 @@ "title":"Database User Permissions", "uri":"drs_12_0007.html", "doc_type":"usermanual", - "p_code":"202", - "code":"254" + "p_code":"219", + "code":"272" }, { "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.", @@ -2291,8 +2453,8 @@ "title":"Checking Whether the Source Database User Has Sufficient Permissions", "uri":"drs_11_0009.html", "doc_type":"usermanual", - "p_code":"254", - "code":"255" + "p_code":"272", + "code":"273" }, { "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.", @@ -2300,8 +2462,8 @@ "title":"Checking Whether the Destination Database User Has Sufficient Permissions", "uri":"drs_11_0008.html", "doc_type":"usermanual", - "p_code":"254", - "code":"256" + "p_code":"272", + "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.", @@ -2309,8 +2471,8 @@ "title":"Database Versions", "uri":"drs_12_0004.html", "doc_type":"usermanual", - "p_code":"202", - "code":"257" + "p_code":"219", + "code":"275" }, { "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.", @@ -2318,8 +2480,8 @@ "title":"Checking Whether the Source Database Version Is Supported", "uri":"drs_11_0005.html", "doc_type":"usermanual", - "p_code":"257", - "code":"258" + "p_code":"275", + "code":"276" }, { "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.", @@ -2327,8 +2489,8 @@ "title":"Checking Whether the Destination Database Version Is Supported", "uri":"drs_11_0006.html", "doc_type":"usermanual", - "p_code":"257", - "code":"259" + "p_code":"275", + "code":"277" }, { "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.", @@ -2336,8 +2498,8 @@ "title":"Checking Whether the Migration Is from an Earlier Database Version to the Same or a Later Version", "uri":"drs_11_0007.html", "doc_type":"usermanual", - "p_code":"257", - "code":"260" + "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.", @@ -2345,8 +2507,8 @@ "title":"Networks", "uri":"drs_12_0003.html", "doc_type":"usermanual", - "p_code":"202", - "code":"261" + "p_code":"219", + "code":"279" }, { "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.", @@ -2354,8 +2516,8 @@ "title":"Checking Whether the Source Database Is Connected", "uri":"drs_precheck.html", "doc_type":"usermanual", - "p_code":"261", - "code":"262" + "p_code":"279", + "code":"280" }, { "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.", @@ -2363,8 +2525,8 @@ "title":"Checking Whether the Destination Database Is Connected", "uri":"drs_11_0002.html", "doc_type":"usermanual", - "p_code":"261", - "code":"263" + "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.", @@ -2372,8 +2534,8 @@ "title":"Checking Whether the Destination Database Can Connect to the Source Database", "uri":"drs_11_0003.html", "doc_type":"usermanual", - "p_code":"261", - "code":"264" + "p_code":"279", + "code":"282" }, { "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.", @@ -2381,8 +2543,8 @@ "title":"Database Objects", "uri":"drs_11_0067.html", "doc_type":"usermanual", - "p_code":"202", - "code":"265" + "p_code":"219", + "code":"283" }, { "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.", @@ -2390,8 +2552,8 @@ "title":"Checking Whether the Source Database Contains a MyISAM Table", "uri":"drs_11_0048.html", "doc_type":"usermanual", - "p_code":"265", - "code":"266" + "p_code":"283", + "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.", @@ -2399,8 +2561,8 @@ "title":"Checking Whether the Source Database Contains the Functions or Stored Procedures that the Source Database User Is Not Authorized to Migrate", "uri":"drs_11_0080.html", "doc_type":"usermanual", - "p_code":"265", - "code":"267" + "p_code":"283", + "code":"285" }, { "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.", @@ -2408,8 +2570,8 @@ "title":"Checking Whether the Source Database Tables Use Storage Engines Not Supported by the Destination Database", "uri":"drs_11_0117.html", "doc_type":"usermanual", - "p_code":"265", - "code":"268" + "p_code":"283", + "code":"286" }, { "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.", @@ -2417,8 +2579,8 @@ "title":"Checking Whether the Source Database Tables Contain Primary Keys", "uri":"drs_15_0020.html", "doc_type":"usermanual", - "p_code":"265", - "code":"269" + "p_code":"283", + "code":"287" }, { "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.", @@ -2426,8 +2588,8 @@ "title":"Checking Whether the Source Database Contains Triggers or Events", "uri":"drs_15_0021.html", "doc_type":"usermanual", - "p_code":"265", - "code":"270" + "p_code":"283", + "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.", @@ -2435,8 +2597,8 @@ "title":"Database Configuration Items", "uri":"drs_11_0068.html", "doc_type":"usermanual", - "p_code":"202", - "code":"271" + "p_code":"219", + "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.", @@ -2444,8 +2606,8 @@ "title":"Checking Whether the Source Database Name Is Valid", "uri":"drs_11_0045.html", "doc_type":"usermanual", - "p_code":"271", - "code":"272" + "p_code":"289", + "code":"290" }, { "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.", @@ -2453,8 +2615,8 @@ "title":"Checking Whether the Source Database Table Name Is Valid", "uri":"drs_11_0105.html", "doc_type":"usermanual", - "p_code":"271", - "code":"273" + "p_code":"289", + "code":"291" }, { "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.", @@ -2462,8 +2624,8 @@ "title":"Checking Whether the Source Database View Name Is Valid", "uri":"drs_11_0072.html", "doc_type":"usermanual", - "p_code":"271", - "code":"274" + "p_code":"289", + "code":"292" }, { "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.", @@ -2471,8 +2633,8 @@ "title":"Checking Whether the Shard Key Can Be Obtained from the Source Database", "uri":"drs_11_0069.html", "doc_type":"usermanual", - "p_code":"271", - "code":"275" + "p_code":"289", + "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.", @@ -2480,8 +2642,8 @@ "title":"Conflicts", "uri":"drs_11_0070.html", "doc_type":"usermanual", - "p_code":"202", - "code":"276" + "p_code":"219", + "code":"294" }, { "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.", @@ -2489,8 +2651,8 @@ "title":"Checking Whether the Names of the Source and Destination Databases Are the Same", "uri":"drs_11_0004.html", "doc_type":"usermanual", - "p_code":"276", - "code":"277" + "p_code":"294", + "code":"295" }, { "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.", @@ -2498,8 +2660,8 @@ "title":"Checking Whether the Destination Database Contains a Non-Empty Collection with the Same Name As the Source Database", "uri":"drs_11_0043.html", "doc_type":"usermanual", - "p_code":"276", - "code":"278" + "p_code":"294", + "code":"296" }, { "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.", @@ -2507,8 +2669,8 @@ "title":"SSL Connections", "uri":"drs_11_0071.html", "doc_type":"usermanual", - "p_code":"202", - "code":"279" + "p_code":"219", + "code":"297" }, { "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.", @@ -2516,8 +2678,8 @@ "title":"Checking Whether the SSL Connection Is Correctly Configured", "uri":"drs_11_0017.html", "doc_type":"usermanual", - "p_code":"279", - "code":"280" + "p_code":"297", + "code":"298" }, { "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.", @@ -2525,8 +2687,8 @@ "title":"Checking Whether the SSL Connection Is Enabled for the Source Database", "uri":"drs_11_0042.html", "doc_type":"usermanual", - "p_code":"279", - "code":"281" + "p_code":"297", + "code":"299" }, { "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.", @@ -2534,8 +2696,8 @@ "title":"Checking Whether the SSL Certificate of the Destination Database Exists", "uri":"drs_11_0107.html", "doc_type":"usermanual", - "p_code":"279", - "code":"282" + "p_code":"297", + "code":"300" }, { "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.", @@ -2543,8 +2705,8 @@ "title":"Object Dependencies", "uri":"drs_11_0220.html", "doc_type":"usermanual", - "p_code":"202", - "code":"283" + "p_code":"219", + "code":"301" }, { "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.", @@ -2552,8 +2714,8 @@ "title":"Checking Whether Referenced Tables Are Selected for Migration", "uri":"drs_11_0222.html", "doc_type":"usermanual", - "p_code":"283", - "code":"284" + "p_code":"301", + "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.", @@ -2561,8 +2723,8 @@ "title":"Failure Cases", "uri":"drs_02_0488.html", "doc_type":"usermanual", - "p_code":"201", - "code":"285" + "p_code":"218", + "code":"303" }, { "desc":"When you migrate full backups from self-built OBS buckets to clouds, the following error message is displayed: restore:null.The possible causes are as follows:Backup file", @@ -2570,8 +2732,8 @@ "title":"Backup Migration Failed Because Backup Files Cannot Be Found", "uri":"drs_13_0002.html", "doc_type":"usermanual", - "p_code":"285", - "code":"286" + "p_code":"303", + "code":"304" }, { "desc":"When you migrate full backups from self-built OBS buckets to clouds, the system displays an error message indicating that the migration failed because the source database", @@ -2579,8 +2741,8 @@ "title":"Backup Migration Failed Because a Backup Database Cannot Be Found in the Backup Files", "uri":"drs_13_0005.html", "doc_type":"usermanual", - "p_code":"285", - "code":"287" + "p_code":"303", + "code":"305" }, { "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.", @@ -2589,6 +2751,6 @@ "uri":"drs_change_history.html", "doc_type":"usermanual", "p_code":"", - "code":"288" + "code":"306" } ] \ No newline at end of file diff --git a/docs/drs/umn/drs_01_0001.html b/docs/drs/umn/drs_01_0001.html index 4474a4088..58b18bf7f 100644 --- a/docs/drs/umn/drs_01_0001.html +++ b/docs/drs/umn/drs_01_0001.html @@ -13,6 +13,8 @@
  • Mapping Data Types
    • +
  • Specification Description
    +
  • Basic Concepts
  • Security Suggestions
    diff --git a/docs/drs/umn/drs_01_0002.html b/docs/drs/umn/drs_01_0002.html index 5e33d3084..885cb7d3e 100644 --- a/docs/drs/umn/drs_01_0002.html +++ b/docs/drs/umn/drs_01_0002.html @@ -1,7 +1,7 @@

    What Is DRS?

    -

    DRS is a stable, efficient, and easy-to-use cloud service for database migration and synchronization in real time.

    +

    DRS is a stable, efficient, and easy-to-use cloud service for database migration and synchronization in real time.

    It simplifies data migration processes and reduces migration costs.

    You can use DRS to quickly transmit data between different DB engines.

    Real-Time Migration

    With DRS, you can migrate data from sources to destinations in real time. You create a replication instance to connect to both the source and destination and configure objects to be migrated. DRS will help you compare metrics and data between source and destination, so you can determine the best time to switch to the destination database while minimizing service downtime.

    diff --git a/docs/drs/umn/drs_01_0004.html b/docs/drs/umn/drs_01_0004.html index c6ca137a9..2a9a5a422 100644 --- a/docs/drs/umn/drs_01_0004.html +++ b/docs/drs/umn/drs_01_0004.html @@ -9,8 +9,8 @@

    Supported network types during migration from MongoDB databases to DDS:

    • VPC
    • VPN
    • Direct Connect
    • Public network
    -

    GaussDB(for MySQL)

    DRS can migrate data from your databases to GaussDB(for MySQL) on the current cloud. For more information about GaussDB(for MySQL), see GaussDB(for MySQL) User Guide.

    -

    Supported network types during migration to GaussDB(for MySQL) on the current cloud:

    +

    TaurusDB

    DRS can migrate data from your databases to TaurusDB on the current cloud. For more information about TaurusDB, see TaurusDB User Guide.

    +

    Supported network types during migration to TaurusDB on the current cloud:

    • VPC
    • VPN
    • Direct Connect
    • Public network

    GaussDB

    DRS can migrate data from your databases to GaussDB on the current cloud. For more information about GaussDB, see GaussDB User Guide.

    diff --git a/docs/drs/umn/drs_01_0005.html b/docs/drs/umn/drs_01_0005.html index f64bab655..273854838 100644 --- a/docs/drs/umn/drs_01_0005.html +++ b/docs/drs/umn/drs_01_0005.html @@ -27,12 +27,12 @@
    Figure 1 Region and AZ

    Project

    A project corresponds to a region. Projects group and isolate resources (including compute, storage, and network resources) across physical regions. Users can be granted permissions in a default project to access all resources in the region associated with the project. If you need more refined access control, create subprojects under a default project and create resources in subprojects. Then you can assign users the permissions required to access only the resources in the specific subprojects.

    -
    Figure 2 Project isolating model
    +
    Figure 2 Project isolating model

    Account Entrustment

    DRS will entrust your account to the administrator to implement some functions. For example, if you enable scheduled startup tasks, DRS will automatically entrust your account to DRS administrator op_svc_rds during the task creation to implement automated management on the scheduled tasks.

    Account entrustment can be implemented in the same region only.

    -

    Temporary Accounts

    To ensure that your database can be successfully migrated to RDS MySQL DB instances, DRS automatically creates temporary accounts drsFull and drsIncremental in the destination database during full migration and incremental migration, respectively. After the migration task is complete, DRS automatically deletes the temporary account.

    +

    Temporary Accounts

    To ensure that your database can be successfully migrated to RDS for MySQL DB instances, DRS automatically creates temporary accounts drsFull and drsIncremental in the destination database during full migration and incremental migration, respectively. After the migration task is complete, DRS automatically deletes the temporary account.

    Attempting to delete, rename, or change the passwords or permissions for these accounts will cause task errors.

    diff --git a/docs/drs/umn/drs_01_0201.html b/docs/drs/umn/drs_01_0201.html index 4db917ab6..c00956126 100644 --- a/docs/drs/umn/drs_01_0201.html +++ b/docs/drs/umn/drs_01_0201.html @@ -1,13 +1,13 @@

    Permissions Management

    -

    If you need to assign different permissions to employees in your enterprise to access your DRS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to have a secure access to cloud resources.

    -

    With IAM, you can use your cloud account to create IAM users for your employees, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use DRS resources but must not delete DRS tasks or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DRS resources.

    +

    If you need to assign different permissions to employees in your enterprise to access your DRS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your cloud resources.

    +

    With IAM, you can use your cloud account to create IAM users for your employees, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use DRS but must not delete DRS resources or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DRS resources.

    If your account does not need individual IAM users for permissions management, you may skip over this topic.

    IAM can be used free of charge. You pay only for the resources in your cloud account. For more information about IAM, see IAM Service Overview.

    DRS Permissions

    By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

    -

    DRS is a project-level service deployed and accessed in specific physical regions. To assign DRS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing DRS, users need to switch to a region where they have been authorized to use DRS.

    -
    You can grant users permissions by using roles and policies.
    • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
    • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most fine-grained policies are API-based.
    +

    DRS is a project-level service deployed and accessed in specific physical regions. To assign DRS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If you select All projects, the permissions will take effect for user groups in all region-specific projects. When accessing DRS, users need to switch to a region where they have been authorized to use DRS.

    +
    You can grant users permissions by using roles and policies.
    • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles which the permissions depend on to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
    • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most fine-grained policies are API-based.

    Table 1 lists all the system policies supported by DRS.

    diff --git a/docs/drs/umn/drs_01_0301.html b/docs/drs/umn/drs_01_0301.html index b34762da5..a8d7fb462 100644 --- a/docs/drs/umn/drs_01_0301.html +++ b/docs/drs/umn/drs_01_0301.html @@ -20,21 +20,21 @@

    MySQL->MySQL

    -
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS MySQL DB instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS for MySQL DB instances
    -

    RDS MySQL DB instances

    +

    RDS for MySQL DB instances

    • Single DB instance
    • Primary/Standby DB instance

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    • On-premises databases
    -
    • ECS databases
    • Databases on other clouds
    • RDS MySQL DB instances
    • GaussDB(for MySQL) instances
    +
    • ECS databases
    • Databases on other clouds
    • RDS for MySQL DB instances
    • TaurusDB instances
    -

    GaussDB(for MySQL) primary/standby

    +

    TaurusDB Cluster

    • Primary/Standby DB instance
    @@ -50,11 +50,11 @@
    • Cluster
    • Replica set
    • Single node
    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    -

    RDS MySQL DB instances

    +

    RDS for MySQL DB instances

    • On-premises databases
    • ECS databases
    • Databases on other clouds
    @@ -62,7 +62,7 @@
    • Single DB instance
    • Primary/Standby DB instance
    -

    From the cloud

    +

    Out of the cloud

    DDS->MongoDB

    @@ -111,21 +111,21 @@

    MongoDB->DDS

    -
    • MongoDB 3.2.x
    • MongoDB 3.4.x
    • MongoDB 3.6.x
    • MongoDB 4.0.x
    • MongoDB 4.2.x
    • MongoDB 4.4.x
    +
    • MongoDB 3.2.x
    • MongoDB 3.4.x
    • MongoDB 3.6.x
    • MongoDB 4.0.x
    • MongoDB 4.2.x
    • MongoDB 4.4.x
    -
    • DDS 3.2.x
    • DDS 3.4.x
    • DDS 4.0.x
    • DDS 4.2.x
    • DDS 4.4.x
    +
    • DDS 3.2.x
    • DDS 3.4.x
    • DDS 4.0.x
    • DDS 4.2.x
    • DDS 4.4.x

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    • MySQL 5.6.x
    • MySQL 5.7.x
    • MySQL 8.0.x
    -

    GaussDB(for MySQL)-MySQL 8.0

    +

    TaurusDB-MySQL 8.0

    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    @@ -134,13 +134,13 @@
    • MySQL 5.6.x
    • MySQL 5.7.x
    • MySQL 8.0.x
    -

    From the cloud

    +

    Out of the cloud

    DDS->MongoDB

    -
    • DDS 3.2.x
    • DDS 3.4.x
    • DDS 4.0.x
    • DDS 4.2.x
    • DDS 4.4.x
    +
    • DDS 3.2.x
    • DDS 3.4.x
    • DDS 4.0.x
    • DDS 4.2.x
    • DDS 4.4.x
    -
    • MongoDB 3.2.x
    • MongoDB 3.4.x
    • MongoDB 3.6.x
    • MongoDB 4.0.x
    • MongoDB 4.2.x
    • MongoDB 4.4.x
    +
    • MongoDB 3.2.x
    • MongoDB 3.4.x
    • MongoDB 3.6.x
    • MongoDB 4.0.x
    • MongoDB 4.2.x
    • MongoDB 4.4.x

    Self-built -> Self-built

    @@ -181,7 +181,7 @@

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    Supported

    @@ -195,12 +195,11 @@
    • Replica set -> Single node
    • Replica set -> Replica set
    • Replica set -> Cluster
    • Single node -> Single node
    • Single node -> Replica set
    • Single node -> Cluster
    • Cluster -> Cluster
    • Replica set -> Single node
    • Replica set -> Replica set
    • Replica set -> Cluster
    • Single node -> Single node
    • Single node -> Replica set
    • Single node -> Cluster
    -
    NOTE:

    If you need to perform an incremental migration for a single-node instance, the source database must be the DDS single-node instance.

    - +
    NOTE:
    • If you need to perform an incremental migration for a single-node instance, the source database must be the DDS single-node instance.
    • The source cannot be a GaussDB(for Mongo) instance.
    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    @@ -209,7 +208,7 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    DDS->MongoDB

    @@ -247,7 +246,7 @@

    Migrations between cloud databases in the same region

    -
    • The source and destination databases must be in the same region.
    • The source and destination databases can be in either the same VPC or in different VPCs.
    • If source and destination databases are in the same VPC, they can communicate with each other by default. Therefore, you do not need to configure a security group.
    • If the source and destination databases are not in the same VPC, the CIDR blocks of the source and destination databases cannot be duplicated or overlapped, and the source and destination databases are connected through a VPC peering connection. DRS automatically establishes a VPC peering connection through a single IP address when you test the network connectivity.
    +
    • The source and destination databases must be in the same region.
    • The source and destination databases can be in either the same VPC or in different VPCs.
    • If source and destination databases are in the same VPC, they can communicate with each other by default. Therefore, you do not need to configure a security group.
    • If the source and destination databases are not in the same VPC, the CIDR blocks of the source and destination databases cannot be duplicated or overlapped, and the source and destination databases are connected through a VPC peering connection. DRS automatically establishes a route through a single IP address when you test the network connectivity.

    VPN

    @@ -305,7 +304,7 @@

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    Supported

    @@ -325,7 +324,7 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    @@ -336,7 +335,7 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    DDS->MongoDB

    @@ -389,7 +388,7 @@

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    Supported

    @@ -409,7 +408,7 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    @@ -420,7 +419,7 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    DDS->MongoDB

    diff --git a/docs/drs/umn/drs_01_0302.html b/docs/drs/umn/drs_01_0302.html index 079035fe5..34075c7d0 100644 --- a/docs/drs/umn/drs_01_0302.html +++ b/docs/drs/umn/drs_01_0302.html @@ -20,31 +20,31 @@

    MySQL->MySQL

    -
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS MySQL DB instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS for MySQL DB instances
    -

    RDS MySQL DB instances

    +

    RDS for MySQL DB instances

    • Single DB instance
    • Primary/Standby DB instance

    To the cloud

    -

    MySQL-> GaussDB distributed

    +

    MySQL -> GaussDB Distributed

    -
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS MySQL DB instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS for MySQL DB instances
    -

    GaussDB distributed

    +

    GaussDB Distributed

    • Cluster

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    -
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS MySQL DB instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS for MySQL DB instances
    -

    GaussDB(for MySQL) primary/standby

    +

    TaurusDB Cluster

    • Primary/Standby DB instance
    @@ -53,9 +53,9 @@

    PostgreSQL->PostgreSQL

    -
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS PostgreSQL DB instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS for PostgreSQL DB instances
    -

    RDS PostgreSQL DB instances

    +

    RDS for PostgreSQL DB instances

    • Single DB instance
    • Primary/Standby DB instance
    @@ -66,7 +66,7 @@
    • On-premises databases
    • ECS databases
    -

    RDS PostgreSQL DB instances

    +

    RDS for PostgreSQL DB instances

    • Single DB instance
    • Primary/Standby DB instance
    @@ -82,35 +82,35 @@

    Clusters

    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    -

    RDS MySQL DB instances

    +

    RDS for MySQL DB instances

    -
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS MySQL DB instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS for MySQL DB instances

    -

    -

    From the cloud

    +

    Out of the cloud

    MySQL->Kafka

    -

    RDS MySQL DB instances

    +

    RDS for MySQL DB instances

    -
    • Kafka
    • DMS for Kafka
    +

    Kafka

    • Cluster
    • Single node
    -

    From the cloud

    +

    Out of the cloud

    -

    GaussDB distributed -> MySQL

    +

    GaussDB Distributed -> MySQL

    -

    GaussDB distributed

    +

    GaussDB Distributed

    -
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS MySQL instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS for MySQL DB instances

    -

    @@ -132,7 +132,7 @@
    • On-premises databases
    • ECS databases
    -
    • Kafka
    • DMS for Kafka
    +

    Kafka

    • Cluster
    • Single node
    @@ -175,7 +175,7 @@

    To the cloud

    -

    MySQL-> GaussDB distributed

    +

    MySQL -> GaussDB Distributed

    Not supported

    @@ -188,7 +188,7 @@

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    Supported

    @@ -238,7 +238,7 @@

    One-way sync

    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    @@ -251,7 +251,7 @@

    One-way sync

    -

    From the cloud

    +

    Out of the cloud

    MySQL->Kafka

    @@ -264,9 +264,9 @@

    One-way sync

    -

    From the cloud

    +

    Out of the cloud

    -

    GaussDB distributed -> MySQL

    +

    GaussDB Distributed -> MySQL

    Supported

    @@ -331,7 +331,7 @@

    To the cloud

    -

    MySQL-> GaussDB distributed

    +

    MySQL -> GaussDB Distributed

    • MySQL 5.5.x
    • MySQL 5.6.x
    • MySQL 5.7.x
    @@ -340,20 +340,20 @@

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    • MySQL 5.5.x
    • MySQL 5.6.x
    • MySQL 5.7.x
    • MySQL 8.0.x
    -

    GaussDB(for MySQL)-MySQL 8.0

    +

    TaurusDB-MySQL 8.0

    To the cloud

    PostgreSQL->PostgreSQL

    -
    • PostgreSQL 9.4.x
    • PostgreSQL 9.5.x
    • PostgreSQL 9.6.x
    • PostgreSQL 10.x
    • PostgreSQL 11.x
    • PostgreSQL 12.x
    • PostgreSQL 13.x
    • PostgreSQL 14.x
    • PostgreSQL 15.x
    +
    • PostgreSQL 9.4.x
    • PostgreSQL 9.5.x
    • PostgreSQL 9.6.x
    • PostgreSQL 10.x
    • PostgreSQL 11.x
    • PostgreSQL 12.x
    • PostgreSQL 13.x
    • PostgreSQL 14.x
    • PostgreSQL 15.x
    -
    • PostgreSQL 9.5.x
    • PostgreSQL 9.6.x
    • PostgreSQL 10.x
    • PostgreSQL 11.x
    • PostgreSQL 12.x
    • PostgreSQL 13.x
    • PostgreSQL 14.x
    • PostgreSQL 15.x
    +
    • PostgreSQL 9.5.x
    • PostgreSQL 9.6.x
    • PostgreSQL 10.x
    • PostgreSQL 11.x
    • PostgreSQL 12.x
    • PostgreSQL 13.x
    • PostgreSQL 14.x
    • PostgreSQL 15.x

    To the cloud

    @@ -374,7 +374,7 @@
    • PostgreSQL 9.5.x
    • PostgreSQL 9.6.x
    • PostgreSQL 10.x
    • PostgreSQL 11.x
    • PostgreSQL 12.x
    • PostgreSQL 13.x
    • PostgreSQL 14.x
    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    @@ -383,18 +383,18 @@
    • MySQL 5.6.x
    • MySQL 5.7.x
    • MySQL 8.0.x
    -

    From the cloud

    +

    Out of the cloud

    MySQL->Kafka

    -
    • MySQL 5.6.x
    • MySQL 5.7.x
    • MySQL 8.0.x
    +
    • MySQL 5.6.x
    • MySQL 5.7.x
    • MySQL 8.0.x

    Kafka 0.11 or later

    -

    From the cloud

    +

    Out of the cloud

    -

    GaussDB distributed -> MySQL

    +

    GaussDB distributed -> MySQL

    GaussDB 1.3

    @@ -495,7 +495,7 @@

    To the cloud

    -

    MySQL-> GaussDB distributed

    +

    MySQL -> GaussDB Distributed

    Supported

    @@ -506,7 +506,7 @@

    To the cloud

    -

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    Supported

    @@ -548,7 +548,7 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    @@ -559,7 +559,7 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    MySQL->Kafka

    @@ -570,9 +570,9 @@

    Supported

    -

    From the cloud

    +

    Out of the cloud

    -

    GaussDB distributed -> MySQL

    +

    GaussDB distributed -> MySQL

    Not supported

    @@ -609,137 +609,137 @@

    Supported Synchronization Objects

    DRS allows you to synchronize different objects. The following table lists the supported objects.

    -
    @@ -265,10 +265,10 @@ @@ -308,7 +308,7 @@ -

  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

    +

  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

    • Table 6 Supported synchronization objects

    Synchronization Direction

    +
    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/drs/umn/drs_01_0303.html b/docs/drs/umn/drs_01_0303.html index a73fa078c..904ac9c68 100644 --- a/docs/drs/umn/drs_01_0303.html +++ b/docs/drs/umn/drs_01_0303.html @@ -11,11 +11,11 @@ - - - @@ -31,7 +31,7 @@ - @@ -51,7 +51,7 @@ - - - - @@ -54,7 +54,7 @@ - @@ -65,7 +65,7 @@ - @@ -106,11 +106,11 @@ - - - diff --git a/docs/drs/umn/drs_01_0313.html b/docs/drs/umn/drs_01_0313.html new file mode 100644 index 000000000..51a3f1672 --- /dev/null +++ b/docs/drs/umn/drs_01_0313.html @@ -0,0 +1,15 @@ + + +

    Specification Description

    +
    +
    + + +
    +
    Parent topic: Service Overview
    +
    +
    + diff --git a/docs/drs/umn/drs_01_0314.html b/docs/drs/umn/drs_01_0314.html new file mode 100644 index 000000000..cdf96c3dd --- /dev/null +++ b/docs/drs/umn/drs_01_0314.html @@ -0,0 +1,169 @@ + + +

    Real-Time Synchronization

    +

    Precautions

    The performance indicators provided in this section are for reference only. The actual environment is affected by factors such as the performance of the source or destination database, network bandwidth, data model, and service model.

    +
    +

    Specifications

    + +
    Table 6 Supported synchronization objects

    Synchronization Direction

    Data Flow

    +

    Data Flow

    Table-level

    +

    Table-level

    Database-level

    +

    Database-level

    Importing an Object File

    +

    Importing an Object File

    To the cloud

    +

    To the cloud

    MySQL->MySQL

    +

    MySQL->MySQL

    Supported

    +

    Supported

    Supported

    +

    Supported

    Supported

    +

    Supported

    To the cloud

    +

    To the cloud

    MySQL-> GaussDB distributed

    +

    MySQL -> GaussDB Distributed

    Supported

    +

    Supported

    Not supported

    +

    Not supported

    Not supported

    +

    Not supported

    To the cloud

    +

    To the cloud

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    Supported

    +

    Supported

    Supported

    +

    Supported

    Supported

    +

    Supported

    To the cloud

    +

    To the cloud

    PostgreSQL->PostgreSQL

    +

    PostgreSQL->PostgreSQL

    Supported

    +

    Supported

    Supported

    +

    Supported

    Supported

    +

    Supported

    To the cloud

    +

    To the cloud

    DDM->DDM

    +

    DDM->DDM

    Supported

    +

    Supported

    Supported

    +

    Supported

    Not supported

    +

    Not supported

    To the cloud

    +

    To the cloud

    Oracle->PostgreSQL

    +

    Oracle->PostgreSQL

    Supported

    +

    Supported

    Not supported

    +

    Not supported

    Supported

    +

    Supported

    From the cloud

    +

    Out of the cloud

    MySQL->MySQL

    +

    MySQL->MySQL

    Supported

    +

    Supported

    Supported

    +

    Supported

    Not supported

    +

    Not supported

    From the cloud

    +

    Out of the cloud

    MySQL->Kafka

    +

    MySQL->Kafka

    Supported

    +

    Supported

    Supported

    +

    Supported

    Supported

    +

    Supported

    From the cloud

    +

    Out of the cloud

    GaussDB distributed -> MySQL

    +

    GaussDB Distributed -> MySQL

    Supported

    +

    Supported

    Not supported

    +

    Not supported

    Not supported

    +

    Not supported

    Self-built -> Self-built

    +

    Self-built -> Self-built

    MySQL->MySQL

    +

    MySQL->MySQL

    Supported

    +

    Supported

    Supported

    +

    Supported

    Not supported

    +

    Not supported

    Self-built -> Self-built

    +

    Self-built -> Self-built

    MySQL->Kafka

    +

    MySQL->Kafka

    Supported

    +

    Supported

    Supported

    +

    Supported

    Supported

    +

    Supported

    Microsoft SQL Server -> RDS Microsoft SQL Server

    +

    Microsoft SQL Server -> RDS for SQL Server

    • On-premises Microsoft SQL Server backup files
    • RDS Microsoft SQL Server full backup files
    • Microsoft SQL Server backup files on other clouds
    +
    • On-premises Microsoft SQL Server backup files
    • RDS for SQL Server full backup files
    • Microsoft SQL Server backup files on other clouds

    RDS Microsoft SQL Server DB instances

    +

    RDS for SQL Server DB instances

    Microsoft SQL Server -> RDS Microsoft SQL Server

    +

    Microsoft SQL Server -> RDS for SQL Server

    Supported

    Microsoft SQL Server -> RDS Microsoft SQL Server

    +

    Microsoft SQL Server -> RDS for SQL Server

    On-premises and other cloud's Microsoft SQL Server backup file versions:

    @@ -60,7 +60,7 @@
    • Microsoft SQL Server 2008
    • Microsoft SQL Server 2012
    • Microsoft SQL Server 2014
    • Microsoft SQL Server 2016
    • Microsoft SQL Server 2017
    • Microsoft SQL Server 2019

    RDS Microsoft SQL Server full backup file versions:

    +

    RDS for SQL Server full backup file versions:

    • Microsoft SQL Server 2008
    • Microsoft SQL Server 2012
    • Microsoft SQL Server 2014
    • Microsoft SQL Server 2016
    • Microsoft SQL Server 2017
    • Microsoft SQL Server 2019
    • Microsoft SQL Server 2008
    • Microsoft SQL Server 2012
    • Microsoft SQL Server 2014
    • Microsoft SQL Server 2016
    • Microsoft SQL Server 2017
    • Microsoft SQL Server 2019
    diff --git a/docs/drs/umn/drs_01_0305.html b/docs/drs/umn/drs_01_0305.html index 3ec63a45d..64fa70a71 100644 --- a/docs/drs/umn/drs_01_0305.html +++ b/docs/drs/umn/drs_01_0305.html @@ -39,11 +39,11 @@

    Current cloud as standby

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • RDS MySQL instances

    GaussDB(for MySQL) primary/standby instances

    +

    TaurusDB cluster instances
    • Primary/Standby instance
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • GaussDB(for Cassandra) instances

    GaussDB(for Cassandra) instances

    +

    GaussDB(for Cassandra) instances
    • Cluster
    • GaussDB(for Cassandra)
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • GaussDB(for Cassandra) instances
    +
    • On-premises databases
    • ECS databases
    • Databases on other clouds
    • GaussDB(for Cassandra) instances
    • Cluster

    Current cloud as standby

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster
    • MySQL 5.6.x
    • MySQL 5.7.x

    GaussDB(for MySQL)-MySQL 8.0

    +

    TaurusDB-MySQL 8.0

    Current cloud as standby

    @@ -211,7 +211,7 @@

    Current cloud as standby

    MySQL -> GaussDB(for MySQL) primary/standby

    +

    MySQL -> TaurusDB Cluster

    Not supported

    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Full synchronization maximum performance

    Data Flow

    +

    Reference Value of Maximum Performance of Full Synchronization (MB/s)

    +

    MySQL as the source

    +

    50

    +

    Oracle as the source

    +

    40

    +

    Redis as the source

    +

    30

    +

    GaussDB as the source

    +

    40

    +

    PostgreSQL as the source

    +

    30

    +

    DDM as the source

    +

    20

    +

    MongoDB as the source

    +

    20

    +
    +
    +
    • There are many factors that affect the DRS migration speed. The current migration speed is the test data when there is no network and database performance bottlenecks and the task specifications are large. The migration speed is for reference only.
    • When the destination database is Oracle, the migration speed in the full phase is 30% to 50% lower than that of other types of databases due to the write mechanism of the destination database.
    • The write performance of the MongoDB database is affected by the number of indexes. The write performance decreases by 5% to 8% when there is one index. The more indexes, the slower the write speed.
    +
    +

    Based on the incremental performance of data flow types, there are six types of specifications: micro, small, medium, large, ultra-large, and macro. Table 2 lists the performance upper limit of each specification.

    + +
    + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Performance upper limit

    Specifications

    +

    Reference Value of Maximum Performance of Incremental Synchronization (Rows/Second)

    +

    Micro

    +

    300

    +

    Small

    +

    3,000

    +

    Medium

    +

    7,500

    +

    Large

    +

    10,000

    +

    Ultra-large

    +

    20,000

    +

    Macro

    +

    > 20,000

    +
    +
    +
    • The performance of each specification is affected by factors such as the networks, source and destination database performance, and latency. The values in the table are for reference only.
    • DRS measures the performance of different specifications using the full (with flow control disabled) and incremental synchronization tasks as the standard.
    • The maximum performance (rows/second) is measured by the number of transactions synchronized per second. The statement types include BEGIN, COMMIT, DML (INSERT, DELETE, and UPDATE), and DDL.
    • If you want to compare values for a DRS task, select large or higher specifications when creating the DRS task.
    +
    + +

    Testing Models

    Create a full+incremental real-time synchronization task for two RDS for MySQL instances. Table 3 shows the instance configurations.

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 3 Instance specifications

    Parameter

    +

    Source RDS for MySQL instance

    +

    Destination RDS for MySQL instance

    +

    Flavor

    +

    c6.4xlarge.4 (general-enhanced II)

    +

    c6.4xlarge.4 (general-enhanced II)

    +

    Instance specifications

    +

    Ultra-high I/O

    +

    Ultra-high I/O

    +

    Storage type

    +

    16 vCPUs|64 GB

    +

    16 vCPUs|64 GB

    +

    Storage space

    +

    300 GB

    +

    300 GB

    +

    Maximum connections

    +

    18,000

    +

    18,000

    +

    Maximum QPS

    +

    3,325

    +

    3,325

    +

    Maximum IOPS

    +

    114,152

    +

    114,152

    +
    +
    +

    Test model:

    +
    • The number of test tables is 20.
    • All test tables have primary keys.
    • The record size is 1 KB.
    • Each transaction contains two DML operations and one COMMIT operation. The ratio of INSERT, UPDATE, and DELETE operations is 1:1:1.
    +
    + +
    +
    +
    Parent topic: Specification Description
    +
    +
    + diff --git a/docs/drs/umn/drs_01_0326.html b/docs/drs/umn/drs_01_0326.html index feeb09518..51b6d06bb 100644 --- a/docs/drs/umn/drs_01_0326.html +++ b/docs/drs/umn/drs_01_0326.html @@ -199,7 +199,7 @@

    TIMESTAMP values supported by MySQL range from '1970-01-01 00:00:01' UTC to '2038-01-19 03:14:07' UTC.

    For details, see official MySQL documentation.

    For GaussDB, 0000-00-00 is an invalid date and will be converted to 1970-01-01 by DRS. For example, '0000-00-00' of the DATE type in MySQL is converted to '1970-01-01' by DRS, and '1000-00-31 23:59:59' of the DATETIME or TIMESTAMP type in MySQL is converted to '1970-01-01 00:00:00' by DRS.

    -
  • TIME values supported by MySQL range from '-838:59:59' to '838:59:59'. For details, see the official MySQL documentation. For GaussDB, the minimum value of the TIME type is 00:00:00 and the maximum value is 24:00:00. In MySQL, if a value of the TIME type is less than 00:00:00 or greater than 24:00:00, DRS will convert it to 00:00:00.
  • YEAR value ranges supported by MySQL are 1901 to 2155 and 0000. For details, see official MySQL documentation. GaussDB does not have the YEAR type, so DRS will convert the YEAR type of MySQL to the SMALLINT type.
  • For MySQL databases, '0000' of the DATE type will be converted to 0 by DRS.
    • +
  • TIME values supported by MySQL range from '-838:59:59' to '838:59:59'. For details, see the official MySQL documentation. For GaussDB, the minimum value of the TIME type is 00:00:00, and the maximum value is 24:00:00. In MySQL, if a value of the TIME type is less than 00:00:00 or greater than 24:00:00, DRS will convert it to 00:00:00.
  • YEAR value ranges supported by MySQL are 1901 to 2155 and 0000. For details, see official MySQL documentation. GaussDB does not have the YEAR type, so DRS will convert the YEAR type of MySQL to the SMALLINT type.
  • For MySQL databases, '0000' of the DATE type will be converted to 0 by DRS.
    • diff --git a/docs/drs/umn/drs_02_0002.html b/docs/drs/umn/drs_02_0002.html index 6535bb140..84941417e 100644 --- a/docs/drs/umn/drs_02_0002.html +++ b/docs/drs/umn/drs_02_0002.html @@ -168,7 +168,7 @@

    SSL Connection

    SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

    -
    NOTE:
    • The maximum size of a single certificate file that can be uploaded is 500 KB.
    • If SSL is disabled, your data may be at risk.
    +
    NOTE:
    • The maximum size of a single certificate file that can be uploaded is 500 KB.
    • If the SSL certificate is not used, your data may be at risk.

    Migrate Account

    During a database migration, accounts need to be migrated separately.

    -
    There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements. If you select Yes, you can select the accounts to be migrated as required.
    • Yes

      If you need to migrate accounts, see Migrating Accounts.

      +
      There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements. If you select Yes, you can select the accounts to be migrated as required.
      -
      • No

        During migration, accounts, permissions, and passwords are not migrated.

        +
        • No

          During migration, accounts, permissions, and passwords are not migrated.
    Table 8 Task startup settings

    Parameter

    Description

    @@ -325,7 +325,7 @@
    -

  • After the task is submitted, view and manage it on the Online Migration Management page.

    • You can view the task status. For more information about task status, see Task Statuses.
    • You can click in the upper right corner to view the latest task status.
    +

  • After the task is submitted, view and manage it on the Online Migration Management page.

    • You can view the task status. For more information about task status, see Task Statuses.
    • You can click in the upper right corner to view the latest task status.
    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

    • diff --git a/docs/drs/umn/drs_02_0005.html b/docs/drs/umn/drs_02_0005.html index 9dfd1b8bf..eeb16e4b7 100644 --- a/docs/drs/umn/drs_02_0005.html +++ b/docs/drs/umn/drs_02_0005.html @@ -4,7 +4,9 @@

    Migration logs refer to the warning-, error-, and info-level logs generated during the migration process. This section describes how to view migration logs to locate and analyze database problems.

    Prerequisites

    • You have logged in to the DRS console.
    • A migration task has been created.
    -

    Procedure

    1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
    2. On the Migration Logs tab, view logs of the migration task by level.

      You can view time, levels, and descriptions of the logs.

      +

      Procedure

      1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
      2. On the Migration Logs tab, view logs of the migration task by level.

        You can view time, levels, and descriptions of the logs.

        +

        For a task whose source database is DDM, you can view the migration logs in each subtask.

        +

    diff --git a/docs/drs/umn/drs_02_0006.html b/docs/drs/umn/drs_02_0006.html index 2a6b06e12..628b5845a 100644 --- a/docs/drs/umn/drs_02_0006.html +++ b/docs/drs/umn/drs_02_0006.html @@ -3,12 +3,12 @@

    Step 2: Query the Migration Progress

    The migration progress of a real-time migration task helps you keep track of the status of the migration task.

    DRS shows the migration progress using a progress bar, helping you learn the migration progress in real time. During full migration, you can check migration details.

    -
    • With the progress bar, you can view the migration progress of structures, data, and indexes. When the progress reaches 100%, the migration is complete. The migration of data and indexes is relatively slow.
    • In the migration details, you can view the migration progress of a specific object. If the number of objects is the same as that of migrated objects, the migration is complete. You can view the migration progress of each object in detail. During incremental migration, the progress details are not displayed. You can view the consistency status on the Migration Comparison tab.
    +
    • With the progress bar, you can view the migration progress of structures, data, and indexes. When the progress reaches 100%, the migration is complete. The migration of data and indexes is relatively slow during the migration.
    • In the migration details, you can view the migration progress of a specific object. If the number of objects is the same as that of migrated objects, the migration is complete. You can view the migration progress of each object in detail. During incremental migration, the progress details are not displayed. You can view the consistency status on the Migration Comparison tab.

    Prerequisites

    • You have logged in to the DRS console.
    • A migration task has been started.
    -

    Procedure

    1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
    2. On the displayed page, click Migration Progress.

      • View the migration progress of structures, data, and indexes.

        When a full migration is complete, the progress of each item reaches 100%.

        +

        Procedure

        1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
        2. On the displayed page, click Migration Progress.

          • View the migration progress of structures, data, and indexes.

            When a full migration is complete, the progress of each item reaches 100%.

            For a full plus incremental migration, you can view the delay of the incremental migration on the Migration Progress page.

            -
            You can also view the incremental migration delay on the Online Migration Management page. When the incremental migration delay exceeds the preset or default threshold, the value of the incremental migration delay is displayed in red in the task list.

            "Delay" refers to the delay from when the transaction was submitted to the source database to when it is synchronized to the destination database and executed.

            +
            You can also view the incremental migration delay on the Online Migration Management page. When the incremental migration delay exceeds the preset or default threshold, the value of the incremental migration delay is displayed in red in the task list.

            "Delay" refers to the delay from when the transaction was submitted to the source database to when it is synchronized to the destination database and executed.

            Transactions are synchronized as follows:

            1. Data is extracted from the source database.
            2. The data is transmitted over the network.
            3. DRS parses the source logs.
            4. The transaction is executed on the destination database.

            If the delay is 0, the source database is consistent with the destination database, and no new transactions need to be synchronized.

            diff --git a/docs/drs/umn/drs_02_0007.html b/docs/drs/umn/drs_02_0007.html index 9d2bc5c50..7c43e10c8 100644 --- a/docs/drs/umn/drs_02_0007.html +++ b/docs/drs/umn/drs_02_0007.html @@ -5,7 +5,7 @@
            Figure 1 Comparison process

            Comparison Scenarios

            You can compare migration objects with different dimensions:

            • Object-level comparison: It helps you compare databases, indexes, tables, views, stored procedures and functions, and sorting rules of tables. You are advised to perform the comparison after a full migration is complete.
            • Data-level comparison is classified into row comparison and value comparison.
              • Row comparison: It helps you compare the number of rows in the tables to be migrated. This comparison method is recommended because it is fast.
              • Value comparison: It helps you check whether data in the migrated table is consistent. The comparison process is relatively slow.
              -
            • Account comparison: It compares usernames and permissions of the source and destination databases.
            • Periodic comparison: DRS periodically compares the number of rows or objects in the source database table with those in the destination database table and displays the comparison results. To compare rows or objects periodically, enable comparison policy.
            +
          • Account comparison: It compares usernames and permissions of the source and destination databases.
          • Periodic comparison: DRS periodically compares the number of rows or objects in the source database table with those in the destination database table and displays the comparison results. To compare rows or objects periodically, enable comparison policy.

          When you check data consistency, compare the number of rows first. If the number of rows are inconsistent, you can then compare the data in the table to determine the inconsistent data.

        Comparison Restrictions

        • A comparison task can be created only when the task is in the incremental phase. When a full task is complete, DRS automatically creates object-level and row comparison tasks.
        • If DDL operations were performed on the source database, you need to compare the objects again to ensure the accuracy of the comparison results.
        • If data in the destination database is modified separately, the comparison results may be inconsistent.
        • Currently, only tables with primary keys support value comparison. For tables that do not support value comparison, you can compare rows. Therefore, you can compare data by row or value based on scenarios.
        • To prevent resources from being occupied for a long time, DRS limits the row comparison duration. If the row comparison duration exceeds the threshold, the row comparison task stops automatically. If the source database is a relational database, the row comparison duration is 60 minutes. If the source database is a non-relational database, for example, MongoDB, the row comparison duration is 30 minutes.
        @@ -17,7 +17,7 @@

        Prerequisites

        • You have logged in to the DRS console.
        • A migration task has been started.

        Creating a comparison task

        You can follow the comparison process or select a comparison method based on your service scenario. The following operations describe how to compare migration items by following the recommended migration process.

        -
        1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
        2. On the Migration Comparison tab, compare objects of the source and destination databases.

          1. Check the integrity of the database object.

            Click Validate Objects. On the Object-Level Comparison tab, view the comparison result of each comparison item.

            +
            1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
            2. On the Migration Comparison tab, compare objects of the source and destination databases.

              1. Check the integrity of the database object.

                Click Validate Objects. On the Object-Level Comparison tab, view the comparison result of each comparison item.

                Locate a comparison item you want to view and click View Details in the Operation column.

              2. After the check is complete, compare the number of rows and values.
                1. In the Before You Start pane, click Validate All Rows/Values.
                2. In the displayed Create Comparison Task dialog box, specify Comparison Type, Comparison Time, and Object. Then, click OK.
                  • Comparison Type: compares rows and values.
                  • Comparison Time: You can select Start upon task creation or Start at a specified time. There is a slight difference in time between the source and destination databases during synchronization. Data inconsistency may occur. You are advised to compare migration items during off-peak hours for more accurate results.
                  • Object: You can select objects to be compared based on the scenarios.

                  After the comparison creation task is submitted, the Data-Level Comparison tab is displayed. Click to refresh the list and view the comparison result of the specified comparison type.

                  @@ -33,8 +33,8 @@

        -

        Periodic Comparison

        Periodic comparison indicates that DRS periodically compares the number of rows or objects in the source database table with those in the destination database table and displays the comparison results.

        -
        1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
        2. Choose Migration Comparison.
        3. Click the Periodic Comparison tab and click Modify Comparison Policy.
        4. In the Modify Comparison Policy dialog box, enable periodic comparison, specify the comparison frequency, time interval, effective time and comparison type, and click Yes.

          • After periodic comparison is enabled, DRS compares the number of rows or objects at the scheduled time. You can view the comparison results on the Data-Level Comparison or Object-Level Comparison tab.
          • After periodic comparison is disabled, only historical comparison results can be viewed.
          • Modifications to the comparison policy settings take effect from the next comparison and do not affect the on-going periodic comparison tasks.
          • During periodic comparison, the source and destination databases will be read. Perform the comparison during off-peak hours.
          • During periodic comparison, ultra-large tables (those with more than 100 million rows) are automatically filtered out. You can use data-level comparison to spot check such large tables. It is not recommended that these large tables be compared periodically.
          +

          Periodic Comparison

          Periodic comparison indicates that DRS periodically compares the number of rows or objects in the source database table with those in the destination database table and displays the comparison results.

          +
          1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
          2. Choose Migration Comparison.
          3. Click the Periodic Comparison tab and click Modify Comparison Policy to modify the comparison policy.
          4. In the Modify Comparison Policy dialog box, enable periodic comparison, configure the comparison frequency and time, and click Yes.

            • After periodic comparison is enabled, DRS compares the number of rows or objects at the scheduled time. You can view the comparison results on the Data-Level Comparison or Object-Level Comparison tab.
            • After periodic comparison is disabled, only historical comparison results can be viewed.
            • Modifications to the comparison policy settings take effect from the next comparison and do not affect the on-going periodic comparison tasks.
            • During periodic comparison, the source and destination databases will be read. Perform the comparison during off-peak hours.
            • During periodic comparison, ultra-large tables (those with more than 100 million rows) are automatically filtered out. You can use data-level comparison to spot check such large tables. It is not recommended that these large tables be compared periodically.

          diff --git a/docs/drs/umn/drs_02_0009.html b/docs/drs/umn/drs_02_0009.html index 7069d3849..2b034f732 100644 --- a/docs/drs/umn/drs_02_0009.html +++ b/docs/drs/umn/drs_02_0009.html @@ -11,7 +11,7 @@

          On-premises and other cloud's Microsoft SQL Server backup file versions:

          • Microsoft SQL Server 2000
          • Microsoft SQL Server 2005
          • Microsoft SQL Server 2008
          • Microsoft SQL Server 2012
          • Microsoft SQL Server 2014
          • Microsoft SQL Server 2016
          • Microsoft SQL Server 2017
          • Microsoft SQL Server 2019
          -

          RDS for Microsoft SQL Server

          +

          RDS for SQL Server

          • Microsoft SQL Server 2008
          • Microsoft SQL Server 2012
          • Microsoft SQL Server 2014
          • Microsoft SQL Server 2016
          • Microsoft SQL Server 2017
          • Microsoft SQL Server 2019

          diff --git a/docs/drs/umn/drs_02_0010.html b/docs/drs/umn/drs_02_0010.html index 1e36314ad..eff3513c5 100644 --- a/docs/drs/umn/drs_02_0010.html +++ b/docs/drs/umn/drs_02_0010.html @@ -8,10 +8,10 @@ -

          RDS Microsoft SQL Server full backup file versions:

          +

          RDS for SQL Server full backup file versions:

          • Microsoft SQL Server 2008
          • Microsoft SQL Server 2012
          • Microsoft SQL Server 2014
          • Microsoft SQL Server 2016
          • Microsoft SQL Server 2017
          • Microsoft SQL Server 2019
          -

          RDS for Microsoft SQL Server

          +

          RDS for SQL Server

          • Microsoft SQL Server 2008
          • Microsoft SQL Server 2012
          • Microsoft SQL Server 2014
          • Microsoft SQL Server 2016
          • Microsoft SQL Server 2017
          • Microsoft SQL Server 2019

          diff --git a/docs/drs/umn/drs_02_0017.html b/docs/drs/umn/drs_02_0017.html index 1657b6dbf..791ff6bbb 100644 --- a/docs/drs/umn/drs_02_0017.html +++ b/docs/drs/umn/drs_02_0017.html @@ -14,6 +14,8 @@
        5. Tag Management
          6. +
        6. Interconnecting with Cloud Eye
          +
    diff --git a/docs/drs/umn/drs_02_0024.html b/docs/drs/umn/drs_02_0024.html index c9319c41a..8774fc3a3 100644 --- a/docs/drs/umn/drs_02_0024.html +++ b/docs/drs/umn/drs_02_0024.html @@ -6,7 +6,7 @@
    -
    • If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.
    • Deleted DR tasks are not displayed in the status list.
    +
    • If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.
    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
    • Deleted DR tasks are not displayed in the status list.
    diff --git a/docs/drs/umn/drs_02_0027.html b/docs/drs/umn/drs_02_0027.html index a8cd74eed..691d14cff 100644 --- a/docs/drs/umn/drs_02_0027.html +++ b/docs/drs/umn/drs_02_0027.html @@ -212,13 +212,7 @@ -

    Database Type

    - -

    By default, Self-built on ECS is selected.

    -

    The destination database can be a Self-built on ECS or an RDS DB instance. If you select RDS DB instance, you need to select the region where the destination database is located. To use the RDS DB instance option, submit a service ticket.

    - - -

    IP Address or Domain Name

    +

    IP Address or Domain Name

    The IP address or domain name of the DR database.

    @@ -301,7 +295,7 @@
    • If the check is complete and the check success rate is 100%, go to the Compare Parameter page.

      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

    -

  • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

    +

  • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

    Table 9 Task and recipient description

    Parameter

    Description

    @@ -318,7 +312,7 @@
    -

  • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

    • You can view the task status. For more information about task status, see Task Statuses.
    • You can click in the upper-right corner to view the latest task status.
    +

  • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

    • You can view the task status. For more information about task status, see Task Statuses.
    • You can click in the upper-right corner to view the latest task status.
    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

    • diff --git a/docs/drs/umn/drs_02_0028.html b/docs/drs/umn/drs_02_0028.html index fb6d7b641..efdf04e64 100644 --- a/docs/drs/umn/drs_02_0028.html +++ b/docs/drs/umn/drs_02_0028.html @@ -4,7 +4,7 @@

    After a DR task starts, you can check the DR progress.

    Prerequisites

    • You have logged in to the DRS console.
    • A DR task has been created and started.
    -

    Procedure

    1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
    2. On the displayed page, click the Disaster Recovery Progress tab to view the DR progress. When the data initialization is complete, the initialization progress is displayed as 100%.

      • On the Disaster Recovery Progress tab, you can view the DR synchronization delay,
      • You can also view the DR synchronization delay on the Disaster Recovery Management page. When the synchronization delay exceeds the preset or default threshold, the value of the synchronization delay is displayed in red in the task list.
      • When the delay is 0, data is synchronized from the service database to the DR database in real-time.
      +

      Procedure

      1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
      2. On the displayed page, click the Disaster Recovery Progress tab to view the DR progress. When the data initialization is complete, the initialization progress is displayed as 100%.

        • On the Disaster Recovery Progress tab, you can view the DR synchronization delay.
        • You can also view the DR synchronization delay on the Disaster Recovery Management page. When the synchronization delay exceeds the preset or default threshold, the value of the synchronization delay is displayed in red in the task list.
        • When the delay is 0, data is synchronized from the service database to the DR database in real-time.

        "Delay" refers to the delay from when the transaction was submitted to the source database to when it is synchronized to the destination database and executed.

        Transactions are synchronized as follows:

        1. Data is extracted from the source database.
        2. The data is transmitted over the network.
        3. DRS parses the source logs.
        4. The transaction is executed on the destination database.
        diff --git a/docs/drs/umn/drs_03_0001.html b/docs/drs/umn/drs_03_0001.html index 5b0d0dde3..b2804178f 100644 --- a/docs/drs/umn/drs_03_0001.html +++ b/docs/drs/umn/drs_03_0001.html @@ -93,7 +93,7 @@
        -
        • If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.
        • Deleted migration tasks are not displayed in the status list.
        +
        • If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.
        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
        • Deleted migration tasks are not displayed in the status list.
        • For a task whose source database is DDM, the statuses listed above mean statuses of its subtask.
        diff --git a/docs/drs/umn/drs_03_0002.html b/docs/drs/umn/drs_03_0002.html index 43e079b9d..c18808008 100644 --- a/docs/drs/umn/drs_03_0002.html +++ b/docs/drs/umn/drs_03_0002.html @@ -29,10 +29,10 @@

        Migrate Account

        During a database migration, accounts need to be migrated separately.

        -
        There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements. If you select Yes, you can select the accounts to be migrated as required.
        • Yes

          If you need to migrate accounts, see Migrating Accounts.

          +
          There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements. If you select Yes, you can select the accounts to be migrated as required.
          -
          • No

            During migration, accounts, permissions, and passwords are not migrated.

            +
            • No

              During migration, accounts, permissions, and passwords are not migrated.

            diff --git a/docs/drs/umn/drs_03_0026.html b/docs/drs/umn/drs_03_0026.html index cd4dc6913..16dba76be 100644 --- a/docs/drs/umn/drs_03_0026.html +++ b/docs/drs/umn/drs_03_0026.html @@ -9,7 +9,7 @@
            • If the check is complete and the check success rate is 100%, go to the Compare Parameter page.

              You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

            -

          • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

            +

          • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

            Table 1 Task and recipient description

            Parameter

            Description

            @@ -26,7 +26,7 @@
            -

          • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

            • You can view the task status. For more information about task status, see Task Statuses.
            • You can click in the upper-right corner to view the latest task status.
            +

          • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

            • You can view the task status. For more information about task status, see Task Statuses.
            • You can click in the upper-right corner to view the latest task status.
            • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

      Method 2

      1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
      2. On the displayed page, click edit this task to go to the Configure Source and Destination Databases page.
      3. Perform 2 through 5 in method 1.
      diff --git a/docs/drs/umn/drs_03_0035.html b/docs/drs/umn/drs_03_0035.html index d7cc11795..e44d6264e 100644 --- a/docs/drs/umn/drs_03_0035.html +++ b/docs/drs/umn/drs_03_0035.html @@ -4,9 +4,15 @@

      DRS processes synchronized objects and allows you to add rules for selected objects.

      Filtering Data

      After a data filtering rule is added, update the source database to ensure data consistency. For example:
      • The filter criteria are met after the update. You need to continue the synchronization and perform the same update operation on the destination database. If no data is matched, the operation will be ignored, causing data inconsistency.
      • The filter criteria are not met after the update. You need to continue the synchronization and perform the same update operation on the destination database.
      -
      1. In the Object area of the Data filtering page, select the table to be processed.
      2. In the Filtering Criteria area, enter the filter criteria (only the part after WHERE in the SQL statement, for example, id=1), and click Verify.

        • Each table has only one verification rule.
        • Up to 500 tables can be filtered at a time.
        • The filter expression cannot use the package, function, variable, or constant of a specific DB engine. It must comply with the general SQL standard. Enter the part following WHERE in the SQL statement (excluding WHERE and semicolons), for example, sid > 3 and sname like "G %". A maximum of 512 characters are allowed.
        • In SQL statements for setting filter criteria, keywords must be enclosed in backquotes, and the value of datatime (including date and time) must be enclosed in single quotation marks, for example, `update` > '2022-07-13 00:00:00' and age >10.
        • Filter criteria cannot be configured for large objects, such as CLOB, BLOB, and BYTEA.
        • You are not advised to set filter criteria for fields of approximate numeric types, such as FLOAT, DECIMAL, and DOUBLE.
        • Do not use fields containing special characters as a filter condition.
        • You are not advised to use non-idempotent expressions or functions as data processing conditions, such as SYSTIMESTAMP and SYSDATE, because the returned result may be different each time the function is called.
        +
        1. On the Data filtering page, select the table objects to be processed in the Object field.
        2. In the Object area, select the table to be processed.
        3. In the Filtering Criteria area, enter the filter criteria (only the part after WHERE in the SQL statement, for example, id=1), and click Verify.

          • Each table has only one verification rule.
          • Up to 500 tables can be filtered at a time.
          • The filter expression cannot use the package, function, variable, or constant of a specific DB engine. It must comply with the general SQL standard. Enter the part following WHERE in the SQL statement (excluding WHERE and semicolons), for example, sid > 3 and sname like "G %". A maximum of 512 characters are allowed.
          • In SQL statements for setting filter criteria, keywords must be enclosed in backquotes, and the value of datatime (including date and time) must be enclosed in single quotation marks, for example, `update` > '2022-07-13 00:00:00' and age >10.
          • Filter criteria cannot be configured for large objects, such as CLOB, BLOB, and BYTEA.
          • You are not advised to set filter criteria for fields of approximate numeric types, such as FLOAT, DECIMAL, and DOUBLE.
          • Do not use fields containing special characters as a filter condition.
          • You are not advised to use non-idempotent expressions or functions as data processing conditions, such as SYSTIMESTAMP and SYSDATE, because the returned result may be different each time the function is called.
          -

        4. After the verification is successful, click Generate Processing Rule. The rule is displayed.
        5. Click Next.
        +

      3. After the verification is successful, click Generate Processing Rule. The rule is displayed.
      4. Click Next.
      +
      +

      Processing Columns

      1. On the Process Data page, select Processing Columns.
      2. In the Object area, select the objects to be processed.

        Figure 1 Processing Columns
        +

      3. Click Edit to the right of the selected object.
      4. In the Edit Column dialog box, select the columns to be mapped and enter new column names.

        Figure 2 Edit Column
        +
        • You can query or filter columns or create new column names.
        • After the column name is edited, the column name of the destination database is changed to the new name.
        • The new column name cannot be the same as the original column name or an existing column name.
        • The column name in the synchronized table cannot be modified.
        • Only the selected columns can be synchronized.
        • MySQL to MySQL and MySQL to TaurusDB Cluster synchronizations do not support column mapping based on the partitioning column of a partitioned table.
        • GaussDB partition keys cannot be filtered.
        +
        +

      5. Click Confirm.
      6. Click Next.

      Viewing Data Filtering Results

      1. In the task list, click the task to be processed.
      2. Click the Process Data tab to view data filtering records. Click in the upper right corner to refresh the record list.
      diff --git a/docs/drs/umn/drs_03_0046.html b/docs/drs/umn/drs_03_0046.html index 72653422a..b0bba0072 100644 --- a/docs/drs/umn/drs_03_0046.html +++ b/docs/drs/umn/drs_03_0046.html @@ -11,7 +11,7 @@

      Method 1

      1. In the Migration Information area on the Basic Information tab, click Modify next to the Flow Control field.
      2. In the displayed dialog box, modify the settings.
      -

      Method 2

      1. In the task list on the Online Migration Management page, locate the target task and choose More > Speed or Speed in the Operation column.
      2. In the displayed dialog box, modify the settings.
      +

      Method 2

      1. In the task list on the Online Migration Management page, locate the target task and choose More > Speed or Speed in the Operation column.
      2. In the displayed dialog box, modify the settings.
      diff --git a/docs/drs/umn/drs_03_0047.html b/docs/drs/umn/drs_03_0047.html index 8b9e472e2..6fb9b5124 100644 --- a/docs/drs/umn/drs_03_0047.html +++ b/docs/drs/umn/drs_03_0047.html @@ -2,12 +2,12 @@

      Modifying the Flow Control Mode

      DRS allows you to change the flow control mode for a task. Currently, only the following DR tasks support this function.

      -
      • MySQL->MySQL
      • MySQL -> GaussDB(for MySQL) primary/standby
      +
      • MySQL->MySQL
      • MySQL -> TaurusDB Cluster

      Prerequisites

      • You have logged in to the DRS console.
      • A disaster recovery task has been created and not started.

      Method 1

      1. In the DR Information area on the Basic Information tab, click Modify next to the Flow Control field.
      2. In the displayed dialog box, modify the settings.
      -

      Method 2

      1. In the task list on the Disaster Recover Management page, locate the target task and choose More > Speed or Speed in the Operation column.
      2. In the displayed dialog box, modify the settings.
      +

      Method 2

      1. In the task list on the Disaster Recover Management page, locate the target task and choose More > Speed or Speed in the Operation column.
      2. In the displayed dialog box, modify the settings.
      diff --git a/docs/drs/umn/drs_03_0100.html b/docs/drs/umn/drs_03_0100.html index 0ca8aae14..07a32e17f 100644 --- a/docs/drs/umn/drs_03_0100.html +++ b/docs/drs/umn/drs_03_0100.html @@ -6,9 +6,9 @@
      • Migration failure status

      Prerequisites

      • You have logged in to the DRS console.
      • A migration task has failed.
      -

      Method 1

      1. In the task list on the Online Migration Management page, locate the target task and click Reset in the Operation column.
      2. In the displayed dialog box, check the migration task again.
      3. After the check is complete and the check success rate is 100%, click Start to submit the migration task again.
      +

      Method 1

      1. In the task list on the Online Migration Management page, locate the target task and click Reset in the Operation column.
      2. In the displayed dialog box, check the migration task again.
      3. After the check is complete and the check success rate is 100%, click Start to submit the migration task again.
      -

      Method 2

      1. On the Data Migration Management page, click the target task name in the Task Name/ID column.
      2. On the displayed page, click the Migration Progress tab, and click Reset in the upper left corner.
      3. Perform 2 to 3 from method 1.
      +

      Method 2

      1. On the Data Migration Management page, click the target task name in the Task Name/ID column.
      2. On the displayed page, click the Migration Progress tab, and click Reset in the upper left corner.
      3. Perform 2 to 3 from method 1.
      diff --git a/docs/drs/umn/drs_03_0105.html b/docs/drs/umn/drs_03_0105.html new file mode 100644 index 000000000..b9addc8a0 --- /dev/null +++ b/docs/drs/umn/drs_03_0105.html @@ -0,0 +1,15 @@ + + +

      Interconnecting with Cloud Eye

      +
      +
      + + +
      +
      Parent topic: Real-Time Migration
      +
      +
      + diff --git a/docs/drs/umn/drs_03_0108.html b/docs/drs/umn/drs_03_0108.html new file mode 100644 index 000000000..514ee481a --- /dev/null +++ b/docs/drs/umn/drs_03_0108.html @@ -0,0 +1,19 @@ + + +

      Viewing Monitoring Metrics

      +

      Scenarios

      Cloud Eye monitors the running statuses of replication, synchronization, and DR instances. You can obtain the monitoring metrics on the management console. Monitored data requires a period of time for transmission and display. The status of the monitored object displayed on the Cloud Eye page is the status obtained 5 to 10 minutes before. You can view the monitored data of a newly created DB instance 5 to 10 minutes later.

      +
      +

      Prerequisites

      An instance is running properly when it is in the following statuses:
      • Real-time migration: Full migration and Incremental migration
      • Real-time synchronization: Full synchronization and Incremental synchronization
      • Real-time disaster recovery: Disaster recovery in progress
      +
      +
      +

      Viewing Metrics

      1. Log in to the management console.
      2. Click in the upper left corner and select a region and project.
      3. Choose Database > Data Replication Service. The Data Replication Service page is displayed.
      4. Take real-time migration as an example. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
      5. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

        By default, the monitoring information about the DRS instance is displayed on this page.

        +

      6. View monitoring metrics of the instance.

        • On the Cloud Eye console, click the target DB instance name and click Select Metric in the upper right corner. In the displayed dialog box, you can select the metrics to be displayed and sort them by dragging them at desired locations.
        • You can sort graphs by dragging them based on service requirements.
        • Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 7 days, and 6 months.
        +

      +
      +
      +
      +
      +
      Parent topic: Interconnecting with Cloud Eye
      +
      +
      + diff --git a/docs/drs/umn/drs_03_0109.html b/docs/drs/umn/drs_03_0109.html index 7be9a61e0..9014f31b4 100644 --- a/docs/drs/umn/drs_03_0109.html +++ b/docs/drs/umn/drs_03_0109.html @@ -8,7 +8,7 @@

      3. Prerequisites

      • You have logged in to the DRS console.
      • The migration task is running properly.
      -

      Pausing a Task

      1. In the task list on the Online Migration Management page, locate the target task and click Pause in the Operation column.
      2. In the displayed Pause Task dialog box, select Pause log capturing and click Yes.

        • After the task is paused, the status of the task becomes Paused.
        • After you select Pause log capturing, the DRS instance will no longer communicate with the source and destination databases. If the pause duration is too long, the task may fail to be resumed because the logs required by the source database expire. It is recommended that the pause duration be less than or equal to 24 hours.
        • You can use the resumable transfer function to continue the migration.
        +

        Pausing a Task

        1. In the task list on the Online Migration Management page, locate the target task and click Pause in the Operation column.
        2. In the displayed Pause Task dialog box, select Pause log capturing and click Yes.

          • After the task is paused, the status of the task becomes Paused.
          • After you select Pause log capturing, the DRS instance will no longer communicate with the source and destination databases. If the pause duration is too long, the task may fail to be resumed because the logs required by the source database expire. It is recommended that the pause duration be less than or equal to 24 hours.
          • You can use the resumable transfer function to continue the migration.

        diff --git a/docs/drs/umn/drs_03_1113.html b/docs/drs/umn/drs_03_1113.html index 37eb0194c..e91e25a88 100644 --- a/docs/drs/umn/drs_03_1113.html +++ b/docs/drs/umn/drs_03_1113.html @@ -8,7 +8,7 @@
      3. Kafka Authentication
        4. -
      4. Forcibly Stopping Synchronization of GaussDB Distributed
        +
      5. Forcibly Stopping Synchronization from GaussDB Distributed
      6. Forcibly Stopping Synchronization of PostgreSQL
        7. diff --git a/docs/drs/umn/drs_03_1117.html b/docs/drs/umn/drs_03_1117.html index 279f9cef3..cc5f5c81e 100644 --- a/docs/drs/umn/drs_03_1117.html +++ b/docs/drs/umn/drs_03_1117.html @@ -311,7 +311,7 @@
      -

    3. On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

      +

    4. On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

      Table 9 Task startup settings

      Parameter

      Description

      @@ -345,7 +345,7 @@ -

    5. On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

      +

    6. On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

      Table 10 Task startup settings

      Parameter

      Description

      @@ -362,7 +362,7 @@
      -

    7. After the task is submitted, view and manage it on the Online Migration Management page.

      • You can view the task status. For more information about task status, see Task Statuses.
      • You can click in the upper right corner to view the latest task status.
      +

    8. After the task is submitted, view and manage it on the Online Migration Management page.

      • You can view the task status. For more information about task status, see Task Statuses.
      • You can click in the upper right corner to view the latest task status.
      • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

      9. diff --git a/docs/drs/umn/drs_03_1118.html b/docs/drs/umn/drs_03_1118.html deleted file mode 100644 index 5ab5bf97c..000000000 --- a/docs/drs/umn/drs_03_1118.html +++ /dev/null @@ -1,331 +0,0 @@ - - -

      From MySQL to MySQL

      -

      Supported Source and Destination Databases

      -
      - - - - - - - -
      Table 1 Supported databases

      Source DB

      -

      Destination DB

      -
      • On-premises MySQL databases
      • MySQL databases on an ECS
      -
      • On-premises MySQL databases
      • MySQL databases on an ECS
      -
      -
      -
      -

      Prerequisites

      • You have logged in to the DRS console.
      • For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
      -
      -

      Suggestions

      • When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
      • To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
      -
      -
      • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
      • Start your synchronization task during off-peak hours. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization. If you have to synchronize data during peak hours, you can select Yes for Flow Control to adjust the synchronization speed.
        • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
        • To ensure data consistency, tables to be synchronized without a primary key may be locked for 3s.
        • The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
        • Due to the inherent characteristics of MySQL, in certain scenarios the performance may be negatively affected. For example, if the CPU resources are insufficient and the storage engine is TokuDB, the read speed on tables may be decreased by 10%.
        • When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
        • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
        - -
      • Data-Level Comparison

        To obtain accurate comparison results, compare data at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

        -
      • For many-to-one synchronization tasks that involve the synchronization of the same table, DDL operations cannot be performed on source databases. Otherwise, all synchronization tasks fail.
      -
      -

      Precautions

      Before creating a synchronization task, read the following notes:

      - -
      - - - - - - - - - - - - - - - - - - - -
      Table 2 Precautions

      Type

      -

      Restrictions

      -

      Database permissions

      -
      • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT.
      • The destination database user must have the following permissions: SELECT, CREATE, DROP, DELETE, INSERT, UPDATE, ALTER, and REFERENCES.
      -

      Synchronization object

      -
      • Only tables, primary key indexes, unique indexes, common indexes, store procedures, views, and functions can be synchronized.
      -
      • During database mapping, the source database cannot contain stored procedures, views, or functions.
      • The databases to be mapped to the destination can only contain tables during synchronization. Otherwise, the synchronization task fails.

        If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

        -
      • Tables with storage engine different to MyISAM and InnoDB cannot be synchronized.
      • For an incremental synchronization task, ensure that the synchronization objects exist in the destination database.
      -

      Source database

      -
      • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
      • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
      • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
      • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
      • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
      • The source database names cannot contain non-ASCII characters, or the following characters: '<`>/\
      • The table and view names in the source database cannot contain non-ASCII characters, or special characters '<>/\
      • The source database name or mapped name cannot start with ib_logfile or be ib_buffer_pool, ib_doublewrite, ibdata1 or ibtmp1.
      • Tables with storage engine different to MyISAM and InnoDB cannot be synchronized to RDS.
      • Database mapping does not support views or stored procedures. If the source database contains views or stored procedures, the synchronization may fail.
      -

      Destination database

      -
      • Data cannot be synchronized from a newer version database to an older version database.
      -
      • The destination DB instance is running properly. If the destination DB instance type is primary/standby, the replication status must also be normal.
      • The destination DB instance must have sufficient storage space.
      • If the destination database (excluding MySQL system database) has the same name as the source database, the table structures in the destination database must be consistent with those in the source database.
      • The character set of the destination database must be the same as that of the source database.
      • The time zone of the destination database must be the same as that of the source database.
      • During a synchronization, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.
      • If the MyISAM tables are included in the synchronization objects, the sql_mode parameter in the destination database cannot contain the no_engine_substitution parameter. Otherwise, the synchronization fails.
      • The source database names mapped to the destination database cannot contain the following characters: dots (.), angle brackets (<>), backslash (\), and single quotation marks (')
      -

      Precautions

      -
      • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
      • Only MySQL to MySQL synchronization supports many-to-one synchronization. During table-level many-to-one synchronization, tables without primary keys cannot exist in the source database.
      • If the source or destination MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
      • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
      • The destination table can contain more columns than the source table. However, the following failures must be avoided:
        • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
        • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
        -
      • The source database does not support point-in-time recovery (PITR).
      • The destination database cannot be restored to a point in time when a full synchronization was being performed.
      • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
      • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
      • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
      • Set the expire_log_day parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
      • After a task is created, the destination database cannot be set to read-only.
      • A real-time synchronization task may fail due to the change of the username and password of the source or destination database. If it happens, rectify the information and then retry the synchronization task on the DRS console. Generally, you are advised not to modify the preceding information during synchronization.
      • If the source or destination database port is changed during data synchronization, the synchronization task fails. You can rectify the fault as follows:
        • If the source database port is wrong, correct the port number on the DRS console and then retry the synchronization task.
        • If the destination database port is wrong, DRS automatically changes the port to the correct one, and then you need to retry the synchronization task.

          Generally, do not modify the port number during synchronization.

          -
        -
      • During real-time synchronization, do not change the IP address.
      • DDL operations are not supported during full synchronization.
      • Data inconsistency may occur when the MyISAM table is modified during a full synchronization.
      • In a full plus incremental synchronization task, the source database cannot contain a table with the same name as a table without a primary key in the destination database.
      • For an incremental synchronization task, if the synchronization point is not precise, data inconsistency may occur.
      • During table-level incremental synchronization, only DDL operations on tables are allowed.
      • During an incremental synchronization of table-level objects, renaming tables is not recommended.
      • For an incremental synchronization task, the start point must be in the standard format. You can run the show master status command in the source database to obtain the start point.
        • If GTID mode is disabled, the format of the start point is File:Position (for example, mysql-bin.014734:8937).
        • After the GTID is enabled, the format of the start point is File:Position. Executed_Gtid_Set (for example, mysql-bin.014734:8937;ea352a82-e9a0-11ea-b650-fa163e1e82ed:1-23377228, 8404bb4b-cc96-11ea-ae7f-fa163ead1b99:1-59684135)
        -
      -
      -
      -
      -

      Procedure

      1. On the Data Synchronization Management page, click Create Synchronization Task.
      2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

        -

        - - - - - - - - - - - - - - - - -
        Table 3 Task and recipient description

        Parameter

        -

        Description

        -

        Region

        -

        The region where the synchronization instance is deployed. You can change the region.

        -

        Project

        -

        The project corresponds to the current region and can be changed.

        -

        Task Name

        -

        The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

        -

        Description

        -

        The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Table 4 Synchronization instance settings

        Parameter

        -

        Description

        -

        Data Flow

        -

        Choose Self-built to self-built.

        -

        Source DB Engine

        -

        Select MySQL.

        -

        Destination DB Engine

        -

        Select MySQL.

        -

        Network Type

        -

        The Public network is used as an example. Available options: Public network and VPN or Direct Connect

        -

        Instance Type

        -

        DRS instance type. The value can be single or primary/standby.

        -
        • primary/standby: This architecture provides HA, improving the reliability of DRS instances. After the primary and standby instances are created, the DRS creates an active subtask and a standby subtask at the same time. If the task on the active node is abnormal, the DRS automatically starts the task on the standby node to continue the synchronization, improving the reliability of the synchronization task.
        • Single: The single-node deployment architecture is used, which is cost-effective.
        -

        VPC

        -

        Select an available VPC.

        -

        Synchronization Instance Subnet

        -

        Select the subnet where the synchronization instance is located. You can also click View Subnet to go to the network console to view the subnet where the instance resides.

        -

        By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides and ensure that there are available IP addresses. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

        -

        Security Group

        -

        Select a security group. You can use security group rules to allow or deny access to the instance.

        -

        Synchronization Mode

        -

        Select Incremental.

        -
        • Full+Incremental

          This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

          -
          NOTE:

          If you select Full+Incremental, data generated during the full synchronization will be continuously synchronized to the destination database, and the source remains accessible.

          -
          -
        -
        • Incremental

          Through log parsing, incremental data generated on the source database is synchronized to the destination database.

          -

          During synchronization, the source database continues to provide services for external systems with zero downtime.

          -
        -

        AZ

        -

        Select the AZ where you want to create the DRS instance. Selecting the one housing the source or destination database can provide better performance.

        -

        If Instance Type is set to primary/standby, you can specify Primary AZ and Standby AZ.

        -

        Tags

        -
        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
        -
        -
        -

        If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

        -
        -

      3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

        -

        - - - - - - - - - - - - - - - - - - - -
        Table 5 Source database settings

        Parameter

        -

        Description

        -

        IP Address or Domain Name

        -

        The IP address or domain name of the source database.

        -

        Port

        -

        The port of the source database. Range: 1 – 65535

        -

        Database Username

        -

        The username for accessing the source database.

        -

        Database Password

        -

        The password for the database username.

        -

        SSL Connection

        -

        SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

        -
        NOTE:
        • The maximum size of a single certificate file that can be uploaded is 500 KB.
        • If SSL is disabled, your data may be at risk.
        -
        -
        -
        - -
        - - - - - - - - - - - - - - - - - - - -
        Table 6 Destination database settings

        Parameter

        -

        Description

        -

        IP Address or Domain Name

        -

        The IP address or domain name of the destination database.

        -

        Port

        -

        The port of the destination database. Range: 1 - 65535

        -

        Database Username

        -

        The username for accessing the destination database.

        -

        Database Password

        -

        The password for the database username.

        -

        SSL Connection

        -

        SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

        -
        NOTE:
        • The maximum size of a single certificate file that can be uploaded is 500 KB.
        • If the SSL certificate is not used, your data may be at risk.
        -
        -
        -
        -

        The username and password of the source and destination databases are encrypted and stored in DRS, and will be cleared after the task is deleted.

        -
        -

      4. On the Set Synchronization Task page, select the synchronization policy, objects, and data format, and click Next.

        -

        - - - - - - - - - - - - - - - - - - - -
        Table 7 Synchronization mode and object

        Parameter

        -

        Description

        -

        Conflict Policy

        -

        The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored. Select any of the following conflict policies:

        -
        • Ignore

          The system will skip the conflicting data and continue the subsequent synchronization process.

          -
        • Report error

          The synchronization task will be stopped and fail.

          -
        • Overwrite

          Conflicting data will be overwritten.

          -
        -

        Filter DROP DATABASE

        -

        During real-time synchronization, executing DDL operations on the source database may affect the synchronization performance. To reduce the risk of synchronization failure, DRS allows you to filter out DDL operations. Currently, only the delete operations on databases can be filtered by default.

        -
        • If you select Yes, the database deletion operation performed on the source database is not synchronized during data synchronization.
        • If you select No, related operations are synchronized to the destination database during data synchronization.
        -

        Synchronize

        -

        Supports index synchronization. You can determine whether to synchronize indexes based on the service requirements. If you deselect Normal index, DDL statements related to index adding will be filtered out in the incremental phase. If the DDL statements contain other operations, they may also be filtered out.

        -

        Start Point

        -

        The position where the incremental log was created based on the source log. It allows you to perform resumable data transfer.

        -

        For an incremental synchronization task, the start point must be in the standard format. You can run the show master status command in the source database to obtain the start point.

        -
        • If GTID mode is disabled, the format of the start point is File:Position (for example, mysql-bin.014734:8937).
        • After the GTID is enabled, the format of the start point is File:Position; Executed_Gtid_Set (for example, mysql-bin.014734:8937;ea352a82-e9a0-11ea-b650-fa163e1e82ed:1-23377228, 8404bb4b-cc96-11ea-ae7f-fa163ead1b99:1-59684135)
        -

        Synchronization Object

        -

        Select Tables, Databases, or Import object file as required.

        -
        NOTE:
        • To quickly select the desired database objects, you can use the search function.
        • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
        -
        • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
        • The name of the selected synchronization object cannot contain spaces.
        -
        -
        -
        -

      5. On the Process Data page, set the filtering rules for data processing.

        • If you do not need to set a processing rule, select No processing and click Next.
        • If you need to set data processing rules, configure related filtering rules by referring to Processing Data.
        -

      6. On the Check Task page, check the synchronization task.

        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
        • If all check items are successful, click Next.

          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

          -
          -
        -

      7. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

        -

        - - - - - - - -
        Table 8 Task startup settings

        Parameter

        -

        Description

        -

        Started Time

        -

        Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

        -
        NOTE:

        After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

        -
        -
        -
        -

      8. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

        • You can view the task status. For more information about task status, see Task Statuses.
        • You can click in the upper-right corner to view the latest task status.
        -

      -
      -
      -
      -
      -
      Parent topic: Between Self-built Databases
      -
      -
      - diff --git a/docs/drs/umn/drs_03_1124.html b/docs/drs/umn/drs_03_1124.html index f5a582760..96a72b991 100644 --- a/docs/drs/umn/drs_03_1124.html +++ b/docs/drs/umn/drs_03_1124.html @@ -1,6 +1,6 @@ -

      From MySQL to GaussDB(for MySQL) Primary/Standby

      +

      From MySQL to TaurusDB Cluster

      Supported Source and Destination Databases

      @@ -10,7 +10,7 @@ - @@ -22,7 +22,7 @@

      Suggestions

      • When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
      • To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
      • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
      • Start your synchronization task during off-peak hours. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization.
        • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
        • To ensure data consistency, tables to be synchronized without a primary key may be locked for 3s.
        • The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
        • Due to the inherent characteristics of MySQL, in certain scenarios the performance may be negatively affected. For example, if the CPU resources are insufficient and the storage engine is TokuDB, the read speed on tables may be decreased by 10%.
        • When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
        • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
        -
      • Data-Level Comparison

        To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

        +
      • Data-Level Comparison

        To obtain accurate comparison results, compare data at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

      Precautions

      Before creating a synchronization task, read the following notes:

      @@ -35,7 +35,7 @@
      - @@ -59,7 +59,7 @@ - @@ -67,7 +67,7 @@
      Table 1 Supported databases

      Source DB
      • On-premises MySQL databases
      • MySQL databases on an ECS
      • MySQL databases on other clouds
      • RDS for MySQL
      • GaussDB(for MySQL) primary/standby
      +
      • TaurusDB Cluster

      Database permissions

      • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT.
      • The destination database user must have the SELECT, CREATE, DROP, DELETE, INSERT, UPDATE, ALTER, CREATE VIEW, CREATE ROUTINE, REFERENCES permissions. By default, the root account of the GaussDB(for MySQL) instance has the preceding permissions.

        If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

        +
      • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT.
      • The destination database user must have the SELECT, CREATE, DROP, DELETE, INSERT, UPDATE, ALTER, CREATE VIEW, CREATE ROUTINE, REFERENCES permissions. By default, the root account of the TaurusDB instance has the preceding permissions.

        If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

      Precautions

      • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
      • If the sources and destinations are RDS instances, database mapping is required.
      • The source and destination databases cannot contain tables that have the same names but do not have primary keys.
      • If the source and destination sides are RDS MySQL instances, tables encrypted using TDE cannot be synchronized.
      • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
      • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
      • The destination table can contain more columns than the source table. However, the following failures must be avoided:
        • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
        • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
        +
      • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
      • If the sources and destinations are RDS instances, database mapping is required.
      • The source and destination databases cannot contain tables that have the same names but do not have primary keys.
      • If the source and destination DB instances are RDS for MySQL instances, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
      • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
      • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
      • The destination table can contain more columns than the source table. However, the following failures must be avoided:
        • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
        • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
      • The source database does not support point-in-time recovery (PITR).
      • The destination database cannot be restored to a point in time when a full synchronization was being performed.
      • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
      • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
      • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
      • After a task is created, the destination database cannot be set to read-only.
      • During synchronization, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
      • Data inconsistency may occur when the MyISAM table is modified during a full synchronization.
      • DDL operations are not supported during full synchronization.
      • Incremental synchronization supports table renaming. Ensure that both the source and destination tables are selected.
      • If you use additional columns and the number of columns in a single table exceeds 500, adding additional columns may lead to the number of columns in a table to reach an upper limit and cause the task to fail.
      • Set the expire_log_day parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
      -

      Procedure

      This section uses real-time synchronization from MySQL to GaussDB(for MySQL) primary/standby as an example to describe how to configure a real-time synchronization task.

      +

      Procedure

      This section uses real-time synchronization from MySQL to TaurusDB Cluster as an example to describe how to configure a real-time synchronization task.

      1. On the Data Synchronization Management page, click Create Synchronization Task.
      2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

        @@ -117,7 +117,7 @@ - - + + + @@ -274,7 +278,7 @@

      3. On the Check Task page, check the synchronization task.

        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
        • If all check items are successful, click Next.

          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

        -

      4. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

        +

      5. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

        6. Table 3 Task and recipient description

        Parameter

        Destination DB Engine

        Select GaussDB(for MySQL) Primary/Standby Edition.

        +

        Select TaurusDB Cluster.

        Network Type

        @@ -127,7 +127,7 @@

        Destination DB Instance

        An available GaussDB(for MySQL) primary/standby instance.

        +

        An available TaurusDB Cluster instance.

        Synchronization Instance Subnet

        @@ -146,6 +146,11 @@

        Specifications

        +

        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

        +

        Tags
        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
        @@ -255,15 +260,14 @@

        Whether to synchronize normal indexes.

        By default, DRS synchronizes the primary key or unique index. A normal index refers to an index other than the primary key or unique index. If you select normal index, all indexes will be synchronized. If you do not select normal index, only the primary key and unique index will be synchronized.

        -

        If you deselect Normal index, DDL statements related to index adding will be filtered out in the incremental phase. If the DDL statements contain other operations, they may also be filtered out.

        Synchronization Object

        Select Tables or Databases as required.

        -
        • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

          If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

          +
          • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

            If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

          -
          NOTE:
          • To quickly select the desired database objects, you can use the search function.
          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
          +
          NOTE:
          • You can search for table names to quickly select the required database objects.
          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
          • The name of the selected synchronization object cannot contain spaces.
        Table 8 Task startup settings

        Parameter

        Description

        @@ -291,7 +295,7 @@
        -

      6. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

        • You can view the task status. For more information about task status, see Task Statuses.
        • You can click in the upper-right corner to view the latest task status.
        +

      7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

        • You can view the task status. For more information about task status, see Task Statuses.
        • You can click in the upper-right corner to view the latest task status.
        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

      diff --git a/docs/drs/umn/drs_03_1131.html b/docs/drs/umn/drs_03_1131.html index 5c30db4ec..197b485eb 100644 --- a/docs/drs/umn/drs_03_1131.html +++ b/docs/drs/umn/drs_03_1131.html @@ -1,10 +1,10 @@ -

      Forcibly Stopping Synchronization of GaussDB Distributed

      -

      This section describes how to clear the streaming replication slots of the source GaussDB distributed database after the incremental or full+incremental synchronization task is forcibly stopped.

      -

      Prerequisites

      Common users do not have the permission to perform the execute direct operation. To delete streaming replication slots, contact GaussDB O&M personnel.

      +

      Forcibly Stopping Synchronization from GaussDB Distributed

      +

      This section describes how to delete streaming replication slots of the source distributed GaussDB database after an incremental or a full+incremental synchronization task is forcibly stopped.

      +

      Prerequisites

      Common users do not have the permission to perform EXECUTE DIRECT. To delete streaming replication slots, contact GaussDB O&M personnel.

      -

      Procedure

      1. Log in to each primary DN node of GaussDB distributed instance as the user used when you tested the connectivity between the DRS instance and the GaussDB distributed instance.
      2. Run the following statement to query the streaming replication slot name of the database object selected for the synchronization task:

        select slot_name from pg_replication_slots where database = 'database';
        +

        Procedure

        1. Log in to each primary DN node of the distributed GaussDB instance as the user used when you tested the connectivity between the DRS instance and the distributed GaussDB instance.
        2. Run the following statement to query the streaming replication slot name of the database object selected for the synchronization task:

          select slot_name from pg_replication_slots where database = 'database';

          In the preceding command, database indicates the database selected in the synchronization task.

        3. Run the following statement to delete the streaming replication slot:

          select * from pg_drop_replication_slot('slot_name');
          diff --git a/docs/drs/umn/drs_03_1134.html b/docs/drs/umn/drs_03_1134.html index 63a87bed2..926d5f1fa 100644 --- a/docs/drs/umn/drs_03_1134.html +++ b/docs/drs/umn/drs_03_1134.html @@ -6,7 +6,7 @@
          • Task name
          • Description
          • Task start time

          Prerequisites

          You have logged in to the DRS console.

          -

          Procedure

          1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
          2. On the Basic Information tab, locate the information to be modified in the Task Information area.

            • You can click to modify the task name and description.
              • To submit the change, click .
              • To cancel the change, click .
              +

              Procedure

              1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
              2. On the Basic Information tab, locate the information to be modified in the Task Information area.

                • You can click to modify the task name and description.
                  • To submit the change, click .
                  • To cancel the change, click .
                  diff --git a/docs/drs/umn/drs_04_0002.html b/docs/drs/umn/drs_04_0002.html index c39399867..276a69566 100644 --- a/docs/drs/umn/drs_04_0002.html +++ b/docs/drs/umn/drs_04_0002.html @@ -4,7 +4,7 @@

                  The Basic Information page of a backup migration task displays information about the task, backup files, and databases. This section describes how to view details about current migration task.

                  Prerequisites

                  You have logged in to the DRS console.

                  -

                  Procedure

                  • In the task list, only tasks created by the current login user are displayed. Tasks created by different users of the same tenant are not displayed.
                  +

                  Procedure

                  The task list displays all tasks under the tenant to which the current login user belongs and for which the login user has the query permission. Tasks created by different users of the same tenant are displayed.

                  1. On the Backup Migration Management page, click the target migration task name in the Task Name/ID column.
                  2. On the displayed Basic Information tab, view details about the migration task.

                    You can view information about the task, backup files, and databases.

                  diff --git a/docs/drs/umn/drs_04_0005.html b/docs/drs/umn/drs_04_0005.html index 0e498c47a..e712ae353 100644 --- a/docs/drs/umn/drs_04_0005.html +++ b/docs/drs/umn/drs_04_0005.html @@ -4,7 +4,7 @@

                  This section describes how to view details about a migration task, including information about the task, replication instance, and migration.

                  Prerequisites

                  • You have logged in to the DRS console.
                  • A migration task has been created.
                  -

                  Procedure

                  • In the task list, only tasks created by the current login user are displayed. Tasks created by different users of the same tenant are not displayed.
                  • For a task whose source database is MySQL Schema and Logic Table or DDM, the task details of each subtask contain the information about the source and destination databases corresponding to the subtask.
                  +

                  Procedure

                  • The task list displays all tasks under the tenant to which the current login user belongs and for which the login user has the query permission. Tasks created by different users of the same tenant are displayed.
                  • For a task whose source database is MySQL Schema and Logic Table or DDM, the task details of each subtask contain the information about the source and destination databases corresponding to the subtask.
                  1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                  2. On the displayed Basic Information tab, view details about the migration task.

                    You can view information about the task, replication instance, and migration.

                  diff --git a/docs/drs/umn/drs_04_0006.html b/docs/drs/umn/drs_04_0006.html index 11eecbb1a..99848b4c6 100644 --- a/docs/drs/umn/drs_04_0006.html +++ b/docs/drs/umn/drs_04_0006.html @@ -6,9 +6,9 @@
                  • Task name
                  • Description
                  • Task start time

                  Prerequisites

                  • You have logged in to the DRS console.
                  • A migration task has been created.
                  -

                  Procedure

                  1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                  2. On the Basic Information tab, locate the information to be modified in the Task Information area.

                    • You can click to modify the task name and description.
                      • To submit the change, click .
                      • To cancel the change, click .
                      +

                      Procedure

                      1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                      2. On the Basic Information tab, locate the information to be modified in the Task Information area.

                        • You can click to modify the task name and description.
                          • To submit the change, click .
                          • To cancel the change, click .
                          -
                  Table 1 Real-time DR task information

                  Task Information

                  Table 1 Task information

                  Task Information

                  +
                  diff --git a/docs/drs/umn/drs_04_0008.html b/docs/drs/umn/drs_04_0008.html index 4bc07336a..785937268 100644 --- a/docs/drs/umn/drs_04_0008.html +++ b/docs/drs/umn/drs_04_0008.html @@ -6,7 +6,7 @@
                  • Task name
                  • Description

                  Prerequisites

                  You have logged in to the DRS console.

                  -

                  Procedure

                  1. On the Backup Migration Management page, click the target migration task name in the Task Name/ID column.
                  2. On the Basic Information page, click next to the information to modify.

                    • To submit the change, click .
                    • To cancel the change, click .
                    +

                    Procedure

                    1. On the Backup Migration Management page, click the target migration task name in the Task Name/ID column.
                    2. On the Basic Information page, click next to the information to modify.

                      • To submit the change, click .
                      • To cancel the change, click .
                  Table 1 Task information

                  Task Information

                  Description
                  diff --git a/docs/drs/umn/drs_04_0030.html b/docs/drs/umn/drs_04_0030.html index 096a76691..7ff6ceb2c 100644 --- a/docs/drs/umn/drs_04_0030.html +++ b/docs/drs/umn/drs_04_0030.html @@ -4,301 +4,303 @@

                  Based on MySQL 5.7, some new features have been added to MySQL 8.0. There are performance differences between the two versions. Before migration, you need to analyze compatibility and provide a corresponding solution. The following shows the analysis:

                  • Compatibility analysis

                    MySQL 8.0 and MySQL 5.7 Community Edition are analyzed as follows:

                    1. Compatibility does not affect migration, but the solutions are different. -
                  Table 1 Task information description

                  Task Information

                  Compatibility

                  +
                  + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

                  Compatibility

                  +

                  Check Item

                  +

                  Function

                  +

                  Status

                  +

                  Solution

                  +

                  Data types or functions

                  Check Item

                  +

                  ENCODE()

                  Function

                  +

                  Encryption

                  Status

                  +

                  Deleted

                  Solution

                  +

                  Replaced by AES_ENCRYPT()

                  Data types or functions

                  +

                  DECODE()

                  ENCODE()

                  +

                  Decryption

                  Encryption

                  +

                  Deleted

                  Deleted

                  -

                  Replaced by AES_ENCRYPT()

                  +

                  Replaced by AES_DECRYPT()

                  DECODE()

                  +

                  ENCRYPT()

                  Decryption

                  +

                  Encryption

                  Deleted

                  +

                  Deleted

                  Replaced by AES_DECRYPT()

                  +

                  Replaced by SHA2()

                  ENCRYPT()

                  +

                  DES_ENCRYPT()

                  Encryption

                  +

                  Encryption

                  Deleted

                  +

                  Deleted

                  Replaced by SHA2()

                  +

                  Replaced by AES_ENCRYPT()

                  DES_ENCRYPT()

                  +

                  DES_DECRYPT()

                  Encryption

                  +

                  Decryption

                  Deleted

                  +

                  Deleted

                  Replaced by AES_ENCRYPT()

                  +

                  Replaced by AES_DECRYPT()

                  DES_DECRYPT()

                  +

                  JSON_APPEND()

                  Decryption

                  +

                  Adds JSON elements.

                  Deleted

                  +

                  Deleted

                  Replaced by AES_DECRYPT()

                  +

                  Replaced by JSON_ARRAY_APPEND()

                  JSON_APPEND()

                  +

                  PASSWORD()

                  Adds JSON elements.

                  +

                  Changes a user password.

                  Deleted

                  +

                  Deleted

                  Replaced by JSON_ARRAY_APPEND()

                  +

                  ALTER USER user IDENTIFIED BY 'auth_string';

                  PASSWORD()

                  +

                  JSON_MERGE()

                  Changes a user password.

                  +

                  Merges multiple JSONs.

                  Deleted

                  +

                  Discarded

                  ALTER USER user IDENTIFIED BY 'auth_string';

                  +

                  Replaced by JSON_MERGE_PERSERVE()

                  JSON_MERGE()

                  +

                  SQL MODE

                  Merges multiple JSONs.

                  +

                  NO_AUTO_CREATE_USER, DB2, MAXDB, MSSQL, MYSQL323, MYSQL40, ORACLE, POSTGRESQL, NO_FIELD_OPTIONS, NO_KEY_OPTIONS, NO_TABLE_OPTIONS

                  Discarded

                  +

                  -

                  Replaced by JSON_MERGE_PERSERVE()

                  +

                  Deleted

                  +

                  -

                  SQL MODE

                  +

                  Foreign key constraint length

                  NO_AUTO_CREATE_USER, DB2, MAXDB, MSSQL, MYSQL323, MYSQL40, ORACLE, POSTGRESQL, NO_FIELD_OPTIONS, NO_KEY_OPTIONS, NO_TABLE_OPTIONS

                  +

                  The constraint name cannot be greater than 64 characters.

                  -

                  +

                  -

                  Deleted

                  +

                  -

                  -

                  -

                  Foreign key constraint length

                  -

                  The constraint name cannot be greater than 64 characters.

                  -

                  -

                  -

                  -

                  -

                  SELECT TABLE_SCHEMA, TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME IN (SELECT LEFT(SUBSTR(ID,INSTR(ID,'/')+1), INSTR(SUBSTR(ID,INSTR(ID,'/')+1),'_ibfk_')-1) FROM INFORMATION_SCHEMA.INNODB_SYS_FOREIGN WHERE LENGTH(SUBSTR(ID,INSTR(ID,'/')+1))>64);

                  +

                  SELECT TABLE_SCHEMA, TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME IN (SELECT LEFT(SUBSTR(ID,INSTR(ID,'/')+1), INSTR(SUBSTR(ID,INSTR(ID,'/')+1),'_ibfk_')-1) FROM INFORMATION_SCHEMA.INNODB_SYS_FOREIGN WHERE LENGTH(SUBSTR(ID,INSTR(ID,'/')+1))>64);

                  Use the ALTER TABLE statement to adjust the length.

                  Features

                  +

                  Features

                  Use the GRANT statement to create users.

                  +

                  Use the GRANT statement to create users.

                  -

                  +

                  -

                  Deleted

                  +

                  Deleted

                  CREATE USER

                  +

                  CREATE USER

                  Use the GRANT statement to modify user information.

                  +

                  Use the GRANT statement to modify user information.

                  -

                  +

                  -

                  Deleted

                  +

                  Deleted

                  ALTER USER

                  +

                  ALTER USER

                  IDENTIFIED BY PASSWORD 'auth_string'

                  +

                  IDENTIFIED BY PASSWORD 'auth_string'

                  Sets new passwords

                  +

                  Sets new passwords

                  Deleted

                  +

                  Deleted

                  IDENTIFIED WITH auth_plugin AS 'auth_string'

                  +

                  IDENTIFIED WITH auth_plugin AS 'auth_string'

                  \N in a SQL statement

                  +

                  \N in a SQL statement

                  NULL

                  +

                  NULL

                  Deleted

                  +

                  Deleted

                  Replaced by NULL

                  +

                  Replaced by NULL

                  PROCEDURE ANALYSE() syntax

                  +

                  PROCEDURE ANALYSE() syntax

                  Specifies the recommended field type is provided after the MySQL field value is analyzed.

                  +

                  Specifies the recommended field type is provided after the MySQL field value is analyzed.

                  Deleted

                  +

                  Deleted

                  -

                  +

                  -

                  Spatial functions

                  +

                  Spatial functions

                  -

                  +

                  -

                  -

                  +

                  -

                  -

                  +

                  -

                  mysql_install_db

                  +

                  mysql_install_db

                  Initialization

                  +

                  Initialization

                  Deleted

                  +

                  Deleted

                  mysqld --initialize or --initialize-insecure

                  +

                  mysqld --initialize or --initialize-insecure
                • The following items affect the migration. You need to check in advance. -

                  Compatibility

                  +
                  + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -690,91 +692,92 @@
                • Remove system variables.

                  The analysis of MySQL 5.7 and 8.0 Community Edition shows that removing system variables does not affect migration.

                  -

                  • Compatibility

                  +

                  Check Item

                  +

                  Function

                  +

                  Status

                  +

                  Solution

                  +

                  Original Usage

                  +

                  Reserving keywords

                  Check Item

                  +

                  cume_dist, dense_rank, empty, except, first_value, grouping, groups, json_table, lag, last_value, lateral, lead, nth_value, ntile, of, over, percent_rank, rank, recursive,row_number, system, window

                  Function

                  +

                  -

                  Status

                  +

                  Added

                  Solution

                  +

                  SET sql_mode = 'ANSI_QUOTES'

                  Original Usage

                  +

                  Name: database, table, index, column, alias, view, stored procedure, partition, and tablespace

                  Reserving keywords

                  +

                  Character set

                  cume_dist, dense_rank, empty, except, first_value, grouping, groups, json_table, lag, last_value, lateral, lead, nth_value, ntile, of, over, percent_rank, rank, recursive,row_number, system, window

                  +

                  UTF8MB3

                  -

                  +

                  -

                  Added

                  +

                  Discarded

                  SET sql_mode = 'ANSI_QUOTES'

                  +

                  Replaced by UTF8MB4.

                  Name: database, table, index, column, alias, view, stored procedure, partition, and tablespace

                  +

                  -

                  Character set

                  +

                  Partition table name

                  UTF8MB3

                  +

                  Partition tables of storage engines that do not support local partitions are not allowed.

                  -

                  +

                  -

                  Discarded

                  +

                  Deleted

                  Replaced by UTF8MB4.

                  -

                  -

                  -

                  Partition table name

                  -

                  Partition tables of storage engines that do not support local partitions are not allowed.

                  -

                  -

                  -

                  Deleted

                  -

                  SELECT TABLE_SCHEMA, TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE ENGINE NOT IN ('innodb', 'ndbcluster') AND CREATE_OPTIONS LIKE '%partitioned%';

                  +

                  SELECT TABLE_SCHEMA, TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE ENGINE NOT IN ('innodb', 'ndbcluster') AND CREATE_OPTIONS LIKE '%partitioned%';

                  You can use either of the following methods:

                  (1) ALTER TABLE table_name ENGINE=INNODB;

                  (2) ALTER TABLE table_name REMOVE PARTITIONING;

                  MyISAM is not supported.

                  +

                  MyISAM is not supported.

                  Syntax

                  +

                  Syntax

                  group by... asc/desc

                  +

                  group by... asc/desc

                  Ascending/Descending

                  +

                  Ascending/Descending

                  Deleted

                  +

                  Deleted

                  Replaced by the ORDER By clause.

                  +

                  Replaced by the ORDER By clause.

                  View and function

                  +

                  View and function

                  Name length

                  +

                  Name length

                  The view name cannot be greater than 64 characters.

                  +

                  The view name cannot be greater than 64 characters.

                  -

                  +

                  -

                  -

                  +

                  -

                  ALTER

                  +

                  ALTER

                  The value can contain a maximum of 255 characters.

                  +

                  The value can contain a maximum of 255 characters.

                  The enum or set element contains a maximum of 255 characters.

                  +

                  The enum or set element contains a maximum of 255 characters.

                  -

                  +

                  -

                  -

                  +

                  -

                  Handled by users.

                  +

                  Handled by users.

                  The value can contain a maximum of 64 KB.

                  +

                  The value can contain a maximum of 64 KB.

                  Upper and lower case letters

                  +

                  Upper and lower case letters

                  lower_case_table_names

                  +

                  lower_case_table_names

                  Specifies whether to set the MySQL table name case sensitive.

                  +

                  Specifies whether to set the MySQL table name case sensitive.

                  -

                  +

                  -

                  If this parameter is set to 1 during the upgrade, ensure that the schema and table names are in lowercase.

                  +

                  If this parameter is set to 1 during the upgrade, ensure that the schema and table names are in lowercase.

                  SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME != LOWER(TABLE_NAME) AND TABLE_TYPE = 'BASE TABLE';

                  SELECT SCHEMA_NAME FROM INFORMATION_SCHEMA.SCHEMATA WHERE SCHEMA_NAME != LOWER(SCHEMA_NAME);

                  -

                  +

                  -

                  Triggers

                  +

                  Triggers

                  Check whether there is an empty definition or invalid creation context.

                  +

                  Check whether there is an empty definition or invalid creation context.

                  -

                  +

                  -

                  -

                  +

                  -

                  Use the SHOW TRIGGERS statement to check the character_set_client, collation_connection, and Database Collation attributes.

                  +

                  Use the SHOW TRIGGERS statement to check the character_set_client, collation_connection, and Database Collation attributes.

                  -

                  +

                  -

                  System variables

                  +
                  + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/drs/umn/drs_04_0088.html b/docs/drs/umn/drs_04_0088.html index 24ef85985..2bb5f6ca8 100644 --- a/docs/drs/umn/drs_04_0088.html +++ b/docs/drs/umn/drs_04_0088.html @@ -41,29 +41,31 @@

                  Database Account Permission Requirements

                  To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                  +
                  • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                  • After changing the account passwords for the source and destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                  +
                  -

                  System variables

                  +

                  innodb_locks_unsafe_for_binlog

                  innodb_locks_unsafe_for_binlog

                  +

                  log_builtin_as_identified_by_password

                  log_builtin_as_identified_by_password

                  +

                  old_passwords

                  old_passwords

                  +

                  query_cache_limit

                  query_cache_limit

                  +

                  query_cache_min_res_unit

                  query_cache_min_res_unit

                  +

                  query_cache_size

                  query_cache_size

                  +

                  query_cache_type

                  query_cache_type

                  +

                  query_cache_wlock_invalidate

                  query_cache_wlock_invalidate

                  +

                  ndb_cache_check_time

                  ndb_cache_check_time

                  +

                  ignore_db_dirs

                  ignore_db_dirs

                  +

                  tx_isolation

                  tx_isolation

                  +

                  tx_read_only

                  tx_read_only

                  +

                  sync_frm

                  sync_frm

                  +

                  secure_auth

                  secure_auth

                  +

                  multi_range_count

                  multi_range_count

                  +

                  log_error_verbosity

                  log_error_verbosity

                  +

                  sql_log_bin

                  sql_log_bin

                  +

                  metadata_locks_cache_size

                  metadata_locks_cache_size

                  +

                  metadata_locks_hash_instances

                  metadata_locks_hash_instances

                  +

                  date_format

                  date_format

                  +

                  datetime_format

                  datetime_format

                  +

                  time_format

                  time_format

                  +

                  max_tmp_tables

                  max_tmp_tables

                  +

                  ignore_builtin_innodb

                  ignore_builtin_innodb

                  +

                  innodb_support_xa

                  innodb_support_xa

                  +

                  innodb_undo_logs

                  innodb_undo_logs

                  +

                  innodb_undo_tablespaces

                  innodb_undo_tablespaces

                  -

                  internal_tmp_disk_storage_engine

                  +

                  internal_tmp_disk_storage_engine
                  - @@ -39,41 +39,43 @@

                  Database Account Permission Requirements

                  To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                  +
                  • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                  • After changing the account passwords for the source and destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                  +
                  -
                  Table 3 Database account permission

                  Type

                  +
                  - - - - - - - @@ -94,7 +96,7 @@
                  • Source database object requirements:
                    • If the source database is an on-premises database and has Percona Server for MySQL 5.6.x or Percona Server for MySQL 5.7.x installed, the memory manager must use Jemalloc to prevent Out of Memory errors caused by frequent queries on system tables.
                    • The source database does not support the mysql binlog dump command.
                    • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                    • Associated objects must be migrated at the same time to avoid migration failure caused by missing associated objects.
                    • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                    • Due to the MySQL constraints, if the one-time event triggering time of the source database is earlier than the migration start time, the event will not be migrated to the destination database.
                  • Destination database parameter requirements:
                    • The destination DB instance is running properly.
                    • The destination DB instance must have sufficient storage space.
                    • You are advised to use the row-based binlog in the destination database. Otherwise, an error may occur during an incremental migration.
                    • The destination database isolation level must be set to at least read committed.
                    • During migration, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.
                    • Enable GTID of the destination database.
                    • The character sets of the source and destination databases must be the same. Otherwise, the migration fails.
                    • The log_bin_trust_function_creators parameter value of the destination database must be set to on. Otherwise, the migration fails.
                    • The value of server_uuid of the destination database must be the same as that of the source database. Otherwise, the incremental migration fails.
                    • The collation_server values of the destination database and source database must be the same. Otherwise, the migration may fail.
                    • The value of time_zone of the destination database must be the same as that of the source database. Otherwise, the migration may fail.
                    • The sql_mode values of the destination database and source database must be the same. Otherwise, the migration may fail.
                    • The innodb_strict_mode values of the destination database and source database must be the same. Otherwise, the migration may fail.
                    • The lower_case_table_names values of the source and destination databases must be the same. Otherwise, the migration fails.
                    • If the MyISAM tables are included in the migration objects, the sql_mode parameter in the destination database cannot contain the no_engine_substitution parameter. Otherwise, the migration fails.
                  • Destination database object requirements:
                    • The destination DB instance cannot contain databases with the same name as the source databases (except the MySQL system database).
                    -
                  • Other notes:
                    • When creating multiple migration tasks in the many-to-one scenario, ensure that the read and write settings of the destination database are consistent in these tasks.
                    • The table without a primary key lacks a unique identifier for rows. When the network is unstable, you may need to retry the task several times, or data inconsistency may occur.
                    • The destination database cannot be restored to a point in time when a full migration was being performed.
                    • If the source and destination sides are RDS MySQL instances, transparent data encryption (TDE) is not supported, and tables with the encryption function cannot be created.
                    • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                    • The destination database of a migration task can be set to Read-only or Read/Write.

                      Read-only: During the migration, the destination database is read-only. After the migration is complete, it restores to the read/write status. This option ensures the integrity and success rate of data migration.

                      +
                    • Other notes:
                      • When creating multiple migration tasks in the many-to-one scenario, ensure that the read and write settings of the destination database are consistent in these tasks.
                      • The table without a primary key lacks a unique identifier for rows. When the network is unstable, you may need to retry the task several times, or data inconsistency may occur.
                      • The destination database cannot be restored to a point in time when a full migration was being performed.
                      • If the source and destination DB instances are RDS for MySQL instances, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                      • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                      • The destination database of a migration task can be set to Read-only or Read/Write.

                        Read-only: During the migration, the destination database is read-only. After the migration is complete, it restores to the read/write status. This option ensures the integrity and success rate of data migration.

                        Read/Write: During the migration, the destination instance can be queried or modified. Data being migrated may be modified when operations are performed or applications are connected. It should be noted that background processes can often generate or modify data, which may result in data conflicts, task faults, and upload failures. Do not select this option if you do not fully understand the risks.

                    @@ -124,7 +126,7 @@

                    Prerequisites

                    • You have logged in to the DRS console.
                    • For details about the DB types and versions supported by real-time migration, see Real-Time Migration.
                    -

                    Procedure

                    This section uses the migration from MySQL to RDS MySQL in a VPC as an example to describe how to configure a migration task on the DRS console.

                    +

                    Procedure

                    This section uses the migration from MySQL to RDS for MySQL in a VPC as an example to describe how to configure a migration task on the DRS console.

                    1. On the Online Migration Management page, click Create Migration Task.
                    2. On the Create Replication Instance page, configure task details, description, and the replication instance, and click Next.

                      • Task information description
                  Table 3 Database account permission

                  Type

                  Full Migration

                  +

                  Full Migration

                  Full+Incremental Migration

                  +

                  Full+Incremental Migration

                  Source database user

                  +

                  Source database user

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, SHOW VIEW, and EVENT

                  The user must have the SELECT permission for mysql.user.

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                  The user must have the SELECT permission for mysql.user.

                  Destination database user

                  +

                  Destination database user

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, INDEX, EVENT, CREATE VIEW, CREATE ROUTINE, TRIGGER, REFERENCES, and WITH GRANT OPTION. If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                  To migrate data, you must have the SELECT, INSERT, UPDATE, and DELETE permissions for the MySQL database.

                  @@ -282,7 +284,7 @@ @@ -379,10 +381,10 @@ @@ -422,7 +424,7 @@ -

                • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                  +

                • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                  • Table 5 Task information

                  Parameter

                  SSL Connection

                  SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                  -
                  NOTE:
                  • The maximum size of a single certificate file that can be uploaded is 500 KB.
                  • If SSL is disabled, your data may be at risk.
                  +
                  NOTE:
                  • The maximum size of a single certificate file that can be uploaded is 500 KB.
                  • If the SSL certificate is not used, your data may be at risk.

                  Migrate Account

                  During a database migration, accounts need to be migrated separately.

                  -
                  There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements. If you select Yes, you can select the accounts to be migrated as required.
                  • Yes

                    If you need to migrate accounts, see Migrating Accounts.

                    +
                    There are accounts that can be migrated completely, accounts whose permissions need to be reduced, and accounts that cannot be migrated. You can choose whether to migrate the accounts based on service requirements. If you select Yes, you can select the accounts to be migrated as required.
                    -
                    • No

                      During migration, accounts, permissions, and passwords are not migrated.

                      +
                      • No

                        During migration, accounts, permissions, and passwords are not migrated.
                  Table 12 Task startup settings

                  Parameter

                  Description

                  @@ -439,7 +441,7 @@
                  -

                • After the task is submitted, view and manage it on the Online Migration Management page.

                  • You can view the task status. For more information about task status, see Task Statuses.
                  • You can click in the upper right corner to view the latest task status.
                  +

                • After the task is submitted, view and manage it on the Online Migration Management page.

                  • You can view the task status. For more information about task status, see Task Statuses.
                  • You can click in the upper right corner to view the latest task status.
                  • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                  • diff --git a/docs/drs/umn/drs_04_0089.html b/docs/drs/umn/drs_04_0089.html index 1a16226c7..16c175def 100644 --- a/docs/drs/umn/drs_04_0089.html +++ b/docs/drs/umn/drs_04_0089.html @@ -27,9 +27,9 @@

                  Migration objects

                  • Migration object level: table level
                  • Supported migration objects:
                    • Only the source database data can be migrated. The table structure and other database objects of the source database cannot be migrated.
                    • The system database and event statuses cannot be migrated.
                    • Tables with storage engine different to MyISAM and InnoDB tables cannot be migrated.
                    • Tables without primary keys cannot be migrated.
                    • Cascade operations cannot be performed on tables with foreign keys.
                    +
                  • Migration object level: table level
                  • Supported migration objects:
                    • Only the source database data can be migrated. The table structure and other database objects of the source database cannot be migrated.
                    • The system database and event statuses cannot be migrated.
                    • Tables with storage engine different to MyISAM and InnoDB tables cannot be migrated.
                    • Tables without primary keys cannot be migrated.
                    • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                    NOTE:

                    The objects that can be migrated have the following constraints:

                    -
                    • The names of the source databases and tables cannot contain non-ASCII characters, or special characters <'>`/\"
                    • The source database name cannot start with ib_logfile and cannot be ib_buffer_pool, ib_doublewrite, ibdata1 or ibtmp1.
                    +
                    • The names of the source databases and tables cannot contain non-ASCII characters, or special characters <'>`/\"
                    • The source database name cannot start with ib_logfile and cannot be ib_buffer_pool, ib_doublewrite, ibdata1 or ibtmp1.
                  Table 3 Database account permission

                  Type

                  +
                  - - - - - - -
                  Table 3 Database account permission

                  Type

                  Full Migration

                  +

                  Full Migration

                  Full+Incremental Migration

                  +

                  Full+Incremental Migration

                  Source database user

                  +

                  Source database user

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, SHOW VIEW, and EVENT

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                  Destination database user

                  +

                  Destination database user

                  • The DDM destination database user must have the following permissions: CREATE, DROP, ALTER, INDEX, INSERT, DELETE, UPDATE, and SELECT. In addition, grant the SELECT permission on all tables.
                  • The DDM destination database user must have the permission on the database to be migrated.
                  +
                  • The DDM destination database user must have the following permissions: CREATE, DROP, ALTER, INDEX, INSERT, DELETE, UPDATE, and SELECT. In addition, grant the SELECT permission on all tables.
                  • The DDM destination database user must have the permission on the database to be migrated.
                  -

                  Suggestions

                  • When a task is being started or in the full migration phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                  • To maintain data consistency before and after the migration, do not write data to the source and destination databases in the full migration mode. In the full+incremental migration mode, you can continue the migration while data is still being written to the source database.
                  +

                  Suggestions

                  • When a task is being started or in the full migration phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                  • To maintain data consistency before and after the migration, do not write data to the source and destination databases in the full migration mode. In the full+incremental migration mode, you can continue the migration while data is still being written to the source database.
                  • The success of database migration depends on environment and manual operations. To ensure a smooth migration, perform a migration trial before you start the migration to help you detect and resolve problems in advance.
                  • Start your migration task during off-peak hours. A less active database is easier to migrate successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the migration.
                    • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full migration, and two to four CPUs are occupied.
                    • The data being migrated may be locked by other transactions for a long period of time, resulting in read timeout.
                    • Due to the inherent characteristics of MySQL, in certain scenarios the performance may be negatively affected. For example, if the CPU resources are insufficient and the storage engine is TokuDB, the read speed on tables may be decreased by 10%.
                    • If DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
                    • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
                  • Data-Level Comparison

                    To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

                  -

                  Precautions

                  The full+incremental migration process consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. A single full migration task contains three phases. To ensure smooth migration, read the following precautions before creating a migration task.

                  +

                  Precautions

                  The full+incremental migration process consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. A single full migration task contains three phases. To ensure smooth migration, read the following precautions before creating a migration task.

                  @@ -83,22 +85,22 @@ - - -
                  Table 4 Precautions

                  Type

                  Starting a task

                  • Source database requirements:
                    • The binlog of the source database must be enabled and use the row-based format during incremental migration.
                    • If the storage space is sufficient, store the source database binlogs for as long as possible. The recommended retention period is three days.
                    • If the expire_logs_days value of the source database is set to 0, the migration may fail. Set expire_logs_day to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
                    • During an incremental migration, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                    • Enable skip-name-resolve for the source database to reduce the possibility of connection timeout.
                    • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                    • The log_slave_updates parameter of the source database must be enabled. Otherwise, the migration fails.
                    • The binlog_row_image parameter value of the source database must be FULL. Otherwise, the migration fails.
                    -
                  • Source database object requirements:
                    • If the source database is an on-premises database and has Percona Server for MySQL 5.6.x or Percona Server for MySQL 5.7.x installed, the memory manager must use Jemalloc to prevent Out of Memory errors caused by frequent queries on system tables.
                    • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                    +
                  • Source database requirements:
                    • The binlog of the source database must be enabled and use the row-based format during incremental migration.
                    • If the storage space is sufficient, store the source database binlogs for as long as possible. The recommended retention period is three days.
                    • If the expire_logs_days value of the source database is set to 0, the migration may fail. Set expire_logs_day to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
                    • During an incremental migration, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                    • Enable skip-name-resolve for the source database to reduce the possibility of connection timeout.
                    • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                    • The log_slave_updates parameter of the source database must be enabled. Otherwise, the migration fails.
                    • The binlog_row_image parameter value of the source database must be FULL. Otherwise, the migration fails.
                    +
                  • Source database object requirements:
                    • If the source database is an on-premises database and has Percona Server for MySQL 5.6.x or Percona Server for MySQL 5.7.x installed, the memory manager must use Jemalloc to prevent Out of Memory errors caused by frequent queries on system tables.
                    • The source database does not support the mysql binlog dump command.
                    • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                  • Destination database parameter requirements:
                    • The destination DB instance and associated RDS DB instance must be available. If the RDS DB instance type is primary/standby, the replication status must be normal.
                    • The associated RDS DB instance must have sufficient storage space.
                    • The character set of the associated RDS database must be the same as that of the source database.
                    • The AUTO_INCREMENT value of a table in the destination cannot be less than that of a table in the source.
                  • Destination database object requirements:
                    • To migrate table structures and other objects, you need to create table structures and indexes in the destination database based on table structures of the source schema. Objects that are not created in the destination database are not to be migrated.
                    • The table structure created in the destination database must be the same as that in the source database.
                    • Ensure that the destination database is empty before starting the migration. Otherwise, data in the destination may be overwritten during incremental migration.
                    • If the destination DB instance uses columns of the TIMESTAMP or DATETIME data type as its sharding key, the seconds precision of the column is removed after the migration.
                    -
                  • Other notes:
                    • If the data types are incompatible, the migration may fail.
                    • If the source DB instance is an RDS MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                    • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                    +
                  • Other notes:
                    • If the data types are incompatible, the migration may fail.
                    • If the source and destination DB instances are RDS for MySQL instances, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                    • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.

                  Full migration

                  • During task startup and full migration, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                  • During migration, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                  • During migration, do not modify the destination database (including but not limited to DDL and DML operations) that is being migrated.
                  • During migration, do not clear the binlog in the source database.
                  • During migration, do not create a database named ib_logfile in the source database.
                  +
                  • During task startup and full migration, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                  • During migration, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                  • During migration, do not modify the destination database (including but not limited to DDL and DML operations) that is being migrated.
                  • During migration, do not clear the binlog in the source database.
                  • During migration, do not create a database named ib_logfile in the source database.

                  Incremental migration

                  • During migration, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                  • During migration, do not modify the destination database (including but not limited to DDL and DML operations) that is being migrated.
                  • During migration, do not clear the binlog in the source database.
                  • During migration, do not create a database named ib_logfile in the source database.
                  • During an incremental migration of table-level objects, renaming tables is not supported.
                  • During an incremental migration, do not perform the point-in-time recovery (PITR) operation on the source database.
                  • During an incremental migration, resumable upload is supported. However, data may be repeatedly inserted into a non-transactional table that does not have a primary key when the server system breaks down.
                  +
                  • During migration, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                  • During migration, do not modify the destination database (including but not limited to DDL and DML operations) that is being migrated.
                  • During migration, do not clear the binlog in the source database.
                  • During migration, do not create a database named ib_logfile on the source side.
                  • During an incremental migration of table-level objects, renaming tables is not supported.
                  • During an incremental migration, do not perform the point-in-time recovery (PITR) operation on the source database.
                  • During an incremental migration, resumable upload is supported. However, data may be repeatedly inserted into a non-transactional table that does not have a primary key when the server system breaks down.

                  Stopping a task

                  @@ -110,8 +112,8 @@
                  -

                  Prerequisites

                  • You have logged in to the DRS console.
                  • For details about the DB types and versions supported by real-time migration, see Real-Time Migration.
                  - +

                  Prerequisites

                  • You have logged in to the DRS console.
                  • For details about the DB types and versions supported by real-time migration, see Real-Time Migration.
                  +

                  Procedure

                  1. On the Create Replication Instance page, configure task details, description, and the replication instance, and click Next.

                    • Task information description
                      Table 5 Task information

                      Parameter

                      @@ -211,6 +213,8 @@
                    +

                    If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                    +

                  2. On the Configure Source and Destination Databases page, wait until the replication instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the replication instance. After the connection tests are successful, select the check box before the agreement and click Next.

                    • Source database configuration
                      @@ -241,7 +245,7 @@ @@ -302,7 +306,7 @@
                      • If the check is complete and the check success rate is 100%, click Next.

                        You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                      -

                    • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                      +

                    • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                      • Table 8 Source database settings

                      Parameter

                      SSL Connection

                      SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                      -
                      NOTE:
                      • The maximum size of a single certificate file that can be uploaded is 500 KB.
                      • If SSL is disabled, your data may be at risk.
                      +
                      NOTE:
                      • The maximum size of a single certificate file that can be uploaded is 500 KB.
                      • If the SSL certificate is not used, your data may be at risk.
                      Table 11 Task startup settings

                      Parameter

                      Description

                      @@ -319,7 +323,7 @@
                      -

                    • After the task is submitted, view and manage it on the Online Migration Management page.

                      • You can view the task status. For more information about task status, see Task Statuses.
                      • You can click in the upper right corner to view the latest task status.
                      +

                    • After the task is submitted, view and manage it on the Online Migration Management page.

                      • You can view the task status. For more information about task status, see Task Statuses.
                      • You can click in the upper right corner to view the latest task status.
                      • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                  diff --git a/docs/drs/umn/drs_04_0090.html b/docs/drs/umn/drs_04_0090.html index 09561e918..50f2b2dce 100644 --- a/docs/drs/umn/drs_04_0090.html +++ b/docs/drs/umn/drs_04_0090.html @@ -1,6 +1,6 @@ -

                  From MySQL to GaussDB(for MySQL) Primary/Standby

                  +

                  From MySQL to TaurusDB Cluster

                  Supported Source and Destination Databases

                  @@ -10,7 +10,7 @@ - @@ -39,29 +39,31 @@

                  Database Account Permission Requirements

                  To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                  +
                  • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                  • After changing the account passwords for the source and destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                  +
                  -
                  Table 1 Supported databases

                  Source DB
                  • On-premises databases (MySQL 5.5, 5.6, 5.7, and 8.0)
                  • ECS databases (MySQL 5.5, 5.6, 5.7, and 8.0)
                  • Other cloud databases (MySQL 5.5, 5.6, 5.7, and 8.0)
                  • RDS for MySQL (5.5, 5.6, 5.7, 8.0)
                  • GaussDB(for MySQL) primary/standby
                  +
                  • TaurusDB cluster instances
                  Table 3 Database account permission

                  Type

                  +
                  - - - - - - - @@ -174,7 +176,7 @@ - - - -
                  Table 3 Database account permission

                  Type

                  Full Migration

                  +

                  Full Migration

                  Full+Incremental Migration

                  +

                  Full+Incremental Migration

                  Source database user

                  +

                  Source database user

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, SHOW VIEW, and EVENT

                  The user must have the SELECT permission for mysql.user.

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                  The user must have the SELECT permission for mysql.user.

                  Destination database user

                  +

                  Destination database user

                  The user must have the following minimum permissions:

                  +

                  The user must have the following minimum permissions:

                  SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, INDEX, EVENT, CREATE VIEW, CREATE ROUTINE, TRIGGER, REFERENCES, and WITH GRANT OPTION. If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                  To migrate data, you must have the SELECT, INSERT, UPDATE, and DELETE permissions for the MySQL database.

                  Destination DB Engine

                  Select GaussDB(for MySQL) Primary/Standby Edition.

                  +

                  Select TaurusDB Cluster.

                  Network Type

                  @@ -185,7 +187,7 @@

                  Destination DB Instance

                  The GaussDB(for MySQL) primary/standby instance you created.

                  +

                  The cluster TaurusDB instance you created.

                  Replication Instance Subnet

                  @@ -281,7 +283,7 @@

                  DB Instance Name

                  The GaussDB(for MySQL) primary/standby instance selected during the migration task creation and cannot be changed.

                  +

                  The cluster TaurusDB instance selected when you created the task. This parameter cannot be changed.

                  Database Username

                  @@ -352,7 +354,7 @@
                  • If the check is complete and the check success rate is 100%, click Next.

                    You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                  -

                • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                  +

                • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                  Table 11 Task startup settings

                  Parameter

                  Description

                  @@ -369,7 +371,7 @@
                  -

                • After the task is submitted, view and manage it on the Online Migration Management page.

                  • You can view the task status. For more information about task status, see Task Statuses.
                  • You can click in the upper right corner to view the latest task status.
                  +

                • After the task is submitted, view and manage it on the Online Migration Management page.

                  • You can view the task status. For more information about task status, see Task Statuses.
                  • You can click in the upper right corner to view the latest task status.
                  • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                  • diff --git a/docs/drs/umn/drs_04_0095.html b/docs/drs/umn/drs_04_0095.html index f6aab5cd5..f733e5123 100644 --- a/docs/drs/umn/drs_04_0095.html +++ b/docs/drs/umn/drs_04_0095.html @@ -8,7 +8,7 @@
                  • On-premises MongoDB (versions 3.2, 3.4, 3.6, 4.0, 4.2, and 4.4)
                  • ECS-hosted MongoDB (versions 3.2, 3.4, 3.6, 4.0, 4.2, and 4.4)
                  • Other Cloud MongoDB (versions 3.2, 3.4, 3.6, 4.0, 4.2, and 4.4)
                  • DDS DB instances (versions 3.2, 3.4, 4.0, 4.2, and 4.4)
                  +
                  • On-premises MongoDB (versions 3.2, 3.4, 3.6, 4.0, 4.2, and 4.4)
                  • ECS-hosted MongoDB (versions 3.2, 3.4, 3.6, 4.0, 4.2, and 4.4)
                  • Other cloud MongoDB (versions 3.2, 3.4, 3.6, 4.0, 4.2, and 4.4)
                  • DDS DB instances (versions 3.2, 3.4, 4.0, 4.2, and 4.4)
                  • DDS DB instances (versions 3.4, 4.0, 4.2, and 4.4)
                    NOTE:

                    The destination database version must be the same as or later than the source database version.

                    @@ -41,25 +41,27 @@

                    Database Account Permission Requirements

                    To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                    +
                    • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                    • After changing the account passwords for the source and destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                    +
                    -
                    Table 3 Database account permission

                    Type

                    +
                    - - - - - - - @@ -99,6 +101,7 @@

                    Change streams support only the following DDLs: drop database, drop collection and rename

                    The DBPointer and DBRef data types are not supported.

                    In the incremental migration phase,the migration speed can reach up to 10,000 rows in a single table per second.

                    +

                    Currently, only whitelisted users can use Change Streams.

                  • If you select Oplog for Source Database Type, DRS will create multiple subtasks based on the number of source shards. If Task Rate Limit is selected, the configured rate limit value is synchronized to each subtask.
                  • If a Time-to-Live (TTL) index already exists in the collection of the source database or is created during an incremental migration, data consistency cannot be ensured when source and destination databases are in different time zone.
                  • The value of block_compressor is determined by stats().wiredTiger.creationString.block_compressor of the collection in the source database. If the destination database contains corresponding empty collections, the compression parameters will not be migrated. If the compression parameters in the source database are not supported by the destination database, configure the compression parameters based on net.compression.compressors of the destination database. If the destination database version is DDS 4.2, DRS does not migrate compression parameters because the destination database does not support compression parameter settings.
                  • If the accounts and roles to be migrated conflict with those in the destination database, DRS will skip the conflict data and continue the migration.
                  • If the MongoDB service of the source database is deployed with other services on the same server, set the value of the cacheSizeGB parameter to the half of the minimum idle cache for the WiredTiger engine of the source database.
                  • If the source is a replica set instance, enter information about all primary and secondary nodes to reduce the impact of a primary/secondary switchover on the migration task. If you enter information about multiple primary and secondary nodes, ensure that all nodes belong to the same replica set instance.
                  • If the source is a cluster instance, enter information about multiple mongos nodes to reduce the impact of single-node failure on the migration task. In addition, ensure that all mongos nodes belong to the same cluster instance. For an incremental migration of a cluster instance, you are advised to enter information about all primary and secondary nodes of the shard node and ensure that all node information belongs to the same shard to reduce the impact of a primary/secondary switchover on the migration task. Ensure that all shard nodes belong to the same cluster.
                  • During the creation of a migration task, the destination database can be set to read-only or read/write if the DDS kernel version supports this setting. After the task is created, this setting cannot be changed.

                    Read-only: During the migration, the destination database is read-only. After the migration is complete, it restores to the read/write status. This option ensures the integrity and success rate of data migration.

                    Read/Write: During the migration, the destination database can be queried or modified. Data being migrated may be modified when operations are performed or applications are connected. It should be noted that background processes can often generate or modify data, which may result in data conflicts, task faults, and upload failures. Do not select this option if you do not fully understand the risks.

                  • In some migration scenarios, to prevent the drop database operation from deleting the existing collections in the destination database, the drop database operation will not be synchronized to the destination database.

                    If the source database version is earlier than MongoDB 3.6, running the drop database command will delete the collections only from the source database. The collections in destination database will not be deleted.

                    @@ -222,7 +225,7 @@
                    • - @@ -381,7 +384,7 @@
                    • If the check is complete and the check success rate is 100%, click Next.

                      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                    -

                  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                    +

                  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                    • Table 3 Database account permission

                    Type

                    Full Migration

                    +

                    Full Migration

                    Full+Incremental Migration

                    +

                    Full+Incremental Migration

                    Source database user

                    +

                    Source database user

                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database.
                    • Cluster: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the config database.
                    • To migrate accounts and roles of the source database, the source and destination database users must have the read permission for the system.users and system.roles system tables of the admin database.
                    +
                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database.
                    • Cluster: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the config database.
                    • To migrate accounts and roles of the source database, the source and destination database users must have the read permission for the system.users and system.roles system tables of the admin database.
                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • Cluster: The source mongos node user must have the readAnyDatabase permission for the admin database and the read permission for the config database. The source shard node user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • To migrate accounts and roles of the source database, the source and destination database users must have the read permission for the system.users and system.roles system tables of the admin database.
                    +
                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • Cluster: The source mongos node user must have the readAnyDatabase permission for the admin database and the read permission for the config database. The source shard node user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • To migrate accounts and roles of the source database, the source and destination database users must have the read permission for the system.users and system.roles system tables of the admin database.

                    Destination database user

                    +

                    Destination database user

                    The user who connects to the destination database must have the dbAdminAnyDatabase permission of the admin database and the readWrite permission of the destination database.

                    +

                    The user who connects to the destination database must have the dbAdminAnyDatabase permission of the admin database and the readWrite permission of the destination database.

                    If the destination database is a cluster instance, the database user must have the clusterManager permission for the admin database.

                    Obtain Incremental Data

                    This parameter is available for configuration if Source DB Instance Type is set to Cluster. You can determine how to capture data changes during the incremental synchronization.

                    -
                    • oplog: For MongoDB 3.2 or later, DRS directly connects to each shard of the source DB instance to extract data. If you select this method, you must disable the balancer of the source database. For details, see How Do I Disable the Balancer? When testing the connectivity between the source and the DRS instance, you need to enter the connection information of each shard in the source database on the task configuration page.
                    • changeStream: This method is recommended. For MongoDB 4.0 and later, DRS connects to mongos nodes of the source database to extract data. If you select this method, you must enable the WiredTiger storage engine of the source database.
                    +
                    • oplog: For MongoDB 3.2 or later, DRS directly connects to each shard of the source DB instance to extract data. If you select this method, you must disable the balancer of the source database. For details, see How Do I Disable the Balancer? When testing the connectivity between the source and the DRS instance, you need to enter the connection information of each shard in the source database on the task configuration page.
                    • changeStream: This method is recommended. For MongoDB 4.0 and later, DRS connects to mongos nodes of the source database to extract data. If you select this method, you must enable the WiredTiger storage engine of the source database.

                    Destination Database Access

                    @@ -267,7 +270,7 @@

                    mongos IP Address or Domain Name

                    +

                    mongos Address

                    IP address or domain name of the source database in the IP address/Domain name:Port format. The port of the source database. Range: 1 - 65535

                    You can enter a maximum of three groups of IP addresses or domain names of the source database. Separate multiple values with commas (,). For example: 192.168.0.1:8080,192.168.0.2:8080. Ensure that the entered IP addresses or domain names belong to the same sharded cluster.

                    @@ -293,14 +296,14 @@

                    SSL Connection

                    SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                    -
                    NOTE:
                    • The maximum size of a single certificate file that can be uploaded is 500 KB.
                    • If SSL is disabled, your data may be at risk.
                    +
                    NOTE:
                    • The maximum size of a single certificate file that can be uploaded is 500 KB.
                    • If the SSL certificate is not used, your data may be at risk.

                    Sharded Database

                    Enter the information about the sharded databases in the source database.

                    -

                    If the source is a DDS instance, apply for an IP address for the shard node by referring to Document Database Service User Guide.

                    +

                    If the source database is a DDS DB instance, apply for the IP address of the shard node by following the instructions provided in DDS User Guide.
                    Table 11 Task startup settings

                    Parameter

                    Description

                    @@ -398,7 +401,7 @@
                    -

                  • After the task is submitted, view and manage it on the Online Migration Management page.

                    • You can view the task status. For more information about task status, see Task Statuses.
                    • You can click in the upper right corner to view the latest task status.
                    +

                  • After the task is submitted, view and manage it on the Online Migration Management page.

                    • You can view the task status. For more information about task status, see Task Statuses.
                    • You can click in the upper right corner to view the latest task status.
                    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                    • diff --git a/docs/drs/umn/drs_04_0100.html b/docs/drs/umn/drs_04_0100.html index 4aa918a15..85415e1a7 100644 --- a/docs/drs/umn/drs_04_0100.html +++ b/docs/drs/umn/drs_04_0100.html @@ -20,29 +20,31 @@

                    Database Account Permission Requirements

                    To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require different permissions. For details, see Table 2. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                    +
                    • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                    • After changing the account passwords for the source and destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                    +
                    -
                    Table 2 Database account permission

                    Type

                    +
                    - - - - - - - @@ -103,7 +105,7 @@

                    Prerequisites

                    • You have logged in to the DRS console.
                    • For details about the DB types and versions supported by real-time migration, see Real-Time Migration.
                    -

                    Procedure

                    This section uses the migration from an RDS MySQL database to a MySQL database on an ECS as an example to describe how to configure a migration task in a VPC network on the DRS management console.

                    +

                    Procedure

                    This section uses the migration from an RDS for MySQL database to a MySQL database on an ECS as an example to describe how to configure a migration task in a VPC network on the DRS management console.

                    1. On the Online Migration Management page, click Create Migration Task.
                    2. On the Create Replication Instance page, configure task details, description, and the replication instance, and click Next.

                      • Task information description
                    Table 2 Database account permission

                    Type

                    Full Migration

                    +

                    Full Migration

                    Full+Incremental Migration

                    +

                    Full+Incremental Migration

                    Source database user

                    +

                    Source database user

                    The user must have the following minimum permissions:

                    +

                    The user must have the following minimum permissions:

                    SELECT, SHOW VIEW, and EVENT

                    During user migration, the user must have the SELECT permission for mysql.user.

                    The user must have the following minimum permissions:

                    +

                    The user must have the following minimum permissions:

                    SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                    During user migration, the user must have the SELECT permission for mysql.user.

                    Destination database user

                    +

                    Destination database user

                    The user must have the following minimum permissions:

                    +

                    The user must have the following minimum permissions:

                    SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, INDEX, EVENT, CREATE VIEW, CREATE ROUTINE, TRIGGER, REFERENCES, and WITH GRANT OPTION. If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                    To migrate data, you must have the SELECT, INSERT, UPDATE, and DELETE permissions for the MySQL database.

                    @@ -154,7 +156,7 @@ - @@ -297,7 +299,7 @@ @@ -329,7 +331,7 @@
                    • If the check is complete and the check success rate is 100%, click Next.

                      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                    -

                  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                    +

                  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                    • Table 4 Task information

                    Parameter

                    Destination DB Engine

                    Select MySQL.

                    +

                    Select MySQL.

                    Network Type

                    @@ -258,7 +260,7 @@

                    SSL Connection

                    SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                    -
                    NOTE:
                    • The maximum size of a single certificate file that can be uploaded is 500 KB.
                    • If SSL is disabled, your data may be at risk.
                    +
                    NOTE:
                    • The maximum size of a single certificate file that can be uploaded is 500 KB.
                    • If the SSL certificate is not used, your data may be at risk.

                    During an incremental migration, executing DDL operations on the source database may affect the data migration performance to some extent. To reduce data migration risks, DRS allows you to filter out DDL operations.

                    The database deletion operation can be filtered out by default.

                    -
                    • If you select Yes, any database deletion operations performed on the source database are not synchronized during data migration.
                    • If you select No, related operations are synchronized to the destination database during data migration.
                      NOTE:

                      Currently, only the full plus incremental migrations from RDS MySQL to MySQL are supported.

                      +
                      • If you select Yes, any database deletion operations performed on the source database are not synchronized during data migration.
                      • If you select No, related operations are synchronized to the destination database during data migration.
                        NOTE:

                        Currently, only the full plus incremental migrations from RDS for MySQL to MySQL are supported.

                    Table 9 Task startup settings

                    Parameter

                    Description

                    @@ -346,7 +348,7 @@
                    -

                  • After the task is submitted, view and manage it on the Online Migration Management page.

                    • You can view the task status. For more information about task status, see Task Statuses.
                    • You can click in the upper right corner to view the latest task status.
                    +

                  • After the task is submitted, view and manage it on the Online Migration Management page.

                    • You can view the task status. For more information about task status, see Task Statuses.
                    • You can click in the upper right corner to view the latest task status.
                    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                    • diff --git a/docs/drs/umn/drs_04_0101.html b/docs/drs/umn/drs_04_0101.html index 93ae84cdb..4bb42c219 100644 --- a/docs/drs/umn/drs_04_0101.html +++ b/docs/drs/umn/drs_04_0101.html @@ -38,25 +38,27 @@

                    Database Account Permission Requirements

                    To start a migration task, the source and destination database users must have permissions listed in the following table. Different types of migration tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                    +
                    • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                    • After changing the account passwords for the source and destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                    +
                    -
                    Table 3 Database account permission

                    Type

                    +
                    - - - - - - - @@ -253,8 +255,8 @@ - @@ -277,7 +279,7 @@ @@ -327,7 +329,7 @@
                    • If the check is complete and the check success rate is 100%, click Next.

                      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                    -

                  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                    +

                  • On the Confirm Task page, specify Start Time and confirm that the configured information is correct and click Submit to submit the task.

                    • Table 3 Database account permission

                    Type

                    Full Migration

                    +

                    Full Migration

                    Full+Incremental Migration

                    +

                    Full+Incremental Migration

                    Source database user

                    +

                    Source database user

                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database.
                    • Cluster: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the config database.
                    +
                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database.
                    • Cluster: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the config database.
                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    +
                    • Replica set: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                    • Single node: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.

                    Destination database user

                    +

                    Destination database user

                    The user who connects to the destination database must have the dbAdminAnyDatabase permission of the admin database and the readWrite permission of the destination database.

                    +

                    The user who connects to the destination database must have the dbAdminAnyDatabase permission of the admin database and the readWrite permission of the destination database.

                    If the destination database is a cluster instance, the database user must have the clusterManager permission for the admin database.

                    IP Address or Domain Name

                    IP address or domain name of the source database in the IP address/Domain name:Port format. The port of the source database. Range: 1 - 65535

                    -

                    You can enter a maximum of three groups of IP addresses or domain names of the source database. Separate multiple values with commas (,). For example: 192.168.0.1:8080,192.168.0.2:8080. Ensure that the entered IP addresses or domain names belong to the same instance.

                    +

                    IP address or domain name of the destination database in the IP address/Domain name:Port format. Enter an integer ranging from 1 to 65535, which indicates the port number of the destination database.

                    +

                    You can enter a maximum of three groups of IP addresses or domain names of the destination database. Separate multiple values with commas (,). For example: 192.168.0.1:8080,192.168.0.2:8080. Ensure that the entered IP addresses or domain names belong to the same instance.

                    NOTE:

                    If multiple IP addresses or domain names are entered, the test connection is successful as long as one IP address or domain name is accessible. Therefore, you must ensure that the IP address or domain name is correct.

                    SSL Connection

                    SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                    -
                    NOTE:
                    • The maximum size of a single certificate file that can be uploaded is 500 KB.
                    • If SSL is disabled, your data may be at risk.
                    +
                    NOTE:
                    • The maximum size of a single certificate file that can be uploaded is 500 KB.
                    • If the SSL certificate is not used, your data may be at risk.
                    Table 11 Task startup settings

                    Parameter

                    Description

                    @@ -344,7 +346,7 @@
                    -

                  • After the task is submitted, view and manage it on the Online Migration Management page.

                    • You can view the task status. For more information about task status, see Task Statuses.
                    • You can click in the upper right corner to view the latest task status.
                    +

                  • After the task is submitted, view and manage it on the Online Migration Management page.

                    • You can view the task status. For more information about task status, see Task Statuses.
                    • You can click in the upper right corner to view the latest task status.
                    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                    • diff --git a/docs/drs/umn/drs_04_0102.html b/docs/drs/umn/drs_04_0102.html index d78bb14ac..6f96069f0 100644 --- a/docs/drs/umn/drs_04_0102.html +++ b/docs/drs/umn/drs_04_0102.html @@ -27,40 +27,42 @@
                  • For many-to-one synchronization tasks that involve the synchronization of the same table, DDL operations cannot be performed on source databases. Otherwise, all synchronization tasks fail.

                    • Precautions

                    Before creating a synchronization task, read the following notes:

                    +
                    • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                    • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                    +
                    -
                    Table 2 Precautions

                    Type

                    +
                    - - - - - - - - - - -
                    Table 2 Precautions

                    Type

                    Restrictions

                    +

                    Restrictions

                    Database permissions

                    +

                    Database permissions

                    • The source database user must have the following permissions:

                      SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                      +
                    • The source database user must have the following permissions:

                      SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                    • The destination database user must have the following permissions:

                      The root account of RDS for MySQL has the following permissions by default: SELECT, CREATE, DROP, DELETE, INSERT, UPDATE, ALTER, CREATE VIEW, CREATE ROUTINE, and REFERENCES If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                    Synchronization object

                    +

                    Synchronization object

                    • Only tables, primary key indexes, unique indexes, common indexes, store procedures, views, and functions can be synchronized.
                    +
                    • Only tables, primary key indexes, unique indexes, common indexes, store procedures, views, and functions can be synchronized.
                    • During database mapping, the source database cannot contain stored procedures, views, or functions.
                    • The databases to be mapped to the destination can only contain tables during synchronization. Otherwise, the synchronization task fails.
                    • If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.
                    • Tables with storage engine different to MyISAM and InnoDB cannot be synchronized.
                    • The DDL operation of renaming an unselected table is filtered out during the synchronization. As a result, the task may fail or data may be inconsistent.
                      • If you rename table A to the name of table B and tables A and B are selected for synchronization, this RENAME statement will not be filtered out.
                      • If you rename table A to the name of table B but table B is not synchronized, this RENAME statement will be filtered out.
                      • You are not advised to perform the rename operation in the many-to-one synchronization scenario. Otherwise, the task may fail or data may be inconsistent.

                    Source database

                    +

                    Source database

                    • The source database names cannot contain non-ASCII characters, or the following characters: '<`>/\"
                    • The source table and view names cannot contain non-ASCII characters, or the following characters: '<>/\"
                    • The source database name or mapped name cannot start with ib_logfile or be ib_buffer_pool, ib_doublewrite, ibdata1 or ibtmp1.
                    • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                    • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                    • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                    • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                    • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                    +
                    • The source database names cannot contain non-ASCII characters, or the following characters: '<`>/\"
                    • The source table and view names cannot contain non-ASCII characters, or the following characters: '<>/\"
                    • The source database name or mapped name cannot start with ib_logfile or be ib_buffer_pool, ib_doublewrite, ibdata1 or ibtmp1.
                    • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                    • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                    • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                    • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                    • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.

                    Destination database

                    +

                    Destination database

                    • Data cannot be synchronized from a newer version database to an older version database.
                    • The destination DB instance is running properly. If the destination DB instance type is primary/standby, the replication status must also be normal.
                    • The destination DB instance must have sufficient storage space.
                    • The character set of the destination database must be the same as that of the source database.
                    • The time zone of the destination database must be the same as that of the source database.
                    • If the destination database (excluding MySQL system database) has the same name as the source database, the table structures in the destination database must be consistent with those in the source database.
                    • During a synchronization, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.
                    • If the MyISAM tables are included in the synchronization objects, the sql_mode parameter in the destination database cannot contain the no_engine_substitution parameter. Otherwise, the synchronization fails.
                    • The source database names mapped to the destination database cannot contain the following characters: dots (.), angle brackets (<>), backslash (\), and single quotation marks (')
                    +
                    • Data cannot be synchronized from a newer version database to an older version database.
                    • The destination DB instance is running properly. If the destination DB instance type is primary/standby, the replication status must also be normal.
                    • The destination DB instance must have sufficient storage space.
                    • The character set of the destination database must be the same as that of the source database.
                    • The time zone of the destination database must be the same as that of the source database.
                    • If the destination database (excluding MySQL system database) has the same name as the source database, the table structures in the destination database must be consistent with those in the source database.
                    • During a synchronization, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.
                    • If the MyISAM tables are included in the synchronization objects, the sql_mode parameter in the destination database cannot contain the no_engine_substitution parameter. Otherwise, the synchronization fails.
                    • The source database names mapped to the destination database cannot contain the following characters: dots (.), angle brackets (<>), backslash (\), and single quotation marks (')

                    Precautions

                    +

                    Precautions

                    • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
                    • Only MySQL to MySQL synchronization supports many-to-one synchronization. During table-level many-to-one synchronization, tables without primary keys cannot exist in the source database.
                    • If you create many-to-one synchronization tasks, the system automatically creates a parent task to associate multiple synchronization tasks after the tasks are started. The parent task is named in the DRS-Group-Destination DB instance name format.
                    • If the sources and destinations are RDS instances, database mapping is required.
                    • The source and destination databases cannot contain tables that have the same names but do not have primary keys.
                    • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                    • If the source and destination sides are RDS MySQL instances, tables encrypted using TDE cannot be synchronized.
                    • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                    • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                    • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                      • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                      • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                      +
                    • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
                    • Only MySQL to MySQL synchronization supports many-to-one synchronization. During table-level many-to-one synchronization, tables without primary keys cannot exist in the source database.
                    • If you create many-to-one synchronization tasks, the system automatically creates a parent task to associate multiple synchronization tasks after the tasks are started. The parent task is named in the DRS-Group-Destination DB instance name format.
                    • If the sources and destinations are RDS instances, database mapping is required.
                    • The source and destination databases cannot contain tables that have the same names but do not have primary keys.
                    • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                    • If the source and destination DB instances are RDS for MySQL instances, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                    • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                    • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                    • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                      • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                      • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                    • The source database does not support point-in-time recovery (PITR).
                    • The destination database cannot be restored to a point in time when a full synchronization was being performed.
                    • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                    • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
                    • The partitioned table does not support column mapping.
                    • Set the expire_log_day parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
                    • After a task is created, the destination database cannot be set to read-only.
                    • A real-time synchronization task may fail due to the change of the username and password of the source or destination database. If it happens, rectify the information and then retry the synchronization task on the DRS console. Generally, you are advised not to modify the preceding information during synchronization.
                    • If the source or destination database port is changed during data synchronization, the synchronization task fails. You can rectify the fault as follows:
                      • If the source database port is wrong, correct the port number on the DRS console and then retry the synchronization task.
                      • If the destination database port is wrong, DRS automatically changes the port to the correct one, and then you need to retry the synchronization task.

                        Generally, do not modify the port number during synchronization.

                    • During data synchronization, if the source database is on an RDS instance that does not belong the current cloud platform, the IP address cannot be changed. If the source database is on an RDS DB instance on the current cloud platform, the system automatically changes the IP address to the correct one. Then, retry the task to continue the synchronization. Therefore, changing the IP address is not recommended.
                    • To ensure data consistency, do not perform operations (including but not limited to DDL and DML operations) on the destination database during the synchronization.
                    • Data inconsistency may occur when the MyISAM table is modified during a full synchronization.
                    • DDL statements can be synchronized during incremental synchronization.
                    • Incremental synchronization supports table renaming. The source and destination tables must be selected in the synchronization object list. Full synchronization does not support the RENAME command.
                    • You can add additional objects during an incremental synchronization.
                    @@ -70,7 +72,7 @@
                    -

                    Procedure

                    This section describes how to synchronize data from a MySQL database to an RDS MySQL database. To configure other storage engines, you can refer to the following procedures.

                    +

                    Procedure

                    This section describes how to synchronize data from a MySQL database to an RDS for MySQL database. To configure other storage engines, you can refer to the following procedures.

                    1. On the Data Synchronization Management page, click Create Synchronization Task.
                    2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                      • Task information description
                        @@ -156,16 +158,31 @@
                        Table 3 Task and recipient description

                        Parameter
                        -
                      • Tags -
                        Table 5 Tags

                        Parameter

                        +
                      • DRS instance specifications +
                        - - - + + +
                        Table 5 Specifications

                        Parameter

                        Description

                        +

                        Description

                        Tags

                        +

                        Specifications

                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        +

                        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                        +
                        +
                        +
                      • Tags +
                        + + + + + @@ -175,7 +192,7 @@

                        If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                      • After the synchronization instance is created, on the Configure Source and Destination Databases page, specify source and destination database information. Then, click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

                        • Source database information -
                        • Table 6 Tags

                        Parameter

                        +

                        Description

                        +

                        Tags

                        +
                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        Table 6 Source database settings

                        Parameter

                        +
                        @@ -206,7 +223,7 @@ @@ -217,7 +234,7 @@
                        • Destination database information -
                        Table 7 Source database settings

                        Parameter

                        Description

                        SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                        This parameter is unavailable when the network type is VPC network and the database type is RDS DB instance.

                        -
                        NOTE:
                        • The maximum size of a single certificate file that can be uploaded is 500 KB.
                        • If SSL is disabled, your data may be at risk.
                        +
                        NOTE:
                        • The maximum size of a single certificate file that can be uploaded is 500 KB.
                        • If the SSL certificate is not used, your data may be at risk.
                        Table 7 Destination database settings

                        Parameter

                        +
                        @@ -247,7 +264,7 @@

                      • On the Set Synchronization Task page, select the conflict policy and synchronization objects, and then click Next.

                        -

                        • Table 8 Destination database settings

                        Parameter

                        Description
                        Table 8 Synchronization mode and object

                        Parameter

                        +
                        @@ -284,7 +301,7 @@ - + + + @@ -306,12 +329,12 @@
                        Table 9 Synchronization mode and object

                        Parameter

                        Description

                        Synchronize

                        Normal indexes and incremental DDLs can be synchronized. You can determine whether to synchronize data based on service requirements. If you deselect Normal index, DDL statements related to index adding will be filtered out in the incremental phase. If the DDL statements contain other operations, they may also be filtered out.

                        +

                        Normal indexes and incremental DDLs can be synchronized. You can determine whether to synchronize normal indexes and DDLs based on service requirements.

                        Start Point

                        @@ -293,12 +310,18 @@

                        Run show master status to obtain the source database position and set File, Position, and Executed_Gtid_Set as prompted. If gtid_mode is disabled, you do not need to specify Executed_Gtid_Set.

                        Online DDL

                        +

                        If table-level synchronization is selected, you can choose whether to synchronize Online DDL. By default, Online DDL is not synchronized.

                        +
                        • Yes: Table-level synchronization supports Online DDL synchronization. You can select three Online DDL tools including PT-OSC, GH-OST, and DMS. The regular expressions can be configured for shadow tables and useless tables in PT-OSC and GH-OST. (Default values are provided. You are advised not to change the regular expressions unless otherwise specified.)
                        • No: Table-level synchronization does not support Online DDL synchronization.
                        +

                        Synchronization Object

                        Select Tables, Import object file, or Databases as required.

                        -
                        • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

                          If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

                          +
                          • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                            If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

                          • For details about how to import an object file, see Importing Synchronization Objects.
                          -
                          NOTE:
                          • To quickly select the desired database objects, you can use the search function.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          +
                          NOTE:
                          • You can search for table names to quickly select the required database objects.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                          • The name of the selected synchronization object cannot contain spaces.
                        -

                      • On the Process Data page, set the filtering rules for data processing.

                        • If data processing is not required, click Next.
                        • If data processing is required, select Data filtering. For details about how to configure related rules, see Processing Data.
                        +

                      • On the Process Data page, set the filtering rules for data processing.

                        • If data processing is not required, click Next.
                        • If data processing is required, select Data Filtering. For details about how to configure related rules, see Processing Data.

                      • On the Check Task page, check the synchronization task.

                        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                        • If all check items are successful, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        -

                        - @@ -26,38 +26,40 @@

                        Precautions

                        Before creating a synchronization task, read the following notes:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        Table 9 Task startup settings

                        Parameter

                        +

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        +

                        @@ -327,7 +350,7 @@
                        Table 10 Task startup settings

                        Parameter

                        Description
                        -

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0104.html b/docs/drs/umn/drs_04_0104.html index a4f876749..f94d3a492 100644 --- a/docs/drs/umn/drs_04_0104.html +++ b/docs/drs/umn/drs_04_0104.html @@ -10,7 +10,7 @@
                        • On-premises MySQL databases
                        • MySQL databases on an ECS
                        • MySQL databases on other clouds
                        • RDS for MySQL
                        • GaussDB distributed
                        +
                        • GaussDB Distributed
                        - - @@ -47,28 +47,30 @@

                        Database Account Permission Requirements

                        To start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        Table 2 Precautions

                        Type

                        +
                        - - - - - - - - - - - @@ -66,7 +68,7 @@
                        Table 2 Precautions

                        Type

                        Restrictions

                        +

                        Restrictions

                        Database permissions

                        +

                        Database permissions

                        • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT.
                        • The destination GaussDB database user must have the following permissions:
                          • Database-level permissions: Log in to the postgres base database as user root or other DATABASE users with the Sysadmin role, and grant the CREATE and CONNECT permissions to user DATABASE.
                          • Schema-level permission: Log in to the database as user root or user DATABASE with the Sysadmin role, or the owner of the object, and grant the CREATE and USAGE permissions of the schema to the user.
                          • Table-level permission: Log in to the database as user root or user DATABASE with the Sysadmin role, or the owner of the object, and grant the SELECT, UPDATE, INSERT, ALTER, INDEX, and DELETE permissions for all tables in the SCHEMA to the user.
                          +
                        • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT.
                        • The destination GaussDB database user must have the following permissions:
                          • Database-level permissions: Log in to the postgres base database as user root or other DATABASE users with the Sysadmin role, and grant the CREATE and CONNECT permissions to user DATABASE.
                          • Schema-level permission: Log in to the database as user root or user DATABASE with the Sysadmin role, or the owner of the object, and grant the CREATE and USAGE permissions of the schema to the user.
                          • Table-level permission: Log in to the database as user root or user DATABASE with the Sysadmin role, or the owner of the object, and grant the SELECT, UPDATE, INSERT, ALTER, INDEX, and DELETE permissions for all tables in the SCHEMA to the user.

                        Synchronization object

                        +

                        Synchronization object

                        • Only tables can be synchronized. Other database objects such as stored procedures cannot be synchronized.
                        • Only tables with primary keys can be synchronized. Tables without primary keys cannot be synchronized.
                        • Incremental synchronization does not support synchronization of DDL.
                        • MySQL tables containing virtual columns cannot be synchronized.
                        +
                        • Only tables can be synchronized. Other database objects such as stored procedures cannot be synchronized.
                        • Only tables with primary keys can be synchronized. Tables without primary keys cannot be synchronized.
                        • Incremental synchronization does not support synchronization of DDL.
                        • MySQL tables containing virtual columns cannot be synchronized.
                        • The following data types are not supported: XML, geometry, point, lineString, polygon, geometrycollection, multipoint, multilinestring, and multipolygon.
                        • Tables with storage engine different to MyISAM and InnoDB cannot be synchronized.

                        Source database

                        +

                        Source database

                        • During the incremental synchronization, the binlog of the source database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the binlogs for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. For MySQL 5.7, the value of server_id ranges from 1 to 4294967296.
                        • The names of the source databases and tables cannot contain non-ASCII characters, or special characters .<'>/\
                        +
                        • During the incremental synchronization, the binlog of the source database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the binlogs for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. For MySQL 5.7, the value of server_id ranges from 1 to 4294967296.
                        • The names of the source databases and tables cannot contain non-ASCII characters, or special characters .<'>/\

                        Destination database

                        +

                        Destination database

                        • The destination DB instance is running properly.
                        • The destination DB instance must have sufficient storage space.
                        • The time zone of the destination database must be the same as that of the source database.
                        • The mapped database configured for the task must exist in the destination database.
                        +
                        • The destination DB instance is running properly.
                        • The destination DB instance must have sufficient storage space.
                        • The time zone of the destination database must be the same as that of the source database.
                        • The mapped database configured for the task must exist in the destination database.

                        Precautions

                        +

                        Precautions

                        • If the network is reconnected within 30 seconds, real-time synchronization will not be affected. If the network is interrupted for more than 30 seconds, the synchronization task will fail.
                        • If the character sets of the source and destination databases are different, data may be inconsistent or synchronization may fail.
                        • If the data types are incompatible, the synchronization may fail.
                        • After a table in the source database is synchronized to the destination database, the table is distributed in hash mode and cannot be replicated.
                        • If the source DB instance is an RDS MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                          +
                        • Cascading one-way synchronization is not supported. For example, data cannot be synchronized from instance A to instance B and then from instance B to instance C.
                        • If the network is reconnected within 30 seconds, real-time synchronization will not be affected. If the network is interrupted for more than 30 seconds, the synchronization task will fail.
                        • If the character sets of the source and destination databases are different, data may be inconsistent or synchronization may fail.
                        • If the data types are incompatible, the synchronization may fail.
                        • After a table in the source database is synchronized to the destination database, the table is distributed in hash mode and cannot be replicated.
                        • If the source DB instance is an RDS for MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                        • The changes to the source database cannot be synchronized to the destination database in multiple tasks at the same time. Otherwise, data inconsistency and synchronization failure may occur.
                        • In a full synchronization for the table structure, the length of char, varchar, nvarchar, enum, and set characters in the source database automatically increases by byte in the destination database (because the length of the destination database is in the unit of byte). The increase multiple depends on the character set of columns in the source database. For example, if the character set of the source database is UTF8, increase the length (byte) by three times. If the character set of the source database is UTF8MB4, increase the length (byte) by four times.
                        • During an incremental synchronization, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                        • During an incremental synchronization, DDLs of the source database cannot be replicated.
                        • During an incremental synchronization, do not perform the restoration operation on the source database.
                        • During task startup or full synchronization, you are not advised to perform DDL operations, such as the deletion operation. Otherwise, the task may fail.
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • The source database cannot be restored.
                        • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • Do not use an imprecise value type as the primary key in the database. This feature affects the synchronization of UPDATE and DELETE statements in the DRS incremental scenario.
                        • If tables without primary keys contain large fields (BLOB, TEXT, CLOB, NCLOB, or BYTEA), data of the large fields may be inconsistent during incremental synchronization.
                        • Floating-point data is approximate numbers and depends on the OS platform and underlying implementation. FLOAT and DOUBLE data is inaccurate. If you synchronize floating-point data between MySQL and GaussDB, there may be some differences. For details, see the official MySQL documentation.
                        • Two-phase commit is not supported.
                        • The ongoing synchronization task cannot be paused.
                        • Data processing is not supported.
                        • If the source table to be synchronized has the AUTO_INCREMENT attribute, DRS automatically updates the start value of the GaussDB auto-increment sequence corresponding to the integer sequence of the table when the task is complete. The updated value is the maximum value of the sequence plus 10,000.
                        -

                        Procedure

                        This section uses real-time synchronization from MySQL to GaussDB distributed as an example to describe how to configure a real-time synchronization task.

                        +

                        Procedure

                        This section uses real-time synchronization from MySQL to GaussDB Distributed as an example to describe how to configure a real-time synchronization task.

                        1. On the Data Synchronization Management page, click Create Synchronization Task.
                        2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                          - - + + + @@ -202,7 +209,7 @@ - @@ -257,7 +264,7 @@

                        3. On the Check Task page, check the synchronization task.

                          • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                          • If all check items are successful, click Next.

                            You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                          -

                        4. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                          +

                        5. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                          6. Table 3 Task and recipient description

                          Parameter

                          @@ -117,7 +119,7 @@

                          Destination DB Engine

                          Select GaussDB Distributed Edition.

                          +

                          Select GaussDB Distributed.

                          Network Type

                          @@ -127,7 +129,7 @@

                          Destination DB Instance

                          An available GaussDB distributed instance.

                          +

                          An available distributed GaussDB instance.

                          Synchronization Instance Subnet

                          @@ -144,6 +146,11 @@

                          Specifications

                          +

                          DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                          +

                          Tags
                          • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                          • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                          @@ -184,7 +191,7 @@

                          SSL Connection

                          SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                          -
                          NOTE:
                          • The maximum size of a single certificate file that can be uploaded is 500 KB.
                          • If SSL is disabled, your data may be at risk.
                          +
                          NOTE:
                          • The maximum size of a single certificate file that can be uploaded is 500 KB.
                          • If the SSL certificate is not used, your data may be at risk.

                          DB Instance Name

                          The GaussDB distributed instance selected during synchronization task creation. This parameter cannot be changed.

                          +

                          The distributed GaussDB instance selected during synchronization task creation. This parameter cannot be changed.

                          Database Username

                          @@ -245,8 +252,8 @@

                          Synchronization Object

                          You can synchronize tables based on the service requirements.

                          -

                          If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

                          -
                          NOTE:
                          • To quickly select the desired database objects, you can use the search function.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          +

                          If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                          +
                          NOTE:
                          • You can search for table names to quickly select the required database objects.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                          • The name of the selected synchronization object cannot contain spaces.
                          Table 8 Task startup settings

                          Parameter

                          Description

                          @@ -274,7 +281,7 @@
                          -

                        6. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                          • You can view the task status. For more information about task status, see Task Statuses.
                          • You can click in the upper-right corner to view the latest task status.
                          +

                        7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                          • You can view the task status. For more information about task status, see Task Statuses.
                          • You can click in the upper-right corner to view the latest task status.
                          • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        diff --git a/docs/drs/umn/drs_04_0107.html b/docs/drs/umn/drs_04_0107.html index 669729035..635704cd6 100644 --- a/docs/drs/umn/drs_04_0107.html +++ b/docs/drs/umn/drs_04_0107.html @@ -8,9 +8,9 @@
                        • On-premises database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14 and 15)
                        • ECS database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14 and 15)
                        • Other cloud database (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14 and 15)
                        • RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13, 14 and 15)
                        +
                        • On-premises databases (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14,15 and 16)
                        • ECS-hosted databases (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14, 15 and 16)
                        • Other cloud databases (PostgreSQL 9.4, 9.5, 9.6, 10, 11, 12, 13, 14, 15 and 16)
                        • RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13, 14, 15 and 16)

                        RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13, 14 and 15)

                        +

                        RDS for PostgreSQL (9.5, 9.6, 10, 11, 12, 13, 14, 15 and 16)

                        NOTE:

                        The major version of the destination database must be the same as or later than that of the source database.
                        - + + + @@ -264,7 +269,7 @@ alter table `ddl_test` drop index `ddl_test_uk`;

                      • On the Check Task page, check the synchronization task.

                        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                        • If all check items are successful, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        +

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        • Table 3 Database account permission

                        Type

                        +
                        - - - - - - - - + + + @@ -304,7 +311,7 @@ - - @@ -406,7 +413,7 @@

                      • On the Check Task page, check the synchronization task.

                        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                        • If all check items are successful, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        +

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        • Table 3 Database account permission

                        Type

                        Full

                        +

                        Full

                        Full+Incremental

                        +

                        Full+Incremental

                        Source database user

                        +

                        Source database user

                        The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permission for sequences, and the SELECT permission for system table catalog pg_catalog.pg_authid (used for synchronizing user passwords)

                        +

                        The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permission for sequences, and the SELECT permission for system table catalog pg_catalog.pg_authid (used for synchronizing user passwords)

                        The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permission for sequences, the SELECT permission for system table catalog pg_catalog.pg_authid (used for synchronizing user passwords), the UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys, and the permission to create replication connections

                        +

                        The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permission for sequences, the SELECT permission for system table catalog pg_catalog.pg_authid (used for synchronizing user passwords), the UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys, and the permission to create replication connections

                        NOTE:
                        • The UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys are only used to temporarily lock tables to ensure data consistency after the migration.
                        • To add the permission to create replication connections, perform the following steps:
                          1. Add host replication <src_user_name> <drs_instance_ip>/32 md5 before all configurations in the pg_hba.conf file of the source database.
                          2. Run select pg_reload_conf(); in the source database as user SUPERUSER, or restart the DB instance to apply the changes.

                        Destination database user

                        +

                        Destination database user

                        • Database-level: The CREATEDB permission is required.
                        • Table-level:
                          • To synchronize databases, the CREATEDB permission is required.
                          • To synchronize a schema, the CONNECT and CREATE permissions for the database that contains the schema are required.
                          • To synchronize objects in a schema, the CONNECT permission for the database that contains the schema, and the USAGE and CREATE permissions for the schema that contain the object are required.
                          +
                        • Database-level: The CREATEDB permission is required.
                        • Table-level:
                          • To synchronize databases, the CREATEDB permission is required.
                          • To synchronize a schema, the CONNECT and CREATE permissions for the database that contains the schema are required.
                          • To synchronize objects in a schema, the CONNECT permission for the database that contains the schema, and the USAGE and CREATE permissions for the schema that contain the object are required.
                        • Synchronization user: The CREATEROLE permission is required.
                        • Synchronization user permissions: The default privilege cannot be modified. Otherwise, the object permissions of the destination database may be inconsistent with those of the source database.
                        NOTE:

                        To synchronize event triggers, text search parsers, and text search templates, the destination database version must be RDS for PostgreSQL 11.11 or later, and the destination database user must be user root or a member of user root.

                        @@ -201,7 +203,7 @@

                        Destination DB Instance

                        The RDS PostgreSQL DB instance.

                        +

                        The RDS for PostgreSQL DB instance.

                        Synchronization Instance Subnet

                        @@ -217,6 +219,11 @@

                        Specifications

                        +

                        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                        +

                        Tags
                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        @@ -281,7 +288,7 @@

                        SSL Connection

                        SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                        -
                        NOTE:
                        • The maximum size of a single certificate file that can be uploaded is 500 KB.
                        • If SSL is disabled, your data may be at risk.
                        +
                        NOTE:
                        • The maximum size of a single certificate file that can be uploaded is 500 KB.
                        • If the SSL certificate is not used, your data may be at risk.

                        DB Instance Name

                        Select the RDS PostgreSQL instance to be synchronized as the source DB instance.

                        +

                        Select the RDS for PostgreSQL instance to be synchronized as the source DB instance.

                        Database Username

                        @@ -330,7 +337,7 @@

                        DB Instance Name

                        The RDS PostgreSQL instance you selected when creating the migration task and cannot be changed.

                        +

                        The RDS for PostgreSQL instance you selected when creating the migration task and cannot be changed.

                        Database Username

                        @@ -387,9 +394,9 @@

                        Select Tables or Databases as required.

                        • Database-level synchronization: In full synchronization, the selected databases and the inventory data of the database objects are synchronized. In incremental synchronization, the DML and some DDL statements of all tables except unlogged tables and temporary tables are synchronized.
                        • Table-level synchronization: In full synchronization, the inventory data of the selected tables, sequences, views, or materialized views is synchronized. In incremental synchronization, the DML and some DDL statements of the selected tables are synchronized.
                        -
                        • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

                          When a schema name or table name is mapped, to prevent conflicts between indexes and constraint names, the original index name in the table is changed to the following format after synchronization: i_+hash value+original index name (which may be truncated)+_key The hash value is calculated based on the original schema name_original table name_original index name. Similarly, after the synchronization, the original constraint name on the table is changed to c_ + hash value + original constraint name (which may be truncated) + _key.

                          +
                          • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                            When a schema name or table name is mapped, to prevent conflicts between indexes and constraint names, the original index name in the table is changed to the following format after synchronization: i_+hash value+original index name (which may be truncated)+_key The hash value is calculated based on the original schema name_original table name_original index name. Similarly, after the synchronization, the original constraint name on the table is changed to c_ + hash value + original constraint name (which may be truncated) + _key.

                          -
                          NOTE:
                          • To quickly select the desired database objects, you can use the search function.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          +
                          NOTE:
                          • You can search for table names to quickly select the required database objects.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                          • The name of the selected synchronization object cannot contain spaces.
                        Table 11 Task startup settings

                        Parameter

                        Description

                        @@ -423,7 +430,7 @@
                        -

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0115.html b/docs/drs/umn/drs_04_0115.html index d257335dd..8b6066ae6 100644 --- a/docs/drs/umn/drs_04_0115.html +++ b/docs/drs/umn/drs_04_0115.html @@ -38,7 +38,7 @@

                        Database permissions
                        • The source database DDM account must have at least one permission, for example, SELECT. The physical sharded database account must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE and REPLICATION CLIENT.
                        -
                        • The destination database user must have the following permissions: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, and UPDATE. The root account of the RDS MySQL DB instance has the preceding permissions by default.
                        +
                        • The destination database user must have the following permissions: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, and UPDATE. The root account of the RDS for MySQL DB instance has the preceding permissions by default.

                        Synchronization object

                        @@ -58,7 +58,7 @@

                        Precautions

                        • If the data types are incompatible, the synchronization may fail.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key when the server system breaks down.
                        • If the source database contains a duplicate primary key or unique key, the data synchronized to the destination database will be less than that in the source database. Therefore, you must check and correct the data before starting the synchronization task.
                        • If the destination DB instance is an RDS MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                          +
                        • If the data types are incompatible, the synchronization may fail.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key when the server system breaks down.
                        • If the source database contains a duplicate primary key or unique key, the data synchronized to the destination database will be less than that in the source database. Therefore, you must check and correct the data before starting the synchronization task.
                        • If the destination DB instance is an RDS for MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                        • After a task is created, the destination database cannot be set to read-only.
                        • After a synchronization task is started, you are not allowed to add a schema or modify the association between the old schema and a new RDS DB instance. Otherwise, the synchronization task will fail.
                        • During synchronization, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                        • During the synchronization, do not change the sharding key of a table on the source DDM instance, or change an unsharded or broadcast table to a sharded table, or change a sharded table to an unsharded or broadcast table.
                        • During an incremental synchronization, do not perform the restoration operation on the source database.
                        • During incremental synchronization, some DDL operations are supported.
                          • DROP_DATABASE, DROP_TABLE, TRUNCATE_TABLE, CREATE_VIEW and DROP_VIEW are not supported.
                          • Online DDL is not supported.
                          • Tables can be created. For example:
                            create table `ddl_test` (id int, c1 varchar(25), primary key(id));
 create table `ddl_test_gho` like `ddl_test`;
                            @@ -163,6 +163,11 @@ alter table `ddl_test` drop index `ddl_test_uk`;

                        Specifications

                        +

                        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                        +

                        Tags
                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        @@ -253,7 +258,7 @@ alter table `ddl_test` drop index `ddl_test_uk`;

                        Synchronization Object

                        DRS supports table-level synchronization. You can select data for synchronization based on your service requirements. To quickly select the desired database objects, you can use the search function.

                        -
                        NOTE:
                        • To quickly select the desired database objects, you can use the search function.
                        • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                        +
                        NOTE:
                        • You can search for table names to quickly select the required database objects.
                        • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                        • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                        • The name of the selected synchronization object cannot contain spaces.
                        Table 8 Task startup settings

                        Parameter

                        Description

                        @@ -281,7 +286,7 @@ alter table `ddl_test` drop index `ddl_test_uk`;
                        -

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0117.html b/docs/drs/umn/drs_04_0117.html index b00a2296b..5567da324 100644 --- a/docs/drs/umn/drs_04_0117.html +++ b/docs/drs/umn/drs_04_0117.html @@ -27,40 +27,42 @@
                      • For many-to-one synchronization tasks that involve the synchronization of the same table, DDL operations cannot be performed on source databases. Otherwise, all synchronization tasks fail.

                        • Precautions

                        Before creating a synchronization task, read the following notes:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        Table 2 Precautions

                        Type

                        +
                        - - - - - - - - - - - + + + @@ -269,15 +276,21 @@ - + + + @@ -285,20 +298,19 @@
                        Table 2 Precautions

                        Type

                        Restrictions

                        +

                        Restrictions

                        Database permissions

                        +

                        Database permissions

                        • The source database user must have the following permissions:

                          SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                          +
                        • The source database user must have the following permissions:

                          SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, and REPLICATION CLIENT

                        • The destination database user must have the following permissions:

                          SELECT, CREATE, INDEX, DROP, DELETE, INSERT, UPDATE, ALTER, CREATE VIEW, CREATE ROUTINE, and REFERENCES. If the destination database version is in the range 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                        Synchronization object

                        +

                        Synchronization object

                        • Only tables, primary key indexes, unique indexes, common indexes, store procedures, views, and functions can be synchronized.
                        +
                        • Only tables, primary key indexes, unique indexes, common indexes, store procedures, views, and functions can be synchronized.
                        • During database mapping, the source database cannot contain stored procedures, views, or functions.
                        • The databases to be mapped to the destination can only contain tables during synchronization. Otherwise, the synchronization task fails.
                        • If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.
                        • Tables with storage engine different to MyISAM and InnoDB cannot be synchronized.
                        • The DDL operation of renaming an unselected table is filtered out during the synchronization. As a result, the task may fail or data may be inconsistent.
                          • If you rename table A to the name of table B and tables A and B are selected for synchronization, this RENAME statement will not be filtered out.
                          • If you rename table A to the name of table B but table B is not synchronized, this RENAME statement will be filtered out.
                          • You are not advised to perform the rename operation in the many-to-one synchronization scenario. Otherwise, the task may fail or data may be inconsistent.

                        Source database

                        +

                        Source database

                        • The source database names cannot contain non-ASCII characters, or the following characters: '<`>/\"
                        • The source table and view names cannot contain non-ASCII characters, or the following characters: '<>/\"
                        • The source database name or mapped name cannot start with ib_logfile or be ib_buffer_pool, ib_doublewrite, ibdata1 or ibtmp1.
                        • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                        +
                        • The source database names cannot contain non-ASCII characters, or the following characters: '<`>/\"
                        • The source table and view names cannot contain non-ASCII characters, or the following characters: '<>/\"
                        • The source database name or mapped name cannot start with ib_logfile or be ib_buffer_pool, ib_doublewrite, ibdata1 or ibtmp1.
                        • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.

                        Destination database

                        +

                        Destination database

                        • Data cannot be synchronized from a newer version database to an older version database.
                        • The destination database must have sufficient disk space.
                        • The character set of the destination database must be the same as that of the source database.
                        • The time zone of the destination database must be the same as that of the source database.
                        • If the destination database (excluding MySQL system database) has the same name as the source database, the table structures in the destination database must be consistent with those in the source database.
                        • During a synchronization, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.
                        • If the MyISAM tables are included in the synchronization objects, the sql_mode parameter in the destination database cannot contain the no_engine_substitution parameter. Otherwise, the synchronization fails.
                        • The source database names mapped to the destination database cannot contain the following characters: dots (.), angle brackets (<>), backslash (\), and single quotation marks (')
                        +
                        • Data cannot be synchronized from a newer version database to an older version database.
                        • The destination database must have sufficient disk space.
                        • The character set of the destination database must be the same as that of the source database.
                        • The time zone of the destination database must be the same as that of the source database.
                        • If the destination database (excluding MySQL system database) has the same name as the source database, the table structures in the destination database must be consistent with those in the source database.
                        • During a synchronization, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.
                        • If the MyISAM tables are included in the synchronization objects, the sql_mode parameter in the destination database cannot contain the no_engine_substitution parameter. Otherwise, the synchronization fails.
                        • The source database names mapped to the destination database cannot contain the following characters: dots (.), angle brackets (<>), backslash (\), and single quotation marks (')

                        Precautions

                        +

                        Precautions

                        • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
                        • Only MySQL to MySQL synchronization supports many-to-one synchronization. During table-level many-to-one synchronization, tables without primary keys cannot exist in the source database.
                        • If the sources and destinations are RDS instances, database mapping is required.
                        • The source and destination databases cannot contain tables that have the same names but do not have primary keys.
                        • If the source and destination DB instances are RDS MySQL instances, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • If the destination MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                          +
                        • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
                        • Only MySQL to MySQL synchronization supports many-to-one synchronization. During table-level many-to-one synchronization, tables without primary keys cannot exist in the source database.
                        • If the sources and destinations are RDS instances, database mapping is required.
                        • The source and destination databases cannot contain tables that have the same names but do not have primary keys.
                        • If the source and destination DB instances are RDS for MySQL instances, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • If the destination MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                        • The source database does not support point-in-time recovery (PITR).
                        • The destination database cannot be restored to a point in time when a full synchronization was being performed.
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
                        • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • Set the expire_log_day parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
                        • After a task is created, the destination database cannot be set to read-only.
                        • A real-time synchronization task may fail due to the change of the username and password of the source or destination database. If it happens, rectify the information and then retry the synchronization task on the DRS console. Generally, you are advised not to modify the preceding information during synchronization.
                        • If the source or destination database port is changed during data synchronization, the synchronization task fails. You can rectify the fault as follows:
                          • If the source database port is wrong, correct the port number on the DRS console and then retry the synchronization task.
                          • If the destination database port is wrong, DRS automatically changes the port to the correct one, and then you need to retry the synchronization task.

                            Generally, do not modify the port number during synchronization.

                        • To ensure data consistency, do not modify the destination database (including but not limited to DDL and DML operations) during synchronization.
                        • Data inconsistency may occur when the MyISAM table is modified during a full synchronization.
                        • Incremental synchronization supports table renaming. Ensure that both the source and destination tables are selected.
                        • You can add additional objects during an incremental synchronization.
                        @@ -151,6 +153,11 @@

                        Specifications

                        +

                        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                        +

                        Tags
                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        @@ -220,7 +227,7 @@

                        SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                        This parameter is unavailable when the network type is VPC network and the database type is RDS DB instance.

                        -
                        NOTE:
                        • The maximum size of a single certificate file that can be uploaded is 500 KB.
                        • If SSL is disabled, your data may be at risk.
                        +
                        NOTE:
                        • The maximum size of a single certificate file that can be uploaded is 500 KB.
                        • If the SSL certificate is not used, your data may be at risk.

                        Synchronize

                        Normal indexes and incremental DDLs can be synchronized. You can determine whether to synchronize data based on service requirements. If you deselect Normal index, DDL statements related to index adding will be filtered out in the incremental phase. If the DDL statements contain other operations, they may also be filtered out.

                        +

                        Normal indexes and incremental DDLs can be synchronized. You can determine whether to synchronize normal indexes and DDLs based on service requirements.

                        +

                        Online DDL

                        +

                        If table-level synchronization is selected, you can choose whether to synchronize Online DDL. By default, Online DDL is not synchronized.

                        +
                        • Yes: Table-level synchronization supports Online DDL synchronization. You can select three Online DDL tools including PT-OSC, GH-OST, and DMS. The regular expressions can be configured for shadow tables and useless tables in PT-OSC and GH-OST. (Default values are provided. You are advised not to change the regular expressions unless otherwise specified.)
                        • No: Table-level synchronization does not support Online DDL synchronization.

                        Synchronization Object

                        Select Tables, Import object file, or Databases as required.

                        -
                        • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

                          If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

                          +
                          • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                            If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

                          • For details about how to import an object file, see Importing Synchronization Objects.
                          -
                          NOTE:
                          • To quickly select the desired database objects, you can use the search function.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          +
                          NOTE:
                          • You can search for table names to quickly select the required database objects.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                          • The name of the selected synchronization object cannot contain spaces.
                        -

                      • On the Process Data page, set the filtering rules for data processing.

                        • If data processing is not required, click Next.
                        • If data processing is required, select Data filtering. For details about how to configure related rules, see Processing Data.

                      • On the Check Task page, check the synchronization task.

                        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                        • If all check items are successful, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        -

                        Table 8 Task startup settings

                        Parameter

                        +

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        +

                        - - - @@ -306,7 +318,7 @@
                        Table 8 Task startup settings

                        Parameter

                        Description

                        +

                        Description

                        Started Time

                        +

                        Started Time

                        Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                        +

                        Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                        NOTE:

                        After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.
                        -

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0118.html b/docs/drs/umn/drs_04_0118.html index 4f4b960e3..28a2a3766 100644 --- a/docs/drs/umn/drs_04_0118.html +++ b/docs/drs/umn/drs_04_0118.html @@ -1,17 +1,16 @@

                        From MySQL to Kafka

                        -

                        DMS for Kafka

                        -

                        Supported Source and Destination Databases

                        -
                        Table 1 Supported databases

                        Source DB

                        +

                        Supported Source and Destination Databases

                        +
                        - - - @@ -23,37 +22,39 @@

                        Suggestions

                        • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                        • It is recommended that you start a task during off-peak hours to minimize the impact of synchronization on your services.

                        Precautions

                        Before creating a synchronization task, read the following notes:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        Table 1 Supported databases

                        Source DB

                        Destination DB

                        +

                        Destination DB
                        • RDS for MySQL
                        +
                        • RDS for MySQL
                        • Kafka
                        • DMS for Kafka
                        +
                        • Kafka
                        Table 2 Precautions

                        Type

                        +
                        - - - - - - - - - - - @@ -61,83 +62,88 @@

                        Procedure

                        1. On the Data Synchronization Management page, click Create Synchronization Task.
                        2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                          -

                        Table 2 Precautions

                        Type

                        Restrictions

                        +

                        Restrictions

                        Database permissions

                        +

                        Database permissions

                        • The source database user must have the following permissions: SELECT, LOCK TABLES, REPLICATION SLAVE, REPLICATION CLIENT, and RELOAD.
                        +
                        • The source database user must have the following permissions: SELECT, LOCK TABLES, REPLICATION SLAVE, REPLICATION CLIENT, and RELOAD.

                        Synchronization object

                        +

                        Synchronization object

                        • The table data can be synchronized.
                        +
                        • The table data can be synchronized.
                        • Tables with storage engine different to MyISAM and InnoDB cannot be synchronized.

                        Source database

                        +

                        Source database

                        • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                        • The database and table names in the source database cannot contain non-ASCII characters, or special characters '<`>/\
                        +
                        • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                        • The database and table names in the source database cannot contain non-ASCII characters, or special characters '<`>/\

                        Destination database

                        +

                        Destination database

                        • The destination database is a Kafka database.
                        +
                        • The destination database is a Kafka database.

                        Precautions

                        +

                        Precautions

                        • If the data types are incompatible, the synchronization may fail.
                        • If the source DB instance is an RDS MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • A real-time synchronization task may fail due to the change of the username and password of the source database. You need to rectify the information and then retry the synchronization task on the DRS console. Generally, you are advised not to modify the preceding information during synchronization.
                        • If the source database port is changed during data synchronization, the synchronization task fails. If the destination database port is wrong, DRS automatically changes the port to the correct one, and then you need to retry the synchronization task. Generally, do not modify the port number during synchronization.
                        • If a real-time synchronization task fails as the IP address is changed, the system automatically changes the IP address to the correct one. Then, you need to retry the task to continue the synchronization. Therefore, changing the IP address is not recommended.
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • The source database does not support point-in-time recovery (PITR).
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
                        • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • Data inconsistency may occur when the MyISAM table is modified during synchronization.
                        • During synchronization of table-level objects, renaming tables is not recommended.
                        • Set the expire_log_day parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
                        +
                        • If the data types are incompatible, the synchronization may fail.
                        • If the source DB instance is an RDS for MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • A real-time synchronization task may fail due to the change of the username and password of the source database. You need to rectify the information and then retry the synchronization task on the DRS console. Generally, you are advised not to modify the preceding information during synchronization.
                        • If the source database port is changed during data synchronization, the synchronization task fails. If the destination database port is wrong, DRS automatically changes the port to the correct one, and then you need to retry the synchronization task. Generally, do not modify the port number during synchronization.
                        • If a real-time synchronization task fails as the IP address is changed, the system automatically changes the IP address to the correct one. Then, you need to retry the task to continue the synchronization. Therefore, changing the IP address is not recommended.
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • The source database does not support point-in-time recovery (PITR).
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
                        • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • Data inconsistency may occur when the MyISAM table is modified during synchronization.
                        • During synchronization of table-level objects, renaming tables is not recommended.
                        • Set the expire_log_day parameter to a proper value to ensure that the binlog does not expire before data transfer resumes. This ensures that services can be recovered after interruption.
                        Table 3 Task and recipient description

                        Parameter

                        +
                        - - - - - - - - -
                        Table 3 Task and recipient description

                        Parameter

                        Description

                        +

                        Description

                        Region

                        +

                        Region

                        The region where the synchronization instance is deployed. You can change the region.

                        +

                        The region where the synchronization instance is deployed. You can change the region.

                        Project

                        +

                        Project

                        The project corresponds to the current region and can be changed.

                        +

                        The project corresponds to the current region and can be changed.

                        Task Name

                        +

                        Task Name

                        The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                        +

                        The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                        Description

                        +

                        Description

                        The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

                        +

                        The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\
                        -
                        Table 4 Synchronization instance settings

                        Parameter

                        +
                        - - - - - - - - - - - - - - - - - + + + @@ -146,25 +152,25 @@

                        If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                      • On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

                        -

                        • Table 4 Synchronization instance settings

                        Parameter

                        Description

                        +

                        Description

                        Data Flow

                        +

                        Data Flow

                        Select Out of the cloud.

                        +

                        Select Out of the cloud.

                        Source DB Engine

                        +

                        Source DB Engine

                        Select MySQL.

                        +

                        Select MySQL.

                        Destination DB Engine

                        +

                        Destination DB Engine

                        Select Kafka.

                        +

                        Select Kafka.

                        Network Type

                        +

                        Network Type

                        The Public network is used as an example. Available options: Public network, VPC, VPN or Direct Connect

                        +

                        The Public network is used as an example. Available options: Public network, VPC, VPN or Direct Connect

                        Source DB Instance

                        +

                        Source DB Instance

                        The RDS MySQL instance you created.

                        +

                        The RDS for MySQL instance you created.

                        Synchronization Instance Subnet

                        +

                        Synchronization Instance Subnet

                        Select the subnet where the synchronization instance is located. You can also click View Subnet to go to the network console to view the subnet where the instance resides.

                        +

                        Select the subnet where the synchronization instance is located. You can also click View Subnet to go to the network console to view the subnet where the instance resides.

                        By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides and ensure that there are available IP addresses. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

                        Synchronization Mode

                        +

                        Synchronization Mode

                        • Incremental

                          Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                          +
                        • Incremental

                          Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                          During synchronization, the source database continues to provide services for external systems with zero downtime.

                        Tags

                        +

                        Specifications

                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        +

                        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                        +

                        Tags

                        +
                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        Table 5 Source database settings

                        Parameter

                        +
                        - - - - - - - @@ -173,84 +179,84 @@

                        The username and password of the source database are encrypted and stored in DRS and will be cleared after the task is deleted.

                        -
                        Table 5 Source database settings

                        Parameter

                        Description

                        +

                        Description

                        DB Instance Name

                        +

                        DB Instance Name

                        The RDS DB instance selected during synchronization task creation. This parameter cannot be changed.

                        +

                        The RDS DB instance selected during synchronization task creation. This parameter cannot be changed.

                        Database Username

                        +

                        Database Username

                        The username for accessing the source database.

                        +

                        The username for accessing the source database.

                        Database Password

                        +

                        Database Password

                        The password for the database username.

                        +

                        The password for the database username.
                        Table 6 Source database information

                        Parameter

                        +
                        - - - - -
                        Table 6 Source database information

                        Parameter

                        Description

                        +

                        Description

                        IP Address or Domain Name

                        +

                        IP Address or Domain Name

                        The IP address or domain name of the destination database.

                        +

                        The IP address or domain name of the destination database.

                        Security Protocol

                        +

                        Security Protocol

                        Available options: PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL. For details, see Kafka Authentication.

                        +

                        Available options: PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL. For details, see Kafka Authentication.

                      • On the Set Synchronization Task page, select the synchronization policy, objects, and data format, and click Next.

                        -

                        Table 7 Synchronization Object

                        Parameter

                        +
                        - - - - - - - - - - - - - - - - - - - @@ -262,16 +268,16 @@

                      • On the Check Task page, check the synchronization task.

                        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                        • If all check items are successful, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        -

                        • Table 7 Synchronization Object

                        Parameter

                        Description

                        +

                        Description

                        Synchronize DML

                        +

                        Synchronize DML

                        Select the DML operations to be synchronized. By default, all DML operations are selected.

                        +

                        Select the DML operations to be synchronized. By default, all DML operations are selected.

                        Topic Synchronization Policy

                        +

                        Topic Synchronization Policy

                        Topic synchronization policy. You can select A specific topic or Auto-generated topics.

                        +

                        Topic synchronization policy. You can select A specific topic or Auto-generated topics.

                        Topic

                        +

                        Topic

                        Select the topic to be synchronized to the destination database. This parameter is available when the topic is set to A specified topic.

                        +

                        Select the topic to be synchronized to the destination database. This parameter is available when the topic is set to A specified topic.

                        Topic Name Format

                        +

                        Topic Name Format

                        Topic name format. This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                        +

                        Topic name format. This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                        Only variables database and tablename are supported. The other characters must be constants. Replace $database$ with the database name and $tablename$ with the table name.

                        For example, if this parameter is set to $database$-$tablename$ and the database name is db1, and the table name is tab1, the topic name is db1-tab1. If DDL statements are synchronized, $tablename$ is empty and the topic name is db1.

                        Number of Partitions

                        +

                        Number of Partitions

                        This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                        +

                        This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                        The number of partitions of a topic. Each topic can have multiple partitions. More partitions can provide higher throughput but consume more resources. Set the number of partitions based on the actual situation of brokers.

                        Replication Factor

                        +

                        Replication Factor

                        This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                        +

                        This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                        Number of copies of a topic. Each topic can have multiple copies, and the copies are placed on different brokers in a cluster. The number of copies cannot exceed the number of brokers. Otherwise, the topic fails to be created.

                        Synchronize Topic To

                        +

                        Synchronize Topic To

                        The policy for synchronizing topics to the Kafka partitions.

                        +

                        The policy for synchronizing topics to the Kafka partitions.

                        • If topics are synchronized to different partitions by hash value of the database and table names, the performance on a single table query can be improved.
                        • If topics are synchronized to partition 0, strong consistency can be obtained but write performance is impacted. If you select Partition 0, only automatically created topics can be synchronized.
                        • If topics are synchronized to different partitions by hash value of the primary key, one table corresponds to one topic.

                        Data Format in Kafka

                        +

                        Data Format in Kafka

                        Select the data format to be delivered from MySQL to Kafka.

                        +

                        Select the data format to be delivered from MySQL to Kafka.

                        • JSON: JSON message format, which is easy to interpret but takes up more space.
                        • JSON-C: A data format that is compatible with multiple batch and stream computing frameworks.

                        For details, see Kafka Message Format.

                        Synchronization Object

                        +

                        Synchronization Object

                        Available options: Tables or Databases as required.

                        -
                        • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.
                        -
                        NOTE:
                        • To quickly select the desired database objects, you can use the search function.
                        • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                        +

                        Available options: Tables or Databases as required.

                        + +
                        NOTE:
                        • You can search for table names to quickly select the required database objects.
                        • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                        • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                        • The name of the selected synchronization object cannot contain spaces.
                        Table 8 Task startup settings

                        Parameter

                        +

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        +

                        - - - @@ -279,7 +285,7 @@
                        Table 8 Task startup settings

                        Parameter

                        Description

                        +

                        Description

                        Started Time

                        +

                        Started Time

                        Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                        +

                        Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                        NOTE:

                        After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.
                        -

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0121.html b/docs/drs/umn/drs_04_0121.html deleted file mode 100644 index 4010d37ce..000000000 --- a/docs/drs/umn/drs_04_0121.html +++ /dev/null @@ -1,316 +0,0 @@ - - -

                        From GaussDB Distributed to MySQL

                        -

                        Supported Source and Destination Databases

                        -
                        - - - - - - - -
                        Table 1 Supported databases

                        Source DB

                        -

                        Destination DB

                        -
                        • GaussDB distributed
                        -
                        • RDS for MySQL 5.6 and 5.7
                        • On-premises MySQL 5.5, 5.6, and 5.7 databases
                        • MySQL 5.5, 5.6, and 5.7 databases on an ECS
                        • MySQL 5.5, 5.6, and 5.7 databases on other clouds
                        -
                        -
                        -
                        -

                        Supported Synchronization Objects

                        Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

                        - -
                        - - - - - - - -
                        Table 2 Supported synchronization objects

                        Type

                        -

                        Synchronization Scope

                        -

                        Synchronization scope

                        -
                        • Instance-level synchronization is not supported. Only one database can be synchronized at a time. To synchronize multiple databases, create multiple tasks.
                        • Supported scenario: Incremental synchronization
                        • Supported fields: INTEGER, TINYINT, SMALLINT, BIGINT, NUMBER, NUMERIC, REAL, DOUBLE PRECISION, CHARACTER, CHARACTER VARYING, NVARCHAR2, BIT, BIT VARYING, BLOB, BYTEA, CLOB, RAW, TEXT, BOOLEAN, DATE, SMALLDATETIME, TIME WITH TIME ZONE, TIME WITHOUT TIME ZONE, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITHOUT TIME ZONE and MONEY.
                        • Table-level synchronization is supported.
                          • During incremental synchronization, only DML statements of selected tables can be synchronized.
                          • Databases without schemas cannot be synchronized.
                          • Schemas without tables cannot be synchronized.
                          • Column-store tables, compressed tables, delay tables, and temporary tables cannot be synchronized. Do not synchronize unlogged tables in the incremental phase.
                          • The database name, schema name, and table name cannot contain special characters /<.>\\'`|\?!
                          -
                        -
                        -
                        -
                        -

                        Database User Permission Requirements

                        Before you start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                        - -
                        - - - - - - - - - - -
                        Table 3 Database user permission

                        Type

                        -

                        Incremental

                        -

                        Source database user

                        -

                        The user must have the sysadmin role or the following minimum permissions:

                        -
                        • The REPLICATION permission or the permission inherited from the built-in role gs_role_replication, the CONNECT permission for databases, the USAGE permission for schemas, and the SELECT permission for tables.
                        -

                        Destination database user

                        -

                        Required permissions:

                        -

                        INSERT, DELETE, UPDATE, SELECT, and SHOW DATABASES

                        -
                        -
                        -
                        -

                        Suggestions

                        • When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                        • To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
                        -
                        -
                        • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                        • Start your synchronization task during off-peak hours. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization.
                          • The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
                          • When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
                          - -
                        • Data-Level Comparison

                          To obtain accurate comparison results, compare data at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

                          -
                        -
                        -

                        Precautions

                        DRS incremental synchronization consists of three phases: task start, incremental synchronization, and task completion. To ensure smooth synchronization, read the following notes before creating a synchronization task.

                        - -
                        - - - - - - - - - - - - - - - - -
                        Table 4 Precautions

                        Type

                        -

                        Restrictions

                        -

                        Starting a task

                        -
                        • Source database requirements:
                          • The wal_level parameter of the source database is set to logical.
                          • The enable_slot_log parameter of the source database is set to on.
                          • The max_replication_slots value of the source database must be greater than the number of used replication slots.
                          • Add a primary key to the table that does not have a primary key, or set REPLICA IDENTITY to FULL for the table that does not have a primary key.
                          -
                        • Source database object requirements:
                          • The names of the source database, schema, and table to be synchronized cannot contain special characters /<.>\\'`|\?!
                          -
                        • Destination database parameter requirements:
                          • The character set of the destination database must be the same as that of the source database.
                          -
                        -
                        • The destination database object must meet the following requirements:
                          • The destination database has sufficient disk space.
                          • Before the synchronization, ensure that the corresponding database has been created in the destination instance.
                          • Before synchronization, ensure that the table structure of the destination database has been created and is the same as that of the source database.
                          -
                        • Other notes:
                          • During real-time synchronization, the consistency of distributed transactions is not ensured.
                          • The table structure information is saved in uppercase in the source database. During synchronization, if the table names in the destination database are different from those in the source database, map the source table names to the destination table names.
                          • If a logical replication slot fails to be created or does not exist due to a long transaction, you can reset the task and then restart it.
                          -
                        -

                        Incremental synchronization

                        -
                        • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                        • Before a task enters the incremental synchronization phase, ensure that long-running transactions are not started in the source database. Starting the long transaction will block the creation of the logical replication slot and cause the task to fail.
                        • Do not execute any DDL statement in the source database. Restricted by the GaussDB logical replication function, DDL statements cannot be synchronized. If you synchronize DDL statements, data may be inconsistent or the task may fail.
                        • Do not change the REPLICA IDENTITY value of a table in the source database. Otherwise, incremental data may be inconsistent or the task may fail.
                        • Do not write data to the destination database. Otherwise, data may be inconsistent.
                        -

                        Synchronization comparison

                        -
                        • You are advised to compare data in the source database during off-peak hours to prevent inconsistent data from being falsely reported and reduce the impact on the source database and DRS tasks.
                        • During incremental synchronization, if data is written to the source database, the comparison results may be inconsistent.
                        • Do not limit the synchronization speed during data comparison.
                        -

                        Stopping a task

                        -

                        Stop a task normally.

                        -
                        • After the task is complete, the streaming replication slot created in the source database is automatically deleted.
                        -

                        Forcibly stop a task.

                        - -
                        -
                        -
                        -

                        Prerequisites

                        • You have logged in to the DRS console.
                        • For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
                        - -
                        -

                        Procedure

                        1. On the Data Synchronization Management page, click Create Synchronization Task.
                        2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                          -

                          - - - - - - - - - - - - - - - - -
                          Table 5 Task and recipient description

                          Parameter

                          -

                          Description

                          -

                          Region

                          -

                          The region where the synchronization instance is deployed. You can change the region.

                          -

                          Project

                          -

                          The project corresponds to the current region and can be changed.

                          -

                          Task Name

                          -

                          The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                          -

                          Description

                          -

                          The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

                          -
                          -
                          - -
                          - - - - - - - - - - - - - - - - - - - - - - - - - -
                          Table 6 Synchronization instance settings

                          Parameter

                          -

                          Description

                          -

                          Data Flow

                          -

                          Select Out of the cloud.

                          -

                          Source DB Engine

                          -

                          Select GaussDB Distributed Edition.

                          -

                          Destination DB Engine

                          -

                          Select MySQL.

                          -

                          Network Type

                          -

                          The public network is used as an example. Available options: Public network and VPN or Direct Connect

                          -

                          Source DB Instance

                          -

                          The GaussDB distributed instance you created.

                          -

                          Synchronization Mode

                          -
                          • Incremental

                            Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                            -
                          -

                          Tags

                          -
                          • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                          • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                          -
                          -
                          -

                          If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                          -
                          -

                        3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, click Next.

                          Establish the connectivity between the DRS instance and the source and destination databases.

                          -
                          • Network connectivity: Ensure that the source and destination databases accept connections from the DRS instance.
                          • Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.
                          - -
                          - - - - - - - - - - - - - -
                          Table 7 Source database settings

                          Parameter

                          -

                          Description

                          -

                          DB Instance Name

                          -

                          The GaussDB distributed instance selected during synchronization task creation. This parameter cannot be changed.

                          -

                          Database Username

                          -

                          The username for accessing the source database.

                          -

                          Database Password

                          -

                          The password for the database username.

                          -
                          -
                          -

                          The username and password of the source database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                          -
                          - -
                          - - - - - - - - - - - - - - - - - - - -
                          Table 8 Destination database settings

                          Parameter

                          -

                          Description

                          -

                          IP Address or Domain Name

                          -

                          IP address or domain name of the destination database in the IP address/Domain name:Port format. The port of the destination database. Range: 1 - 65535

                          -

                          Port

                          -

                          The port of the destination database. Range: 1 - 65535

                          -

                          Database Username

                          -

                          The username for accessing the destination database.

                          -

                          Database Password

                          -

                          The password for the database username.

                          -

                          SSL Connection

                          -

                          SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                          -
                          NOTE:
                          • The maximum size of a single certificate file that can be uploaded is 500 KB.
                          • If SSL is disabled, your data may be at risk.
                          -
                          -
                          -
                          -

                          The username and password of the destination database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                          -
                          -

                        4. On the Set Synchronization Task page, select the objects to be synchronized, and then click Next.

                          -

                          - - - - - - - - - - -
                          Table 9 Synchronization Object

                          Parameter

                          -

                          Description

                          -

                          Incremental Conflict Policy

                          -

                          The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored. Select any of the following conflict policies:

                          -
                          • Ignore

                            The system will skip the conflicting data and continue the subsequent synchronization process.

                            -
                          • Report error

                            The synchronization task will be stopped and fail.

                            -
                          • Overwrite

                            Conflicting data will be overwritten.

                            -
                          -

                          Synchronization Object

                          -

                          DRS supports table-level synchronization. You can select data for synchronization based on your service requirements.

                          -

                          If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

                          -
                          NOTE:
                          • To quickly select the desired database objects, you can use the search function.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          -
                          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                          • The name of the selected synchronization object cannot contain spaces.
                          -
                          -
                          -
                          -

                        5. On the Check Task page, check the synchronization task.

                          • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                          • If all check items are successful, click Next.

                            You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                            -
                            -
                          -

                        6. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                          -

                          - - - - - - - -
                          Table 10 Task startup settings

                          Parameter

                          -

                          Description

                          -

                          Started Time

                          -

                          Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                          -
                          NOTE:

                          After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

                          -
                          -
                          -
                          -

                        7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                          • You can view the task status. For more information about task status, see Task Statuses.
                          • You can click in the upper-right corner to view the latest task status.
                          -

                        -
                        -
                        -
                        -
                        -
                        Parent topic: Out of the Cloud
                        -
                        -
                        - diff --git a/docs/drs/umn/drs_04_0122.html b/docs/drs/umn/drs_04_0122.html index 23bb0312d..2b4c00038 100644 --- a/docs/drs/umn/drs_04_0122.html +++ b/docs/drs/umn/drs_04_0122.html @@ -27,38 +27,40 @@

                        Precautions

                        Before creating a DR task, read the following precautions:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the service or DR databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        Table 2 Precautions

                        Type

                        +
                        - - - - - - - - - - - @@ -265,13 +267,7 @@ - - - - @@ -354,7 +350,7 @@
                        • If the check is complete and the check success rate is 100%, go to the Compare Parameter page.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

                        +

                      • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

                        • Table 2 Precautions

                        Type

                        Constraint

                        +

                        Constraint

                        Database permissions

                        +

                        Database permissions

                        • The service database user must have the following permissions:

                          The user root of the RDS for MySQL instance has the following permissions by default: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, TRIGGER, REFERENCES, SHOW VIEW, EVENT, INDEX, LOCK TABLES, CREATE VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, RELOAD, REPLICATION SLAVE, REPLICATION CLIENT, and WITH GRANT OPTION If the service database version is 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                          +
                        • The service database user must have the following permissions:

                          The user root of the RDS for MySQL instance has the following permissions by default: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, TRIGGER, REFERENCES, SHOW VIEW, EVENT, INDEX, LOCK TABLES, CREATE VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, RELOAD, REPLICATION SLAVE, REPLICATION CLIENT, and WITH GRANT OPTION If the service database version is 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                        • The DR database user must have the following permissions:

                          The user root of the RDS for MySQL instance has the following permissions by default: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, TRIGGER, REFERENCES, SHOW VIEW, EVENT, INDEX, LOCK TABLES, CREATE VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, RELOAD, REPLICATION SLAVE, REPLICATION CLIENT, and WITH GRANT OPTION If the DR database version is 8.0.14 to 8.0.18, the SESSION_VARIABLES_ADMIN permission is required.

                        Disaster recovery objects

                        +

                        Disaster recovery objects

                        • Tables with storage engine different to MyISAM and InnoDB do not support disaster recovery.
                        • System tables are not supported.
                        • Triggers and events do not support disaster recovery.
                        • Accounts that have operation permissions on customized objects in the system database cannot be used for disaster recovery.
                        • Backup and disaster recovery, cross-database DDL, and rename operations cannot be performed on some specified service databases. Otherwise, the disaster recovery fails.
                        +
                        • Tables with storage engine different to MyISAM and InnoDB do not support disaster recovery.
                        • System tables are not supported.
                        • Triggers and events do not support disaster recovery.
                        • Accounts that have operation permissions on customized objects in the system database cannot be used for disaster recovery.
                        • Backup and disaster recovery, cross-database DDL, and rename operations cannot be performed on some specified service databases. Otherwise, the disaster recovery fails.

                        Service database configuration

                        +

                        Service database configuration

                        • The binlog of the MySQL service database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the service database binlog for as long as possible. The recommended retention period is seven days.
                        • The service database username or password cannot be empty.
                        • server_id in the MySQL service database must be set. If the service database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the service database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                        • GTID must be enabled for the database.
                        • The service database name must contain 1 to 64 characters, including only lowercase letters, digits, hyphens (-), and underscores (_).
                        • The table name and view name in the service database cannot contain non-ASCII characters, or the following characters: '<>/\
                        • If the expire_logs_days value of the database is set to 0, the disaster recovery may fail.
                        +
                        • The binlog of the MySQL service database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the service database binlog for as long as possible. The recommended retention period is seven days.
                        • The service database username or password cannot be empty.
                        • server_id in the MySQL service database must be set. If the service database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the service database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                        • GTID must be enabled for the database.
                        • The service database name must contain 1 to 64 characters, including only lowercase letters, digits, hyphens (-), and underscores (_).
                        • The table name and view name in the service database cannot contain non-ASCII characters, or the following characters: '<>/\
                        • If the expire_logs_days value of the database is set to 0, the disaster recovery may fail.

                        DR database configuration

                        +

                        DR database configuration

                        • The DR DB instance is running properly. If the DR DB instance is a primary/standby instance, the replication status must also be normal.
                        • The DR DB instance must have sufficient storage space.
                        • The major version of the DR database must be the same as that of the service database.
                        • The binlog of the DR database must be enabled and use the row-based format.
                        • GTID must be enabled for the DR database.
                        • Except the MySQL system database, the DR database must be empty. After a DR task starts, the DR database is set to read-only.
                        +
                        • The DR DB instance is running properly. If the DR DB instance is a primary/standby instance, the replication status must also be normal.
                        • The DR DB instance must have sufficient storage space.
                        • The major version of the DR database must be the same as that of the service database.
                        • The binlog of the DR database must be enabled and use the row-based format.
                        • GTID must be enabled for the DR database.
                        • Except the MySQL system database, the DR database must be empty. After a DR task starts, the DR database is set to read-only.

                        Precautions

                        +

                        Precautions

                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • The service database does not support point-in-time recovery (PITR).
                        • Binlogs cannot be forcibly deleted. Otherwise, the DR task fails.
                        • The service database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • If the network is reconnected within 30 seconds, disaster recovery will not be affected. If the network is interrupted for more than 30 seconds, the DR task will fail.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • Migration or synchronization tasks cannot be created when a DR task exists.
                        • The parameter modification of the service database is not recorded in logs and is not synchronized to the DR database. Therefore, you need to modify the parameters after the DR database is promoted to the primary.
                        • If the service database and DR database are RDS MySQL instances, tables with TDE enabled cannot be created.
                        • If a high-privilege user created in an external database is not supported by RDS MySQL, the user will not be synchronized to the DR database, for example, the super user.
                        • If the external database does not provide the superuser permission, it cannot be set to read-only when it acts as a standby database. Ensure that the data of the standby node is synchronized only from the primary node. Any other write operations will pollute the data in the standby database, data conflicts may occur in the DR center and cannot be resolved.
                        • If the external database is a standby and read-only database, only the account with the superuser permission can write data to that database. But you still need to ensure that data is written only by this account. Otherwise, the standby database may be polluted, and data conflicts occur in the DR center and cannot be resolved.
                        • During disaster recovery, if the password of the service database is changed, the DR task will fail. To rectify the fault, you can correct the service database information on the DRS console and retry the task to continue disaster recovery. Generally, you are advised not to modify the preceding information during disaster recovery.
                        • If the service database port is changed during disaster recovery, the DR task fails. Generally, you are advised not to modify the service database port during disaster recovery.
                        • During disaster recovery, if the service database is on an RDS DB instance that does not belong the current cloud platform, the IP address cannot be changed. If the service database is an RDS instance on the current cloud and the DR task fails due to changes on the IP address, DRS automatically changes the IP address to the correct one. Then, you can retry the task to continue disaster recovery. Therefore, changing the IP address is not recommended.
                        • During disaster recovery, you can create accounts for the service database.
                        • During the DR initialization, do not perform DDL operations on the source database. Otherwise, the DR task may be abnormal.
                        • Do not write data to the source database during the primary/standby switchover. Otherwise, data pollution or table structure inconsistency may occur, resulting in data inconsistency between the service database and DR database.
                        +
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • The service database does not support point-in-time recovery (PITR).
                        • Binlogs cannot be forcibly deleted. Otherwise, the DR task fails.
                        • The service database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • If the network is reconnected within 30 seconds, disaster recovery will not be affected. If the network is interrupted for more than 30 seconds, the DR task will fail.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • Migration or synchronization tasks cannot be created when a DR task exists.
                        • The parameter modification of the service database is not recorded in logs and is not synchronized to the DR database. Therefore, you need to modify the parameters after the DR database is promoted to the primary.
                        • If the service database and DR database are RDS for MySQL instances, tables with TDE enabled cannot be created.
                        • If a high-privilege user created in an external database is not supported by RDS for MySQL, the user will not be synchronized to the DR database, for example, the super user.
                        • If the external database does not provide the superuser permission, it cannot be set to read-only when it acts as a standby database. Ensure that the data of the standby node is synchronized only from the primary node. Any other write operations will pollute the data in the standby database, data conflicts may occur in the DR center and cannot be resolved.
                        • If the external database is a standby and read-only database, only the account with the superuser permission can write data to that database. But you still need to ensure that data is written only by this account. Otherwise, the standby database may be polluted, and data conflicts occur in the DR center and cannot be resolved.
                        • During disaster recovery, if the password of the service database is changed, the DR task will fail. To rectify the fault, you can correct the service database information on the DRS console and retry the task to continue disaster recovery. Generally, you are advised not to modify the preceding information during disaster recovery.
                        • If the service database port is changed during disaster recovery, the DR task fails. Generally, you are advised not to modify the service database port during disaster recovery.
                        • During disaster recovery, if the service database is on an RDS DB instance that does not belong the current cloud platform, the IP address cannot be changed. If the service database is an RDS instance on the current cloud and the DR task fails due to changes on the IP address, DRS automatically changes the IP address to the correct one. Then, you can retry the task to continue disaster recovery. Therefore, changing the IP address is not recommended.
                        • During disaster recovery, you can create accounts for the service database.
                        • During the DR initialization, do not perform DDL operations on the source database. Otherwise, the DR task may be abnormal.
                        • Do not write data to the source database during the primary/standby switchover. Otherwise, data pollution or table structure inconsistency may occur, resulting in data inconsistency between the service database and DR database.

                        Database Type

                        -

                        By default, Self-built on ECS is selected.

                        -

                        The destination database can be a Self-built on ECS or an RDS DB instance. If you select RDS DB instance, you need to select the region where the destination database is located. To use the RDS DB instance option, submit a service ticket.

                        -

                        IP Address or Domain Name

                        +

                        IP Address or Domain Name

                        The IP address or domain name of the DR database.

                        Table 11 Task and recipient description

                        Parameter

                        Description

                        @@ -371,7 +367,7 @@
                        -

                      • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0123.html b/docs/drs/umn/drs_04_0123.html index 813c9e148..8d9183eca 100644 --- a/docs/drs/umn/drs_04_0123.html +++ b/docs/drs/umn/drs_04_0123.html @@ -1,6 +1,6 @@ -

                        From MySQL to GaussDB(for MySQL) Primary/Standby

                        +

                        From MySQL to TaurusDB Cluster

                        Supported Source and Destination Databases

                        @@ -10,7 +10,7 @@ - @@ -27,36 +27,38 @@

                        Precautions

                        Before creating a DR task, read the following precautions:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the service or DR databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        Table 1 Supported databases

                        Service Database
                        • On-premises MySQL databases
                        • MySQL databases on an ECS
                        • MySQL databases on other clouds
                        • RDS for MySQL
                        • GaussDB(for MySQL) primary/standby
                        +
                        • TaurusDB Cluster
                        Table 2 Precautions

                        Type

                        +
                        - - - - - - - - - - - @@ -114,7 +116,7 @@ - - - - @@ -22,37 +22,39 @@

                        Suggestions

                        • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                        • It is recommended that you start a task during off-peak hours to minimize the impact of synchronization on your services.

                        Precautions

                        Before creating a synchronization task, read the following notes:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        Table 2 Precautions

                        Type

                        Restrictions

                        +

                        Restrictions

                        Database permissions

                        +

                        Database permissions

                        • The service database user must have the following permissions: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, TRIGGER, REFERENCES, SHOW VIEW, EVENT, INDEX, LOCK TABLES, CREATE VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, RELOAD, REPLICATION SLAVE, REPLICATION CLIENT, and WITH GRANT OPTION.
                        • The DR database user must have the following permissions: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, TRIGGER, REFERENCES, SHOW VIEW, EVENT, INDEX, LOCK TABLES, CREATE VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, RELOAD, REPLICATION SLAVE, REPLICATION CLIENT, and WITH GRANT OPTION.
                        • The root account of the RDS MySQL DB instance has the preceding permissions by default.
                        +
                        • The service database user must have the following permissions: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, TRIGGER, REFERENCES, SHOW VIEW, EVENT, INDEX, LOCK TABLES, CREATE VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, RELOAD, REPLICATION SLAVE, REPLICATION CLIENT, and WITH GRANT OPTION.
                        • The DR database user must have the following permissions: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, UPDATE, TRIGGER, REFERENCES, SHOW VIEW, EVENT, INDEX, LOCK TABLES, CREATE VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, RELOAD, REPLICATION SLAVE, REPLICATION CLIENT, and WITH GRANT OPTION.
                        • The root account of the RDS for MySQL DB instance has the preceding permissions by default.

                        Disaster recovery objects

                        +

                        Disaster recovery objects

                        • Tables with storage engine different to MyISAM and InnoDB do not support disaster recovery.
                        • System tables are not supported.
                        • Triggers and events do not support disaster recovery.
                        • Accounts that have operation permissions on customized objects in the system database cannot be used for disaster recovery.
                        • Backup and disaster recovery, cross-database DDL, and rename operations cannot be performed on some specified service databases. Otherwise, the disaster recovery fails.
                        +
                        • Tables with storage engine different to MyISAM and InnoDB do not support disaster recovery.
                        • System tables are not supported.
                        • Triggers and events do not support disaster recovery.
                        • Accounts that have operation permissions on customized objects in the system database cannot be used for disaster recovery.
                        • Backup and disaster recovery, cross-database DDL, and rename operations cannot be performed on some specified service databases. Otherwise, the disaster recovery fails.

                        Service database configuration

                        +

                        Service database configuration

                        • The binlog of the MySQL service database must be enabled and use the row-based format.
                        • If the storage space is sufficient, you are advised to store the service database binlog for as long as possible. The recommended retention period is seven days.
                        • The service database username or password cannot be empty.
                        • server-id in the MySQL service database must be set. If the service database version is MySQL 5.6 or earlier, the server-id value ranges from 2 to 4294967296. If the service database is MySQL 5.7 or later, the server-id value ranges from 1 to 4294967296.
                        • GTID must be enabled for the database.
                        • The service database name must contain 1 to 64 characters, including only lowercase letters, digits, hyphens (-), and underscores (_).
                        • The table name and view name in the service database cannot contain non-ASCII characters, or the following characters: '<>/\
                        • If the expire_logs_days value of the database is set to 0, the disaster recovery may fail.
                        +
                        • The binlog of the MySQL service database must be enabled and use the row-based format.
                        • If the storage space is sufficient, you are advised to store the service database binlog for as long as possible. The recommended retention period is seven days.
                        • The service database username or password cannot be empty.
                        • server-id in the MySQL service database must be set. If the service database version is MySQL 5.6 or earlier, the server-id value ranges from 2 to 4294967296. If the service database is MySQL 5.7 or later, the server-id value ranges from 1 to 4294967296.
                        • GTID must be enabled for the database.
                        • The service database name must contain 1 to 64 characters, including only lowercase letters, digits, hyphens (-), and underscores (_).
                        • The table name and view name in the service database cannot contain non-ASCII characters, or the following characters: '<>/\
                        • If the expire_logs_days value of the database is set to 0, the disaster recovery may fail.

                        DR database configuration

                        +

                        DR database configuration

                        • The DR DB instance is running properly. If the DR DB instance is a primary/standby instance, the replication status must also be normal.
                        • The DR DB instance must have sufficient storage space.
                        • The binlog of the DR database must be enabled and use the row-based format.
                        • GTID must be enabled for the DR database.
                        • The DR DB instance cannot contain any service databases except the system database.
                        +
                        • The DR DB instance is running properly. If the DR DB instance is a primary/standby instance, the replication status must also be normal.
                        • The DR DB instance must have sufficient storage space.
                        • The binlog of the DR database must be enabled and use the row-based format.
                        • GTID must be enabled for the DR database.
                        • The DR DB instance cannot contain any service databases except the system database.

                        Precautions

                        +

                        Precautions

                        • The parameter modification of the service database is not recorded in logs and is not synchronized to the DR database. Therefore, you need to modify the parameters after the DR database is promoted to the primary.
                        • If a high-privilege user created in an external database is not supported by RDS MySQL, the user will not be synchronized to the DR database, for example, the super user.
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • The service database does not support point-in-time recovery (PITR).
                        • Binlogs cannot be forcibly deleted. Otherwise, the DR task fails.
                        • The service database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • If the network is reconnected within 30 seconds, disaster recovery will not be affected. If the network is interrupted for more than 30 seconds, the DR task will fail.
                        • If the DCC does not support instances with 4 vCPUs and 8 GB memory or higher instance specifications, the DR task cannot be created.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • Migration or synchronization tasks cannot be created when a DR task exists.
                        • If the external database does not provide the superuser permission, it cannot be set to read-only when it acts as a standby database. Ensure that the data of the standby node is synchronized only from the primary node. Any other write operations will pollute the data in the standby database, data conflicts occur in the DR center and cannot be resolved.
                        • If the external database is a standby and read-only database, only the account with the superuser permission can write data to that database. But you still need to ensure that data is written only by this account. Otherwise, the standby database may be polluted, and data conflicts occur in the DR center and cannot be resolved.
                        • When DR occurs between an earlier version database and a later version database, service activities must be compatible with both the earlier version and the later version. Otherwise, the DR may fail.
                        • If the service database is an RDS MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • During disaster recovery, if the password of the service database is changed, the DR task will fail. To rectify the fault, you can correct the service database information on the DRS console and retry the task to continue disaster recovery. Generally, you are advised not to modify the preceding information during disaster recovery.
                        • If the service database port is changed during disaster recovery, the DR task fails. Generally, you are advised not to modify the service database port during disaster recovery.
                        • During disaster recovery, if the service database is on an RDS DB instance that does not belong the current cloud platform, the IP address cannot be changed. If the service database is an RDS DB instance on the current cloud and the DR task fails due to changes on the IP address, DRS automatically changes the IP address to the correct one. Then, you can retry the task to continue disaster recovery. Therefore, changing the IP address is not recommended.
                        • During disaster recovery, you can create accounts for the service database.
                        • During the DR initialization, do not perform DDL operations on the source database. Otherwise, the DR task may be abnormal.
                        • Do not write data to the source database during the primary/standby switchover. Otherwise, data pollution or table structure inconsistency may occur, resulting in data inconsistency between the service database and DR database.
                        +
                        • The parameter modification of the service database is not recorded in logs and is not synchronized to the DR database. Therefore, you need to modify the parameters after the DR database is promoted to the primary.
                        • If a high-privilege user created in an external database is not supported by RDS for MySQL, the user will not be synchronized to the DR database, for example, the super user.
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • The service database does not support point-in-time recovery (PITR).
                        • Binlogs cannot be forcibly deleted. Otherwise, the DR task fails.
                        • The service database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • If the network is reconnected within 30 seconds, disaster recovery will not be affected. If the network is interrupted for more than 30 seconds, the DR task will fail.
                        • If the DCC does not support instances with 4 vCPUs and 8 GB memory or higher instance specifications, the DR task cannot be created.
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
                        • Migration or synchronization tasks cannot be created when a DR task exists.
                        • If the external database does not provide the superuser permission, it cannot be set to read-only when it acts as a standby database. Ensure that the data of the standby node is synchronized only from the primary node. Any other write operations will pollute the data in the standby database, data conflicts occur in the DR center and cannot be resolved.
                        • If the external database is a standby and read-only database, only the account with the superuser permission can write data to that database. But you still need to ensure that data is written only by this account. Otherwise, the standby database may be polluted, and data conflicts occur in the DR center and cannot be resolved.
                        • When DR occurs between an earlier version database and a later version database, service activities must be compatible with both the earlier version and the later version. Otherwise, the DR may fail.
                        • If the service database is an RDS for MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • During disaster recovery, if the password of the service database is changed, the DR task will fail. To rectify the fault, you can correct the service database information on the DRS console and retry the task to continue disaster recovery. Generally, you are advised not to modify the preceding information during disaster recovery.
                        • If the service database port is changed during disaster recovery, the DR task fails. Generally, you are advised not to modify the service database port during disaster recovery.
                        • During disaster recovery, if the service database is on an RDS DB instance that does not belong the current cloud platform, the IP address cannot be changed. If the service database is an RDS DB instance on the current cloud and the DR task fails due to changes on the IP address, DRS automatically changes the IP address to the correct one. Then, you can retry the task to continue disaster recovery. Therefore, changing the IP address is not recommended.
                        • During disaster recovery, you can create accounts for the service database.
                        • During the DR initialization, do not perform DDL operations on the source database. Otherwise, the DR task may be abnormal.
                        • Do not write data to the source database during the primary/standby switchover. Otherwise, data pollution or table structure inconsistency may occur, resulting in data inconsistency between the service database and DR database.

                        DR DB Engine

                        Select GaussDB(for MySQL) Primary/Standby Edition.

                        +

                        Select TaurusDB Cluster.

                        Network Type

                        @@ -125,7 +127,7 @@

                        DR DB Instance

                        The GaussDB(for MySQL) primary/standby instance you created.

                        +

                        The cluster TaurusDB instance you created.

                        Disaster Recovery Instance Subnet

                        @@ -195,7 +197,7 @@

                        DB Instance Name

                        The GaussDB(for MySQL) primary/standby instance you selected when creating the DR. This parameter cannot be changed.

                        +

                        The cluster TaurusDB instance selected when you created the task. This parameter cannot be changed.

                        Database Username

                        @@ -248,7 +250,7 @@
                        • If the check is complete and the check success rate is 100%, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

                        +

                      • On the Confirm Task page, specify Start Time and DR instance details. Then, click Submit.

                        Table 8 Task and recipient description

                        Parameter

                        Description

                        @@ -265,7 +267,7 @@
                        -

                      • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the DR task is submitted, view and manage it on the Disaster Recovery Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0128.html b/docs/drs/umn/drs_04_0128.html index f8c28ac2a..1403fe22b 100644 --- a/docs/drs/umn/drs_04_0128.html +++ b/docs/drs/umn/drs_04_0128.html @@ -10,7 +10,7 @@
                        • On-premises MySQL databases
                        • MySQL databases on an ECS
                        • Kafka
                        • DMS for Kafka
                        +
                        • Kafka
                        @@ -148,6 +148,11 @@ + + + @@ -277,7 +282,7 @@

                      • On the Check Task page, check the synchronization task.

                        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                        • If all check items are successful, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                        -

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        +

                      • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                        • Table 2 Precautions

                        Type

                        +
                        - - - - - - - - - - - @@ -145,6 +147,11 @@ + + +
                        Table 2 Precautions

                        Type

                        Restrictions

                        +

                        Restrictions

                        Database permissions

                        +

                        Database permissions

                        • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, REPLICATION CLIENT, and RELOAD.
                        +
                        • The source database user must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE, REPLICATION CLIENT, and RELOAD.

                        Synchronization object

                        +

                        Synchronization object

                        • The table data can be synchronized.
                        +
                        • The table data can be synchronized.
                        • Tables with storage engine different to MyISAM and InnoDB cannot be synchronized.

                        Source database

                        +

                        Source database

                        • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7, the server_id value ranges from 1 to 4294967296.
                        • The database and table names in the source database cannot contain non-ASCII characters, or special characters '<`>/\
                        +
                        • During the incremental synchronization, the binlog of the source MySQL database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • If the expire_logs_days value of the source database is set to 0, the synchronization may fail.
                        • Enable GTID for the source database. If GTID is not enabled for the source database, primary/standby switchover is not supported. DRS tasks will be interrupted and cannot be restored during a switchover.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7, the server_id value ranges from 1 to 4294967296.
                        • The database and table names in the source database cannot contain non-ASCII characters, or special characters '<`>/\

                        Destination database

                        +

                        Destination database

                        • The destination database is a Kafka database.
                        +
                        • The destination database is a Kafka database.

                        Precautions

                        +

                        Precautions

                        • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
                        • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • During the synchronization, do not delete or change the username, password, or permission of the source database, or change the port of the destination database.
                        • Data inconsistency may occur when the MyISAM table is modified during synchronization.
                        • During synchronization of table-level objects, renaming tables is not recommended.
                        +
                        • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure. Common dependencies: tables referenced by views, views referenced by views, views and tables referenced by stored procedures/functions/triggers, and tables referenced by primary and foreign keys
                        • Cascade operations cannot be performed on tables with foreign keys. If the foreign key index of a table is a common index, the table structure may fail to be created. You are advised to use a unique index.
                        • Binlogs cannot be forcibly deleted. Otherwise, the synchronization task fails.
                        • The source database does not support the reset master or reset master to command, which may cause DRS task failures or data inconsistency.
                        • If the source MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • During the synchronization, do not delete or change the username, password, or permission of the source database, or change the port of the destination database.
                        • Data inconsistency may occur when the MyISAM table is modified during synchronization.
                        • During synchronization of table-level objects, renaming tables is not recommended.

                        Specifications

                        +

                        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                        +

                        Tags
                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        @@ -267,17 +274,17 @@

                        Synchronization Object

                        Available options: Tables and Databases.

                        -
                        • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.
                        +

                      • On the Process Data page, select the columns to be processed.

                        • If data processing is not required, click Next.
                        • If you need to process columns, set processing rules by referring to Processing Data.
                        -

                      • On the Check Task page, check the synchronization task.

                        • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                        • If all check items are successful, click Next.

                          You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                          +

                        • On the Check Task page, check the synchronization task.

                          • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                          • If all check items are successful, click Next.

                            You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                          -

                        • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                          +

                        • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                          Table 8 Task startup settings

                          Parameter

                          Description

                          @@ -294,7 +301,7 @@
                          -

                        • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                          • You can view the task status. For more information about task status, see Task Statuses.
                          • You can click in the upper-right corner to view the latest task status.
                          +

                        • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                          • You can view the task status. For more information about task status, see Task Statuses.
                          • You can click in the upper-right corner to view the latest task status.
                          • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                          • diff --git a/docs/drs/umn/drs_04_0446.html b/docs/drs/umn/drs_04_0446.html index 949ca83e9..99b2c58bd 100644 --- a/docs/drs/umn/drs_04_0446.html +++ b/docs/drs/umn/drs_04_0446.html @@ -59,7 +59,7 @@

                        • Precautions
                        • Objects that have dependencies must be synchronized at the same time to avoid synchronization failure.
                        • Object names, such as table names, are converted to lowercase letters after being synchronized to the destination database. For example, ABC is converted to abc. In incremental synchronization, the source database cannot contain tables with the same name but different letter cases. Otherwise, the synchronization will fail.
                        • If there are special characters in the Oracle database, the code of the destination Oracle database must be the same as the code of the source Oracle database. Otherwise, garbled characters are displayed in the destination database.
                        • If a task fails because the (self-built) table structure of a table without primary keys is not synchronized and the task cannot be resumed after the table structure is restored, reset the task.
                        • During table structure synchronization, if the destination database has a constraint with the same name as the source database, the table fails to be created.
                        • If you use DRS to synchronize table structures, the tables, constraints, and indexes in the same schema cannot have the same name with different letter cases. For example, table A contains an index named inx1, and table B contains an index name a. Table A and index a have the same name with different letter cases, which will cause table structure synchronization to fail. If multiple schemas are mapped to one schema, the source schemas cannot contain tables, constraints, and indexes with the same name but different letter cases.
                        • If the Oracle character set is WE8MSWIN1252, the CLOB column synchronized to the destination database may contain garbled characters. You can change the character set of the source database to AL32UTF8 before the synchronization.
                        • If the length of a table structure in the Oracle database exceeds 65,535 bytes, the synchronization may fail. The length of a table structure is the total length of all columns. The length of the char or varchar2 type is related to the code.
                        • The size of an Oracle archive log file must be greater than the maximum size of a single data record to prevent incremental data parsing exceptions caused by cross-file (more than two log files) of a single data record.
                        • For an Oracle RAC cluster, use the scan IP address and service name to create a task. The SCAN IP address can provide better fault tolerance, load capability, and synchronization experience.
                        • If the source is an Oracle RAC database and the SCAN IP address is used to configure a DRS task, ensure that the SCAN IP address and DRS node IP address can communicate with all virtual IP addresses of the source database. Otherwise, the connectivity check fails. If the SCAN IP address is not used, the virtual IP address of a node can be used. In this case, DRS logs are parsed only on the RAC node specified by the virtual IP address.
                        • If the source is an RAC database, all RAC nodes must be online when incremental synchronization is started for the first time. Otherwise, an error occurs during incremental synchronization.
                        • If the source is an RAC database, the number of nodes cannot be increased or decreased during incremental synchronization to avoid incremental synchronization exceptions and ensure strong data consistency.
                        • During synchronization, do not delete the username, password, and permissions of the source and destination databases or change the port of the destination database.
                        • During the synchronization, do not perform the resetlogs operation on the source Oracle database. Otherwise, data cannot be synchronized and tasks cannot be restored.
                        • During synchronization, the rollback operation of the LOB type is not supported. Otherwise, the synchronization task fails.
                        • In a full synchronization for the table structure, the length of the char and varchar2 characters in the source database is automatically increased by at least 1.5 times by byte in the destination database (because the length of the destination database is in the unit of byte). The increase multiple depends on the character set of the source and destination databases. For example, if the character set is UTF8, increase the length (byte) by three times by default. If the character set is GBK, increase the length (byte) by two times by default.
                        • During full synchronization of the partitioned table structure, the table is converted to a non-partitioned table. During incremental synchronization, operations related to the partitioned table in the source database may fail to be executed in the destination database.
                        • Only normal indexes are synchronized when indexes are synchronized. Primary key constraints are synchronized with the table structure.
                        • During an incremental synchronization, 0x00 at the end of BLOB and the spaces at the end of CLOB are truncated.
                        • During incremental synchronization, some DDL operations are supported.
                          • Table-level synchronization supports alter table add column, alter table drop column, alter table rename column, alter table modify column, and truncate table. The modification of default values is not supported.
                          -
                        • The names of mapped table-level objects are case-insensitive. For example, the ABC table mapped to the destination database will be changed to table abc.
                        • When editing the task to add a new table, ensure that transactions of the new table have been committed. Otherwise, transactions that are not committed may fail to be synchronized to the destination database. You are advised to add tables during off-peak hours.
                        • During a full synchronization, DRS writes large amount of data to the destination PostgreSQL database. As a result, the number of PostgreSQL WAL logs increases sharply, and the PostgreSQL disk space may be used up. You can disable the PostgreSQL log backup function before the full synchronization to reduce the number of WAL logs. After the synchronization is complete, enable the function.
                          CAUTION:

                          Disabling log backup will affect database disaster recovery. Exercise caution when performing this operation.

                          +
                        • The names of mapped table-level objects are case-insensitive. For example, the ABC table mapped to the destination database will be changed to table abc.
                        • When editing the task to add a new table, ensure that transactions of the new table have been committed. Otherwise, transactions that are not committed may fail to be synchronized to the destination database. You are advised to add tables during off-peak hours.
                        • In a full+incremental or incremental synchronization, the PDB database cannot be directly connected if you set the incremental read mode to LogMiner. You need to provide the service name/SID, username, and password of the CDB.
                        • During a full synchronization, DRS writes large amount of data to the destination PostgreSQL database. As a result, the number of PostgreSQL WAL logs increases sharply, and the PostgreSQL disk space may be used up. You can disable the PostgreSQL log backup function before the full synchronization to reduce the number of WAL logs. After the synchronization is complete, enable the function.
                          CAUTION:

                          Disabling log backup will affect database disaster recovery. Exercise caution when performing this operation.

                        Specifications

                        +

                        DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                        +

                        Tags
                        • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                        • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                        @@ -265,8 +270,8 @@

                        Synchronization Object

                        Select Tables or Databases as required.

                        -
                        • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.
                        -
                        NOTE:
                        • To quickly select the desired database objects, you can use the search function.
                        • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                        + +
                        NOTE:
                        • You can search for table names to quickly select the required database objects.
                        • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                        • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                        • The name of the selected synchronization object cannot contain spaces.
                        Table 8 Task startup settings

                        Parameter

                        Description

                        @@ -294,7 +299,7 @@
                        -

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        +

                      • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                        • You can view the task status. For more information about task status, see Task Statuses.
                        • You can click in the upper-right corner to view the latest task status.
                        • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                        • diff --git a/docs/drs/umn/drs_04_0451.html b/docs/drs/umn/drs_04_0451.html index 131e2816f..27ba53613 100644 --- a/docs/drs/umn/drs_04_0451.html +++ b/docs/drs/umn/drs_04_0451.html @@ -10,7 +10,15 @@
                      • From DDM to MySQL
                        • -
                      • From GaussDB Distributed to MySQL
                        +
                      • From DDS to MongoDB
                        +
                        • +
                      • From PostgreSQL to PostgreSQL
                        +
                        • +
                      • From GaussDB Distributed to Oracle
                        +
                        • +
                      • From GaussDB Distributed to Kafka
                        +
                        • +
                      • From GaussDB Distributed to GaussDB Distributed
                        • diff --git a/docs/drs/umn/drs_04_0452.html b/docs/drs/umn/drs_04_0452.html index 0a02606e9..aebaf8788 100644 --- a/docs/drs/umn/drs_04_0452.html +++ b/docs/drs/umn/drs_04_0452.html @@ -5,8 +5,6 @@
                        diff --git a/docs/drs/umn/drs_04_0453.html b/docs/drs/umn/drs_04_0453.html index ade0cbdce..7165c9f36 100644 --- a/docs/drs/umn/drs_04_0453.html +++ b/docs/drs/umn/drs_04_0453.html @@ -26,44 +26,253 @@

                        Precautions

                        Before creating a synchronization task, read the following notes:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        -
                        - - -
                        Table 2 Precautions

                        Type

                        +
                        - - - - - - - - - - -
                        Table 2 Precautions

                        Type

                        Restrictions

                        +

                        Restrictions

                        Database permissions

                        +

                        Database permissions

                        • The source database DDM account must have the SELECT permission. The physical sharded database account must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE and REPLICATION CLIENT.
                        -
                        • The destination database user must have the following permissions: SELECT, CREATE, DROP, DELETE, INSERT, and UPDATE. The root account of the RDS MySQL DB instance has the preceding permissions by default.
                        +
                        • The source database DDM account must have at least one permission, for example, SELECT. The physical sharded database account must have the following permissions: SELECT, SHOW VIEW, EVENT, LOCK TABLES, REPLICATION SLAVE and REPLICATION CLIENT.
                        +
                        • The destination database user must have the following permissions: SELECT, CREATE, ALTER, DROP, DELETE, INSERT, and UPDATE. The root account of the RDS for MySQL DB instance has the preceding permissions by default.

                        Synchronization object

                        +

                        Synchronization object

                        • Full synchronization supports the synchronization of data, table structures, and indexes.
                        • The source database cannot contain tables whose sharding keys are timestamp.
                        • The sharding key of the source table must be added to the primary key and unique key of the destination table, which means that the primary key and unique key columns of the destination table must contain the sharded columns of the source table to avoid data conflict and inconsistency.
                        +
                        • Full synchronization supports the synchronization of data, table structures, and indexes.
                        • The source database cannot contain tables whose sharding keys are timestamp.
                        • The sharding key of the source table must be added to the primary key and unique key of the destination table, which means that the primary key and unique key columns of the destination table must contain the sharded columns of the source table to avoid data conflict and inconsistency.

                        Source database

                        +

                        Source database

                        • During the incremental synchronization, the binlog of the source sharded database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                        • The database names and table names of the source sharding middleware cannot contain the following characters: '<>/\ and non-ASCII characters.
                        • Enable skip-name-resolve for the MySQL source database to reduce the possibility of connection timeout.
                        • Enable GTID of the source database.
                        +
                        • During the incremental synchronization, the binlog of the source sharded database must be enabled and use the row-based format.
                        • If the storage space is sufficient, store the source database binlog for as long as possible. The recommended retention period is three days.
                        • During an incremental synchronization, the server_id value of the MySQL source database must be set. If the source database version is MySQL 5.6 or earlier, the server_id value ranges from 2 to 4294967296. If the source database is MySQL 5.7 or later, the server_id value ranges from 1 to 4294967296.
                        • The database names and table names of the source sharding middleware cannot contain the following characters: '<>/\ and non-ASCII characters.
                        • Enable skip-name-resolve for the MySQL source database to reduce the possibility of connection timeout.
                        • Enable GTID of the source database.

                        Destination database

                        +

                        Destination database

                        • The destination database is an on-premises MySQL database.
                        • The destination DB instance must have sufficient storage space.
                        • If the destination database (excluding MySQL system database) has the same name as the source database, the table structures in the destination database must be consistent with those in the source database.
                        • The character set of the destination database must be the same as that of the source database.
                        • The time zone of the destination database must be the same as that of the source database.
                        • During a synchronization, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.
                        +
                        • The destination database is an on-premises MySQL database.
                        • The destination DB instance must have sufficient storage space.
                        • If the destination database (excluding MySQL system database) has the same name as the source database, the table structures in the destination database must be consistent with those in the source database.
                        • The character set of the destination database must be the same as that of the source database.
                        • The time zone of the destination database must be the same as that of the source database.
                        • During a synchronization, a large amount of data is written to the destination database. If the value of the max_allowed_packet parameter of the destination database is too small, data cannot be written. You are advised to set the max_allowed_packet parameter to a value greater than 100 MB.

                        Precautions

                        +

                        Precautions

                        • If the data types are incompatible, the synchronization may fail.
                        • If the source database contains a duplicate primary key or unique key, the data synchronized to the destination database will be less than that in the source database. Therefore, you must check and correct the data before starting the synchronization task.
                        • If the destination DB instance is an RDS MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • If the destination MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                          -
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key when the server system breaks down.
                        • When creating a synchronization task, do not set the destination database to read-only.
                        • After a synchronization task is created, you are not allowed to add a schema or modify the association between the old schema and a new RDS DB instance. Otherwise, the synchronization task will fail.
                        • During synchronization, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                        • During the synchronization, do not change the sharding key of a table on the source DDM instance, or change an unsharded or broadcast table to a sharded table, or change a sharded table to an unsharded or broadcast table.
                        • DDL operations are not supported during synchronization.
                        • During an incremental synchronization, do not modify the table structure to be synchronized in the source database.
                        • During an incremental synchronization, do not perform the restoration operation on the source database.
                        +
                        • If the data types are incompatible, the synchronization may fail.
                        • If the source database contains a duplicate primary key or unique key, the data synchronized to the destination database will be less than that in the source database. Therefore, you must check and correct the data before starting the synchronization task.
                        • If the destination DB instance is an RDS for MySQL instance, tables encrypted using Transparent Data Encryption (TDE) cannot be synchronized.
                        • If the destination MySQL database does not support TLS 1.2 or is a self-built database of an earlier version (earlier than 5.6.46 or between 5.7 and 5.7.28), you need to submit an O&M application for testing the SSL connection.
                        • The destination table can contain more columns than the source table. However, the following failures must be avoided:
                          • Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.
                          • Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.
                          +
                        • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key when the server system breaks down.
                        • After a task is created, the destination database cannot be set to read-only.
                        • After a synchronization task is started, you are not allowed to add a schema or modify the association between the old schema and a new RDS DB instance. Otherwise, the synchronization task will fail.
                        • During synchronization, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                        • During the synchronization, do not change the sharding key of a table on the source DDM instance, or change an unsharded or broadcast table to a sharded table, or change a sharded table to an unsharded or broadcast table.
                        • DDL operations are not supported during synchronization.
                        • During an incremental synchronization, do not modify the table structure to be synchronized in the source database.
                        • During an incremental synchronization, do not perform the restoration operation on the source database.
                        +

                        Procedure

                        1. On the Data Synchronization Management page, click Create Synchronization Task.
                        2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                          +

                          + + + + + + + + + + + + + + + + +
                          Table 3 Task and recipient description

                          Parameter

                          +

                          Description

                          +

                          Region

                          +

                          The region where your service is running. You can change the region.

                          +

                          Project

                          +

                          The project corresponds to the current region and can be changed.

                          +

                          Task Name

                          +

                          The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                          +

                          Description

                          +

                          The description can contain up to 256 characters and cannot contain special characters !=<>&'\"

                          +
                          +
                          + +
                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                          Table 4 Synchronization instance details

                          Parameter

                          +

                          Description

                          +

                          Data Flow

                          +

                          Select Out of the cloud.

                          +

                          Source DB Engine

                          +

                          Select DDM.

                          +

                          Destination DB Engine

                          +

                          Select MySQL.

                          +

                          Network Type

                          +

                          The public network is used as an example. Available options: VPC, Public network and VPN or Direct Connect

                          +

                          Destination DB Instance

                          +

                          The RDS instance you created.

                          +

                          Synchronization Instance Subnet

                          +

                          Select the subnet where the synchronization instance is located. You can also click View Subnets to go to the network console to view the subnet where the instance resides.

                          +

                          By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides, and there are available IP addresses for the subnet. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

                          +

                          Synchronization Mode

                          +
                          • Full+Incremental

                            This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

                            +
                          • Full

                            All objects and data in non-system databases are synchronized to the destination database at a time. This mode is applicable to scenarios where service interruption is acceptable.

                            +
                          • Incremental

                            Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                            +
                          +
                          NOTE:

                          If you select Full+Incremental, data generated during the full synchronization will be continuously synchronized to the destination database, and the source remains accessible.

                          +
                          +

                          Source DB Instance Quantity

                          +

                          The default minimum number of source DB instances is 2. You can set this parameter based on the number of source database shards.

                          +
                          NOTE:

                          After a task is created, DRS creates subtasks, whose quantity is the same as the number of source DB instances. Each subtask migrates data from its source database to the destination database.

                          +
                          +

                          Specifications

                          +

                          DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                          +

                          Tags

                          +
                          • Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                          • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                          +
                          +
                          +

                          If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                          +
                          +

                        3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

                          +

                          + + + + + + + + + + + + + +
                          Table 5 Source database information

                          Parameter

                          +

                          Description

                          +

                          DB Instance Name

                          +

                          The DDM instance you selected when you create a synchronization task. The instance name cannot be changed.

                          +

                          Database Username

                          +

                          The username for accessing the source database.

                          +

                          Database Password

                          +

                          The password for the database username.

                          +
                          +
                          +

                          The IP address, domain name, username, and password of the source database are encrypted and stored in DRS, and will be cleared after the task is deleted.

                          +
                          +
                          +
                          + + + + + + + + + + + + + + + + + + + +
                          Table 6 Destination database information

                          Parameter

                          +

                          Description

                          +

                          IP Address or Domain Name

                          +

                          The IP address or domain name of the destination database.

                          +

                          Port

                          +

                          The port of the destination database. Range: 1 - 65535

                          +

                          Database Username

                          +

                          The username for accessing the destination database.

                          +

                          Database Password

                          +

                          The password for the database username.

                          +

                          SSL Connection

                          +

                          SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                          +

                          This parameter is unavailable when the network type is VPC network and the database type is RDS DB instance.

                          +
                          NOTE:
                          • The maximum size of a single certificate file that can be uploaded is 500 KB.
                          • If the SSL certificate is not used, your data may be at risk.
                          +
                          +
                          +
                          +
                          +

                        4. On the Set Synchronization Task page, select the objects to be synchronized, and then click Next.

                          +

                          + + + + + + + +
                          Table 7 Synchronization mode and object

                          Parameter

                          +

                          Description

                          +

                          Synchronization Object

                          +

                          DRS supports table-level synchronization. You can select data for synchronization based on your service requirements. To quickly select the desired database objects, you can use the search function.

                          +
                          NOTE:
                          • You can search for table names to quickly select the required database objects.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          +
                          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                          • The name of the selected synchronization object cannot contain spaces.
                          +
                          +
                          +
                          +

                        5. On the Check Task page, check the synchronization task.

                          • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                          • If all check items are successful, click Next.

                            You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                            +
                            +
                          +

                        6. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Next.

                          +

                          + + + + + + + +
                          Table 8 Task startup settings

                          Parameter

                          +

                          Description

                          +

                          Start Time

                          +

                          Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                          +
                          NOTE:

                          After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

                          +
                          +
                          +
                          +

                        7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                          • You can view the task status. For more information about task status, see Task Statuses.
                          • You can click in the upper-right corner to view the latest task status.
                          • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                          +

                        +
                        diff --git a/docs/drs/umn/drs_04_0464.html b/docs/drs/umn/drs_04_0464.html new file mode 100644 index 000000000..282fc9446 --- /dev/null +++ b/docs/drs/umn/drs_04_0464.html @@ -0,0 +1,285 @@ + + +

                        From DDS to MongoDB

                        +

                        Supported Source and Destination Databases

                        +
                        + + + + + + + +
                        Table 1 Supported databases

                        Source DB

                        +

                        Destination DB

                        +
                        • DDS instances
                        +
                        • On-premises MongoDB databases
                        • MongoDB databases on an ECS
                        • MongoDB database on other clouds
                        +
                        +
                        +
                        +

                        Prerequisites

                        • You have logged in to the DRS console.
                        • For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
                        +
                        +

                        Suggestions

                        • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                        • It is recommended that you start a task during off-peak hours to minimize the impact of synchronization on your services.
                        +
                        +

                        Precautions

                        Before creating a synchronization task, read the following notes:

                        +
                        • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                        • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                        +
                        + +
                        + + + + + + + + + + + + + + + + + + + +
                        Table 2 Precautions

                        Type

                        +

                        Restrictions

                        +

                        Database permissions

                        +

                        Source database (minimum permissions):

                        +
                        • Permission requirements for incremental synchronization:
                          • Replica set: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                          • Single node: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.
                          • Cluster: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the config database.
                          +
                        +

                        Minimum permission requirements: The destination database user must have the dbAdminAnyDatabase permission for the admin database and the readWrite permission for the destination database. If the destination database is a cluster instance, the database user must have the read permission for the config database.

                        +

                        Synchronization object

                        +
                        • Replica set: Only collections (including validator and capped and non-capped collections), indexes, and views can be synchronized.
                        • Cluster: Currently, only collections (including validator and capped and non-capped collections), shard keys, indexes, and views can be synchronized.
                        • Single node: Only collections (including validator and capped collections), indexes, and views can be synchronized.
                        • Collections that contain the _id field without indexes are not supported.
                        • The first parameter of BinData() cannot be 2.
                        • If ranged sharding is used, maxKey cannot be used as the primary key.
                        • If the source database is a cluster database, DBPointer and DBRef are not supported.
                        +

                        Source database

                        +
                        • During the incremental synchronization, the Oplog of the source database must be enabled.
                        • If the storage space is sufficient, store the source database Oplog for as long as possible. The recommended retention period is three days.
                        • The source database name cannot contain /\.$ or spaces. The collection name and view name cannot start with system. or contain the dollar sign ($).
                        +

                        Destination database

                        +
                        • Data cannot be synchronized from a newer version database to an older version database.
                        +
                        • The destination DB instance is running properly.
                        • The destination DB instance must have sufficient storage space.
                        +

                        Precautions

                        +
                        • If the source is not a cluster instance, the following operations and commands are supported during incremental synchronization:
                          • Creating and deleting databases
                          • Adding, deleting, and updating documents
                          • Creating and deleting collections
                          • Creating and deleting indexes
                          • Creating and deleting views
                          • The convertToCapped, collMod, and renameCollection commands are supported.
                          +
                        • If the source is a cluster instance:
                          • The cluster version cannot be earlier than 4.0.
                          • Do not delete synchronization objects in the incremental synchronization phase. Otherwise, the synchronization task will fail.
                          • The synchronization process consumes certain CPU and memory resources of the source database. Evaluate the source database resources in advance.
                          • If the load on the source database is heavy, the processing speed of change streams cannot keep up with the oplog generation speed. As a result, DRS synchronization delay occurs.
                          • Only the following DDLs are supported: drop database, drop collection and rename
                          • In the incremental synchronization phase, the synchronization speed can reach up to 10,000 rows in a single table per second.
                          +
                        +
                        • During startup, the specified start point must be within the Oplog range.
                        • The destination database user must have the write permission. If the destination is a cluster instance, the database user must have the read permission for the config data.
                        • If a Time-to-Live (TTL) index already exists in the collection of the source database or is created during an incremental synchronization, data consistency cannot be ensured when source and destination databases are in different time zone.
                        • The value of block_compressor is determined by stats().wiredTiger.creationString.block_compressor of the collection in the source database. If the destination database contains corresponding empty collections, the compression parameters will not be migrated. If the compression parameters in the source database are not supported by the destination database, configure the compression parameters based on net.compression.compressors of the destination database. If the storage engine of the destination database is not WiredTiger, DRS does not synchronize compression parameters.
                        • If the destination is a replica set instance out of the cloud, enter information about all primary and secondary nodes to reduce the impact of a primary/secondary switchover on the synchronization task. If you enter information about primary and secondary nodes, ensure that all nodes belong to the same replica set instance.
                        • If the destination is a cluster instance out of the cloud, enter information about multiple mongos nodes to reduce the impact of the single-node failure on the synchronization task. In addition, multiple mongos nodes support load balancing. In addition, ensure that all mongos nodes belong to the same cluster instance.
                        • During synchronization, do not modify or delete the usernames, passwords, permissions, or ports of the source and destination databases.
                        • To ensure data consistency, do not modify the destination database (including but not limited to DDL and DML operations) during the entire synchronization process.
                        • During the synchronization, data rollback caused by a primary/standby switchover of the source database is not supported.
                        • The system database cannot be synchronized. The username and role must be manually created in the destination database.
                        • Documents larger than 16 MB in the source database cannot be inserted or updated during incremental synchronization.
                        • In the incremental synchronization phase, concurrent replay is performed at the collection level to maintain the synchronization performance. In the following scenarios, only single-thread write is supported and concurrent replay is not supported:
                          • The collection index contains a unique key.
                          • The value of capped of the collection attribute is true.
                          +

                          In either of the preceding scenarios, the task delay may increase.

                          +
                        • To prevent loopback, the to-the-cloud migration task and out-of-cloud synchronization task cannot be started at the same time.
                        • During row comparison, if an orphan document exists in a cluster instance or chunks are being synchronized, the number of returned rows is incorrect and the comparison results are inconsistent.
                        +
                        +
                        +
                        +

                        Procedure

                        This section uses real-time incremental synchronization from DDS to MongoDB as an example to describe how to configure a real-time synchronization task.

                        +
                        1. On the Data Synchronization Management page, click Create Synchronization Task.
                        2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                          +

                          + + + + + + + + + + + + + + + + +
                          Table 3 Task and recipient description

                          Parameter

                          +

                          Description

                          +

                          Region

                          +

                          The region where the synchronization instance is deployed. You can change the region.

                          +

                          Project

                          +

                          The project corresponds to the current region and can be changed.

                          +

                          Task Name

                          +

                          The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                          +

                          Description

                          +

                          The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

                          +
                          +
                          + +
                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                          Table 4 Synchronization instance settings

                          Parameter

                          +

                          Description

                          +

                          Data Flow

                          +

                          Select Out of the cloud.

                          +

                          Source DB Engine

                          +

                          Select DDS.

                          +

                          Destination DB Engine

                          +

                          Select MongoDB.

                          +

                          Network Type

                          +

                          The Public network is used as an example. Available options: VPC, Public network and VPN or Direct Connect

                          +

                          Source DB Instance

                          +

                          An available DDS instance

                          +

                          Synchronization Instance Subnet

                          +

                          Select the subnet where the synchronization instance is located. You can also click View Subnet to go to the network console to view the subnet where the instance resides.

                          +

                          By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides and ensure that there are available IP addresses. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

                          +

                          Synchronization Mode

                          +
                          • Incremental

                            Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                            +

                            During synchronization, the source database continues to provide services for external systems with zero downtime.

                            +
                          +

                          Specifications

                          +

                          DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                          +

                          Tags

                          +
                          • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                          • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                          +
                          +
                          +

                          If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                          +
                          +

                        3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, click Next.

                          +

                          + + + + + + + + + + + + + +
                          Table 5 Source database settings

                          Parameter

                          +

                          Description

                          +

                          DB Instance Name

                          +

                          The DDS instance that you selected when creating the replication instance and cannot be changed.

                          +

                          Database Username

                          +

                          The username for accessing the source database.

                          +

                          Database Password

                          +

                          The password for the database username.

                          +
                          +
                          +

                          The IP address, port, username, and password of the source database are encrypted and stored in the database and the synchronization instance, and will be cleared after the task is deleted.

                          +
                          + +
                          + + + + + + + + + + + + + + + + + + + +
                          Table 6 Destination database settings

                          Parameter

                          +

                          Description

                          +

                          IP Address or Domain Name

                          +

                          IP address or domain name of the destination database in the IP address/Domain name:Port format. The port of the destination database. Range: 1 - 65535

                          +

                          You can enter up to 3 groups of IP addresses or domain names of the source database. Separate multiple values with commas (,). For example: 192.168.0.1:8080,192.168.0.2:8080. Ensure that the entered IP addresses or domain names belong to the same instance.

                          +
                          NOTE:

                          If multiple IP addresses or domain names are entered, the test connection is successful as long as one IP address or domain name is accessible. Therefore, you must ensure that the IP address or domain name is correct.

                          +
                          +

                          Authentication Database

                          +

                          The name of the destination database.

                          +

                          Database Username

                          +

                          The username for accessing the destination database.

                          +

                          Database Password

                          +

                          The password for the database username.

                          +

                          SSL Connection

                          +

                          SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                          +
                          NOTE:
                          • The maximum size of a single certificate file that can be uploaded is 500 KB.
                          • If the SSL certificate is not used, your data may be at risk.
                          +
                          +
                          +
                          +

                          The username and password of the destination database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                          +
                          +

                        4. On the Set Task page, select the start point and synchronization objects, and click Next.

                          +

                          + + + + + + + + + + +
                          Table 7 Synchronization Object

                          Parameter

                          +

                          Description

                          +

                          Start Point

                          +

                          The start time of incremental synchronization. The value is in the format of timestamp:incre. timestamp is the Unix timestamp (unit: second), and incre is the command execution sequence in a second. A synchronization task obtains incremental logs of the source database from the start position (including the current start position).

                          +
                          • Run db.getSiblingDB("local").oplog.rs.find() to query the source database oplog. The format of the ts field is timestamp:incre.
                          • A cluster cannot query the oplog from mongos. timestamp can be converted into the Unix timestamp format based on the start time. The value of incre is 1.
                          +

                          Synchronization Object

                          +

                          DRS supports database- and table-level synchronization. You can select data for synchronization based on your service requirements.

                          +
                          NOTE:
                          • You can search for table names to quickly select the required database objects.
                          • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                          +
                          • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                          • The name of the selected synchronization object cannot contain spaces.
                          +
                          +
                          +
                          +

                        5. On the Check Task page, check the synchronization task.

                          • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                          • If all check items are successful, click Next.

                            You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                            +
                            +
                          +

                        6. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                          +

                          + + + + + + + +
                          Table 8 Task startup settings

                          Parameter

                          +

                          Description

                          +

                          Started Time

                          +

                          Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                          +
                          NOTE:

                          After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

                          +
                          +
                          +
                          +

                        7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                          • You can view the task status. For more information about task status, see Task Statuses.
                          • You can click in the upper-right corner to view the latest task status.
                          • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                          +

                        +
                        +
                        +
                        +
                        +
                        Parent topic: Out of the Cloud
                        +
                        +
                        + diff --git a/docs/drs/umn/drs_04_0465.html b/docs/drs/umn/drs_04_0465.html index 45ccabb37..97656fc74 100644 --- a/docs/drs/umn/drs_04_0465.html +++ b/docs/drs/umn/drs_04_0465.html @@ -136,14 +136,6 @@

                        By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides and ensure that there are available IP addresses. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

                        Synchronization Mode

                        -
                        • Full+Incremental

                          This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

                          -
                        -
                        NOTE:

                        If you select Full+Incremental, data generated during the full synchronization will be continuously synchronized to the destination database, and the source remains accessible.

                        -
                        -

                        Source DB Instance Quantity

                        Specifies the number of DB instances bound to the source DDM database. The default value is 2. The value ranges from 1 to 64. Set this parameter based on the site requirements.

                        @@ -155,16 +147,31 @@
                        -
                        • Tags -
                          Table 5 Tags

                          Parameter

                          +
                          • DRS instance specifications +
                            - - - + + +
                            Table 5 Specifications

                            Parameter

                            Description

                            +

                            Description

                            Tags

                            +

                            Specifications

                            • Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                            • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                            +

                            DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                            +
                            +
                            +
                          • Tags +
                            + + + + + @@ -174,7 +181,7 @@

                            If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                          • On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

                            -

                            • Table 6 Tags

                            Parameter

                            +

                            Description

                            +

                            Tags

                            +
                            • Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                            • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                            Table 6 Source database settings

                            Parameter

                            +
                            @@ -218,7 +225,7 @@

                            The IP address, domain name, username, and password of the source database are encrypted and stored in DRS, and will be cleared after the task is deleted.

                            -
                            Table 7 Source database settings

                            Parameter

                            Description
                            Table 7 Destination database settings

                            Parameter

                            +
                            @@ -244,7 +251,7 @@

                          • On the Set Synchronization Task page, select the objects to be synchronized, and then click Next.

                            -

                            • Table 8 Destination database settings

                            Parameter

                            Description
                            Table 8 Synchronization mode and object

                            Parameter

                            +
                            @@ -258,8 +265,8 @@ @@ -270,8 +277,8 @@

                          • On the Check Task page, check the synchronization task.

                            • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                            • If all check items are successful, click Next.

                              You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                            -

                          • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                            -

                            • Table 9 Synchronization mode and object

                            Parameter

                            Description

                            Synchronization Object

                            Select Tables, Databases, or Import object file as required.

                            -

                            If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

                            -
                            NOTE:
                            • To quickly select the desired database objects, you can use the search function.
                            • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                            +

                            If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                            +
                            NOTE:
                            • You can search for table names to quickly select the required database objects.
                            • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                            • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                            • The name of the selected synchronization object cannot contain spaces.
                            Table 9 Task startup settings

                            Parameter

                            +

                          • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                            +

                            @@ -287,7 +294,7 @@
                            Table 10 Task startup settings

                            Parameter

                            Description
                            -

                          • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                            • You can view the task status. For more information about task status, see Task Statuses.
                            • You can click in the upper-right corner to view the latest task status.
                            +

                          • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                            • You can view the task status. For more information about task status, see Task Statuses.
                            • You can click in the upper-right corner to view the latest task status.
                            • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                            • diff --git a/docs/drs/umn/drs_04_0508.html b/docs/drs/umn/drs_04_0508.html new file mode 100644 index 000000000..5fe23703b --- /dev/null +++ b/docs/drs/umn/drs_04_0508.html @@ -0,0 +1,428 @@ + + +

                            From PostgreSQL to PostgreSQL

                            +

                            Supported Source and Destination Databases

                            +
                            + + + + + + + +
                            Table 1 Supported databases

                            Source DB

                            +

                            Destination DB

                            +

                            RDS for PostgreSQL (versions 9.5, 9.6, 10, 11, 12, 13, 14, 15 and 16)

                            +
                            • On-premises databases (PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15 and 16)
                            • ECS-hosted databases (PostgreSQL 9.5, 9.6, 10, 11, 12, 13, 14, 15 and 16)
                            +
                            NOTE:

                            The major version of the destination database must be the same as or later than that of the source database.

                            +
                            +
                            +
                            +
                            +

                            Supported Synchronization Objects

                            Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

                            + +
                            + + + + + + + +
                            Table 2 Supported synchronization objects

                            Type

                            +

                            Notes

                            +

                            Objects

                            +
                            • Instance-level synchronization is not supported. Only one database can be synchronized at a time. Multiple DRS tasks are required to synchronize multiple databases.
                            • Supported field types:

                              Digit, currency, character, binary, date/time, boolean, enumeration, geometry, network address, bit, text search, UUID, XML, JSON, array, compound, and range.

                              +
                            • Scope of full synchronization
                              • The following objects are supported in the database-level synchronization: schemas, tables, indexes, constraints, views, materialized views, sequences, stored procedures, rules, triggers, foreign keys, sorting rules, plug-ins, code conversion information, aggregate functions, operators, statistics extension, conversion information, text search configurations, functions, data types, type conversion, event triggers, text search parsers, and text search templates

                                During the table-level synchronization, only tables, views, materialized views, sequences, and common indexes can be synchronized.

                                +
                              • System objects such as system schemas, system tables, system users, and system functions cannot be synchronized. Other objects such as tablespaces, foreign data wrappers, foreign servers, user mappings, releases, subscriptions, and users cannot be synchronized. Object permissions cannot be synchronized.
                              +
                              NOTE:

                              The restrictions on the objects that can be synchronized are as follows:

                              +
                              • Object name: The database name cannot contain +"%'\<>, the schema name and table name cannot contain ".'<>, and the column name cannot contain double quotation marks (") and single quotation marks (').
                              • Table: Temporary tables are not synchronized. During table-level synchronization, table constraints, indexes, and rules are synchronized, except for table triggers.
                              • Function: Do not synchronize C language functions or functions with the leakproof or support attribute.
                              • Plug-in: The metadata of plug-ins is not synchronized.
                              • Data type: Basic data types are not synchronized.
                              • Type conversion: The binary coercion type cannot be converted.
                              +
                              +
                            • Scope of incremental synchronization
                              • Some DML statements, including INSERT, UPDATE, and DELETE, can be synchronized.
                              • Some DDL statements can be synchronized, including TRUNCATE (only for PostgreSQL 11 or later), CREATE SCHEMA, CREATE TABLE, DROP TABLE, ALTER TABLE (including ADD COLUMN, DROP COLUMN, ALTER COLUMN, RENAME COLUMN, ADD CONSTRAINT, DROP CONSTRAINT and RENAME), CREATE SEQUENCE, DROP SEQUENCE, ALTER SEQUENCE, CREATE INDEX, ALTER INDEX, DROP INDEX, CREATE VIEW, ALTER VIEW, COMMENT ON COLUMN, COMMENT ON TABLE, COMMENT ON SCHEMA, COMMENT ON SEQUENCE, COMMENT ON INDEX, and COMMENT ON VIEW.

                                During table-level synchronization, only the following DDL operations can be synchronized: TRUNCATE (only for PostgreSQL 11 or later), DROP TABLE, COMMENT ON COLUMN, COMMENT ON TABLE, and ALTER TABLE (including ADD COLUMN, DROP COLUMN, ALTER COLUMN, RENAME COLUMN, ADD CONSTRAINT, DROP CONSTRAINT and RENAME).

                                +
                              • Not synchronized: DML statements of unlogged tables and temporary tables
                              +
                              NOTE:
                              • The source database captures DDL statements using event triggers and records them in specific tables, so you need to create event triggers and functions in the source database in advance. For details, see Creating Triggers and Functions to Implement Incremental DDL Synchronization for PostgreSQL.
                              • Incremental heartbeat information sending: For PostgreSQL 9.6 and later versions, if no data is written to the source database for a long time (more than 10 hours), the log extraction process invokes pg_logical_emit_message to insert heartbeat information into WAL logs of the source database, which ensures that the logical replication slot number is updated normally. (Only WAL logs are added, and services are not affected.)
                              +
                              +
                            +
                            +
                            +
                            +

                            Database Account Permission Requirements

                            To start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                            +
                            • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                            • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                            +
                            + +
                            + + + + + + + + + + + + +
                            Table 3 Database account permission

                            Type

                            +

                            Full

                            +

                            Full+Incremental

                            +

                            Source database user

                            +

                            Database CONNECT permission, schema USAGE permission, table SELECT permission, and sequence SELECT permission

                            +

                            The CONNECT permission for databases, the USAGE permission for schemas, the SELECT permission for tables, the SELECT permissions for sequences, the UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys, and the permission to create replication connections

                            +
                            NOTE:

                            The UPDATE, DELETE, and TRUNCATE permissions for tables that do not have primary keys are only used to temporarily lock tables to ensure data consistency after the migration.

                            +
                            +

                            Destination database user

                            +
                            • Database-level:
                              • If the destination database is not postgres, the CREATEDB permission is required.
                              • If the destination database is postgres, the CONNECT and CREATE permissions on the postgres database and the USAGE and CREATE permissions on public schemas are required.
                              +
                            • Table-level:
                              • To synchronize databases, the CREATEDB permission is required.
                              • To synchronize a schema, the CONNECT and CREATE permissions for the database that contains the schema are required.
                              • To synchronize objects in a schema, the CONNECT permission for the database that contains the schema, and the USAGE and CREATE permissions for the schema that contain the object are required.
                                NOTE:

                                If the destination database version is PostgreSQL 15 and no database is created on the destination database for database-level synchronization and table-level synchronization, full or incremental synchronization may fail due to lack of the USAGE and CREATE permissions of the public schema.

                                +
                                +
                              +
                            +
                            +
                            +
                            +

                            Suggestions

                            • When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                            • To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
                            +
                            +
                            • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                            • You are advised to start your synchronization task during off-peak hours by setting Start Time to Start at a specified time. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization.
                              • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
                              • To ensure data consistency, tables to be synchronized without a primary key may be locked for 3s.
                              • The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
                              • When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
                              • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
                              +
                            • Data-Level Comparison

                              To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

                              +
                            +
                            +

                            Precautions

                            The full+incremental synchronization process consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. (A single incremental synchronization task or a single full synchronization task contains three phases.) To ensure smooth synchronization, read the following notes before creating a synchronization task.

                            + +
                            + + + + + + + + + + + + + + + + + + + +
                            Table 4 Precautions

                            Type

                            +

                            Constraints

                            +

                            Starting a task

                            +
                            • Source database parameter requirements:
                              • The partition table trigger of the source database cannot be set to disable.
                              • For a full synchronization task, the source database can be a standby database, but hot_standby_feedback must be set to on. For an incremental synchronization task, the source database cannot be a standby database.
                              • To perform incremental synchronization:

                                The wal_level value of the source database must be logical.

                                +

                                The replica identity attribute of tables that do not have primary keys in the source database must be full.

                                +

                                The max_replication_slots value of the source database must be greater than the number of used replication slots.

                                +

                                The max_wal_senders value of the source database must be greater than or equal to the max_replication_slots value.

                                +

                                If the toast attribute of the primary key column in the source database is main, external, or extended, the replica identity attribute must be full.

                                +
                              +
                            • Source database object requirements:
                              • Triggers with the same name cannot exist in the source database.
                              • The objects that have dependencies must be synchronized at the same time. Otherwise, the synchronization may fail.
                              +
                            • Destination database parameter requirements:
                              • The block_size value of the destination database must be greater than or equal to that of the source database.
                              • The lc_monetary values of the source and destination databases must be the same.
                              • To perform incremental synchronization, if the synchronization object contains foreign keys, triggers, or event triggers, set session_replication_role of the destination database to replica. After the synchronization is complete, change the value to the original one.
                              +
                            • Destination database object requirements:
                              • The destination database cannot contain objects with the same type and name as the objects to be synchronized, including databases, schemas, and tables. System databases, system schemas, and system tables are excluded.
                              • The destination table can contain more columns than the source table. However, the following failures must be avoided:

                                Assume that extra columns on the destination cannot be null or have default values. If newly inserted data records are synchronized from the source to the destination, the extra columns will become null, which does not meet the requirements of the destination and will cause the task to fail.

                                +

                                Assume that extra columns on the destination must be fixed at a default value and have a unique constraint. If newly inserted data records are synchronized from the source to the destination, the extra columns will contain multiple default values. That does not meet the unique constraint of the destination and will cause the task to fail.

                                +
                              • Before full synchronization, ensure that there is no data in the destination database table. Otherwise, data may be inconsistent or the task may fail.
                              • If retry upon failure or resumable transfer occurs during full synchronization, the truncate command is executed to clear data in tables without primary keys in the destination database that have not been synchronized, and then the tables are synchronized again. Before full synchronization, ensure that the synchronization user has the TRUNCATE permission on the tables without primary keys in the destination database. Otherwise, the task may fail.
                              +
                            • Other notes:
                              • When a schema name or table name is mapped, to prevent conflicts between indexes and constraint names, the original index name in the table is changed to the following format after synchronization: i_+hash value+original index name (which may be truncated)+_key The hash value is calculated based on the original schema name_original table name_original index name. Similarly, the original constraint name on the table is changed to c_ + hash value + original constraint name (which may be truncated) + _key.
                              • Before starting a full+incremental or incremental synchronization task, ensure that no long transaction is started in the source database. Starting the long transaction will block the creation of the logical replication slot and cause the task to fail.
                              • For a full+incremental or incremental synchronization task, if an internal error occurs during the pre-check and the task stops before it is started, check and delete the streaming replication slot by referring to Forcibly Stopping Synchronization of PostgreSQL to avoid residual streaming replication slots in the source database.
                              • After a full+incremental or incremental task is started, a primary/standby switchover can be performed only on the source database of the following versions: RDS for PostgreSQL 12.6 or later and RDS for PostgreSQL 13 or later.
                              • By default, the PostgreSQL-to-PostgreSQL synchronization task does not support loopback or cascading synchronization. That is, data cannot be synchronized from instance A to instance B and then from instance B to instance C.
                              • If you choose to synchronize DDL statements, ensure that the DDL statements executed on the source database are compatible with the destination database.
                                NOTE:

                                DDL statements are captured using event triggers in the source database, recorded in a specific table, and then synchronized to the destination database. You need to create event triggers and functions in the source database before starting a task. For details, see Creating Triggers and Functions to Implement Incremental DDL Synchronization for PostgreSQL.

                                +
                                +
                              +
                            +

                            Full synchronization

                            +
                            • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                            • Do not run any DDL statement in the source database. Otherwise, data may be inconsistent or the task may fail.
                            • Do not write data to the destination database. Otherwise, data may be inconsistent.
                            • To ensure normal synchronization and data consistency, you are advised to create a DRS task again during off-peak hours to meet the preceding requirements.
                            +

                            Incremental synchronization

                            +
                            • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                            • Do not change the primary key or unique key (if the primary key does not exist) of the source database table. Otherwise, incremental data may be inconsistent or the task may fail.
                            • Do not modify the replica identity attribute of tables in the source database. Otherwise, incremental data may be inconsistent or the task may fail.
                            • Do not write data to the destination database. Otherwise, data may be inconsistent.
                            • To ensure normal synchronization and data consistency, you are advised to create a DRS task again during off-peak hours to meet the preceding requirements.
                            • During database-level synchronization, if a table without a primary key is added to the source database, you must set replica identity of the table to full before writing data. Otherwise, data may be inconsistent or the task may fail.
                            • During database-level synchronization, if a primary key table is added to the source database and the toast attribute of the primary key column is main, external, or extended, the replica identity attribute of the table must be set to full before writing data. Otherwise, data may be inconsistent or the task may fail.
                            +

                            Synchronization comparison

                            +
                            • You are advised to compare data in the source database during off-peak hours to prevent inconsistent data from being falsely reported and reduce the impact on the source database and DRS tasks.
                            • During incremental synchronization, if data is written to the source database, the comparison results may be inconsistent.
                            • Data cannot be compared during full synchronization.
                            • Do not limit the synchronization speed during data comparison.
                            +

                            Stopping a task

                            +
                            • Stop a task normally:
                              • The destination database sequence value is automatically reset. The auto-increment sequence value is the source database sequence value plus the security margin, and the auto-decrement sequence value is the source database sequence value minus the security margin. The default security margin is 10,000. If users are synchronized, the user memberships are automatically synchronized after the task is complete.
                              • When a full+incremental synchronization task is complete, the streaming replication slot created by the task in the source database is automatically deleted.
                              • If the value of destination database session_replication_role is replica when the full+incremental synchronization task is complete, change the value to origin.
                              +
                            +
                            • Forcibly stop a task:
                              • You need to manually update the sequence value in the destination database. For details, see Forcibly Stopping Synchronization of PostgreSQL.
                              • To forcibly stop a full+incremental real-time synchronization task, you need to manually delete the replication slots that may remain in the source database. For details, see Forcibly Stopping Synchronization of PostgreSQL.
                              • If the value of destination database session_replication_role is replica, change it to origin to forcibly stop the full+incremental synchronization task.
                              +
                            +
                            +
                            +
                            +

                            Procedure

                            This section uses out-of-cloud synchronization from PostgreSQL to PostgreSQL as an example to describe how to configure a real-time synchronization task in the VPC network scenario.

                            +
                            1. On the Data Synchronization Management page, click Create Synchronization Task.
                            2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Create Now.

                              • Task information description +
                                + + + + + + + + + + + + + + + + +
                                Table 5 Task information

                                Parameter

                                +

                                Description

                                +

                                Region

                                +

                                The region where the replication instance is deployed. You can change the region.

                                +

                                Project

                                +

                                The project corresponds to the current region and can be changed.

                                +

                                Task Name

                                +

                                The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                                +

                                Description

                                +

                                The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

                                +
                                +
                                +
                              • Synchronization instance details +
                                + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 6 Synchronization instance settings

                                Parameter

                                +

                                Description

                                +

                                Data Flow

                                +

                                Select Out of the cloud.

                                +

                                Source DB Engine

                                +

                                Select PostgreSQL.

                                +

                                Destination DB Engine

                                +

                                Select PostgreSQL.

                                +

                                Network Type

                                +

                                Available options: VPC, Public network, and VPN or Direct Connect. VPC is used as an example.

                                +
                                • VPC is suitable for data synchronization between cloud databases of the same account in the same region and VPC.
                                • Public network is suitable for data synchronization from on-premises or external cloud databases to the destination databases bound with an EIP.
                                • VPN or Direct Connect is suitable for data synchronization from on-premises databases to cloud databases, between databases of different accounts in the same region on the cloud, or between databases across regions on the cloud using a VPN, Direct Connect, Cloud Connect, VPCEP, or a VPC peering connection.
                                +

                                Source DB Instance

                                +

                                The RDS for PostgreSQL DB instance.

                                +

                                Synchronization Instance Subnet

                                +

                                Select the subnet where the synchronization instance is located. You can also click View Subnets to go to the network console to view the subnet where the instance resides.

                                +

                                By default, the DRS instance and the destination DB instance are in the same subnet. You need to select the subnet where the DRS instance resides, and there are available IP addresses for the subnet. To ensure that the synchronization instance is successfully created, only subnets with DHCP enabled are displayed.

                                +

                                Synchronization Mode

                                +
                                • Full+Incremental

                                  This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

                                  +
                                • Full

                                  All objects and data in non-system databases are synchronized to the destination database at a time. This mode is applicable to scenarios where service interruption is acceptable.

                                  +
                                • Incremental

                                  Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                                  +
                                +

                                Specify EIP

                                +

                                This parameter is available when you select Public network for Network Type. Select an EIP to be bound to the DRS instance. DRS will automatically bind the specified EIP to the DRS instance and unbind the EIP after the task is complete. The number of specified EIPs must be the consistent with that of DB instances.

                                +
                                +
                                +
                              • DRS instance specifications +
                                + + + + + + + +
                                Table 7 Specifications

                                Parameter

                                +

                                Description

                                +

                                Specifications

                                +

                                DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                                +
                                +
                                +
                              • Tags

                                + +
                                + + + + + + + +
                                Table 8 Tags

                                Parameter

                                +

                                Description

                                +

                                Tags

                                +
                                • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                                • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                                +
                                +
                                +
                              +

                              If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically stops.

                              +
                              +

                            3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

                              Establish the connectivity between the DRS instance and the source and destination databases.

                              +
                              • Source database configuration +
                                + + + + + + + + + + + + + +
                                Table 9 Source database settings

                                Parameter

                                +

                                Description

                                +

                                DB Instance Name

                                +

                                The RDS for PostgreSQL instance you selected when creating the task. The parameter cannot be changed.

                                +

                                Database Username

                                +

                                The username for accessing the source database.

                                +

                                Database Password

                                +

                                The password for the database username.

                                +
                                +
                                +
                              • Destination database configuration +
                                + + + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 10 Destination database settings

                                Parameter

                                +

                                Description

                                +

                                VPC

                                +

                                A dedicated virtual network in which the destination database is located. It isolates networks for different services. You can select an existing VPC or create a VPC.

                                +

                                Subnet

                                +

                                A subnet provides dedicated network resources that are isolated from other networks, improving network security. The subnet must be in the AZ where the destination database resides. You need to enable DHCP for creating the destination database subnet.

                                +

                                IP Address or Domain Name

                                +

                                The IP address or domain name of the destination database.

                                +

                                Port

                                +

                                The port of the destination database. Range: 1 - 65535

                                +

                                Database Username

                                +

                                The username for accessing the destination database.

                                +

                                Database Password

                                +

                                The password for the database username.

                                +

                                SSL Connection

                                +

                                SSL encrypts the connections between the source and destination databases.

                                +
                                +
                                +
                              +

                              The username and password of the source and destination databases are encrypted and stored in the databases and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                              +
                              +

                            4. On the Set Synchronization Task page, select the synchronization policy and synchronization object, and click Next.

                              +

                              + + + + + + + + + + + + + + + + + + + + + + +
                              Table 11 Synchronization Object

                              Parameter

                              +

                              Description

                              +

                              Flow Control

                              +

                              You can choose whether to control the flow.

                              +
                              • Yes

                                You can customize the maximum migration speed.

                                +

                                In addition, you can set the time range based on your service requirements. The traffic rate setting usually includes setting of a rate limiting time period and a traffic rate value. Flow can be controlled all day or during specific time ranges. The default value is All day. A maximum of three time ranges can be set, and they cannot overlap.

                                +

                                The flow rate must be set based on the service scenario and cannot exceed 9,999 MB/s.

                                +
                              • No
                                The synchronization speed is not limited and the outbound bandwidth of the source database is maximally used, which will increase the read burden on the source database. For example, if the outbound bandwidth of the source database is 100 MB/s and 80% bandwidth is used, the I/O consumption on the source database is 80 MB/s.
                                NOTE:
                                • The flow control mode takes effect only in the full synchronization phase.
                                • You can also change the flow control mode after creating a task. For details, see Modifying the Flow Control Mode.
                                +
                                +
                                +
                              +

                              Incremental Conflict Policy

                              +

                              The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored. Select any of the following conflict policies:

                              +
                              • Ignore

                                The system will skip the conflicting data and continue the subsequent synchronization process. If you select Ignore, data in the source database may be inconsistent with that in the destination database.

                                +
                              • Report error

                                The synchronization task will be stopped and fail.

                                +
                              • Overwrite

                                Conflicting data will be overwritten.

                                +
                              +

                              If the synchronized data conflicts with the existing data in the destination database, selecting Ignore cannot ensure data consistency. To ensure data consistency, select Overwrite.

                              +

                              Synchronize

                              +

                              Available options: Normal index, Incremental DDLs, and Populate materialized views during the full synchronization phase

                              +

                              Populate materialized views during the full synchronization phase: This option takes effect only for materialized views that was populated in the source database. This operation affects the full synchronization performance. You perform this operation after the full synchronization is complete.

                              +

                              Synchronize DML

                              +

                              Select the DML operations to be synchronized. By default, all DML operations are selected.

                              +

                              If you do not select Delete, DELETE statements in the incremental data of the source database will not be synchronized, which may cause a data inconsistency. As a result, there may be a data conflict or the task may fail.

                              +

                              Source Database Replication Slot Name

                              +

                              You can choose whether to specify the replication slot of the source database. This parameter is available for incremental tasks. After replication slot is enabled, enter the replication slot name. The name can contain a maximum of 63 characters and cannot start with a digit. Only lowercase letters, digits, and underscores (_) are allowed.

                              +

                              Synchronization Object

                              +

                              The left pane displays the source database objects, and the right pane displays the selected objects. You can select Tables or Databases for Synchronization Object as required.

                              +
                              • Database-level synchronization: In full synchronization, the selected databases and the inventory data of the database objects are synchronized. In incremental synchronization, the DML and some DDL statements of all tables except unlogged tables and temporary tables are synchronized.
                              +
                              • Table-level synchronization: In full synchronization, the inventory data of the selected tables, sequences, views, or materialized views is synchronized. In incremental synchronization, the DML and some DDL statements of the selected tables are synchronized.
                              +
                              • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                                When a schema name or table name is mapped, to prevent conflicts between indexes and constraint names, the original index name in the table is changed to the following format after synchronization: i_+hash value+original index name (which may be truncated)+_key The hash value is calculated based on the original schema name_original table name_original index name. Similarly, after the synchronization, the original constraint name on the table is changed to c_ + hash value + original constraint name (which may be truncated) + _key.

                                +
                              +
                              NOTE:
                              • To quickly select the desired database objects, you can use the search function.
                              • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                              +
                              • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                              • The name of the selected synchronization object cannot contain spaces.
                              +
                              +
                              +
                              +

                            5. On the Check Task page, check the synchronization task.

                              • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                              • If all check items are successful, click Next.

                                You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                                +
                                +
                              +

                            6. On the displayed page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                              + +
                              + + + + + + + +
                              Table 12 Task startup settings

                              Parameter

                              +

                              Description

                              +

                              Start Time

                              +

                              Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                              +
                              NOTE:

                              After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

                              +
                              +
                              +
                              +

                            7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                              • You can view the task status. For more information about task status, see Task Statuses.
                              • You can click in the upper-right corner to view the latest task status.
                              • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                              +

                            +
                            +
                            +
                            +
                            +
                            Parent topic: Out of the Cloud
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_05_0006.html b/docs/drs/umn/drs_05_0006.html index 174d9fecc..2031a492d 100644 --- a/docs/drs/umn/drs_05_0006.html +++ b/docs/drs/umn/drs_05_0006.html @@ -20,6 +20,12 @@
                          • Resetting a Synchronization Task
                            • +
                          • Restarting a Synchronization Task
                            +
                            • +
                          • Changing a Single-AZ Task to a Dual-AZ Task
                            +
                            • +
                          • Cloning a Synchronization Task
                            +
                          • Stopping a Synchronization Task
                          • Deleting a Synchronization Task
                            diff --git a/docs/drs/umn/drs_05_0007.html b/docs/drs/umn/drs_05_0007.html index 5e22bf2db..c88aea3b0 100644 --- a/docs/drs/umn/drs_05_0007.html +++ b/docs/drs/umn/drs_05_0007.html @@ -12,7 +12,7 @@
                          • Importing Synchronization Objects
                            • -
                          • Mapping Object Names
                            +
                          • Changing Object Names (Mapping Object Names)
                          • Viewing Synchronization Mapping Information
                            • diff --git a/docs/drs/umn/drs_05_0011.html b/docs/drs/umn/drs_05_0011.html new file mode 100644 index 000000000..3e540ed28 --- /dev/null +++ b/docs/drs/umn/drs_05_0011.html @@ -0,0 +1,19 @@ + + +

                            Interconnecting with Cloud Eye

                            +
                            + + diff --git a/docs/drs/umn/drs_05_0012.html b/docs/drs/umn/drs_05_0012.html new file mode 100644 index 000000000..0fd185bfa --- /dev/null +++ b/docs/drs/umn/drs_05_0012.html @@ -0,0 +1,319 @@ + + +

                            Supported Metrics

                            +

                            Description

                            This section describes metrics reported by the Data Replication Service (DRS) to Cloud Eye as well as their namespaces and dimensions. You can use APIs provided by Cloud Eye to query the metrics of the monitored object and alarms generated for DRS.

                            +
                            +

                            Namespace

                            SYS.DRS

                            +
                            +

                            DB Instance Monitoring Metrics

                            Table 1 lists the DRS performance metrics. +
                            + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                            Table 1 DRS metrics

                            Metric ID

                            +

                            Metrics Name

                            +

                            Description

                            +

                            Value Range

                            +

                            Monitored Object

                            +

                            Monitoring Interval (Raw Data)

                            +

                            cpu_util

                            +

                            CPU Usage

                            +

                            CPU usage of the monitored object

                            +

                            0-100%

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            mem_util

                            +

                            Memory Usage

                            +

                            Memory usage of the monitored object

                            +

                            0-100%

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            network_incoming_bytes_rate

                            +

                            Network Input Throughput

                            +

                            Incoming traffic in bytes per second

                            +

                            ≥ 0 bytes/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            network_outgoing_bytes_rate

                            +

                            Network Output Throughput

                            +

                            Outgoing traffic in bytes per second

                            +

                            ≥ 0 bytes/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            disk_read_bytes_rate

                            +

                            Disk Read Throughput

                            +

                            Number of bytes read from the disk per second (bytes/second).

                            +

                            ≥ 0 bytes/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            disk_write_bytes_rate

                            +

                            Disk Write Throughput

                            +

                            Number of bytes written to the disk per second (bytes/second).

                            +

                            ≥ 0 bytes/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            disk_util

                            +

                            Storage Space Usage

                            +

                            Storage space usage of the monitored object

                            +

                            0-100%

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            extract_bytes_rate

                            +

                            Source Database Read Throughput

                            +

                            Table data or WAL bytes read from the source database per second

                            +

                            ≥ 0 bytes/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            extract_rows_rate

                            +

                            Rows Read from Source Database per Second

                            +

                            Number of table data rows or WAL rows read from the source database per second Unit: rows/s.

                            +

                            ≥ 0 row/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            extract_latency

                            +

                            Source Database WAL Extract Lag

                            +

                            Latency of extracting WAL from the source database Unit: ms.

                            +

                            ≥ms

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_bytes_rate

                            +

                            Destination Database Write Throughput

                            +

                            Number of bytes written to the destination database per second.

                            +

                            ≥ 0 bytes/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_rows_rate

                            +

                            Rows Written into Destination Database per Second

                            +

                            Number of rows that are written to the destination database per second Unit: rows/s.

                            +

                            ≥ 0 row/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_transactions_rate

                            +

                            DML TPS

                            +

                            Number of DML transactions written to the destination database per second.

                            +

                            ≥ 0 transaction/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_ddls_rate

                            +

                            DDL TPS

                            +

                            Number of DDLs written to the destination database per second.

                            +

                            ≥ 0 transaction/s

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_latency

                            +

                            Replication Delay

                            +

                            Delay (in milliseconds) of data replay.

                            +

                            ≥ 0 ms

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_average_execute_time

                            +

                            Average Transaction Execution Time

                            +

                            Average execution time (RT = Execution time + Commit time) of a transaction in the destination database. The unit is millisecond.

                            +

                            ≥ 0 ms

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_average_commit_time

                            +

                            Average Transaction Commit Time

                            +

                            Average commit time (RT = Execution time + Commit time) of a transaction in the destination database. The unit is ms.

                            +

                            ≥ 0 ms

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_current_state

                            +

                            Synchronization Status

                            +

                            This metric is the synchronization status of the current kernel data (10: abnormal; 1: idle; 2: DML; 3: DDL), instead of the task status.

                            +

                            10: abnormal

                            +

                            1: idle

                            +

                            2: DML is executed.

                            +

                            3: DDL is executed.

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +

                            apply_thread_workers

                            +

                            Synchronization Threads

                            +

                            Number of working threads for data synchronization

                            +

                            ≥ 0

                            +

                            Monitored object: ECS

                            +

                            Monitored instance type: replication, synchronization, and DR instances

                            +

                            1 minute

                            +
                            +
                            +
                            +
                            +

                            Dimensions

                            +
                            + + + + + + + +

                            Key

                            +

                            Value

                            +

                            instance_id

                            +

                            DRS instance ID

                            +
                            +
                            +
                            +
                            +
                            +
                            +
                            Parent topic: Interconnecting with Cloud Eye
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_05_0013.html b/docs/drs/umn/drs_05_0013.html new file mode 100644 index 000000000..595da07d1 --- /dev/null +++ b/docs/drs/umn/drs_05_0013.html @@ -0,0 +1,16 @@ + + +

                            Configuring Alarm Rules

                            +

                            Scenarios

                            You can configure DRS alarm rules to customize the monitored objects and notification policies and learn the DRS running status in a timely manner.

                            +

                            This section describes how to set DRS alarm rules, including the alarm rule name, service, dimension, monitoring scope, template, and whether to send a notification.

                            +
                            +

                            Procedure

                            1. Log in to the management console.
                            2. Under Management & Deployment, click 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: Interconnecting with Cloud Eye
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_05_0014.html b/docs/drs/umn/drs_05_0014.html new file mode 100644 index 000000000..2bd6db594 --- /dev/null +++ b/docs/drs/umn/drs_05_0014.html @@ -0,0 +1,19 @@ + + +

                            Viewing Monitoring Metrics

                            +

                            Scenarios

                            Cloud Eye monitors the running statuses of replication, synchronization, and DR instances. You can obtain the monitoring metrics on the management console. Monitored data requires a period of time for transmission and display. The status of the monitored object displayed on the Cloud Eye page is the status obtained 5 to 10 minutes before. You can view the monitored data of a newly created DB instance 5 to 10 minutes later.

                            +
                            +

                            Prerequisites

                            An instance is running properly when it is in the following statuses:
                            • Real-time migration: Full migration and Incremental migration
                            • Real-time synchronization: Full synchronization and Incremental synchronization
                            • Real-time disaster recovery: Disaster recovery in progress
                            +
                            +
                            +

                            Viewing Metrics

                            1. Log in to the management console.
                            2. Click in the upper left corner and select a region and project.
                            3. Choose Database > Data Replication Service. The Data Replication Service page is displayed.
                            4. Take real-time migration as an example. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                            5. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

                              By default, the monitoring information about the DRS instance is displayed on this page.

                              +

                            6. View monitoring metrics of the instance.

                              • On the Cloud Eye console, click the target DB instance name and click Select Metric in the upper right corner. In the displayed dialog box, you can select the metrics to be displayed and sort them by dragging them at desired locations.
                              • You can sort graphs by dragging them based on service requirements.
                              • Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 7 days, and 6 months.
                              +

                            +
                            +
                            +
                            +
                            +
                            Parent topic: Interconnecting with Cloud Eye
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_06_0003.html b/docs/drs/umn/drs_06_0003.html index fe94e35a7..aef8d1ebf 100644 --- a/docs/drs/umn/drs_06_0003.html +++ b/docs/drs/umn/drs_06_0003.html @@ -8,7 +8,7 @@
                          • From MySQL to GaussDB Distributed
                            • -
                          • From MySQL to GaussDB(for MySQL) Primary/Standby
                            +
                          • From MySQL to TaurusDB Cluster
                          • From PostgreSQL to PostgreSQL
                            • diff --git a/docs/drs/umn/drs_06_0004.html b/docs/drs/umn/drs_06_0004.html index 44be7b2fb..36812fe46 100644 --- a/docs/drs/umn/drs_06_0004.html +++ b/docs/drs/umn/drs_06_0004.html @@ -102,7 +102,7 @@
                            -
                            • If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.
                            • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                            • Deleted synchronization tasks are not displayed in the status list.
                            • For a task whose source database is DDM or GaussDB Distributed,the statuses listed above mean statuses of its subtask.
                            +
                            • If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.
                            • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                            • Deleted synchronization tasks are not displayed in the status list.
                            • For a task whose source database is DDM or GaussDB Distributed, the statuses listed above mean statuses of its subtask.
                            diff --git a/docs/drs/umn/drs_06_0005.html b/docs/drs/umn/drs_06_0005.html index 5d541daab..af0853c26 100644 --- a/docs/drs/umn/drs_06_0005.html +++ b/docs/drs/umn/drs_06_0005.html @@ -95,16 +95,31 @@
                            -
                          • Tags -
                            Table 3 Tags

                            Parameter

                            +
                          • DRS instance specifications +
                            - - - + + +
                            Table 3 Specifications

                            Parameter

                            Description

                            +

                            Description

                            Tags

                            +

                            Specifications

                            • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                            • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                            +

                            DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                            +
                            +
                            +
                          • Tags +
                            + + + + + @@ -114,7 +129,7 @@

                            If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                          • After the synchronization instance is created, on the Configure Source and Destination Databases page, specify source and destination database information. Then, click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, select the check box before the agreement and click Next.

                            • Source database information -
                            • Table 4 Tags

                            Parameter

                            +

                            Description

                            +

                            Tags

                            +
                            • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                            • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                            Table 4 Source database settings

                            Parameter

                            +
                            @@ -145,7 +160,7 @@ @@ -156,7 +171,7 @@
                            • Destination database information -
                            Table 5 Source database settings

                            Parameter

                            Description

                            SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                            This parameter is unavailable when the network type is VPC network and the database type is RDS DB instance.

                            -
                            NOTE:
                            • The maximum size of a single certificate file that can be uploaded is 500 KB.
                            • If SSL is disabled, your data may be at risk.
                            +
                            NOTE:
                            • The maximum size of a single certificate file that can be uploaded is 500 KB.
                            • If the SSL certificate is not used, your data may be at risk.
                            Table 5 Destination database settings

                            Parameter

                            +
                            @@ -186,7 +201,7 @@

                          • On the Set Synchronization Task page, select the conflict policy and synchronization objects, and then click Next.

                            -

                            • Table 6 Destination database settings

                            Parameter

                            Description
                            Table 6 Synchronization mode and object

                            Parameter

                            +
                            @@ -223,7 +238,7 @@ - + + + @@ -245,12 +266,12 @@
                            Table 7 Synchronization mode and object

                            Parameter

                            Description

                            Synchronize

                            Normal indexes and incremental DDLs can be synchronized. You can determine whether to synchronize data based on service requirements. If you deselect Normal index, DDL statements related to index adding will be filtered out in the incremental phase. If the DDL statements contain other operations, they may also be filtered out.

                            +

                            Normal indexes and incremental DDLs can be synchronized. You can determine whether to synchronize normal indexes and DDLs based on service requirements.

                            Start Point

                            @@ -232,12 +247,18 @@

                            Run show master status to obtain the source database position and set File, Position, and Executed_Gtid_Set as prompted. If gtid_mode is disabled, you do not need to specify Executed_Gtid_Set.

                            Online DDL

                            +

                            If table-level synchronization is selected, you can choose whether to synchronize Online DDL. By default, Online DDL is not synchronized.

                            +
                            • Yes: Table-level synchronization supports Online DDL synchronization. You can select three Online DDL tools including PT-OSC, GH-OST, and DMS. The regular expressions can be configured for shadow tables and useless tables in PT-OSC and GH-OST. (Default values are provided. You are advised not to change the regular expressions unless otherwise specified.)
                            • No: Table-level synchronization does not support Online DDL synchronization.
                            +

                            Synchronization Object

                            Select Tables, Import object file, or Databases as required.

                            -
                            • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Mapping Object Names.

                              If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

                              +
                              • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                                If the database table name contains characters other than letters, digits, and underscores (_), or the mapped database table name contains hyphens (-) and number signs (#), the name length cannot exceed 42 characters.

                              • For details about how to import an object file, see Importing Synchronization Objects.
                              -
                              NOTE:
                              • To quickly select the desired database objects, you can use the search function.
                              • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                              +
                              NOTE:
                              • You can search for table names to quickly select the required database objects.
                              • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                              • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                              • The name of the selected synchronization object cannot contain spaces.
                            -

                          • On the Process Data page, set the filtering rules for data processing.

                            • If data processing is not required, click Next.
                            • If data processing is required, select Data filtering. For details about how to configure related rules, see Processing Data.
                            +

                          • On the Process Data page, set the filtering rules for data processing.

                            • If data processing is not required, click Next.
                            • If data processing is required, select Data Filtering. For details about how to configure related rules, see Processing Data.

                          • On the Check Task page, check the synchronization task.

                            • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                            • If all check items are successful, click Next.

                              You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                            -

                          • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                            -

                            - - - diff --git a/docs/drs/umn/drs_11_0006.html b/docs/drs/umn/drs_11_0006.html index 1a34e9a28..6f2eb982c 100644 --- a/docs/drs/umn/drs_11_0006.html +++ b/docs/drs/umn/drs_11_0006.html @@ -42,13 +42,13 @@ -
                            Table 7 Task startup settings

                            Parameter

                            +

                          • On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                            +

                            @@ -266,7 +287,7 @@
                            Table 8 Task startup settings

                            Parameter

                            Description
                            -

                          • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                            • You can view the task status. For more information about task status, see Task Statuses.
                            • You can click in the upper-right corner to view the latest task status.
                            +

                          • After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                            • You can view the task status. For more information about task status, see Task Statuses.
                            • You can click in the upper-right corner to view the latest task status.
                            • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.

                            • diff --git a/docs/drs/umn/drs_06_0010.html b/docs/drs/umn/drs_06_0010.html new file mode 100644 index 000000000..708f4cb4a --- /dev/null +++ b/docs/drs/umn/drs_06_0010.html @@ -0,0 +1,15 @@ + + +

                            Changing a Single-AZ Task to a Dual-AZ Task

                            +

                            DRS allows you to change a single-AZ task to a dual-AZ task, improving task reliability while remaining the original task.

                            +

                            Constraints

                            • A dual-AZ task cannot be changed to a single-AZ task.
                            • Only tasks in the Incremental or Incremental failed state can be changed.
                            • Only synchronization tasks from GaussDB Centralized to Kafka can be changed.
                            +
                            +

                            Procedure

                            1. Log in to the management console.
                            2. Click in the upper left corner and select a region and project.
                            3. Choose Databases > Data Replication Service. The Data Replication Service page is displayed.
                            4. On the Data Synchronization Management page, select the target task and choose More > Change to Primary/Standby in the Operation column.
                            5. On the displayed page, select the standby AZ. If the task is over a public network, you need to specify the EIP of the standby task and click OK.
                            6. After submitting the change, click Back to Task List. On the Data Synchronization Management page, the task status is Changing to primary/standby. After the task is changed, you can see that the parent task contains one primary and one standby subtask. The standby subtask and the parent task are in the Configuration state.
                            7. Click Edit in the Operation column of the parent task. On the displayed page, test the connections to the source and destination databases. If the connections are normal, click Next.
                            8. On the Confirm Task page, click Start Task. If the task is billed on a yearly/monthly basis, click Pay and Start to go to the payment page.
                            +
                            +
                            +
                            +
                            +
                            Parent topic: Task Life Cycle
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_08_0012.html b/docs/drs/umn/drs_08_0012.html index 120a7f899..b0d1432a9 100644 --- a/docs/drs/umn/drs_08_0012.html +++ b/docs/drs/umn/drs_08_0012.html @@ -1,12 +1,12 @@

                            Creating a User and Granting Permissions

                            -

                            This section describes IAM's fine-grained permissions management for DRS.

                            +

                            This section describes IAM's fine-grained permissions management for DRS.

                            • With IAM, you can:
                              • Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to DRS resources.
                              • Grant only the permissions required for users to perform a specific task.
                              • Entrust an account or cloud service to perform professional and efficient O&M on your DRS resources.

                            If your account does not require individual IAM users, skip this chapter.

                            This section describes the procedure for granting permissions (see Figure 1).

                            -

                            Prerequisites

                            Learn about the permissions (see Permissions Management) supported by DRS and choose policies or roles according to your requirements.

                            +

                            Prerequisites

                            Learn about the permissions (see Permissions Management) supported by DRS and choose policies or roles according to your requirements.

                            Process Flow

                            Figure 1 Process for granting DRS permissions
                            1. Create a user group and assign permissions to it.

                              Create a user group on the IAM console, and assign the DRS Administrator policy to the group.

                              diff --git a/docs/drs/umn/drs_08_0088.html b/docs/drs/umn/drs_08_0088.html index c4e14c2f5..4aef8e907 100644 --- a/docs/drs/umn/drs_08_0088.html +++ b/docs/drs/umn/drs_08_0088.html @@ -5,14 +5,14 @@

                              You can create custom policies in either of the following ways:

                              • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
                              • JSON: Create a policy in JSON format or edit the JSON strings of an existing policy.

                              For details about how to create a custom policy, see Identity and Access Management User Guide. The following describes examples of common DRS custom policies.

                              -

                              Example Custom Policies

                              • Example 1: Allowing users to create DRS migration instances
                                {
+
                                Example Custom Policies
                                • Example 1: Allowing users to create DRS instances
                                  {
 	"Version": "1.1",
 	"Statement": [{
-		"Action": ["drs:migrationJob:create"],
+                "Action": ["drs:migrationJob:create"],
 		"Effect": "Allow"
 	}]
 }
                                  
-
                                • Example 2: Denying DRS migration instance deletion
                                  A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
                                  
+
                                • Example 2: Denying DRS instance deletion
                                  A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
                                  
 
                                  The following method can be used if you need to assign permissions of the DRS FullAccess policy to a user but you want to prevent the user from deleting DRS instances. Create a custom policy for denying DRS instance deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on DRS instances except deleting DRS instances. The following is an example of a deny policy:
                                  
 
                                  {
 	"Version": "1.1",
diff --git a/docs/drs/umn/drs_09_0101.html b/docs/drs/umn/drs_09_0101.html
index 2144fd831..6fb96df9d 100644
--- a/docs/drs/umn/drs_09_0101.html
+++ b/docs/drs/umn/drs_09_0101.html
@@ -3,9 +3,9 @@
 
                                  How Do I Delete Orphaned Documents in MongoDB Sharded Clusters?
                                  
 
                                  What Is Orphaned Document?
                                  In a sharded cluster, orphaned documents are those documents on a shard that also exist in chunks on other shards as a result of failed migrations or incomplete migration cleanup due to abnormal shutdown.
                                  
 
                                  
-
                                  Migration Impact
                                  During cluster migration, DRS extracts full data from shards. Normal documents and orphaned documents are on different shards and DRS will migrate them all. If the conflict policy of DRS migration from MongoDB to DDS is Ignore, documents that are first migrated to the destination are stored, resulting in data inconsistency.
                                  
+
                                  Migration Impact
                                  During cluster migration, DRS extracts full data from shards. Normal documents and orphaned documents are on different shards and DRS will migrate them all. If the conflict policy of DRS migration from MongoDB to DDS is Ignore, documents that are first migrated to the destination are stored, resulting in data inconsistency.
                                  
 
                                  
-
                                  Procedure
                                  1. Contact technical support to obtain the cleanupOrphaned script for deleting orphaned files and decompress the script.
                                  2. Modify the cleanupOrphaned.js script file and replace test with the database name of the orphaned document to be cleared.
                                  3. Run the following command to clear the orphaned documents of all collections in the specified database on the shard node:
                                    mongo --host ShardIP --port Primaryport --authenticationDatabase database -u username -p password cleanupOrphaned.js
                                    
+
                                    Procedure
                                    1. Contact technical support to obtain the cleanupOrphaned script for deleting orphaned files and decompress the script.
                                    2. Modify the cleanupOrphaned.js script file and replace test with the database name of the orphaned document to be cleared.
                                    3. Run the following command to clear the orphaned documents of all collections in the specified database on the shard node:
                                      mongo --host ShardIP --port Primaryport --authenticationDatabase database -u username -p password cleanupOrphaned.js
                                      
 
                                       
                                      • ShardIP: indicates the IP address of the shard node.
                                      • Primaryport: indicates the service port of the primary shard node.
                                      • database: indicates the database name.
                                      • username: indicates the username for logging in to the database.
                                      • password indicates the password for logging in to the database.
                                      
 
                                      
 
                                       
                                      If you have multiple databases, repeat 2 and 3 to clean up orphaned documents in each database on each shard node.
                                      
diff --git a/docs/drs/umn/drs_10_0002.html b/docs/drs/umn/drs_10_0002.html
index 064995540..d6a02a9c6 100644
--- a/docs/drs/umn/drs_10_0002.html
+++ b/docs/drs/umn/drs_10_0002.html
@@ -16,6 +16,8 @@
 
                                      4. 
 
                                    4. Tag Management
                                      
 
                                      5. 
+
                                    5. Interconnecting with Cloud Eye
                                      
+
                                      6. 
 
                                    6. Operation Reference in Synchronization Scenarios
                                      
 
                                      7. 
 
                                
diff --git a/docs/drs/umn/drs_10_0003.html b/docs/drs/umn/drs_10_0003.html
index 174246fde..1e5702055 100644
--- a/docs/drs/umn/drs_10_0003.html
+++ b/docs/drs/umn/drs_10_0003.html
@@ -4,9 +4,9 @@
 
                                View the information about the synchronization tasks and synchronization instances. This section describes how to view details about a synchronization task you have created.
                                
 
                                Prerequisites
                                You have logged in to the DRS console.
                                
 
                                
-
                                Procedure
                                 
                                • In the task list, only tasks created by the current login user are displayed. Tasks created by different users of the same tenant are not displayed.
                                • For a task whose source database is MySQL Schema and Logic Table or DDM, the task details of each subtask contain the information about the source and destination databases corresponding to the subtask.
                                
+
                                Procedure
                                 
                                • The task list displays all tasks under the tenant to which the current login user belongs and for which the login user has the query permission. Tasks created by different users of the same tenant are displayed.
                                • For a task whose source database is MySQL Schema and Logic Table or DDM, the task details of each subtask contain the information about the source and destination databases corresponding to the subtask.
                                
 
                                
-
                                1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                2. On the displayed Basic Information page, view details about the migration task.
                                  You can view information about the task, synchronization instance, and synchronization.
                                  
+
                                  1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                  2. On the displayed Basic Information page, view details about the migration task.
                                    You can view information about the task, synchronization instance, and synchronization.
                                    
 
                                  
 
                                
 
                                
diff --git a/docs/drs/umn/drs_10_0004.html b/docs/drs/umn/drs_10_0004.html
index 2a440792d..b80390a79 100644
--- a/docs/drs/umn/drs_10_0004.html
+++ b/docs/drs/umn/drs_10_0004.html
@@ -6,7 +6,7 @@
 
                                • Task name
                                • Description
                                • Task start time
                                
 
                                Prerequisites
                                You have logged in to the DRS console.
                                
 
                                
-
                                Procedure
                                1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                2. On the Basic Information tab, locate the information to be modified in the Task Information area.
                                  • You can click  to modify the task name and description.
                                    • To submit the change, click .
                                    • To cancel the change, click .
                                    
+
                                    Procedure
                                    1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                    2. On the Basic Information tab, locate the information to be modified in the Task Information area.
                                      • You can click  to modify the task name and description.
                                        • To submit the change, click .
                                        • To cancel the change, click .
                                        
 
 
                                        
diff --git a/docs/drs/umn/drs_10_0007.html b/docs/drs/umn/drs_10_0007.html
index 8f1bf36b3..89a666652 100644
--- a/docs/drs/umn/drs_10_0007.html
+++ b/docs/drs/umn/drs_10_0007.html
@@ -5,7 +5,7 @@
 
                                        • During a full synchronization, DRS displays the progress overview. You can view the structure, data, and index migration progress. When the progress reaches 100%, the synchronization is complete. The synchronization of data and indexes is relatively slow.
                                        • During an incremental synchronization, DRS displays the incremental synchronization delay. You can determine the synchronization status between the source and destination databases based on the delay. If the delay is 0, the source and destination databases are instantaneously consistent, and no new transaction needs to be synchronized.
                                        Prerequisites
                                        You have logged in to the DRS console.
                                        
 
                                        
-
                                        Procedure
                                        1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                        2. On the displayed page, click Synchronization Progress to view table synchronization progress.
                                          • When a full synchronization is complete, the progress reaches 100%.
                                          • After the full synchronization is complete, the incremental synchronization starts. You can view the incremental synchronization delay on the Synchronization Progress tab.
                                          • You can also view the incremental synchronization delay on the Data Synchronization Management page. When the incremental synchronization delay exceeds the preset or default threshold, the value of the incremental synchronization delay is displayed in red in the task list.
                                          • When the delay is 0s, the data in the source and destination databases is synchronized in real time.
                                          
+
                                          Procedure
                                          1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                          2. On the displayed page, click Synchronization Progress to view table synchronization progress.
                                            • When a full synchronization is complete, the progress reaches 100%.
                                            • After the full synchronization is complete, the incremental synchronization starts. You can view the incremental synchronization delay on the Synchronization Progress tab.
                                            • You can also view the incremental synchronization delay on the Data Synchronization Management page. When the incremental synchronization delay exceeds the preset or default threshold, the value of the incremental synchronization delay is displayed in red in the task list.
                                            • When the delay is 0s, the data in the source and destination databases is synchronized in real time.
                                            
 
                                             
                                            "Delay" refers to the delay from when the transaction was submitted to the source database to when it is synchronized to the destination database and executed.
                                            
 
                                            Transactions are synchronized as follows:
                                            
 
                                            1. Data is extracted from the source database.
                                            2. The data is transmitted over the network.
                                            3. DRS parses the source logs.
                                            4. The transaction is executed on the destination database.
                                            
diff --git a/docs/drs/umn/drs_10_0009.html b/docs/drs/umn/drs_10_0009.html
index 930eb4894..2321a3916 100644
--- a/docs/drs/umn/drs_10_0009.html
+++ b/docs/drs/umn/drs_10_0009.html
@@ -9,7 +9,7 @@
 
                                            3. 
 
                                          3. In the synchronization task list on the Data Synchronization Management page, the current task status is Incremental synchronization, and a subtask in the Modifying task status is generated. After the subtask change is complete, incremental synchronization is performed for the edited synchronization objects.
                                          
 
                                          
-
                                          Method 2
                                          1. On the Data Synchronization Management page, click the target synchronization task.
                                          2. On the displayed page, click the Synchronization Mapping tab and click Edit to the right of the synchronization object.
                                          3. Perform 2 to 4 from method 1.
                                          
+
                                          Method 2
                                          1. On the Data Synchronization Management page, click the target synchronization task.
                                          2. On the displayed page, click the Synchronization Mapping tab and click Edit to the right of the synchronization object.
                                          3. Perform 2 to 4 from method 1.
                                          
 
                                          
 
                                          
 
                                          
diff --git a/docs/drs/umn/drs_10_0012.html b/docs/drs/umn/drs_10_0012.html
index bd9043415..9574bbcdf 100644
--- a/docs/drs/umn/drs_10_0012.html
+++ b/docs/drs/umn/drs_10_0012.html
@@ -1,7 +1,7 @@
 
 
 
                                          Step 4: Compare Synchronization Items
                                          
-
                                          Scenarios
                                          This section describes how to compare synchronization items to check if there are any differences between source and destination databases. To minimize the impact on services and shorten the service interruption duration, the following comparison methods are provided:
                                          
+
                                          Scenarios
                                          This section describes how to compare synchronization items to check if there are any differences between source and destination databases. To minimize the impact on services and shorten the service interruption duration, the following comparison methods are provided:
                                          
 
                                          • Object-level comparison: compares objects such as databases, indexes, tables, views, stored procedures, functions, and table sorting rules.
                                          • Data-level comparison is classified into row comparison and value comparison.
                                            • Row comparison: It helps you compare the number of rows in the tables to be synchronized. This comparison method is recommended because it is fast.
                                            • Value comparison: It helps you check whether data in the synchronized table is consistent. The comparison process is relatively slow.
                                            
 
                                          • Account comparison: It compares usernames and permissions of the source and destination databases.
                                          • Periodic comparison: DRS periodically compares the number of rows in the source database table with those in the destination database table and displays the comparison results. To compare objects periodically, enable comparison policy.
                                          
 
                                          When you check data consistency, compare the number of rows first. If the number of rows are inconsistent, you can then compare the data in the table to determine the inconsistent data.
                                          
@@ -11,7 +11,7 @@
 
                                          
 
                                          Prerequisites
                                          • You have logged in to the DRS console.
                                          • A synchronization task has been started.
                                          
 
                                          
-
                                          Creating a Comparison Task
                                          1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                          2. Click the Synchronization Comparison tab.
                                          3. Compare synchronization items.
                                            • On the Object-Level Comparison tab, check whether the comparison results of the source and destination databases are consistent. Locate a comparison item you want to view and click View Details in the Operation column.
                                            • On the Data-Level Comparison tab, click Create Comparison Task. In the displayed dialog box, specify Comparison Type, Comparison Time, and Object. Then, click OK.
                                              • Comparison Type: compares rows and values.
                                                • Row comparison: checks whether the source table has the same number of rows as the destination table.
                                                   
                                                  • After a task enters the incremental comparison phase, you can create a row comparison task.
                                                  
+
                                                  Creating a Comparison Task
                                                  1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                                  2. Click the Synchronization Comparison tab.
                                                  3. Compare synchronization items.
                                                    • On the Object-Level Comparison tab, check whether the comparison results of the source and destination databases are consistent. Locate a comparison item you want to view and click View Details in the Operation column.
                                                    • On the Data-Level Comparison tab, click Create Comparison Task. In the displayed dialog box, specify Comparison Type, Comparison Time, and Object. Then, click OK.
                                                      • Comparison Type: compares rows and values.
                                                        • Row comparison: checks whether the source table has the same number of rows as the destination table.
                                                           
                                                          • After a task enters the incremental comparison phase, you can create a row comparison task.
                                                          
 
                                                          
 
                                                        • Value comparison: checks whether the source table has the same data as the destination table.
                                                           
                                                          • After a task enters the incremental synchronization phase, you can create a value comparison task. After the full synchronization is complete, data in the source database cannot be changed. Otherwise, the comparison result will be inconsistent.
                                                          
 
                                                          
@@ -32,7 +32,7 @@
 
                                                  
 
                                                  
 
                                                  Periodic Comparison
                                                  Periodic comparison indicates that DRS periodically compares the number of rows in the source database table with those in the destination database table and displays the comparison results.
                                                  
-
                                                  1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                                  2. Click the Synchronization Comparison tab.
                                                  3. Click the Periodic Comparison tab and click Modify Comparison Policy to modify the comparison policy.
                                                  4. In the Modify Comparison Policy dialog box, enable periodic comparison, configure the comparison frequency and time, and click Yes.
                                                     
                                                    • After periodic comparison is enabled, DRS compares the number of rows at the scheduled time. You can view the comparison results on the Data-Level Comparison tab.
                                                    • After periodic comparison is disabled, only historical comparison results can be viewed.
                                                    • Modifications to the comparison policy settings take effect from the next comparison and do not affect the on-going periodic comparison tasks.
                                                    • During periodic comparison, the source and destination databases will be read. Perform the comparison during off-peak hours.
                                                    • During periodic comparison, ultra-large tables (those with more than 100 million rows) are automatically filtered out. You can use data-level comparison to spot check such large tables. It is not recommended that these large tables be compared periodically.
                                                    
+
                                                    1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                                    2. Click the Synchronization Comparison tab.
                                                    3. Click the Periodic Comparison tab and click Modify Comparison Policy to modify the comparison policy.
                                                    4. In the Modify Comparison Policy dialog box, enable periodic comparison, configure the comparison frequency and time, and click Yes.
                                                       
                                                      • After periodic comparison is enabled, DRS compares the number of rows at the scheduled time. You can view the comparison results on the Data-Level Comparison tab.
                                                      • After periodic comparison is disabled, only historical comparison results can be viewed.
                                                      • Modifications to the comparison policy settings take effect from the next comparison and do not affect the on-going periodic comparison tasks.
                                                      • During periodic comparison, the source and destination databases will be read. Perform the comparison during off-peak hours.
                                                      • During periodic comparison, ultra-large tables (those with more than 100 million rows) are automatically filtered out. You can use data-level comparison to spot check such large tables. It is not recommended that these large tables be compared periodically.
                                                      
 
                                                      
 
                                                    
 
                                                    
diff --git a/docs/drs/umn/drs_10_0015.html b/docs/drs/umn/drs_10_0015.html
index 74a894105..457d508e8 100644
--- a/docs/drs/umn/drs_10_0015.html
+++ b/docs/drs/umn/drs_10_0015.html
@@ -1,12 +1,17 @@
 
 
-
                                                    Mapping Object Names
                                                    
-
                                                    Data synchronization allows you to synchronize objects (including databases, schemas and tables) in a sources database to the corresponding objects in a destination database. If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. The object types that can be mapped include database, schema, and table.
                                                    
+
                                                    Changing Object Names (Mapping Object Names)
                                                    
+
                                                    Data synchronization allows you to synchronize objects (including databases, schemas and tables) in a sources database to the corresponding objects in a destination database. If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one by changing the object name. The objects that can be changed or mapped include databases, schemas, and tables.
                                                    
 
                                                    Object name mapping can be used only in the following scenarios:
                                                    
 
                                                    • For the first time you select synchronization objects for a data synchronization task.
                                                    • For the first time you add or delete the synchronization object which is not in a mapping relationship.
                                                    
-
                                                     
                                                    • If the destination DB is a type of PostgreSQL, the destination schema name cannot start with pg_. Otherwise, the migration fails.
                                                    
+
                                                     
                                                    • If the destination DB is a type of PostgreSQL, the destination schema name cannot start with pg_. Otherwise, the migration fails.
                                                    
 
                                                    
 
                                                    This section describes how to map objects when configuring a data synchronization task. For details about the mapping relationship, see Viewing Synchronization Mapping Information.
                                                    
+
                                                    Changing an Object Name
                                                    During real-time synchronization, if the names of source databases, schemas, or tables to be synchronized are different from those in the destination, you can map the source names to the destination ones. 
                                                    
+
                                                    1. On the Set Synchronization Task page, select the database that needs to be mapped from the synchronization objects on the right area and click Edit.
                                                    2. Change a name.
                                                      In the displayed dialog box, enter a new object name. The new name is the name of the object saved in the destination database.
                                                      
+
                                                    3. Check the result.
                                                      After the name is changed, the name before modification and the new name are displayed. The object name mapping is complete.
                                                      
+
                                                    
+
                                                    
 
                                                    Mapping Databases
                                                    During real-time synchronization, if the names of source databases to be synchronized are different from those in the destination, you can map the source database names to the destination ones. For example, when synchronizing database A in the source database to database B in the destination database, you need to map database name first.
                                                    
 
                                                    1. On the Set Synchronization Task page, select the database that needs to be mapped from the synchronization objects on the right area and click Edit.
                                                    2. Changing a database name
                                                      In the displayed dialog box, enter a new database name. The new database name is the name of the database saved in the destination DB instance.
                                                      
 
                                                    3. Check the result.
                                                      After the database name is changed, the database name before modification and the new database name are displayed. The database mapping is complete.
                                                      
diff --git a/docs/drs/umn/drs_10_0401.html b/docs/drs/umn/drs_10_0401.html
index c08e21c2e..931b5ac22 100644
--- a/docs/drs/umn/drs_10_0401.html
+++ b/docs/drs/umn/drs_10_0401.html
@@ -2,7 +2,7 @@
 
 
                                                      Modifying the Flow Control Mode
                                                      
 
                                                      You can choose whether to control the flow. DRS allows you to change the flow control mode after a task is created. Currently, only the following real-time migration types support this function:
                                                      
-
                                                      • To the cloud
                                                        • MySQL->MySQL
                                                        • MySQL -> GaussDB(for MySQL) primary/standby
                                                        • Oracle->PostgreSQL
                                                        • PostgreSQL->PostgreSQL
                                                        
+
                                                        • To the cloud
                                                          • MySQL->MySQL
                                                          • MySQL -> TaurusDB Cluster
                                                          • Oracle->PostgreSQL
                                                          • PostgreSQL->PostgreSQL
                                                          
 
                                                        • Out of the cloud
                                                          • MySQL->MySQL
                                                          
 
                                                        • Self-built databases -> Self-built databases
                                                          • MySQL->MySQL
                                                          
 
                                                        
diff --git a/docs/drs/umn/drs_10_0402.html b/docs/drs/umn/drs_10_0402.html
index a05862a4b..7d4157043 100644
--- a/docs/drs/umn/drs_10_0402.html
+++ b/docs/drs/umn/drs_10_0402.html
@@ -1,8 +1,8 @@
 
 
 
                                                        Importing Synchronization Objects
                                                        
-
                                                        Real-time synchronization supports the import of objects through files. After a task is created, you can import object files on the Set Synchronization Task page. 
                                                        
-
                                                         
                                                        • Only Windows Microsoft Excel 97-2003 (*.xls) and 2007 and later (*.xlsx) files can be imported. The downloaded compressed package provides the templates of the two versions.
                                                        • The file name can contain only spaces, letters, digits, hyphens (-), underscores (_), and parentheses.
                                                        • The format of the object information in the template must meet the Excel file requirements. The database object names (such as the database name, schema name, or table name) in the file is case-sensitive and cannot include angle brackets (<>), periods (.), double quotation marks ("), and cannot start or end with a space.
                                                        • The task in the configuration supports table-level synchronization, database-level synchronization, or file import mode. Each time you switch to a new mode, the selected or imported database objects are cleared, and you need to select or import them again.
                                                        • If you want to import a file for mapping, fill in the first and second columns of the file based on the template. If the first two columns of a row are left blank, the row will be ignored.
                                                        • For the task created using the file import mode, database-level and table-level synchronization are not supported after the task is started.
                                                        • If you edit a task, the imported file must contain information about all objects. Importing only the updated objects is not allowed.
                                                        • If you edit a task again, the objects that have been synchronized cannot be mapped again. Ensure that the object names remain unchanged after the mapping.
                                                        • If you edit a task again, the exported object information is the synchronized object information.
                                                        • If the verification fails after the file is uploaded, click View Failure Details to download the error information.
                                                        • The object names entered in the Excel file must use the same letter case as the source object names.
                                                        
+
                                                        Real-time synchronization supports the import of objects through files. After a task is created, you can import object files on the Set Synchronization Task page. 
                                                        
+
                                                         
                                                        • Only Windows Microsoft Excel 97-2003 (*.xls) and 2007 and later (*.xlsx) files can be imported. The downloaded compressed package provides the templates of the two versions.
                                                        • The file name can contain only spaces, letters, digits, hyphens (-), underscores (_), and parentheses.
                                                        • The object information in the template must be filled in according to the format in the Excel file. The database object name (such as the database name, schema name, and table name) is case sensitive and cannot contain the following characters: <>.". Object names starting or ending with spaces are not supported.
                                                        • The task in the configuration supports table-level synchronization, database-level synchronization, or file import mode. Each time you switch to a new mode, the selected or imported database objects are cleared, and you need to select or import them again.
                                                        • If you want to import a file for mapping, fill in the first and second columns of the file based on the template. If the first two columns of a row are left blank, the row will be ignored.
                                                        • For the task created using the file import mode, database-level and table-level synchronization are not supported after the task is started.
                                                        • If you edit a task, the imported file must contain information about all objects. Importing only the updated objects is not allowed.
                                                        • If you edit a task again, the objects that have been synchronized cannot be mapped again. Ensure that the object names remain unchanged after the mapping.
                                                        • If you edit a task again, the exported object information is the synchronized object information.
                                                        • If the verification fails after the file is uploaded, click View Failure Details to download the error information.
                                                        • The object names entered in the Excel file must use the same letter case as the source object names.
                                                        
 
                                                        
 
                                                        Procedure
                                                        1. On the Set Synchronization Task page, click Import object file in the Synchronization Object field.
                                                        2. Click Download Template.
                                                        3. Download the template and enter information about the objects to be imported.
                                                        4. Click Select File. In the displayed dialog box, select the edited template.
                                                        5. Click Upload.
                                                          
 
                                                        
diff --git a/docs/drs/umn/drs_10_0409.html b/docs/drs/umn/drs_10_0409.html
new file mode 100644
index 000000000..5e5d5182a
--- /dev/null
+++ b/docs/drs/umn/drs_10_0409.html
@@ -0,0 +1,21 @@
+
+
+
+  
                                                        Managing Parameters
                                                        
+
+  
                                                        
+
                                                        
+
+
+
diff --git a/docs/drs/umn/drs_10_0410.html b/docs/drs/umn/drs_10_0410.html
new file mode 100644
index 000000000..f7f38c768
--- /dev/null
+++ b/docs/drs/umn/drs_10_0410.html
@@ -0,0 +1,401 @@
+
+
+
                                                        Changing Task Parameters
                                                        
+
                                                        DRS allows you to change task parameters based on service requirements.
                                                        
+
                                                        Constraints
                                                        • You can change parameters of a synchronization task in the Configuration, Full, Full synchronization failed, Incremental, Incremental synchronization failed, or Paused state.
                                                        • After some parameters of a task are changed, the changes take effect only after you restart the task by referring to Restarting a Synchronization Task. In addition, operations for resetting a task, resuming a task, rebuilding a task, performing primary/standby switchover, or changing the flow control in the full synchronization phase will restart task processes for the parameter changes to take effect.
                                                        
+
                                                        
+
                                                        Procedure
                                                        1. On the Data Synchronization Management page, locate the target synchronization task.
                                                        2. Click the task name. The Basic Information page is displayed.
                                                        3. Choose Parameters on the left pane. On the Parameters tab page, query and change the parameters of the current synchronization task by name.
                                                          
+
                                                        4. Click Save or Cancel.
                                                          • To save your changes, click Save. In the displayed dialog box, click Yes.
                                                          • To cancel your changes, click Cancel. In the displayed dialog box, click Yes.
                                                          
+
                                                        5. Restart the task for the changes to take effect. You can click Restart in the upper right corner.
                                                          In addition, operations for resetting a task, resuming a task, rebuilding a task, performing primary/standby switchover, or changing the flow control in the full synchronization phase will restart task processes for the parameter changes to take effect.
                                                          
+
                                                        
+
                                                        
+
                                                        Task Parameter Description
                                                        
+
                                        Table 1 Task information
                                        Task Information
                                        
                                         		
 
                                        
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
                                        Table 1 Task parameters
                                        Parameter
                                        
+
                                        Description
                                        
+
                                        Value Range
                                        
+
                                        Default Value
                                        
+
                                        Type
                                        
+
                                        Restart Required
                                        
+
                                        Applicable Data Flow
                                        
+
                                        applier_thread_num
                                        
+
                                        Number of threads for writing data to the destination database during the full synchronization phase.
                                        
+
                                        The value range depends on the task specifications.
                                        
+
                                        • Micro: 1-4
                                        • Small: 1-4
                                        • Medium: 1-8
                                        • Large: 1-18
                                        • Ultra-large: 1-24
                                        
+
                                        The default value depends on the task specifications.
                                        
+
                                        • Micro: 2
                                        • Small: 2
                                        • Medium: 4
                                        • Large: 8
                                        • Ultra-large: 12
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • MySQL->MySQL
                                        • MySQL->PostgreSQL
                                        • MySQL -> GaussDB Distributed
                                        • MySQL->TaurusDB
                                        • MySQL->Kafka
                                        • MySQL->Oracle
                                        • Microsoft SQL Server->MySQL
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        • Microsoft SQL Server->TaurusDB
                                        • Microsoft SQL Server->Microsoft SQL Server
                                        • DDM->DDM
                                        • DDM->MySQL
                                        
+
                                        read_task_num
                                        
+
                                        Number of threads for reading data from the source database during the full synchronization phase.
                                        
+
                                        The value range depends on the task specifications.
                                        
+
                                        • Micro: 1-2
                                        • Small: 1-2
                                        • Medium: 1-4
                                        • Large: 1-8
                                        • Ultra-large: 1-12
                                        
+
                                        The default value depends on the task specifications.
                                        
+
                                        • Micro: 1
                                        • Small: 1
                                        • Medium: 2
                                        • Large: 4
                                        • Ultra-large: 6
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • MySQL->MySQL
                                        • MySQL->PostgreSQL
                                        • MySQL -> GaussDB Distributed
                                        • MySQL->TaurusDB
                                        • MySQL->Kafka
                                        • MySQL->Oracle
                                        • Microsoft SQL Server->MySQL
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        • Microsoft SQL Server->TaurusDB
                                        • Microsoft SQL Server->Microsoft SQL Server
                                        • DDM->DDM
                                        • DDM->MySQL
                                        
+
                                        shard_task_num
                                        
+
                                        Number of sharding threads in the source database during the full synchronization phase.
                                        
+
                                        The value range depends on the task specifications.
                                        
+
                                        • Micro: 1-2
                                        • Small: 1-2
                                        • Medium: 1-4
                                        • Large: 1-8
                                        • Ultra-large: 1-8
                                        
+
                                        The default value depends on the task specifications.
                                        
+
                                        • Micro: 1
                                        • Small: 1
                                        • Medium: 2
                                        • Large: 4
                                        • Ultra-large: 4
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • MySQL->MySQL
                                        • MySQL->PostgreSQL
                                        • MySQL -> GaussDB Distributed
                                        • MySQL->TaurusDB
                                        • MySQL->Kafka
                                        • MySQL->Oracle
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        • Microsoft SQL Server->MySQL
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        • Microsoft SQL Server->TaurusDB
                                        • Microsoft SQL Server->Microsoft SQL Server
                                        • DDM->DDM
                                        • DDM->MySQL
                                        
+
                                        increment_writer_num
                                        
+
                                        Number of threads for writing data to the destination database during the incremental synchronization phase.
                                        
+
                                        The value range depends on the task specifications.
                                        
+
                                        • Micro: 1-8
                                        • Small: 1-16
                                        • Medium: 1-32
                                        • Large: 1-128
                                        • Ultra-large: 1-128
                                        
+
                                        The default value depends on the task specifications.
                                        
+
                                        • Micro: 4
                                        • Small: 8
                                        • Medium: 16
                                        • Large: 64
                                        • Ultra-large: 64
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • MySQL->MySQL
                                        • MySQL->PostgreSQL
                                        • MySQL -> GaussDB Distributed
                                        • MySQL->TaurusDB
                                        • MySQL->Kafka
                                        • MySQL->Oracle
                                        • DDM->DDM
                                        • DDM->MySQL
                                        
+
                                        relay_socket_timeout
                                        
+
                                        Timeout interval for obtaining logs from the source database during the incremental synchronization phase.
                                        
+
                                        30000-2147483647 ms
                                        
+
                                        30000 ms
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • MySQL->MySQL
                                        • MySQL->PostgreSQL
                                        • MySQL -> GaussDB Distributed
                                        • MySQL->TaurusDB
                                        • MySQL->Kafka
                                        • MySQL->Oracle
                                        • DDM->DDM
                                        • DDM->KAFKA
                                        • DDM->MySQL
                                        
+
                                        datamove_source_socket_timeout
                                        
+
                                        Timeout interval for obtaining data from the source database during the full synchronization phase.
                                        
+
                                        The value range depends on the DRS task engine.
                                        
+
                                        • MySQL -> MySQL: 120000-2147483647 ms
                                        • MySQL -> PostgreSQL: 120000-2147483647 ms
                                        • MySQL -> GaussDB Distributed: 120000-2147483647 ms
                                        • MySQL -> TaurusDB: 120000-2147483647 ms
                                        • MySQL -> Kafka: 120000-2147483647 ms
                                        • MySQL -> CSS/ES: 120000-2147483647 ms
                                        • MySQL -> Oracle: 120000-2147483647 ms
                                        • Oracle -> MySQL: 600000-2147483647 ms
                                        • Oracle -> PostgreSQL: 600000-2147483647 ms
                                        • Oracle -> GaussDB Distributed: 600000-2147483647 ms
                                        • Oracle -> DDM: 600000-2147483647 ms
                                        • Oracle -> Kafka: 600000-2147483647 ms
                                        • Microsoft SQL Server -> MySQL: 360000-2147483647 ms
                                        • Microsoft SQL Server -> PostgreSQL: 360000-2147483647 ms
                                        • Microsoft SQL Server -> GaussDB Distributed: 360000-2147483647 ms
                                        • Microsoft SQL Server -> TaurusDB: 360000-2147483647 ms
                                        • Microsoft SQL Server -> Kafka: 360000-2147483647 ms
                                        • Microsoft SQL Server -> Microsoft SQL Server: 360000-2147483647 ms
                                        
+
                                        The value range depends on the DRS task engine.
                                        
+
                                        • MySQL -> MySQL: 120000 ms
                                        • MySQL -> PostgreSQL: 120000 ms
                                        • MySQL -> GaussDB Distributed: 120000 ms
                                        • MySQL -> TaurusDB: 120000 ms
                                        • MySQL -> Kafka: 120000 ms
                                        • MySQL -> CSS/ES: 120000 ms
                                        • MySQL->Oracle
                                          : 120000 ms
                                          
+
                                        • Oracle -> MySQL: 600000 ms
                                        • Oracle -> PostgreSQL: 600000 ms
                                        • Oracle -> GaussDB Distributed: 600000 ms
                                        • Oracle -> GaussDB Centralized: 600000 ms
                                        • Oracle -> TaurusDB: 600000 ms
                                        • Oracle -> DDM: 600000 ms
                                        • Oracle -> Kafka: 600000 ms
                                        • Microsoft SQL Server -> MySQL: 360000 ms
                                        • Microsoft SQL Server -> PostgreSQL: 360000 ms
                                        • Microsoft SQL Server -> GaussDB Distributed: 360000 ms
                                        • Microsoft SQL Server -> GaussDB Centralized: 360000 ms
                                        • Microsoft SQL Server -> TaurusDB: 360000 ms
                                        • Microsoft SQL Server -> Kafka: 360000 ms
                                        • Microsoft SQL Server -> Microsoft SQL Server: 360000 ms
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • MySQL->MySQL
                                        • MySQL->PostgreSQL
                                        • MySQL -> GaussDB Distributed
                                        • MySQL->TaurusDB
                                        • MySQL->Kafka
                                        • MySQL->CSS/ES
                                        • MySQL->Oracle
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle -> GaussDB Centralized
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        • Oracle->Kafka
                                        • Microsoft SQL Server->MySQL
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        • Microsoft SQL Server -> GaussDB Centralized
                                        • Microsoft SQL Server->TaurusDB
                                        • Microsoft SQL Server->Kafka
                                        • Microsoft SQL Server->Microsoft SQL Server
                                        • DDM->DDM
                                        • DDM->KAFKA
                                        • DDM->MySQL
                                        
+
                                        shard_length
                                        
+
                                        Rows per shard during full synchronization
                                        
+
                                        520000-1000000000 or 0
                                        
+
                                        520000
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle -> GaussDB Centralized
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        • Microsoft SQL Server->MySQL
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        • Microsoft SQL Server -> GaussDB Centralized
                                        • Microsoft SQL Server->TaurusDB
                                        • Microsoft SQL Server->Microsoft SQL Server
                                        • DDM->DDM
                                        • DDM->DWS
                                        • DDM->KAFKA
                                        • DDM->MySQL
                                        
+
                                        datamove_fetchsize
                                        
+
                                        The size of the data reads from the source database during a full synchronization.
                                        
+
                                        10-10000
                                        
+
                                        The value range depends on the DRS task engine.
                                        
+
                                        • Oracle -> MySQL: 1000
                                        • Oracle->PostgreSQL
                                          : 1000
                                          
+
                                        • Oracle -> GaussDB Distributed: 10000
                                        • Oracle->TaurusDB
                                          : 1000
                                          
+
                                        • Oracle->DDM
                                          : 1000
                                          
+
                                        • Oracle->Kafka
                                          : 1000
                                          
+
                                        
+
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        
+
                                        datamove_copy_mode
                                        
+
                                        The write mode used when writing data to the destination database during an incremental synchronization. The write performance of COPY is higher than that of INSERT.
                                        
+
                                        true indicates the COPY mode, and false indicates the INSERT mode.
                                        
+
                                        true/false
                                        
+
                                        true
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        
+
                                        datamove_split_partition
                                        
+
                                        Whether to shard a partition table during full synchronization. true: Partition tables in the source database are sharded for parallel synchronization to improve the synchronization speed of large partitions. false: Partition tables are not sharded.
                                        
+
                                        true/false
                                        
+
                                        true
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        
+
                                        read_log_num
                                        
+
                                        Number of threads for obtaining logs from the source database during incremental synchronization.
                                        
+
                                        1-16
                                        
+
                                        2
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        • Oracle->Kafka
                                        
+
                                        logminer_fetchsize
                                        
+
                                        The size of the data reads when using LogMiner in scenarios where the source database is Oracle and incremental log read mode is set to LogMiner.
                                        
+
                                        10-10000
                                        
+
                                        1000
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle -> GaussDB Centralized
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        • Oracle->Kafka
                                        
+
                                        deal_hot_table
                                        
+
                                        Whether to accelerate the replay of hot tables with frequent DML operations in the source database during incremental synchronization. true: The replay of hot tables is accelerated; false: The replay of hot tables is not accelerated.
                                        
+
                                        true/false
                                        
+
                                        false
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle -> GaussDB Centralized
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        • Microsoft SQL Server->MySQL
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        • Microsoft SQL Server -> GaussDB Centralized
                                        • Microsoft SQL Server->TaurusDB
                                        • Microsoft SQL Server->Microsoft SQL Server
                                        • DDM->DDM
                                        • DDM->DWS
                                        • DDM->MySQL
                                        
+
                                        skip_all_ddl
                                        
+
                                        Whether to ignore all DDL statements during incremental synchronization. If there are a lot of irrelevant DDL statements, enable this function to improve the incremental synchronization performance. true: All DDL statements are ignored. false: All DDL statements are not ignored.
                                        
+
                                        true/false
                                        
+
                                        false
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • Oracle->MySQL
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle -> GaussDB Centralized
                                        • Oracle->TaurusDB
                                        • Oracle->DDM
                                        • Oracle->Kafka
                                        • DDM->DDM
                                        • DDM->MySQL
                                        
+
                                        replace_invalid_time
                                        
+
                                        Whether to replace the source time type with the default time when the source time type is invalid after being synchronized to the destination database during full+incremental synchronization. Default timestamp: 1970-01-01 00:00:00; default date: 1970-01-01; default time: 00:00:00. true: the source time type is replaced with the default time; false: the source time type is not replaced with the default time.
                                        
+
                                        true/false
                                        
+
                                        false
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Oracle -> GaussDB Centralized
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        • Microsoft SQL Server -> GaussDB Centralized
                                        
+
                                        replace_0x00
                                        
+
                                        Whether to replace 0x00 characters that are not supported by the destination database with spaces during full+incremental synchronization. true: 0x00 characters are replaced with spaces; false: 0x00 characters are not replaced with spaces.
                                        
+
                                        true/false
                                        
+
                                        true
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        
+
                                        replace_0xefbfbd
                                        
+
                                        Whether to replace abnormal characters with the default value '?' during full+incremental synchronization. DRS sets the character set of the JDBC client to UTF-8. During the query in the source database, abnormal bytes are converted to the UTF-8-encoded exception code EFBFBD. true: Abnormal code in UTF-8 encoding is replaced with '?'. false: Abnormal code is not replaced.
                                        
+
                                        true/false
                                        
+
                                        false
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • Oracle->PostgreSQL
                                        • Oracle -> GaussDB Distributed
                                        • Microsoft SQL Server->PostgreSQL
                                        • Microsoft SQL Server -> GaussDB Distributed
                                        
+
                                        big_column_value_limit
                                        
+
                                        Large field filtering threshold.
                                        
+
                                        0-99 * 1024 * 1024
                                        
+
                                        0
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • DDM->KAFKA
                                        
+
                                        big_column_value_replace
                                        
+
                                        Large field replacement characters.
                                        
+
                                        A character string without special characters
                                        
+
                                        -
                                        
+
                                        string
                                        
+
                                        Yes
                                        
+
                                        • DDM->KAFKA
                                        
+
                                        datamove_replace_invalid_time
                                        
+
                                        Whether to replace the source time type with the default time when the source time type is invalid after being synchronized to the destination database during a full synchronization. Default timestamp: 1970-01-01 00:00:00; default date: 1970-01-01; default time: 00:00:00. true: the source time type is replaced with the default time; false: the source time type is not replaced with the default time.
                                        
+
                                        true/false
                                        
+
                                        false
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+                                        		 
                                        increment_replace_invalid_time
                                        
+
                                        Whether to replace the source time type with the default time when the source time type is invalid after being synchronized to the destination database during an incremental synchronization. Default timestamp: 1970-01-01 00:00:00; default date: 1970-01-01; default time: 00:00:00. true: the source time type is replaced with the default time; false: the source time type is not replaced with the default time.
                                        
+
                                        true/false
                                        
+
                                        false
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+                                        		 
                                        datamove_chunk_size
                                        
+
                                        The amount of data transferred to the destination database at a time, in bytes.
                                        
+
                                        1000-35000000
                                        
+
                                        35000000
                                        
+
                                        int
                                        
+
                                        Yes
                                        
+
                                        • DDM->DDM
                                        • DDM->MySQL
                                        
+
                                        skip_failed_ddl
                                        
+
                                        Whether to skip failed DDL statements.
                                        
+
                                        true/false
                                        
+
                                        false
                                        
+
                                        boolean
                                        
+
                                        Yes
                                        
+
                                        • DDM->DDM
                                        • DDM->MySQL
                                        
+
                                        
+
                                        
+
                                        
+
                                    
+
                                
+
                                
+
                                
+
                                Parent topic: Managing Parameters
                                
+
                                
+
                                
+
diff --git a/docs/drs/umn/drs_10_0411.html b/docs/drs/umn/drs_10_0411.html
new file mode 100644
index 000000000..b2eb56135
--- /dev/null
+++ b/docs/drs/umn/drs_10_0411.html
@@ -0,0 +1,15 @@
+
+
+
                                Viewing Parameter Change History
                                
+
                                DRS allows you to view the change history of task parameters to meet service requirements.
                                
+
                                Procedure
                                1. On the Data Synchronization Management page, locate the target synchronization task.
                                2. Click the task name. The Basic Information page is displayed.
                                3. Choose Parameters on the left pane. On the Change History tab page, view the change history of parameters of the current synchronization task.
                                  By default, the parameter change history of the last seven days can be queried.
                                  
+
                                  
+
                                
+
                                
+
                                
+
                                
+
                                
+
                                Parent topic: Managing Parameters
                                
+
                                
+
                                
+
diff --git a/docs/drs/umn/drs_10_0412.html b/docs/drs/umn/drs_10_0412.html
new file mode 100644
index 000000000..0cbc87d9b
--- /dev/null
+++ b/docs/drs/umn/drs_10_0412.html
@@ -0,0 +1,18 @@
+
+
+
                                Restarting a Synchronization Task
                                
+
                                DRS allows you to restart a synchronization task after task parameters are changed in Changing Task Parameters.
                                
+
                                Constraints
                                • Tasks in the Full, Full synchronization failed, Incremental, or Incremental synchronization failed state can be restarted.
                                • Only the synchronization tasks of the following engines can be restarted:
                                  • MySQL->MySQL
                                  • MySQL->PostgreSQL
                                  • MySQL -> GaussDB Distributed
                                  • MySQL -> GaussDB Centralized
                                  • MySQL->TaurusDB
                                  • MySQL->Kafka
                                  • MySQL->CSS/ES
                                  • MySQL->Oracle
                                  
+
                                
+
                                
+
                                Method 1
                                1. In the task list on the Data Synchronization Management page, locate the target task and click Restart in the Operation column.
                                2. In the displayed Restart Task dialog box, click Yes.
                                
+
                                
+
                                Method 2
                                1. On the Data Synchronization Management page, click the target synchronization task in the Task Name/ID column.
                                2. On the Basic Information page, click Restart in the upper right corner.
                                3. In the displayed Restart Task dialog box, click Yes.
                                
+
                                
+
                                
+
                                
+
                                
+
                                Parent topic: Task Life Cycle
                                
+
                                
+
                                
+
diff --git a/docs/drs/umn/drs_11_0005.html b/docs/drs/umn/drs_11_0005.html
index 7891ed1aa..d36238241 100644
--- a/docs/drs/umn/drs_11_0005.html
+++ b/docs/drs/umn/drs_11_0005.html
@@ -51,12 +51,12 @@
 
                                Handling suggestion: Check whether the source database version is MongoDB 3.2x, 3.4.x, 3.6.x, 4.0.x, 4.2.x, or 4.4.x.

                            Failure cause: This item cannot be checked because the source database fails to be connected.

                            -

                            Handling suggestion: Check whether the source database is connected.

                            +

                            Failure cause: This item cannot be checked because the source database fails to be connected.

                            +

                            Handling suggestion: Check whether the source database is connected.

                            Failure cause: The incremental data is obtained in changeStream mode but the source database version is earlier than 4.0.

                            -

                            Handling suggestion: In changeStream mode, ensure that the source database version is 4.0 or later.

                            +

                            Failure cause: The incremental data is obtained in changeStream mode but the source database version is earlier than 4.0.

                            +

                            Handling suggestion: In changeStream mode, ensure that the source database version is 4.0 or later.

                            Failure cause: An internal error occurs.

                            @@ -75,13 +75,13 @@

                            Description

                            Check whether the source database version is Oracle 10g, 11g, 12c, 18c, 19c, or 21c.

                            +

                            Check whether the source database version is Oracle 10g, 11g, 12c, 18c, 19c, or 21c.

                            Failure Cause and Handling Suggestion

                            Failure cause: The source database version is not supported.

                            -

                            Handling suggestion: Check whether the source database version is supported. Currently, only Oracle 10g, 11g, 12c, 18c, 19c, or 21c are supported.

                            +

                            Handling suggestion: Check whether the source database version is supported. Currently, only Oracle 10g, 11g, 12c, 18c, 19c, and 21c are supported.

                            Description

                            Check whether the destination database version is 3.4.x, 4.0.x, 4.2.x, or 4.4.x.

                            +

                            Check whether the destination database version is MongoDB 3.4.x, 4.0.x, 4.2.x, or 4.4.x.

                            Failure Cause and Handling Suggestion

                            Failure cause: The destination database version is not supported.

                            -

                            Handling suggestion: Check whether the destination database version is 3.4.x, 4.0.x, 4.2.x, or 4.4.x.

                            +

                            Handling suggestion: Check whether the destination database version is MongoDB 3.4.x, 4.0.x, 4.2.x, or 4.4.x.

                            Failure cause: This item cannot be checked because the destination database fails to be connected.

                            diff --git a/docs/drs/umn/drs_11_0007.html b/docs/drs/umn/drs_11_0007.html index aea372a26..fcdc38ecc 100644 --- a/docs/drs/umn/drs_11_0007.html +++ b/docs/drs/umn/drs_11_0007.html @@ -96,7 +96,7 @@
                            -

                            Migration from MongoDB to DDS

                            +

                            MongoDB Migration

                            - - - - + + + - - - - - - - - - - - - - - - - - diff --git a/docs/drs/umn/drs_online_migration.html b/docs/drs/umn/drs_online_migration.html index b664370dc..cd7f725c9 100644 --- a/docs/drs/umn/drs_online_migration.html +++ b/docs/drs/umn/drs_online_migration.html @@ -8,7 +8,7 @@
                          • From MySQL to DDM
                            • -
                          • From MySQL to GaussDB(for MySQL) Primary/Standby
                            +
                          • From MySQL to TaurusDB Cluster
                          • From MongoDB to DDS
                            • diff --git a/docs/drs/umn/drs_online_tag.html b/docs/drs/umn/drs_online_tag.html index 92bdb4174..b081a8dbc 100644 --- a/docs/drs/umn/drs_online_tag.html +++ b/docs/drs/umn/drs_online_tag.html @@ -4,13 +4,14 @@

                            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, and other cloud services manage their own tags. If you have to manage a large number of tasks, you can use different tags to identify and search for tasks.
                            • 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.
                            • Each DB instance can have up to 20 tags.
                            -

                            Adding a Tag

                            1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                            2. On the Basic Information tab, click the Tags tab.
                            3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                              -
                              • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, numbers, spaces, and the following characters: _ . : = + - @.
                              • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, numbers, spaces, and the following characters: _ . : / = + - @.
                              • The key of a tag cannot be _sys_enterprise_project_id. _sys_enterprise_project_id is a fixed tag of the enterprise project system and cannot be manually added.
                              +

                              Adding a Tag

                              1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                                +

                                • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, digits, spaces, and special characters _.:=+-@

                                  +
                                • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, digits, spaces, and special characters _.:=+-@
                                • The key of a tag cannot be _sys_enterprise_project_id, which is a fixed tag of the enterprise project system and cannot be manually added.

                              4. After a tag has been added, you can view and manage it on the Tags page.
                              -

                              Editing a Tag

                              1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags page, click Add/Edit Tags. In the displayed dialog box, modify the tag and click OK.
                              +

                              Editing a Tag

                              1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags page, click Add/Edit Tags. In the displayed dialog box, modify the tag and click OK.
                              -

                              Delete a Tag

                              1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                              4. After the tag is deleted, it will no longer be displayed on the Tags page.
                              +

                              Delete a Tag

                              1. On the Online Migration Management page, click the target migration task name in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                              4. After the tag is deleted, it will no longer be displayed on the Tags page.
                              diff --git a/docs/drs/umn/drs_synchronization_tag.html b/docs/drs/umn/drs_synchronization_tag.html index c2ceaeea4..7ef49fcdd 100644 --- a/docs/drs/umn/drs_synchronization_tag.html +++ b/docs/drs/umn/drs_synchronization_tag.html @@ -4,8 +4,9 @@

                              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, and other cloud services manage their own tags. If you have to manage a large number of tasks, you can use different tags to identify and search for tasks.
                              • 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.
                              • Each DB instance can have up to 20 tags.
                              -

                              Adding a Tag

                              1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                                -
                                • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, numbers, spaces, and the following characters: _ . : = + - @.
                                • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, numbers, spaces, and the following characters: _ . : / = + - @.
                                • The key of a tag cannot be _sys_enterprise_project_id. _sys_enterprise_project_id is a fixed tag of the enterprise project system and cannot be manually added.
                                +

                                Adding a Tag

                                1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                2. On the Basic Information tab, click the Tags tab.
                                3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                                  +

                                  • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, digits, spaces, and special characters _.:=+-@

                                    +
                                  • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, digits, spaces, and special characters _.:=+-@
                                  • The key of a tag cannot be _sys_enterprise_project_id, which is a fixed tag of the enterprise project system and cannot be manually added.

                                4. After a tag has been added, you can view and manage it on the Tags page.

                                Editing a Tag

                                1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
                                2. On the Basic Information tab, click the Tags tab.
                                3. On the Tags page, click Add/Edit Tags. In the displayed dialog box, modify the tag and click OK.
                                diff --git a/docs/drs/umn/en-us_image_0000001320979513.png b/docs/drs/umn/en-us_image_0000001320979513.png new file mode 100644 index 0000000000000000000000000000000000000000..9de4b86313e980a7261d2a48a0d06a20501c0646 GIT binary patch literal 444 zcmV;t0YmPx#1ZP1_K>z@;j|==^1poj532;bRa{vGmbN~PnbOGLGA9w%&0Z~arK~y+T#gnab zgfI}r`(Gmv5itlv1O|bKz?`T+U?UKi6BQ8{#EA$DA|fK@T>`llj*pwUcBXG;XCQg| zTgYxc@W=WepfwuW*zk6)L!cccsv}9(Wvcj>RuoxbFn$jfVxHIO~jc@SbLUgQ5Naq zC{BR=g*XENmnRL7Jb+#T2h@o(kPG^-vMXy`BYZO+ao7|I?klFkq2Jf9fG@^ogkak< zIac@pCS2x^R!z~(JTh6U!^*LAn@wKUti3BBY=?51F@}0)1|PDj2J>G>N_0=QHPFd) z7bM;sQRJ1xuuQN6WR-(X`w2e#ZP5+T%iP>;pgt)?OhMztySqi=wmPx#1ZP1_K>z@;j|==^1poj532;bRa{vGi!~g&e!~vBn4jTXf0e?wEK~zXfWBd;U z3{(b8P@1ZMEJI(Pn8r}vwu0gISEv9QAldt`_jNE7EqKbnz{iyJBl z10X|*1+VtD|Bs2y`Cq;F#sB|bF8-fgnDak8XXgK_U!V%0fM`Qe41|F%hyS;siva;q zVG8rId_oOFi<3B1^d-aYo|Oz2S*025bzx#q05u#Z!0N*PFaGap0D3*C{r|34P$49M z*HCf{1Oc3el4~FcU^Vpp@gA}b1OY6De*Ay5E9ZaAyo*pi2oP@|2w=wkuWJmaFEcP` zX(~VkfU(@z!Z7!dG(&Pn1%s<7R2UDy%u(0pGsLz(V6abhU=Y22j^W_B2Mo`C6K^00 zU>f>x1w(r6QHGB|CYOjbgT9kFgTIX#ZU$Y09jamGCZPx#1ZP1_K>z@;j|==^1poj532;bRa{vGi!~g&e!~vBn4jTXf0e?wEK~zXfWBd;U z3{(b8P@1ZMEJI(Pn8r}vwu0gISEv9QAldt`_jNE7EqKbnz{iyJBl z10X|*1+VtD|Bs2y`Cq;F#sB|bF8-fgnDak8XXgK_U!V%0fM`Qe41|F%hyS;siva;q zVG8rId_oOFi<3B1^d-aYo|Oz2S*025bzx#q05u#Z!0N*PFaGap0D3*C{r|34P$49M z*HCf{1Oc3el4~FcU^Vpp@gA}b1OY6De*Ay5E9ZaAyo*pi2oP@|2w=wkuWJmaFEcP` zX(~VkfU(@z!Z7!dG(&Pn1%s<7R2UDy%u(0pGsLz(V6abhU=Y22j^W_B2Mo`C6K^00 zU>f>x1w(r6QHGB|CYOjbgT9kFgTIX#ZU$Y09jamGCZNn{1`ISV`@iy0XB4ude`@%$AjK*4%X7sn6_|E*U7`5F{>m;>H>*?U5Q23LFT>teWpK@blt&n-1p)$lQj#J<+#EExymjGl?8IV zU!b|CJIEloZT%#h?Mh)LVvcM772P$8ag7fQ`5Ruh!R6tz$TS=GK-=!C-$IsZv*f+u bSv-^bme_BBg~uL)e8b@B>gTe~DWM4f`2e7D%F2O(yu7@Ef`TF#C@Co^gMo^QimIxrnwpwA7-(o{XliO|X=!PL zfsT%juCA`0o}RwGz5y5*8X6iI85tWJo0yoGnwpxKnVFlLTUc0FT3T9JSy@|K+kkCcvmzTGP*6~CaBxUSNN8wiSXfv@L_}m{WK>jCbaZq~OiWx{Tzq_dLPA1fVq$V~a!N`{ zYHDg)T3SX%MrLMaR#sMac6M%VZeCtqetv#oVPR2GQAtTjX=!O$Sy@FzMP+4WRaI3@ zO-*fWZGC-xLqkJTQ&V$ub4yE0TU%RudwXYRXIEEOPft&8Z*PBp|AYw>CQX_&dGh3` zQ>RX!K7GcF8M9{1nmv2=+_`h-&!4|w!GcAL7A;=9cQ>uk5sDH4e!pN zM?2c%!f)$Moqn;JbAR{#-LH2<-aWd<6M=_Uy)Vz z>Gb1s+(~DB#NsS6_)g4`cRj>@b~4MGr%TsH2#HlrdJFVdQ&MBb@08(^UA^-pY literal 0 HcmV?d00001 diff --git a/docs/drs/umn/en-us_image_0000001710471120.png b/docs/drs/umn/en-us_image_0000001710471120.png new file mode 100644 index 0000000000000000000000000000000000000000..fade3839972f4bee25a9008dac8575d920e45390 GIT binary patch literal 27150 zcmd432UJtt+AbPJL_x$)MN|x^sHh0o0O?=>6af(dAruwq1dtX<2%*>&uuxP=klqqN zQXmi_qM#tX1QL>thH)`ea-KMz2+@0%3A*x+qyWeNaP zCdsVcmK49<9Bknf3IJ^Vvi7?!MQy7h0N|T@`J(BK`)(|nT$KG{=D5ga(}NA0mM?r3 zZ8-Vl%0c1goB5ccuW>1_?zC=UeQOEQ>mMA<*QQ!Tx99v= z=;&_gZ1^kL&-bsAZK7KM)BW3ok8WA)H`yeL9v8If{@fn;I{o*Nq0o8g)B)ZqaXbsw z&f^QBNQ}_HmP<+N#8U*sbWV+k)+P%89JmxLxAxcM+h0QxYX{pxHi$1+{PSR6gW;cp z1Lpq|6L=hd+}&Z2QRnjW?{f#|CqGvbg%=7IU(>klQq4n5qhns=om(m-c}cj}{%2^I zi`XfhK5j=45LYM^Y*5tBBN=N6xk?6L%~b{wS2~xRsgLOTc!p0=I3iaW6y=$>XyacS zJt{)$-Q~+6aiWTuy@<8@0|2Bw2ek^ugT7ZHMc`sVk2~!SGCkR&L*Vg{r5j8^roT1Y zYKiy7k2#Nhsuw0N@vWQ^3}^9F@EzL%LAi)y28j~RtB{@Dtl#Gs6f9Z(S)0ztdz@5c ze|Zvod45@YK;|ue+Tf>+)zvpg?o#4OXIeJq6|UI*D&;OYfp9A?+v-D$1j1=s?L)Q5 z{KCb`oVaz`u$5~}%fFZGNqlv9Yg#t*KJ95JS1^vFa_IV>1M7`iqh}!c(`xSf{L)+e z!BjSs-#|(qc5Zcdaq#5?p{isQG$?t@jnu|@Y4CkFJKoZJLRDHD@?_vkL&B{LPuVGd zV<;w#uwpkeCNY{1iD5I`j`3L-C?i>OSp5ZM)jlD~=r=O#Ss$s9rm2 z&MYV&F^1lMM1362ArJWbCk=3hbbkN~8_hcg!1Plq@lw)t9bp6X6_zc&gHach*TzlN zWdYL*-IsdVLYFLfHLDuDP@fwOw+j$DnhnBx9urvpuvQ1<0O1eB(&Bke_1)UYH6Ms6 z)nu#l3Oihad6li$?(>(B-qTgQEFT!*SA66|X2 zu&OfV^E1&{ezNk5La6D4XgNq{FiF&m;x@Yh%0FFiU?o0#!{yn~d_+rW_-gQKV=3R| zmX#?1znX-s=@YhPbfu291%aWKP!i7wjeXQ4!);W)`jNECzDTVsq+9Kf{7G5` zV-1&^cMPd-LI_pKwX9t)EFklsZt&)scz%ua(|(`yAQGfEOW3}Mn-03dQsgCkB=NhH z__sirq>If(r6e{>H1lSJ>rEF5Scv1eXM)0MW8tWSqWj5DsnF&Xs@O&H6)Mzb@H=@V z;>y^8T0Zvx8y72u@Wzw|bgoi%c(d9T`?#udt|LbCqM3RUlgN=@Te+9#e(f4!#zNg; zm>7HO1eppU+238(^%c5Ql}G!&rJd30_(;6vxGuEM+k2YF2Kw$1@T+gP(;8hZ zmlKJqU|zjl#KOQHK0N$ghebGzY%Xhwe^b~_HPh_O`Uy5yUzDEi^Fxo?WEgnsy3L3# zUm_A`t+AO#q4dS|odlFsQbE|A)V6fp&n&x!nJ`5iXpBAiEWv>(tK2_O=6iuAA#sVX zy`Q*vp-B2MuIO_1&w5QQkGWPg+cC~J^WCy{KRMk6w>!+i6El4G72n{^b=>@-C z1fNVauw!WruF?mlH6h1aB$gBj@(qy zjN<(hld|15uM2OrsafrG;|3c8dAD5fDp5SSXD*z05wG01lC$bm!zwcv9s3i^wqJO@ zt=xNoLteloBv_f&7xlUE29tm(Ki7B7yUhS~-B+MJ^7oBa7tizgg-5jHL?bq;l%fw- z>WrSk-xLO1WCl?d5I*iDKhMTa0zVAgjOVI3T#}TqIyG0W1NZ963drur_4v@C)EOdG zvNvGjr4ZeUfMHf2w#wNJO{P9=7Pg&($UKCeJ^>1^pt)^cTickdQ2RLktj9(|;G!{H zkX>sodZF-zBurO9r$oi+*u*I{JT*>q!$GJJb_AIZD9N+@|Rt!8r%(AHQ&HVGeXp(#tWrr2Nd>Q&nSO~Kr zfPIt~&PJnpT*IcZj1rU1c@a=qthHum;gQzPVP4JgFp*5-mt* z-Zb_QjlS}y87}Ybm3QHd`U^P-o&;z`Q_AIVjM5{Wz+M1sRTDo*R#vMrhE93Fn6!@R z=^7b!7BqoLM;NYivxz6+f^U`f=%1&JE+#LP{fOo^ixxd#OMK-Tfo~+=)Y4th9n80( zd#j5U9)LKCNu(eVhY@v$s%A}DmQkSD{GPnLD4GmrWs16S~jWr$Lg7zHTCO;YkVKqJE==^{NByia14247Gc3q` zALP1r0|74Zd&|e_=vU+h`3<6>KzH%>WzWO~{`n03sI)so+2L_XM>S*8(J?&Sj!fiF z%^4poXZ6GWSP*uo^MKjNN!X-!3cHXO)@ioY3U9pX9BV}g4DMO~$HqnSpG635?vE#L z(vAE3>*o`PmDX%xUaC|}tsU(Dy@~zbnK0)#L&ggNqEKz&h^D5}2XW5wGON~9edsZSDW^XEW7k%R>4&%%jy|tpwGKjM@8|8X zTPr5irRP?-W@-gqOCR|v$c~-vwc~W%UkK`99qpTuP6=9P3n&%7?jJRier{hKhp$8y2>Tkm{f%J;*Xb)snB;F&;ib^5P}(%vNW?PVQmN)HX$XKM6H$YW-eL z?RTKJ9j6^**PLI-CIfXs}0yFVh zA>)~u9Ph@$NdvzpD~7VhL~8Uh#XO?A3&i~>sB>X9H|_{mgs~Fxsoq1o}Z-}X0?kV={n5CzU zhP=rLCNP&(=gcWJ{s<0loOZxcbfN=-%Jc%_IrWTaQFe7O=puH71p;z^t$_p*6{?y$#)Kd z4+=Y1sty9_!;;+bbetiB%2kl&J3;$XSTuEe^t|-Up2OOlbRKn;{|H1QSfxQVGSG9< zJn|q>hJ)8k+gcUd*Vl$z4)erj{!sSP!EBnQ8arTd-mn7r?FKS>%gInxYKDFtT0OfZO+2_Rsz`V)?0rhub#Y2um4d4eoG2_fZhk0k0a_Z zu<=fBz*+h_oGMrlR|WSZbhv$}KWVl|v5+d^?8q@Rq?R!F-;U?PZAwgFOo>uO-X)&X z7%kPWwjbUZM!mGtHp#q{y4yo#-p0w^^FmKc%43w#NE{F~(;*R5cSMcx%sH#7t6p@2 zW9R^`h_As%lHVAS548@|G|-D?@U(TZ@-SA|WEznJOLaxsdUAw!O7pFHmWLAx*;p%( zCiu+CctSxFclrlbAJIW&)JS@P@PpbqM8U#c$B~QaBbid6K}>HcvXG+fJ@gCCq2Kpa zrV89@GP%3_)m_i6&N`GT84csd2gSI{>R4kB z;#uok=eHIpLZr~29*t&UdlsRzL!2?+hvp+O z&oqF%CKirap(DZ-%wKITUtWEBPKu(}RO~w`B+xTHN44s~KbPd#Ke*4qmP23451so0 ze}=iIqE6OlKrZf!xA@}^7TBE6rV*>3jPUHN7Q0l$$Vq*~fDD>ADQ2wSu#rN=y3n%4umk?r2$`rM zKN8yD_LO30m>8fEN1A6nJ##&%FOoftWnY4Rmf0x`_AWdz>6dZa7%9nV1V)DNkLlBj z*keMUGvS2@TJ&75`&n7Vy6ptDTab&HnFc^GmDOdGiIoUi<_L0SBPzPoDx?w~x;=mt zC+JX*?A$sNm!9eNA-de&-h1%dtU4&hL)XFAZRRKGg$l2}uNHhMcppRmwxI5t$`egH zBHYgkE*MlBYaZ7RvU%~rmXg37ynujTs@4re^M^xEvX5A`y&YH7z(z;L#<4?zXX{kp*ZGm_ z9`Fh;ZL_oEX2FA@d2J3nN7<=V`fZ^($0Fvp4{`<6U?_y~FZk1bhL+orR~vDqzbg7J zGGB9^c2rKC#fo_XOtLbXi%4lR9tF=p|GzC#A2~iWK?Q7q1hp`_u|V-F@R$q_0*)_OEPv zxfX1t!!2>R8feIbp-PNe&CGNUI{*G9ui5_cy537V5t7;`L@$6t zgk~A@I(0Iq(q?Oh@B7j3EmPjIeNr@jR=KDbcebMzV`JJ%UpB+u#GQAYm+Bid_tZ+2 z&$q0{M3()^o(&6*S_s#Jj4neTsYr1=dy~GjUgt<5 z^F4bsNU$;$IeXcLaz!C7^j?go=LYXz-Z+2np7FIF=+}WoDKX|s&M>+KQmZ@2{?f%h zHr5|hozQOVr5`x)FN)51d#s|Al)M?^Jo9Pjo5|n7*YN_Z%U(*y3 z#D3g_M`Bmia5S>n&OF$Ofjlq0X=)_`ieQ z)sz@yZss>kdeb=d|aCy#)=mvi(rs2SdNAgz4TPiu1 z-hqK?nwtiee?C3heB^wa5;dwCDZk7Ckr0nrMrXcI$p(sNXR28XMhx@tNr%%B8L~b@ zo*YrZPzzoOXN0%Lc4w$?f0onnJe?r?TpN;-6*?Hvc$9M=N-e?^c>HCB%!pFF>F%qH z7JM?At52I_HG@0b?53L>jGOoCI|_I|i>?zqe26A9+wgehC zG~K=HE;O{NYX}4u(xp7vE`7TAaL%6An%j4Ks(=SEPy^{l0~3{~AQh_27ltUW!EDIr zI}E|$1H*e+{&>V(MpY=ZQ!^}Q!5t^P2G=8@ICB0 z!Jh<)(f#PVAmT_^h0O=6TK_s(qnUc5uv8GyRlCdV(q!8j(-3y!3K=1-8HrhqMBmpX zh9?Nh?!1Ky>J@Wwe|P7d@{Zcy543NkHlb7l1`>8`p8nJ3)8dBf^L=Pz`lDxH-pk_l zHD7UhVg?l8cY8>C%UVeOikIsSrE0Kj%TSJplLSN|YNla(@Md0t@%lbpO$ z(fw?HJydj}Hh4A;XmG<55{2%)Zs$?Tr&lrU)YR1%o43g&tBI#?@7O9YhInG~@T@nP zxZk5lO6TomZDuQk5K|w-xS=2N`wVEY3B>Ih1E=cxyp&Z;^+qg7F)#}YLg9O`N_CQP zi##BPUQ#+LO&FB`ymq#?#|nCq(qQjKt+<&8p6KT6m(Beo#2T?fdGglTUU3` zA+)T2C69X#wJdg&+ZV(vjfL}622P0g)V@EnpWjkeTjoxR7G_u`?$ezTZUw&gzC?Zz z9&0Ry8wR$C-SV{qTyTs^06(^R7xhMV@7Ycyw5G!*^Nx+ttZLxf$c`|?aj|Lj-=?(L z5eLMtyo7y5y-0DAe3`KZR9#j-j1{-&R*TKz8NA*h=GgZ8ddeyVNJ!lscs13rdJNUW zp_6LH$ZXAj4%!dUtWef3_(XRibxkpCR_w}q7lw&ef#)FX3}dmU>^JyxW;HEr5^edb zei@EiEx0qP7%_G=*LZxpB-fLJ5I2s?Selk#J~cg^)gj(Uo8-iRn#pxVEx&5`2(Nxh za%PnK!<}?XIV}kPM%4y%p>Yqj7D7^w94+Lw7z=-}vyA$TjKe>YcCB4tp399lmlXcR zANpS9a-Sn28)ew|L9suq7JI3fZ^82s<4S7B>f5hhzrI>rIr!hWf!pZn@_fY9jd*6F zn0hPE_s-*o>Lm^v36DAg0MJr&s@mF?p0K}eXQzH9G+S25pvW>-y!A{D9{68_fdAs$ z;zj>|fD$chCT86sSDc*QrKF~=cmMzkO21=gn@>ps793pLBz$ZBmq_D(Fvvemu4_P7 z$(h$39K7=L^MyC5)>>x=2oP;&v1^Hm&1{{$$-18kXs5nzyqm|j`&_INx&O|EwHRQV ztoDAvCs@>^NgmAmwOKoA>DnKAy{M%pVERW|{c67ElHKR0|5!J@XCar~D6vxA-4U<1 z>;??at#<}>*{^NC^EEk}dH)W9{tMmvWKbLfh77^3QM<(UfYE2?)@F~HoF1&=_Luil zbCZlcW$G7IxsMU6hOikqr7B}lsmK$iCijO%#UzDX;;r2pObL5wGi+>7ft8Ogon5E>W?7P4=R8D{JDhO!^{uedl{zck#t5 zjjspnQ)55f9R)4c8RsT7yL6SKFnujXM|sVZ zeuo6xgMCL1Uua9^Z^>NRR~gL}Gq_9TlwIZX5|z&vYklPy=Bx09S#AE^W{tGvMBo_; z5_;LsucWP>7s#JWtG}ft9F^5y89as9`ttr!$1fUty6t#-^k#MM2&R+Owu=|#%cYte z{^6)r`0N*dR;=zB+DwWQ#Mx`i1Ytd%VT{OnE|2=P3V1)UPKSvAdEx0d?vP)oEfl(4 z-ZT56wlFf*E|)cgZAMBT(rA&NxSXMEvZF=bQ01#-Fd_Mucpp27bB%GocHe8YGYJp< z2KsjvNIG~lsh?5$B*rU|QdE|85hvi7^{IKiud{1v#Tt{LbWp-py+ouzdzET4M ze~NiA2A^cYkHAxX?Nq6sVkKPszv$C1g*Ap>(k=*27HL=|0!ynBI6)D}(sIZa)f5+R ziPNX+I%Z#4)%|o<+im#SXsE6Ygzm4OS*F&JL9B(zjrz3CTdFo$5gY_)(keA2WzsLN zPx4A#QV`kZXb94H$!LK#O@n-b8-ei)soU|>fgJsnyL^qb*{6w_TvwzW2OlK59W-@` z^LA8Q`7wd8!-0FdrjLwVNac8pw`b0CA*=G^PXcJ%Vphq(IFT@sSXkex2}R}$e;>nl zc(-TV8$aJaY#KrRojx6GzbHR$o{HD(N|jB7`H!3XH(zWP5I?rjD}BO{yaL6b;O5^w znJ^c!Cd+$lKe73crKM$6f~RuLylHFVOuK*Pg;&)D+^rs{H{f|iX|PP}raHv5dfs0YCxccDM{kaPWfb)eLK-4h3yml5Q*i%IjOzVoU=#~=-2jfIh-3XQe&^2rFn zkSKz|(Ln?y8e`$W?>n~Jo6nhic@!c!D%~QVtajA#kaCNB<)mND!9V>@;Xb{vZ)S=6 zCX=w>bVwyVSa2Uv1{SXy#K!VRyHb=>Q$BmomF$$7=)e}MepPG|mHl!kAnn$4*N$Dp z=i!v`!uy-QoJ63GTzR`-ClgP6uz=R22iE8g2J%OqH$nON8+3Xi*yymHuvbh$N0uSS z^SoV|kIM(v+?ZCDA=5MQ!cd)Q{6+#CCTdg<FDj^vuv-=FfzR*Y!{A5ts7t4Ke(5D2h_d?N6?YkB@p3(?wg^9lRE^WJu=k9Uh z7t9?_G_$AB#%}C==48|3`~0Zx)=hm{=E%`dyFlFS3-i-6Km8O(!R1rmY^hbe7^~Xc z-Xkvh?X4EP|8ZKStA}}=XFTV?>%^yi{DS+NxhNfl+K$jN zT)VV+Qdq0Pt``+|$}8@*4XlT>Pej@MqRp*Z*w`cy0)n?jWzTCbLNj=*!T{s2Ie#_iFdDHC5d_DP<%A*=VZN%!iQnc^~ z+#0TV<)Zz|uG#L{G#^f`;2CD|O{U{??&&6<@vAce^V&z4@>k@MncI;Xc1kZ_v4ITz zq1pBh#b2jwGx54~y`DP%e1s^P%_ol={%m`W>(Fbe%#xYd=UEmcTEU}D!caT`Zge#= zQ(2i1X2!59(|fIYs3h@s>=W7l^3iK(3!`MUJ3W0Nmp(&U86Owz9A$D%wceLVvXH6$ z84Za_xIxA-cO)oEnP$au^}gTLvm~ zUDxLdF3)fO{!OqmT>VB)-d-o$oIHv>3wFrx>D&uQYyuajdExQa%Bu19$R2; zQ*?dvf>1yk2VZ_DMNHZVcYtf!+ncBJU>Rw9a1aA*LO_rxV2KY}(BPMj*gWji_My9X%KSD^N$ySiS^^T+X9S-t^b?{b_~li!)=&R@l# zPhZ5wY(VXrq#MYGVK^valJwSBIV=y*_*D@3+V908aFN#WCE?i(%;Ffm2DOVm&gir* z=HBbAH~jf7qw?B!3>7+c^~%H8C7$_)evzeUbmb|@4K)@~YeD52I@`sxCTH9hJ+bEl zVcbm%c4fhi_~n?z%dniIv9_%8qEsR>&GhRP*Xo5(8PQyM&|rEHD)i}Ng6yT9(`R-Z zzUWQdFgG%1vkI>Bkc}=VrUdt4N{`I2u%z(K*ZeV=GH#!XFREpKx#k)d7T0{`U4h2l zzG!CE7UhUzJ7gzzXU%e#@f`RtcUgxM5TaG2Q1{~e(_a?lF}con`^=ip(|X-Ni#QT0 zfj!SOq;${0Ui40&%C9<7dxF2IeaXAO8P#vAP;#^09elx6E!Xy^sn+8LE>HQ~bZSz8 zN~>9xG77k(kDxYk4K+KZgJ9LGS&^6d<)!KEjX)%ORywsfH9gbwO;Amj{1-P~yKT6N z|7B)<)rYc3k_x*ve3)l);r9l*sG^XG3P9GCs$@X~`}|T)V{mR}hCPjXukIHPZmMymGV8UZu$N z1}ppYmcFQnWHzwJP`z89>TZ=j}HC$M6cYd?&|Pe!X+I(2pUmrE4M) zq|@`(WGfq5GnZ{R4D2vvM;`)GeUg`s#~QCVB`^=>!^jw5_+dL10+xJE?XLv0=9}tA z8|ru^u^;TkuW?o2dZ&9A*xWVgIPrl4 z)po4##SPv(_UfVBuKFjq+=~^H(KYLAL6Tt|X#^~5h)8A?ZcrG&vGi$rc1IY$jhZ!r z-lg_luVCm4q5Bh*&K+zxW#AIN@Golyb?Qtz1XB23vLL{<+ncxYUH5k8V-GDkB@Z2{Yv({Fx&G!E3lNGu%HC}_SA3FV#VIH&G#ptv%h!4 z{HTPtcurC9yLvxIRW}5Rnz%jA2Eq#08i!6ivHsLHN@ewATD2aZKf(A&6Vw+geahJd z2*1=NL@}<7We(MdGacPd4nF8o-)4CDY!6k(@Z$NWR(1u@$q!0<9oH8>&br8cuCyzp zpI_?iX87Xb9+>5olPOOo*Bu7o0wFd=_P5P0GuLrKCyo{9Xu45I(`!$)R3Rgg~hnNJBSgG6IH_g0h9<96*ogB%m?S5mE@-Ao)*9fc<(!Fid zG=U!Qf;WZMgUz6bYEFLf{+GX;0m*wN`4j@Uuoig@yQ+tKHU8vi1KEhFe@(WsT@lWh z+Fk@NE*ju)mpgx|XrDXNlMZP&e064SwUfKpncklYX03Mi#DesX@VUwuh)(qH#7I9s z_u9yAS$e%!4P1jkXfztEqyptU4^6ohp&=`VogUa`R}{Xz)Pmq{E0+BC^gwvLA>6no4(4OTF{fPyAOoF;x8MM*nU(5ZZ#ZK zIcLRz4YHl>Z&abtDSA?i3wI@zDu)|%p8Su+t!9fnm?3g8R(A)KB$W7TiTZa$3c6wrt8_2fr`_2CFyhC zDa_M#6AX4_+&&GnfW#=7)vPz!Esirv8+e8RQ!G5; z@!PP+;Y^*u7BVBGe373qTM!rp*p_hmSI{b3z-?x@ZL?$P#VlouN8Tg;-oER7hfag1 z?((NNLmuuK5$UyzqglO&&0K|IG>5YWb$)*M-wM2Hlw{dbvU_hmmQ$V;!)L^lxj55z zt8OO=;#CBg9CbW9*~O?a4ktA9qZmGmi-oJl#2BH4>7YUZ-D}UDS-6Fx%?N}&k|egy z&i!L99xCSUd8OTmeRh9vRD+kW|5i-)PyFV;*PH#nG5I$XNPo(Idfd`_fNAgLEx25{ z`{aqXUFtvZPvcis>;Qo36}@DsgGc^}of_^PDi{28138n)V+<-|PT#Dx1rk_TBf1_Ia!Sl$@yU>PJpLeyXkqcessGOY7$dJn* z>c-da(2pN0L61&_uiHN>_KUi^>W>jD+^&sah4dW6 zV!>kEb!iPne63xbRCX^*8~h&SjBP>o{QmNE2bai!m)AJx_6NGP4BW6p9SCvl^D(EU z`c-*%WYG+4S|#7*G{wL8XedSv4GTa&*BoYd=p$k4bHhbz$cek{( zjNS8GYPtLT*|Q;x1sJTj={XL){4H{C+%BN3CUN04c<|%bv9|Q_G0E|0%%}u7Uzt!4 zKdC-`$x?2;v&LIAZ)` z)dVT+1{#x`k}hJb^yAB_s|Qlm zL1Sb7iYRquA9X=zbcPX}LL`kHGklVvpl;Y1=8Cs5TE07PGy!!ZgcXYd0caezd-n&I zt~?^R`3k4FV|k`guC}8DQ=OOh1xXG25%xmM#<#HBhsCVEH!`HR5*-$mdcx_Kk&S<= zl-?V3>E~e-o*u&A6`-^9LV6m+b$jx|9FVQ=@^!erDO%{5!o6SGcz`;oIcWQMEAS(n z&&9smOpBUt)4ua%6Hl)w+~Kp*^KaqyrKlfA1|BuZZ`$y#!p(o1jJvS7OS2=c8x=}%IN3u4E;>^Fo7NNQNGK3va;b+thssx0FTdxSW*Un_ zEtsHO&Um*6)O%sGq`NCOZUj6CxnzDgq~_qc2yv?oL4dlAB>A}>g&w>2rTI`m^=Brb zR#pk1Bbz3$aH9AwCn)N;b-_$~&dLD@mfaDpj(6U_c{7rPwb~p3*?^}=VVjC!H!*By zV4rhAK45sz8;Mn39hTzGwQANj-0-1i1mVLjzKBtArPD!o<&{)Se@@lwP&MwLs)K-;%I?`S5qxZymOUG+F=)fD# zYePm`)CiH`4^Hn1AAgod`6Z@@96L7|d0(68oU<#qdT-A?nAR88-y0>;6+%#o3rt~! zyRyE`y_$S19W&Lg9QMv$q3ythN7a$t4$y3L)_bKbrjFMEl{qedl~yFHg>A_tA`2$9 zHxQE&b zo>!(;@~@sqy_$ytOWfYps-^5AM=-i!B0I5S`@!yEhXqQValLin!b2mP`*Dg_=jR^r zto^U4-#dPBBPPIHW*R_{68Aouj+i>EDMCfLNcG{vhwPxcCpGlAUB@>%gX;5d_Jl9K zf6^a%zS$z>z$~IOx!l4sv<=Pr|_24#xOZM|A>kNfUBd0uX z0za^hsYny<7OQ1GYTwY-vNN2M${y{;?F=YVd+P&xMO#>?NnR&q{5bc;Mb|D2Tc1-m zLP)w~gvG91N+(^boSh7P`DzRtp z8BB`O#NHdF*DA6eO-)T%=gR|rl@rgJi7{)u%LjNTU(&ZK(Raqg5GVyUp5O|H3h>Z$_~7=qnLCw*?vIog>m9BKsJ8LPw8#4P3s?mDO>0N44w5Klp+7dcp2u2 zV`lyD2Shi|h<@bG=j$4~1G+v(rJpM*HODa&F{tkIyEmx7fM|EO5zKV6GxEjPHOy_|JG+v9o`ZRh;S zAG?Nn$kU&6=N)X0VzF3U@Xzz0$~zB@B~5Nl5a7R_s+N8D(12XOKj5finDwPg4-FSO zFNjIe;VBuGAy1;GN8nh=Ow0PUCfTokATH_lPv6gWTmP-S9e3C=bs$4GR9yavXR$_| zK~>}U+8bz;EQByJ-5~O#Vy_^A*^knOai_;-zp<-dwfepLhW49MQuxu64Lcsk+tjqq z#kC9FWAfX;6;Ftk=rH03^oA!J9nIV{b}8bGJ@iAQ>E7(K7bYz$qE7g3ikY!k2ziJD zPCwpAgqTpJ3-Cip5C&XlN^g5j(krA@k1~A0R%gTfqS7m*PKby~(E*t3h~w`DQ!wAf zN!x?Za8hKtG6tnR%;e1Y1x=(+EzG?-6Tw^F|OoH!LZg@gqD~vJAS$Ed(~Hynf+?Vj#cL5%nH%}i;$pfLo>9C@cj9!x-ia9L89C$Ciner}jyC_ne1%VaWP14CozD8_ zQO*tAvvsR;t-_4N=hLYr;yVC%4YEm5+Zj_DF8r$C9uQ6XmU_=#JEBRPo^#m<^JCxS z0-fHAOI@az!LD}MzTw{zHN@`7?m@5>EmUQ)LHj-0^xa%{zNJ7Hu>BH7KYHjLfy=@jSsZH zE`u;XT9H)u^)h}-u)Yewp5Ezg*ERy3B)0CK#YAM5>@NwdB8bi$ zoj86gsSaYaHyqgZ<40ZDCsa5l(EI3HM?Atd&Bd7=`#n;=*SFA7QQNdLk7*c(<^tsxlsZ?!zDvcZ{WaA5id|!mccm#51bV!Zyf6RFp05;U z)dR;&SxfD|hY8Otd3aUbqhV2yBw9*plVtZ71(ycqQLHPhu=P^B^hMTnsj`Wn>U&5d4X2nNLynD{zLlb-lzO}L}9UPE4kuv8x|&Rvf|Y-}BFN7yW4 zra_8!#$5btvgPddW{v#Bk{bIQ#+%e=MERgj(?DE-cg>eTrYUTq*^2=(=+-0nL9Qp@ zvUZi8N7yJ^0!+qT6AVrciW?$5vA|`UwOD*`ff|DNxWkpuu6@Wsz5KMhA;4UVvaLjryMl z{r_8L1KG#}01g4>J}r&B6-U!j^jNIH|L2cI{aea<;uSQyPL1)gvHh&}irt+aWA(Nx z&r}EAezq0vToZ<@C0JknT0syZ&aoE33<)=w0GtkOMy0;V9JP7cR!PwVk$%E!IrQ2! zpy1*k7@&u1iw4B}?(H*p8Mtg{qQwNZ#av>BVH}Kh{Ub*~<^UGaEZ6xCV^N(V;K7BQ z6g6l%;fxn!>D}NNW_puIK+=|VY<(uLHvLpJtK!k4jfj@R^78WB&I@uiB*1Is2Ke@B z=LW**9qZR;kK39`W$RXxXPP9!ij!_v*+3YVGdBm@C73 zS?+na5b=xpZ?uK;s$OqI!j=P@hCLRk0xw=&_X56(BHh0(TYUp>;-u&M76S!Mw`m)3 zX+(@&-(HA}rZ}LS*RJ`wX1&i^18tSAJ@{VBKVW%ow9T|y=;zX-B`Pk=3c0ZDi&O)@ zE^@vMjc&J+@j+xoj_pa;hoC`_!H=HYq0o--l6*a#Mwz+sbnpr{|L1J6@Q3zlNBLP< zKrr^NA=TJ?%QWZ6$Qr}BZz>uSTm2gQN|bu+iNY>h>F>ZinzG-)Vjzj#iTSrb6b5K zrdUg4shJLU9_g47L%)5lq9BBS#1BhnEwpE!O14UJAai%=++7OBS3|vjwkHfo+V2`T z7<#>V7{=hcU7d`$tGOAv3Gn^lu+iodH!D6}xpHOtp@LhmDNkH#xR|{}A~{W3Kg5zb zH|S)(+VbMAz;3&sXq+X`)prWRnW1y{)5;f%xIYX z!7oroRO_=J?S9NGeypz>LAQExu`jzr!Qf>DG0aIG2+p5fVaIVQiFNDO)O@PPfS)@${Ea5ImasNRko31M1WMyndN$BP%Q5HIdBad+ewA|0&m>At zTuTc^m6E3ll&`ghy18XBLl{alq;jNkecY{ZUeb`8K}J9Tfg|+m^uB)h%8beR{0==X zs%uU>egkV)LpHcMcU&T-G)e4p8?-R$J3>5Pm?~7`wnz3AFokO2JqPbeZFh&b%^$zv zPx}TtX@4(!oe8JYd2f%C^mKEQa*&!MI&9=hd~(4Cy!5ecj_-F4si4`v&6AYEV_~p3 z(BpozE3;`ahA2iy2JZ7>s{c5>S!v?5lVG5*aQMpsk`naDm z-U)9uhk3dJOn3+XEzh(XYUENP`+l1#<_H3{0e}fw?=vOTQ1*eP%m}f0?r6PK9e0JQ zy_g76SLJt0xZk-amPhml-Dj|Cc^YCp-~LxGrJ9tRF>rC~v|l$|OYTrLXPsDBcXK%v z7*SB!h1{Ml^!0VPZqU%QGjXm^EXCa%d299FRjRqT(fK1N1vviw&bl?7?Ys&5ztoF9 z;)Cor1U0!{iEmq#415Z0kleyUsTj;zwWCLajWc%#{pr@^)z^~!JF!a~4!EV6kdT00 zdj$K?*0l$)x4(!RznJzdMJ%gcF#G2-+W*NviV>?dFRQdYvVMCPzcZ<_LAcYZb&q3! zj@90v3q7ls#TwShHPP(Lv)9$X^2=?YS@K#^O9>IexU`?V){nO29mC=e%hr&0i@k*? zzh-SJ8nxbKd7U?|Gj;AAi*+-R|E#_wTx|>-t{b z+ZGjeZB5cMSHHmRlAUl~ZhkoUmM4=zu4S`Sjeopgo?CUP&e^UBU&>&!Xw8i+j_K)6 z&h3xFou65ru02ofOFv0QRsv|+ia|mVKDp5Dto5CS6l z{vly?O2|#r!l}%GMkAZ8I3KNIa@l}`_`AC1f>9jwWKv_0=erpR?8>oxi0fkNkhO&p zHa>>LPE8<@GOr7YzfK+Imwk}wQmM5tH)gLbyk4VZly6cw_fmtthjXJ~KYE>7uok6| z)$v<+B5Bak0zM{TLEsxbObgFfw?tLkMn84^_z~s4O4RXYS^F*{(_gKa&JDe*JkF}u zFKAjm)_c6OdG~BY`b?q#yV5>rLkAA{8yXokBb1>wPH%7sMCOX!uvJ$# z@}R2v03es1`yrXnh+%eBR87L9EiobCQY{bo=ME7IFGUO}MfqqZlbK~*y|Mh=J9}vv zw0p)tTVY!uPmdSFvyu5ctHi4#^0P8rou-g$+q8S}2)RJs+Ofuu!%&(h+yDKGTTdLa%8e zboq;Eqt6Ky)x#0x1@;2DL!Z84xqCObA)8hFW;a(g9~c-N9ffRPX}&#CHd%4fy(51x zwLYsk`us!{IZECk#U99r1YZ@KIu@!VCwHaqr`CJPw|KsT5e}Kc;%HyLDq4e3Olo!F zZI8>BQ|0IQaQKNwP71sR%?-P;TEW3N?c1k&6D4xU(mlLUR*v1u$@n?22b_uvgX^ON z(7bHUSlh+X^L_fq@vHs}T6@VFJ9nVBEPcyta!SwFaj(s2$dp`!R}}a`n*bo;HSRaI z3)d1;C&f4s9#Uz#ng`{t7=xJsZu&cOVN?~a#(nR=(49MXRwB(6hn69)*zd6V%0MLZ zfUoD_k!2Dm_r8U={-Mo`AimzGH~564Gk{Xgo)o?Eg0~Y8{qU!(T?dANR@J)EBhJzYzdnT$ywIMYX2W^S?Gq5=rS3 z60O;@gZbs0MOYexX9l@61ZHdqd0Pd(mFm>j(pOK!)>~ z?twejd=6>@2d<+EI}#09j4a2vP8`mMn3&lA;fBm)Jc<(9;Z#X1U%0bwPm6P$Uf2bq z5oxqLDt?=*zGHwXw7qCM9K00y?9>}?Fz#?6SSJ!^l<|mZ*%X>*?nT~Zmz-XWg+_v4 z=%XeByUmB&>`=lI@TnZTL^7fTU!Ta!($5sOR%+EQ77714&I`k zg^(#P0Is;GXpYmSp;F8%U*zh%&58g#Q6)J7%-iBh&J62`PyHPoXE9Sk)P~;pKCD1Q z2I+i;*A9iN0s=6#>CO-awRm-3?If2Y4(Kh_Wr2eo-j_Uy`wf1Cb{v#225z%kpq^aQ zQ;kcvOC}rJ2~|8{-gEjH)4+>zOon6pMa{|RTupUOhZLgcg9)ZTDfs+|$CYnr9=gD} z?2fGIH!EEQ&cWUKhH1;x+I`sUtxQ(hCYfkawItJ=8u+BTl~$nmuV*|}@v6}?I`OMj z$dzAJCU4&PdKtq4L4W&uc);n@Q#9g#JStkgY~zHDs?Pbs8HrVP0;$LHDQy2N{`jcP-N z3&qpHkDl6W9e9)a$a&K5ber$A%Gs1S*jeY0hA3@eHM5*bxkQ7eoPsAR?j_44x_GAo zb)B2H^7Zy7#hREMPYv8q1hZHqZ0Gogp$g*3VP^Xg!Zogl@WRc{%em+9uN$=;nt`QJ zR;Xmy9RG5;;O1T8?HEJ)JcBUsOpCO=C^;?hmX!0$NZ2POfyi7pyLfoV8ir5mdIaiD z(&sRrd0;*x2c0Va!iI{jvaeENte6y}$ZsF+#!SjcwPjU(a!dI01>y zne{?ll@VyVoSfX88kB=$?rHW;DxF9vES@=I^ORdyhd|RPNsfw=ed=#zsCh?Htwsj6 zZh%j_W&khORJl@Nzd-=w&uksvYv0;BzNKGnorIe9Csq-uIaj->P9X{=7v7^;rgd+T zVpdvux?RW105aZe<0{ow*BClDnfLbsSt$aCn3R{-BJK9+d+`cBQa@5;vrz4IUfEfdxdz`MSq`GrOAbuKZGn68J4GxJ?C;#mr~&*yC`KtfO84gsX=Um!{?olrV%}z1_u$~kS8D?Q zuqgK9H9B$PtWw^vpJ110oy&E<@hDNvW5&kTV4*0kJ!U~hEimIFoj(dxh@$Qw41nsS ztgIZ8*+ulzMlX|-mk0N$S!5uTrX2PykK}e;V%(@c%o=O7yoYPZ?Fzz}=4%^z$;-%_AhoA5~|AH|C;<=M7kNC2YpFuGub=<&vn5 z1B`Be@_27ro0wr*CPbyIDjt8xiV;A{J5alaPbh(Z@G@^^BT;ncLuw^)HV->Dj%AGV z=;-JKhlF%fTe5Xo-MXzel4Z>q>`mExQ6JYdYE6H7M3%^xW7M55R7gCBuY@X+Db3Sv z>)JXKJ{U9LHh2!(+KuE*O|DPeJ!YZhHRoyqbV>pvU%-7M>S!|eWwe48g%87Ux+jh9 z3XQ(tJPrZ0+4#tPQ! zXt_p3aNqc&72x7~y`g@0+w?n^v+iqUeEv~Qo`$1Fe3*|G>y?-m+s>R(NM;^NY#~fG zS%oDZ|BmVVLUeC(;k*E#->IT<;`z@x62Q5ULk}@*t zWDflBJ8S-5&4|zI1WPj9+~+{AQ@79jt$&C25nDKDn`XWnqIf+d zXGc;nrBt0?Tdjd8US$1T5tq3^U{Ef}AVMR@&6;E(qX+U7J@QhdvX5+>S^_N-AB*#v z(ydIOXbkH{79ThWUGGTIJ1^9b@Tg8Nl{TnDh{pvuemam znw6CvoSlN~{3_KlYI04)ve&PaWh;|jVG);!}Q z4f~dq><3PHrPv2d=qUp&c7_B7Fx8@ka(TXnbh2~*IedW}f8Bwow6vN??kIFM*$tPD z)T>QjR6N-O&7Nk|jXpGuiJk`>BK;sEyi}Udp9VpbywSI!Hpn%6h%xc-WO+DtxUM9g zJeInwJ-Wdqb5d92Zy>6?Xj%1G@kO|$btqkYg=t^y$TXBC$9M9v+MPdn%}3oH zYR<$nDAFm}4sDuYKiE73p>EYz-(!AAMz|1K7_`9Fugwh>b7{UeMYZJ zvaCC6kWqWTkBs>OGA7sC1{(;yw=X*g7)zp!=t#n<@Z6Ny7&XtJ@)dHj=eh0Oa<&z)8 zm*i2tO1-wR#~>h(dv+-se8cnco}~bi;|b*x1_!e0@VAne1MYwKcIh z#Bwe*j7>_aICAtTd)LAA>`|W}ho&=D>m}IRQ<;&$7q+|-vHkhOw%@JdHK;0+&pvT- z{(P2R{zs$ovUj8LFT21IA+-$`FkFUkzZXS6r;h$WW4$w(*Gwswo&uMhIY}*r^5)QT z)IjY-Lf;9R)eoiyFu4zihK?3(k@%g!stS=r`?;p-_Ia&r%$jC*+lsIKkA+s$_s}pr5$mFsSkcZJ8=n;CJ-cSsSA9z_~r-dzl){2Q# zaMe>iJ8lGURIU8IX?iuee4>x0`kppHJW^!cOr1ye-eZK$`tb@TLC!Su9Wlsj5dr~c zFSt9OwYMj0#X89iYmHUxQE?eG&CUmZBFAXq4R?Y2G7pHzTp2?OY8Il)mf-Wpv87EXM(;#!oCF{ls4J>SHV(X#EU(ZqDt}wriC&W61ujkqT5B{m^i;<%+N|r`ry5Kga*DL+=*u0~^uRKR z6qGePbwpeF$lF`h=IGB(3&~9FQ;f@B2;mxSqNrk8iuAI{UUxdUPNV@|UfwJKbyf0>E6moGsG|E4ndnnxT}be+GRC3=`fYzWM2J$1S0zyz!}$IRfz zmM$8Yy=6_*LN=hDZG_m$RE;xcbi&+7X;|*mJBZ>$xc5HS&u-!MJ(Qsxt&G(d>L&m< zU}*L{;p&xMDLbQVZfe?3PLEP&gEbDA}@HBc`~MEdyIsdt%gsR8>*gIa8+0Yijh`Q0Fw?8>FERCA?GP-kAu zxqL%#Th!1tr=h|Rzep$w_7mJWH`B^KslM{p!VO<~96;{&lQb+kO`IE_y#5JT*-U)w z>7~}^R|rI;yy=#&e}y_nPWNBGe)pfe%D;7q@88IMe1W*X82b3KE=b}-VN&Y5ekAdc zDTBf$E|y)WD>sF9M|!s+$i=UOhuCv!f*Q{woa&#d3baK0NaDD#LyQAh-phc zBm%2*-@ob`>|}Z!~XwFl&bArVuXV z_i~WjhmHP#t~hVVB&H&1{qN_1la;dr`*Dw+JZaKEy_D3hV7g_6#!|U zgW#vX+{i=VZA(3IJ0Hun={Y?wD@IH!-$<3MtvlFFv*UWe`hb_IXJ}m^p!Vte=1Ye@ zw;xY*Jo$Od^b3_2z1CXo9M1iS%nZ7M7M1v`z+2#e?Sr`D8qeAf87pEW*Xc4A*o z7O`Q!ohl^~W;1-!btrG_u8E?n`9R;tds>6sf+XU3sP+%NoZEpyRVV*-g}QaXRhOts6{E4MSLhF-jIe+^9*;W56ss8Tgc z$V3>=5iK4kmUKt@vYv+)58{qrj=lIJU&sdS;ZfSrOX+^J#={sX4MDa}_O>OT%Hbv_oF zN=ry&ozqb4cBi9aycD8)i5#jqbqyEHq>xsSLdK*!?iRUA$j!{n&F$uK8)t7+*~WQ^ z|Mwsrhdjyrb11)z_^O z6cI5o{ox>-e)x}HrP-)MyqS#Pp$5|beVR#g=nag@A1S*Pb#0=T!8n0#Xqg*`xI%-y zT+a9#$nrmZN||uL`V$5UAPthk*Pvg6+~ir%0O zEE8}R6t(~FOk6Q#0vjw!W{(RqFOL#&oBuhXQVhg39}N=OfS(^Zrcg3q{PU2|Ah+!` zF4Oa3cer+n5Fo+Ad@knQf0t5ub$;5f^Z-)6a+Lk2dzq`RQUBharlB6~|292ojD)DW z7fl{_xbEKPHX`$9q~utFHPi8wSOW*`PivE_MIFj25pj`ydEIyC)PYtyetsfy@!2uI z*c}H~Ov3lw{$955o&`#PikU+HvBtR7qa(hw`sn9rsvQsZ`9xmq&md{}gBvxq-`5U9 z3fP|y{r&D9YTx_c#;A}qREadOP;=o|LhL0#RwmL#*^WP8c;_?W_YVhHC?1^+WIK$E zpuyio)E)l+^!f(IXD7*IT*aiA#)Qkr$Y`gym1C5nR-VxM$o|yX(Luw&PYep+!VvIk zqpE~D^7i>Oj87;VE(*p_2%!0cd?}RDYaup|MBt*o6L-}coo+TT;-R3dIJN!H^#zhD zlirHl9zXnP2%z>vuWF(?vx=3k&YG>F=NJP|6Fz{v3EV7W`V4A&zx0P;Q42B)8o+|- zf)ZrbwwE7gh=T)EuYQiu^SB#Ws*r}wDn0c*^*myDEqkzvh;l!L3H~!!`-$N2uNPi% zii(Q;zs45oJRdA)sx=4&S{-o(1O)7k!UzbH>prb(-{0S1blr?wA;yi#evUXIVRD`6 za63fUsTYls675~!s=9K{ef(oxh%$)RBh6ckQ0+I@d*|bKkc^eUi!7Y-4+T{%ABsJ; zlu-jHxCx#K2TwK{kaQg{YB1?HMesrCsEzZ=jjOr+{1t7$U)`OOPH+QbGehIW9&k?xpcwTPNY zr={sAx~gU7uPOQ+dzgi%o_2yXZ8a|2`{-ot%w~pJto709IKVFQRour1&>YswF8CJ! zW&b;~Es>na_myW}NAn@=XC!vVoUr&Qx1Av_`-L79S>Rh(z4RL(1~(0yQ8KXiv39-8 zLG!c}o*ZKKuMpks-Iayih}?chR44uAGkdFo&D}M(U~;n zq56B`1To=ZVYD(EOk=))&^ZlA#e z?|~!hMYUXR5M&woL2LGI)YZd<7O8Y}`0si&4vz8p3;B+1^Wu+^oSGGeYU#mmOje5YWLnez^BL{(V=w-V*1a_RSn~ai%E|cP;JhQ?7uC40sE8?p>KS z)`UiPu)+NE=TCh*0M|;G*v{{2EI)sxf=>@Z){EsmEgwR|a%I$~O3)si*}3 zFn#^A$JNf--Swg?;~(8#%g-6D7!Smq71Arzx>;U$mo1hs2`JbFb!H3a4v3kT`A)Eu}Zi$;BrnDgi58y~d1ii$;aYM!lMHRAN*KrM{oBu^S&q zngF%hZHtPEa=xB^d(vuOiMrv+NVkNW`gbmC7!h+h6fxuKtKYnck8gF+QqnF*C%=oskN(T)CQlN9sW)XN;n^E+H?K(OK7HPYO`P;n1q?>0 z1+F&-QSGphwt7Oz&x%Xyjg0?~4>TqMaUf26g0rB1V z$QvED+J}4kuPUOi1^7r+od+Eb`T8(07QwMC%y`(bO#H1zTGPT?UJrCs=UHO2gn=a7}vzYd*uY%-?08@*!c z>Cz}o)Rh-CyVYLa&ky;VPHmwX+QwxLw`acL9Jl@*To*(~ zc&ap_F3njh8X%$^m@Hv?v4%dKNZJDeEF4U*u*NS5_T?ZBmHAslrtF5)Z<9L1Ipe_IFU! z90lLx#;g|rto5K{S*{kY>^||L=nUxp{CB&u=~2!>^AC)?zh)}p|7cjU<-Sz+IIb2g zz>sh3Ah17|Doj8YPvL7?fAxVpjv^jvW8nu=YYs-Y)j5+96!*%N`^T^p&GpbeYvmoz z{3C2ahXID<4xERTRa=pqojd=caEK}dHcCNW{j+-C$g415c=tsAK8|GMP{55M@{~OD zLA#(1jQ-PRu594^B2eYU^uLa)cjV8?NB|_+eMm%)fpcgYGq{Ny^(eAAucTaS7^NG| zS%7yV-24T`b(_WNabS%hhy5nfZCkyA+sLWrY9c*b9o{+AsCIq0z3jqIGnI7*8r|AN z1E+HgCdn#QS+$$>UjzQ&w@v$`@wl4h-T)j^Dl6595nH&sRZ-IM1Bm)H-=<6l;EQsy zcS8)DZ}sLJs^l;7VrVtf@WFK3wYmS$vdx$YenIV+a+3F|N#JAH_FcF0Z?mJSb_Ep` zIgX325yHREF@1>!|3Lx@h~%*vH>`tiJZ+rqTHR)jfw7X3ro?Y@-s6{oE{+RmAt_af zp*D*)?qxKX;7(W5drMQ8qw!|}?aGts>x#6?Yk{*3G(hk@`?Pr;8!gz_&YNEnW0BD8 z!K0vgq3C1^Dvt<%%IJj!i=aYnZSRY=lSR3%uR!mPVL^z!hCuA;*3Ca)8|J02gkQpB zP(x0+|M>a^QODz8TMCn!p?GC{Z9E_S{@U7FRqtuu#>UxulE85vPYcjA^`Q`K(a>ev z$SYrM`WGa{ju8mX~K?JiKXdF~zkY&L=2?cIHC8L1n zyiPZyIdN@mmX*rP0y7nRk*+;QTgW&vzYGnt87?{nX0KGdT`{dDySZ=|_u)KSmBbaY))Lle6elpjvHXxv^IO za(O>BKv)#n*SqG#bK!L&2Tp<2*%rl}>^$~JVe73l_$h9}o z`_610`xV2^9>T}ya`d&$Jj|XhQ^}s- zLgpzO``Lf6UannDW(Yjy3m9FFh>GIB^RMp-pFvJ%(|b`QAKSNVHr6%7q*<$H z)EgbagWr*-$7A_v`s-NvjtPF)3zOF?;H!+(hr`3e*g%r|XrYU}y+_xB&f=eR_6sdI z7jI@-!Eqro!mF z(y-`PKT9sO1f%Jj zQnHq*pzv|90K|L}=V;PKbwB0e1QNg;%vhRZb>tn{f) z?StR>_f@!~yDmZ+-cfcpzR#LDl{#oQKUfTOskT^bKiipXh`3;LBc;c1m8>4 zH%f=3rTnE8>0%EmZ*5)Pe$C#`Ga(*wNilD>8I`KvXjo{D>0cdUM)8=+S}?c{Q){u; z!x`O!)LL!j@;y7HsqEWPbcdzht`9BP zhv;1D${04*^UVr5F^r7KNB3@)y3t=_vNJ#6mjS$u$YG(Cs}D*{_^~Y$wIA=G6j9BYEl?4Gdb1Q{oH(E^%v!ua1D)pi7h}d$YRs7txk+W}^aGl2) z@he`*ws_1h8kIZnc)~%|{CzVcm;FNu;D^0{zAKNbZm&;PD=LReIvvWHZ2sa62Ppsz zWr?HkC4Zmn_3B*a?XnAD4o8B^bBNloAEltS@0GtI*q<-?70J7WHMj|;d_0A0uhm_F z-dU-F@)^wHQjnf{$JqdVaq5KF0hq+Soc{?W`J-0n$K0A4jtohGSNBQOHy;01RqM}gz zS^AC`XLF^_w?a(b4H~u}(+c$x-j&3j4q;@^e4h(jAIX&OMT)Z{f7)puB$FHBN(K04 zJrpKc_!hU<#&^-$i!tBQB_wz^BOGRrSN!0NGM|D}x_b78yLnu?%g<>VD(W2yk|MIQ^uD|TaLJ5~$WRFry+ zskc8zpF98%HQJMwhBVmVFyAt3(cKOFZW~;ukc?f-SmaMT0fT8c{-)nQsnx_U7?e71 zw_fO}#*B%wrdeBG5AkemnuhmR<}*fR{sh=M&<}|_2G5c)^d(;aJ}};$omcQc^wkvv z2zi7J?u3QSg)6mcYZg|_dh9T9rKP2K?jI@cxLD0Wfav6z5iC7bIgs#%bvfqk<-7%5 zC*3ZaWsd4z4s3?U(N2qW2VFE(j1J<993um!$m`Dn_FlrmIw+<}}JH z7XGAdaV}UQBDAy&h3a&|Wd_ZcVt?2BCn=2BbpzKH^3_mKv(~4mS?{z)qPnbnBwMNk z8qMgNmDmjy=!RX%hp%QP?aP|-6&skg3FN03md&V>U**I`D74;h%Cs}kbl@wr76PBC z>DM#j-58W^(j%Oi1S&}-)jzv3Kmr273EFe>V7?0}(r$jn96`dM5~Z}Y^(*n;gAMfH zReK|eMn#S~gI32MR#g6_`w2&c>e0-2?QM#z1AQpyz&d>?yOWLnH=Z=u2uAQ*zjJ0| z?TuBisSXqiMSM;LZ{q3blnygagwA=GSw*Gv`n}2PHX~*mqt|CpUEe3f{-i1nE>VzJ zV_Ps&n4;s$59xgZK)H50B^8tv-l4CC0oC)2^X8V8)0KjGc7v(8Zy!sD7%ItltKxl+ zdeMu%#{OKP3V_On^N4?qL`2$b#Qj1dc<8bmPvd>njDMSKZSMG$l2jr}C zdXUPGlF3cQO%VXQxvOQ|DX8DYTslJ^<_w)k_h~xeW>&jJ)Dnme-S9LsWF0%V*KVKd>Q(@rxeCKHFEUWV@U8Sk54kCGuxna zIZzuQMaS0-&xGElu#`yJ%YhaKp*n=^Io5h$OudHy@^zo_GB;@6D1@31Hf6Lmw+)(h z!Jqo(+}^K}^YdQt?8Lpd>_XHy;DIQGMQti8n`=%iG2z;T{_FWdIv3B}P2T2pS|@SI z70hB=cX+&k-~fCF&}k!`wp{B$KbnRjK(>TtwHh!TQ2XC2npYz5R@ArGe7UE2 z7AzkWZC6HHm~>8Db`rUbpFFOT0_Ckt=V|WQtuShhyF~GFpG|a>pX)YIC>eQt?|1wT zmqMg?V$+nI3Phlw@WoAp4z=uuYC#I-7rH-*eGz>O5x@l#Lj@=qrad%ELZL+#LcgHV z`w8XH(tTa;av-5w1{NW-P(OT7!e z+FzbitNN_=id|b~kmNlwE9N9cU|AaMft~zLry7Z^&gvh?vSUXCqv^d9>$^ zHwWG>G7U^r1~JmV)d}j@CCZeLm@H_^=rdgz`L5Ct?`+xU6H{j%3&{@o;jRR;f>M!U zcbj2riV7!bR+Kafm@Qp?DqOi|;lP=EfxAZn;(LAkNk*>JJsWJFORq>A9uJDg{g?&? zG;oAKG=6oO=VEuIxza>NRmuO#8@giT7S=XYcBS9cbo}_X!N+jev&OJTy_0-c$UJbw ziiA-ro_3UOLaIfUvI1;kxvAd)0qBU)6uwD~i67f>l(k7l)w|ROH-@BaQr0=vs9?-{ zeLAM^%`=>!!^32d)FpWtd(7)4)Nz+)TCO)R?c-@Pb)L8M)?!dXv;Do|%IfP$-HsR# z#Qsr`ZIeTeHLW@{KE8Hon6bHOU*SQFKx9Z_8Q~4@QOItLOS_(23iN$B$4lcvn__JL zwEo=ZnV2I-O`=+&wTBz)o$29QNySW83;fqFzqk|)N*=wYCAnZ2%d-B$YkSQEQ)$lz z)5d$uN`6NZ5vk*GM%S)24*3Nnv(w2E566X0(1eIh3=G=oyxFx(@Jz6mn~d@Z!D55BiC}UFNqZ3KL%Vd$&`vwZTeHSc4?S5WrE{6hD2|q) zE?Mk%gSZBG&#k;Y@TntkkTCv9J_2zg?x3 z9}VDefE;?O5u{uSt2j|9wJY8U&8Z$8p&dgbdh0yL^t&r#QKKqMSgU!ZTEtnG;};*~ zp8rwF7Qx{uo0vhZlz4^*jNrMAv*_HYQR9BAJF+Z#1v86_=gwkM;1;m`sgTTsR;b_n z4dca&j*aaU3B7X9&0);)U?AZsF!MMukO2IgJ)7`?7jxOw!^cP=7x>qDzWkQA`j z+BGKj8*cL2uHzTRpSNWFZsv3_=1GftfB7<>Ru0c~<7;V}r}TiTJkhfbUpRXiJq9R)!3HBjEq#^#p@8U0H^*igHcHrNQG4~r)VvDAs9Wa z^UdU60*5Y@v}!Oi;FETx;IJO|or2+=Q_w7{PLXAG*75Q2WLl8JLQ6qF$Su=~8WI;* zea5>08iuUFwXo=w-QB;zsOeIUw{D{kdy5mSbicx=tObHG;+o8;(l@fny1Ks~om8S| z`Y?Zy!EM7rmf_LS@o*L52mlOcTuiVb_y)Q_a~r0L3Ue>9QF($u6ft|0g;IKf@q-Tr zj%XZ!kb#z(TFvfpdn^yVcdBG{-QWcR$Jka|j?Fj!UCrkgCEygu6BL175MJ2sZEmgx zgn|n6g*mzG?f)g%R^L>_z{U=3_5R0fwsd4{RH&yab^w!P9v;DP-6m%)skpEC`WLn& zez^E949GvmTE_AO-&AT>@$Xl~^vk~3KNk;=`(8!bSZDLYQuDkvLMjYv_4^~rtVPxcOZ)BhkLRJ8an#E-6Ga2 ziJQ|+?nSvd@zY%8TVH}SPJ^I_yQ?C#WI3iy4aH^g<|epSv#pi}!;6duQL3WR9;5e8 zK}X_)Eok<5p|zme8l{ewA*-Yb+KqO56WFcCg%eN)C`fvF_YU>&g;dxJqIYh$$}zWR zoa92zAHebUPJ0&eIBz1WOZ|quSQqLoH_2dwO2q5~nbTGuntiljxai)!2n%JaN8C`; zTnWvD_qGJYpZ>*8$CsDCda)j5bA3GU2`P#;%Zx*O6cm*^@(;>N2M5xsBjV!tEzDmL zk7mbDm4K~DU!@z!6-Pr%&$2p7bCgI$T|}@Er0fUkngy5Txo%r~d$y}68BZxNJiM%I z&S~?avG~d;3?vfi=Cb|Lx`%{W>5YKB6iy@O3*z&JtNnSt{ZW37sfjkP3FCXAYk^Tv z=l9WtusyzS`+^esXgoqoQqod~{*24(PFojBB%D7M=iKW34UowA?ep)ry3f9(oFNjS z*$=!wyDTg6NJP3tnngM~wqS1b`1qT6jQvS!70Tm=s*XFTk{poOY<@Xqdu*xrutLRI zmI&3Qva|d8y?*U-|z8$oYG5vQHe(mC2Xj z?LFoC)!+0y<1it%ncw?$P}bMzqvil#5^BW2>1^_y2J?24Ir`5CuWL*iDYZs@=;{(S zelDY)ic-RB78?6eI|(!ek-NUeDt|N;n?8bd@=+&1*$f(9c>v#P{8D@!8Xb*w|G>Js zQ(v@mWiQTaxAZEKAwSWA{yLy)&@8J;;k!n)k4H{)yg=U+-C2*Q%fy41nb#zxjI3-y z7v_w5@<(~(i87EknLukdY1r6yVp>#1a+&RSmIb3KT{Rp>dTTMiow^ zAdA~33e)^yvQyQm@yPQ%QNTRzo<=eUtox{Sd$9}V2njffwFmwhp zK4BZ7a=F#pbi!POcWgT@KCSqZWz^`lEOt#ux50yaJw(U1&J;`;!8JU~ce%MoGTR(@ z)^+}u_Nahn5jA@ArgOrwRqT*OYwkr=qX= zH533zPlC`*u#R>Ae6^LpOt~7$bgA<620cIjQ3E(4<*b?Eca2_WDWFFb|5ejM6({k< z-Ym~TC$=#|8+@sJ+jjV24dyEybc!`XD7D0FU)$S&H~v?VHiA z1;<|C6$tf~r|cml;Nfo9jae0Ii@hnnLW#nup;s~eglEuExXF5Us%wIp*9Ib!d>Av1 zG8j)aD83~M3TVL-g5{o4PzrrkfDZf>N7ZN|@)_jC_DxR9&F#R6b_vYqt;V0^risvFH_sKJPzWLePu;aSGvPPd>gm2F&l5M>vq}hAOkC z*>WvukkS?Q&1jjb(Vsxy@Hxog7TRO<@Ng4MKm8yV6VmwpXTy()S#SF`z5+vy!T^9Dwac`-}qE z?IvzK3l1)r9b-Q{RWCGmAsnR?fFDNDX%H80>2J@t-pvXQweh!+%q?GSZZ&94V?A5T8U`9P($Z*GBG62>C zn`gH;c=Y=EW`|DGy-S=oO>=2?KCtpWGMO_;CPA-&)oLS1eKNNWn2tWFY2<8=VKwoA zb})WuYWD)hUEW&0r}1W z?8jBBLlv4k_|Hhf*Y^*qxAT(AI8vrk!QO{qA%KYti*ydXZ{Q)bxui|~A`bYWrC6X( zpR+BggPF4OsO++d+>|fpjmr9{l{4_-HrVpXl9Z3V1WMarwF)4o-nY<}C;$?bCyg>#%4c|I)7i^wn!|ieaU_CHY>MS&9sBnKr~*4y zx}t5PKF3s&|IS-@@@;z)(g1i( z^3M|8lR`*}k{halZ?Grr=LzGP8Uw}!Nlkr9%Dj1;{qFdsW^s*pV;J9SMWC%x3FKUq zXSqz1*`DWF(SbNfUF`MoJknirEsh^fK*>XuPRTK^^HQy2KvVx=Tw^Fmjwc#KA?#VGn98DKNJ(CdwpoSw83tRdDUZQ$xDg_XTUqgE zGQOVzIB0`qEsIA1Sc%ewmle|?W2Lc zcI-XFrTF>z(p}LDZ+B^ReY+^coBnme7pdpArROKllL!c#<#aw1oy&wN64m?6lF`u> zqo#1@YZ;SJ5EX^6Oh4y6%{vro8brVkcchZh^uausuSZqLxl@`22R#BBppaAdL3+CH zUfNTV&i+))X8SrlNSPcNK>N^%9rbcJZ}VTQrrKc6O0ZS{*EVw^q=_@k~^RG z*)RF6JSoeKi?SGGx%p+chVO(go84!VYCion41GA_3VIzM-*+e~q=VeHg8i?L@w+<{ zXShcs2L1~x8N79))2a;$)RMoFZM1cgObVk9pO0vL%MW<)@ez1?;}Eu~q+>09K!$Lf zU@BW#D`k>JUrEsJr<@FzqzQuS17m0V`le(Hz_fTpuCpT@G3zR_aeXnThDS3~Z8n6k z%iJL0I-d)&nMxCr5P9!j8bpvVUuDw))1hlik#L@gNW}O<9AP{AjfRP7h%zV3XE}u# zkz>fBzc`Y^+J1_rk50GUkL(SUwR2#mbEYixveGLx<3r?R)a;H~b!w_m5*SB}Len?| zBw?Qpi;gz6UN&0ZhwNln9|~~zk3W&8xsntiGI{-jgCwcnuI;`ETh6>@%Mdn6#%O1a zjgOB9%(Q%(-`Euzm%5EgXVKa#bg0s=j>0v~8Rz z{XO+c*!lRaT>R_URD{R`)CB)y+^S<6${6#s&{e~Jf91cu<;%Hqxa7GWo7--r*iSQDjmv)#|J-8UhIOQF^RhDB{v*~n zRDuR*j3))<1;$g6VgnJYv@U}%FWW23 z!Y<|8Eihh||MgM$t?#o_6nDgGa6hb%{;ONTR}&lL_(u~WlfwFcQrN?e5M#$9OURfv zT>Oh6Ttj{?QXWB)$yfeWtkiEO)mwNGtgTi5kHn_fwC58a$!FrB%#J5RrGG{JOi%w? zHqP}g*`Rqt_@9pa|3$+|dJ00|v_pdkz;)|=Pzno8tC(drj3%)JT5XXzIXMwp?iz?o z3hc1s)jzDnJ@E!By~q(p#Utuj)Tc1I-N$MP<`(c){6y ziSHwJ!JQXy1U%mnMKbX_!@{K$vSm+g%@KVQ>9H@cFa6k~{qL;(_Mq=ag)ZaXqWqA1 zj3t|8HT!QT(0NlIf8DG zEGcN^=s2GU9==g;TD5L?zUW<*RSGm$m?U2OYy6MMI%mJj)&0*kPO43975G`a-@@Y# z4OYRbOA^rVqdt@MQq$e2W=JI>m_Ry$pQ1vl79u#s{ohP8#(qEgl6rj;&Z&%yl6!Td zBX0WB1S%Q)lEiD=F9C49bw_=Rc%2Jgi`mk6!sndW6Wcdgp=QGke2~UbdU{5KKqHE{ z3I2dJWjY21J&l5Ag~}6lL8hjrg%{AUKogt=;P-QL(6jf1i6>%_h{6J$W!zu6S7N2; zeP4kF)q<0~og%lqNB(sr#y%IK_08@JdXr6cD<9cPL-p()*1m9iMhS&RX^V<3s_8kw8Z zR#$^bboQHe|C`#&aId~#ND9_4!0Y_a@bLw6*xdBsN;c=xAZKs<_Y*=!m%SMqY$`5X zlWZHFvY399E02B?GX~q2F1Lu{f*S|aEPlr?+$H|i%_X|WaCL;NvJibfqCnhs1>aod zl^zi(X;^BdfGvAS3XBBgi_C7o8=Re;-7K@jV8QcwS@K{Za45_5p;J>(X<}MctZ=zD zr${lCEsiA5-w-6gvt3a+JbZ7^=-K#49%xKRLK0qF{KO(j4srMs^X0ozYZ|$b->X1u zsu0O#|6p&P!M@p9qUq9!S#P&3j^On4bjmU_`A5^Z_6r7GWk3q?eJ6HMkmTp`GuZ7S zb>oHF(uXonK9SE)6t@XTRSK(8keqYGTfFK=*#psdqzy^bsh*4Yg|k=aTJi!i6Aegm zwhPZ5^X6E}@x|5EsO>@236<7Q)`|y2_V1E&PIY|vMTaq##V>Pa8CzY^KCvnN<5pN6 z@RFp?Oh7UHlB>@I@Lo``uS^pY$GF9Dq2Qr!Tt>!pZ9`AD#gziF2JKZI2R{t=iUb2c zHo9Ig;1CEn&c{hDF_S!;r={jQ433K`M5ul*EUBzBpVJS`{N8O#6zE?|4~Cj<9R!Y{ zIj};U{#bG-P#$wF(AK6CBk4gs-KbeiYItAxc<)VUs%G(%*g>6s>+1~q7Bhf=wi%T= zl`#~Zmstl*Y$BqfP0wYyAz6IizW*qa_zGv=&$Zx)qdXqcYrq>W6`OReE8ZDdH+iM_8014W4-+V z8M|(?otD6zZR=d^r)%FeY`^neFG~a5q8niBYM$irn=Uxg^N07SCk&r_FUIgrwuer# zHXWA;zC5e#j&~s}T`RSW{m}K93rE4kdmSZ)T=W^Mc8x3{VOMxKs6XRGgGrJ;1kSb%Y3_ZU$y?KBIi#|_FVgEuC&X`4V!k(a9Hc^BT!lSdzwR#HLQWO3z%sQ zZ7F%~2_ExpwwsnpPyFdR+Qz)&E{~2-rjMh>7{9koLbGv9IUJ92PR>9*Tnc}FVONmv z-EALUW$-iGmEWt6do-_8rZ>JWx$Hwt6(|jzM2F;|Cp`-;%ECgX#iBCAhV=mNBN-yd8_QT^t z^R>smF|-S1uhysJItY2(Vn61c<7rndJB43Lq`2!cmrE zAvexLUBLLERRss8bDC>B-Y&P5%BH3~;YDzun#+Zdj#qOn^ibq&`6Vn}(Zeacj&kxi zRX}ldb{&^g@2j4`ca|-pI=B7+!CT)cHbfDbqnNy+w+CVmBLoH9gfKg0kKI`H+=x|v zpMVY?>`!OBw&ANpU|f)N zxU~D@R&`LRAC=^ZsjLg+ClUc8qPE0VFLixsqBX^Mc|(L|dp05AT`Wa0Hn?4D?Q8Xd z=bp=l0zXpGOLEW5L!(B==yqKAG<4)f29i!GNL6FltX8|~I-X(|maGR=B-B-mHlK%r zTfiRjV%dIqX4H%aBh20$3v7c+b2w51lT&B^9t=j2kLvs#@Uz_&6I3dLoQHA8+KiG~Qx0UL=$|Irp$5rSfqM{4Cd8<(QyO z;n~sUkiWk4ojr)sCpfX+WZE!d4_f_+lJECZrt$439({;p7MHJw@8sxyO*2@1Qnqp{ zcCyz*wVL9brcf8huD=b8>bxsh~M z6i^an)7B1Pte$hnih5Jelr!#tFp}_3-kQ>o;btHKg3-m@g0uLpOxQW6Eyty!v$OIgo_QJZi~hEJQk>MI znMM1Sauau{%a^Q2J)GGU@D(t!fto!ZrL{kH`OEeu0lqiBFu&Im$pw-`?po@ml#7?A znv{_Uu2D*@K-ub_tdn%mkjtASykJZIytw$SLM(kgR>JM%Rc30*`4AWFCTq9YNxD#4 zLjzEqpM*od0+2v1J(i7_$$24Q{vM(Twd?JbzuYR;v7J8Pymx;RDSW_+{L#EE0c z)kQTv1w<^sH#5QU%uB!h#vf1{$zPpa5ZRtks@3breiqPueowuf`21pj$5%D$7SBvFq19wDN(2YnIxl9w-DaN!;`4N)kU?roQa=*Z3D|x>_gbElB$RA_E<`R)X^GrU zhA8_fNrTVO4R@bidbYuj;(RD@L<6{CHMHuGV&oFf>ThjNc?K?n)l*TrQX!TV30?3b z1K^GQr=|U3hLt&bXtUzu=4kygzT;L$kM}-q_4|}Z3;EQ zt_MOjsvi5A(6bmnN5Lz&_~$=8VncjtaU^r;S}aK2YSDI$>4>6QJ*@43!@@N_!7JqzX%bQ#F-J$t zeR-&Z0X_5==Ab+!_WknabgW|YleiFNW7=9Gi+jHdi3skwk{N8LxgJ7<3bA!t>4Sb< zei^2+zekp#@@D>UIlSGlNWaxKxQOAUa;>nu9GrclaCyjZ#-a!Hz54#2d}H=p#z3Vj z78{0S<(?SKq-bL1Dp0Mm4Hb}V!%48dw3;t@)O&rax@~_v?($Jl$@YF@jiWYI{~Bn} zVwaGY_!VbA>&rR=Oj|I~qpc(sV4JlUL?0P-K;@mnqBli{rQvdYtY!pp!Jmln8;`m5 z9J%!JE#_fR$%{nqy!<8R_B%m>i)Tucoi9d5>M}aVzEY<;l$pVsjNcVmO8STUvSPJX zh);7fb}3u7x&b?%n5$&cu6p#*;bDozy}HG>jvL&P3&kakksy(DedfV41-G@Af7ivU zcVMN2Hqo~V$tg4DqHzt0OZ6$K4le{q{xn(@HKj^uz8iM6Uli>AL&UNXJMy^c;p5Zc z-h)oB^a{Gkl7%%xYjiYy$}~~(OHn0F-IF{r-@X>L@(#h!kS<(D^gIo1pUmBBToPPq z*a@2Lw5L6W#oV}_l=?I90bffXhWc2WJf&$1%jsP$=EG}359-LsUVBedBgsUVHeyP) z&9>U|h+5<011zV)Cncxd6SoQu)6DAl)34ttd=I!V)b|hHHpA2*IlwP$>ih6g&rxy^LG;iihIg!{R4&h8 zsNuBCCpWRAb(-$t2lWlIqxa7(L{AOHde^=8>ObniIQy6BD5ip`x2e1YbnY65Z;XvO z%^z8s)NQ<& zrxafid%hq7+Dnsk>|qAawDqN!VPb52NnwD40^gM2RUD2o?I7e|>fb5&9hc&kA72;M zl8QQ#jmyc|S^6t=rj^?UH%Dq%?)q3{k=s)n<$D#>-N^WO`C@O-sO_9aa_K;mQA&d}3h&uVJaKot zqpogI%D`KCzsHMs9g)u;Y!m<1JqO<3vOneuVXsK8fhC+jId?89c9rk{KA9k`f(0PS7}h?3|=KDm*qV# zaI`_+E}4?~Y+O4w-%uhP`%QI-+UCjQpviu_G(lw!hn0=dQTs2+k%$A3AVOHXA0B&c zU~tYMi)@aGi|kd}L?*bA3Rh||n;&f#A|ApIHR1pSe|-=n-UO%h<&c_j1wuYM@THze zr}UOkhD_D~-Rx{3!}Xli?v2~*1EX`%b-okNl0SA@PqK0gKPirNE#^xaw|@NnLiA~b zkBi+K&n8m=hD<$8r>oK(P_dJ^dpg7{XjDL596egq9)01aw2#oXUspLbHVd9?@g=<+ z6561KvfCUE#nbgwXmoaXE+lazW+oD^L^N6*a`fqByVnzOkFTh22;gtvCnd@5!qVb0eo+%K-9+0L*Ic(pkDJIj{~ z6GG24w1?z`>61JLI8o%hma_FXKkvpCN+BDsdUZ`eAGMD;hkvew^x6g&Iq>Q9PnU)8 z9<&l?_muXo6|jD*&-(UZjE5$K(t<67p)jp3d9~a#vIdJZ(Uk@!Ufco*X0wSJEgzs2 zO*bf2?@Vf#X#)6*N|rjVj*Qo*;LmX`p@{;gJVD)gJ*uLX&>^D=da!op1Vz+IQ6Th) zovQcgE8q6%Uo$b@&cKH$@*)FkrhDtXN0l^X`W^`jI{`3zW}1s3ZeBc5r>7Ry8N%gx zui3QgEdCAZQ0)b~{z2z5(ev)z4}Dd^qd0O=OVN-P+*B4VDTD8x2lKJo>>Bzsn`eME z{5skpeQtl!YSlR34zafO4%@L7cR^PXM;qu`(zbHN>tq+dscl1JT9`Svkm`tUv1q(7 z0Se%lV$D?J7y2-5Z4xobuH~Q6oc&EVrF2OfqahAJT5*Z+MSv5mFp^K;$!4~zzGY2` z^M5h-)^Sm`jk>6TgeWN@h~&@$(hU*F z%(?M>*IwUQ>)UJXwa?n;9R5___cy~c^E}smQ;N z&&le@Z2X0C*>zTXzsQibQ%w#J-YO#%+cop3S}^Q^RP|!^{O6dPwTP$Nl-z^%KLm{{ z-dfTt{HWdjLG`LYd%)&fd{d@)jWgffkGh`&$S;r~(v~_|P+7~uK(x`-VG%ejvB7FD zmELQ3wXE^c)F@TDgh)hYqAHU4T-*`^zWsULiwqtz)o6GpU$7edZOyoZ}a;y3LoX8pTpr$5eU9xckPh1 z5nH8v){<*c7o%K>PcnBwQO{LwB|meUiYYuaGAAczDylmwOrQd4*`<11Tu-LbK#Lz~ ztZ@|Y=TlubPc<5cy=Z&sDxX}yr{kE2tRX0T$tM%%qDV))L zIgT1mWp`z&dsdtf)_~YpZfjLes)!QhwqNeQuuRL5~k4YR9y z#o}aRUv^7Cq%w>~rfe>GBXXBg;(3^!nkvaLw!CF@=+pPzt9TwKQAN ztivFD+|-ti`Wzd=@lJ^8Y_8B;qf79%0iuMNcdMNNn!sTlHx;$3SGq9_TgUR7P>|SS zxteFA;TqiBdrn{5m^WmzHSMFhtdJz2gMr20{#=^m?OAgl&3D(;HTn2hKT1)Pwq_uu@!_)nG^*rWhZM?XuY&B7Hz7ZDC%`XRH z1}1*~f?IC)47|??)4WTPk9=ahd#!D4eB0cGLos?Pyg@0-%CVzTYJ8%O{4FN>3c)R} zdzS`e!K}Dbw@F^6soBpN)H!~NyUAFKV$}+CwoXpw(9lK2zuu--MWWxo8uY|qR@IO3 zWoA^x(a?@t8~Rpw>Gs6;jcJ>TI#gw1HQbqQ7I&a8wxp1MjFjGmR;$c47QGZ$>_se| zRIOiaxqAN)9E+c_qtE?w65wAZrMf&HNtSdu9P3$e4Q2FSGK5T5<}b7DPeMi4 z473G~2F0y1?#uK*ciyD;Kd@^jv!t0MWRod1^m&btjeMS5Xldlc)AwcCHFIQ%y54m0 zxJBGasC<`*^`P%Fw7F)CNNMZQ@iuID$(79}Vm#`Gwq;6IXnI&Nj8&;*qGGewk*ukl z`dp4lb^)Cf!7XF+;T=C#sbh5572YJ%{>;Kd7X2ye#e%4Gau-Px>}fB$92 zP1mv!Y}b>8v{3eXug#!p7m@q?}l{4LqiBc7p9myGWFKqbUtq3Gf!p2$p2K zg3BI3nf)9c;&onhm5ZmzEha-G6&{Za);5~ZHi0Kq)UZibZT^Ld{TM|~%-s#*G!I!H zu1yvDy#y1#=ayGLvxpBDG3reuyk_E3FP>m3^?;!{nLKcq0QC)0IImh!B*VRg= zKWh$?58H-B&dn)pEc$G2#0YBk2HRs0qGcQ`I{Uq=w%@BSJktwXX{GWf)nG~O`25M9 zsEY*1U%lY}5A-m}e`=1s7RvBX>tl`Lcbh#WM>zTE>NrpA+7EOK<{4_oofzx>XlQzp z-qx;*-|nByzmbd)zvX>;bI4C$3%j-GAC)9YNn@iwIuR&9`ri<){@s7FIL5{(-3rn2 z!H<%lVk0JhEUAGN!CNz?xwN7k&5=O(`#*kL;N^7j`o}1xDzv)LM9@$(d91VO_7h!F zF#DEdO#o4B1P9|gzMinq)QY81Vy4yRhsW@XO%n*l+*?O#ZxSDb`(L7AVh1nQ&(SU! z95Pn=;=k&p@a^u2vkJPfk_SbQ{mNC%iIS_Y4lb#9$#%-)|&6e|$qkpxwzG?bN3ktX-a|CT)?9TmiJnM*_O%U|K zw?uyZK=_<^YlQz4m4a#NdocFTKLlYBIrMd$W2_YJfI?+gskXYr<| zT7c}_cmTF&{`+$pW8eMRxw$Yn+&EvS5g!AG3{hfGW{$s3v``AUb+)-8Ku(QJuS+HLJ>MSgs?+(`P?#k8g zW`?(g7>OaDLj7x#lld_We&gyh$u1|XYdO9u!e_eYk;ZZV$HVoN{St&TkJBcDvG!ugxf(Y7QV9rH!{ zpiyR-&zvtHVWgLp`glx9Xb{leq98LTUy`WNAu?LSasx;sKfg2wIgOp}cVJ=*hI|%o z3g&HNQW>zmcx;7{R2i7N%XX)Bxr7ZYjJ+uWS$i@o?Uk4QtNU&QgmAc4zGU~azD zh1Jo{Nh+6s_T@KY=ze7$_n~1&M@K^AYkcn$3ruSHjOZjXX_Z|_I`6LD5$CF>4Z^(1pD5 z;)!X5XjPuVn@g1a6TWwNKAj_w3FGA737IttK)8!) zhjpQVTQMq1`S*7_PNt;Wji49gcZpLi|4!d$)bS{aDa5}ho6!qIwnXLE84sj9pPs4%Em5)ll zhke~c_VW8{u>f+>Hw~!gT$Y*!ja@OMC~HlV&hEruOjXmnMtxJS$%I@Vf#|S*9+u6* zc`Tv5-F|&dQuIZWL=blegDyN0>%GvyC0rN8!?8jivPneP;Ld-+*d9c_N3z(8&r970 zp7<|VE$*r|$o%QA+qCP^9P#eS3#T7G>2UpKQmOiGGu^77gJ;I7V#8|l+qhFX3~F<< zHJQ_eHJW|6RBAI;cAs@gTp2iV$#~c0Eq(>_7EOQL%9mPFAcobzcJo<~o*SEIYTia~PERVdDwkMG7aMv-{ND0Zv?G2!L65N72oJ`~+ z^^3d7Mw4A*1f6mv?sY^@R{{Ym_2pDSLE+SC#AvyLo?N2qA@A%#A|_w*+>*KPSf#C~ z^Ts`dJxP^Ad>Y$G!E{*t`O&Vf%&0({fsHP{2~2~3`i1nbg#9!9e7#yM=u+LQI#;`b zM_62o4!a1V-?m7$*Z>4+z2%{{uuogERrOOEB2f>&jQP5h2sfqaSA)#Kzf zQYh>`8M*(xl<|V#ch^zOvvrpiMhhd{Q=eSuTXAvmsJBSAdSc@m$cV}o?NW8FmXS3{ zlu2s0`?<&@b}aL`)r)XYo5mM&469lRh9)Q`TXmB=ObU1l-OE!4Y=7V?x3nQ)S`a6l z$us(eTC}E~VJvG>Vg%%~KDUw}R3@3sll|#~AaPa8u3xbbOehpe7ddK)Qz21>no=Z< z;g>-&_c%xA^tKFHpeWfH@y9DR`(NkCE`A*Iq!Wuon``jSdgj&o_S)VsR&Ghj$d3i| z)BZ#CB5fi7-+y##?RPife}%S`EarVjkPQ($O1&p)!pf6Z9vWGP+Th=3_gW&;<6&az z?AEb5`ti)HP!!qePC!?~6s;uA4^146N^!#{J_`T-7 zmU@v^-nK@)Ha8hZ;#GTN>zmcRVN5}{yMjF-W{LcXGM`FPUK@`uz*TD1ozS)gg8|v} zk&upr-%`=EWD^|iMp!xOo@KY&_)+>cI^K@7WqihZZQ7^x`qsf~E}MxPy!$?M3tk$;@JAe=~OJ z2$WwfRV62987al-mAO{ijPRE>-s(P*`L3BMrRJKv@M$k@gUnXkQUI4+z;Ckl*s@Xp zOVhMFA#X8H9rPWE#5#D%wABXAYqWT?!_n(~rYKxMq|&1Oc8S*)&FXRs2wB3g{3<2IUso!G#%FC^~Do z%$@prE`KEjRtEc-w__zldKBI_Y#WZK(d!Pv$RDWeGl=QLC1MAmZEWB3yaTinAbly& z0zU7#0IUsUBH?eJb7{-EGm%5SDUW0Bx+_^9hmsoL?Hx2zN#a{HJ`6s6yWO}iP$N9{ zg6*A3?M3eojh=&EK8K|+(-W(njxT=vU+RuJ_gxpWmL10{Z6*te)oO%Fit^M81IBIZ z@2vCMAPDn3QQ}=wP5xuw2200jvN!7AOV@}5f1dOxi*4)hv<*^l<9Aw%iBrzC9y9A~ zCn3B+A>uidVw|^PkFz}2XTi^A1A|KE`T3LG9+%Hx0vLrh?hLWoKWPe^8jq7rO zM*s0Dec7Jb_|c7g{o1r;@y?;x79xW8U8lw1@o+G~HxpCgs6j2i)qdWUPp#E^~Xk1|BjP2J5uy``5wct2dM=yvMT5udG zXmaa zS5&y0smldFnwlniWPd}hM`e`5dn`XbvIpDGc>NBxyH%IJuBU7a!#C~*o5HP~gT3dk z9Al8=!5MUs%(_+I8_axf-6?xPJ$fM*fu2OSZZo}Q`c$joR;>$$jsu*+I0OB7yY84V zZ572tr;zBo^83*y0ri5h>QBfcf-2~Ktq@!^BZUFp6*|P%-o!Y`=?rQ!N2V{p7v(Z4 zO&1F7&Of|OJ2tM*v8>! zOmuc665~|yDCxDdr8kpW!*}Pl(TnKqSAGfb7VNI57%!}D+Wx4xXHe3vn4@7EKEx%I zRdZB1!G{q_1&=98ierHk+z7_5GZ4txq5hga64uSN67xI(ye6! z_uB?u=b1e5U4c_kRRf0-o#|yip}buD;YS;zc_x|Kv7l(yGW?MPSv&vBt9aH22(^Qu zT+D(yi`9`F4vThy(P_Mk6Od(T4F_*|j>R(5Lnim$3!~o*o@c*M^3UpZx@_IyS!#Y> z)>JrxA#Z%bdDwq2yB_=Zy*pV^cIXX7B7@3G2t9N^LdKldhY+m&_7Yh9Hl4}VOnPHV z%e9Gpi?g%2+ly9(76@*}r$Q;qvw4&TbeKP*Ad+o#&6C3&WH;Jl7oN*B9qh7Xl}kuR z1nNhAk)0_J3mv_|FQekX(-fyGxp%kvJ9N5r&!qEp??s^d^A597YgTvFoIZp|RZ-)f z&{p+2P8FY-%geOrqbEf=wRHMV`YCMd*>BkDkTf3XZMPK)X<>YS;dhr6XMqjf)ib=-L(STU&nU~<{EA%C7rg+ zhi+?jb^VQOz?xvy)1$YimE|N+Q+8GBnn*Y2w2myPt;(hohAf=T&u;bZ@2ExE5~5K- ze|m^g4958z(0^EzwWow&Mvv*_a>rl2=XkABBOpV^c6ko!KUyfqM4tgWP!P_OrUoyJ zS%YFBA)(2hn=|76~(xU2yHpYs&M0wL^Vt-cEt{8-=K17+=V4^JA9Y5X4R{{yV#W>an3VlNJ&h{ zUmV9yd^3M1(=FRq43elOp!=@^I^^bU68oLrb-n)v!jSbLZyLw}eLQEDL1Z z(hR`VG)#2pg!Br7+Dar4`mV0mdIkm*Pu|n{R!$H}Y#$I1h1?~AqcbhSpDt#UyTixx}#Bv*ATHCMfdH2ZDR{L4-+9^Cqj z7oi!ia$#dHy2fiGy`8JG(mgS9qgiUaW$x!VG73B-{rFNfJd2{D%$ZTu8~zrWmmKB= zj@`qrb9CL(uo&h4jtneT(3JQ;`CIQAYxLr^7CxRYdW7YCpAksN3(KJ4)htWg2zizQ$M4*K}87nVOm(w7Gl6jK}q1oQMc!_b#B)&{hMpSxr@GAB6Vod(@ z%1mI2%85d%#uG6qc9z2P)u1iumi5QY{x6?!zImONSMJWe_kF}+9KfS=9(yz(Xa*v) zE=4f03Iw;fU-CCK=G8Nm=#rP2?nFXI?GggcVoBCnr$_TjjZI}F4rR8v_n00FJ7+XR z+LDV!}43+klQ&~p@H{;d8{hQHG&+uYc?y6l7=uD(@RnjmPc38 z1}kPT@6u7>1LMfU&B{r?%(id~&N|2Sv$^%{Vh^_S2K}Ois;}DBCCF}Bas6DCJE?T= z;pc@I_9^nbZ8GD@I$y#W%{Ip>mcTc5)qegi@yLNyN0y%{XtZ|qn!#|lfh9|DnZLwc z?2H{yH-;LTOob(uvaNiiVHpCq&LPO+Fz-||XeQTp%tOdU$x@GsSNMmM=ze2MV~4rI)F<}k98@Eh_RtI@OcPLA~lr_o8n3BMmbL5qou`Fh(P z;xA%7d0h1>SLLkn9%d{uNF_^FM%-4EO*tcBD)l+~ht3ieW?Gj7sJu+wj91{j0N4n0 zQ!N)pyMdiN^eTnVjQ|v8Tisy9C?ERX86sP;-#vA>V05K5T~G%1#vUQ1W)!r~p=MMK zw~n-q)|rKB+^yc1D@oKx2*p3-WQ?C$5{LK;)4IZp#4PoJGwrz>V^D5-El5bezk2Xd z$3)3$_i?II9Ho3hT7M^LTsn zS5~;N8!NZYp7$I2W=H)2Y89-Pua0jovW#91Fj1Lk`q5yikeRH4%(Wx-%{v9%=r;aYz#Z^7p^3x}N?n}^?f00(Bu8vCjxf{8nf#T&$ z?FJ~`)Ya~zUMYhq$^`1E-jj_$4kTxW)v`S+xum08;el&3tJB_N5`sDz*mz~%ynE$C zDy*M7_?ZKlIvQMWU&i}lF{aIzD*jZej{0yxx$oeAS>!?8<=;=n|A)5Q zzr!&9SdsBZ9{BJ5gPeU(zMmGCkPzHYnA44df-X@zJ3A?hX@Yl7PUYEuia(U4_7wa8 zHnVf}aJzQ+S;-<(K(1otw*!MlYg>}|pO;0_!K)VrgTYEu$uQj%oOPaDH+}@$ydv}e zOVy}Y=MV#Bmn}y>CeM6qqRF+#Z#ie^6fN)c95-sKh6FQ+@`DQF$@G;7VUJ@iRRsN{ zdgIkJ8|IYDk0fzNH$$WOozBM;bG;rE56B6ffjsXk%u`5n${`l{Lo{>7AiHS1>OO#jhWp6pR+d|U|Hb1p>uK}H zoiI_L0%AaG-w4Jw4%vH9rmn4uh)+ogTUmLuPBIXCesanC-FymCcYM@!vK#*f9A)9$ z%c3?mHm)Tjnb(!u+_c-8jc>3``!0#S++Bk5@|_i8=kDftL)xWN?&$o8peG7k!0 zlv}FD zZ|PrKjIOPW`d<4qULq$Wv(DBHF_Y&M?$nC|i&(Xu*2 zQCcq&0`@@BdR&u-YoP}BtF2y*UJGXYeUb;Rq7SSl;jc&vJMVwxjDHZ|20baM3 z6}#x&!Owlqz*s=tVQc7hri7fF9CPeRKGsi)Mz5e^8lNV8!hGxT28rqOlaObGF`G?c zj5Ky~wdw+&3VlGkJlJnI|L_!$xLob&>~0Xtk#B{ADmrDxchXkJvG=b?f{fb46;yWU zr@XA*hbXsNj!xFoYsRkwo4tH0AK4&%#1HB1`VW9Jv%+IjX_O8+;-z6^!~#0jpc`Vd zcW{sp)F2KlTcn0Yj2yq6t|0oRR`6DV8w)DXCQ$+nULP(9?9oxFc?l&bG28a$vd}e1 zSDlL9CO`ws!~~?Nv9dB1BI8pvA&(>Z{578J`RN#jFIQ%V@AaKAog?dVXXY{$_{_r% zUtn9&4y|(HBPUQYpG)ob)yu2~Rf@2(EM7 zo5?d_J%MR|80|-^I@MxBHzCBL2#eC5Zs(g;{bdmet!Rlt#SJz;cBh~_&V!N-sCN7IoG|1kHdQgmQTTsYm6+{6EPy^fH+ zS^4|xv!>YY$NcVo4N~Ou^z#0Ba-D}S3Qe}QY|eP~P*bQAE5}VFF$f?07`JUOZhMA6 zIPw!kfv(?o6`iomWSzb#HgkTDjJ_M2ON2zJFiN-=F4i0{wSOxx0dXZ`?Ph~KDYXlJ z<4C%@;dX?HPjF)|m?=Rqy3R6aJ2t3v{?LJ;=K*eHc;OH+MR*6a!(MVh+ny3=kV(f- zg#V}DV413f=iMVYkOtHejXbI7kT=&?0}Pu&RvB5IksL?YH5TV*?p?Q`PGgz zQDU8Ymp&(3R@!m)Fh{~Ohap$b%hTF3a+<40a9?*RV|`C?p| zFZ=m=To2G0A)DV~Mt3P$9&jtDQ1QB8jS+Tly>QcQP{0d-U=`?aA+;|*I9V-$7YIkC zPxKB&VRiXZD)<2rdp>eZeHEPmA3wKmv4&=n!?Z{1Yk7{iO(4@qQ0u2Pqtz0%V7|w> z`|3rL<}T;vqjgwIY?^*x?Bz_ikP$1S+Q-VKrWm4aBFm(j<>zpm<|Xi*kA|Q{PQ#Lf z%OKNzSPr=Z;%&?40<&POXY3XXyh?bWAtFZ0o$R}Z@>E&qaD&1o8#F}vd0MSa^SZ5%pR|Wa=ItmCM-LhQ&qtNQ z0kvD(z8cdPcyE9s=Ki{Z!sA&R&dn(Dz8@VI(MWSD?r*qG4PabpyT~QdtxAWYUJs(I z2pd1Du%7%GGi@3p7H_^I|gC zfn*Y(rGIEaqJ~3xYQdPJ({sRV>BkqmlbENL!d+>E^nE`X#Vyu>e_&vkzOwVmsvAE)8o0VX=(mt``xGYl*#fwYA2=Nb zikDv&hDC4#5CMKTV74`nXlZH91o`pyk~S&?{=m7(uYBl#?_Q0V_(euW25(aWI0!z+-#AEPDxupJBmE1m#K@_cXze0(H!I zMal`y0XCVdSs<0UVBkClU)%!5RXI?Y59rUsu$4})i>t?)T($&L9_J<(Ctc6TMC}ks z`xIbBN@#Rl+0lG@ED7e4KmGj<2+4+u)Ymo-5C2M%J=JTF!y^MSFoF&%+zm+N?jsr6 z+}|`E>^}@W6&^KvZ+fmW=(y95KVhfi5p%RZd}{Bzd&C-SbUl2w7yD0uT6qOtWqmnk zc27cHthf;>?IS(6sjXn(KC8XxuzfQLor_l}V3S4+ZkE(gV~l-tEl1 zvHo&46K%_GGWPTnzw^e#C#-0*xgWmGH5ek9rS$%UY`7?jtJjklPl(u@|_OT=i=x|Yxu<-4~6d)z`x+NJx~8r{$&LQ zXLeW%@Zqg;)m)|WqEb>*Hy@Xvp>H85eOecyzUt-GD9Tw6z=&M4ZP~id%~I6majp)P z>duij2s6WmOKLrozO#<3hT|j%*zsj6k^4qWdE5u^V1!a1?j3=%X)C3oLV!cTpS=$s zPtD1p?~G^5>>Gq7NKch|jjMlEFE8O9hCo)ya69Oz3NkMw!-okcQNURkddQ{~0+ydL3pBqEOv9BH202vvHcTmZd=Pr zj;{YAf>UQEp$*4V`*t$FrC4c6BCizRdwlICA>9VkW#kc#)kZhpg(7W zHGmx?$d&N7^o#6nxl8guY+~_A0dA+aS&^?Bz!na}%3>Dy-7ILpCV&@8N0mdAT)W)- zdrIz-LNxYWvC(o2N{XuHuCOw zB%lPLLFT*Df;q#K>p9^j>(GA3axt%KW3Qkc2iYC$Yzp0ux~NS06{`hy@1I;%HE>&MWj0{zRfU<2Wu?uvW@8#-3Dyy6c!J4Qr_ z34>41Vp@);Jp-WgL1PghVD_VD_ztvV=`04vHk$8XeQ@1x1d#Ya-0?OL4jHWm6z;T_ zLYImn%tqWNoHU|H)JJ35sD;9x>t$bXcc@aZ^p9{#zT_&VQqn7RmZUE>siYwOo7nms zp~hG`FQ(04nFKdnuXv8OiDi16A;daOhbayVK(dfpee!Cq;dWr*$3viOb$%!c62{#Y zOG2aNkM!l?c-}S;c724P&$W)Vp#*>$fHpw{ixDy5Bs|D4;QoYZ1W%L=mZ>{76kV$+-&iOCS{B!40J>dP+s#_yMbMKZhKF$3N9t%d_Z7u()4Ig4 zX`uHVtY*2yul&wsc0cwasddI!_X=6=)(LQ~6bW8)(pfj^SCYur066MU^2}k{VZ_?? za#Lx?ywA*$(jK^iEbxY|DuUjPTng{3B~ws?0kncQ^|=-_6V}~kx3tZ~( zORr1j`TXS}4hOEwdS+!Pq!VgCK2=emlTdQ@l-xTX7wEQc3~@g>setIcN8hJH*Ne_|Mi!Ns=`UkR!mMy(D&fb|ZnSOwuK$Snl&4|=V`aP(XAB>uEwZ!g zIKEE{%3%6rDygbbwUMk3!QhvFdODks(A^cTj5?{#{DY5?I`KpX#1#6kWs|ZS^;CwwtIlPg%I737>z)!hHt(-S_{HhjaU1;oSiY%ce&nV%lj%W3d!d_GuyHG3;E+pYesEH5@a(*kr8z*&U`f8ayL*-b zuwKwV!FvCHBITw%QOrxd24PB#j{?*;w|*@fpn@+kaAt>jMG?#XK2K~$mgGk3QD5j) z$o0~`cbSbHC-4~I=zA{e3Eqsm+keGYAE+nhap>j_i18LsA@OYIaCuhs8(dLt+cnY& zYKwhJhSP{c62d;8t=Y#=)RC?i*4xz~wB`q)vbOK9v+#Prv{0~bFaEpZohND@uWr}U zr#qD&hbHJM_^!Gk<-&8_V#_CWbwbLZw}2b$B<^JzQGNOS*z-ms?$uqItCO4i#H<4| z_2V?D1FOB^C$qIm&sN4G6rO85y6!Jo?^)QD*!@MnZQf54(%f)~!R|g`e8IKCDWCd` z3=C^hcgF4d2L)mHIb&G)?X=lWzu9Ov_&$PWHD0mZe=Oon-Hm4A@yw`GW&%+dtC+by z?Y7@HIy%}wCHH!U^%IM!JUKA>eOoUZddQ;XYj$?@v(Be=_IL5i=m!@eF4Ls14P%P6 zon5xEkc$G712!}xjP;eBV^$kk@(LZbS4khf85bbj_RS|q& zqF)^dx%$vo)z)Te4*b-{aypX_;64^5Sa~~9N3=OsHe@AkAxiP!Sy7bs3=#9l7q$It z_f0(eOZ$?-$5tcO;-z%=%NIun2XEhBA88spOm@@{nftY~5d2jpv2JQhvKJE2v*cQRpx?!VZG<5UnCDyv%y`WkPd@d=;DD;H&m$p$_bW=;yh#n zb(h%pE*-+MXjvyV^riNaEpbg1YyuLd!MHhEoDpiW_~zeuSFTYqplmmH~E z6V*;>a(X4|dCbis#}BQ+y5zSMYPh=4^NPUtxrcZzOvAw@LPZYdk7wS_ee1S7p`FUr z$wAkyeEVU*h~7dYt2-RS;>%YH*vEqLTli)436r6FRi4R|m{0=kO7r~kv-|7F?sDL* zK{Z<66x@{8#0fY#LCe>wRMugWY#Eiw*DQZ1!teQ>5MOzUvb+FsA8hQXq=QC~8k6p% z(*6dqz=^wRHDO#fuPEf=3lLWRAfo4-Ik}l>vQG!x@>t^H5$g`s*$~LmRYCP?E6hBW zF;_nJZttYW(dv)6Fc~~Hyu{n>#D9h7!#b_^pYk%`p+6$T z#Nzk0i4e_ksdj~X7)&6GQ%#2fM|l}_HE}%Q^jP2LobY-B{7LXc=C}kYT6yCp)r6A| zZr#~Z5U}IQ7Tp1jQUSF+Wzz0Kx9Rtlv@-*TzKRT;+Bo{uHBN~wf!Nz`;aK~WiHb_= z^@rK{BB4PP>zR#{ugYaVjNH zId@d5hP_a5d@a4##VG24_X)ffe^Ku=`;Hj8EmSH=Z;zBX-gEk;IJjekIX;G+H)5|E z7TXQ-oSdHSDZ0d%K@(#IIXeN@m-)eGaA~t?!`FiC>943vs+B8AAMoVqOM*23TgUDp%3Exw;WoJE zWUMQJ!zpB^kKrVK^|r@(hJul8-OyxPQquWfHDh|$hmTIB3s0||tsgfT3<~oBEeHZH zpgg`f4NN|#@9Fu?$lO?n;(@;F&eI%w!fvw+o!!%So0oX1*FbtrO#N^(7n#tKR#p(vlv{?cu8gZH3ehl!3$k`?mx5fu4z!n9?x3C&~9*H0UApG$XLvvtWX~0}36p z9eQ)T^*Zc{D3P_mLNq9j{mom$7srLB~6DAu+H-G^Ls(y zZsn=FI-++iTjmtNtCp?|;$k%S8J7UzXL7&~29=mQ%mj%SI%3`L#1ESN9q*nCt&A9nr^65>m#nQ9F+G(PiFaz#^LA2B)k9q=Jm z*1sk#a3~_$Drq9-<&Dp7H*ipg{POUU%Y4QD=WwjN75&$9=Qnwzz2HWLwf1Ker_vs; zLoh>M7w^BECPa@B*KUct#f=mMQ z@uymU+D?bdO{{KsKN12I7B4LXGSjTo`0FHOuz)dM>4St~B99y)$En9@XZgzB%AmQ2 zmD$1CB{irI(vrIcEE(e4-fZ(nwG_X)ihSOKlns*Xbu&oT*8t6SF3%Q&Mu1L=BHf!G z)8lBXG>#frzrZU)yCS)R;_!NHYfxsf@hQIMTvOGd4-hAhcEl;bw=p+j*XQy>#*4c; z;9C(~!X_eebC>Q$U)Mj92%U@Ll_*MN!L(m^hKY<9r)b6uGwsF zXDE1oe$_VJ<5bCZT`^Xm&GjqtO{M~Md;oB>uG#wo*<#-`+&?dmIa?t;)K6c3#nXTu zG&bTF7uz8P36xF$gNNl<(BBWs4_itHZNC0Nc54SDVBXh+1zeU>HTPv#e8R_}K!O<> z+eoW7_%UGgMZl}4=F`epJ;j#K3YKF{(PQ9A(y(g$b*%_C7beGpo;5 zU${O>quAjIPv^@mKU}p|1-Rh^h*0HH1{D@#Vf?PUu`c*eo@DO-gN&5$%#99*OlDN6 z$^|QrP86t9ndYSu-svmT=|-DtkNnFxP4}U z9mQj-X1MTeo^~}gDA2W|-hkjFZA;#|vQ%Sg0>?9!B;Kat$d{5Yq>b8oC%@{Ka{x+! zv%?qLX0spNSJ1zVx=4Fi_8m{x_C&e#2vjn$E1m_@UL_Jj>2xhuofv8|-~_g=*QMY& zbC6A=_|R$#NnjqJqZ@z5kK49-EyN(@HZN9DpG85SI{fhn#Cw03~&Vc@!79F7%d+X^bltG=z z={0>_%n)FzKx!HJw8^gd%;~%HC7sn);C5_Mx-H`a-tltYllSWS*1xONZkxEJhgCpd z{cS_?b(;Mdc>N^yAp5bza?^b1b0KmeXL!CiXl7kirLwpRDh?lyC=<%pE+u!F9915n zKUc1y=WiF;-`gA7l$VQs5FI&*C@kNa?rsf$z%BWq5fD#c6Ddx{SAGb{9Wh`AY#@8d zqY-_ZivAg{!%qj@dt?i@X1^9hMtdHvsj)ti2b{E`~+%ZJ!C`9CTnP8Y>Xvf-l8bC$Yiq`t#Uy9bnF=?Ae7Oig;1nn`8 zb#o#o{+OXM@W;qkLV+f#8~Ihnzz52zm@eXKhCPO*Kvk%(qP6AxfHZTzl7pqQeox#yq z7pbX>0;#*(B)@+B(tBob)CP(r%NF0vSoMt;5M5m@;(PDKgfrtIlICZXZ_vs<7_q~W z4$pSp7J_4-l>n`tU7$Jwcj+|WAyEjWyFRX zsNAn7NqX3x%-eKvM-Gp`T{peU9!u+di*gWV?4 z*gbm8W=XL4au{-xLve2A3r)>LQu*WZb5;COFZ<2d!dDzObdLHmXqgAHog8Wx#cKqi zymU~8UUvZvp-CKxpy#UmTPh3Gm^yj6T{Ka<-GwRat%4yhyt6~-?h;x# zb*^jMw)E&XK(D6~?#m~U{e;MgQ0Q}aRK3gG;>h$!@~fwM6->=y6@avVF^*)pme8*K zPV&@tFK``cs=>d7#igdakJlc50+$hA)jly+ZNK%ZRXQS^A6>NwDzGK7_w$XdN)Ti8;j z@IFhudagJBuyVYS6XK!=6MQT@Rm!aIvu;%H5Oc3)Yiv@Q`L(F7BIynv=}y<>irWBjDkkizIG)hZ6Cl)&bRAe z1rGxbE`%-6byHFY7MnZ{+<^T)jFgjI8ktJ2g-Xx7YQ-?Uv}abM?$ibR3B#P%X|i_N z%LZEpfJtji;a%a5rxw#-!uih5o(@6yRuu=&b8S&3jkBUT#Tsqsan2$$Qd`wNe4^a^ zOmx40dzBnaER-++^A?#1dBp$K-E{{wweNW@B2}6oNDW*8DGG)wAVmU*bcCSv4$^xG z0U@9WB2_6Dl-@)@ia;pRdzB8NQUWT34xxvZ_ls|Lc4lXH-p=fQFMs6BnUi`ZIp=#m z)kBrL=WTDyNmzmE<>rRL~8`y`D zfm_Yy4G;j|^PW49Zh%SexnMynZspt~nf+v!jF>UDk zjCYvXJ+%9p6YiUjZj{+L>P6edgPB;=vW%Y+5EQDj^%A<>!#&{XGAvI>fe@pv$(F-~ z8h+5Uv%wgq%4a+*YIzZc3>s_sjnKUmJn=4#hClNCjL71o#K%kpicl>!r>oI*{*6{3 z%CV^8{ts;ub&8zwmqW9HxgveAJDWUTK$hqB{$UGfdl*YiAgq52BoUc%RSr@L1v2#M z3Lp9}Wth;;&U7|GZ7{pzO*7RQY;0_CYp>($svjDH!~iR8?F#F01K)r>C*Rw<&BuPX za&61X8_0oH>?a6pYR_x3s9T2G9h|h zGf^w%awk6;j4EBVUkqSb0$|^U2Ef!{u@|&z7ueEtet=E&G}8vhLDg)k8gS-b_>t}t zVNlU7>R;oce(5Zmbk4thDmB$dPVO$llT$tbF7@*fiOU_8P@d}VFoGnhoyJKH2rm3G z!5l#c>4J3hSdAdFtmZy@c}lcRp|wJnPJ6q$*oODlB5`@a?S@%&%KOECZ=dL7t?g25 zwTzprf*cksBZ%kTU+-t$+v!{rJM1Wj1w|cVf~j^1=I#e)P#5>P>k+?C{GJ7)&B0+pAyw*=5EJLpA z_otrU$sr<(e&iQHB|$OhfA~~ipN$x>F9fn>5N00+lG5}1D{_D99@HLabaT~KPbrv? ze(M@ASXeR`+(#I$rtpR=G(cY1j7>Wt8GOi5K&Vn6l$pMlF-te!o~jf2S|{DQUNv~fe_62D;GicfM7#6lXyUEF zIU9f#Jxtl(+aB2`2f6J9v1{gN44)zZ;1kJf?ng6!Vc*_(rYHc%sp5Xz-;bEjUmFGi znO?utD4nND$boX4?@e~lY7G8p0Skj7+w?#KVOoGb!nFC!no{6FMy$SzWbTt{4MDxS z*AE~P_S8e^k*!D=-TlGUzrDmynVTVUTCi!5X3hwKysD9sQgt=sBtN@76GUGH;6LYy zLIXD7mYg`_nO?E$S9IR_rd%z24xq~<8EMC{wdbkcJ(pZy?r{3n874ucN3XFhZ_q2MnDKaa;=dkUz{+g_gD-ecIg zxr>bUq=#=fSMB%AFqwr$%_aNmFmdfAbC(l(&hDg@T>xsbZVzPZ5W_}+eOr+!qKCVg z9^q`*(X-VQ>X5k^2a;EEkmY4Z_>))AqYy|A2o3@BZbo%Mi8^2a>tjtNdT*L`50h=b zhdO=dY@BG3B1i4YQ!@)bofP0@q+u<;9ob`i>HPc}swINEj_LgaRjZ@INdMJH)oO`c z!$XRFyi+1GC0Y$H&xH!a^n<;?`n1gmAm#%x17rYLoJ0U) zrlzSt{(Yt7#IUZxL2a!1p_uX9FxkKrU|!reC^oV%MLm`cD|wGfV>xCwu8GMK6UL`Z z1r%Ko(z_~R=yAIZ`B5GjR8y=kTriEo*3e1)Oo7O^y~3bg9%_m6_l5FZ`&9Z`-KeRl zi6M9uUGw6XgO?Zf^P#WVp-124Zyw22cjS`bhe|k%f~tp;9T)ZOY}%jX%f5N-_IGkgs(WKI5(xAg@?x@a}RP=b6XHl06?WJ5q(;r9ng6QqLLmo48G z?^ASjP2ax+d{+}twm2wzQJ)bR)n?1t54Rw~e&F{F!G`?umWgHAO`BhfE0M{A96v)W zn?9`hmKc)SAd$7v^|;<0oIrpl+NAeDMYSh8=-b$_oP=Sb;A3ATKh=SU^LGVIIod;L z!#hd8Qr@_{gy7t}rB0f70sNjcZVq3k1Wx4fGQqJa)6KF<$36|T)2x|Gu1~5jDqhv% z&*%BIuCvxiq3_j!<>a|~nxcwmvU#`w39ERkAvyiPydImvjl)_UZTD#50S6W5-L1On zSOE^8&`_){KL4)ofH}V>V;Q;y2uOg46h(H9ExI6PLbXzosoC;_ei;?cHeq{58Bmx? zJ25($cf$=OhVB(YI(agO*0crzJeWfmsIaf#>Wj9+o@4Wq0)gQ#WmULJS zf`8>(*!8YcO_PSMyYeL8jAIru|YzGzP-tb|mOV&FmA2I^|F z{5#S5M7_~mA*5DhiZtI7g>z!0T{;_Vo@d78^QFux~kdp zwKy1x7#aU}4v^UAg-3h?1z05xQ)2j-Io26?gy4w=bKhHxtKb%LfgV_S7#Zyh%VxU- zWdvA64Bb9%jfONOC>Mg9Q^7YKuo)GpXWScs)u zJBud&A??D`|0kUm`!5}x|JINAO`2*eCwX*o$;5D#%KmxY3w5D3r>ga~({)%>@_$rl zrQK(yrF8>Tu{;FA%jsb&v?G+5b)JIk;{%-Ww zGWVMC(vp~2Ts^`iJ0=S_7sP#T?2(a@KKBglk^JWqf$Kuh(#HGsZe^8DUasvM&d1N! zMQUmo;K6PGqSWl=|LoKdOu4c-LPv{qYuAQa7uH&T0$$BrqErfC()Ym;6X4^^-5uby z1+NT$mw@kPsn-b|lbNKyQrfNaoG`DtdXYowV{&h^4RV$)r9Hf&7CZiR4o$mSW*YS( zur|l4s{703U#|h>8e%U-%zDiQkodBvD(fYPG&eA;e!2Wf1Zde#@w$K3j}lqp$~&w( zF9`IO9UtHqIQ?-FC0;u!3Te{}^48Qghh(Ojc3GOExpzEBhdaj|_5!|c!;fEDw5Vr2 zq{dqlR{p};fSkvx&^-zOYDWeTVmiQF2@I$os+mD2_HWY+3#PdVKEg+l^E{*@(mKyK zl?=yAIHBr`hYR`KJP~yElHyM>S-6{{b~5Q zH!mS!mJ_#k&nQA7ewcGB^liRcUUR;g9w{Tjy80xI6B7|dI3bOFwXRa_6_V?8#A}{{ zc6`KrK$Dt5JBrm;IV~%1ngb1HQN}*3Hmx)$c%`ye#?sQ#i%PrG`Cq@n0I&PwJR(yq zz&C&tKvt6=OpdGd1cHhUph?ai$kWLKIz^)@_q?IReA}}ZH|tN$4-Z?T%NwIXOZ7Fm z)7wP%sqf}@4pdek7hnv=7QtT`{N&;Xs|;xQdb)YNyPRG6L*$AL?}v-Qx<7TOer&4+ z*Hp_CTLrNTuw@q)s@9W&0!n=FEkD0i*P*f@0mkK+YY^14?Z}6WkSClCn;~QrnIV%V z$FQAd2Nu!prQ&_YrT`AJMw<3gEvNPR6JBkDsF^1;a>WKJ3el#Xr?okP-li1H4Yi5; zt7|>bL>@I8fFbs$dgnYq`nFC)c0d6<9JDv*0tieQ;0p1b`{E|c0H$Lq+lYBkP1lWH z@j-C55w&ix@pzwpaT@(=+8YO_}ni;hzr_{NJ;ydOrDL#z{a34vCsX{aSWp zE;KqPY|Lu9KGG-Y#?hzK6>v>V&}GEYCNbapQ5E`5DThYFk#E$|hBQ*5If|LVSa3A# zZ*t2>#o405UKOp0uvj>&h7E7w4F(&R_g@vy{|_qMeZ9 zD}$Zs`7yKhGEZv3=ZqnIV1QL$KDZ0fr;i#YK2!Xenz&iIFSC(v6C zH$QxOXjh>ZXrU09&!w^8F@qi7d?Orf``eK74qGOwYkK=QQJ6H6ug*8d>N zPI0hsB)!o7D0cX?s4ZKiMvC{5nX92tYD~PV19u%zTya>B~EB89PH01?uRyak!p0@njAR_ZOq}7 zRb(SkP#__>KAk$E)dH0c#E)g$PpBQAPM?ibPkkk*D590|kNOX;TJ7|E2tGvW=r#2< zXWKt=FszmTR&DChRHJXXK9`dLY0kr6@p+!d%8Cmat|B-eMRZu}8yGDAJgl7#d<)y1 z-P0f;p`;|4&u^Z|TZntmC0X`x<(S-*RrHleO%dF|#AHKQ**>(Q=r5+%gJDazMHsc; z`WtIWOd=gm0wHw^@=K+`NS$&ykKW`#XO#je-q9~*k1TK^|&&94;zcuYAo|77-0YOa$WhSLJ#afCN7Sb~@ z+cBV!tFS(hyXFIjTi~v_-QD3ANox6OVs5hqZEfRi<|Om|;y-6#(v)0|Rk!hm4H4`2TEDP&nowpsv(iOPJgwzLxs^2g+qiR-yj@bI_TI literal 0 HcmV?d00001 diff --git a/docs/drs/umn/en-us_image_0000001710631156.png b/docs/drs/umn/en-us_image_0000001710631156.png deleted file mode 100644 index 97358745f009dd50dcb080ec1310ba59a7a18736..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 234 zcmeAS@N?(olHy`uVBq!ia0vp^Vn8g+!3HF!RQ~M%QjEnx?oJHr&dIz4a#+$GeH|GX zHuiJ>Nn{1`ISV`@iy0XB4ude`@%$AjK*4%X7sn6_|E*U7`5F{>m;>H>*?U5Q23LFT>teWpK@blt&n-1p)$lQj#J<+#EExymjGl?8IV zU!b|CJIEloZT%#h?Mh)LVvcM772P$8ag7fQ`5Ruh!R6tz$TS=GK-=!C-$IsZv*f+u bSv-^bme_BBg~uL)e8b@B>gTe~DWM4f`2Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!~g&e!~vBn4jTXf0e?wEK~zXfWBd;U z3{(b8P@1ZMEJI(Pn8r}vwu0gISEv9QAldt`_jNE7EqKbnz{iyJBl z10X|*1+VtD|Bs2y`Cq;F#sB|bF8-fgnDak8XXgK_U!V%0fM`Qe41|F%hyS;siva;q zVG8rId_oOFi<3B1^d-aYo|Oz2S*025bzx#q05u#Z!0N*PFaGap0D3*C{r|34P$49M z*HCf{1Oc3el4~FcU^Vpp@gA}b1OY6De*Ay5E9ZaAyo*pi2oP@|2w=wkuWJmaFEcP` zX(~VkfU(@z!Z7!dG(&Pn1%s<7R2UDy%u(0pGsLz(V6abhU=Y22j^W_B2Mo`C6K^00 zU>f>x1w(r6QHGB|CYOjbgT9kFgTIX#ZU$Y09jamGCZPx#1ZP1_K>z@;j|==^1poj532;bRa{vGi!~g&e!~vBn4jTXf0e?wEK~zXfWBd;U z3{(b8P@1ZMEJI(Pn8r}vwu0gISEv9QAldt`_jNE7EqKbnz{iyJBl z10X|*1+VtD|Bs2y`Cq;F#sB|bF8-fgnDak8XXgK_U!V%0fM`Qe41|F%hyS;siva;q zVG8rId_oOFi<3B1^d-aYo|Oz2S*025bzx#q05u#Z!0N*PFaGap0D3*C{r|34P$49M z*HCf{1Oc3el4~FcU^Vpp@gA}b1OY6De*Ay5E9ZaAyo*pi2oP@|2w=wkuWJmaFEcP` zX(~VkfU(@z!Z7!dG(&Pn1%s<7R2UDy%u(0pGsLz(V6abhU=Y22j^W_B2Mo`C6K^00 zU>f>x1w(r6QHGB|CYOjbgT9kFgTIX#ZU$Y09jamGCZNn{1`ISV`@iy0XB4ude`@%$AjK*4%X7sn6_|E*U7`5F{>m;>H>*?U5Q23LFT>teWpK@blt&n-1p)$lQj#J<+#EExymjGl?8IV zU!b|CJIEloZT%#h?Mh)LVvcM772P$8ag7fQ`5Ruh!R6tz$TS=GK-=!C-$IsZv*f+u bSv-^bme_BBg~uL)e8b@B>gTe~DWM4f`23;enDMnT^N0^wx9{>SmmlX8bZ9zqmlp1t&(LeCi486GF^oXImboiJ-M zTTe0PbQZ<+n3_?|un-O~d{edt(Un>EjH{T6! zE%Puws-&8;`~e&T#~MX7p0fAm3wCUT+0s+vGEdTmayi1X6~Y{q8QnM&s=mrZlQ3-t zz1lo`cJI>z#aMq$`02V=`c*3i(*TBw{TVkg!;TvKn9#Jt{vB1^Tj2h8q<7Pa{NE9K zpfJI|BT{KFuI{d9ycuml+m7ZtV=~*D*d?f7Uf|B;Qf1+_ zS0B`UX+~}N(y?Tf&89hfb}&AjR-!bcOy1HjaY5YDLljNhF<&t$lRK*YcNK?PLfQh1 z>t2FTFOO3m305-!apN+wZPFPgKJEJj&7$Nt%b%R@q3?=k1f7-Npr z-lFjvtSM|Q=i7u%dX4vwJ9lgnJ}mccsMzQ?uYEme{I8&G+Z7dbn-@FAr!ByQycJ4^ zyA!obNmbOpyLR?)NfhrrCS2ud)D_A15T@*)e|GT(p;JD-aa#4c{0lO6|0UMtA>M1#LSTL3DhAWK%QkM9N@&{UX@5deM#LDf71<&Y z-ioC^YyUIvOjn|O^7m3r?}Z73O=aEe{dmX@8o=eISlixy_hhD{*!$q?VE^hOdbGFk z-E8FQy52Ln=S)BN?PC*LrQ13nI!W=iVld;(g;gAy&Y$!tM z8$W{~NZmgB<(DYU`FB!;RoY>#(cn{^JTTf0C%==xTiX+0mCC=IRuu`n?4*Cz^wo~J z{#R{?N-^1;vtQzD*y};?BP#VAy|eoG7wwFtoYh3KbQ2X&H{xM9BSff8p!k zHM-}}z6PUh`ubxjMt4C~hORFEn;{DjxU*`mBFOrxVmfjx6;R+c`A z@U>l)OTV&Qnp!nd%dwFcUf$h&Bzv1uO&9tGbB02 z^mtRABPr--?cMlw>3XI+_oLym{kmgzl}i7HNC95%X8x}a$?9?5GsS0vv3ePLVfbE`7zsFhD^__RmHFjG4VC#ch@1U*_P$oaN4shf3?Sq7TcdgLc|!G zLr$`t;elPZA%r+iE`nvpWohoU#e zU36>@PhBIiv1We=-_P3UlU&eCK0>OG?o`1DniGpLi@L>bCjC%lYsE3-I8{kvRw?uJ zue82Y^Od#2>jAj3)Of9_1A*{KO}BczLLotWa*{uyhi#`--mA|9*W7N14`fbsWaB`F z5=HNx8>ohd&Z|N~8X7cy>*xxp(S59~Cv(%*S*Ri*i;j3< z*Y))-WC%<)BzDxfvR0}mQTw7IJ)8$h00}V8!hafM&i7=*)h2Mva>Pf?)y@sgiZL2` z$FVg~)-I$SY;XT%Y)}!ng%5T%8frKs4Y{$Oq$O#Yy*x;e>z0*OQ|k_O(t!KIt)|t6 zcB-KI&@kiLZXn*!FBS zcaypBAZZ#jc#xR^GOW`h4cRkjCHhBjAQkdcuPT-}G;|I9&3oj!FGhTyGwpXkGWh^| zL8(ojn$nxvd4S~+BdP)`_S?xl3<)Amv6{>GlF^&>P&rNn5orYY00a+TDEh@MNI(eeDXKfqa!P>Qz7s|e;P2VICfA)eNH$vBrj#5(Y!?*w zKr@C!1CI&ASQ-am4+p?O{J6+=H1wn2!NDgh#w9C#%mn_OW3h`6tobQx-KpYdNfzsu zY##dh@zs>@D}|o(X{yCpRvpn7e7bq5)-Ix1GqjX*j%YF4Y-EGxvqQsXC&oadtswOY(PDftG*{pdW*8WNXy!=w{+_3 zUFdZ$+Kw!@lbB^3$ds)ZGqhOt$9%Y2PvI>uZjSKL(yXM*khKo)kB+z|IM`rFafc{0 zBt0bWj>SU7rJn=>09lDaalxJCmt`nTn(^hsB{rMsE%xaZt?5*GF1cy%3!i}sgLmSK zE!{_-Ato9&&%inio0xGq9EeZ-Cn7n*etk4@gxISF9VWxVB+9ziq327iftQj83yK@l z{@JH!85v9vaN5#bdA*gGm)Ud*mJ}c;)57$N`VNr=mR)t|eL+f?RgELVeOCJ^_AIoo zow=wBZLyf3jJ3|9=Sn>v1W$OCS`$tY z#+%JQDh=j=>KJ;H*VRQygxV_)9(8&af1I}MS)ml#TBkYqO8yBS;+q*4?X3;2&Z{|~ zfT-Yk=X>tVxAD1g{IaT8G5TjjTb2`VT>8o_MRZTT)`5{^#F%y{bT#X`i6ofv;b{Xh z;Py5_g1sF*3f<}fWKy?Ts~>5&Fa2E|nG zza?x`sF9TmjaPTr)aorK6F}ru!W+i0(M4pmWD6To(W?=(2a;w&UqS#6h06-$n{jNlg1DyV84|&YV}frmh9DtB z41In|q1>=C=iu+O$Xy<6em>z#tQdMi&rANFx`Oy44Y;@tbJoeyQebK-3PlTJYAzJD z+x+SaeHr(R7`7%Ea0xQ7gVg!f-_C_G96Av!F(FydwOhKVRoXj59As<;$fQb9_GqKh z@eRJh<%+@n0C5N@LRB%*mCS7&opx1Y!oEJm0hM`>@mO*<(BSG8)OD02ko7d%o}{dH z@u*JH8Ygp=I2cEQ1?>{-yKPenID!ppQohAYks-2!BA$x}W@6m9dypg@A*}}YzIyZN zFU3@8AH3EzCdMmY1X7}=`HH;KbNgC2SXh?Yg)QDgya65zL0Iovl1dmEXqk~LJ)WTSkBhS6(cA*F-5=e;DUWe} zcfW?F9JWpI?^cqf%sDr%zd^@v(T9go(-EsH{K_h84#t&`wyl+r9I+HOO1vBIGU4v` zL%pfl+Qi=|KK^S-`|@tflxw08zTtI<@AjgV(Cj)2FzX@TJ(k8Drywq7|jCOCDJccfjZnCAD?u9ks}F+>JM~ zp+LDqPKZaU*Zk8h-;IVkQEGFx2Qi%8OEIVp7p%*p`6ihWu3h2{&E>?X?)T&OwX zABjd$R9Bq3swE}j|NhfaUMDs4Rmv<8n#4--*24O3d>)qQ2~66tZI8V;{Y1;##=9rW zc=)DHrr_?2(Rbn&FVs}KcZmf_A>Oxv8L0n|Jid6PDE94D(Y@gB1Ut`Drr*lSq?DA? zFcafe4A%O|(zX05nOS>jX)3O9_5%)=`SoZwkk)-wzO_Ug98J||I$WfAE6iBwbvF0b z{%6?yTKCxzDjYB;#E>_a=(6ud5&V*F@6^A0HyV%{h=hrWuWy<*1S8vAGLV~an4=z* zZmDX*+sUr7mU+DbS`+=;p6V-oEXlvtSB(D*rCoO^>yD_;YE*^sy`>ui|4oYGzAt zE=HrrELFt@5vVsNZ-lwKKev_?AuueVOcKOqA>;v(waIq`okMHoAx*DWisJZ6S<=tV zz>rJsz7e)##~G3b>j}~(5K0Q#)ZEDX`qwMEvY%ZftCQlHi0y9LS8)?7&YIdo4zjiG z+pmOhTsAMpJ%^k{Y;b25fJFJMUh|1A^{vx3NufK}iidk1{rmwzn_O;<*PHm(;L<>P zd-{H^?kF4Cr)LxJe!nM74V*oy=zpo0O~0vH@WqcDSi+4Y_0>QT(}4KG8;WW_m0qc- zDY#ah#%r<_z6ow8BZkI3Ab9Hkr5G?^f`cwDzGnn~PvlrAKsjmZ_K)I7QQjfac!(FC zqP|*FiK$V)rjvUEmR!HWx>^>((*6Uo<^z`M+*d@h%Gy1N^djQ|FU1dn|5lh_jRPUK zr~|Luih6wSeaE_f(uV-@icbwsei~MtoQ;ppJPI{}c|nq1urgHZ3K_4_`e;0$Q@)1g z0?H2cXM-G#qVbwGq=7^{Tf$gG&RtNK$z#sb`%7#^q`{#fb2A^?(6w(fC;p>#-ITh)uDlt^Pa4wCm^et3 z@kSKQPH1AuwkxQgB*w^)xE6Qa#321s93NHiW)T4RE_w4Ml8D$=zej}6{YM3jK`sb_ ztsuU-3z3fZ_Hn=E=0OfzKfbjS)}lPDSrO1hanRryhhwBnuj5!USDz6f`+oY|8E4JW zT^3A>WtoFgJAG{bBMihui6K$Oe6*%L{;SFre3X+OLc6jlq8uQZcLRp$3@;r-`<*%1 zvBUNoI-V2MAY($}$3E*YboM~<^G?i{V!-gEHOL`slb=J7+8TG*2`ack+J?%v zEpK+hq#g!&UiSC`w(MD5UyV;0Z437Ux z8N5`<3n?9P2z!X7;z7or%<1)t)m|VC0u8Fv{`R;=DKhbYxovIiV&n_O()h8dPJGAd zfVt8Wquax%MwgTElq_nbuE(URFuaECTL$!MOj zq*K(BFP(a9L3x@>>LU=Qe6|k#C zg;hIjP3kXG#7KUuxXE!1C~#@{zK6d&8alme_4-MR>9gZGtF+f}6wP(-PihknS9KdJ zx98tae&6V9e`!>!C(sF_WB)bbtXKMKc)enu@fiRB=T%)z!SkLMl$LiR;8oG;Wn_tz zr%Ta+S(^qO$&Z+;!D!Nl0*(Xw>GI$N5-cK2g{;KU&T{B5_&P!$g|MzZ738AA-)?*Os*t(gUU^SP)h=JKhM?E3#O++5pc-8BP_&muxb~rQYnfKUR zVcW>RurUhjTL07d;F|scXBBt&WJv4YPa}SD+U@?)(Mp_x!Idb&lboa05aCpDcVTak zyS0V4BrY;6gjYRjbpWhvP4+KVKkk1@pguu@c9)W)%)wI4RZ{WEU!O=mJlpV>8Ix1#rB_iVquO3N2zY2XfoQnbO*8SqS5R8ecLxTD{4p=P2EbFbZ7|)2=Va{ zZJ1U8`%*O`FCf0FOHuPMKTjF(b}IDqZ)mak?tWq4bH7S{U{pS|O$YcjLbc!{G~a>* zHFHPUi5#P#45TkKyY)3vq8|o1uX$VkuBBM4^kGvamW z&*{ljfro43G{{qbXs&!!(pTWp+1~Cz_4Uu|B+_ch%Nmt?n!Y@o-KrH5?W^09ocMMx=I{|hW381wc3~8 zYEz#&f3W`hH&Q$K^0ag3GcO=TO#A~ykQoNT=Th)08-9{WB#8LE>x%`E)yf7}N?1iZ z{b9-dQeRC+`{#+^Wt&pJr~2R?Q=ok}nm891vn68B$|eMi9^2X?oiQMh+Tf-hsr$Ob zp?`kSsqrBwd4ACV;eLGKjUi-vL=UjU_e9a>gkAaV`}owDKALyjCQ;=`fF+WkA$?oHog?zYdXTb8->x`A>vs-hrRCqNJRIEBG_J)Ah@rR>2-5SzHTq3 z50NlZA>$54aICh-()T=t*z%Wr3~k2cWv1m}ScTe`2e<*oa?~F#Uz8%H6xr9~Wj+#Y zLOWG(jIuqP2MpJWD{ zcH-jVJre`c0-G<8 zkBTtEETMS`bK@0*zRXJu2_4T1i+T6&Xx#OG@aWE_;buo3;?y6?WuX`5fC|oVC6M|l z`aARWv!tU9r8AKs8hqsd+FW%#p#inq-bP?b4?9Km^`uNSQO^N28x8GC{=~(*WFc_G z9Bl-=r*Y#f+-i>_`jfoV$296HY0h;wTHE@ab!mW)uv{8iPLdalnB4Yqp{SUk!*zK? zd#U#V>E=+A_kxbuDN$GFWn3wX)58OH6&am{68xdNMQuYabEk-O8VMnu{*Sb5wyY!H z+irTM0S@}a_2~T9G;$@1)Nxd8ISfeL%3=NEv8Wq}hsrKh!W>X<%h9CO^^EX_C)=M= zFFv4>BT!b4Z~G|3h0Z^H5X0+H>g9@-#W204Ar8)B0aIpI+3>2!JRF%omux2&b%SoQ z{)|nfe-299K^%^!*xpbhKs?PnG<;;pPZ(9_nNn+9TpVm#sqm?ZW(Y}E-7zP`_P~I7 z*=l9!JO95KYOXlV>FR`%1jpvJ`i)$UWM)B0)~-2`doNQ>xYCdErpe2I?1It-gMrO7 zFg-rHk<;$Zl>T#WF#aG1+@M+S(l`Z-!z+1w)pl9XUg80$+t{s#Z;ff|hdORd4oAG2 zdin5!ADlJm>KM4hW`z_wjO5IPlBF_(v|xGvYAC~G?*v-O*m?xW5F4nAz(uXZgDU$k zE-#YV(I!#~(|D%C4@315f!c@7RP-D}8ziybf6ft2F$I8p&*D&}8`Q4!?%J|i$Z-5G zeKy}iM2v10!O!QWp}Bca34D+8jg3;Sj^zXgl+c@0_0D!^b^GsJ)g&l7n`ik~!Sgu; z7cs4b~uglzs#a zK!g^0p9w!inRKO)jLv-I!K$omv0t=U7tnp=D7&DE@s!beRv zZ>TTTQmBhehVrtbANrM!ugp4syeO1_Cv>z*zJO;FI8c5Wyu($&vA|8eP*BK$`@^95 z4M26n{G&|u=pdRA{Pj*u+L``Jh}+o*t7LeQ~zTxQMcK7|TC3QXl&>}&89Tt_hknf}Vf4u-()9Q}k_P(|5Uvbhinxg2MznHHG z5>~e`RxH-xCP45n1?Rj}nst~h+3zvj!NOh=Ex>HuR+QL|Ym57mQ?JZaHc0Mdq+%Z7%6eLF0zr+Era5#F5*3NL`AejFJp z&zSH2L1>Yz*j@pRjN)IcXn2w=@FE5_ zMB}iY&l2F{sS|mvjEXGIi72#V^a^^)k-6PVoiMY>#7-I#^)CpDE;0+hYU`5zD=~f4 z{FnZ##{T=JRg$y`TuW??yTQ6{9%VokREXng0F}eW{}QeRpHBH5y?i>C^HdB-mHNr)S_)wy4>Yq$WjOd5IGTu^Q+l`-Lz_c# zWg?@n)vBBE(0pCxU#9MtFik7J^>2UdorLvoqtlF{WADd&o)R_~2r;j@ zp;Y$sNQE)KN9o17H$!es@%f%?JIz#_*J*Y?4I|7QkjwP19ir4l4Gn_F+;HK#?Gqky@6ppkC~&xxEC!=ROu6~Q?rO2ZD- zSq{gUBUs~Us=cTXR@qf)-uf*lk@e>>VQ~M7xMczN{j+nJX>VEDRLZpuQ+$OKf2e|z zNOfD_S!q1JwAUExv)bccIGyY*whH~;`s*g)HH(EWcJ7Cm` zos{a2ysUX^+3V>SQ|ERzZ{4%imG%;3GR&BZ}?*2s{y3L1M( z)L+He(9b;e&WZ=C`!od1f-MNb#C-+1<4QKF#b={o61c`JOlE7H$)6mzzlZt7$=Gp; z+T&01UP&@7gm;^~#ENh-u-SXGw;L6YR@?G7b|*WbrCVYBbTog`L2!$UdL{$x5}U^X zaUdLL4R3s6LjQ)VrY*li2btK#!TRthJF(2tzx29Ue?;5fJ8X1R>!#1v5ub!z zBbKE;1tsrC_p==GnAf(3fVl9g&)~p_8EATSyY9H4_Ft7!Z{jMGy|v#Z%yN^|Yv}$Y z@?{x0#U4pm)_u^mqTK%Yu5C_P&+3jNoNt)XQDBjq@{!Y85~Zd0CQ|z1()Hr<09ePJ z3`FoCW$-~;jU4AsG;&3Qgy;7ier1CRL6`66oJ^#5ZG!hL4hP=b4Q<}`Om$U&6~pz@ z6gjF16D;cP-V1|KfsBh=xTHe~zSvS4FWh;J=l7e^{__}_J{v#`eU`-cJNmfzSavs4 z)Us?z9uijbuDpXm8LNsz(N8u_oZP2d6}st;>H!pn1gPZubJ_$as#?5YZtjS^E}xD0 zuC908w(2zJXrAR(hYF{kua-pBrw|-4zEuV_Yz2Umj18l!v+^#h6f_|j6(^1vlny`E zwxtKls$^5TmAqApWApAI{b45tE(#R=E;T|C8h6s`X|D(GZ&kS6uZ&hMrIO!Jjdr&r z{{0#V6726R1onP*_Ho_n=(`$c82KE6GcMP*4668o}{HZnD0r zB7}Ey$qJiIWy3h@(X|GUxq(2$@Z31znju9sH!-N|>E~s?u+`wXB);4~27MR9EY=b2 z(J1l~2i=3{4Y0~3{Y@P`t+bMx!uubEQ`v*8=b~z4K8|n)2=^WQBRdu&^_O=8>rF`g z9YE(3TpwBY0&)~Sm-jJ4Qf>L60X#;J*K!-o)i8+ZkNx=6GZJzah z8{bzXwtkR^5+IqWVvCHn+M2H}2^6uvxYIwb1+jfd$aiRK#OyDnJLTO_`IJCM>*WN< ziF-S4Pd{5Qky6GIuS{K$PR*yfw)~bcy`3_BUtPjQO4}_ix3I=SopiXMDM1D0;uP3Z zjNuX&H#Av7p)xd?E#EqR91H*65Ynb{7T<gn|lxG>$wv*l`tbl)tvpEMjVB2N3Sg(a}_S!98}4x8JLLfpePrc|8uZ6`sF{h5zj`ws7g)Mt4F`^N}|-A^`1Z;aZ- zB|p`(1#TYbT%W=1_CQJ=(5;yCv%kQlW5a-*(mWq=qs4yK=*bdWjanuP$gKGu(Q(NP zF;x}!c7!Egy)-+22h(MAmwiANC3aM%Q#zATRv?+hN+Q3XH+)~y)L)I>QZ0NG)Di4N zgJcLuy(~aEU*%MSFWSh0W=Kms?EPz6onc-9c3#$DMV%Wy{?d6nV+%XPf%73PLf+C{ z1Ae}(idBws$@LKzOrS(n(cMc4hWC2eq(;s_r*t@}u?5JJ-uFYvMGMC_JhrVstCb=p z%jW;pcpqr;`su^_vOA4S$P#Tl<{Xz|*>8BiGtw~im;5d9T`B2PdPsE8cV4jSppD5& zvv&$Ms%G}gs?$mQsUzspuu{LFhffa5fdDp+ra;Ts!k|b%e!^F6^LpubTEmJ3(4o8UL&>P!CLwHlf_#k zvdGrOQRBe}T3LF_ETQ#HdbGf;(QLDhmwU^W;i=ZgrSkXyarDVC%k@1D1+UKrnCMT# zimr_CEAoK>A07>M{}^iAC=%UQF4We)6+3zq_!BGfSCexyEpTh`__ZB0qWWhHh$Ns7 zhvfnPV!y^;`Fbcv_+vp5jOCNGW{ei^F#OE#$;*UaA97LH!I*M9VsM+6o(JH5Gf#_TE{)PtS2g!J@V&i4rD zsq?L1^f9S1(aPdIpgmC@i1^jJjh~lIm=Kofc=wYA&ifAf=Pog;QkU})wvJVl4RH6< zDJm)7RWhmKgkB;SiS;oF3D8108Rbw_yT;Y&_YX#d|pmivKLB=g< z5};;d@=7q;HB03!x%aO=dAb$d1g;hgO@g#cS<~()IPZM96>R1H;xOFZ%g@rAUGV$u z9B9pf@=+6)1jD|gP?YAw59!AfQm2`{E^3iMKixQa=yI6&i+q!=s_FHHkOT!6n+tC4C*fimIAha@1lIAmAd2{#Y5X5?USnkSC zSnA^wpRU^SRfqnXKQ~l9-Hqm3C-EpqlGV=hpb}W#-9$s>t`)0%iZ4Xe6pi!@iJv)Q!$(Qd%(aKk zjO$OiiuWr$9p;{0?^RsfOcra?C zKS}wth&BS}%<;TRhB?I%7Qp&~#_|@3X*#@}nwb-U3{h*r5k9Q5UyoLRb%u5CCqhFd zcE`Z6-}$Ut>BQi=v(zOz54EJFmN@OH9U7!QTIkc6ue_BCjDq6ozntlv3$Tt zFr=ha8b@X+$s>3HW>x5NHN{&oZZ}oP|7S-M7BeRoLt9-BkiO`Ekse9^EUz0;9_S4RY8>OK;z*jTE)8N2?fO8u5=*qS)y23AZ*IX)NX|49ze%jF=>o>ec ze;pe*l5cySCa4bIbk}545u5jL|D1t{D_85ca_EyBx?FcC8((v1IBB^rve+>g*c6+S zl|Xg1-M2s`MEa2oi&<0lVnX5v7rm>5rppmR5Xg{(v4kooR40W_bqt6VO1+HUJ?Jsj zi$4JK$N66CqyDU!k+mFEkuLo5+ws6~m)PW;4{-Sb90yhy(K)b*ROh4f6&7>T3V&Mz z-vH1tVG)7CuA9DIFVdzz%3xAg)NQ8|Ap|{HsWarf#D2I-^YZDRT`MkYvT~gsx)u*3 zTcfed_%}<${twB07Ff3kq^@>}5O<8vr+R(JeaaI*oZ>!Pd{qlv!8>RMJ=XtbHCqr8 zoCOq9C7oDJg`cQ!(B;ka_P@1yWT*V7jlIpI9QE(ezsOhN_PkRQakSDuxRfu*vDxdR z;D4Y{wuO`=6Fc45&q?Dn1mN*?H@NUrrFY$9w4-r-0gInoLFLr;tf}c#-ak7kc6eP# zS~&l;$AX3ornkx5N^?sFKgwm?5nswG+1H4{6nxS3JH`F3=7znsAV)t#uGbBJ(7J~T zn=4nxwi0gG2iWjq#$p0ItPFnagJC^I@AZuZ8_jYz{oDlz=ukg3Kip*urs+`d=V|hK zf~0Dxjf&KMUGuRJrX!8>xTCzO1X^prx`{L1R;<&5>6biimtBlX<*aM|w$C>@O*V=n z{KjR1QGh8ZE~Hy2^)TSpFIBR`Hv9XJxR{g6YUBFnd?K8wca;eQSpvmo8^~)HRbn^`PE(q`H?7qVNa^ z87l+b0s4Q0uEzo)AM7uHT91eHbFF|>uuYC6EXNf@Gmbox&Uyo2KF$SvAb^-o$8efq za^j;9O(($RhdbRuySsLb=0xAO^t1F9uAG#rF&O|JF+wFG<#*Lk`M?&$=dFOz9jkdfEws~lIdK|s=JLwA* z+zK{ec60DtV)l;*w!q zET+YoS={r-4xH0nQ>=~1&(E;&HyarpvUiTqeA0>(K`^}N$}LZK#?HsGv61h=+4>3# zmFT4*P|)%=GZHhr@Qxi$AKNGnRn~Jl4EQ?C>I85sAybJo~aMU@6T< zo$6rw2P+GyKRK7pWXc?iM{3W*H*w-&IJ0D zqvk)z(@l#q*|Q5ewJne9lvr?Gg9P`J2V*yUtUrAQ_3^OOC~p-7sA5AaKJU?d^h5W6 zQF$|1FLTqp6D!o$!?H5vwmJX{nUbe8J9BDg~A7$)Q%Emh`cWM*rs>fP^?c3l$Zq5mpDBNx>fkZ zF-iO3jIUYaQIdqCjal|2iIRA^7c{iOaJ(wYe5U66+w$<9F+W7|T zMAYaUfV7k{83Mi`M8{%iiK@#ZD^ZOM678@W>`;uSM!>Cjs7Ot;Sc-;Y^CW&f$m>H%iz#%8%^^V?Prc7$8zXSKwGB!;;(Yt zqxaG?Raty>@{tfb5_^7!Hda>zUn+!1zrSP^I!|Xh}DXB`Q4+F!~ z_3|HTs^g0gjq9dDDKEDh^Wbhr#@i|=WjFF8ElY>d;hT<{+>ea;OQoY)yMMe9KC0ze zC|mm;dv(I8S#aL7cVzW~EwAZU5|^f+*{|_s&V;k72N-e$h%Mz(=Vvrry!*q!WLN0r z=Z!(Fv+eZXv71%27w@UWl7AFjtkC?>MaldJOyYD@xlIb`jM3E1Qb5IynAE^RVLPAF zW{jRV&;@fWvtf`98JgD5V%)J7LA^2O{^0WpATGExcgOR{cL#YPAv-fQG)5a-KY5&SR;^zdLI9l|C)%06~=&7r&AJ1WQ%a7KSy(gMzyt#xn`7ar{A2Ahgi>4F ziohAC9idZlkUh*%iG)o*~L+Ty2j9!E~I zegF(Vda`TB-UG2d)`ay{o2&IabG1Z6qA|;SN%R<(waVJTD@RB0V2ms`rHMVl3Xt}q ziGCaj*|TcZ=4>$Y9<=8A_gYI1Xcc`Ky0>P%T0;5`YKremSZuD?)YWU7CiTo!e^aV% z|1N6bgtE%}n46!Q8a-JYlWHnqa-$ulv*e1xon7&PH}_qK9<1_BE|0UN0O$i*hvjtj z%-5s*bnS=^=7ve-UBJie;b^rPACPO?`lQ3%^{+GlmR9DYe=W&wJw<3b`0U!`!596T z3+KWC74tE^zIg9q70KF~Ops~BnE66rRyX{rkPJCE(zwQV~usOvtf zE;Z2cAAQM^wz2V>NU5X5M{W8*YY*ox567`S(sKC|zr1BXLmu&=^O-d*%ZwB%7W8h- z_tA{w>O7^k)OZ%v`-iZh^IfL8(Rp>^p>#oVl;k%M1`h?FZp9T}?U`LX@PFvJJ7~PU zVq>N*p4Vjv7!j66Vl$hI0;JOEkxxq_P$$MWi#UNcp+=^T&5!QVk2p_uWi*+Cm1wJ` zn?YNWv`EU#krQrrdk$=|{SIJ=?s3HIQPA=)e(dc_RcUJ8o$I36A(N01A%`8T^ zzF*{OE+xYnA3%`c8Hde4V3W6b?FDjHl?)-iS?<60)>vu9N%SD0&BKaREdCY6eNl-C zF}U}v)wju3&h~QU$xoC~uS^w9Zk!*sW?wTd$Q2^oG&_9Tyy#kw<;>+5)9Q$&$H4Ln zczOIEo&X!4QMFE50VMMbNFzw;VvusIIQo}*ysG_rf=H|rG%>#H-FbCZmtmuA4J_{f zAv8T(gu1VeP-#BKe>au4H@W=RWsY}S&ik*BM;YUm^R~eer8#1I`0varZ*5f}mApVw z1Lm<~^p-?6*wWH?qADhA$22Pr-|SVK`oCTPu(gsV0fai{EWm1gZTk%* zhfFK&ShMdAHkr+rCk&3i^zKCiYQ4F0zG}+_x7hSb*h5atC65wj-13RgA8}b#n^ENo zQ7AOFwozk>bwFjdRm}^e8>M1(1!@6|2%-y!{=&^LpPaIicv38(3y5$Yfi=oO#${YVLxp8zeq z7Lb@CUFRl1ltDN*5Y5ln1BCfd3vj{mSMZvYVqZZ1qUr$skvciGx1ar%|FX2nP3$xZ zyor6COAuPRyHFjPx+@r>&}-3h={c4(ZqG7szk|5R~{QQ90QrBkzze>hqb;~ zO|c(L+K1j!T_hk#N3}|=mqh}Ug|Di$Mr!h4c^}7G$bVVuhP0VDfgvKuI{jVkb(AA5 z?~9bG*lmiagBfVzp1tranJ^~50t%49Ymk{Xd+k>XwXA)$+Xd7Sn5N&=UOk;r3bJTq zJ3riG^p3qF5+u1G9ym0oac*e>y~zJ;!f?v>eD$hoGj1N}NsUtbSd;0BwrOQ{)0Xu2 zA7zDl%c1R-35r3fu&iQmrmBPS&!5Z9t5g4--a~Q!)A-VOt!b>r0W_p7hN7nPd>PtX z^0brt$nE(B5Hz{q`_o*mP6Lj8;dG`n*^o7!109K%)6z zJ49tF-<-@~Db|=+vn<_=tGzP0j*LHI{%RI*FJUn&L>0(~2wg%XCAuDSg;CKY<0M ziG3WYtAXpQn(JD{^n&(gt|D9Zn`bLbRX`w-};WA;yIp{0OgFyn? z5>sQ6i#2;HNGf<2xRp~BIlz98)37J>hoWxpDy~ah!^X>~Vn;C~ZR`9{=W62E6v(B( z-o$ecJzF&q57}Rj00jn86;(MEtR)-?ao6cluuRH&AMW6Yt9E|EEXll$1x2!W02jfIx&_BjnojC@uHc zK~@{yB1GNvoEi_Ec;9bzg3ce=D9!Q$#Hh^G-mczkgJZkO8|p zLHX2t$|Fxx?thLA$do5JfP-e&w?(8TLK{UT?J4rCci%5Zf51xnzbmlcbaB7!(cf0> zrXHSAzl#uPVnf#Tvn4vd26D)o>uPHJL`3_+6ndA{kCja<{Oa}&)~v^IAa7oN>#5vt zV^Q%r-YEKY8Xw2kul4JZ68O>=`PMRp|7}C1rh{pbfyN2Q|3lSV2UOKW{lW)9Q0Z=v z?(S|7DN#D4k?uwg2+}DC(kb2D-65cKcS%V~^Ud*j-|ybbKfpfw>^-w)&C1_e10hKV zbz{;1tftY}o&JUkt(wW{l2{mYRgk+b!)fl~g#2qJgQmo&2}(!ijTESj-DG50LqBq~ zdK}19G6|!C{6-WBtO*T23aBhudHoi-x8yBV9*wbEU{)`fN=#B5K$^&yvJWBnh|7_f zyTTy<=v;Cj<>Ua8hZlWK&>Ag$u0wq#SXmIP_GYDzL5C6%(y=zd`<3}SsHc^YA$w#> zK)`TIK!8Ak4FS4eGr5_`3rCKbhK z=w*T=uWylB2=+AoHrCq_d-Y#F`oO`Y+yq2A=%xo0-p zJbRpVd7%wU+ST5D3F4Uj~R;@EQ!!^8{k(3$Pn%Wm@(nzOh=Mm@3Il zD{=Jy=Lru6DSi-_EZ4q)jInYC&uX9)hOY^k!5u*`8hp zZ@VJt=q#u%-t<1)JGrr23LUa55cu_bp6L-06Pyj`sW7NHDedM;TRQ?8K#|Fo{$x)G zN)kYBK4W4a_M*;FIo*Yacu7wUlxa0Or*4*mXP5iIRQHc)Lz<^>T)=NPSZ z3D!b4WCCS)5I>(AHKS@&Bt-c4JO6T|pd!}1Ias%v9hR~2*oA|%=5CGgLh7InW?)@9 zL_rT25N>BbTsr&A>(hVri!1vIMwQlF9Sbt^DA94WAF<*q&Y*(p$<1k@cSJtxO{4~L zUcGEkpJf~ZwEtdR@6GDfwc=7NU;a_&3KAw0{nr2iVpUXfQ3A0MALr)3R=LGPCe;(3_*_oXpzSO5%RTGzJH!muUV`;ALBIwjCcq*6prX_MO@=-A+^TVF zYv8jxC#>4xKj8~d8D#Dx2;P5&0Rm+j&gZfP6_gP{ZZLh5kVZQGwJXs^IuG}okksls6we>i@WptWXMa&u3}i;30sW*%7mdPKTX0Q|KMjue zx>c&c7;p^I;m-KI1^>t!4_-~->^6@5sQaYFJut~WF_2Kyhcxp!*9hRa%msY*2rJ*s zh6LPMh@Kt*s392f(-bi)^b9jnFJ%e_=b2YJP^KGt5y6jdo^MtB3!CK%rn`9=d7>A8KZc6YC|O|?wlC9f)Agob>j537^m;-I2A zeZ7FTK0x}xnEEiYKMi63{VH`*3N`%56OrXc%S%h)h_YFN+{I~+Fg6(dI$P)L;|EJ$+c&7V(o@K>uew2krI>2!i_ zRC*U?FquQ|Xx2L7%}U4MH_|6g32ml#FOeWREvv@QASIWYhc3!;vRI%DmCbmK`aIM` z>OFD-+S**-9?40g+()}%-hlAbtWB0!1!?KKm#@1s-F@}2*|0F(l0J*}p1@L&=JWV|M7%drxll*-I zi^g6R;V?U^{`e=|d+N?|T00~9%yNE&$Bs>fS*5CS!VUJ4uLu?=Z^J1d6$csh6N8eK zsq|*UQ<6YIB8p(2KZoNZzw~~CiI~?f$>F!$9wj&C&^ar6x1l2t@Y4_4Av4wxl}7o^ zFKgGjuQwLRTAh|rFk|Kixg(dL`}B$xDe2hk*ThBi_Al|RgDd5(Dl`dJG4>BwSGNU5 zKOq{qUG0bDpMjVB`E&3{fbD1Ja3y<9_o%4EX0<0%8q?#~v9{`Ax5>fkh4`au1Sy;b zPA8SYHSb z@ULMmG-+dx{=Y7I$X&+r;L}<7jp-VV1)1~C7ljw|e1cA4{0CWJ9C@6#ZuguwA#evM zj)|o{O)W$YXK?6a57BTyB}_*sor91w6HR2Uku-N$8BiwRb)S1<-82h^LiH>~<9pu# zRZxb2&nLo*g^Gr_m~e|B6JO7bMjVA1t+Dmr?Z08&{AL6Eg3&!ZUg(@uD!u=19QInC zG0%cO$OL9#8LGonF_~25>s&V-)Ef)C4Er&pDuCG{es!k3zkl5$%?3P$ zT^&LDw>C92nh7BVZ{m^FlS0x-#mv+C6STAAi#N%0I-gzl50H1R!TOO^urtFfEZ8H8 zpaQ$t%onp{B^a2v@4hDIUfDa80AfH&P+=M!GLENSy!TD6#ZEz_&bSJCJ-|R>4S}#1 zCn*rX`?&#!l}Dk}8PJEUO3hVEK&nWu-3zoj0blg%HL3LPoS*fOggBVO_T)FFc3 z2CO2Og5$qgb}UCQ(cGI5pu?^WcmG?Q3J&$-&zfSL`ZwW;H?|JEL21943Bp>d+QKMfg+{I_%^jc~~Q z6Pq%Oc?Dm;8^6fNhKKmMuDYTcehBHdDSGpTMrNuUvGob;c{W4j6uzG=5UBtOwtZEJ zbBwLds`Pq1AO{Gg=eCUM7#G8-6QBMqBN+3<#{I=Gn2H;KEeXZq@X)=!Q3tjaWIRez zhE>h%@-Y-NK|AhD1h<~!n~>yv3x(_84e36h*DoO`H_ip*sWCZ$Do7@6G98Z|N|8aRmInCwTpd-(WNdigNM27V@C_5*ns%?!C<&%%2_?L;&E znjF}akQ#Z~Zt6Ci1iPVQdve{_YZRTmM*jw2 z*|W2qigy3os?FvLQr`)G1NauC&YypzO^Y5(3j(poI8m2+J1Hqs*OhY`_rH{RI5b`ohDbv$ygn zPWmfuF&Myv7~=-5p4mUM%&CvXn6^!>n*-%}hg$(!HKywFtF7Luk`WrtP`&5yPau$6 z3{*5M)s7!>0ReQ;h^2pG?!I{4RvpfhTx1FGoH2t~EDw96(A8V3ZD_#mUC()s2Br2@Xk$nDEO{7_Z40V(mRks=uW z?+<8OD7~XOrJ@js)|!k`aC#zmHiIKOc5BD4+YtP4@gL z8S2wN`Eat@mB~yB|1H~-kAPUB>*QQLMht*B3l!LufuKTzEr%N=Q;7#Y0c-k#Ab+qQ;*8Nx%jKHge@2Pld?tsd3+_ zy?)CfQ+Zb4j>s-aVvZS>SGql1*ivA{vvFwDjszk@0JkCveMv+z5;he|B_#^&c!9q6 zWoH*?C{9dFu~%{`YxH387)td@?J)y_5+S-2Xw^|JmA_&Fl|Bb|LD6Nwbeb56NForC zO3ys_)1y+eM<``RS4Y5hR2*rLK_N1JViU+ah_~h>7@1F*I^oDjBnkXSNb5IN4Z9Tu zIwu;g46%{%LOzF4Fu!fQcULSAt!z-RWQ9A;`vH#mE+R8stj0Ff?_8bO0V>ZggjX6uAjO!3a)L%%Wsl9;;MY zQZJqUGw03Czq_SB@dYy>9E|WBn0&9phFFVrSlSXaxqrMsx7qr=J#AyK(xD2*$YnVz zzR~$22*D2kq|w6iDx(*7-p!@b@6{`W&A)khY3ee$)noJ&;wQ!KXga*jVy2y>Vy=`C zQpp^leJg?+$3G5s1`(MTd-~D2Z9dopN|&V0Ik|$@ z=EZ@L-$!o@ifObL`F6k?dWUqQWn^0hhLt>i!v*|lc>+C}*qV|wJ43A>-a~1)K3pL_ zf1WTuf(&TQdhnOqX0r>616%BS+zJp1P<2+-Q#>?ouq9-7sWHF!M)a9mta}5c*B3~! zi*#1Fz4JV0$s!1AVn2b-(}A4h38^lcVn_%B&)joHYtDDnkiM4|c{Mm5tH zcJI*|JV*BkP8z!d$V8}sT-=rFlV%2^Ey?62w+|unv>P6cWzyW6B!-a-0-+7$FA3Lr zk-(xE`Q!MnG#e6CwqNigP`k1~-YH5%cPM5Aa%9OfmQTzdlfM@Ul>&o>7`_kbZesev z#B=DoLbT&@bp=#`?TR<{71yG(;GdMrZ%5A0JpP-xL4W09yCvCh3mx z`$2)Wzr8A$_H)%xIBn&E=^_xe90}Az#3!{aDg^BAvUoz#Qo!rZt8rXuUIi*#z4OL?3eQQ1fBqNQLTuUF8ewV9}>bdUZXq(EEFcqL1IZoz*YBl z{Icj8ylk4BU@dx#mORQ0UfdvvoB@A9lQXcAVx^M8KD_K2yj{cWfVkskUzY+?Vf3w4 z9rW!dY1qmn(Wymu4*~U$5$x)pZK+U<9$|aDVSNqu#evi8@$*{|0va#?mJQiB(^>7Onbw%}l+|1M(70h+bx5J5IaqMhgE==2M_@#M7Q)bKpTMUq<}9 z+4n5U7zGl65lpHkh1VxQ3e+DAlMUe(hsiJp3;uLr3KvxP@vQi%PrwoY{W}{P_6D9+ z0oCo7M+=Hm5uf;nbKOgYrR9&C-dmZ6YLu;u!$ZWyPJ`GHA%bebhk&_(Ff!OmjT$uR z1~oIF)9q6YG}_n1*m6P4r`dCFsQPXlfnv`julzw1Yy#HF5H{|ZIJtnpBE5ovz#?JZ zO(~c(sbFHVVVd)!F^1{SjcRwmW$(Hqd-vBE8rv2CJ6uhfkRi3Kmm7mh=!iZ zeq=euMl2bZ8wn{*mSzH~8RGZwpB0a$M5+0D^R;x3m!nR;gUyze&own@tpwAK0U9^p zw}S<>%oJOGc)W+8eW0A#NY}U?P)m@^$4tQkajhBl%f~&A0|vk=6?`Qm%=#r2#RvXV z$>Eh2C_KjC+q>o~Wd`YupHCn{QY3CK!~Z%LX_$ONRwsnnHXZM^*)gqWtz-XNFnU@J zKr7}1;TX&e-S*U>@IGAFtH$&GS$IFob&RG=4}=40>lgjiVGIlLfuAx$a-!TE3scv4 znP*koJGJOy+Ox&&K9Go8+*tKpjFs*9#jOaHX#MKCLl2;>0+Cfu$)D`%R$16ag51Eb zR|KGDOc0`?E&sron*z2FU3K289%)ah`8UH=T|^loLQuuW{M=jg2m|ee_~xYbCB>83 z7(TogtC?VRzg0*pe&wZ&Lb<+zV-lt|p~Oq>ff?BRibW9|5Fpfr3MwfKl)t{1`tboT zAw-0b^sxT6(1J*zZ74Q-WkF;x^eyvecr*w^-?WzY#&j1y2t*_yXx}Q`3B*E9ASqHL z({OS9LG~*O`yv-Uk{Qs?{L71J7>3G!b~t*N@3IWd#gGmqmod9C!F9DLiOb; z=!#Gn1sv@Ap%N~FDrBgm`Bl<5m)1qt zEtjf{cLhWJK`pa<)#PZ!HCaH}6ioqws9Q@<-XtO}3S&B^cK4$@Ct52Jh z_~mn;ZKOu|1(TmNMe;#~+$KGyD0j%VdlDL|@a&nNE}Zpvc=R}Dn+hKRg}=H6Z%4LA zKw=85>Yedo>vC(ap5Nr{?0wG4y1Lfd!nC@^!SboKfUvx(l~(Do$aJJ@_9?aTpEpW+ z<+g_h8|Og-G=`>-O!)uHTl~yl5mb1@wX?YJ|!J zec9FQyO^HeY!US#r$CKW8LJySlb04^`OLjc@aGTGNJT`JZj+Y8nid#vpH*8bZt-ow z6QO6k0@#hQtLy%v6bFA_;s?;4NzZGwWN;-Ay5Z^;rmQo7YT0V!|qd02SN1$F;ZT-G{C#R8}d+Xw< z-kuh}^C~QPAU@*w!oB2f{#J4TemxaUq)>unnjtJNH#~moW22Gwn`8Mf;9-<+55HgL ziO_JYP_JVaKxc>?3Vo~m6?hY13S{RISBv~4byXsmTq4xQmzieA7LB+X$kU}Sr5LBb zXD8@VP_BD?c)3pE8G+pQh6k~El%zCfvdX0r0ugwF+YU{(+C_E(-##AT_^#t?wV{BT9>#4%e&8%k{OP=BwNUBc!s75mhyqAwpy3s;t1~R*qNVqeD@M8~Xw_qP130f~oJ4N5J{--EarTIVrJUqdAw=@U`JUEIc3=o)12VYVL#K1q^HbHSm5_}%TTqOQvLIV#*7 zo=q^jzQg=nR>>#ZYD3EU(O*|$vbZ$%kVfVD6w6xVCRT%TL>s*zK9^DV2^d;+Y>wwZQ`S!MTz zRL3h!k=X!BhGJ){-wJQd@ONJ3=b#@`=`Qc1NH^>fem2%u8@1Wf*dv#+B!FxbOjT^6 zUOIHy9PCHO*r6ZGbF-w6{-fxsfzZvNYxNjJDKzLX+Uk<6kv) zwP0I%p3~??+V?$_JmD&1JuG;iD~nl2J4GV8Ylv(~ri}*^Qa^?4_c)`i(4!dy7s6aQ zT&eno!kG$Ta>KJdOex6W*^5N>Th)RAU?(K()g`cMyukH5ovnx_@93=U*yJ`*)p{qO z+N3Y9@;UeotvO$URi*vsL)zQ;gw|@z$A+1-Qz6$KWclmMX1()>{aFU?`TEsOX6pE> z{`>I`J25WjBax$72F-I6bMt~XQE1IisvucI}?_A7#TUqE~o zK8`JmpdT%60%ywTqWWFuak2-dHJy-D{9fk^8v8GLlt6L_ULZPJct82`=Q)xif%xB^ z2~TWWa?43&5?KwM9Mg7sqx`3_vb2%iA@r-;bkV3LYu{^u9RA2@&D>Hu!1ZgM#OGcN z7(vn{Vitj$ee1z_OfMD~&`k8`(l`3jdtj8ZQN=MY{J_r3enOd$ukGQK%mMxn=HqraH9K#F_dDwJe9~dmhdM1p z`c!dLR5c;~+En8wH;D@}@~sH4D{jp8rO!Yp3A6_icJ347wZxl7W2vVcdkn*Qjzkn! zT|PNPcs=~6fj#5+^{-;QA!0|*@pPNL_y8q3NoF1Zc zrF2GC&Hhd^n4|bEx?=He*BpEWE^XqeKw%?wlTHgdd+B@E>)PQ zCy`r(gUhm=J*Tw~Yyea=*?@pV$h}RuL@7uYN>UKn~NJU!%Xs1NTCB+ai*o!O;At|0!)**c+_pH&~h;t7oA zlH@~SQ&S)3>d?htmLX-{CsJys+(zjwzkE#854J<#x@o6tBq52e3Sz51RZp z_o4#F%N6Q)eFJChl9Y8+>Uo>YEVjd4Z-@~8dl|j$?zh$!WTxo4@bbCVoR*>~_GkB3 zZQ2tROA?ftk{Z@XeK(6Pm9Ycy%%>e!rTa56A+AXYtw0;iomI{Z5z;(xY>Pj(<il_hE0lfeVa~c9^>mn!`mav zA}bpXS?Rzcn}w}xAExwCVg(^x@=mFwSFIlSktNe)L`1*yPqSr=#|IQQv{A7tk6J}v z_o905NLYEP4lj2q?n(hYL~FNZk4@w#EHi4;_*9!foET(Gnj<2+Ki+{Z`mcU+JG1ou z656s(t~yPgkH1aI`JDBar?@^eXbS#P0XWSEJ&e52i} zp{w^pdy~-ewh_FVwKcC_%#OKg*B(u7$9DjTl&@>&E0bS!aE?en61kXCx~3%Ps=hNY zX65#cTqU=)EWM#&@%>CSAOF;L>-UBlBO>FcrJF<36V$rB@tL*6+0e%_)3Hr$+T8Y z@z;?0%{ufHUK6Am_KoYP${8$3&Dgc#xMAtBC!m!zf*{75@47^+g~*?IUs8(VxQ zzppFbAGitn-=@5RFKZJMsqxg%Rs8h}sm3LVQ{ns2*JK(WgTQfWrFPk6jEDD-d7sOL zzk&=9!;xm+q#_$jH}jDJqAtu)b+O74%VZ8DM}89TA&FU06gYIY2LAHZuC9eLotBIR z%Un|-xrxL$!Bl0FkJA`gya*+v* z#*5Ujv76xaJ?Q9TvsFEj-IH#VN;iIpf+{Be&BSiEQ0njOj@t#gS;@3o#?8OwA z)|i1L!pPP|ZoGNUWCq1wN+z*6>P{pjHG z>Lzw-KnPyV4|e|bw(;qsu=lja5=HJ)A?nw=R)#o;7TkjW%Nko@^k+`h4B?irOL?6`asa>Fq( z7FOZCm9j_<;V~saE$wOg5@_oQpE>ob_jQxj^M-2+2aM+j4+jjzw&0F*rg=_eE)bsh z!c_T+MtHY#gc})Hkm{9%Ef%%nT-91)?mCUH>Dr@Tf4b+G35rGKog}iKo$BiqsF{!Y z8PqM&$6PX9k~H}+x?H;$26NGZSKSd!^nlY-8BiR$|NZE}|9$b#ptr;h0_Qo4f|$;Z zX!%BkCE3#>wemO14>id0m#ou-5dv~#8~z+l&+qSh+N8nO1d6TnhWAT12O}*X@+ZvC za4wtD1f}OjnvYFR2ELy_GQhUx?mOz)pv^50zt6q7^@8L;S~^KnTA(ey!x^3IeF4rw zvC22izjq0a)~mHwnqLN_KW> z&nj!_?UQ(xv>zofP6Xh-UZ!kRYv*ulOAmn)mva<*IEm(XG4B7pU=Zm-;{=2r$JOWQ z{GC)EV_K#wilaShRYb1huVacs$uhP3N8RmoxH{e}gznXdr{PSV^evp?j@~ii_9Ww=<(3 znGcleR8E2gM#xW_&5Wegibcmc9qXj$_XtHdlM08vhQG5)&?x&A5Z`CqaVkhE5-5h? zXD40;*Nl;idSCU;JnTe9KXXKuCplF9iDx7?^;rMWI_OsG?iq%!fsMa&t z8nejFOSYrmb8X2DG)vHWR|SvVflZrP+)vJe5#+P{Av*SSR`r$YN6RsG?ZsqX`yHF5 zUIy$rK+=q^mP0ai?J+qJ#^)2B((+n=&9TtYemkr4DkXIv=npyDemAP%#6XVN>`@v{ zI?0Dh3i1cu&{tpi)M{xNeqa9Cf7zH7x1pBnIU3GvlkXgTt#Tq^5 z@1|b7^aF>OlM{QxBP?yD$`lLr;;)wmbD8euCmY+s3yZb~I^3drPn^-t>@Fn_j|K5Fpo5UCsb;Ri7lSnHdDL-lE)e*&q`D zurLnePbc$4i!}F&;Xgk%v82Kj`pm4@?!6Tu{5KuAmSAHfdNj}fMMG!a;l%Uj5r-|T z-N<8@klPTh&`hsEchg4seR@b;&EQ|TT_BaKrMo#^D8-8TQ#~1nx5!0jF?h{$I6agM zb@j68>3V7ma>lIcPT8L~l+9l&ve&-8s*#tfD~zOjE;#e;R``RYmyjZO) z@ML}Jf(`MVgGDnk)|--bL0~4iVfpY{VAY8i!FZr+{%T|Gde3)dji%LLWtRB`*E$l& zZ4ub}NqG|jeeDJkzwTTz2u4Cb)uw=*cf)UA-oz9z@ibE0j$0)59Y`n@=+%{Snd|btOH`iEtge-2QN9 zPtDdO(W;6|5Odh(6@)2?hY6SyhdazKLs5pLfr^ z@h`oZC$O5|e8E57VHYUvMBDdNx|fXkheB9))^)IsVuPw0e8NrsKI>^suEgRk*XRu| zF&mYCj=oXx&>B9i)PpASYy!0*HLPfD#D2_IG_43zx3MV+9Dze1z9LS7SgJe>(zJdl z0PA$=Yb^}o7{CE>_{h>nq+iJ)P})D-oE{NnOmZ_063a8rJJ=MDvoT|D(N)UPO!D4W z+xYs(%!l|!KG$?HBKj(6mkM>W-&zC{ctrv01yGIX9^S>2CXF zY#l{qWDt!gYzcAPc>jfkYX0bt4`BJk}d@4Xxk+%xx0ls!03n_E`833l-b44)%;r)a2I1t6|r(+q0C@;{HfvGIE;#G>3oo#1EXl zXc0blyGzWp)G<#j!!xtSs`jSd0zX9bHYS=p1QDsVWnYckR8Q!+j{?sjr{L_uCuJYY zG9f(>|Hs1X)iqFJ1Q3)CPH;j_R9?SqcBjOKB-R<{r3Cyimud&_Uo~DEn|G~&q;W<> zRB|hwxOaIVVe;dLclI3G*fW*78A`xRbz;Gh7T9c-g^cy*a##ZAbbvgz^ z^RggFH*QV|T%%w5-5#3&gonuw3JNch|K&vP4z4&*zyY~hv$HX5UzqkZtBqZ420j$Z z4cuDtYZ%Zr^2+7J_1rq{X89T|0Bqha?Kuqi2x+#~A_dNp?jH%VYmNIV#&=G5{iNW! z&A%E1h@rcGI6wfT(pMJ8X5%qBb#&|gmbjtnL65zwcs5#tdI9%;!wyaJpp2{hcfj(Sj&5YuC|g!} zX@J_oB&(VaKv8;Yfz?k0$#f4g`KmqNqNkYbVqySMkUWNw2|}4|;Sdu7vS&mj!k*kA zFkoT;C-m7T_1}X3FbyNEBgjNIh5Vh#@VJ%`^m-xn zWE>qZR~`G~^@kbO_V)d6N@DjBVg!OdM?$SF_U(7=zHbN2LU$v{ACzA5J84PbWMnXH zR^56ZysbSQe!Rgh)S<|(Uh&E8hcAd;L&i5qgWeEUj|>)TmcxowJ5mq&J_~;p5CD(g zAMCl?$=It`RLmeE4ZnOCgA+8~dw_SN&@I!cNYS#WYWqQmX_f#GtP)6&-Rw1j_!$N# z#HWprdw55Jjs$ES%A56@Ddh5YLQ>yF+UTa3;rF-X$8-tp^X>^?R3?q^m@FTm)%`n< zpiPr?!jhq~u_W10D)VNQ=CU_m+Ku_GPsrF9%b4$VSFdKbN&g9gHLFBM3^v$(#z=LT6KZOBS&v?b=s%kF*MANFzIkF+3x1vdOmoU3>_Yk-t8$U@0Y`XGy%la?C|--Sc}8SRNkZ7fLVJ3 zRNY|TWvkVF7`eI|73OfwJtxA-eJaOt0vs8`F5uWP|}W=Dh3ms5dc`k{~+)8|U& z^j9EVUbYl(QqBI;y)^4#jB^bfLR(fw$jS72Sl?Js-D45>~Y$Phf3um<2;dELvC}Du(B)dmpfjn+5GqHIIq{Y zLD(SS>(PA}n1c3*k$PQn+){eXQevE${B`i~84KF@Qq2|k9+HwxTy@Q#F}1-r=9uMm zkYJcx(@hoqo5ogVV5T4ZtI+;nLc(Tc`vc#G-|p2$;G#C3YVXcY(@g2077lHL$fwni z+5p6n!M3zGFF^qgpQ1g-BbHyw|ukbCY2p5#5&ypIvRTPOC3pIFdLczB4M5NS|oy=GZD`#mR@ z!ivzGf+wckFxKbX`qGE9eLDBT_>lQacWO`S!S7UVJi0a)!PBluRShq5VSh7u&zG8i z=*6B;5#!=9ukiTRDk_U6nZp?-*UkUwVBiGRuK|?=;=9U72@Xmn6r8*?0R%} zKEmbS+$N*b9h7pG;oJ9Ge|{xY#a>I4!{@bwH*KCu<;ra9_7?akPpkmYk?pQo6L9#{ zsVg6EQXD;hi~0Xz0gy6cMAGB-3lW;x1@V^ltfRy(5v*<$hv-mt9knz{ls~i7w+&|d zq{+c|>9R!x-`gdWmf(L6lwKB9pcOijo^_`bKEl;2vD=^Tx{vBN0(7_?B5&50|11zH z(6}!=Ni|HapUO%0(hWf+0$-WRL`nMZZAw&XQMvl#4dObxpA@LvGL-Z0 zpEx(Y9r8XV8k-$^*xT0OE!1gryY|7;CHUd{KdUQc7?MK|Z>y70IMB=SNbQ7%vhp2tg<$5PhJ1}`Z! z0=n%|lLb=R?nM9T1Y*a;)ysoIjc3kS&Q%M}RXnZ!C_)O!qakCq-L3JZri_Bz#A6t$ zO?wlWkxo!zxtDvw&2-N`(51 z)ZXb4$l`}_ApPuH*&o*MSF{>xr{Q)s(`h#;MhD3h2kb@$oA*<&k9&5b(oXZE&|Nbl zzSP=H3h|cx__<4c0u{D|KPLl(V}bQHwaLW|$F1u}I(LXnZ}VN;=6e_}zgRRfzL}hy z_@K>3v4QA(Fw$=Meq7vuR(4^!ZK>@+Xj(pu#n+l%8K$$mjxb1l?+SNDtD8IV3M+{S zed3z;@-u);A@m8<31>k|`4#Sy_aU9boP+OiYvyfjtky$O%&?pAlU<+GPXcq*0-hbu zJ++*x0`pEt#C;iP3lp>7#)dJ3rPXhq4(6FrRiBJ3Xg*j7oA_QFtFlj<~oPRUx9;YHuf`h zRo^QXjksUBRB$VbiI=DQ)DYjI>zFIMxk(x;^Iiav6{+%M$#qi~W)v|9C{&(#2t3&p zIbeSNBOu8+`9n8h3drN8#HFRhB*r0SX~sk%qSsANkyAh` zpi^Pqw@(s56Ozp5$ZY5w8Vxla8k;=#`Gxr@H7~};DswiX`Sknw?$5dQ2N7Z_M@||ifFp=PA6C+a?hPp*sUe&Wa8>P z?%)g5@xEwDgU49eSot@MPY>un_eX7@cecF11r=&@k95&!(N~MWBkATCVxCeNR7>J# z;(qN7RDRuh1ZdX20q@lysInq3dewU4)tVGKe)djIi;807$mwA7QLNp~YKF`0{(Gy@ z;euR!TuIy{*ozN8yiv^<$d{CV{~T0v+0D(TJP>83K7G93Zf&-7Y<=14Y-i zdXD)YZ~t|Eu%GQcmY$uN6TN9J8?KJ^85=}X9#|e3EK?q^8ym!%M#fTrZ}s0FsYh%1 z;l2qHHavUFZ4dwqW@Zw0y8{NsQB8Ky-l3Ow=0>zgJ;> z+fB@T{1==7FLDI`uojJIFavuL|SKi`a~ja+Z&AGuB$>w315TBzr`J1e!g~ z3$FJf%oY}|lNHU2OEvt&V>M_lqIbq;gVjbkf|Oo+E~e&`Jz-v=pdavcVTfbrOl{!p z&3(H|)&NRWoE87_dl}tY8s%mU3=TpDG!TKK8g~|vH zcuNcT9eTi1vM~;1{IvRNA1gjjcXiK5VxlW4$o^{)ZlTVcCA=sl<2LUKyFQT3OwCKS zt>=ALkxNHW)ap#7LX=9tT4cf2O@G94B-sAG^l!=&-{gNIOLl$-C_g&8X^Y)>(gaQt zswg`3OUUr(%GPn~DD=@{mIzRo;<6Ygtv!5~eot|NmUh%_gX3t6yVYyi9EI`zmT@c1(rTY)@)mWcw)B{ZW+*n<^z&WdGt2=kd>< zej=e{9_p8^_I0%}18mf%X-g#Ic9$GWjBxrPpf{xO_bIL=cz=xU#9+>}19RZI9<_5GlxSiecj3?E2pInD!u z*-5XgrhDSQHJYn%wF5YS#aikdGH{V#vc1d%nKU(yG!+P=+q0jC-`f;V!6pri^ISOueK3<&E!8V>@b_9Szlklb?A7S8xF2)my<6EuKAGnbyPbQtGg@D! z`ea1DdTbE5R!qmO!+l&BB#nP=QULD6nasLHCjke!&*(05@5re?#o2xbTc=f?4E5Q8 zS_^ZbP%gUnyqStk9gh3$LqPC)?!=d!{OG&$(Eh+7sl6=B!mPGcv6791Pn_C03Kj!MGJAt-D$FIN@KS{sNC^ks3ZT0W z(_opYQH^V9lU}xQ?44Ew%6NCZC&3d?21XiQh5L48@p@y=dByUE2f3Q>qIyf;HyIk+ zKA~crrVR}5_ZHKHB9(Wz!=woHAAAp6bFIvvmt1b1A8!Wn3veqZhE-6nsXjc%X;?&oBw1O z2-UV@TdE%AED=X2Tp#7hoKNyCfsJMZGn+2sX?Tlr;MRa<2Xg?RzQw9~dvj2NEY2pt zflzTfmzQmfp)=uLrNHc)>;BV@-^iS9P1@z-U8uenVLK;C>!47IiuHGei#wRkpva8TUN$A59thL@<)%RQQHC*9^ggh3 zCGgDUCCbI6LH#uQCjBI|%C?4-9?Ugmz<1;A;p2U}k+sT=!^!VJ&9*#Du(qFZ zX>8}@6Zetx^ElV-@%8QOz^>ifQ75!F-Hnc&pFIX0&)+2r8Ppze$pooezEjCqx=@ww zC!g8(IhUmFNVRcRuH&LWcUOKr71kzu3LN!=LOV1?)1Dou+uf{-DK!yEPao&B3b`!b zm^Xgg90%K#>Dt5ggz~Tz&b{0Z)(`(*dvEy{)fc@D4=R-Da+mbPTdIPuE&eRn zZ}A>ZS7}}JN{8;!z`t|`x(nC(o7JnVO@OY<_<;kwMlWQ2V6%)0-5}d=EL)y=(qC;c zJsoOr^NI$#KAo;WN`dEnbJ^yfDoQcIQTdpSm{>{dlz@DG&+KIK-kK5eNL#G_9X-n z)eKCaeY5Z|i0bSO>|IalVLYh!Ancp^HfeR~`&H5}xLihERT^7nUegD9 zdK@#x`i>V{x1E$(1Cf2{;uPD`xtRfLXJ^C?38g&0?<|j~fCT~4eH#8_+D`?zkjGO1 zrn4$v8~r@n8tt9>eW(RBqo=t|Qi5CgW^4Dsvu?3wK&F>GHHp}~zW#WfNi9(XpEjz$ zb)COF<(^wby5Q7Wu*k7sSd{k(DDwSS*n2JR=?z2*!<(*eafS!6}sm`F0UiLw_l z>&0_7{N=IPx>72>1$;#PHqGT-ys#@t8Wq9`6W*(iPdSE4O)l_#T*_T(bn7`Qvta~mB^T?(FqkS_z~?=E~kv}+#0o{@647I-;7 z;J!mfhyX;;np4aTQLtx-2QnXSEe0!dAOlx*9zS$|0PbPGs>Timd=5xlp1O225_`aLGjZDmL4v*FcGQ|U%-o&h{>GXD?lscs{;{uU^S4Q5R)pwWY zZ2$n_CRjd$;%fF!`cy}0Iiog~MujK#c={+qH$Wm|v(-G+?iZVZ_Yx{-aA_2p$E%ab zCUOwfvbnwBi7Fim;&?>K_30sNUB-U23-U>lyX1+z@`F8>b*3)EM|wt{umXZX zz^Q}~B&$!cloN@(Kw$LB1qD2GK7!5%MZqpMQ{DCk*W~4BVk2;#f}b)q+3IZN_c62m zdvzRBuq?$*>}ywi0zx^f4ynM`E8z!}2{8xcA_|7vN8vA6j!A@-U-jtMCE(XiTMP>X1>LiLTT7;^Up9F1QjhH>3Oc{&>awRlcrir(5 z8l220$`=<{C8&U-ioi(v=J}9Q7qe?E-Dgvo%cmeq+ZS$hn?4KuEF|N70_%0v%2Bx? zavK%{weg_r8*Jq4fLwchTG95bsx!$1K9phqWF{HISQ-8JBJEH6W}-&lx6J2I+3iFm z7pJwJ&h($?8D?iP{Fby}QEtb5VV{^QqI-8G;9xIKlVpFL<+ADK4LP23(uP^I-u2sg z5YwAIMxMwZsP{cFxLQDhE|?_JCCTF8gTUaWX2L`N_GGP=dOPs6M!h=yX8V1VA_UqI z_AH1ba`rv4hSAx1(|q}pyGpunv5rZqTufel>5ve;v51 zg$*+hL81ro+RumYt>#6UX+zu|oR|q{Mz;;N5M?m{x5^9{)!u+ymUYV}-=SYv%%l|m zqO28|V%ep~+@0TCj!sD(7H z{=Wa;AAxNue}LW_e?|GRo|BIvRWHcf%_f?T+~^pxwP5+IN8?`i=A z(wFs`T$ma~!B^7J_Do=&ctnEq|7Iz%;J#KMxEdzb%sGEsj!L zm5~|YU;($2aQeh_Saynkin;yUThR{d#DBCa2Kk-B!ZFRGRZuy1OD{IYyv8|yF3n8_ z_?M6}5%rK?RFRl9#fjiim4Dp&H(M4f38UH;v4RLvsUC-6VFMzZ6kxSNjM0G46UF(b z712kBNow_NxQr?<4*FL5sJ+(SPu=zUPYWs&gW`mt{9G~8=s z5r0v8Dx`~mKO}zCQ|KdsGzSjYRE;Gs!~E3_l1bT2W-nL<+&5JRnT_dS2K0HPLwP#? zM^(n@KsHrpYet?k?frCkEdiYS{*WuPfGyup`*1thC^Zb46ZJ5|S$Hb#v)uC=N~5)P zQy;Fx0XD(0p}*HbQ8hu@>Rq;ecaQ3pvX;6x@x-;NBI)oounXx}Tc{O|oMFs&dWg4S z@1DSQn3TN7TA@4Rj1wS2gr>dn5laek392#I9wb+QqWW*&Z2SY9FsP`Q<5}1#p75Ae z@eon9mRB|qKWp&dJBUa>kn2bxd=gL{`-(4`oSF79bbFRM%6v*PAUA6 zUdgjXW*}*Ys{Rfjz$K+L05;7%j3AlotiY>fYO{yNfrXE4bu^CwiEedszpQK1IT&k} zuzUDZ;o@JN$V4wxYI)YkBF83*`UE#t_2vV5gi?P&IZ@;XIsfW}iPL~b`hP$nN_X^l z*U;c|9wE6jiTHbzzTwA*X`?J%ghear$+&lQFGV%D)YS?QsQz@eJS**<-=Lz!FTi!@ zq1W+z%0A(X`)~IL)RfwZsyHUTTct}O>JPt1$X%dr6mn?g=xAt)5qCCz9r1mFoa{<> z4hU{h%0+#9SGV_jh`90l&>risHG z&*xNP$N{suv$i_@(9NrU_ z$YdNsB`Qk3++JhDv=L6Q-QBxV^-N|Y(x6QsuWdXc#cVyysfMC4yLobFrs^1t&T8|Q zyw<=fkmsTys-z9!|E+T4>zZ6WRRmf{`has=xqq)CJ-#=gNTje0QkQwp7)*3fuYFsY zXW?1R!hF=V6E`$;-Ms!!y5&biyrc%3`pPxT4&yod{^4DWmoVeT0LABGUM+3w(v0z> z<(|V0M{%NUPjR^G%jUl`m<}yul@MB6$4bVjD*}ZRs^Two=XLXwMv*8ZcDiNnLs@Hq z@t3u{57IygpUe@!6O3Vu3FPt_?BC=pA@6rgU#TOpwzy4J${gr>o z&L@*2h|(DDT~={E|NC^yjww;hx+ym{)RN6(Givn5w+dH-o|1*6q|4ynk6qjQ0UNSM zrLJEbe=DMu{%;y{#X}Mf|5t zgOB*~5$$-Ri+s#vQ0KNnPXvg6y#~Img+Sk%Qbo&xN^V8sM3)Rqv@^&xY79oDVc_R@n0yPQoh`ggsQ%rX45cW!G zX02_l^Os-4(1I}kksN_67l}$}u2EYH_h0gk#Ftl0 zc(nG56C}RwC2CFM>nF4zUT-PArLsvMAgjRy2|;%uJN~Ld_M!)AUBChei(>zfNr*{lkk=|Z{IJHTBzCZQ|Cmwe*Zt+B$=|g6G}FfU#Jl0f&t-h!y^86D+mGO%n4FMl zF29nf$Rn-qPU9&5jiE!rGS_`h2~k+sX^=rlB>MO5DP$CS zjyC)VckP^7K^Acta_zhSw=!gzDQJ6t`!QvtX7e|KV_B-t(SP&y^_wqBq_KXp$9_cH zAd1_k>dB)|HxpYfnSaQbTsxJISa>6`Yhr9V}AvnG#$!F|38y5I$DEml&W!TH9 zl_E0w-dm>`OiM8~m?oSMd)laY`IGUkxpiMEuu%HFDcw@3oR$sd*}gZ%TmV-0-) zQ;7#hAsUR6XMZ6K_v*9@o+>MUVi2zH8~tCk0D_-dui6ZO^qZe}!fG zpwYYRe(L7&{1AKhKx)O2E>lxz=ZV*0i`ag|ip;$YATaY20|ON^Ko!+|N-+PEnu#F~ z14U#&aWW@7ip}@^!_d3Sn0MEqLPCXN_D5IIvee9$Z-aDp-t0p**LsDDp&?dC9&&Zj zsOYgLOKyIyt~S9|j$`pB3_%&k7Y@(<%706;i3y0$r_%ABff;N0+1UOKvMit6c*A2O zzS1=~ThkP`yDu%>jTzQAXmZEBO7-Q*6T!(?)kPM<6cozm)1%acB~P_zwLhi)3f#Qg zFCH14q*Vr@DJy4Oz01QI6bx;1wxTZvuVbTQ{Bo01!RV)+P@OZaoAxC~v0-Bnn`b^h zgP)?L=Vdn90Qo;xK_oI6={P^Ndd z#(vn6Fd2DI$@8~1ltJs#_0<{%CCIvaU0iK%Um8V=akBgDQ_iiRu~&86<9!t3;l#va zg1?nOJw{$gf`+3WVgPNaH9Bbygewpd4Pr#8C7NyEnT{Uf9;*4&bz-IW*{#RBgQ zf}#!u#A@_}p!<|qx&FMHl6Jku>e3x0Xw1++f$4b#vsT+DxCAnGo@8S)nQNcHvhD6F z&||4@=OWI1x3@~tqikY?vI?yC%`!xdYD9O)rnLs}=gzU(OUh38TK_ho`EAlNdlXTD zOy3bq41O8zV`86M;D|sp$BD{bnf^uV+ba7|LLr|2lT|p-NkPiOMM3(v_?O`U)jtWY zi&r7z#kURKDiHBwA`;WZpbQbXmoB3r0;XbtYaXh?NED|zr4)~Y8#a{v0`VFe*mO!T zcCDTs4^$FS)&1>Q7tcYH_H1iaAX>-{)B;HlDcck{gVf1sxDm%a{IxpO%-W;qSC{@yW85A0x^y0MWYU zGs!@c8d!>2Mz3}f9;(DO#}=I$*JNi^F=Wz>kZ0NP7k@tMMfs_t(Uo%Ipeg zp}&isxgKunua7KtTy0JCcJl#oi^=HjVoMxPcSb3k>*wAsxUNN@rK{lM0giOr&^1EM ztWNF02Bp-!Z&-WE?TKD6i*@9bd`zzJy$`*(#Y^Kl7|R*N#RTC^_P754+8#fiY*xa0JPkSW_z3y8UHAgSBMzr0otKwX1rtdMV!Z_s3+x5guOZ;a;`h$*RxW zM-X=gP+iA|reIJ8 z;2bP;+xC-Q4&1m7ApR1*qW&CxKOAlM@6Ft`{$cdk1g$9!rQ6SeoqfCLJ}hS`@oSCS zcm4o~N{NQV)1m24ZM<=Je_=}%T;E>N-zsf>GdMpP0DKh+$-v1B%@oC|>Yka!NdFiX z>UA9Bj}Ea;4rf`di6C^(^p(oHt->Q z#!AcodVigtd*T%buUqQY|8|JHxjbcal4k9!F0Nch9~JvEc1sHaV?@`l9zZtUf_+k5 z7<9ZT!)Jx0$FaP3IId-EuH^D!sXW`;zLPa!evj(6nN*b=&5uvwg3)d0#8J+dSKq*I zGIjn+cnD`NMxNi?EECk^{q(1*v#~V))RO76EzD>i9%}FJOBI0Hf`ijNDtsZw*Vy)+ zXhC}SlYD-I-$3TSi9`kcg&Ox{xM|*bm}(jL=Uq6vZ`6*U>Yv!~z{SF)6Q3s}siiTB zv$abJ_Sb^mi-SKz{3uH0UvT3H*RM$6rhff^hVux#WVi{m*EM1l)rOaussnuhapsMy zd{RD7mF~AINNQW0roTHwZ6D?raDwbqlJ zrJAVO>yCO!#c|z_%a$Y0D0Z2*6e3UE@vKs-Sbx2_e&nf}vy^%B=R?W#DK9hrnA1>^ zf1=(z)@d~GoY;If7?5DVhzpwGHo;fc{$QIMu)3md&^a6@A&OvN*b>L{_zH29@_23% zXF9^gp#OF4%_?A2V0}^-qRU|8nG#T>_)|KoxE)ky^;yn&6Rc5k$iAw!1s*A#6<` z)4P*ZC$v+@bPbB5`{xG&<&pUnlU34Y4lM13@b~YiwsT3MSnRto^ysa0Jc%WeKrZ(m z216W_Llsnjo61A5L|ysLfaMY}HP1@vBTKDt?XoZ(c)6}JB?Am5YXTBJVn%X#N8tN= zjT6A*^50T?GMXs7@}zjSemBkRFxN(7v8VXti&!= z4Q~$YU&Ow7I-UmQ9%b)s&fJXYhUsO6ck=M&+YQ*foVQTYGAK~N5)PdHZ)2(Hx#`ir|?x<2DM7!!tCT#R;Rw%yk@l()uX0_XIJ+uUUIMUz-}j#!1)W6L5QAss~cfC({JKU-PRv&x&R7HXSjznpKL z`HcAV3j2HAaX}rCDzAbj2$jT=lR2nuTPdDUMiLMn>kVDbHem!_ycrIggfW=iBfzko zyc+okC9n3R`khq5hdTerH#`w2!hTTI9f8-0MTNIMMsccHuaJ_9W4^mL?~f@sb@1iqM(U^&J&aTA zi{~X5wS|CfejKbk&sQ@yv0ZN-BcGMH+mJwgvp+TQPCoz5+qgqJW$ec(Ul{@ylF=a& zkV-J&u;JR{lwWPT#r(f|oxwRC>+-s>X{VA%Z0v6rop&ND%7%XB*ZP352Ga?6hy-)D z66BolRrZ_6<5^!3-tpbOjF#PGC{xb+uehdpl5mKr1X7=aZlxYb!a`+9cF-XP&jxWB zXdKH~XlPBn4&nLztv>?jJ@7IVRbH2Tl6QMBb)9V_D5&8O4{+O1cK##LBAp^CZO_!v zg{w@lucL6-JV~#RFeEWQBWr){_MPC zCA3dYTNMPo;|0rl_8HaV>FWgzWwv9lxX|jEA(wX61h}~O$x41{7nDcrumhFlM7&wg zZ-O612x`F2;3}&+-=*G?HxIrc&nFl$O1xT*4J>YMZ2Kh7`?U8DS@n$19@@mp3b2hd zhp0?wiFxmB%&B^I-SE8Pr@t7U5yFHC)7SXao&pCV!OS6iPh#Rt&n~89`Mc}R=4-XI z^pQh@65^bcOPxL!FpEIUEJpdbsqJa8PkN1{Mc;a5sGks@y-L&}?VVC7D-(HICQo^) z$yt;_L9OwYk%YajW%J4a0i=Z&Y*%La8kSvLj8??X-&7S9*}TBF%iemZsAgem`EK$$ zd)`3!#>KDLGS$jMDo2l{s8!152si#6$-?XTM#KTZRzUwtnT^?CQycBmHw+2@MfnV&Om z%2fqL#RM785g9iJ8)h;VKcO#subY}&>?9bX4<-k}Vl{Ych3(G9E8EL*pExGHS)m=q zX_^$XX9nujaGWgo^Mzq$aPMA=;!Yg|a0T zHgm7Pw^<%<`R&ZE&Z;wXsd?OFh{l~&@Q8`f|D28q%aaR-?78Scl^zg4qbkHr z@Wm*opS57>wkgZmzY4f2QjfgJZZA=u-|2As^~$n;nS+-%(DmdBR9MD9Cpg!LADl*=C9A0Y zK^F0=U z0OLm`5NT0OlHwMOe&jX+k_58$w%l&NOt}wJ?*(cALH|$y#E+wZv!TY75xryJ^Mv|2 z!N}!0u(@j*EQ3=blyRFb#?z!HU)jEo;OP{eo33SXLcQPBA74aU;fL9tjPC}6?9eS( z((A^Yax*_UUB5fKmbulBx&5Vu01{*f6oa!Sysr_!rxa48Npyd=+*JV}s8)g*+RSj; zGUOsteOa*ZYQPax&4Ms#Os?>G?BIQgeP(;CqH-DsJIUfRfEGn%L3m{JgkAtu+j}*P zQ;STu5A-rIOTxo~NL=0m>{=3rY=tW&}8ZO{I5M+ z6!>mfXt;P7F*wOnzAnmzNz1G>SSx@--rJ3fzB>j-O4IQfd?!-9?Lf;cIPK~_2?zr& zhqDcphs;T0z}wuP-}O|N%2^LAR#%QzQI@|hztGk4M$L!^LQiZBn_GK!qMlHO)9;3e zkVAsM;ug|d4Pb3;zp?*qtvsruQR~dNrNGVHxup^C2tJ@z8Ix@MB)65fumuA7X$M?P ztK?Y3X0Bv<1pcvXuTTX_s@c_b`YnDuu)L+v#6|0yjW?s=b9r~}L2Q%K;=6RF-1@JR zfyAy};=HJ8;LAvf=PNax7G=Aj0eBDs@^wL98n=+h0{xx;!B8TVJc{aei!z1T zhk1l_2H`o(ou9t{IxJ^qrSSH1{gykM7!@UY^Ih<$CoK>}eI*%zM#Rf4kOf@ZsO`e3 zxyc5J=jOt%VnJ#@m71&q4-z~g5x6pR_WCJaTtvyoT;QdA9&5bR^yj8b4(pu1K2Ylm z;c}`xcZ97uZ1puewfKRvgL(U|4W)l9DHJ>nDDQCRVC7?d&J9rf22MRbBxvuJvPlX; z<1zirA(qR+(x>%n3eF$i8Ii8fXF7ElyDtQoXNj8{;y|p)XNM=fTS+a9AP{$M;AVbG zu*>mNjkC0v<}4Upv%*qvJ5S({fo2O{SXNXhM!tHIa;(?FcC!NlrtviKndqgi?d z;F&_VdH`X7&p|Fv?%v)#=yVb|2|0q#?pVEp53cdgOAzX5YdagjyB^Qf zq$|?r<>tnAnPXqGP1$>TcxXs39h?mhtHQ7D>Q5MGYg?}+Y`RZZ6st3}ACW+&!~ZqB zg&g7X1VKbJQ?tIlzI-5Xxx!aa#-7^OKQJ&;(?@_7#FwpeTY(_)Wm$mTsL8&m_#W#@ z-QLpDw{CE7$FB4K@$uKj+s+;{&9Wpb=dG`;QT*Y`9B{I?H?P$3m*YxK%gnT*p8GPz zQd?H`|A&Krq{h)A#~P#B+>D0o}P z+hxub*Y#t>23fLQCq#h(sUrFB@D;Zjhi&Os(%`Ns2Dpu*qjF;O>XDBp4x|duWpAH` z*K0xN<>@*348GG9$FPMbe+0==(*D<%7R)*wRcZMg)em}grI%Y{ML;1eWKS;vd3Amy zP2;lJ8aib^?()RI-*U#2D_MP{Pg7G)T!MBDRg?Eljm_i$R8wzf8;W3Jkd7JsdO7lvFymrL5} z>S{|xeAIHj`wo5ErNM-Oj!wZI=cr!Jnj3Ft>Jx+x_%~aRs#j)eDz~uQOyf;gJLt)6 z9K+eDuE{+rxL#1eSc&$-jmM|1zAd?^)u=9j9Fk?0{7kD4`eNWHAt8YRez@u?h;Shx zAwf@$S{499jNDrl=oFJabRIU7hVGop%Wx>P+$SIqqJ0+jaQLGb}7D8~6!E%0F1y*^B0HA41s zQw+wVt7M4C(Z>mS`XRR-31dU*UUMZY=8g39^dNDIk9`PwDkvDF!9s;&JQCS_(pOQ8 zm7`MQVC0eYGA^2hCQMq=Ndp;H-qAej5TyeKkKM3gVU!Y#YF{iw@|4l&GgnNihtN}J z>mP|#TEvN9CfO=EoHm$1B#vzRNjR)L=pKZrGmQx-5ASDWtdH5}6w5sl+I+D)EYCbs z15-CDh8HGNu+7wr&1ia@kKNAX8{Bul%*O(wK7Yn<^ifby01H7;7&9p077nnjg?>>j zP~W#K-EM*+yPure>5PMFQsOXa?##-{sbay?-!%@R&twP>lyX$p-Uf?NgdvuZx#27S zV+oECrwVZSo1fA&*-*n#sD`CQ8bz#Y9MydTbW5G_I0hAI+GNE-f!?DAeKtg^He|4T zZEfvA*zd!`3L$vR!1`mA75l$?QxZ=J>W42qxQ{gr7zMXlq5^mo)B~CRiU6C;M=gvF zNdfTgsebQK3$h=wjl<|H%ll5?z8R)K)c2?t=%j`2JJbJTM1~$|kLkrL(sL&(E`PwT zp7!^c`3Mc(lKGip)vvBOV?0yiFtcS<0)r8Uph+;OF*C5SvKDyBJ^DSW@EdBAHO4yn z-eBO*pENNBcvF)y@NNIzzkY98Q5}`M2OUqwNH$5fk+ybze+Dp8`ufFQvIrN$CO@Cg zG%N_0<7e`swiZF8?1rPl%uTn}t2NW7wDgmE-=zbF+R?W1bE8;*@zN)Iz#QTu-sS zSr|B7PEZpZ{fb+w?`UDsp4OG~{Miuz%JO+5czAf05k@pINtu}w$^91>&@7LkCp-zj znXa!R!}LAox2tJNOG{JaG>wZ?3r2zOZTjsoyTzw6(%LF1l+LHJGcYi)9e0zlZs1X^ zbj0>9>UB@W@pBjqcJ!7CB9wVfwdj*!=+|MMz-WLpkP6W(Tq>CB)1PRx9nXb#A2n=E zq38OE!RBL+Pu!onz0zaQDo2w@{3diyg8j`1ET!3>CMKUvlMCB;j2U!a6}T!rV2P94 z-`LsNecl)2=eO#gaQZ~f2bLrBoi2Uc+vToN%O9!*DVeEbomVN3a|63Iv}Sll;9Iu! z;H4GFYGNRDOdmjm=D`-W<2!w$+l#PDak_>w8ZlOoV$Y{nnXSrcg~P(eR`}6^rAO69 z{X?sXLH4+aMrSUS;9o2QRPsyz?8LxL#WgNoaI&aG&s$312-H7oAZ0!MY3f{T&1zJ( zMtasJ@H;w;cnPN`CkF{HfqTb-kIE&l`v7al>!h|nxj;`{(N|Skw<@hNo>-&>>QDEA z9cI?*$GW@aJ$ztI?{p<{*Oq^l7Qs}vi|)+zt2YNCDYp&gl5}Fz2G;GytGn6@aMn`Q z^KPBAU?MSO5F9xVX{AY4%pKVTjy;7}^FnGpXWiIgW;`>)Q5h9YO-*HG#^Y{2 z8Hs(Cq@<*M{K&Bu*Hr)Rt6C z71ypNSiIH4hwMsJ(gsnTFBqasI8*z!K7|6OD4#e?}AR!RS zrQw7w01UudD)i!+@OZ4qic__vm%uA74kH!TB%F(NAP{jC%Y@=}j|- z7QmXX>*Cf?7!s#61Q>&r|Jych*KKjT^o=TVVvqB|gb3``+Mq|#F!+`{^+#A8#RM|R ztxseCueef2jV)0jZ=@FkE2uwDmmYZ@>C|*iU)F6dLS>|{udkzHbKepiBhqDFIFLA5 z(^yuPHJ4>K#~CkQaJpw_Uo%~Zb*e-k2VUIKe5CzMDgQAs*tG&L6M8k$;PXv8{by-% zC~~+iWcS6LBG1Nl8uENX$Sh5|ax?H1#W%R>Dn+&|V|Y$%FqUR_X+G~?a0g!-8^+W= zERy86XkY41ps8STlai3A3*P`wA5avIST0m=cDBBf($OvfUf!`Q%}v>+kI$Z45-NNkQFpMgkWs?)G=M`P;21~b z+^BW=ExKh^K*#y0K-$Hn$58tA^oJYsz!8PCR_V4OqvMF)s*m9^5!1P!Vdm?J$0K5E zx&{LoqV>lome&?@q>%gIf5eU=u$)5IQguU4`OqPC;9$j|G7hUoEtr|bOih1J@7Pk2 zV3Zo_tyr?+*2o0@QbtF#eqXVvo}QkavqED=qJ<7XAU3D{qs?YCG1j?ceGNKdna$}Y zH;^D@vjpgvuL{qAZu_zez+Do;Ahg4YXfcnAkB@I5WA`sv7J!ax2W{6~F!8d=7ydLw`2BVl~VAVDvH6f|ozI$JB1I$R0zIj*&7-SHq?0aHM=;A?-U z$Ux7k>l%dy2+91MJ-m<$wqd8WwSw`9f>CatSrl&`8Yt&biGzMy%ZV2Ew=Nxc8y8K# z4AHUF^(wgad=F}>t9h}uFeC&lxX4Anh-D7&lVN^Q&P(RK3$Z2!9bV+RU2;+CtZ{3y zyZ^1ol!)%_J9!t}P-9H@>bWa``n!7yFF9chf6KNyvn`XgMSws_rjwUVQp!hIQ>kH0 z);oYN73s(PHEOKK!9iw{z^?*OTwGktW1R+P0mu}TEkdS4Eaf1J53G}~)>55%6S}-b zntuMAJUfDS=h>3*Pu(uILE{8Xrg+?7YbD2{r6tp4VfwhP_V#u?GQi~)w z(|HC!DsUn>IXNJ1Fc?ac&l%o4K0M?CCqHJDfTIHL3t9I3U_$FL=ep31_Y{nZ8(8-^ z`hFcr6^(f8bq;>0s_JW>B_)EBm|88$+@_&g0XNKEg3DbUN98bRVzX_zN-1`sy4yMQc&jbQb*}L=o7%hvpH=wJ7?AyO1 zM7=^m%&tqHIRNbb#)C531PcqUWOJ^rrdv8gQ2nhbU+qOxWiOG0Gdml??tVr*p@ zTeca?*crz5j<)-G-sgTl{=fad6*Irzb)DyN9_Mi$*Hw{swKdM2y?B;{gyh_3@9+Kjbdv^Hk@7I&;rrPC*C$A<_(cDF`oG_O@@yb!OK%L5jWqecu8#N#_AuI0 z|F1{?|1balHtf5KfFL9Sadfm#AebKUFCgEP2h3gjV5nK-;OO+~)W4-HTA4(2i;oM+ z2KE+#a(Zj-n!ShZ40(p7nLWO0DRlqS^~7nG{{bN}%?)8BR#=CcfvZ4P^$gs^*b3U< zh&yDor}quqveGf`t=Ah1VN2Bkj?@q1V`nh`28bzRAXo*imJDHEQv^66+#Nw-E*{<|1O*|FwoDgb8GE^))cUz@o5}Mgz`i^ZgX%k+UlQTX!T-IY30F-=i<#O;GZ}5Y$zVWUNt-<;Ehw=KPIVk>tY*06Rw2 zJ9Zxf%$8~5Gg6$~sQxY7MKp?(jp`9gU`cl9E!BfEbT1CFbE>YAR=@?@YqAh--9jPfsUi3d!B8+PjxPSWneG1SRYwAC-xI_|F7Rc>s?B0}lC*k6r{F zkGQSqT)_+(VhW_c1&)8{E#5&*;6)B(Tw2VxiGYPz>TMo;yFx)GUu1)QUpO-k< zvwS*{rP{+uNTQY5)1^jS%H^Xhcim*5K9uO5UNb+T0Z9D(wbcJwwJVTY=xV&;f<0uk zcwu-6vk~ZY4>3D8WFa+&*_g}K%Y{UJ;m`EaPoe}VPMsrX4@3OO=+AMd<*Pq^+_HHY zHA2?l3|wr_Z>5_2QtjqkJ&HG7BnACPAfbjddDU@vbGVwoS3qVK zr~djldSP6ECr$^vSi^NucgT{*xQ> z{()nrc&**ZxR0`kY;g%7DrSGwnP)K7VFtVI$rt>8Aeu*pF_c2$F=)3+4=(d^)A z4`{F7DJGKuOT7~>)OHQ+Ksa9 z)pU7T?{Td0ioQ-P22{FRkneFJO>{)&mM6V-=R{8K3PK41?vvLWc)isThtiFzJNo1`DpC4BB2moV>ryS$JYQ5YA9x<>jDdIyx2;=~ z&zAPr=EiK3EPq_GIoU^$wG|pY>KLMA1TXFg=#HUEL zkGEdcy&8yGwO01I4Gy^0+gigl6vo{o`lhukZb$ISN2Yx7}Loqrj zwC9Xx_3(7QXL~$-=4x(>=--HX(?GR2?HbRg=r{>qe2Y%`Cb${KQD9pL9tVXN8v|AB@otu(eysgoGwk98Jt^!M6P=yBhw3biH`l zb=@niU1>YEzIJfG8z1MOln-mlv3>Ero!w63N*2~S3{U{xB@mP;c_`Uk6#>jj6@e<= ziW+VUgTRXC9#PfyhS%7tbmW>OsedE4$&GyMsz;G(|IE%=6hf=X>v-NeGOO@3QY(G~ zT%$?k>8qS)6{q%qqt5d6jkU|mehB7@-Fcu%YCL)o(|)bRXYrUj`GYp2j+U;KIOz=i z-}Fn8GAgQIHR}OHJgw>|ie`G>O%CnD^D0qutQimkpwoKC8eEg6NRx1M)3t01LP3NW z4){UD1b#yrw&wh>Hg?deJR)!JeDf3JeaARMK_B7QNc4Ku`QQ5_vj}IGtpY zK)LAhIAOR^nX=;D9SI=!!5md>Q;mNccG_^^aY3M2L9>0N?V&@xo+0kwN~z175P3Xq zG>P|P(PFVzVVGs*C4O}4_;PHu!qBCFb?Izmde>hRxaef8Y`K5x^fe190@oZ|$Pj`U z`%o#wK7+vSKNN3OuYJ#?XL94xyQlD5(H1IGHpF<`$j)L1TBu}1UUlfhUT5uFSnX*xHh!VL^L- z>*fbEviL=hQt_5SA<2ZzgNuM1SWNkDT_Ig?L1N>SegvYi0iJut-?>WuokSMS)31Xi z_fJL3K7S^!Z}_Q0HCHb4%Emyn4k{>YvSM8dScY9Gz5II1-L6+3bdW@>#h5-_8bC2G zxc=MiIG;vCZxZO+CNMvYeOOf~GS$5UQiV7j1WK#z0kgJyVQ7ux=cOm*64Ty%4{Bsv z)Tz3GuU#Q~iI~(=K+pUI3L7}jGV2N6hVcduYrHtp<4%^Ie4^0@U*jY_Ih}h6^Z-2j zU2BoZ)u`%=#e_lMn6?s9D4ypT69HkZg_=lJq%#OpoSp7U@k(1!nxY4C$5nYOQ@+H+ z?4UQgJb!AE6D?`RF;#z^N6)veZgMu+=xs`>Do_16V_e+QfJ3RDc;|PWC4GBsc2`Tl z&cWSQXNKjjhCI<*vJ;7N-+Q!))wj$Qam=RmU^&d8dPEzOq7cjmi;Py8ngebfHpmBm z56D84iwjOXsSRX4>`H6@Q`FfYv-3CfKXdFP-ISVJ5H9+bQj}}U&j95^Dt{Ss;QDsO z(oUV3pap;VlnTlV&fCmyu}voH6n49~K5l(aCKo=%dPi}}j>yL`5}doIpf2FNptdam zb-CwvtG@<)rc&b|fnw--d-}#Uwp!H@Uw*ffsR&>Zd5T&@M=_YjE2Q1bLb=DH?g>|7 zx6{0YhxzuPF!}AdR7PNrYEx_P9e*$A*6qVjhM=)XVtUgQtnY> zcFe>sbAdGS9hZ|k!S;LJZxOjmN{VBOWinEwClBH27LF9~Td=rPy@!_2JUkfP{TyBM zB4YCf@07dZX7{GVrg}`E;%?C9m)+eJj<7&~5Xn>;s3dziO+6Oj&k0TX3=_T)CE58~ z6Ryz%)YwPpv?Zo*A@7;ZxnKRkBUALWE`4Bp!@O5us8V0wzUZ?QP(JNhP-dpo`&vUi zoG(MJp2g5TL{Bm2n*`;EcgkwM&css2uqrf!H-#ypdFnbYp8|j-Nl67)xucwe9P^iH z=TxxdVYEMu7nX2E1{H1(@8rgFG%d~#kwzBv9fb{OKF>|9Ay^G(X-?ew%rC{@1r$eG z9r3ttA7-Jf;hR^H$z2^S9NIi%3`lo{`vFGr9iHy(E$^-^!Kbsw^^#D_7e-$9(5S?S zU)%*i$!K1cY_M-8g^~bS6*B_g^_M@}cAP?3Z;^ICr2Wa)J?iYL=LDPgql+3yhJwvu z0cn28`$c7%jgC?i4cuWXFF|za2S+p&ti-X9Vaz-50CQL(?Ws;)G!b7{zrbUW~c? zGT?-tcsVlCOc7H%Ggn27EH|1h9?MluZ;K4&J6+Bc8~Q;kTS*1dMr0hGBq$~VAF|aN zmKbxbN~K}=i*S7G;n;TzpKqo)iHn7!9dk=mo=fHX?`F(+_kZB9qXrtyZpQ$Jy0(sT zqR^I4k;ExYMFP3g2jgB6bhvf&!8O99-9H@fxyxeQe~sHNw-sTIIS7)WQZGxZ(4zeG zT#NLd92)v;LT1ZCcS2>OtN3HImPKHGYX8AR#g*bT3}Z{D882GE$;U#-(%B_Zp|)_t z{nCj3ho^3VN|F=&vFNFThs26v3uE{U_LhS-h*f}i8;DvK&)y4pQDvEI>x^tq>Zc%T zp8@i%v_u5Bm|}iwQ>%G{_fL026C@k#(lYwx(5{}eIHG`)UWw^XLIP%Pb^_q6jJ zv9gK6n7XPVqU=w(*ZZ+x+H9H%GhU=Rvpn+1|!8RP8qWMTRf>>_Po2(cB8XR{| z$9k_!={7V|6W@9RxTsN_G-M7we5tfZ)bB+3v;-<-=r4UGT>s&XQU1o&8H%;1f{8)q zD7&BHDp--0X4_(CW!3V?;-htrRY`{0ck2_47{-5}!<7l}xZUWG$viZ6>mfnJVj4tD z_$9zL*SnV9qijuFg3tV}m!uxU$!j=3v#llYB}pkl^(>d~<*TVDZ zL+fJQF^LnfcW)U#7i?CaQN^6Fu|E^E;WHAknu}V~eee8yS41&pRmciEb724gv{27D z%e}1vseM^BuDO5B){Y4P_6Cu5<2Zu}jO^6*l-WPqma7cZ=u0%_bLFM95!DgFch}|` z8(1843&nq8lsJj@=rloK^XJZu3Yr{U9<-Lj>>V`9D^nB6ROIX~36zZ1)h#4ufExJH z9@Owk@hv9E1MPpy5=(LCWPsfD25cYJz)}!N@lzf3TkYW>qWMegBHS5BMvjn03bEs| z<*d^}797Ok>NGf!V~q+JC87t3Iq`ZY5}!H07QQ0D5i3xKBLh7P?`L}X(=l$6hZe~A8nvu^ zo;mwd-2$PlGxtXYH|I3Aybn)|I~S}jBY=!pw(yw*Z}~@TkL+Ae0fc!o@S%w^!9VTW ziIYX0Co#%&m(MCqtpgX&-9JW*A^^wtuqS?^Kp-N-)}pZ0uBjHH^ZnJfi#;eM|WYgNN`N)!C51Qls%oM7;bMcQhD@EF2W z!>PI=B5T71H&ipxwY_0`LF^!e$mcqW^(ssIrVY7qUev!dhpQOW9x8Qw^7^_xiN9cw-tl!0@+fu+mc$NFO92G1t@c1 zQlLtyP@PoNLoKvHh3Jubtjx( zQ%}}4)h|-`oK#p54M=HlG6gchRy;B-ee!4&_p5Y9!do!*`cLSv#4GMOu5#M36kmUx z4Vf_xnYB|u02vZDYq-o9r^DQ&lm5c!E9-c2PL*oaMnNv^4nd%|2()9=$^3!Ju)!j-(`>1<2uQJHhmC%}Bs?%V|US#~?1 z-JXl`cUE*cf6c~Jnu?ZV9}$Bxd0oY>6rx+_2kqSxn-=e{UyiQ2>d!r{)_(erTqo{* z63izvAE0rkvGtV>9I2#f{_A&5G{jcM>SiE6mb>w~{D{9gAxM&&U$CbCY60f~I8l*psIj3Y;`nh(FP_cX_qPi*47QV5$FOCf>7|X^=2wEb zqZmrBAtgMw4zS5Zp;nRU?$WBmV__lRP2??SPrCORC})TbO`PzJXi*7o(x3H*LZ<53y|;R1&EYF9Th?5`RDDBTi8Fb03Lco-CXG&) z3aagvtoDZ0OdMDDZd_my5 z<>`6ny|tXNy2<^%(<8rRnG|q3;gh{BpNvhq3jF>FbQGtq03~Epd?+ccu=<=a>dri_ z_U)*T5`1JoS5r-6H~p}_QKqFf&~Mj?fz|Zt@f|yvE4Cch{HE#!HI7a4{W_S-#BxH> zhJNx3YH(%X_^L+f%;A@v6B}UVR#T8%dg~9l4y)fxrK(u39Djt*4V;jD6|UoXT68PF z#(w!C6eq+Zc)j@B>`D2Mf(}BS!JOAw{X@nx&Eq~E)k@~g(Bbk5r){=})U;)^Pu*zy z)Va3YtQx5g8hfi~&azRv*<&F3YsDIzBIBnsg-H}PUD&L!uK}CS1M(@36>GTNvzmb2IQxWBhUGMpU>$eL*C!7;=;Cht14j3->I?B|ECEIb)o6SZH!*J z>b7O7K9MbAh4p(eQ|m`FZELyQYL(hLQA@_KN+f?Vnziu=jSaL{*mu*tm=cHWPtU9b zrdO>eIX;+|9u06UfMDkN?79KLh;HC95;lago9sv16)XQvk3I(266i+L&p zxn=vYm2>S&^bGR}quk)iFi$GRCL9YIRSGM4c;d`AHQ_u*2}oE_g;vG8)lqxGX($<8 zUj2v4-GVFS3!lD-{&Gyhxz_MYFeKD6A~T%gE9xmC;H9Fc35v^;218U3L3mjg{DKXc*P&v6GsXI7B5<}bZrga3U$6Z4UOSp z=MaZwoXl1~AxHwSv?Q1s_fz{2hn_ErY_%z+P5kvLG0S|2pPa`I(8}CMJQU6{_qkK$ zIl&gc(REqA$hTxm`27Aj0~^_MDwPK+iq(J}%ddjdW z-5Rhu3_W~#8a<6ZL!Kq<5%d0MSv7$w@N+n7d>npbvcZbcno()VU37m_B*+@Czw{(^ z`fXN37X0GbEx(v&koucIL6{sOa57s>{^!d5X-Va-wGB`&C|F^`DYy9R7dZK{F#H<9 zRVUB(k7?REl9NN%M!uUYm(X-sj@Dv1eD>^^rr6!`j5u}dp4gVGADuR>uAu;Ei=K+3J{{3Hs@Cj z#{;(lSCEc@OZzo2j|sAo!XU2u&7q9*yEcG$hoG@%$A^t0B&RuCB>sG7 zu2gp=UTFSvz5tDUc6jdao#k5%%CxL!v3@kY%EtC%2t()4!fN%20-ohx5-Xeh_Viq+ z=_p#LW&ODp#}~ms`bgwyYL-d@<%$Fqwd3glFwsxE?0B@@ngSuKaWMOH7odVKM%dUw zTtfT=bR>XWt_)#@LzjgG>Ggnc8Wkk!#l;)oB!-@&gEHntJ>W0-cPk_C(>M6`Te-nR zORlsazAK5CgX_Sy-8kf61G}p#Ab`eY`!%LDGA>W{xOpjErysd5hD#o<;rFenLhzQqc#Qh&4WvxE-T0vd6s6J!Gdo zovU{&T1dS+4<{kYU}-$AYNxJO)AIHHv{t=dT<+%B>B!tVi+*aOn#YuX-nyd9er*0R z7;7%T_8nw}eHcD(6kUszVndhzh@QJP@he?)zW;fQ$BjT7JibZA$+0Ac!sJE|O5&a`ov0;VlHt?MVdEJx)x+^i#Od-UIKYzf(901CDN#_Nmk_$ZcA6)XZVEtQzGZLlOR}>^Li9 zH8OFGBLZO7Lq0^Sqfe-|C3Y-vcrV!0eQ z^Q~YgC1~&_oG!lT>YHC3lqenZL0ESse;aQUax)?`H>wjZRd9)wXWP(xd042oL4S)s z9$)wOtZFR~I4$-(K;9c^f$)pz>_H&|Ft#R5jtr7jDivn@6l{OJMSlq>Va|>~xo)FM zJl%Fw)bd(XwjqQLA7$TMxRAk9QMo^()9Cc!piJP`Oh^QveEc(cM%7UT9sjE_pYiDQ zJ>xdVy2F6lR|}6Bvh2pUJ9s~Rrk0}mDgI92>PNJ*khb1T6hh8zobQj73wz4TuPfL- z{c|m$NrN^5MQdqkxvrLihAFfryRwI&?iR zb$h#fjx#LXsYPg)|I>heI;k%yQ{o@64ue5T1}K^#b6!uz>GzTsin-Z;Z0Zp-k53%I zlM*5x|ItNgtPW>;_KasQ%2{C-&Xi7WOt?6B;mv_*4A<&fU)nyC7W%2ePs(zU`G*Jk0gdIunu^I(kan_tQTc#8&vitOOrNp1z;P#*MW8wg}v$S!8 zF?Y&^d@wB?#-<#Vmg)N)F40~lOh;F^oO^IQt~^B z2QwBG&gA>B5bl|etFuD^wk6Dg+t&mXQ)zz}9Z_e;D%QKJ#o(kcWK*^q1PfDpjGBex zn%XYjRqvP8Kupp;O`ccDaAGAP^(m4e-G*Fr%RWzErF64ABI8iw^@f<@J#`}W3H3b+ z|J9>^vLiPDCk8uAvOdn)b|OAmm@%Gr;_7@*x3g-%|9-Uk-?tx|K^z zkjPz6j=s}93g%N=Y4DYPu%=w%-{TJUHGhC_7}g(uwq6A(Lp!%Qz8ku`DetmWfB0VZ z4>PzBJ<(`m|Dyp+3Y`a$mOGx$X4!($JZ-VQUf9_2Y^gu*Wp{o3OdfgAmnL|qodAok zkp$Ugu3eVlS8td6bJK3hnjE`%r_nQzBaZcC1fV114!JwNQ&h1+CvAQE@^5XSBI6QId?85VMi#O-F1rybRTXZZ%Qdd>jV4$e?=#&=OBu5le z-G$b6n-=Y;K!*`))6c)ggcDqOvp^SM6YbYG+}nAP=??08Q5F+_W)i>oqHJ$3?kTx{`=g6H)%NLA=Dv)u8$%|a9;8#Y01b>@qKQS5&T-;RIr&f(d zDXtFd6Hbn+iGln1D=q+;j{%r?TBW{PrRijAho-rzv{jWH_Xi#%01Riz-q?Uw*v8|v z+BO=OKU;m)qymaN7ksF}ZF#r{7Tx0D8ha6KPBX@NtoSwQcQaO;Vh4^EccB?Sseuo@ zz!-~#Fz569^&Fj?&;AO3@GduCuKd+;iQb{?R$YBAjS3r+e+s&lb(rCoK0jG$6AdU1 zr4ZDK+nBqhyItjz&SIi)fKLN&?>3=&rIjgvocfa(7xkvlyO)q_6jm+0WNn7#pcX+Z zYDdt(pQI{IDFWw(LsIyB+41SCQ52cN6Xfd$Jp)8{|F`tmeIlcBD5iT}&9YpEUUUme zBP9&1xpxH3`#qi$SMv#U8z~SZGMT;-4N=_M`iAQ8^*y!+|4lOe$&M(pgb8n$h!6N- zPi=>~2tjP<^ke#w3b*&)%%=S-S>;QWsnZl!&qL>I+ zXxl$5N=#b+%H6=5k*`kDce3OuF7n-#yExi_YoL~1-cz~%6h8@+nmZ#6Oz1t%N&~aq zOc(mg*L;ATt_>XT4fx6>qQUTbfc>A{-v;=m6Kr=73cOuj5gSa#V|YTlmpV!3Sz*@a8|6djRYl`b4X`J%W88g!q0bosD2} zRPlFho8*HsHiS);F0pU$U1iDu5yybF<1Xz8ve>r2#HqnEWo38hIM~{kP1rX;dMq8p zGLq`xxL%%2nLh&xz1;-Qwut`qgynDH$7DAmeg3A!RT5AqC*S|sXBQC89YV00I_=!c z{Wo^r($EdH68Tedds+{P=!=2SskDE5`1l6!ua;q7vj=X~WYjo>p;Rq{x&Tw56i^+Q z65-cKL_`)8G>cNw@i-^CMP9OF(MwH&*l4esN#?s8BjJ9&V#1KI7&0z0#LI}47E zE#Kyth;vnM|h$U1pg^m#16w-xo_`=wOt62tBK7AaX2Smjk+uDC#)MR?hyP(@l zsz40i4PFr>2I*rPG$`j6$bb|$<_b3WQ&m$Lz=I2!!UuXRqFZX~G}GDSS* z>~(x6;>Ar%dHTt&vFX!LEnufDdk_j?u)|e+o-~e4pYSC!_cz%>y?ED#6lSnuC<^J9 zOauTn=T>Cqor(+7DA-u0F-SI4k%4{2pVlCGc&~l)zSV+elIVIxPwAu2jFX-#d)sn; z%S-{9j=f)&K!ZNmbxR~W-=?eodIr*X@>Z@e6T!^ST-bi^CXll#0=8XZ*B-(EdffLr zaVMpcn%1-^)&rB!BT|+~(uP$=T6y+-sEYCcH7B?gBQZwkAk!{(A3Hy#3jCLIx1Qg3T!i5*lfmVnK8RtZMS}&lelf?q!6%Eff(o& z1?>vWY_N9o)A3bzl*@?gpPc&sB9d6TVShwEJ_zwnKO$53)5OJY7_=(GKT}2g98`uj zskH@S>NJKpx<1Kyp}Hy2ls9&m*2<>#p2f5st*uq~_K@~lf#ya3V*ibY-x6iAn(2Y8 zni-mRqI`4)WH*G*FE*4f$x}CuJ#oH0)ZGTYIUtDNAb+@(>E_BkBjp@Di+6C6Gj+lJWk2J@AyE;F>rkII&XZ! z-VaNGcNnEQ$GLe`+^>T;Sp)+4jnF~)sGr3 zON6)5C?u|NimK<26ezz(?+|Ex4hS9%YYIcv8%}VvPy0F4WO$P}oU_MNw!YW0v$b|U zw%r@9ulpXovDuw?I_GG`Y%tX%(e0CmFPjfMGm|$`5%z6I&8V)$o+IP*XHtl^2s?)J z?u3fzK^%Tu!ILq%zYcWo_933P2;-mT*I3debmV>-I3b^^`1K{hctOcMdQ!xDSF)dY z?GU>fLy@Ip2Pr0R>6N>7a;^RbT~f%4P^Rf2d`sLH>WA;ibGrN)ow#>*owfo4=3>a- z(pqF)Draog6Goml;#u3;vazBMX*wk5OYqW%Q^;$`&R1Haiv1d;8H;4K2A3|QH@Y#V z5g(EhHDlBE={|D;skECIDTF8F++6k8mM8A-jxE>evTUniHw^theqHetw9+yOF-RN2 z?`=dzG6Lm86px!fAq9FFL88Z2fm_0t9HZ6VzR4Bl+3@^U?eVp{Y~?{uz|D$A;~PX# z7>Q#<66sEsq+q_%sBqx}i4Ry31hr>0q7~wPCPAv3mAQI$bEZN?97vB02;^v@Cmjrp zeQ9Tn0^i|8sXx1NgePcaUdFrRjz6b7=j;!Hf|t+3qqK6atSmKDI7ImzHonyxX?W9S zcGal^q78f5df<43J$#s6JTR%ex5hD}d4uDw&23pjE!d+H#SCQi6O1e94ef0+vs*qK zO?;LM3XBpdl3WjYTM`9^`7ZnUm6=ae7r4Bj2TnvNwp60drzrRqPn_4dcRwG!E)_RF zQY6=nG)b4jt7q<9Fuzitszu2*C3LE#_j%~plXWiBJkIwph-UnqBwRV%ayN z$SjXaPiAYSfWriXP*oV6RgQ1RdxtHUg%8Cs^RSPM8ivC*K0^4KO6qn#Nu3 z%ZbcArpOGSHT6xqf(pGT1EHx(sCJ+Yi{dj0kf&0Wg*M#)nWek0pMKVTy%m9qgfxg@ z2n~@NDLz}sq#<4P;QVUS#cx4hYh5Ts)Hv2cnS4vwjRdcb0E0@Dn$rkBs?G*c&^!VK zUw&2S9I)z{GOTyxooLHM^+ObPc~5p!^mTdU^^fL^&RLFo57Gm^*D9!pLf%Ut-xFxl z3{d{*oiw~)Z!q*$g^sA);oT&w>$wHP<6pB|%{m|(wdgy6p-Ht*a)(O~b}U>Ut{Cr; zakMQz2d%O0v6mzTm;xU67`#?#Za@F&8jz0h-qAUZ%fQqH0uM(eOjI{8LadC3^k!ff z^+qjB+(qW5$MQ!|g_Nz#CZl^%+isAL^D-*?nuY|CjKiak_b1L;r=U@SM@5^=MtLtOQO_42)LU8*;- z+N!hnn8$%cxsH=wM>5BzF>j0?saF_(^D0%fx)X6Zkh$nE8Dcg>^(_<> zx9^1e3dqAn;5_9e9kGN<MkP}Hm}Hb&fLpa@ zxa)}1Af&$tmya7P7UykL=$kM&j?NI>76FJtd=&zWw3x!0q{t0Qdr!AKH4ABzd(E8~ zZ&wDE<>lZl$~DjKOibg)IR|J>M=x&&`g>+F=x(L1??qd<%#U&IY#zA(2x3|Nn$svX z>#ovnPquKM+kE-!iVQNl(9x&fw+bsm#U3CnMB2FO=PTkuqe3mg-kNrqp&QnJsxDHC zO+ABL)ck9&a@9M2rE7EbOfy!Uf_r_=Pug*Dr>o%g<9U`X=NWYl%(74(0l6-fUu6~0 zfFRR}fU8cM!A&}#uWt2GjUQjtygjAwXeopgUNMz}lciYmV^+@_Pc35xWN)orDnN!$ zmo9Ksha7S@q~C9!gzXN2BPH@ER3PlBMXlcw;g#g z+*{nDHpY163&O=SVA%b`>41HrW1M=pCRO$V)zG!q`Eeb#x8T0L8tr<)UDX{QEL`5W zJlT`TJE1c_CS|?tXd$fdnZ@P$3nt&*rYJR)$!+($H{6y~K&rBrN!>ap>Ez5pZUx&6 zA~}Ni{T*A|U&@u&7b3ZOYMRiCf~pT}9|lZZERInw{H75?l&)N z!RpJnvv5;gJM{h18<4WOr5_IKP)1<-%?t#xjb&6G<=*ln$g#z1-X>lDdo-#*a%EFC zoqus|o3igpF-rg267C*+U=x}vWn=klunPVq<-PoiXYDpDY@1?4`%1}LAEqJ5O0{^| zIe-KTwpMOo3ceYM`Y1UNszRqn-!7Q86dpi#?p`2II;Cz4F6o&Vd2HhgpfQd_@UfZf z2h3*+(6v5{p063oGfhdzaNi0d&;AHIod&8fDyuR5O4A+R=s`>6lJDZiy4kd}P}eV? zICyluZxFLTS}krH8&E0MUA|#Nh0opf%N1?<8UTu;xnhl3jmMWBwB4_G*2|fc7l{0n zFg4y@6M11N&Ej6eU4hwQK1`sKw6oPL*b4%Q?jS3WA;040w_o+K4&Cj)R&`)BjdJt? zmE6nlMe4rS2ATatz zRW;uJh|0}T3B{O7ilIt((H^}Bjxbh_2b~|SJ^Q>3j@OpBKp|_rGj4(wg`r=-a%LXO z!L8h8*gDvS%d9qR2V{KomHiVrN~*EA|GgjW?C-8TS{> zjOJRm&5(!Y>%tc{8X~>Nhs{w1d`Pk4EiXsSr3SIrhO49_tBztlADw4&5KozhT~yYJ zwhseLOI?S~O!OrQyLJH*hD>SrHWjC*xZmGock63b14q7LWusMtIDhiokKLVtX!&hV zI-%suqWC*7MnJ!#{#A~MjqFmF^Yh`0x6|CO9QivJMlboV@1{i$q1wCM1yIjR-a_28 zab2iXp;4Dj$PsC|sDhKcmnrjc)Ex_O4IPxmkC38gc<5CY7$g>viMNeX12vo`#m)9L zSH2fw)fCW84y8mLzfY>6H#ZmPcH&WbMC;vkqfGD$$B}Y zl;;DJ+W4aF7}B$4Huh9*x-Y2Y>&)P^uT<_bLA_AZ{rghP?!?(wqooUTGmY8Rn83-w zqVBX^&K%UhXtX(MhgC{_7?IYrg%81mOppkXKR)QLfsRB*-2`3Fv<7i+_H-E;eQ=}^ zTDCNUtG;@aq?QPix(UkOaUk86R;I}F`V%$g_os7* z#_8nE_|~uK2Rga%o7j}z#7(?mLkI%j*|bCQc-$%p2}|+B)7zR;(1>DsFToke^2DM2RNSUdvb!!Ko*XWYpQ&4YQzgvdTc0>@RdoR~vAQ7F27I{pX%Zu&%5wQC zly-oOQ5go0$ZX*UvX^jxmGfXUGMt@7!~I?1SmIqdyU!aMBdvn9D_V@|4gL)GDzMRz zCx;wmR~3dRl+8d{v>EzhRO%yCZS zE>%63ii}RFa-?c8yCN$1aG=N``pR}ywfyS--OlfIHZs*8B}_&yjEo)ZHUXMyL4#@` zI0@-Qym!3@dyE5v;zlj-EI9{6uH|hyW3$F!hq6Xp&X7~ixRohdWmZ?F_N%63_hSP? z&Nx`*`e$wCA7R3Po#w~`X3(&|Q7e|mtu(G!l%M%=57rWeHq)`1Y27F*7{om7q>zzU zXz*9qVG}6u+*vmJA`GwfR+`c$I)SX-@6cIB6fITR^Gz$$qs%m*%;_kRYq;HOx?(L9 z-)_)kw{9QdD(mDUFO_8vJ~>Rh{^u?L?hdYMuZ-T@U`U@%OC5e4qq*4Ljd>|KyHn^N z=WeO*=R$wYV~z@_PFaQDkKkw>=1fSwDLGy7eO)po`ueK+UcX*TEk*I`$&emBo0*sc zlXoM+-AkhhA^OFM2QQ?S_au<1-`+19^4?|0HW@3^Z|_Lm zsX6e7wH{|y;SUZ=wOfSzS63#>3 zu;r(XA}zkh+(5t~gKh`$z^Au;3JGqJI5SAg6wBw@2^8jTO5ziIad*Crd-`ObbF#{3 zl(VpT@s8ibgj*@i&bGyRCo~(kNz*$nfZ0q<%hX^M6TDnuB&hJAg#r+BIm27O?!4h` z+1HYNt>KrS4R3R6hSJ$`-j_%V z`-lMK+XJg`?7-)pxN}d6;+YDMd$!+(re%^v*EPIy(3(Ca^TNSJ>4AWi;k0sBK~^XQ z9f!B~C7A@*%)!&?k1!wD-?VCzi+2tBgV-3YKKf%9o)|u1h&?zcL#Z&0f3?TFBHRnk ze{s4P#olYhMFHo!k4|;K3`9G&I!3|4ch93CaM|4!^X|jm-~2$X>m>C7B;ob&lwTXI*m z7W}{;inbODAtz_K6%n!2c%bJRKOU!E-!cD4B}I#!sc9IRJ0p`&PHPQTi6 zX?3eoWUQhXavySyuG$nW3>XHtimSs}a#z3OCEnjTh#u}+`FfGMe5&S!ZVU}9{~^li zOOc=BxVTOLRpI=*_FZk6p#vl~9F4D?-uv#na$Miq(?`&^9%*l#-mpVVQv+GGo4mdz zO@Wo4M^XYI?OMO z8=t0KlTX2t;KYAHguQyXdfhJAy5bweRNb*2JB(|q40P}x_C&t-Er5hc*1yI7fQ=tn zZZar8>9A}JSCw~P(W`L7IrxtZS-)?aiEKKdxe}{ScGI2E@z%;4>{HD*Tj1mrDN7Wj z&7m)@s_r&Rs&-VFmc^Ts%M~=>gmrGvEYy98-Pc2(oBa6k3$x6Ci8;SDY~K<8-QCu} z#N<2dV9ALwxuHiZqq~5W?4nmr)D4AI_a{*^fdSVs^p>UkVz8tE7N>QIkrjX)1H*P; zi9NArZPU)sY*q>$H)pito5L5YF)+1vHX1&kIv|fUSY_zhGb!w@cMHLV8X+7w*7T2Fu1H?5|M#%9v(ez%u>hxIIOy>(CITq!TMr}B18dqKRM1SKmZmn#Q9ecv+0RTG}tkTs7>!qRv>=P&m4^Yi8~Oagu+epto$X>6PwoV+e^WnqYKZj-61@T#FCf zAh1H$-?oO>Nlu(8b=_#?9dn+6%<4U+G^9{76|bA3opBlBeW<#wTa4ngI)C%Px0>Te z#qiF|TGx`9Tu*f~YPxsUVMRp>wt*_YZnIR+iM`6R5SC z06=+v&O=|RH6VhfVzR`(9rrET`Bgh{2>1l>V{t|DDH5S-&WS^5ZQ0Bm5uJilSS%-JlTs5aCzvKG&j(mNeFb$*D}gJH}J1CssA zHoBIMc%TT-aGKVP%cEW6WtkL@B0PQfYkMloC%G+`0N;+5Q-PGE9O0seUaS}5ZhMs`$k1s*AQ*}*XlOdKFTkvY*m zF^ah4U(th0rvRz3Cs_-VQ&Mm|qPwi2Tm1+^cs$ zbggcdV`3r&Qv&fjW`j?EJdQ1v7@OA=xjIMte8Ims5T)Sdfhfign4y_fS|f4<5q@Sv z-s>|Q>gG{%NnC#G2^-Z;JCNqp`OlrsUjyI{LjER`3GU+U$YoWu;k-sQTj1=@&ayXR zov+#MZBWA*C?W7sL)-c29rAbM&rJ?!&G*0bxaPpXw5(+}uZ2+38H?}aJ2PDUP~(>4 z=!EK=-I*Ke+^La(M9mR?1PO#N2ImwBLMHFvKBPuwSH>h*`ftd8n-Oavm6w01xL256 zGujf>9U9>hlkec(W3Bs`XDmET)N)qiPAt;}ciy>h%W*@vd!TYkhF_@ZHm=6C zcR|u6lEppF0z?^m>iH{N)hXq?E4pFL|A(kIafiBn-~P8uk^9VB4x3v#fWTmzqw}N1CO6=Y%ak!#oQ+oGpO?+;_#yW`%h!FHDY9& zT!o6K6S-+}$HZo1J2Oo5CwBXN6x8}&v)dcwaVKw*%dMbW{Pi-5Q-bME;PRhvE1HTX z5_VMma6v1+%q5AmL{##G_kwG^;2(1q?{cf3jtq`Y-~W_mua7OhmiO4s+j|66Y*gx( z*gDYqYcg0L5J|ESXlc7nGhXcBcH6w-cR$&&3~4GSL1mT+9t^SC6AD{f$zr#R0ov!{ z8ttn>R)Pf_OfpFLG(`L~5m>wA!EfBDR*hV#RoM$_`{^&CD-s=!l5nwwmTfL8w(fc? zCtbaWZ#ByJ=41Eg{7ZCycFf#qFPF3Nnb{#hL=uBosGGRi5Z;t*GLlP~MahLwH=R?~ z?ibOQ%!DwHZm83?b?|`juldn&>-{;rNzORZAADn!y^(U@=263?Z!_8lS1sP7OG~je zGLdnY{&E(R-!`@egoimPd@3a;dYwzGC*PukPfA|2b-ypA**Y+A&G$!Nu-iFf`wAi@ z-l#0RhXpXd_3cqh^~Xn?YYe~TI`|oe)xsUjs;oYVck1Q6c{4~hzA~3*@NBN>#Ol>m zJHN1;CRrGT`LT6n@e#xE`j{OjaEg|YMr?hzT-Iqzp7cv$Rh3e09VA&BKQ zbfYXu>A@jcr&KzB?nbLaw1s_7#LxSYJs#UpBWeYyq@{wWPU+99uc$^~X3O2tzN`73 zlvSJUraT}y%hz6VoIzmKoEhkM;;X-~9sGA4_J-gvaaEK=7Q{ znxY}ofwt?!%pj#3RNj|?VkWL#@ii_ad{|#-()_*fKLWe_mS1lU#o8(}UN|2)qfCBg zmmd3H%C|Sh`;{%(`@-*yZ!RGr~77jHz?Jt1ch^JFr=Uiqxb2O*UR~ zg}JFjUJ3|NxG*s#WLX^&^ytBQ^1(p0x*cZINYb@&J*l*cTKv<_823lSv_cnri>B9t znHqG(mbX|jutC=8aw4#~kaBy$BiA6qSyDv_3^4p`E)G1DxJbBEruMF)k6khEl#HYb z&ik)T6QWraN3JnDSZ+|a9mGNBR-pj5>Cf7+B5meQ4-!L3sY~$Np+c0~Io`o=c<|JP zIKN1_So3?2fLeg+C$RcOzvVFR2zc#LA;E(Cd`Q$Bx+fB11rQe#$ z$^MByHBDc*c#pDn?gnW0&gXt)TGECV`3twaeM!=|_)YcKZSnGJM+!%Bs`cgqVEC~` ze-M&d8tzX-#mzlLS0pxccRN+gG)ojg<&Y!WQ~-qH1L(ZUj82#R zxiH}C8mmAQiDL4V{{0OM&px=-EHV%1Hfs8MaH#n`|EU;km~E7&5SaNz0+I6kjY*2b z-4_9bsG|V+!tlDH+J=)IQL$R87-grFU+xi*Izw#BCY};N4MwFDxgfjG@!nrwT~o)W zkkUd=WdFFsp}e;mfJsElk0n&8K7y2Io}wwA@OM`re5Z8wlDoUd)s80GyAl8#J@=u- ztN~%x?d|=@974A%&TlZtjj~%<_Bfw``b?TCQQD(lA!Y^1Uo%UZbm;u0lyn?-^S8{w zTW7y?ypEN-_u`odM^SC39bx*%udhqDMqho$%S|Ejm6-Iq3*r%`tYWOprj>V-`dumE&Sg_jIZtA{4aYf6>>~7*8E0OXvb_V5G|Gn3D!ok^7E3w@ z;tN7l-fPAMFax$T>72SrMKD~Wu+23=#upFqH>$U9*gU`6LA`EQmgC;n2RvxT4&r#+ ztZyM=>O#)vHbD;!Tjcv$MpZ1Q47avu^UfHx%_!<~J=NBX^o@F+IBZp44#)ltTsyDv zHoj{w@2(cLgC4AstSBrdQ}sP6<+PQ?HuO*;*|MUh?ixsC$RuUi#$T1AOi2-%n}q;D zRSpvmTrGgudnrk(n%$KBq_BJ&8I;~iQ#6)rO>I^pDr zj6?Lnsv4)WnsW0qXhBtV#6j2HtAGM96PeDDK=FBz#r|wa+TRQ24zowbz2-fC~?tfw$7)o1~%6oA>-u#{*6U z;o=|X;W@2|X=C||UluX~*EUbLCXC6j*4*YENvD|@3;H;fwwL+$519P^)oy=Td&6Dn zs9)zBL375zL2=wVMovw; zh%@t=u}VYJ#)keZ&45~jXi<%Lcb9$!6F8Z5nI>nbD)$T=z*zbx8~NIMUzPJ<*F?r~ zCk^y-Arr7~6Oa-OzDEuT%W2wH=$>}UjVrMyRlnb?PkZ<4vhd;b zcG{XcuC6KY<^#tgFKy9l&Flf5`+Pvs$Eb{p1kMV zjr_?H|e6 zZngg+Gasqx|5#L4j4oR!rocZaO8A0$oD3REc-Fz2D0C4R~Aj=f^gRF48vF803EiP1{p@B^@^T zyd=*%V0@VQ@8tJ@{0>8K{2>0e!SjG`fW11tyTTfF&vDu~KHTVF@{ntl4CC(TUB#EY z`GB?zdF_FWVfR!!+`&ZjDyo?A#d*_Itz-HHO4YrG_Qy*~JJ;7Ih}<0yBk0K2rW&M$0PI2w_2<0@sZu*h`chej-7w#gw8KcT$q0Vu@c-65aZ37TtV`Nv0$b<|5+a;jgeObJUhwu#iI?! zU?}Z&QrMv*+$iasg)cHo|IqlL6ERl6e+ z9ta&#ei2H!{l0j6n}7FK$-zg$HVW@oG=FlYEw`x-s0@^NeW2i6r#jvdA~DC-99hE4 zx^#o(?UJIs4YY|i@m!LHhq|X7_~5ASMACvZ^C<=h;w~<*-5YrmixHeR%a&)pssqFX zp=e-|_qtixWg_`+`s_;)VY@`2u%vj9gi@fv^zRbB45MGs z0t#`{A#3c?j7m3~kJU94f24b=^5%mDjl$WR5LIqu#q{gCA2ldgwy>4@!raFIy7z>v zK@tKWIkI{eFdL|5f|}Ug?hV*u+a2(&HCznCepfi~)iQfe1SZ$>x_pi0F$Ns_ zxtq$&)LAr}_c)C7Yc02TaNTaJr`MY~xJD~nPH69DUY-_Aig*6XuR-1)Xx$0D|M6;| z?g5$aH%0tngIy{cn=dqUg(sHX+i_0265ytOB=gsAkDAQD0lT`g+Eg~$5ho(y@Fgcw zlv$K2@=|F5mKnozU1q85&uD7IU!42BGN#I~-|NVCHKI_qz-VQjI{Imgu%Ddj_mAVS zh2uKHt}DMj2mG8nK|3vKMc>($His}Efj{qP&}bv}?*tbyUY2)qo+Ua8Bu-8b&gbKI zFLjUQO*nBzRw%rfpp=BSmvCw6fz@S?m?UPH$y1WL6AS}Qh zQ^M&8J>38s+x^vHvOZey9e@z}Kog1yYwkA7q@VuuchuVA_H(%>|XzlHmEbjW^+M|12*E8o5iXRqK^A7}%_oFJ9Y*<*m7W z=mAFKF_6agWTHHbKe2I8hm#{1*co? zmB!GM+fOdWSq;@s_@8oK+t{R`FL5r__WLI+u-c9IIx`vW8kQw1wF+~qQgtrm z&LE*mv7*bSmMtJ_9dH9v`qgkbTdDh#aFeLeg3Y`Bxi6W|6J=Hbjs7d%e91iv{pzd{ zt$J5GBD6oGf*n=|ED76GFG6;F;eFU1@V{)M_ZeArVXrmE*m9y`X^0#A076jH!pLDupGn|k+jDcJh zR!m>>7=`bUn*9B&I4-)5q!W;dT(Vf2A~Rs0HUUx{OG_b0(^cbAS%x13r(yCH0jyiYbSu)iI zHs?9>9h$Lw|GgUO*R{_AZehL+rlpchkCcX}6&WGXo=Po-tlh5AQ0hX_@T2x4pN689 zZ`_ejktQUGYoo+!=6($G=*< zFE5((S<8qM4(u)p-0!vT!G~E3&VK|Vpc2gZzu04(t7#U{)W+O!=g}m@8HqXr6V8i<*0dZ4BziD&lo$jl)Yszg7F`oJFT{bR;KRtl>Za*k~D@o6t zWvCo0hnOJ}YQzG(XTV(|l1^mzKve^Cthw-YA0R%N=YgL93agCx51xLdp>@>ysS}1? zl(8{4vnQrAPIRJZ#P~%HCp<{$_V^AlJp2*%10?DAHh0}_vdh+6$ao;1yr}t+bH;T{ zkJui1xm(E}-$>Y)-N;VlK{r~o!~DAJVT-T2iYO1wKV@burgJNu;9Dwur`k1K9lAjm zez;ixhPPUFHn*+quykE_^y)tBnxo{HEw!@s!vQ-_f>kK#VBT49Kh1)=g$qsmg9ZUl zmL#WJQPwv8SK{mXY<$}K->a1s?msXKzgd=^Xyr&pOUa!+Jf5eFa$`$$Q0RR^&PEVc(`Jjs)DiPPJE*DHx24{LtvH{@7?%YM@E!Nb7{>t_#WoYVd= z(@}s5`2Yj$%tZ9~d~mI3Fxfj7)A-F=iZPvTeCjhNOhVZ6rJI6w(=WvjkTF*uyx`b} z!ci*IjB~%m5a9Sa_gv&7c^lViNx@{Fl^~~^OrH;E?wy6V-`RtAe<6k;v)`z z$hrPQ`RbsWAgnWz5c_0>*_#CHd|sE*P4Tn3^>N{UVY66NTGD+pbJsX)>_pmB@BDp1 zao#lMQBh$VwO3VO)3lP$D??-~cac8v2Qsm)BlP&^r<$AWwv>9b^fYDyRMdw2jJGGR9LHIF8in!~gB?HwRq^E;#Y&Rm1lBBPHO&C*X0ipG_jKjF(icSH($_VuRT#EAIrwI6~7Z z;lwLf0zbFYBsOL&|J=9n#(;o8si0RT#dK&fZ1ZBBAxi;2cZ{am-6V)@;=ci33`W*X zr)|pYwPA9*t{z_=dAay*v7@tiH?#j`PUlG>{(t{rFCg(IXV$wyg#frW;Iw-p-0Uck z1{r(}>6B3^IpMlR={ow}pJyFED)rK;xHjn8I;rzsls0J1Nh5aaljVYYwL`{57iykN za4#RsddzF;|3j!3Z7K`%XCyW&YtfsBhjnn5$@#H@wc_sHEMCB=hJJ8xp=R)^KzC(c z*Tw+|K-|vsW0{8g@z7kUt*%+!DK`>CinAu!KmAo5ZbAmpH=NAbQ^t;& zRw6!%a1=l;sE!h5=<9;m!eq&n#%-)j<08(Dr4&9w#amykNx`0mzj^^>y- z7E6BmjQJND*>flGQy3V?KCOAVVYv0S0h`);NQLf|2Xq6mn}{1tf7UeJ^ob=K?r6Kc z`zLVQV~aO8OV}HAd9tl6Ewo3KE%l!0DqW@74#uS4dI$U(JULQzw!s8-@<2Bt=793i z`BvQwl&Y#`N8gI9-FG+BGhc$g3J?vSR+5^16_h#)*8_yaUi~1QQfZm-U9-uF&b2O@ zSb_(;co$b-dTp93b16RwGHpL;vevZWM6ySFirAxF*Y)0m{Ccvuq|dtXIKc}5?eGie`hl)%oP_1zh!CpKv=RtCwz&0|_; zX<#NKDQVM`M`53q2ZG9jr=o{5I^8$*xlmM(0$%SR?tkg;+21Z4e`zZDOvGPO1^Rbx zRJy}cdt&n04^jLw?ADhMhAmm`a%zy|iPz6HI~4%O=Iy+JA~Ger#}0pNxAs@KA6_J% z0xp(M$=6o)2Vv!AGBPs$`dG`PY|+WAlk8#3uR8m%d&;sYL0*3IZ_IO_4Vg1JHVG9{ z_@L565_~r(OT6N|WykKc?&<=JpOuf*n;0{A}e>X>6FLT{jmjH?or2O#_jg2d~PaP75!dSx`|+44=y7C4i>oo)3h zx|<$0V5Q-P-K}oCEoS)Wa%$$dA_c%W58St&hLeTs8kLcH$BLC7@-MGvV4MwOt=HjIqFUdARel9{fx+cP@NV zr%KwJ1o-#!U|{sf7~1b(dM&o1{u(U`H0V9jzKE%951NY7k*8S`x^HQxa;0NphYw`~ ztgz8K`E#2sG^28vmnAiM2ip$Oulr;9K0wC$G?YLu0%|F0_^r^;^@uS)UO;w;bvyn+ z&Kg;USy^9`1-v-e?&h_PlzI}Pw?=MYzv+Y#){gBt5~vwlu4&TG%){jhwdLhj0H@d4 z$xp&R7-U?3*%blMHdS~+xa6FW0;~@ykFI<|L=hi3eSsZ%jTrK8$x4Ur?jP#bOa1`I z?hy9gL5D5V0+WsQJsGGyV(wF5U;R`bdECFYt8T~^VD(s~0Z`B@mJ=sGTM$sZEft(5 z5Apjy{i48^)!XtXy8YaH>4x8u2t(HwF&ZIJJHBiz=GM4YE zJ@~N=G1whEVfzkNlhIaLBZyG)``pM1*IeK2WIb!?Trd!QRPovS%zY$)AJ^PwE+Z-< zOb_x8`beK3%R`B`+KVMYlwB1+GBp)s{w zkDv1afEPY*Jap_P&nYhaiy`E9H&tzKjO?Vp0Jf7^jiee-+C*$i+MYiFTIx=z04|r= z9|la=7=F(6O*P{Hnw)2S;T=FG#zUu9eI=}a@~ZzX&VAdKA%(06gErRu*x)|cx%EM9 zy%*HzLfej%IG=~wSQQBXB|3eo3nhrK(9=@8w}p;UU`3!q#5Ypr^k==E4{CnW6qT{YvIII*4sMh)t=U3fuy9a%EoX2S;x-IO{5J%^UcK=| z;+x;!V8A5qJzPOaM2Hi9i2}drakEsT*Wyg36t5(lZ9z;M??OwwSRvp4O9*q{Wx}?3 z$qK-bNHPG=hF9cFv|k9{;sDU<{H%jDT`V#4_}e=fa^ja6e)Nu?^WYsusZ@krYIew= zh2XMVA$M-qL7*SG?Pjs>`{7@m)?d1WhJ>fQ(d!CM!hV5;vlj&htE&)wI8W}?PbERzk3>MQZsD3R6EBIX_*&s>mR3xtlth4hUp|8Qp>*R@J zdm?CC43}kRk$$YgPA@PWUZ?xO5s)0ESaDnI&)i$Ul$qOYi2bmv<_%6>cSIY}mqv+d zmtsn&-nzVAUkVizz{>$p@QJeOAGfr5V8&gE*9}s*0=HQ2|)&RTYE7IgoOg zb6;pfKn|oN0TMS<3GuM2??^&q(9Q(4O8t&`}F!TZ2u=i$!fg-@zJ? z<|-#)OziHD3ipwfW!-Rc)9P-?pno3!s=TR#Oo|M}u|`_3^GA=}qa(9-t15m$20et8 z=Jx#6{EE^1t2T-(YwkY#`=IlUXCfGk>$L4RlG-nI*Xrlb=}lM(CrtHot?(lOAFxJ! z&4AAToYB?9u6=8SBs(su|BnuB zj4(}I_Z{2*PV0wF`5uk_CO21V&nRYo4IXA)zY{0_If|y3xY>y4udSNyzLjd-a=v^l z@u7UXFB*v&qr-g+LIpSwK1wCm8N_va5i2VqxI*wqU%~Xj5wp9qSJ` zn2rxt^ZMT37j-s8YNN^AVF%V3^H9b8bDd^dtgpnIJDlRlr}*A&zSy;XSKpAWzP`?Y zYW;9obm;U89;2``cL zEszY_tE41q_mm!9_w?Em3R8Kvx+q{6QI1gntyJ_jg2(TaePp)P+XlCZ+QODo7HDwW zHJ#7q&#&a$de|W(o<@rb414|3HjcSf*Lo2Ppd2^i_N@C?*n%NASZQi5u;NCyrP#V= znWnVeG;P1E`VGkf^#9*yd_!bqAhDqJ3H-x*U@iW@q}1F!=NPSv7^}$*m$($G5^k3% zA%l?e{<3jiT4>b?nNhpXCVqDr^UUFVLkx{ycViZ3Q9lqpOuUe>c`dOeBC#rqr1E;k zw;D`g9M!tQ)>#f|F~gi6T_LINwlU2*ton~73|K6Q?cEWG&x!x5=ZUfmRZ|7em0iVm zou^Jte+~>odjO<;&y@GJw5?io4t;H%y|?|CI_yN}@w4b^)4osJ*(wCA$6lvC3*xUT zTr=J-4Q`M`HzuJ=*@aU2h(xJuFwBTHJuCPWZ|#t}1a|0Yn<jvfK9KT{x<6T_ zNBgT}w5P_0b-LJU{+|9Rp%aWos}ZFOQYhPr1ecBA?Cd5llnv)CH=uY;Fj6HBJ6>Y-l03fGJ^z_8i&R8pE?iY{Y&dlGvcrcZIiJAzIY)vVWvj~XZ= zR|YnwXX_KjVrHHo+``%2&?~EQOpTr*#2LkGzBwxp83gh?F0-fZUy!RBfLk)npUcaq z-RnpB!ot=r80<5aMX!s1?M+?h>b12~*&E>gjHmnb0Oz0Cy!O8zU5Iq#6A#^vy}XYw zev7Q>`eRq^4cL5LVnhY-FJSCdh;^P6|Eq6(;6$ab$1USOtn-TI#Tnoj$)Tis#?p$` z{yM!XEjqCmTusB%xOFl~HL&H7okj?SUN<*RP0shnxK21ML{W=z3jldjedU8`TKO0H zN6~}>>`oQZNn0fiy1m!SmD$WKJ=!*R!y;&)PgzFp_NFRfV5mExYKV7zc_97--3R6l z7x_1B$-6(xB)t3DSk*4RP9!|1YdxqX`??=Oe|(&rNcf-tkL#E=$` zy@pnqm=Bh7|KSnh!8ZT_OM?g9-C!c&Nv|6H-DiBPbNjj!o#AQaE2WVy9nlyS8`cmM zzHc^_=_0Ow#vbLg?ijI}(u3T*&sZ%KZUZ_N3&0xlcf*h6VK*P&AP?xc8KW}8mm{1i zKvf%o8qYuT#VVyZBhqT+$h|@|FLNs_*t|49WYqO64>nu2 z@$f60&zHiqhD$6cmZMtj7@aI}!ccUA=*M_UMff9I@0~05rnwg&+lqupA5L}@xG$fq zfpWMU+tkol&ngx!|9+M`#DBNwvN0FUY^e9$HGsS|27>}-(7v4z;G_YU!Zd zrV=wmwwg&Y`YE<7TkHm-!$5r+C61WU4L>sDzN46YuGd_VCKmbnLKTDA&8~D~oZD+{ zdq~YPc4|w^NT7HH53Jm2OZeqpV6RRcH08|D=JD>~UA|+q9y3AgZk8d;i?HZi$kDC2 zfI%27UGq<7H)(EQN%X3coy=j4%a#Gv3r=_omfylaN_VbNuWB8@kot9=+fN8_3UHE~B~CH$VxI4<~?d70P%~Ui)cK zK9~aM+M|b4k$1pF0hdacY~;QLFWj72u=;*4&~lNsd$%%3zu9$UD5DYy*(+#WQC~)Y>=y8>F6ZZ(niF}8!CTNRkJHhE z>Wk4lRioGtR!N3PJ8(i+UZc~h97cO}`|I8(O4+M~@Y5p^N0l||?O*FAt?~_r1Y)O_n~W2pfX%D**$ED#8#vBJb*ZqV6VCN>eH-WLDQ$U zlnAtdoDd7N=>=lrB_pl5$~x(fwqA17i3%elo2fF=^=?%CHI8=IO&|d5V}Is?c9Hfq z`8!QRo_#VKjq4vM@Ay?-6^YG6N*0uqW2Kod7-Elw$u|F{*AXd}8-N$qb`*BAbsHZT**j)UX;x`p7(Mi{yMHcN$YJnG zsHs59CQKi7{0@T9u$fVjUG`I_Zce{c5W3^UTMZyG?w-SL8&Z3DEDuau9@m4Fi%$<> zGCfS>W!|CgZ<1L46K2s6oTo{%T{9#+W7k4k zIR(FK=ibT^b)izDw?m&5{IuV}-@+)^`}LCDT_bK>41&6?6}$p2ViT5HcOI-f25+0B zuOmhX4!W6S7Y?r1={ad9^g~_)XKJpGp%!V+`B2NmR$1e8*|^8u&7KHr0&{so8Y^An z+KpG_V{A6gS~bA^2@l|fgU^A~KDE&C0LRqg0FMLjXVrExuJ6J$cfU$5Oq%L%Z>W0+ zCX;{@6Btb9+$BmT_oGoJY$l1unp=lvfWt&fSsJ{NMZ9I!Rk*(sadc#Cpce3c>_p7+-b`?Gg z?Kf*Cu({6h6HrUqe?P>}zH6Jd+?hk`vrSqQ?icPPBINi)rdOE!px`8aC7))6|CsOx zTMlyTQ0MU@;Z~GLV1IAN>c_~$pajQQ2IA#pmkIcd*`vF2r&|WoJzD;H?|VNbAx(Ek zYO@$!T!aDmjcLIRjsNa*5)RcUFwR{q0sC%8HzxP(%g(g<_S>m;HeR)2iLi?)f@i^p zZ5qV!vn91xvdd-g?<%y?fjFHiYp47zIqTiR(-pe)ty*Y3%xtc^aleznKu{Om0zT0F zs9SJ1s6D+VtPhS9cm{Rm;GfoCsRKjYrT%&q6?6~3+E>}0Suzf4kRf;`7>UYj?^>YF zw5lMx+6V6!cjE~Hdt#A%xE97t-WMVNN)^vSIcm4=X2Yg+iQw6wP^@%VVn9dVe*8~F zn#cj%bE11w5%NGf%`7$cPy_a0{Z7(#4GmK8M6uE8Jh1Dv;gAyRJhz;0cC;0h*529K zN8Asq@Krj>s=mELihJcz^%&9Y!kIzyf@#YI7R5z@` zYj#6RM8}F0NNvm$XW~sUMfPhhO<9nAD4MK-cP7e_Vx4v8C5nHjo!PXQ&9E~xQjWo&w>jHZl z8h+R+c)(^DSU;ywv%fYDg`ZJzN_lfu#Mpu#YqT(F(f6$5M8 z;ZE}{H-4jzY4$`NY%~wApXXN?QDfsjou8gHPM~rxXiMfn+d3I##Oej{3vkV zGBGlCf}m4%v7r|QHWThvyB8QlB^+}15taXple^ISdNb9Nw`7*_b9&l-Wnz)kt&U{t12-JqzYoqjM@&3?6nnjfbXoXR z{e_InVj|mLs9h=No)2Po9GscD+2j;mT0Ow12QZNZJ&JjOn!rq0pa~x5x#zRZ_B<1R z;FCf8enPf+cz?r0{(N+=y5ORA^zTKr*Ye}#eyrMkSTy@7@biEu<&>ket;XjyjT6^X zFj7~pVdUt=c}dw+beZPm7RYoKijD6buY&K*uN5RXY7<=&>cZcJ*Y7Mr;~V9Pg`q+6 z&1IZsMtR!6B!F$=(JBgWWlushhtFh%XD$|d` z+rm%EgdqrEu3Ld=lU&42snZXe)T8?sdYiZ(M@_P$G9?NMGA~>kQVb8thNCto=oP&{ zX}j+i$3*_VxPYw_aUHQQ?QM}qPmx;MW(oT3ot2*rwe6g9vXep*FM_P*=yQJpPH;Sl z6@7Ty!A`q`tZ%523@iSF!cev}Wsj;2C7 zaGs3ubNh~K*qBEGlTh*)z5&-#1TuI?Bq{cZR_5dM^mcc;$1G_%ey35)%ILL2&*-(! zZu*3FZ53Oi`o{Y~g_P{xqWU7IwvSVKcVzljv1!)rDm(#q(OO;=ELC4CQ&Zbi?L=8w zgK@Zp1E2SYJn_N(kNdDYvAfUw8rJ@H0)xBbYxmh$ZeU3JEIImy3a=Uepd#zz>%j|knN8m604>X zr+^d3vfFT1F0hoTHZn7&3>&F@^UIrI%k8v|i!CB180EQDPY&V#ge+3< zXS>N2R4t=ob5b#fcOX1Lr9_`&7k**GlXwz5V&7cRHu!l*L)&vNO#f@kGuY;jaxZ;V zunM?z^((Niweu|bPrb6#zGisB-jzhEk!5jnTxzeeRC~dpm}q*;bEQ3oaU8hQY%mKZ>3IRiMdtmMq!zu#ECV8 zI8vV`Ub4`fz=DSh`eM3x=3nLEY%Wm{8%P|?E#^41PIqo6tO1rQh-`F={h3mf^KvFE zE6IojJThM~{BZ4#z9zA)b>)J^wwxi&=O`Q_H#P3Sz`MV2jBjJ}W*qQ7+sGEP0RT&N z<2(Mkzii#1-MlyN`EQ#Odh*?i7;)G@5#CpTM{N(W;41mvty^{1Xpe8+WTk3EMw7=C zK_U|SRugJT>v;5x+1B}G4}~D`!Q5~xmv_Ksrv_gp^3I>VH=$2dG7Zdgkk9WZC2*K zTNZOlP~>r?-YH)HjyjMvaQ{^(zg|>@q&CC+kk3ng60S ze)hO+rw)`lk6I4k05%jf8djb`YQM7@2PCscQ8Q-l%Us|1;UX#eiWRuX3I=qo7-ct! zhM(7Z6i~BmvUmIxcmAdNA?CzyE4ebZCQQ8?c(?7W`jLAD1&(DgvLL}#tf0wro8>H1 zq36oT)FQ)#3f{BzYNL$*i#aY&&E=MI-)273s?I-W-m_Kp3oIl)cntZkgZTCA$iv5VQ9l;@3S zZL7M2v3ElwW4@Dp+`_STH5N$N$e{YjSy?ramAz<71OgK0Vn6jzcwDf z_36YwCXvUZpA*rD+ft9MQhL^rmKUs~Q8jsrKlj)|5H-GD&eX{23+No0ft0z`1=VnCh z?3%4L75ieTy1tz9MhKgyr?RjNx~Sm&EqDcB{obg~V56DjfwqeXek0cqGpssWEUp4* zJ_oA0uW#yiq^c?{Ap3-@hY%SS8(mX5r+DLTsAT1~_oM%}y%15bfr(C{j zt|%J2)ERIEO!}KponGBHDW0MQ(E5}z*IF-X$qxqqBY*A(#Ryhow05X#aD8H1o|na3 zNuq1n&9wzP1yrw8th;z#HcKD>uj=vqb7pt*p5>8WKaMRD z8t=*QPwFcYd@$7;qcK^kYX*HaopL0Pchs@LV^D^&ybG?pBHX>}|V; z+ud*U*|)GL!l9+=bnOh(iO^O4G0+{OQC`E8q?VOmUSCf2G?L&k`D2isj+vJ|n0NT^ z&Cof*xtX|fuj}F6>MwquCf{fZzc!FHq0BkL$tVl@ z+h1a**1wcvIdAFb#;5eoYH1RG9#M+^{bMYcD+8CAj(?e#i{@Jqn(G9nVWG2P^(Qb- zlgJE%H-BYsywnjY%DfUt#~Wn%3aE^8oa1&FsfXrXf`ZUXxVWaadX(3m=gR5nL`3|* zyLJJ|@zZ2Uxq=4@WdN=)?JG~}NgUxTMQtFN+~R`VzRz&FuQ!oy}eO3EmQ2R#^eM)VYy z@<#6O_Ly%MUD4u=z}8ZUV|9NubRY~a|FIBOkK3KfQP28z3vAMISEx4ad3IM=@8p|< zKa%u_Jqhi*Yt&j$tgwW}#b|W&(YK;qtD1R{A~fiN#oO97AQE~oy?tmGn(s56Mr#JhCb>9vkJpr*t zlS0L^MW5=`Q(m2uhjqG1K>Gz*x8oA<0JvxA>U^Ty{9biyBI^ps$MXN9>8szGeB-ta z6clBIbcaqQCLj%)G>CwR0!mC62uMlC7?bWCDKQm=uOf`@k{&G}qbJ?9!NwTz^1R3M z`~&w7_kA7L=RQAYiSPxhqq}iGTB!HnV_kkb#zMzYAAC+|Px;1p_Du9cs_we+Vtr^BOSsf-a2Xgw`FT^iUm#yut0#zTV5i@Gui{^g=l(_i4H7jH}jsE!t(t9e$s5KhxqTxY)}!zi$Bq(ggQw%|Ng z2QV%Fe#E!8c)Jba-+k-%7du>(ixs zQ9spQidA3NY8G;?zAR~@h%@e zNy;s!C+VQ6SpRZU@ui6$*2vl@3udhbl8g^-E;gZP5x>W5P(i0InG1ge*6g0++2p!` zTQFXT56nHKHdV!r`WU7*c442dhhY56D<;?Kiv8bLS#7^Mcg-OX=VbSY)G=337|+Ua zT1$jJc=%i;x;y$oRCg|72G-y{#UC^(F-w2kP6bTZz@*W?bbj%-ZdDxO0=f}Jhz|s( zuU5!3zO&*gBq&g5!8^3>%#Fa-*9cr|lHZ*bP(6=?!}}``53iIn)1w$!9F3ylte#(I za)%H0G|c8Sq9=aTC0VW<&R8Do8d_mVys8T@A@oiUa6X6ThV%XEcSvEa^L9B$0$&{v zc6>UfQ?uT;;+5k?Vhh@K`Sq=`RL&ChglkuthiU~>Uo|x5kcfsUaeh+BDa(yiB%D5S z%9KnmzmKzFJNK|~*HqS4PGaX-^zPeNU5h_eAp~^zX5j9wl&iYb)U7825?)WSkRsv^ zK;4DABjOg`=%;l`O2hV>-iE@C#i$0Kq5j%O@3voSNm;m|(9Pke9pl~d_?5>H`)!Wu z&n3J=M*DH>r=(l{XAD;og+BBQYbPrb8LptiKE|x64gWXMg)7eRe>nKZK*+V(DC!Ak zI5pu>+~^yjOJj3Fil2=MN{(h!)veB{@Q?MHS~I10u{@078Pz>UC-Z{s89cX28ZM&D^)5)13%Wsj{UL1c&TM%&paxMu>>K^=}h#ny?h#2QXX zzqdZGEMyKdJ)HtHYD;$4(l#Ms_JgK_3v=lKb*?bqsoyF|WhcJiRw^HlCaYoONcEWG zCgwoRaLRCIS`pkjeTJ@QZAUI%{hBOnP-|wr(A-Qk*`o>u6&;>z4f6d{W}UiOe!4YE z{Y7_Vb?q{9r_UVfkkx{9E_?h2W0Sr1rUutbgj|%NyJZ`XKVb`$KJwMG<=pO zx=fh4P6FU1WtgP*mSxCJhbou5R*$>wB9t5MWtDf|>-p}gcflOFou4JsRBn!PRTi}8 z+3AeafhPZ}DhEQddDdTvPVQZh<4bqkx0dQBlL`7=zQ+QcbM)c)Q>~f1;b&-}8>_KC zD@MwY;1iJhcfOQ_KSO4d^_8G4u0`p0Spdl$rw_#wQ_8(7-X*^gt++H9WBaL>Q75!y zo|7S!OTQwvvKq?q+nsL?SFJ*BU10Pshrpx*w}!%tA4x;SzaDY>OeXs%8X^TAct0(y zvY70RdT!cu_{&YdyJS`UU(%N$b`fkhNgSc zBay#;SBRGveq*l=UNtIZloYu&)#&P(!W?fl+{hEjlfv~0H(kd-bEk~X!=Z7#D;r+J zeRj`UNGY1%8Kn&8$N_{c+HR@b(v@ZX%1mH?A#t*I7LOF_A^v_~*nE=NayKh%q+=tk z#tzHcA-@j-ih2jQ)sTnD5vb@hRZtMHz$^J z8^%*NM>O~0Ln<|JsK4PwNwA*n{n#p^HwDBo7a;Z0R;MdLAM$G`d?BI$K^Lz!4%ILoc^p;tclW$b=d6!#6Zw9E= zJ*a&tKe(t7`sUa(tOWb=4V=i!bQ z*Ug>#e zTfjBsmVmN69=_DayWNfO-$POr~Z@H-?2BdY570RRN{hAVqJ5d+_ni_ zDwA8vNN$>!Ps(SXDOnmOv?h#ot$Q}`i-r3NtGx88;DF-3$afzhvMPaNQ$e8G^ z+8#wXi*(byQ9c_zCbz=MkRHYdLd@c;%j#WT)f-`Z6U)Prko?vU5k3A_x1qa8nUsqMzv(8VF67l|~ zUQ8F44v1+AEFHHSk?8rX(k6+N8}oRZ3@JP5SJ|7aXRgt|6$UI5-Vu%v=T}dNrzj#` z6eD6#1;RCRb9ZQ$zZ`S2Y|{^LZUdl2ela>k@7~UnPv-#(3fqawl1=HDcQpq`c}!m- z1G(h;Rm6T(OC1D1VgBrnQJYtKlprKcN}wcDbN0)ermjFOAv?P2*O37EsP*`*pH7GI zwJEJn9n#(et@M+>)uE=I69419J}s@fqp@Hm`3wfoArr z%ws(}6b)%(9$&(~)%2aCH~;O{S=03_ou#lju`o|;N-$fqVSKtGxY%&PTK&_K3Ue4O zVyp@)=dbQFu|WQJ#@{+Nn$QM2k~+cS8T#Q5ZNm%?>?i)i6eo;+lwhYm^>IaRUSE-;MvO7bMnz{X5>Yu&ax!vc9*YiY*?&KBLf!+<8otMH4MUIrFTb}3irjv(EcXKmWgc|@Ja@$@Zzh4mJ~v7(`S^e$h!>5e+OH?w6lv7 z1Fv^CzB72fQk&*ei0eX#vYq~!zDysrM zXKf$1lkU}^;&&nsPItQrRYt7q2Y>KmMrJyNeIQ$%qzk`zQvIIl=2NF{_j@4xv9wcC zAnfo!v{Etcy5wo5+4rV|y5nwaKVMOxxZ3v`_lw#R)!im#tmI<@^>(_}F1%$h+3`>bfHd$^lVmMbMHHP>N_1ewb;+Pkg_>lpVN|@y|0nixGJGbU0Q|T zM6$jXQ7^t!iCo>)6M9PxU|T^|_E7a6%&f}O`zAsR@6F4Jy&ALMccIGO$nrlggMV5w za}v=H%9TMIEzF6POWIQE1%xy{?SX&0TPitL)a`DldqF`Iqb&(Aw__v9x&@IZ3mEA> zWEO65!wiLe0z!^W|H`aCe*i7{44W6OMDKa}RUS_@dKa+c1i10QZW z5rmkVmv$(x@;CE@wS*>5RO+mO&e4U?)gSH2zS8Ma+WYe*yA4^M&E0h^p~`kUD>7#+ zpRLXB9;dRGD>+H(oRt~%QU$}`GjAGq!n5=&ym>w9#VrfAYT&;kp=J2OVD1|FK{+zmaKlD-xX^U-t$qImpeRt)_Y zzX;(Q7cc+rdesUj*YNlnPrG7a3Qn#>J$FCW6OXxuDs->tI_TlcsPX5hp*29ENEjRaV?ICeca6w{ zFecj+=Qm!C&0fA9Pd&yIC5?53`((f!^zF{`n?Scv!&e#p_n)y;)M1!`XNmZn8o_3* z=7dPIox9zZfX1F{Y}lFeAJgOi=2b8cLPa18a{QU1)<4Zmc?0*(k_-Rbg)MFM+oP-z zTp7P+;6Bj%K87#;k^`qO)V_m??srtKppk@NO692cwVfcv9JoCTWOUj6ZO)fImwBgt z?tODZO!_IGlU>EE???&Ym`-i~Z0t7aRq7Xq%8-Et_*wJ)E4t31jhC?YnnXLvIl>dN zbVJK>eWtWd3Z*fb+*&&%FL)=s5&JqX&1=^QCR>BL{th!<$Sc4dcmMMlg-1FMA^#31 zQl#@R>G^#p+oHLKTZ!^UavwN`lD+kFZiVM|Vg!Q!!}l;@KcjOWOCo3OCo~(46Qk~Q z{I&bRU+scri!YK^dGq&$ zqg-BmoBi^`T|@7oq0=8Z{VIP5xbEplt`76XRM@`m$p^?Xk7b|9ddq`p=Y~>4LdjAp z;z$!;pV#Hw)k-4JpYuu`M2AktmI7rDGf4?_|Ct@Kbyl%3_)Umwdfy?4Ja266!Y!WO zmc|aK#vEQqDz(Z*_w*(3-}J`?xZaiR0)PRFXYiDd2kL-Fuv3vw5pG%q|8C=3To(>( z@;dqs_n*r=qAM3JT?h@H-0}%2HM6B-DJIk2rl!{Ax*|TxyF(Ft(Sn7Np)dLT_EXW* zw3EhK!V1UlTg|U{LRO;3ilQB>(=g?k#$QJkMly-bIlrtw8vN zkW0%-r(hSj&E99sZEDfPyZ==TzE_DmQ&sD)@+Kln_yLWzJ+hvmlPk|b%b{=f=cKob91Cx>&ISS%Cd{vM8vg-W?RL+m=W z?sbReCp|jpZZ6$d0NTw?qX{a;}9omIU9N?dgbqT8S{Ffp^*8{1r zKYotGUe88p7)RgM?GPB`ineVw-fcxJlpTrUziYd6*=_Kc8HCJi=_`4jwU#eP9y7z| z1ugOGd<(ly()iSj@tAL1lri^2nc%EWBOW($mD95$h6V~(Ef57R$<$kEZqqB%%CZqln1`sZ@J`7xZjx zk3Hq1tcpj2;&9PUbHtTA?lKOlzPqH-3;fqu_hPu-(M^7*@WNw{bC;#`y1r9SWgxOe zuF02_3CET|k9L#381h(v#-2Y@Df`h~>8tTk|f^xbdgrLmLfORl80z7!}ARYQJsjStCR>=pJ<0$uZ;(lCpS7KNns#@4mT+sQSJzpDIvzV=a zH(qsfm%rnQn|qD@#K(_4@JY@eZBN_#GZU`NO!+2TitN6FR5TKqjIzt?LQs9#BG2Ah zlC5Sv?~B0P-pr93=ehWy9=08^RLA~o8ralE3%N*5j_%Jrw-s;3ERG?`GJ0;+d-=h9*vFkRRhs$)5vhBEF!Jr>>#*FeE}}(>Sh;$@2gPyc zjj)^8BoPI(JCQtto|ZylZ9#A(%e?S{uuBMp5Zn=IY1p_zbR;RrUbJErxVn+qgXn=c zPMVkl>O@zGB)D{^PNc<|VSi61Cy3J3DFWMh|M(QB-KNRv&{vEHJ7A5w9Cl8W9 z^==XIyD5Ws%P0?!$70&NyzLr`b`3kq(0N00o0n>MNE zOWTcS$swT@(sf!T4heLe8$=#4==Y1v74tGc`R{RJycBU_sWk`}>fOf$WVDqw2#J=z z&3_xjl)R$eyB}F5z>JE^Bt*Ccs2DolRu1Ywmfu-C$u*eBX$~%xWEOE@oUix;(dl8r zh}5Z(THhsECnibcwAAPZm55`9)9&!dW*TBnfc-q1aj%Yc$~2!L(E2Zi`NxIXrFZJi zy9%i(Lq7fSZ8BaQXPj?f1an$cZJ9mSY!;&5$2oO2_n4ec+PC zwi1Ljnd)lq)Zo?%#g>NHP9&T}Hig@MLkPTd0W=^YL~+NoPvwK>NUO654Mgg!*OE%( zPz^k-JK$~mf)is!>sFfF%>K5(-XFS3)R%|7@& zwuGt}7*OV3neC!Kzps>6!fia)hy6SBM(FzK6c*e|#I zbHS$WD>yOHX4Ymy!7d<6yAq$r>EqPq(>b?g@uBqeGE~8LGtoKKZMd(hemv-(N<{Td zB{b;u2vc$Kavryoc1{=KGCV2FvEh9Czyn%*6bD!Dbe$2;L3o*E1H^M+p|^ zTvt?fgY?omN;0k9%K!v%D7}Meroimo+n6 zxiq4*I&K{Ue}~|2-&R`B=QH^As&UN2xiOgAon@j(CRgOm1m4B?nIu$1@`iLucLApB z{lXvjfd7A=@uHWjSY{NzNbz5P^_VNdz-&VmcS8lv!Jy2<(wSMidgJ9lVtU<6Qn*Jv z<&S}K2IVA+p6TNkSjrcluPkt=Y|-Dqqx;ZS9h;XH?LLe0nAql zmu^3^50oJ12G)+;&AtlQ@ZkPO@8WSHTej{u!PSMo@xHwVi%5(gv76c?`ZD_Y)0_m! z7%JW0V?o`i+y+{#ANe2hvG;aZ`#^z{W*fOIZl-8vCC(2Ku2 z{N=yj0ADXOo9NJrItZHM8qevtDJ$e@WXDi#$Vma_*;N8ySEFn;c>XEBEgy?M}*v27S9EA>l!B|=_`XU;k+(v z3A1eNVGu+LIfs}kEw|)mA;`vu!80Ci>0Pjl9ZZBPVmF_Q<_+S>Pd?wl-A^d~2U?0^ zA3`$v>+i_e9elULSp!y8T*`W%n{1L6f z;hTWRa*KDTE75)6iB6B>G==;sc9$-p4}9)_n~RqyaOVaO&<*6A`i>rU_<HydB~+{-BnYl&9VAu0PTb%lC7B(|YRXS(~FlCzpS6`6o~u)`NFbcZMtI!Da*E z(*6;{XW+lvKQzfP|{qcdKNr?V{oxz@t0X&ZoI+8~`BkWmMn~7v)F6ww}(KQCXHTNTAbO z$l`ZOxp#*^6gRW-5%#iZPR`4aevx&n6Nu**^fl4sOu*T}Z=uNjjaqxjH@d!Ee@Hsm zRZG4n5=79sDWM15udq}#*%xTqoKWYN#2)M>3rnnTsb(LR+o4YnM%@>qtYyB(4=E7m zKI12=%Ce~R)hWWy_RPHruO?o#-1{Q{^}+~{O#PEiV~VF{n;kjit?7ReiuOOPlGCEG z@W$e;4{$&oMnwHubqoa5Y=!;3yB165%DQJXu|D?}4q0px9sFBJ3Q1+;wDCYK{rTju z+9Yn!5WP06%zW9sc$GJWK0U*nsyZI$9Z=BP#6WgMhr;W7t_!oo1hTddkVSYMe2*2q zCHx*M=z3j_{3BDIb*zVwr^r=zC2?;s9v_`#gX*fRoeNx zO(nbLOwva~tEr2@Owppl_8pY?nXf}nfd(A2K*t~VU6*-)iJ5wnX+brHk`L zTf-J&?+J1LZ|-lUnAIx*_#X(iBT$F5KxJ5O9epWc>Qap2AjStKaa1spze1dQmO0?bvEQ+iRJ>w^JZ$ z^T2ZV(~{vmG55lu+uF;ODq`t8tz0XAxI#ZQ2oEjLNWt{{{cVnqYqX6Mw-5au$xYrp z@5L>NQWOom6BeXl65M011XX`)al2ZpBNS<0q`IpNVAr6sq^Pi7zt5eW>Ex4A`BS9UXEp0dl%YI}~uzTXd_`EEm zc=pB+-c+lVU={AgHg)v$`)s#NUbt*jxY(NRk!ElnOt-c3)Hocxl<5k5vCs|zlGPFp z3K4(M9m#llQKrIGmPybHLG0zDG(sA#QV&t88J39G<9>bO7MP2iQoNyoV<{hyC}uAy zHzNH9#Teh)^W^k#V?fs5DzJ(yfI_sFFBNfBbU_|FsLsn%Z3$D zf8c4@Ht9^Lg?lAy^ejioP}pAitR35ImR&a4Q_1rp;SpLVX7c#1L}{%5KX(yq1j3dO zdup9njNfrtX7PGp_>{iI!Tz|Nr^BLMzU;C|Tf1$s`+u2z_)6f?>e-?E{G593DHm{Z zAR={gH`6-sWu1a<;ZvAMan;}LWw!{t$?k``XNt#VZhvCF?LI564acCd{AwJ?Xg$$mWV;}@YYg2E$7e<8lx#!LcfkAKqimwq9!inU$egyqCEeSscV z&RHqB?u*&sGB!VfKGk$&)K_X1e~3z#l=gqHX^yz`9Uvgv@os5#0w^#UwV%7$@t8a- zf6bX%vLt8IQETQJ@XOe6fC+_C5Pt!(O+M&H@WGmEgm<4x{AO5ooSG!1_a)lr_s`NR zbKLH$SjecNt`?GoAY{`&oqQ=EN=7OE+Xti?n&tc1s}uoGqa(7nZtvTKQl|AqfXSZm zMfLg%*y%S@i0(V01>g+#VbZnZ#*I!biKsov*%4~SIjBJ3J!k$(qO*xbB(Dr9`kJ?K z0Sc0KAiya+<5OIEfVqa1trAMxDcsJ;Qwk(O*S%UJBuM4$2QhT0)3ZbW9uOt6$}fRn?Cn7m=3PQpF|1l#!0qAE=Ta5_>|AZ+@e|5T>A zxywvcYtADV3oqnNQ*1-~GE)_8{6d~<;y3-s2$gmB_>ec``wjNCWji##MV{VN{hYIA z`{W=I{{RD2e_)C;cp3HIbl{=+d2-6lpjksrwJ5p~swz-9Cn?IleaAe7Vg9NvKk$ym zCk{?#+2a~>t}i+%HvOZfBfxal#ONO<&qa|V)uq2rN{#Av&itcNQFf@(Ye4d6W4Lv@t^01=fZRy!33*j%J<|m2ph^0E0?An9< z1NSoDF6VzNLq@eAFZdRA|Adz&=z6ev#M!Mk_B*QoSQr@};OK2d$54BFagK7_ta@|PjaX%`lrQMYXG*|eRqm~M>!UCG0rj4G8$Bx#yM6-C-Jc^oe^nWXk7q>Q zK+2<3{LD&ophQa|$W2Ia2X-?X6iJ!iF_Xz{Z!}=KgVpBD3x_}57#19f>4^O2S)Jh zWS5<1-=4`R!yH*hW89X6-3w2?K=nGhmxD&~ z@Ae1oxAs8uh+LuwI^G;Q^~Ye?sM)fwIt0onqfjlVck3z=%p%y3CA@Xrb^n<|?d)q~ zXQRLxLg8t-j5#A>T+W$e7wu|lbDXF8AU~V=Bx)ki9xt}dPB>q(&@pp3U-^tP^y-~L*$IXBxCW) z{fjkPm-u+yc+egl!^pJDm?5D*O`hDK8|gqO)G7W{WX1Tl(}? z$nC|0*Q?S!42*5C5E;iyY{JRfy8W_>QqO2$jOiD#e>&Va{OTy z=@@>WK(f==}|#{w&((>&xaY-TJXjniBAG0xDAI*_c)5y=_MK z$J3u!^3n2+fq53xWbpfEM+{S|-sA#m^wFI*Q4e{~VLmUo)$}I3?7d_^;>p4bkNj6W znW$rTc!jo9gbSn#fNwxZ18g@dTY?7gUE-iXWfJQ$A)vnuVDRhyZ$wuhh(DqO9RD>i z&6>l6+Z(x$c{3k|8W1HvTDahywsx1Vrn4D$vuuv;iU3x?>?AvURO2{oHZ6yP+;Lz^ep#h>%I0r4tzSKf za@t3Wv+|3mlN1F1j7Nay{WXIeW)?qVPS}-xLfWejk!!Nlln%$ET81tTAHc8G2agBD zNfN}>b(LoA2EYihxcZ-fx^L!#Lao5-t~30wff-bP_Y7^@n8Evp+NHZOb3IPxeJUFi zZiOsLvC2L~MLUc)iaZ!Jl$_b_-YY&NJ+f%)c$Z_qfapJEN<@$hue?xr82FAMVXA9~ zH3HSOYyFLwJnv z#}hJ7z&s%4VokB>NcbZ9+N|h4^?A7V(WpR@i25CZ*gr}E_~yBmPLzh=jn7x|5UO;) z2v0t3uK*pH-N2NH*Z8;*Sw?^XTZdcUM0WbR0aWu>hv~%_HFfJJG0x)xQ0)HPVNY@S zs9yn58M!I*gtH$sAC8m^C-p70IC@RCwVMoD7F6w-rP8(@ECI?6k1APyoZCagOE&$d zJ}^F}POuXq0>X@(PA@;)d+m~=nD;I;@T1_}^fr|b1bL42bU=AJy^L&trAPjJKfJzE zN3(byb2wgbt7}jvK>1|#P0bDX5YY=}UWQDnBk0v{dxM`j;g7(U{j9I_}*w*vt)rYCi3gaUTEeWGWE3n?xrW53T z@ar5aRN`ct30aS<$&??+hq`4R>K#7(JCHfGef%jO>OV;&YvD-OsU-C+nw)H#Vp%$H z;G;sAm275F>a_0R5J8RGSscpvuOqClSi=(qc527LWsSL1TW0TGXlJNGRfB>5lyBR# zO`H=}CO2Ie2K|?HoeJBUPahK0+tly+)Cbd_>S$c@ZtR8@%b8mylJrY*$=56X>;igU zRjJy(cZ+&lS=T0Do{~^zmH8du553uDj2SJUG)j^9cCt!!_s8bkxl0b<%>qC*hF$-Q zrbXFj77@4qnou1>iDYg%Kjn88P|7Opg}I8`pOCCq@$s_mLGp3J)~f2;2UDt7M2uF^ zJxWa}BDu?PEIhrOPOtyVhZ5tG4&(;t{om;^vn8#Hyl)olyc*G$2`ozIaV^w~yv@CE z??k|;NX}3AE=uFBpkUmmmiEE@x5bfH;V^wpGi`{A^6KX0h~v+NN%Ex6LRsThznEl| z_tV{u3Jk+o>|7Rbp5NEHP80x32602EFWW#`4(jS8AHR+6LPYIDt@qtv%6tp24EfbG zEXuc6Bq4zkr3!A0cF1t8ia|8Jw|LN+M5m)95X$&cm725+ly+wUG0xAW48nw zI5_2QCh0pHr;|K#gfec;0(+ae6JN!;GMDeb7()qqE^F*;@A54Z&E~;96h|PrwIzWY zYiCn1L7aQ!QsVI#XMWlkOc4+Y#UWd)d-93=bTn+#^vl4qa>dI(Zuf1``i5cLd0{w-2 zBE(f)RX*4J!Vl6KvB<}68SxD42(2n5f2m%*V>m5cI}Wd!N1X;+H(Qai5ceOE9uY_O z?5tLf<0hk2Nqr1S@mbJxbs-1yXRO_#i1K*iGoTB1K+sX-WHmVz)Ev?LTZ?;CMQsQw zQ8?{L99h-svBBu9w!&5lH|GN?Ea7_m4rE+Xky$;otpuBozDOvhI8pe;7cFgAkLe}O z;$(JNNbv6Fu01faCE*fm1Bann1oR9;4N(Bg*EfrdIS}{9hwfQugtPy9xbkD;AxnRc88p zbE^y5$X$x)$+;(ot8}mVy>v-w;1#zgGc6O$McL&ovTp8(xh|>Pt>4gMYPWUJA_V{^ zOmD%LTSC;k4j%&Ei7``)WSH{Hfp>saWj<*#hjAwpOHe#$0@q#v0*DQ17TbfPmnzVRaSU?9 zv`j9-|p#D@w_Pc9k5IA%XdacZ0TChIMcGTW)Q5EF6B-_WAi&vGE>L z>TzJ>f{sl@=E|qNNEjz%U3|Oy9mP}E?ZV~9!$?2>SMn7Sd%2{c{@t^MPwo~=FA|(z zLMv68&-m|OQ(g0k4cx8&0WJS4%iC#KvPrCL9{STbH$*u-wjbYGdCJ!xTSXE!ecJ3_Q~tm$6S{lgpjDPKf#)2t}YFUp&ZlywG{4 zqR8L$v<&3BAlTrMXf`(p*O)aHFFaHY9WVG5W4WAou6=_~ZcOnkNzdZpxdJyX2$LraD zZ??M+2feEW zHVHRdCq$V~ROW(iWdf6A4zx-Fi%?${ktom^J$siKqIg-+N|gO*lxe(MxljIq=^f#w zbcqAKlJWY%l&eHr|GdmCp!oxKTxERo^X{#d9^{k|#&W1H8|=no7wf&BWKV;`s>V=YeMS94%{jL3Q+_(u%zt zTP({b|7XVnG`|kWA?7YgmtTw32q_Z7iTRm);Yv}m1JUDlF^$j7buKe{Sg;VtOB%ut z1Pu#Ew}OKv5Rs1@M2r>wUaO0ak4kcgMOqWp-i6`Ay}n_%E&c=Hk~`k}*v1Vbvxl!p zRPOdltb|>(-Txt((bnTx{!a^_XYSA*;*x!?x_)-YMmnPBM;!on+I|G0+>xr4OQ*!; zdr6t}phPL;^Pav{5qo?B%LduI?q~>*IPO+5))XrDFFfteutVk6nk;`LRo&%PZTpq^gt$j^?9+ZNakt8JdX% zt6JzNSDuMJd$3xtWf|CSzp<71acSmw#I`p*hkLQZF;aaftvS!hS~qlvx5bNo6{GwWaz2w)Qo|N zGd4cA#04+%GKKN}@irvLv1RfHe$Cy#rp4zWKHWrd>`H7n&y5%P)C&)I3T#yr`#auh z-fXEunb}wYU>kd4{L4SY1gPp$Y%uBJd=QWCmsGIy5!8~EojBo@<^ObmG^_0nlbrqc zb%M@t-podn^L?7OpJnOn;VvOgL#fMi=ym@vXj%;PG$9qg?F@;23vSOVQud}|R{W7k zA3x=rm>pTUXnY~Z!*47D&Oa&li^Jmy4Io`FLh729>j|ySl9By zNU6fLY2Mc$#xa7#vAUaPo=BYvg6Z>D&8UG>xl)&vFc zX!A?HYI$>NFGfet%)|@LAQ37>Had2DoLn0eZT49!X3KPcQo_5 zuc>?Vb6{6GgcGK8_^?3$nNY)$CPLOY`%SX6Dst=PQ3Rbj6PS%BfLU$QtI7_emETzk zw(F$Pxhp}VLx{CG6Y}Cr=-)1H{_*`^knAqh>g9BkS7*f1 zwaZAh_xL=)9KkRCp>!sac)!;Ux+lG!G>x4XQIwza`o1-e4p*YeEhVq)`>JUU-bxu% z(Jy!HM~mnRW+~RW?~Y|`)y<zU}H!YFto(KWYnat=;|deZsJRkH2(H z`!@wPAM}(4z>&EK;5@;1{$Obika(1ysqL{9I(n8EV}C2lx51AIHKW~IqfJOLbK;fM zc7D;aVp;8p@40854cP06wS%_jjj@xCoZ>_w--X?UUvtYAh)o90FQ&dCKi%CW96O=; zs|ylaQwYa?%|USPOlzq4IaTZoXMY+gbf_A%HEE3xH{3q^=gB@TJ{olHw&XOBh|f4y zV-9flyZHl0S7K155orH~U*yU{9&AlIvwt#@$$Wz>5|i3F52I!FvpvI5bPQ9)U?#bQ+XtmkPtAy! z4}XZOezMGy{(r8xC4Z^(U(24jWxiNdT17ISHN5UW;@&HNGb75pi@I<%Or%=j{HfM~ z?<@?nU@L^%JrF8PxpfLZF~BUxFQ*bjr;8Dp_KU~br}ZX!3a9nOc!~n4W2|A2lajSh zm$fY8vM$>(5rFwwxH^zfw(9IQd&ZBaxTrP^0wiqCC!_H@v`|bn$M`OB>wwEGtY!Tg z@plRI;C~cpY!hM@jUOsUh$jd+nv}P-_m}#P@@Ya>s$_L9tvy6YqC2j3zwRis6w>-y zJ9J*GJU6rAs3|&}uaj7J_C_{FW1WVjTT{S!d~{{3Lg7#zF)?w4+kqSRjc@Aj>C}X_ zM+E6LGUZFcq=?d~>Se$>|xden?=bXSY)t>08*H{2vdP1IsMxLoH^(DsVq`)}% zH$j23N9om1BAT>&S7-go%8L6a<)+h zCm|o7zlyDJ-@R^)BJX9w@C6e&w`Q%)_L%>Wa(~t;6_z2ONe8AuKQ*7JV8$@AUA|PO zp7FWKB{ti{LvI7%U$I^Boxp;*AXa`4JL&C3@0DA~h2P_&n0V#sp*ld#BJt|Aj8`jh z2($ex#m$o#EcaFp^$mxc?Gupu=;>x8Q~th%4A_>TJe69Z;`<$ugutcmR<2qt&K@Vi z-Ft>1d?8Jjg*3_eh2*pg4^+RvN{&X9O;*R#2YW_6o?vXMn%3JOw%(d3+Ck7Y@4K&# zyoZHwPfktsI3NG#Sk#A)v7Ab8b& zrg~ALWm|<9?S7kkBVfgH8sfM)Ce9seVGZPOu!`5to_J_qr|sIWKl{lLKc(391*11z zl~){C`(8hBC7aj9s?&!!N@Gney`iv|064gp&B4vK3Sul3Dmqb`Xw-6Db0So=f|fK= zoKUsgi-%+eaY$_fE>9`^*A0YGBh`Y9pl_d`%@A{7=5=5DyXX|ya1-ShyaV=?v)^BR zj}VrN-I7hG>QzTRgI=YK?3U_I z!%j1$ccBN!vIonCY869Ya(No+Wf64|gyq!|LzuJMz-V5qLgn{0L-RrSQ9JeUnHLQM zX8`lOz@9DLjM!Au2d&>ZH1sih29N%e2P%ACP?@qSWiNmG8hV&fH)a%bB48-sv}O^V zA;OZv;n<;<@f$~o{nin#AI?+zru(cT;P9^G9%U4`pm<}FH>e3i37l^quyCv{j1Ru; z0@oNsxuASyx=(4Xq)i0sIi@Ef?f3`?k|&hJQG**EQh6RF+ZUR-x^KKw)Oi%;`}cPy zboso}QbC8aaoq3j(fFaK)yhBNW(hD;U$FXdMaT7ymc0;zsZ1%xmTaoEH0JGOwD#Jo ztuYdZiTNC;QyR@|+)g-Axbm>)WgM@W)s@TB?EsdmCK~2^_i3wffE0gH$#G17Ev@!Q5c1BAH0Jee}2EH(#1rNorygXtEEHl1xtCB*k0^_NA0nr z7H``rjXu*Zb2as&8&~O8%%1d`A(#P-=Za-5u7&6m$bKH#J0($p-z4SC#YOb z(+TOWsng)a?QgQ%HC3mpmrA_Es+qduL8VS*T8UU6g-ldXS)$WL3+%Ry zm>e`7bku!Zg3Pm3F_Z)C-#d#oxG*EK{09HLa5xKmR#Pzle_VZcSX0l|E+7a9Qlv{S z3W$h+^e)mYAo5d`7HKMmj`To4M0!Vx^dhK0La(9s8W1F*2I&wW)C3X|Zam*T=brEW zwVx+@_LO&4*391Xu6IebJ@5HxZJ2QNPo?Cn*_h}9(P%$Tf`4-&z@*n|vQy+D*)Lzl z*ID}IyF1>l16^XAcV%3BALDxB>9VY3g1B4`yzLFh@s1Brj)2`G&-Li=syy5|939pRm>Q9QkTaR?%AR6^~S$6o%XD zq%IBEZ<8?p+IZXttMtl}a94|%q+XY3hUou!HOu@qX=!XA3x0 z-ECcKujuwe;ch6l5PGT?#b77^K3lmBdXB3(PPq|vucmPHg5OG0g-Wmp(*K-BIr`|? zW4AsH!Ru$~y#zg-+)vuuPGUyKzA9ntnZ-;|u^!fI<$#%rmFfixyb2V7TApKNN>0I+ z0IC&^tHEK87uP+v51SHZ?pVUUXSjAIp~aj7C)6oa<1hGUQMUd;}Rd=$o1xb_#SpyBtkQZI_&HplMnE(JHa(gtG8c zDimTkJOOvwtSw39ideKh+vfMq6ZpIC4yb% zSiiZ-@r?Dw_ki;cVf~-{#L^J{XaXHj4$@T5njg8MxMxv1y{;R)H@66u1(#h?l<@Tu z@HTz3sy8;bK4`Me`N88Nv;78VfQzc_WCbz9V^djy=Md~Iy{V(q;+NCYE8-Q#wYy0EETLmL=RK<* zf;sT{<;eDY zjXDz&Q^`X#`IPzYb*46C(YD@^Suf5t024lt(6=&5orDzK2fxW_bm-A{Kv>Uzl($Xa~k+-4L!IO;v|Y!nYAOBfEmPdc$Xg zHoDm5>|QM>ua2i4ldB;!2Ql1mvsdHFT4o9t4WVQJFc6k%9@S}dd5Ux!sg~p+-0v)= zVmd&FM9`=Ajy-~HszD17CsS3%+v9!5tePhok<>@tU%6cRA*VOxXxd8K$omiRm7s!+ zFTP^3)j`h=4Ksey)T@}tHjjv|s!WToODitqg05PEtmj$1jcvmgpmP4SmuR_n33EPf^mqrK7~EL& z%A*8~-3OCwC_?o;<=a%hQ5W82aOMPysasICOXKa0uiZ@iawtO=o1>n5eFXkZFu=#t zr+9FzudHqd^FX@)g9gZ@_)nj{-F>Pzr?k%|5HGr39vw;bNrG9#8;E7A(K~l~Jk|$b zO7m$=;w5c}3ukNa*ZYmv8ptOrL&!fD8hU_en1r`u(>DR4RY0 z{&4V^KmG%#l5q)j!(UgPE*4D8lJm%`_E+Qe3Tl5_2i*js9?w)-2dvs#q62JE0jm6g zAwF+zM?k#!mv25UHjwskM#Lrn+K*}`8DKo5YKGwAFj+s-;O)eM_G}SMgS#Xn%H%ld zn1=P`p^n~Z1!pf+*Kf%cbqjlHK| zf*!T6QZip-7h|m!^m-y=lvW#daCoMZQD4^s>oG>2KWI69Q*W9F`sRWg&`Ox$nm5$4 zt?t)GepiUiNRRVtkM`jZ@_5?YF1lAvJfcI|{JQv=+bb8-+_*>6wx*p2Rbim-{Fq1GuMg*- z7oLGMaGV*r54;%awHo3M(7xk7+Ut#fgc1fv7;O!E>)fiVbA-%QjulFM0Qw!lZCo;1!;bxlHI;2uGO|~BaY@7YO`>`etm638Z zoZD()W;C^6ULA91=DW{I%7!H`Cdi(-TqWJlb$U2nQygbjo|&O|*5N#+BY@fOy1s>* z#-Etf|6C~FQk2)fX|S^OXz^{p{A>iT%tItG$@jS?uVfmyCo$nU`O|blFAnlSW>e8& zXd(P<*RY6tx`fc5PP-QNGm%Gyzt!t*pX)%BJvs})N*8wOF~l;DhJ;mJVstb1KAyRy zywd3G&s(s@w3()1`prkGhS$7*>G$+JZ|_TSr!2t@m~JmrqzC2fOM3F~+Cu6Hycyp9 zY8qQIj;*KN;dYsAqG_4wJ>z|$a1P;@tG2;?>hv$xrJ)F-rRPRk4i{dZN!wtgMG|KN znP5uiI`maso&WOkMA>;qIKF#K7!3464kZ87&R!Tgk{Df%+f-IcSE)K0h4vTzoz#EKkQAjXG=_aU-W2* zBSiFjNwe(d%RrSE%=Er{JqU&BxHa^XEOTT+H~4& zBumWKc3{dsuP0<$6Y9CJ-!uhLr`~2HF{|dduBR^XVN31{4TiZ=Sw{Lw{%X(46YFC% zS?==z#rM_YmHOEFJAhGvr(GnDl&Fo5b1^B@QG#~4RbqQI{ZHE7w_3!|A{rV?7BkWh z{@@3yuF1@F`opGaoip>gr&HT&M0Zys*wLyp>JAG7nNu2c3$pZh6s$BREdP1opya$kd|fBHe;jn~xL6%uKpVQDtL^ZPog9kx7GS03 zWQ*VfQg@{B4J_vX%|C|e1t#;GJ3K_1wk7Y?htL_$>7(Mu6LWJgTMWA!808XBqKM<( zW@(&Lm^&lc%e7<0UA>t4-2Pls9v8PsKRs};+s^c;ZmP}8h^^WV6vQETAA9C*fezl5 zRv*-DWT-XA*Z2Qi!n~|+Ejkfs=WdDoww!e8RZ-EYy1xB;af(#sJ*R@V@Q-)f@!~Bp z`Qe+Q#GeK61?u9AG|O7A!-MC|s+k3MK4o7MAIVZQ5scCzJ_qAOH!`dS)=#G7*FW$i z@5&O410l{G%mEYjhaXSLd!R7S4c4kx=LJty^WLg|oCm^rdX=K>R%scW)|eUIi{3Ky zdpCCfcH(!TCa&gWx@NIUHwRbnuZsr4zG+1^+pav68{eCfkrUp12e1x*d{i|spdi(0 z>Mq79oZ$HY^dURE0_WS+0}%aOV4pPc!L7f=`D}zlQ!13NT)MTbl9Yj2pJ85U-$!k$ z*(*UF89N`gCVxuu;_)3o%WgqA0N2ufFncO`Jmj@rpD!AEz9t7i%`^NeoBr_220QE; z%Vjl@=VNtNnF2h7;%yQ8w93|Ga;US}qn*jV#4Rtf$kIiPNz+qH~c~^p&B%0;2m|y^p9P=)i{z4T}TFUqqt{ks+i(4lBfbZK7j0{{*d(Xv3xaRK`~RT# z(Q41VkzN`$9ldthvRsSrRoo_(>{aYxOU67;5XoA<3hL(;@Z`Lgx3}ZGl{VaiTZ};# z;4^E>UHLKpr_fbj!g(ENaZo&WDh4fbiP*EZZQ#m z0FikP^!^{d6>>f-8i0Kb#J4k38L?NsglR>qhRliOq5A8)R4Rf?)|FI1W()7;>$H!J^ zgoY1lW-nX{T%@%&d2zF0i9zd~?@)mza;|C&k&%KMbG2Mjo34G?Ib9ptR!d9_s4@=l z(g1xxNxIb-qctvbUwn5l2!i5X5}3ZPbzkUg@QVtW#MzIDZN8@6&~#te745vclhtShsG`KOXHB$^VC=Ei zgC28+vvGBy zz3<&7Zp{5I0ic_sDzL!K=Gb0jLX_-*jd8wj3o9>jns}4mSOfdXm$b-6dH(iO?ptUC zMpzdm4+z$omPoysbig1omdvHw;VS>_Wu4i>+a>nrH$4hcJ~p{tqe$;nKUr6073;nU zIqABvdvZWooy^|Zd|!y{p%@!&&{KQsVUJ~lYHMEWHwl-<%6u9U%jBblaM{{<7Ul)B zHuNmT?>fdU8)Zf6)Hp`)uYGgjZSivHJUCfA_nSi!V)O1&aJC@l0+w3>7rd%AC=qW# z7V)cmeOK#^*6$>2t$bm&z_`FyXgx=!J=(9TbjUiE;~J+%VI^+n#9uR&h0MnqCp|Vd zN*rUGF@q&8Ev?tlQEDD`?Q_=;Gm0?&8hdbs%NWUv;h|g97VHjy=}b4*Mhwa*mHk>i z`#x|2a^dH6?W)ka;cGGfyC)+GI@j5)Gy3ZqAg!l8s>xS^a$2!%M*lF1yn*dGe1z}H zX=~nYE8a6w_pz#blgLK!_qyud3N&E3XO1n%3%0Qy9=m_|^fRl&LJ3KA-30teYXIV= zH_~%)6Pit96Rq1hw9mGlX<6sC5W^h-8k9U#S%jWhD89@i`J-;qDl0)`yggkvkD8`h zo5obSl05gUz4)qQ;>03cj7J`|CKq7u8z=e88dOK23ro=rh(smGhQ^bo+A-5}n--h1 zb6;!|R6ah>ttaBWy2EBf7a_x)Ln~oav&M#>l5_9XcTBVg2YJWvDisJqxUN5;dXr4% zHyMi9^P^^(28wbHBYfOpNgAnuRXpBE`?^m!T|m#9*{3^KszX*{)UREExt5+*y1o^R zO8R&fR%JHE?(CZMK&>e#_<&I7n`7HX=;*W$MRFv!+h-iT*Id88{G)E<$O_<9iu`u| z&!bE$RR0fy=81LEN7%@>xcO`ujYY-w;g>CM4d1v;mH=PTFeA&Dg~_UZ943Kv4O-5t z%4=EbFk{g7QbO#RWy_~I<33uqre2cU^IAa2Fx72_PP3QR`6u%WBJ~^wb+HG(PvSG8 znp*A$vu~uF)_n9pyajly;fGV6G__sR@^ZQ1l*~sb7_@j5T$-&T;I0WR75vS_YLXLc zs0MLw-9{}vQS-BQ7BSw%59yz%VHs>V5GuZSl*>f6Yr4HXDY%I6QzPQ0K>V&)rT)dd zXnfJ1?(C;yKU*WWB0CdvJZtr(S8u)Xaz#b_j?eA)vffFLV>**v_i6v4CEZRc6TG|% zzhl@o8z+hJZ+CMC*+6C#JwZHgKXg!Is`gQ1;;)r~wol{| zQk858nfJQqFV4*NOTQBz--uu&KB(361QiYyZ8M1EtMh~_8HP%fw_Syo3ytJ3au^vqga{7F9M4GgA?m5ad5t@V&569ECrq- za`Ma?UUaSI+>;$2l^ntW^nrc&4RL_R|`8J4Dq}!)G0ke7pm5ZMjHswRA z$l>5WDbnkv!Lvng-hg?epXQZ&4EwkC~o76g|=4`(bPG>pq=PczGr`p-RPU=N@NTI^_~C$R~go=$AeyIcBOF zSrSdd7$#!`B&kec((@gpov)5ujoY|}IIsu+1#Pk>_51rmFukp-Qs)m%Pc1H`@u)u83hpvwnF9rT6PhoPK8+48P=DZrQzntB8M-w?a znynsm=XWlBpB1gortpDxjuEjpjDE0|Ar`#_)Ou{QEI*gJn=`~Vm8@Eh(Fp(W z{>3AWd(|*#gUIL&J|ut2jP-5xvtAeO=Ok7i6)p@V3DgN|d2!(zG1unGJWe9!bBlV~ z2VBsqkYn2+?ee-si(UplXW}*gwkTkpmUsPWaM#vnh0>93H&XxPlUwzg!kj3+6JKAH zr#H&N{NG#v%k~yuXo&GI?SnUg9zkX$6;a-jmNc5H(sHxrHPEPVNk9OsHQD-uFO}?o z2{OC7P-Yi-jhXAy+pNHp5hpJ*a8;mgnlth0h3mk*Gk(IcsWSV0SA!{I4bi?J<5+N6 zAT83>5-tZzwLdxN8-o5bL913aW~kpM zzd>l3ml@zgQ)!p&qel>XX_H)=K}sFf4}HW>N50K75lt;f7eeFWZUXTQk$mKe!%doV z`3;PlMD9bD_G#-(#)JL=X;447Qfa7o|0isbeJ#x_Y+PgudByJ1T@ z*4o2h7d1)KbtN?;avWNApRdV})Yx_gtsGnSDLAalD2$84PBnq$r6 zTBQucHhnn}Ym{K|X8`*?sJoY#%2(Ih@CL3Axto?FNZhN788kqHg3q!h3tp7xw99<% z2#}i^{KRjY6n-L9n`{+HvRtJ$iu8=5(u#_jnjCn%JyQ|WR$G+9W$r1-;PtNbuBl~T zW1BUz)3GC!UnQ->$}ocT%mM6=p8iHpz49z z%b5jsd9tBDwy!HNs*yx-hO<1vD6elDHwUY$(mbR2pMZ01z6Hrf$fXtyh0DI!-41AW zv(`r`B?rx56qnypKz8PPKFY=9922;pWiXzYEpVLq!6XRT(?duL7X1t$uc&rzJ%Fxx zGBxUTMm60$$Ee_UTqJ3hE)`Z)2r|2evs(o8!|uPx=Y}iXI<9%m>{-x04ePzk!q%c7 zHti!<@1v;Y>q*XlFjaMc5aTzDk340~d^Sguw}-o$m0WqvRKKPElNru;)+iYWOmWZu z*W0*QGYjny*H*O)Pd~Kv+nxo6!~kEsUV^iOdjPbSjmrJ4kDEa2J2^x{YgUY2{o&KI z@u0*6zV?BnEENf&HPh-w#N|}znXKE4Rx*Q1X3?RRMMJ_7QbuL^J^#)CA#%s*DB7CL zvOd4j_XHD-hS4@!=Y1$NZ2YQ0J}0|-`{nTuZZ(P^e(Kww#k$pVeIx06UsZ8+R!cU% z6}EAVFKopo(JgsbF{}1v3wJ|hUmRX@n9N2*CB7f7bW3DNiTvL4s}{(@Zsv2by&GSg zzXM!wjp&VNv$le(JYU>tuMZ>bK}#RwB?;Fs1N7Ugb)(|B{zN0(K`Al=OUeusx3iO7 zYai8|Qbvru965bw(^tF^bNmi)e9&9}CB*)*zw|<_Y0w*ZZNu8K>&_4)S$9%#Ru*z8 zMGowy+W>5{@pyu24zf;gkM%cOf8SlnrIKIwUP+D-QRRv>Y=My90khv`GB@)h1K)#| zY!3np0_VsQ=pv3UpYC4yo-pq3(8f-6dp?~i>+JUxXO8;!HA`;0nbjyVwLfczx)mFyWY#~>@-|%OI9pyxrR9Bg$9Zlr zEnbgvbul`0f`{h_lBXi12GWdb^r2E&Z=G77RW@@+u||EqQN@w=KJ=uu(IyTNyjp2z zLj2V*foUoUuKOzJGRV4)?>$!#^Z+CVrAajjV5Ja9&p7<=(ig<(l6f6=E`kd5YzFZ} z>*wQs%@6D|y_~1ifrli|VdKHR=0jog;Ma18kIx#7e*0ps`@mX|P?_=Q+Gp(7pKV}< zh4Kq4dJ;eV7UO-G{i;~$nl_EEt-$(14#8JzjYil?(x^2{vKj6R=61R=Okpvp?Z8v|DO+0EW{LvgLu=+E)02IHvRc29p;{es5R$Raedx1 ztPj{LXVqzu<4ps;yA3gGU8a;N*!4JLz5~)@gAM?Cy7p)uS)lK>52S0nOFw{Vh15=( zs9Vic4oe}m=O$ku6C3paW5TWlEjwOgEiHN*BR2>{oziUIY;vv+O-+MJOY zZq3h+C*v0sj3{l?wkR{5^0wwTTkCvEeGv$kJF4AjkhcR{t7D6Oc1q{m0aE_S&7q-N zg>f*SnI1>4g$)9FnQI`w(hVu=+)~%p^TsEXb2F-q4q@bxcl)`Z_H6Q~3(;#ed$8oa7e0FK^yr3>yqo=#^*h98 zxmcAR@qR^|mhI)1cL@aJSIsX7o6T>$?4nQbaqj}RHNk?R9p{yzxcL|mlAL)WVSr2O z(>Xw+_fY3&Jd*3dYxa{CyUf)gK5^Nuk6KY-maEy(nBcBt8V&leO_>1YJB2#v-}jk! zx5c!R=Au4}fvz7^P3Sx>?slAfQ7&~f0hs<3kt%OrJ+N`U|7~+7R!xyt&M8?-ey^)) zfN`!txoiEt@$NAtfotBb_r`8RkF3W}t#3jwc}^v}hvy8_=CY`h2!2;CuWBo;H$^kX zS&+lqvW*!iS&90IJF5xUr%t?mW|#p??=-*WkD|ROt6^AMljdD#MemVKpcd=4Dv!*j z}e z-u39#ZGC;0$TtR+lQHbM&%VTNbIi;G9-Z`G1iSQWpxz0(7+YS1-T7lU4~1|flpRdx z;bHB`&uf8P=5ZKM4yi&eMY~Aa6^9dfbB#=LCs6TT3xvH;=iKpqP`vSe$L*S9fp3!V zLKEa#1m|2Wn^!7xP3xkd*Vws`kfWT8d+QO(r87Hpn7_5w|CLmrqFf`yy42;#;{K0C zuMetO+^O83VpF%8KWjJ&U|4G-6rJ&s-MMpPC|cosJeMCDi&Ca!u&C%h6CH>i z*Im{Q_dQ6#j+-D6QPIl@qbsUIK%bI4@{6QJsp9I*nL_^-#pw^#_KQl>DLFJ@aU-=~ zG{+UOTFs>QHUmLI&)d&alcnMfVn*+zDav?VcCfH-L-{gqQ{U;rqu7OY6+#=6UQPJ8<67;F-zWgH+WvtQO zj9wZhywiHq+`}gw3OFgerwtBn)4=@A^UgG?dx$9hIn_vIYlk(k#Z7H3D5|7BJt{EZlP89l20nHvFU5@bV#UW&FA*AD6D;E{Ii}auN(TvO zrujp7g-u-GI<+MD~|PG|9xu7m#ok4WR)=bAWX{;xQB(fc*rYK>xd-~pk9Aj#ra z>KMpGdbrxEig1LA5z}kqi=mxFvq9Qfy)Fk~<@@HDCcj4MBa8-a6fgufgVw6?);?J> zsF=n386j4ZK&91d{k%S|m-@+JhH33t!4>JP3k_K-`akbwN|w%;l2hs?qVHkL16PW6 zZYhh1@Op01elY2ARad8qL-O2LE?DLZhU)FAl18spISgq$S6XhIGu{DjXZ23 zvu~;MM9x;2!q7GUDPUbeB$TFY?vjdA-fCyA9pHEaG&1~=&ofFFk`%wV=irftKd+C_ zz3eC+6>WY^88(jhz`Rl+NATM($kzuvwwC@h-UJ$%+z2ihWkrFZxp3m>~Y zm~Y&YHj=F5RBGpdc}ULviW}tA`t$8v1VZCWj_hMQ^$c#}B((-}7T^J4!4BEU^n$i@z(=}1MYmL@N3J2O+E&_5=p`dRYNhHk(P4B?T zc(?jB&4qau@sy3(CKlIZnz4F+U$^Crxvn-M4z3qoyoEypo1IvNp zx-0K1DEeTxNiuy5rd{459OJ**ma`&@%Q!vj?(8np85 zAk+0KfJ*w|%_e301YDstq&Nq6b@N!*xmeJtTi;j^2;F)c^&~4D zKiL=kD865Hs1CV~ewhb#(X84Ez-)^Oz+63b$MWXcyWt!R{d*?Yv8CQ+cO8Iwoo9h| z)T9c4;0;Ob`;@)boTyE+q}_18foRZO6p3l4VQg5GbK+y&JUT)jrQ-?A}-jv zDuRZYAMI!~*amT2!s4#&E!-F@;=FfWYAIW?F7|YE@Llq5bKMmQW<0jq}yV z^+aimuPR%@x;eT%9qtISf236rsFJ7nY^+bf&ItkIV!Vxx`lAURVGZWT+{9S!HJJo6 z^wA3Nl$j|0Y5g5!DK~XRP-blzxP#5dXx#R^KKqIe6J4l?gQ?TO#Hr@)XVWNq9sUIC zQY1cx8L+>Du~6&#JSCsprWeoAsN7dGq^bts5k5D#eDGW?O^6n2b3d%V-;*;VWMalG zIa~RImF!xK-JK5@yL`g)*{(B5ONWVZTd($`yt{L|N(nM6-Hl0xmX#cRMGJ$HvdK(t ztb{TY+SzB76iL#{n-S;dZOQEK3d8R9DZppTh-!o~lj>gYaV})W*+O58HJ=$ox39Kk zq2{i5l^G*u;Bm`6FycO`=XFmA_7P5gN2`IxXIK%~ej*s7*@6Y5_)^}QL<-2Wqm6Q{ zN1Bve55Nw_$+u&22|a_x!8h2ht5EQJFN(!tiBiHVBvXM(v}V&|5;_0vF3F1nr6%%^ zk7tpaTN!roI0~Dppc7E$hKxF?om^3IPYn7t+LW;pMD!j2V_OeQvBJ3;;BfGk5~Gn1 zDzbHX(<92yumt~1aYy280`H}PH`DL4D(1B#=QoAtL6;TXIz=#530kG140^tpw}@J_S!&v! zOD^DiuDMi`VXsvvNaJAHPrrc|+V7Tx!M#aF-ba*N%}P$SH?b?SKu+Rt zlms!pm4QP~>{EP3`k_U;?1vN3$N zum;4O)mOqW;w+V zE%i3ZUWM$uTE7*%sF-bQ0KjPCPsdHqr-DSLedh?^#@ZGcV}IMp4F~MR;YT_cAJ6;n z&&D7os&0W#`V*5Y2&2^dV^->?WfVKrW9YDsw<7t!%2q4i2D3wLU~|Tmi1$UO=6Sme z)|R{~c|j86)|WR*AD4S|kvWQas`tSV7rYF?-X?v8tXECa7)KFPE}SAjNx=iC(S_xr zy4c}9MFjmBws~N#oK+xOyv4_UiV~$I@75j-sfK=fzO+M~;VI*#*ChQ5)Hc>?W_SIF zU1ob6Mmu-d#^L#bSIK80A}%;NIDpx4uK%cR^{032WdSi}uGk>b!|_Mr^nD%)v#&=| zkcUnYRnF)N`>|Gpdr^6%@7`pqMm5T((zBrFG0~(^<$Y}Kc!!p4GHc$8j;*{ay;`=z z6KC91obtU}+s7g?o})L;^4lDVVr(Vx4|A2mJ6>olMiyR5I zQLFmHOj`aSQd`73@ePkw=uApR7+rF14T!9hz zJ@AS6E&bafian1I6Y<>B^SSxLWwp zt+x2ak?^aBKx^=v_$d4&ajV{S&wtCZ(;>OZ!hAN)$~LJPvm9JtFFsc`gK67{zi5x{ z7)~rm?=@vtdhzK*OX^v5NQ;Cz;p-7z$el%*j*q&HmP({~uhrzV(NJ3S&x7hvy4p6Q z%a{L5FZw=9m@abxXvrL^Z5gP2Jr`RUH%XQ?Qr)yRf<5GX(dB$CSj}3^ZhZZT6&|l) z9Q0&%H`uzoz$A2LDn^0pbhK%q4~yrT);e;12Fjc1gEz#jetnDD$a23&;-gZH`b1@= zcNYI)9QiyHt^lh)vl>Pl=ST8w5{)!FULnS;3l0 z(Kzg6aN|U0>0jW2)Tp-!mm;B8o6;Qe=!UF^z43Wtdig(EPjqsi;-PdRGAD6uI@kId zkAGT6cDH6r)6?-dW`BZ$OtUamr!3bzeJ~5*tBfiTIAV7v=fORM4{y4%BvUA0EPeNV zH*LIl=z`ILLFK7W%T_pFJ=MsS_9L7(%hQpMi4uA$F?dHW)cbHE`d z*&Ff4PMyZ+sm~f#d2M-Z-9&x^eS*K=?5V#zFNRj#=Co?&F6#_2dRhN!#y-fmlg!&%)J^! zq^4+2P0p+ADf3Kvkw}bGSVnfZ4riGR=pyi{+`aqb4B59|7IvJ;4|>)LP%}}{hK6-W z3EkDyo`j1hI@GoaJ=B|W947fxs2DxoTXm1yTFo{h#W7zvWZ`9%1`P)r-?ktB{C3-F znAS};UDMQeETL)7q$d0bV>5|J6kVv6^tMwcypwmVLQPZ7m7!C4j)H7bj;MHb1X*Aq zQvKnW$d0SY1?;mGn{W{uy@1-9?_8Z+4*Y|keS*+v44VEf3#+gJHFebI+E!%UwYFf6acyMLpt6wyXX`TS;M~`})pzY*uz z1@oIY!oyvC}`BvwO4bSna0Hz4|ISX3uZFNxyd*YqLC-t{-!q zkAr^>1CU6v ziuK3LF1s+pO4^AewhZ^t_2$#XK3Wn#nn$XkVr~L(Ny@Gu=n+u`qM#PYRCL6UwHKE5 zPDb8Xuz0(uH&~LKeyUVpKuvkYVZ@(qm#ppf*Tnt7864X;*t9RqR})KJuSsxGw1#3E(-m9M>NR}_kT=RXDLQF zpScJ~=*>Q*^YRT3J^33A`k&UAsAR$^f@S^@qyn2>v{Cb@f*I}wV}`-$K$ao^JI)^a zUnOZnWgxU|^y1yQ%40l@RBk%s)we@i;{f;l+baK6?tgsrEh>=*TF$aQ2 z5*q%O`Djv8UMpDfeNaI@? zdWyz?7fGm#!1vLvmm?l*s_>|K_`{_L(dSwhTV;nUp?Hlo@bg#d3TpeT`WqiQ&EvMJ z2>+QR=qK&7-KT_^B6H6@Uyv?wGJc)-IqKhB0NNIOlVD)l*+;O6 ziJA=aFORMz20LQq;Cc;FB7{K7%lY|IFp=TT?o{}+M*03@_5XlC#&n;O4#^g)g*dGl zrIk3X7CGanIZ?q3H+wVwKdf|?dRb3>K?*j4o4F|kf?RG%fvrU4xIFP0LGaOP8EbwD z^|$tgLPvpt$qV>mlYmM*`l<5wsI`*29?sXZy87h6;<;@!EVSwrIx|GiM~cnwqvdFp zJtUlp;k6n9>i9lY;55`S^hG|$I~t3>7v(srm#;j&eo{^Pf4{w>iRWP9T+^bW7Ya~c zO${_@mt+4)&wZ{$skPG*P&PgZoKz^VfBqd;@!IT!#r+|wOtsxOUn|<@#J=#z?SJZh zN0a-CGT024i9Uboa@9yn%#!*2zwcOt(n?TJyszk*p#4PLW=Rh%c-Dwg2G?C--Y;!3 zyUOxdO)H6Kvm_J}7FGMXTm^9DER z-q~nx9f3T0KPH;<>vrv8GEg$vTblbl%U$$sw2+5a4vyFZ)L>_SHU>+~t7QYk@37lZ zxvzV~oS6JGCHvoCp2DaC;9*eeLV{9|@&$|#6DXnSbJM-{f(-T28T&YT>3p%3@*X8; z`3;II68Hkn;MIVSF14FAh)Z9Ygv#<1U=pi-ZI?=<{z3(PvGnZj2Xpl>eSqU@u02XY zU(xnb@T#^@s!pi}#ixN&O0hbIKuw%T=x?|RdZI#GYWxa$?0+vHn^1}el==kPG-rjE zABCEq{eyaQ0o&g#AOk1>4Y68rSo;Pk{#vHW|6VTj-rY0WkY{l4t3egv66pS_2U33+ zyRIwr9Y08LX6zrIUyA9cT++1ZjYs~izaw4B-Jjdy4~>a1eo6}@ z4>v(7f5|MDV={}EBDN_{tFNu*Pw=dd@=rl<-a#7jgY?WtlbV@51FPDr23o1b3YQZuyDqP(W{o&H|$W$28+el=B0CA?v;27HRh<{MvU9`ve( zE@0Iemxs`#zfJzz;+Gh&d?K*7g4J|ihz}G{+_)5v4VtHaQ)>2(<_b-p*NqqdT+Vp6 zbXWUPMASix`T?tt0CaBaYX^ZQ|6g zaQ&(+@_tk1FTnoLQMTz|eP+lFX%$nvmVi9r z0yyJ7++~lTdEvRN(166rye_E=`Rpt;$D}w3ZS?{Rcts;%52s&r=88a#3&}>5dq4Dm z|K$Pj!Fh8eTB_o4IuQCY!NYerS@d;k!D?JQ&WjBW^Ay=DW<`Om-}5Ckw550d2u$U+T~1N=Rg~0 z^cfp>JrFToh8k#EOj_h=pbDpIOhcYkAd0(oZdsc!=qB9k5S*63eQ*C&+;3H9OFPcCDUUzX0NH|~<#&JmG{;6&P5=B%qz}PUpch{( z?Oa*<`tijWIwlV;L$AB0e5q$D%O%)Pi=cBlb}r}Vx3RDI*O78P)rPWN=BE@otm{V6 zc@7wrt)E?wR(dUGc;lk&7AlA`INBs&(rLzoop}5V%G^-dka9Fek2DkqvNIQqar2lhKE&q|ayvOke#Cv_ubaW$N`&yFd|yB>fqY~bbm2-I zfIL$ho?FbEM8sbM?zo~zDQecDZA_IP}9fd^Y^; zZ3Ed@AkdJor>ZC@;J5j6q1T@&!aC^A5a7R4P#d!MTxXg!Sm6&nI9xyxxGY|ZgcvVkMa(RcD@Qi=&iy+ ztgmY=SGa$1v12N$2umsyz@`A%td-%c1{h70(kqw0E`iy!14{Gf>meVG@2ak#C!KfV zzr2^gckL5XugkdSqqP6sqL zXi&c_E-t;z*Zu20#L52$CMX}m3$NnZrX@KVqCg?=?jZ5dX=9hX8a}5Hp>Cx)rasi; zwRkny!Mw3fCA#rYD&lJG_A_E>6%(r&_;LzIq#kM^SQ-#NIM)eJhBsS$m{!)2-MA;@ z1Xux_?4X^(J4AUB?=YPOa<=N6&zQWSnH9gZ|?S2c~7ltXRnM5K^6 zz?C?T93-6OQYD)-<-=GR%X+T%GlffVyBlcZh_|QlS@MDrIhIoU&#&x27|3z^zk)x| z@aoX0=O3GkSO-|Bo%Krz;jUa+<|yiUMz5+%HyGa^Zok@6UBQ+0D;f{ zIhIM_$JmZ8W$8v6)ss{Ai^jbS_>Rf0gblX|(ccPHszFlUjI8K*LgS7)c!1-%s_Qlu z!27So)%^|4FJI@I+7c8KI*xUozbNb}avA0RBwx4W2Nk_K!5^Qg+uHK_En(gN{BViu1J`;fTZ@$P+?WUc&=kBT4t+4}e?Tj&iq7-vrd0<8-&ZS6E%DMl!j?eBCi;uR^r1U-Dh zmO3_n>HG2ZcVPO@lea$ba~%cBkE_{xo)hYCC?V*{?1!DrODXfZe{rzCGLXd*K+?F- z(CZ#g;1@~fR(SEx{?Dont$Z0-*&GL{eR>)ymd71%^AIYl!(ghcwqMCQH?&1&YM7xLbu+hU|(g!swa=`gp?5+maZ?C3fkV!d1ngl{$#?JqfyIoDnQdm9KoFi zGeLt0>m8pR1JuXgha2Ruv#iSqarj6PPz%~9v9bK z{lOseQ3D!?Az#DxY7+$eP0l+I{O*Sm^0Xzx~dTXZ@4V{y;_>Z`FGK*qh^Y z?y3+4>;&j?oUlPOjh|Ef+AWhYg{dAl>^$v1NgK}$2247-Y6MNK0p!I=y_M>U{dEy_ zqPlOW@2&l}kW`29(hYj8b4-K(?-i?FZu92>TK!081F+Q8NQlDh+^uJ{v5arUovFXC zRx!%)tKZae74!s~#7nvB-H9CZ->?5T!-9C<;#D$N{&!9PP63H{=OGY0zAzJ^z^FlB z3=+{&KlUQf`;yUoM-!|aN}Hq!X+Zd5kIWtB+rCQE8A4V#b97-W)A?M?A zW`7LTRro4S?pRkVm!0MTc3F`)W4Vvu&@--?QZ|coqi@!KcX+PY zAi#!mAFD8=`7e{1uqGfLm0l!;?3&bP%1fI*e{m2DeP*c2oHgXiGpG*G7?T_nu*)5H z+)kZ$j1Bn^UNf&EcyP?xE3#;XeE!M|H8RN{louX2Y*=JoON`J29+ z=jA$?e<0RbcVIrg;Jr7W7;o6F%;egybf9OgPyBjdvN7}c{u(k}sLWZhCXkeYccUXz zYJtEb2q$1T_d-eb^~(hgf;VYjZ8P;UKQ;0H@IuJ@w30=-^VUANiv@GNA6gS?G4wBB zYHTTJtDYS5Me6*qi3}*^{#qIQ1ib8TT*^r@NJ`~(yh1@E2SgbJ;@ILn1FJv-#W)TA z8asBF1Q5Ve*T?&rf${u*JPjEr`3dLCm$ek3IL&?6ZFz6W$-gip8`bDT^6}wB@|HD+ zmn~o@}2f^TI$KTvF2UQN;w@6U{~M}A=xN@-Mq#wK3Z!rk3;ZfR^H z1;bL`+~!a^CoF|;Equ@)y>a8z`B@#lhMpW#FVBq%TZl}wsAPVr{vg`JkT^%6s|FkG zNXp}LY@*!eB;~UJ&T+nQ#`6kX5R^QUM{6>OZI@vTuf4tDy~o}8YmDU3GYCsG^@)8{#^#))PoAmgih3{?zMCdO(MioVYl-&`@p z9de}HGOYJY)2v2rd&TaZ&KKP`RiO9oU#Fr^S(E${GgNe7Zw9^(Y^cqu%G5enOZ^ME z4LpOqxgjMP#A~G{v%DlfB#D7TH?D{G4@)g*>k%$7klCFgB+FhxO%E<}3e^g9vD}zu z*122p&F(3L-|Vd#<$8;UFz!=(mv5mKpzG>@a5zN0^L5d~x1=h1Wjcr8jo*bjz_h=w zey$N9Ul?4@(u>HTf3pc-l*83_CDTpdq`7TTegwe8p(vdkEIGm2m=5AD1$r#>u`#8o z zXc@ehTP;z(H5cSF`56_WH>}>8pBQLW^Z^1{R>sp-awpPCPyp1wX!Ctm2@@)tZ$aWnKVCK-0%My zn>*m=ldtA;nW6B@G_`^ri3~sCP?@fe9iu{@ewIZ?er^51a?Hed2Jm4+WE;3zGRxhq z{l~#gnvv@){A}h_ht#TtUF`9w)n!vu3LqPh$MMK}tzbt5ew3rMDr>(!Aw%}5*8B+^ zcC7-*@~Snh3zou_uAQ$y7olmdf> z=I9yPPxo5;h^c`C6lw&o3bs|L9e17>DgS0fs%*Y0vo+byNl@K-G@yyBcynTizJaf2x47{ZUEIWPM!gDmrR$% zdjg_8Fm?n~pu;-r?s=6(^X*rryNgtw{5{LaTf*1_%NCP(;Hw?A5xC#o@b}y~FQcEf zR|fnYfYwTeV$o}Oysd1TyU|sl{wP(%yoPJbop} zl(OAtZ~r25S0o$Y3;d71)|HE^=)XYfHi?*Gv~P*`7jS`Y@MAt_yKX7j{2BUhsB{$k zN&6lX>Ql+|$cj_Ui8M z7lDu_hwlnr^m<9s7@+MP8O^xQ=R)KvMZFk{Q)0NkW`$M9q;z< zNTE3)AVVB-B)_H#eq?hZSw|9xXJ7hR|8`pG(s;4Y+qt}xYO5S{I7M?*nbO;6*78o~ z_^RC%;u=k4Y+((MhqgEA$P6#F-6fpp#+!&FWZj2tx3L}_YxOtmhiwv5VsqhP2?0m+ zpc*6vW@2RQeV3T7s)DPhM%C)41kb z^X;j9W|c<|)hQgJ?{3)Q6QN(pW`9R{WlrjN0pd@N#dPG&zTb@3fywgDkrMkWZ5rh+ zx(TRN2fZ#~VeE`PnVikPTog~|8MlGOcC1`d)C;>WBEi=dZC}r#hJZrMDpReRuWX}k zlT;CDWlCcV9IrKjx0%pDCBIU^39rru+jYGjLamSdjmK8Py6k$Y7cZ-KlEQ9MgKn+< zffQTQGqOFHa`J0-&2r!=jiWsFOts;3s0jGT9#bp09vtx^lube8_l7no{ELS6twYbE zGFh9+`tAq#GO6`CbZr~$2j`@8Qi|ydFq|>SN#i((^O3*6$1su}VY>6_i_t5#quIMG z;liN?{B?NRSBy=Z$`CyA zMulWcxsp|A!Srzh&~bbVB&Y0OI4wPs7qNQYovpeD;(Pz#Lv`KygNawQAfp^@EhyPw zKI9>6%-Ax(8|H%q%e$BWp3Rl1jno^}kb+h%59F-CF8Z`fLBh>#?xF)eXflhm{9v+G zO|#2=z{?>F{*%&vd^*}q+*UODWGte~((^)>ljTvj1Jj%!w2zZ~T`%2s(XbwuKazIH zAJFC8e%*Y+`+U~vRKz|T*k^YKvWIJ4*3sb$`6c_lJt)>7miha;zk;t`gvv&4{uI-y5c`b`3nwuQO}`~R!HZ6bZQ6wIm!Q^>GO{4dXFqfA8$PO!XnIUtU{ zMRO%tKu|27ae^%=01(Z{-~ISAk7UB+UfXR#IeU1csM3VmUgj*detLlBp^j(qf9Uz? zaZTTeICM{f6PjOtKJCTnREPn$R-0LZeNjOC_fOU*D=i&otNremD(*YC6g&ogLkpv- zwzi~$B7-{LlM0P8y{VL)(s3_=6Y2VX?}Q8_DwX6sC0GL*z-k92UjQn^Js-hhS(@iF z1Jr3p2TU6G8h3`I8wl{qwrXcxgpdM4dN+jD_8sN{HY`HfGW?zRj_&WqF5@hlG?tc6^EZuC!>-2i6xgs}(Roa*VowQ*Oo z3QL>ak)%|x0#=C*0@$+!HGmk$B0%5C)gwNDFjoG(95^XMi|OVRegO53@^i{pL1|JN`)oj35%NADYfK`K z;d(7`drn5}(v(TwBnRQsmAbuVEv8vbFuU%o)c7lA0l@YLOG(3O6MA8L3#gH#5LRrL zhpA;d5~w&ghrodL&W!Eoo~}sR>1}i77>Y|g%`wnYDfcY;WA?&1tkrT{Z9 zID5e&a`PU=N4$sclcyZDEnPZywhB)lbL^E?@~V6UHMrw{{?^b@8!l8khJK;a4cp5V}obkZHM-`|y&DF@t zNnZ-|_jNR?tRzm7GByZdkC->%6Nc%z%}H?y%FtC|RUXtKdXIOU9Rrg$if+1mzK4cv>XWIPqj7=_?>ZP*0ne{wz8>Vlxkbj=CuA|G zA*Zu*Jb$R{sFPW~RB$G?+Hp}wnBW>(p6X-zR7-()6-P|CkH<8hWd+o@eDJ;J^M~Vj6*Fl$ZE&FYm;9JMzUv^IA`ZF@w4`7!+G-S}o z2_SY|_~)6QouG7;1eGVqEJN6~8(qr2Gxfe?Zl+nFAjYnpm@D3<85@N{LGs78eCPGV zzW~P=|C>$;-}K9+0XbP#LqvD*Xg>8rITFjL(&GIR2Afrfqj?y7Nn*!}*;8Svk=MH= zVx$4^5bGY(CvjSB>+S0}Rg|S-?G4+$#k%beATILPBjuGV-rX%tq~m3)`#>NF#l$A` zr$%&^u?_O<$!w4T)Lzn(T59k*GDxkHENPyh?GdFDhxS50{^Dx&dW~@7^hN3UqKa4b z>||p^L1;{T!2@c%R7Z=XP1zN{J*%*o<)POOq=49Z z`1AQj4JD%FzH;67v6v<1-~L^9iJwK=s65+QmA_>7)Q73SSwd%oM$)PF(f=q$9$ope z(454cp?rQcf?fi*&(%591v0{>vC(%xm5tr<#1A$N(6E+esfaN&AAxQCv8>#U?#FSB zv*K4fxTFLw>1NoU#c-R4i2h_=v&6qq`!VAHJ#tWq_U-y(nZ0(MKfQ8eE4hRoxV&H} z_Z`okntw=j?TW0n7Q;6-JYbj4xMMD1{_#XVfiI0I^uQVAS?<4mTbrBUIxFArQHQC0 z@VREu`9N}|khXgmd^-bvQYP!=aGFuhC}f+FC-388BvPY3C_^=rA_Ib&FlsHsqw?U&VMN4Q6st0O>ah+psUc6H<3XtjhtQ+KdkLN+$s7r?^ zt$1Gr(61*&4%VXrN;UNKtrkBJwoWRu8aMYp&-!1joi&}i#fy8bUhj8c3-fshX2pFF z&ux>Ad2sGXL`NE+T=T64(b#=kJG1SU^%WKS%XGblYfwYiz4N1r_OYmq6DvGVHco*2 z*19!D6IdlVy`v~C2x7%yPLJAO{%5P$)x~7|%i}V@kh)lpViLO_#8(AdzY*Lq%ir?< zUV!nsC+H<`L?aY|h21g=G4!|Ke1vPZ<-@;*pyx4K^%}C6(X(_)vA^61`zH#RFXLcG zfaAJpogWQ3f62{?VY zJZe207u16%o(nvIBJ|Qt)qEOr6wok0ee3;KZxvY-r(U}%E~td!>}SOP$$3HEF6d}z zr%*#4;&RTZw-DFdLSsB#$F?4RJ9;{S|{U)pj+WPZts__3WXy!pLxY|7B*GrNn0AY zG){E;zCTe}2BjJ>)9R>cdPVVJ;Fhpr9sR?L`v(~Y#5yjj9iQL&HXI@ePx}pvq1Pn$ zDyOUeQ5IbuK*BB8*B_mX)Ukew+WY5o%A^wQ z|4@>6HlaGqN0YyCe)Ck|c@T(C$VGI@w!JTXaa1%FD0w_j)iGJ5U*Brdg3qO92NoWR zGlw&~f~7y<>XhEB_1}7k3`-9Z_{>bfOa3~CF#xI_^3WJp?uwz%>ah%A5I^{&gYfoG z8|R=7oIZe2dkx^|E)Dc>6%|AZ4w8Z@qbhxpY_m1G#VsKei@ecT$+nM1b_XVPF`PU(zotR&1U^O$+>MRoC}LHq zLFrdK7)!}D3)#?4?0geP14^|aMKf@MeryK;*1i$m4Ih%3lztKy^vvMDR}CxJEqviP zg0%N0ezp5c^fFN0oxd;8-yX879gnPf`K?~~+HH}ML=6|iu=TnCU58WJFNnTPo8&_7 z@+T;*s+uYjVi7Q2f}*|bsOy~X%WQTicFf%d6v8`F{Hs1 z%%;J9?O|h9Kqj+yo6W=+6cL5|6`T0^Mx3!;*Dr0)uU9B``@RBtaKohlRqyUsoqjW_ z*zE~Kg)(d6K;8_wm-RBwR_HrDBj2_`Js3@7XP3b@LXH$zFr{S~*}!WDSdvZB;mr|_ zmeoSnWANwBAX?<5$H|31htQ2b%%eRyW|bV4$Lim4&pomna-<0~+qX=b7-YlV5GaMz zO=d2xiMO_Zw)wMj1WnH!xlk9A;dDfKW*wi4d9_}EC3_O5tK`Iy)xC)7^v8*dHm`gR zkEdb>J_Ab6h8cupuQu164=&4(BR4+_D{nShH>9D@;tiSZ26)6g&X_mPK;6xKw?Wzf ze=#7t-I9pD(ih+Q?A$0pY|BFz%RlRSYiV0idv-zj7#k)&+pt8*L)Fom>eEA0ATlw;9lh~IUomAhFyJvrXz}J<^Go8McE0DvRpZI&^3LkUq{PA5- z)!6aR)prN?7ihN)D)e`&BZQO>&%JE?bBhk-N^tyFjWvDD0QXyYwMUpdHah3+X=grd z;5l+sa|Ly8%qXcxyKSNoPJp}BjWBEnW(hFs!cO__z2|O;)9=>XuTX> zEzPVdTE6{c{P2=tI+j|nG={vPHv02=$@QpHdv!wP##qhRywJIp5WD4DMc0xwN2Mku zHV5Nt-;P#c>ie42pL5`&N&=)3<@%c_1)&f0`jtme< zU(2{c&I47ib=T^VXhL8eJRYjth&LUWNH-ufrk&Ce(4dV zIkH{`e8oPt>$+X${NpOw{=XSB5A{bCgaP}vVO5#94-rJkld7!k0krM9azvLNfydzn zMMDWIKlLWxSI$`t3!x3GhKeq)jkryCVE0W#3)Bx0NG}9lrM9VjVnkf*crmSUV@^(l z|JS7(CPNBqwOFw`TK8t141Kkxu%oIv#hVgPlVn!~@)=fAT4sKx8TGJ{^=N8M#K^W2SIncM6RiYUb$?VY2)5euDrN$)};drcKf?#-@xFfmvapz-Cke; za$&1Bb-Ckn9+^~G-4F&Tb6SZVb73DbII?KJ>EWi3v^~+cwIH)p;_t0hvDq9@Zy7Oo zmd1U}H~e1HC39=iMUk%B=$~IO#9qZ6{M2|h^&?G-Hdj3w73>3lx2Dp+1y`7;;H}F8 z4cGhi-D_5L2U|D(F2tUjEk3HAT02$bUUxG8ptA^ib3W~n-EtBtQGGAh$)`PB@S%L& z?goK3jv=IktH)hegZB2ngT8vt+Mn>rw5?l`%z0l}I*QkGHFx`!R-EtPCz~+~FO4?& z$+>2|@zli)7ic8G^R!5lLSD5VQSd};A{t`z5b)t;1RNba9IW8o8s~yPzUJ`z5PxIR z-TIu`WGG#@0Z$jrS6ZMZIrb~)yQltX?Y}#r+ zsu&jFE>=sBhyZ>HIo%^T{KwZO-+myMK`kSUxMO@jU3y1ij0l@%IZhw2%t^+#ZRO5v z_oyPYOi7^s0uOFQ2x9zO1y(XF*AJCeAD_fYh0X8hu_G`!o+^BEoFzvDi#l8XOcGgM zGMxXUf_3fGM<(tCKsV&BEV=B(mlSN?ZaZ(xL zB~CW7vrmIf1@N@#PbVqYS2YgM2q+su#&{f}sX;T@q?%_8uirT^JqNEpFBzT{y(ri4MP4orGkQ8T6S$QaQbF55`~hHYv5%t4!E zE!}ulPY!A~thSFx}A@)sj{4BV=^;x4^YXU=Fo) z(4X;pXXpGzF>cZD#g{6*mz+~Z#*b3z#=>Y&sJSz$$9|A~yNcmaP5Qw6n4gzn zkeb~>!kR-@APXe8C8~sx>nqwreyj+W+IcYXCn(w(2stY3a1;*Xayd)Q)2aScJ%~+I z_iv~9uulOUd*g^LC+8wG_)GauO87Q0c-}XfFUy5{NGYDX?n5HW{3H&5hguMFN#iE_ zZuvHQzI_87GvxyMvrPW`bGHg4X{Jqs?l1=;la$9klReaKQH~FtazmPkqU^AO49wmo=l#gY%6%5Ye67bLVvtIH?Yyy;QExO@(W0H}Ag|HTjZZs%W%iff7zMgZ?&hdINWr#Ld||s-zZx4-J0}M z4A=0+Fmz9nUpE%j6ElC)np6H~XOZQRy*zT5F7sTw9eRgVyQ}qF>m7}`EdVDr+hmgE zvLGNv1w>=CQ*Hkw$Ag}K=Yf}7D;)ftO%2va)T~w2Lm9MRn;+?%-P2Wj`dDnY{6oez z20?^gvGACa=z#b8a=s>N+?T2vpvdgRJLFb8aX)|hAXybVWVAnB{7psrhSj(EJCYOm zipCy?ZQ+g>YQ?i)_0imNo0US+(ANb4UGh*zc0*lkE-@R^UrNszS_Rr*4PK<+Hp{Fl z%QoUnRU&W%L}JB=au2dd0qJg~R?b=t=@RorAqL~*oq_>vp)Fz^+ZaUPLgLc=zUUEK zy>UMz9b0|rt_pAM-szJM_`~#|yS%4@dB|#datz#;~HP9mz2D>~fy4zr5yB4*yI`^qS+-reJM@ca15Hkna9t(?2tF>)Tx z`;=C_Ihb(bgLO{1p~FF?Lo^iZ)#P)2|kR~l4*tO-@DM`^Ty9DsX{M^yG?FtP<=8;WyoGpoC-%)> zR~H+8XbrsDP!T=(6&v=D9hLpe@q=~a_ya7VDRHrAJfS3Y6&LkxE&FPTNjsqC-MTMzk6wPLiL=~4EtM`&zH zQ+^8wnThGxO9yWCDvz#A$eHUO*vDL+l*3ihenVa7CYI=dxOb z7(TqcSrR%h%sY4*fBw0=EJ6E~_%kGqc}_>)nAy$^mHU(z5@zqg%N+i!P5X7NUNJ?E zEPxoBjSaA>jk>z%e5|&p>!sgUb%MtK5UsX@p7e3zi5s_!M7)jP;(vJmQob&xty|Mv zaeX+MTwXZpZ@xZ%D!{ZnvAo7x<(+$ZG;McVj``%IoIV_ynT)+xIfb`43gAs8*a?@k z??tfdVv(-<1fv$OJR(VwNbf@#70#Cbb2jMnT%PBT7Gu&z`K&ZBoCgcM@Eu`#8I$G$ zE4XD>!srCB3cg0Z**~&LVaus5O<4@tHIH~B@G#$9$qv|7Cv{z4?VI&(Wnc7K#dk&Q zJ%%153c|*QnFzF9k2@d>lxhw{w}^gEl)LL7YE=HC`~s;rVEb%n6@Bcp0hwTH(Vx6L z5GMWoov0dI*p6~h(o5YHY?y;<u-N2>Nfy@cN~$xL z%uZAS2Va}nUMQ{pBaJV!2olx6_%?448^dp-+jbIG;qb@2V@^Wq2EA*=hzuHj;p`6rg)o4$k&h11{P^>Y=id zm)k-LG>=*5-Xdfh0JwnanS#3nGhZjGaie+?&7&pWa?hLio+`;6?InMhaT4CoN?koM z4t!DJ(EROS^@s!+DbL0~gdevDRef;{xB6p#p#S~&aB>&f-{jps>tEtVAYJ9^cZO_* zhiyqFv?%j%?u4$*And^qKH!ft1>!H0fe&I082&RD<6j>h;Mn%f^hh@I<~Y^&=tg9a zI+*}$go-W7Nf&ag)AnbZ0)h>WgE<%8j@&U z#i#=b8%_LbwA(XlC&LkeL*VdVv#?$QKdG1emUzBrO-N3}%Oaxd!~T6jj`C9po3_ET zw&v>lCjVTMkN)h?9Jh1cFfSj5uAD2u`SSwygo!$!Pi(R0+atpPw}Q^p@DbnRDy5!B z+eY1qYUc}G$6r-X_!Gd87iI9G2=F%Z^XQ{D`qfg}KHq-%{SG4@l=xL2pEr&AHrX$&j6Sk0NIEtm|AOD#-}!^qb$$X@Yf&&k+wM*ZXf1+8%(%>rT1 zZS_QK(3EMlWDw=>`)Fc+Bd;BJk<#N0*rv@q18=+Ux_;o!*gN39oP@j-wrRdo*w|xx`TWIZvjI&SQa6vU~Z?bICi*nF89{HDoMr z5Ex9UV;*}uqAj3XXRmyCyvFwG4BK(gD(Qpnl(W_hd#;MvPOH{~wmj(ZK$<`cFeS!& zIk){Q=CFUcTty zGUeM_^}4(uIo#gT!H;cX8RECD(ch|ou7#w0*HDh?T_MQD$SiKu+h>mZ*)(dd6U*iO z(s$&%wPGWyj`AXO&i3#0Z^&ko^w?H=YOT}BD0u%OP%2V z84;2X+FicT(mHmHm<2*kG}^D^U!*)?Cd@yNip2EgeXa$eAK=7=;C1o>Uy*PU zQ5s+&`(%8}I9Wv2;KSArQfq4NJv{7NTkNe}tqfD)7;c@=3H5%fTW#@y+G%6RXzDBhv`+6WZ5d2vp2H+ zqKJm``s@+gzK2JYjp^(!74!y4({EYMKI3|u`3$_u8r@>ohA5=HGqkasjhGHpR4?aE zg!TS?WfDFzMCTb{&-Qa?MDvz(>gnA~XEQt0wUeEXtQx$yPUv$6pQ|{2%`>Fc#`9d~ zjMerA0v2a=1Q_JjXNNnE%?R?4$#EVkZ^E^CsNZ|@NwoVPh;Kj3@A6LFHsHb4Ce_q3 z_|jZivVW}=Nkd98-)gvd@ZO2)VUp47o?zk;EuAP#;9T7e((p>ohdM9tBjQrlrr+pk zjf7}=ovxc@m2UC!6qE{MjRQx=Sl_eG&0FEvJk3y&>!Wd@AO|o6bWNDc6Nx4)#C4X+ za%d}ol=gE~@3*jxOc?>(VIF?!rJ6cd+e0{yAd0sI0v;(7IX3vI4-*;cK5Bijhd>cY z!+H9mtulRA_DKRWHh$N3&DWKY9iy4(w{eLVLlgO_Bf&-(-3mrFLeON2lmz*5yi>tLybp!u^a<0b*f_PF zdpBmXi>~M1b*W#rPRyX`dIr%{yhr6ra$c}cK)BWJwj7&351f6ZfKEOZKh@B3iJBUR zzR?Y9GPQ)eKM;xIxK>}9715qwqm_8vaMLw|>Zh?QxgV=huT{zYl^(9@DnNu&{zjdE zrF&|JrgLX`lH&ZLOvBuJ%S}!F-x zmcqQzZPndxek!P^T@t897x;YoagCfiRYGr*GwD8_9oj0nghR|L-O@N(N+IkjO>PI& z>;wh6o>P3GV?T(I%F2nRDsD=Vbrfgagdy0{DE6{b2jtYcdrw9x2MC z&K6rYOORJt^aQ!_IRmcLlzSfN@2H$w&i$Na%-z`)vjsNH2ewN);Fv99QJF>VVyo%! zZ@dIQ*nt4LCY?c;-|dom$zQw1(S)PxBmN6kyR`0FGDzUnhL&VDLpFK;=rX#8Vay6- z*w0NG*e`=`66@O!>n3ObH~#6mOQrt3`>#rQvhLA4;r|ARoO$l#;Bz^3Z-cHk!*S^> zH3D36Wg!CrvA2H_Uwn3w?i#kJ+3_6naI?!fWBi)3)$d7|M2xNLL0lcCneN3;@vGOo zRk?MoG`hBOBXqaVp)%n6>|8*i>cV}opX9(vT2`TzjA!WP2od{)vtoeM@2j`Ts2QB; zrje*G5*=PY9U0#Hc1baeP3ks>U+Q#3s+ky+v#D+_*Mv@#a{VI0Wi{3r&V+@(I2dEi z)B{@Q-bUpy-W1&X&+Y}HQ+(!G%%%P-<%cQ&L(ou{jPC8tK!G%~kt<2@c0WnG6e4mU z#^G5(sx1_URpc8^qjtFum1sHJjH8LJii@LO-u~~&=ky7DTyGEgl~$A8W_3nnjQ~*= z>ZAC{t{8HsFAlHw!~rOz8`eFFC)BlRdFpv+&D>+J=2*0>+J3UaFD^CQji?cf$cEi= z{!M?J=m*-S)nna!;W=w@B>V~ubr~QRWUMU4aKwBUdN-uaWlHff>*T$*%FLa{P#q_jzX4>;Ny_u@{Gu2VC4%bxW*TX@=#NWnklUj&H05TnG%3=|D^ zvaE6TsR9%Of&@UnYNESAvVthT7Im=>S?^juYynKWuxfT~K`064@#`LZ+$pGT9ky!T z=~$3QyQ^F(m?X3GmUy-0KnP(S6y5{%E1PK3&=Gd8*V4+agZDBMeS#qO4OEZ??1<=^ zLAXm>KtVLo!7Q2Rq51)NfL9&eI*vGC+}fcVT79IzzjeQBt=JYt^#|nRK>inS6XEwY zZ{#rk`Ca&sSvL$)-$!-ehc6G11ugQR%Phws>-C@fqp-h-S|2jkid%m(-eL<5ngpPuB>))vwj{Tc*MM_HCm@JP+WQ3nPA=2$OiW$5e_8ur zQl~e`!KE`vu{Z=$uF?5Pr~Jly@h3n?@P`X~6DN8aRbBPJrLlQ2Z_pQ~&7DV-iHSij z{+WG(Co{idALnN>5MM(4V7`0}d%qCf7a{J!#S;QxNJG|e_-!#I>4-J{%f%>2( zn28ysm~}4XlIN)>53bM{#pG#;ePfZjIzrIub!U7bIOAx?An--1t&82I`#|t&D`#`+ zj&vxPjS*wa8O=QAad5qYLsT2j8(%imbZ`C-u-8k^T9gR`u`z!Wb8lrBlN7PymKbZJrQ<$Y=*`zuDvHjJt>Grk#$FRqUFnH~9ri*lL#8H-i ziR?Ltr-^^^5127*e$F#JM{K8E%)2`AkS|MGGdBL2!HejzEz`?bn$#(K8e8y1s`paO ziq3whR8M)UV&6tb>e6}gjv@zp?*V^V(MCDC`_OGR&d925Fiw94_zwq2u(D|@=r{$L zD;6vzF>S}0H38oVRiZZMi^F-7iMu0HM?ru5Kf>De^iT9f zy)Xv|s}Z|zXzETmo@QR@5wV>Pgb~|LUYw{JzP4SWzC|?Pt3b{sVzx&8DYM^pfmU+| zkLdOd=tC5d+sB#Vx%{<C#ZL-y`)2;<3wgs6ZNC z70|OYpW&}z4(>t*Te=-g1qsuXeTVf5Rf!h;sR>s)=}A{}w*=@|ddm;62$^)(C{6XO zo2~UerX!AQr#J5-COY8=)f{0{xJ+@IU7CwuvPTF+hAbV>kpk@bGK zZmb6GGa0?r@q6pJW#r)%K!KjmvUFOsuU?5xHX!h_AxifrngKU7;PZ1}m@#?EdlhrQ z^3cMN?e`Efz^c2xf|SORR-cls|5|Dv*qz?jo1F9IukqjWdrf-S_k?tE?=Qq#xx36U zeKuyj!}woF=2$vwNkud)sv#VbN*$D&zckA^Umu}_WUD3~?;dkQ-zy&?W_0u+a5}v- zdtLbkvrgYER_hP*F$7br$`OQ(Eme}nEz=%6c~Qr@^anN26}&i+J=b@Raz3r&pwSvw z3-G^@35@rg;=UtnTJgPiTSRjv z%v^DD=$gCHviVa3^O{LpP*pG=O-& zJSbo|O11+b#*;a>SzxEy+|hl*KPUn+ZJ1 zbGfHHs`)*)rFnrEWgDaq}Qda3WLNpRKR#@n3SAL3$gB3 zG-0aAAf!9(oI~lL)vm9wnrSlnud^up17M%jp*6}$#0lnbsG+9e7AdBD;tWQSFM+H?*3eiJ|LLy zn(h*)=HYI^MeqqYHG`>;nrZaSxi^0Qm-#q-LLFCmd5#DwtsQtc7C0nM)YAO2b`aR^ zib0#8<{xBFRz-PhR2hl&+r6v>-rPUp!mKMFKNlt&_OZoPU-c8UDen2td!G_Xh|j| z#Jz!XQ`z2-XQ!pS__OtWQ}e{lx@GPO-)jfu>zp~yv*9mo$BW?YYaepa4We4|??mHb7Nx$z+~Hz?Z3ZE%-;4zuA1-%(XT>Ma!WZhOimVS*E*NYHueC zcI^6yYFN>?n?#Vx4CYYag~Xz53gFJyBqRyTlmUeLMO(t zv5s%TGQxd0GO>I4;h#p+_(7qL{A*ApQN)fv?2rx72PK!Q{cxLpBuor_-&3gUDin6x zcpcA0{NTU1bE`j-Fl4pdfUUF*>QG0+G8JYHG$M$L*V(9s{w?FRSc{~%U*3tso0gFn zQ@di7%S^1kkUN3Vyn<=P=o@xXH>)Q*`yVJ0gWN zfYroY?D(UcSacA$3=$$ZXD>Wk6E1iGTxOyzRx1B4+7?5rDT9EQJTvTTC zhb$~|;cB9;60B;8e5_-DR^D{fIUNR7cXcmXHD1sXl5c)*G^%Lt|<3jGNzR$|knI_>GQ zbT{TX9O@!N2CeBLph-UuAtYCjlyN|}24!0VHJ3T(*xNp`cni=cGqj_h%tzLuv<0Q> zZDU_DW?fB-ZDej-2y1U>l+F=5Zu}_0P<_2W^2zH~>gH^fl=~f|FZBr}X?hhucVQeL z9|S|-d{T+(2@(ZyG)qDNIX?I>_>yN&`Z-HdP3FV?b=X=5-a~6-x3LQe9q=_tgm9|5 zXY58r)C8XTHF~V;X5VdaZej8d$9_d+ON5j*nNC}K!f=2y#*%wGZE7gv6`1Mj4szVk z2XSNsTiZ=z_qdVBb}ryp?fFyN^d2iufzBVL02{YJ??h8XfA!vjvDi!(|B@pF^u7K% z%yjl$Nk4e_Z_DPU(p}*J?-T3iG4R-;lv?65CHwt6{Czv6{mMkq3IEs6UM?X`TFB+dxMz<1 zc8~kx)}sO@ywl4Kx&qzO-3LcC5+k4V&x>FYkda=+D0qC!o{{C12*i#Le zGQo1A)9Q7aFeaOOi}RR!Zy0%?IoFJrUjC|fdrH(-R=Re~sKou&L|F^8LHqd}z1{ZD z*^D*GvB+99zJfJw;~Wz><0qyFv_N?_!%JCvxm=i|O_TofJ)CphA)q1`LOqA@0ic~l ze<%KvYn+u!R!$!5HL+W+8GA7iRjQmwc40R}uV7rO^;AIJ8MwUjW5{N*=h%3_2#i=U zeEq1&AF@>c>OiiONiC%Dddk}2hD&nw#Bkl(DCL^gZc%TUsVEzdN5lwa%Rc@q2eT zWvMnF@*`Hs|E)5lh#n0#T`%KhnV8*%QH~=lCZqQ$r_n8W z8na)4ZyZD_XB!L`mHsW2B0dIi8Hg^Q*i*lgDCbld#)yMmfQ*x?V(-VV?9IzfVe!8J zAZ`xc=4-aVTdh#Pd$23R959RNOZbnd!ASnKcYfK&eZKZFPPw|8v3Rs+Vnm~66^l@k z66^2l-hT$&?*L3Y$6DrkHY5OtnU3(k-+T4m>W=_+0;pZE=#j!%(gnakI7dOf^pID0 zmmW1a3*YifnQ-gnYWZ1%+ft53_?5lUA}}^IvPl8~iJO{{D>j(Pr?bJszy4RJ%|^gDO~x3I)$_UFvZsmKb^;k;A;pd|RE|O=vBHThV*`qu`KQsII*(NNcaI&C z3X_vyP|Rq|sr9sKL<^1Q}y|&&&FY7$tYM~#?Abark;4)V(bVMff`j`4%F&EIs zGaZl@KZ5{}s9OlDSl@9pP9;ibnG@%JBIrA~g<^%>`cqdQ@uS&lvaG)R_mJu9&0TYC zQP;Wei&OGl{-|0v-qkzJ2+d4_*Ce&o%C5Y}vDvzpNfeq4 zWcT=dc$waR(R8c!q(e4J8c0w~ZMz$HspZljQ&1Iy>eyD&YaLGVS5IcW^Y{(d3=blW zrJmjeMf`vb0Jr~-rt^+w^9}!h>`_IF+CtUdwP&cRE~C|=R*b5>YllP?tre|2;Tl_rx1QllDt!Xw(mo$#o^m4DBi{&UR`z3X|XeeRFgxjd67#k-992k zX9|mcN!z7`@Z354?8N4p+_qmX}2DmtYY6S#0y6=3$~(CLuZU|hpEa5C1bZlh0W8EKT0y2xl%_~_5o z3p()Aw9BC}s7VC?+k(58{nq5L-tb^H`M+aq8HewuPE#=$-y0ZHf@FANnhH#a(%7?B zS25l>i2L!{B=a?O0bGXpdOD2l#8tu&jwY(Mc~N`_9<#uvbvsw%s$^L5JCuy^61(!U zWA}eqoD9db3nhV9(%^uyCScQV)sA)H#Y^pS6_w4r!{uKQI&eopvAP#7J2*)BH-MTM zU)*vJ9j>3%@@Nx9W{$9Pp~G8tw5*fB7ABOg2ZEE6F;!`&sd-yMT2w-9Jao>)>O4Ww z3vQ-;#1`7aYxJS+f)7#+iy{#s@dVKM>7!Y2-^mmy;e>=A+EwMw)JsE7geWf^Y6Td> zo@IbMI1o=t#uW%gT(MTg%+pmE2?0FjGMFHIj{?WIxaH%WZTyj{YAn5pRl7DQKnvS2 zsJDgXBSv;;UFBar)<9i1fwtxzLvRS7zK-|dF#rkTpPT@`Miu@*E6E(rt%U4>zYPUl z{2H#Im=>;j$G`dDKV4NZ+pKdv<hpQK}NbyU4!8#WDoM@xk zq04iM&;N}7L`6l9mFvHfM3opTYel!4X{9Z;kPN%iz3<0*BnV{!kO;f*e-Drk#VxnQ z@)c1apD$Ec&;I8MDv&jb@zua?^?~8PxFmn)h!=D_Kr1sXvcW9by)SS-a?@flM{I2` zaWc2^Up>cOK(Q_Qr??7BM(kq-DL-(r^0)KDAF%vp`ZC3G zN?xYT7UYyKPsPeTxm34Ne8mo39gPo)dBdB9_-fc(ovs3Y6vVV(w~MK8sEPzaw%nMi zk0Tl#JhfP^sb{m==tf2TIG`HaI9NN@Jj0;G;p)aB7}lYM{-r(Xe!d1V)pWPTKJ%X8 zoFC2M*PAO(m~d)ZxcaO_8(Ubez{jhIwh?we&QOZnfAlPq^p) z9hBkUNgBJ`|DG@oYf-KgbOo#I2xiV+Yx%1ar;lm$weKeIHpV(JMqUoALbvi5+L)>s za?Z8cJ&CFd)#WSUz>ao^mN2+YrG?pv{?!JN-=5b>jp=f+>gW}v-Y;8$LeOvH{%fxT zzGKzJ!hb}OeZYUBh3cx9j8xRSj|}%r&0`&P>ej-+p_qJ!hIvw~&b~ntN;U3fmAe0Y z*GYMiPGl$wsb_lT>-7@2YjWO}3`fgnY9Jlfi)7>YaiQezBy7LwIQ#V*YEHQyqdqhb zX=ppk3I-$7v$Yx*sQmX}n=&2dly{L|SW~1M`~@gkN7U?;-x2(GdIz-3S$mW6efo^F zyf2<^?tY|tM=V*0`1<|gtCnw)J^u~XSd9?AwcWtcK-$Qr;~bJ0(115IsS&R}Vk4fB zIHHilM$z885FiM$a~hn!WOh~et|k!-y@_I%(Vz*>9h_B&^=)W&*&PL+;oq0d88*PR ziqhvx>DwHYmFG8i|9%UIfr+45XCIcy)A42dA6wmTK3LrzG+$a_>6dA9-=g{Bj9iI)p`hXLSzjIQQSiXY z*jL&7<_K@!fr3vjMYV*kWHJ!pB%_X6N;ss{y^3^1PG=$qPreDw?jUx{4DDUYe^C0v zhW$~!QuY{%z7aoN2HO&hu@(#Vb*kLQkd%@nB3|-8he7%W(5j100h|s4 zd|1?hpky(HEwNB=>(Ko!ZKYhIZqo-C0$)=sH$vG;DDQKa_Oc99RG#;mQu&7!DGK~- z{q`)nlhwCG>K?^x^?~V04CHF89}q9xCcb~qo1s92_k4G9^CkE>(+(B=#~TFKfW!@D z$HF!BQhR|}KfVq0)z->x)@{|Gb@T6eoy{x_~$UvmM{CsldzEpPz^Hd3d8Em4o(`p}Wj`^pQEiy*@d{L} zXT4p7{DJe!v*Glivz5Ufy#PFzl5b;LlSS3sCdxtN%sjrXVBPa+dd=4s?@X+I-4hP7OdYKiQ!>1XI6>lKCDFN(FOUVzT!)6 z!*dFP%g^=i6>U!Je|)c0@h^Gm8UgMj89ywEx1}ZpL%FFXa_00)AUZpCRL1)occ){u zPc}U&8A6E>yo<{2Al3pW?zj6~8$%kpsBo)+_m{Eo`?cQeCYR>*Oc8K$q?}-NvZICl zZzqnX)j4M^4-)T892djZPw<<#a(;pSmur=)eG1)|6UuV+BU-!eT{TY;h0L0Rqb<^C z@^Nk7pdzPgs45BCpI%Tz9=DRsdI5Zg@PUG&dh!o@3T>E@>%OV1jF%5uM7+~UQeIi_ ziPgBvzK@=|?f@&go3gEkG~IIZiSGE+X&+P~B9adZDf!xFMrTzVGqp^DT;A5u^#a5{ zkOS!V&@8fn&kePO2Q7`>SD9O_SlWfk&Q%RqtUWqNA$snODJ3901BY3hhY+VdoNqlw-Ou+1t>x=*cS^gI8!tN5($_3Mu_-3i}M!B zztvt0h^sHtTKj|?JLs8H(La*{_;YYd2|bas;u-SO%8PjG)qnim1u#b~dTrERN8 zyDxM=m9p2tWD$tP(62b|hzE~nc~G7maWGSPUQt@kxs?yNzD!jy789}%r%+7cc}q;g zn9G#hl5iLweJyHqZW%vIWBK*$ddYvno#$;sco&)KO?Mhg3h4Sbj@MUS@|wERr6w;Y zS73z;))!y=1GrY2vjbQQ*r7Jo<}YbM*M=$YI<(wTBat+Io6~-Mnz@+2WVa1f$e5BJ z!;lUSRSH~(`(7vev3V+L-%ja2m1j0MkBhN zy(wF;sJeai@Y6=yWhjL3Nz2Uu*);^ngc*+gIflF4Acl(dTZ)*Ml$%J|n>|`X^*#uClv8@LNjWF8tsm`F-?_6}Kto4!Q8K_i(OZhz* zxaKt5eV#Ll&-PRQ=&xdbVBhNirBI5_jG>>U3tiE!3yrFIUoX-1%CM0k2%phQnbts5PS+d}1X1tRS z^?lwF2dmI%nS-y^ zH4Vi-+^K-jbx16kD6C%FuTg9^{0~2CCdn$WbkV;3G{Cb>1i%}k0F1sX0vn+Vdt=Kt zir|+Pc_*?&FKAq7Ia7sU5>S76`@33q5}r23iTd;9!tb32)Kljnv<^(-ES_|Axl-b5 z0#P2n5$N=)=|adY)UwlDZ6cn%N8-1BeIZ_)uCpgI@i1Jz`E(`Zr*^>kHkfnC{x5nI z=~!vXi4S6RQ{UGv#Cf2pR|+{m%qB8Ec}~-VHTRg!N@~dBXuMw!crd}8_Vo}tB$uTk z$T&dpfFEBgw=RE}u5pnS_QPYQD%0Wrv;Z3}XlpsEa{(eSZkxhU15doXaUhH(lCz+BnwC&e!|^_nCUxU4PU0 zlU>>#hZ_%1WNOaunfrvXy>-GjeR<-Y0&RWoL%6Ti#k{}zDjSr+vikHKpzdL(z{ueuL) zy=>?0r5+VNy7;c;As3JirZSZ!d~9BA+-l&fhf+QBn=8DhZQLX}bbbc$1H}*;YymTV znyy zA9;Uq-0{op5CE3^9tex|VThHaCmeQ5siij5VX*#ZPw9K>&32Yw+37IKE(-NtTzi|I zer07gpd`XSVAF35H13(g!a}pxaZY*S=uAht-hy)qZHJGEpNH#QN29&~s$Vyh-flm3 zOm^gJJ7ka+Q8AzDMNDEYzH*iKQJg&kDH+Aen72OnHAzT~3f2j=Ca$t3;OdLHze6}{MH0unb?!XFF)D(t6qAfSYdBo8g=^pQ@}7TLJwY7xbm8aox{x zT+hX8ff`W7LzB2oDSdVH?g2P zTuy{fy$Poe881JV^#<;Q6H$&Qys?on@!Lh@K>^Y>ik^|7;99jGZ@B&QYA1lpDdskl zMs(}h8XXu`u+;pA>U{1mW6B|~PQ+<=1SpIoCBkcqL z{|wx^Ukhqw-^@@1dxt|P{29l!`%q1d^=RG zbbgkXh|UT1EH68ILy}CcJnD>~j4;7boOKf3>ngu^vA!g+hKl*%DYj36JsOx`Xj40_ zHab=Q@Mt1vZZgq|uUzC^sd{a94%_PkwIbtWOuzewz4SxR`v7%zvyPsZa0)(pXxO@RQDS_8|-v1FQBqFY|er*=M(%Ro%`gc zYCVt8*a){4Ag}xEF6--kH3g(5LffRHbI+lb zQpOgejE`w9!{QF>EY=?TmC8g`@6w$844Y9ul2Twf}w!_lpDsQ2EdX^nBk9JxDvb-jWLx`;1!TbWk2L+%D!v~PahTb*4l zj|ijF2z`XeLX|)Kins33Po~n*dF`1_b>4fDGpoidJat4+LQT^hrJi{X&HjCrr>g!+ zpmyt2YZdzSf8sBO{u>4;ZX8ejH_iA&Nfi8r&ocnrf|}ZbM%IVlM?Im{2k7pJAtp*# z>4|?I>To$Bxo&Lh$TPQZ3I!l1okNVi}=jL5Y_R9%1^O90hhnCsu@_M_j z#fHITqce*csPuZ&=lTzATE22*?+Fn|iP$Nv73<7(UDedoAhr)JIo8p3|=)yjm z<$nPWd>>Gl{yc`?HG`gH7P63$W89(!DX;9`JGNW6rq*v$vi(X;T*@0)t)Y zjdvaATz@*$1`-PRFTSo>lC?ph&_-wu@W&*9!TjQ3e_dAK29Hw_xW2}!0N)rqqwk++ zkUOq5Hz>v*{Y|RdjhW#rY|b%xjdLynG&JzDRh=Be+vSHjrpf;2((e{8=O=NJb87wT zw@=6Lrj4oQXssmq`IIXjMzwV7H)z{K?IC3Q`d}qYC-HU&ll&`|OuiKLVjkG2!&56| z9D#0lEaJBG3PjCBx1%~gGQ?0<4Ek7mnr5#Pe=8`GADM4v4)=bY3e+0OUZ(&WYS)9} z-Y}}52M}{_i42Rp8kZCy#u2P^s{d#;B~)-xypVl3FEo~wQnu^W+&f(QCkd#oecqMP zM-JllwUs)#ZGnFuqsukiWo_v67EI%!JdYl1UI-fI_ffk06SeZ^zgFX=hxQXJ@$_Iav&3PdOK^R@6%>&*GIAg%w=a zN#Y1%8kKZqkKh%&eP5}&()WJ%S!2sjE2TIP5`Bt0AzG!=}6Kj6++7LQ=r0@uoI3?PSxx zNvlxsGI>wG*frpwC!tRK_C6Pp*$ggYnt!MEO*Mg7laE#4Ew6D4TkZ#1y!H!w_H0r41GVR!SO_KwJ*Tz)z`4XZy9PNI5I!58qCz|{-j5WcQm!q6 zh%k5mA-q8=XV>`5$+-@E3-5R74(6??g?=B3aLVsut&Ydb#T4GqN0- zohw3kG4sHc_0vLQquV*hJgy7HCXl|%A9g{DUk@2jr(@5iM;bLqVa8u8yYe8R^N^k5 ztk`=2-iP}?hzuz#;e^Lyr(imb-{)jY^zQlXmS^{_>dPtH;$NaW+#tU5)~9*qOIeI+ ziS7DslsXiAGWK!yU>-Wtx-)dVaY6}^`;)VLSL8G^!L=(NCQjPVJtAaMxK4)}Iq}E( zF}XTQ>HBqDF_rKd6RVu!8&;Z;zuz?#>Ld$nFWD_DeqQ9Cw&5gF8S!`l|KyRk5obQ# zR>{mtQsdm)!BAUl9J<#0i=6kjHODu#%n}1%mj2$5DQQ_2=*Ocr1uu9 z!XzIHDf`qz%Nq5iubv(|#hmV|S>3H|j9OjyFf+W}OsCzg@m;A|rkwS|)HTJ&XVs&? z+=pcv6l;HIkKK$f+%m6OTcApJC~un0D=i#4on;~%0+izNKyDhF*@1r|GOGI5)H2xW z{GdO;5gUzx%q}gVvP>YVS1$P-3+BI{E>!-zCpH<~{jA2NQf=tJttwodOb%rrU8tS) zEBw!fmFrp#YQZ=h-)#z%tZ1_kU)uX-H4ux@>5$qSG8IRP7SP$>XK5w^wuWVp|CVrh zl;3N7&T!j2bw+~0b+=!42LRTZJ}o{2MK>wLuB6Ez`^>gPI4fdKOyuLN*2DFVHE+9k z-v+^;8!YOKw?y{V{i^e=@-vwT;$qypzSlsNtA}0ZiC$9=`!0-Fjp`rC0{$xHU-4w; zB?*jyi}|rmix+d%*kISCnd%#MssnNdClQ}CCq&l__c8l?gkO<6nmd_J1?1in?s)G?#r5(jgpb>kwg2T=s`UCz-2xyIZA&DDaBiiWJpnZ`-8|AZHFCcUk7DXEm& z#Qy0TuKET^`IzHP8)%wF z?G51*C|qX$OyDirS5{;9xeaA$rRG{&XtU4iml*@ock0isx-sh~okiW^C-V-&U3!G4 ztaY?bTc9VLm^+o%#1|`NW-^Zz%j?5}A_GYM;R3ur%fFE9Oer)tFV({JxRIr+|I;F5 zxLl{w)E>(d{AyhIpH-gk9Z%hFk2s~*mzrAF)$RfqoO(|(aC$A6yXt#GGeOal;T~bW%Co8$`MTT5qItvc$=i~*UtOWwZ0&N?#JAx!A7o3 zq0-|b(X0l5u;STZnOlWUmA0EAlJj+?psx&dSYPQJw7aUhS3e1F&uYEqf`8$(--SHY zKwg#K3Lu6HWJ?6M=7nF@dJKH+))#f4l3hoEl%;bA8iBDd7h$km7fv5jRg-Szz>K&3c=& zN~ePEHHt}xl_hC|lJ5{A~lWza1DJ@~2wvwN`i)4ZRc-=?E|kh8|$ zxMBBl<8-eikswd&&MWvHbEj0o6K#RbSZ%!Tp0QJR4Tm!LusP7194PSf%EDK^X*k<~ z0`$k_P`YQwaKHe%_;u>;brIP0@ z!_x!C5gv&$)sp@nvd!D{r}J<-UML}8ui5L7Y+Jkn@Pxa2U2>`}%PgQ8zNgPdsHymdaZgwo`=Id=noY@TT`S1Fg2b7JFB2$){rluwPnQTwYq z-jlkgCgPiieS*zUBjU5ke&cWdBO7Cps&4zjkjr-@?d$SpfRRVtrZe6k-j6ztwmg1G z9Hsj**5tbe=IqtAexMPN%#S3#lf@ z!a$G(kd5h~bR|d1C`I=8ldd~?j0#<{6!%vJwnnNJ9%(K5C@0y_F=5p?NH4;-fP`Av zf4E--);iv52zQ172IlaH;u1&~1^O}#8IVS(R5!L9(5cgje{#NeIl5op4KvqgOYWH6 z@ZqclB^@sJ&3>ipZ4J^v%GwSOi7v_?xg3*5)-M3?xR+jd{vtV!##}-pB}KfK1J)~r zeky(FGkxSAmbPnF6#7AxGQRPieD9t&F*Z8O$AXng_TLE!O2cd@ZJ!TPP)e46u@Vn% zYhqAe!J;0s*F2&Fy-ZLTIpDoImJcTZQTJc}Z+2lFWxhq*(uhA zbdk;}y}I(xS9zS~81fu63rZ_u>r|WLNc#+&)7Udgo_d{iqoxEoL{~7Z8(CPTZ?P(U z8vT0rtpX3cz7(bklwyeeJ>=<9@d0>YYu3zp%p(z`wqpv~j{6osygKsJh>KJ2Qp4MQ zyQU}e^e-Pd>PdVsaKGmE;V$lS2)r)4A;gz|@OBCcd`_+j4bwH38v*fKQ5SFBf*w}1 z#j*Q-(ie<%_(mm0rOJ2#nJuuPc>{Pme4A@zJdIb4I^3OG*UdXm>ReEMql}GIxSQL; zp*X2qMe+Fj-guy5^Ct`}bu`aM$FKHr#L3@Mnv2gqbH%+z9?4Qw`~21rvjnfYJq7dp zUQOIL+bm8Z(u`kU71vl}NCG5xz@xiRQ0#!RHrF$$C){TbwiVGWlo{A*+(NQ;*!H2f z6z}hvgfO4F+T`d@uRS|Sz?(KFO<(xXP4)XpO}ZXUC*%gYte5t8ju1NAT~8h>|V$Ml8$|!x8xMoxQv3C!x%G2jX<7LZKh(xIm1{7 zfzFC1@bxaWFFNd-7m5XwUg%j=rh((Fi3Gm+G?SeERgdLN*CR0AXxr(Cbb*`vL{c(V z+PB$```F0>tLv|D=SZf@3LoJ;eH%6ud%2Bt?dI}ngWEt`2|vT?yIGy6*35KrW|vjQ z`3Iv{S^35va!f3fg8oWo42sjv@uaILv&;JnKHcknGt?3lOO8ts^#NCkb2`P|LQ1uizr z0PRp^>C2*V-lg*$6xHJi)_SX}zZ}QWv(a%V1aCyEpYnIZ`UGZ0aF}Zik8LeGki|aC z$?l(n!tedmKocp8R`Zd^uh*Q8Cj2;7zUKHXh^NHHhUHw_Do<{Ll-ERV#U1EqMTNVN zyO}K+l++X#QQMAYEUqze-gOjjDy6Uh9sa3RCjh1ubg|^elziLr!(<31O^*+D4R9Sl z8u2V{))Ywe$uu`N7;L1uFCs4*M7e$$*|U>-OBHPUPr0hicMhHyF1RXk9tP>V=C_xN z%c>#^@8q@u9+!?soJTA)a(>WI@-BtfKmQbum+^S+@!n9OW*g56l+s@=dQ(7cZD8U0 zel7)$lwH}mc(K@&3zJ!E>MVTTAV76uAfVW7!@*>`q&Zt{7oeFZ@Xnd^LjNk{xKa*d`bo zeFZ|PL>Y3E>lc+H;Kid{bI=J@LGPxoV!q?A))PaoGpCKn=n9}qX7*)Rx+qmM182=` zrQa5v8CIgtZoPA>88bc>t0sf_a>V7Ob*!qIJdjVp3~tGsDB zR1jA=z<;&Fss|yU3b~vQgmlgMZjmRMKoIalvgc4}bL-mgps$O>!QnVNHq9vvIhjI# zFpk(<2m@7fQ#U#+G@BFyqSXM8X>_ENvZ}uU9Mot52~W$M{)!=*y=HMWOPn%M&ABXe z7C%%Pa8r98ew-mO1g_{CgeKdA1Stwa-XqY9TKAUD#V!mn91)OraFOR1JXO80HHx1$ zRO{~cdp4*HmuOI(InOaESSR+taoCe=r>t)I;ePbt;9})s;LW9Y9RcA83^V@jWTNrc z|1u27M(*VZ!DsP@H+040dLvM$lNQa2 zj+U{i4M_T<>L?d_u>adf+?NyuJ_{fBFqZ<#_3p6#J&W8 zT)n_=6$938Ev4*=v8r8&ro54X!COxJf-YaSQCl})T0Fy()stz!f1Hxb3I%sh&xRR8 zx2($OYU-4&BiS@pJC9e@R^?XToFTvg-+-(uJX$xp3q%%$htyF530UQeX{rYe`Z9cR zPEMeU;hzx{rd_1(!GqxMs$@#TUu+Q3b2lu-XMuEY<}k-%RwLOR9?8|;3;DzEK>F`h zcKMGr#eFO*KLL!zha1SsTj#E%QqDeir;S-%eoZMwX$^Zmq2WvY><&l|c!D|kmESH@ zVfC6``2({IY4xEObcu&K(u*SS*g}`ar$Nk|7UW&IOKeX(0_D~~hZCM% zAQR>FC}=@U$90PoBX3gzVlZ2MxULl!s;msZ)2VA**?!WT^XOSez0ff2qQye9SRV~a1H#~o$pTbWpeVhCTw-HlXf^UK6|4IrA+kL> z?zaQRYrgZ!ED50okw0~mfQ1vh7$u9!+->*@Zag<{sN4wK5ugBmVW<-;54G0DcV9AQ z{vF(BW9;$;>I&UfXs_j_$sSsc{g8p=H^p)BI(hhTzuBBz^ah?+V0}2Rz&kK6;DB{vYd^g zPk174XsP#0#T8L5%ZVH>PvW1+VU6j1;_uy@su0LvBvq=`1VmQFfK)0L^?c9>u?;>Z zR2L!KI>OMQ1sZ2uG6%r@3sQlit)gb8$A7KMtivG1%?$?_?)yMKvdBn+lDB3e8t} z+_TkjmNp$9*zmfKdmU;Fw}x-j^q`GB_UFm1Ek&tDAjIqEM zKzklVt7yLitag?ecva<7z-k;ts;6T4^}RIk;!ir*ieHPi{Rly~o@cY3%Dm7yB^}YK zLR1dE3`x1X&x({9Q5M#{N7N@MS?uInj2uMH+eNrX?BusqCSAol#ASGio2%bDNlO}( z!MEE4fc>;W2tAcK7J1R(TLZ6FLG>%=6A?DS2YvYZ?q{{Q{0sH&?;=sqlekLC^!m$$k*2p78KKi011P>Z5ubci4KT&F8$Xe)W6#wfpiSxsjx zfT@1(#2|eW>^W3jy4B#v+)M2^LZysP515Pq)cuqJOjds7i>o?Hr6oT>Gy_SYXDhJa20zm{2!i_#+pT%dfyH}Ez}HCbwL^2~VstHM|=HcbA~?Y|Oa zkNh`4{;0p*@#0mQk!a%8&4mb2n$@$6^CER7--HXrDF@BCJ1@!jgsg6&_V?8gDgo~5 z+v0lyAWzMP643T+lz}dNsn>>b#AAM8%TfHdJ&z3(q-&$!d7~}DA+Qu%Q;A4C8D;V3 ztA7CP_rUVvphqUN<3rR~9mC>l2cP}m+g<4DT&dfk$a$9b!D~*dYKR0b6|fGm6>X%x z7-OCXs)O5)lA$cSzaB6pr}^_Wos#rie!bMu;^Y%nGZx5e3!wJoy5KvsG%u9mTBXPk z$a~bmQXVJpe_DVYPa4?*z|u@*;F3PNS*vm9f)nI6M^5GF75b=mPr$G`aY!=~rgOk6 zScuLpF!s=6stZb19K(3QuU0=aO{o9jh>sjHDE$H<*6uQNmC`o{5!7zl92Xj=@Xq9k=Mg3sIIl4Y<~r*L9Q=J}D%*c+8qO2B)S zH-AVC!QTukG5yz--91BP6ZtXSjeFDnq-1Tv7r;xQC)6Uxm22W(qHocU`2(KVtB4=_ zVKJ}Hnny|&;$%RF5ifuCv~K_%Sry0q6qExLv%P39_%eBao&hLYfpr8JLsm}0a}(hvRuEe&hDODXN!g; zBY}Q4iIbjg()||!Oh2lU150<6NzM>eu!pB(V85_VYDlXz1(c<$arsz?@?9bD_la84 zjpYKP1)x~a%@`QlI^_a;w7+Mwy`s0NS^tmUBTp?TN7-38uWdb+j`wE(dk=M18hn4s zRJ7yfS=!Je)Fswcccv`L-O(>Ys8=bfJdqoh+n1&+ZAhzV7r{GsZq#TlzA_1_3q)v= z%;gS0q%`?9_pd5t=9(zTSr2*CsQQ2BGlm-)4=k)(;8xe3zk9)zaW=A8-PF0x7ic&8 zyG^}hKoP8^vXv=)lAodrWf_FJYB|IgQ%4yKR^nup&g0cN<2J5_@@0ZJ5jV0s2H7*r zQ}5q2oe4md;CY35oazYC;32=UGRmETd^IkQNAkz)C%9$dz%j)4hT*56ncL54V`cncWPv!vl-fyxPE#u3( zj1*$57*&JZn+uIFrA>}~lbgxr15K?rDVv7t=$}^Pz4!XrG`$mZ3;v*NKkNn4LR%H? z_i=aYms%!n-uS)GkE*bld&xb2{ErX27WBktJ98scEnRX9hF_ly?CfnGw_cVbFGHLA zXEBG!Q~#mUJE1cT7ds_+K4|YD0vN-CGr4?;3?dH89X}y-o&LIm@E_Rc_PTc|V{(Yw zwKx$1P|)ixDKHeX7V&y}#mT4r9ymkxSV8kt{l>ib-WEyb2FkCsw48JV*6ra;DzejYKc;3-c#F^e{-+0>zteZl;B>oPky_4KA@w{fyHi&cA?z} z_3&f`%f;p-{l)x*m`BMm<3B+A+UK%kGI4*qL*-638&4q_1Y!Le8@xlJZI{MYiAj3H z_TZ~J__SbErbvN8(f;XAL7hxB$93G9w(h1ZLQA*cEqzo1HG*=OWBHGT>o>viP9WRa z!L`Nu@+*(fw;Q+>o-5qH`Imk3v89rbM-uw(f8a~OL zbAEckJ@g)?^4TjS9Qf$mJIZ0=8%pvf`c~adxr>;_YSkQ{I?#kHxOly zwevhthr-aB`QzrnAj(TWdQFvr&t*PbWG4;f%KG&lZK zlBUw8R-1UjvEi}^W75~brCbCj5xxKKeBq}Y3TXrm8ybE@d5KNhO00CUtOC8#7L zdv_A1^_U`Rn8j@AwQfflH1hs7;t;m|ZoOe4v?+M`_O%kV^7|ZpQ}>{tW7RLiH*>rO zOHxGqdT69hOE@6d;A;Zokq!KzM;E-Qdmp=GRw@~SL{J9ReT}vst)0|2^F@a06bZlb zSGW1b;g29Y;U|Y%EOLhgiDzWzsupDKJ6Jl>2Sl?JVRy}9!a@fz5FmpV@R3r4a!)P| z&nC|0B-I}N>M)Ohdl^jp-AS#I>tv>&hg^%g$yfd6UqU0X_;cgmiTu0Vo0A56HU6Bz zb-Q;a>)hVtZON&g+P-`3&>!)TJ`L`6$`xD{aMVzD%$1?`n6*6g*Zl@JOwH-pW1B$h zo!MU7v!~_W0p#Nu!Le_nB_G2LPPa~Wfn<@2zK5AftB9s`#kPiY1^H`S4uO@zK_|tU@xX_ZlL43iQV18x%Y(0A6W@Qaka4CpDsQI z6XbE2C~L*d5%w=Hp}{&ds?)0B6}g?anfMI z%C$hXst{)r>jdb2*~N_a#%_p7)W}7N|7Z;&!vX;$+Vsy})HWh;94Lf2=)iXNvCwf_ zRh@^QWTcn%Vt76t$xz%oIV*wWHP5M3053^{oMvae9C?}uM}ZVj)-wspNZWIXe3nf^ zRkzSl*}_|hxi-*UR5$MZ>Ed+c_U02GMpLuLp1(g%H}xRLGc7YHpYA{J8@dejM1o^V zM38A(tplGctQL|x^2|Ra6JBjrLv6YwnCTW5PTDFG{9KT5^0aMm^X+bsXXFh#^U4rH z%kCzm_Ve}@-aw|xtNFJArY@*#JMghAv1q{6;?S(M_MpoU>riGjUx~gENDAJSfC%`NnuI{;O%A-XBlm zTwX)jo3wMYoJ>U1oAK>QHCx!Pr*el)H!`4jmKQwp zc-Dd|3E~bM$6$rMveqke>iHidm%ZQ*=r1**h(o2v+Q*xE^8oaQJn zsmFX|XQU}Vz4zFdz4_3VkILQY#CGe&$#yeP{>{RtBpP77yX#eW3!f2OO?By&5>+=r73}+lwq;=I?xO(K^?L#x3)i8`S(G_zQp?q3Oz;Mdb(f*9 z8#~febLZ(k4=z#8lkd_Bc5IUNuk&HGn0he;w>aPHVjXapm^t z;O!g6mf`s}Jkfd4TpH2yq2q_!kHBB<6Wth&_Cbr`b8i+##@js@mHGx+RKah}{%B-@ z=fQV5H_=HUY!TKpwdN`t--hdILRrfOyA!XZdgE^8vFEhpjvs%5ETYoZ9A2Y<7TJ!{Gc+Nr)03pwc+h_Le}UD;-gTu z>t4#|D`x%WCPASFd?FcY#-Qw$=cK3o(+gc=*YmgPw%<88YdBRQ-Dm&#C?aN_#)4ZP zF7Z*an2?Ky<>tKzhE*ev1y99&2vEsV6MtFy>psfVb%T=(vY#FpnqkoD%nUtP%AgA-YmbK*DS#2T~gSI{4rpqWUxU*@BX zrgiL>7iW8110}tgr+V68ucYyWc#By@-tEhFY$!CQV8aUn*12^iNz~76uSy46nlBo( zw5C5Fc%ZXp61uLou{qQ?cp^7eaW3mr&|RN+r7z-4+xgi{Ah5mE?on0i4|Ns_`e)=C zIQ>r=(Bmn{Cj&pQlU8CBW}@5Xb2m^wEHK>Jxj5lH656xlrrrF+9Dky7=>Pul^}q4o z*KVdIyms)}m(u(jIdyti5?O(q>47KM%0$97F*%N~N)Z{A@ncJ^ZdT$}$bS0T$vDlw z-T3>iUL^#HC2XMVrjZ?ISKA7y4rH>yf8jCK7qU^bn|)>lO+HYUHBX+7yU3zCjy}|> z^>W;D*qTybL(Z!}RYX610=1`SuuD?d3P)IP`a-Tm3589RUgv>if1&>3+I4J(_8S1d zm1SEQyvxh^1`@OO^P%6-ArQ)>j-NH(`JD1>+nnOz9UDfQfBGvJ$)BYQ?!g?yXJUwY zyS&;)PV=vj<>!OS_zaKQ?Z7#bICyIuVF&fK^!%1|?%FbYNcft2{v%K{zjYuzsY29i zKetW+>JBE9YBkKx!6`kurBdtatiX(#7(6IJIL+h(@Lsxtv;p3Y&q&FU(8RUh|RBY#d_&X?}$&AIcToLoGi(fkN5lWd3^tZ@8>rU7uR{5$MQUm<2;VzyqczRGRG`o?qR*AaULgxg0`ax z^0XS}b(xx$xFLebVs1zciS(cud?|i|jQabb7?;lNhjdgD@k*t_xwkK0mA~&2X^~J0 z|EOs)eM=W2PU$(&SPgG`TlZ5*Fvo)LB8l3`DGQJ1M{3|Q>ZL(4ffn4FJl00vE;(Np zEPNU=se*2*j&4}Ia-cO0^JFnF2p=+ut01RrDhuD0XSWa*Av!E)ocH`M-|Yg1$F}KJ z)d*i=@uCIQuW4(ltvlF<%0K4V;%IlmQXzhSl0GW8l1#6vRZ5`Mn4YkgLE5=(7W>9G zh*#R2yO)QEuIeFv=jPMbiC^;-3B1wa9gFE@6I=~`SL%vK>I$WqWK72D%1_xg8B1Cm zek7pkxUL9uGMgLz)wykOFH4SXa=(@_m}mVuR5Z4mxVUZA>ZQ1ngGhc=H{CgxpE2Kj zMZVNqd0`XGHMfpzSDyQU`Vp9WI}NlBr{v6ofvy+Fqqy-QGUb7+{e(Ob&~)FLvocb2 z&&nxYlQE7~bn<1LxXNhca@co?@Wt&E#k_E}21dQFX63WXl9(}xS@Qmb?XjPnVx=uB zdHtRD_db?KRhQWgcbOaPH`+YUlAS7_%YH2;)DhU$U*X9gc<$;yz8J$wl+VkLo!=z6 z9g|9#9*UPGhZ|-a+R-uQi0}htals)o&ZdFq>79ebZH_b@2bLqt2u666^>xve7utHe zu{0MWTr|rQ=20;3P54j;*ZZj6Q#FJgnR?vBLeP+36HvlzMRvv&_eHBpFNL~>ZCQtw_H(2cpdJGm5G4l9b$}R-`_U4CYWyW z>CQJ-siVu%YIq@;z?zw`oy&SDhiqcK7+pE{^KgTm1hIf-uLWTEBKA2nMWG^j7r{Q1 zf=p8zz>!YPO4;+2p>Vi0-UuIxOFpPpIse|7O=V0O>vLe=26bc9m9fsQ>+2I6YgA|$y`GU=PakBR!~A$P z|IF-{ zr#|>0Bl)Wj98RITIs;{Hx=bIRNz_Wya_QzSchyIgg+H1jy_v0JI88Hf_YsqCtPDWwYj)*6sb0^O?6~C&CR+t4I7_4Y5%B^2%BH}M6ln5IW^=`40JH+7CFuSDxPHsw>KB)5#iS+7@g!AD9Co)n|1km={ZQ8Q1SnPo%L~6q z=K6m8pY$&5WuRkgv_XA__KhHv!Qr^p^X9J6 zHjQ?U2&>QUqXlsrw|r~;KmIuINmg&m%Fpr4wTcWX?Q)`XO}f>$uEf-#4$|?0L{3q; zRcqF~=qn^>BfykDF3#x{5(f`-^_0!9vY%JSW$_{*e4MhpMS-njBzeD8@a$7fD$?a@ zA5yE!){|n(a_Kn%bSu8YCTzJZ);h+>P_Y}1Fl=>}+ZI(oNb=q5ecaHb7v5aN(F3pW zacd!3n)uE@g%zs-8SXN>QQRlSc%S1}LG6*G$%R)JHT6kUO#0y;(POvj}NCvWw> z>2r~PcxIu`t5#A4f$2=vvXy2cHHU{!=uE8Ck+~Surl1qXq#6=_G0K%fvKNOn3vHdt4p{; zC33uRvYx@B*Jcjo#`ZR(+9v9OmXAyz1CRLR;yvkGstul#7k4kF72Taje6_V14xK)J zP6csEZ2OBtO_C8BLDlS=Z(f-n1-m#y-E8i*MYIYEFcka-y9TDEsJE5E*Pt5!5 zR05Ag_ zWUaj$aRm=bC|Go1uTR;CSBC|1QLmqt#MQX5Otx>INhtLRxqVb6IluhVqeOe%@+iv0 zd$s94d3s#%Cy`Ap^kJ_@9{f>dd2w3CXJfQGXvgD=T31}W(6s?g@QEbbX(&DHxOIzZ zFNBHL5?J%qEKr6Pni6Yrg;!mA(>hjFCs7^qP+nE(-8H0GkaQKu+A?u!A*4>B4KI=R zXpC*2`%~F~$M(gJki)>i7kc?Fc*QR^^nj~e7O&3$=^|`WL))3`>&5y>x`sYU+^nf9VALkiTz!5{ce&}PTjF)9 z{O4pg=!|!mNI$V+FVJqhu(s%ql0Ku-#N?X>8{VYbkz}bpF8p8qTTdqu!l$Z(Zf!L2@>>>@^p(zz5P8F2|${%0mjz>#dMZe4tUhXQM|2wpDk(l(?H--<$S z)yD;RWX8CF_7Rexu9R?e12hL`ouyoL8k-cM_l;pX6jjNuGQVGR7VVx+RPU> zR_ai@HPYmSwbf#(ykUUSTbU?fa{5>YMJrS7S3Zw&-D*fRyUj#ZPXGMjh8O4dFFu$E zKFSbRw`(#K{sMWgXC;*FP`kns5>-?a6DXdt!6C0j`A0R|eDf&5ucQeFm7eIuTVHq% z&kW8kNW#M z?1_vE4Gs8Fr^Tr0>;s$EoXX6eI{1cntEaS<)(<9b360a~bfQvL~%`F^rjOTFibPdmSL!PHxNy3fKQe5<} z#1lx{Gh)l%SAy-BRn)la3PGT|Tp~4E5=4vHDf~B$&;y6K9!okb>I(ky!+vTX9 zwfK+2LIpLX&d&I%-+|p>PZ$l43p!3iLvHNjf=j>nqrxt&k(tx~toyqdt0vuis3y(J zWpUz-L&m$W(h@z~`NvfqU%VSH2(-pWmYlTlTJ+NTd*Tc(Ye=%MP~AmssSqM~t2e05 zCbE18EY$10nZ2s;8%cNL`odCjoe+bfHt=89GiWG52_j;|r zRO!%;Tv7@ldom0z$En&1R)%-NNKKDbGPEXDB7;F0t$x?5e6P>^rC_oUV~HF|6i|GM zAZ4AFyy>v*v~wc9T^4Ei(4lX8<=UYKB9Gioe0jr`6sR*AJ+EDecS0h}%)JPuoihCW zk<$1irZ=8$dAzoMCwxtgemdw(x>Cnb7w^%c=p2M`_ynijEicKcp#$b8qBvir{vdB9 zsjG{cxwybkAJ^)JQLNNSex+MD%4Vqpa_X_qc!qB}WnQ~F!PkLVn%;!|SrqQ`v`Uj0 z2@?!XO$iUvsq=S$J1wl_;05o%VMcJNH_(G4QAl^^2>d1$PmLl^7@0mi@wihs^@TF` zN7;P|A~;njNt$k;e&JCMAp~|c3 z)>Q1&^BIE|fKc=1W2X_B1?{!YV^|scI;47NcsA!}Bimu2GPUX?tfo?3bv}Kk*meaX z2^?TwH?rTax#G6wMhYssiAo63z%!YxWl5QZC}Gb@(BsFxu5gyEx&|5YE}oxPbX$P+ zt_th%qI>~*TR}S^I%)XT9iFA|ckw4V#ZH4WLJ&WEpK<&h#Xf8uL=f_he$h2I z_P!lDdPt+x@ZVkl*X#|V^VD&q5^q=zNY9Ej!u(o^*4NJVpIh*?YjT(X{vSG{Cy#!G(jxRa}*RX5D z5RzAjcOEz2nAPIXbTFBm57r`c<&%kGr<@j8()k)99rGHg)IJBr8Q^B{U*Iu?1Rz4tq$kMTY zg{x1JZ+QV)C8J2rdMj=2&hzAv$GCgj{6Q~KgJNf+#o`Zju}@^5T~v$n=u`vW^|rs! zW1u@9C}1|3jF;PT-O;zLVa^yeR5I>kBXQDv$Bu2lL(H@_jy*OGa8bs+&v@=cdfr^3 z0~x1>KVa)?$37a*A{iYe?3{O6u}MfMRCq%!WXtE(I5f97yRU*6p_|U>zs{rt#5W5^ zkxhgYH#L{FBS?WM9PW^}ZT@_>zO9&imVIefias&ROsI@=jeGKY4%_F-KT;8EC#oNF zojoJoC|^o>a~34gsHyOG%5?LxnS?Fked)%S^<0ivy4JgIc4sG|z1*{p#(q@=%fAGl zP>O5u(o8ZAc}gT1lyXc$`lzGceU&bFl*YYaWA-f^xn9I4eecgD9Y1eftM zN7bdt${OptED?85rhn!ynrP|rGY`9%=A|n9vpco7Zp=j*#Z*R%#BWGDh99mpJTs_4 z$Zi|%L~s|{VP4;;sbT~hHDK0Qk1Ef~6&tJi#Nc53EfY!u>jqQQU_YJ76*E$&uiIm} z8%Ky8Z~EME&JVnr;8Vy@cQe)6t!vh4kS8v(;t%XbMFI!S&J>emD{k7Af>j5-M->88 z14{8db~!;_rmOVeQDL{$WK5yITGWzjbSLXoNWF}*0?!j6z2|J z>{;M#A^1|ex$}34p!oAnAXA`B(4CBW^R2n+i5k8#S=o-G9l_VJvVyUi&6HfSkiQ|* z0heT~8Wbh0OPR}Kb|uwwaVC$f=Q0p+Kz~Qkc3D_ z7x0#n0=6JWCmJ#zt~8w*CT4qPO)X?~(%vCT{V^7&Ap<0c$Z+pE!d9B^S3xIC#x*a0 zrG@(-$XSg`DAP$8K4|(c42nS{*O~JVcm&lZ+Cw1YM zbrF~Ke)C;P3(O=x7$Y(`lAl#{QVN3|D$om|w#n+wI_oKnxy2TcRYf`668AuLWkrr# z8h^Ur5URS8^tEKlZ5IpG{Qb@=2{g?YkP9c9;V_I%eTzD_dv^S{9lMD^@ApC4;8l$w zpk}+ny*WW37!YQ+Yj#tQ^6SG6u)vyLbCGykq{w`I1GMk9Gxkf|LEytVLmE3QGvDmsfgn~{f*vZ6bFu0S3zM!-7!nAsu#2Kf8U+YMi4sH57a$`xOTs;8$~vSHV&9- z4lP>idO&c*VJc~yWc9IvC$bJwE$gc=e`>L@P4U8|wuq5Zk^<8TT3t-&9VOL2%jCq< zY0Z?0JR~g>ZvA>R_-3=V{1+Z{oE)ZTQFBM0REj===_^do>{ezQvXn%XP$^9Jpl+8k zC#zNMH|?&BP2ohc?HyFs3+ft+wq3pL5OZy-#zj`sodA`LQm2t@7Pm%de&HTFEOj3; zG7oFR>X=F4?@w?SloVDj4+;Q_+BZGIAHEYfLu7Igjy2c0TYnYD7%bQ9=pidBG$|o# zZqZKeO=9GgrnieM`F7G|2&%k-)fG%{bK0^@62g7AE>BT(4=C8CH`@8+&`%UxUz?Db z>7(L1{C|W{d_rX61`eA0l!QTgLL5}!#=h+uhY%YRp6BC6ke&@mQ*`KOogY?y?-V9* z8%M&LouXdA)_#Y*#KOs^_eFoi8`5G(@@f-}%RXwS^%)J+sl~gF+>QK@FP}@ZON?>7 zS)co4GltRf4);wkp)=liX&*+KNXr1P8S}@}MD+Q^nIw6ql9{yR$_!1SjmVHY*akWN zv`s&u{7mr`>HXbU50fn2w5{*3>tu{fpb}KahbAJ2RNm+b%tNlYd*s`e>U32edS?s@ zaqvdYYhtJpeU6$wUV`y*eqMv_Mzw^T{7ps;fBJV1?=LAW}VIBGZ z;-y(cU(mBn%YHky&1-8{wI#FT%nZR}L=PVRCREH*}} zvyeB)(@aLp#Iw4tyhM7vZnU z#l;-WWL4=DxA5K1dRvYYoG)5XVo8~5W!Ug6w)cIi}-fN+eaj6ZcBYP6J zx-;kwgPb`$Q@m>g>e&LJFCGm?$B7IWtu2m2nbgn~`%2iwtKM_?!^u+ch2q~Mc)S#+ zO@Xknv4jb2j?oWsnCePI!~qwd+OOKOSBqyM7Bl#uSI7;d)?C$NC%DuH&N4yO_Tbjm z$c&l@Cv>->4s5al86l~Nm9xXiIY@K+Fa;m*B&_H{(zNA2Ba3xlv4XkZxN96Ht9x$D zwq+rj%J-s`#61`KHQLVwx8gc4Nqv8J~E5*H2C1+gbt*4jkVM<)4}^aA11=<#mH zcnh}skZ91%?_{sbd0)*9+eBG2=y0agcHFKr%Q2@}tdI5`O8Lc^hSTKmAzJ<>stZ9L zV}0FFH}$!TRW7-M-ks0#k^mH5A*ZRkL8TT2+$Jyh_HinFMRj(4U|Iwl zy-W^-OuyH;>BlR0-g)W!^AX73lRoOtEmgd=pjYlsUt-=hpLwD3>ofk-$Xog8dpB9k z!z|gS_2UoK3hVABNqI}YisQ6DB^O`{8z*V1ZoX&zerDrOC$EwamN^=TM)bQ?9|9Sy zIDu5;+dj4?vqf!Q>9Ed!i@jC$3=sfFkU2MJ*vyCEiuWva+qtt)*ZA*AHP6;ugAjHhIds+oA9olmJvu7-f-R;y zbJ6w*B)|mxYlaDH_UWwua=98xEr7i%BYZ;q4BlyRMI~;1pP2xOjn&=d`Shz8gIqJ3 z*f@1JM=u4bxkjGLdO35W{u-qY`w{as$6sP%4zyw$av1i#5<{-aO%2OM zR9a=o_+H|uYWvV?o@K?Kcs2JlY2JR?b@wfdoD^w(D#$x%vc5lQ0bFGd)s*n)H66ss?VXqKb&78tOHknv%Bho|}F%h80m0 zl-Ve9pZX92*-p4Ny-=@sM(w`26DYR9i+$5`>LF+JyuDatAmYnd=9Wmm;cK~u zQdEsirnMabuG%@XKmDrR$#* zQKQrC1@*OOp~nbX{z^KhyQLO30|b!uWW+LdV>2|w$(I?(@ZgwD#zoKXmnFrHgHsjU<%ax*!G7F3p4dTVAAOQ4yijen#H=vKVP)JaFaYeZKK ztoU@9c{xzIBCuW%EymHWr+K)%DIua>wvvrP4%IX4^VY;Dcu zU2<(M+ZWt46h5`<4RV=uT1PVOLA*SgXu#F@M9dQLxYrgoQoz64c&yHF+$ya0^2+zb_EKQ?pJHW{?YJ$ydtOljQzKa_BkeHYE%^`5;%Ry z+nbSfU8uI&o3RA_k`(`O=55EpQ9<+rSZxjq_?Fl2UYDN`9PCI9o^T@1e)lP^v-6Bi zm)FEXuvX=m?Qm$|YU$=x)Vq|CZib&$VzA@YUgm(90L9s7^e#^NZv)eV5o%sueof8_ zESR9jg8GaxiQP~mvpdNQYZ*c2+>tjwR8C=TRVE3xqZR9|{_PWHU`u&_;Kg+!Xfp#*^EeDv$cEtQ%1BFuqzpJt$i6nu%%^pHYNr6GW+fs)vSHoJz4b$U*9*G zf@Jn%AsEzL8hR?xx8G-Q@t;5-aCedcU-C2KH&vUJ!G%&Q)tkd(&wg`HaG#&TY@kR* zxt%-Fm%#{n1}><{t|GWLAflJV3fWecR>trbkC>soE6eV+jH`*jPN8EiIK%DfZj|C}?vGaC@oxDCHzAu6- z^MRO+XzX(rneX-px_ikPZ?Ws;q(85Z+caM^UMLt&2#Y{nY`C_aK;Sp-F8Fd>(zx{1<@^|i?h43Itr+gQ>&ZI|QZG^r5c@EN%-tSH6^lLx*T`75ur4YZ?bg$tf| zZ^^x%XG%7r`O(-vu<(nNm;1QI*TuQdiFekO%@jnc2i12jKTt!!?^<$7bw3kMr_7bu zkNAXyt9}kbV9z)w>a;)T5b_;4bKgi2c^Q6|{E0I^!mp1$Bl|a&XNfcu86V;gA`&~V z95^uDE~X$?CyT+Gh_k$-93iS_P zP=B96StBLu$N7ABiwXM`SZhwWcB1c1?)lv;{e;3R%lUncenj!j`yv}*7SJc;?Yu3s z7+lEN4S%$VA`WBhl8KQ@tl@m&a_N+U@mFHZ=gf4RpjDhR2bYb#;;>reOXnB<_E4zQ zW{(q7t+qj1Gmx8_eaM8n1V;S!J3(%z*caZe=_2@aN!@B7HqsXmmJ~1V zB*CL*0*O@Rjc1ENFH^FvWK%jE-=aIg%gm2OpBDr4GnzNw^-nB#hqkxWYQ+6)uo5fp zeQ1aE-H`)YWMBt0O(oWIxEt%0t-od7BD9T}J)Y5aeY1N!axOSp>)@}RNcE2L)B;)O zj2EAjkVyWwC-E}cr$r{H!o4#a8FgL6(N#C-7t8j_S(JhLqvPsHO(p@oUW#{w%k^9uZiYF|I}RQCb${_bJ_+aeNo7O5 zId8HvZESk4ot7mpsmr5vGJ>J*M>&6>MB;F;s({RS)OJJV_?QuxPMAwRlr5cix$RSo zd8~pz(I|Oa*AH8K+aKQJ4*PIlCVR;%|3k_^-n9~YtC~{QQeQKjrwRP zupfH%Inxzqy{tGVd|HKSeM=NTdk>3+lZojkD6x~Nla z&D58B%VVx254peVK)F$4R_t-62Wz~kQg_7hvzqhn43GGm8T%wYUhcftx{J5F-`cB8>GY|Uys9$L!vWVpno4#pdhm+W$v*^tPu4=>gE`8QY4?GKfr zT5pOrj`OLOjwhC1hyX168Je3JP+qyyg1-=R6j&Gd)xL;g8FBM_ZFvX<vO7p3-@5xi4aD?+ue|Ga6sL2-o(HW|Z1yS5W-S-C1s~{XEU* zB6dQPe0xK0^PKw!m?+tMMJrjLzhJ$A>+0Hcn4iq+~8n&+f%$w6yq81wBAv^U=1z-y@2ao z9)e?^(nXG(+wle%LcV$PFW{|6o~7jbc!UvgmsK9Uegq&&GNSqK%ey%th62BjMhKms zZPSnD4KK&W9pfH+)9S;ozTNTMF}q%xZH<|wM*!q$-*e-?$nBJ=8_T=f(sFxWc~VKW z#b&AzPlNvKBF{6@w#I1i%T`B$9~kppNSFsJ=+yZez|OFDK2-3e@=S6xsAacPgt$>@ z`<$1?Hrh`E(0!MCvViJC>!xrBYg!bF;i)1mUFq}#;hi=Md(2*Pdy-7 zxv49sNA!xWoMl!$dra< z*&nhyZCq7exyznL$4U_26X>J7VO!_LMD5E0M}5n&6s*9LBRX?(8eIX>iQ8^HSlWS^ zyjXx4mH{$90eMRH8yta^X-f-S`+0ItL1cJp?I&zAIfq29M(*Pl&3IvONyt!4{jA>Z zMJ|2a9*Vj4`TO#ZEHS9^kBo*!w4j+s?lk4Rm$***UzNA^T z$v;rxuZoYmXfn$5MWOONZOjl)*)@$$PPqGGTa0_KvRj_2yLpttq<2AHSjq`55&rv- zHuR&)uY{}I-ZC$QLp9}|0zBo_6EAv5@(G7OVQp=@q+ZZLY>GSH&iHqA-C3bS?K)%n zJ2P5N@;3&NvOJyOUc;$jaIX`F?!o@?0O4`{tc}u_%JP+MN}*~Uw6;`XULw1RG}y@r z>7Pu@3|+;+?%n0ev`wyo;6g6YETc2K1wIs*|dT=&LuKs?BaOCk_GD62_Y%#x34& z6N74LsXLL+JP=yHXZZCIFWUPNUN$Krr_B%iffCWUR@45{Hpkv2y=>{v+C;aT^Z8&Q zQch~0W@TBE-3<}104JTbPlR0#NiHD!?W*b8bI{A66FJIoN$+b?zG0)j&x;*z+E(fV zh7iEaGLcx{;NCGxJ#(`{bW0ByVT(wY`O5Q=&=ds{J-iP<5~&F3=bli~wr$Eg{JF1X z_okxn3Bb?YcbAL!(pkZju)ZFvZsX5*M@WWkT)5d`wg{2yEc`i=`svYk&Fx}V7JifbBj0oxUIQLX9r-x?&aV3xuJP4 z;^>fgP6*3JE_;_KmkZPWGDZK<+R)tfc}$e5%K^`9a)K5kDxk1KksJCRz=x!{&QpNTt>kWG z42UJ0QEug5NJ$MNA);bEv}vM*viLf6`3X;AJcdwrr}paYZ=2%l+33kPggdP)*Hy95 zV#F_DF1}!QF8McCC5oH|Kv{j{b7=dHVrZ=P+}306O*5Aky2-O)+s~(1!O!+vvFe~b z2cEBahCR{W|7Te~eR7>!G%zH{@a1ykBPE?Q_Kdx(z!QETLe_iou&I5B@FKCa?o=eE zrVcSN^2HUY(+=?&!R#F05hmxF-Wp<`zGD5`@9g@c@7mnr_YQeRCfip`j__f~lKq?k zAvr2%X7`2pX18SUfDC!g*k#WPo0$M66Qh|v3}{Ib|E-88Lt2J|y&AFN{hd*-YhOxX zQp*Q7DVrydPpStXcO?`e#|134vfztp^+mc5vYQ91;sz?;t2F?k6cZO8xQpYP3x@FS zFW)Sc-29epy|Fw*xfj9p$K3~;1D;r6lJW^~|KahvLYcKs%Y1ZPW2~`yvnIjea&p(x zs|4j#VLZB2P3vgu^ixBw2TBYEC*J@n1AxXj|J(H5hDw+hsX4L;lwU5}S2x zuO9?(73q6pNESK5uYkZL_XW3Px$qEef+~%cif|a2u)a?t@01Y;<145;$17o&r5+-~ zW3z?h&j#XJXJBdtctJ7Gla9IK`2JvHUC+AH_qjeN;?jr=JghzX-(G;Uvyp$W`k6QY z>AHG=%=SfGk1#yCjAC({Jw9benY)B9A!^@p#1$O zSW4P+@dKgp!2p(lq`vapkPa@q#q>!2#c1Lg)(+C?))2xN6&j%~4`tB8!RYjKu~W*w zHqG1n8&22a9gINpE8|&LF?-Z&>wl?){BfLkzQBPidE4pPR^vEnqb?G##c zguowuGc*8k>0nNq0jx>kTavUDGM~K0E7+EIt|Q&-JIl81p(oKJ_9<||Qz&O5F%0E@ zVjhigWmvgCmB3EeBD1_LaM{8Om2Tnh~;|9Gt~n%b%r{jh4z!j zV<0Y@d?$mDWi6cFYIx-oQsQz@+GTc5{!&nAyDG3yHFuyh+(5@#1=Z59zRdb|3!|VJ zeCx~~XM;)s)(INy*!w#HZe}cS{%iGIWAwxCJf2Ve#i=Oi_aUGe%O3QpxXzZElD22S zyfsFLuj?sJHqUgwieG#nYO5KSxl}U0C%@GP6i2ffr&>{}bgJ1lm2<8ck|OIDFsn-ip0)l!!PHM90aYR|iwTr^4q zbb@?t79XGyiKd;+#4pp3o@)EAR{T^RljcdsPSbMX=0=jfz>wV#zH2}Fj|#6314%8s zG3@p+0BkOE-HrEEl(8wl`)vW~9A<^qd{j|=FV{h(o*(~IBvApl0^qrjSo(=f{q@aJ zJDXB}3=I^f5W)ru-1l@){Y8_r0PMYJP2zj2o-v0{IRxvz*f06|BK`2S1N|~!bL#KC z$NyWtSl|%xnkD1?j|Iu)n%|+=kV|@*+^T{<1CdSxZ^r2SOXLL9Mos84TV+OV#ta)J@49l^NRh#QV_`@6kf5EUn@n_BLV19@Wm%v{Qxw z|0}*1)*J-1WR9*bDIW}Ma%Fl7tN0h`0XA<08;&&njA4Cb+$$aG(@-UeWy~&fj zhf*(Eh4=v+l6;%-Cwq%&tyX&8)YxmC?4;D*aIW8*pHO7NH9n3#tbg=KRgYL0d@ghB z@m@j+kh&hny~FPhdX&jUFgsG<$S|P{b=>W^zdQfwOd11rZ4I=l@9-ygYyHlrdlZsU zA$bqr!YQ65#qF%_>X(XQhmJ)&kA>9r%86F$d;xR$DcP5pe0$nI*#v|Np=ypd#DTq(3fz(yMoCpwK0dnN zhojq5xx8J6O@g_3zKF-i(9zEhev03=Bb02F>HsDKEV_>?=nep@rkZcQ z0vjJYf91e8X@A7X$JCn@(q~^j(aD>0Z*loTBL8AwcP}{|%IT&F7w+<;8uWkO;@K9h z`N;hrxjl<{VeRkzx|dJdv1f{8GbEtg;$3HnGnhv5*=>I+f1>_J4}p9fu=;w4(eFJ# z6^zCmE6*w`VKyA+v4Zi$&PWr}$>RU~+A6h9TSH-MFemdDeYaLD@XotqDEU_ZC&`Hn z4~>6ilrH&IP_^`jUBoc8iSVz3d;v7t18UJ`dj34X&+S9E9JHoK>)zcJ|Hn6gr!3p6 za6zxg`q3Mmn94fNQyhEMaM~LG8e7LU*DB}yheRMDmfv4Ke5TY07xdC8#Kei~sr|e= zNyOkRTHahK>JN5}?M0H;Aa{#^T`2SODAtr0DG(2Gs0Lq8Y!X{eg&n=D))FV|V{+Dd;=EvzZNc{@*o!=jOQIgl_Gxm%wZ_$rSG-{piiq2YdfY)T#~ zo;k1!c81ScQP>QpRx8z`X@66l;?^H; z2Uy#X?Mb%{{O)FhF+=6m1=OCBI{Ikb0h^DUZx&sTwr zXXT_flT=S_-X@O?HY<2!&3bg`|L)yOUiMHR0?WVNFa#orl|fRUg!j?FhoWGYF(fME zhGB7uCOT~-=C@!}bOhh_K8v$P97Z2k#G`F2B9YOqr z8Y6Fs-sXdhj{Fm_9+H=}q+_8o68zD}kz0N;GYMv8U+^mFg8bkDu*+<{3cM_pIpF#TETiKQN zK9g%Qf|7q?WPqze5j*khMYeMWOd8|%yr(3XEgC^P-m9ZOj-oW(OV@tPVTI*Jx$$W6 z08Bc#e4!1P<#USDHC@tK$CF^Y_F|V0+c&ShdSNzfFSe@;`yByoOwyJ-{3p2yHsPXZ ze8H6HY?$4I`4OZ@Vkwi5n`cXJjHHiQzX|<&<@*y>v`+MV!&e}x4_DZWALru&_Wo5& zvj258<&~aT=35V?&nKeA4!^t!GSyA$@aU+BE7;wT`wZ$6dG$vk>(>BX2#N)zqOD#W z0Z~rP5Q)TCPACy=vWtT0AsbqQwRF&CJMdtwX52uId|!!4%a;(toF-Z<;<_tje$X~# z8;iDq>sdIg8TkwA2yGwC#-f}}hyB79FM=ox7M!T1Eh0q%qJPZZ$@@6lXmc;L5MXS+ z)*?~2ZFB~%_DOA zcggtgccWHdk4v@x+4ZgYkS@)tn*Y}$wqkge{8hEh@XD}cfWfqdsb){@$~V*=Zqk`?WsVRviDM@QTmI8|R%N$`dM`RDGO<6JJ~ zWOOK~FPB|2?p1b`X%4pVH0*gWFiB&Fx9{KwEP8E1SfgGyx7`-5t|WckUPMzv%8XY0 z+ZkOK{?vfv0dL)65aqwO9yCVRL|laeA;ZR0PTgnK{QSI9E;zvfF{~F-2uDg!LL^0Z zJJRt}3W0snKYIHZ)jK-bF^o;Buh>9t_iLzNHnpD>ApHp;Vz+^(KwXH*=@5as5 ze@i)E`PQ*R_KT*Wlb?DWI|VOF1g|-nkLh%OH#%__H`TRp(#^Lvl(~v8dt4qkS4E!Q zaqml@%@O*rs;+V8Jx9|Q^u07UN?#IAQ$ap3__H!Z5Jr?9miNpeTr>OqUP$u{h)qmi zLH48*q&KT9$jteQFe*(HoV;b8(xX};hR4+Ao&ja{cPEB-R-xxQKf+l=Qf2MdSYX`? z&vrz`(UCjx)<%@cm9Ee5sweNDN{51Uys-rB@rxlL)AqEXnT0nplk^NGaLFd^^IqLz zFCb~Xqw8P1ZDt2s`OcZZy+%W)h?5P$plQG zbY3h6fNrO3Aa?Sg>r4PV4Z0&PJ(u-1&u8q=T+R-5WBPFStqGasfHwQ&o<<4h3b*SB zW5NDf#n)ZA*s>vM){vQt?@zPc#1be~P><|w=oU8t?SO{pmNRy7m7$Ju%}=05ZYoT z)RXK2b!Scc$cviOD7+P{wyyTDtOdC^#-HiQECLn%175({r6pL z>WFaNno*R+M$^|jdXRh$`?JF2e?`GgsV}sRx4vs?RQB&Y*%8O)C~t+_?l}=i6r9|P_y%t*j)T@&)PPq+4XlWR-Lq^51;5`3LB-oU?Gs*uLkj1twtqZWP#<@nrn zU6ga{5MOz!?T_fP4!|P%mipljPGqsKS?|O7x>vqRk+|n`u+hE z_&iFly0`aS&;00un;oL!?NR$`e=ku1MFsz4r6k+FkoRMb^MtL|= z6AVmmjS7Xb5A~o?6|Q_gjuVv zXJndLkn%fqF)igi!}Q=aYpK;M*q;=rRRm_XROCLi6uy4et52HLJCkt*WM3tYuWGRl zN~cQpoNn@RWSz&=XyfY&{=2RWd_<=blE}_oXQS%yP?e}&aOj?NF3PBtNQ$wQD$5gk1OTr59Po);)2}a7q?HYnMEDsW3 zo%F|NMSqO{gIYniT4nslWHyPse-A6PR4&)W)QILbUd^;Q3*W@SCenYd{o`@08D;kM z1pfHn-A}pWswzV7;Tm%hiE3);eU8=scOO@H5!C$=XMXEMnxWmRL&sQ<#bl-bLPQUs z?Lb`rO!K_*)fGB+PCn1^sj`h5boDkrIXOq9T_?nc?})* zh7FwLsn=F!t~Gei_=etv&AWyZ>ED*#R66?=h!QV{w_Iica7)~a1anc+mVn42c$)uD zH&_0bWVXi5aVE2JQd=gQqB5oOP7{)t4uUzQW2RW$!E&RbGE>1MMFL?g@6Fxor3_bW zu?>;TTuQM`$4C)3G`DdfCCeQ}7KM8-yLbMDJMWM0`+nZfd(Ly7=lMS0?{f}jg+F9v zqFbNkzG<9q&qRjXt;B~Bwy%t5o?A_i&J{A{K__=S@4vgn=b^`=`#jbit?j7?(vL+W zPqLE8g)3%It-=FYd5Kp_cOcYno9Ot+I&!?2Wxq(u0qOnBnGa~~AF-PayrSCx!ix*5 z@aEWQ+-PoldP=xw#$;=KP1yUp92iGNV50kJ)cQaQw}?CNh#f3rA&B-3oXUWaA7MRv zi5x_xmt)o0&GcVnjy#mKndv?rtlorf)hWihppKt~G=ZRwIr!oqPkgQ3#=L~`LyypG zmdspgr`JrI{z15hK@f}J&}Q}ZRVa#Fys~QRK>D(x;^kR0gSZ`DA~8O7m~Z_vRN95T z|AwpzvG!$ECocD0w1}m?YVOq^c^zE_P!_o8J(&tKt%g9_H8p!hxtH zl2nlm55fNP89S<8+i5NJ&2nvFHmyvR;}V8_Ryd3oX_e#hs`^MfO^dJQ9gtIauAr)z zQDr9qe7AJ-Dkg!e9~a-l<*|M{FUBA8BlBwH$=1-)$WGqP6xX`KcTFC#;RzDel%SZm zC)q75cpX#5%vxP`-K@WSeP^{TblR?f@Er&7T1)i~LZIY5 zON6!qvROwGlt_LsI`x!(hOm}&1FPM(R!G^!bxBV871QOw{(u=ix8{9X+NrqFeDO`q zr_sY@Q;9ah{*-_=)0$3NmF$7}@dU;vHz|-4xJQAQf zhpOkIIYw%u%PgcuY}FWH!@1UJKthgP3@yn|B#Cn|4*0EnsuCak5C@etHQ>X4+LCnM zxf@y|9hj&`W1~hOWacCD(n9`f;si}pm%%67pwv~p29@LkAE^U(b}f$SxS>KCn8Wj{ zgMBRHJzlThO~@T!kHT)mNp|jb`AN)-Dlaan_eKod4mqbGo#o_+e*IT1<=DH)N}qZZ zt~hGutIP@pGB|+J(j7Esq2!aGi{I*uKbfI-M|$qr{*j z5|YB7r>Nx!y(2N{v3$9bFtdj@d}@%E?GLv2PO_E9d%HG&V5D3$o-8yDfOS)XK zZU+Y<=9y8&vhj^GbJ5PDgB9~bl2^i)g~=+<3pq7K!5o`)M=c-=uvxbh{jBmty^3r` z*>^i{!VkQfZ?QCqLEY}E6nyPYy;iBcHGd)htk8+HRv1LvAb;JS56PRB-x%7EKpirf&hK$;D?2uGGP+=V_OKUF!jW)L*9DIGhl3g2 zl>XcDOxPCMI7j2kNBwR|weJXFDvNAhTFEnM0X`k8N(T~^UHe-*<$^G+C|dDUZY}3( z&OJACe~n2bwx3t|#_Cp&PSv6>;DrQw5={o(4GU5?I=#W=lV#j*?cYN7q zaiSohFG}@vn3SgY9%Z%^pNnAAVfzR&$Bfxq@$c${bvpPNi?( zd9vB+-Q=4L!jTlNRPqVd!Jkf8R)HB(-=Xp^l(z=J{A6YbnlnRimn{>hGYm&(L~`}Y zhSeFOkB7m@tDn)k%(RgRedKw-&IjNfU$YJIEj}k@h zS)#p47{O8bQg(TJ$OYg|pn7ru?178^f{Nc|si+N0x-+UXyqWLrmYnMImY<+A|3joto zY!=6Z_*8ubrUI3!uY@agyF7}L_NJFEVupp{{EL4)L&&FG1{d$ X+N90gKI;HIaJe1u++XN?;_`n06AnWV diff --git a/docs/drs/umn/en-us_image_0000001918683154.png b/docs/drs/umn/en-us_image_0000001918683154.png new file mode 100644 index 0000000000000000000000000000000000000000..fafc744b14a803500f5deaadd390d13fa006d416 GIT binary patch literal 547 zcmV+;0^I$HP)Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!~g&e!~vBn4jTXf0k}y-K~zXf-IdRa zK~WUPzcUG0A-#nK8w({YtfVX~tVoodwZF?kDRvgJ#|n{+vVF0TP^3JsX6Br^GmV*h zU*?C+d^YFYb8lboe(yPXIG@i?xC4(O{yG0xc)#C^>^3YPZ$6)6Fc{!?JcPZ@p7JP#bOb`V32beQsLEVg=Vt}o6UxNK7S=J z9*@!M^?0vZt-@}%i=Atv9uJ2@j_GvzUG&Z4L?VGmBm&bkF_}!bCPOMrBJ@S!aG2Ni zdL6Y|4V_Mh*YS9q<8ry=D8sTV=$eLM;BYwbnmqo<<#G|(SERyDr<1QrUXwU=K`a(S zsZ`>9UDr9%gQ}1Uhe9Ea)9I9>-|t5zlYz_S;x)A)L0+qn3P+<+Zn4E;f%SSVs;|su zGi){+_Px#1ZP1_K>z@;j|==^1poj532;bRa{vGmbN~PnbOGLGA9w%&0Z~arK~y+T#gnab zgfI}r`(Gmv5itlv1O|bKz?`T+U?UKi6BQ8{#EA$DA|fK@T>`llj*pwUcBXG;XCQg| zTgYxc@W=WepfwuW*zk6)L!cccsv}9(Wvcj>RuoxbFn$jfVxHIO~jc@SbLUgQ5Naq zC{BR=g*XENmnRL7Jb+#T2h@o(kPG^-vMXy`BYZO+ao7|I?klFkq2Jf9fG@^ogkak< zIac@pCS2x^R!z~(JTh6U!^*LAn@wKUti3BBY=?51F@}0)1|PDj2J>G>N_0=QHPFd) z7bM;sQRJ1xuuQN6WR-(X`w2e#ZP5+T%iP>;pgt)?OhMztySqi=wmPx#1ZP1_K>z@;j|==^1poj532;bRa{vGmbN~PnbOGLGA9w%&0Z~arK~y+T#gnab zgfI}r`(Gmv5itlv1O|bKz?`T+U?UKi6BQ8{#EA$DA|fK@T>`llj*pwUcBXG;XCQg| zTgYxc@W=WepfwuW*zk6)L!cccsv}9(Wvcj>RuoxbFn$jfVxHIO~jc@SbLUgQ5Naq zC{BR=g*XENmnRL7Jb+#T2h@o(kPG^-vMXy`BYZO+ao7|I?klFkq2Jf9fG@^ogkak< zIac@pCS2x^R!z~(JTh6U!^*LAn@wKUti3BBY=?51F@}0)1|PDj2J>G>N_0=QHPFd) z7bM;sQRJ1xuuQN6WR-(X`w2e#ZP5+T%iP>;pgt)?OhMztySqi=wm
                            Table 3 Checking Whether the Source Database Version Is Supported

                            Check Item

                            Whether the migration is from an earlier database version to the same or a later version

                            diff --git a/docs/drs/umn/drs_11_0008.html b/docs/drs/umn/drs_11_0008.html index 7e65ebdb6..ea1bb194e 100644 --- a/docs/drs/umn/drs_11_0008.html +++ b/docs/drs/umn/drs_11_0008.html @@ -126,12 +126,12 @@

                            Oracle -> PostgreSQL Synchronization

                            -
                            Table 4 Checking whether the destination database user has sufficient permissions

                            Check Item

                            +
                            - diff --git a/docs/drs/umn/drs_11_0009.html b/docs/drs/umn/drs_11_0009.html index f2469ed83..f91503b46 100644 --- a/docs/drs/umn/drs_11_0009.html +++ b/docs/drs/umn/drs_11_0009.html @@ -96,7 +96,7 @@
                            Table 4 Checking whether the destination database user has sufficient permissions

                            Check Item

                            Whether the destination database user has sufficient permissions

                            Description

                            +

                            Description

                            Check whether the destination database user permissions meet the migration requirements. If the permissions are insufficient, the migration will fail.

                            -

                            Migration from MongoDB to DDS

                            +

                            MongoDB Migration

                            - - + + + + + + + + + +
                            Table 3 Checking whether the source database user has sufficient permissions

                            Check Item

                            Whether the source database user has sufficient permissions

                            @@ -107,14 +107,42 @@

                            Check whether the source database user permissions meet the migration requirements. If the permissions are insufficient, the migration will fail.

                            Failure Cause and Handling Suggestion

                            +

                            Failure Cause and Handling Suggestion

                            Failure cause: This item cannot be checked because the source database fails to be connected.

                            Handling suggestion: Check whether the source database is connected.

                            Failure cause: The source database user does not have the required permissions.

                            -

                            Handling suggestion: Check whether the source database user permissions meet the migration requirements.

                            +

                            Failure cause: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the local database.

                            +

                            Handling suggestion: Grant permissions to the source database user.

                            +
                            db.grantRolesToUser("Username",[{role:"readAnyDatabase",db:"admin"}, {role:"read",db:"local"}])
                            +

                            Failure cause: The source database user must have the readAnyDatabase permission for the admin database and the read permission for the config database.

                            +

                            Handling suggestion: Grant permissions to the source database user.

                            +
                            db.grantRolesToUser("Username",[{role:"readAnyDatabase",db:"admin"}, {role:"read",db:"config"}])
                            +

                            Failure cause: The source mongos node user must have the readAnyDatabase permission for the admin database, and the read permission for the config database. The source shard node user must have the readAnyDatabase permission for the admin database, and the read permission for the local database.

                            +

                            Handling suggestion: Grant permissions to the source database user.

                            +
                            • Statement for mongos:
                              db.grantRolesToUser("Username",[{role:"readAnyDatabase",db:"admin"}, {role:"read",db:"config"}])
                              +
                            • Statement for shard:
                              db.grantRolesToUser("Username",[{role:"readAnyDatabase",db:"admin"}, {role:"read",db:"local"}])
                              +
                            +

                            Failure cause: The source database user must have the readAnyDatabase permission for the admin database.

                            +

                            Handling suggestion: Grant permissions to the source database user.

                            +
                            db.grantRolesToUser("Username",[{role:"readAnyDatabase",db:"admin"}])
                            +

                            Failure cause: The source database user must have the read permission for the local database.

                            +

                            Handling suggestion: Grant permissions to the source database user.

                            +
                            db.grantRolesToUser("Username",[{role:"read",db:"local"}])
                            +

                            Failure cause: The source database user must have the read permission for the config database.

                            +

                            Handling suggestion: Grant permissions to the source database user.

                            +
                            db.grantRolesToUser("Username",[{role:"read",db:"config"}])

                            Failure cause: An internal error occurs.

                            @@ -125,6 +153,29 @@
                            +

                            MySQL -> PostgreSQL Synchronization

                            +
                            + + + + + + + + + +
                            Table 4 Checking whether the source database user has sufficient permissions

                            Check Item

                            +

                            Whether the source database user has sufficient permissions

                            +

                            Description

                            +

                            Check whether the source database user permissions meet the migration requirements. If the permissions are insufficient, the migration will fail.

                            +

                            Failure Cause and Handling Suggestion

                            +

                            Failure cause: The source database user does not have sufficient permissions. During the incremental synchronization, the SELECT permission on INFORMATION_SCHEMA is required.

                            +

                            Handling suggestions: Grant the source database user the corresponding permissions.

                            +

                            Run the following command:

                            +
                            grant select on [dbname];
                            +
                            +
                            +
                            diff --git a/docs/drs/umn/drs_11_0010.html b/docs/drs/umn/drs_11_0010.html index 8110079b0..5c79688e6 100644 --- a/docs/drs/umn/drs_11_0010.html +++ b/docs/drs/umn/drs_11_0010.html @@ -69,7 +69,7 @@
                            -

                            Migration from MongoDB to DDS

                            +

                            MongoDB Migration

                            diff --git a/docs/drs/umn/drs_11_0436.html b/docs/drs/umn/drs_11_0436.html new file mode 100644 index 000000000..d6a87e9fa --- /dev/null +++ b/docs/drs/umn/drs_11_0436.html @@ -0,0 +1,417 @@ + + +

                            From GaussDB Distributed to Oracle

                            +

                            Supported Source and Destination Databases

                            +
                            Table 3 Checking whether the destination database has sufficient storage space

                            Check Item

                            Whether the destination database has sufficient storage space

                            diff --git a/docs/drs/umn/drs_11_0226.html b/docs/drs/umn/drs_11_0226.html new file mode 100644 index 000000000..f24b34f9a --- /dev/null +++ b/docs/drs/umn/drs_11_0226.html @@ -0,0 +1,35 @@ + + +

                            Checking Whether GTID Is Enabled for the Source Database

                            +

                            MySQL

                            +
                            + + + + + + + + + +
                            Table 1 Checking whether GTID is enabled for the source database

                            Check Item

                            +

                            Whether GTID is enabled for the source database

                            +

                            Description

                            +

                            During disaster recovery, GTID should be enabled for the source database. Otherwise, the migration fails.

                            +

                            Item to Be Confirmed and Handling Suggestion

                            +

                            Failure cause: GTID is disabled for the source database

                            +

                            Handling suggestion: In the configuration file of the source database, set parameters as followings. Then, restart the source database for the modifications to take effect.

                            +

                            Parameters to be configured:

                            +
                            gtid_mode = on;
+log_slave_updates = true; 
+enforce_gtid_consistency = on;
                            +
                            +
                            +
                            +
                            +
                            +
                            +
                            Parent topic: Database Parameters
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_11_0228.html b/docs/drs/umn/drs_11_0228.html index 86e5f8501..a37f7b525 100644 --- a/docs/drs/umn/drs_11_0228.html +++ b/docs/drs/umn/drs_11_0228.html @@ -15,7 +15,7 @@

                            Failure Cause and Handling Suggestion

                            Failure cause: The sql_mode value in the destination database is NO_ENGINE_SUBSTITUTION.

                            -

                            Handling suggestion: In the destination database, set SQL_MODE to a value other than NO_ENGINE_SUBSTITUTION. For details, see "Modifying Parameters" in the Relational Database Service User Guide.

                            +

                            Handling suggestion: In the destination database, set SQL_MODE to a value other than NO_ENGINE_SUBSTITUTION. For details, see "Modifying Parameters" in the Relational Database Service User Guide.
                            + + + + + + + +
                            Table 1 Supported databases

                            Source DB

                            +

                            Destination DB

                            +
                            • GaussDB Distributed
                            +
                            • On-premises Oracle 11g and 19c databases
                            • Oracle 11g and 19c databases on an ECS
                            +
                            +
                            +
                            +

                            Supported Synchronization Objects

                            Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

                            + +
                            + + + + + + + +
                            Table 2 Supported synchronization objects

                            Type

                            +

                            Synchronization Scope

                            +

                            Synchronization scope

                            +
                            • Instance-level synchronization is not supported. Only one database can be synchronized at a time. To synchronize multiple databases, create multiple tasks.
                            • Supported scenarios: full synchronization, incremental synchronization, and full+incremental synchronization.
                            • Supported fields: INTEGER, TINYINT, SMALLINT, BIGINT, NUMBER, NUMERIC, REAL, DOUBLE PRECISION, CHARACTER, CHARACTER VARYING, NVARCHAR2, BIT, BIT VARYING, BLOB, BYTEA, CLOB, RAW, TEXT, BOOLEAN, DATE, SMALLDATETIME, TIME WITH TIME ZONE, TIME WITHOUT TIME ZONE, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITHOUT TIME ZONE and MONEY.
                            • Table-level synchronization or object file import is supported.
                              • During full synchronization, only data in the selected tables can be synchronized.
                              • During incremental synchronization, only DML statements of selected tables can be synchronized.
                              • Databases without schemas cannot be synchronized.
                              • Schemas without tables cannot be synchronized.
                              • Column-store tables, compressed tables, delay tables, and temporary tables cannot be synchronized. Do not synchronize unlogged tables in the incremental phase.
                              • The database name, schema name, and table name cannot contain special characters /<.>\'`|,?!
                              • If you select tables by importing an object file, ensure that the imported table exists in the source database or is visible to the synchronization user.
                              +
                            +
                            +
                            +
                            +

                            Database User Permission Requirements

                            Before you start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                            +
                            • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                            • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                            +
                            + +
                            + + + + + + + + + + + + + + + + +
                            Table 3 Database user permission

                            Type

                            +

                            Full

                            +

                            Incremental

                            +

                            Full+Incremental

                            +

                            Source database user

                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +

                            The CONNECT permission for databases, USAGE permission for schemas, SELECT or UPDATE permission for tables, the UPDATE permission for locking tables without primary keys, and SELECT permission for sequences.

                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +

                            The REPLICATION permission or the permission inherited from the built-in role gs_role_replication, the CONNECT permission for databases, the USAGE permission for schemas, and the SELECT permission for tables.

                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +

                            The REPLICATION permission or the permission inherited from the built-in role gs_role_replication, the CONNECT permission for databases, the USAGE permission for schemas, the SELECT or UPDATE permission for tables, the UPDATE permission for locking tables that do not have primary keys, and the SELECT permission for sequences.

                            +

                            Destination database user

                            +

                            The user must have the DBA role or the following minimum permissions:

                            +

                            CREATE SESSION, SELECT and INSERT permissions for tables, or the RESOURCE role.

                            +

                            The user must have the DBA role or the following minimum permissions:

                            +

                            CREATE SESSION, SELECT, INSERT, UPDATE, and DELETE permissions for tables or the RESOURCE role

                            +

                            The user must have the DBA role or the following minimum permissions:

                            +

                            CREATE SESSION, SELECT, INSERT, UPDATE, and DELETE permissions for tables or the RESOURCE role

                            +
                            +
                            +
                            +

                            Suggestions

                            • When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                            • To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
                            +
                            +
                            • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                            • Start your synchronization task during off-peak hours. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization.
                              • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
                              • To ensure data consistency, tables to be synchronized without a primary key may be locked for 3s.
                              • The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
                              • When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
                              • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
                              +
                            • Data-Level Comparison

                              To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

                              +
                            +
                            +

                            Precautions

                            The full+incremental synchronization consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. A single full or incremental synchronization task contains three phases. To ensure smooth synchronization, read the following notes before creating a synchronization task.

                            + +
                            + + + + + + + + + + + + + + + + + + + + + + +
                            Table 4 Precautions

                            Type

                            +

                            Restrictions

                            +

                            Starting a task

                            +
                            • Source database requirements:

                              If incremental synchronization or full+incremental synchronization is selected:

                              +
                              • The wal_level parameter of the source database is set to logical.
                              • The enable_slot_log parameter of the source database is set to on.
                              • The max_replication_slots value of the source database must be greater than the number of used replication slots.
                              • Add a primary key to the table that does not have a primary key, or set REPLICA IDENTITY to FULL for the table that does not have a primary key.
                              +
                            • Source database object requirements:
                              • The names of the source database, schema, and table to be synchronized cannot contain special characters /<.>\'`|,?!
                              +
                            • Destination database parameter requirements:
                              • The character set of the destination database must be the same as that of the source database and must be UTF8.
                              +
                            • Destination database object requirements:
                              • Before synchronization, ensure that the corresponding table structure has been created in the destination database and is the same as that in the source instance. If column processing is performed, ensure the consistency of the table structure after column processing.
                              • Triggers enabled in the destination database cannot be associated with synchronization tables.
                              • The destination database has sufficient disk space.
                              +
                            • Other notes:
                              • Cascading one-way synchronization is not supported. For example, data cannot be synchronized from instance A to instance B and then from instance B to instance C.
                              • During real-time synchronization, the consistency of distributed transactions is not ensured.
                              • Synchronization from GaussDB Distributed to Oracle is the backward synchronization process for synchronization from Oracle to GaussDB Distributed. You are not advised to use either of the two synchronization modes independently.
                              • The selected source database cannot contain tables with the same name but different cases. Otherwise, the synchronization fails. To meet reverse synchronization requirements, you are advised to synchronize only the schema and table names that are in uppercase in the Oracle database, and the schema and table names that are in lowercase in the distributed GaussDB database.
                              • Before a task enters the incremental synchronization phase, ensure that long-running transactions are not started in the source database. Starting the long transaction will block the creation of the logical replication slot and cause the task to fail.
                              • If a logical replication slot fails to be created or does not exist due to a long transaction, you can reset the task and then restart it.
                              • Do not use foreign keys for tables during incremental synchronization. Otherwise, the sequence of writing data to different tables may be inconsistent with that in the source database, which may trigger foreign key constraints and cause synchronization failures.
                              +
                            +

                            Full synchronization

                            +
                            • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                            • Do not run any DDL statement in the source database. Otherwise, data may be inconsistent or the task may fail.
                            • Do not write data to the destination database. Otherwise, data may be inconsistent.
                            +

                            Incremental synchronization

                            +
                            • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                            • Do not execute any DDL statement in the source database. Restricted by the logical replication function of GaussDB, DDL statements cannot be synchronized. Otherwise, data may be inconsistent or the task may fail.
                            • Do not change the REPLICA IDENTITY value of a table in the source database. Otherwise, incremental data may be inconsistent or the task may fail.
                            • Do not write data to the destination database. Otherwise, data may be inconsistent.
                            • Replication of interval partition tables is not supported.
                            • After a DDL statement is executed in a transaction, the DDL statement and subsequent statements are not decoded.
                            +

                            Data processing

                            +
                            • During column processing, the primary key, unique key, and distribution column cannot be filtered out.
                            +

                            Synchronization comparison

                            +
                            • You are advised to compare data in the source database during off-peak hours to prevent inconsistent data from being falsely reported and reduce the impact on the source database and DRS tasks.
                            • During incremental synchronization, if data is written to the source database, the comparison results may be inconsistent.
                            • Data cannot be compared during full synchronization.
                            • Do not limit the synchronization speed during data comparison.
                            +

                            Stopping a task

                            +

                            Stop a task normally.

                            +
                            • After an incremental or full+incremental synchronization is complete, the streaming replication slot created by the task in the source database is automatically deleted.
                            +

                            Forcibly stop a task.

                            + +
                            +
                            +
                            +

                            Prerequisites

                            • You have logged in to the DRS console.
                            • For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
                            + +
                            +

                            Procedure

                            1. On the Data Synchronization Management page, click Create Synchronization Task.
                            2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                              +

                              + + + + + + + + + + + + + + + + +
                              Table 5 Task and recipient description

                              Parameter

                              +

                              Description

                              +

                              Region

                              +

                              The region where the synchronization instance is deployed. You can change the region.

                              +

                              Project

                              +

                              The project corresponds to the current region and can be changed.

                              +

                              Task Name

                              +

                              The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                              +

                              Description

                              +

                              The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

                              +
                              +
                              + +
                              + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                              Table 6 Synchronization instance settings

                              Parameter

                              +

                              Description

                              +

                              Data Flow

                              +

                              Select Out of the cloud.

                              +

                              Source DB Engine

                              +

                              Select GaussDB Distributed.

                              +

                              Destination DB Engine

                              +

                              Select Oracle.

                              +

                              Network Type

                              +

                              The public network is used as an example. Available options: Public network and VPN or Direct Connect

                              +

                              Source DB Instance

                              +

                              The distributed GaussDB instance you created.

                              +

                              Synchronization Mode

                              +

                              Available options: Full+Incremental, Full, and Incremental. Full+Incremental is used as an example.

                              +
                              • Full+Incremental

                                This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

                                +
                                NOTE:

                                If you select Full+Incremental, data generated during the full synchronization will be continuously synchronized to the destination database, and the source remains accessible.

                                +
                                +
                              +
                              • Full

                                In this mode, data is synchronized from the source to the destination at a time.

                                +
                              • Incremental

                                Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                                +
                              +

                              Specifications

                              +

                              DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                              +

                              Tags

                              +
                              • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                              • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                              +
                              +
                              +

                              If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                              +
                              +

                            3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, click Next.

                              Establish the connectivity between the DRS instance and the source and destination databases.

                              +
                              • Network connectivity: Ensure that the source and destination databases accept connections from the DRS instance.
                              • Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.
                              + +
                              + + + + + + + + + + + + + +
                              Table 7 Source database settings

                              Parameter

                              +

                              Description

                              +

                              DB Instance Name

                              +

                              The distributed GaussDB instance selected during synchronization task creation. This parameter cannot be changed.

                              +

                              Database Username

                              +

                              The username for accessing the source database.

                              +

                              Database Password

                              +

                              The password for the database username.

                              +
                              +
                              +

                              The username and password of the source database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                              +
                              + +
                              + + + + + + + + + + + + + + + + + + + + + + +
                              Table 8 Destination database settings

                              Parameter

                              +

                              Description

                              +

                              IP Address or Domain Name

                              +

                              The IP address or domain name of the destination database.

                              +
                              NOTE:

                              For a RAC cluster, use a scan IP address and specify Service Name to improve access performance.

                              +
                              +

                              Port

                              +

                              The port of the destination database. Range: 1 - 65535

                              +

                              Database Service Name

                              +

                              Enter a database service name (Service Name/SID). The client can connect to the Oracle database through the database service name. For details about how to query the database service name, see the prompt on the GUI.

                              +

                              Database Username

                              +

                              The username for accessing the destination database.

                              +

                              Database Password

                              +

                              The password for the database username.

                              +

                              SSL Connection

                              +

                              SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

                              +
                              NOTE:
                              • The maximum size of a single certificate file that can be uploaded is 500 KB.
                              • If the SSL certificate is not used, your data may be at risk.
                              +
                              +
                              +
                              +

                              The username and password of the destination database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                              +
                              +

                            4. On the Set Synchronization Task page, select the objects to be synchronized, and then click Next.

                              +

                              + + + + + + + + + + +
                              Table 9 Synchronization Object

                              Parameter

                              +

                              Description

                              +

                              Incremental Conflict Policy

                              +

                              The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored. Select any of the following conflict policies:

                              +
                              • Ignore

                                The system will skip the conflicting data and continue the subsequent synchronization process.

                                +
                              • Report error

                                The synchronization task will be stopped and fail.

                                +
                              • Overwrite

                                Conflicting data will be overwritten.

                                +
                              +

                              Synchronization Object

                              +

                              Select Tables or Import object file as required.

                              + +
                              NOTE:
                              • You can search for table names to quickly select the required database objects.
                              • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                              +
                              • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                              • The name of the selected synchronization object cannot contain spaces.
                              +
                              +
                              +
                              +

                            5. On the Advanced Settings page, set the parameters for full+incremental synchronization selected in 2 and click Next.

                              +

                              + + + + + + + + + + + + + + + + + +
                              Table 10 Full synchronization settings

                              Parameter

                              +

                              Description

                              +

                              Default Value

                              +

                              Concurrent Export Tasks

                              +

                              Number of export threads. Value range: 1 to 16. A larger value indicates higher load on the source database.

                              +

                              8

                              +

                              Concurrent Import Tasks

                              +

                              Number of import threads. Value range: 1 to 16. A larger value indicates higher load on the destination database.

                              +

                              8

                              +

                              Rows per Shard

                              +

                              Value range: 0 or 520,000 to 1,000,000,000

                              +
                              • 0

                                All tables are not sharded, and each table is synchronized as a whole.

                                +
                              • Other values

                                The table is sharded based on the specified value (or the primary key column). If the number of records in a table is less than the value of this parameter, the table is not sharded.

                                +
                              +

                              520000

                              +
                              +
                              + +
                              + + + + + + + + + +
                              Table 11 Incremental synchronization settings

                              Parameter

                              +

                              Description

                              +

                              Default Value

                              +

                              Concurrent Replay Tasks

                              +

                              Number of concurrent threads for data replay. Value range: 1 to 64. Incremental data is concurrently written to the destination database. A larger value indicates higher load on the destination database.

                              +

                              64

                              +
                              +
                              +

                            6. On the Process Data page, set the filtering rules for data processing.

                              • If data processing is not required, click Next.
                              • If you need process columns or filter out data, set the corresponding rules by referring to Processing Data.
                              +

                            7. On the Check Task page, check the synchronization task.

                              • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                              • If all check items are successful, click Next.

                                You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                                +
                                +
                              +

                            8. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                              +

                              + + + + + + + +
                              Table 12 Task startup settings

                              Parameter

                              +

                              Description

                              +

                              Started Time

                              +

                              Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                              +
                              NOTE:

                              After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

                              +
                              +
                              +
                              +

                            9. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                              • You can view the task status. For more information about task status, see Task Statuses.
                              • You can click in the upper-right corner to view the latest task status.
                              • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                              +

                            +
                            +
                            +
                            +
                            +
                            Parent topic: Out of the Cloud
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_11_0442.html b/docs/drs/umn/drs_11_0442.html new file mode 100644 index 000000000..76e4b3c7f --- /dev/null +++ b/docs/drs/umn/drs_11_0442.html @@ -0,0 +1,423 @@ + + +

                            From GaussDB Distributed to GaussDB Distributed

                            +

                            Supported Source and Destination Databases

                            +
                            + + + + + + + +
                            Table 1 Supported databases

                            Source DB

                            +

                            Destination DB

                            +
                            • GaussDB Distributed
                            +
                            • GaussDB Distributed
                              NOTE:
                              • The destination database version must be the same as or later than the source database version.
                              +
                              +
                            +
                            +
                            +
                            +

                            Supported Synchronization Objects

                            Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

                            + +
                            + + + + + + + +
                            Table 2 Supported synchronization objects

                            Type

                            +

                            Constraints

                            +

                            Synchronization scope

                            +
                            • Instance-level synchronization is not supported. Only one database can be synchronized at a time. To synchronize multiple databases, create multiple tasks.
                            • Supported scenarios: full synchronization, incremental synchronization, and full+incremental synchronization.
                            • Supported fields: INTEGER, TINYINT, SMALLINT, BIGINT, NUMBER, NUMERIC, REAL, DOUBLE PRECISION, CHARACTER, CHARACTER VARYING, NVARCHAR2, BIT, BIT VARYING, BLOB, BYTEA, CLOB, RAW, TEXT, JSON, BOOLEAN, DATE, SMALLDATETIME, TIME WITH TIME ZONE, TIME WITHOUT TIME ZONE, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITHOUT TIME ZONE, INTERVAL, BOX, CIDR, CIRCLE, INET, LSEG, MACADDR, MONEY, PATH, POINT, POLYGON, TSQUERY, TSVECTOR, REFCURSOR, UUID and ARRAY.
                            • Table-level synchronization or object file import is supported.
                              • During full synchronization, only the structure, sequence, data, constraints, and indexes of the selected table can be synchronized.
                              • During incremental synchronization, only DML statements of selected tables can be synchronized.
                              • Databases without schemas cannot be synchronized.
                              • Schemas without tables cannot be selected.
                              • Column-store tables, compressed tables, delay tables, and temporary tables cannot be synchronized. Do not synchronize unlogged tables in the incremental phase.
                              • The database name, schema name, and table name cannot contain special characters /<.>\'`|,?!
                              • If you select tables by importing an object file, ensure that the imported table exists in the source database or is visible to the synchronization user.
                              +
                            +
                            +
                            +
                            +

                            Database User Permission Requirements

                            Before you start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                            +
                            • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                            • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                            +
                            + +
                            + + + + + + + + + + + + + + + + +
                            Table 3 Database user permission

                            Type

                            +

                            Full

                            +

                            Incremental

                            +

                            Full+Incremental

                            +

                            Source database user

                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +
                            • The CONNECT permission for databases, USAGE permission for schemas, SELECT or UPDATE permission for tables, the UPDATE permission for locking tables without primary keys, and SELECT permission for sequences.
                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +
                            • The REPLICATION permission or the permission inherited from the built-in role gs_role_replication, the CONNECT permission for databases, the USAGE permission for schemas, and the SELECT permission for tables. To compare content, the MONADMIN permission is required.
                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +
                            • The REPLICATION permission or the permission inherited from the built-in role gs_role_replication, the CONNECT permission for databases, the USAGE permission for schemas, and the SELECT permission for tables. To compare content, the MONADMIN permission is required.
                            +

                            Destination database user

                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +
                            • The CONNECT and CREATE permissions for databases, the USAGE and CREATE permissions for schemas, and the INSERT, UPDATE, DELETE, SELECT, ALTER, and INDEX permissions for tables.
                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +
                            • The CONNECT and CREATE permissions for databases, the USAGE and CREATE permissions for schemas, and the INSERT, UPDATE, DELETE, SELECT, ALTER, and INDEX permissions for tables are required. To compare content, the MONADMIN permission is required.
                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +
                            • The CONNECT and CREATE permissions for databases, the USAGE and CREATE permissions for schemas, and the INSERT, UPDATE, DELETE, SELECT, ALTER, and INDEX permissions for tables are required. To compare content, the MONADMIN permission is required.
                            +
                            +
                            +
                            +

                            Suggestions

                            • When a task is being started or in the full synchronization phase, do not perform DDL operations on the source database. Otherwise, the task may be abnormal.
                            • To keep data consistency before and after the synchronization, ensure that no data is written to the destination database during the synchronization.
                            +
                            +
                            • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                            • Start your synchronization task during off-peak hours. A less active database is easier to synchronize successfully. If the data is fairly static, there is less likely to be any severe performance impacts during the synchronization.
                              • If network bandwidth is not limited, the query rate of the source database increases by about 50 MB/s during full synchronization, and two to four CPUs are occupied.
                              • To ensure data consistency, tables to be synchronized without a primary key may be locked for 3s.
                              • The data being synchronized may be locked by other transactions for a long period of time, resulting in read timeout.
                              • When DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
                              • If you read a table, especially a large table, during the full migration, the exclusive lock on that table may be blocked.
                              +
                            • Data-Level Comparison

                              To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

                              +
                            +
                            +

                            Precautions

                            The full+incremental synchronization consists of four phases: task startup, full synchronization, incremental synchronization, and task completion. A single full or incremental synchronization task contains three phases. To ensure smooth synchronization, read the following notes before creating a synchronization task.

                            + +
                            + + + + + + + + + + + + + + + + + + + + + + +
                            Table 4 Precautions

                            Type

                            +

                            Constraints

                            +

                            Starting a task

                            +
                            • Source database requirements:

                              If incremental synchronization or full+incremental synchronization is selected:

                              +
                              • The wal_level parameter of the source database is set to logical.
                              • The enable_slot_log parameter of the source database is set to on.
                              • The max_replication_slots value of the source database must be greater than the number of used replication slots.
                              • Add a primary key to the table that does not have a primary key, or set REPLICA IDENTITY to FULL for the table that does not have a primary key.
                              +
                            • Source database object requirements:
                              • The names of the source database, schema, and table to be synchronized cannot contain special characters /<.>\'`|,?!
                              +
                            • Destination database parameter requirements:
                              • The character set of the destination database must be the same as that of the source database.
                              • Ensure that the source and destination databases are compatible with each other.
                              +
                            • Destination database object requirements:
                              • The destination must be a distributed GaussDB instance.
                              • Before the synchronization, ensure that the corresponding database has been created in the destination instance.
                              • If you select incremental synchronization, ensure that the table structure of the destination database is the same as that of the source database. If columns are processed in the DRS instance, ensure that the table structure in the destination database is the same as the processed table structure.
                              • If you select full or full+incremental synchronization, ensure that the table structure of the destination database is the same as that of the source database. If columns are processed in the DRS instance, ensure that the table structure in the destination database is the same as the processed table structure.
                              • Triggers enabled in the destination database cannot be associated with synchronization tables.
                              +
                            • Other notes:
                              • SSL is not supported.
                              • Cascading one-way synchronization is not supported. For example, data cannot be synchronized from instance A to instance B and then from instance B to instance C.
                              • During real-time synchronization, the consistency of distributed transactions is not ensured.
                              +
                              • After a table is synchronized and renamed, the new index name format is i_+hash value+original index name (which may be truncated)+_key. The hash value is calculated based on the original schema name_original table name_mapped schema name_mapped table name_original index name
                              • After a table is synchronized and renamed, the new constraint name format is c_+hash value+original constraint name (which may be truncated)+_key. The hash value is calculated based on the original schema name_original table name_mapped schema name_mapped table name_original index name
                              • GaussDB Distributed supports only ranged partitioned tables. Therefore, other types of partitioned tables are synchronized to the destination database as common tables.
                              • If a logical replication slot fails to be created or does not exist due to a long transaction, you can reset the task and then restart it.
                              +
                            +

                            Full synchronization

                            +
                            • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                            • Do not execute any DDL statement in the source database. Restricted by the logical replication function of GaussDB, DDL statements cannot be synchronized. If you synchronize DDL statements, data may be inconsistent or the task may fail.
                            • Do not write data to the destination database. Otherwise, data may be inconsistent.
                            +

                            Incremental synchronization

                            +
                            • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                            • Before a task enters the incremental synchronization phase, ensure that long-running transactions are not started in the source database. Starting the long transaction will block the creation of the logical replication slot and cause the task to fail.
                            • Do not execute any DDL statement in the source database. Restricted by the logical replication function of GaussDB, DDL statements cannot be synchronized. If you synchronize DDL statements, data may be inconsistent or the task may fail.
                            • Do not change the REPLICA IDENTITY value of a table in the source database. Otherwise, incremental data may be inconsistent or the task may fail.
                            • Do not write data to the destination database. Otherwise, data may be inconsistent.
                            • Replication of interval partition tables is not supported.
                            • After a DDL statement is executed in a transaction, the DDL statement and subsequent statements are not decoded.
                            +

                            Data processing

                            +
                            • During column processing, the primary key, unique key, and distribution column cannot be filtered out.
                            • If table columns are renamed or filtered, the conditional expressions of the partial index in the index definition are ignored, expression columns in common indexes are excluded, and unique indexes that contain expression columns are excluded.
                            • If table columns are filtered, the corresponding columns in the common index and foreign key are also filtered.
                            +

                            Synchronization comparison

                            +
                            • You are advised to compare data in the source database during off-peak hours to prevent inconsistent data from being falsely reported and reduce the impact on the source database and DRS tasks.
                            • The topology structure of the source database must be the same as that of the destination database. Otherwise, the content comparison function is unavailable.
                            • During incremental synchronization, if data is written to the source database, the comparison results may be inconsistent.
                            • Data cannot be compared during full synchronization.
                            • Do not limit the synchronization speed during data comparison.
                            +

                            Stopping a task

                            +
                            • Stop a task normally.

                              After an incremental or full+incremental synchronization is complete, the streaming replication slot created by the task in the source database is automatically deleted.

                              +
                            • Forcibly stop a task.

                              To forcibly stop an incremental or a full+incremental synchronization task, delete the replication slots that may remain in the source database. For details, see Forcibly Stopping Synchronization from GaussDB Distributed.

                              +
                            +
                            +
                            +
                            +

                            Prerequisites

                            • You have logged in to the DRS console.
                            • For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
                            + +
                            +

                            Procedure

                            1. On the Data Synchronization Management page, click Create Synchronization Task.
                            2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                              +

                              + + + + + + + + + + + + + + + + +
                              Table 5 Task and recipient description

                              Parameter

                              +

                              Description

                              +

                              Region

                              +

                              The region where the synchronization instance is deployed. You can change the region.

                              +

                              Project

                              +

                              The project corresponds to the current region and can be changed.

                              +

                              Task Name

                              +

                              The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                              +

                              Description

                              +

                              The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

                              +
                              +
                              + +
                              + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                              Table 6 Synchronization instance settings

                              Parameter

                              +

                              Description

                              +

                              Data Flow

                              +

                              Select Out of the cloud.

                              +

                              Source DB Engine

                              +

                              Select GaussDB Distributed.

                              +

                              Destination DB Engine

                              +

                              Select GaussDB Distributed.

                              +

                              Network Type

                              +

                              The public network is used as an example. Available options: VPC, Public network and VPN or Direct Connect

                              +

                              Source DB Instance

                              +

                              The distributed GaussDB instance you created.

                              +

                              Synchronization Mode

                              +

                              Available options: Full+Incremental, Full, and Incremental. Full+Incremental is used as an example.

                              +
                              • Full+Incremental

                                This synchronization mode allows you to synchronize data in real time. After a full synchronization initializes the destination database, an incremental synchronization parses logs to ensure data consistency between the source and destination databases.

                                +
                                NOTE:

                                If you select Full+Incremental, data generated during the full synchronization will be continuously synchronized to the destination database, and the source remains accessible.

                                +
                                +
                              +
                              • Full

                                In this mode, data is synchronized from the source to the destination at a time.

                                +
                              • Incremental

                                Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                                +
                              +

                              Specifications

                              +

                              DRS instance specifications. Different specifications have different performance upper limits. For details, see Real-Time Synchronization.

                              +

                              Tags

                              +
                              • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                              • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                              +
                              +
                              +

                              If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                              +
                              +

                            3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, click Next.

                              Establish the connectivity between the DRS instance and the source and destination databases.

                              +
                              • Network connectivity: Ensure that the source and destination databases accept connections from the DRS instance.
                              • Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.
                              + +
                              + + + + + + + + + + + + + +
                              Table 7 Source database settings

                              Parameter

                              +

                              Description

                              +

                              DB Instance Name

                              +

                              The distributed GaussDB instance selected during synchronization task creation. This parameter cannot be changed.

                              +

                              Database Username

                              +

                              The username for accessing the source database.

                              +

                              Database Password

                              +

                              The password for the database username.

                              +
                              +
                              +

                              The username and password of the source database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                              +
                              + +
                              + + + + + + + + + + + + + +
                              Table 8 Destination database settings

                              Parameter

                              +

                              Description

                              +

                              IP Address or Domain Name

                              +

                              IP address or domain name of the destination database in the IP address/Domain name:Port format. The port of the destination database. Range: 1 - 65535

                              +

                              You can enter up to 10 groups of IP addresses or domain names of the source database. Separate multiple values with commas (,). For example: 192.168.0.1:8080,192.168.0.2:8080.

                              +

                              Database Username

                              +

                              The username for accessing the destination database.

                              +

                              Database Password

                              +

                              The password for the database username.

                              +
                              +
                              +

                              The username and password of the destination database are encrypted and stored in the database and the synchronization instance during the synchronization. After the task is deleted, the username and password are permanently deleted.

                              +
                              +

                            4. On the Set Synchronization Task page, select the synchronization policy and synchronization objects, and click Next.

                              +

                              + + + + + + + + + + + + + +
                              Table 9 Synchronization Object

                              Parameter

                              +

                              Description

                              +

                              Flow Control

                              +

                              You can choose whether to control the flow.

                              +
                              • Yes

                                You can customize the maximum migration speed.

                                +

                                In addition, you can set the time range based on your service requirements. The traffic rate setting usually includes setting of a rate limiting time period and a traffic rate value. Flow can be controlled all day or during specific time ranges. The default value is All day. A maximum of three time ranges can be set, and they cannot overlap.

                                +

                                The flow rate must be set based on the service scenario and cannot exceed 9,999 MB/s.

                                +
                              • No
                                The synchronization speed is not limited and the outbound bandwidth of the source database is maximally used, which will increase the read burden on the source database. For example, if the outbound bandwidth of the source database is 100 MB/s and 80% bandwidth is used, the I/O consumption on the source database is 80 MB/s.
                                NOTE:
                                • The flow control mode takes effect only in the full synchronization phase.
                                • You can also change the flow control mode after creating a task. For details, see Modifying the Flow Control Mode.
                                +
                                +
                                +
                              +

                              Incremental Conflict Policy

                              +

                              The conflict policy refers to the conflict handling policy during incremental synchronization. By default, conflicts in the full synchronization phase are ignored.

                              +

                              The following conflict policies are supported:

                              +
                              • Ignore

                                The system will skip the conflicting data and continue the subsequent synchronization process.

                                +
                              • Overwrite

                                Conflicting data will be overwritten.

                                +
                              • Report error

                                The synchronization task will be stopped and fail.

                                +
                              +

                              Ignore and overwrite: Synchronization stability is prioritized, so tasks will not be interrupted as data conflicts occur.

                              +

                              Report error: Data quality is prioritized. Any data conflicts are not allowed, so once a conflict occurs, the synchronization task fails and an error is reported. You need to manually find the cause of the fault. If the task is in the failed state for a long time, the storage space may be used up and the task cannot be restored.

                              +

                              Synchronization Object

                              +

                              Select Tables or Import object file based on your service requirements.

                              +
                              • If the synchronization objects in source and destination databases have different names, you can map the source object name to the destination one. For details, see Changing Object Names (Mapping Object Names).

                                When you map a schema name or table name to the target object, name the indexes and constraints of the mapped table in the following format: prefix + full name-based hash value + original index/constraint name + _key to prevent index/constraint name conflicts. The prefix of the index is i_, the prefix of the constraint is c_, and the full name is "schema name_table name_index/constraint name". The original index/constraint name may be truncated due to length limitation.

                                +
                              • You can change object names when you select Import object file. For details, see Importing Synchronization Objects.
                                NOTE:
                                • You can search for table names to quickly select the required database objects.
                                • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                                +
                                • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                                • The name of the selected synchronization object cannot contain spaces.
                                +
                                +
                              +
                              +
                              +

                            5. On the Advanced Settings page, set the parameters for full+incremental synchronization selected in 2 and click Next.

                              +

                              + + + + + + + + + + + + + + + + + + + + + +
                              Table 10 Full synchronization settings

                              Parameter

                              +

                              Description

                              +

                              Default Value

                              +

                              Synchronization Object Type

                              +

                              Select whether to synchronize indexes based on the service requirements. Table structure and data are mandatory.

                              +

                              All options

                              +

                              Concurrent Export Tasks

                              +

                              Number of export threads. Value range: 1 to 16. A larger value indicates higher load on the source database.

                              +

                              8

                              +

                              Concurrent Import Tasks

                              +

                              Number of import threads. Value range: 1 to 16. A larger value indicates higher load on the destination database.

                              +

                              8

                              +

                              Rows per Shard

                              +

                              Value range: 0 or 520,000 to 1,000,000,000

                              +
                              • 0

                                All tables are not sharded, and each table is synchronized as a whole.

                                +
                              • Other values

                                The table is sharded based on the specified value (or the primary key column). If the number of records in a table is less than the value of this parameter, the table is not sharded.

                                +
                              +

                              520000

                              +
                              +
                              + +
                              + + + + + + + + + +
                              Table 11 Incremental synchronization settings

                              Parameter

                              +

                              Description

                              +

                              Default Value

                              +

                              Concurrent Replay Tasks

                              +

                              Number of concurrent threads for data replay. Value range: 1 to 64. Incremental data is concurrently written to the destination database. A larger value indicates higher load on the destination database.

                              +

                              64

                              +
                              +
                              +

                            6. On the Check Task page, check the synchronization task.

                              • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                              • If all check items are successful, click Next.

                                You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                                +
                                +
                              +

                            7. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                              +

                              + + + + + + + +
                              Table 12 Task startup settings

                              Parameter

                              +

                              Description

                              +

                              Started Time

                              +

                              Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                              +
                              NOTE:

                              After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

                              +
                              +
                              +
                              +

                            8. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                              • You can view the task status. For more information about task status, see Task Statuses.
                              • You can click in the upper-right corner to view the latest task status.
                              • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                              +

                            +
                            +
                            +
                            +
                            +
                            Parent topic: Out of the Cloud
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_11_0454.html b/docs/drs/umn/drs_11_0454.html new file mode 100644 index 000000000..13280d976 --- /dev/null +++ b/docs/drs/umn/drs_11_0454.html @@ -0,0 +1,321 @@ + + +

                            From GaussDB Distributed to Kafka

                            +

                            Supported Source and Destination Databases

                            +
                            + + + + + + + +
                            Table 1 Supported databases

                            Source DB

                            +

                            Destination DB

                            +
                            • GaussDB Distributed
                            +
                            • Kafka

                              0.11 or later

                              +
                            +
                            +
                            +
                            +

                            Supported Synchronization Objects

                            Table 2 lists the objects that can be synchronized in different scenarios. DRS will automatically check the objects you selected before the synchronization.

                            + +
                            + + + + + + + +
                            Table 2 Supported synchronization objects

                            Type

                            +

                            Synchronization Scope

                            +

                            Synchronization scope

                            +
                            • Instance-level synchronization is not supported. Only one database can be synchronized at a time. To synchronize multiple databases, create multiple tasks.
                            • Supported scenario: Incremental synchronization
                            • Supported fields: INTEGER, TINYINT, SMALLINT, BIGINT, NUMBER, NUMERIC, REAL, DOUBLE PRECISION, CHARACTER, CHARACTER VARYING, NVARCHAR2, BIT, BIT VARYING, BLOB, BYTEA, CLOB, RAW, TEXT, JSON, BOOLEAN, DATE, SMALLDATETIME, TIME WITH TIME ZONE, TIME WITHOUT TIME ZONE, TIMESTAMP WITH TIME ZONE, TIMESTAMP WITHOUT TIME ZONE, INTERVAL, BOX, CIDR, CIRCLE, INET, LSEG, MACADDR, MONEY, PATH, POINT, POLYGON, TSQUERY, TSVECTOR, REFCURSOR, UUID and ARRAY.
                            • Table-level synchronization or object file import is supported.
                              • Only DML statements of the selected table can be synchronized.
                              • Databases without schemas cannot be synchronized.
                              • Schemas without tables cannot be synchronized.
                              • Column-store tables, compressed tables, delay tables, and temporary tables cannot be synchronized. Do not synchronize unlogged tables.
                              • The database name, schema name, and table name cannot contain special characters /<.>\'`|,?!
                              • If you select tables by importing an object file, ensure that the imported table exists in the source database or is visible to the synchronization user.
                              +
                            +
                            +
                            +
                            +

                            Database User Permission Requirements

                            Before you start a synchronization task, the source and destination database users must meet the requirements in the following table. Different types of synchronization tasks require different permissions. For details, see Table 3. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

                            +
                            • You are advised to create an independent database account for DRS task connection to prevent task failures caused by account modification.
                            • After changing the account passwords for the source or destination databases, modify the connection information in the DRS task as soon as possible to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.
                            +
                            + +
                            + + + + + + + +
                            Table 3 Database user permission

                            Type

                            +

                            Incremental

                            +

                            Source database user

                            +

                            The user has the sysadmin role or the following minimum permissions:

                            +

                            The REPLICATION permission or the permission inherited from the built-in role gs_role_replication, the CONNECT permission for databases, the USAGE permission for schemas, and the SELECT permission for tables.

                            +
                            +
                            +
                            +

                            Suggestions

                            • The success of database synchronization depends on environment and manual operations. To ensure a smooth synchronization, perform a synchronization trial before you start the synchronization to help you detect and resolve problems in advance.
                            • It is recommended that you start a task during off-peak hours to minimize the impact of synchronization on your services.
                            +
                            +

                            Precautions

                            DRS incremental synchronization consists of three phases: task start, incremental synchronization, and task completion. To ensure smooth synchronization, read the following notes before creating a synchronization task.

                            + +
                            + + + + + + + + + + + + + +
                            Table 4 Precautions

                            Type

                            +

                            Constraints

                            +

                            Starting a task

                            +
                            • Source database requirements:

                              If incremental synchronization is selected:

                              +
                              • The wal_level parameter of the source database is set to logical.
                              • The enable_slot_log parameter of the source database is set to on.
                              • The max_replication_slots value of the source database must be greater than the number of used replication slots.
                              • Set the REPLICA IDENTITY attribute of a table without a primary key to FULL, or add a primary key to the table.
                              • Set the REPLICA IDENTITY attribute of the table that has a primary key to FULL.
                              +
                            • Source database object requirements:
                              • The names of the source database, schema, and table to be synchronized cannot contain special characters /<.>\'`|,?!
                              +
                            • Destination database requirements:
                              • The destination database is a Kafka database.
                              +
                            • Other notes:
                              • The source must be a distributed GaussDB instance on the current cloud.
                              • Before a task enters the incremental synchronization phase, ensure that long-running transactions are not started in the source database. Starting the long transaction will block the creation of the logical replication slot and cause the task to fail.
                              • If a logical replication slot fails to be created or does not exist due to a long transaction, you can reset the task and then restart it.
                              +
                            +

                            Incremental synchronization

                            +
                            • Do not change the port of the source and destination databases, or change or delete the passwords and permissions of the source and destination database users. Otherwise, the task may fail.
                            • Do not change the REPLICA IDENTITY value of a table in the source database. Otherwise, incremental data may be inconsistent or the task may fail.
                            • During migration of table-level objects, you are not advised to rename the tables.
                            • Replication of interval partition tables is not supported.
                            • After a DDL statement is executed in a transaction, the DDL statement and subsequent statements are not decoded.
                            +

                            Stopping a task

                            +
                            • Stop a task normally:
                              • When an incremental synchronization task is complete, the streaming replication slot created by the task in the source database is automatically deleted.
                              +
                            + +
                            +
                            +
                            +

                            Prerequisites

                            • You have logged in to the DRS console.
                            • For details about the DB types and versions supported by real-time synchronization, see Real-Time Synchronization.
                            + +
                            +

                            Procedure

                            1. On the Data Synchronization Management page, click Create Synchronization Task.
                            2. On the Create Synchronization Instance page, specify the task name, description, and the synchronization instance details, and click Next.

                              +

                              + + + + + + + + + + + + + + + + +
                              Table 5 Task and recipient description

                              Parameter

                              +

                              Description

                              +

                              Region

                              +

                              The region where the synchronization instance is deployed. You can change the region.

                              +

                              Project

                              +

                              The project corresponds to the current region and can be changed.

                              +

                              Task Name

                              +

                              The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

                              +

                              Description

                              +

                              The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

                              +
                              +
                              + +
                              + + + + + + + + + + + + + + + + + + + + + + + + + +
                              Table 6 Synchronization instance settings

                              Parameter

                              +

                              Description

                              +

                              Data Flow

                              +

                              Select Out of the cloud.

                              +

                              Source DB Engine

                              +

                              Select GaussDB Distributed.

                              +

                              Destination DB Engine

                              +

                              Select Kafka.

                              +

                              Network Type

                              +

                              The public network is used as an example. Available options: Public network and VPN or Direct Connect

                              +

                              Source DB Instance

                              +

                              The distributed GaussDB instance you created.

                              +

                              Synchronization Mode

                              +
                              • Incremental

                                Through log parsing, incremental data generated on the source database is synchronized to the destination database.

                                +

                                During synchronization, the source database continues to provide services for external systems with zero downtime.

                                +
                              +

                              Tags

                              +
                              • This setting is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
                              • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
                              +
                              +
                              +

                              If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically ends.

                              +
                              +

                            3. On the Configure Source and Destination Databases page, wait until the synchronization instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the synchronization instance. After the connection tests are successful, click Next.

                              Establish the connectivity between the DRS instance and the source and destination databases.

                              +
                              • Network connectivity: Ensure that the source and destination databases accept connections from the DRS instance.
                              • Account connectivity: Ensure that the source and destination databases allows connections from the DRS instance using the username and password.
                              + +
                              + + + + + + + + + + + + + +
                              Table 7 Source database settings

                              Parameter

                              +

                              Description

                              +

                              DB Instance Name

                              +

                              The distributed GaussDB instance selected during synchronization task creation. This parameter cannot be changed.

                              +

                              Database Username

                              +

                              The username for accessing the source database.

                              +

                              Database Password

                              +

                              The password for the database username.

                              +
                              +
                              +

                              The username and password of the source database are encrypted and stored in DRS and will be cleared after the task is deleted.

                              +
                              + +
                              + + + + + + + + + + +
                              Table 8 Destination database settings

                              Parameter

                              +

                              Description

                              +

                              IP Address or Domain Name

                              +

                              IP address or domain name of the destination database in the IP address/Domain name:Port format. The port of the destination database. Range: 1 - 65535

                              +

                              You can enter up to 10 groups of IP addresses or domain names of the source database. Separate multiple values with commas (,). For example: 192.168.0.1:8080,192.168.0.2:8080.

                              +

                              Method

                              +

                              Available options: PLAINTEXT, SSL, SASL_PLAINTEXT, and SASL_SSL. For details, see Kafka Authentication.

                              +
                              +
                              +

                            4. On the Set Synchronization Task page, select the synchronization policy, objects, and data format, and click Next.

                              +

                              + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                              Table 9 Synchronization Object

                              Parameter

                              +

                              Description

                              +

                              Source Database Replication Slot Name

                              +

                              You can choose whether to specify the replication slot of the source database. After replication slot is enabled, enter the replication slot name. The name contains 63 characters and cannot start with a digit. Only lowercase letters, digits, and underscores (_) are allowed.

                              +

                              Topic Synchronization Policy

                              +

                              Topic synchronization policy. You can select A specific topic or Auto-generated topics.

                              +

                              Topic

                              +

                              Select the topic to be synchronized to the destination database. This parameter is available when the topic is set to A specified topic.

                              +

                              Topic Name Format

                              +

                              This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                              +

                              Number of Partitions

                              +

                              This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                              +

                              The number of partitions of a topic. Each topic can have multiple partitions. More partitions can provide higher throughput but consume more resources. Set the number of partitions based on the actual situation of brokers.

                              +

                              Replication Factor

                              +

                              This parameter is available when Topic Synchronization Policy is set to Auto-generated topics.

                              +

                              Number of copies of a topic. Each topic can have multiple copies, and the copies are placed on different brokers in a cluster. The number of copies cannot exceed the number of brokers. Otherwise, the topic fails to be created.

                              +

                              Synchronize Topic To

                              +

                              The policy for synchronizing topics to the Kafka partitions.

                              +
                              • If topics are synchronized to different partitions by hash value of the database, schema and table names, the performance on a single table query can be improved.
                              • If topics are synchronized to different partitions by hash value of the primary key, one table corresponds to one topic. This prevents data from being written to the same partition, and consumers can obtain data from different partitions concurrently.

                                For a table without a primary key, if you select Partitions are identified by the hash values of the primary key, topics are synchronized to different partitions based on the hash value of the database_name.schema.table_name.

                                +
                              • Partitions are differentiated by the hash values of database_name.schema_name: This mode applies to scenarios where one database corresponds to one topic, preventing multiple schemas from being written to the same partition, so that consumers can obtain data from different partitions concurrently.
                              • If topics are synchronized to partition 0, strong consistency can be obtained but write performance is impacted.
                              +

                              Data Format in Kafka

                              +

                              Select the data format to be delivered to Kafka.

                              +
                              • Avro refers to binary encoded format.
                              • JSON: JSON message format, which is easy to interpret but takes up more space.
                              +

                              For details, see Kafka Message Format.

                              +

                              Synchronization Object

                              +

                              DRS supports table-level synchronization. You can select data for synchronization based on your service requirements.

                              +
                              NOTE:
                              • You can search for table names to quickly select the required database objects.
                              • If there are changes made to the source databases or objects, click in the upper right corner to update the objects to be synchronized.
                              +
                              • If an object name contains spaces, the spaces before and after the object name are not displayed. If there are two or more consecutive spaces in the middle of the object name, only one space is displayed.
                              • The name of the selected synchronization object cannot contain spaces.
                              +
                              +
                              +
                              +

                            5. On the Check Task page, check the synchronization task.

                              • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.
                              • If all check items are successful, click Next.

                                You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

                                +
                                +
                              +

                            6. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Submit to submit the task.

                              +

                              + + + + + + + +
                              Table 10 Task startup settings

                              Parameter

                              +

                              Description

                              +

                              Started Time

                              +

                              Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

                              +
                              NOTE:

                              After a synchronization task is started, the performance of the source and destination databases may be affected. You are advised to start a synchronization task during off-peak hours.

                              +
                              +
                              +
                              +

                            7. After the task is submitted, you can view and manage it on the Data Synchronization Management page.

                              • You can view the task status. For more information about task status, see Task Statuses.
                              • You can click in the upper-right corner to view the latest task status.
                              • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources for the task again.
                              +

                            +
                            +
                            +
                            +
                            +
                            Parent topic: Out of the Cloud
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_11_0462.html b/docs/drs/umn/drs_11_0462.html new file mode 100644 index 000000000..16ef8968f --- /dev/null +++ b/docs/drs/umn/drs_11_0462.html @@ -0,0 +1,22 @@ + + +

                            Cloning a Synchronization Task

                            +

                            DRS allows you to clone the configuration of existing synchronization tasks. However, tasks in the following status cannot be cloned:

                            +
                            • Creating
                            • Creation failed
                            • Configuration
                            • Pending start
                            • Starting
                            • Deleted
                            +

                            You can clone the following data flow types:

                            +
                            • To the cloud
                              • MySQL->MySQL
                              +
                            • From the cloud
                              • MySQL->MySQL
                              +
                            +
                            • When a task is cloned, the source and destination database passwords are not cloned. You need to enter the passwords again for the new task.
                            • When you clone a task, the advanced settings for data filtering are not cloned. You need to set the advanced settings for the cloned task again.
                            • Many-to-one task cloning is not supported.
                            • When you clone a task that is being changed, if the change information has been saved to the database, the clone task configuration is the same as the changed configuration.
                            • After a clone task is created, the EIP and private IP address of the new task are different from those of the original task. You may need to configure the network to ensure that the new task can communicate with the source and destination databases.
                            +
                            +

                            Prerequisites

                            • You have logged in to the DRS console.
                            • A synchronization task has been created.
                            +
                            +

                            Procedure

                            1. On the Data Synchronization Management page, select the task to be cloned and click Clone in the Operation column.
                            2. In the displayed dialog box, confirm the new task name and click OK.
                            3. After the task is submitted and the task clone is complete, the task status changes to Configuration. You can click Edit in the Operation column, enter the source and destination database passwords again, and edit and start the task.
                            +
                            +
                            +
                            +
                            +
                            Parent topic: Task Life Cycle
                            +
                            +
                            + diff --git a/docs/drs/umn/drs_12_0008.html b/docs/drs/umn/drs_12_0008.html index 1a7d46eab..9c08376e4 100644 --- a/docs/drs/umn/drs_12_0008.html +++ b/docs/drs/umn/drs_12_0008.html @@ -58,6 +58,8 @@
                          • Checking Whether log_bin_trust_function_creators Is Set to On in Both the Source and Destination Databases
                            • +
                          • Checking Whether GTID Is Enabled for the Source Database
                            +
                          • Checking Whether log_bin_trust_function_creators Is Set to On in the Destination Database
                          • Checking Whether the max_allowed_packet Value of the Destination Database Is too Small
                            diff --git a/docs/drs/umn/drs_12_0009.html b/docs/drs/umn/drs_12_0009.html index 262479d68..6e696bfca 100644 --- a/docs/drs/umn/drs_12_0009.html +++ b/docs/drs/umn/drs_12_0009.html @@ -12,7 +12,7 @@

                            If the query result is empty, the streaming replication slot is deleted.

                            • -

                            Synchronizing Sequence Values

                            If sequence objects are not synchronized or the destination database is GaussDB, skip this section.

                            +

                            Synchronizing Sequence Values

                            If sequence objects are not synchronized or the destination database type is GaussDB, skip the following steps.

                            1. Use a high-privilege account (with the USAGE permission for all sequences) to connect to the source database and run the following statement:

                              select 'SELECT pg_catalog.setval('||quote_literal(quote_ident(n.nspname)||'.'||quote_ident(c.relname))||', '||nextval(c.oid)||');' as sqls from pg_class c join pg_namespace n on c.relnamespace=n.oid where c.relkind = 'S' and n.nspname !~'^pg_' and n.nspname<>'information_schema' and not (c.relname='hwdrs_ddl_info_id_seq' and n.nspname='public') order by n.nspname, c.relname;

                              The query result is the SQL statement that needs to be executed in the destination database.

                            2. Log in to the destination database as the destination database user used in the synchronization task and run the SQL statement queried in 1 in the destination database.
                            3. Run the following statement in the destination database to check the sequence value synchronization result:

                              SELECT n.nspname, c.relname, nextval(c.oid) from pg_class c join pg_namespace n on c.relnamespace=n.oid where c.relkind = 'S' and n.nspname !~'^pg_' and n.nspname<>'information_schema' order by 1,2;
                              diff --git a/docs/drs/umn/drs_15_0100.html b/docs/drs/umn/drs_15_0100.html index 8a800e058..872fbe27e 100644 --- a/docs/drs/umn/drs_15_0100.html +++ b/docs/drs/umn/drs_15_0100.html @@ -4,7 +4,7 @@

                              Scenarios

                              Out of memory (OOM) occurs during the migration from MongoDB to DDS, causing migration failures.

                              Possible Cause

                              The possible causes are as follows:

                              -
                              • If the mongod service of the source database is deployed on a single server, OOM occurs when the migration process consumes large amounts of memory through operations such as creating indexes and sorting queries.
                              • If the mongod service is deployed on a server with other services and the cacheSizeGB value is not specified, OOM occurs when all available memory has been allocated to other services, so the WiredTiger engine does not have sufficient memory.

                                By default, the memory used by the WiredTiger engine of mongod is calculated as follows: (Memory in GB-1 GB) x 50% for version 3.2 or (Memory in GB-1 GB) x 60% for version 3.4 and later.

                                +
                                • If the mongod service of the source database is deployed on a single server, OOM occurs when the migration process consumes large amounts of memory through operations such as creating indexes and sorting queries.
                                • If the mongod service is deployed on a server with other services and the cacheSizeGB value is not specified, OOM occurs when all available memory has been allocated to other services, so the WiredTiger engine does not have sufficient memory.

                                  By default, the memory used by the WiredTiger engine of mongod is calculated as follows: (Memory in GB - 1 GB) x 50% for version 3.2 or (Memory in GB - 1 GB) x 60% for version 3.4 and later.

                                diff --git a/docs/drs/umn/drs_16_0001.html b/docs/drs/umn/drs_16_0001.html index 080710e67..5a530aaa7 100644 --- a/docs/drs/umn/drs_16_0001.html +++ b/docs/drs/umn/drs_16_0001.html @@ -4,7 +4,7 @@

                                Before using the DRS service to migrate collections between sharded clusters, you must disable the balancer of the collections to be migrated.

                                • After the migration is complete, enable the balancer. The balancer is disabled during the migration, generating different numbers of chunks on each shard of the source database. After the balancer is enabled, chunks will be distributed between shards in the cluster, which may affect the performance of the source database.
                                -

                                Procedure

                                1. Log in to a database through shell tools.
                                2. Run the following command in the command window of the mongos node to switch to the config database:

                                  use config

                                  +

                                  Procedure

                                  1. Log in to the database using Shell.
                                  2. Run the following command in the command window of the mongos node to switch to the config database:

                                    use config

                                  3. Run the following commands to check whether the balancer can be disabled:

                                    while( sh.isBalancerRunning() ) {      
           print("waiting...");           
           sleep(1000);
diff --git a/docs/drs/umn/drs_16_1148.html b/docs/drs/umn/drs_16_1148.html
index f1da68a1d..2c0fc11c2 100644
--- a/docs/drs/umn/drs_16_1148.html
+++ b/docs/drs/umn/drs_16_1148.html
@@ -1,17 +1,17 @@
 
 
 
                                    Why Does the Delay of DR Tasks Increase?
                                    
-
                                    Causes for an Increase in RTO
                                    Recovery Time Objective (RTO) is duration of time within which transactions on the DRS instance are transmitted and replayed to the destination database during incremental synchronization. If the RTO value is large, transactions to be replayed on the DRS instance are stacked. The possible causes are as follows:
                                    
+
                                    Causes for an Increase in RTO
                                    Recovery Time Objective (RTO) is duration of time within which transactions on the DRS instance are transmitted and replayed to the destination database during incremental synchronization. If the RTO value is large, transactions to be replayed on the DRS instance are stacked. The possible causes are as follows:
                                    
 
                                    1. After a DR task is initialized, the incremental data generated from the time when the DR task is started to the current time needs to be replayed.
                                    2. Batch operations are performed on service database tables that do not have primary keys. The DR instance is synchronizing tables that do not have primary keys and have a large amount of changed data. To ensure data consistency in tables without primary keys, all operations are recorded. As a result, the operation execution efficiency is lower than that in tables with primary keys. In addition, if the destination table has no index, the data update efficiency is lower.
                                    3. If the DDL operation is performed on the service database, the DR instance can replay data only after the execution of the DDL operation is complete.
                                    4. Frequently executed operations are performed on hot tables in the service database. The DR instance combines the transactions of the hot table and then replays the transactions, reducing frequent operations on the destination database.
                                    5. The access to the DR database is abnormal. As a result, the incremental data cannot be replayed.
                                    
 
                                    
-
                                    Handling Suggestion for an Increase in RTO
                                    1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
                                    2. On the Basic Information page, click the Disaster Recovery Monitoring tab to view the changes of RTO.
                                      • If RTO decreases gradually or increases only in a short time, no action is required.
                                      • If RTO keeps increasing, run the following statement in the DR database to check whether there are SQL statements that take a long time to execute or DDL statements that are being executed:
                                        show processlist
                                        
+
                                        Handling Suggestion for an Increase in RTO
                                        1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
                                        2. On the Basic Information page, click the Disaster Recovery Monitoring tab to view the changes of RTO.
                                          • If RTO decreases gradually or increases only in a short time, no action is required.
                                          • If RTO keeps increasing, run the following statement in the DR database to check whether there are SQL statements that take a long time to execute or DDL statements that are being executed:
                                            show processlist
                                            
 
                                          • If the DR database is abnormal, contact database O&M engineers.
                                          
 
                                        
 
                                        
-
                                        Causes for an Increase in RPO
                                        Recovery Point Objective (RPO) refers to the time that passes from when a transaction in the service database is submitted and the time when the transaction is synchronized to the DRS instance during the incremental synchronization. If RPO is large, the latest changes made to the service database data have not been extracted to the DR instance. The possible causes are as follows:
                                        
+
                                        Causes for an Increase in RPO
                                        Recovery Point Objective (RPO) refers to the time that passes from when a transaction in the service database is submitted and the time when the transaction is synchronized to the DRS instance during the incremental synchronization. If RPO is large, the latest changes made to the service database data have not been extracted to the DR instance. The possible causes are as follows:
                                        
 
                                        1. The network between the service database and the DRS DR instance is unstable. Reading changes in logs from the service database is slow.
                                        2. The service database cannot be accessed. As a result, incremental data cannot be extracted.
                                        
 
                                        
-
                                        Handling Suggestion for an Increase in RPO
                                        1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
                                        2. On the Basic Information page, click the Disaster Recovery Monitoring tab to view the changes of RPO.
                                          • If RPO decreases gradually or increases only in a short time, no action is required.
                                          • If the service database is abnormal, contact database O&M engineers.
                                          
+
                                          Handling Suggestion for an Increase in RPO
                                          1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
                                          2. On the Basic Information page, click the Disaster Recovery Monitoring tab to view the changes of RPO.
                                            • If RPO decreases gradually or increases only in a short time, no action is required.
                                            • If the service database is abnormal, contact database O&M engineers.
                                            
 
                                          
 
                                          
 
                                        
diff --git a/docs/drs/umn/drs_16_1155.html b/docs/drs/umn/drs_16_1155.html
index a6e86386a..20f2f4806 100644
--- a/docs/drs/umn/drs_16_1155.html
+++ b/docs/drs/umn/drs_16_1155.html
@@ -9,21 +9,17 @@
 
                                         
                                        DRS incremental synchronization requirements can be met if any of the following checks are passed.
                                        
 
                                        
 
                                        Table-level PK/UI Supplemental Logging Check (Minimum Requirement)
                                        Check whether supplemental logging of the table-level objects to be synchronized meets the requirements.
                                        
-
                                        1. Run the following SQL statement in the source database:
                                          select * from ALL_LOG_GROUPS where (LOG_GROUP_TYPE='UNIQUE KEY LOGGING' or LOG_GROUP_TYPE='PRIMARY KEY LOGGING') and OWNER='Schema name in uppercase' and TABLE_NAME='Table name in uppercase';
                                          
+
                                          1. Run the following SQL statement in the source database:
                                            select * from ALL_LOG_GROUPS where (LOG_GROUP_TYPE='UNIQUE KEY LOGGING' or LOG_GROUP_TYPE='PRIMARY KEY LOGGING') and OWNER='Schema name in uppercase' and TABLE_NAME='Table name in uppercase';
                                            
 
                                            If the table name corresponds to the records whose LOG_GROUP_TYPE is UNIQUE KEY LOGGING and PRIMARY KEY LOGGING in the query result, the DRS incremental synchronization requirements are met.
                                            
 
                                          2. If the requirements are not met, run the following SQL statement to enable table-level PK/UI logging:
                                            alter database add supplemental log data; 
-alter table Schema_name.Table_name add supplemental log data(primary key,unique) columns;
                                            
-
                                             
                                            In the preceding command, Schema_name.Table_name should replace with some existing schema names and table names.
                                            
-
                                            
+alter table Schema_name.Table_name add supplemental log data(primary key,unique) columns;

                                  All Table-Level Supplemental Log Check

                                  Check whether supplemental logging of the table-level objects to be synchronized meets the requirements.

                                  -
                                  1. Run the following SQL statement in the source database:

                                    select * from ALL_LOG_GROUPS where LOG_GROUP_TYPE='ALL COLUMN LOGGING' and OWNER='Schema_name in uppercase' and TABLE_NAME='Table name in uppercase';
                                    +
                                    1. Run the following SQL statement in the source database:

                                      select * from ALL_LOG_GROUPS where LOG_GROUP_TYPE='ALL COLUMN LOGGING' and OWNER='Schema_name in uppercase' and TABLE_NAME='Table_name in uppercase';

                                      If the table name is recorded in the query result, the DRS incremental synchronization requirements can be met.

                                    2. If the requirements are not met, run the following SQL statement to enable all column supplemental logging at the table level:

                                      alter database add supplemental log data; 
 alter table Schema_name.Table_name add supplemental log data(all) columns;
                                      -

                                      In the preceding command, Schema_name.Table_name should replace with some existing schema names and table names.

                                      -

                                  Database-level Supplemental Log Check

                                  For the database-level objects to be synchronized, check whether supplemental logging meets the requirements.

                                  diff --git a/docs/drs/umn/drs_TaskMangement.html b/docs/drs/umn/drs_TaskMangement.html index 9f4300a1b..f691c4c45 100644 --- a/docs/drs/umn/drs_TaskMangement.html +++ b/docs/drs/umn/drs_TaskMangement.html @@ -14,6 +14,8 @@
                                3. Managing Objects
                                  4. +
                                4. Managing Parameters
                                  +
                                5. Task Life Cycle
                              diff --git a/docs/drs/umn/drs_backup_tag.html b/docs/drs/umn/drs_backup_tag.html index c9c7c4b08..cfb1b8177 100644 --- a/docs/drs/umn/drs_backup_tag.html +++ b/docs/drs/umn/drs_backup_tag.html @@ -4,8 +4,9 @@

                              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, and other cloud services manage their own tags. If you have to manage a large number of tasks, you can use different tags to identify and search for tasks.
                              • 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.
                              • Each DB instance can have up to 20 tags.
                              -

                              Adding a Tag

                              1. On the Backup Migration Management page, click the target migration task name in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                                -
                                • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, numbers, spaces, and the following characters: _ . : = + - @.
                                • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, numbers, spaces, and the following characters: _ . : / = + - @.
                                • The key of a tag cannot be _sys_enterprise_project_id. _sys_enterprise_project_id is a fixed tag of the enterprise project system and cannot be manually added.
                                +

                                Adding a Tag

                                1. On the Backup Migration Management page, click the target migration task name in the Task Name/ID column.
                                2. On the Basic Information tab, click the Tags tab.
                                3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                                  +

                                  • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, digits, spaces, and special characters _.:=+-@

                                    +
                                  • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, digits, spaces, and special characters _.:=+-@
                                  • The key of a tag cannot be _sys_enterprise_project_id, which is a fixed tag of the enterprise project system and cannot be manually added.

                                4. After a tag has been added, you can view and manage it on the Tags page.

                                Editing a Tag

                                1. On the Backup Migration Management page, click the target migration task name in the Task Name/ID column.
                                2. On the Basic Information tab, click the Tags tab.
                                3. On the Tags page, click Add/Edit Tags. In the displayed dialog box, modify the tag and click OK.
                                diff --git a/docs/drs/umn/drs_change_history.html b/docs/drs/umn/drs_change_history.html index 6f44e4f23..d37aea301 100644 --- a/docs/drs/umn/drs_change_history.html +++ b/docs/drs/umn/drs_change_history.html @@ -8,52 +8,58 @@

                            2024-06-11

                            +

                            2025-02-10

                            This issue is the seventeenth official release, which incorporates the following changes:

                            -
                            • Modified Processing Data contents.
                            • Modified Importing Synchronization Objects contents.
                            • Supported real-time synchronization of PostgreSQL 15.
                            +

                            This issue is the seventeenth official release, which incorporates the following change:

                            +
                            • Added six types of specifications for DRS synchronization tasks.

                            2024-05-20

                            +

                            2024-06-11

                            This issue is the sixteenth official release, which incorporates the following changes:

                            +

                            This issue is the sixteenth official release, which incorporates the following changes:

                            +
                            • Optimized the content in "Processing Data."
                            • Optimized the content in "Importing Synchronization Objects."
                            • Supported real-time synchronization for PostgreSQL 15.
                            +

                            2024-05-20

                            +

                            This issue is the sixteenth official release, which incorporates the following change:

                            • Supported real-time synchronization from DDM to DDM.

                            2024-04-15

                            +

                            2024-04-15

                            This issue is the fifteenth official release, which incorporates the following changes:

                            - +

                            This issue is the fifteenth official release, which incorporates the following change:

                            +
                            • Supported object file import and data filtering for real-time synchronization from MySQL to MySQL.

                            2024-03-07

                            +

                            2024-03-07

                            This issue is the fourteenth official release, which incorporates the following changes:

                            -
                            • Supported real-time synchronization of PostgreSQL 14.
                            • Modified Tag Management contents.
                            +

                            This issue is the fourteenth official release, which incorporates the following changes:

                            +
                            • Supported real-time synchronization for PostgreSQL 14.
                            • Optimized the content in "Tag Management."

                            2024-01-10

                            +

                            2024-01-10

                            This issue is the thirteenth official release, which incorporates the following changes:

                            - +

                            This issue is the thirteenth official release, which incorporates the following changes:

                            +

                            2023-11-17

                            +

                            2023-11-17

                            This issue is the twelfth official release, which incorporates the following changes:

                            -
                            • Supported real-time migration of DDS 4.4.
                            +

                            This issue is the twelfth official release, which incorporates the following change:

                            +
                            • Supported real-time migration of DDS 4.4.

                            2023-10-17

                            +

                            2023-10-17

                            This issue is the eleventh official release, which incorporates the following changes:

                            -
                            • Supported real-time migration from MySQL to GaussDB(for MySQL).
                            • Supported periodic comparison.
                            +

                            This issue is the eleventh official release, which incorporates the following changes:

                            +
                            • Supported real-time migration from MySQL to TaurusDB.
                            • Supported periodic comparison.

                            2023-05-23

                            +

                            2023-05-23

                            This issue is the tenth official release, which incorporates the following changes:

                            -
                            • Added DMS for Kafka as the Destination DB.
                            +

                            This issue is the tenth official release, which incorporates the following change:

                            +
                            • Supported synchronization with DMS for Kafka as the destination database.

                            2023-02-10

                            @@ -77,7 +83,7 @@

                            2021-08-30

                            This issue is the sixth official release, which incorporates the following changes:

                            -
                            • Supported real-time synchronization from MySQL to GaussDB(for MySQL) across AZs.
                            +
                            • Supported real-time synchronization from MySQL to TaurusDB across AZs.

                            2021-05-31

                            @@ -95,13 +101,13 @@

                            2020-11-13

                            This issue is the third official release, which incorporates the following change:

                            -

                            Supported two-way synchronization between MySQL and GaussDB.

                            +

                            Supported two-way synchronization between MySQL and GaussDB.

                            2020-07-31

                            This issue is the second official release, which incorporates the following changes:

                            -
                            • Supported synchronization from MySQL to GaussDB.
                            • Supported Cassandra disaster recovery.
                            • Supported disaster recovery from MySQL to GaussDB(for MySQL).
                            +
                            • Supported synchronization from MySQL to GaussDB.
                            • Supported Cassandra disaster recovery.
                            • Supported real-time disaster recovery from MySQL to TaurusDB.

                            2019-11-30

                            diff --git a/docs/drs/umn/drs_disaster_tag.html b/docs/drs/umn/drs_disaster_tag.html index a0c87136a..8a6a74474 100644 --- a/docs/drs/umn/drs_disaster_tag.html +++ b/docs/drs/umn/drs_disaster_tag.html @@ -4,8 +4,9 @@

                            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, and other cloud services manage their own tags. If you have to manage a large number of tasks, you can use different tags to identify and search for tasks.
                            • 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.
                            • Each DB instance can have up to 20 tags.
                            -

                            Adding a Tag

                            1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
                            2. On the Basic Information tab, click the Tags tab.
                            3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                              -
                              • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, numbers, spaces, and the following characters: _ . : = + - @.
                              • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, numbers, spaces, and the following characters: _ . : / = + - @.
                              • The key of a tag cannot be _sys_enterprise_project_id. _sys_enterprise_project_id is a fixed tag of the enterprise project system and cannot be manually added.
                              +

                              Adding a Tag

                              1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags tab, click Add/Edit Tag. In the displayed dialog box, enter a tag key and value, click Add, and click OK.

                                +

                                • The tag key cannot be empty and must be unique. It cannot start or end with a space or start with _sys_. It can contain 1 to 128 characters, including letters, digits, spaces, and special characters _.:=+-@

                                  +
                                • The tag value can be empty. It cannot start or end with a space and can contain 0 to 255 characters, including letters, digits, spaces, and special characters _.:=+-@
                                • The key of a tag cannot be _sys_enterprise_project_id, which is a fixed tag of the enterprise project system and cannot be manually added.

                              4. After a tag has been added, you can view and manage it on the Tags page.

                              Editing a Tag

                              1. On the Disaster Recovery Management page, click the target DR task in the Task Name/ID column.
                              2. On the Basic Information tab, click the Tags tab.
                              3. On the Tags page, click Add/Edit Tags. In the displayed dialog box, modify the tag and click OK.
                              diff --git a/docs/drs/umn/drs_offline_migration.html b/docs/drs/umn/drs_offline_migration.html index 7aec55bf9..d075cf43f 100644 --- a/docs/drs/umn/drs_offline_migration.html +++ b/docs/drs/umn/drs_offline_migration.html @@ -14,19 +14,17 @@

                            Full backup file of RDS Microsoft SQL Server

                            +

                            Full backup file of RDS for SQL Server

                            RDS for Microsoft SQL Server

                            +

                            RDS for SQL Server

                            Creating an RDS Backup Migration Task

                            Backup files of on-premises and other cloud Microsoft SQL Server

                            +

                            Backup files of on-premises and other cloud Microsoft SQL Server

                            RDS for Microsoft SQL Server

                            -

                            Creating a Backup Using OBS Buckets

                            +

                            Creating a Backup Using OBS Buckets