vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

ddm_umn

Browse Source 
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: Ru, Li Yi <liyiru7@huawei.com>
Co-committed-by: Ru, Li Yi <liyiru7@huawei.com>
This commit is contained in:
Ru, Li Yi 2024-04-11 11:39:26 +00:00 committed by zuul
parent 2b90aa9fff
commit 4b09a03a51
81 changed files with 753 additions and 747 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

138
docs/ddm/umn/ALL_META.TXT.json
View File

File diff suppressed because it is too large Load Diff

70
docs/ddm/umn/CLASS.TXT.json
View File

File diff suppressed because it is too large Load Diff

31
docs/ddm/umn/ddm-08-0004.html
View File

@ -1,31 +0,0 @@
<a name="ddm-08-0004"></a><a name="ddm-08-0004"></a>
<h1 class="topictitle1">DML</h1>
<div id="body1597045079929"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="ddm-08-0005.html">INSERT</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-08-0007.html">REPLACE</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-08-0008.html">DELETE</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-08-0009.html">UPDATE</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-08-0006.html">SELECT</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-08-0010.html">SELECT JOIN Syntax</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-08-0011.html">SELECT UNION Syntax</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-08-0012.html">SELECT Subquery Syntax</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_12_0100.html">Supported System Schema Queries</a></strong><br>
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0001.html">SQL Syntax</a></div>
</div>
</div>

16
docs/ddm/umn/ddm-08-0008.html
View File

@ -1,16 +0,0 @@
<a name="ddm-08-0008"></a><a name="ddm-08-0008"></a>
<h1 class="topictitle1">DELETE</h1>
<div id="body1597045079932"><p id="ddm-08-0008__p1225913363529">DELETE is used to delete rows that meet conditions from a table.</p>
<div class="section" id="ddm-08-0008__section16157550115213"><h4 class="sectiontitle">Common Syntax</h4><pre class="screen" id="ddm-08-0008__screen178161921142219">DELETE [IGNORE]
FROM tbl_name [WHERE where_condition]</pre>
</div>
<div class="section" id="ddm-08-0008__section11542530185813"><h4 class="sectiontitle">Syntax Restrictions</h4><ul id="ddm-08-0008__ul97198382583"><li id="ddm-08-0008__li8537185884617">The WHERE clause does not support subqueries, including correlated and non-correlated subqueries.</li><li id="ddm-08-0008__li95371587463">Data in reference tables cannot be deleted when multiple tables are deleted at a time.</li><li id="ddm-08-0008__li1855703817222">PARTITION clauses are not supported.</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0004.html">DML</a></div>
</div>
</div>

17
docs/ddm/umn/ddm-08-0009.html
View File

@ -1,17 +0,0 @@
<a name="ddm-08-0009"></a><a name="ddm-08-0009"></a>
<h1 class="topictitle1">UPDATE</h1>
<div id="body1597045079933"><div class="section" id="ddm-08-0009__section0886140223"><h4 class="sectiontitle">Common Syntax</h4><pre class="screen" id="ddm-08-0009__screen2034416355214">UPDATE table_reference
SET col_name1={expr1} [, col_name2={expr2}] ...
[WHERE where_condition]</pre>
</div>
<div class="section" id="ddm-08-0009__section13101911638"><h4 class="sectiontitle">Syntax Restrictions</h4><ul id="ddm-08-0009__ul19343647289"><li id="ddm-08-0009__li595783310450">Subqueries are not supported, including correlated and non-correlated subqueries.</li><li id="ddm-08-0009__li1595451902312">Cross-shard subquery is not supported.</li><li id="ddm-08-0009__li1655810534458">The WHERE condition in the UPDATE statement does not support arithmetic expressions and their subqueries.</li><li id="ddm-08-0009__li34801448174515">Modifying broadcast tables is not supported during an update of multiple tables. (Data in columns of a broadcast table cannot be on the left of SET assignment statements).</li><li id="ddm-08-0009__li395763394519">Updating the sharding key field of a logical table is not supported because this operation may cause data redistribution.</li><li id="ddm-08-0009__li2243101572415">Setting <strong id="ddm-08-0009__b1382162013496">datetime</strong> to <strong id="ddm-08-0009__b43841320194920">1582</strong> or any value smaller in UPDATE statements is not supported.</li><li id="ddm-08-0009__li397144103312">UPDATE cannot be used to update sharding key value <strong id="ddm-08-0009__b144531158194914">DEFAULT</strong>.</li><li id="ddm-08-0009__li151721114114716">Repeatedly updating the same field in an UPDATE statement is not supported.</li><li id="ddm-08-0009__li15439163024720">Updating a sharding key using UPDATE JOIN syntax is not supported.</li><li id="ddm-08-0009__li64396431858">UPDATE cannot be used to update self-joins.</li><li id="ddm-08-0009__li19551013286">Referencing other object columns in assignment statements or expressions may cause unexpected update results. Example:<p id="ddm-08-0009__p18887153252820"><a name="ddm-08-0009__li19551013286"></a><a name="li19551013286"></a>update tbl_1 a,tbl_2 b set a.name=concat(b.name,'aaaa'),b.name=concat(a.name,'bbbb') on a.id=b.id</p>
</li><li id="ddm-08-0009__li1691531614442">UPDATE JOIN supports only joins with WHERE conditions.</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0004.html">DML</a></div>
</div>
</div>

16
docs/ddm/umn/ddm-08-0013.html
View File

@ -1,16 +0,0 @@
<a name="ddm-08-0013"></a><a name="ddm-08-0013"></a>
<h1 class="topictitle1">Use Constraints</h1>
<div id="body1597045079948"><p id="ddm-08-0013__p466232353417">DDM is compatible with the MySQL license and syntax, but the use of SQL statements is limited due to differences between distributed databases and single-node databases.</p>
<div class="section" id="ddm-08-0013__section3131558184018"><h4 class="sectiontitle">Unsupported SQL Statements</h4><ul id="ddm-08-0013__ul71302554104"><li id="ddm-08-0013__li580003915295">Triggers</li><li id="ddm-08-0013__li5290184312411">Temporary tables</li><li id="ddm-08-0013__li1413194211305">DO statement</li><li id="ddm-08-0013__li1627111476295">Association with foreign keys</li><li id="ddm-08-0013__li515914301114">RESET statement</li><li id="ddm-08-0013__li115312913124">FLUSH statement</li><li id="ddm-08-0013__li1346194081816">BINLOG statement</li><li id="ddm-08-0013__li11979203815161">HANDLER statement</li><li id="ddm-08-0013__li54647442619">SHOW WARNINGS statement</li><li id="ddm-08-0013__li0459622202811">Assignment operator :=</li><li id="ddm-08-0013__li1736135114358">Operators less than (&lt;), assignment (=), and more than (&gt;)</li><li id="ddm-08-0013__li5971853365">Expression IS UNKNOWN</li><li id="ddm-08-0013__li4135132014123">INSTALL and UNINSTALL PLUGIN statements</li><li id="ddm-08-0013__li171137023014">Cross-shard stored procedures and custom functions</li><li id="ddm-08-0013__li1527811613301">Statements for modifying database names, table names, and sharding field names and types</li><li id="ddm-08-0013__li585183291110">Most of SHOW statements such as SHOW PROFILES and SHOW ERRORS</li><li id="ddm-08-0013__li209371125413">Table maintenance statements, including ANALYZE, CHECK, CHECKSUM, OPTIMIZE, and REPAIR TABLE</li><li id="ddm-08-0013__li929665115111">Statements for assigning a value to or querying variable <strong id="ddm-08-0013__b918724332216">session</strong>, for example, set @rowid=0;select @rowid:=@rowid+1,id from user</li><li id="ddm-08-0013__li8771013185216">SQL statements that use -- or /*...*/ to comment out a single line or multiple lines of code</li><li id="ddm-08-0013__li16348133183816">The result of the REPEAT function contains a maximum of 1,000,000 characters (in version 3.0.9 or later).</li></ul>
</div>
<div class="section" id="ddm-08-0013__section6930101771618"><h4 class="sectiontitle">Permission Levels</h4><p id="ddm-08-0013__p1916616713487">Permission levels supported by DDM are as follows:</p>
<ul id="ddm-08-0013__ul1923091081615"><li id="ddm-08-0013__li122301810131610">Global level (not supported)</li><li id="ddm-08-0013__li152306109169">Database level (supported)</li><li id="ddm-08-0013__li192301510171615">Table level (supported)</li><li id="ddm-08-0013__li1523051051618">Column level (not supported)</li><li id="ddm-08-0013__li52301510111620">Subprogram level (not supported)</li><li id="ddm-08-0013__li42197472214">User level (supported)</li></ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0001.html">SQL Syntax</a></div>
</div>
</div>

32
docs/ddm/umn/ddm-08-0015.html
View File

@ -1,32 +0,0 @@
<a name="ddm-08-0015"></a><a name="ddm-08-0015"></a>
<h1 class="topictitle1">SHOW RULE</h1>
<div id="body1599640064069"><p id="ddm-08-0015__p17329111808"><strong id="ddm-08-0015__b174541916461">Command Format 1:</strong></p>
<p id="ddm-08-0015__p4717115171317"><strong id="ddm-08-0015__b122140235135">show rule</strong>;</p>
<p id="ddm-08-0015__p1914614161357">It is used to view the sharding rule of each logical table in a certain schema.</p>
<p id="ddm-08-0015__p33291011607">Command output:</p>
<p id="ddm-08-0015__p1296332641613"><span><img id="ddm-08-0015__image86454510116" src="en-us_image_0000001733146413.png"></span></p>
<p id="ddm-08-0015__p457218521611"><strong id="ddm-08-0015__b14701443862">Command Format 2:</strong></p>
<p id="ddm-08-0015__p111111916137"><strong id="ddm-08-0015__b14610326137">show rule from </strong><em id="ddm-08-0015__i17843251312">&lt;table_name&gt;</em>;</p>
<p id="ddm-08-0015__p6146171610511">It is used to view the sharding rule of a specific logical table in a certain schema.</p>
<p id="ddm-08-0015__p161401112419">Command output:</p>
<p id="ddm-08-0015__p815911513412"><span><img id="ddm-08-0015__image111598519414" src="en-us_image_0000001733266529.png"></span></p>
<p id="ddm-08-0015__p11143132210419"><strong id="ddm-08-0015__b15476133325519">Output Details:</strong></p>
<p id="ddm-08-0015__p1414332212420"><strong id="ddm-08-0015__b9425205613">TABLE_NAME</strong>: indicates the name of the logical table.</p>
<p id="ddm-08-0015__p142881856440"><strong id="ddm-08-0015__b12430457203516">BROADCAST</strong>: specifies whether the table is a broadcast table. <strong id="ddm-08-0015__b243165710358">0</strong> indicates that the table is not a broadcast table. <strong id="ddm-08-0015__b44322576359">1</strong> indicates the table is a broadcast table.</p>
<p id="ddm-08-0015__p192881256446"><strong id="ddm-08-0015__b39883487314">DB_PARTITION_KEY</strong>: indicates the database sharding key. Leave this field blank if database sharding is not required.</p>
<p id="ddm-08-0015__p8288175611414"><strong id="ddm-08-0015__b128071322257">DB_PARTITION_POLICY</strong>: indicates the database sharding algorithm. The value can be <strong id="ddm-08-0015__b1314422518450">HASH</strong>, <strong id="ddm-08-0015__b1699116414403">YYYYMM</strong>, <strong id="ddm-08-0015__b14508184444013">YYYYDD</strong>, and <strong id="ddm-08-0015__b162001646134013">YYYYWEEK</strong>.</p>
<p id="ddm-08-0015__p628817561242"><strong id="ddm-08-0015__b6492257154015">DB_PARTITION_COUNT</strong>: indicates the number of database shards.</p>
<p id="ddm-08-0015__p42880561443"><strong id="ddm-08-0015__b168871140370">DB_PARTITION_OFFSET</strong>: indicates where a new database shard starts from.</p>
<p id="ddm-08-0015__p14177305304"><strong id="ddm-08-0015__b954013450424">PARTITION_RANGE</strong>: indicates the sharding range when the database sharding algorithm is range.</p>
<p id="ddm-08-0015__p112871556346"><strong id="ddm-08-0015__b1536611135431">TB_PARTITION_KEY</strong>: indicates the table sharding key. Leave this field blank if table sharding is not required.</p>
<p id="ddm-08-0015__p5287155612414"><strong id="ddm-08-0015__b15041145445">TB_PARTITION_POLICY</strong>: indicates the table sharding algorithm. The value can be <strong id="ddm-08-0015__b1294954154515">HASH</strong>, <strong id="ddm-08-0015__b17410056184515">MM</strong>, <strong id="ddm-08-0015__b18989518463">DD</strong>, <strong id="ddm-08-0015__b19429664616">MMDD</strong>, or <strong id="ddm-08-0015__b2558414154616">WEEK</strong>.</p>
<p id="ddm-08-0015__p61449221743"><strong id="ddm-08-0015__b17202944617">TB_PARTITION_COUNT</strong>: indicates the number of physical tables in each database shard.</p>
<p id="ddm-08-0015__p614418227417"><strong id="ddm-08-0015__b133341913153817">TB_PARTITION_OFFSET</strong>: indicates where a new physical table starts from.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0002.html">Supported SQL Statements</a></div>
</div>
</div>

