In a two-server cluster, when the primary server fails or is shut down which causes the hierarchies to fail over to the backup server, and the backup server also fails or is shut down before the hierarchies are entirely failed over to the backup server, the following behavior has been detected:

When both servers are rebooted, some of the resources in the hierarchies will be in service on one server and some will be in service on the other server. Some of the higher-level parent resources may not be in service on either server.


After both servers have been restarted and have completed SIOS Protection Suite initialization, select the parent resource in a hierarchy that did not come in-service from the Hierarchy Administration interface and bring it in-service manually. Repeat this task until all hierarchies are in-service.


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