geminidb_umn
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: wangdengke2 <wangdengke2@huawei.com> Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
|
Before Width: | Height: | Size: 214 B After Width: | Height: | Size: 214 B |
|
Before Width: | Height: | Size: 389 B After Width: | Height: | Size: 389 B |
|
Before Width: | Height: | Size: 389 B After Width: | Height: | Size: 389 B |
|
Before Width: | Height: | Size: 214 B After Width: | Height: | Size: 214 B |
|
Before Width: | Height: | Size: 1004 B After Width: | Height: | Size: 1004 B |
BIN
docs/geminidb/umn/en-us_image_0000002417434604.png
Normal file
|
After Width: | Height: | Size: 214 B |
|
Before Width: | Height: | Size: 117 KiB After Width: | Height: | Size: 117 KiB |
|
Before Width: | Height: | Size: 567 B After Width: | Height: | Size: 567 B |
|
Before Width: | Height: | Size: 295 B After Width: | Height: | Size: 295 B |
|
Before Width: | Height: | Size: 540 B After Width: | Height: | Size: 540 B |
BIN
docs/geminidb/umn/en-us_image_0000002417594332.png
Normal file
|
After Width: | Height: | Size: 241 B |
|
Before Width: | Height: | Size: 248 B After Width: | Height: | Size: 248 B |
|
Before Width: | Height: | Size: 293 B After Width: | Height: | Size: 293 B |
BIN
docs/geminidb/umn/en-us_image_0000002417594376.png
Normal file
|
After Width: | Height: | Size: 293 B |
BIN
docs/geminidb/umn/en-us_image_0000002417594456.png
Normal file
|
After Width: | Height: | Size: 295 B |
|
Before Width: | Height: | Size: 1004 B After Width: | Height: | Size: 1004 B |
|
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 82 KiB After Width: | Height: | Size: 82 KiB |
BIN
docs/geminidb/umn/en-us_image_0000002417594664.png
Normal file
|
After Width: | Height: | Size: 214 B |
|
Before Width: | Height: | Size: 1004 B After Width: | Height: | Size: 1004 B |
BIN
docs/geminidb/umn/en-us_image_0000002450993413.png
Normal file
|
After Width: | Height: | Size: 477 B |
|
Before Width: | Height: | Size: 296 B After Width: | Height: | Size: 296 B |
BIN
docs/geminidb/umn/en-us_image_0000002450993545.png
Normal file
|
After Width: | Height: | Size: 296 B |
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 1004 B After Width: | Height: | Size: 1004 B |
|
Before Width: | Height: | Size: 389 B After Width: | Height: | Size: 389 B |
BIN
docs/geminidb/umn/en-us_image_0000002451073389.png
Normal file
|
After Width: | Height: | Size: 1004 B |
|
Before Width: | Height: | Size: 126 KiB After Width: | Height: | Size: 126 KiB |
BIN
docs/geminidb/umn/en-us_image_0000002451073417.png
Normal file
|
After Width: | Height: | Size: 389 B |
BIN
docs/geminidb/umn/en-us_image_0000002451073449.png
Normal file
|
After Width: | Height: | Size: 389 B |
BIN
docs/geminidb/umn/en-us_image_0000002451073457.png
Normal file
|
After Width: | Height: | Size: 389 B |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 102 KiB After Width: | Height: | Size: 102 KiB |
BIN
docs/geminidb/umn/en-us_image_0000002547619553.png
Normal file
|
After Width: | Height: | Size: 202 KiB |
BIN
docs/geminidb/umn/en-us_image_0000002548274029.png
Normal file
|
After Width: | Height: | Size: 600 B |
@ -18,6 +18,13 @@
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.3 "><p id="nosql_01_0007__p178173167253">3.11 and 4.0</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="nosql_01_0007__row08552097306"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.1 "><p id="nosql_01_0007__p914295017588">InfluxDB</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.2 "><p id="nosql_01_0007__p148565910303">Cluster (performance-enhanced)</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.1.3 "><p id="nosql_01_0007__p28568983012">1.7</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
<a name="nosql_01_0010"></a><a name="nosql_01_0010"></a>
|
||||
|
||||
<h1 class="topictitle1">Typical Application Scenarios</h1>
|
||||
<div id="body1558943571786"><div class="section" id="nosql_01_0010__section8477172513453"><h4 class="sectiontitle">IoT</h4><p id="nosql_01_0010__p3687103794412"><span id="nosql_01_0010__text4303161512381">GeminiDB</span> is compatible with Cassandra APIs. It is designed for write-intensive scenarios, specifically applied in manufacturing, logistics, health care, real estate, energy production, and agriculture. It can process data sent by different types of sensors for further analysis.</p>
|
||||
<div id="body1558943571786"><div class="section" id="nosql_01_0010__section8477172513453"><h4 class="sectiontitle">IoT</h4><p id="nosql_01_0010__p3687103794412"><span id="nosql_01_0010__text4303161512381">GeminiDB</span> is compatible with Cassandra. It is designed for write-intensive scenarios, specifically in manufacturing, logistics, health care, real estate, energy production, and agriculture sectors. It can process data from different types of sensors for further analysis.</p>
|
||||
<p id="nosql_01_0010__p1868743716445"><strong id="nosql_01_0010__b11971247125118">Highlights</strong></p>
|
||||
<ul id="nosql_01_0010__ul1966331415497"><li id="nosql_01_0010__li6664814174911"><strong id="nosql_01_0010__b1349479104210">High Write Performance</strong>: GeminiDB provides higher write performance than other NoSQL services.</li><li id="nosql_01_0010__li8664171411496"><strong id="nosql_01_0010__b74551950114211">High Scalability</strong>: Compute nodes can be scaled in or out to flexibly cope with traffic surges or large writes loads at any time.</li></ul>
|
||||
</div>
|
||||
@ -9,10 +9,24 @@
|
||||
<p id="nosql_01_0010__p1317250184418"><strong id="nosql_01_0010__b19221951165118">Highlights</strong></p>
|
||||
<ul id="nosql_01_0010__ul117364744810"><li id="nosql_01_0010__li173647154813"><strong id="nosql_01_0010__b8302191904418">High Write Performance</strong>: GeminiDB provides higher write performance than other NoSQL services.</li><li id="nosql_01_0010__li18736677484"><strong id="nosql_01_0010__b1622414477443">Big Data Analysis</strong>: GeminiDB can work with Spark to provide recommendations to your customers in real-time.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_01_0010__section394685515450"><h4 class="sectiontitle">Finance</h4><p id="nosql_01_0010__p086912597441">With Spark′s big data analysis capabilities, <span id="nosql_01_0010__text20150144718382">GeminiDB</span> helps companies in the finance sector build risk control systems and mitigate fraud.</p>
|
||||
<div class="section" id="nosql_01_0010__section394685515450"><h4 class="sectiontitle">Finance</h4><p id="nosql_01_0010__p086912597441">By leveraging big data analysis tools such as Spark, <span id="nosql_01_0010__text20150144718382">GeminiDB</span> helps companies in the finance sector build risk control systems and mitigate fraud.</p>
|
||||
<p id="nosql_01_0010__p1886915994413"><strong id="nosql_01_0010__b592585113517">Highlights</strong></p>
|
||||
<p id="nosql_01_0010__p106915463817"><strong id="nosql_01_0010__b11975174174520">Big Data Analysis</strong>: Spark and other big data processing technologies enable real-time fraud detection and prevention.</p>
|
||||
</div>
|
||||
<div class="section" id="nosql_01_0010__section19517123063610"><h4 class="sectiontitle">Securities and Cryptocurrency Transactions</h4><p id="nosql_01_0010__p751494912311">GeminiDB Influx API stores user bank statements and builds an anti-fraud system for the financial industry.</p>
|
||||
<p id="nosql_01_0010__p205143499313"><strong id="nosql_01_0010__b0928115155112">Highlights</strong></p>
|
||||
<ul id="nosql_01_0010__ul7903131763717"><li id="nosql_01_0010__li790311176373"><strong id="nosql_01_0010__b1924615573327">Efficient query</strong>: GeminiDB Influx instances are deployed nearby, so they can quickly address queries.</li></ul>
|
||||
<ul id="nosql_01_0010__ul844102103717"><li id="nosql_01_0010__li12441102118377"><strong id="nosql_01_0010__b99437438820">Real-time analysis</strong>: Series data can be synchronized to the cloud and can be analyzed in real time.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_01_0010__section01305486378"><h4 class="sectiontitle">Real-Time Monitoring of Hardware and Software</h4><p id="nosql_01_0010__p17824110163412">GeminiDB Influx API stores user behavior data, accelerating user profiling and precision marketing.</p>
|
||||
<p id="nosql_01_0010__p15824703344"><strong id="nosql_01_0010__b203391639145110">Highlights</strong></p>
|
||||
<ul id="nosql_01_0010__ul1554612283811"><li id="nosql_01_0010__li65462223810">GeminiDB Influx API handles trillions of data points per day and supports multi-node and multi-thread parallel queries.</li></ul>
|
||||
<ul id="nosql_01_0010__ul33341059388"><li id="nosql_01_0010__li633411553816"><strong id="nosql_01_0010__b2952540181419">Real-time analysis</strong>: Series data can be synchronized to the cloud and can be analyzed in real time.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_01_0010__section81441425203817"><h4 class="sectiontitle">Environmental Protection Industry</h4><p id="nosql_01_0010__p18911241143520">GeminiDB Influx API supports writes of massive amounts of time series data, stable and reliable for environmental protection data collection.</p>
|
||||
<p id="nosql_01_0010__p2091204117356"><strong id="nosql_01_0010__b1034383915114">Highlights</strong></p>
|
||||
<p id="nosql_01_0010__p1291134193512"><strong id="nosql_01_0010__b18394250111616">Efficient write and query</strong>: Vectorized query engines and efficient time series data query operators such as aggregation and convolution can process enormous concurrent writes and queries.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
|
||||
@ -8,7 +8,7 @@
|
||||
</li></ul>
|
||||
<ul id="nosql_02_0004__ul11655735142317"><li id="nosql_02_0004__li18793238132312">By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0004__section9281154719202"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_02_0004__ol49383781586"><li id="nosql_02_0004__li93899141586"><span>Log in to the management console.</span></li><li id="nosql_02_0004__li1870917810588"><span>Click <span><img id="nosql_02_0004__image145037112071" src="en-us_image_0000001815205124.png"></span> in the upper left corner and select a region and a project.</span></li><li id="nosql_02_0004__li297543615857"><span>Click <strong id="nosql_02_0004__b16609152125710">Service List</strong>. Under <strong id="nosql_02_0004__b12610162114575">Network</strong>, click <strong id="nosql_02_0004__b1061219218575">Virtual Private Cloud</strong>.</span></li><li id="nosql_02_0004__li3171015115916"><span>In the navigation pane on the left, choose <span class="menucascade" id="nosql_02_0004__menucascade113137392162"><b><span class="uicontrol" id="nosql_02_0004__uicontrol931312398163">Access Control</span></b> > <b><span class="uicontrol" id="nosql_02_0004__uicontrol103131952161613">Security Groups</span></b></span>.</span></li><li id="nosql_02_0004__li140569415930"><span>On the <strong id="nosql_02_0004__b497332911519">Security Groups</strong> page, click the security group name.</span></li><li id="nosql_02_0004__li5489049115946"><span>On the <strong id="nosql_02_0004__b4976153713515">Inbound Rules</strong> tab, click <strong id="nosql_02_0004__b1697715371258">Add Rule</strong>. In the displayed <strong id="nosql_02_0004__b297743711512">Add Inbound Rule</strong> dialog box, set required parameters to add inbound rules. On the <strong id="nosql_02_0004__b271817563411">Outbound Rules</strong> tab, click <strong id="nosql_02_0004__b37191456543">Add Rule</strong>. In the displayed <strong id="nosql_02_0004__b37191156048">Add Outbound Rule</strong> dialog box, set required parameters to add outbound rules.</span></li><li id="nosql_02_0004__li436714418571"><span>In the displayed dialog box, set required parameters.</span></li><li id="nosql_02_0004__li21369327151121"><span>Click <strong id="nosql_02_0004__b191192582312">OK</strong>.</span></li></ol>
|
||||
<div class="section" id="nosql_02_0004__section9281154719202"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_02_0004__ol49383781586"><li id="nosql_02_0004__li93899141586"><span>Log in to the management console.</span></li><li id="nosql_02_0004__li1870917810588"><span>Click <span><img id="nosql_02_0004__image145037112071" src="en-us_image_0000002417594484.png"></span> in the upper left corner and select a region and a project.</span></li><li id="nosql_02_0004__li297543615857"><span>Click <strong id="nosql_02_0004__b16609152125710">Service List</strong>. Under <strong id="nosql_02_0004__b12610162114575">Network</strong>, click <strong id="nosql_02_0004__b1061219218575">Virtual Private Cloud</strong>.</span></li><li id="nosql_02_0004__li3171015115916"><span>In the navigation pane on the left, choose <span class="menucascade" id="nosql_02_0004__menucascade113137392162"><b><span class="uicontrol" id="nosql_02_0004__uicontrol931312398163">Access Control</span></b> > <b><span class="uicontrol" id="nosql_02_0004__uicontrol103131952161613">Security Groups</span></b></span>.</span></li><li id="nosql_02_0004__li140569415930"><span>On the <strong id="nosql_02_0004__b497332911519">Security Groups</strong> page, click the security group name.</span></li><li id="nosql_02_0004__li5489049115946"><span>On the <strong id="nosql_02_0004__b4976153713515">Inbound Rules</strong> tab, click <strong id="nosql_02_0004__b1697715371258">Add Rule</strong>. In the displayed <strong id="nosql_02_0004__b297743711512">Add Inbound Rule</strong> dialog box, set required parameters to add inbound rules. On the <strong id="nosql_02_0004__b271817563411">Outbound Rules</strong> tab, click <strong id="nosql_02_0004__b37191456543">Add Rule</strong>. In the displayed <strong id="nosql_02_0004__b37191156048">Add Outbound Rule</strong> dialog box, set required parameters to add outbound rules.</span></li><li id="nosql_02_0004__li436714418571"><span>In the displayed dialog box, set required parameters.</span></li><li id="nosql_02_0004__li21369327151121"><span>Click <strong id="nosql_02_0004__b191192582312">OK</strong>.</span></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
@ -6,7 +6,7 @@
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0011__en-us_topic_0249811530_section9456131432010"><h4 class="sectiontitle"><strong id="nosql_02_0011__en-us_topic_0249811530_b622952211485">Precautions</strong></h4><ul id="nosql_02_0011__ul205571531163210"><li id="nosql_02_0011__li15557173173216">By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.</li><li id="nosql_02_0011__li91454673219">To access a <span id="nosql_02_0011__text92192397449">GeminiDB Cassandra</span> instance from resources outside the security group, you need to configure an inbound rule to allow access to the <span id="nosql_02_0011__text1356754617444">GeminiDB Cassandra</span> instance.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0011__en-us_topic_0249811530_section9281154719202"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_02_0011__ol49383781586"><li id="nosql_02_0011__li93899141586"><span>Log in to the management console.</span></li><li id="nosql_02_0011__li1870917810588"><span>Click <span><img id="nosql_02_0011__image145037112071" src="en-us_image_0000001861844977.png"></span> in the upper left corner and select a region and a project.</span></li><li id="nosql_02_0011__li297543615857"><span>Click <strong id="nosql_02_0011__b1366210549553">Service List</strong>. Under <strong id="nosql_02_0011__b1966319541559">Network</strong>, click <strong id="nosql_02_0011__b11664155413553">Virtual Private Cloud</strong>.</span></li><li id="nosql_02_0011__li3171015115916"><span>In the navigation pane on the left, choose <span class="menucascade" id="nosql_02_0011__en-us_topic_0249811530_menucascade113137392162"><b><span class="uicontrol" id="nosql_02_0011__uicontrol931312398163">Access Control</span></b> > <b><span class="uicontrol" id="nosql_02_0011__uicontrol103131952161613">Security Groups</span></b></span>.</span></li><li id="nosql_02_0011__li140569415930"><span>On the <strong id="nosql_02_0011__en-us_topic_0249811530_b497332911519">Security Groups</strong> page, click the security group name.</span></li><li id="nosql_02_0011__li5489049115946"><span>On the <strong id="nosql_02_0011__en-us_topic_0249811530_b4976153713515">Inbound Rules</strong> tab, click <strong id="nosql_02_0011__en-us_topic_0249811530_b1697715371258">Add Rule</strong>. In the displayed <strong id="nosql_02_0011__en-us_topic_0249811530_b297743711512">Add Inbound Rule</strong> dialog box, set required parameters to add inbound rules. On the <strong id="nosql_02_0011__en-us_topic_0249811530_b271817563411">Outbound Rules</strong> tab, click <strong id="nosql_02_0011__en-us_topic_0249811530_b37191456543">Add Rule</strong>. In the displayed <strong id="nosql_02_0011__en-us_topic_0249811530_b37191156048">Add Outbound Rule</strong> dialog box, set required parameters to add outbound rules.</span></li><li id="nosql_02_0011__li186941447135716"><span>In the displayed dialog box, set required parameters.</span></li><li id="nosql_02_0011__li21369327151121"><span>Click <strong id="nosql_02_0011__b1897812399275">OK</strong>.</span></li></ol>
|
||||
<div class="section" id="nosql_02_0011__en-us_topic_0249811530_section9281154719202"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_02_0011__ol49383781586"><li id="nosql_02_0011__li93899141586"><span>Log in to the management console.</span></li><li id="nosql_02_0011__li1870917810588"><span>Click <span><img id="nosql_02_0011__image145037112071" src="en-us_image_0000002450993685.png"></span> in the upper left corner and select a region and a project.</span></li><li id="nosql_02_0011__li297543615857"><span>Click <strong id="nosql_02_0011__b1366210549553">Service List</strong>. Under <strong id="nosql_02_0011__b1966319541559">Network</strong>, click <strong id="nosql_02_0011__b11664155413553">Virtual Private Cloud</strong>.</span></li><li id="nosql_02_0011__li3171015115916"><span>In the navigation pane on the left, choose <span class="menucascade" id="nosql_02_0011__en-us_topic_0249811530_menucascade113137392162"><b><span class="uicontrol" id="nosql_02_0011__uicontrol931312398163">Access Control</span></b> > <b><span class="uicontrol" id="nosql_02_0011__uicontrol103131952161613">Security Groups</span></b></span>.</span></li><li id="nosql_02_0011__li140569415930"><span>On the <strong id="nosql_02_0011__en-us_topic_0249811530_b497332911519">Security Groups</strong> page, click the security group name.</span></li><li id="nosql_02_0011__li5489049115946"><span>On the <strong id="nosql_02_0011__en-us_topic_0249811530_b4976153713515">Inbound Rules</strong> tab, click <strong id="nosql_02_0011__en-us_topic_0249811530_b1697715371258">Add Rule</strong>. In the displayed <strong id="nosql_02_0011__en-us_topic_0249811530_b297743711512">Add Inbound Rule</strong> dialog box, set required parameters to add inbound rules. On the <strong id="nosql_02_0011__en-us_topic_0249811530_b271817563411">Outbound Rules</strong> tab, click <strong id="nosql_02_0011__en-us_topic_0249811530_b37191456543">Add Rule</strong>. In the displayed <strong id="nosql_02_0011__en-us_topic_0249811530_b37191156048">Add Outbound Rule</strong> dialog box, set required parameters to add outbound rules.</span></li><li id="nosql_02_0011__li186941447135716"><span>In the displayed dialog box, set required parameters.</span></li><li id="nosql_02_0011__li21369327151121"><span>Click <strong id="nosql_02_0011__b1897812399275">OK</strong>.</span></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
19
docs/geminidb/umn/nosql_02_0050.html
Normal file
@ -0,0 +1,19 @@
|
||||
<a name="nosql_02_0050"></a><a name="nosql_02_0050"></a>
|
||||
|
||||
<h1 class="topictitle1">Getting Started with <span id="text33451613183213">GeminiDB Influx</span></h1>
|
||||
<div id="body1575537965814"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="nosql_06_0010.html">Instance Connection Methods</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="nosql_02_0051.html">Creating a GeminiDB Influx Instance</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="nosql_09_0092.html">Connecting to a GeminiDB Influx Instance on the Console</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="nosql_06_0015.html">Connecting to a GeminiDB Influx Instance Over Private Networks</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="nosql_09_0100.html">Connecting to a GeminiDB Influx Instance Using Program Code</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
192
docs/geminidb/umn/nosql_02_0051.html
Normal file
36
docs/geminidb/umn/nosql_02_0052.html
Normal file
@ -0,0 +1,36 @@
|
||||
<a name="nosql_02_0052"></a><a name="nosql_02_0052"></a>
|
||||
|
||||
<h1 class="topictitle1">Configuring Security Group Rules</h1>
|
||||
<div id="body8662426"><div class="section" id="nosql_02_0052__en-us_topic_0249811530_section3152058916230"><h4 class="sectiontitle">Scenarios</h4><p id="nosql_02_0052__en-us_topic_0249811530_p199191161250">The default security group rule allows all outgoing data packets. <span id="nosql_02_0052__en-us_topic_0249811530_text84651218553">ECS</span><span id="nosql_02_0052__en-us_topic_0249811530_text154659184517"></span>s and <span id="nosql_02_0052__en-us_topic_0249811530_text346516182514">GeminiDB</span> instances in the same security group can access each other. After a security group is created, you can define different access rules. After a <span id="nosql_02_0052__en-us_topic_0249811530_text24651218954">GeminiDB</span> instance is added to the security group, it is protected by the access rules.</p>
|
||||
<p id="nosql_02_0052__en-us_topic_0249811530_p43222116204125">The following describes how to set security groups.</p>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0052__en-us_topic_0249811530_section9456131432010"><h4 class="sectiontitle">Precautions </h4><ul id="nosql_02_0052__en-us_topic_0249811530_ul10612183218515"><li id="nosql_02_0052__en-us_topic_0249811530_li8531887277">If the ECS and DB instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured.</li><li id="nosql_02_0052__en-us_topic_0249811530_li06121321516">If the ECS and DB instance are in different security groups, you need to configure security group rules for the ECS and DB instance separately.<ul id="nosql_02_0052__en-us_topic_0249811530_ul13612732951"><li id="nosql_02_0052__en-us_topic_0249811530_li4571145411248">To allow access to the <span id="nosql_02_0052__text1846332371213">GeminiDB Influx</span> instance, you need to configure an inbound rule for the security group where the instance resides.</li><li id="nosql_02_0052__en-us_topic_0249811530_li14612163220515">By default, the security group allows all outbound data packets, so you do not need to configure a security rule for the ECS. If not all access from the ECS is allowed, you need to configure an outbound rule for the ECS.</li></ul>
|
||||
</li></ul>
|
||||
<ul id="nosql_02_0052__en-us_topic_0249811530_ul11655735142317"><li id="nosql_02_0052__en-us_topic_0249811530_li18793238132312">By default, you can create up to 500 security group rules. However, too many rules increase network latency for initial access, so it is recommended that you add no more than 50 rules for each security group.</li><li id="nosql_02_0052__li95871802045">Currently, a GeminiDB Influx instance can be associated with only one security group.</li><li id="nosql_02_0052__li1060914101246"><a href="#nosql_02_0052__table78461843145">Table 1</a> lists security group rules.</li></ul>
|
||||
|
||||
<div class="tablenoborder"><a name="nosql_02_0052__table78461843145"></a><a name="table78461843145"></a><table cellpadding="4" cellspacing="0" summary="" id="nosql_02_0052__table78461843145" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Security group rules</caption><thead align="left"><tr id="nosql_02_0052__row16847343547"><th align="left" class="cellrowborder" valign="top" width="25.7%" id="mcps1.3.2.4.2.3.1.1"><p id="nosql_02_0052__p107834476110">Scenario</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="74.3%" id="mcps1.3.2.4.2.3.1.2"><p id="nosql_02_0052__p1878315471816">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="nosql_02_0052__row1847443744"><td class="cellrowborder" valign="top" width="25.7%" headers="mcps1.3.2.4.2.3.1.1 "><p id="nosql_02_0052__p147831747415">Connecting to an instance over a private network</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="74.3%" headers="mcps1.3.2.4.2.3.1.2 "><div class="p" id="nosql_02_0052__p24811801632">Configure security group rules as follows:<ul id="nosql_02_0052__ul748118013312"><li id="nosql_02_0052__li74811303311">If the ECS and GeminiDB Influx instance are in the same security group, they can communicate with each other by default. No security group rule needs to be configured.</li><li id="nosql_02_0052__li84811804316">If they are in different security groups, configure security group rules for them, separately.<ul id="nosql_02_0052__ul12481401737"><li id="nosql_02_0052__li1481906315">Configure inbound rules for the security group associated with the GeminiDB Influx instance. For details, see <a href="#nosql_02_0052__en-us_topic_0249811530_section9281154719202">Procedure</a>.</li><li id="nosql_02_0052__li04816017317">By default, the security group allows all outbound data packets, so you do not need to configure a security rule for the ECS. If not all access from the ECS is allowed, you need to configure an outbound rule for the ECS.</li></ul>
|
||||
</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0052__en-us_topic_0249811530_section9281154719202"><a name="nosql_02_0052__en-us_topic_0249811530_section9281154719202"></a><a name="en-us_topic_0249811530_section9281154719202"></a><h4 class="sectiontitle">Procedure</h4><ol id="nosql_02_0052__en-us_topic_0249811530_ol49383781586"><li id="nosql_02_0052__en-us_topic_0249811530_li93899141586"><span>Log in to the console.</span></li><li id="nosql_02_0052__en-us_topic_0249811530_li1870917810588"><span>Click <span><img id="nosql_02_0052__en-us_topic_0249811530_image145037112071" src="en-us_image_0000002417434596.png"></span> in the upper left corner and select a region and a project.</span></li><li id="nosql_02_0052__en-us_topic_0249811530_li297543615857"><span>Click <strong id="nosql_02_0052__b147681750126">Service List</strong>. Under <strong id="nosql_02_0052__b1769185011212">Networking</strong>, click <strong id="nosql_02_0052__b177013501428">Virtual Private Cloud</strong>.</span></li><li id="nosql_02_0052__en-us_topic_0249811530_li3171015115916"><span>In the navigation pane on the left, choose <span class="menucascade" id="nosql_02_0052__en-us_topic_0249811530_menucascade113137392162"><b><span class="uicontrol" id="nosql_02_0052__uicontrol931312398163">Access Control</span></b> > <b><span class="uicontrol" id="nosql_02_0052__uicontrol103131952161613">Security Groups</span></b></span>.</span></li><li id="nosql_02_0052__en-us_topic_0249811530_li140569415930"><span>On the <strong id="nosql_02_0052__en-us_topic_0249811530_b497332911519">Security Groups</strong> page, click the security group name.</span></li><li id="nosql_02_0052__en-us_topic_0249811530_li5489049115946"><span>On the <strong id="nosql_02_0052__en-us_topic_0249811530_b4976153713515">Inbound Rules</strong> tab, click <strong id="nosql_02_0052__en-us_topic_0249811530_b1697715371258">Add Rule</strong>. In the displayed <strong id="nosql_02_0052__en-us_topic_0249811530_b297743711512">Add Inbound Rule</strong> dialog box, set required parameters to add inbound rules. On the <strong id="nosql_02_0052__en-us_topic_0249811530_b271817563411">Outbound Rules</strong> tab, click <strong id="nosql_02_0052__en-us_topic_0249811530_b37191456543">Add Rule</strong>. In the displayed <strong id="nosql_02_0052__en-us_topic_0249811530_b37191156048">Add Outbound Rule</strong> dialog box, set required parameters to add outbound rules.</span></li><li id="nosql_02_0052__en-us_topic_0249811530_li21369327151121"><span>Click <strong id="nosql_02_0052__en-us_topic_0249811530_b191192582312">OK</strong>.</span></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="nosql_06_0015.html">Connecting to a GeminiDB Influx Instance Over Private Networks</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
61
docs/geminidb/umn/nosql_02_0053.html
Normal file
@ -0,0 +1,61 @@
|
||||
<a name="nosql_02_0053"></a><a name="nosql_02_0053"></a>
|
||||
|
||||
<h1 class="topictitle1">Connecting to a <span id="text15505124818153">GeminiDB Influx</span> Instance Over Private Networks</h1>
|
||||
<div id="body1575537965934"><div class="section" id="nosql_02_0053__section46429645141251"><h4 class="sectiontitle">Scenarios</h4><p id="nosql_02_0053__p1112805719352">This section uses the Linux operating system as an example to describe how to connect an <span id="nosql_02_0053__text849915338398">ECS</span><span id="nosql_02_0053__text55865377397"></span> to a <span id="nosql_02_0053__text102813393820">GeminiDB Influx</span> instance over private networks.</p>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0053__section135810251275"><h4 class="sectiontitle">Usage Notes</h4><ul id="nosql_02_0053__ul53814073144559"><li id="nosql_02_0053__li109347144559">The target instance and ECS must be in the same VPC and subnet.</li><li id="nosql_02_0053__li09011230251">The ECS must be in a security group that can access the target instance.<ul id="nosql_02_0053__ul53121930773"><li id="nosql_02_0053__li92211747371">If the target instance is associated with the default security group, you do not need to configure security group rules for the instance and <span id="nosql_02_0053__text118031121588">ECS</span>.</li><li id="nosql_02_0053__li14221947274">If the target instance is associated with a non-default security group, check whether the non-default security group rules allow the <span id="nosql_02_0053__text10241162294019">ECS</span><span id="nosql_02_0053__text467519254405"></span> to access the instance. For details, see section <a href="nosql_02_0052.html">Configuring Security Group Rules</a>.</li></ul>
|
||||
</li><li id="nosql_02_0053__li7354102612436">The default port of the <span id="nosql_02_0053__text886881112388">GeminiDB Influx</span> instance is 8635 and cannot be changed.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0053__section109203094413"><h4 class="sectiontitle">Prerequisites</h4>
|
||||
<div class="notice" id="nosql_02_0053__note9816173342312"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="nosql_02_0053__p88161933142312">The instance and ECS must be in the same VPC and subnet.</p>
|
||||
</div></div>
|
||||
<ul id="nosql_02_0053__ul6439114913236"><li id="nosql_02_0053__li2043915496232">Download the InfluxDB client from the <a href="https://dl.influxdata.com/influxdb/releases/influxdb-1.7.9-static_linux_amd64.tar.gz" target="_blank" rel="noopener noreferrer">official website</a>.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0053__section34671588472"><h4 class="sectiontitle">SSL Connection</h4><ol id="nosql_02_0053__ol19411151824918"><li id="nosql_02_0053__li10707753164715"><span>Log in to the <span id="nosql_02_0053__text1212914742410">ECS</span><span id="nosql_02_0053__text10129547142410"></span>. For details, see section "Creating <span id="nosql_02_0053__text121293471243">ECS</span><span id="nosql_02_0053__text9129104782413"></span>s" in the <em id="nosql_02_0053__i10129114782420">Elastic Cloud Server User Guide</em>. </span></li><li id="nosql_02_0053__li1225316984811"><span>Upload the InfluxDB client installation package to the <span id="nosql_02_0053__text9456181013482">ECS</span><span id="nosql_02_0053__text1645691014481"></span>.</span></li><li id="nosql_02_0053__li114111186497"><span>Decompress the client package.</span><p><pre class="screen" id="nosql_02_0053__screen15915134732713"><strong id="nosql_02_0053__b1625644084814">tar -xzf influxdb-1.7.9-static_linux_amd64.tar.gz</strong></pre>
|
||||
</p></li><li id="nosql_02_0053__li1829794317496"><span>Connect your instance to the InfluxDB client.</span><p><ol type="a" id="nosql_02_0053__ol9297743104916"><li id="nosql_02_0053__li10297194314916">Run the following command to go to the InfluxDB directory:<pre class="screen" id="nosql_02_0053__screen157981059105615"><strong id="nosql_02_0053__b481095925611">cd </strong><strong id="nosql_02_0053__b981011593566">influxdb-1.7.9</strong><strong id="nosql_02_0053__b281095915620">-1</strong></pre>
|
||||
</li><li id="nosql_02_0053__li529844318491">Run the following command to connect to the InfluxDB shell:<pre class="screen" id="nosql_02_0053__screen114541859572"><strong id="nosql_02_0053__b18455554579">./influx -ssl </strong><strong id="nosql_02_0053__b345545205714">-host </strong><strong id="nosql_02_0053__b1545516545715"><<em id="nosql_02_0053__i1545517513577">DB_HOST</em>></strong><strong id="nosql_02_0053__b204552595712"> -port </strong><strong id="nosql_02_0053__b134551359573"><<em id="nosql_02_0053__i194557513578">DB_PORT</em>></strong></pre>
|
||||
<p id="nosql_02_0053__p112981243184918">Example:</p>
|
||||
<pre class="screen" id="nosql_02_0053__screen479711145715"><strong id="nosql_02_0053__b19798131111573">./influx -ssl -host 192.168.1.201 -port 8635</strong></pre>
|
||||
</li><li id="nosql_02_0053__li22981743184916">Run the <strong id="nosql_02_0053__b2082414592248">auth</strong> command to authenticate the user.<p id="nosql_02_0053__p32982043184911"><strong id="nosql_02_0053__b10298164314495">auth</strong></p>
|
||||
<p id="nosql_02_0053__p1229864313494">Enter the username and password as prompted.</p>
|
||||
<p id="nosql_02_0053__p14298124304919"><strong id="nosql_02_0053__b6773112516812">username</strong>:<em id="nosql_02_0053__i577472517811"><DB_USER></em></p>
|
||||
<p id="nosql_02_0053__p15298343134910"><strong id="nosql_02_0053__b76743110816">password</strong>:<em id="nosql_02_0053__i116713311586"><DB_PWD></em></p>
|
||||
</li></ol>
|
||||
<div class="note" id="nosql_02_0053__note72981343174911"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="nosql_02_0053__ul11298114384911"><li id="nosql_02_0053__li202986436497"><em id="nosql_02_0053__i3117453204912"><DB_USER></em> indicates the administrator name. The default value is <strong id="nosql_02_0053__b5365123814168">rwuser</strong>.</li><li id="nosql_02_0053__li729864334918"><em id="nosql_02_0053__i91566446820"><DB_PWD></em> indicates the administrator password.</li><li id="nosql_02_0053__li1429844354911"><em id="nosql_02_0053__i32711048489"><DB_HOST></em> indicates the private IP address of the node to be connected. Obtain the value from the <span class="uicontrol" id="nosql_02_0053__uicontrol18271184813819"><b>Private IP Address</b></span> column in the node list on the <span class="uicontrol" id="nosql_02_0053__uicontrol927116481688"><b>Basic Information</b></span> page.<p id="nosql_02_0053__p2298164354916">If your instance has multiple nodes, select the private IP address of a node.</p>
|
||||
</li><li id="nosql_02_0053__li1229834334917"><em id="nosql_02_0053__i12863512145010"><DB_PORT></em> indicates the port. The default value is <strong id="nosql_02_0053__b1420213915184">8635</strong> and cannot be changed.</li></ul>
|
||||
</div></div>
|
||||
</p></li><li id="nosql_02_0053__li1633021714718"><span>After the authentication is successful, run the <strong id="nosql_02_0053__b1016882532120">show databases</strong> command.</span><p><p id="nosql_02_0053__p1330131794715">If the following information is displayed, the connection is successful.</p>
|
||||
<pre class="screen" id="nosql_02_0053__screen3330151712470">name: databases
|
||||
name
|
||||
----
|
||||
_internal</pre>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0053__section398995894218"><h4 class="sectiontitle">Non-SSL Connection</h4><ol id="nosql_02_0053__o12386b3d9147482881ddfdfd9a3f787c"><li id="nosql_02_0053__li15792125011462"><span>Log in to the <span id="nosql_02_0053__text1358214242472">ECS</span><span id="nosql_02_0053__text192696272471"></span>. For details, see section "Creating <span id="nosql_02_0053__text163612134486">ECS</span><span id="nosql_02_0053__text49960159481"></span>s" in the <em id="nosql_02_0053__i181651121152920">Elastic Cloud Server User Guide</em>. </span></li><li id="nosql_02_0053__li44786699134732"><span>Upload the InfluxDB client installation package to the <span id="nosql_02_0053__text10635113811529">ECS</span><span id="nosql_02_0053__text2063514389528"></span>.</span></li><li id="nosql_02_0053__li19981956102810"><span>Decompress the client package.</span><p><pre class="screen" id="nosql_02_0053__screen62831556144813"><strong id="nosql_02_0053__b1528411564483">tar -xzf influxdb-1.7.9-static_linux_amd64.tar.gz</strong></pre>
|
||||
</p></li><li id="nosql_02_0053__lf50bb4c0b07747cfac89f74cc2b28b4a"><span>Connect your instance to the InfluxDB client.</span><p><ol type="a" id="nosql_02_0053__ol1075176163616"><li id="nosql_02_0053__li37513611368">Run the following command to go to the InfluxDB directory:<p id="nosql_02_0053__p1569652293620"><a name="nosql_02_0053__li37513611368"></a><a name="li37513611368"></a><strong id="nosql_02_0053__b1964720144376">cd </strong><strong id="nosql_02_0053__b107755589361">influxdb-1.7.9</strong><strong id="nosql_02_0053__b96474141378">-1</strong></p>
|
||||
</li><li id="nosql_02_0053__li7690121443613">Run the following command to connect to the InfluxDB shell:<pre class="screen" id="nosql_02_0053__screen126081744125813"><strong id="nosql_02_0053__b961924418587">./influx </strong><strong id="nosql_02_0053__b1061954415817">-host </strong><strong id="nosql_02_0053__b15619744195812"><<em id="nosql_02_0053__i17619144165813">DB_HOST</em>></strong><strong id="nosql_02_0053__b1061994455818"> -port </strong><strong id="nosql_02_0053__b1861994413581"><<em id="nosql_02_0053__i126191344135810">DB_PORT</em>></strong></pre>
|
||||
<p id="nosql_02_0053__p117911241163715">Example:</p>
|
||||
<pre class="screen" id="nosql_02_0053__screen1730594855815"><strong id="nosql_02_0053__b20305248175816">./influx -host 192.168.1.201 -port 8635</strong></pre>
|
||||
</li><li id="nosql_02_0053__li1949923123619">Run the <strong id="nosql_02_0053__b137751310115613">auth</strong> command to authenticate the user.<p id="nosql_02_0053__p1151162418551"><strong id="nosql_02_0053__b36167241913">auth</strong></p>
|
||||
<p id="nosql_02_0053__p10346123693911">Enter the username and password as prompted.</p>
|
||||
<p id="nosql_02_0053__p1264125819558"><strong id="nosql_02_0053__b1761416579325">username</strong>:<em id="nosql_02_0053__i1573535910328"><DB_USER></em></p>
|
||||
<p id="nosql_02_0053__p19760111675616"><strong id="nosql_02_0053__b158620383312">password</strong>:<em id="nosql_02_0053__i166412593320"><DB_PWD></em></p>
|
||||
</li></ol>
|
||||
<div class="note" id="nosql_02_0053__note21381431122218"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="nosql_02_0053__ul18138931152220"><li id="nosql_02_0053__li20641594515"><em id="nosql_02_0053__i945122181"><DB_USER></em> indicates the administrator name. The default value is <strong id="nosql_02_0053__b1149132422">rwuser</strong>.</li><li id="nosql_02_0053__li17338113019173"><em id="nosql_02_0053__i15993856204913"><DB_PWD></em> indicates the administrator password.</li><li id="nosql_02_0053__li127671321206"><em id="nosql_02_0053__i580819015011"><DB_HOST></em> indicates the private IP address of the node to be connected. Obtain the value from the <span class="uicontrol" id="nosql_02_0053__uicontrol15255103614524"><b>Private IP Address</b></span> column in the node list on the <span class="uicontrol" id="nosql_02_0053__uicontrol5256183616525"><b>Basic Information</b></span> page.<p id="nosql_02_0053__p59437318124">If your instance has multiple nodes, select the private IP address of a node.</p>
|
||||
</li><li id="nosql_02_0053__li322017284014"><em id="nosql_02_0053__i1857715505810"><DB_PORT></em> indicates the port. The default value is <strong id="nosql_02_0053__b16577105205818">8635</strong> and cannot be changed.</li></ul>
|
||||
</div></div>
|
||||
</p></li><li id="nosql_02_0053__li2356085813016"><span>After the authentication is successful, run the <strong id="nosql_02_0053__b11210158165717">show databases</strong> command.</span><p><p id="nosql_02_0053__p147454117478"><strong id="nosql_02_0053__b581119107479">show database</strong><strong id="nosql_02_0053__b9741343914">s</strong></p>
|
||||
<p id="nosql_02_0053__p1033114215459">If the following information is displayed, the connection is successful.</p>
|
||||
<pre class="screen" id="nosql_02_0053__screen10317125994513">name: databases
|
||||
name
|
||||
----
|
||||
_internal</pre>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="nosql_06_0015.html">Connecting to a GeminiDB Influx Instance Over Private Networks</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -7,8 +7,8 @@
|
||||
<div class="section" id="nosql_02_0116__section213410193216"><h4 class="sectiontitle">Usage Notes</h4><ul id="nosql_02_0116__ul9190163311348"><li id="nosql_02_0116__li6190113314342">This feature is available only to new GeminiDB Cassandra instances.</li><li id="nosql_02_0116__li2190733193420">After the automated backup policy is enabled, the system performs an incremental backup based on the preset interval. The incremental backup data is stored in OBS.</li></ul>
|
||||
<ul id="nosql_02_0116__ul719053316349"><li id="nosql_02_0116__li1119023363417">Data can be restored to a specified time point only after the automated backup policy is enabled.</li><li id="nosql_02_0116__li51901033133416">During instance restoration, backups are downloaded from the OBS bucket to the data directory of the restored instance.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_02_0116__section189359417525"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_02_0116__ol10937748529"><li id="nosql_02_0116__li1374519431356"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li id="nosql_02_0116__li34566410153117"><span>On the <strong id="nosql_02_0116__b998616102573">Instances</strong> page, click the target <span id="nosql_02_0116__text698701025716">GeminiDB Cassandra</span> instance.</span></li><li id="nosql_02_0116__li187932301440"><span>In the navigation pane on the left, click <span class="uicontrol" id="nosql_02_0116__uicontrol2063522410211"><b>Backups & Restorations</b></span>.</span></li><li id="nosql_02_0116__li56577057154136"><span>On the <strong id="nosql_02_0116__b143237278214">Backups & Restorations</strong> page, click <span class="uicontrol" id="nosql_02_0116__uicontrol032510271228"><b>Restore to Point In Time</b></span>.</span><p><div class="fignone" id="nosql_02_0116__fig12895422195110"><span class="figcap"><b>Figure 1 </b>Restoring data to a specified point in time</span><br><span><img id="nosql_02_0116__image789542215515" src="en-us_image_0000002200454268.png"></span></div>
|
||||
</p></li><li id="nosql_02_0116__li292666312"><span>Select the restoration date and the time point to which the data is restored and then click <strong id="nosql_02_0116__b14545101495716">OK</strong>.</span><p><div class="fignone" id="nosql_02_0116__fig1097101985219"><span class="figcap"><b>Figure 2 </b>Restore to Point in Time</span><br><span><img id="nosql_02_0116__image10977191526" src="en-us_image_0000002200454892.png"></span></div>
|
||||
<div class="section" id="nosql_02_0116__section189359417525"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_02_0116__ol10937748529"><li id="nosql_02_0116__li1374519431356"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li id="nosql_02_0116__li34566410153117"><span>On the <strong id="nosql_02_0116__b998616102573">Instances</strong> page, click the target <span id="nosql_02_0116__text698701025716">GeminiDB Cassandra</span> instance.</span></li><li id="nosql_02_0116__li187932301440"><span>In the navigation pane on the left, click <span class="uicontrol" id="nosql_02_0116__uicontrol2063522410211"><b>Backups & Restorations</b></span>.</span></li><li id="nosql_02_0116__li56577057154136"><span>On the <strong id="nosql_02_0116__b143237278214">Backups & Restorations</strong> page, click <span class="uicontrol" id="nosql_02_0116__uicontrol032510271228"><b>Restore to Point In Time</b></span>.</span><p><div class="fignone" id="nosql_02_0116__fig12895422195110"><span class="figcap"><b>Figure 1 </b>Restoring data to a specified point in time</span><br><span><img id="nosql_02_0116__image789542215515" src="en-us_image_0000002451073537.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="nosql_02_0116__li292666312"><span>Select the restoration date and the time point to which the data is restored and then click <strong id="nosql_02_0116__b14545101495716">OK</strong>.</span><p><div class="fignone" id="nosql_02_0116__fig1097101985219"><span class="figcap"><b>Figure 2 </b>Restore to Point in Time</span><br><span><img id="nosql_02_0116__image10977191526" src="en-us_image_0000002417434680.png" title="Click to enlarge" class="imgResize"></span></div>
|
||||
</p></li><li id="nosql_02_0116__li1666195115133"><span>On the displayed <span class="menucascade" id="nosql_02_0116__menucascade12787134717271"><b><span class="uicontrol" id="nosql_02_0116__uicontrol1978711475271">Create New Instance</span></b></span> page, create a DB instance of the same specifications as the DB instance to be restored. The new DB instance is independent from the original one.</span><p><ul id="nosql_02_0116__ul47340213174014"><li id="nosql_02_0116__li3477171483016">You are recommended to deploy the restored DB instance in a different AZ to ensure that your applications will not be adversely affected by the failure in any single AZ.</li><li id="nosql_02_0116__li13824155912588">The compatible API, DB instance type, DB instance version, and CPU type are the same as those of the original and cannot be changed.</li><li id="nosql_02_0116__li114141250185718">Other settings are the same as those of the original instance by default and can be modified. For details, see <a href="nosql_06_0003.html">Creating a GeminiDB Cassandra Instance</a>.</li></ul>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
@ -19,3 +19,10 @@
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
||||
<script language="JavaScript">
|
||||
<!--
|
||||
image_size('.imgResize');
|
||||
var msg_imageMax = "view original image";
|
||||
var msg_imageClose = "close";
|
||||
//--></script>
|
||||
@ -24,6 +24,8 @@
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="nosql_03_0014.html">Managing Tags</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="nosql_03_0201.html">Recycle Bin</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
|
||||
@ -5,7 +5,7 @@
|
||||
</div>
|
||||
<div class="section" id="nosql_03_0005__section446061684012"><h4 class="sectiontitle">Precautions</h4><ul id="nosql_03_0005__ul7767199204315"><li id="nosql_03_0005__li41417833194215">If you delete a DB instance, all the data in it and all automated backups are automatically deleted as well and cannot be restored, so exercise caution when performing this operation.</li><li id="nosql_03_0005__li88270310244">If you delete an instance, all nodes in the instance are also deleted.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="nosql_03_0005__section18870192318343"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_03_0005__ol9213165010343"><li id="nosql_03_0005__li1374519431356"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li id="nosql_03_0005__l3af6a9cc8c404c93b5c915fc46a3aaac"><span>On the <strong id="nosql_03_0005__b12537122319278">Instances</strong> page, locate the instance you want to delete and choose <strong id="nosql_03_0005__b18538162392717">More</strong> > <strong id="nosql_03_0005__b155398238279">Delete</strong> in the <strong id="nosql_03_0005__b1254022312714">Operation</strong> column.</span></li><li id="nosql_03_0005__li1895112033916"><span>On the displayed page, click <span class="uicontrol" id="nosql_03_0005__uicontrol1345370416853"><b>Yes</b></span>.</span><p><p id="nosql_03_0005__p202594174414">Deleted DB instances are not displayed in the instance list.</p>
|
||||
<div class="section" id="nosql_03_0005__section18870192318343"><h4 class="sectiontitle">Procedure</h4><ol id="nosql_03_0005__ol9213165010343"><li id="nosql_03_0005__li1374519431356"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li id="nosql_03_0005__l3af6a9cc8c404c93b5c915fc46a3aaac"><span>On the <strong id="nosql_03_0005__b36481731205318">Instances</strong> page, locate the target instance and choose <strong id="nosql_03_0005__b20648731155319">More</strong> > <strong id="nosql_03_0005__b8648163114537">Delete</strong> in the <strong id="nosql_03_0005__b0648631125311">Operation</strong> column.</span></li><li id="nosql_03_0005__li1895112033916"><span>On the displayed page, click <span class="uicontrol" id="nosql_03_0005__uicontrol1345370416853"><b>Yes</b></span>.</span><p><p id="nosql_03_0005__p202594174414">Deleted DB instances are not displayed in the instance list.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@ -11,20 +11,20 @@
|
||||
</li><li class="msonormal" id="nosql_03_0007__li98537291401">After a DB instance is created, you can modify the automated backup policy as needed. You can change the time window after the DB instance is created. The system backs up data based on the automated backup policy you have set.</li><li id="nosql_03_0007__li26181725153018">If the automated backup policy is disabled, any automated backups in progress stop immediately.</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="nosql_03_0007__section20760141313178"><h4 class="sectiontitle">Modifying an Automated Backup Policy</h4><ol id="nosql_03_0007__ol2947132381714"><li id="nosql_03_0007__li1374519431356"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li class="msonormal" id="nosql_03_0007__li2094772391716"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol477024712299"><b>Instances</b></span> page, click the DB instance you wish to modify the policy for.</span></li><li class="msonormal" id="nosql_03_0007__li191115272176"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol174011451132914"><b>Backups & Restorations</b></span> page, click <span class="uicontrol" id="nosql_03_0007__uicontrol19403351102919"><b>Modify Backup Policy</b></span>. In the displayed dialog box, set the backup policy. Then, click <strong id="nosql_03_0007__b1157575012231">Yes</strong> to save the configuration.</span><p><p class="msonormal" id="nosql_03_0007__p127861032145811">For details about how to set a backup policy, see <a href="#nosql_03_0007__section7348925133816">Automated Backup Policy</a>.</p>
|
||||
</p></li><li id="nosql_03_0007__li1755121142419"><span>Check or manage the generated backups on the <strong id="nosql_03_0007__b583641433310">Backup Management</strong> page or on the <strong id="nosql_03_0007__b1657919235333">Backups & Restorations</strong> page.</span></li></ol>
|
||||
<div class="section" id="nosql_03_0007__section20760141313178"><h4 class="sectiontitle">Modifying an Automated Backup Policy</h4><ol id="nosql_03_0007__ol2947132381714"><li id="nosql_03_0007__li1374519431356"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li class="msonormal" id="nosql_03_0007__li2094772391716"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol31027897924348"><b>Instances</b></span> page, click the target instance. The <strong id="nosql_03_0007__b53736023124348">Basic Information page</strong> is displayed.</span></li><li class="msonormal" id="nosql_03_0007__li191115272176"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol174011451132914"><b>Backups & Restorations</b></span> page, click <span class="uicontrol" id="nosql_03_0007__uicontrol19403351102919"><b>Modify Backup Policy</b></span>. In the displayed dialog box, set the backup policy. Then, click <strong id="nosql_03_0007__b1157575012231">Yes</strong> to save the configuration.</span><p><p class="msonormal" id="nosql_03_0007__p127861032145811">For details about how to set a backup policy, see <a href="#nosql_03_0007__section7348925133816">Automated Backup Policy</a>.</p>
|
||||
</p></li><li id="nosql_03_0007__li1755121142419"><span>Check or manage the generated backups on the <strong id="nosql_03_0007__b19467183955617">Backups</strong> or <strong id="nosql_03_0007__b246733965611">Backups & Restorations</strong> page.</span></li></ol>
|
||||
</div>
|
||||
<div class="section" id="nosql_03_0007__section183408257484"><h4 class="sectiontitle">Disabling Automated Backup Policy</h4><ol id="nosql_03_0007__ol816443794818"><li id="nosql_03_0007__li15521418113"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li class="msonormal" id="nosql_03_0007__li7561139114819"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol108349465474"><b>Instances</b></span> page, click the DB instance you wish to modify the policy for.</span></li><li class="msonormal" id="nosql_03_0007__li9561539174819"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol125927323348"><b>Backups & Restorations</b></span> page, click <span class="uicontrol" id="nosql_03_0007__uicontrol9592183243414"><b>Modify Backup Policy</b></span>.</span></li><li class="msonormal" id="nosql_03_0007__li41124215919"><span>In the displayed dialog box, click <span><img id="nosql_03_0007__image1579591812514" src="en-us_image_0000001815204936.png"></span> to disable the backup policy and click <strong id="nosql_03_0007__b12482105356">Yes</strong>.</span><p><div class="p" id="nosql_03_0007__p9767171951815">When disabling the automated backup policy, you can decide whether to delete the automated backups by selecting <strong id="nosql_03_0007__b154463598487">Delete automated backups</strong>.<ul id="nosql_03_0007__ul11589220161813"><li id="nosql_03_0007__li1129575005411">If you select it, all backup files within the retention period will be deleted. No automated backups are displayed in the backup list until you enable the automated backup policy again.</li><li id="nosql_03_0007__li25901420131819">If you do not select it, all backup files within the retention period will be retained, but you can still manually delete them later if needed. For details, see section <a href="#nosql_03_0007__section106721241354">Deleting an Automated Backup</a>.</li></ul>
|
||||
<div class="section" id="nosql_03_0007__section183408257484"><h4 class="sectiontitle">Disabling Automated Backup Policy</h4><ol id="nosql_03_0007__ol816443794818"><li id="nosql_03_0007__li15521418113"><span><a href="nosql_login.html">Log in to the GeminiDB console.</a></span></li><li class="msonormal" id="nosql_03_0007__li7561139114819"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol211570328424348"><b>Instances</b></span> page, click the target instance. The <strong id="nosql_03_0007__b56807844624348">Basic Information page</strong> is displayed.</span></li><li class="msonormal" id="nosql_03_0007__li9561539174819"><span>On the <span class="uicontrol" id="nosql_03_0007__uicontrol125927323348"><b>Backups & Restorations</b></span> page, click <span class="uicontrol" id="nosql_03_0007__uicontrol9592183243414"><b>Modify Backup Policy</b></span>.</span></li><li class="msonormal" id="nosql_03_0007__li41124215919"><span>In the displayed dialog box, click <span><img id="nosql_03_0007__image1579591812514" src="en-us_image_0000002417434784.png"></span> to disable the backup policy and click <strong id="nosql_03_0007__b12482105356">Yes</strong>.</span><p><div class="p" id="nosql_03_0007__p9767171951815">When disabling the automated backup policy, you can decide whether to delete the automated backups by selecting <strong id="nosql_03_0007__b154463598487">Delete automated backups</strong>.<ul id="nosql_03_0007__ul11589220161813"><li id="nosql_03_0007__li1129575005411">If you select it, all backup files within the retention period will be deleted. No automated backups are displayed in the backup list until you enable the automated backup policy again.</li><li id="nosql_03_0007__li25901420131819">If you do not select it, all backup files within the retention period will be retained, but you can still manually delete them later if needed. For details, see section <a href="#nosql_03_0007__section106721241354">Deleting an Automated Backup</a>.</li></ul>
|
||||
</div>
|
||||
<p class="msonormal" id="nosql_03_0007__p14144201314514">If the automated backup policy is disabled, any automated backups in progress stop immediately.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="nosql_03_0007__section106721241354"><a name="nosql_03_0007__section106721241354"></a><a name="section106721241354"></a><h4 class="sectiontitle">Deleting an Automated Backup</h4><p id="nosql_03_0007__p7885171214114">If the automated backup policy is disabled, you can delete stored automated backups to free up storage space.</p>
|
||||
<p id="nosql_03_0007__p17461454161517">If the automated backup policy is enabled, the system will delete automated backups as they expire. You cannot delete them manually.</p>
|
||||
<p id="nosql_03_0007__p17461454161517">If the automated backup policy is enabled, the system will delete automated backups as they expire. You cannot delete them.</p>
|
||||
<div class="notice" id="nosql_03_0007__note74761119183414"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="nosql_03_0007__p43244209111154">The deletion operation is irreversible, so exercise caution when performing this operation.</p>
|
||||
</div></div>
|
||||
<ul id="nosql_03_0007__ul11682203227"><li id="nosql_03_0007__li1968152012224"><strong id="nosql_03_0007__b54221939205114">Method 1</strong><ol id="nosql_03_0007__ol174832111454"><li class="msonormal" id="nosql_03_0007__li2482121119518">On the <span class="uicontrol" id="nosql_03_0007__uicontrol11591843195711"><b>Instances</b></span> page, click the DB instance you wish to delete backups for.</li><li class="msonormal" id="nosql_03_0007__li9483511655">On the <span class="uicontrol" id="nosql_03_0007__uicontrol10587164818578"><b>Backups & Restorations</b></span> page, locate the backup you wish to delete and click <span class="uicontrol" id="nosql_03_0007__uicontrol135881548195713"><b>Delete</b></span>.</li><li id="nosql_03_0007__li20483181111519">In the <strong id="nosql_03_0007__b12781130135919">Delete Backup</strong> dialog box, confirm the backup information and click <strong id="nosql_03_0007__b131961445011">Yes</strong>.</li></ol>
|
||||
</li><li id="nosql_03_0007__li115512472814"><strong id="nosql_03_0007__b785154318518">Method 2</strong><ol id="nosql_03_0007__ol6697163119286"><li id="nosql_03_0007__li146978318282">On the <span class="uicontrol" id="nosql_03_0007__uicontrol18815194815013"><b>Backup Management</b></span> page, locate the target backup and click <span class="uicontrol" id="nosql_03_0007__uicontrol38161848404"><b>Delete</b></span>.</li><li id="nosql_03_0007__li5881659103218">In the <strong id="nosql_03_0007__b1037513581114">Delete Backup</strong> dialog box, confirm the backup information and click <strong id="nosql_03_0007__b2037785813120">Yes</strong>.</li></ol>
|
||||
<ul id="nosql_03_0007__ul11682203227"><li id="nosql_03_0007__li1968152012224"><strong id="nosql_03_0007__b54221939205114">Method 1</strong><ol id="nosql_03_0007__ol174832111454"><li class="msonormal" id="nosql_03_0007__li2482121119518">On the <span class="uicontrol" id="nosql_03_0007__uicontrol71257707524348"><b>Instances</b></span> page, click the target instance. The <strong id="nosql_03_0007__b113440277224348">Basic Information page</strong> is displayed.</li><li class="msonormal" id="nosql_03_0007__li9483511655">On the <span class="uicontrol" id="nosql_03_0007__uicontrol10587164818578"><b>Backups & Restorations</b></span> page, locate the backup you wish to delete and click <span class="uicontrol" id="nosql_03_0007__uicontrol135881548195713"><b>Delete</b></span>.</li><li id="nosql_03_0007__li20483181111519">In the <strong id="nosql_03_0007__b12781130135919">Delete Backup</strong> dialog box, confirm the backup information and click <strong id="nosql_03_0007__b131961445011">Yes</strong>.</li></ol>
|
||||
</li><li id="nosql_03_0007__li115512472814"><strong id="nosql_03_0007__b785154318518">Method 2</strong><ol id="nosql_03_0007__ol6697163119286"><li id="nosql_03_0007__li146978318282">On the <span class="uicontrol" id="nosql_03_0007__uicontrol911644316566"><b>Backups</b></span> page, locate the target backup and click <span class="uicontrol" id="nosql_03_0007__uicontrol131161943205618"><b>Delete</b></span>.</li><li id="nosql_03_0007__li5881659103218">In the <strong id="nosql_03_0007__b1037513581114">Delete Backup</strong> dialog box, confirm the backup information and click <strong id="nosql_03_0007__b2037785813120">Yes</strong>.</li></ol>
|
||||
</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
|
||||