On 2016-11-23 02:23, Ulrich Windl wrote:
I'd recommend making a backup of the DRBD data (you always should, anyway), the shut down the cluster, upgrade all the needed components, then start the cluster again. Do your basic tests. If you corrupted your data, re-create DRBD from scratch. Then test again. If your data is currupted again, the new version has a problem. Then you should go back to your old version (You have desaster-suitable backups, right?).
Very funny: run a full backup a small 100TB live mail spool for a kernel upgrade. When the cluster fscks it up, run a full restore. While the mail spool is highly unavailable.
How about an easier solution: never install any patches. Or better yet don't use pacemaker. Hilarious.
Dima _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
