How to Create Failback Policies

How to Create Failback Policies

B. Test Preferred Owner

8. In the left column, right mouse click on HOL169-NODE1 and choose Stop
Cluster Service.

9. All groups would now be owned by HOL169-NODE2. You can select the Active Groups under HOL169-NODE2 Node, notice that the Cluster Group and File Shares entries have moved to the HOL169-NODE2 Active Groups.

10. Once the Cluster Service has stopped on HOL169-NODE1 (designated by the red
‘x’), right mouse click it again and select Start Cluster Service.

11. Notice that when HOL169-NODE1 starts up, the File Shares Group are
immediately moved over and now reside on that node.

Note: This setting only takes effect when the Cluster Service starts on the particular
node. If you were to manually move the File shares Group to HOL169-NODE2, it will
stay there and will not automatically moved back to HOL169-NODE1. This is
because Failback policies ONLY come into play when the Cluster Service on the
particular node starts.

Previous Next

Post your questions, comments, feedbacks and suggestions

Contact a consultant