VMware Live Site recovery 8.x
VMware Live Site recovery 9.x
The SRA cannot reach HORCMINST=0@X.X.X.X and failed with an error code 1003 indicating a possible network connectivity problem, firewall block, or wrong IP/hostname.
VMware SRM's vmware-dr.log indicates there is an issue on the SRA side.
2025-05-26T07:29:12.743Z info vmware-dr[303336] [SRM@6876 sub=DrTask opID=########-####-####-####-############-discoverArrays:669c] Task 'dr.storage.ArrayManager.discoverArrays176' failed
--> (dr.storage.fault.CommandFailed) {
--> faultCause = (dr.storage.fault.LocalizableAdapterFault) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> code = "########-####-####-####-############.1003",
--> arg = <unset>
--> msg = ""
--> },
--> faultMessage = <unset>,
--> commandName = "discoverArrays"
--> msg = ""
--> }
2025-05-26T07:29:12.729Z error vmware-dr[303729] [SRM@6876 sub=SraCommand opID=########-####-####-####-############-discoverArrays:669c] Command discoverArrays's stderr:
--> Please DO NOT logon to this system, if you are not an authorized user!!!
--> [RMSRA20][Mon May 26 15:29:07 2025]: [RMSRAVER] : 02.05.01( build : Linux/x64 Aug 29 2023 )
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_name] : discoverArrays
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_con_id] : HORCM_REMOTE_LOCAL
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_con_addr] : HORCMINST=0@X.X.X.X
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_outfile] : /tmp/sra-output-24-213
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_statfile] : /tmp/sra-status-25-39
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_logdir] : /srm/sra/log
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_loglvl] : verbose
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_arrayId] :
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_peerId] :
--> [RMSRA20][Mon May 26 15:29:07 2025]: [RMSRATOV] : 600 sec
--> [RMSRA20][Mon May 26 15:29:07 2025]: [RMSRATMU] : 2
--> [RMSRA20][Mon May 26 15:29:07 2025]: [TF_split] :
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_Con_ID] : HORCM_REMOTE_LOCAL
--> [RMSRA20][Mon May 26 15:29:07 2025]: [XML_Con_ADR] : HORCMINST=0@X.X.X.X
--> [RMSRA20][Mon May 26 15:29:09 2025]: [horcmconn_exe] : '/usr/bin/raidqry -IH -l 2>/dev/null 1>/dev/null' returned with RC=251 on HORCMINST=0.
--> [RMSRA20][Mon May 26 15:29:12 2025]: [horcmconn_exe] : '/usr/bin/horcmstart.sh 2>/dev/null 1>/dev/null' failed with RC=3.
--> [RMSRA20][Mon May 26 15:29:12 2025]: [conn_chk_XML] : Can't be connected to HORCMINST=0@X.X.X.X with error(0x00000003).
--> [RMSRA20][Mon May 26 15:29:12 2025]: [exit_main] : returns with [1003]
FYI :
HORCM means Hitachi RAID Command Manager, and this is a background service used by Hitachi's storage software to manage and monitor replication operations like TrueCopy, ShadowImage, and Universal Replicator.
HORCMINST
stands for "HORCM instance".
It identifies a specific instance of the HORCM service, which allows multiple HORCM processes to run on the same server (each managing different replication configurations).
Each instance is tied to a HORCM configuration file, typically named:
horcm0.conf
for instance 0
horcm1.conf
for instance 1
... and so on.
If your SRA configuration has HORCMINST=0@X.X.X.X it means SRA will try to communicate with the HORCM instance 0 on X.X.X.X
1. Verify that the username and password for the specified connection address are correct.
2. Ensure that the username, password, and connection address do not contain any unsupported characters as outlined in the Hitachi Storage Replication Adapter 2.5.1 documentation, specifically under:
If the above fix does not work, then please engage your Hitachi SRA Vendor to investigate the issue accordingly.