This site best when viewed with a modern standards-compliant browser. We recommend Firefox Get Firefox!.

Linux-HA project logo
Providing Open Source High-Availability Software for Linux and other OSes since 1999.

USA Flag UK Flag

Japanese Flag

Homepage

About Us

Contact Us

Legal Info

How To Contribute

Security Issues

7th - 10th October 2008 Linux-Kongress in Hamburg will have several sessions on Linux-HA - see you there!

18 August 2008 Heartbeat release 2.1.4 is now out Download it

11 October 2007 NEW educational HA/DR Blog hosted by Alan Robertson

9 April 2007 Check out the Cool Heartbeat Screencasts: Installation, Intro to the GUI Part of the Heartbeat Education project

Last site update:
2008-11-23 11:40:53

Properties

Upgrade Type

Version Issues

Service Outage

Recovery During Upgrade

Exercises Fail-over Logic

Reattach

no

no

no

no

Compatibility Table

Target Version

Oldest Compatible Version

>=2.0.4

2.0.4

Procedure

  1. Set the is_managed_default cluster preference to false

    • # crm_attribute -t crm_config -n is_managed_default -v false

  2. For any resource that has a value for is_managed reset it to false

    • # crm_resource -t primitive -r <rsc_id> -p is_managed -v false

  3. On each node:
    1. Shutdown Heartbeat
    2. Upgrade the Heartbeat program - This may also include upgrading the underlying operating system.
  4. Check the configuration manually or with the crm_verify tool if available.
  5. On each node:
    1. Start the Heartbeat program
  6. Verify the cluster re-detected all resources correctly
  7. Set is_managed_default to true

    • # crm_attribute -t crm_config -n is_managed_default -v true

  8. For any resource that has a value for is_managed reset it to true if desired.

Notes

  1. Always check your existing configuration is still compatible with the version you are installing before starting the cluster.

  2. Versions 2.0.5 and later will actively enforce the DTD they ship with to prevent invalid changes to the configuration.

    If you do not want this to occur, enable the ignore_dtd feature by setting it to true in the top-level cib tag.

    <cib ignore_dtd="true" ... >

See Also

v2/upgrade,