Before upgrading IBM® Runbook Automation
to a new code version, it is recommended to temporarily disable the replication. This prevents an
old code level from reading data schemas that might be introduced in a newer version of RBA. It also
ensures that potential data migration tasks are handled correctly during deployment.
About this task
The recommended upgrade scenario includes the following steps.
Procedure
-
Back up the current data.
-
Disable the replication between site 'A' and site 'B' by invoking the script from Replication configuration with the delete command:
./couchdbReplication.sh delete
-
Install the new version of Runbook Automation on site 'A'. Site 'B' stays
operational and actively in use.
-
Verify that the upgrade on site 'A' was successful by opening the Runbook Automation User Interface.
-
Install the new version of Runbook Automation on site 'B'. Site 'A' stays
operational and actively in use, but lacks the data that is created on site 'B' while the
replication was not active.
-
Verify that the upgrade on site 'B' was successful by opening the Runbook Automation User Interface.
-
Resume the replication between site 'A' and site 'B' by invoking the script from Replication configuration with the setup command:
./couchdbReplication.sh setup
Results
By following this upgrade scenario, there is always one side up and running. The only impact
is reduced redundancy during the upgrade and potential data inconsistencies. This is eventually
resolved after resuming the replication.