Offline Single-node Evaluation Mode

Preparation

1. Make sure that there is enough disk space on the node.
2. Download the full offline bundle (sf.tar.gz) on the chosen server.
3. Download and unzip the new installer (installer.zip) on the primary server.
   Note: Give proper permissions to the folder by running sudo chmod 755 -R <installer-folder>.
4. Make the original cluster_config.json file available on the server.
5. Generate the new cluster_config.json file as follows:
   • If you have the old cluster_config.json , use the following command to generate the configuration file from the cluster.

     cd /path/to/new-installer ./configureUiPathAS.sh config get -i /path/to/old/cluster_config.json -o /path/to/store/generated/cluster_config.json

   • If you do not have the old configuration file, run the following command:

     cd /path/to/new-installer ./configureUiPathAS.sh config get -o /path/to/store/generated/cluster_config.json

     Note: See Advanced installation experience to fill up the remaining parameters.

Execution

Maintenance and Backup

1. Make sure you have enabled the backup on the cluster. For details, see Backing up and restoring the cluster.
2. Connect to server node via SSH.
3. Verify that all volumes have backups in the cluster by running the following command:

   /path/to/new-installer/configureUiPathAS.sh verify-volumes-backup

   Note: The backup might take some time, so wait for approximately 15-20 minutes, and then verify the volumes backup again.
4. To verify if Automation Suite is healthy, run:

   kubectl get applications -n argocd

5. Put the cluster in maintenance mode as follows:
   1. Execute the following command:

      /path/to/new-installer/configureUiPathAS.sh enable-maintenance-mode

   2. Verify that the cluster is in maintenance mode by running the following command:

      /path/to/new-installer/configureUiPathAS.sh is-maintenance-enabled

6. Create the SQL database backup.

Upgrade Infrastructure and Services on Servers

1. Connect to server via SSH.
2. Become root by running sudo su -.
3. Run the following command:

   /path/to/new-installer/install-uipath.sh --upgrade -k -i /path/to/cluster_config.json --offline-bundle "/path/to/sf.tar.gz" --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement -o /path/to/output.json

   /path/to/new-installer/install-uipath.sh --upgrade -f -s -i /path/to/cluster_config.json --offline-bundle "/path/to/sf.tar.gz" --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement -o /path/to/output.json

   Note: This command disables the maintenance mode that you enabled before the upgrade because all services are required to be up during the upgrade. Note that this command also creates a backup of the cluster state and pauses all other scheduled backups.
4. After the successful upgrade and verification, resume the backup scheduling on the node by running the following command:

   /path/to/new-installer/configureUiPathAS.sh resume-scheduled-backups

Rollback on Error

Preparation

1. Create a separate folder to store old bundles, and perform the following operations inside that folder.
2. Download the infra-only offline bundle (sf-infra-bundle.tar.gz) corresponding to the old version on all the nodes.
3. Download and unzip the installer of the old version (installer.zip) on all the nodes.
   Note: Give proper permissions to the folder by running sudo chmod 755 -R <installer-folder>.
4. Create a restore.json file and copy it to the node. For details, see Backing up and restoring the cluster.
5. Verify that the etcd backup data is present on the primary server at the following location: /mnt/backup/backup/<etcdBackupPath>/<node-name>/snapshots.
   • etcdBackupPath - this is the same as the one specified in backup.json while enabling the backup's node-name;
   • node-name - the hostname of the primary server VM.

Cluster Cleanup

1. Copy and run the dedicated script to uninstall everything from that node. For details, see Troubleshooting.
2. Restore all UiPath databases to the older backup created before the upgrade.

Restore Infra on Server Nodes

1. Connect to the server node.
2. Restore infra by running the following command:

   /path/to/older-installer/install-uipath.sh -i /path/to/restore.json -o /path/to/output.json -r --offline-bundle "/path/to/older-version/sf-infra-bundle.tar.gz" --offline-tmp-folder /uipath --install-offline-prereqs --accept-license-agreement --install-type offline

Restore Volumes Data

1. Connect to the server via SSH.
2. Go to the new installer folder.
   Note: The previous infra restore commands were executed using the old installer, and the following commands are executed using the new installer bundle.
3. Disable the maintenance mode on the cluster by running the following command:

   /path/to/new-installer/configureUiPathAS.sh disable-maintenance-mode

4. Verify that maintenance mode is disabled by executing the following command:

   /path/to/new-installer/configureUiPathAS.sh is-maintenance-enabled

5. Copy the restore.json file that was used in the infra restore stage to the new installer bundle folder.
6. Restore volumes from the new installer bundle by executing the following command:

   /path/to/new-installer/install-uipath.sh -i /path/to/new-installer/restore.json -o /path/to/new-installer/output.json -r --volume-restore --accept-license-agreement --install-type offline

7. Once the restore is complete, verify if everything is restored and working properly.
8. During the upgrade, scheduled backups were disabled on this node. To enable them again, run the following command:

   /path/to/new-installer/configureUiPathAS.sh resume-scheduled-backups