20
docs/ddm/umn/ddm-08-0017.html
View File

@ -1,20 +0,0 @@
<a name="ddm-08-0017"></a><a name="ddm-08-0017"></a>
<h1 class="topictitle1">SHOW TOPOLOGY</h1>
<div id="body1599640064071"><p id="ddm-08-0017__p1757111616590"><strong id="ddm-08-0017__b193203366262">Command Format:</strong></p>
<p id="ddm-08-0017__p1477441910141"><strong id="ddm-08-0017__b2096392771413">show topology from </strong><em id="ddm-08-0017__i96077289147">&lt;table_name&gt;</em>;</p>
<p id="ddm-08-0017__p1892154917406">It is used to view physical tables corresponding to a specified logical table.</p>
<p id="ddm-08-0017__p14193513164311"><strong id="ddm-08-0017__b7157144510264">Output Details:</strong></p>
<p id="ddm-08-0017__p787181316454"><strong id="ddm-08-0017__b1893725775010">RDS_instance_id</strong>: indicates the ID of the RDS instance.</p>
<p id="ddm-08-0017__p187451427184519"><strong id="ddm-08-0017__b117160573493">HOST</strong>: indicates the IP address of the RDS instance.</p>
<p id="ddm-08-0017__p13877132454"><strong id="ddm-08-0017__b14347650192615">PORT</strong>: indicates the port number of the RDS instance.</p>
<p id="ddm-08-0017__p98710132455"><strong id="ddm-08-0017__b4178155142617">DATABASE</strong>: indicates the physical database in the RDS instance.</p>
<p id="ddm-08-0017__p387111354517"><strong id="ddm-08-0017__b1555955215263">TABLE</strong>: indicates the physical table.</p>
<p id="ddm-08-0017__p48751315455"><strong id="ddm-08-0017__b149801855172317">ROW_COUNT</strong>: indicates the estimated number of data entries in each physical table. The value is obtained from information_schema.TABLES.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0002.html">Supported SQL Statements</a></div>
</div>
</div>

22
docs/ddm/umn/ddm-08-0021.html
View File

@ -1,22 +0,0 @@
<a name="ddm-08-0021"></a><a name="ddm-08-0021"></a>
<h1 class="topictitle1">Checking DDL Consistency of Physical Tables in All Logical Tables</h1>
<div id="body1599642876907"><p id="ddm-08-0021__p8282141889"><strong id="ddm-08-0021__b2519615111917">Purpose:</strong> To check DDL consistency of all logical tables in one schema</p>
<p id="ddm-08-0021__p1328481393019"><strong id="ddm-08-0021__b1343215571332">Command Format:</strong></p>
<pre class="codeblock" id="ddm-08-0021__codeblock189571212305"> <em id="ddm-08-0021__i997511531412">check table</em></pre>
<p id="ddm-08-0021__p48551722121215"><strong id="ddm-08-0021__b910922194612">Command Output:</strong></p>
<p id="ddm-08-0021__p06194263302">The following output is returned if DDL check results of all logical tables are consistent.</p>
<p id="ddm-08-0021__p51012272307"><span><img id="ddm-08-0021__image18244182363518" src="en-us_image_0000001685307210.png"></span></p>
<p id="ddm-08-0021__p386503843810">The following output is returned if there are logical tables with inconsistent DDL check results.</p>
<p id="ddm-08-0021__p4718117142014"><span><img id="ddm-08-0021__image1471821715207" src="en-us_image_0000001733146277.png"></span></p>
<p id="ddm-08-0021__p941994510383"><strong id="ddm-08-0021__b17471618182315">Output Details:</strong></p>
<p id="ddm-08-0021__p018843517345">Each row contains the check result of a logical table.</p>
<ul id="ddm-08-0021__ul1763524413013"><li id="ddm-08-0021__li6635204414305"><strong id="ddm-08-0021__b124621913155020">DATABASE_NAME</strong>: indicates the schema name.</li><li id="ddm-08-0021__li1613754163014"><strong id="ddm-08-0021__b1820194619503">TABLE_NAME</strong>: indicates the logical table name.</li><li id="ddm-08-0021__li29071545313"><strong id="ddm-08-0021__b12586163911513">TABLE_TYPE</strong>: indicates the logical table type.<ul id="ddm-08-0021__ul88071612103110"><li id="ddm-08-0021__li18553171293117"><strong id="ddm-08-0021__b13561457526">SINGLE</strong>: indicates that the logical table is unsharded.</li><li id="ddm-08-0021__li159693172311"><strong id="ddm-08-0021__b9512165755320">BROADCAST</strong>: indicates that the table is a broadcast table.</li><li id="ddm-08-0021__li37151624103117"><strong id="ddm-08-0021__b19980144310179">SHARDING</strong>: indicates that the table is sharded.</li></ul>
</li><li id="ddm-08-0021__li37641240163114"><strong id="ddm-08-0021__b1195591550">DDL_CONSISTENCY</strong>: indicates whether DDL results of all physical tables corresponding to the logical table are consistent.</li><li id="ddm-08-0021__li17845206173217"><strong id="ddm-08-0021__b11266919576">TOTAL_COUNT</strong>: indicates the number of physical tables in the logical table.</li><li id="ddm-08-0021__li218620190321"><strong id="ddm-08-0021__b18840102215716">INCONSISTENT_COUNT</strong>: indicates the number of physical tables with inconsistent DDL results.</li><li id="ddm-08-0021__li124811355143219"><strong id="ddm-08-0021__b56681748165911">DETAILS</strong>: indicates names of the physical tables with inconsistent DDL check results.</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0014.html">CHECK TABLE</a></div>
</div>
</div>

21
docs/ddm/umn/ddm-08-0022.html
View File

@ -1,21 +0,0 @@
<a name="ddm-08-0022"></a><a name="ddm-08-0022"></a>
<h1 class="topictitle1">Checking DDL Consistency of Physical Tables in One Logical Table</h1>
<div id="body1599642877312"><p id="ddm-08-0022__p1637718320364"><strong id="ddm-08-0022__b1912013479136">Purpose:</strong> To check DDL consistency of physical tables in a specific logical table</p>
<p id="ddm-08-0022__p14863442113015"><strong id="ddm-08-0022__b1869740538">Command Format:</strong></p>
<pre class="codeblock" id="ddm-08-0022__codeblock178147173017"><em id="ddm-08-0022__i4965194518416">check table </em><em id="ddm-08-0022__i191194710302">&lt;table_name&gt;</em></pre>
<p id="ddm-08-0022__p1274668103013"><strong id="ddm-08-0022__b0677184317312">Command Output:</strong></p>
<p id="ddm-08-0022__p18570103913335">If the returned result set is empty, DDL results of physical tables in this logical table are consistent.</p>
<p id="ddm-08-0022__p48521825103620"><span><img id="ddm-08-0022__image6463033183618" src="en-us_image_0000001733266429.png"></span></p>
<p id="ddm-08-0022__p170120263413">If the returned result set is not empty, there are physical tables with inconsistent DDL results.</p>
<p id="ddm-08-0022__p62180374333"><span><img id="ddm-08-0022__image189685336394" src="en-us_image_0000001685147494.png"></span></p>
<p id="ddm-08-0022__p467723504215"><strong id="ddm-08-0022__b14102183817186">Output Details:</strong></p>
<p id="ddm-08-0022__p56397974319">Each row displays details of a physical table with inconsistent DDL results.</p>
<ul id="ddm-08-0022__ul527415364219"><li id="ddm-08-0022__li3274155354211"><strong id="ddm-08-0022__b123879122284">DATABASE_NAME</strong>: indicates the database shard containing the physical table.</li><li id="ddm-08-0022__li2816519104316"><strong id="ddm-08-0022__b694284920281">TABLE_NAME</strong>: indicates the name of the physical table.</li><li id="ddm-08-0022__li1553015384436"><strong id="ddm-08-0022__b1142310162917">TABLE_TYPE</strong>: indicates the type of the logical table that the physical table belongs to.</li><li id="ddm-08-0022__li1496125794416"><strong id="ddm-08-0022__b898566123218">EXTRA_COLUMNS</strong>: indicates extra columns in the physical table.</li><li id="ddm-08-0022__li45740236450"><strong id="ddm-08-0022__b18101133233219">MISSING_COLUMNS</strong>: indicates missing columns in the physical table.</li><li id="ddm-08-0022__li690701054517"><strong id="ddm-08-0022__b1591053318338">DIFFERENT_COLUMNS</strong>: indicates name and type columns whose attributes are inconsistent in the physical table.</li><li id="ddm-08-0022__li2061954714455"><strong id="ddm-08-0022__b1157253372">KEY_DIFF</strong>: indicates inconsistent indexes in the physical table.</li><li id="ddm-08-0022__li1293523015545"><strong id="ddm-08-0022__b3554185694015">ENGINE_DIFF</strong>: indicates inconsistent engines in the physical table.</li><li id="ddm-08-0022__li1864915342545"><strong id="ddm-08-0022__b17811171964118">CHARSET_DIFF</strong>: indicates inconsistent character sets in the physical table.</li><li id="ddm-08-0022__li1571617389541"><strong id="ddm-08-0022__b47818518423">COLLATE_DIFF</strong>: indicates inconsistent collations in the physical table.</li><li id="ddm-08-0022__li136025476547"><strong id="ddm-08-0022__b798614418432">EXTRA_PARTITIONS</strong>: indicates extra partitions in the physical table. This field is only available to partitioned tables.</li><li id="ddm-08-0022__li834616494541"><strong id="ddm-08-0022__b0852144674614">MISSING_PARTITIONS</strong>: indicates missing partitions in the physical table. This field is only available to partitioned tables.</li><li id="ddm-08-0022__li108978526542"><strong id="ddm-08-0022__b143251030475">DIFFERENT_PARTITIONS</strong>: indicates partitions with inconsistent attributes in the physical table. This field is only available to partitioned tables.</li><li id="ddm-08-0022__li137019543545"><strong id="ddm-08-0022__b20530161024720">EXTRA_INFO</strong>: indicates other information such as missing physical tables.</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0014.html">CHECK TABLE</a></div>
</div>
</div>

16
docs/ddm/umn/ddm-08-0024.html
View File

