How to create High Priority Service Groups that will failover to a new node and offline Low Priority Service Groups in the process
Article ID: 100022961
Updated On:
Resolution
1) The high priority Service Group needs to be in a FailOver type Service Group.
2) The low priority Service Group needs to be in a Parallel Service Group and both Service Groups need to be offline on both nodes.
(These distinctions are made when you first create and configure the Service Group)
3) Once the Service Groups have been created for each SQL instance within the Veritas Cluster Management - Java Console, highlight the name of the cluster itself inside the directory tree of the Veritas Cluster Management Console (the very first listing in the tree - at the top on the left-hand side). Once this is highlighted, click the Service Groups tab in the pane on the right-hand side.
4) Both Service Groups should be visible here. Click the LINK button and then select the High Priority Service Group by left-clicking onto the Service Group.
5) Next, click onto the Low Priority SQL Service Group.
6) In the window that comes up, select ONLINE REMOTE and then select the option for SOFT.
That should complete the process and you will want to test the configuration to ensure that when the High Priority Service Group fails over to the second node, it automatically brings the low priority Service Group offline on that node, as expected.
1) Your high priority instance of SQL needs to be in a FailOver type Service Group.
2) The low priority instance of SQL needs to be in a Parallel Service Group and both Service Groups need to be offline on both nodes.
(These distinctions are made when you first create and configure the Service Group)
3) Once the Service Groups have been created for each SQL instance within the Veritas Cluster Management - Java Console, highlight the name of the cluster itself inside the directory tree of the Veritas Cluster Management Console (the very first listing in the tree - at the top on the left-hand side). Once this is highlighted, click the Service Groups tab in the pane on the right-hand side.
4) You should see the two SQL Service Groups here. Click the LINK button and then select the High Priority SQL Service Group by left-clicking onto the Service Group.
5) Next, click onto the Low Priority SQL Service Group.
6) In the window that comes up, select ONLINE REMOTE and then select the option for SOFT.
7) Highlight the High priority Service Group and click the Properties Tab
8) Click the All Attributes option and ensure that the attribute ClusterFailover is set to Auto.
2) The low priority Service Group needs to be in a Parallel Service Group and both Service Groups need to be offline on both nodes.
(These distinctions are made when you first create and configure the Service Group)
3) Once the Service Groups have been created for each SQL instance within the Veritas Cluster Management - Java Console, highlight the name of the cluster itself inside the directory tree of the Veritas Cluster Management Console (the very first listing in the tree - at the top on the left-hand side). Once this is highlighted, click the Service Groups tab in the pane on the right-hand side.
4) Both Service Groups should be visible here. Click the LINK button and then select the High Priority Service Group by left-clicking onto the Service Group.
5) Next, click onto the Low Priority SQL Service Group.
6) In the window that comes up, select ONLINE REMOTE and then select the option for SOFT.
That should complete the process and you will want to test the configuration to ensure that when the High Priority Service Group fails over to the second node, it automatically brings the low priority Service Group offline on that node, as expected.
1) Your high priority instance of SQL needs to be in a FailOver type Service Group.
2) The low priority instance of SQL needs to be in a Parallel Service Group and both Service Groups need to be offline on both nodes.
(These distinctions are made when you first create and configure the Service Group)
3) Once the Service Groups have been created for each SQL instance within the Veritas Cluster Management - Java Console, highlight the name of the cluster itself inside the directory tree of the Veritas Cluster Management Console (the very first listing in the tree - at the top on the left-hand side). Once this is highlighted, click the Service Groups tab in the pane on the right-hand side.
4) You should see the two SQL Service Groups here. Click the LINK button and then select the High Priority SQL Service Group by left-clicking onto the Service Group.
5) Next, click onto the Low Priority SQL Service Group.
6) In the window that comes up, select ONLINE REMOTE and then select the option for SOFT.
7) Highlight the High priority Service Group and click the Properties Tab
8) Click the All Attributes option and ensure that the attribute ClusterFailover is set to Auto.
Information on Service Group Dependencies on pages in the Veritas Cluster Server Administrator's Guide.
Issue/Introduction
When working with Service Groups, it may be necessary at times to establish priority levels and link Service Groups together to ensure that priority applications will always have a failover location, even if they must bring other Service Groups offline to do so.
Example:
Two node cluster with two instances of SQL, where the first instance of SQL (Instance 1) is High Priority and must always be available. The second instance of SQL (Instance 2) is low priority and can be offline as necessary. In this situation Instance 1 must always have a failover node and because Instance 2 cannot be online on the same node, then if Instance 1 faults, it will failover to the second node, forcing Instance 2 offline, while bringing Instance 1 online.
Was this article helpful?
Yes
No
Powered by
