Problem:
If an ISM node crashes, shuts down or reboots whilst a replication or snapshot data flow is being activated, Protector will indicate that the job(s) associated with the activation has failed.
Solution:
Protector is resilient to this type of failure. Try retriggering the operations on the associated data flow(s) once the ISM has finished rebooting.