Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux

Technical white paper | Migrating Symantec Veritas Cluster Server to HP Serviceguard for Linux
VCS service group
attributes, which can be
editable by users
Corresponding SG/LX package attributes
(equivalent to some extent) present in
package ASCII file, which can be editable
by users
Descriptions
6 AutoStartPolicy failover_policy In VCS, the “AutoStartPolicy” attribute sets the policy which VCS
uses to select the system to bring a service group online if
multiple systems are available. This attribute has three options:
Order, Load and Priority.
In Serviceguard, the following failover policies can be used to
determine which node should be chosen to bring up a package:
• “configured_node”: ordered list of nodes
• “min_package_node”: A node, which has minimum number of
packages, can be selected to bring up the package or failover
the package.
7
ClusterFailOverPolicy failover_policy In VCS, the “ClusterFailOverPolicy” attribute determines how a
global service group behaves when a cluster faults or when a
global group faults. The attribute can take the following values:
• Manual: The group does not fail over to another cluster
automatically.
• Auto: The group fails over to another cluster automatically if
it is unable to failover within the local cluster or if the entire
cluster faults.
• Connected: The group fails over automatically to another
cluster only if it is unable to fail over within the local cluster.
With HP Metrocluster, a cluster can be divided into sites. The sites
can be located far from each other. Serviceguard provides
different failover policies for the sites:
• “site_preferred_manual”: This failover_policy helps ensure
that the SG/LX package never fails over to another site
automatically.
• “site_preferred”: This failover_policy helps ensure that the
SG/LX package fails over to another site only when it is unable
to fail over within the current site.
8 Enabled auto_run In VCS, the “Enabled” attribute indicates if a service group can be
failed over or brought online.
In Serviceguard, the “auto_run” attribute determines if a package
can be failed over or brought online.
9 Evacuate cmhaltnode –f In VCS, the “Evacuate” attribute initiates an automatic failover
before stopping VCS on the node.
In Serviceguard, the “cmhaltnode –f” command initiates automatic
failover of the packages, provided the global and node switching
is enabled for those packages. This is a default Serviceguard
behavior.
10 FailOverPolicy failover_policy In VCS, the “FailOverPolicy” attribute sets the policy, which VCS
uses, to select a system on which a service group will failover
to if multiple systems exist. This attribute can take the
following values:
• Priority: The system defined as the lowest priority in the
SystemList attribute is chosen.
• Load: The system defined with the least value in the system’s
Load attribute is chosen.
• Round robin: Systems are chosen according to how many
active service groups they are hosting. The system with the
least number of active service groups is chosen first.
In Serviceguard, the “failover_policy” attribute determines which
node be chosen to start or failover the package. Following values
are used for “failover_policy” parameter in Serviceguard cluster:
• “configured_node”: The node which is first in the eligible nodes
list is selected as an adoptive node.
• “min_package_node”: The node which is running the minimum
number of packages is selected as an adoptive node.
14