@ -1,16 +0,0 @@
<a name="ddm-08-0024"></a><a name="ddm-08-0024"></a>
<h1 class="topictitle1">HINT-DB</h1>
<div id="body1600050169485"><p id="ddm-08-0024__p1757111616590"><strong id="ddm-08-0024__b174116162418">Command Format:</strong></p>
<p id="ddm-08-0024__p986420481142"><strong id="ddm-08-0024__b84121429155">/*+db=</strong><em id="ddm-08-0024__i134131022156">&lt;physical_db_name&gt;</em><strong id="ddm-08-0024__b1682915751510">*/ TRUNCATE TABLE </strong><em id="ddm-08-0024__i2830678154">&lt;table_name&gt;</em></p>
<p id="ddm-08-0024__p9175464010"><strong id="ddm-08-0024__b1897251715245">Description:</strong></p>
<p id="ddm-08-0024__p8060118">Deleting data in physical tables corresponding to <em id="ddm-08-0024__i119040351442">&lt;table_name&gt;</em> in <em id="ddm-08-0024__i1790653544412">&lt;physical_db_name&gt;</em> does not affect physical tables in other database shards.</p>
<div class="note" id="ddm-08-0024__note383785817303"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm-08-0024__p108388587304">HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way.</p>
</div></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0023.html">TRUNCATE TABLE</a></div>
</div>
</div>

21
docs/ddm/umn/ddm-08-0025.html
View File

@ -1,21 +0,0 @@
<a name="ddm-08-0025"></a><a name="ddm-08-0025"></a>
<h1 class="topictitle1">HINT-TABLE</h1>
<div id="body1600050169485"><p id="ddm-08-0025__p778112619212">HINTs are instructions within a SQL statement that tell the optimizer to execute the statement in a flexible way. This section describes how to use HINT syntax to delete data from a table.</p>
<p id="ddm-08-0025__p174162613016"><strong id="ddm-08-0025__b11170520132816">Command Format:</strong></p>
<p id="ddm-08-0025__p19151517111511"><strong id="ddm-08-0025__b53581626111517">/*+table=</strong><em id="ddm-08-0025__i33593266150">&lt;physical_table_name&gt;</em><strong id="ddm-08-0025__b843263181512">*/ TRUNCATE TABLE </strong><em id="ddm-08-0025__i543393113159">&lt;table_name&gt;</em></p>
<p id="ddm-08-0025__p139461421019"><strong id="ddm-08-0025__b56993236284">Description:</strong></p>
<p id="ddm-08-0025__p8060118">Deleting data in physical table <em id="ddm-08-0025__i16835417496">&lt;physical_table_name&gt;</em> in the current database shard does not affect other physical tables.</p>
<p id="ddm-08-0025__p117681729165512"><strong id="ddm-08-0025__b1494774314514">Example output before the table is deleted:</strong></p>
<p id="ddm-08-0025__p15383102211595"><span><img id="ddm-08-0025__image138352215915" src="en-us_image_0000001685307430.png"></span></p>
<p id="ddm-08-0025__p9707542112113"><strong id="ddm-08-0025__b1120218474512">Example output after the table is deleted:</strong></p>
<p id="ddm-08-0025__p1316931052217"><span><img id="ddm-08-0025__image1016819109229" src="en-us_image_0000001733266617.png"></span></p>
<div class="note" id="ddm-08-0025__note1462131013712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm-08-0025__p10832923205916">Hints are valid only for sharded tables.</p>
</div></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0023.html">TRUNCATE TABLE</a></div>
</div>
</div>

16
docs/ddm/umn/ddm-08-0026.html
View File

@ -1,16 +0,0 @@
<a name="ddm-08-0026"></a><a name="ddm-08-0026"></a>
<h1 class="topictitle1">HINT-DB/TABLE</h1>
<div id="body1600050169485"><p id="ddm-08-0026__p6886071116"><strong id="ddm-08-0026__b3761203982913">Command Format:</strong></p>
<p id="ddm-08-0026__p61314913182"><strong id="ddm-08-0026__b15592112012187">/*+db=</strong><em id="ddm-08-0026__i105961920101817">&lt;physical_db_name&gt;</em><strong id="ddm-08-0026__b1745172741817">,table=</strong><em id="ddm-08-0026__i16491227191815">&lt;physical_table_name&gt;</em><strong id="ddm-08-0026__b85721030131810">*/ TRUNCATE TABLE </strong><em id="ddm-08-0026__i125731330151815">&lt;table_name&gt;</em></p>
<p id="ddm-08-0026__p1422714101211"><strong id="ddm-08-0026__b36651941192911">Description:</strong></p>
<p id="ddm-08-0026__p8060118">Deleting data in physical table <em id="ddm-08-0026__i149174910509">&lt;physical_table_name&gt;</em> in database shard <em id="ddm-08-0026__i9362203144812">&lt;physical_db_name&gt;</em> does not affect other physical tables.</p>
<div class="note" id="ddm-08-0026__note1246562314711"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm-08-0026__p10832923205916">Hints are valid only for sharded tables.</p>
</div></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0023.html">TRUNCATE TABLE</a></div>
</div>
</div>

18
docs/ddm/umn/ddm-08-0029.html
View File

@ -1,18 +0,0 @@
<a name="ddm-08-0029"></a><a name="ddm-08-0029"></a>
<h1 class="topictitle1">SHOW DATA NODE</h1>
<div id="body1600053876218"><p id="ddm-08-0029__p8060118"><strong id="ddm-08-0029__b139411243125410">Command Format:</strong></p>
<p id="ddm-08-0029__p35717081316"><strong id="ddm-08-0029__b171210619133">show data node</strong>;</p>
<p id="ddm-08-0029__p1556215194018">It is used to view data about database shards in the RDS instance.</p>
<p id="ddm-08-0029__p105088934818"><strong id="ddm-08-0029__b1136074995410">Output Details:</strong></p>
<p id="ddm-08-0029__p12641185911718"><strong id="ddm-08-0029__b18344137185113">RDS_instance_id</strong>: indicates the ID of the RDS instance.</p>
<p id="ddm-08-0029__p1164155918179"><strong id="ddm-08-0029__b63591628115511">PHYSICAL_NODE</strong>: used to view physical databases in the RDS instance.</p>
<p id="ddm-08-0029__p1664185981715"><strong id="ddm-08-0029__b03533156558">HOST</strong>: indicates the IP address of the RDS instance.</p>
<p id="ddm-08-0029__p156415595175"><strong id="ddm-08-0029__b11546631">PORT</strong>: indicates the port number of the RDS instance.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0002.html">Supported SQL Statements</a></div>
</div>
</div>

4
docs/ddm/umn/ddm_01_0000.html
View File

@ -12,11 +12,11 @@
</li>
<li class="ulchildlink"><strong><a href="ddm_01_0017.html">Product Specifications</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-01-0003.html">Usage Constraints</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_01_0003.html">Usage Constraints</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_01_0007.html">Regions and AZs</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm-01-0002.html">Application Scenarios</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_01_0002.html">Application Scenarios</a></strong><br>
</li>
</ul>
</div>

10
docs/ddm/umn/ddm-01-0002.html → docs/ddm/umn/ddm_01_0002.html
View File

@ -1,10 +1,10 @@
<a name="ddm-01-0002"></a><a name="ddm-01-0002"></a>
<a name="ddm_01_0002"></a><a name="ddm_01_0002"></a>
<h1 class="topictitle1">Application Scenarios</h1>
<div id="body1553068858241"><p class="litext" id="ddm-01-0002__p30971651">It is especially suitable for applications requiring high-concurrency access to large volumes of data. Typical application scenarios are as follows:</p>
<ul id="ddm-01-0002__ul10309404"><li id="ddm-01-0002__li61374531"><strong id="ddm-01-0002__b094592313314">Internet</strong><p id="ddm-01-0002__p5281111">E-commerce, finance, O2O, retail, and social networking applications usually face challenges such as large user base, frequent marketing events, and slow response of core transactional systems. DDM can scale compute and storage resources to improve database processing of high-concurrency transactions and ensure fast access to data.</p>
</li><li id="ddm-01-0002__li47530006"><strong id="ddm-01-0002__b15802911172517">IoT</strong><p id="ddm-01-0002__p24725298">In industrial monitoring, remote control, smart city extension, smart home, and Internet of Vehicles (IoV) scenarios, a large number of sensors and monitoring devices frequently collect data and generate huge amounts of data, which may exceed the storage capability of single-node databases. DDM provides horizontal expansion to help you store massive data at low costs.</p>
</li><li id="ddm-01-0002__li20561848"><strong id="ddm-01-0002__b1096815718335">Traditional sectors</strong><p id="ddm-01-0002__p54897010">Government agencies, large-sized enterprises, banks, and the like usually use commercial solutions to support high-concurrency access to large volumes of data. These solutions are expensive because they need to rely on mid-range computers and high-end storage devices. DDM, deployed in clusters with common ECSs, provides cost-efficient database solutions with the same or even higher performance than traditional commercial database solutions.</p>
<div id="body1553068858241"><p class="litext" id="ddm_01_0002__p30971651">It is especially suitable for applications requiring high-concurrency access to large volumes of data. Typical application scenarios are as follows:</p>
<ul id="ddm_01_0002__ul10309404"><li id="ddm_01_0002__li61374531"><strong id="ddm_01_0002__b094592313314">Internet</strong><p id="ddm_01_0002__p5281111">E-commerce, finance, O2O, retail, and social networking applications usually face challenges such as large user base, frequent marketing events, and slow response of core transactional systems. DDM can scale compute and storage resources to improve database processing of high-concurrency transactions and ensure fast access to data.</p>
</li><li id="ddm_01_0002__li47530006"><strong id="ddm_01_0002__b15802911172517">IoT</strong><p id="ddm_01_0002__p24725298">In industrial monitoring, remote control, smart city extension, smart home, and Internet of Vehicles (IoV) scenarios, a large number of sensors and monitoring devices frequently collect data and generate huge amounts of data, which may exceed the storage capability of single-node databases. DDM provides horizontal expansion to help you store massive data at low costs.</p>
</li><li id="ddm_01_0002__li20561848"><strong id="ddm_01_0002__b1096815718335">Traditional sectors</strong><p id="ddm_01_0002__p54897010">Government agencies, large-sized enterprises, banks, and the like usually use commercial solutions to support high-concurrency access to large volumes of data. These solutions are expensive because they need to rely on mid-range computers and high-end storage devices. DDM, deployed in clusters with common ECSs, provides cost-efficient database solutions with the same or even higher performance than traditional commercial database solutions.</p>
</li></ul>
</div>
<div>

4
docs/ddm/umn/ddm-01-0003.html → docs/ddm/umn/ddm_01_0003.html
View File

@ -1,10 +1,10 @@
<a name="ddm-01-0003"></a><a name="ddm-01-0003"></a>
<a name="ddm_01_0003"></a><a name="ddm_01_0003"></a>
<h1 class="topictitle1">Usage Constraints</h1>
<div id="body1553068858245"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="ddm-01-0004.html">Network Access</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_01_0004.html">Network Access</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_01_0005.html">Data Nodes</a></strong><br>
</li>

8
docs/ddm/umn/ddm-01-0004.html → docs/ddm/umn/ddm_01_0004.html
View File

