Performing a side-by-side upgrade

The Automation Suite side-by-side upgrade allows you to perform upgrade operations safely using a parallel environment instead of upgrading in place.

This method allows administrators to switch traffic from the old Automation Suite cluster (i.e, the blue deployment) to the new Automation Suite cluster (i.e., the green deployment) after verifying the new deployment. If you detect a problem, you can roll back to the old deployment quickly.

When performing a side-by side upgrade, the two parallel clusters share one single license.

Requirements

• Both the source and the target environments must meet the same hardware and software requirements.

• You must install the same UiPath® services in the source environment and target environments.

• You must establish connectivity between the source and target environments.

• The target cluster requires its own load balancer.

• If you plan to upgrade from Automation Suite 2022.10 or earlier, and Process Mining is enabled, you must migrate process apps to the new process graph layout before starting the upgrade.

Data migration and responsibilities

Data	Upgrade mechanism
	Status	Responsibility
SQL	Retained	Customer
FQDN	Retained; optional You must choose a new FQDN for the new cluster. Optionally, you can revert to the previous FQDN if needed.	Customer
On-demand bundles	Not migrated Run a script to see which bundles are in the cluster. Manually seeding is needed.	Customer
Certificates	Not migrated You must bring certificates as part of the new cluster installation.	Customer
Cluster configuration	Not migrated You must generate cluster_config.json from the original source cluster so that you map the same services to the new cluster installation.	Customer
Custom alerts and dashboards created by users	Not migrated You must reconfigure the custom alerts and dashboards post-upgrade.	Customer
Application logs / Prometheus streaming configuration created by users	Not migrated You must reconfigure application log and Prometheus streaming.	Customer
Dynamic workloads	Depends on application AI Center training jobs are lost; Skills are retained.	Skills (script needed to be executed after upgrade): UiPath® Training jobs: Customer
Objectstore	Retained	In-cluster objectstore (Ceph): UiPath® External objectstore: Customer
Insights	Retained	UiPath®
MongoDB data	Retained MongoDB data is moved to the target SQL.	UiPath®
RabbitMQ	Not needed	UiPath®
Monitoring (data)	Not needed Monitoring data does not apply to the new cluster.	N/A
Docker registry	Not needed You must install an in-cluster docker registry or bring an external docker registry.	N/A

Process overview

#	Upgrade process steps
1	Prepare the new cluster: Prepare the cluster_config.json file. Install your new cluster (infrastructure and fabric only). Configure the additional CA certificates.
2	Migrate the data to the new cluster: Hydrate the docker registry with the offline upgrade images. Put the cluster in maintenance mode. Clone your source cluster databases. Run the data migration script on the source cluster. If you configured an external objectstore, clone the objectstore buckets.
3	Complete the upgrade: Edit the cluster_config.json file to point to the cloned databases and buckets. Run the service installer on the target cluster. If you did not provide the certificates during installation, update them post-installation. Validate if the target cluster works as expected. Optionally update the FQDN of the target cluster to be same as the FQDN of the source cluster. Alternatively, you can use a new FQDN. Enable the backup on the target cluster.