DSA impd-notify failed to start

Products

• CA Identity Suite

Issue/Introduction

After planning CR to deploy the CHF1 and due to that taking offline image backup of all 4 VAPP server. hostname-impd-notify failed to start 

Environment

Vapp 14.4 CP2

Cause

All provisioning Directory DSAs are setup with MW-DISP recovery replication out of the box and by default.

Sometimes if the DSA is not offline for a longer period of time.  Vapp does not update the .dp file that keeps track of the last communication times between DSAs for replication. As the DSA could not find correct time, it fails to start assuming the DSA was out of sync from it's peer for long time to maintain data integrity.

Resolution

On the nodes where hostname-impd-notify are failing to start, run following as 'dsa' user 

dxdisp hostname-impd-notify