@ -1,12 +1,12 @@
<a name="ddm-01-0004"></a><a name="ddm-01-0004"></a>
<a name="ddm_01_0004"></a><a name="ddm_01_0004"></a>
<h1 class="topictitle1">Network Access</h1>
<div id="body1557802079200"><p id="ddm-01-0004__p6179243184919">Restrictions on network access are as follows:</p>
<ul id="ddm-01-0004__ul1240194704010"><li id="ddm-01-0004__li14516223117">The data nodes and ECSs running your applications must be in the same VPC as your DDM instance.</li><li id="ddm-01-0004__li1119413183215">To access DDM from your computer, you need to bind an EIP to your DDM instance and then use the EIP to access the DDM instance.</li></ul>
<div id="body1557802079200"><p id="ddm_01_0004__p6179243184919">Restrictions on network access are as follows:</p>
<ul id="ddm_01_0004__ul1240194704010"><li id="ddm_01_0004__li14516223117">The data nodes and ECSs running your applications must be in the same VPC as your DDM instance.</li><li id="ddm_01_0004__li1119413183215">To access DDM from your computer, you need to bind an EIP to your DDM instance and then use the EIP to access the DDM instance.</li></ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-01-0003.html">Usage Constraints</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_01_0003.html">Usage Constraints</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_01_0005.html
View File

@ -8,7 +8,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-01-0003.html">Usage Constraints</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_01_0003.html">Usage Constraints</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_01_0174.html
View File

@ -69,7 +69,7 @@ ON DUPLICATE KEY UPDATE b = b + c;</pre>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-01-0003.html">Usage Constraints</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_01_0003.html">Usage Constraints</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_01_0175.html
View File

@ -6,7 +6,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-01-0003.html">Usage Constraints</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_01_0003.html">Usage Constraints</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0030.html
View File

@ -13,7 +13,7 @@
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0001.html">SQL Syntax</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0001.html">SQL Syntax</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0031.html
View File

@ -24,7 +24,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0002.html">Supported SQL Statements</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0002.html">Supported SQL Statements</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0032.html
View File

@ -28,7 +28,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0001.html">SQL Syntax</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0001.html">SQL Syntax</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0034.html
View File

@ -14,7 +14,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0002.html">Supported SQL Statements</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0002.html">Supported SQL Statements</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0035.html
View File

@ -21,7 +21,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0001.html">SQL Syntax</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0001.html">SQL Syntax</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0038.html
View File

@ -503,7 +503,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0003.html">DDL</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0003.html">DDL</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0039.html
View File

@ -8,7 +8,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0002.html">Supported SQL Statements</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0002.html">Supported SQL Statements</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0040.html
View File

@ -12,7 +12,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0002.html">Supported SQL Statements</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0002.html">Supported SQL Statements</a></div>
</div>
</div>

4
docs/ddm/umn/ddm_03_0053.html
View File

@ -37,7 +37,7 @@
</tr>
<tr id="ddm_03_0053__row29027819718"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.3.2.3.1.1 "><p id="ddm_03_0053__p49031881711">Flexible shards configuration for a schema</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.3.2.3.1.2 "><p id="ddm_03_0053__p190313811720">You can increase shards or data nodes to scale out storage. For details, see <a href="ddm_03_0064.html">Shard Configuration</a>.</p>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.3.2.3.1.2 "><p id="ddm_03_0053__p190313811720">You can increase shards or data nodes to scale out storage. For details, see <a href="ddm_03_0131.html">Shard Configuration</a>.</p>
</td>
</tr>
<tr id="ddm_03_0053__row12471626174616"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.3.2.3.1.1 "><p id="ddm_03_0053__p1657016515532">Accounts</p>
@ -52,7 +52,7 @@
</tr>
<tr id="ddm_03_0053__row1453522113464"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.3.2.3.1.1 "><p id="ddm_03_0053__p15535192154620">SQL syntax</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.3.2.3.1.2 "><p id="ddm_03_0053__p145363214464">Describing DDL, DML, global sequence, SQL statements, and sharding algorithms. For details, see <a href="ddm-08-0001.html">SQL Syntax</a>.</p>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.3.2.3.1.2 "><p id="ddm_03_0053__p145363214464">Describing DDL, DML, global sequence, SQL statements, and sharding algorithms. For details, see <a href="ddm_08_0001.html">SQL Syntax</a>.</p>
</td>
</tr>
</tbody>

2
docs/ddm/umn/ddm_03_0062.html
View File

@ -73,7 +73,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0001.html">SQL Syntax</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0001.html">SQL Syntax</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0063.html
View File

@ -202,7 +202,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm-08-0001.html">SQL Syntax</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_08_0001.html">SQL Syntax</a></div>
</div>
</div>

4
docs/ddm/umn/ddm_03_0067.html
View File

@ -4,9 +4,9 @@
<div id="body0000001076524863"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="ddm_0600016.html">Restoring Data to a New Instance</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_06_0016.html">Restoring Data to a New Instance</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_0600017.html">Restoring Metadata</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_06_0017.html">Restoring Metadata</a></strong><br>
</li>
</ul>
</div>

2
docs/ddm/umn/ddm_03_0068.html
View File

@ -20,7 +20,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0064.html">Shard Configuration</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0131.html">Shard Configuration</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0069.html
View File

@ -6,7 +6,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0064.html">Shard Configuration</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0131.html">Shard Configuration</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0070.html
View File

@ -104,7 +104,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0064.html">Shard Configuration</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0131.html">Shard Configuration</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0071.html
View File

@ -33,7 +33,7 @@
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0064.html">Shard Configuration</a></div>
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0131.html">Shard Configuration</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_03_0064.html → docs/ddm/umn/ddm_03_0131.html
View File

@ -1,4 +1,4 @@
<a name="ddm_03_0064"></a><a name="ddm_03_0064"></a>
<a name="ddm_03_0131"></a><a name="ddm_03_0131"></a>
<h1 class="topictitle1">Shard Configuration</h1>
<div id="body0000001271200744"></div>

2
docs/ddm/umn/ddm_04_0009.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">What Version and Parameters Should I Select?</h1>
<div id="body1530839785505"><p id="ddm_04_0009__p154917472143">Currently, you cannot connect to DDM using <span class="keyword" id="ddm_04_0009__keyword6221118123813">JDBC driver</span> 5.1.46. Versions 5.1.35 to 5.1.45 are recommended.</p>
<p id="ddm_04_0009__p36001427162215">JDBC driver download address: <a href="https://dev.mysql.com/downloads/connector/j/" target="_blank" rel="noopener noreferrer">https://dev.mysql.com/doc/index-connectors.html</a></p>
<p id="ddm_04_0009__p36001427162215">JDBC driver download address:<a href="https://dev.mysql.com/downloads/connector/j/" target="_blank" rel="noopener noreferrer">https://dev.mysql.com/downloads/connector/j/</a></p>
<p id="ddm_04_0009__p1945754017221"><a href="#ddm_04_0009__table127264441235">Table 1</a> describes the recommended parameters for the JDBC URL.</p>
<div class="tablenoborder"><a name="ddm_04_0009__table127264441235"></a><a name="table127264441235"></a><table cellpadding="4" cellspacing="0" summary="" id="ddm_04_0009__table127264441235" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters</caption><thead align="left"><tr id="ddm_04_0009__row137266445234"><th align="left" class="cellrowborder" valign="top" width="19%" id="mcps1.3.4.2.4.1.1"><p id="ddm_04_0009__p372644482318">Parameter</p>

4
docs/ddm/umn/ddm_05_0001.html
View File

@ -6,9 +6,9 @@
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="ddm_05_0002.html">Creating an Account</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_05_0003.html">Modifying an Account</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_05_0133.html">Modifying an Account</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_05_0004.html">Deleting an Account</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_05_0134.html">Deleting an Account</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_05_0008.html">Resetting the Password of an Account</a></strong><br>
</li>

15
docs/ddm/umn/ddm_05_0003.html
View File

@ -1,15 +0,0 @@
<a name="ddm_05_0003"></a><a name="ddm_05_0003"></a>
<h1 class="topictitle1">Modifying an Account</h1>
<div id="body1585554409299"><div class="section" id="ddm_05_0003__section1539512419299"><h4 class="sectiontitle">Prerequisites</h4><p id="ddm_05_0003__p2085114424292">You have logged in to the DDM console.</p>
</div>
<div class="section" id="ddm_05_0003__section16597233133416"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_05_0003__ol172601822134919"><li id="ddm_05_0003__li18845223192514"><span>In the instance list, locate the DDM instance that you want to modify and click its name.</span></li><li id="ddm_05_0003__li16917753172513"><span>In the navigation pane, choose <strong id="ddm_05_0003__b194461298188">Accounts</strong>.</span></li><li id="ddm_05_0003__li877881015353"><span>In the account list, locate the required account and click <strong id="ddm_05_0003__b69141335141811">Modify</strong> in the <strong id="ddm_05_0003__b1192603511816">Operation</strong> column.</span></li><li id="ddm_05_0003__li31613483616"><span>In the displayed dialog box, modify the associated schemas, permissions, and description.</span><p><p id="ddm_05_0003__p1589151117"></p>
</p></li><li id="ddm_05_0003__li9754176193712"><span>Click <strong id="ddm_05_0003__b1889241152110">OK</strong>.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_05_0001.html">Account Management</a></div>
</div>
</div>

16
docs/ddm/umn/ddm_05_0004.html
View File

@ -1,16 +0,0 @@
<a name="ddm_05_0004"></a><a name="ddm_05_0004"></a>
<h1 class="topictitle1">Deleting an Account</h1>
<div id="body1585554409299"><div class="section" id="ddm_05_0004__section1539512419299"><h4 class="sectiontitle">Prerequisites</h4><p id="ddm_05_0004__p2085114424292">You have logged in to the DDM console.</p>
<div class="note" id="ddm_05_0004__note1442122410492"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm_05_0004__p144315241499">Deleted accounts cannot be recovered. Exercise caution when performing this operation.</p>
</div></div>
</div>
<div class="section" id="ddm_05_0004__section1024831334916"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_05_0004__ol172601822134919"><li id="ddm_05_0004__li18845223192514"><span>In the instance list, locate the DDM instance with the account that you want to delete and click its name.</span></li><li id="ddm_05_0004__li16917753172513"><span>In the navigation pane, choose <strong id="ddm_05_0004__b1343101215226">Accounts</strong>.</span></li><li id="ddm_05_0004__li877881015353"><span>In the account list, locate the account that you want to delete and choose <strong id="ddm_05_0004__b91905541103">More</strong> &gt; <strong id="ddm_05_0004__b319521517221">Delete</strong> in the <strong id="ddm_05_0004__b119613153224">Operation</strong> column.</span></li><li id="ddm_05_0004__li31613483616"><span>In the displayed dialog box, click <span class="uicontrol" id="ddm_05_0004__uicontrol16741322102218"><b>Yes</b></span>.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_05_0001.html">Account Management</a></div>
</div>
</div>

15
docs/ddm/umn/ddm_05_0133.html Normal file
View File

@ -0,0 +1,15 @@
<a name="ddm_05_0133"></a><a name="ddm_05_0133"></a>
<h1 class="topictitle1">Modifying an Account</h1>
<div id="body1585554409299"><div class="section" id="ddm_05_0133__section1539512419299"><h4 class="sectiontitle">Prerequisites</h4><p id="ddm_05_0133__p2085114424292">You have logged in to the DDM console.</p>
</div>
<div class="section" id="ddm_05_0133__section16597233133416"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_05_0133__ol172601822134919"><li id="ddm_05_0133__li18845223192514"><span>In the instance list, locate the DDM instance that you want to modify and click its name.</span></li><li id="ddm_05_0133__li16917753172513"><span>In the navigation pane, choose <strong id="ddm_05_0133__b194461298188">Accounts</strong>.</span></li><li id="ddm_05_0133__li877881015353"><span>In the account list, locate the required account and click <strong id="ddm_05_0133__b69141335141811">Modify</strong> in the <strong id="ddm_05_0133__b1192603511816">Operation</strong> column.</span></li><li id="ddm_05_0133__li31613483616"><span>In the displayed dialog box, modify the associated schemas, permissions, and description.</span><p><p id="ddm_05_0133__p1589151117"></p>
</p></li><li id="ddm_05_0133__li9754176193712"><span>Click <strong id="ddm_05_0133__b1889241152110">OK</strong>.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_05_0001.html">Account Management</a></div>
</div>
</div>

