Forum Discussion

Tilin_vcs's avatar
Tilin_vcs
Level 2
12 years ago

how to configure service group!!!!

 

hello:
 
Anyone have an idea how to configure the following
 
I have 2 nodes (node1 Production) (Node 2 Quality) VCS 6.0
 
For performance of HW need to configure the service group of production to realize that when one switchover or failover to node 2 the Quality Service Group take offline on node 2 before lifting the production service group on this node 2
business continuity
Cluster Server
Configuring
Solaris
  • mikebounds's avatar
    mikebounds
    12 years ago

    Command to create dependency is:

    hagrp -link SG_Production SG_QUA offline local

    This means SG_QUA must be offline on node2 to be able to online or switch SG_Production to node2, so you will get a 'group dependency violation error' if you try to do this as the expectation is that if you manually switch or online SG_Production on node2, that you manually offline SG_QUA first, BUT, if SG_Production faults (or its system fails) and tries to switch to node2, then the service group dependency means VCS will automatically offlines SG_QUA so that SG_Production can online on node2 and in this instance if SG_QUA can only run on node2 (only system in SystemList), it will stay down, but if SG_QUA is defined in both systems then SG_QUA  would switch to node1 if it is available.

    When SG_Production is running on node2 (after a failover), you would need an outage for SG_Production to switch back to node1, therefore it is recommended you leave it there indefinately until it fails again and switches back to node1.  Therefore it is recommended you allow SG_QUA  to run on node1, otherwise SG_QUA is down for a long period, or you create an unecessary outage for SG_Production if you switch it back to node1.
     
    Mike
     

7 Replies

Sort By
  • Tilin_vcs's avatar
    Tilin_vcs
    Level 2
    12 years ago

    arangari: 

    Thanks for answering but I did not understand your answer, could you please explain

  • Armando_Crisafo's avatar
    Armando_Crisafo
    Level 2
    12 years ago

    Hi,

    Offline local is the service group dependency that can help in this case. In particular:

    • The Child (PRODsg) can come online anywhere the parent is offline
    • The Parent (TESTsg) can come online only where child is offline

    Failover example:

    • The child faults and fails over to an available system
    • If the selected target system for the child is not running the parent, then the parent continues to run
    • If the selected target has the parent is online:
    1. The parent is taken offline
    2. The child is brought online
    3. The parent then restarts on a system different from the child's system

     

    Thanks,
    Armando

     

     

     

  • Tilin_vcs's avatar
    Tilin_vcs
    Level 2
    12 years ago

     

    I have 2 nodes
     
    node1 is running (Service Group called SG_Production)
    node2 is running (Service Group called SG_QUA)
     
    I need to realize that when switchover or failover to node2 SG_Production, SG_QUA automatically turns off, so you can use all the hardware resources on node2 SG_Production.
  • arangari's avatar
    arangari
    Level 5
    12 years ago

    SG_QUA should have node2 as the only system in its SystemList. 

  • mikebounds's avatar
    mikebounds
    Level 6
    12 years ago

    Command to create dependency is:

    hagrp -link SG_Production SG_QUA offline local

    This means SG_QUA must be offline on node2 to be able to online or switch SG_Production to node2, so you will get a 'group dependency violation error' if you try to do this as the expectation is that if you manually switch or online SG_Production on node2, that you manually offline SG_QUA first, BUT, if SG_Production faults (or its system fails) and tries to switch to node2, then the service group dependency means VCS will automatically offlines SG_QUA so that SG_Production can online on node2 and in this instance if SG_QUA can only run on node2 (only system in SystemList), it will stay down, but if SG_QUA is defined in both systems then SG_QUA  would switch to node1 if it is available.

    When SG_Production is running on node2 (after a failover), you would need an outage for SG_Production to switch back to node1, therefore it is recommended you leave it there indefinately until it fails again and switches back to node1.  Therefore it is recommended you allow SG_QUA  to run on node1, otherwise SG_QUA is down for a long period, or you create an unecessary outage for SG_Production if you switch it back to node1.
     
    Mike