forked from docs/doc-exports
Wang , Deng Ke
04da47cae2
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com> Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
31 lines
4.6 KiB
HTML
31 lines
4.6 KiB
HTML
<a name="opengauss_01_0003"></a><a name="opengauss_01_0003"></a>
|
|
|
|
<h1 class="topictitle1">Basic Concepts</h1>
|
|
<div id="body1603702783071"><div class="section" id="opengauss_01_0003__section1319213812395"><h4 class="sectiontitle">DB Instances</h4><p id="opengauss_01_0003__a7472f2a2bb3643c39f5de90e0bcd5aa2">DB instances are the smallest management units used by <span id="opengauss_01_0003__text19653144416">GaussDB(openGauss)</span>. Each is an isolated database environment on the cloud. You can create and manage DB instances on the management console. For details about DB instance types, specifications, engines, versions, and statuses, see <a href="opengauss_01_0005.html">DB Instance Description</a>.</p>
|
|
</div>
|
|
<div class="section" id="opengauss_01_0003__section79302616515"><h4 class="sectiontitle">Instance Versions</h4><p id="opengauss_01_0003__p1033662210234">Currently, only <span id="opengauss_01_0003__text639210358551">2020 Enterprise Edition</span> is supported.</p>
|
|
</div>
|
|
<div class="section" id="opengauss_01_0003__section4661194916550"><h4 class="sectiontitle">DB Instance Types</h4><p id="opengauss_01_0003__p27439525569"><span id="opengauss_01_0003__text52861926516">GaussDB(openGauss)</span> supports distributed DB instances. Distributed DB instances support capability expansion through shards to cope with highly concurrent access to massive volumes of data. Primary/standby DB instances are suitable for scenarios with small and stable volumes of data and that have high requirements on data reliability and service availability.</p>
|
|
</div>
|
|
<div class="section" id="opengauss_01_0003__section13364710386"><h4 class="sectiontitle">DB Instance Classes</h4><p id="opengauss_01_0003__p171420440918">DB instance classes consist of vCPUs and memory (GB). For details, see <a href="opengauss_01_0007.html">DB Instance Classes</a>.</p>
|
|
</div>
|
|
<div class="section" id="opengauss_01_0003__section138061426174214"><h4 class="sectiontitle">Automated Backups</h4><p id="opengauss_01_0003__aeb1c5ddc847b4e558d9bad06b5ee3ba5">When you create a DB instance, the automated backup function is enabled by default. After the DB instance is created, you can modify the backup policy. <span id="opengauss_01_0003__text19672538165916">GaussDB(openGauss)</span> will automatically create backups for DB instances based on your settings.</p>
|
|
</div>
|
|
<div class="section" id="opengauss_01_0003__section10188162964311"><h4 class="sectiontitle">Manual Backups</h4><p id="opengauss_01_0003__p1343312336439">Manual backups are user-initiated full backups of DB instances. They are retained until you delete them manually.</p>
|
|
</div>
|
|
<div class="section" id="opengauss_01_0003__section877771314110"><h4 class="sectiontitle">Regions and AZs</h4><p id="opengauss_01_0003__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="opengauss_01_0003__ul625657104212"><li id="opengauss_01_0003__ldf9ddb6eb4d1469bba87f7456f48b857">A region is a physical data center. Each region is completely independent, improving fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.</li><li id="opengauss_01_0003__l777eb31bb9e34616ae15eae943d9572e">An AZ is a physical location using independent power supplies and networks. Faults in an AZ do not affect other AZs. A region can contain multiple AZs, which are physically isolated but interconnected through internal networks. This ensures the independence of AZs and provides low-cost and low-latency network connections.</li></ul>
|
|
|
|
<p id="opengauss_01_0003__p1329614613437"><a href="#opengauss_01_0003__fig2922183194716">Figure 1</a> shows the relationship between regions and AZs.</p>
|
|
<div class="fignone" id="opengauss_01_0003__fig2922183194716"><a name="opengauss_01_0003__fig2922183194716"></a><a name="fig2922183194716"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="opengauss_01_0003__i3b5f03a48fab455fbe4a2861843da04d" src="en-us_image_0000001072470721.png"></span></div>
|
|
</div>
|
|
<div class="section" id="opengauss_01_0003__section3455131419443"><h4 class="sectiontitle">Projects</h4><p id="opengauss_01_0003__p1986541612440">Projects are used to group and isolate OpenStack resources (computing resources, storage resources, and network resources). A project can be a department or a project team. Multiple projects can be created for one account.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="opengauss_01_0001.html">Introduction</a></div>
|
|
</div>
|
|
</div>
|
|
|