- Getting Started
- Requirements
- Best Practices
- Installation
- Updating
- Identity Server
- High Availability Add-on
Upgrading
This section details the steps necessary to upgrade the UiPath High Availability Add-on, including upgrading each respective node and the HAA database(s).
rlcheck
, and rladmin status extra all
.
- Download the node upgrade script by running:
wget http://download.uipath.com/haa/2.0.1/haa-2.0.1.tar.gz
. - Unpack the script by running:
tar -xf haa-2.0.1.tar.gz
. - Make the script executable:
chmod a+x install.sh
. - Run the script:
sudo ./install.sh
.
sudo ./install.sh
. Alternatively, you can add the -y
parameter to respond yes to all.
rladmin upgrade db <db-name>
.During the database upgrade process, the database is restarted. As a result:
• For databases that have replication enabled, a failover is done before the master database restarts to make sure that there is no downtime.
• For databases without replication but with persistence enabled, the database is unavailable during the restart because data is restored from the persistence file. The length of the downtime is different for each persistence option. For example, AOF usually takes longer than an RDB file.
• For databases that have neither replication nor persistence enabled, the database loses all its data after it is restarted.
• Upgrade all instances of a specific CRDB within a reasonable time frame to avoid temporary inconsistencies between the instances.
• Make sure that you upgrade all instances of a specific CRDB before you do global operations on the CRDB, such as removing instances or adding new instances.