Metrocluster rolling upgrade?

[Olivier Masse]

Hi

I'm planning to upgrade from Metrocluster CA EVA 2.0 to 4.0 this fall, as my current versions of Metrocluster and Command View are quickly falling behind.

However, the documentation doesn't have any procedure on how to perform a rolling upgrade. My guess is that I can simply upgrade the Metrocluster package and reconfigure it from scratch, one node at a time?

I'll have to start by setting up a test environment to simulate the upgrade, but anyone did this already and would have suggestions or best practices to offer?

Points will be awarded, thanks.

[Steven E. Protter]

Shalom,

A rolling update is a rolling update.

Officially an update of the serviceguard software itself requires downtime.

1) Fail all packages over to one of the nodes or clusters.

2) Remove one location from the cluster/group

3) Perform upgrades and reboots.

4) Downtime --- Bring up all services at the upgraded location. You will need to cmhaltnode the current running location.

5) Repeat step 3.

This can be done with a minimum of downtime, but users should be notified.

Backups should be performed so that if there is a problem it does not degrade into a service disaster.

SEP

[Olivier Masse]

I'm talking here about updating Metrocluster, not ServiceGuard itself.

Thanks