Views:

Summary



In DPX 4.5.5 a check was added to NDMPC, to not allow the secondary node to backed up using more than one Master node. If there is already a connection established to NDMPC from a Master, the new connection will be terminated and Error -1 will be seen in the Job Log

Symptoms



After updating to DPX 4.5.5 some backup jobs fail with error <EXCEPTION CATEGORY="BEXEXCEPTION"><CODE>-1</CODE></EXCEPTION> seeing the Job Log causing the Job to fail, while only one master exist in the environment performing a backup of the secondary node.

Job Log
xxx.xxx.xxx.xxx sssvh <date> SNBNCJ_111E  Job context init for NDMPC on host(hostname) failed with exception: <EXCEPTION CATEGORY="BEXEXCEPTION"><CODE>-1</CODE></EXCEPTION>

Corresponding .ncl Log:

<date_time> SNBNCX3069E Extraneous connection from server(nodename@hostname) is not same with current server(xxx.xxx.xxx.xxx)
<date_time> SNBNCX1031E Error calling fn (ms_process_msg) rc (-1)

The error is due to a compare of HostName of the Master  and IP address of the Master, which fails. The connection is then terminated.
 



Resolution



As a temporary workaround the Resolvable Node Name of the master node (Configure Enterprise screen in DPX UI) can be changed to an IP address.

This behavior has been addressed in a DPX Maintenance Update. Please perform a DPX Autoupdate to apply latest DPX release.  (This can be performed from Help | Autoupdate DPX with the DPX Management Console.)
See the Software Update Release Notes for DPX 4.6.0 referencing Issue ID DPSUST-4659.
If the issue continues to occur after applying the update please contact  Catalogic Software Data Protection Technical Support referencing the Issue ID.