When attempting to add or reload a NetApp Storage Replication Adapter (SRA) in VMware Site Recovery Manager (SRM), the following symptoms may occur:
The SRA adapter fails to load or shows an error state in the SRM UI.
The SRM VAMI page may show the SRA as installed, but the SRM interface cannot discover the storage arrays.
Manual health checks of the SRA management endpoint return an HTTP 404 Not Found error.
From VMware-dr.log:2026-05-02T22:33:13.072+08:00 error vmware-dr[01388] [SRM@6876 sub=Storage opID=...] Failed to load SRA from 'netapp:9.13P1'--> SRA Server IP file does not exist.vp_url =-1 Log_output : output = sra_server_url =-1
From drconfig.log from the SRM appliance shows that SRA manager task may complete as shown below:
2026-05-02T22:31:57.167+08:00 verbose drconfig[02287] [SRM@6876 sub=DrConfigSRAManager opID=32617b03-####-####-####-d519######bd-getSraImages:6463:8534] Found '1' SRA containers.2026-05-02T22:31:57.167+08:00 verbose drconfig[01073] [SRM@6876 sub=DrConfigSRAManager ctxID=39aa379d opID=32617b03-####-####-####-d519######bd-getSraImages:6463] OnComplete: SRA manager task is complete.
VMware Live Site Recovery 9.x
This issue is caused by a communication failure between the SRM appliance and the SRA management service on the NetApp ONTAP Tools appliance.
While the network connection to the ONTAP Tools appliance may be active, the specific SRA service container or its internal API gateway is misconfigured or not running, resulting in the HTTP 404 Not Found response when SRM attempts to query the health endpoint.
Restoring communication between SRM and the SRA service is required to resolve this issue.
Run the following command from the SRM appliance to test the SRA health endpoint:
#curl -k -v https://[SRA_SERVER_IP]:8143/api/v1/health
If the response is HTTP 404 Not Found, the service is not active on the NetApp appliance.
If the health check continues to return a 404 error, engage NetApp vendor to investigate the ONTAP Tools service status and ensure the SRA management container is running correctly