Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I am upgrading from a version of Linux-HA which supported nice_failback to one that supports auto_failback. How to I avoid a flash cut in this upgrade?

0
Posted

I am upgrading from a version of Linux-HA which supported nice_failback to one that supports auto_failback. How to I avoid a flash cut in this upgrade?

0

To upgrade from a pre-auto_failback version of Heartbeat to one which supports auto_failback, the following procedures are recommended to avoid a flash cut on the whole cluster. • Stop Heartbeat on one node in the cluster. • Upgrade this node. If the other node has nice_failback on in ha.cf then set auto_failback off in the new ha.cf file. If the other node in the cluster has nice_failback off then set auto_failback legacy in the new ha.cf file. • Start the new version of Heartbeat on this node. • Stop Heartbeat on the other node in the cluster. • Upgrade this second node in the cluster with the new version of Heartbeat. Set auto_failback the same as it was set in the previous step. • Start Heartbeat on this second node in the cluster. • If you set auto_failback to on or off, then you are done. Congratulations! • If you set auto_failback legacy in your ha.cf file, then continue as described below… • Schedule a time to shut down the entire cluster for a few seconds. • At the scheduled

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123