16
docs/ddm/umn/ddm_05_0134.html Normal file
View File

@ -0,0 +1,16 @@
<a name="ddm_05_0134"></a><a name="ddm_05_0134"></a>
<h1 class="topictitle1">Deleting an Account</h1>
<div id="body1585554409299"><div class="section" id="ddm_05_0134__section1539512419299"><h4 class="sectiontitle">Prerequisites</h4><p id="ddm_05_0134__p2085114424292">You have logged in to the DDM console.</p>
<div class="note" id="ddm_05_0134__note1442122410492"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm_05_0134__p144315241499">Deleted accounts cannot be recovered. Exercise caution when performing this operation.</p>
</div></div>
</div>
<div class="section" id="ddm_05_0134__section1024831334916"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_05_0134__ol172601822134919"><li id="ddm_05_0134__li18845223192514"><span>In the instance list, locate the DDM instance with the account that you want to delete and click its name.</span></li><li id="ddm_05_0134__li16917753172513"><span>In the navigation pane, choose <strong id="ddm_05_0134__b1343101215226">Accounts</strong>.</span></li><li id="ddm_05_0134__li877881015353"><span>In the account list, locate the account that you want to delete and choose <strong id="ddm_05_0134__b91905541103">More</strong> &gt; <strong id="ddm_05_0134__b319521517221">Delete</strong> in the <strong id="ddm_05_0134__b119613153224">Operation</strong> column.</span></li><li id="ddm_05_0134__li31613483616"><span>In the displayed dialog box, click <span class="uicontrol" id="ddm_05_0134__uicontrol16741322102218"><b>Yes</b></span>.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_05_0001.html">Account Management</a></div>
</div>
</div>

72
docs/ddm/umn/ddm_0600017.html
View File

@ -1,72 +0,0 @@
<a name="ddm_0600017"></a><a name="ddm_0600017"></a>
<h1 class="topictitle1">Restoring Metadata</h1>
<div id="body0000001733313057"><p id="ddm_0600017__p9645118115513">DDM automatically backs up DDM instance metadata at 02:00 UTC+00:00 every day and retains the backup data for 30 days. Metadata backup is also triggered by key operations that affect metadata, such as deleting a schema, deleting data after shard configuration, and deleting instances.</p>
<p id="ddm_0600017__p46473114585">When you delete a schema by mistake or your RDS for MySQL instances become abnormal, metadata restoration allows you to restore your DDM instance metadata and match the metadata with the RDS instance that has completed PITR to re-establish the relationship between your DDM instance and RDS instance. Metadata restoration supports only RDS for MySQL.</p>
<p id="ddm_0600017__p533912361448">To restore metadata of a DDM instance, you can specify a point in time by referring to <a href="#ddm_0600017__section128315484524">Restoring Metadata to a Point in Time</a>, or using an available backup by referring to <a href="#ddm_0600017__section132806221525">Restoring Metadata Using an Available Backup</a>.</p>
<div class="section" id="ddm_0600017__section16311542101119"><h4 class="sectiontitle">Precautions</h4><ul id="ddm_0600017__ul1983134241110"><li id="ddm_0600017__li9846734131911">Metadata restoration mainly restores the metadata of your DDM instance to a new DDM instance. It starts after a point-in-time recovery (PITR) for the associated data nodes is complete.<div class="note" id="ddm_0600017__note102541316208"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm_0600017__p425483152014">PITR indicates that a data node has been restored to a specified point in time.</p>
</div></div>
</li><li id="ddm_0600017__li884942201112">The destination DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.</li><li id="ddm_0600017__li14849426116">Ensure that the selected RDS for MySQL instance has completed PITR.</li><li id="ddm_0600017__li02281512112">Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.</li><li id="ddm_0600017__li750871015158">The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.</li><li id="ddm_0600017__li3128144163914">Time points that data can be restored to depend on the backup policy set on original data nodes.</li></ul>
</div>
<div class="section" id="ddm_0600017__section128315484524"><a name="ddm_0600017__section128315484524"></a><a name="section128315484524"></a><h4 class="sectiontitle">Restoring Metadata to a Point in Time</h4><ol id="ddm_0600017__ol5371100162518"><li id="ddm_0600017__li1366514210243"><span>Log in to the DDM console.</span></li><li id="ddm_0600017__li4793191882712"><a name="ddm_0600017__li4793191882712"></a><a name="li4793191882712"></a><span><a href="ddm_06_00017.html">Create a new DDM instance</a>.</span></li><li id="ddm_0600017__li203725032512"><span>In the DDM instance list, locate the newly-created instance and click its name.</span></li><li id="ddm_0600017__li382416102214"><span>In the navigation pane on the left, choose <strong id="ddm_0600017__b2066407356621">Backups &amp; Restorations</strong>.</span></li><li id="ddm_0600017__li723812134011"><span>Click <strong id="ddm_0600017__b698802603620">Restore Metadata</strong>.</span></li><li id="ddm_0600017__li179543119201"><span>On the displayed page, specify a time point. DDM will select an appropriate DDM metadata backup closest to the time point.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_0600017__table1941672742313" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="ddm_0600017__row11417102722314"><th align="left" class="cellrowborder" valign="top" width="24.87%" id="mcps1.3.5.2.6.2.1.2.3.1.1"><p id="ddm_0600017__p10417112762314">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="75.13%" id="mcps1.3.5.2.6.2.1.2.3.1.2"><p id="ddm_0600017__p4417172715233">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="ddm_0600017__row2041742752312"><td class="cellrowborder" valign="top" width="24.87%" headers="mcps1.3.5.2.6.2.1.2.3.1.1 "><p id="ddm_0600017__p10417182702317">Restore To</p>
</td>
<td class="cellrowborder" valign="top" width="75.13%" headers="mcps1.3.5.2.6.2.1.2.3.1.2 "><p id="ddm_0600017__p1541713271235">Specify a point in time. DDM will restore metadata to this point in time using the most recent backup.</p>
</td>
</tr>
<tr id="ddm_0600017__row164171527112318"><td class="cellrowborder" valign="top" width="24.87%" headers="mcps1.3.5.2.6.2.1.2.3.1.1 "><p id="ddm_0600017__p12417192719231">Destination DDM Instance</p>
</td>
<td class="cellrowborder" valign="top" width="75.13%" headers="mcps1.3.5.2.6.2.1.2.3.1.2 "><p id="ddm_0600017__p174171127142318">Select the DDM instance created in <a href="#ddm_0600017__li4793191882712">2</a> as the destination instance.</p>
</td>
</tr>
<tr id="ddm_0600017__row8417172719237"><td class="cellrowborder" valign="top" width="24.87%" headers="mcps1.3.5.2.6.2.1.2.3.1.1 "><p id="ddm_0600017__p1941772722315">Destination Data Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="75.13%" headers="mcps1.3.5.2.6.2.1.2.3.1.2 "><p id="ddm_0600017__p441719279239">Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="ddm_0600017__li160757161013"><span>Click <strong id="ddm_0600017__b4545118193711">OK</strong>. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.</span></li></ol>
</div>
<div class="section" id="ddm_0600017__section132806221525"><a name="ddm_0600017__section132806221525"></a><a name="section132806221525"></a><h4 class="sectiontitle">Restoring Metadata Using an Available Backup</h4><ol id="ddm_0600017__ol5281162245210"><li id="ddm_0600017__li106372611521"><span>Log in to the DDM console.</span></li><li id="ddm_0600017__li881143742017"><a name="ddm_0600017__li881143742017"></a><a name="li881143742017"></a><span><a href="ddm_06_00017.html">Create a new DDM instance</a>.</span></li><li id="ddm_0600017__li1828118220524"><span>In the navigation pane on the left, choose <strong id="ddm_0600017__b18421019163711">Backups</strong>.</span></li><li id="ddm_0600017__li1528112265210"><span>Locate the required backup based on the instance name and backup time and click <strong id="ddm_0600017__b137151723143718">Restore</strong> in the <strong id="ddm_0600017__b1371519233371">Operation</strong> column.</span><p><p id="ddm_0600017__p42821322165212"></p>
</p></li><li id="ddm_0600017__li10282152255212"><span>On the displayed page, configure required parameters.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_0600017__table5752162417313" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Parameter description</caption><thead align="left"><tr id="ddm_0600017__row13753624163111"><th align="left" class="cellrowborder" valign="top" width="26.26%" id="mcps1.3.6.2.5.2.1.2.3.1.1"><p id="ddm_0600017__p3753192410319">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="73.74000000000001%" id="mcps1.3.6.2.5.2.1.2.3.1.2"><p id="ddm_0600017__p7753924173119">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="ddm_0600017__row13753172417319"><td class="cellrowborder" valign="top" width="26.26%" headers="mcps1.3.6.2.5.2.1.2.3.1.1 "><p id="ddm_0600017__p475392418317">Backup Name</p>
</td>
<td class="cellrowborder" valign="top" width="73.74000000000001%" headers="mcps1.3.6.2.5.2.1.2.3.1.2 "><p id="ddm_0600017__p107531424133110">Name of the backup to be restored.</p>
</td>
</tr>
<tr id="ddm_0600017__row10753162412318"><td class="cellrowborder" valign="top" width="26.26%" headers="mcps1.3.6.2.5.2.1.2.3.1.1 "><p id="ddm_0600017__p7753924143114">Destination DDM Instance</p>
</td>
<td class="cellrowborder" valign="top" width="73.74000000000001%" headers="mcps1.3.6.2.5.2.1.2.3.1.2 "><p id="ddm_0600017__p275312248311">Select the DDM instance created in <a href="#ddm_0600017__li881143742017">2</a> as the destination instance.</p>
</td>
</tr>
<tr id="ddm_0600017__row7753524143120"><td class="cellrowborder" valign="top" width="26.26%" headers="mcps1.3.6.2.5.2.1.2.3.1.1 "><p id="ddm_0600017__p10753824153111">Destination Data Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="73.74000000000001%" headers="mcps1.3.6.2.5.2.1.2.3.1.2 "><p id="ddm_0600017__p375342483120">Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="ddm_0600017__li13282222195212"><span>Click <strong id="ddm_0600017__b10719115463710">OK</strong>. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0067.html">Backups and Restorations</a></div>
</div>
</div>

2
docs/ddm/umn/ddm_06_0001.html
View File

@ -4,7 +4,7 @@
<div id="body4656305"></div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="ddm_06_00017.html">Creating a DDM Instance</a></strong><br>
<li class="ulchildlink"><strong><a href="ddm_06_0132.html">Creating a DDM Instance</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="ddm_06_0025.html">Splitting Read-only and Read-Write Services</a></strong><br>
</li>

94
docs/ddm/umn/ddm_06_00017.html
View File

