Converting an existing installation to multi-site setup

Convert single-site Automation Suite to multi-site Active/Passive deployment on EKS/AKS.

You can convert an existing installation into multi-site by taking the following steps:

1. Convert the standalone Automation Suite cluster into the primary cluster. For details, refer to Converting a standalone cluster into a primary cluster.
2. Install secondary Automation Suite cluster. For details, refer to Disaster Recovery - Installing the secondary cluster.

Note:

Ensure that the certificates are the same on the primary and secondary clusters. This check is not performed or enforced automatically.

Converting a standalone cluster into a primary cluster

To convert an existing Automation Suite cluster into a primary cluster of the multi-site deployment, take the following steps:

1. Update input.json. Add or update fqdn, cluster_fqdn, and enable multisite.

   "fqdn" : "<global traffic manager fqdn>"
   "cluster_fqdn": "<fqdn of the primary cluster>",
   
   "multisite": {
       "enabled": true,
       "primary": true
    }
   

   For details, refer to Advanced installation experience. Update the TLS certificate section to configure the new certificate, ensuring it meets the requirements outlined in the section.

   Note:

   It is recommended to keep the FQDN of your existing Automation Suite setup to avoid reconfiguring all your robots.

2. Reapply the manifest by running the following command:

   uipathctl manifest apply input.json --versions versions.json
   

   Refer to Installing Automation Suite.