An Alarm Is Reported Upon the OceanStor ReplicationDirector Agent Reinstallation After an Abnormally Terminated Installation

6

Ignore this alarm. After the installation is complete, run the lslpp -l "ReplicationDirector-Agent.rte" command to check whether the alarm is in COMMITTED state.

If yes, the installation succeeds.
If no, the installation failed. Delete the newly installed files.

Run the installp -u or installp -C command to delete the files and retry.

Other related questions:
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.

Disaster recovery host types supported by an OceanStor ReplicationDirector agent
An OceanStor ReplicationDirector agent supports the following disaster recovery host types: Windows, Linux, AIX, and HP-UX.

OceanStor ReplicationDirector installation process
The OceanStor ReplicationDirector (mainstream version: V100R003C10) has the following installation components: 1. OceanStor ReplicationDirector server The OceanStor ReplicationDirector server can be installed on a VM or physical server using an ISO image, template, or software package. 2. OceanStor ReplicationDirector agent An OceanStor ReplicationDirector agent needs to be installed on the disaster recovery host if the protected object is an Oracle database, IBM DB2 database, Microsoft SQL Server database, Microsoft Exchange Server email database, or local NTFS file system. The agent can be installed on a VM or physical server using a software package. 3. VRG The host replication software VRG needs to be installed if the protected object is a FusionSphere VM and host replication-based disaster recovery is used.

Why OceanStor ReplicationDirector Fails to Start After Installed On Virtual Machines?
Set the memory and CPU resources allocated to the OceanStor ReplicationDirector virtual machine to fixed sizes instead of dynamic allocation. For details about how to set sizes of memory and CPU resources, see the OceanStor ReplicationDirector standard configuration. Restart the virtual machine and shut down all virtual machines that are not in use.

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