NMMedi ISB/IDR backups stop working once proxy VM is protected through RP4VM replica

NetWorker Module for Meditech version 19.12.0.0.21
RecoverPoint for Virtual Machines version 5.3.SP4.P1(m.193) 

Both ISB and IDR type backups stopped working when NMMedi proxy VM was protected through RP4VM to replicate it to a different site.

The Errors reported in debug nsrmedisv.raw were as follows:

104144 5/26/2026 5:48:02 AM  0 5 15 3416 1496 0 nmmedi_proxy_name nsrmedisv NSR info RPClient(106): addComponentWWN failed with error Found no Consistency Group for the Source Volume 'Source Volume UUID (88 characters long)' on RecoverPoint Cluster 'RP4VM Cluster Name'. Please verify that the Consistency Group protecting the source volume exists and is enabled. -  

167197 5/26/2026 5:48:02 AM  0 5 15 3416 1496 0 nmmedi_proxy_name nsrmedisv NSR info ERROR : isSnappable() failed. Adding all segments in failed list. 

0 5/26/2026 5:48:02 AM  1 0 0 3416 1496 0 nmmedi_proxy_name nsrmedisv NSR notice D:/views/nw/19.12/nsr/db_apps/NMMedi/nmmedisummary.cpp (44) Segment added in the failed list Medi-A E 
112491 5/26/2026 5:48:02 AM  0 5 15 3416 1496 0 nmmedi_proxy_name nsrmedisv NSR info No source LUNs to snapshot for Coherency Group CG_Name 
51415 5/26/2026 5:48:02 AM  5 0 0 3416 1496 0 nmmedi_proxy_name nsrmedisv NSR critical nsrmedisv(2296): Unable to build backup information for CG_Name.

All UUIDs belonging to Meditech segments were verified to be in the Consistency Group

The backups were looking for the incorrect UUID that belonged to the C drive of NMMedi proxy.

• Unprotect the NMMedi proxy VM using the RP4VM UI. Then, power on a copy of the proxy VM at the desired site and rerun the NMMedi backup test.
• In a multisite setup, maintain a dedicated proxy VM for each site.
• Ensure that the proxy VM name specified in the variable exactly matches the VM_NAME in vCenter (case-sensitive).

NSR_RP4VM_NMMEDI_PROXYVM_NAME=VM_NAME

RecoverPoint for Virtual Machines also do not recommend protecting the proxy VM or backup appliance for different reasons.

Please refer to:

RecoverPoint Knowledge Object