If you have multiple cluster networks, IP Addresses shouldn’t be set up on the same network that DataKeeper Volume resources are using for replication. Network errors may cause the DataKeeper mirror to go into a Paused state. If the network error also causes the cluster IP Address resource to fail its health checks, any resource hierarchy that contains both a DataKeeper Volume resource and the cluster IP Address will not be brought Online on remote nodes due to the DataKeeper Volume mirror state being in a non-Mirroring state.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment