forked from docs/doc-exports
Chen, Junjie
ea05d1a734
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-authored-by: Chen, Junjie <chenjunjie@huawei.com> Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
29 lines
4.8 KiB
HTML
29 lines
4.8 KiB
HTML
<a name="GlobalDRPolicy"></a><a name="GlobalDRPolicy"></a>
|
|
|
|
<h1 class="topictitle1">HA and DR Policies</h1>
|
|
<div id="body8662426"><p id="GlobalDRPolicy__en-us_topic_0161126124_p8060118">Whether you use DCS as the frontend cache or backend data store, DCS is always ready to ensure data reliability and service availability. The following figure shows the evolution of DCS DR architectures.</p>
|
|
<div class="fignone" id="GlobalDRPolicy__en-us_topic_0161126124_fig16302053154911"><span class="figcap"><b>Figure 1 </b>DCS DR architecture evolution</span><br><span><img id="GlobalDRPolicy__en-us_topic_0161126124_image153322437119" src="en-us_image_0266235346.png"></span></div>
|
|
<p id="GlobalDRPolicy__en-us_topic_0161126124_p196901189533">To meet the reliability requirements of your data and services, you can choose to deploy your DCS instance within a single AZ or across AZs.</p>
|
|
<div class="section" id="GlobalDRPolicy__en-us_topic_0161126124_section9873193151517"><h4 class="sectiontitle">Single-AZ HA</h4><p id="GlobalDRPolicy__en-us_topic_0161126124_p11449191363119">Single-AZ deployment means deploying an instance within a physical equipment room. DCS provides process/service HA, data persistence, and hot standby DR policies for different types of DCS instances.</p>
|
|
<p id="GlobalDRPolicy__en-us_topic_0161126124_p1795194162611"><strong id="GlobalDRPolicy__en-us_topic_0161126124_b67201447135919">Single-node DCS instance</strong>: When DCS detects a process fault, a new process is started to ensure service HA.</p>
|
|
<div class="fignone" id="GlobalDRPolicy__en-us_topic_0161126124_fig175040231000"><span class="figcap"><b>Figure 2 </b>HA for a single-node DCS instance deployed within an AZ</span><br><span><img class="vsd" id="GlobalDRPolicy__en-us_topic_0161126124_image164201427202219" src="en-us_image_0266235448.png"></span></div>
|
|
<p id="GlobalDRPolicy__en-us_topic_0161126124_p398014445284"><strong id="GlobalDRPolicy__en-us_topic_0161126124_b166451111105">Master/Standby DCS instance</strong>: Data is persisted to disk in the master node and incrementally synchronized and persisted to the standby node, achieving hot standby and data persistence.</p>
|
|
<div class="fignone" id="GlobalDRPolicy__en-us_topic_0161126124_fig9238184592511"><span class="figcap"><b>Figure 3 </b>HA for a master/standby DCS instance deployed within an AZ</span><br><span><img class="vsd" id="GlobalDRPolicy__en-us_topic_0161126124_image169901810234" src="en-us_image_0266235321.png"></span></div>
|
|
<p id="GlobalDRPolicy__en-us_topic_0161126124_p81313812814"><strong id="GlobalDRPolicy__en-us_topic_0161126124_b568512479108">Cluster DCS instance</strong>: Similar to a master/standby instance, data in each shard (instance process) of a cluster instance is synchronized between master and standby nodes and persisted on both nodes.</p>
|
|
<div class="fignone" id="GlobalDRPolicy__en-us_topic_0161126124_fig18044436405"><span class="figcap"><b>Figure 4 </b>HA for a cluster DCS instance deployed within an AZ</span><br><span><img class="vsd" id="GlobalDRPolicy__en-us_topic_0161126124_image03261413152416" src="en-us_image_0266235394.png"></span></div>
|
|
</div>
|
|
<div class="section" id="GlobalDRPolicy__en-us_topic_0161126124_section724471151511"><h4 class="sectiontitle">Cross-AZ DR</h4><p id="GlobalDRPolicy__en-us_topic_0161126124_p73698714013">The master and standby nodes of a master/standby or cluster DCS instance can be deployed across AZs (in different equipment rooms). Power supplies and networks of different AZs are physically isolated. When a fault occurs in the AZ where the master node is deployed, the standby node connects to the client and takes over data read and write operations.</p>
|
|
<div class="fignone" id="GlobalDRPolicy__en-us_topic_0161126124_fig2046754742112"><span class="figcap"><b>Figure 5 </b>Cross-AZ deployment of a master/standby DCS instance</span><br><span><img class="vsd" id="GlobalDRPolicy__en-us_topic_0161126124_image1079294613241" src="en-us_image_0266235441.png"></span></div>
|
|
<div class="note" id="GlobalDRPolicy__en-us_topic_0161126124_note41824212218"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="GlobalDRPolicy__en-us_topic_0161126124_p17181423225">This mechanism applies in a similar way to a cluster DCS instance. Each shard (process) is deployed across AZs.</p>
|
|
</div></div>
|
|
<p id="GlobalDRPolicy__en-us_topic_0161126124_p1333015655118">When creating a master/standby or cluster DCS instance, select a standby AZ that is different from the primary AZ.</p>
|
|
<p id="GlobalDRPolicy__p1110819147496">Backup, configuration modification, and password change functions cannot be used during the fault.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dcs-pd-0326001.html">Service Overview</a></div>
|
|
</div>
|
|
</div>
|
|
|