IRIS FailSafe 2.1.x is not a new release of the IRIS FailSafe 1.2 product. Instead, it is a new set of files and scripts that provides many additional possibilities for the size and complexity of a highly available system.
If you wish to migrate a 1.2 system to a 2.1.x system to take advantage of these features, you must upgrade your system configuration. There is no upgrade installation option to automatically upgrade 1.2 to 2.1.x.
This chapter discusses the following:
In 1.2, the unit of failover is the node. In 2.1.x, the unit of failover is the resource group. Because of this, the concepts of node failover, node failback, and node state do not apply to 2.1. x. In addition, all FailSafe scripts differ between the two releases.
Table 1-1 summarizes the differences between the 1.2 and 2.1.x releases.
FailSafe 2.1. x
Much of the data contained in the 1.2 ha.conf file will be used in the 2.1. x database, but the format is completely different. You will configure the database using the FailSafe Manager graphical user interface (GUI) or the cmgr command.
Resource group states (online, offline, pending, maintenance, error).
exclusive, probe, restart
Software links specify application ordering.
Software links are not used for ordering.
Scripts require configuration checksum verification.
There is no configuration checksum verification in the scripts.
Scripts require resource ownership.
Action scripts have no notion of resource ownership.
Scripts do not run in parallel.
Multiple instances of action scripts can be run at the same time.
There is a unit of failover (a resource group) for each highly available service.
With 2.1.x, you can test the hardware configuration with FailSafe diagnostic commands. (See IRIS FailSafe Version 2 Administrator's Guide, for instructions on using FailSafe to test the connections.) These diagnostics are not run automatically when you start FailSafe 2.1.x; you must run them manually.
You can also use the admin ping command to test the serial reset line in 2.1.x. This command replaces the ha_spng command you used with FailSafe 1.2.
# /usr/etc/ha_spng -i 1 -d msc -f /dev/ttyd2 # echo $status
cmgr> admin ping dev_name /dev/ttyd2 of dev_type tty with sysctrl_type msc
If the crsd daemon is running, this command will not run.
See the IRIS FailSafe Version 2 Administrator's Guide for information on using cmgr commands.
FailSafe 1.2 contains a configuration file, ha.conf. In 2.1.x, configuration information is contained in a cluster database at /var/cluster/cdb/cdb.db that is kept in all FailSafe nodes in the pool. You configure the cluster database using the cmgr command or the GUI.
|Note: If you are running 2.1.x in coexecution with CXFS, there may be some CXFS client-only nodes in the cluster that do not contain the cluster database.|
The 2.1.x cluster database is automatically copied to all administration nodes in the pool. The 2.1. x configuration is kept in all administration nodes in the pool.
You must reconfigure your 1.2 system by using the 2.1.x FailSafe Manager GUI or the 2.1.x cmgr command. For information on using these administration tools, see the IRIS FailSafe Version 2 Administrator's Guide.
To update a 1.2 configuration, consider how the 1.2 configuration maps onto the concept of resource groups:
Each resource group contains all the applications that were primary on each node and backed up by the other node.
When you configure a 2.1.x system, you perform the following steps:
Add nodes to the pool.
Define the cluster.
Add nodes to the cluster.
Set HA parameters (FailSafe 2.1. x can be started at this point, if desired).
Define failover policies.
Define resource groups.
Add resources to resource groups.
Put resource groups online.
The guided configuration tasks in the GUI lead you through these steps.
All customized 1.2 scripts must be rewritten for 2.1.x. For more information, see Chapter 3, “Script Changes for Programmers”.
You can keep continuous watch on the state of a cluster using the GUI.
You can query the status of an individual resource group, node, or cluster using either the GUI or cmgr.
For information on performing these tasks, see the IRIS FailSafe Version 2 Administrator's Guide.
After you have defined your nodes, cluster, and resources, you define your resource groups, a task which has no equivalent in FailSafe 1.2. When you define a resource group, you specify the resources that will be included in the resource group and the failover policy that determines which node will take over the services of the resource group on failure.
After you have configured your system, you can start FailSafe services, as described in the IRIS FailSafe Version 2 Administrator's Guide.