@ -1,94 +0,0 @@
<a name="ddm_06_00017"></a><a name="ddm_06_00017"></a>
<h1 class="topictitle1">Creating a DDM Instance</h1>
<div id="body0000001076623307"><div class="section" id="ddm_06_00017__section1539512419299"><h4 class="sectiontitle">Prerequisites</h4><p id="ddm_06_00017__p105251164135">You have logged in to the DDM console.</p>
</div>
<div class="section" id="ddm_06_00017__section9154117443"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_06_00017__ol17147626193112"><li id="ddm_06_00017__li18147172663112"><span>On the displayed page, in the upper right corner, click <strong id="ddm_06_00017__b776115125713">Create</strong> <strong id="ddm_06_00017__b1776214535713">DDM Instance</strong>.</span></li><li id="ddm_06_00017__li17771152918316"><span>On the displayed page, configure the required parameters.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_06_00017__table112871916153214" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="ddm_06_00017__ddm_06_0002_row9751102692514"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.2.2.2.2.1.2.3.1.1"><p id="ddm_06_00017__ddm_06_0002_p675112613254"><strong id="ddm_06_00017__ddm_06_0002_b747016188616">Parameter</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="85%" id="mcps1.3.2.2.2.2.1.2.3.1.2"><p id="ddm_06_00017__ddm_06_0002_p47511726162513"><strong id="ddm_06_00017__ddm_06_0002_b141267241165">Description</strong></p>
</th>
</tr>
</thead>
<tbody><tr id="ddm_06_00017__ddm_06_0002_row1751726122517"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p775122672516">Region</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p14751152662518">Region where the DDM instance is located. Select the required region.</p>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row7751142652510"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p117511826132515">AZ</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p157516264254">Availability zone where the DDM instance is deployed.</p>
<p id="ddm_06_00017__ddm_06_0002_p15156346343">Nodes in a DDM instance can be deployed on different physical servers in the same AZ to keep services always available even if one physical server becomes faulty.</p>
<p id="ddm_06_00017__ddm_06_0002_p1475152672520">A DDM instance can be deployed across AZs to provide cross-AZ DR.</p>
<p id="ddm_06_00017__ddm_06_0002_p14751172614258">If necessary, you can select multiple AZs when you create a DDM instance. Then nodes of the instance will be deployed in multiple different AZs.</p>
<div class="note" id="ddm_06_00017__ddm_06_0002_note45701042194119"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_00017__ddm_06_0002_p1557054224110">Deploy your application, DDM instance, and required RDS instances in the same AZ to reduce network latency. Cross-AZ deployment may increase network latency.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row1375302682515"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p575314262251">Instance Name</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p11753122672515">Name of the DDM instance, which:</p>
<ul id="ddm_06_00017__ddm_06_0002_ul1675322620259"><li id="ddm_06_00017__ddm_06_0002_li775319263257">Cannot be left blank.</li><li id="ddm_06_00017__ddm_06_0002_li27536269259">Must start with a letter.</li><li id="ddm_06_00017__ddm_06_0002_li875314262255">Must be 4 to 64 characters long.</li><li id="ddm_06_00017__ddm_06_0002_li147531426122519">Can contain only letters, digits, and hyphens (-).</li></ul>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row168121828104919"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p87511726112515">Node Class</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p0753172642512">Class of the DDM instance node. You can select <span class="uicontrol" id="ddm_06_00017__ddm_06_0002_uicontrol435661819428"><b>General-enhanced</b></span> or <span class="uicontrol" id="ddm_06_00017__ddm_06_0002_uicontrol236913187421"><b>Kunpeng general computing-plus</b></span> and then specify a node class.</p>
<div class="note" id="ddm_06_00017__ddm_06_0002_note1590513564213"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_00017__ddm_06_0002_p840511131335">Estimate compute and storage requirements of your applications based on your service type and scale before you create a DDM instance, and then select an appropriate node class so that the CPU and memory specifications of your DDM instance can better meet your needs.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row69742118516"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p1697461185119">Instance Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p179741111195119">Number of nodes in a DDM instance. Up to 32 nodes are supported. </p>
<div class="note" id="ddm_06_00017__ddm_06_0002_note1885285318449"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_00017__ddm_06_0002_p16381115154520">At least 2 nodes are recommended because using a single node cannot guarantee high availability.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row1575302622517"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p1775342611257">VPC</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p4753226132519">VPC that the DDM instance belongs to. This VPC isolates networks for different services. It allows you to manage and configure private networks, simplifying network management.</p>
<p id="ddm_06_00017__ddm_06_0002_p1875342618258">Click <strong id="ddm_06_00017__ddm_06_0002_b3672427422">View VPC</strong> to show more details and security group rules.</p>
<div class="note" id="ddm_06_00017__ddm_06_0002_note1527318329511"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_00017__ddm_06_0002_p1327343265116">The DDM instance should be in the same VPC as the required RDS for MySQL instance.</p>
<p id="ddm_06_00017__ddm_06_0002_p930541110587">To ensure network connectivity, the DDM instance you purchased must be in the same VPC as your applications and RDS for MySQL instances.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row1775462614254"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p1475314263250">Subnet</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p47531326132519">Name and IP address range of the subnet</p>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row197543269253"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p1675462615253">Security Group</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p4754162613256">Select an existing security group.</p>
<p id="ddm_06_00017__ddm_06_0002_p275419262254">You are advised to select the same security group for your DDM instance, application, and RDS for MySQL instances so that they can communicate with each other. If different security groups are selected, add security group rules to enable network access.</p>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row17754152662519"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p6842195115516">Parameter Template</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p3840165111553">Select an existing parameter template. You can also click <strong id="ddm_06_00017__ddm_06_0002_b3746172414520">View Parameter Template</strong> to set parameters on the displayed page.</p>
</td>
</tr>
<tr id="ddm_06_00017__ddm_06_0002_row145541234223"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_00017__ddm_06_0002_p55541133222">Tags</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_00017__ddm_06_0002_p33052204214">(Optional) Adding tags helps you better identify and manage your DDM resources.</p>
<p id="ddm_06_00017__ddm_06_0002_p10301317172010">You can add tags to your instance. Each instance can have a maximum of 20 tags.</p>
<p id="ddm_06_00017__ddm_06_0002_p518511568169"><strong id="ddm_06_00017__ddm_06_0002_b2055913016506">Tag key: This parameter is mandatory and cannot be null.</strong></p>
<ul id="ddm_06_00017__ddm_06_0002_ul7185125617166"><li id="ddm_06_00017__ddm_06_0002_li418535613169">Must be unique for each instance.</li><li id="ddm_06_00017__ddm_06_0002_li4623205412137">Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).</li><li id="ddm_06_00017__ddm_06_0002_li2185156201614">Can include 1 to 36 characters.</li><li id="ddm_06_00017__ddm_06_0002_li1218515651614">Cannot be an empty string or start with <strong id="ddm_06_00017__ddm_06_0002_b13858555813">_sys_</strong>.</li></ul>
<div class="p" id="ddm_06_00017__ddm_06_0002_p12846447155817"><strong id="ddm_06_00017__ddm_06_0002_b14774485403">Tag value: This parameter is mandatory.</strong><ul id="ddm_06_00017__ddm_06_0002_ul81858569165"><li id="ddm_06_00017__ddm_06_0002_li696611145920">Is an empty string by default.</li><li id="ddm_06_00017__ddm_06_0002_li557525001416">Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).</li><li id="ddm_06_00017__ddm_06_0002_li14185356131613">Can contain 0 to 43 characters.</li></ul>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="ddm_06_00017__li1079672992516"><span>After the configuration is complete, click Create Now at the bottom of the page.</span></li><li id="ddm_06_00017__li10119404163"><span>Confirm the configurations and click <span class="uicontrol" id="ddm_06_00017__uicontrol8785810144815"><b>Submit</b></span>.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_06_0001.html">Instance Management</a></div>
</div>
</div>

40
docs/ddm/umn/ddm_0600016.html → docs/ddm/umn/ddm_06_0016.html
View File

