Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- What's New
- Product Bulletin
- Service Overview
- Getting Started
-
User Guide
- Permissions Management
-
Asynchronous Replication
- Managing a Replica Pair
- Managing a Protection Group
- Managing Protected Instances
- Managing DR Drills
- Managing Clients
- Synchronous Replication Management (for Installed Base Operations)
- Appendixes
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
SDRS APIs
- Job
- API Version
- Active-Active Domain
-
Protection Group
- Creating a Protection Group
- Querying Protection Groups
- Querying the Details of a Protection Group
- Deleting a Protection Group
- Changing the Name of a Protection Group
- Enabling Protection or Enabling Protection Again for a Protection Group
- Disabling Protection for a Protection Group
- Performing a Failover for a Protection Group
- Performing a Planned Failover for a Protection Group
-
Protected Instance
- Creating a Protected Instance
- Deleting a Protected Instance
- Querying Protected Instances
- Querying Details About a Protected Instance
- Changing the Name of a Protected Instance
- Attaching a Replication Pair to a Protected Instance
- Detaching a Replication Pair from a Protected Instance
- Adding an NIC to a Protected Instance
- Deleting an NIC from a Protected Instance
- Modifying the Specifications of a Protected Instance
- Batch Creating Protected Instances
- Batch Deleting Protected Instances
- Replication Pair
- DR Drill
- Tag Management
- Task Center
- Tenant Quota Management
- Appendixes
- Change History
- SDK Reference
-
FAQs
- Common Problems
-
Synchronous Replication (for Installed Base Operations)
- Do I Need to Manually Create DR Resources?
- What Can I Do When the EIP Cannot Be Pinged After I Perform a Switchover for a Protection Group Containing a SUSE Server?
- What Can I Do If the NIC Names of the DR Drill Server and Production Site Server Are Different?
- What Can I Do If hostname of the Production Site Server and DR Site Server Are Different After a Switchover or Failover?
- Why NICs of DR Site Servers Are Not Displayed After I Perform a Failover?
- What Are the Precautions If the Production Site Server Uses the Key Login Mode?
- What Should I Pay Attention to When Logging In to the Server After the First Time Ever I Executed a Switchover, Failover, or DR Drill?
- How Do I Use a Resource Package?
-
Asynchronous Replication
- How Do I Handle the drm Process Start Failure?
- Failed to Install and Configure Disaster Recovery Gateway When Process drm Exists But Port 7443 Is Not Listened
- What Can I Do If the Name of a Production Site Server or the Host Name Reported by the Gateway Is Incorrect and Always Displayed as "localhost"?
- What Can I Do If the Disaster Recovery Site VM Is Not Started After a Switchover?
- How Do I Obtain the Installation Package on a Production Site Server from the Gateway?
- How Do I Enable or Disable an ECS Firewall and Add a Port Exception to the Firewall?
- Why Can't I Find the Disaster Recovery Gateway When Associating a Replica Pair with It?
- Why Is No Production Site Server Displayed When I Create Protected Instances?
- Videos
- Glossary
- Best Practices
- General Reference
Copied.
Upgrading a Proxy client
Scenarios
When a new version of the proxy client is released, you need to upgrade the existing proxy client deployed.
Procedure
If the production services are running at the production site, upgrading the proxy client will resynchronize data.
Linux
In the following example, sdrs_xxxx_24.9.0.xxxx.tar.gz is the package (24.9.0) used to upgrade the proxy client.
- Obtain the proxy client package and upload it to a directory on the target server. Ensure the package integrity by comparing the SHA256 values in advance.
- IDC-to-cloud: Click the link on the console to download the package and upload it to the target server.
- Cross-region and Cross-AZ: Select the OS type and version of your production site server on the console and copy the command provided. Then, log in to the production server, go to the desired directory, and paste and run the command to obtain the package.
- IDC-to-cloud: Click the link on the console to download the package and upload it to the target server.
- In the directory containing the package, run the following command as user root to decompress the package:
tar -zxvf sdrs_xxxx_24.9.0.xxxx.tar.gz
- Go to the directory containing the upgrade script.
cd sdrs_xxxx_24.9.0.xxxx
- Upgrade the proxy client.
sh upgrade.sh
If the command output contains the following information, the proxy client has been upgraded:... Upgrade SDRS successfully.
Windows
In the following example, sdrs_xxxx_24.9.0.xxxx.zip is the package (24.9.0) used to upgrade the proxy client on Windows Server 2019.
- Obtain the proxy client package and upload it to a directory on the target server. Ensure the package integrity by comparing the SHA256 values in advance.
- IDC-to-cloud: Click the link on the console to download the package and upload it to the target server.
- Cross-region and Cross-AZ: Select the OS type and version of your production site server on the console and copy the command provided. Then, log in to the production server, go to the desired directory, and paste and run the command to obtain the package.
- IDC-to-cloud: Click the link on the console to download the package and upload it to the target server.
- In the directory containing the package, right-click the package to decompress it.
- Double-click the decompressed directory to go to the directory containing the upgrade script.
- Double-click upgrade.bat to run the script.
- Enter y to continue the upgrade if the confirmation information is displayed.
- If the command output contains the following information, the proxy client has been upgraded: (The cmd window automatically exits after the upgrade is complete.)
... Upgrade SDRS successfully.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot