Migrating from 10.7 to a newer 10.7 version
This section applies when migrating from a 10.7 version using dynamic configuration (config-tool) to a new version.
Preparation steps
1. Ensure all your nodes are up and running.
2. Run config-tool diagnostic to ensure:
a. that the configuration state is not broken on each node (nodes can accept changes).
b. that all nodes have the same configuration (last change UUID).
c. that no node need to be restarted (because of a pending change requiring a restart).
Important:
Please restart the nodes that need a restart first.
Migration steps WITHOUT downtime
An upgrade without downtime is possible if not stated otherwise. There can be some cases sometimes where a node running with a newer version won’t be compatible with a node still running with an old version.
1. First start by upgrading the passive nodes
a. Shutdown passive nodes by using the cluster tool shutdown-if-passive command
b. Swap their kit with the new version
c. Restart them
d. Wait until they become PASSIVE
2. Then upgrade the active nodes
a. Shutdown active nodes by using the cluster tool shutdown-if-active command
b. Existing PASSIVE nodes will become ACTIVE (failover)
c. Swap the kit of the shutdown nodes with the new version
d. Restart them
e. Wait until they become PASSIVE
Migration steps WITH downtime
1. Shutdown nodes by using the cluster tool shutdown command
2. Swap their kit with the new version
3. Restart them