Hi, I would like to know what the recommended way is to update a cluster. Every week or so bug fixes and security patches are released for a various parts of the used software. Take for instance mysql: an update might change the binary and/or some data in the internal database.
So for e.g. in a 2 node setup using drbd I would: - Create a snapshot of drbd and rootfs of the slave (as fallback) - Create a snapshot of drbd to work on a copy - Take slave offline (corosync) and mount the copy under the standard path - Proceed with update (with the data copy) - Manually start mysql on slave - Take primary offline, switching manually to slave - Proceed with update on primary on the actual data - Start primary node switching manually back from slave - Get rid of slave "copy" snapshots and start slave node Sounds complex and thus error prone to me. The problem seems to me that e.g. in a release upgrade scenario the mysql binary must match its data version for it to work correctly. Any suggestions? Thanks, Stefan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
