forked from docs/doc-exports
SDRS UMN 11104 Version
Reviewed-by: Muller, Martin <martin.muller@t-systems.com> Co-authored-by: weihongmin1 <weihongmin1@huawei.com> Co-committed-by: weihongmin1 <weihongmin1@huawei.com>
This commit is contained in:
File diff suppressed because it is too large
Load Diff
@ -18,9 +18,9 @@
|
|||||||
"code":"2"
|
"code":"2"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"desc":"SDRS has the following advantages:Convenient service recoverySDRS provides a management console. You can configure and manage server replication and perform a planned fai",
|
"desc":"SDRS has the following advantages:Convenient service recoverySDRS provides a management console. You can configure and manage server replication and perform switchovers o",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"Product Advantages",
|
"title":"SDRS Advantages",
|
||||||
"uri":"en-us_topic_0108180804.html",
|
"uri":"en-us_topic_0108180804.html",
|
||||||
"doc_type":"usermanual",
|
"doc_type":"usermanual",
|
||||||
"p_code":"1",
|
"p_code":"1",
|
||||||
@ -74,7 +74,7 @@
|
|||||||
{
|
{
|
||||||
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
|
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"SDRS Basic Concepts",
|
"title":"SDRS Concepts",
|
||||||
"uri":"sdrs_pro_0013.html",
|
"uri":"sdrs_pro_0013.html",
|
||||||
"doc_type":"usermanual",
|
"doc_type":"usermanual",
|
||||||
"p_code":"8",
|
"p_code":"8",
|
||||||
@ -180,9 +180,9 @@
|
|||||||
"code":"20"
|
"code":"20"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"desc":"After you perform a planned failover, services at the production site are failed over to the DR site, and services at the DR site are failed over to the production site. ",
|
"desc":"After you perform a switchover, services at the production site are switched to the DR site, and services at the DR site are switched over to the production site. Table 1",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"Performing a Planned Failover",
|
"title":"Performing a Switchover",
|
||||||
"uri":"sdrs_ug_pg_0002.html",
|
"uri":"sdrs_ug_pg_0002.html",
|
||||||
"doc_type":"usermanual",
|
"doc_type":"usermanual",
|
||||||
"p_code":"19",
|
"p_code":"19",
|
||||||
@ -396,7 +396,7 @@
|
|||||||
"code":"44"
|
"code":"44"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"desc":"Disaster recovery (DR) is a broad concept. In a broad sense, disaster recovery is a systematic project that includes all contents related to service continuity. Regarding",
|
"desc":"Disaster recovery (DR) is a broad concept.In a broad sense, DR is a systematic project that includes all abilities related to business continuity. Regarding IT, DR provid",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"What Is DR?",
|
"title":"What Is DR?",
|
||||||
"uri":"sdrs_06_0410.html",
|
"uri":"sdrs_06_0410.html",
|
||||||
@ -405,7 +405,7 @@
|
|||||||
"code":"45"
|
"code":"45"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"desc":"SDRS provides the following features:Convenient service recoverySDRS provides a management console. You can configure and manage server replication and perform a planned ",
|
"desc":"SDRS provides the following features:Convenient service recoverySDRS provides a management console. You can configure and manage server replication and perform a switchov",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"What Are the Highlights of SDRS?",
|
"title":"What Are the Highlights of SDRS?",
|
||||||
"uri":"sdrs_06_0430.html",
|
"uri":"sdrs_06_0430.html",
|
||||||
@ -432,9 +432,9 @@
|
|||||||
"code":"48"
|
"code":"48"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"desc":"The production site server in a protection group runs the SUSE OS. After users enable protection and perform a planned failover for the protection group, the EIP of the s",
|
"desc":"The production site server in a protection group runs the SUSE OS. After users enable protection and perform a switchover for the protection group, the EIP of the server ",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"What Can I Do When the EIP Cannot Be Pinged After I Perform a Planned Failover for a Protection Group Containing a SUSE Server?",
|
"title":"What Can I Do When the EIP Cannot Be Pinged After I Perform a Switchover for a Protection Group Containing a SUSE Server?",
|
||||||
"uri":"sdrs_06_0402.html",
|
"uri":"sdrs_06_0402.html",
|
||||||
"doc_type":"usermanual",
|
"doc_type":"usermanual",
|
||||||
"p_code":"44",
|
"p_code":"44",
|
||||||
@ -450,16 +450,16 @@
|
|||||||
"code":"50"
|
"code":"50"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"desc":"Users have changed hostname of the production site server before they perform a planned failover or failover for the first time. After the planned failover or failover, u",
|
"desc":"Users have changed hostname of the production site server before they perform a switchover or failover for the first time. After the switchover or failover, users start t",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?",
|
"title":"What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Switchover or Failover?",
|
||||||
"uri":"sdrs_06_0404.html",
|
"uri":"sdrs_06_0404.html",
|
||||||
"doc_type":"usermanual",
|
"doc_type":"usermanual",
|
||||||
"p_code":"44",
|
"p_code":"44",
|
||||||
"code":"51"
|
"code":"51"
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"desc":"SDRS performs planned failovers or failovers for protection groups. After a planned failover or failover, the production site and DR site exchange. When the production si",
|
"desc":"SDRS performs switchovers or failovers for protection groups. After a switchover or failover, the production site and DR site exchange. When the production site is functi",
|
||||||
"product_code":"sdrs",
|
"product_code":"sdrs",
|
||||||
"title":"Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?",
|
"title":"Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?",
|
||||||
"uri":"sdrs_faq_0004.html",
|
"uri":"sdrs_faq_0004.html",
|
||||||
|
|||||||
BIN
docs/sdrs/umn/en-us_image_0000002148848834.png
Normal file
BIN
docs/sdrs/umn/en-us_image_0000002148848834.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 108 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 30 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665326.png
Normal file
BIN
docs/sdrs/umn/en-us_image_0288665326.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 31 KiB |
BIN
docs/sdrs/umn/en-us_image_0288665372.png
Normal file
BIN
docs/sdrs/umn/en-us_image_0288665372.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 19 KiB |
@ -1,17 +1,17 @@
|
|||||||
<a name="en-us_topic_0108180804"></a><a name="en-us_topic_0108180804"></a>
|
<a name="en-us_topic_0108180804"></a><a name="en-us_topic_0108180804"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Product Advantages</h1>
|
<h1 class="topictitle1">SDRS Advantages</h1>
|
||||||
<div id="body1524282728470"><p id="en-us_topic_0108180804__p8060118">SDRS has the following advantages:</p>
|
<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>
|
<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 switchovers or failovers.</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__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__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__li2709124016430">Zero impact on applications<p id="en-us_topic_0108180804__p76440964611"><a name="en-us_topic_0108180804__li2709124016430"></a><a name="li2709124016430"></a>You can replicate all applications on the <span id="en-us_topic_0108180804__text831742511326">server</span><span id="en-us_topic_0108180804__text17317182573212"></span>s. The replication has no 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__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__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__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 run disaster recovery 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__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 switchovers for expected interruptions with zero data loss, or failovers for unexpected failures to recover 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__li1644792917448">Efficient network switchover<p id="en-us_topic_0108180804__p486213804716"><a name="en-us_topic_0108180804__li1644792917448"></a><a name="li1644792917448"></a>Streamline resource management during switchovers or failovers, for example, to reserve IP addresses and MAC addresses.</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><li id="en-us_topic_0108180804__li266510540435">Cost-effective<p id="en-us_topic_0108180804__p7703101104410"><a name="en-us_topic_0108180804__li266510540435"></a><a name="li266510540435"></a>When production site services are running properly, servers at the DR site are stopped. This greatly reduces the disaster recovery TCO.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -3,9 +3,9 @@
|
|||||||
<h1 class="topictitle1">Step 1: Create a Protection Group</h1>
|
<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>
|
<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>
|
<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 class="fignone" id="en-us_topic_0108180805__fig679314635210"><span class="figcap"><b>Figure 1 </b>Creating a protection group</span><br><span><img id="en-us_topic_0108180805__image14794646135216" src="en-us_image_0000002148848834.png"></span></div>
|
||||||
</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>
|
<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__b1883558596">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>
|
</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>
|
<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>
|
</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>
|
||||||
|
|||||||
@ -9,9 +9,9 @@
|
|||||||
<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 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>
|
||||||
<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>
|
<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>
|
<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 Switchover or Failover?</a></p>
|
||||||
</div>
|
</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 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__b12605142617168">Protecting</strong>, <strong id="en-us_topic_0108560208__b460672631618">Switchover failed</strong>, or <strong id="en-us_topic_0108560208__b360652671614">Failover failed</strong> state.</li></ul>
|
||||||
</div>
|
</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>
|
<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__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>
|
||||||
@ -21,7 +21,7 @@
|
|||||||
</div>
|
</div>
|
||||||
</p></li></ol>
|
</p></li></ol>
|
||||||
</div>
|
</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 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__b0372113012375">Failover complete</strong>. Then, you need to switch to the protected instance details page and manually 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>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -1,7 +1,7 @@
|
|||||||
<a name="en-us_topic_0109956554"></a><a name="en-us_topic_0109956554"></a>
|
<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>
|
<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 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 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_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>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -3,7 +3,7 @@
|
|||||||
<h1 class="topictitle1">Step 2: Create a Protected Instance</h1>
|
<h1 class="topictitle1">Step 2: Create a Protected Instance</h1>
|
||||||
<div id="body1525426324197"><div class="section" id="en-us_topic_0110037558__section1078504973319"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0110037558__p3642940172714">You can create protected instances using the servers that you want to perform DR protection. If the current production site encounters an unexpected large-scale server failure, you can call the related protection group API to perform a failover, ensuring that services running on protected instances are not affected.</p>
|
<div id="body1525426324197"><div class="section" id="en-us_topic_0110037558__section1078504973319"><h4 class="sectiontitle">Scenarios</h4><p id="en-us_topic_0110037558__p3642940172714">You can create protected instances using the servers that you want to perform DR protection. If the current production site encounters an unexpected large-scale server failure, you can call the related protection group API to perform a failover, ensuring that services running on protected instances are not affected.</p>
|
||||||
<p id="en-us_topic_0110037558__p838617534298">Select a protection group for each <span id="en-us_topic_0110037558__text1056900173120">server</span><span id="en-us_topic_0110037558__text185691083112"></span> to be replicated and create a protected instance using the <span id="en-us_topic_0110037558__text1080903015205">server</span><span id="en-us_topic_0110037558__text168101830162014"></span>. When you create a protected instance, the server and disk will be created at the DR site for the production site server and disk. The server specifications can be configured as required. Specifically, the specifications of the DR site server can be different from those of the production site server. The disks of the production site and DR site are of the same specifications and can automatically form a replication pair.</p>
|
<p id="en-us_topic_0110037558__p838617534298">Select a protection group for each <span id="en-us_topic_0110037558__text1056900173120">server</span><span id="en-us_topic_0110037558__text185691083112"></span> to be replicated and create a protected instance using the <span id="en-us_topic_0110037558__text1080903015205">server</span><span id="en-us_topic_0110037558__text168101830162014"></span>. When you create a protected instance, the server and disk will be created at the DR site for the production site server and disk. The server specifications can be configured as required. Specifically, the specifications of the DR site server can be different from those of the production site server. The disks of the production site and DR site are of the same specifications and can automatically form a replication pair.</p>
|
||||||
<p id="en-us_topic_0110037558__p1558164404814">The <span id="en-us_topic_0110037558__text499813520110">server</span><span id="en-us_topic_0110037558__text1599825615"></span> at the DR site is in the Stopped state after the protected instance created. These automatically created resources, including the DR site servers and disks, cannot be used before a planned failover or failover.</p>
|
<p id="en-us_topic_0110037558__p1558164404814">The <span id="en-us_topic_0110037558__text499813520110">server</span><span id="en-us_topic_0110037558__text1599825615"></span> at the DR site is in the Stopped state after the protected instance created. These automatically created resources, including the DR site servers and disks, cannot be used before a switchover or failover.</p>
|
||||||
<div class="fignone" id="en-us_topic_0110037558__fig1679017015306"><span class="figcap"><b>Figure 1 </b>Creating a protected instance</span><br><span><img class="vsd" id="en-us_topic_0110037558__image1779018010301" src="en-us_image_0288665321.png"></span></div>
|
<div class="fignone" id="en-us_topic_0110037558__fig1679017015306"><span class="figcap"><b>Figure 1 </b>Creating a protected instance</span><br><span><img class="vsd" id="en-us_topic_0110037558__image1779018010301" src="en-us_image_0288665321.png"></span></div>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="en-us_topic_0110037558__section112247299141"><h4 class="sectiontitle">Notes</h4><ul id="en-us_topic_0110037558__ul4638637134918"><li id="en-us_topic_0110037558__li141103214814">If a production site server has been added to an ECS group, you are not allowed to specify a DeH to create the DR site server for the production site server.</li><li id="en-us_topic_0110037558__li1183882919">When a protected instance is created, the default name of the server at the DR site is the same as that of the server at the production site, but their IDs are different.</li><li id="en-us_topic_0110037558__li0120381299">To modify a server name, switch to the protected instance details page and click the server name to switch to the server details page.</li><li id="en-us_topic_0110037558__li463833711492">After you create a protected instance and enable protection for the protection group, modifications to the <strong id="en-us_topic_0110037558__b9355111317465">Hostname</strong>, <strong id="en-us_topic_0110037558__b9542164015208">Name</strong>, <strong id="en-us_topic_0110037558__b61062571578">Agency</strong>, <strong id="en-us_topic_0110037558__b410711571574">ECS Group</strong>, <strong id="en-us_topic_0110037558__b101070578571">Security Group</strong>, <strong id="en-us_topic_0110037558__b1210855715717">Tags</strong>, and <strong id="en-us_topic_0110037558__b201081457165717">Auto Recovery</strong> configurations of the production site server will not synchronize to the DR site server. You can log in to the management console and manually add the configuration items to the servers at the DR site.</li><li id="en-us_topic_0110037558__li9322853151410">If protection is enabled for servers created during capacity expansion of an Auto Scaling (AS) group, these servers cannot be deleted when the capacity of the AS group is reduced.</li><li id="en-us_topic_0110037558__li1322195311148">If the server at the production site runs Windows and you choose the key login mode, ensure that the key pair of the server exists when you create a protected instance. Otherwise, the server at the DR site may fail to create, causing the protected instance creation failure.<div class="note" id="en-us_topic_0110037558__note123512812439"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110037558__p12236389432">If the key pair of the server at the production site has been deleted, create a key pair with the same name.</p>
|
<div class="section" id="en-us_topic_0110037558__section112247299141"><h4 class="sectiontitle">Notes</h4><ul id="en-us_topic_0110037558__ul4638637134918"><li id="en-us_topic_0110037558__li141103214814">If a production site server has been added to an ECS group, you are not allowed to specify a DeH to create the DR site server for the production site server.</li><li id="en-us_topic_0110037558__li1183882919">When a protected instance is created, the default name of the server at the DR site is the same as that of the server at the production site, but their IDs are different.</li><li id="en-us_topic_0110037558__li0120381299">To modify a server name, switch to the protected instance details page and click the server name to switch to the server details page.</li><li id="en-us_topic_0110037558__li463833711492">After you create a protected instance and enable protection for the protection group, modifications to the <strong id="en-us_topic_0110037558__b9355111317465">Hostname</strong>, <strong id="en-us_topic_0110037558__b9542164015208">Name</strong>, <strong id="en-us_topic_0110037558__b61062571578">Agency</strong>, <strong id="en-us_topic_0110037558__b410711571574">ECS Group</strong>, <strong id="en-us_topic_0110037558__b101070578571">Security Group</strong>, <strong id="en-us_topic_0110037558__b1210855715717">Tags</strong>, and <strong id="en-us_topic_0110037558__b201081457165717">Auto Recovery</strong> configurations of the production site server will not synchronize to the DR site server. You can log in to the management console and manually add the configuration items to the servers at the DR site.</li><li id="en-us_topic_0110037558__li9322853151410">If protection is enabled for servers created during capacity expansion of an Auto Scaling (AS) group, these servers cannot be deleted when the capacity of the AS group is reduced.</li><li id="en-us_topic_0110037558__li1322195311148">If the server at the production site runs Windows and you choose the key login mode, ensure that the key pair of the server exists when you create a protected instance. Otherwise, the server at the DR site may fail to create, causing the protected instance creation failure.<div class="note" id="en-us_topic_0110037558__note123512812439"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110037558__p12236389432">If the key pair of the server at the production site has been deleted, create a key pair with the same name.</p>
|
||||||
|
|||||||
@ -14,11 +14,11 @@
|
|||||||
</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>
|
</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>
|
<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>
|
</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>
|
<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">Parameter</p>
|
||||||
</th>
|
</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 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">Description</p>
|
||||||
</th>
|
</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 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">Example Value</p>
|
||||||
</th>
|
</th>
|
||||||
</tr>
|
</tr>
|
||||||
</thead>
|
</thead>
|
||||||
|
|||||||
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
<h1 class="topictitle1">Step 3: Enable Protection</h1>
|
<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>
|
<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>
|
<p id="en-us_topic_0110046974__p137091719513">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 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>
|
||||||
<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 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>
|
||||||
|
|||||||
@ -1,43 +1,16 @@
|
|||||||
|
<a name="en-us_topic_0110273585"></a><a name="en-us_topic_0110273585"></a>
|
||||||
<!DOCTYPE html
|
|
||||||
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
|
||||||
<html lang="en-us" xml:lang="en-us">
|
|
||||||
<head>
|
|
||||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
||||||
|
|
||||||
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
|
||||||
<meta name="DC.Type" content="topic">
|
|
||||||
<meta name="DC.Title" content="Modifying Specifications of a Protected Instance">
|
|
||||||
<meta name="product" content="">
|
|
||||||
<meta name="DC.Relation" scheme="URI" content="sdrs_ug_pi_0000.html">
|
|
||||||
<meta name="prodname" content="">
|
|
||||||
<meta name="version" content="">
|
|
||||||
<meta name="brand" content="Storage Disaster Recovery Service">
|
|
||||||
<meta name="DC.Publisher" content="20241026">
|
|
||||||
<meta name="prodname" content="sdrs">
|
|
||||||
<meta name="documenttype" content="usermanual">
|
|
||||||
<meta name="IsMulti" content="Yes">
|
|
||||||
<meta name="IsBot" content="Yes">
|
|
||||||
<meta name="opensource" content="true">
|
|
||||||
<meta name="DC.Format" content="XHTML">
|
|
||||||
<meta name="DC.Identifier" content="en-us_topic_0110273585">
|
|
||||||
<meta name="DC.Language" content="en-us">
|
|
||||||
<link rel="stylesheet" type="text/css" href="public_sys-resources/commonltr.css">
|
|
||||||
<title>Modifying Specifications of a Protected Instance</title>
|
|
||||||
</head>
|
|
||||||
<body style="clear:both; padding-left:10px; padding-top:5px; padding-right:5px; padding-bottom:5px"><a name="en-us_topic_0110273585"></a><a name="en-us_topic_0110273585"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Modifying Specifications of a Protected Instance</h1>
|
<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>
|
<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>
|
<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>
|
<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>
|
||||||
<div class="section" id="en-us_topic_0110273585__section8218163017179"><h4 class="sectiontitle">Prerequisites</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 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>
|
||||||
<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__en-us_topic_0108180805_b17945113171413">Service List</strong> and choose <strong id="en-us_topic_0110273585__en-us_topic_0108180805_b1590754116342">Storage</strong> > <strong id="en-us_topic_0110273585__en-us_topic_0108180805_b149086418342">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__en-us_topic_0108180805_b161375626">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
<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__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_0168363715.png"></span></div>
|
</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_0168373790.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 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>
|
</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><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>
|
||||||
@ -49,5 +22,4 @@
|
|||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_ug_pi_0000.html">Managing Protected Instances</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_ug_pi_0000.html">Managing Protected Instances</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</body>
|
|
||||||
</html>
|
|
||||||
|
|||||||
@ -12,7 +12,7 @@
|
|||||||
<tbody><tr id="en-us_topic_0110981899__row1646139131316"><td class="cellrowborder" valign="top" width="19.259999999999998%" headers="mcps1.3.2.2.3.1.1 "><p id="en-us_topic_0110981899__p44719395133">Computing</p>
|
<tbody><tr id="en-us_topic_0110981899__row1646139131316"><td class="cellrowborder" valign="top" width="19.259999999999998%" headers="mcps1.3.2.2.3.1.1 "><p id="en-us_topic_0110981899__p44719395133">Computing</p>
|
||||||
</td>
|
</td>
|
||||||
<td class="cellrowborder" valign="top" width="80.74%" headers="mcps1.3.2.2.3.1.2 "><p id="en-us_topic_0110981899__p990411910122">Constraints on server types:</p>
|
<td class="cellrowborder" valign="top" width="80.74%" headers="mcps1.3.2.2.3.1.2 "><p id="en-us_topic_0110981899__p990411910122">Constraints on server types:</p>
|
||||||
<li id="en-us_topic_0110981899__li10903612181217">x86 ECSs with GPU-accelerated and FPGA-accelerated types are not supported.</li></ul>
|
<ul id="en-us_topic_0110981899__ul10975758911"><li id="en-us_topic_0110981899__li79764581616">GPU-accelerated, FPGA-accelerated, and C6 ECSs are not supported.<ul id="en-us_topic_0110981899__ul1890317124122"><li id="en-us_topic_0110981899__li1434231821415">Kunpeng ECSs are not supported.</li><li id="en-us_topic_0110981899__li10903612181217">x86 ECSs with GPU-accelerated and FPGA-accelerated types are not supported.</li></ul>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
@ -56,11 +56,14 @@
|
|||||||
</div>
|
</div>
|
||||||
<div class="note" id="en-us_topic_0110981899__note376910459449"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p94762355446">If the AZ of the production site becomes faulty, you can use the DR drill function to restore the <span id="en-us_topic_0110981899__text316715993110">server</span><span id="en-us_topic_0110981899__text41671497317"></span> services in the AZ.</p>
|
<div class="note" id="en-us_topic_0110981899__note376910459449"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p94762355446">If the AZ of the production site becomes faulty, you can use the DR drill function to restore the <span id="en-us_topic_0110981899__text316715993110">server</span><span id="en-us_topic_0110981899__text41671497317"></span> services in the AZ.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
<div class="section" id="en-us_topic_0110981899__section330514140125"><h4 class="sectiontitle">Restrictions on Logging In to a Server After You Perform a Planned Failover, Failover, or DR Drill for the First Time</h4><ul id="en-us_topic_0110981899__ul1345182955615"><li id="en-us_topic_0110981899__li19451132918566">For servers with Cloud-Init/Cloudbase-Init installed, after you perform a planned failover, failover, or DR drill for the first time, Cloud-Init/Cloudbase-Init will start when the servers start for the first time to inject the initial data. The password or key pair for logging in to the production site server, DR site server, or DR drill server will change.</li><li id="en-us_topic_0110981899__li1345142945617">For servers without Cloud-Init/Cloudbase-Init installed, the password or key pair for logging in to the production site, DR site server, or DR drill server will not change after you perform a planned failover or failover for the first time.</li></ul>
|
<div class="section" id="en-us_topic_0110981899__section330514140125"><h4 class="sectiontitle">Constraints on Logging In to the Server After a Switchover, Failover, or DR Drill Is Executed First Time Ever</h4><ul id="en-us_topic_0110981899__ul1345182955615"><li id="en-us_topic_0110981899__li19451132918566"><p id="en-us_topic_0110981899__p8853133775119"><a name="en-us_topic_0110981899__li19451132918566"></a><a name="li19451132918566"></a>After you have performed a switchover, failover, or DR drill for the first time:</p>
|
||||||
<p id="en-us_topic_0110981899__p0226658455">The following describes an example of server login restrictions after you perform a planned failover or failover for the first time. For details about the login restrictions for the DR drill server, see the login restrictions for the DR site server in this scenario.</p>
|
<p id="en-us_topic_0110981899__p11469829105216">If your servers are installed with Cloud-Init/Cloudbase-Init, Cloud-Init/Cloudbase-Init will start along with the server's first startup to inject the initial data. In this case, the password or key pair used to log in to the production site server, DR site server, or drill server will change.</p>
|
||||||
<p id="en-us_topic_0110981899__p16190122612519">Server A and server B are deployed. After the first time planned failover or failover, the production site server and DR site server are listed in <a href="#en-us_topic_0110981899__table92017496206">Table 2</a>.</p>
|
</li><li id="en-us_topic_0110981899__li1345142945617"><p id="en-us_topic_0110981899__p1222512775219"><a name="en-us_topic_0110981899__li1345142945617"></a><a name="li1345142945617"></a>If your servers are not installed with Cloud-Init/Cloudbase-Init, the password or key pair used to log in to the production site server, DR site server, or drill server will not change.</p>
|
||||||
|
</li></ul>
|
||||||
|
<p id="en-us_topic_0110981899__p0226658455">The following uses a switchover or failover as the example operation. For the login constraints on drill servers, see those for DR site servers.</p>
|
||||||
|
<p id="en-us_topic_0110981899__p16190122612519">In the following example, Server A and server B are deployed. <a href="#en-us_topic_0110981899__table92017496206">Table 2</a> shows the servers before and after the operation.</p>
|
||||||
|
|
||||||
<div class="tablenoborder"><a name="en-us_topic_0110981899__table92017496206"></a><a name="table92017496206"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0110981899__table92017496206" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Production site and DR site servers after a planned failover or failover</caption><thead align="left"><tr id="en-us_topic_0110981899__row92016497207"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.4.5.2.4.1.1"><p id="en-us_topic_0110981899__p22014982019">N/A</p>
|
<div class="tablenoborder"><a name="en-us_topic_0110981899__table92017496206"></a><a name="table92017496206"></a><table cellpadding="4" cellspacing="0" summary="" id="en-us_topic_0110981899__table92017496206" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Servers before and after a switchover or failover</caption><thead align="left"><tr id="en-us_topic_0110981899__row92016497207"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.4.5.2.4.1.1"><p id="en-us_topic_0110981899__p22014982019">N/A</p>
|
||||||
</th>
|
</th>
|
||||||
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.4.5.2.4.1.2"><p id="en-us_topic_0110981899__p12201349182012">Production Site Server</p>
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.4.5.2.4.1.2"><p id="en-us_topic_0110981899__p12201349182012">Production Site Server</p>
|
||||||
</th>
|
</th>
|
||||||
@ -85,27 +88,27 @@
|
|||||||
</tbody>
|
</tbody>
|
||||||
</table>
|
</table>
|
||||||
</div>
|
</div>
|
||||||
<p id="en-us_topic_0110981899__p710994010515">In this case, the detailed login restrictions are as follows:</p>
|
<p id="en-us_topic_0110981899__p710994010515">Detailed login constraints are described as follows:</p>
|
||||||
<div class="p" id="en-us_topic_0110981899__p269721242114">Scenario 1: Server A runs Windows and does not have Cloudbase-Init installed. After the first time planned failover or failover:<ul id="en-us_topic_0110981899__ul16782047152110"><li id="en-us_topic_0110981899__li27894712218">If you choose to use a password for the server login, use the password of server A to log in to the production site server B or DR site server A.</li><li id="en-us_topic_0110981899__li207874716219">If you choose to use a key pair for the server login, use the password obtained from server A to log in to the production site server B or DR site server A.</li></ul>
|
<div class="p" id="en-us_topic_0110981899__p269721242114"><strong id="en-us_topic_0110981899__b5648113511383">Scenario 1</strong>: Server A runs Windows and does not have Cloudbase-Init installed. After the first time switchover or failover:<ul id="en-us_topic_0110981899__ul16782047152110"><li id="en-us_topic_0110981899__li27894712218">If your servers use password for login, you can use the password of Server A to log in to the production site server (Server B) or DR site server (Server A).</li><li id="en-us_topic_0110981899__li207874716219">If your servers use key pair for login, you can use the obtained password of Server A to log in to the production site server (Server B) or DR site server (Server A).</li></ul>
|
||||||
<div class="note" id="en-us_topic_0110981899__note561615617134"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p173611236101614">From the second time planned failover or failover, the login password or key pair of the server without Cloudbase-Init installed will remain the same. Take servers listed in <a href="#en-us_topic_0110981899__table92017496206">Table 2</a> as an example.</p>
|
<div class="note" id="en-us_topic_0110981899__note561615617134"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p173611236101614">After the first time switchover or failover, the password or key pair remains the same for the subsequent switchovers or failovers. Take servers listed in <a href="#en-us_topic_0110981899__table92017496206">Table 2</a> as an example.</p>
|
||||||
<p id="en-us_topic_0110981899__p117381940151419">You can use the password of server A to log in to the production site server or DR site server.</p>
|
<p id="en-us_topic_0110981899__p117381940151419">You can use the password of Server A to log in to the production site server or DR site server.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</div>
|
</div>
|
||||||
<div class="p" id="en-us_topic_0110981899__p5726014182217">Scenario 2: Server A runs Windows and already has Cloudbase-Init installed. After the first time planned failover or failover:<ul id="en-us_topic_0110981899__ul42373322295"><li id="en-us_topic_0110981899__li2237332192911">If you choose to use a password for the server login, check whether Cloudbase-Init is started.<p id="en-us_topic_0110981899__p181652054785"><a name="en-us_topic_0110981899__li2237332192911"></a><a name="li2237332192911"></a>If Cloudbase-Init is not started (normally within three to five minutes after the production site server starts), you can use the password of server B for the login.</p>
|
<div class="p" id="en-us_topic_0110981899__p5726014182217"><strong id="en-us_topic_0110981899__b171941059143916">Scenario 2</strong>: Server A runs Windows and already has Cloudbase-Init installed. After the first time switchover or failover:<ul id="en-us_topic_0110981899__ul42373322295"><li id="en-us_topic_0110981899__li2237332192911">When your servers use password for login,<p id="en-us_topic_0110981899__p181652054785"><a name="en-us_topic_0110981899__li2237332192911"></a><a name="li2237332192911"></a>If Cloudbase-Init is not started (normally within 3 to 5 minutes after the production site server starts), you can use the password of Server B for login.</p>
|
||||||
<p id="en-us_topic_0110981899__p1919784018213">After the Cloudbase-Init is started, the login password of server B set before the planned failover or failover becomes invalid. You need to reset the login password of server B and then use the new password to log in to server B.</p>
|
<p id="en-us_topic_0110981899__p1919784018213">After Cloudbase-Init is started, the login password of Server B becomes invalid. Reset the password and use the new password for login.</p>
|
||||||
</li><li id="en-us_topic_0110981899__li4989164082014">If you choose to use a key pair for the server login, check whether Cloudbase-Init is started.<p id="en-us_topic_0110981899__p15989840132013"><a name="en-us_topic_0110981899__li4989164082014"></a><a name="li4989164082014"></a>If Cloudbase-Init is not started (normally within three to five minutes after the production site server starts), you can use the password of server B for the login.</p>
|
</li><li id="en-us_topic_0110981899__li4989164082014">When your servers use key pair for login,<p id="en-us_topic_0110981899__p15989840132013"><a name="en-us_topic_0110981899__li4989164082014"></a><a name="li4989164082014"></a>If Cloudbase-Init is not started (normally within 3 to 5 minutes after the production site server starts), you can use the obtained login password of Server B for login.</p>
|
||||||
<p id="en-us_topic_0110981899__p198924010206">After the Cloudbase-Init is started, the login password of server B obtained before the planned failover or failover becomes invalid. You need to obtain the login password of server B again.</p>
|
<p id="en-us_topic_0110981899__p198924010206">After Cloudbase-Init is started, the obtained login password of Server B becomes invalid. Obtain the password again.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
<div class="note" id="en-us_topic_0110981899__note1934520333568"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p1434516335567">From the second time planned failover or failover, the login password or key pair of the server with Cloudbase-Init installed will remain the same. Take servers listed in <a href="#en-us_topic_0110981899__table92017496206">Table 2</a> as an example.</p>
|
<div class="note" id="en-us_topic_0110981899__note1934520333568"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p1434516335567">After the first time switchover or failover, the password or key pair remains the same for the subsequent switchovers or failovers. Take servers listed in <a href="#en-us_topic_0110981899__table92017496206">Table 2</a> as an example.</p>
|
||||||
<ul id="en-us_topic_0110981899__ul2345193365620"><li id="en-us_topic_0110981899__li5345733135618">Login using a password: Reset the password of server B and use the new password to log in to server B after the first time planned failover or failover.</li><li id="en-us_topic_0110981899__li14345193395615">Login using a key pair: Obtain the password of server B and use the obtained password to log in to server B after the first time planned failover or failover.</li></ul>
|
<ul id="en-us_topic_0110981899__ul2345193365620"><li id="en-us_topic_0110981899__li5345733135618">Login using a password: Reset the password of Server B and use the new password for login.</li><li id="en-us_topic_0110981899__li14345193395615">Login using a key pair: Obtain the password of Server B again and use the obtained password to log in to Server B.</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
</div>
|
</div>
|
||||||
<div class="p" id="en-us_topic_0110981899__p183325334563">Scenario 3: Server A runs Linux. After the first time planned failover or failover:<ul id="en-us_topic_0110981899__ul0767614125816"><li id="en-us_topic_0110981899__li18767121419586">If you choose to use a password for the server login, use the password of server A to log in to the production site server B or DR site server A. <p id="en-us_topic_0110981899__p15512540183319"><a name="en-us_topic_0110981899__li18767121419586"></a><a name="li18767121419586"></a>If the login password of server A is not changed before the planned failover or failover, use the login password configured when server A is created after the planned failover or failover. </p>
|
<div class="p" id="en-us_topic_0110981899__p183325334563"><strong id="en-us_topic_0110981899__b1615462304120">Scenario 3</strong>: Server A runs Linux. After the first time switchover or failover:<ul id="en-us_topic_0110981899__ul0767614125816"><li id="en-us_topic_0110981899__li18767121419586">If your servers use password for login, you can use the password of Server A to log in to the production site server (Server B) or disaster recovery site server (Server A). Specifically:<p id="en-us_topic_0110981899__p15512540183319"><a name="en-us_topic_0110981899__li18767121419586"></a><a name="li18767121419586"></a>If the login password of Server A is not changed before the operation, use this password for login.</p>
|
||||||
<div class="p" id="en-us_topic_0110981899__p96514020349">If the login password of server A is changed before the planned failover or failover, use the new login password after the planned failover or failover.<div class="note" id="en-us_topic_0110981899__note1023795412328"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p6142132171710">For ECSs running OSs other than CoreOS, the login password does not change after the first-time planned failover or failover.</p>
|
<div class="p" id="en-us_topic_0110981899__p96514020349">If the login password of server A has been changed before the operation, use the new password for login.<div class="note" id="en-us_topic_0110981899__note1023795412328"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="en-us_topic_0110981899__p6142132171710">For ECS OSs other than CoreOS, the login password does not change after the first time switchover or failover.</p>
|
||||||
<p id="en-us_topic_0110981899__p767512424">For ECSs running CoreOS, the login password of server A will restore to the initial one after the first-time planned failover or failover. Therefore, you need to use the login password configured when server A is created to log in to production site server A or DR site server B.</p>
|
<p id="en-us_topic_0110981899__p767512424">For ECSs running CoreOS, the login password of Server A will restore to the initial one after the first time switchover or failover. In this case, use the login password configured when Server A is created to log in to production site Server A or DR site Server B.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</div>
|
</div>
|
||||||
</li><li id="en-us_topic_0110981899__li676891415584">If you choose to use a key pair for the server login, use the key pair of server A to log in to the production site server B or DR site server A in SSH mode. </li></ul>
|
</li><li id="en-us_topic_0110981899__li676891415584">If your server uses key pair for login, use the SSH key pair of Server A to log in to production site Server B or DR site Server A.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
@ -13,7 +13,7 @@
|
|||||||
</div></div>
|
</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>
|
</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>
|
||||||
<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 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__b73399720414">Available</strong>, <strong id="en-us_topic_0122528555__b153401377413">Protecting</strong>, <strong id="en-us_topic_0122528555__b2340157640">Failover complete</strong>, <strong id="en-us_topic_0122528555__b8341971641">Enabling protection failed</strong>, <strong id="en-us_topic_0122528555__b113421471844">Disabling protection failed</strong>, <strong id="en-us_topic_0122528555__b93432714411">Switchover failed</strong>, <strong id="en-us_topic_0122528555__b43440719418">Re-enabling protection failed</strong>, or <strong id="en-us_topic_0122528555__b5344570412">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>
|
||||||
<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>
|
<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__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>
|
||||||
|
|||||||
File diff suppressed because it is too large
Load Diff
Binary file not shown.
|
Before Width: | Height: | Size: 68 B After Width: | Height: | Size: 1.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 70 B After Width: | Height: | Size: 1.8 KiB |
@ -12,11 +12,11 @@
|
|||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="en-us_topic_0109956554.html">What Are the Differences Between DR and Backup?</a></strong><br>
|
<li class="ulchildlink"><strong><a href="en-us_topic_0109956554.html">What Are the Differences Between DR and Backup?</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_06_0402.html">What Can I Do When the EIP Cannot Be Pinged After I Perform a Planned Failover for a Protection Group Containing a SUSE Server?</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_06_0402.html">What Can I Do When the EIP Cannot Be Pinged After I Perform a Switchover for a Protection Group Containing a SUSE Server?</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_06_0403.html">What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_06_0403.html">What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><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></strong><br>
|
<li class="ulchildlink"><strong><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 Switchover or Failover?</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_faq_0004.html">Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_faq_0004.html">Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
|
|||||||
@ -1,11 +1,11 @@
|
|||||||
<a name="sdrs_06_0402"></a><a name="sdrs_06_0402"></a>
|
<a name="sdrs_06_0402"></a><a name="sdrs_06_0402"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">What Can I Do When the EIP Cannot Be Pinged After I Perform a Planned Failover for a Protection Group Containing a SUSE Server?</h1>
|
<h1 class="topictitle1">What Can I Do When the EIP Cannot Be Pinged After I Perform a Switchover for a Protection Group Containing a SUSE Server?</h1>
|
||||||
<div id="body1543310051463"><div class="section" id="sdrs_06_0402__section22559532136"><h4 class="sectiontitle">Symptom</h4><p id="sdrs_06_0402__p3552184271614">The production site server in a protection group runs the SUSE OS. After users enable protection and perform a planned failover for the protection group, the EIP of the server cannot be pinged.</p>
|
<div id="body1543310051463"><div class="section" id="sdrs_06_0402__section22559532136"><h4 class="sectiontitle">Symptom</h4><p id="sdrs_06_0402__p3552184271614">The production site server in a protection group runs the SUSE OS. After users enable protection and perform a switchover for the protection group, the EIP of the server cannot be pinged.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_06_0402__section67031648161616"><h4 class="sectiontitle">Root Cause</h4><p id="sdrs_06_0402__p1571010483165">After the planned failover, the server NIC name may already change. If the NIC has an EIP bound, the EIP cannot be pinged.</p>
|
<div class="section" id="sdrs_06_0402__section67031648161616"><h4 class="sectiontitle">Root Cause</h4><p id="sdrs_06_0402__p1571010483165">After the switchover, the server NIC name may already change. If the NIC has an EIP bound, the EIP cannot be pinged.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_06_0402__section12474891189"><h4 class="sectiontitle">Handling Method</h4><p id="sdrs_06_0402__p151611713111817">After the planned failover, delete the <strong id="sdrs_06_0402__b842352706191559">/etc/udev/rules.d/70-persistent-net.rules</strong> file on the DR site server and then restart it. The procedure is as follows.</p>
|
<div class="section" id="sdrs_06_0402__section12474891189"><h4 class="sectiontitle">Handling Method</h4><p id="sdrs_06_0402__p151611713111817">After the switchover, delete the <strong id="sdrs_06_0402__b1635175132018">/etc/udev/rules.d/70-persistent-net.rules</strong> file on the DR site server and then restart it. The procedure is as follows.</p>
|
||||||
<ol id="sdrs_06_0402__ol72182209167"><li id="sdrs_06_0402__li13218102081618"><span>Log in to the DR site server.</span><p><ol type="a" id="sdrs_06_0402__ol15555193712188"><li id="sdrs_06_0402__li115551637101811">Log in to the management console and click <strong id="sdrs_06_0402__b1646823116339">Elastic Cloud Server</strong> under <strong id="sdrs_06_0402__b1547093116339">Computing</strong>.</li><li id="sdrs_06_0402__li645119222513">In the server list, select the DR site server.</li><li id="sdrs_06_0402__li195612354511">Locate the row containing the server and click <strong id="sdrs_06_0402__b45069891102259">Remote Login</strong> in the <strong id="sdrs_06_0402__b2975843102259">Operation</strong> column.<p id="sdrs_06_0402__p1458173312117">Log in to the server as prompted.</p>
|
<ol id="sdrs_06_0402__ol72182209167"><li id="sdrs_06_0402__li13218102081618"><span>Log in to the DR site server.</span><p><ol type="a" id="sdrs_06_0402__ol15555193712188"><li id="sdrs_06_0402__li115551637101811">Log in to the management console and click <strong id="sdrs_06_0402__b1646823116339">Elastic Cloud Server</strong> under <strong id="sdrs_06_0402__b1547093116339">Computing</strong>.</li><li id="sdrs_06_0402__li645119222513">In the server list, select the DR site server.</li><li id="sdrs_06_0402__li195612354511">Locate the row containing the server and click <strong id="sdrs_06_0402__b45069891102259">Remote Login</strong> in the <strong id="sdrs_06_0402__b2975843102259">Operation</strong> column.<p id="sdrs_06_0402__p1458173312117">Log in to the server as prompted.</p>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
</p></li><li id="sdrs_06_0402__li142916238168"><span>Run the following command to delete the file:</span><p><p id="sdrs_06_0402__p16949231114216"><strong id="sdrs_06_0402__b14210123544212">rm /etc/udev/rules.d/70-persistent-net.rules</strong></p>
|
</p></li><li id="sdrs_06_0402__li142916238168"><span>Run the following command to delete the file:</span><p><p id="sdrs_06_0402__p16949231114216"><strong id="sdrs_06_0402__b14210123544212">rm /etc/udev/rules.d/70-persistent-net.rules</strong></p>
|
||||||
|
|||||||
@ -1,20 +1,20 @@
|
|||||||
<a name="sdrs_06_0404"></a><a name="sdrs_06_0404"></a>
|
<a name="sdrs_06_0404"></a><a name="sdrs_06_0404"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?</h1>
|
<h1 class="topictitle1">What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Switchover or Failover?</h1>
|
||||||
<div id="body1560821721889"><div class="section" id="sdrs_06_0404__section37204431987"><h4 class="sectiontitle">Symptom</h4><p id="sdrs_06_0404__p46037471784">Users have changed <strong id="sdrs_06_0404__b916751020582">hostname</strong> of the production site server before they perform a planned failover or failover for the first time. After the planned failover or failover, users start the DR site server and find that <strong id="sdrs_06_0404__b17932115885818">hostname</strong> of the DR site server is not updated accordingly.</p>
|
<div id="body1560821721889"><div class="section" id="sdrs_06_0404__section37204431987"><h4 class="sectiontitle">Symptom</h4><p id="sdrs_06_0404__p46037471784">Users have changed <strong id="sdrs_06_0404__b6758141672017">hostname</strong> of the production site server before they perform a switchover or failover for the first time. After the switchover or failover, users start the DR site server and find that <strong id="sdrs_06_0404__b12853112115203">hostname</strong> of the DR site server is not updated accordingly.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_06_0404__section11269131061117"><h4 class="sectiontitle"><strong id="sdrs_06_0404__b1666416541068">Possible Causes</strong></h4><p id="sdrs_06_0404__p8622141219116">For Linux servers, if you have changed <strong id="sdrs_06_0404__b12854624195716">hostname</strong> of the production site server before you perform a planned failover or failover for the first time, this modification will not synchronize to the DR site server.</p>
|
<div class="section" id="sdrs_06_0404__section11269131061117"><h4 class="sectiontitle">Possible Causes</h4><p id="sdrs_06_0404__p8622141219116">For Linux servers, if you have changed <strong id="sdrs_06_0404__b17723334142012">hostname</strong> of the production site server before you perform a switchover or failover for the first time, this modification will not synchronize to the DR site server.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_06_0404__section2084985454913"><h4 class="sectiontitle"><strong id="sdrs_06_0404__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="sdrs_06_0404__ul378213355020"><li id="sdrs_06_0404__li278212305013">The production site server is a Linux server with Cloud-Init installed.</li><li id="sdrs_06_0404__li861091335011"><strong id="sdrs_06_0404__b164870341720">hostname</strong> of the production site server has been changed.</li></ul>
|
<div class="section" id="sdrs_06_0404__section2084985454913"><h4 class="sectiontitle">Prerequisites</h4><ul id="sdrs_06_0404__ul378213355020"><li id="sdrs_06_0404__li278212305013">The production site server is a Linux server with Cloud-Init installed.</li><li id="sdrs_06_0404__li861091335011"><strong id="sdrs_06_0404__b164870341720">hostname</strong> of the production site server has been changed.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_06_0404__section183011437149"><h4 class="sectiontitle">Solution 1 (If You Have Not Performed a Planned Failover or Failover)</h4><p id="sdrs_06_0404__p4458154574718">Set <span class="parmvalue" id="sdrs_06_0404__parmvalue15303175791819"><b>preserve_hostname: false</b></span> to <span class="parmvalue" id="sdrs_06_0404__parmvalue2303155701814"><b>preserve_hostname: true</b></span> in the Cloud-Init configuration file <strong id="sdrs_06_0404__b1290015442310">/etc/cloud/cloud.cfg</strong> to ensure that <strong id="sdrs_06_0404__b51851045132418">hostname</strong> of the production site server and DR site server are the same after you enable protection.</p>
|
<div class="section" id="sdrs_06_0404__section183011437149"><h4 class="sectiontitle">Solution 1 (If You Have Not Performed a Switchover or Failover)</h4><p id="sdrs_06_0404__p4458154574718">Set <span class="parmvalue" id="sdrs_06_0404__parmvalue15303175791819"><b>preserve_hostname: false</b></span> to <span class="parmvalue" id="sdrs_06_0404__parmvalue2303155701814"><b>preserve_hostname: true</b></span> in the Cloud-Init configuration file <strong id="sdrs_06_0404__b1290015442310">/etc/cloud/cloud.cfg</strong> to ensure that <strong id="sdrs_06_0404__b51851045132418">hostname</strong> of the production site server and DR site server are the same after you enable protection.</p>
|
||||||
<p id="sdrs_06_0404__p767874541420">The procedure is as follows:</p>
|
<p id="sdrs_06_0404__p767874541420">The procedure is as follows:</p>
|
||||||
</div>
|
</div>
|
||||||
<ol id="sdrs_06_0404__ol16293105113237"><li id="sdrs_06_0404__li1329311519231">Log in to the production site server.</li><li id="sdrs_06_0404__li1282121102419">Run the following command to edit the <strong id="sdrs_06_0404__b842352706192723">/etc/cloud/cloud.cfg</strong> configuration file:<p id="sdrs_06_0404__p1515233122417"><strong id="sdrs_06_0404__b27741446202410">sudo vim /etc/cloud/cloud.cfg</strong></p>
|
<ol id="sdrs_06_0404__ol16293105113237"><li id="sdrs_06_0404__li1329311519231">Log in to the production site server.</li><li id="sdrs_06_0404__li1282121102419">Run the following command to edit the <strong id="sdrs_06_0404__b842352706192723">/etc/cloud/cloud.cfg</strong> configuration file:<p id="sdrs_06_0404__p1515233122417"><strong id="sdrs_06_0404__b27741446202410">sudo vim /etc/cloud/cloud.cfg</strong></p>
|
||||||
</li><li id="sdrs_06_0404__li134135462410">Modify <strong id="sdrs_06_0404__b1841672862611">preserve_hostname</strong>.<ul id="sdrs_06_0404__ul1342852572614"><li id="sdrs_06_0404__li14429182510265">If <strong id="sdrs_06_0404__b842352706192827">preserve_hostname: false</strong> is already available in the <strong id="sdrs_06_0404__b842352706192837">/etc/cloud/cloud.cfg</strong> configuration file, change it to <strong id="sdrs_06_0404__b842352706192851">preserve_hostname: true</strong>.</li><li id="sdrs_06_0404__li64291925192615">If <strong id="sdrs_06_0404__b154393914193010">preserve_hostname: false</strong> is unavailable in the <strong id="sdrs_06_0404__b842352706193047">/etc/cloud/cloud.cfg</strong> configuration file, add <strong id="sdrs_06_0404__b198044657219342">preserve_hostname: true</strong> before <strong id="sdrs_06_0404__b84235270619312">cloud_init_modules</strong>.</li></ul>
|
</li><li id="sdrs_06_0404__li134135462410">Modify <strong id="sdrs_06_0404__b1841672862611">preserve_hostname</strong>.<ul id="sdrs_06_0404__ul1342852572614"><li id="sdrs_06_0404__li14429182510265">If <strong id="sdrs_06_0404__b842352706192827">preserve_hostname: false</strong> is already available in the <strong id="sdrs_06_0404__b842352706192837">/etc/cloud/cloud.cfg</strong> configuration file, change it to <strong id="sdrs_06_0404__b842352706192851">preserve_hostname: true</strong>.</li><li id="sdrs_06_0404__li64291925192615">If <strong id="sdrs_06_0404__b154393914193010">preserve_hostname: false</strong> is unavailable in the <strong id="sdrs_06_0404__b842352706193047">/etc/cloud/cloud.cfg</strong> configuration file, add <strong id="sdrs_06_0404__b198044657219342">preserve_hostname: true</strong> before <strong id="sdrs_06_0404__b84235270619312">cloud_init_modules</strong>.</li></ul>
|
||||||
</li><li id="sdrs_06_0404__li143771326102713">Perform a planned failover or failover.<p id="sdrs_06_0404__p6341386508"><a name="sdrs_06_0404__li143771326102713"></a><a name="li143771326102713"></a>After the planned failover or failover, <strong id="sdrs_06_0404__b1011410116286">hostname</strong> of the DR site server and production site server are the same.</p>
|
</li><li id="sdrs_06_0404__li143771326102713">Perform a switchover or failover.<p id="sdrs_06_0404__p6341386508"><a name="sdrs_06_0404__li143771326102713"></a><a name="li143771326102713"></a>After the switchover or failover, <strong id="sdrs_06_0404__b92431651132019">hostname</strong> of the DR site server and production site server are the same.</p>
|
||||||
</li></ol>
|
</li></ol>
|
||||||
<div class="section" id="sdrs_06_0404__section2538238204516"><h4 class="sectiontitle">Solution 2 (If You Have Performed a Planned Failover or Failover)</h4><p id="sdrs_06_0404__p457484134517">If you have not modified configuration file <strong id="sdrs_06_0404__b913112455334">/etc/cloud/cloud.cfg</strong> before the planned failover or failover, log in to the DR site server and manually change <strong id="sdrs_06_0404__b139865919368">hostname</strong> of the DR site server to that of the production site server.</p>
|
<div class="section" id="sdrs_06_0404__section2538238204516"><h4 class="sectiontitle">Solution 2 (If You Have Performed a Switchover or Failover)</h4><p id="sdrs_06_0404__p457484134517">If you have not modified configuration file <strong id="sdrs_06_0404__b181307192114">/etc/cloud/cloud.cfg</strong> before the switchover or failover, log in to the DR site server and manually change <strong id="sdrs_06_0404__b181301213211">hostname</strong> of the DR site server to that of the production site server.</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -1,7 +1,8 @@
|
|||||||
<a name="sdrs_06_0410"></a><a name="sdrs_06_0410"></a>
|
<a name="sdrs_06_0410"></a><a name="sdrs_06_0410"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">What Is DR?</h1>
|
<h1 class="topictitle1">What Is DR?</h1>
|
||||||
<div id="body1524730611989"><p id="sdrs_06_0410__p8060118">Disaster recovery (DR) is a broad concept. In a broad sense, disaster recovery is a systematic project that includes all contents related to service continuity. Regarding IT, DR provides a computing system that protects user service systems from various disasters. DR is the ability to provide continuous services after an accident, such as a fire, earthquake, or power outage. This is achieved by setting up two or more IT systems with the same functions in dispersed areas. If one system stops, the services can quickly recover on the other system and continue to run properly.</p>
|
<div id="body1524730611989"><p id="sdrs_06_0410__p198625411475">Disaster recovery (DR) is a broad concept.</p>
|
||||||
|
<ul id="sdrs_06_0410__ul1382105424720"><li id="sdrs_06_0410__li18929135914474">In a broad sense, DR is a systematic project that includes all abilities related to business continuity. Regarding IT, DR provides a computing system that protects user service systems from various disasters.</li><li id="sdrs_06_0410__li168285404711">DR is the ability to provide continuous services after an accident, such as a fire, earthquake, or power outage. This is achieved by setting up two or more IT systems with the same functions in dispersed areas. If one system stops, the services can quickly recover on the other system and continue to run properly.</li></ul>
|
||||||
<p id="sdrs_06_0410__p42081240132417">The purpose of DR is to ensure maximum service continuity in the event of a natural or human-caused disaster on production systems.</p>
|
<p id="sdrs_06_0410__p42081240132417">The purpose of DR is to ensure maximum service continuity in the event of a natural or human-caused disaster on production systems.</p>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -2,15 +2,15 @@
|
|||||||
|
|
||||||
<h1 class="topictitle1">What Are the Highlights of SDRS?</h1>
|
<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>
|
<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>
|
<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 switchover 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_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_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_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>
|
</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 when users perform a switchover 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>
|
<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_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_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_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 switchovers for expected interruptions with zero data loss, or failovers for unexpected failures to recover 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_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><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>
|
</li></ul>
|
||||||
|
|||||||
@ -3,7 +3,8 @@
|
|||||||
<h1 class="topictitle1">What Are RPO and RTO?</h1>
|
<h1 class="topictitle1">What Are RPO and RTO?</h1>
|
||||||
<div id="body1524730611989"><p id="sdrs_06_0440__p2375828939">Recovery Point Objective (RPO): the maximum data loss amount tolerated by the system.</p>
|
<div id="body1524730611989"><p id="sdrs_06_0440__p2375828939">Recovery Point Objective (RPO): the maximum data loss amount tolerated by the system.</p>
|
||||||
<p id="sdrs_06_0440__p2375142812315">Recovery Time Objective (RTO): the maximum service interruption duration tolerated by the system. It refers to the requirement for the recovery duration of an information system failure or service function failure caused by a disaster.</p>
|
<p id="sdrs_06_0440__p2375142812315">Recovery Time Objective (RTO): the maximum service interruption duration tolerated by the system. It refers to the requirement for the recovery duration of an information system failure or service function failure caused by a disaster.</p>
|
||||||
<div class="fignone" id="sdrs_06_0440__fig163389455573"><span class="figcap"><b>Figure 1 </b>RPO and RTO</span><br><span><img class="vsd" id="sdrs_06_0440__image93399455572" src="en-us_image_0288665392.png"></span></div>
|
<p id="sdrs_06_0440__p10324175411918"><a href="#sdrs_06_0440__fig163389455573">Figure 1</a> shows an example of RPO and RTO.</p>
|
||||||
|
<div class="fignone" id="sdrs_06_0440__fig163389455573"><a name="sdrs_06_0440__fig163389455573"></a><a name="fig163389455573"></a><span class="figcap"><b>Figure 1 </b>RPO and RTO</span><br><span><img class="vsd" id="sdrs_06_0440__image93399455572" src="en-us_image_0288665392.png"></span></div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<div class="familylinks">
|
<div class="familylinks">
|
||||||
|
|||||||
@ -1,7 +1,7 @@
|
|||||||
<a name="sdrs_faq_0004"></a><a name="sdrs_faq_0004"></a>
|
<a name="sdrs_faq_0004"></a><a name="sdrs_faq_0004"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?</h1>
|
<h1 class="topictitle1">Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?</h1>
|
||||||
<div id="body1566975392276"><div class="p" id="sdrs_faq_0004__p8060118">SDRS performs planned failovers or failovers for protection groups. After a planned failover or failover, the production site and DR site exchange. When the production site is functional, users can perform a planned failover according to plans. When a fault occurs at the production site, users need to perform a failover.<ul id="sdrs_faq_0004__ul14861146191915"><li id="sdrs_faq_0004__li144864466196">During a planned failover, NICs of the production site <span id="sdrs_faq_0004__text070286172120">server</span><span id="sdrs_faq_0004__text270214615217"></span>s and DR site <span id="sdrs_faq_0004__text1183920127217">server</span><span id="sdrs_faq_0004__text128392125211"></span>s will exchange. In this way, <span id="sdrs_faq_0004__text19728277219">server</span><span id="sdrs_faq_0004__text372162732117"></span>s can be accessed using the same IP addresses and MAC addresses after the planned failover.</li><li id="sdrs_faq_0004__li109855133207">During a failover, production site <span id="sdrs_faq_0004__text3418100112417">server</span><span id="sdrs_faq_0004__text94188052411"></span>s do not work properly, NICs of the production site <span id="sdrs_faq_0004__text195478305282">server</span><span id="sdrs_faq_0004__text554973019281"></span>s will be migrated to the DR site <span id="sdrs_faq_0004__text1184194112813">server</span><span id="sdrs_faq_0004__text1518714419285"></span>s. The primary NICs of the DR site <span id="sdrs_faq_0004__text33277882917">server</span><span id="sdrs_faq_0004__text5333158102917"></span>s will enter the to-be-used state. Therefore, after a failover, the original production site <span id="sdrs_faq_0004__text18713155258">server</span><span id="sdrs_faq_0004__text67139542516"></span>s will not have NICs. When users perform reprotection for the protection group after the original production site <span id="sdrs_faq_0004__text38282112311">server</span><span id="sdrs_faq_0004__text18352173110"></span>s restore, the primary NICs in the to-be-used state detached from the original DR site <span id="sdrs_faq_0004__text1945636192518">server</span><span id="sdrs_faq_0004__text139451936142518"></span>s will be attached to the original production site <span id="sdrs_faq_0004__text134395017322">server</span><span id="sdrs_faq_0004__text1246165023216"></span>s. Then, the NICs of the production site <span id="sdrs_faq_0004__text195024416332">server</span><span id="sdrs_faq_0004__text1650934183317"></span>s and DR site <span id="sdrs_faq_0004__text154781782334">server</span><span id="sdrs_faq_0004__text549115811332"></span>s are exchanged.</li></ul>
|
<div id="body1566975392276"><div class="p" id="sdrs_faq_0004__p8060118">SDRS performs switchovers or failovers for protection groups. After a switchover or failover, the production site and DR site exchange. When the production site is functional, users can perform a switchover according to plans. When a fault occurs at the production site, users need to perform a failover.<ul id="sdrs_faq_0004__ul14861146191915"><li id="sdrs_faq_0004__li144864466196">During a switchover, NICs of the production site <span id="sdrs_faq_0004__text070286172120">server</span><span id="sdrs_faq_0004__text270214615217"></span>s and DR site <span id="sdrs_faq_0004__text1183920127217">server</span><span id="sdrs_faq_0004__text128392125211"></span>s will exchange. In this way, <span id="sdrs_faq_0004__text19728277219">server</span><span id="sdrs_faq_0004__text372162732117"></span>s can be accessed using the same IP addresses and MAC addresses after the switchover.</li><li id="sdrs_faq_0004__li109855133207">During a failover, production site <span id="sdrs_faq_0004__text3418100112417">server</span><span id="sdrs_faq_0004__text94188052411"></span>s do not work properly, NICs of the production site <span id="sdrs_faq_0004__text195478305282">server</span><span id="sdrs_faq_0004__text554973019281"></span>s will be migrated to the DR site <span id="sdrs_faq_0004__text1184194112813">server</span><span id="sdrs_faq_0004__text1518714419285"></span>s. The primary NICs of the DR site <span id="sdrs_faq_0004__text33277882917">server</span><span id="sdrs_faq_0004__text5333158102917"></span>s will enter the to-be-used state. Therefore, after a failover, the original production site <span id="sdrs_faq_0004__text18713155258">server</span><span id="sdrs_faq_0004__text67139542516"></span>s will not have NICs. When users perform reprotection for the protection group after the original production site <span id="sdrs_faq_0004__text38282112311">server</span><span id="sdrs_faq_0004__text18352173110"></span>s restore, the primary NICs in the to-be-used state detached from the original DR site <span id="sdrs_faq_0004__text1945636192518">server</span><span id="sdrs_faq_0004__text139451936142518"></span>s will be attached to the original production site <span id="sdrs_faq_0004__text134395017322">server</span><span id="sdrs_faq_0004__text1246165023216"></span>s. Then, the NICs of the production site <span id="sdrs_faq_0004__text195024416332">server</span><span id="sdrs_faq_0004__text1650934183317"></span>s and DR site <span id="sdrs_faq_0004__text154781782334">server</span><span id="sdrs_faq_0004__text549115811332"></span>s are exchanged.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -6,7 +6,7 @@
|
|||||||
<ul class="ullinks">
|
<ul class="ullinks">
|
||||||
<li class="ulchildlink"><strong><a href="en-us_topic_0125068221.html">What Is SDRS?</a></strong><br>
|
<li class="ulchildlink"><strong><a href="en-us_topic_0125068221.html">What Is SDRS?</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="en-us_topic_0108180804.html">Product Advantages</a></strong><br>
|
<li class="ulchildlink"><strong><a href="en-us_topic_0108180804.html">SDRS Advantages</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_pro_0003.html">Application Scenarios</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_pro_0003.html">Application Scenarios</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
|
|||||||
@ -8,12 +8,12 @@
|
|||||||
<p id="sdrs_pro_0008__p241725022710">For more information about the DR drill function, see <a href="en-us_topic_0122528555.html">Performing a DR Drill</a>.</p>
|
<p id="sdrs_pro_0008__p241725022710">For more information about the DR drill function, see <a href="en-us_topic_0122528555.html">Performing a DR Drill</a>.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_pro_0008__section8466142612574"><h4 class="sectiontitle">DR Site Is Faulty</h4><ul id="sdrs_pro_0008__ul2528144561220"><li id="sdrs_pro_0008__li105281145151220">Description<p id="sdrs_pro_0008__p1762385315142"><a name="sdrs_pro_0008__li105281145151220"></a><a name="li105281145151220"></a>The DR site has a fault. Services at the production site are not affected, but the planned failover cannot be performed. </p>
|
<div class="section" id="sdrs_pro_0008__section8466142612574"><h4 class="sectiontitle">DR Site Is Faulty</h4><ul id="sdrs_pro_0008__ul2528144561220"><li id="sdrs_pro_0008__li105281145151220">Description<p id="sdrs_pro_0008__p1762385315142"><a name="sdrs_pro_0008__li105281145151220"></a><a name="li105281145151220"></a>The DR site has a fault. Services at the production site are not affected, but a switchover cannot be performed.</p>
|
||||||
<div class="fignone" id="sdrs_pro_0008__fig12161743402"><span class="figcap"><b>Figure 2 </b>DR site being faulty</span><br><span><img class="vsd" id="sdrs_pro_0008__image61613418405" src="en-us_image_0288665264.png"></span></div>
|
<div class="fignone" id="sdrs_pro_0008__fig12161743402"><span class="figcap"><b>Figure 2 </b>DR site being faulty</span><br><span><img class="vsd" id="sdrs_pro_0008__image61613418405" src="en-us_image_0288665264.png"></span></div>
|
||||||
</li><li id="sdrs_pro_0008__li452864516121">Solution<p id="sdrs_pro_0008__p10943101981618"><a name="sdrs_pro_0008__li452864516121"></a><a name="li452864516121"></a>Contact the customer service to obtain technical support.</p>
|
</li><li id="sdrs_pro_0008__li452864516121">Solution<p id="sdrs_pro_0008__p10943101981618"><a name="sdrs_pro_0008__li452864516121"></a><a name="li452864516121"></a>Contact the customer service to obtain technical support.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_pro_0008__section107495164323"><h4 class="sectiontitle">Replication Link Is Faulty</h4><ul id="sdrs_pro_0008__ul1896092663219"><li id="sdrs_pro_0008__li11960132618325">Description<p id="sdrs_pro_0008__p18180954133210"><a name="sdrs_pro_0008__li11960132618325"></a><a name="li11960132618325"></a>The replication link between the production site and DR site becomes faulty. Services at the production site are not affected, but the planned failover cannot be performed. </p>
|
<div class="section" id="sdrs_pro_0008__section107495164323"><h4 class="sectiontitle">Replication Link Is Faulty</h4><ul id="sdrs_pro_0008__ul1896092663219"><li id="sdrs_pro_0008__li11960132618325">Description<p id="sdrs_pro_0008__p18180954133210"><a name="sdrs_pro_0008__li11960132618325"></a><a name="li11960132618325"></a>The replication link between the production site and DR site becomes faulty. Services at the production site are not affected, but a switchover cannot be performed.</p>
|
||||||
<div class="fignone" id="sdrs_pro_0008__fig14944168432"><span class="figcap"><b>Figure 3 </b>Replication link being faulty</span><br><span><img class="vsd" id="sdrs_pro_0008__image1394181644316" src="en-us_image_0288665385.png"></span></div>
|
<div class="fignone" id="sdrs_pro_0008__fig14944168432"><span class="figcap"><b>Figure 3 </b>Replication link being faulty</span><br><span><img class="vsd" id="sdrs_pro_0008__image1394181644316" src="en-us_image_0288665385.png"></span></div>
|
||||||
</li><li id="sdrs_pro_0008__li314043215322">Solution<p id="sdrs_pro_0008__p10149143510346"><a name="sdrs_pro_0008__li314043215322"></a><a name="li314043215322"></a>You do not need to perform any operations. The DR protection will automatically restore once the replication link fault is rectified.</p>
|
</li><li id="sdrs_pro_0008__li314043215322">Solution<p id="sdrs_pro_0008__p10149143510346"><a name="sdrs_pro_0008__li314043215322"></a><a name="li314043215322"></a>You do not need to perform any operations. The DR protection will automatically restore once the replication link fault is rectified.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
@ -24,7 +24,7 @@
|
|||||||
<p id="sdrs_pro_0008__p4597121861719">For more information about the failover function, see <a href="en-us_topic_0108560208.html">Performing a Failover</a>.</p>
|
<p id="sdrs_pro_0008__p4597121861719">For more information about the failover function, see <a href="en-us_topic_0108560208.html">Performing a Failover</a>.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_pro_0008__section1518717206394"><h4 class="sectiontitle">Storage Resource at the DR Site Is Faulty </h4><ul id="sdrs_pro_0008__ul2136112814392"><li id="sdrs_pro_0008__li3136142818396">Description<p id="sdrs_pro_0008__p1192917520407"><a name="sdrs_pro_0008__li3136142818396"></a><a name="li3136142818396"></a>The storage resource at the DR site has a fault. Services at the production site are not affected, but the planned failover or failover cannot be performed. </p>
|
<div class="section" id="sdrs_pro_0008__section1518717206394"><h4 class="sectiontitle">Storage Resource at the DR Site Is Faulty </h4><ul id="sdrs_pro_0008__ul2136112814392"><li id="sdrs_pro_0008__li3136142818396">Description<p id="sdrs_pro_0008__p1192917520407"><a name="sdrs_pro_0008__li3136142818396"></a><a name="li3136142818396"></a>The storage resource at the DR site has a fault. Services at the production site are not affected, but a switchover or failover cannot be performed.</p>
|
||||||
<div class="fignone" id="sdrs_pro_0008__fig756316184494"><span class="figcap"><b>Figure 5 </b>Storage resource at the DR site being faulty </span><br><span><img class="vsd" id="sdrs_pro_0008__image1356314183493" src="en-us_image_0288665319.png"></span></div>
|
<div class="fignone" id="sdrs_pro_0008__fig756316184494"><span class="figcap"><b>Figure 5 </b>Storage resource at the DR site being faulty </span><br><span><img class="vsd" id="sdrs_pro_0008__image1356314183493" src="en-us_image_0288665319.png"></span></div>
|
||||||
</li><li id="sdrs_pro_0008__li62972032123919">Solution<p id="sdrs_pro_0008__p17901172014120"><a name="sdrs_pro_0008__li62972032123919"></a><a name="li62972032123919"></a>Contact the customer service to obtain technical support.</p>
|
</li><li id="sdrs_pro_0008__li62972032123919">Solution<p id="sdrs_pro_0008__p17901172014120"><a name="sdrs_pro_0008__li62972032123919"></a><a name="li62972032123919"></a>Contact the customer service to obtain technical support.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
|
|||||||
@ -5,7 +5,7 @@
|
|||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
<ul class="ullinks">
|
<ul class="ullinks">
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_pro_0013.html">SDRS Basic Concepts</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_pro_0013.html">SDRS Concepts</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_pro_0014.html">Region and AZ</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_pro_0014.html">Region and AZ</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
|
|||||||
File diff suppressed because it is too large
Load Diff
@ -6,12 +6,12 @@
|
|||||||
<p id="sdrs_pro_0014__en-us_topic_0184026189_p1479174514614"><a href="#sdrs_pro_0014__en-us_topic_0184026189_fig8747114281212">Figure 1</a> shows the relationship between regions and AZs.</p>
|
<p id="sdrs_pro_0014__en-us_topic_0184026189_p1479174514614"><a href="#sdrs_pro_0014__en-us_topic_0184026189_fig8747114281212">Figure 1</a> shows the relationship between regions and AZs.</p>
|
||||||
<div class="fignone" id="sdrs_pro_0014__en-us_topic_0184026189_fig8747114281212"><a name="sdrs_pro_0014__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="sdrs_pro_0014__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png"></span></div>
|
<div class="fignone" id="sdrs_pro_0014__en-us_topic_0184026189_fig8747114281212"><a name="sdrs_pro_0014__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="sdrs_pro_0014__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png"></span></div>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_pro_0014__en-us_topic_0184026189_section67281149192216"><h4 class="sectiontitle">Selecting a Region</h4><p id="sdrs_pro_0014__en-us_topic_0184026189_p68521454132212">Select a region closest to your target users for lower network latency and quick access.</p>
|
<div class="section" id="sdrs_pro_0014__en-us_topic_0184026189_section67281149192216"><h4 class="sectiontitle">Selecting a Region</h4><p id="sdrs_pro_0014__en-us_topic_0184026189_p68521454132212">You are advised to select a region close to you or your target users. This helps ensure low access latency.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_pro_0014__en-us_topic_0184026189_section193971112578"><h4 class="sectiontitle">Selecting an AZ</h4><p id="sdrs_pro_0014__en-us_topic_0184026189_p859161416717">When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.</p>
|
<div class="section" id="sdrs_pro_0014__en-us_topic_0184026189_section193971112578"><h4 class="sectiontitle">Selecting an AZ</h4><p id="sdrs_pro_0014__en-us_topic_0184026189_p859161416717">When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.</p>
|
||||||
<ul id="sdrs_pro_0014__en-us_topic_0184026189_ul157203571473"><li id="sdrs_pro_0014__en-us_topic_0184026189_li7720175710711">For high DR capability, deploy resources in different AZs within the same region.</li><li id="sdrs_pro_0014__en-us_topic_0184026189_li109763595719">For lower network latency, deploy resources in the same AZ.</li></ul>
|
<ul id="sdrs_pro_0014__en-us_topic_0184026189_ul157203571473"><li id="sdrs_pro_0014__en-us_topic_0184026189_li7720175710711">For high DR capability, deploy resources in different AZs within the same region.</li><li id="sdrs_pro_0014__en-us_topic_0184026189_li109763595719">For lower network latency, deploy resources in the same AZ.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_pro_0014__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="sdrs_pro_0014__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/en-us/endpoint/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
<div class="section" id="sdrs_pro_0014__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="sdrs_pro_0014__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<div>
|
<div>
|
||||||
|
|||||||
@ -59,7 +59,7 @@
|
|||||||
<td class="cellrowborder" valign="top" width="32.98989898989899%" headers="mcps1.3.1.2.4.1.3 "><p id="sdrs_ug_cts_0001__en-us_topic_0107462581_p1677115214261">failoverProtectionGroup</p>
|
<td class="cellrowborder" valign="top" width="32.98989898989899%" headers="mcps1.3.1.2.4.1.3 "><p id="sdrs_ug_cts_0001__en-us_topic_0107462581_p1677115214261">failoverProtectionGroup</p>
|
||||||
</td>
|
</td>
|
||||||
</tr>
|
</tr>
|
||||||
<tr id="sdrs_ug_cts_0001__en-us_topic_0107462581_row12512153102519"><td class="cellrowborder" valign="top" width="33.84848484848485%" headers="mcps1.3.1.2.4.1.1 "><p id="sdrs_ug_cts_0001__en-us_topic_0107462581_p1277125292618">Performing a planned failover</p>
|
<tr id="sdrs_ug_cts_0001__en-us_topic_0107462581_row12512153102519"><td class="cellrowborder" valign="top" width="33.84848484848485%" headers="mcps1.3.1.2.4.1.1 "><p id="sdrs_ug_cts_0001__en-us_topic_0107462581_p1277125292618">Reprotecting a protection group</p>
|
||||||
</td>
|
</td>
|
||||||
<td class="cellrowborder" valign="top" width="33.16161616161616%" headers="mcps1.3.1.2.4.1.2 "><p id="sdrs_ug_cts_0001__p15186830194620">protectionGroup</p>
|
<td class="cellrowborder" valign="top" width="33.16161616161616%" headers="mcps1.3.1.2.4.1.2 "><p id="sdrs_ug_cts_0001__p15186830194620">protectionGroup</p>
|
||||||
</td>
|
</td>
|
||||||
|
|||||||
@ -13,7 +13,7 @@
|
|||||||
</div></div>
|
</div></div>
|
||||||
</li><li id="sdrs_ug_dr_0001__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="sdrs_ug_dr_0001__en-us_topic_0122528555_li1685105125012">After you create a DR drill, modifications to the <strong id="sdrs_ug_dr_0001__b631513317332">Hostname</strong>, <strong id="sdrs_ug_dr_0001__b732310312335">Name</strong>, <strong id="sdrs_ug_dr_0001__b532393133313">Agency</strong>, <strong id="sdrs_ug_dr_0001__b1323931336">ECS Group</strong>, <strong id="sdrs_ug_dr_0001__b1032463113313">Security Group</strong>, <strong id="sdrs_ug_dr_0001__b20324193103316">Tags</strong>, and <strong id="sdrs_ug_dr_0001__b1132410312337">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="sdrs_ug_dr_0001__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>
|
</li><li id="sdrs_ug_dr_0001__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="sdrs_ug_dr_0001__en-us_topic_0122528555_li1685105125012">After you create a DR drill, modifications to the <strong id="sdrs_ug_dr_0001__b631513317332">Hostname</strong>, <strong id="sdrs_ug_dr_0001__b732310312335">Name</strong>, <strong id="sdrs_ug_dr_0001__b532393133313">Agency</strong>, <strong id="sdrs_ug_dr_0001__b1323931336">ECS Group</strong>, <strong id="sdrs_ug_dr_0001__b1032463113313">Security Group</strong>, <strong id="sdrs_ug_dr_0001__b20324193103316">Tags</strong>, and <strong id="sdrs_ug_dr_0001__b1132410312337">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="sdrs_ug_dr_0001__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>
|
||||||
<div class="section" id="sdrs_ug_dr_0001__en-us_topic_0122528555_section67593181295"><h4 class="sectiontitle">Prerequisites</h4><ul id="sdrs_ug_dr_0001__en-us_topic_0122528555_ul19475131019563"><li id="sdrs_ug_dr_0001__en-us_topic_0122528555_li0301715105613">The protection group is in the <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b1968765112219">Available</strong>, <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b068845116219">Protecting</strong>, <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b176882511827">Failover complete</strong>, <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b126891451122">Enabling protection failed</strong>, <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b1868955116210">Disabling protection failed</strong>, <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b86901351423">Planned failover failed</strong>, <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b12691551923">Re-enabling protection failed</strong>, or <strong id="sdrs_ug_dr_0001__en-us_topic_0170796126_b26918519210">Failover failed</strong> state.</li><li id="sdrs_ug_dr_0001__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 class="section" id="sdrs_ug_dr_0001__en-us_topic_0122528555_section67593181295"><h4 class="sectiontitle">Prerequisites</h4><ul id="sdrs_ug_dr_0001__en-us_topic_0122528555_ul19475131019563"><li id="sdrs_ug_dr_0001__en-us_topic_0122528555_li0301715105613">The protection group is in the <strong id="sdrs_ug_dr_0001__b251924114175">Available</strong>, <strong id="sdrs_ug_dr_0001__b552019410170">Protecting</strong>, <strong id="sdrs_ug_dr_0001__b12521114114172">Failover complete</strong>, <strong id="sdrs_ug_dr_0001__b11522114151710">Enabling protection failed</strong>, <strong id="sdrs_ug_dr_0001__b17523841171712">Disabling protection failed</strong>, <strong id="sdrs_ug_dr_0001__b6524124111177">Switchover failed</strong>, <strong id="sdrs_ug_dr_0001__b185242410176">Re-enabling protection failed</strong>, or <strong id="sdrs_ug_dr_0001__b1952584171710">Failover failed</strong> state.</li><li id="sdrs_ug_dr_0001__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>
|
||||||
<div class="section" id="sdrs_ug_dr_0001__en-us_topic_0122528555_section37751719193414"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_dr_0001__en-us_topic_0122528555_ol2989153814717"><li id="sdrs_ug_dr_0001__en-us_topic_0122528555_li9223419142715"><span>Log in to the management console.</span></li><li id="sdrs_ug_dr_0001__en-us_topic_0122528555_li12972105114527"><span>Click <strong id="sdrs_ug_dr_0001__b77131056175513">Service List</strong> and choose <strong id="sdrs_ug_dr_0001__b572311564559">Storage</strong> > <strong id="sdrs_ug_dr_0001__b1772313567555">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_dr_0001__en-us_topic_0122528555_en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_dr_0001__b17315111341">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
<div class="section" id="sdrs_ug_dr_0001__en-us_topic_0122528555_section37751719193414"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_dr_0001__en-us_topic_0122528555_ol2989153814717"><li id="sdrs_ug_dr_0001__en-us_topic_0122528555_li9223419142715"><span>Log in to the management console.</span></li><li id="sdrs_ug_dr_0001__en-us_topic_0122528555_li12972105114527"><span>Click <strong id="sdrs_ug_dr_0001__b77131056175513">Service List</strong> and choose <strong id="sdrs_ug_dr_0001__b572311564559">Storage</strong> > <strong id="sdrs_ug_dr_0001__b1772313567555">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_dr_0001__en-us_topic_0122528555_en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_dr_0001__b17315111341">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||||
</p></li><li id="sdrs_ug_dr_0001__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="sdrs_ug_dr_0001__en-us_topic_0170796126_b84235270611125">DR Drills</strong>.</span><p><p id="sdrs_ug_dr_0001__en-us_topic_0122528555_p18473824191114">The operation page for the protection group is displayed.</p>
|
</p></li><li id="sdrs_ug_dr_0001__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="sdrs_ug_dr_0001__en-us_topic_0170796126_b84235270611125">DR Drills</strong>.</span><p><p id="sdrs_ug_dr_0001__en-us_topic_0122528555_p18473824191114">The operation page for the protection group is displayed.</p>
|
||||||
|
|||||||
@ -6,7 +6,7 @@
|
|||||||
<ul class="ullinks">
|
<ul class="ullinks">
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_ug_pg_0001.html">Disabling Protection</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_ug_pg_0001.html">Disabling Protection</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="sdrs_ug_pg_0002.html">Performing a Planned Failover</a></strong><br>
|
<li class="ulchildlink"><strong><a href="sdrs_ug_pg_0002.html">Performing a Switchover</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
<li class="ulchildlink"><strong><a href="en-us_topic_0108560208.html">Performing a Failover</a></strong><br>
|
<li class="ulchildlink"><strong><a href="en-us_topic_0108560208.html">Performing a Failover</a></strong><br>
|
||||||
</li>
|
</li>
|
||||||
|
|||||||
@ -1,9 +1,9 @@
|
|||||||
<a name="sdrs_ug_pg_0002"></a><a name="sdrs_ug_pg_0002"></a>
|
<a name="sdrs_ug_pg_0002"></a><a name="sdrs_ug_pg_0002"></a>
|
||||||
|
|
||||||
<h1 class="topictitle1">Performing a Planned Failover</h1>
|
<h1 class="topictitle1">Performing a Switchover</h1>
|
||||||
<div id="body1524550430906"><div class="section" id="sdrs_ug_pg_0002__section15531549458"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_pg_0002__p323210143285">After you perform a planned failover, services at the production site are failed over to the DR site, and services at the DR site are failed over to the production site. <a href="#sdrs_ug_pg_0002__table938371263712">Table 1</a> shows the direction change.</p>
|
<div id="body1524550430906"><div class="section" id="sdrs_ug_pg_0002__section15531549458"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_pg_0002__p323210143285">After you perform a switchover, services at the production site are switched to the DR site, and services at the DR site are switched over to the production site. <a href="#sdrs_ug_pg_0002__table938371263712">Table 1</a> shows the direction change.</p>
|
||||||
|
|
||||||
<div class="tablenoborder"><a name="sdrs_ug_pg_0002__table938371263712"></a><a name="table938371263712"></a><table cellpadding="4" cellspacing="0" summary="" id="sdrs_ug_pg_0002__table938371263712" frame="border" border="1" rules="all"><caption><b>Table 1 </b>DR direction change after a planned failover</caption><thead align="left"><tr id="sdrs_ug_pg_0002__row12384181223713"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.1.3.2.4.1.1"><p id="sdrs_ug_pg_0002__p12385121203719">-</p>
|
<div class="tablenoborder"><a name="sdrs_ug_pg_0002__table938371263712"></a><a name="table938371263712"></a><table cellpadding="4" cellspacing="0" summary="" id="sdrs_ug_pg_0002__table938371263712" frame="border" border="1" rules="all"><caption><b>Table 1 </b>DR direction change after a switchover</caption><thead align="left"><tr id="sdrs_ug_pg_0002__row12384181223713"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.1.3.2.4.1.1"><p id="sdrs_ug_pg_0002__p12385121203719">-</p>
|
||||||
</th>
|
</th>
|
||||||
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.1.3.2.4.1.2"><p id="sdrs_ug_pg_0002__p9385191216378">Production Site</p>
|
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.1.3.2.4.1.2"><p id="sdrs_ug_pg_0002__p9385191216378">Production Site</p>
|
||||||
</th>
|
</th>
|
||||||
@ -28,20 +28,20 @@
|
|||||||
</tbody>
|
</tbody>
|
||||||
</table>
|
</table>
|
||||||
</div>
|
</div>
|
||||||
<p id="sdrs_ug_pg_0002__p727911372284">After the planned failover, data synchronization continues, but the DR direction is changed (from the DR site to the production site). You can perform a planned failover when you are certain that the production site will encounter an interruption. For example, if the production site (AZ1) is going to encounter a power failure, you can perform a planned failover to fail over services in AZ1 to the DR site (AZ2). The planned failover will not affect data synchronization of the protection group.</p>
|
<p id="sdrs_ug_pg_0002__p727911372284">After the switchover, data synchronization continues, but the DR direction is changed from the DR site to the production site. You can perform a switchover when you are certain that the production site will encounter an interruption. For example, if the production site (AZ1) is going to encounter a power failure, you can perform a switchover to switch services in AZ1 to the DR site (AZ2). The switchover does not affect data synchronization of the protection group.</p>
|
||||||
<p id="sdrs_ug_pg_0002__p19391104613203">SDRS will migrate NICs on the server during the planned failover. After the planned 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>
|
<p id="sdrs_ug_pg_0002__p19391104613203">SDRS will migrate NICs on the server during the switchover. Once completed, 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="sdrs_ug_pg_0002__note74071714111919"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sdrs_ug_pg_0002__ul7746144015512"><li id="sdrs_ug_pg_0002__li0303155516359">Check the status to ensure that all the servers in the protection group are stopped before the planned failover. </li><li id="sdrs_ug_pg_0002__li0859285174">During the planned failover, do not start the servers in the protection group. Otherwise, the planned failover may fail.</li><li id="sdrs_ug_pg_0002__li6746134012518">Once a planned failover is complete, data synchronization will not stop, only the synchronization direction will reverse.</li><li id="sdrs_ug_pg_0002__li874634016512">After the planned failover is complete, the status of the protection group changes to <strong id="sdrs_ug_pg_0002__b18841612101914">Protecting</strong>. Then, you need to switch to the protected instance details page and start the production site server.</li></ul>
|
<div class="note" id="sdrs_ug_pg_0002__note74071714111919"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sdrs_ug_pg_0002__ul7746144015512"><li id="sdrs_ug_pg_0002__li0303155516359">Check the status to ensure that all the servers in the protection group are stopped before a switchover.</li><li id="sdrs_ug_pg_0002__li0859285174">During a switchover, do not start the servers in the protection group. Or, the switchover may fail.</li><li id="sdrs_ug_pg_0002__li6746134012518">Once a switchover is complete, data synchronization will not stop, only the synchronization direction will reverse.</li><li id="sdrs_ug_pg_0002__li874634016512">Once a switchover is complete, the status of the protection group changes to <strong id="sdrs_ug_pg_0002__b3379154814518">Protecting</strong>. Then, you need to go to the protected instance details page and start the production site server.</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
<div class="fignone" id="sdrs_ug_pg_0002__fig17126650144717"><span class="figcap"><b>Figure 1 </b>Performing a planned failover</span><br><span><img class="vsd" id="sdrs_ug_pg_0002__image11127550144718" src="en-us_image_0288665337.png"></span></div>
|
<div class="fignone" id="sdrs_ug_pg_0002__fig17126650144717"><span class="figcap"><b>Figure 1 </b>Performing a switchover</span><br><span><img class="vsd" id="sdrs_ug_pg_0002__image11127550144718" src="en-us_image_0288665337.png"></span></div>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_pg_0002__section8684144414202"><h4 class="sectiontitle">Notes</h4><p id="sdrs_ug_pg_0002__p368336151313">For Linux servers with Cloud-Init installed, if you have changed <strong id="sdrs_ug_pg_0002__b1631815576407">hostname</strong> of the production site server before you perform a planned failover for the first time, this modification will not synchronize to the DR site server.</p>
|
<div class="section" id="sdrs_ug_pg_0002__section8684144414202"><h4 class="sectiontitle">Notes</h4><p id="sdrs_ug_pg_0002__p368336151313">For Linux servers with Cloud-Init installed, if you have changed <strong id="sdrs_ug_pg_0002__b99054141169">hostname</strong> of the production site server before you perform a switchover for the first time, this modification will not synchronize to the DR site server.</p>
|
||||||
<p id="sdrs_ug_pg_0002__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>
|
<p id="sdrs_ug_pg_0002__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 Switchover or Failover?</a></p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_pg_0002__section142217284496"><h4 class="sectiontitle">Prerequisites</h4><ul id="sdrs_ug_pg_0002__ul7239352565"><li id="sdrs_ug_pg_0002__li8328647185010">All the servers in the protection group are stopped.</li><li id="sdrs_ug_pg_0002__li201322342517">The protection group has replication pairs.</li><li id="sdrs_ug_pg_0002__li888614872415">Protection is enabled for the protection group, and the protection group is in the <strong id="sdrs_ug_pg_0002__b84235270615147">Protecting</strong> or <strong id="sdrs_ug_pg_0002__b12578699477">Planned failover failed</strong> state.</li></ul>
|
<div class="section" id="sdrs_ug_pg_0002__section142217284496"><h4 class="sectiontitle">Prerequisites</h4><ul id="sdrs_ug_pg_0002__ul7239352565"><li id="sdrs_ug_pg_0002__li8328647185010">All the servers in the protection group are stopped.</li><li id="sdrs_ug_pg_0002__li201322342517">The protection group has replication pairs.</li><li id="sdrs_ug_pg_0002__li888614872415">Protection is enabled for the protection group, and the protection group is in the <strong id="sdrs_ug_pg_0002__b3242174212614">Protecting</strong> or <strong id="sdrs_ug_pg_0002__b724394213613">Switchover failed</strong> state.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_pg_0002__section10857512011"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_pg_0002__ol1740114773111"><li id="sdrs_ug_pg_0002__li109831058719"><span>Log in to the management console.</span></li><li id="sdrs_ug_pg_0002__li12972105114527"><span>Click <strong id="sdrs_ug_pg_0002__b166117273527">Service List</strong> and choose <strong id="sdrs_ug_pg_0002__b171172785215">Storage</strong> > <strong id="sdrs_ug_pg_0002__b12721527155214">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_pg_0002__en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_pg_0002__b118631640192818">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
<div class="section" id="sdrs_ug_pg_0002__section10857512011"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_pg_0002__ol1740114773111"><li id="sdrs_ug_pg_0002__li109831058719"><span>Log in to the management console.</span></li><li id="sdrs_ug_pg_0002__li12972105114527"><span>Click <strong id="sdrs_ug_pg_0002__b166117273527">Service List</strong> and choose <strong id="sdrs_ug_pg_0002__b171172785215">Storage</strong> > <strong id="sdrs_ug_pg_0002__b12721527155214">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_pg_0002__en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_pg_0002__b118631640192818">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||||
</p></li><li id="sdrs_ug_pg_0002__li149975244444"><span>In the pane of the desired protection group, click <strong id="sdrs_ug_pg_0002__b842352706171955">Protected Instances</strong>. </span></li><li id="sdrs_ug_pg_0002__li84211239334"><span>On the operation page of the protection group, click <strong id="sdrs_ug_pg_0002__b84235270610232">Execute Planned Failover</strong> in the upper right corner.</span></li><li id="sdrs_ug_pg_0002__li1063715212408"><span>In the displayed dialog box, check whether all the servers in this protection group are stopped.</span><p><ul id="sdrs_ug_pg_0002__ul19491640560"><li id="sdrs_ug_pg_0002__li134911445565">If yes, go to step <a href="#sdrs_ug_pg_0002__li812255515532">6</a>.</li><li id="sdrs_ug_pg_0002__li16097406564">If no, select the servers to be stopped and click <strong id="sdrs_ug_pg_0002__b624410553336">Stop</strong>.</li></ul>
|
</p></li><li id="sdrs_ug_pg_0002__li149975244444"><span>In the pane of the desired protection group, click <strong id="sdrs_ug_pg_0002__b842352706171955">Protected Instances</strong>. </span></li><li id="sdrs_ug_pg_0002__li84211239334"><span>In the upper right corner of the page, click <strong id="sdrs_ug_pg_0002__b112021239132">Execute Switchover</strong>.</span></li><li id="sdrs_ug_pg_0002__li1063715212408"><span>In the displayed dialog box, check whether all the servers in this protection group are stopped.</span><p><ul id="sdrs_ug_pg_0002__ul19491640560"><li id="sdrs_ug_pg_0002__li134911445565">If yes, go to step <a href="#sdrs_ug_pg_0002__li812255515532">6</a>.</li><li id="sdrs_ug_pg_0002__li16097406564">If no, select the servers to be stopped and click <strong id="sdrs_ug_pg_0002__b624410553336">Stop</strong>.</li></ul>
|
||||||
</p></li><li id="sdrs_ug_pg_0002__li812255515532"><a name="sdrs_ug_pg_0002__li812255515532"></a><a name="li812255515532"></a><span>In the <strong id="sdrs_ug_pg_0002__b842352706103224">Execute Planned Failover</strong> dialog box, click <strong id="sdrs_ug_pg_0002__b842352706103257">Execute Planned Failover</strong>.</span><p><div class="note" id="sdrs_ug_pg_0002__note1648581784018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="sdrs_ug_pg_0002__p1048718175402">During the planned failover, do not start the servers in the protection group. Otherwise, the planned failover may fail.</p>
|
</p></li><li id="sdrs_ug_pg_0002__li812255515532"><a name="sdrs_ug_pg_0002__li812255515532"></a><a name="li812255515532"></a><span>In the displayed dialog box, click <strong id="sdrs_ug_pg_0002__b74776831318">Execute Switchover</strong>.</span><p><div class="note" id="sdrs_ug_pg_0002__note1648581784018"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="sdrs_ug_pg_0002__p1048718175402">During a switchover, do not start the servers in the protection group. Or, the switchover may fail.</p>
|
||||||
</div></div>
|
</div></div>
|
||||||
</p></li></ol>
|
</p></li></ol>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
@ -1,43 +1,16 @@
|
|||||||
|
<a name="sdrs_ug_pi_0002"></a><a name="sdrs_ug_pi_0002"></a>
|
||||||
<!DOCTYPE html
|
|
||||||
PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
|
||||||
<html lang="en-us" xml:lang="en-us">
|
|
||||||
<head>
|
|
||||||
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
||||||
|
|
||||||
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
|
||||||
<meta name="DC.Type" content="topic">
|
|
||||||
<meta name="DC.Title" content="Deleting a Protected Instance">
|
|
||||||
<meta name="product" content="">
|
|
||||||
<meta name="DC.Relation" scheme="URI" content="sdrs_ug_pi_0000.html">
|
|
||||||
<meta name="prodname" content="">
|
|
||||||
<meta name="version" content="">
|
|
||||||
<meta name="brand" content="Storage Disaster Recovery Service">
|
|
||||||
<meta name="DC.Publisher" content="20241026">
|
|
||||||
<meta name="prodname" content="sdrs">
|
|
||||||
<meta name="documenttype" content="usermanual">
|
|
||||||
<meta name="IsMulti" content="Yes">
|
|
||||||
<meta name="IsBot" content="Yes">
|
|
||||||
<meta name="opensource" content="true">
|
|
||||||
<meta name="DC.Format" content="XHTML">
|
|
||||||
<meta name="DC.Identifier" content="sdrs_ug_pi_0002">
|
|
||||||
<meta name="DC.Language" content="en-us">
|
|
||||||
<link rel="stylesheet" type="text/css" href="public_sys-resources/commonltr.css">
|
|
||||||
<title>Deleting a Protected Instance</title>
|
|
||||||
</head>
|
|
||||||
<body style="clear:both; padding-left:10px; padding-top:5px; padding-right:5px; padding-bottom:5px"><a name="sdrs_ug_pi_0002"></a><a name="sdrs_ug_pi_0002"></a>
|
|
||||||
|
|
||||||
<h1 class="topictitle1">Deleting a Protected Instance</h1>
|
<h1 class="topictitle1">Deleting a Protected Instance</h1>
|
||||||
<div id="body1525684597644"><div class="section" id="sdrs_ug_pi_0002__section11558347360"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_pi_0002__p1912642712232">If you do not need a protected instance, delete it to cancel the protection relationship between the servers and the protection group.</p>
|
<div id="body1525684597644"><div class="section" id="sdrs_ug_pi_0002__section11558347360"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_pi_0002__p1912642712232">If you do not need a protected instance, you can delete it to cancel the protection relationship between the servers and the protection group.</p>
|
||||||
<p id="sdrs_ug_pi_0002__p1165622918188">When you delete a protected instance, the production site server in the protected instance will not be deleted, and services at the production site will not be affected.</p>
|
<p id="sdrs_ug_pi_0002__p1165622918188">When you delete a protected instance, the production site server in the protected instance will not be deleted, and services at the production site will not be affected.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_pi_0002__section1815764912368"><h4 class="sectiontitle">Prerequisites</h4><p id="sdrs_ug_pi_0002__p9100156205717">The protected instance is in the <strong id="sdrs_ug_pi_0002__b18774113171416">Available</strong>, <strong id="sdrs_ug_pi_0002__b2077893118149">Protecting</strong>, <strong id="sdrs_ug_pi_0002__b1077953161413">Failover complete</strong>, <strong id="sdrs_ug_pi_0002__b1578019315142">Creation failed</strong>, <strong id="sdrs_ug_pi_0002__b8780153131417">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0002__b1478123113145">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0002__b1782113131410">Switchover failed</strong>, <strong id="sdrs_ug_pi_0002__b9783531111410">Failover failed</strong>, <strong id="sdrs_ug_pi_0002__b10784193117144">Deletion failed</strong>, <strong id="sdrs_ug_pi_0002__b578513171416">Re-enabling protection failed</strong>, <strong id="sdrs_ug_pi_0002__b078616311148">Modifying specifications failed</strong>, <strong id="sdrs_ug_pi_0002__b19787103161419">Invalid</strong>, or <strong id="sdrs_ug_pi_0002__b1678819317141">Faulty</strong> state.</p>
|
<div class="section" id="sdrs_ug_pi_0002__section1815764912368"><h4 class="sectiontitle"><strong id="sdrs_ug_pi_0002__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><p id="sdrs_ug_pi_0002__p9100156205717">The protected instance is in the <strong id="sdrs_ug_pi_0002__b12363134411618">Available</strong>, <strong id="sdrs_ug_pi_0002__b15365194411167">Protecting</strong>, <strong id="sdrs_ug_pi_0002__b1636574491617">Failover complete</strong>, <strong id="sdrs_ug_pi_0002__b10366144414169">Creation failed</strong>, <strong id="sdrs_ug_pi_0002__b183661447166">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0002__b1536716443166">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0002__b536716447166">Switchover failed</strong>, <strong id="sdrs_ug_pi_0002__b17368104441618">Failover failed</strong>, <strong id="sdrs_ug_pi_0002__b7368194461610">Deletion failed</strong>, <strong id="sdrs_ug_pi_0002__b7369204413161">Re-enabling protection failed</strong>, <strong id="sdrs_ug_pi_0002__b193691644131612">Modifying specifications failed</strong>, <strong id="sdrs_ug_pi_0002__b1437074416163">Invalid</strong>, or <strong id="sdrs_ug_pi_0002__b937034416162">Faulty</strong> state.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_pi_0002__section686414381417"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_pi_0002__ol169412094217"><li id="sdrs_ug_pi_0002__li109831058719"><span>Log in to the management console.</span></li><li id="sdrs_ug_pi_0002__li12972105114527"><span>Click <strong id="sdrs_ug_pi_0002__en-us_topic_0108180805_b17945113171413">Service List</strong> and choose <strong id="sdrs_ug_pi_0002__en-us_topic_0108180805_b1590754116342">Storage</strong> > <strong id="sdrs_ug_pi_0002__en-us_topic_0108180805_b149086418342">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_pi_0002__en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_pi_0002__en-us_topic_0108180805_b161375626">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
<div class="section" id="sdrs_ug_pi_0002__section686414381417"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_pi_0002__ol169412094217"><li id="sdrs_ug_pi_0002__li109831058719"><span>Log in to the management console.</span></li><li id="sdrs_ug_pi_0002__li12972105114527"><span>Click <strong id="sdrs_ug_pi_0002__b1056034875317">Service List</strong> and choose <strong id="sdrs_ug_pi_0002__b1757284819536">Storage</strong> > <strong id="sdrs_ug_pi_0002__b10573154875314">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_pi_0002__en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_pi_0002__b1888519474354">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||||
</p></li><li id="sdrs_ug_pi_0002__li18696809428"><span>In the pane of the protection group for which the protected instance is to be deleted, click <strong id="sdrs_ug_pi_0002__b84235270611125">Protected Instances</strong>.</span><p><p id="sdrs_ug_pi_0002__p969714014218">The protection group details page is displayed.</p>
|
</p></li><li id="sdrs_ug_pi_0002__li18696809428"><span>In the pane of the protection group for which the protected instance is to be deleted, click <strong id="sdrs_ug_pi_0002__b84235270611125">Protected Instances</strong>.</span><p><p id="sdrs_ug_pi_0002__p969714014218">The operation page for the protection group is displayed.</p>
|
||||||
</p></li><li id="sdrs_ug_pi_0002__li76971707429"><span>On the <strong id="sdrs_ug_pi_0002__b842352706114358">Protected Instances</strong> tab, locate the row containing the protected instance to be deleted, click <strong id="sdrs_ug_pi_0002__b842352706143139">More</strong> in the <strong id="sdrs_ug_pi_0002__b842352706115353">Operation</strong> column, and choose <strong id="sdrs_ug_pi_0002__b842352706143211">Delete</strong> from the drop-down list.</span><p><p id="sdrs_ug_pi_0002__p04731142131011">To delete protected instances in batches, select the target protected instances and click <strong id="sdrs_ug_pi_0002__b19816181515423">Delete</strong> above the protected instance list.</p>
|
</p></li><li id="sdrs_ug_pi_0002__li76971707429"><span>On the <strong id="sdrs_ug_pi_0002__b842352706114358">Protected Instances</strong> tab, locate the row containing the protected instance to be deleted, click <strong id="sdrs_ug_pi_0002__b842352706143139">More</strong> in the <strong id="sdrs_ug_pi_0002__b842352706115353">Operation</strong> column, and choose <strong id="sdrs_ug_pi_0002__b842352706143211">Delete</strong> from the drop-down list.</span><p><p id="sdrs_ug_pi_0002__p04731142131011">To delete protected instances in batches, select the target protected instances and click <strong id="sdrs_ug_pi_0002__b19816181515423">Delete</strong> above the protected instance list.</p>
|
||||||
<p id="sdrs_ug_pi_0002__p1630418102">The <strong id="sdrs_ug_pi_0002__b842352706164031">Delete Protected Instance</strong> page is displayed.</p>
|
<p id="sdrs_ug_pi_0002__p1630418102">The <strong id="sdrs_ug_pi_0002__b842352706164031">Delete Protected Instance</strong> page is displayed.</p>
|
||||||
<div class="fignone" id="sdrs_ug_pi_0002__fig1963154181010"><span class="figcap"><b>Figure 1 </b>Deleting a protected instance</span><br><span><img id="sdrs_ug_pi_0002__image12631541191015" src="en-us_image_0155735363.png"></span></div>
|
<div class="fignone" id="sdrs_ug_pi_0002__fig1963154181010"><span class="figcap"><b>Figure 1 </b>Deleting a protected instance</span><br><span><img id="sdrs_ug_pi_0002__image12631541191015" src="en-us_image_0288665372.png"></span></div>
|
||||||
</p></li><li id="sdrs_ug_pi_0002__li16980013429"><span>On the <strong id="sdrs_ug_pi_0002__b92267596812950">Delete Protected Instance</strong> page, select the desired operation.</span><p><div class="note" id="sdrs_ug_pi_0002__note81231613121914"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sdrs_ug_pi_0002__ul38176812219"><li id="sdrs_ug_pi_0002__li2817168102214">If you select <strong id="sdrs_ug_pi_0002__b11564125511138">Delete DR site server</strong>, do not perform any other operations on the DR site server or its related resources when the system is deleting the DR site server.</li></ul>
|
</p></li><li id="sdrs_ug_pi_0002__li16980013429"><span>On the <strong id="sdrs_ug_pi_0002__b92267596812950">Delete Protected Instance</strong> page, select the desired operation.</span><p><div class="note" id="sdrs_ug_pi_0002__note81231613121914"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sdrs_ug_pi_0002__ul38176812219"><li id="sdrs_ug_pi_0002__li2817168102214">If you select <strong id="sdrs_ug_pi_0002__b11564125511138">Delete DR site server</strong>, do not perform any other operations on the DR site server or its related resources when the system is deleting the DR site server.</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
<ul id="sdrs_ug_pi_0002__ul129403333199"><li id="sdrs_ug_pi_0002__li179401133181912">Delete DR site server<ul id="sdrs_ug_pi_0002__ul149681482014"><li id="sdrs_ug_pi_0002__li159511145203">If you do not select this option, the protection relationship between the protected instance and protection group will be canceled, but the DR site server and disks attached to the server will be retained.</li><li id="sdrs_ug_pi_0002__li19611419208">If you select this option, the protection relationship between the protected instance and protection group will be canceled, and the DR site server and disks attached to the server will be deleted.</li></ul>
|
<ul id="sdrs_ug_pi_0002__ul129403333199"><li id="sdrs_ug_pi_0002__li179401133181912">Delete DR site server<ul id="sdrs_ug_pi_0002__ul149681482014"><li id="sdrs_ug_pi_0002__li159511145203">If you do not select this option, the protection relationship between the protected instance and protection group will be canceled, but the DR site server and disks attached to the server will be retained.</li><li id="sdrs_ug_pi_0002__li19611419208">If you select this option, the protection relationship between the protected instance and protection group will be canceled, and the DR site server and disks attached to the server will be deleted.</li></ul>
|
||||||
@ -53,5 +26,4 @@
|
|||||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_ug_pi_0000.html">Managing Protected Instances</a></div>
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="sdrs_ug_pi_0000.html">Managing Protected Instances</a></div>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
</body>
|
|
||||||
</html>
|
|
||||||
|
|||||||
@ -3,7 +3,7 @@
|
|||||||
<h1 class="topictitle1">Detaching a Replication Pair</h1>
|
<h1 class="topictitle1">Detaching a Replication Pair</h1>
|
||||||
<div id="body1525684597644"><div class="section" id="sdrs_ug_pi_0005__section11716195481510"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_pi_0005__p8746152134420">You can perform steps provided in this section to detach a replication pair from a protected instance. Then, data of the servers in the protected instance will not be written in to the disks in the replication pair.</p>
|
<div id="body1525684597644"><div class="section" id="sdrs_ug_pi_0005__section11716195481510"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_pi_0005__p8746152134420">You can perform steps provided in this section to detach a replication pair from a protected instance. Then, data of the servers in the protected instance will not be written in to the disks in the replication pair.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_pi_0005__section189551041174318"><h4 class="sectiontitle"><strong id="sdrs_ug_pi_0005__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="sdrs_ug_pi_0005__ul19615623376"><li id="sdrs_ug_pi_0005__li4950155564520">The protection group is in the <strong id="sdrs_ug_pi_0005__b2500777182">Available</strong>, <strong id="sdrs_ug_pi_0005__b5576171271812">Protecting</strong>, <strong id="sdrs_ug_pi_0005__b481816111814">Failover complete</strong>, <strong id="sdrs_ug_pi_0005__b7460141910187">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b1086112341812">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b11866132192">Planned failover failed</strong>, or <strong id="sdrs_ug_pi_0005__b8778141661911">Failover failed</strong> state.</li><li id="sdrs_ug_pi_0005__li98913488586">The protected instance is in the <strong id="sdrs_ug_pi_0005__b3984123031910">Available</strong>, <strong id="sdrs_ug_pi_0005__b1798473071920">Protecting</strong>, <strong id="sdrs_ug_pi_0005__b1298417301190">Failover complete</strong>, <strong id="sdrs_ug_pi_0005__b698593081912">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b11985730141913">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b998513013194">Planned failover failed</strong>, <strong id="sdrs_ug_pi_0005__b3985173091912">Failover failed</strong>, <strong id="sdrs_ug_pi_0005__b1334912582010">Deletion failed</strong>, <strong id="sdrs_ug_pi_0005__b8262142042020">Re-enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b1862113512202">Modifying specifications failed</strong>, <strong id="sdrs_ug_pi_0005__b83669516201">Invalid</strong>, or <strong id="sdrs_ug_pi_0005__b125511753112013">Faulty</strong> state.</li><li id="sdrs_ug_pi_0005__li18501415175918">The replication pair is in the <strong id="sdrs_ug_pi_0005__b19892131682112">Available</strong>, <strong id="sdrs_ug_pi_0005__b1190001632118">Protecting</strong>, <strong id="sdrs_ug_pi_0005__b3747115732214">Failover complete</strong>, <strong id="sdrs_ug_pi_0005__b83821141361">Attaching failed</strong>, <strong id="sdrs_ug_pi_0005__b1235211311239">Detaching failed</strong>, <strong id="sdrs_ug_pi_0005__b13105326256">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b692924412916">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b972245072912">Planned failover failed</strong>, <strong id="sdrs_ug_pi_0005__b7105135672911">Failover failed</strong>, <strong id="sdrs_ug_pi_0005__b1385785962917">Deletion failed</strong>, <strong id="sdrs_ug_pi_0005__b101601418303">Re-enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b95351194307">Expansion failed</strong>, <strong id="sdrs_ug_pi_0005__b182374125307">Invalid</strong>, or <strong id="sdrs_ug_pi_0005__b8843114113015">Faulty</strong> state.</li><li id="sdrs_ug_pi_0005__li197845754710">The replication pair has been attached to a protected instance.</li><li id="sdrs_ug_pi_0005__li206983019444">Disks in the <strong id="sdrs_ug_pi_0005__b84235270694628">In-use</strong> state have been attached to the production and DR site servers.</li></ul>
|
<div class="section" id="sdrs_ug_pi_0005__section189551041174318"><h4 class="sectiontitle"><strong id="sdrs_ug_pi_0005__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="sdrs_ug_pi_0005__ul19615623376"><li id="sdrs_ug_pi_0005__li4950155564520">The protection group is in the <strong id="sdrs_ug_pi_0005__b17671253161616">Available</strong>, <strong id="sdrs_ug_pi_0005__b1167165320166">Protecting</strong>, <strong id="sdrs_ug_pi_0005__b467295310165">Failover complete</strong>, <strong id="sdrs_ug_pi_0005__b126721253151617">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b4673753151610">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b167395311165">Switchover failed</strong>, or <strong id="sdrs_ug_pi_0005__b1667315536165">Failover failed</strong> state.</li><li id="sdrs_ug_pi_0005__li98913488586">The protected instance is in the <strong id="sdrs_ug_pi_0005__b3558111141717">Available</strong>, <strong id="sdrs_ug_pi_0005__b12559814179">Protecting</strong>, <strong id="sdrs_ug_pi_0005__b75605161716">Failover complete</strong>, <strong id="sdrs_ug_pi_0005__b15611719171">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b9561131131712">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b356271121718">Switchover failed</strong>, <strong id="sdrs_ug_pi_0005__b856361181710">Failover failed</strong>, <strong id="sdrs_ug_pi_0005__b1756411181718">Deletion failed</strong>, <strong id="sdrs_ug_pi_0005__b13565171111713">Re-enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b2056610111714">Modifying specifications failed</strong>, <strong id="sdrs_ug_pi_0005__b1756614151714">Invalid</strong>, or <strong id="sdrs_ug_pi_0005__b15671714178">Faulty</strong> state.</li><li id="sdrs_ug_pi_0005__li18501415175918">The replication pair is in the <strong id="sdrs_ug_pi_0005__b204871384172">Available</strong>, <strong id="sdrs_ug_pi_0005__b54887814179">Protecting</strong>, <strong id="sdrs_ug_pi_0005__b5490386174">Failover complete</strong>, <strong id="sdrs_ug_pi_0005__b74911181173">Attaching failed</strong>, <strong id="sdrs_ug_pi_0005__b549238141718">Detaching failed</strong>, <strong id="sdrs_ug_pi_0005__b134936841713">Enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b164945831715">Disabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b174945851714">Switchover failed</strong>, <strong id="sdrs_ug_pi_0005__b11495208151720">Failover failed</strong>, <strong id="sdrs_ug_pi_0005__b64961483170">Deletion failed</strong>, <strong id="sdrs_ug_pi_0005__b1649711871715">Re-enabling protection failed</strong>, <strong id="sdrs_ug_pi_0005__b2498083176">Expansion failed</strong>, <strong id="sdrs_ug_pi_0005__b2499138151713">Invalid</strong>, or <strong id="sdrs_ug_pi_0005__b65014820179">Faulty</strong> state.</li><li id="sdrs_ug_pi_0005__li197845754710">The replication pair has been attached to a protected instance.</li><li id="sdrs_ug_pi_0005__li206983019444">Disks in the <strong id="sdrs_ug_pi_0005__b84235270694628">In-use</strong> state have been attached to the production and DR site servers.</li></ul>
|
||||||
<div class="note" id="sdrs_ug_pi_0005__note1231513114615"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sdrs_ug_pi_0005__ul91584185320"><li id="sdrs_ug_pi_0005__li1415194117534">A system disk (mounted on the <strong id="sdrs_ug_pi_0005__b842352706204835">/dev/sda</strong> or <strong id="sdrs_ug_pi_0005__b84235270604012">/dev/vda</strong> mount point) can be detached from a <span id="sdrs_ug_pi_0005__text83591121152516">server</span><span id="sdrs_ug_pi_0005__text3345142432516"></span> only when the <span id="sdrs_ug_pi_0005__text2673204373117">server</span><span id="sdrs_ug_pi_0005__text1167564311314"></span> is in the <strong id="sdrs_ug_pi_0005__b84235270620485">Stopped</strong> state. Therefore, stop the <span id="sdrs_ug_pi_0005__text791564773120">server</span><span id="sdrs_ug_pi_0005__text2091813471314"></span> before detaching the system disk.</li><li id="sdrs_ug_pi_0005__li161515413535">A data disk can be detached from a <span id="sdrs_ug_pi_0005__text0498140103212">server</span><span id="sdrs_ug_pi_0005__text550094020324"></span> online or offline, specifically, when the <span id="sdrs_ug_pi_0005__text727964922711">server</span><span id="sdrs_ug_pi_0005__text3279134912714"></span> is in the <strong id="sdrs_ug_pi_0005__b842352706205021">Stopped</strong> or <strong id="sdrs_ug_pi_0005__b842352706205024">Running</strong> state. <p id="sdrs_ug_pi_0005__p171517412537">For details about how to detach a disk online, see <span class="menucascade" id="sdrs_ug_pi_0005__menucascade40704968493044"><b><span class="uicontrol" id="sdrs_ug_pi_0005__uicontrol23094277793053">Storage</span></b> > <b><span class="uicontrol" id="sdrs_ug_pi_0005__uicontrol36060107193056">Detaching an EVS Disk from a Running ECS</span></b></span> in the <em id="sdrs_ug_pi_0005__i84235269793020">Elastic Cloud Server User Guide</em>.</p>
|
<div class="note" id="sdrs_ug_pi_0005__note1231513114615"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="sdrs_ug_pi_0005__ul91584185320"><li id="sdrs_ug_pi_0005__li1415194117534">A system disk (mounted on the <strong id="sdrs_ug_pi_0005__b842352706204835">/dev/sda</strong> or <strong id="sdrs_ug_pi_0005__b84235270604012">/dev/vda</strong> mount point) can be detached from a <span id="sdrs_ug_pi_0005__text83591121152516">server</span><span id="sdrs_ug_pi_0005__text3345142432516"></span> only when the <span id="sdrs_ug_pi_0005__text2673204373117">server</span><span id="sdrs_ug_pi_0005__text1167564311314"></span> is in the <strong id="sdrs_ug_pi_0005__b84235270620485">Stopped</strong> state. Therefore, stop the <span id="sdrs_ug_pi_0005__text791564773120">server</span><span id="sdrs_ug_pi_0005__text2091813471314"></span> before detaching the system disk.</li><li id="sdrs_ug_pi_0005__li161515413535">A data disk can be detached from a <span id="sdrs_ug_pi_0005__text0498140103212">server</span><span id="sdrs_ug_pi_0005__text550094020324"></span> online or offline, specifically, when the <span id="sdrs_ug_pi_0005__text727964922711">server</span><span id="sdrs_ug_pi_0005__text3279134912714"></span> is in the <strong id="sdrs_ug_pi_0005__b842352706205021">Stopped</strong> or <strong id="sdrs_ug_pi_0005__b842352706205024">Running</strong> state. <p id="sdrs_ug_pi_0005__p171517412537">For details about how to detach a disk online, see <span class="menucascade" id="sdrs_ug_pi_0005__menucascade40704968493044"><b><span class="uicontrol" id="sdrs_ug_pi_0005__uicontrol23094277793053">Storage</span></b> > <b><span class="uicontrol" id="sdrs_ug_pi_0005__uicontrol36060107193056">Detaching an EVS Disk from a Running ECS</span></b></span> in the <em id="sdrs_ug_pi_0005__i84235269793020">Elastic Cloud Server User Guide</em>.</p>
|
||||||
</li></ul>
|
</li></ul>
|
||||||
</div></div>
|
</div></div>
|
||||||
|
|||||||
@ -14,11 +14,11 @@
|
|||||||
</p></li><li id="sdrs_ug_rp_0001__en-us_topic_0110037559_li1063715212408"><span>On the <strong id="sdrs_ug_rp_0001__b842352706105036">Replication Pairs</strong> tab, click <strong id="sdrs_ug_rp_0001__b84235270695047">Create Replication Pair</strong>.</span><p><p id="sdrs_ug_rp_0001__en-us_topic_0110037559_p3676113041218">The <strong id="sdrs_ug_rp_0001__b84235270693643">Create Replication Pair</strong> page is displayed.</p>
|
</p></li><li id="sdrs_ug_rp_0001__en-us_topic_0110037559_li1063715212408"><span>On the <strong id="sdrs_ug_rp_0001__b842352706105036">Replication Pairs</strong> tab, click <strong id="sdrs_ug_rp_0001__b84235270695047">Create Replication Pair</strong>.</span><p><p id="sdrs_ug_rp_0001__en-us_topic_0110037559_p3676113041218">The <strong id="sdrs_ug_rp_0001__b84235270693643">Create Replication Pair</strong> page is displayed.</p>
|
||||||
<div class="fignone" id="sdrs_ug_rp_0001__en-us_topic_0110037559_fig259912464915"><span class="figcap"><b>Figure 1 </b>Creating a replication pair</span><br><span><img id="sdrs_ug_rp_0001__en-us_topic_0110037559_image7334182173313" src="en-us_image_0288665399.png"></span></div>
|
<div class="fignone" id="sdrs_ug_rp_0001__en-us_topic_0110037559_fig259912464915"><span class="figcap"><b>Figure 1 </b>Creating a replication pair</span><br><span><img id="sdrs_ug_rp_0001__en-us_topic_0110037559_image7334182173313" src="en-us_image_0288665399.png"></span></div>
|
||||||
</p></li><li id="sdrs_ug_rp_0001__en-us_topic_0110037559_li74435623116"><span>Configure the basic information about the replication pair listed in <a href="#sdrs_ug_rp_0001__en-us_topic_0110037559_table14113172215131">Table 1</a>.</span><p>
|
</p></li><li id="sdrs_ug_rp_0001__en-us_topic_0110037559_li74435623116"><span>Configure the basic information about the replication pair listed in <a href="#sdrs_ug_rp_0001__en-us_topic_0110037559_table14113172215131">Table 1</a>.</span><p>
|
||||||
<div class="tablenoborder"><a name="sdrs_ug_rp_0001__en-us_topic_0110037559_table14113172215131"></a><a name="en-us_topic_0110037559_table14113172215131"></a><table cellpadding="4" cellspacing="0" summary="" id="sdrs_ug_rp_0001__en-us_topic_0110037559_table14113172215131" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="sdrs_ug_rp_0001__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="sdrs_ug_rp_0001__en-us_topic_0110037559_p111164221133"><strong id="sdrs_ug_rp_0001__b842352706211121">Parameter</strong></p>
|
<div class="tablenoborder"><a name="sdrs_ug_rp_0001__en-us_topic_0110037559_table14113172215131"></a><a name="en-us_topic_0110037559_table14113172215131"></a><table cellpadding="4" cellspacing="0" summary="" id="sdrs_ug_rp_0001__en-us_topic_0110037559_table14113172215131" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameter description</caption><thead align="left"><tr id="sdrs_ug_rp_0001__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="sdrs_ug_rp_0001__en-us_topic_0110037559_p111164221133">Parameter</p>
|
||||||
</th>
|
</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="sdrs_ug_rp_0001__en-us_topic_0110037559_p5116172261316"><strong id="sdrs_ug_rp_0001__b84235270611218">Description</strong></p>
|
<th align="left" class="cellrowborder" valign="top" width="51.93519351935193%" id="mcps1.3.3.2.5.2.1.2.4.1.2"><p id="sdrs_ug_rp_0001__en-us_topic_0110037559_p5116172261316">Description</p>
|
||||||
</th>
|
</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="sdrs_ug_rp_0001__en-us_topic_0110037559_p1211612224133"><strong>Example Value</strong></p>
|
<th align="left" class="cellrowborder" valign="top" width="22.84228422842284%" id="mcps1.3.3.2.5.2.1.2.4.1.3"><p id="sdrs_ug_rp_0001__en-us_topic_0110037559_p1211612224133">Example Value</p>
|
||||||
</th>
|
</th>
|
||||||
</tr>
|
</tr>
|
||||||
</thead>
|
</thead>
|
||||||
|
|||||||
@ -4,7 +4,7 @@
|
|||||||
<div id="body1525685782789"><div class="section" id="sdrs_ug_rp_0003__section17280141395413"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_rp_0003__p136491830163719">If a replication pair is no longer used, you can release the associated virtual resources by deleting the replication pair from the system.</p>
|
<div id="body1525685782789"><div class="section" id="sdrs_ug_rp_0003__section17280141395413"><h4 class="sectiontitle">Scenarios</h4><p id="sdrs_ug_rp_0003__p136491830163719">If a replication pair is no longer used, you can release the associated virtual resources by deleting the replication pair from the system.</p>
|
||||||
<p id="sdrs_ug_rp_0003__p1154563330">When you delete a replication pair, the production site disk in the replication pair will not be deleted. You can decide whether to delete the DR site disk.</p>
|
<p id="sdrs_ug_rp_0003__p1154563330">When you delete a replication pair, the production site disk in the replication pair will not be deleted. You can decide whether to delete the DR site disk.</p>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_rp_0003__section728071365418"><h4 class="sectiontitle"><strong id="sdrs_ug_rp_0003__en-us_topic_0040236005_en-us_topic_0035268496_b842352706102921">Prerequisites</strong></h4><ul id="sdrs_ug_rp_0003__ul1724511233343"><li id="sdrs_ug_rp_0003__li669919716445">The protection group is in the <strong id="sdrs_ug_rp_0003__b527573314217">Available</strong>, <strong id="sdrs_ug_rp_0003__b72761933204219">Protecting</strong>, <strong id="sdrs_ug_rp_0003__b15277173354213">Failover complete</strong>, <strong id="sdrs_ug_rp_0003__b14277193314219">Enabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b327823364216">Disabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b15279133312425">Planned failover failed</strong>, <strong id="sdrs_ug_rp_0003__b152831133154214">Failover failed</strong>, Deletion failed, or <strong id="sdrs_ug_rp_0003__b19637410114311">Re-enabling protection failed</strong> state.</li><li id="sdrs_ug_rp_0003__li169219341111">The replication pair is in the <strong id="sdrs_ug_rp_0003__b1847221474310">Available</strong>, <strong id="sdrs_ug_rp_0003__b14475121484310">Protecting</strong>, <strong id="sdrs_ug_rp_0003__b1477111416438">Failover complete</strong>, <strong id="sdrs_ug_rp_0003__b12677185715435">Creation failed</strong>, <strong id="sdrs_ug_rp_0003__b54811714184314">Enabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b17483161413437">Disabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b9485161474316">Planned failover failed</strong>, <strong id="sdrs_ug_rp_0003__b11486191484312">Failover failed</strong>, <strong id="sdrs_ug_rp_0003__b248841474318">Deletion failed</strong>, <strong id="sdrs_ug_rp_0003__b10489214144314">Re-enabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b0401733114411">Attaching failed</strong>, <strong id="sdrs_ug_rp_0003__b149151412435">Expansion failed</strong>, <strong id="sdrs_ug_rp_0003__b34939146438">Invalid</strong>, or <strong id="sdrs_ug_rp_0003__b6495914184313">Faulty</strong> state.</li><li id="sdrs_ug_rp_0003__li92452023183414">The replication pair is not attached to any protected instance. For details about how to detach a replication pair, see <a href="sdrs_ug_pi_0005.html">Detaching a Replication Pair</a>.</li></ul>
|
<div class="section" id="sdrs_ug_rp_0003__section728071365418"><h4 class="sectiontitle">Prerequisites</h4><ul id="sdrs_ug_rp_0003__ul1724511233343"><li id="sdrs_ug_rp_0003__li669919716445">The protection group is in the <strong id="sdrs_ug_rp_0003__b26211727161711">Available</strong>, <strong id="sdrs_ug_rp_0003__b4622112713179">Protecting</strong>, <strong id="sdrs_ug_rp_0003__b176225273175">Failover complete</strong>, <strong id="sdrs_ug_rp_0003__b12623027131710">Enabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b16241227191719">Disabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b15624112751712">Switchover failed</strong>, <strong id="sdrs_ug_rp_0003__b86251727181718">Failover failed</strong>, Deletion failed, or <strong id="sdrs_ug_rp_0003__b7626122711717">Re-enabling protection failed</strong> state.</li><li id="sdrs_ug_rp_0003__li169219341111">The replication pair is in the <strong id="sdrs_ug_rp_0003__b6529183212175">Available</strong>, <strong id="sdrs_ug_rp_0003__b185299329172">Protecting</strong>, <strong id="sdrs_ug_rp_0003__b10530113220177">Failover complete</strong>, <strong id="sdrs_ug_rp_0003__b753111320178">Creation failed</strong>, <strong id="sdrs_ug_rp_0003__b553133215171">Enabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b353363281718">Disabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b55356320177">Switchover failed</strong>, <strong id="sdrs_ug_rp_0003__b12536173215178">Failover failed</strong>, <strong id="sdrs_ug_rp_0003__b7537153216174">Deletion failed</strong>, <strong id="sdrs_ug_rp_0003__b553812328179">Re-enabling protection failed</strong>, <strong id="sdrs_ug_rp_0003__b753853217178">Attaching failed</strong>, <strong id="sdrs_ug_rp_0003__b1353923217172">Expansion failed</strong>, <strong id="sdrs_ug_rp_0003__b205401532111714">Invalid</strong>, or <strong id="sdrs_ug_rp_0003__b17541133291715">Faulty</strong> state.</li><li id="sdrs_ug_rp_0003__li92452023183414">The replication pair is not attached to any protected instance. For details about how to detach a replication pair, see <a href="sdrs_ug_pi_0005.html">Detaching a Replication Pair</a>.</li></ul>
|
||||||
</div>
|
</div>
|
||||||
<div class="section" id="sdrs_ug_rp_0003__section129182182540"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_rp_0003__ol25521131154217"><li id="sdrs_ug_rp_0003__li109831058719"><span>Log in to the management console.</span></li><li id="sdrs_ug_rp_0003__li12972105114527"><span>Click <strong id="sdrs_ug_rp_0003__b109361349105516">Service List</strong> and choose <strong id="sdrs_ug_rp_0003__b1594634955515">Storage</strong> > <strong id="sdrs_ug_rp_0003__b3947134911558">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_rp_0003__en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_rp_0003__b1751112468494">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
<div class="section" id="sdrs_ug_rp_0003__section129182182540"><h4 class="sectiontitle">Procedure</h4><ol id="sdrs_ug_rp_0003__ol25521131154217"><li id="sdrs_ug_rp_0003__li109831058719"><span>Log in to the management console.</span></li><li id="sdrs_ug_rp_0003__li12972105114527"><span>Click <strong id="sdrs_ug_rp_0003__b109361349105516">Service List</strong> and choose <strong id="sdrs_ug_rp_0003__b1594634955515">Storage</strong> > <strong id="sdrs_ug_rp_0003__b3947134911558">Storage Disaster Recovery Service</strong>.</span><p><p id="sdrs_ug_rp_0003__en-us_topic_0108180805_p45581331134216">The <strong id="sdrs_ug_rp_0003__b1751112468494">Storage Disaster Recovery Service</strong> page is displayed.</p>
|
||||||
</p></li><li id="sdrs_ug_rp_0003__li10559731134212"><span>In the pane of the protection group, click <strong id="sdrs_ug_rp_0003__b84235270611125">Replication Pairs</strong>.</span><p><p id="sdrs_ug_rp_0003__p14560331104217">The operation page for the protection group is displayed.</p>
|
</p></li><li id="sdrs_ug_rp_0003__li10559731134212"><span>In the pane of the protection group, click <strong id="sdrs_ug_rp_0003__b84235270611125">Replication Pairs</strong>.</span><p><p id="sdrs_ug_rp_0003__p14560331104217">The operation page for the protection group is displayed.</p>
|
||||||
|
|||||||
Reference in New Issue
Block a user