@ -1,47 +1,47 @@
<a name="ddm_0600016"></a><a name="ddm_0600016"></a>
<a name="ddm_06_0016"></a><a name="ddm_06_0016"></a>
<h1 class="topictitle1">Restoring Data to a New Instance</h1>
<div id="body0000001685194148"><p id="ddm_0600016__p1415815614540">DDM allows you to restore data from the current instance to any point in time using an existing backup. This is a good choice for routine service backup and restoration.</p>
<p id="ddm_0600016__p10381634123216">This section uses an RDS for MySQL instance as an example to describe how to restore data to a new DDM instance.</p>
<div class="section" id="ddm_0600016__section9831131045613"><h4 class="sectiontitle">Precautions</h4><ul id="ddm_0600016__ul086122419334"><li id="ddm_0600016__li148614241330">Restoring data to a new instance restores your DDM instance and its data nodes (RDS for MySQL instances). Before the restoration, you need to prepare a new DDM instance and as many new RDS for MySQL instances as there are data nodes.</li></ul>
<div id="body0000001685194148"><p id="ddm_06_0016__p1415815614540">DDM allows you to restore data from the current instance to any point in time using an existing backup. This is a good choice for routine service backup and restoration.</p>
<p id="ddm_06_0016__p10381634123216">This section uses an RDS for MySQL instance as an example to describe how to restore data to a new DDM instance.</p>
<div class="section" id="ddm_06_0016__section9831131045613"><h4 class="sectiontitle">Precautions</h4><ul id="ddm_06_0016__ul086122419334"><li id="ddm_06_0016__li148614241330">Restoring data to a new instance restores your DDM instance and its data nodes (RDS for MySQL instances). Before the restoration, you need to prepare a new DDM instance and as many new RDS for MySQL instances as there are data nodes.</li></ul>
</div>
<ul id="ddm_0600016__ul1983134241110"><li id="ddm_0600016__li884942201112">Restoring data to a new DDM instance will overwrite data on it and cause the instance to be unavailable during restoration.</li><li id="ddm_0600016__li9842424116">The new RDS for MySQL instances must have the same or later versions and as much as or more storage space than the original ones.</li><li id="ddm_0600016__li02281512112">Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.</li><li id="ddm_0600016__li10937638171916">The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.</li><li id="ddm_0600016__li3128144163914">Time points that data can be restored to depend on the backup policy set on original data nodes.</li></ul>
<div class="section" id="ddm_0600016__section56821323182215"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_0600016__ol5371100162518"><li id="ddm_0600016__li212881212410"><span>Log in to the DDM console.</span></li><li id="ddm_0600016__li4793191882712"><a name="ddm_0600016__li4793191882712"></a><a name="li4793191882712"></a><span>Create a new DDM instance in the region where the source DDM instance is located or select an existing DDM instance that meets the requirements. </span><p><div class="note" id="ddm_0600016__note1612301271217"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm_0600016__p9621531173616">Ensure that the new DDM instance or the selected existing DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.</p>
<ul id="ddm_06_0016__ul1983134241110"><li id="ddm_06_0016__li884942201112">Restoring data to a new DDM instance will overwrite data on it and cause the instance to be unavailable during restoration.</li><li id="ddm_06_0016__li9842424116">The new RDS for MySQL instances must have the same or later versions and as much as or more storage space than the original ones.</li><li id="ddm_06_0016__li02281512112">Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.</li><li id="ddm_06_0016__li10937638171916">The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.</li><li id="ddm_06_0016__li3128144163914">Time points that data can be restored to depend on the backup policy set on original data nodes.</li></ul>
<div class="section" id="ddm_06_0016__section56821323182215"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_06_0016__ol5371100162518"><li id="ddm_06_0016__li212881212410"><span>Log in to the DDM console.</span></li><li id="ddm_06_0016__li4793191882712"><a name="ddm_06_0016__li4793191882712"></a><a name="li4793191882712"></a><span>Create a new DDM instance in the region where the source DDM instance is located or select an existing DDM instance that meets the requirements. </span><p><div class="note" id="ddm_06_0016__note1612301271217"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="ddm_06_0016__p9621531173616">Ensure that the new DDM instance or the selected existing DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.</p>
</div></div>
</p></li><li id="ddm_0600016__li1017501443616"><a name="ddm_0600016__li1017501443616"></a><a name="li1017501443616"></a><span>On the RDS console, create as many RDS for MySQL instances as there are in the source DDM instance.</span><p><div class="note" id="ddm_0600016__note9182141942712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="ddm_0600016__ul722745823619"><li id="ddm_0600016__li6344193217464">Ensure that the new RDS instances have the same or later versions than RDS instances associated with the source DDM instance.</li><li id="ddm_0600016__li62301358173611">Ensure that each new RDS for MySQL instance has the same or larger storage space than each source RDS instance.</li></ul>
</p></li><li id="ddm_06_0016__li1017501443616"><a name="ddm_06_0016__li1017501443616"></a><a name="li1017501443616"></a><span>On the RDS console, create as many RDS for MySQL instances as there are in the source DDM instance.</span><p><div class="note" id="ddm_06_0016__note9182141942712"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="ddm_06_0016__ul722745823619"><li id="ddm_06_0016__li6344193217464">Ensure that the new RDS instances have the same or later versions than RDS instances associated with the source DDM instance.</li><li id="ddm_06_0016__li62301358173611">Ensure that each new RDS for MySQL instance has the same or larger storage space than each source RDS instance.</li></ul>
</div></div>
</p></li><li id="ddm_0600016__li203725032512"><span>Switch back to the DDM console, in the instance list, locate the DDM instance whose data you want to restore, and click its name.</span></li><li id="ddm_0600016__li2938164712387"><span>In the navigation pane on the left, choose <strong id="ddm_0600016__b35133551212">Backups &amp; Restorations</strong>.</span></li><li id="ddm_0600016__li723812134011"><span>Click <strong id="ddm_0600016__b1969121127">Restore to New Instance</strong>.</span></li><li id="ddm_0600016__li03361718184120"><span>On the displayed <strong id="ddm_0600016__b91921018425">Restore to New Instance</strong> page, specify a time range and a point in time, and select destination DDM instance and associated data nodes.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_0600016__table1237113116582" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="ddm_0600016__row1538831145819"><th align="left" class="cellrowborder" valign="top" width="23.01%" id="mcps1.3.5.2.7.2.1.2.3.1.1"><p id="ddm_0600016__p638123114582">Parameter</p>
</p></li><li id="ddm_06_0016__li203725032512"><span>Switch back to the DDM console, in the instance list, locate the DDM instance whose data you want to restore, and click its name.</span></li><li id="ddm_06_0016__li2938164712387"><span>In the navigation pane on the left, choose <strong id="ddm_06_0016__b35133551212">Backups &amp; Restorations</strong>.</span></li><li id="ddm_06_0016__li723812134011"><span>Click <strong id="ddm_06_0016__b1969121127">Restore to New Instance</strong>.</span></li><li id="ddm_06_0016__li03361718184120"><span>On the displayed <strong id="ddm_06_0016__b91921018425">Restore to New Instance</strong> page, specify a time range and a point in time, and select destination DDM instance and associated data nodes.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_06_0016__table1237113116582" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="ddm_06_0016__row1538831145819"><th align="left" class="cellrowborder" valign="top" width="23.01%" id="mcps1.3.5.2.7.2.1.2.3.1.1"><p id="ddm_06_0016__p638123114582">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="76.99000000000001%" id="mcps1.3.5.2.7.2.1.2.3.1.2"><p id="ddm_0600016__p1038163113581">Description</p>
<th align="left" class="cellrowborder" valign="top" width="76.99000000000001%" id="mcps1.3.5.2.7.2.1.2.3.1.2"><p id="ddm_06_0016__p1038163113581">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="ddm_0600016__row1438123114587"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_0600016__p5385316588">Time Range</p>
<tbody><tr id="ddm_06_0016__row1438123114587"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_06_0016__p5385316588">Time Range</p>
</td>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_0600016__p338163195816">Select a time range.</p>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_06_0016__p338163195816">Select a time range.</p>
</td>
</tr>
<tr id="ddm_0600016__row183811314587"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_0600016__p63817317582">Time Point</p>
<tr id="ddm_06_0016__row183811314587"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_06_0016__p63817317582">Time Point</p>
</td>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_0600016__p1538331165810">Select a time point.</p>
<p id="ddm_0600016__p6349530568">DDM checks whether the associated data nodes have available backups at the selected point in time.</p>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_06_0016__p1538331165810">Select a time point.</p>
<p id="ddm_06_0016__p6349530568">DDM checks whether the associated data nodes have available backups at the selected point in time.</p>
</td>
</tr>
<tr id="ddm_0600016__row93853135814"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_0600016__p4381931145816">Destination DDM Instance</p>
<tr id="ddm_06_0016__row93853135814"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_06_0016__p4381931145816">Destination DDM Instance</p>
</td>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_0600016__p123873118588">Select the DDM instance created in <a href="#ddm_0600016__li4793191882712">2</a> as the destination instance.</p>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_06_0016__p123873118588">Select the DDM instance created in <a href="#ddm_06_0016__li4793191882712">2</a> as the destination instance.</p>
</td>
</tr>
<tr id="ddm_0600016__row138133118587"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_0600016__p638113125820">Associated Data Nodes</p>
<tr id="ddm_06_0016__row138133118587"><td class="cellrowborder" valign="top" width="23.01%" headers="mcps1.3.5.2.7.2.1.2.3.1.1 "><p id="ddm_06_0016__p638113125820">Associated Data Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_0600016__p16381731185815">Select the RDS for MySQL instances created in <a href="#ddm_0600016__li1017501443616">3</a> as the destination data nodes.</p>
<td class="cellrowborder" valign="top" width="76.99000000000001%" headers="mcps1.3.5.2.7.2.1.2.3.1.2 "><p id="ddm_06_0016__p16381731185815">Select the RDS for MySQL instances created in <a href="#ddm_06_0016__li1017501443616">3</a> as the destination data nodes.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="ddm_0600016__li160757161013"><span>Confirm the information and click <strong id="ddm_0600016__b2240921633">OK</strong>. Wait for 1 to 3 minutes for the data restoration to complete.</span></li></ol>
</p></li><li id="ddm_06_0016__li160757161013"><span>Confirm the information and click <strong id="ddm_06_0016__b2240921633">OK</strong>. Wait for 1 to 3 minutes for the data restoration to complete.</span></li></ol>
</div>
</div>
<div>

73
docs/ddm/umn/ddm_06_0017.html Normal file
View File

@ -0,0 +1,73 @@
<a name="ddm_06_0017"></a><a name="ddm_06_0017"></a>
<h1 class="topictitle1">Restoring Metadata</h1>
<div id="body0000001733313057"><p id="ddm_06_0017__p9645118115513">DDM automatically backs up DDM instance metadata at 02:00 UTC+00:00 every day and retains the backup data for 30 days. Metadata backup is also triggered by key operations, such as deleting a schema, deleting data after shard configuration, and deleting instances.</p>
<p id="ddm_06_0017__p46473114585">When you delete a schema by mistake or your RDS for MySQL instances become abnormal, metadata restoration allows you to restore your DDM instance metadata and match the metadata with the RDS instance that has completed PITR to re-establish the relationship between your DDM instance and RDS instance. Metadata restoration supports only RDS for MySQL.</p>
<p id="ddm_06_0017__p533912361448">To restore metadata of a DDM instance, you can specify a point in time by referring to <a href="#ddm_06_0017__section128315484524">Restoring Metadata to a Point in Time</a>, or using an available backup by referring to <a href="#ddm_06_0017__section132806221525">Restoring Metadata Using Backups</a>.</p>
<p id="ddm_06_0017__p115306341696">Metadata restoration mainly restores the metadata of your DDM instance to a new DDM instance. It starts after a point-in-time recovery (PITR) for the associated data nodes is complete.</p>
<div class="section" id="ddm_06_0017__section738494914255"><h4 class="sectiontitle">Prerequisites</h4><ul id="ddm_06_0017__ul935817253264"><li id="ddm_06_0017__li23588251267">There is a source DDM instance available and associated with an RDS for MySQL instance. This DB instance is the source data node.</li><li id="ddm_06_0017__li10969101072817">The source data node has been restored to a specified time point.</li></ul>
</div>
<div class="section" id="ddm_06_0017__section16311542101119"><h4 class="sectiontitle">Constraints</h4><ul id="ddm_06_0017__ul1983134241110"><li id="ddm_06_0017__li884942201112">The destination DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.</li><li id="ddm_06_0017__li02281512112">Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.</li><li id="ddm_06_0017__li750871015158">The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.</li><li id="ddm_06_0017__li3128144163914">Time points that data can be restored to depend on the backup policy set on original data nodes.</li></ul>
</div>
<div class="section" id="ddm_06_0017__section128315484524"><a name="ddm_06_0017__section128315484524"></a><a name="section128315484524"></a><h4 class="sectiontitle">Restoring Metadata to a Point in Time</h4><ol id="ddm_06_0017__ol5371100162518"><li id="ddm_06_0017__li1366514210243"><span>Log in to the DDM console.</span></li><li id="ddm_06_0017__li4793191882712"><a name="ddm_06_0017__li4793191882712"></a><a name="li4793191882712"></a><span><a href="ddm_06_0132.html">Create a new DDM instance</a> and use it as the destination DDM instance. For details, see<a href="ddm_06_0132.html">Creating a DDM Instance</a>.</span></li><li id="ddm_06_0017__li203725032512"><span>In the DDM instance list, locate the source instance and click its name.</span></li><li id="ddm_06_0017__li382416102214"><span>In the navigation pane on the left, choose <strong id="ddm_06_0017__b2066407356621">Backups &amp; Restorations</strong>.</span></li><li id="ddm_06_0017__li723812134011"><span>Click <strong id="ddm_06_0017__b698802603620">Restore Metadata</strong>.</span></li><li id="ddm_06_0017__li179543119201"><span>On the displayed page, specify a time point. The source DDM instance will select an appropriate DDM metadata backup closest to the time point.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_06_0017__table1941672742313" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="ddm_06_0017__row11417102722314"><th align="left" class="cellrowborder" valign="top" width="24.87%" id="mcps1.3.7.2.6.2.1.2.3.1.1"><p id="ddm_06_0017__p10417112762314">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="75.13%" id="mcps1.3.7.2.6.2.1.2.3.1.2"><p id="ddm_06_0017__p4417172715233">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="ddm_06_0017__row2041742752312"><td class="cellrowborder" valign="top" width="24.87%" headers="mcps1.3.7.2.6.2.1.2.3.1.1 "><p id="ddm_06_0017__p10417182702317">Restore To</p>
</td>
<td class="cellrowborder" valign="top" width="75.13%" headers="mcps1.3.7.2.6.2.1.2.3.1.2 "><p id="ddm_06_0017__p1541713271235">Specify a point in time. DDM will restore metadata to this point in time using the most recent backup.</p>
</td>
</tr>
<tr id="ddm_06_0017__row164171527112318"><td class="cellrowborder" valign="top" width="24.87%" headers="mcps1.3.7.2.6.2.1.2.3.1.1 "><p id="ddm_06_0017__p12417192719231">Destination DDM Instance</p>
</td>
<td class="cellrowborder" valign="top" width="75.13%" headers="mcps1.3.7.2.6.2.1.2.3.1.2 "><p id="ddm_06_0017__p174171127142318">Select the DDM instance created in <a href="#ddm_06_0017__li4793191882712">2</a>.</p>
</td>
</tr>
<tr id="ddm_06_0017__row8417172719237"><td class="cellrowborder" valign="top" width="24.87%" headers="mcps1.3.7.2.6.2.1.2.3.1.1 "><p id="ddm_06_0017__p1941772722315">Destination Data Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="75.13%" headers="mcps1.3.7.2.6.2.1.2.3.1.2 "><p id="ddm_06_0017__p441719279239">Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="ddm_06_0017__li160757161013"><span>Click <strong id="ddm_06_0017__b4545118193711">OK</strong>. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.</span></li></ol>
</div>
<div class="section" id="ddm_06_0017__section132806221525"><a name="ddm_06_0017__section132806221525"></a><a name="section132806221525"></a><h4 class="sectiontitle">Restoring Metadata Using Backups</h4><ol id="ddm_06_0017__ol5281162245210"><li id="ddm_06_0017__li106372611521"><span>Log in to the DDM console.</span></li><li id="ddm_06_0017__li881143742017"><a name="ddm_06_0017__li881143742017"></a><a name="li881143742017"></a><span><a href="ddm_06_0132.html">Create a new DDM instance</a> and use it as the destination DDM instance. For details, see<a href="ddm_06_0132.html">Creating a DDM Instance</a>.</span></li><li id="ddm_06_0017__li2065410461265"><span>In the DDM instance list, locate the source instance and click its name.</span></li><li id="ddm_06_0017__li1828118220524"><span>In the navigation pane on the left, choose <strong id="ddm_06_0017__b18421019163711">Backups</strong>.</span></li><li id="ddm_06_0017__li1528112265210"><span>Locate the required backup based on the instance name and backup time and click <strong id="ddm_06_0017__b137151723143718">Restore</strong> in the <strong id="ddm_06_0017__b1371519233371">Operation</strong> column.</span><p><p id="ddm_06_0017__p42821322165212"></p>
</p></li><li id="ddm_06_0017__li10282152255212"><span>On the displayed page, configure required parameters.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_06_0017__table5752162417313" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Parameter description</caption><thead align="left"><tr id="ddm_06_0017__row13753624163111"><th align="left" class="cellrowborder" valign="top" width="26.26%" id="mcps1.3.8.2.6.2.1.2.3.1.1"><p id="ddm_06_0017__p3753192410319">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="73.74000000000001%" id="mcps1.3.8.2.6.2.1.2.3.1.2"><p id="ddm_06_0017__p7753924173119">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="ddm_06_0017__row13753172417319"><td class="cellrowborder" valign="top" width="26.26%" headers="mcps1.3.8.2.6.2.1.2.3.1.1 "><p id="ddm_06_0017__p475392418317">Backup Name</p>
</td>
<td class="cellrowborder" valign="top" width="73.74000000000001%" headers="mcps1.3.8.2.6.2.1.2.3.1.2 "><p id="ddm_06_0017__p107531424133110">Name of the backup to be restored.</p>
</td>
</tr>
<tr id="ddm_06_0017__row10753162412318"><td class="cellrowborder" valign="top" width="26.26%" headers="mcps1.3.8.2.6.2.1.2.3.1.1 "><p id="ddm_06_0017__p7753924143114">Destination DDM Instance</p>
</td>
<td class="cellrowborder" valign="top" width="73.74000000000001%" headers="mcps1.3.8.2.6.2.1.2.3.1.2 "><p id="ddm_06_0017__p275312248311">Select the DDM instance created in <a href="#ddm_06_0017__li881143742017">2</a>.</p>
</td>
</tr>
<tr id="ddm_06_0017__row7753524143120"><td class="cellrowborder" valign="top" width="26.26%" headers="mcps1.3.8.2.6.2.1.2.3.1.1 "><p id="ddm_06_0017__p10753824153111">Destination Data Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="73.74000000000001%" headers="mcps1.3.8.2.6.2.1.2.3.1.2 "><p id="ddm_06_0017__p375342483120">Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.</p>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="ddm_06_0017__li13282222195212"><span>Click <strong id="ddm_06_0017__b1171242963619">OK</strong>. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_03_0067.html">Backups and Restorations</a></div>
</div>
</div>

