Can the OceanStor ReplicationDirector server be deployed on Windows or Linux

1

The OceanStor ReplicationDirector server can be deployed on Windows or Linux.

Other related questions:
How to replace a Windows DHCP server with a Linux DHCP server
If the operating system of an S series switch (except an S1700 switch) that functions as a DHCP server is switched from Windows to Linux, its IP address remains unchanged and no other configuration is required.

OceanStor ReplicationDirector deployment modes
The OceanStor ReplicationDirector (mainstream version: V100R003C10) supports centralized deployment and distributed deployment.
1. Centralized deployment: An OceanStor ReplicationDirector server is deployed on an independent server at the disaster recovery site to manage production and disaster recovery resources. The OceanStor ReplicationDirector server deployed at the disaster recovery site must be able to communicate with the production site.
2. Distributed deployment: Two OceanStor ReplicationDirector servers are deployed at the production site and disaster recovery site to manage site resources. The two ReplicationDirector servers must be able to communicate with each other.

Failed to Start the OceanStor ReplicationDirector Agent in Windows
Log in to the host where database applications reside and check the operation logs of the OceanStor ReplicationDirector Agent. Click the log folder in the installation path of the OceanStor ReplicationDirector Agent. Open rdagent.log. In the log file, search "Starting service failed, because the port is used by other" or "bind failed". If the words are found, the communication port for the OceanStor ReplicationDirector Agent is occupied. Run netstat –ano | findstr "\<59526\>, check whether the communication port for the OceanStor ReplicationDirector Agent is occupied. If the information shown in the above figure is returned, port 59526 is occupied by the process whose ID is 1536. Run tasklist | findstr 1536 to view the process name. If the process is not required by the current services, stop the process. Run the command in 2 to check whether the communication port for the OceanStor ReplicationDirector Agent is released. If the port is released, start the OceanStor ReplicationDirector Agent again. If the process occupying the communication port for the OceanStor ReplicationDirector Agent is required for the current services, open configuration file /conf/rdagent.ini in the installation path of the OceanStor ReplicationDirector Agent, change the value of the port configuration item to an unoccupied port number, save the file, and start the OceanStor ReplicationDirector Agent again. On the OceanStor ReplicationDirector server end, use the new port number to discover the host.

Deployment mode of OceanStor ReplicationDirector in the local high-availability solution
One piece of OceanStor ReplicationDirector is deployed in the local high-availability solution.

Deployment mode of OceanStor ReplicationDirector in the local protection disaster recovery solution
One piece of OceanStor ReplicationDirector is deployed in the local protection disaster recovery solution.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top