forked from docs/doc-exports
wangdengke2
06c8ac5e62
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: wangdengke2 <wangdengke2@huawei.com> Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
33 lines
5.5 KiB
HTML
33 lines
5.5 KiB
HTML
<a name="EN-US_TOPIC_0000002124277413"></a><a name="EN-US_TOPIC_0000002124277413"></a>
|
|
|
|
<h1 class="topictitle1">Basic Concepts</h1>
|
|
<div id="body1603702783071"><div class="section" id="EN-US_TOPIC_0000002124277413__section1319213812395"><h4 class="sectiontitle">Instances</h4><p id="EN-US_TOPIC_0000002124277413__a7472f2a2bb3643c39f5de90e0bcd5aa2">The smallest management unit in <span id="EN-US_TOPIC_0000002124277413__text19653144416">GaussDB</span> is the instance. A DB instance is an isolated database environment hosted in the cloud. You can create and manage <span id="EN-US_TOPIC_0000002124277413__text916483544417">GaussDB</span> instances on the management console. For details about instance statuses, instance specifications, storage types, and versions, see <a href="opengauss_01_0005.html">DB Instance Description</a>.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section79302616515"><h4 class="sectiontitle">Instance Versions</h4><p id="EN-US_TOPIC_0000002124277413__p1342581115810">Currently, <span id="EN-US_TOPIC_0000002124277413__en-us_topic_0000002088677498_text795354316501">GaussDB</span> V2.0-8.102, V2.0-3.223, V2.0-3.222, and V2.0-3.208 are supported.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section4661194916550"><h4 class="sectiontitle">Instance Types</h4><p id="EN-US_TOPIC_0000002124277413__p27439525569"><span id="EN-US_TOPIC_0000002124277413__text027640185713">GaussDB</span> supports <span id="EN-US_TOPIC_0000002124277413__text11128913142311">distributed</span> instances. Distributed instances allow you to add nodes as needed to handle large volumes of concurrent requests. The <span id="EN-US_TOPIC_0000002124277413__text101720325235">primary/standby</span> instances are suitable for scenarios with small and stable volumes of data, where data reliability and service availability are important.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section13364710386"><h4 class="sectiontitle">Instance Specifications</h4><p id="EN-US_TOPIC_0000002124277413__p171420440918">The instance specifications determine the computation (vCPUs) and memory capacity (in GB) of an instance. For details, see <a href="opengauss_01_0007.html">Instance Specifications</a>.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section738313553114"><h4 class="sectiontitle">Coordinator Nodes</h4><p id="EN-US_TOPIC_0000002124277413__p7894725193219">Coordinator nodes (CNs) store database metadata, distribute and execute query tasks, and then return the query results from DNs to applications.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section17205823337"><h4 class="sectiontitle">Data Nodes</h4><p id="EN-US_TOPIC_0000002124277413__en-us_topic_0085413843_en-us_topic_0059777370_p289189549138">Data nodes (DNs) store and query table data.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section138061426174214"><h4 class="sectiontitle">Automated Backups</h4><p id="EN-US_TOPIC_0000002124277413__aeb1c5ddc847b4e558d9bad06b5ee3ba5">When you create an instance, <span class="keyword" id="EN-US_TOPIC_0000002124277413__keyword443352834210">automated backup</span> is enabled by default. After the instance is created, you can modify the backup policy. <span id="EN-US_TOPIC_0000002124277413__text7479657155816">GaussDB</span> will automatically create backups for instances based on your settings.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section10188162964311"><h4 class="sectiontitle">Manual Backups</h4><p id="EN-US_TOPIC_0000002124277413__p1343312336439">Manual backups are user-initiated full backups of instances. They are retained until you delete them manually.</p>
|
|
</div>
|
|
<div class="section" id="EN-US_TOPIC_0000002124277413__section877771314110"><h4 class="sectiontitle">Regions and AZs</h4><p id="EN-US_TOPIC_0000002124277413__p5482171915414">A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.</p>
|
|
<ul id="EN-US_TOPIC_0000002124277413__ul625657104212"><li id="EN-US_TOPIC_0000002124277413__en-us_topic_0185177741_en-us_topic_0184026189_li14657175334618">A region is a physical data center. Each region is isolated from the other regions, improving fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.</li><li id="EN-US_TOPIC_0000002124277413__en-us_topic_0185177741_en-us_topic_0184026189_li45875020473">An AZ is a physical location where resources use independent power supplies and networks. Within a region, there can be multiple AZs that are physically isolated from each other but interconnected through internal networks. This ensures the independence of each AZ while also providing low-cost and low-latency network connectivity.</li></ul>
|
|
|
|
<p id="EN-US_TOPIC_0000002124277413__p1329614613437"><a href="#EN-US_TOPIC_0000002124277413__fig2922183194716">Figure 1</a> shows the relationship between regions and AZs.</p>
|
|
<div class="fignone" id="EN-US_TOPIC_0000002124277413__fig2922183194716"><a name="EN-US_TOPIC_0000002124277413__fig2922183194716"></a><a name="fig2922183194716"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="EN-US_TOPIC_0000002124277413__en-us_topic_0185177741_en-us_topic_0184026189_image12748194211128" src="figure/en-us_image_0000002088518190.png" width="NaN" height="NaN"></span></div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="opengauss_01_0001.html">Service Overview</a></div>
|
|
</div>
|
|
</div>
|
|
|