94
docs/ddm/umn/ddm_06_0132.html Normal file
View File

@ -0,0 +1,94 @@
<a name="ddm_06_0132"></a><a name="ddm_06_0132"></a>
<h1 class="topictitle1">Creating a DDM Instance</h1>
<div id="body0000001076623307"><div class="section" id="ddm_06_0132__section1539512419299"><h4 class="sectiontitle">Prerequisites</h4><p id="ddm_06_0132__p105251164135">You have logged in to the DDM console.</p>
</div>
<div class="section" id="ddm_06_0132__section9154117443"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_06_0132__ol17147626193112"><li id="ddm_06_0132__li18147172663112"><span>On the displayed page, in the upper right corner, click <strong id="ddm_06_0132__b776115125713">Create</strong> <strong id="ddm_06_0132__b1776214535713">DDM Instance</strong>.</span></li><li id="ddm_06_0132__li17771152918316"><span>On the displayed page, configure the required parameters.</span><p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ddm_06_0132__table112871916153214" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="ddm_06_0132__ddm_06_0002_row9751102692514"><th align="left" class="cellrowborder" valign="top" width="15%" id="mcps1.3.2.2.2.2.1.2.3.1.1"><p id="ddm_06_0132__ddm_06_0002_p675112613254"><strong id="ddm_06_0132__ddm_06_0002_b747016188616">Parameter</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="85%" id="mcps1.3.2.2.2.2.1.2.3.1.2"><p id="ddm_06_0132__ddm_06_0002_p47511726162513"><strong id="ddm_06_0132__ddm_06_0002_b141267241165">Description</strong></p>
</th>
</tr>
</thead>
<tbody><tr id="ddm_06_0132__ddm_06_0002_row1751726122517"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p775122672516">Region</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p14751152662518">Region where the DDM instance is located. Select the required region.</p>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row7751142652510"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p117511826132515">AZ</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p157516264254">Availability zone where the DDM instance is deployed.</p>
<p id="ddm_06_0132__ddm_06_0002_p15156346343">Nodes in a DDM instance can be deployed on different physical servers in the same AZ to keep services always available even if one physical server becomes faulty.</p>
<p id="ddm_06_0132__ddm_06_0002_p1475152672520">A DDM instance can be deployed across AZs to provide cross-AZ DR.</p>
<p id="ddm_06_0132__ddm_06_0002_p14751172614258">If necessary, you can select multiple AZs when you create a DDM instance. Then nodes of the instance will be deployed in multiple different AZs.</p>
<div class="note" id="ddm_06_0132__ddm_06_0002_note45701042194119"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_0132__ddm_06_0002_p1557054224110">Deploy your application, DDM instance, and required RDS instances in the same AZ to reduce network latency. Cross-AZ deployment may increase network latency.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row1375302682515"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p575314262251">Instance Name</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p11753122672515">Name of the DDM instance, which:</p>
<ul id="ddm_06_0132__ddm_06_0002_ul1675322620259"><li id="ddm_06_0132__ddm_06_0002_li775319263257">Cannot be left blank.</li><li id="ddm_06_0132__ddm_06_0002_li27536269259">Must start with a letter.</li><li id="ddm_06_0132__ddm_06_0002_li875314262255">Must be 4 to 64 characters long.</li><li id="ddm_06_0132__ddm_06_0002_li147531426122519">Can contain only letters, digits, and hyphens (-).</li></ul>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row168121828104919"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p87511726112515">Node Class</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p0753172642512">Class of the DDM instance node. You can select <span class="uicontrol" id="ddm_06_0132__ddm_06_0002_uicontrol435661819428"><b>General-enhanced</b></span> or <span class="uicontrol" id="ddm_06_0132__ddm_06_0002_uicontrol236913187421"><b>Kunpeng general computing-plus</b></span> and then specify a node class.</p>
<div class="note" id="ddm_06_0132__ddm_06_0002_note1590513564213"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_0132__ddm_06_0002_p840511131335">Estimate compute and storage requirements of your applications based on your service type and scale before you create a DDM instance, and then select an appropriate node class so that the CPU and memory specifications of your DDM instance can better meet your needs.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row69742118516"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p1697461185119">Instance Nodes</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p179741111195119">Number of nodes in a DDM instance. Up to 32 nodes are supported. </p>
<div class="note" id="ddm_06_0132__ddm_06_0002_note1885285318449"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_0132__ddm_06_0002_p16381115154520">At least 2 nodes are recommended because using a single node cannot guarantee high availability.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row1575302622517"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p1775342611257">VPC</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p4753226132519">VPC that the DDM instance belongs to. This VPC isolates networks for different services. It allows you to manage and configure private networks, simplifying network management.</p>
<p id="ddm_06_0132__ddm_06_0002_p1875342618258">Click <strong id="ddm_06_0132__ddm_06_0002_b3672427422">View VPC</strong> to show more details and security group rules.</p>
<div class="note" id="ddm_06_0132__ddm_06_0002_note1527318329511"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="ddm_06_0132__ddm_06_0002_p1327343265116">The DDM instance should be in the same VPC as the required RDS for MySQL instance.</p>
<p id="ddm_06_0132__ddm_06_0002_p930541110587">To ensure network connectivity, the DDM instance you purchased must be in the same VPC as your applications and RDS for MySQL instances.</p>
</div></div>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row1775462614254"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p1475314263250">Subnet</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p47531326132519">Name and IP address range of the subnet</p>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row197543269253"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p1675462615253">Security Group</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p4754162613256">Select an existing security group.</p>
<p id="ddm_06_0132__ddm_06_0002_p275419262254">You are advised to select the same security group for your DDM instance, application, and RDS for MySQL instances so that they can communicate with each other. If different security groups are selected, add security group rules to enable network access.</p>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row17754152662519"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p6842195115516">Parameter Template</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p3840165111553">Select an existing parameter template. You can also click <strong id="ddm_06_0132__ddm_06_0002_b3746172414520">View Parameter Template</strong> to set parameters on the displayed page.</p>
</td>
</tr>
<tr id="ddm_06_0132__ddm_06_0002_row145541234223"><td class="cellrowborder" valign="top" width="15%" headers="mcps1.3.2.2.2.2.1.2.3.1.1 "><p id="ddm_06_0132__ddm_06_0002_p55541133222">Tags</p>
</td>
<td class="cellrowborder" valign="top" width="85%" headers="mcps1.3.2.2.2.2.1.2.3.1.2 "><p id="ddm_06_0132__ddm_06_0002_p33052204214">(Optional) Adding tags helps you better identify and manage your DDM resources.</p>
<p id="ddm_06_0132__ddm_06_0002_p10301317172010">You can add tags to your instance. Each instance can have a maximum of 20 tags.</p>
<p id="ddm_06_0132__ddm_06_0002_p518511568169"><strong id="ddm_06_0132__ddm_06_0002_b2055913016506">Tag key: This parameter is mandatory and cannot be null.</strong></p>
<ul id="ddm_06_0132__ddm_06_0002_ul7185125617166"><li id="ddm_06_0132__ddm_06_0002_li418535613169">Must be unique for each instance.</li><li id="ddm_06_0132__ddm_06_0002_li4623205412137">Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).</li><li id="ddm_06_0132__ddm_06_0002_li2185156201614">Can include 1 to 36 characters.</li><li id="ddm_06_0132__ddm_06_0002_li1218515651614">Cannot be an empty string or start with <strong id="ddm_06_0132__ddm_06_0002_b13858555813">_sys_</strong>.</li></ul>
<div class="p" id="ddm_06_0132__ddm_06_0002_p12846447155817"><strong id="ddm_06_0132__ddm_06_0002_b14774485403">Tag value: This parameter is mandatory.</strong><ul id="ddm_06_0132__ddm_06_0002_ul81858569165"><li id="ddm_06_0132__ddm_06_0002_li696611145920">Is an empty string by default.</li><li id="ddm_06_0132__ddm_06_0002_li557525001416">Can only consist of digits, letters, underscores (_), hyphens (-), and at sign (@).</li><li id="ddm_06_0132__ddm_06_0002_li14185356131613">Can contain 0 to 43 characters.</li></ul>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</p></li><li id="ddm_06_0132__li1079672992516"><span>After the configuration is complete, click Create Now at the bottom of the page.</span></li><li id="ddm_06_0132__li10119404163"><span>Confirm the configurations and click <span class="uicontrol" id="ddm_06_0132__uicontrol8785810144815"><b>Submit</b></span>.</span></li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_06_0001.html">Instance Management</a></div>
</div>
</div>

Some files were not shown because too many files have changed in this diff Show More