SDRS UMN initial version
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>
562
docs/sdrs/umn/ALL_META.TXT.json
Normal file
506
docs/sdrs/umn/CLASS.TXT.json
Normal file
3
docs/sdrs/umn/PARAMETERS.txt
Normal file
@ -0,0 +1,3 @@
|
||||
version=""
|
||||
language="en-us"
|
||||
type=""
|
BIN
docs/sdrs/umn/en-us_image_0184026531.png
Normal file
After Width: | Height: | Size: 3.4 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665263.png
Normal file
After Width: | Height: | Size: 25 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665264.png
Normal file
After Width: | Height: | Size: 25 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665266.png
Normal file
After Width: | Height: | Size: 21 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665274.png
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665280.png
Normal file
After Width: | Height: | Size: 51 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665281.png
Normal file
After Width: | Height: | Size: 23 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665304.png
Normal file
After Width: | Height: | Size: 418 B |
BIN
docs/sdrs/umn/en-us_image_0288665307.png
Normal file
After Width: | Height: | Size: 25 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665316.png
Normal file
After Width: | Height: | Size: 15 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665319.png
Normal file
After Width: | Height: | Size: 25 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665320.png
Normal file
After Width: | Height: | Size: 15 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665321.png
Normal file
After Width: | Height: | Size: 49 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665326.png
Normal file
After Width: | Height: | Size: 33 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665327.png
Normal file
After Width: | Height: | Size: 46 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665328.png
Normal file
After Width: | Height: | Size: 59 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665337.png
Normal file
After Width: | Height: | Size: 49 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665357.png
Normal file
After Width: | Height: | Size: 31 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665358.png
Normal file
After Width: | Height: | Size: 12 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665371.png
Normal file
After Width: | Height: | Size: 6.8 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665372.png
Normal file
After Width: | Height: | Size: 19 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665377.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665385.png
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665386.png
Normal file
After Width: | Height: | Size: 23 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665392.png
Normal file
After Width: | Height: | Size: 16 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665395.png
Normal file
After Width: | Height: | Size: 432 B |
BIN
docs/sdrs/umn/en-us_image_0288665398.png
Normal file
After Width: | Height: | Size: 17 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665399.png
Normal file
After Width: | Height: | Size: 31 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665400.png
Normal file
After Width: | Height: | Size: 18 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665401.png
Normal file
After Width: | Height: | Size: 49 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665404.jpg
Normal file
After Width: | Height: | Size: 744 B |
BIN
docs/sdrs/umn/en-us_image_0288665405.png
Normal file
After Width: | Height: | Size: 44 KiB |
22
docs/sdrs/umn/en-us_topic_0108180804.html
Normal file
@ -0,0 +1,22 @@
|
||||
<a name="en-us_topic_0108180804"></a><a name="en-us_topic_0108180804"></a>
|
||||
|
||||
<h1 class="topictitle1">Product Advantages</h1>
|
||||
<div id="body1524282728470"><p id="en-us_topic_0108180804__p8060118">SDRS has the following advantages:</p>
|
||||
<ul id="en-us_topic_0108180804__ul119111683435"><li id="en-us_topic_0108180804__li69110814318">Convenient service recovery<p id="en-us_topic_0108180804__p8704940204411"><a name="en-us_topic_0108180804__li69110814318"></a><a name="li69110814318"></a>SDRS provides a management console. You can configure and manage <span id="en-us_topic_0108180804__text164511550123112">server</span><span id="en-us_topic_0108180804__text1240115317318"></span> replication and perform a planned failover or failover.</p>
|
||||
</li><li id="en-us_topic_0108180804__li11151132074319"><span id="en-us_topic_0108180804__text617004514305">server</span><span id="en-us_topic_0108180804__text617120454305"></span> replication<p id="en-us_topic_0108180804__p3670124510456">You can establish a replication relationship between the production site and the DR site.</p>
|
||||
</li><li id="en-us_topic_0108180804__li677642916431">Replication on demand<p id="en-us_topic_0108180804__p10423135794515"><a name="en-us_topic_0108180804__li677642916431"></a><a name="li677642916431"></a>You can replicate <span id="en-us_topic_0108180804__text125048107329">server</span><span id="en-us_topic_0108180804__text20504101013210"></span>s in an AZ to another AZ as required, thereby reducing the costs and complexity of maintaining another data center.</p>
|
||||
</li><li id="en-us_topic_0108180804__li2709124016430">Zero impact on applications<p id="en-us_topic_0108180804__p76440964611"><a name="en-us_topic_0108180804__li2709124016430"></a><a name="li2709124016430"></a>Applications running on <span id="en-us_topic_0108180804__text831742511326">server</span><span id="en-us_topic_0108180804__text17317182573212"></span>s can be replicated, and the replication will not have any impact on the applications.</p>
|
||||
</li><li id="en-us_topic_0108180804__li0571850194317">RPO target<p id="en-us_topic_0108180804__p18438182017467"><a name="en-us_topic_0108180804__li0571850194317"></a><a name="li0571850194317"></a>SDRS provides continuous and synchronous replication for <span id="en-us_topic_0108180804__text882713111910">server</span><span id="en-us_topic_0108180804__text5827141111916"></span>s to ensure zero recovery point objective (RPO).</p>
|
||||
</li><li id="en-us_topic_0108180804__li139391599433">Crash consistency<p id="en-us_topic_0108180804__p3258193244610"><a name="en-us_topic_0108180804__li139391599433"></a><a name="li139391599433"></a>Storage-based, real-time data synchronization keeps crash consistency for your data across two AZs. Specifically, application data might not be consistent during a failover, but disk data is always consistent.</p>
|
||||
</li><li id="en-us_topic_0108180804__li105981091445">Seamless DR drills<p id="en-us_topic_0108180804__p1834825304615"><a name="en-us_topic_0108180804__li105981091445"></a><a name="li105981091445"></a>You can easily perform DR drills without affecting ongoing replication.</p>
|
||||
</li><li id="en-us_topic_0108180804__li1359161924410">Flexible failover<p id="en-us_topic_0108180804__p1922616517476"><a name="en-us_topic_0108180804__li1359161924410"></a><a name="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="en-us_topic_0108180804__li1644792917448">Efficient network switchover<p id="en-us_topic_0108180804__p486213804716"><a name="en-us_topic_0108180804__li1644792917448"></a><a name="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="en-us_topic_0108180804__li266510540435">Excellent performance for the price<p id="en-us_topic_0108180804__p7703101104410"><a name="en-us_topic_0108180804__li266510540435"></a><a name="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_pro_0000.html">Service Overview</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
71
docs/sdrs/umn/en-us_topic_0108180805.html
Normal file
@ -0,0 +1,71 @@
|
||||
<a name="en-us_topic_0108180805"></a><a name="en-us_topic_0108180805"></a>
|
||||
|
||||
<h1 class="topictitle1">Step 1: Create a Protection Group</h1>
|
||||
<div id="body1524282728471"><div class="section" id="en-us_topic_0108180805__section1266142102019"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0108180805__p72641256209">You can specify two AZs as the source and target AZs, and create a protection group. Then, you can create protected instances and replication pairs in this protection group.</p>
|
||||
<p id="en-us_topic_0108180805__p66322374264">Verify the servers at the production and DR sites before you create a protection group. In this version, only the VPC migration deployment model is supported. Specifically, the servers at the production and DR sites must be in different AZs but in the same VPC. </p>
|
||||
<div class="fignone" id="en-us_topic_0108180805__fig9364464217"><span class="figcap"><b>Figure 1 </b>Creating a protection group</span><br><span><img class="vsd" id="en-us_topic_0108180805__image2361446192112" src="en-us_image_0288665357.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0108180805__section684619122203"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_0108180805__ol593635663111"><li id="en-us_topic_0108180805__li673701651310"><span>Log in to the management console.</span></li><li id="en-us_topic_0108180805__li1555831184219"><span>Click <strong id="en-us_topic_0108180805__b1665574185211">Service List</strong> and choose <strong id="en-us_topic_0108180805__b1590754116342">Storage</strong> > <strong id="en-us_topic_0108180805__b149086418342">Storage Disaster Recovery Service</strong>.</span><p><p id="en-us_topic_0108180805__p45581331134216">The <strong id="en-us_topic_0108180805__b1275337543">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0108180805__li15810161703512"><span>Click <strong id="en-us_topic_0108180805__b119263597486">Create Protection Group</strong>.</span><p><p id="en-us_topic_0108180805__p109981757608">The <strong id="en-us_topic_0108180805__b842352706164031">Create Protection Group</strong> page is displayed.</p>
|
||||
<div class="fignone" id="en-us_topic_0108180805__fig1677474514378"><span class="figcap"><b>Figure 2 </b>Creating a protection group</span><br><span><img id="en-us_topic_0108180805__image2314141895414" src="en-us_image_0288665274.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0108180805__li74435623116"><span>Configure the basic information about the protection group listed in <a href="#en-us_topic_0108180805__table0120161710336">Table 1</a>. </span><p><div class="note" id="en-us_topic_0108180805__note218184593013"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0108180805__p81821945133016">All the parameters in the following table are mandatory.</p>
|
||||
</div></div>
|
||||
|
||||
<div class="tablenoborder"><a name="en-us_topic_0108180805__table0120161710336"></a><a name="table0120161710336"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0108180805__table0120161710336" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="en-us_topic_0108180805__row10120117163319"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.4.2.2.2.4.1.1"><p id="en-us_topic_0108180805__p1012041715334">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.4.2.2.2.4.1.2"><p id="en-us_topic_0108180805__p1312018173335">Description</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.4.2.2.2.4.1.3"><p id="en-us_topic_0108180805__p312061716330">Example Value</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="en-us_topic_0108180805__row4120201713314"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.1 "><p id="en-us_topic_0108180805__p112031713310">Region</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.2 "><p id="en-us_topic_0108180805__p1041215984713">A region is a geographic area where resources used by servers are located.</p>
|
||||
<p id="en-us_topic_0108180805__p34476578162953">If the region is incorrect, click the drop-down list for correction.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.3 "><p id="en-us_topic_0108180805__p129831635135611">eu-de</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0108180805__row101221617153317"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.1 "><p id="en-us_topic_0108180805__p99001313420">DR Direction</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.2 "><ul id="en-us_topic_0108180805__ul13691336183613"><li id="en-us_topic_0108180805__li19369336133619">Production site: Select the AZ of the production site server.</li><li id="en-us_topic_0108180805__li091620397362">DR site: Select the AZ of the DR site server.</li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.3 "><p id="en-us_topic_0108180805__p0229123912587">Production site: az-01</p>
|
||||
<p id="en-us_topic_0108180805__p11988134874711">DR site: az-02</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0108180805__row14577105111253"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.1 "><p id="en-us_topic_0108180805__p1057819516252">Deployment Model</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.2 "><p id="en-us_topic_0108180805__p147501443112510">Currently, only the VPC migration model is supported. All resources at the production and DR sites belong to the same VPC.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.3 "><p id="en-us_topic_0108180805__p25789514251">VPC migration</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0108180805__row41343352614"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.1 "><p id="en-us_topic_0108180805__p15134631261">VPC</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.2 "><p id="en-us_topic_0108180805__p1213413152610">Specifies the VPC where the protection group is located.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.3 "><p id="en-us_topic_0108180805__p61341316261">vpc-test</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0108180805__row7122131763316"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.1 "><p id="en-us_topic_0108180805__p69405172348">Protection Group Name</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.2 "><p id="en-us_topic_0108180805__p6161512716573">Enter the protection group name. It is used for group classification and search.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.4.2.2.2.4.1.3 "><p id="en-us_topic_0108180805__p2122161717335">protection_group_001</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</p></li><li id="en-us_topic_0108180805__li117757217194"><span>Click <strong id="en-us_topic_0108180805__b6922192512529">Create Now</strong>.</span></li><li id="en-us_topic_0108180805__li1120027192514"><span>Click <strong id="en-us_topic_0108180805__b842352706212441">Back to Protection Group List</strong> to return to the SDRS homepage and query the protection group status.</span><p><p id="en-us_topic_0108180805__p52001273251">If the protection group is displayed in the <strong id="en-us_topic_0108180805__b51734067191225">Storage Disaster Recovery Service</strong> page and its status is <strong id="en-us_topic_0108180805__b84235270614115">Available</strong> (<span><img id="en-us_topic_0108180805__image2894918165617" src="en-us_image_0288665395.png"></span>), the protection group has been created successfully.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_qs_0001.html">Configuring Cross-AZ DR</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
15
docs/sdrs/umn/en-us_topic_0108180816.html
Normal file
@ -0,0 +1,15 @@
|
||||
<a name="en-us_topic_0108180816"></a><a name="en-us_topic_0108180816"></a>
|
||||
|
||||
<h1 class="topictitle1">Configuration Process</h1>
|
||||
<div id="body1524282728471"><p id="en-us_topic_0108180816__p4377289117">SDRS provides cross-AZ <span id="en-us_topic_0108180816__text9832138192211">server</span>-level protection (RPO = 0) in case applications at a production site cannot restore in a short period of time caused by force majeure like fires or earthquakes or device faults like damaged software or hardware. Synchronous replication at the storage layer is used to provide cross-AZ DR protection, and thereby meeting the crash consistency of data. If the production site becomes faulty, you can rapidly restore the services at the DR site after simple configuration.</p>
|
||||
<p id="en-us_topic_0108180816__p18440183693214"><a href="#en-us_topic_0108180816__fig19593154813218">Figure 1</a> shows the cross-AZ DR configuration process.</p>
|
||||
<div class="note" id="en-us_topic_0108180816__note742412368321"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0108180816__p1125685211181">When you create a protected instance, the system creates a replication pair for the disks of the servers at the production and DR site by default. </p>
|
||||
</div></div>
|
||||
<div class="fignone" id="en-us_topic_0108180816__fig19593154813218"><a name="en-us_topic_0108180816__fig19593154813218"></a><a name="fig19593154813218"></a><span class="figcap"><b>Figure 1 </b>Cross-AZ DR configuration process</span><br><span><img id="en-us_topic_0108180816__image191646565527" src="en-us_image_0288665371.png"></span></div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_qs_0001.html">Configuring Cross-AZ DR</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
32
docs/sdrs/umn/en-us_topic_0108560208.html
Normal file
@ -0,0 +1,32 @@
|
||||
<a name="en-us_topic_0108560208"></a><a name="en-us_topic_0108560208"></a>
|
||||
|
||||
<h1 class="topictitle1">Performing a Failover</h1>
|
||||
<div id="body1524550430906"><div class="section" id="en-us_topic_0108560208__section15531549458"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0108560208__p17111657194519">When the servers and disks at the production site become faulty due to force majeure, you can perform a failover for them and enable the servers and disks at the DR site to ensure the service continuity.</p>
|
||||
<p id="en-us_topic_0108560208__p195711585494">Once you perform a failover, the DR site servers and disks become available immediately. You can power on the servers, or use Cloud Server Backup Service (CSBS) or Volume Backup Service (VBS) to restore the data to a specified data recovery point.</p>
|
||||
<p id="en-us_topic_0108560208__p17166356142710">SDRS will migrate NICs on the server during the failover. After the failover, the IP, EIP, and MAC addresses of the production site server will be migrated to the DR site server, so that the IP, EIP, and MAC addresses remain the same.</p>
|
||||
<div class="note" id="en-us_topic_0108560208__note1231513114615"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="en-us_topic_0108560208__ul198992214618"><li id="en-us_topic_0108560208__li189112219619">Once the failover is started, data synchronization stops.</li><li id="en-us_topic_0108560208__li18918229614">After the failover is complete, the status of the protection group changes to <strong id="en-us_topic_0108560208__b6809831205818">Failover complete</strong>. Then, you need to switch to the protected instance details page and start the DR site server.</li></ul>
|
||||
</div></div>
|
||||
<div class="fignone" id="en-us_topic_0108560208__fig45075558307"><span class="figcap"><b>Figure 1 </b>Performing a failover</span><br><span><img class="vsd" id="en-us_topic_0108560208__image050745583010" src="en-us_image_0288665280.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0108560208__section8684144414202"><h4 class="sectiontitle">Notes</h4><p id="en-us_topic_0108560208__p368336151313">For Linux servers with Cloud-Init installed, if you have changed <strong id="en-us_topic_0108560208__b13595155915421">hostname</strong> of the production site server before you perform a failover for the first time, this modification will not synchronize to the DR site server.</p>
|
||||
<p id="en-us_topic_0108560208__p1563245543711">To resolve this problem, see <a href="sdrs_06_0404.html">What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?</a></p>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0108560208__section142217284496"><h4 class="sectiontitle">Prerequisites</h4><ul id="en-us_topic_0108560208__ul55311758153314"><li id="en-us_topic_0108560208__li1560363610387">You have confirmed with customer service that the servers and disks at the production site are faulty, and the deployed services are unavailable.</li><li id="en-us_topic_0108560208__li201322342517">The protection group has replication pairs.</li><li id="en-us_topic_0108560208__li888614872415">Protection is enabled for the protection group, and the protection group is in the <strong id="en-us_topic_0108560208__b1078713312527">Protecting</strong>, <strong id="en-us_topic_0108560208__b27895315212">Planned failover failed</strong>, or <strong id="en-us_topic_0108560208__b13701311185311">Failover failed</strong> state.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0108560208__section1953224694910"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_0108560208__ol1740114773111"><li id="en-us_topic_0108560208__li109831058719"><span>Log in to the management console.</span></li><li id="en-us_topic_0108560208__li12972105114527"><span>Click <strong id="en-us_topic_0108560208__b20200135810529">Service List</strong> and choose <strong id="en-us_topic_0108560208__b320375810526">Storage</strong> > <strong id="en-us_topic_0108560208__b120385819521">Storage Disaster Recovery Service</strong>.</span><p><p id="en-us_topic_0108560208__en-us_topic_0108180805_p45581331134216">The <strong id="en-us_topic_0108560208__b1966192163111">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0108560208__li84211239334"><span>In the pane of the desired protection group, click <strong id="en-us_topic_0108560208__b842352706171955">Protected Instances</strong>. </span><p><p id="en-us_topic_0108560208__p9587154617541">The operation page for the protection group is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0108560208__li1473016461596"><span>In the upper right corner of the page, click <strong id="en-us_topic_0108560208__b84235270615953">More</strong> and choose <strong id="en-us_topic_0108560208__b84235270610232">Fail Over</strong> from the drop-down list. </span><p><p id="en-us_topic_0108560208__p11585173675814">The <strong id="en-us_topic_0108560208__b842352706202347">Fail Over</strong> dialog box is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0108560208__li812255515532"><span>Click <strong id="en-us_topic_0108560208__b32295632193623">Fail Over</strong>.</span><p><div class="p" id="en-us_topic_0108560208__p136783619258">During the failover, do not start or stop the servers in the protection group. Otherwise, the failover may fail.<div class="note" id="en-us_topic_0108560208__note1492495819240"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0108560208__p3924175810244">After you confirm the failover, production site servers will encounter blue screen of death (BSOD) or be forcibly stopped, and will not be able to start anymore.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0108560208__section52491320105910"><h4 class="sectiontitle">Related Operations</h4><ul id="en-us_topic_0108560208__ul58831332372"><li id="en-us_topic_0108560208__li88838343715">After the failover is complete, the status of the protection group changes to <strong id="en-us_topic_0108560208__b7437152611018">Failover complete</strong>. Then, you need to switch to the protected instance details page and start the DR site server.</li><li id="en-us_topic_0108560208__li288313317373">After the failover is complete, the protection group is in the <strong id="en-us_topic_0108560208__b6810115810416">Protection disabled</strong> state. You need to enable protection again to start data synchronization. For details, see <a href="sdrs_ug_pg_0006.html">Performing Reprotection</a>.</li><li id="en-us_topic_0108560208__li19139331519">After the failover is complete, the NIC and IP address information of the servers at the DR site (original production site) will not be displayed. For details, see <a href="sdrs_faq_0004.html">Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?</a></li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_ug_pg_0000.html">Managing Protection Groups</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
12
docs/sdrs/umn/en-us_topic_0109956554.html
Normal file
@ -0,0 +1,12 @@
|
||||
<a name="en-us_topic_0109956554"></a><a name="en-us_topic_0109956554"></a>
|
||||
|
||||
<h1 class="topictitle1">What Are the Differences Between DR and Backup?</h1>
|
||||
<div id="body1525403013793"><div class="p" id="en-us_topic_0109956554__p6438446161119">Differences between disaster recovery (DR) and backup are as follows:<ul id="en-us_topic_0109956554__ul42312057131111"><li id="en-us_topic_0109956554__li923175713119">DR is used to prevent impacts on the systems caused by natural disasters, such as fires and earthquakes. A production site and its DR site must be located with a certain secure distance. Backup is to prevent impacts on the systems caused by inappropriate manual operations, virus infection, and logic errors. It is used to restore the service system data. Usually, a system and its backup are deployed in the same data center.</li><li id="en-us_topic_0109956554__li1336725917121">A DR system protects data but more focuses on protecting service continuity. A data backup system only ensures that data generated at different time points can be restored. Generally, the system performs the full backup for the first time, which takes a long period of time. The subsequent backup is incremental and can be completed within a short period of time.</li><li id="en-us_topic_0109956554__li390311111316">The highest DR standard is to implement zero RPO. You can set a maximum of 24 automatic backup policies at different time points in one day to restore data to different backup points.</li><li id="en-us_topic_0109956554__li376419542137">If a disaster occurs, such as earthquakes or fires, a DR system takes only several minutes to perform a failover, but a backup system takes several hours or even dozens of hours to restore the data.</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_06_0400.html">FAQs</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
125
docs/sdrs/umn/en-us_topic_0110037558.html
Normal file
82
docs/sdrs/umn/en-us_topic_0110037559.html
Normal file
@ -0,0 +1,82 @@
|
||||
<a name="en-us_topic_0110037559"></a><a name="en-us_topic_0110037559"></a>
|
||||
|
||||
<h1 class="topictitle1">Creating a Replication Pair</h1>
|
||||
<div id="body1525426324198"><div class="section" id="en-us_topic_0110037559__section19872813193710"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0110037559__p424413310370">You can create replication pairs for desired disks and add the replication pairs to a specified protection group. When you create a replication pair:</p>
|
||||
<ul id="en-us_topic_0110037559__ul1088410704110"><li id="en-us_topic_0110037559__li1088407174112">If the protection group is in the <strong id="en-us_topic_0110037559__b1343665311410">Available</strong> state, protection is disabled. The production site disk and DR site disk have formed a replication pair, but data synchronization is not started. To start data synchronization, enable protection.</li><li id="en-us_topic_0110037559__li3884076416">If the protection group is in the <strong id="en-us_topic_0110037559__b1195182019614">Protecting</strong> state, protection is enabled. After you create a replication pair, data synchronization is automatically started.</li></ul>
|
||||
<div class="note" id="en-us_topic_0110037559__note1792122418373"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110037559__p5169134312313">After a replication pair is created, the default name of the DR site disk is the same as the name of the production site disk, but their IDs are different.</p>
|
||||
<p id="en-us_topic_0110037559__p13843132817373">To modify a disk name, click the disk name on the replication pair details page to switch to the disk details page and modify it.</p>
|
||||
</div></div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0110037559__section1528842413918"><h4 class="sectiontitle"><strong id="en-us_topic_0110037559__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="en-us_topic_0110037559__ul6574135153912"><li id="en-us_topic_0110037559__li7423133313265">The protection group is in the <strong id="en-us_topic_0110037559__b12171725205019">Available</strong> or <strong id="en-us_topic_0110037559__b2017212505015">Protecting</strong> state.</li><li id="en-us_topic_0110037559__li1537122114327">If <strong id="en-us_topic_0110037559__b75133257211">Server Type</strong> of the protection group is <strong id="en-us_topic_0110037559__b8168911132612">ECS</strong>, the disks used to create the replication pair are in the <strong id="en-us_topic_0110037559__b8423527061650">Available</strong> state.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0110037559__section1243511993716"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_0110037559__ol2989153814717"><li id="en-us_topic_0110037559__li109831058719"><span>Log in to the management console.</span></li><li id="en-us_topic_0110037559__li12972105114527"><span>Click <strong id="en-us_topic_0110037559__b0806105510534">Service List</strong> and choose <strong id="en-us_topic_0110037559__b1814135511535">Storage</strong> > <strong id="en-us_topic_0110037559__b8814125512536">Storage Disaster Recovery Service</strong>.</span><p><p id="en-us_topic_0110037559__en-us_topic_0108180805_p45581331134216">The <strong id="en-us_topic_0110037559__b15491162863611">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0110037559__li84211239334"><span>In the pane of the protection group for which replication pairs are to be added, click <strong id="en-us_topic_0110037559__b84235270611125">Replication Pairs</strong>.</span><p><p id="en-us_topic_0110037559__p18473824191114">The operation page for the protection group is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0110037559__li1063715212408"><span>On the <strong id="en-us_topic_0110037559__b842352706105036">Replication Pairs</strong> tab, click <strong id="en-us_topic_0110037559__b84235270695047">Create Replication Pair</strong>.</span><p><p id="en-us_topic_0110037559__p3676113041218">The <strong id="en-us_topic_0110037559__b84235270693643">Create Replication Pair</strong> page is displayed.</p>
|
||||
<div class="fignone" id="en-us_topic_0110037559__fig259912464915"><span class="figcap"><b>Figure 1 </b>Creating a replication pair</span><br><span><img id="en-us_topic_0110037559__image7334182173313" src="en-us_image_0288665399.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0110037559__li74435623116"><span>Configure the basic information about the replication pair listed in <a href="#en-us_topic_0110037559__table14113172215131">Table 1</a>.</span><p>
|
||||
<div class="tablenoborder"><a name="en-us_topic_0110037559__table14113172215131"></a><a name="table14113172215131"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0110037559__table14113172215131" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="en-us_topic_0110037559__row711682216134"><th align="left" class="cellrowborder" valign="top" width="25.22252225222522%" id="mcps1.3.3.2.5.2.1.2.4.1.1"><p id="en-us_topic_0110037559__p111164221133"><strong id="en-us_topic_0110037559__b842352706211121">Parameter</strong></p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="51.93519351935193%" id="mcps1.3.3.2.5.2.1.2.4.1.2"><p id="en-us_topic_0110037559__p5116172261316"><strong id="en-us_topic_0110037559__b84235270611218">Description</strong></p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="22.84228422842284%" id="mcps1.3.3.2.5.2.1.2.4.1.3"><p id="en-us_topic_0110037559__p1211612224133"><strong>Example Value</strong></p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="en-us_topic_0110037559__row16116152218134"><td class="cellrowborder" valign="top" width="25.22252225222522%" headers="mcps1.3.3.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0110037559__p1111622216136">Protection Group Name</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.93519351935193%" headers="mcps1.3.3.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0110037559__p12116112241316">Indicates the name of the protection group to which the replication pair to be created belongs. You do not need to configure it.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.84228422842284%" headers="mcps1.3.3.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0110037559__p11826105813010">Protection-Group-test</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0110037559__row13973165510190"><td class="cellrowborder" valign="top" width="25.22252225222522%" headers="mcps1.3.3.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0110037559__p29731755161918">Protection Group ID</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.93519351935193%" headers="mcps1.3.3.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0110037559__p9973155518194">Specifies the ID of a protection group.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.84228422842284%" headers="mcps1.3.3.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0110037559__p1997315541911">619c57e9-3927-48f8-ad14-3e293260b8a0</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0110037559__row2116722191312"><td class="cellrowborder" valign="top" width="25.22252225222522%" headers="mcps1.3.3.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0110037559__p121161122161311">DR Direction</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.93519351935193%" headers="mcps1.3.3.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0110037559__p121169227135">Indicates the replication direction of the protection group to which the replication pair to be created belongs. You do not need to configure it.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.84228422842284%" headers="mcps1.3.3.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0110037559__p11826358193017">eu-de-01 -> eu-de-02</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0110037559__row10720384287"><td class="cellrowborder" valign="top" width="25.22252225222522%" headers="mcps1.3.3.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0110037559__p1673163813283">Production Site</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.93519351935193%" headers="mcps1.3.3.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0110037559__p1773113862815">Specifies the AZ of the production site. </p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.84228422842284%" headers="mcps1.3.3.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0110037559__p101401053173316">eu-de-01</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0110037559__row0405151012192"><td class="cellrowborder" valign="top" width="25.22252225222522%" headers="mcps1.3.3.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0110037559__p7405810191910">Production Site Disk</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.93519351935193%" headers="mcps1.3.3.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0110037559__p692281643110">This parameter is mandatory.</p>
|
||||
<p id="en-us_topic_0110037559__p1292241693116">Select a disk.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.84228422842284%" headers="mcps1.3.3.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0110037559__p1928814226494">volume-01</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0110037559__row1498954271619"><td class="cellrowborder" valign="top" width="25.22252225222522%" headers="mcps1.3.3.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0110037559__p398964210165">Replication Pair Name</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="51.93519351935193%" headers="mcps1.3.3.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0110037559__p5904190816573">Indicates the replication pair name. This parameter is mandatory.</p>
|
||||
<p id="en-us_topic_0110037559__p6161512716573">Configure this parameter when you create a replication pair. Then, you can use this name to classify and search this replication pair.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.84228422842284%" headers="mcps1.3.3.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0110037559__p19989164261619">replication_001</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</p></li><li id="en-us_topic_0110037559__li117757217194"><span>Click <strong id="en-us_topic_0110037559__b20583112512311">Create Now</strong>.</span></li><li id="en-us_topic_0110037559__li11250997172443"><span>On the <strong id="en-us_topic_0110037559__b842352706212317">Confirm</strong> page, you can confirm the replication pair information.</span><p><ul id="en-us_topic_0110037559__ul38915531172443"><li id="en-us_topic_0110037559__li14695463172443">If you do not need to modify the information, click <strong id="en-us_topic_0110037559__b84235270613125">Submit</strong>.</li><li id="en-us_topic_0110037559__li65150306172443">If you need to modify the information, click <strong id="en-us_topic_0110037559__b842352706113037">Previous</strong>.</li></ul>
|
||||
</p></li><li id="en-us_topic_0110037559__li83691754143219"><span>Click <strong id="en-us_topic_0110037559__b842352706212441">Back to Protection Group Details Page</strong> and query the replication pairs of the protection group.</span><p><p id="en-us_topic_0110037559__p1037011543323">If the replication pair status changes to <strong id="en-us_topic_0110037559__b842352706143143">Available</strong> or <strong id="en-us_topic_0110037559__b5859633125015">Protecting</strong>, the replication pair has been created successfully.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_ug_pi_0000.html">Managing Protected Instances</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
23
docs/sdrs/umn/en-us_topic_0110046974.html
Normal file
@ -0,0 +1,23 @@
|
||||
<a name="en-us_topic_0110046974"></a><a name="en-us_topic_0110046974"></a>
|
||||
|
||||
<h1 class="topictitle1">Step 3: Enable Protection</h1>
|
||||
<div id="body1525429292582"><div class="section" id="en-us_topic_0110046974__section869114914345"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0110046974__p123195311348">If you want to enable protection for all resources in a specified protection group, you can perform steps provided in this section.</p>
|
||||
<p id="en-us_topic_0110046974__p1086712512497">When data is written to the disks of the production site server, SDRS synchronizes the data to the disks of the DR site server in real time. Both the production site and DR site can use Cloud Server Backup Service (CSBS) and Volume Backup Service (VBS) to back up the servers and disks.</p>
|
||||
<div class="fignone" id="en-us_topic_0110046974__fig865513519224"><span class="figcap"><b>Figure 1 </b>Enabling protection</span><br><span><img class="vsd" id="en-us_topic_0110046974__image365525116223" src="en-us_image_0288665401.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0110046974__section197240210353"><h4 class="sectiontitle"><strong id="en-us_topic_0110046974__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="en-us_topic_0110046974__ul86195138358"><li id="en-us_topic_0110046974__li186191513153514">The protection group has replication pairs.</li><li id="en-us_topic_0110046974__li934211712357">The protection group is in the <strong id="en-us_topic_0110046974__b917815195126">Available</strong> or <strong id="en-us_topic_0110046974__b1112310470137">Enabling protection failed</strong> state.</li><li id="en-us_topic_0110046974__li134831826131818">After you create a protected instance and enable protection on servers at the production site, modifications to the <strong id="en-us_topic_0110046974__b113091987183">Hostname</strong>, <strong id="en-us_topic_0110046974__b12309168161816">Name</strong>, <strong id="en-us_topic_0110046974__b33091821810">Security Group</strong>, <strong id="en-us_topic_0110046974__b10310687189">Agency</strong>, <strong id="en-us_topic_0110046974__b1131016817187">ECS Group</strong>, <strong id="en-us_topic_0110046974__b13111085185">Tags</strong>, and <strong id="en-us_topic_0110046974__b2311980181">Auto Recovery</strong> configurations of servers on the production site will not synchronize to the servers at the DR site. You can manually add the configuration items to the servers at the DR site on the management console.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0110046974__section1316212298357"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_0110046974__ol25521131154217"><li id="en-us_topic_0110046974__li519102768"><span>Log in to the management console.</span></li><li id="en-us_topic_0110046974__li12972105114527"><span>Click <strong id="en-us_topic_0110046974__b771935410511">Service List</strong> and choose <strong id="en-us_topic_0110046974__b87216544514">Storage</strong> > <strong id="en-us_topic_0110046974__b167219546519">Storage Disaster Recovery Service</strong>.</span><p><p id="en-us_topic_0110046974__en-us_topic_0108180805_p45581331134216">The <strong id="en-us_topic_0110046974__b11268543191817">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0110046974__li186841954153419"><span>In the pane of the desired protection group, click <strong id="en-us_topic_0110046974__b84235270611125">Enable Protection</strong>.</span><p><div class="fignone" id="en-us_topic_0110046974__fig131085174416"><span class="figcap"><b>Figure 2 </b>Enabling protection</span><br><span><img id="en-us_topic_0110046974__image131116524412" src="en-us_image_0288665358.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0110046974__li625242814369"><span>In the displayed dialog box, click <strong id="en-us_topic_0110046974__b199591055163414">Yes</strong>.</span><p><p id="en-us_topic_0110046974__p28918794018">Once protection is enabled, data synchronization starts.</p>
|
||||
<div class="note" id="en-us_topic_0110046974__note12862043201719"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110046974__p1686417435171">The synchronization time is in direct proportion to the disk capacity. Larger disk capacity requires longer synchronization time.</p>
|
||||
</div></div>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_qs_0001.html">Configuring Cross-AZ DR</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
25
docs/sdrs/umn/en-us_topic_0110273585.html
Normal file
@ -0,0 +1,25 @@
|
||||
<a name="en-us_topic_0110273585"></a><a name="en-us_topic_0110273585"></a>
|
||||
|
||||
<h1 class="topictitle1">Modifying Specifications of a Protected Instance</h1>
|
||||
<div id="body1525684597644"><div class="section" id="en-us_topic_0110273585__section1484312317349"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0110273585__p8537103712516">If the specifications of an existing protected instance cannot meet the service requirements, you can perform steps provided in this section to modify the server specifications, including the vCPU and memory. </p>
|
||||
<p id="en-us_topic_0110273585__p1185733173414">The following scenarios may involve:</p>
|
||||
<ul id="en-us_topic_0110273585__ul5933838175213"><li id="en-us_topic_0110273585__li593423845219">Modifying the specifications of both the production and DR site servers</li><li id="en-us_topic_0110273585__li993473810523">Modifying the specifications of the production site server only</li><li id="en-us_topic_0110273585__li139341238105213">Modifying the specifications of the DR site server only</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0110273585__section8218163017179"><h4 class="sectiontitle"><strong id="en-us_topic_0110273585__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="en-us_topic_0110273585__ul3545340201717"><li id="en-us_topic_0110273585__li444298443">The protection group is in the <strong id="en-us_topic_0110273585__b415154013152">Available</strong> or <strong id="en-us_topic_0110273585__b1324524331510">Protecting state</strong>.</li><li id="en-us_topic_0110273585__li854534021717">The protected instance is in the <strong id="en-us_topic_0110273585__b7478102131617">Available</strong>, <strong id="en-us_topic_0110273585__b12436519121612">Protecting</strong>, or <strong id="en-us_topic_0110273585__b81171016101610">Modifying specifications failed</strong>.</li><li id="en-us_topic_0110273585__li145455401170">Servers of which the specifications to be modified are stopped.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0110273585__section12404242193417"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_0110273585__ol390693720350"><li id="en-us_topic_0110273585__li109831058719"><span>Log in to the management console.</span></li><li id="en-us_topic_0110273585__li12972105114527"><span>Click <strong id="en-us_topic_0110273585__b673120411534">Service List</strong> and choose <strong id="en-us_topic_0110273585__b15741154145318">Storage</strong> > <strong id="en-us_topic_0110273585__b974124115310">Storage Disaster Recovery Service</strong>.</span><p><p id="en-us_topic_0110273585__en-us_topic_0108180805_p45581331134216">The <strong id="en-us_topic_0110273585__b1240313142359">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0110273585__li192915515350"><span>In the pane of the protection group for which the protected instance specifications are to be modified, click <strong id="en-us_topic_0110273585__b84235270611125">Protected Instances</strong>.</span><p><p id="en-us_topic_0110273585__p1629175183520">The operation page for the protection group is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0110273585__li2291251193519"><span>On the <strong id="en-us_topic_0110273585__b842352706114358">Protected Instances</strong> tab, locate the row containing the target protected instance, click <strong id="en-us_topic_0110273585__b842352706115336">More</strong> in the <strong id="en-us_topic_0110273585__b842352706115353">Operation</strong> column, and choose <strong id="en-us_topic_0110273585__b842352706142750">Modify Production Site Server Specifications</strong> or <strong id="en-us_topic_0110273585__b0256152694218">Modify DR Site Server Specifications</strong> from the drop-down list. </span><p><div class="fignone" id="en-us_topic_0110273585__fig18486161131816"><span class="figcap"><b>Figure 1 </b>Modifying specifications</span><br><span><img id="en-us_topic_0110273585__image1848615111184" src="en-us_image_0288665266.png"></span></div>
|
||||
</p></li><li id="en-us_topic_0110273585__li329105173516"><span>In the displayed dialog box, select new server type, vCPU, and memory specifications.</span></li><li id="en-us_topic_0110273585__li17974181115918"><span>(Optional) If you need to modify the specifications of both the production site server and DR site server, select <strong id="en-us_topic_0110273585__b1820913376455">Modify the specifications of both the production and DR site servers</strong>. After you select this item, the system will modify the specifications of both the production site server and DR site server to the same specifications.</span><p><div class="fignone" id="en-us_topic_0110273585__fig9965423103213"><span class="figcap"><b>Figure 2 </b>Modifying the specifications of both the production site server and DR site server</span><br><span><img id="en-us_topic_0110273585__image15965123113212" src="en-us_image_0288665326.png"></span></div>
|
||||
<div class="note" id="en-us_topic_0110273585__note11977155123317"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110273585__p139786553330">This item is deselected by default, indicating that the system modifies the specifications of only the production site server or DR site server.</p>
|
||||
</div></div>
|
||||
</p></li><li id="en-us_topic_0110273585__li2298519357"><span>Click <strong id="en-us_topic_0110273585__b84235270613125">OK</strong>.</span><p><p id="en-us_topic_0110273585__p16262125017114">To ensure proper server running, do not perform any operations to the servers during specification modifications. </p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_ug_pi_0000.html">Managing Protected Instances</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
117
docs/sdrs/umn/en-us_topic_0110981899.html
Normal file
59
docs/sdrs/umn/en-us_topic_0122528555.html
Normal file
@ -0,0 +1,59 @@
|
||||
<a name="en-us_topic_0122528555"></a><a name="en-us_topic_0122528555"></a>
|
||||
|
||||
<h1 class="topictitle1">Performing a DR Drill</h1>
|
||||
<div id="body1531999471001"><div class="section" id="en-us_topic_0122528555__section171315582320"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0122528555__p91618033318">DR drills can be used to simulate fault scenarios, develop emergency recovery solutions, and verify whether the solutions are applicable and effective. Existing services will not be affected during a DR drill. When a fault occurs, you can use the solutions to rapidly restore services, enhancing service continuity.</p>
|
||||
<p id="en-us_topic_0122528555__p598930122518">SDRS provides the DR drill function. You can perform DR drills in a drill VPC (different from the VPC of the DR site). This function allows you to use the disk snapshots of the DR site servers to create drill servers with the server specifications and disk types same as the DR site servers.</p>
|
||||
<div class="note" id="en-us_topic_0122528555__note20483133513441"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0122528555__p64557191303">After the DR drill server is created, the production site server and DR drill server will independently run at the same time (data will not be synchronized between these two servers).</p>
|
||||
</div></div>
|
||||
<p id="en-us_topic_0122528555__p97681816112810">To ensure that a failover can be properly performed if a disaster happens, you are recommended to perform DR drills regularly to verify that:</p>
|
||||
<ul id="en-us_topic_0122528555__ul88242642913"><li id="en-us_topic_0122528555__li128282615293">The production site data and DR site data are consistent at the moment when you create a DR drill.</li><li id="en-us_topic_0122528555__li1682626152920">The services at the DR site can run properly after a failover.<div class="fignone" id="en-us_topic_0122528555__fig135261922851"><span class="figcap"><b>Figure 1 </b>Performing a DR drill</span><br><span><img id="en-us_topic_0122528555__image34730501789" src="en-us_image_0288665327.png"></span></div>
|
||||
</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0122528555__section1613910364214"><h4 class="sectiontitle">Notes</h4><ul id="en-us_topic_0122528555__ul8606151212421"><li id="en-us_topic_0122528555__li1231711587815">When you use a created drill VPC to create a drill, the subnet ACL rule of the drill VPC will be different from that of the VPC of the protection group. You need to manually set them to be the same one if needed.</li><li id="en-us_topic_0122528555__li116071912114215">When you create a DR drill, if the VPC of the protection group has a customized routing table and subnets configured, the corresponding routing table will not be automatically created for the drill VPC. You need to manually create it if needed.</li><li id="en-us_topic_0122528555__li1322195311148">If the DR site server runs Windows and uses the key login mode, ensure that the key pair of the DR site server exists when you create a DR drill. Otherwise, the DR drill server may fail to create, resulting in the DR drill creation failure.<div class="note" id="en-us_topic_0122528555__note123512812439"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0122528555__p12236389432">If the key pair of the DR site server has been deleted, create a key pair with the same name.</p>
|
||||
</div></div>
|
||||
</li><li id="en-us_topic_0122528555__li09071551194019">When you create a DR drill, if the DR site server runs Linux and uses the key login mode, the key pair information will not be displayed on the details page of the DR drill server after the DR drill server is created. You can use the key pair of the DR site server to log in to the DR drill server.</li><li id="en-us_topic_0122528555__li1685105125012">After you create a DR drill, modifications to the <strong id="en-us_topic_0122528555__b178018296462">Hostname</strong>, <strong id="en-us_topic_0122528555__b67883295469">Name</strong>, <strong id="en-us_topic_0122528555__b15788102916469">Agency</strong>, <strong id="en-us_topic_0122528555__b1478822974617">ECS Group</strong>, <strong id="en-us_topic_0122528555__b37891329184610">Security Group</strong>, <strong id="en-us_topic_0122528555__b1778920295465">Tags</strong>, and <strong id="en-us_topic_0122528555__b2790129114618">Auto Recovery</strong> configurations of the DR site server before the drill will not synchronize to the DR drill server. You can log in to the management console and manually add the configuration items to the drill server.</li><li id="en-us_topic_0122528555__li18284122185317">If the synchronization progress of replication pairs in the protection group is not 100%, the created DR drill server may fail to start. You are advised to perform a DR drill after all replication pairs are synchronized.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0122528555__section67593181295"><h4 class="sectiontitle">Prerequisites</h4><ul id="en-us_topic_0122528555__ul19475131019563"><li id="en-us_topic_0122528555__li0301715105613">The protection group is in the <strong id="en-us_topic_0122528555__b16159403467">Available</strong>, <strong id="en-us_topic_0122528555__b202294044612">Protecting</strong>, <strong id="en-us_topic_0122528555__b1222154015463">Failover complete</strong>, <strong id="en-us_topic_0122528555__b19221840174618">Enabling protection failed</strong>, <strong id="en-us_topic_0122528555__b17239406467">Disabling protection failed</strong>, <strong id="en-us_topic_0122528555__b1223114074612">Planned failover failed</strong>, <strong id="en-us_topic_0122528555__b112314017461">Re-enabling protection failed</strong>, or <strong id="en-us_topic_0122528555__b4232407465">Failover failed</strong> state.</li><li id="en-us_topic_0122528555__li3185374356">Do not perform a DR drill before the first time data synchronization between the production site server and DR site server completes. Otherwise, the drill server may not start properly.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0122528555__section37751719193414"><h4 class="sectiontitle">Procedure</h4><ol id="en-us_topic_0122528555__ol2989153814717"><li id="en-us_topic_0122528555__li9223419142715"><span>Log in to the management console.</span></li><li id="en-us_topic_0122528555__li12972105114527"><span>Click <strong id="en-us_topic_0122528555__b208842046523">Service List</strong> and choose <strong id="en-us_topic_0122528555__b9893144125216">Storage</strong> > <strong id="en-us_topic_0122528555__b289484195214">Storage Disaster Recovery Service</strong>.</span><p><p id="en-us_topic_0122528555__en-us_topic_0108180805_p45581331134216">The <strong id="en-us_topic_0122528555__b17315111341">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0122528555__li84211239334"><span>In the pane of the protection group to which a DR drill is to be added, click <strong id="en-us_topic_0122528555__b1941420911470">DR Drills</strong>.</span><p><p id="en-us_topic_0122528555__p18473824191114">The operation page for the protection group is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0122528555__li15636173715436"><span>On the <strong id="en-us_topic_0122528555__b11815151324712">DR Drills</strong> tab, click <strong id="en-us_topic_0122528555__b1882315138476">Create DR Drill</strong>.</span><p><p id="en-us_topic_0122528555__p234174413430">The <strong id="en-us_topic_0122528555__b9858181544714">Create DR Drill</strong> dialog box is displayed.</p>
|
||||
</p></li><li id="en-us_topic_0122528555__li1280494716437"><span>Configure <strong id="en-us_topic_0122528555__b1291316254479">Name</strong> and <strong id="en-us_topic_0122528555__b19920132515471">Drill VPC</strong>.</span><p>
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0122528555__table17278611195315" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="en-us_topic_0122528555__row18279121110532"><th align="left" class="cellrowborder" valign="top" width="17.001700170017003%" id="mcps1.3.4.2.5.2.1.2.4.1.1"><p id="en-us_topic_0122528555__p1673616279539">Parameter</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="60.33603360336033%" id="mcps1.3.4.2.5.2.1.2.4.1.2"><p id="en-us_topic_0122528555__p6737152714535">Description</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="22.662266226622663%" id="mcps1.3.4.2.5.2.1.2.4.1.3"><p id="en-us_topic_0122528555__p197371427125317">Example Value</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="en-us_topic_0122528555__row1527915119539"><td class="cellrowborder" valign="top" width="17.001700170017003%" headers="mcps1.3.4.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0122528555__p57403279534">Name</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60.33603360336033%" headers="mcps1.3.4.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0122528555__p177411527185315">DR drill name</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.662266226622663%" headers="mcps1.3.4.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0122528555__p374242715310">DR drill servername</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="en-us_topic_0122528555__row1627921117530"><td class="cellrowborder" valign="top" width="17.001700170017003%" headers="mcps1.3.4.2.5.2.1.2.4.1.1 "><p id="en-us_topic_0122528555__p274392717539">Drill VPC</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60.33603360336033%" headers="mcps1.3.4.2.5.2.1.2.4.1.2 "><p id="en-us_topic_0122528555__p0743927135319">VPC that used for a DR drill. It cannot be the same as the VPC of the DR site server. The value can be <strong id="en-us_topic_0122528555__b18613125212470">Automatically create</strong> or <strong id="en-us_topic_0122528555__b1062011529477">Use existing</strong>.</p>
|
||||
<ul id="en-us_topic_0122528555__ul3372115552310"><li id="en-us_topic_0122528555__li737225515235"><strong id="en-us_topic_0122528555__b10397175415473">Automatically create</strong>: The system automatically creates a drill VPC and subnets for the protection group.</li><li id="en-us_topic_0122528555__li137255519235"><strong id="en-us_topic_0122528555__b162051556194716">Use existing</strong>: The system uses an existing VPC as the drill VPC. If you select to use an existing VPC, the subnet CIDR block of the drill VPC must be consistent with that of the production group VPC.</li></ul>
|
||||
<div class="note" id="en-us_topic_0122528555__note1476474313238"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="en-us_topic_0122528555__p7764843112313">The drill VPC cannot be the same as the VPC of the protection group.</p>
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.662266226622663%" headers="mcps1.3.4.2.5.2.1.2.4.1.3 "><p id="en-us_topic_0122528555__p4744172725315">vpc-f9f7</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</p></li><li id="en-us_topic_0122528555__li567975719477"><span>Click <strong id="en-us_topic_0122528555__en-us_topic_0170796126_b168421590392">OK</strong>.</span><p><p id="en-us_topic_0122528555__p153101214196">After a DR drill is created, you can log in to the DR drill server and check whether services are running properly.</p>
|
||||
</p></li></ol>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_qs_0000.html">Getting Started</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
17
docs/sdrs/umn/en-us_topic_0125068221.html
Normal file
@ -0,0 +1,17 @@
|
||||
<a name="en-us_topic_0125068221"></a><a name="en-us_topic_0125068221"></a>
|
||||
|
||||
<h1 class="topictitle1">What Is SDRS?</h1>
|
||||
<div id="body1533544920745"><div class="section" id="en-us_topic_0125068221__section12514216133"><h4 class="sectiontitle">Storage DR</h4><p id="en-us_topic_0125068221__p258816153176">Storage Disaster Recovery Service (SDRS) provides disaster recovery (DR) services for many cloud services, such as Elastic Cloud Server (ECS) and Elastic Volume Service (EVS). By leveraging techniques, such as storage replication, data redundancy, and cache acceleration, SDRS offers high data reliability and service continuity for users.</p>
|
||||
<p id="en-us_topic_0125068221__p8060118">SDRS protects your service applications by replicating the server data and configurations to a DR site. It allows service applications to start and run at the DR site in the event that the production site <span id="en-us_topic_0125068221__text121476611527">server</span><span id="en-us_topic_0125068221__text6771796520"></span> stops. This improves service availability and continuity.</p>
|
||||
<div class="fignone" id="en-us_topic_0125068221__fig116715192015"><span class="figcap"><b>Figure 1 </b>Storage DR</span><br><span><img class="vsd" id="en-us_topic_0125068221__image56761112010" src="en-us_image_0288665328.png"></span></div>
|
||||
</div>
|
||||
<div class="section" id="en-us_topic_0125068221__section485881831312"><h4 class="sectiontitle">DR and Backup</h4><div class="p" id="en-us_topic_0125068221__p6438446161119">Differences between DR and backup are as follows:<ul id="en-us_topic_0125068221__en-us_topic_0109956554_ul42312057131111"><li id="en-us_topic_0125068221__en-us_topic_0109956554_li923175713119">DR is used to prevent impacts on the systems caused by natural disasters, such as fires and earthquakes. A production site and its DR site must be located with a certain secure distance. Backup is to prevent impacts on the systems caused by inappropriate manual operations, virus infection, and logic errors. It is used to restore the service system data. Usually, a system and its backup are deployed in the same data center.</li><li id="en-us_topic_0125068221__en-us_topic_0109956554_li1336725917121">A DR system protects data but focuses more on protecting service continuity. A data backup system only ensures that data generated at different time points can be restored. Generally, the system performs the full backup for the first time, which takes a long period of time. The subsequent backup is incremental and can be completed within a short period of time.</li><li id="en-us_topic_0125068221__en-us_topic_0109956554_li390311111316">The highest DR standard is to implement zero RPO. You can set a maximum of 24 automatic backup policies at different time points in one day to restore data to different backup points.</li><li id="en-us_topic_0125068221__en-us_topic_0109956554_li376419542137">If a disaster occurs, such as earthquakes or fires, a DR system takes only several minutes to perform a failover, but a backup system takes several hours or even dozens of hours to restore the data.</li></ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_pro_0000.html">Service Overview</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
158
docs/sdrs/umn/en-us_topic_0288665269.html
Normal file
7
docs/sdrs/umn/en-us_topic_0288665370.html
Normal file
@ -0,0 +1,7 @@
|
||||
<a name="EN-US_TOPIC_0288665370"></a><a name="EN-US_TOPIC_0288665370"></a>
|
||||
|
||||
<h1 class="topictitle1">Glossary</h1>
|
||||
<div id="body1533698633686"><p id="EN-US_TOPIC_0288665370__en-us_topic_0047892914_p8060118">For details about the glossaries in this document, see <a href="https://docs.otc.t-systems.com/en-us/glossary/index.html" target="_blank" rel="noopener noreferrer">Glossary</a>.</p>
|
||||
</div>
|
||||
<div></div>
|
||||
|
1
docs/sdrs/umn/public_sys-resources/ExpandCollapse.js
Normal file
@ -0,0 +1 @@
|
||||
var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d<f.length;d++){var e=f[d];if(e.className.indexOf(expandClassName)!=-1||e.className.indexOf(collapseClassName)!=-1||e.className.indexOf(collapseTableClassName)!=-1){if(a=="collapse"){if(e.tagName.toLowerCase()=="table"){e.className=collapseTableClassName}else{e.className=collapseClassName}}else{e.className=expandClassName}}}}function ExpandForHref(f){if(null==f||"#"==f||"###"==f){return}var a=null;try{a=document.getElementById(f)}catch(d){}if(null==a||a.length==0){return}try{var b=a.parentNode;while(b!=null&&b.tagName!="body"){if(b.className==collapseClassName){b.className=expandClassName}b=b.parentNode}}catch(c){}}window.onload=function(){var b=document.getElementsByTagName("div");for(var c=0;c<b.length;c++){var j=b[c];if(j.className.indexOf(expandClassName)!=-1){j.className=collapseClassName}}var d=document.getElementsByTagName("a");try{for(var c=0;c<d.length;c++){var f=d[c];var h=f.getAttribute("href");if(h!=""&&h!=null){f.addEventListener("click",showHasConref,false)}}}catch(g){}};function showHasConref(b){var a=b.currentTarget.getAttribute("href");try{if(a!=null&&a!="#"&&a.lastIndexOf("#")>-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}};
|