diff --git a/docs/sdrs/umn/ALL_META.TXT.json b/docs/sdrs/umn/ALL_META.TXT.json new file mode 100644 index 00000000..45c3a745 --- /dev/null +++ b/docs/sdrs/umn/ALL_META.TXT.json @@ -0,0 +1,562 @@ +[ + { + "uri":"sdrs_pro_0000.html", + "product_code":"sdrs", + "code":"1", + "des":"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.", + "doc_type":"usermanual", + "kw":"Service Overview", + "title":"Service Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0125068221.html", + "product_code":"sdrs", + "code":"2", + "des":"Storage Disaster Recovery Service (SDRS) provides disaster recovery (DR) services for many cloud services, such as Elastic Cloud Server (ECS) and Elastic Volume Service (", + "doc_type":"usermanual", + "kw":"SDRS,存储容灾,容灾与备份,What Is SDRS?,Service Overview,User Guide", + "title":"What Is SDRS?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0108180804.html", + "product_code":"sdrs", + "code":"3", + "des":"SDRS has the following advantages:Convenient service recoverySDRS provides a management console. You can configure and manage server replication and perform a planned fai", + "doc_type":"usermanual", + "kw":"Product Advantages,Service Overview,User Guide", + "title":"Product Advantages", + "githuburl":"" + }, + { + "uri":"sdrs_pro_0003.html", + "product_code":"sdrs", + "code":"4", + "des":"SDRS uses storage-layer synchronization and replication to provide cross-AZ DR to ensure data crash consistency and server-level protection with zero RPO. If a source AZ ", + "doc_type":"usermanual", + "kw":"Application Scenarios,Service Overview,User Guide", + "title":"Application Scenarios", + "githuburl":"" + }, + { + "uri":"en-us_topic_0110981899.html", + "product_code":"sdrs", + "code":"5", + "des":"Before using SDRS, learn about the constraints listed in Table 1.If the AZ of the production site becomes faulty, you can use the DR drill function to restore the server ", + "doc_type":"usermanual", + "kw":"Constraints,Service Overview,User Guide", + "title":"Constraints", + "githuburl":"" + }, + { + "uri":"sdrs_pro_0008.html", + "product_code":"sdrs", + "code":"6", + "des":"DescriptionThe production site has a fault. Services at the production site are affected and cannot be restored using the failover function.Production site being faultyTh", + "doc_type":"usermanual", + "kw":"Supported DR Scenarios,Service Overview,User Guide", + "title":"Supported DR Scenarios", + "githuburl":"" + }, + { + "uri":"sdrs_pro_0010.html", + "product_code":"sdrs", + "code":"7", + "des":"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.", + "doc_type":"usermanual", + "kw":"Relationships with Other Services,Service Overview,User Guide", + "title":"Relationships with Other Services", + "githuburl":"" + }, + { + "uri":"sdrs_pro_0012.html", + "product_code":"sdrs", + "code":"8", + "des":"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.", + "doc_type":"usermanual", + "kw":"Basic Concepts", + "title":"Basic Concepts", + "githuburl":"" + }, + { + "uri":"sdrs_pro_0013.html", + "product_code":"sdrs", + "code":"9", + "des":"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.", + "doc_type":"usermanual", + "kw":"SDRS Basic Concepts,Basic Concepts,User Guide", + "title":"SDRS Basic Concepts", + "githuburl":"" + }, + { + "uri":"sdrs_pro_0014.html", + "product_code":"sdrs", + "code":"10", + "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "doc_type":"usermanual", + "kw":"Region and AZ,Basic Concepts,User Guide", + "title":"Region and AZ", + "githuburl":"" + }, + { + "uri":"sdrs_qs_0000.html", + "product_code":"sdrs", + "code":"11", + "des":"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.", + "doc_type":"usermanual", + "kw":"Getting Started", + "title":"Getting Started", + "githuburl":"" + }, + { + "uri":"sdrs_qs_0001.html", + "product_code":"sdrs", + "code":"12", + "des":"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.", + "doc_type":"usermanual", + "kw":"Configuring Cross-AZ DR", + "title":"Configuring Cross-AZ DR", + "githuburl":"" + }, + { + "uri":"en-us_topic_0108180816.html", + "product_code":"sdrs", + "code":"13", + "des":"SDRS provides cross-AZ server-level protection (RPO = 0) in case applications at a production site cannot restore in a short period of time caused by force majeure like f", + "doc_type":"usermanual", + "kw":"Configuration Process,Configuring Cross-AZ DR,User Guide", + "title":"Configuration Process", + "githuburl":"" + }, + { + "uri":"en-us_topic_0108180805.html", + "product_code":"sdrs", + "code":"14", + "des":"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 gro", + "doc_type":"usermanual", + "kw":"Step 1: Create a Protection Group,Configuring Cross-AZ DR,User Guide", + "title":"Step 1: Create a Protection Group", + "githuburl":"" + }, + { + "uri":"en-us_topic_0110037558.html", + "product_code":"sdrs", + "code":"15", + "des":"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 fa", + "doc_type":"usermanual", + "kw":"Step 2: Create a Protected Instance,Configuring Cross-AZ DR,User Guide", + "title":"Step 2: Create a Protected Instance", + "githuburl":"" + }, + { + "uri":"en-us_topic_0110046974.html", + "product_code":"sdrs", + "code":"16", + "des":"If you want to enable protection for all resources in a specified protection group, you can perform steps provided in this section.When data is written to the disks of th", + "doc_type":"usermanual", + "kw":"Step 3: Enable Protection,Configuring Cross-AZ DR,User Guide", + "title":"Step 3: Enable Protection", + "githuburl":"" + }, + { + "uri":"en-us_topic_0122528555.html", + "product_code":"sdrs", + "code":"17", + "des":"DR drills can be used to simulate fault scenarios, develop emergency recovery solutions, and verify whether the solutions are applicable and effective. Existing services ", + "doc_type":"usermanual", + "kw":"创建容灾演练,Performing a DR Drill,Getting Started,User Guide", + "title":"Performing a DR Drill", + "githuburl":"" + }, + { + "uri":"sdrs_ug_0000.html", + "product_code":"sdrs", + "code":"18", + "des":"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.", + "doc_type":"usermanual", + "kw":"Management", + "title":"Management", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pg_0000.html", + "product_code":"sdrs", + "code":"19", + "des":"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.", + "doc_type":"usermanual", + "kw":"Managing Protection Groups", + "title":"Managing Protection Groups", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pg_0001.html", + "product_code":"sdrs", + "code":"20", + "des":"If you want to disable protection for all resources in a specified protection group, you can perform steps provided in this section.Once the protection is disabled, data ", + "doc_type":"usermanual", + "kw":"Disabling Protection,Managing Protection Groups,User Guide", + "title":"Disabling Protection", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pg_0002.html", + "product_code":"sdrs", + "code":"21", + "des":"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. ", + "doc_type":"usermanual", + "kw":"Performing a Planned Failover,Managing Protection Groups,User Guide", + "title":"Performing a Planned Failover", + "githuburl":"" + }, + { + "uri":"en-us_topic_0108560208.html", + "product_code":"sdrs", + "code":"22", + "des":"When the servers and disks at the production site become faulty due to force majeure, you can perform a failover for them and enable the servers and disks at the DR site ", + "doc_type":"usermanual", + "kw":"Performing a Failover,Managing Protection Groups,User Guide", + "title":"Performing a Failover", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pg_0006.html", + "product_code":"sdrs", + "code":"23", + "des":"Once the failover is started, data synchronization stops. After the failover is complete, the protection group is in the Protection disabled state. To restart data synchr", + "doc_type":"usermanual", + "kw":"Performing Reprotection,Managing Protection Groups,User Guide", + "title":"Performing Reprotection", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pg_0007.html", + "product_code":"sdrs", + "code":"24", + "des":"If a protection group is no longer used, you can release the virtual resources by deleting the protection group from the system.All the protected instances, DR drills, an", + "doc_type":"usermanual", + "kw":"Deleting a Protection Group,Managing Protection Groups,User Guide", + "title":"Deleting a Protection Group", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pi_0000.html", + "product_code":"sdrs", + "code":"25", + "des":"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.", + "doc_type":"usermanual", + "kw":"Managing Protected Instances", + "title":"Managing Protected Instances", + "githuburl":"" + }, + { + "uri":"en-us_topic_0110273585.html", + "product_code":"sdrs", + "code":"26", + "des":"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 specific", + "doc_type":"usermanual", + "kw":"Modifying Specifications of a Protected Instance,Managing Protected Instances,User Guide", + "title":"Modifying Specifications of a Protected Instance", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pi_0002.html", + "product_code":"sdrs", + "code":"27", + "des":"If you do not need a protected instance, you can delete it to cancel the protection relationship between the servers and the protection group.When you delete a protected ", + "doc_type":"usermanual", + "kw":"Deleting a Protected Instance,Managing Protected Instances,User Guide", + "title":"Deleting a Protected Instance", + "githuburl":"" + }, + { + "uri":"en-us_topic_0110037559.html", + "product_code":"sdrs", + "code":"28", + "des":"You can create replication pairs for desired disks and add the replication pairs to a specified protection group. When you create a replication pair:If the protection gro", + "doc_type":"usermanual", + "kw":"Creating a Replication Pair,Managing Protected Instances,User Guide", + "title":"Creating a Replication Pair", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pi_0004.html", + "product_code":"sdrs", + "code":"29", + "des":"You can perform steps provided in this section to attach a replication pair to a protected instance. Then, the production site disk is attached to the production site ser", + "doc_type":"usermanual", + "kw":"Attaching a Replication Pair,Managing Protected Instances,User Guide", + "title":"Attaching a Replication Pair", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pi_0005.html", + "product_code":"sdrs", + "code":"30", + "des":"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 wri", + "doc_type":"usermanual", + "kw":"Detaching a Replication Pair,Managing Protected Instances,User Guide", + "title":"Detaching a Replication Pair", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pi_0006.html", + "product_code":"sdrs", + "code":"31", + "des":"If more NICs are required for your protected instance, you can perform steps provided in this section to add a NIC to the protected instance.The protection group is in th", + "doc_type":"usermanual", + "kw":"Adding a NIC,Managing Protected Instances,User Guide", + "title":"Adding a NIC", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pi_0007.html", + "product_code":"sdrs", + "code":"32", + "des":"A protected instance can have up to 12 NICs, including one primary NIC that cannot be deleted. You can perform steps provided in this section to delete a NIC other than t", + "doc_type":"usermanual", + "kw":"Deleting a NIC,Managing Protected Instances,User Guide", + "title":"Deleting a NIC", + "githuburl":"" + }, + { + "uri":"sdrs_ug_pi_0008.html", + "product_code":"sdrs", + "code":"33", + "des":"Tags are identifiers of protected instances. You can add tags for protected instances, and classify and search the protected instances based on these tags.You can add a m", + "doc_type":"usermanual", + "kw":"Managing Protected Instance Tags,Managing Protected Instances,User Guide", + "title":"Managing Protected Instance Tags", + "githuburl":"" + }, + { + "uri":"sdrs_ug_rp_0000.html", + "product_code":"sdrs", + "code":"34", + "des":"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.", + "doc_type":"usermanual", + "kw":"Managing Replication Pairs", + "title":"Managing Replication Pairs", + "githuburl":"" + }, + { + "uri":"sdrs_ug_rp_0001.html", + "product_code":"sdrs", + "code":"35", + "des":"You can create replication pairs for desired disks and add the replication pairs to a specified protection group. When you create a replication pair:If the protection gro", + "doc_type":"usermanual", + "kw":"Creating a Replication Pair,Managing Replication Pairs,User Guide", + "title":"Creating a Replication Pair", + "githuburl":"" + }, + { + "uri":"sdrs_ug_rp_0002.html", + "product_code":"sdrs", + "code":"36", + "des":"If the replication pair capacity of your protection groups cannot meet your service requirements, you can perform steps provided in this section to expand the capacity of", + "doc_type":"usermanual", + "kw":"Expanding Replication Pair Capacity,Managing Replication Pairs,User Guide", + "title":"Expanding Replication Pair Capacity", + "githuburl":"" + }, + { + "uri":"sdrs_ug_rp_0003.html", + "product_code":"sdrs", + "code":"37", + "des":"If a replication pair is no longer used, you can release the associated virtual resources by deleting the replication pair from the system.When you delete a replication p", + "doc_type":"usermanual", + "kw":"Deleting a Replication Pair,Managing Replication Pairs,User Guide", + "title":"Deleting a Replication Pair", + "githuburl":"" + }, + { + "uri":"sdrs_ug_dr_0000.html", + "product_code":"sdrs", + "code":"38", + "des":"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.", + "doc_type":"usermanual", + "kw":"Managing DR Drills", + "title":"Managing DR Drills", + "githuburl":"" + }, + { + "uri":"sdrs_ug_dr_0001.html", + "product_code":"sdrs", + "code":"39", + "des":"DR drills can be used to simulate fault scenarios, develop emergency recovery solutions, and verify whether the solutions are applicable and effective. Existing services ", + "doc_type":"usermanual", + "kw":"创建容灾演练,Performing a DR Drill,Managing DR Drills,User Guide", + "title":"Performing a DR Drill", + "githuburl":"" + }, + { + "uri":"sdrs_ug_dr_0002.html", + "product_code":"sdrs", + "code":"40", + "des":"If a DR drill is no longer used, you can release the virtual resources by deleting the DR drill from the system. When you delete a DR drill, all the drill servers in it a", + "doc_type":"usermanual", + "kw":"Deleting a DR Drill,Managing DR Drills,User Guide", + "title":"Deleting a DR Drill", + "githuburl":"" + }, + { + "uri":"sdrs_ug_cts_0000.html", + "product_code":"sdrs", + "code":"41", + "des":"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.", + "doc_type":"usermanual", + "kw":"Interconnecting with CTS", + "title":"Interconnecting with CTS", + "githuburl":"" + }, + { + "uri":"sdrs_ug_cts_0001.html", + "product_code":"sdrs", + "code":"42", + "des":"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.", + "doc_type":"usermanual", + "kw":"Key SDRS Operations Recorded by CTS,Interconnecting with CTS,User Guide", + "title":"Key SDRS Operations Recorded by CTS", + "githuburl":"" + }, + { + "uri":"sdrs_ug_cts_0002.html", + "product_code":"sdrs", + "code":"43", + "des":"After you enable CTS, the system starts recording operations on SDRS. You can view operation records of the last seven days on the management console.Log in to the manage", + "doc_type":"usermanual", + "kw":"Viewing Traces,Interconnecting with CTS,User Guide", + "title":"Viewing Traces", + "githuburl":"" + }, + { + "uri":"sdrs_06_0400.html", + "product_code":"sdrs", + "code":"44", + "des":"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.", + "doc_type":"usermanual", + "kw":"FAQs", + "title":"FAQs", + "githuburl":"" + }, + { + "uri":"sdrs_06_0410.html", + "product_code":"sdrs", + "code":"45", + "des":"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", + "doc_type":"usermanual", + "kw":"What Is DR?,FAQs,User Guide", + "title":"What Is DR?", + "githuburl":"" + }, + { + "uri":"sdrs_06_0430.html", + "product_code":"sdrs", + "code":"46", + "des":"SDRS provides the following features:Convenient service recoverySDRS provides a management console. You can configure and manage server replication and perform a planned ", + "doc_type":"usermanual", + "kw":"What Are the Highlights of SDRS?,FAQs,User Guide", + "title":"What Are the Highlights of SDRS?", + "githuburl":"" + }, + { + "uri":"sdrs_06_0440.html", + "product_code":"sdrs", + "code":"47", + "des":"Recovery Point Objective (RPO): the maximum data loss amount tolerated by the system.Recovery Time Objective (RTO): the maximum service interruption duration tolerated by", + "doc_type":"usermanual", + "kw":"What Are RPO and RTO?,FAQs,User Guide", + "title":"What Are RPO and RTO?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0109956554.html", + "product_code":"sdrs", + "code":"48", + "des":"Differences between disaster recovery (DR) and backup are as follows:DR is used to prevent impacts on the systems caused by natural disasters, such as fires and earthquak", + "doc_type":"usermanual", + "kw":"What Are the Differences Between DR and Backup?,FAQs,User Guide", + "title":"What Are the Differences Between DR and Backup?", + "githuburl":"" + }, + { + "uri":"sdrs_06_0402.html", + "product_code":"sdrs", + "code":"49", + "des":"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", + "doc_type":"usermanual", + "kw":"What Can I Do When the EIP Cannot Be Pinged After I Perform a Planned Failover for a Protection Grou", + "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?", + "githuburl":"" + }, + { + "uri":"sdrs_06_0403.html", + "product_code":"sdrs", + "code":"50", + "des":"The production site server runs the SUSE OS. After users create a DR drill using this server, the NIC names of the DR drill server are different from those of the product", + "doc_type":"usermanual", + "kw":"What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?,FAQs", + "title":"What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?", + "githuburl":"" + }, + { + "uri":"sdrs_06_0404.html", + "product_code":"sdrs", + "code":"51", + "des":"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", + "doc_type":"usermanual", + "kw":"What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Pla", + "title":"What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?", + "githuburl":"" + }, + { + "uri":"sdrs_faq_0004.html", + "product_code":"sdrs", + "code":"52", + "des":"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", + "doc_type":"usermanual", + "kw":"Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?,FAQs,User Guide", + "title":"Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?", + "githuburl":"" + }, + { + "uri":"sdrs_faq_0005.html", + "product_code":"sdrs", + "code":"53", + "des":"If the production site server runs Windows and uses a key pair for login, ensure that the key pair exists when you create a protected instance or a DR drill. Or, the DR s", + "doc_type":"usermanual", + "kw":"What Are the Precautions If I Log In to the Production Site Server Using a Key Pair?,FAQs,User Guide", + "title":"What Are the Precautions If I Log In to the Production Site Server Using a Key Pair?", + "githuburl":"" + }, + { + "uri":"sdrs_faq_0007.html", + "product_code":"sdrs", + "code":"54", + "des":"No. SDRS does not support automatic failover. You need to manually execute a failover via API or on the console.", + "doc_type":"usermanual", + "kw":"Does SDRS Support Automatic Failover?,FAQs,User Guide", + "title":"Does SDRS Support Automatic Failover?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0288665269.html", + "product_code":"sdrs", + "code":"55", + "des":"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.", + "doc_type":"usermanual", + "kw":"Change History,User Guide", + "title":"Change History", + "githuburl":"" + }, + { + "uri":"en-us_topic_0288665370.html", + "product_code":"sdrs", + "code":"56", + "des":"For details about the glossaries in this document, see Glossary.", + "doc_type":"usermanual", + "kw":"Glossary,User Guide", + "title":"Glossary", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/sdrs/umn/CLASS.TXT.json b/docs/sdrs/umn/CLASS.TXT.json new file mode 100644 index 00000000..4ce0648f --- /dev/null +++ b/docs/sdrs/umn/CLASS.TXT.json @@ -0,0 +1,506 @@ +[ + { + "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", + "title":"Service Overview", + "uri":"sdrs_pro_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"Storage Disaster Recovery Service (SDRS) provides disaster recovery (DR) services for many cloud services, such as Elastic Cloud Server (ECS) and Elastic Volume Service (", + "product_code":"sdrs", + "title":"What Is SDRS?", + "uri":"en-us_topic_0125068221.html", + "doc_type":"usermanual", + "p_code":"1", + "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", + "product_code":"sdrs", + "title":"Product Advantages", + "uri":"en-us_topic_0108180804.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"3" + }, + { + "desc":"SDRS uses storage-layer synchronization and replication to provide cross-AZ DR to ensure data crash consistency and server-level protection with zero RPO. If a source AZ ", + "product_code":"sdrs", + "title":"Application Scenarios", + "uri":"sdrs_pro_0003.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"4" + }, + { + "desc":"Before using SDRS, learn about the constraints listed in Table 1.If the AZ of the production site becomes faulty, you can use the DR drill function to restore the server ", + "product_code":"sdrs", + "title":"Constraints", + "uri":"en-us_topic_0110981899.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"5" + }, + { + "desc":"DescriptionThe production site has a fault. Services at the production site are affected and cannot be restored using the failover function.Production site being faultyTh", + "product_code":"sdrs", + "title":"Supported DR Scenarios", + "uri":"sdrs_pro_0008.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"6" + }, + { + "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", + "title":"Relationships with Other Services", + "uri":"sdrs_pro_0010.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"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.", + "product_code":"sdrs", + "title":"Basic Concepts", + "uri":"sdrs_pro_0012.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"8" + }, + { + "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", + "title":"SDRS Basic Concepts", + "uri":"sdrs_pro_0013.html", + "doc_type":"usermanual", + "p_code":"8", + "code":"9" + }, + { + "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "product_code":"sdrs", + "title":"Region and AZ", + "uri":"sdrs_pro_0014.html", + "doc_type":"usermanual", + "p_code":"8", + "code":"10" + }, + { + "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", + "title":"Getting Started", + "uri":"sdrs_qs_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"11" + }, + { + "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", + "title":"Configuring Cross-AZ DR", + "uri":"sdrs_qs_0001.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"12" + }, + { + "desc":"SDRS provides cross-AZ server-level protection (RPO = 0) in case applications at a production site cannot restore in a short period of time caused by force majeure like f", + "product_code":"sdrs", + "title":"Configuration Process", + "uri":"en-us_topic_0108180816.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"13" + }, + { + "desc":"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 gro", + "product_code":"sdrs", + "title":"Step 1: Create a Protection Group", + "uri":"en-us_topic_0108180805.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"14" + }, + { + "desc":"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 fa", + "product_code":"sdrs", + "title":"Step 2: Create a Protected Instance", + "uri":"en-us_topic_0110037558.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"15" + }, + { + "desc":"If you want to enable protection for all resources in a specified protection group, you can perform steps provided in this section.When data is written to the disks of th", + "product_code":"sdrs", + "title":"Step 3: Enable Protection", + "uri":"en-us_topic_0110046974.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"16" + }, + { + "desc":"DR drills can be used to simulate fault scenarios, develop emergency recovery solutions, and verify whether the solutions are applicable and effective. Existing services ", + "product_code":"sdrs", + "title":"Performing a DR Drill", + "uri":"en-us_topic_0122528555.html", + "doc_type":"usermanual", + "p_code":"11", + "code":"17" + }, + { + "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", + "title":"Management", + "uri":"sdrs_ug_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"18" + }, + { + "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", + "title":"Managing Protection Groups", + "uri":"sdrs_ug_pg_0000.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"19" + }, + { + "desc":"If you want to disable protection for all resources in a specified protection group, you can perform steps provided in this section.Once the protection is disabled, data ", + "product_code":"sdrs", + "title":"Disabling Protection", + "uri":"sdrs_ug_pg_0001.html", + "doc_type":"usermanual", + "p_code":"19", + "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. ", + "product_code":"sdrs", + "title":"Performing a Planned Failover", + "uri":"sdrs_ug_pg_0002.html", + "doc_type":"usermanual", + "p_code":"19", + "code":"21" + }, + { + "desc":"When the servers and disks at the production site become faulty due to force majeure, you can perform a failover for them and enable the servers and disks at the DR site ", + "product_code":"sdrs", + "title":"Performing a Failover", + "uri":"en-us_topic_0108560208.html", + "doc_type":"usermanual", + "p_code":"19", + "code":"22" + }, + { + "desc":"Once the failover is started, data synchronization stops. After the failover is complete, the protection group is in the Protection disabled state. To restart data synchr", + "product_code":"sdrs", + "title":"Performing Reprotection", + "uri":"sdrs_ug_pg_0006.html", + "doc_type":"usermanual", + "p_code":"19", + "code":"23" + }, + { + "desc":"If a protection group is no longer used, you can release the virtual resources by deleting the protection group from the system.All the protected instances, DR drills, an", + "product_code":"sdrs", + "title":"Deleting a Protection Group", + "uri":"sdrs_ug_pg_0007.html", + "doc_type":"usermanual", + "p_code":"19", + "code":"24" + }, + { + "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", + "title":"Managing Protected Instances", + "uri":"sdrs_ug_pi_0000.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"25" + }, + { + "desc":"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 specific", + "product_code":"sdrs", + "title":"Modifying Specifications of a Protected Instance", + "uri":"en-us_topic_0110273585.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"26" + }, + { + "desc":"If you do not need a protected instance, you can delete it to cancel the protection relationship between the servers and the protection group.When you delete a protected ", + "product_code":"sdrs", + "title":"Deleting a Protected Instance", + "uri":"sdrs_ug_pi_0002.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"27" + }, + { + "desc":"You can create replication pairs for desired disks and add the replication pairs to a specified protection group. When you create a replication pair:If the protection gro", + "product_code":"sdrs", + "title":"Creating a Replication Pair", + "uri":"en-us_topic_0110037559.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"28" + }, + { + "desc":"You can perform steps provided in this section to attach a replication pair to a protected instance. Then, the production site disk is attached to the production site ser", + "product_code":"sdrs", + "title":"Attaching a Replication Pair", + "uri":"sdrs_ug_pi_0004.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"29" + }, + { + "desc":"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 wri", + "product_code":"sdrs", + "title":"Detaching a Replication Pair", + "uri":"sdrs_ug_pi_0005.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"30" + }, + { + "desc":"If more NICs are required for your protected instance, you can perform steps provided in this section to add a NIC to the protected instance.The protection group is in th", + "product_code":"sdrs", + "title":"Adding a NIC", + "uri":"sdrs_ug_pi_0006.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"31" + }, + { + "desc":"A protected instance can have up to 12 NICs, including one primary NIC that cannot be deleted. You can perform steps provided in this section to delete a NIC other than t", + "product_code":"sdrs", + "title":"Deleting a NIC", + "uri":"sdrs_ug_pi_0007.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"32" + }, + { + "desc":"Tags are identifiers of protected instances. You can add tags for protected instances, and classify and search the protected instances based on these tags.You can add a m", + "product_code":"sdrs", + "title":"Managing Protected Instance Tags", + "uri":"sdrs_ug_pi_0008.html", + "doc_type":"usermanual", + "p_code":"25", + "code":"33" + }, + { + "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", + "title":"Managing Replication Pairs", + "uri":"sdrs_ug_rp_0000.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"34" + }, + { + "desc":"You can create replication pairs for desired disks and add the replication pairs to a specified protection group. When you create a replication pair:If the protection gro", + "product_code":"sdrs", + "title":"Creating a Replication Pair", + "uri":"sdrs_ug_rp_0001.html", + "doc_type":"usermanual", + "p_code":"34", + "code":"35" + }, + { + "desc":"If the replication pair capacity of your protection groups cannot meet your service requirements, you can perform steps provided in this section to expand the capacity of", + "product_code":"sdrs", + "title":"Expanding Replication Pair Capacity", + "uri":"sdrs_ug_rp_0002.html", + "doc_type":"usermanual", + "p_code":"34", + "code":"36" + }, + { + "desc":"If a replication pair is no longer used, you can release the associated virtual resources by deleting the replication pair from the system.When you delete a replication p", + "product_code":"sdrs", + "title":"Deleting a Replication Pair", + "uri":"sdrs_ug_rp_0003.html", + "doc_type":"usermanual", + "p_code":"34", + "code":"37" + }, + { + "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", + "title":"Managing DR Drills", + "uri":"sdrs_ug_dr_0000.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"38" + }, + { + "desc":"DR drills can be used to simulate fault scenarios, develop emergency recovery solutions, and verify whether the solutions are applicable and effective. Existing services ", + "product_code":"sdrs", + "title":"Performing a DR Drill", + "uri":"sdrs_ug_dr_0001.html", + "doc_type":"usermanual", + "p_code":"38", + "code":"39" + }, + { + "desc":"If a DR drill is no longer used, you can release the virtual resources by deleting the DR drill from the system. When you delete a DR drill, all the drill servers in it a", + "product_code":"sdrs", + "title":"Deleting a DR Drill", + "uri":"sdrs_ug_dr_0002.html", + "doc_type":"usermanual", + "p_code":"38", + "code":"40" + }, + { + "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", + "title":"Interconnecting with CTS", + "uri":"sdrs_ug_cts_0000.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"41" + }, + { + "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", + "title":"Key SDRS Operations Recorded by CTS", + "uri":"sdrs_ug_cts_0001.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"42" + }, + { + "desc":"After you enable CTS, the system starts recording operations on SDRS. You can view operation records of the last seven days on the management console.Log in to the manage", + "product_code":"sdrs", + "title":"Viewing Traces", + "uri":"sdrs_ug_cts_0002.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"43" + }, + { + "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", + "title":"FAQs", + "uri":"sdrs_06_0400.html", + "doc_type":"usermanual", + "p_code":"", + "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", + "product_code":"sdrs", + "title":"What Is DR?", + "uri":"sdrs_06_0410.html", + "doc_type":"usermanual", + "p_code":"44", + "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 ", + "product_code":"sdrs", + "title":"What Are the Highlights of SDRS?", + "uri":"sdrs_06_0430.html", + "doc_type":"usermanual", + "p_code":"44", + "code":"46" + }, + { + "desc":"Recovery Point Objective (RPO): the maximum data loss amount tolerated by the system.Recovery Time Objective (RTO): the maximum service interruption duration tolerated by", + "product_code":"sdrs", + "title":"What Are RPO and RTO?", + "uri":"sdrs_06_0440.html", + "doc_type":"usermanual", + "p_code":"44", + "code":"47" + }, + { + "desc":"Differences between disaster recovery (DR) and backup are as follows:DR is used to prevent impacts on the systems caused by natural disasters, such as fires and earthquak", + "product_code":"sdrs", + "title":"What Are the Differences Between DR and Backup?", + "uri":"en-us_topic_0109956554.html", + "doc_type":"usermanual", + "p_code":"44", + "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", + "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?", + "uri":"sdrs_06_0402.html", + "doc_type":"usermanual", + "p_code":"44", + "code":"49" + }, + { + "desc":"The production site server runs the SUSE OS. After users create a DR drill using this server, the NIC names of the DR drill server are different from those of the product", + "product_code":"sdrs", + "title":"What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?", + "uri":"sdrs_06_0403.html", + "doc_type":"usermanual", + "p_code":"44", + "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", + "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?", + "uri":"sdrs_06_0404.html", + "doc_type":"usermanual", + "p_code":"44", + "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", + "product_code":"sdrs", + "title":"Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?", + "uri":"sdrs_faq_0004.html", + "doc_type":"usermanual", + "p_code":"44", + "code":"52" + }, + { + "desc":"If the production site server runs Windows and uses a key pair for login, ensure that the key pair exists when you create a protected instance or a DR drill. Or, the DR s", + "product_code":"sdrs", + "title":"What Are the Precautions If I Log In to the Production Site Server Using a Key Pair?", + "uri":"sdrs_faq_0005.html", + "doc_type":"usermanual", + "p_code":"44", + "code":"53" + }, + { + "desc":"No. SDRS does not support automatic failover. You need to manually execute a failover via API or on the console.", + "product_code":"sdrs", + "title":"Does SDRS Support Automatic Failover?", + "uri":"sdrs_faq_0007.html", + "doc_type":"usermanual", + "p_code":"44", + "code":"54" + }, + { + "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", + "title":"Change History", + "uri":"en-us_topic_0288665269.html", + "doc_type":"usermanual", + "p_code":"", + "code":"55" + }, + { + "desc":"For details about the glossaries in this document, see Glossary.", + "product_code":"sdrs", + "title":"Glossary", + "uri":"en-us_topic_0288665370.html", + "doc_type":"usermanual", + "p_code":"", + "code":"56" + } +] \ No newline at end of file diff --git a/docs/sdrs/umn/PARAMETERS.txt b/docs/sdrs/umn/PARAMETERS.txt new file mode 100644 index 00000000..6da8d5f0 --- /dev/null +++ b/docs/sdrs/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/sdrs/umn/en-us_image_0184026531.png b/docs/sdrs/umn/en-us_image_0184026531.png new file mode 100644 index 00000000..1303a51c Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0184026531.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665263.png b/docs/sdrs/umn/en-us_image_0288665263.png new file mode 100644 index 00000000..52b62968 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665263.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665264.png b/docs/sdrs/umn/en-us_image_0288665264.png new file mode 100644 index 00000000..061e1e6d Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665264.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665266.png b/docs/sdrs/umn/en-us_image_0288665266.png new file mode 100644 index 00000000..c8b5302f Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665266.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665274.png b/docs/sdrs/umn/en-us_image_0288665274.png new file mode 100644 index 00000000..f351fdd7 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665274.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665280.png b/docs/sdrs/umn/en-us_image_0288665280.png new file mode 100644 index 00000000..5b010b2f Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665280.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665281.png b/docs/sdrs/umn/en-us_image_0288665281.png new file mode 100644 index 00000000..3cbde582 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665281.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665304.png b/docs/sdrs/umn/en-us_image_0288665304.png new file mode 100644 index 00000000..9518f07d Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665304.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665307.png b/docs/sdrs/umn/en-us_image_0288665307.png new file mode 100644 index 00000000..f4a2e78e Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665307.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665316.png b/docs/sdrs/umn/en-us_image_0288665316.png new file mode 100644 index 00000000..0bd408ed Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665316.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665319.png b/docs/sdrs/umn/en-us_image_0288665319.png new file mode 100644 index 00000000..93fb5802 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665319.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665320.png b/docs/sdrs/umn/en-us_image_0288665320.png new file mode 100644 index 00000000..661f8adc Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665320.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665321.png b/docs/sdrs/umn/en-us_image_0288665321.png new file mode 100644 index 00000000..5f0bffe6 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665321.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665326.png b/docs/sdrs/umn/en-us_image_0288665326.png new file mode 100644 index 00000000..ad4349c9 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665326.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665327.png b/docs/sdrs/umn/en-us_image_0288665327.png new file mode 100644 index 00000000..467e035e Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665327.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665328.png b/docs/sdrs/umn/en-us_image_0288665328.png new file mode 100644 index 00000000..126e37f0 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665328.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665337.png b/docs/sdrs/umn/en-us_image_0288665337.png new file mode 100644 index 00000000..876c6046 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665337.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665357.png b/docs/sdrs/umn/en-us_image_0288665357.png new file mode 100644 index 00000000..d3f625a1 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665357.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665358.png b/docs/sdrs/umn/en-us_image_0288665358.png new file mode 100644 index 00000000..66472ce6 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665358.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665371.png b/docs/sdrs/umn/en-us_image_0288665371.png new file mode 100644 index 00000000..7d76b0ba Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665371.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665372.png b/docs/sdrs/umn/en-us_image_0288665372.png new file mode 100644 index 00000000..f78ae1ab Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665372.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665377.png b/docs/sdrs/umn/en-us_image_0288665377.png new file mode 100644 index 00000000..b90a9b5b Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665377.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665385.png b/docs/sdrs/umn/en-us_image_0288665385.png new file mode 100644 index 00000000..c5eb299e Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665385.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665386.png b/docs/sdrs/umn/en-us_image_0288665386.png new file mode 100644 index 00000000..2129e1ec Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665386.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665392.png b/docs/sdrs/umn/en-us_image_0288665392.png new file mode 100644 index 00000000..ea3a9d09 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665392.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665395.png b/docs/sdrs/umn/en-us_image_0288665395.png new file mode 100644 index 00000000..8644dbb3 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665395.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665398.png b/docs/sdrs/umn/en-us_image_0288665398.png new file mode 100644 index 00000000..d774d811 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665398.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665399.png b/docs/sdrs/umn/en-us_image_0288665399.png new file mode 100644 index 00000000..cffd7e48 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665399.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665400.png b/docs/sdrs/umn/en-us_image_0288665400.png new file mode 100644 index 00000000..abad420b Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665400.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665401.png b/docs/sdrs/umn/en-us_image_0288665401.png new file mode 100644 index 00000000..8f172d49 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665401.png differ diff --git a/docs/sdrs/umn/en-us_image_0288665404.jpg b/docs/sdrs/umn/en-us_image_0288665404.jpg new file mode 100644 index 00000000..fac6892b Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665404.jpg differ diff --git a/docs/sdrs/umn/en-us_image_0288665405.png b/docs/sdrs/umn/en-us_image_0288665405.png new file mode 100644 index 00000000..503d09c2 Binary files /dev/null and b/docs/sdrs/umn/en-us_image_0288665405.png differ diff --git a/docs/sdrs/umn/en-us_topic_0108180804.html b/docs/sdrs/umn/en-us_topic_0108180804.html new file mode 100644 index 00000000..246ca4ec --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0108180804.html @@ -0,0 +1,22 @@ + + +

Product Advantages

+

SDRS has the following advantages:

+ +
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0108180805.html b/docs/sdrs/umn/en-us_topic_0108180805.html new file mode 100644 index 00000000..62bd63f5 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0108180805.html @@ -0,0 +1,71 @@ + + +

Step 1: Create a Protection Group

+

Scenarios

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.

+

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.

+
Figure 1 Creating a protection group
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. Click Create Protection Group.

    The Create Protection Group page is displayed.

    +
    Figure 2 Creating a protection group
    +

  4. Configure the basic information about the protection group listed in Table 1.

    All the parameters in the following table are mandatory.

    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Region

    +

    A region is a geographic area where resources used by servers are located.

    +

    If the region is incorrect, click the drop-down list for correction.

    +

    eu-de

    +

    DR Direction

    +
    • Production site: Select the AZ of the production site server.
    • DR site: Select the AZ of the DR site server.
    +

    Production site: az-01

    +

    DR site: az-02

    +

    Deployment Model

    +

    Currently, only the VPC migration model is supported. All resources at the production and DR sites belong to the same VPC.

    +

    VPC migration

    +

    VPC

    +

    Specifies the VPC where the protection group is located.

    +

    vpc-test

    +

    Protection Group Name

    +

    Enter the protection group name. It is used for group classification and search.

    +

    protection_group_001

    +
    +
    +

  5. Click Create Now.
  6. Click Back to Protection Group List to return to the SDRS homepage and query the protection group status.

    If the protection group is displayed in the Storage Disaster Recovery Service page and its status is Available (), the protection group has been created successfully.

    +

+
+
+
+
+
Parent topic: Configuring Cross-AZ DR
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0108180816.html b/docs/sdrs/umn/en-us_topic_0108180816.html new file mode 100644 index 00000000..abfe791b --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0108180816.html @@ -0,0 +1,15 @@ + + +

Configuration Process

+

SDRS provides cross-AZ server-level protection (RPO = 0) in case applications at a production site cannot restore in a short period of time caused by force majeure like fires or earthquakes or device faults like damaged software or hardware. Synchronous replication at the storage layer is used to provide cross-AZ DR protection, and thereby meeting the crash consistency of data. If the production site becomes faulty, you can rapidly restore the services at the DR site after simple configuration.

+

Figure 1 shows the cross-AZ DR configuration process.

+

When you create a protected instance, the system creates a replication pair for the disks of the servers at the production and DR site by default.

+
+
Figure 1 Cross-AZ DR configuration process
+
+
+
+
Parent topic: Configuring Cross-AZ DR
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0108560208.html b/docs/sdrs/umn/en-us_topic_0108560208.html new file mode 100644 index 00000000..fb6d6d37 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0108560208.html @@ -0,0 +1,32 @@ + + +

Performing a Failover

+

Scenarios

When the servers and disks at the production site become faulty due to force majeure, you can perform a failover for them and enable the servers and disks at the DR site to ensure the service continuity.

+

Once you perform a failover, the DR site servers and disks become available immediately. You can power on the servers, or use Cloud Server Backup Service (CSBS) or Volume Backup Service (VBS) to restore the data to a specified data recovery point.

+

SDRS will migrate NICs on the server during the failover. After the failover, the IP, EIP, and MAC addresses of the production site server will be migrated to the DR site server, so that the IP, EIP, and MAC addresses remain the same.

+
  • Once the failover is started, data synchronization stops.
  • After the failover is complete, the status of the protection group changes to Failover complete. Then, you need to switch to the protected instance details page and start the DR site server.
+
+
Figure 1 Performing a failover
+
+

Notes

For Linux servers with Cloud-Init installed, if you have changed hostname of the production site server before you perform a failover for the first time, this modification will not synchronize to the DR site server.

+

To resolve this problem, see What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?

+
+

Prerequisites

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the desired protection group, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. In the upper right corner of the page, click More and choose Fail Over from the drop-down list.

    The Fail Over dialog box is displayed.

    +

  5. Click Fail Over.

    During the failover, do not start or stop the servers in the protection group. Otherwise, the failover may fail.

    After you confirm the failover, production site servers will encounter blue screen of death (BSOD) or be forcibly stopped, and will not be able to start anymore.

    +
    +
    +

+
+

Related Operations

+
+
+
+
+
Parent topic: Managing Protection Groups
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0109956554.html b/docs/sdrs/umn/en-us_topic_0109956554.html new file mode 100644 index 00000000..8284dded --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0109956554.html @@ -0,0 +1,12 @@ + + +

What Are the Differences Between DR and Backup?

+
Differences between disaster recovery (DR) and backup are as follows: +
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0110037558.html b/docs/sdrs/umn/en-us_topic_0110037558.html new file mode 100644 index 00000000..a8497d0a --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0110037558.html @@ -0,0 +1,125 @@ + + +

Step 2: Create a Protected Instance

+

Scenarios

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.

+

Select a protection group for each server to be replicated and create a protected instance using the server. 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.

+

The server 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.

+
Figure 1 Creating a protected instance
+
+

Notes

+
+

Prerequisites

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which protected instances are to be added, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. On the Protected Instances tab, click Create Protected Instance.

    The Create Protected Instance page is displayed.

    +
    Figure 2 Creating a protected instance
    +

  5. Configure the basic information about the protected instance, as described in Table 1.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Protection Group Name

    +

    Indicates the name of the protection group to which the protected instance to be created belongs. You do not need to configure it.

    +

    protection_group_001

    +

    Protection Group ID

    +

    Indicates the ID of the protection group to which the protected instance to be created belongs.

    +

    2a663c5c-4774-4775-a321-562a1ea163e3

    +

    DR Direction

    +

    Indicates the replication direction of the protection group to which the protected instance to be created belongs. You do not need to configure it.

    +

    eu-de-01 -> eu-de-02

    +

    Production Site

    +

    Indicates the AZ of the production site server. You do not need to configure it.

    +

    az-01

    +

    Deployment Model

    +

    Indicates the deployment model of the protection group to which the protected instance to be created belongs. You do not need to configure it.

    +

    VPC migration

    +

    VPC

    +

    Indicates the VPC of the protection group to which the protected instance to be created belongs. You do not need to configure it.

    +

    vpc1

    +

    Production Site Server

    +

    This parameter is mandatory.

    +

    In the server list, select the server and specifications to be used to create the protected instance.

    + +
    NOTE:
    • If Server Type of the protection group is ECS, select the DR site server specifications. The specifications of the production site server and DR site server can be different. Select the specifications from the DR Site Server Specifications drop-down list.
    +
    +

    ecs-test > s3.small.1

    +

    DR Site VPC

    +

    Indicates the VPC of the DR site server.

    +

    Its value is the same as the VPC value and do not need to be configured.

    +

    vpc1

    +

    Protected Instance Name

    +

    This parameter is mandatory.

    +

    Enter the protected instance name. It is used for protected instance classification and search.

    +

    Protected-Instance-test

    +

    Tag

    +

    This parameter is optional.

    +

    Tags are identifiers of protected instances. You can add tags for protected instances, and classify and search for the protected instances based on these tags. You can add up to 10 tags for each server.

    +

    For details, see Managing Protected Instance Tags.

    +

    Organization/Marketing

    +
    +
    +

  6. Click Create Now.
  7. On the Confirm page, you can confirm the protected instance information.

    • If you do not need to modify the information, click Submit.
    • If you need to modify the information, click Previous.
    +

  8. Click Back to Protection Group Details Page and view the protected instances of the protection group.

    If the protected instance status changes to Available or Protecting, the protected instance has been created successfully.

    +

    After a protected instance is created, the system automatically creates replication pairs for the disks of the protected instance and backs up all the disks.

    +

    Query the replication pairs.

    +
    1. Switch to the operation page for the protection group.
    2. Click the Replication Pairs tab.

      On this tab, you can query the statuses of the replication pairs, target protected instance, and production site disk.

      +
    +
    +

+
+
+
+
+
Parent topic: Configuring Cross-AZ DR
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0110037559.html b/docs/sdrs/umn/en-us_topic_0110037559.html new file mode 100644 index 00000000..b39e73f4 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0110037559.html @@ -0,0 +1,82 @@ + + +

Creating a Replication Pair

+

Scenarios

You can create replication pairs for desired disks and add the replication pairs to a specified protection group. When you create a replication pair:

+ +

After a replication pair is created, the default name of the DR site disk is the same as the name of the production site disk, but their IDs are different.

+

To modify a disk name, click the disk name on the replication pair details page to switch to the disk details page and modify it.

+
+
+

Prerequisites

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which replication pairs are to be added, click Replication Pairs.

    The operation page for the protection group is displayed.

    +

  4. On the Replication Pairs tab, click Create Replication Pair.

    The Create Replication Pair page is displayed.

    +
    Figure 1 Creating a replication pair
    +

  5. Configure the basic information about the replication pair listed in Table 1.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Protection Group Name

    +

    Indicates the name of the protection group to which the replication pair to be created belongs. You do not need to configure it.

    +

    Protection-Group-test

    +

    Protection Group ID

    +

    Specifies the ID of a protection group.

    +

    619c57e9-3927-48f8-ad14-3e293260b8a0

    +

    DR Direction

    +

    Indicates the replication direction of the protection group to which the replication pair to be created belongs. You do not need to configure it.

    +

    eu-de-01 -> eu-de-02

    +

    Production Site

    +

    Specifies the AZ of the production site.

    +

    eu-de-01

    +

    Production Site Disk

    +

    This parameter is mandatory.

    +

    Select a disk.

    +

    volume-01

    +

    Replication Pair Name

    +

    Indicates the replication pair name. This parameter is mandatory.

    +

    Configure this parameter when you create a replication pair. Then, you can use this name to classify and search this replication pair.

    +

    replication_001

    +
    +
    +

  6. Click Create Now.
  7. On the Confirm page, you can confirm the replication pair information.

    • If you do not need to modify the information, click Submit.
    • If you need to modify the information, click Previous.
    +

  8. Click Back to Protection Group Details Page and query the replication pairs of the protection group.

    If the replication pair status changes to Available or Protecting, the replication pair has been created successfully.

    +

+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0110046974.html b/docs/sdrs/umn/en-us_topic_0110046974.html new file mode 100644 index 00000000..378394a8 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0110046974.html @@ -0,0 +1,23 @@ + + +

Step 3: Enable Protection

+

Scenarios

If you want to enable protection for all resources in a specified protection group, you can perform steps provided in this section.

+

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.

+
Figure 1 Enabling protection
+
+

Prerequisites

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the desired protection group, click Enable Protection.

    Figure 2 Enabling protection
    +

  4. In the displayed dialog box, click Yes.

    Once protection is enabled, data synchronization starts.

    +

    The synchronization time is in direct proportion to the disk capacity. Larger disk capacity requires longer synchronization time.

    +
    +

+
+
+
+
+
Parent topic: Configuring Cross-AZ DR
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0110273585.html b/docs/sdrs/umn/en-us_topic_0110273585.html new file mode 100644 index 00000000..255540da --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0110273585.html @@ -0,0 +1,25 @@ + + +

Modifying Specifications of a Protected Instance

+

Scenarios

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.

+

The following scenarios may involve:

+ +
+

Prerequisites

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which the protected instance specifications are to be modified, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. On the Protected Instances tab, locate the row containing the target protected instance, click More in the Operation column, and choose Modify Production Site Server Specifications or Modify DR Site Server Specifications from the drop-down list.

    Figure 1 Modifying specifications
    +

  5. In the displayed dialog box, select new server type, vCPU, and memory specifications.
  6. (Optional) If you need to modify the specifications of both the production site server and DR site server, select Modify the specifications of both the production and DR site servers. 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.

    Figure 2 Modifying the specifications of both the production site server and DR site server
    +

    This item is deselected by default, indicating that the system modifies the specifications of only the production site server or DR site server.

    +
    +

  7. Click OK.

    To ensure proper server running, do not perform any operations to the servers during specification modifications.

    +

+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0110981899.html b/docs/sdrs/umn/en-us_topic_0110981899.html new file mode 100644 index 00000000..db7e4bd8 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0110981899.html @@ -0,0 +1,117 @@ + + +

Constraints

+

Before using SDRS, learn about the constraints listed in Table 1.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Constraints

Constraint

+

Description

+

Computing

+

Constraints on server types:

+
  • GPU-accelerated, FPGA-accelerated, and C6 ECSs are not supported.
    • Kunpeng ECSs are not supported.
    • x86 ECSs with GPU-accelerated and FPGA-accelerated types are not supported.
    +
+

Replication

+
Constraints on servers:
  • The servers must be from two AZs of the same region.
  • BMSs are not supported.
  • The following types of servers cannot be used to create protected instances:
    • Large Memory (Xen): This type of servers is bound to InfiniBand NICs.
    +
    • Disk Intensive I (Xen): This type of servers has local disks.
    • Disk Intensive II (KVM): This type of ECSs has local disks.
    • Servers already attached with shared EVS disks.
    +
    NOTE:

    You can create a replication pair using Available, shared disks and attach the replication pair to protected instances.

    +

    A replication pair consisting of shared disks can be attached to multiple protected instances.

    +
    +
+
+

Constraints on EVS disks:

+
  • Disks used to create replication pairs cannot be deleted, and the disk snapshot cannot be used to roll back data.
+

Storage

+

This service is applicable for servers using only EVS.

+

Application

+

Storage-based synchronous replication ensures disk data consistency but cannot ensure application consistency. If your applications support crash consistency, you can run and replicate applications.

+

Deployment model

+

VPC migration: Servers at the production site and those at the DR site are in the same VPC. NIC migration and multiple NICs are supported for each server.

+

Backup and restoration

+

Only servers at the production site can be backed up and restored. Servers at the DR site can only be backed up.

+
+
+

If the AZ of the production site becomes faulty, you can use the DR drill function to restore the server services in the AZ.

+
+

Restrictions on Logging In to a Server After You Perform a Planned Failover, Failover, or DR Drill for the First Time

+

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.

+

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 Table 2.

+ +
+ + + + + + + + + + + + + +
Table 2 Production site and DR site servers after a planned failover or failover

N/A

+

Production Site Server

+

DR Site Server

+

Before

+

A

+

B

+

After

+

B

+

A

+
+
+

In this case, the detailed login restrictions are as follows:

+
Scenario 1: Server A runs Windows and does not have Cloudbase-Init installed. After the first time planned failover or failover:
  • 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.
  • 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.
+

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 Table 2 as an example.

+

You can use the password of server A to log in to the production site server or DR site server.

+
+
+
Scenario 2: Server A runs Windows and already has Cloudbase-Init installed. After the first time planned failover or failover:
  • If you choose to use a password for the server login, check whether Cloudbase-Init is started.

    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.

    +

    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.

    +
  • If you choose to use a key pair for the server login, check whether Cloudbase-Init is started.

    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.

    +

    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.

    +
+

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 Table 2 as an example.

+
  • 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.
  • 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.
+
+
+
Scenario 3: Server A runs Linux. After the first time planned failover or failover:
  • 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.

    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.

    +
    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.

    For ECSs running OSs other than CoreOS, the login password does not change after the first-time planned failover or failover.

    +

    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.

    +
    +
    +
  • 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.
+
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0122528555.html b/docs/sdrs/umn/en-us_topic_0122528555.html new file mode 100644 index 00000000..b4c441a4 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0122528555.html @@ -0,0 +1,59 @@ + + +

Performing a DR Drill

+

Scenarios

DR drills can be used to simulate fault scenarios, develop emergency recovery solutions, and verify whether the solutions are applicable and effective. Existing services will not be affected during a DR drill. When a fault occurs, you can use the solutions to rapidly restore services, enhancing service continuity.

+

SDRS provides the DR drill function. You can perform DR drills in a drill VPC (different from the VPC of the DR site). This function allows you to use the disk snapshots of the DR site servers to create drill servers with the server specifications and disk types same as the DR site servers.

+

After the DR drill server is created, the production site server and DR drill server will independently run at the same time (data will not be synchronized between these two servers).

+
+

To ensure that a failover can be properly performed if a disaster happens, you are recommended to perform DR drills regularly to verify that:

+ +
+

Notes

+
+

Prerequisites

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group to which a DR drill is to be added, click DR Drills.

    The operation page for the protection group is displayed.

    +

  4. On the DR Drills tab, click Create DR Drill.

    The Create DR Drill dialog box is displayed.

    +

  5. Configure Name and Drill VPC.

    +

    + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Name

    +

    DR drill name

    +

    DR drill servername

    +

    Drill VPC

    +

    VPC that used for a DR drill. It cannot be the same as the VPC of the DR site server. The value can be Automatically create or Use existing.

    +
    • Automatically create: The system automatically creates a drill VPC and subnets for the protection group.
    • Use existing: The system uses an existing VPC as the drill VPC. If you select to use an existing VPC, the subnet CIDR block of the drill VPC must be consistent with that of the production group VPC.
    +
    NOTE:

    The drill VPC cannot be the same as the VPC of the protection group.

    +
    +

    vpc-f9f7

    +
    +
    +

  6. Click OK.

    After a DR drill is created, you can log in to the DR drill server and check whether services are running properly.

    +

+
+
+
+
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0125068221.html b/docs/sdrs/umn/en-us_topic_0125068221.html new file mode 100644 index 00000000..f1d7681b --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0125068221.html @@ -0,0 +1,17 @@ + + +

What Is SDRS?

+

Storage DR

Storage Disaster Recovery Service (SDRS) provides disaster recovery (DR) services for many cloud services, such as Elastic Cloud Server (ECS) and Elastic Volume Service (EVS). By leveraging techniques, such as storage replication, data redundancy, and cache acceleration, SDRS offers high data reliability and service continuity for users.

+

SDRS protects your service applications by replicating the server data and configurations to a DR site. It allows service applications to start and run at the DR site in the event that the production site server stops. This improves service availability and continuity.

+
Figure 1 Storage DR
+
+

DR and Backup

Differences between DR and backup are as follows:
  • 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.
  • 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.
  • 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.
  • 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.
+
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0288665269.html b/docs/sdrs/umn/en-us_topic_0288665269.html new file mode 100644 index 00000000..78e14d65 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0288665269.html @@ -0,0 +1,158 @@ + + +

Change History

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Released On

+

Description

+

2022-08-31

+

Deleted the yearly/monthly billing from corresponding parameter descriptions.

+

2021-11-17

+

Modified the following content:

+

Added a note in What Are the Precautions If I Log In to the Production Site Server Using a Key Pair?.

+

2019-11-19

+

Modified the following content:

+ +

2019-09-10

+

Modified the following content:

+

Modified the table heading and parameter example in Managing Protected Instance Tags.

+

2019-08-29

+

Added the following content:

+ +

Modified the following content:

+
  • Modified Enable Protection Again to Reprotect in Performing Reprotection.
  • Deleted the restriction that the specifications of the DR site server must be consistent with those of the production site server in Constraints.
+

2019-06-10

+

Accepted for RM-487 and RM-351.

+

2019-06-05

+

Modified the following content:

+ +

2019-05-24

+

Added the following content:

+ +

Modified the following content:

+ +

2019-05-09

+

Deleted the following content:

+
  • What Are the Standards of DR?
  • What Can I Do If an Error Occurred When I Expand the Replication Pair Capacity?
  • What Can I Do When My Protection Group Quotas Are Insufficient?
+

Modified the following content:

+ + +

2019-04-17

+

Modified the following content:

+ +

2019-03-30

+

Added the following content:

+ +

Modified the following content:

+
  • Modified descriptions of modifying the specifications of the production site server and DR site server in Modifying Specifications of a Protected Instance.
  • Deleted concepts of the source end, target end, preferred end, and added the concepts of the production site and DR site.
+

Deleted the following content:

+
  • Section "Performing a Planned Failback"
  • Section "Performing a Failback"
+

2018-11-08

+
Added the following content: +
+

2018-11-07

+

Accepted in OTC 3.2

+

2018-10-27

+

Added the following content:

+

A note in Creating a Replication Pair

+

Modified the following content:

+ +

2018-10-23

+

Added the following content:

+ +

Modified the following content:

+ +

2018-09-29

+

Modified the following content:

+

Prerequisites in Expanding Replication Pair Capacity

+

2018-09-25

+

Added the following content:

+ +

2018-09-11

+

Added the following content:

+ + +

2018-09-03

+

Added the following content:

+ +

Modified the following content:

+ + +

Deleted the following content:

+
  • Section "Adding a NIC"
  • Section "Deleting a NIC"
+

2018-08-08

+

Modified the following content:

+ +

2018-06-30

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/sdrs/umn/en-us_topic_0288665370.html b/docs/sdrs/umn/en-us_topic_0288665370.html new file mode 100644 index 00000000..05ffec76 --- /dev/null +++ b/docs/sdrs/umn/en-us_topic_0288665370.html @@ -0,0 +1,7 @@ + + +

Glossary

+

For details about the glossaries in this document, see Glossary.

+
+
+ diff --git a/docs/sdrs/umn/public_sys-resources/ExpandCollapse.js b/docs/sdrs/umn/public_sys-resources/ExpandCollapse.js new file mode 100644 index 00000000..116ddaab --- /dev/null +++ b/docs/sdrs/umn/public_sys-resources/ExpandCollapse.js @@ -0,0 +1 @@ +var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}}; \ No newline at end of file diff --git a/docs/sdrs/umn/public_sys-resources/avgCompile.js b/docs/sdrs/umn/public_sys-resources/avgCompile.js new file mode 100644 index 00000000..32782268 --- /dev/null +++ b/docs/sdrs/umn/public_sys-resources/avgCompile.js @@ -0,0 +1 @@ +var name1=null;function test1(a){a=a.parentNode;a.className="test1"}function test2(a){a=a.parentNode;a.className="test2"}function test3(a){a=a.parentNode;a.className="test3"}function test4(a){a=a.parentNode;a.className="test4"}function test5(a){a=a.parentNode;a.className="test5"}function test6(a){a=a.parentNode;a.className="test6"}function test7(a){a=a.parentNode;a.className="test7"}function test8(a){a=a.parentNode;a.className="test8"}function test9(a){a=a.parentNode;a.className="test9"}function test10(a){a=a.parentNode;a.className="test10"}function test11(a){a=a.parentNode;a.className="test11"}function test12(a){a=a.parentNode;a.className="test12"}function test13(a){a=a.parentNode;a.className="test13"}function test2(a){a=a.parentNode;a.className="test2"}function test14(a){a=a.parentNode;a.className="test14"}function test15(a){a=a.parentNode;a.className="test15"}function test16(a){a=a.parentNode;a.className="test16"}function test17(a){a=a.parentNode;a.className="test17"}function test18(a){a=a.parentNode;a.className="test18"}function test19(a){a=a.parentNode;a.className="test19"}function test20(a){a=a.parentNode;a.className="test20"}function test21(a){a=a.parentNode;a.className="test21"}function test22(a){a=a.parentNode;a.className="test22"}function test23(a){a=a.parentNode;a.className="test23"}; \ No newline at end of file diff --git a/docs/sdrs/umn/public_sys-resources/caution_3.0-en-us.png b/docs/sdrs/umn/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 00000000..60f60762 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/caution_3.0-en-us.png differ diff --git a/docs/sdrs/umn/public_sys-resources/commonltr.css b/docs/sdrs/umn/public_sys-resources/commonltr.css new file mode 100644 index 00000000..c5480b0a --- /dev/null +++ b/docs/sdrs/umn/public_sys-resources/commonltr.css @@ -0,0 +1 @@ +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/sdrs/umn/public_sys-resources/commonltr_print.css b/docs/sdrs/umn/public_sys-resources/commonltr_print.css new file mode 100644 index 00000000..a5982314 --- /dev/null +++ b/docs/sdrs/umn/public_sys-resources/commonltr_print.css @@ -0,0 +1 @@ +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/sdrs/umn/public_sys-resources/commonrtl.css b/docs/sdrs/umn/public_sys-resources/commonrtl.css new file mode 100644 index 00000000..f261da75 --- /dev/null +++ b/docs/sdrs/umn/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +/*! Copyright (c) Huawei Technologies Co., Ltd. 2020-2022. All rights reserved. */.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/sdrs/umn/public_sys-resources/danger_3.0-en-us.png b/docs/sdrs/umn/public_sys-resources/danger_3.0-en-us.png new file mode 100644 index 00000000..47a9c723 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/danger_3.0-en-us.png differ diff --git a/docs/sdrs/umn/public_sys-resources/delta.gif b/docs/sdrs/umn/public_sys-resources/delta.gif new file mode 100644 index 00000000..0d1b1f67 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/delta.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/deltaend.gif b/docs/sdrs/umn/public_sys-resources/deltaend.gif new file mode 100644 index 00000000..cc7da0fc Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/deltaend.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-arrowdn.gif b/docs/sdrs/umn/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 00000000..84eec9be Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-arrowrt.gif b/docs/sdrs/umn/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 00000000..39583d16 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-caution.gif b/docs/sdrs/umn/public_sys-resources/icon-caution.gif new file mode 100644 index 00000000..079c79b2 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-caution.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-danger.gif b/docs/sdrs/umn/public_sys-resources/icon-danger.gif new file mode 100644 index 00000000..079c79b2 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-danger.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-huawei.gif b/docs/sdrs/umn/public_sys-resources/icon-huawei.gif new file mode 100644 index 00000000..a31d60f8 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-huawei.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-note.gif b/docs/sdrs/umn/public_sys-resources/icon-note.gif new file mode 100644 index 00000000..31be2b03 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-note.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-notice.gif b/docs/sdrs/umn/public_sys-resources/icon-notice.gif new file mode 100644 index 00000000..40907065 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-notice.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-tip.gif b/docs/sdrs/umn/public_sys-resources/icon-tip.gif new file mode 100644 index 00000000..c47bae05 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-tip.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/icon-warning.gif b/docs/sdrs/umn/public_sys-resources/icon-warning.gif new file mode 100644 index 00000000..079c79b2 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/icon-warning.gif differ diff --git a/docs/sdrs/umn/public_sys-resources/note_3.0-en-us.png b/docs/sdrs/umn/public_sys-resources/note_3.0-en-us.png new file mode 100644 index 00000000..57a0e1f5 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/note_3.0-en-us.png differ diff --git a/docs/sdrs/umn/public_sys-resources/notice_3.0-en-us.png b/docs/sdrs/umn/public_sys-resources/notice_3.0-en-us.png new file mode 100644 index 00000000..fa4b6499 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/notice_3.0-en-us.png differ diff --git a/docs/sdrs/umn/public_sys-resources/popup.js b/docs/sdrs/umn/public_sys-resources/popup.js new file mode 100644 index 00000000..a550862e --- /dev/null +++ b/docs/sdrs/umn/public_sys-resources/popup.js @@ -0,0 +1 @@ +var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file diff --git a/docs/sdrs/umn/public_sys-resources/warning_3.0-en-us.png b/docs/sdrs/umn/public_sys-resources/warning_3.0-en-us.png new file mode 100644 index 00000000..def5c356 Binary files /dev/null and b/docs/sdrs/umn/public_sys-resources/warning_3.0-en-us.png differ diff --git a/docs/sdrs/umn/sdrs_06_0400.html b/docs/sdrs/umn/sdrs_06_0400.html new file mode 100644 index 00000000..e16d6731 --- /dev/null +++ b/docs/sdrs/umn/sdrs_06_0400.html @@ -0,0 +1,29 @@ + + +

FAQs

+
+
+ +
+ diff --git a/docs/sdrs/umn/sdrs_06_0402.html b/docs/sdrs/umn/sdrs_06_0402.html new file mode 100644 index 00000000..60727835 --- /dev/null +++ b/docs/sdrs/umn/sdrs_06_0402.html @@ -0,0 +1,21 @@ + + +

What Can I Do When the EIP Cannot Be Pinged After I Perform a Planned Failover for a Protection Group Containing a SUSE Server?

+

Symptom

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.

+
+

Root Cause

After the planned failover, the server NIC name may already change. If the NIC has an EIP bound, the EIP cannot be pinged.

+
+

Handling Method

After the planned failover, delete the /etc/udev/rules.d/70-persistent-net.rules file on the DR site server and then restart it. The procedure is as follows.

+
  1. Log in to the DR site server.

    1. Log in to the management console and click Elastic Cloud Server under Computing.
    2. In the server list, select the DR site server.
    3. Locate the row containing the server and click Remote Login in the Operation column.

      Log in to the server as prompted.

      +
    +

  2. Run the following command to delete the file:

    rm /etc/udev/rules.d/70-persistent-net.rules

    +

  3. Run the following command to restart the DR site server:

    reboot

    +

+
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_06_0403.html b/docs/sdrs/umn/sdrs_06_0403.html new file mode 100644 index 00000000..8846a62a --- /dev/null +++ b/docs/sdrs/umn/sdrs_06_0403.html @@ -0,0 +1,27 @@ + + +

What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?

+

Symptom

The production site server runs the SUSE OS. After users create a DR drill using this server, the NIC names of the DR drill server are different from those of the production site server.

+

The following is an example:

+

A production site server running Novell SUSE Linux Enterprise Server 12 SP3 64-bit has five NICs attached. Log in to the production site server and query the NIC names (eth0 to eth4).

+
Figure 1 Production site server NIC names
+

Log in to the DR drill server and query the NIC names (eth5 to eth9).

+
Figure 2 DR drill server NIC names
+

The NIC names of the DR drill server are different from those of the production site server.

+
+

Root Cause

The NIC names may change when users create a DR drill.

+
+

Handling Method

After the DR drill, delete the /etc/udev/rules.d/70-persistent-net.rules file on the DR drill server and then restart it. The procedure is as follows.

+
  1. Log in to the DR drill server.

    1. Log in to the management console and click Elastic Cloud Server under Computing.
    2. In the server list, select the DR drill server.
    3. Locate the row containing the server and click Remote Login in the Operation column.

      Log in to the server as prompted.

      +
    +

  2. Run the following command to delete the file:

    rm /etc/udev/rules.d/70-persistent-net.rules

    +

  3. Run the following command to restart the DR drill server:

    reboot

    +

+
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_06_0404.html b/docs/sdrs/umn/sdrs_06_0404.html new file mode 100644 index 00000000..a6253738 --- /dev/null +++ b/docs/sdrs/umn/sdrs_06_0404.html @@ -0,0 +1,25 @@ + + +

What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?

+

Symptom

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, users start the DR site server and find that hostname of the DR site server is not updated accordingly.

+
+

Possible Causes

For Linux servers, if you have changed hostname 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.

+
+

Prerequisites

  • The production site server is a Linux server with Cloud-Init installed.
  • hostname of the production site server has been changed.
+
+

Solution 1 (If You Have Not Performed a Planned Failover or Failover)

Set preserve_hostname: false to preserve_hostname: true in the Cloud-Init configuration file /etc/cloud/cloud.cfg to ensure that hostname of the production site server and DR site server are the same after you enable protection.

+

The procedure is as follows:

+
+
  1. Log in to the production site server.
  2. Run the following command to edit the /etc/cloud/cloud.cfg configuration file:

    sudo vim /etc/cloud/cloud.cfg

    +
  3. Modify preserve_hostname.
    • If preserve_hostname: false is already available in the /etc/cloud/cloud.cfg configuration file, change it to preserve_hostname: true.
    • If preserve_hostname: false is unavailable in the /etc/cloud/cloud.cfg configuration file, add preserve_hostname: true before cloud_init_modules.
    +
  4. Perform a planned failover or failover.

    After the planned failover or failover, hostname of the DR site server and production site server are the same.

    +
+

Solution 2 (If You Have Performed a Planned Failover or Failover)

If you have not modified configuration file /etc/cloud/cloud.cfg before the planned failover or failover, log in to the DR site server and manually change hostname of the DR site server to that of the production site server.

+
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_06_0410.html b/docs/sdrs/umn/sdrs_06_0410.html new file mode 100644 index 00000000..fe299cd3 --- /dev/null +++ b/docs/sdrs/umn/sdrs_06_0410.html @@ -0,0 +1,12 @@ + + +

What Is DR?

+

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.

+

The purpose of DR is to ensure maximum service continuity in the event of a natural or human-caused disaster on production systems.

+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_06_0430.html b/docs/sdrs/umn/sdrs_06_0430.html new file mode 100644 index 00000000..2205dcac --- /dev/null +++ b/docs/sdrs/umn/sdrs_06_0430.html @@ -0,0 +1,23 @@ + + +

What Are the Highlights of SDRS?

+

SDRS provides the following features:

+
  • Convenient service recovery

    SDRS provides a management console. You can configure and manage server replication and perform a planned failover or failover.

    +
  • Server replication

    You can establish a replication relationship between the production site and the DR site.

    +
  • Replication on demand

    You can replicate servers in an AZ to another AZ, thereby reducing the costs and complexity of maintaining another data center.

    +
  • Zero impact on applications

    Applications running on servers can be replicated, and the replication will not have any impact on the applications.

    +
  • High RTO and RPO standard

    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 servers 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.

    +

    SDRS provides continuous and synchronous replication for servers to ensure zero recovery point objective (RPO).

    +
  • Crash consistency

    Real-time data synchronization based on storage ensures that data synchronized across two AZs maintains crash consistency.

    +
  • Seamless DR drills

    You can easily perform DR drills without affecting ongoing replication.

    +
  • Flexible failover

    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.

    +
  • Efficient network switchover

    SDRS simplifies program resource management during failovers, including reserving IP addresses and MAC addresses, all of which facilitates efficient network switchovers.

    +
  • Cost effectiveness

    When services are running properly, servers at the DR site are stopped and thereby will not be billed. This greatly reduces the DR TCO.

    +
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_06_0440.html b/docs/sdrs/umn/sdrs_06_0440.html new file mode 100644 index 00000000..9dcf4c89 --- /dev/null +++ b/docs/sdrs/umn/sdrs_06_0440.html @@ -0,0 +1,13 @@ + + +

What Are RPO and RTO?

+

Recovery Point Objective (RPO): the maximum data loss amount tolerated by the system.

+

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.

+
Figure 1 RPO and RTO
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_faq_0004.html b/docs/sdrs/umn/sdrs_faq_0004.html new file mode 100644 index 00000000..2c8ec8ed --- /dev/null +++ b/docs/sdrs/umn/sdrs_faq_0004.html @@ -0,0 +1,12 @@ + + +

Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?

+
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.
  • During a planned failover, NICs of the production site servers and DR site servers will exchange. In this way, servers can be accessed using the same IP addresses and MAC addresses after the planned failover.
  • During a failover, production site servers do not work properly, NICs of the production site servers will be migrated to the DR site servers. The primary NICs of the DR site servers will enter the to-be-used state. Therefore, after a failover, the original production site servers will not have NICs. When users perform reprotection for the protection group after the original production site servers restore, the primary NICs in the to-be-used state detached from the original DR site servers will be attached to the original production site servers. Then, the NICs of the production site servers and DR site servers are exchanged.
+
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_faq_0005.html b/docs/sdrs/umn/sdrs_faq_0005.html new file mode 100644 index 00000000..1589d287 --- /dev/null +++ b/docs/sdrs/umn/sdrs_faq_0005.html @@ -0,0 +1,13 @@ + + +

What Are the Precautions If I Log In to the Production Site Server Using a Key Pair?

+
  • If the production site server runs Windows and uses a key pair for login, ensure that the key pair exists when you create a protected instance or a DR drill. Or, the DR site server or drill server may fail to create, thus causing the creation failure of the protected instance or DR drill.
  • If the production site server runs Linux and uses a key pair for login, you can create a protected instance or DR drill regardless of whether the key pair exists or not. Key pair information will not be shown on the details page of the created DR site server or drill server. But you can use the key pair of the production site server to log in to the created DR site server and drill server.

    If the production site server runs Windows, uses a key pair for login, and is created by an IAM user, only that IAM user can create a protected instance for this server. Other users do not have permissions on the key pair of this server. If they create a protected instance for this server, the creation will fail.

    +
    +
+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_faq_0007.html b/docs/sdrs/umn/sdrs_faq_0007.html new file mode 100644 index 00000000..f4df5c23 --- /dev/null +++ b/docs/sdrs/umn/sdrs_faq_0007.html @@ -0,0 +1,11 @@ + + +

Does SDRS Support Automatic Failover?

+

No. SDRS does not support automatic failover. You need to manually execute a failover via API or on the console.

+
+
+
+
Parent topic: FAQs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_pro_0000.html b/docs/sdrs/umn/sdrs_pro_0000.html new file mode 100644 index 00000000..6e67b18c --- /dev/null +++ b/docs/sdrs/umn/sdrs_pro_0000.html @@ -0,0 +1,23 @@ + + +

Service Overview

+
+
+ +
+ diff --git a/docs/sdrs/umn/sdrs_pro_0003.html b/docs/sdrs/umn/sdrs_pro_0003.html new file mode 100644 index 00000000..d3e8f1d5 --- /dev/null +++ b/docs/sdrs/umn/sdrs_pro_0003.html @@ -0,0 +1,15 @@ + + +

Application Scenarios

+

Cross-AZ DR

SDRS uses storage-layer synchronization and replication to provide cross-AZ DR to ensure data crash consistency and server-level protection with zero RPO. If a source AZ encounters a disaster (such as a fire or an earthquake) or a device fault (such as a software or hardware damage), replications running in the source AZ can quickly restore in the target AZ.

+

For users of stateful applications, such as users of Microsoft Office 365, the data of these users must be stored on the disks of the servers with Microsoft Office 365 deployed. For such users, SDRS is suitable.

+
+

DR Drill

DR drills can be used to simulate fault scenarios, specify the emergency recovery solutions, and verify whether the solutions are applicable and effective. The existing services will not be affected during the DR drill. When a real fault occurs, you can use the solutions to rapidly restore services, enhancing service continuity.

+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/sdrs/umn/sdrs_pro_0008.html b/docs/sdrs/umn/sdrs_pro_0008.html new file mode 100644 index 00000000..c7c7ff7f --- /dev/null +++ b/docs/sdrs/umn/sdrs_pro_0008.html @@ -0,0 +1,38 @@ + + +

Supported DR Scenarios

+

Production Site Is Faulty

  • Description

    The production site has a fault. Services at the production site are affected and cannot be restored using the failover function.

    +
    Figure 1 Production site being faulty
    +
+
  • Solution

    You can use the DR drill function to create DR drill servers at the DR site to resume the services.

    +

    For more information about the DR drill function, see Performing a DR Drill.

    +
+
+

DR Site Is Faulty

  • Description

    The DR site has a fault. Services at the production site are not affected, but the planned failover cannot be performed.

    +
    Figure 2 DR site being faulty
    +
  • Solution

    Contact the customer service to obtain technical support.

    +
+
+

Replication Link Is Faulty

  • Description

    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.

    +
    Figure 3 Replication link being faulty
    +
  • Solution

    You do not need to perform any operations. The DR protection will automatically restore once the replication link fault is rectified.

    +
+
+

Storage Resource at the Production Site Is Faulty

  • Description

    Services at the production site are affected because the storage resource at the production site has a fault.

    +
    Figure 4 Storage resource at the production site is faulty
    +
  • Solution

    Use the failover function to start resources such as servers and disks at the DR site to resume the services.

    +

    For more information about the failover function, see Performing a Failover.

    +
+
+

Storage Resource at the DR Site Is Faulty

  • Description

    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.

    +
    Figure 5 Storage resource at the DR site being faulty
    +
  • Solution

    Contact the customer service to obtain technical support.

    +
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/sdrs/umn/sdrs_pro_0010.html b/docs/sdrs/umn/sdrs_pro_0010.html new file mode 100644 index 00000000..9de7c08e --- /dev/null +++ b/docs/sdrs/umn/sdrs_pro_0010.html @@ -0,0 +1,57 @@ + + +

Relationships with Other Services

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Relationships with other services

Interactive Function

+

Related Service

+

Reference

+

You can use ECSs to create protected instances in SDRS.

+

ECS

+		 +

You can use EVS disks to create replication pairs in SDRS.

+

EVS

+		 +

You can select a VPC for protection groups in SDRS.

+

VPC

+		 +

You can use CTS to record SDRS operations for querying, auditing, or backtracking later.

+

CTS

+		 +

Tags are identifiers of protected instances. You can add tags for protected instances, and classify and search for the protected instances based on these tags.

+

Tag Management Service (TMS)

+		 +
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/sdrs/umn/sdrs_pro_0012.html b/docs/sdrs/umn/sdrs_pro_0012.html new file mode 100644 index 00000000..8b44fc9a --- /dev/null +++ b/docs/sdrs/umn/sdrs_pro_0012.html @@ -0,0 +1,18 @@ + + +

Basic Concepts

+

+
+
+ + +
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/sdrs/umn/sdrs_pro_0013.html b/docs/sdrs/umn/sdrs_pro_0013.html new file mode 100644 index 00000000..b2e5673c --- /dev/null +++ b/docs/sdrs/umn/sdrs_pro_0013.html @@ -0,0 +1,131 @@ + + +

SDRS Basic Concepts

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 SDRS basic concepts

Concept

+

Description

+

Production site

+

A production site is the data center that independently carries services in normal cases. For SDRS, it is the AZ where your servers locate. This parameter is specified when you create a protection group.

+

DR site

+

A DR site is the data center that does not carry services when the production site works properly. It is used to back up data in real time. When the production site fails (planned or unexpected), the DR site can take over the services after a failover. It can reside in the same city as the service management center or in another city.

+

In this version, the production and DR sites must be in different AZs in the same region.

+

Protection group

+

Used to manage a group of servers to be replicated. One protection group is for servers in one VPC. If you have multiple VPCs, you need to create multiple protection groups.

+

Protected instance

+

Indicates a server and its replication server. A protected instance belongs to one protection group. Therefore, the production site and DR site of the protected instance are the same as those of the protected instance's protection group.

+

Replication pair

+

Indicates a disk and its replication disk. A replication pair belongs to one protection group and can be attached to a protected instance in this protection group.

+

Planned failover

+

You can temporarily stop servers at the production site and then perform a planned failover to fail over services from the production site to the DR site. After the planned failover, data synchronization continues, but the DR direction is changed (from the DR site to the production site). Servers and disks at the DR site are ready to start.

+

Failover

+

The system forcibly stops the servers and disks at the production site and sets the servers and disks at the DR site to ready-to-start state. This action affects all the protected instances in the protection group. After the failover, you need to start the servers at the DR site. The protection group status changes to Failover complete, and data synchronization of the protection group stops. You need to enable protection again to restore data synchronization.

+

Enabling protection

+

This operation can be performed after a protection group is created or data synchronization stops. Once the protection is enabled, the data synchronization starts, and the synchronization progress is displayed on the web page. This operation affects all protected instances and replication pairs in the protection group.

+

When you click Enable Protection, the status of the protection group changes to Synchronizing, and Disable Protection is not available.

+

Enabling protection again

+

This operation can be performed after a failover. Once the protection is enabled again, the data synchronization starts, and the synchronization progress is displayed on the web page. This operation affects all protected instances and replication pairs in the protection group.

+

When you click Reprotect after a failover, the status of the protection group changes to Re-protecting, and Disable Protection becomes unavailable.

+

Disabling protection

+

Can be performed after the data synchronization is complete. Once the protection is disabled, the data synchronization stops, and the protection status of the protection group changes to Available.

+

Attaching a replication pair to a protected instance

+

Indicates to attach the two disks in a replication pair to the two servers in a protected instance.

+

Detaching a replication pair from a protected instance

+

Indicates to detach the two disks in a replication pair from the two servers in a protected instance.

+

DR direction

+

Indicates the data replication direction. The data replication is from the production site to the DR site when users create a protection group.

+

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.

+

Protection group status

+

Indicates the status of a protection group when users perform an operation on the protection group, such as creating or deleting a protection group, enabling or disabling protection, or performing a planned failover or failover.

+

For details, see the protection group status section in the Appendixes of Storage Disaster Recovery Service API Reference.

+

Synchronization status

+

Indicates the status of the data replication between the production and DR sites.

+

VPC

+

Indicates the VPC of the protection group. A VPC facilitates internal network management and configuration, allowing secure and quick modifications to networks. The servers in the same VPC can communicate with each other, but those in different VPCs cannot communicate with each other by default.

+

VBD

+

Virtual Block Device (VBD) is the default type of disks. Disks of the VBD type support only simple Small Computer System Interface (SCSI) read and write commands. This disk type applies to enterprise office applications as well as development and testing scenarios.

+

SCSI

+

SCSI is another disk type. Disks of this type support transparent SCSI command transmission to allow the server OS to directly access the underlying storage media. In addition to simple SCSI read and write commands, SCSI disks also support advanced SCSI commands, for example, persistent lock reservation command, suitable for using the lock mechanism to ensure data security for cluster applications.

+

RPO

+

Indicates recovery point objective. It is a service switchover policy, minimizing data loss during DR switchover. The data recovery point is used as the objective to ensure that the data used for DR switchover is the latest backup data.

+

RTO

+

Indicates recovery time objective. It is the target time on the recovery of interrupted key businesses to an acceptable level. RTO is set to minimize an interruption's impacts on the services. 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 servers 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 within 30 minutes.

+

DR drill

+

Is to verify that a DR site server can take over services from a production site server once a failover is performed.

+

In DR drills, you can simulate fault recovery scenarios and formulate emergency recovery plans. When a real fault occurs, the plans can be used to quickly recover services, improving service continuity.

+
+
+
+
+
+
Parent topic: Basic Concepts
+
+
+ diff --git a/docs/sdrs/umn/sdrs_pro_0014.html b/docs/sdrs/umn/sdrs_pro_0014.html new file mode 100644 index 00000000..cc085af6 --- /dev/null +++ b/docs/sdrs/umn/sdrs_pro_0014.html @@ -0,0 +1,22 @@ + + +

Region and AZ

+

Concept

A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

+
  • A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
  • An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.
+

Figure 1 shows the relationship between regions and AZs.

+
Figure 1 Regions and AZs
+
+

Selecting a Region

Select a region closest to your target users for lower network latency and quick access.

+
+

Selecting an AZ

When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.

+
  • For high DR capability, deploy resources in different AZs within the same region.
  • For lower network latency, deploy resources in the same AZ.
+
+

Regions and Endpoints

Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.

+
+
+
+
+
Parent topic: Basic Concepts
+
+
+ diff --git a/docs/sdrs/umn/sdrs_qs_0000.html b/docs/sdrs/umn/sdrs_qs_0000.html new file mode 100644 index 00000000..9e30813f --- /dev/null +++ b/docs/sdrs/umn/sdrs_qs_0000.html @@ -0,0 +1,13 @@ + + +

Getting Started

+
+
+ +
+ diff --git a/docs/sdrs/umn/sdrs_qs_0001.html b/docs/sdrs/umn/sdrs_qs_0001.html new file mode 100644 index 00000000..923e39ad --- /dev/null +++ b/docs/sdrs/umn/sdrs_qs_0001.html @@ -0,0 +1,21 @@ + + +

Configuring Cross-AZ DR

+
+
+ + +
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_0000.html b/docs/sdrs/umn/sdrs_ug_0000.html new file mode 100644 index 00000000..6fe20c46 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_0000.html @@ -0,0 +1,19 @@ + + +

Management

+
+
+ +
+ diff --git a/docs/sdrs/umn/sdrs_ug_cts_0000.html b/docs/sdrs/umn/sdrs_ug_cts_0000.html new file mode 100644 index 00000000..48a72eb0 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_cts_0000.html @@ -0,0 +1,18 @@ + + +

Interconnecting with CTS

+

+
+
+ + +
+
Parent topic: Management
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_cts_0001.html b/docs/sdrs/umn/sdrs_ug_cts_0001.html new file mode 100644 index 00000000..3e893b9b --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_cts_0001.html @@ -0,0 +1,190 @@ + + +

Key SDRS Operations Recorded by CTS

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 SDRS operations that can be recorded by CTS

Operation

+

Resource Type

+

Trace Name

+

Creating a protection group

+

protectionGroup

+

createProtectionGroup

+

Deleting a protection group

+

protectionGroup

+

deleteProtectionGroup

+

Updating a protection group

+

protectionGroup

+

updateProtectionGroup

+

Enabling protection for a protection group (when the protection group is in the Available state)

+

protectionGroup

+

startProtectionGroup

+

Enabling protection for a protection group (when the protection group is in the failed-over state)

+

protectionGroup

+

reprotectProtectionGroup

+

Disabling protection for a protection group

+

protectionGroup

+

stopProtectionGroup

+

Performing a failover for a protection group

+

protectionGroup

+

failoverProtectionGroup

+

Performing a planned failover

+

protectionGroup

+

reverseProtectionGroup

+

Action performed when a job of the protection group failed to submit

+

protectionGroup

+

protectionGroupAction

+

Creating a protected instance

+

protectedInstance

+

createProtectedInstance

+

Deleting a protected instance

+

protectedInstance

+

deleteProtectedInstance

+

Updating a protected instance

+

protectedInstance

+

updateProtectedInstance

+

Attaching a replication pair to a protected instance

+

protectedInstance

+

attachReplicationPair

+

Detaching a replication pair from a protected instance

+

protectedInstance

+

detachReplicationPair

+

Adding a NIC to a protected instance

+

protectedInstance

+

addNic

+

Deleting a NIC from a protected instance

+

protectedInstance

+

deleteNic

+

Modifying the specifications of a protected instance

+

protectedInstance

+

resizeProtectedInstance

+

Creating a replication pair

+

replicationPair

+

createReplicationPair

+

Deleting a replication pair

+

replicationPair

+

deleteReplicationPair

+

Updating a replication pair

+

replicationPair

+

updateReplicationPair

+

Expanding the capacity of a replication pair

+

replicationPair

+

expandReplicationPair

+

Creating a DR drill

+

disasterRecoveryDrill

+

createDrDrill

+

Deleting a DR drill

+

disasterRecoveryDrill

+

deleteDrDrill

+

Updating a DR drill

+

disasterRecoveryDrill

+

updateDrDrill

+
+
+
+
+
+
Parent topic: Interconnecting with CTS
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_cts_0002.html b/docs/sdrs/umn/sdrs_ug_cts_0002.html new file mode 100644 index 00000000..519d4e8e --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_cts_0002.html @@ -0,0 +1,18 @@ + + +

Viewing Traces

+

Scenarios

After you enable CTS, the system starts recording operations on SDRS. You can view operation records of the last seven days on the management console.

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and select Cloud Trace Service under Management & Deployment.
  3. In the navigation pane on the left, choose Trace List.
  4. In the upper right corner of the trace list, click Filter to set the search criteria.
    The following four filters are available:
    • Trace Source, Resource Type, and Search By
      • Select a filter criterion from the drop-down list. Select SDRS for Trace Source.
      • When you select Trace name for Search By, you need to select a specific trace name.
      • When you select Resource ID for Search By, you need to select or enter a specific resource ID.
      • When you select Resource name for Search By, you need to select or enter a specific resource name.
      +
    • Operator: Select a specific operator (at user level rather than tenant level).
    • Trace Status: Available options include All trace statuses, normal, warning, and incident. You can only select one of them.
    • Time Range: You can query traces generated during any time range of the last seven days.
    +
    +
  5. Click on the left of the required trace to expand its details.
    Figure 1 Expanding trace details
    +
  6. Locate a trace and click View Trace in the Operation column.
+
+
+
+
+
Parent topic: Interconnecting with CTS
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_dr_0000.html b/docs/sdrs/umn/sdrs_ug_dr_0000.html new file mode 100644 index 00000000..6a285f19 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_dr_0000.html @@ -0,0 +1,17 @@ + + +

Managing DR Drills

+
+
+ + +
+
Parent topic: Management
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_dr_0001.html b/docs/sdrs/umn/sdrs_ug_dr_0001.html new file mode 100644 index 00000000..4a11ce1c --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_dr_0001.html @@ -0,0 +1,59 @@ + + +

Performing a DR Drill

+

Scenarios

DR drills can be used to simulate fault scenarios, develop emergency recovery solutions, and verify whether the solutions are applicable and effective. Existing services will not be affected during a DR drill. When a fault occurs, you can use the solutions to rapidly restore services, enhancing service continuity.

+

SDRS provides the DR drill function. You can perform DR drills in a drill VPC (different from the VPC of the DR site). This function allows you to use the disk snapshots of the DR site servers to create drill servers with the server specifications and disk types same as the DR site servers.

+

After the DR drill server is created, the production site server and DR drill server will independently run at the same time (data will not be synchronized between these two servers).

+
+

To ensure that a failover can be properly performed if a disaster happens, you are recommended to perform DR drills regularly to verify that:

+
  • The production site data and DR site data are consistent at the moment when you create a DR drill.
  • The services at the DR site can run properly after a failover.
    Figure 1 Performing a DR drill
    +
+
+

Notes

  • When you use a created drill VPC to create a drill, the subnet ACL rule of the drill VPC will be different from that of the VPC of the protection group. You need to manually set them to be the same one if needed.
  • When you create a DR drill, if the VPC of the protection group has a customized routing table and subnets configured, the corresponding routing table will not be automatically created for the drill VPC. You need to manually create it if needed.
  • If the DR site server runs Windows and uses the key login mode, ensure that the key pair of the DR site server exists when you create a DR drill. Otherwise, the DR drill server may fail to create, resulting in the DR drill creation failure.

    If the key pair of the DR site server has been deleted, create a key pair with the same name.

    +
    +
  • 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.
  • After you create a DR drill, modifications to the Hostname, Name, Agency, ECS Group, Security Group, Tags, and Auto Recovery 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.
  • 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.
+
+

Prerequisites

  • The protection group is in the Available, Protecting, Failover complete, Enabling protection failed, Disabling protection failed, Planned failover failed, Re-enabling protection failed, or Failover failed state.
  • 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.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group to which a DR drill is to be added, click DR Drills.

    The operation page for the protection group is displayed.

    +

  4. On the DR Drills tab, click Create DR Drill.

    The Create DR Drill dialog box is displayed.

    +

  5. Configure Name and Drill VPC.

    +

    + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Name

    +

    DR drill name

    +

    DR drill servername

    +

    Drill VPC

    +

    VPC that used for a DR drill. It cannot be the same as the VPC of the DR site server. The value can be Automatically create or Use existing.

    +
    • Automatically create: The system automatically creates a drill VPC and subnets for the protection group.
    • Use existing: The system uses an existing VPC as the drill VPC. If you select to use an existing VPC, the subnet CIDR block of the drill VPC must be consistent with that of the production group VPC.
    +
    NOTE:

    The drill VPC cannot be the same as the VPC of the protection group.

    +
    +

    vpc-f9f7

    +
    +
    +

  6. Click OK.

    After a DR drill is created, you can log in to the DR drill server and check whether services are running properly.

    +

+
+
+
+
+
Parent topic: Managing DR Drills
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_dr_0002.html b/docs/sdrs/umn/sdrs_ug_dr_0002.html new file mode 100644 index 00000000..25da97c7 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_dr_0002.html @@ -0,0 +1,22 @@ + + +

Deleting a DR Drill

+

Scenarios

If a DR drill is no longer used, you can release the virtual resources by deleting the DR drill from the system. When you delete a DR drill, all the drill servers in it are automatically deleted.

+
+

Prerequisites

The DR drill is in the Available, Creation failed, or Deletion failed state.

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group from which a DR drill is to be deleted, click DR Drills.

    The operation page for the protection group is displayed.

    +

  4. On the DR Drills tab, locate the row containing the DR drill to be deleted and click Delete in the Operation column.

    The Delete DR Drill dialog box is displayed.

    +
    Figure 1 Deleting a DR drill
    +

    If you bind an EIP to a DR drill server, the EIP will be unbound from the DR drill server when you delete the DR drill but will not be deleted. You can bind the EIP to another server.

    +
    +

  5. Click Yes.
+
+
+
+
+
Parent topic: Managing DR Drills
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pg_0000.html b/docs/sdrs/umn/sdrs_ug_pg_0000.html new file mode 100644 index 00000000..cd9aa913 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pg_0000.html @@ -0,0 +1,23 @@ + + +

Managing Protection Groups

+
+
+ + +
+
Parent topic: Management
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pg_0001.html b/docs/sdrs/umn/sdrs_ug_pg_0001.html new file mode 100644 index 00000000..c0d2f98c --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pg_0001.html @@ -0,0 +1,21 @@ + + +

Disabling Protection

+

Scenarios

If you want to disable protection for all resources in a specified protection group, you can perform steps provided in this section.

+

Once the protection is disabled, data synchronization for all protected instances in the protection group will stop.

+
+

Prerequisites

  • The protection group has replication pairs.
+
  • The protection group is in the Protecting or Disabling protection failed state.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the desired protection group, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. In the upper right corner of the page, click Disable Protection.
  5. In the displayed dialog box, click Yes.

    Once the protection is disabled, data synchronization between the production site and DR site for all protected instances in the protection group will stop.

    +

+
+
+
+
+
Parent topic: Managing Protection Groups
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pg_0002.html b/docs/sdrs/umn/sdrs_ug_pg_0002.html new file mode 100644 index 00000000..d93b3e62 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pg_0002.html @@ -0,0 +1,54 @@ + + +

Performing a Planned Failover

+

Scenarios

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. Table 1 shows the direction change.

+ +
+ + + + + + + + + + + + + +
Table 1 DR direction change after a planned failover

-

+

Production Site

+

DR Site

+

Before

+

AZ1

+

AZ2

+

After

+

AZ2

+

AZ1

+
+
+

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.

+

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.

+
  • Check the status to ensure that all the servers in the protection group are stopped before the planned failover.
  • During the planned failover, do not start the servers in the protection group. Otherwise, the planned failover may fail.
  • Once a planned failover is complete, data synchronization will not stop, only the synchronization direction will reverse.
  • After the planned failover is complete, the status of the protection group changes to Protecting. Then, you need to switch to the protected instance details page and start the production site server.
+
+
Figure 1 Performing a planned failover
+
+

Notes

For Linux servers with Cloud-Init installed, if you have changed hostname 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.

+

To resolve this problem, see What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Planned Failover or Failover?

+
+

Prerequisites

  • All the servers in the protection group are stopped.
  • The protection group has replication pairs.
  • Protection is enabled for the protection group, and the protection group is in the Protecting or Planned failover failed state.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the desired protection group, click Protected Instances.
  4. On the operation page of the protection group, click Execute Planned Failover in the upper right corner.
  5. In the displayed dialog box, check whether all the servers in this protection group are stopped.

    • If yes, go to step 6.
    • If no, select the servers to be stopped and click Stop.
    +

  6. In the Execute Planned Failover dialog box, click Execute Planned Failover.

    During the planned failover, do not start the servers in the protection group. Otherwise, the planned failover may fail.

    +
    +

+
+
+
+
+
Parent topic: Managing Protection Groups
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pg_0006.html b/docs/sdrs/umn/sdrs_ug_pg_0006.html new file mode 100644 index 00000000..9d701766 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pg_0006.html @@ -0,0 +1,20 @@ + + +

Performing Reprotection

+

Scenarios

Once the failover is started, data synchronization stops. After the failover is complete, the protection group is in the Protection disabled state. To restart data synchronization, perform steps provided in this section.

+
+

Prerequisites

  • The protection group has replication pairs.
  • The protection group is in the Failover complete or Re-enabling protection failed.
  • The DR site server is stopped.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the desired protection group, click Protected Instances.
  4. In the upper right corner of the page, click More and choose Reprotect from the drop-down list.

    The Reprotect dialog box is displayed.

    +

  5. Check whether all the DR site servers in this protection group are stopped.

    • If yes, go to step 6.
    • If no, select the servers to be stopped and click Stop.
    +

  6. On the Reprotect dialog box, click Reprotect.

    During the reprotection, do not start the DR site servers in the protection group. Otherwise, the reprotection may fail.

    +

+
+
+
+
+
Parent topic: Managing Protection Groups
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pg_0007.html b/docs/sdrs/umn/sdrs_ug_pg_0007.html new file mode 100644 index 00000000..4df3cfca --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pg_0007.html @@ -0,0 +1,17 @@ + + +

Deleting a Protection Group

+

Scenarios

If a protection group is no longer used, you can release the virtual resources by deleting the protection group from the system.

+
+

Prerequisites

All the protected instances, DR drills, and replication pairs have been deleted from the protection group.

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group to be deleted, click More and choose Delete from the drop-down list.
  4. In the displayed dialog box, click Yes.
+
+
+
+
+
Parent topic: Managing Protection Groups
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pi_0000.html b/docs/sdrs/umn/sdrs_ug_pi_0000.html new file mode 100644 index 00000000..e0a05102 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pi_0000.html @@ -0,0 +1,29 @@ + + +

Managing Protected Instances

+
+
+ + +
+
Parent topic: Management
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pi_0002.html b/docs/sdrs/umn/sdrs_ug_pi_0002.html new file mode 100644 index 00000000..c6c22667 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pi_0002.html @@ -0,0 +1,29 @@ + + +

Deleting a Protected Instance

+

Scenarios

If you do not need a protected instance, you can delete it to cancel the protection relationship between the servers and the protection group.

+

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.

+
+

Prerequisites

The protected instance is in the Available, Protecting, Failover complete, Creation failed, Enabling protection failed, Disabling protection failed, Planned failover failed, Failover failed, Deletion failed, Re-enabling protection failed, Modifying specifications failed, Invalid, or Faulty state.

+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which the protected instance is to be deleted, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. On the Protected Instances tab, locate the row containing the protected instance to be deleted, click More in the Operation column, and choose Delete from the drop-down list.

    To delete protected instances in batches, select the target protected instances and click Delete above the protected instance list.

    +

    The Delete Protected Instance page is displayed.

    +
    Figure 1 Deleting a protected instance
    +

  5. On the Delete Protected Instance page, select the desired operation.

    • If you select Delete DR site server, do not perform any other operations on the DR site server or its related resources when the system is deleting the DR site server.
    +
    +
    • Delete DR site server
      • 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.
      • 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.
      +
    +
    • Release the EIP bound to the following DR site server

      This parameter is displayed when you select Delete DR site server.

      +
      • If you do not select this option, the DR site server will be deleted, but the EIP bound to the server will be retained.
      • If you select this option, the DR site server will be deleted, and the EIP bound to the server will be released.
      +
    +

  6. Click Yes.
+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pi_0004.html b/docs/sdrs/umn/sdrs_ug_pi_0004.html new file mode 100644 index 00000000..a222ea9e --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pi_0004.html @@ -0,0 +1,22 @@ + + +

Attaching a Replication Pair

+

Scenarios

You can perform steps provided in this section to attach a replication pair to a protected instance. Then, the production site disk is attached to the production site server, and the DR site disk is attached to the DR site server.

+

After protection is enabled for a protection group, when data is written into the production site disk, the same data is written into the DR site disk synchronously.

+
+

Prerequisites

  • The protection group is in the Available or Protecting state.
  • The protected instance is in the Available or Protecting state.
  • The replication pair is in the Available or Protecting state.
  • The non-shared replication pair has not been attached to any protected instance.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which the replication pair is to be attached to the protected instance, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. On the Protected Instances tab, locate the row containing the desired protected instance and click Attach in the Operation column.

    The Attach Replication Pair page is displayed.
    Figure 1 Attaching a replication pair
    +
    +

  5. Select the replication pair to be attached and a desired device name, and click OK.

    The replication pair is attached to the specified protected instance.

    +

+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pi_0005.html b/docs/sdrs/umn/sdrs_ug_pi_0005.html new file mode 100644 index 00000000..eb2b5bd9 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pi_0005.html @@ -0,0 +1,24 @@ + + +

Detaching a Replication Pair

+

Scenarios

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.

+
+

Prerequisites

  • The protection group is in the Available, Protecting, Failover complete, Enabling protection failed, Disabling protection failed, Planned failover failed, or Failover failed state.
  • The protected instance is in the Available, Protecting, Failover complete, Enabling protection failed, Disabling protection failed, Planned failover failed, Failover failed, Deletion failed, Re-enabling protection failed, Modifying specifications failed, Invalid, or Faulty state.
  • The replication pair is in the Available, Protecting, Failover complete, Attaching failed, Detaching failed, Enabling protection failed, Disabling protection failed, Planned failover failed, Failover failed, Deletion failed, Re-enabling protection failed, Expansion failed, Invalid, or Faulty state.
  • The replication pair has been attached to a protected instance.
  • Disks in the In-use state have been attached to the production and DR site servers.
+
  • A system disk (mounted on the /dev/sda or /dev/vda mount point) can be detached from a server only when the server is in the Stopped state. Therefore, stop the server before detaching the system disk.
  • A data disk can be detached from a server online or offline, specifically, when the server is in the Stopped or Running state.

    For details about how to detach a disk online, see Storage > Detaching an EVS Disk from a Running ECS in the Elastic Cloud Server User Guide.

    +
+
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which the replication pair is to be detached from the protected instance, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. On the Protected Instances tab, locate the row containing the desired protected instance and click Detach in the Operation column.

    The Detach Replication Pair page is displayed.
    Figure 1 Detaching a replication pair
    +
    +

  5. Select the replication pair to be detached and click Yes.

    Then, data of the servers in the protected instance will not be written in to the disks in the replication pair.

    +

+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pi_0006.html b/docs/sdrs/umn/sdrs_ug_pi_0006.html new file mode 100644 index 00000000..b5dfa8c8 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pi_0006.html @@ -0,0 +1,21 @@ + + +

Adding a NIC

+

Scenarios

If more NICs are required for your protected instance, you can perform steps provided in this section to add a NIC to the protected instance.

+
+

Prerequisites

  • The protection group is in the Available or Protecting state.
  • The protected instance is in the Available or Protecting state.
  • The subnet of the NIC to be added must belong to the same VPC of the protection group and protected instance.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. On the Protected Instances tab, click the protected instance.

    The protected instance details page is displayed.

    +

  5. Click the NICs tab and click Add NIC.
  6. Select the security group and subnet to be added.

    • You can select multiple security groups. When multiple security groups are selected, the access rules of all the selected security groups apply on the server.
    • If you want to add a NIC with a specified IP address, enter an IP address into the Private IP Address field.
    +
    +

  7. Click OK.
+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pi_0007.html b/docs/sdrs/umn/sdrs_ug_pi_0007.html new file mode 100644 index 00000000..fc9e72bf --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pi_0007.html @@ -0,0 +1,19 @@ + + +

Deleting a NIC

+

Scenarios

A protected instance can have up to 12 NICs, including one primary NIC that cannot be deleted. You can perform steps provided in this section to delete a NIC other than the primary one.

+
+

Prerequisites

  • The protection group is in the Available or Protecting state.
  • The protected instance is in the Available or Protecting state.
  • The primary NIC cannot be deleted.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which a NIC is to be deleted from the protected instance, click Protected Instances.

    The operation page for the protection group is displayed.

    +

  4. On the Protected Instances tab, click the protected instance.

    The protected instance details page is displayed.

    +

  5. Click the NICs tab. Then, click Delete in the row that contains the NIC to be deleted.
  6. Click Yes.
+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_pi_0008.html b/docs/sdrs/umn/sdrs_ug_pi_0008.html new file mode 100644 index 00000000..d32210f3 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_pi_0008.html @@ -0,0 +1,56 @@ + + +

Managing Protected Instance Tags

+

Scenarios

Tags are identifiers of protected instances. You can add tags for protected instances, and classify and search the protected instances based on these tags.

+

You can add a maximum of 10 tags for each protected instance when creating the protected instance or add them on the details page of the created protected instance.

+
+

Context

A tag consists of a tag key and a tag value. Table 1 lists the tag key and value requirements. +
+ + + + + + + + + + + + + +
Table 1 Tag key and value requirements

Parameter

+

Requirement

+

Example

+

Tag key

+
  • Cannot be left blank.
  • Must be unique.
  • Can contain a maximum of 36 characters.
  • Can only consist of digits, letters, hyphens (-), and underscores (_).
+

Organization

+

Tag value

+
  • Can contain a maximum of 43 characters.
  • Can only consist of digits, letters, hyphens (-), and underscores (_).
+

Marketing

+
+
+
+
+

Procedure

You can perform the following operations based on tags:

+
  • Adding tags for a protected instance when you create the protected instance

    For details, see Step 2: Create a Protected Instance.

    +
  • Searching for protected instances by tag on the protected instance list page
    1. Log in to the management console.
    2. Choose Storage > Storage Disaster Recovery Service.
    3. In the pane of the protection group, click Protected Instances.
    4. On the Protected Instances tab, click Search by Tag in the upper right corner of the protected instance list to expand the search area.
    5. Enter the tag of the protected instance to be searched.

      Both the tag key and tag value must be specified. When the tag key or tag value is matched, the system automatically shows the target protected instances.

      +
    6. Click to add a tag.

      The system supports multiple tags and uses the intersection set of all tags to search for protected instances.

      +
    7. Click Search.

      The system searches for protection instances by tags.

      +
    +
  • Adding, deleting, modifying, and searching for tags on the Protected Instance Details page
    1. Log in to the management console.
    2. Choose Storage > Storage Disaster Recovery Service.
    3. In the pane of the protection group, click Protected Instances.
    4. Click the Protected Instances tab and click the name of the specified protected instance.

      The Protected Instance Details page is displayed.

      +
    5. Click the Tags tab and perform desired operations.
      • View tags.

        You can view details of protected instance tags, including the number of tags and the key and value of each tag.

        +
      • Add a tag.

        Click Add Tag in the upper left corner. In the displayed dialog box, enter the key and value of the tag to be added, and click OK.

        +
      • Modify a tag.

        Locate the row containing the tag to be edited and click Edit in the Operation column. In the Edit Tag dialog box, change the key and value of the tag and click OK.

        +
      • Delete a tag.

        Locate the row containing the tag to be deleted and click Delete in the Operation column. In the Delete Tag dialog box, click OK.

        +
      +
    +
+
+
+
+
+
Parent topic: Managing Protected Instances
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_rp_0000.html b/docs/sdrs/umn/sdrs_ug_rp_0000.html new file mode 100644 index 00000000..0b688163 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_rp_0000.html @@ -0,0 +1,19 @@ + + +

Managing Replication Pairs

+
+
+ + +
+
Parent topic: Management
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_rp_0001.html b/docs/sdrs/umn/sdrs_ug_rp_0001.html new file mode 100644 index 00000000..cb1d03a8 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_rp_0001.html @@ -0,0 +1,82 @@ + + +

Creating a Replication Pair

+

Scenarios

You can create replication pairs for desired disks and add the replication pairs to a specified protection group. When you create a replication pair:

+
  • If the protection group is in the Available state, protection is disabled. The production site disk and DR site disk have formed a replication pair, but data synchronization is not started. To start data synchronization, enable protection.
  • If the protection group is in the Protecting state, protection is enabled. After you create a replication pair, data synchronization is automatically started.
+

After a replication pair is created, the default name of the DR site disk is the same as the name of the production site disk, but their IDs are different.

+

To modify a disk name, click the disk name on the replication pair details page to switch to the disk details page and modify it.

+
+
+

Prerequisites

  • The protection group is in the Available or Protecting state.
  • If Server Type of the protection group is ECS, the disks used to create the replication pair are in the Available state.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which replication pairs are to be added, click Replication Pairs.

    The operation page for the protection group is displayed.

    +

  4. On the Replication Pairs tab, click Create Replication Pair.

    The Create Replication Pair page is displayed.

    +
    Figure 1 Creating a replication pair
    +

  5. Configure the basic information about the replication pair listed in Table 1.

    +

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Parameter

    +

    Description

    +

    Example Value

    +

    Protection Group Name

    +

    Indicates the name of the protection group to which the replication pair to be created belongs. You do not need to configure it.

    +

    Protection-Group-test

    +

    Protection Group ID

    +

    Specifies the ID of a protection group.

    +

    619c57e9-3927-48f8-ad14-3e293260b8a0

    +

    DR Direction

    +

    Indicates the replication direction of the protection group to which the replication pair to be created belongs. You do not need to configure it.

    +

    eu-de-01 -> eu-de-02

    +

    Production Site

    +

    Specifies the AZ of the production site.

    +

    eu-de-01

    +

    Production Site Disk

    +

    This parameter is mandatory.

    +

    Select a disk.

    +

    volume-01

    +

    Replication Pair Name

    +

    Indicates the replication pair name. This parameter is mandatory.

    +

    Configure this parameter when you create a replication pair. Then, you can use this name to classify and search this replication pair.

    +

    replication_001

    +
    +
    +

  6. Click Create Now.
  7. On the Confirm page, you can confirm the replication pair information.

    • If you do not need to modify the information, click Submit.
    • If you need to modify the information, click Previous.
    +

  8. Click Back to Protection Group Details Page and query the replication pairs of the protection group.

    If the replication pair status changes to Available or Protecting, the replication pair has been created successfully.

    +

+
+
+
+
+
Parent topic: Managing Replication Pairs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_rp_0002.html b/docs/sdrs/umn/sdrs_ug_rp_0002.html new file mode 100644 index 00000000..8b0f8170 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_rp_0002.html @@ -0,0 +1,26 @@ + + +

Expanding Replication Pair Capacity

+

Scenarios

If the replication pair capacity of your protection groups cannot meet your service requirements, you can perform steps provided in this section to expand the capacity of the specified replication pair. Replication pairs do not support capacity reduction or rollback after a successful capacity expansion.

+

After you expand the capacity of a replication pair, the capacity of both the production and DR site disks are changed.

+
+

Prerequisites

  • The replication pair for which the capacity is to be expanded is in the Available, Protecting, or Expansion failed state.
  • The disks in the replication pair are in the Available or In-use state.
+
  • When the disks in a replication pair are not shared

    If the disks in the replication pair are in the In-use state, the replication pair capacity can be expanded only when online capacity expansion is supported. If online capacity expansion is not supported, Expand Capacity in the Operation column is unavailable.

    +
+
  • When the disks in a replication pair are shared

    The replication pair capacity cannot be expanded online if the disks are in the In-use state.

    +
+
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group for which the capacity of the replication pair is to be expanded, click Replication Pairs.

    The operation page for the protection group is displayed.

    +

  4. On the Replication Pairs tab, locate the row containing the replication pair for which the capacity is to be expanded and click Expand Capacity in the Operation column.

    The Expand Capacity page is displayed.

    +

  5. On the Expand Capacity page, confirm the replication pair information, configure Add Capacity, and click Next.
  6. If you do not need to modify the information, click Submit.

    If you want to modify the information, click Previous and modify the information as required.

    +

+
+
+
+
+
Parent topic: Managing Replication Pairs
+
+
+ diff --git a/docs/sdrs/umn/sdrs_ug_rp_0003.html b/docs/sdrs/umn/sdrs_ug_rp_0003.html new file mode 100644 index 00000000..8abb8189 --- /dev/null +++ b/docs/sdrs/umn/sdrs_ug_rp_0003.html @@ -0,0 +1,25 @@ + + +

Deleting a Replication Pair

+

Scenarios

If a replication pair is no longer used, you can release the associated virtual resources by deleting the replication pair from the system.

+

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.

+
+

Prerequisites

  • The protection group is in the Available, Protecting, Failover complete, Enabling protection failed, Disabling protection failed, Planned failover failed, Failover failed, Deletion failed, or Re-enabling protection failed state.
  • The replication pair is in the Available, Protecting, Failover complete, Creation failed, Enabling protection failed, Disabling protection failed, Planned failover failed, Failover failed, Deletion failed, Re-enabling protection failed, Attaching failed, Expansion failed, Invalid, or Faulty state.
  • The replication pair is not attached to any protected instance. For details about how to detach a replication pair, see Detaching a Replication Pair.
+
+

Procedure

  1. Log in to the management console.
  2. Click Service List and choose Storage > Storage Disaster Recovery Service.

    The Storage Disaster Recovery Service page is displayed.

    +

  3. In the pane of the protection group, click Replication Pairs.

    The operation page for the protection group is displayed.

    +

  4. On the Replication Pairs tab, locate the row containing the replication pair to be deleted and click Delete in the Operation column.

    The Delete Replication Pair dialog box is displayed.

    +
    Figure 1 Deleting a replication pair
    +

    When you delete a replication pair, the production site disk will not be deleted.

    +
    +

  5. Determine the subsequent operation.

    Delete DR Site Disk

    +
    • If you do not select this option, the replication pair relationship between the production site disk and DR site disk will be canceled, and the DR site disk will be retained.
    • If you select this option, the replication pair relationship between the production site disk and DR site disk will be canceled, and the DR site disk will be deleted.
    +

  6. Click Yes.
+
+
+
+
+
Parent topic: Managing Replication Pairs
+
+
+