forked from docs/doc-exports
gtema
28ee660433
Reviewed-by: Goncharov, Artem <artem.goncharov@t-systems.com> Co-authored-by: gtema <artem.goncharov@gmail.com> Co-committed-by: gtema <artem.goncharov@gmail.com>
24 lines
5.2 KiB
HTML
24 lines
5.2 KiB
HTML
<a name="sdrs_06_0430"></a><a name="sdrs_06_0430"></a>
|
|
|
|
<h1 class="topictitle1">What Are the Highlights of SDRS?</h1>
|
|
<div id="body1525403013793"><p id="sdrs_06_0430__p102497422915">SDRS provides the following features:</p>
|
|
<ul id="sdrs_06_0430__ul119111683435"><li id="sdrs_06_0430__en-us_topic_0108180804_li69110814318">Convenient service recovery<p id="sdrs_06_0430__en-us_topic_0108180804_p8704940204411"><a name="sdrs_06_0430__en-us_topic_0108180804_li69110814318"></a><a name="en-us_topic_0108180804_li69110814318"></a>SDRS provides a management console. You can configure and manage <span id="sdrs_06_0430__en-us_topic_0108180804_text164511550123112"><span id="sdrs_06_0430__text768415918279">server</span></span> replication and perform a planned failover or failover.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li11151132074319">Server replication<p id="sdrs_06_0430__en-us_topic_0108180804_p3670124510456"><a name="sdrs_06_0430__en-us_topic_0108180804_li11151132074319"></a><a name="en-us_topic_0108180804_li11151132074319"></a>You can establish a replication relationship between the production site and the DR site.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li677642916431">Replication on demand<p id="sdrs_06_0430__en-us_topic_0108180804_p10423135794515"><a name="sdrs_06_0430__en-us_topic_0108180804_li677642916431"></a><a name="en-us_topic_0108180804_li677642916431"></a>You can replicate <span id="sdrs_06_0430__text17772113287"><span id="sdrs_06_0430__text2077810285">server</span>s</span> in an AZ to another AZ, thereby reducing the costs and complexity of maintaining another data center.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li2709124016430">Zero impact on applications<p id="sdrs_06_0430__en-us_topic_0108180804_p76440964611"><a name="sdrs_06_0430__en-us_topic_0108180804_li2709124016430"></a><a name="en-us_topic_0108180804_li2709124016430"></a>Applications running on <span id="sdrs_06_0430__text91739672818"><span id="sdrs_06_0430__text171736622816">server</span>s</span> can be replicated, and the replication will not have any impact on the applications.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li0571850194317">High RTO and RPO standard<p id="sdrs_06_0430__en-us_topic_0108180804_p191011614125211"><a name="sdrs_06_0430__en-us_topic_0108180804_li0571850194317"></a><a name="en-us_topic_0108180804_li0571850194317"></a>For SDRS, recovery time objective (RTO) refers to the period from the time when users perform a planned failover or failover at the production site to the time when the <span id="sdrs_06_0430__text11616141014284"><span id="sdrs_06_0430__text2061615105281">server</span>s</span> at the DR site start to run. This period does not include the time spent on DNS configuration, security group configuration, or customer script execution, and is shorter than 30 minutes.</p>
|
|
<p id="sdrs_06_0430__en-us_topic_0108180804_p18438182017467">SDRS provides continuous and synchronous replication for <span id="sdrs_06_0430__text130154284"><span id="sdrs_06_0430__text183115152811">server</span>s</span> to ensure zero recovery point objective (RPO).</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li139391599433">Crash consistency<p id="sdrs_06_0430__en-us_topic_0108180804_p3258193244610"><a name="sdrs_06_0430__en-us_topic_0108180804_li139391599433"></a><a name="en-us_topic_0108180804_li139391599433"></a>Real-time data synchronization based on storage ensures that data synchronized across two AZs maintains crash consistency.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li105981091445">Seamless DR drills<p id="sdrs_06_0430__en-us_topic_0108180804_p1834825304615"><a name="sdrs_06_0430__en-us_topic_0108180804_li105981091445"></a><a name="en-us_topic_0108180804_li105981091445"></a>You can easily perform DR drills without affecting ongoing replication.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li1359161924410">Flexible failover<p id="sdrs_06_0430__en-us_topic_0108180804_p1922616517476"><a name="sdrs_06_0430__en-us_topic_0108180804_li1359161924410"></a><a name="en-us_topic_0108180804_li1359161924410"></a>You can perform a planned failover for an expected service interruption to prevent data loss, or perform a failover for unexpected failures to restore services quickly.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li1644792917448">Efficient network switchover<p id="sdrs_06_0430__en-us_topic_0108180804_p486213804716"><a name="sdrs_06_0430__en-us_topic_0108180804_li1644792917448"></a><a name="en-us_topic_0108180804_li1644792917448"></a>SDRS simplifies program resource management during failovers, including reserving IP addresses and MAC addresses, all of which facilitates efficient network switchovers.</p>
|
|
</li><li id="sdrs_06_0430__en-us_topic_0108180804_li266510540435">Cost effectiveness<p id="sdrs_06_0430__en-us_topic_0108180804_p7703101104410"><a name="sdrs_06_0430__en-us_topic_0108180804_li266510540435"></a><a name="en-us_topic_0108180804_li266510540435"></a>When services are running properly, servers at the DR site are stopped and thereby will not be billed. This greatly reduces the DR TCO.</p>
|
|
</li></ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_06_0400.html">FAQs</a></div>
|
|
</div>
|
|
</div>
|
|
|