Upgrading from pre-9.7.0

When upgrading HANA from pre-9.7.0, the info field will be updated on all systems to allow a resource to be extended to more than one target.

Inspect the info field using the following command:
/opt/LifeKeeper/bin/ins_list -d <HostName> -t <Tag> -f: | cut -d: -f6 | tr '\002' ':'

On systems running LifeKeeper prior to 9.7.0, the output would look something like this:
SPS:HDB00:sync:SiteA:logreplay

With the updated LifeKeeper version, the output will look something like this:
SPS:HDB00:node2/sync:SiteA:node2/logreplay

In the case of a 3 node cluster, the output would look something like this:
SPS:HDB00:node2/sync node3/async:SiteA:node2/logreplay node3/logreplay

How does LifeKeeper automatically update the info field structure after an upgrade?

The info field structure is updated on each node in the following cases:

• When a HANA resource is brought in-service on a system running LifeKeeper 9.7.0 or later, the first successful quickCheck will update the info field, if necessary, on each equivalent system.
• When extending a HANA resource to a system running LifeKeeper 9.7.0 or later, the HANA extend script will update the info field, if necessary, on each equivalent system.
• When taking a HANA resource out of service on a system running LifeKeeper 9.7.0 or later, the HANA remove script will update the info field, if necessary, on each equivalent system.
• When unextending a HANA resource from a node, the HANA delete script removes the information about that node from each equivalent resource info field.
  

The LifeKeeper GUI running on the upgraded server will show the SAP HANA resource on the standby server with an unknown status until quickCheck updates the info field on the standby server.

In the event of a failure during a rolling upgrade, see Failure During Rolling Upgrade of a Pre-9.7.0 Cluster.