Batch Installing Windows Proxy Clients

Updated on 2024-10-29 GMT+08:00

View PDF

Prerequisites

It is recommended that you deploy the disaster recovery gateway and proxy client in the same security group and only allow ECSs within the security group to communication with each other. For details, see Security Group Configuration Examples.
Ensure that the ports listed in Port Description (Asynchronous Replication) are not used.
If the firewall is enabled on the ECS where you want to deploy the proxy client, enable port 59526 on the firewall.
The disaster recovery gateway of 24.9.0 or later has been installed.
The passwords of administrators used for logging in to the production site servers have been obtained. Ensure that all of the production site servers run Windows.
A Windows proxy client has been manually installed. For details, see Installing a Proxy Client.
The network between the cloud disaster recovery gateway server and production site servers (regardless of whether the proxy client is installed or not) is connected, and all the servers on the network can be pinged.

Procedure

In the following example, sdrs_win_24.9.0.xxxx_with_certs.zip is the proxy client package (24.9.0) used for illustration.

Repackage the Windows installation package sdrs_win_24.9.0.xxxx_with_certs.zip by referring to Installing a Proxy Client, and manually install the client. After the installation is successful, log in to the cloud disaster recovery gateway and run the following command to check whether the connection between the client and the gateway has been established:
```
/opt/cloud/sdrs/sidecar/script/cmd_tools.sh list
```
In the following figure, 10.1.0.131 is the IP address of the gateway server, and 10.1.0.39 is the IP address of server where you have manually installed the proxy client.
Generate the Windows installation package sdrs_win_24.9.0.xxxx_with_certs.zip, including the certificate file, on the gateway server. For details, see section "Installing a Proxy Client."
Use the following command to create the windows-host-list.txt file and add the private IP addresses and administrator passwords of the production site servers to the file.

Command format:
```
echo "IP address Administrator AdminPassword drmIP hostagentIP" >> windows-host-list.txt
```
Parameter description:

IP address: The IP address of the production site server used for remote login.

Administrator: The administrator username.

AdminPassword: The password of the administrator account.

drmIp: The IP address of the gateway server.

hostagentIp: The IP address of the primary NIC on the production site server.

A complete example command is as follows:
```
echo "10.1.0.76 Administrator AdminPassword 10.1.0.131 10.1.0.76">> windows-host-list.txt
```
To add information of multiple production site servers, separate the information of each server with a line separator.

Example:
```
echo "10.1.0.76 Administrator AdminPassword 10.1.0.131 10.1.0.76">> windows-host-list.txt
echo "10.1.0.148 Administrator AdminPassword 10.1.0.131 10.1.0.148">> windows-host-list.txt 
```
Check whether all of the information is added to windows-host-list.txt.
```
cat windows-host-list.txt
```
Run the following command as user root to install proxy clients in a batch:
```
/opt/cloud/sdrs/sidecar/script/cmd_tools.sh install --host-list=host_list_file_path --package=package_path --timeout=cmd_timeout_in_s
```
Parameter description:

--host-list: The path of the windows-host-list.txt file.

--package: The path of the Windows installation package sdrs_win_24.9.0.xxxx_with_certs.zip.

--timeout: The command timeout interval, in seconds. The default value is 300. You are advised to set the timeout interval based on the number of production site servers. The formula is as follows: Number of production site servers x 300 (time required for installing a proxy client)

A complete example command is as follows:
```
/opt/cloud/sdrs/sidecar/script/cmd_tools.sh install --host-list=/root/windows-host-list.txt --package=/root/sdrs_win_24.9.0.20240927004242_with_certs.zip --timeout=600
```
Check the command output. If "install SDRS successfully" is returned, the proxy client is successfully installed on all production site servers.
Delete the windows-host-list.txt file to prevent password leakage.
```
rm -rf windows-host-list.txt
```

Troubleshooting

If "error: install SDRS timeout" is returned, the script execution timed out. Perform the following steps on the gateway server to troubleshoot the fault:

Check the "IP address install successfully" information in the command output for production site servers with proxy client successfully installed.
Wait for several minutes and run this command again to check whether there are new servers displayed. If yes, the configured timeout interval is too short, but the background installation is successful. Wait for several more minutes and check whether the remaining servers are successfully installed.
```
/opt/cloud/sdrs/sidecar/script/cmd_tools.sh list
```
If the client still cannot be found in the command output, check whether the client password specified in the windows-host-list.txt file is correct.