Converting an existing installation to multi-site setup

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, see Converting a standalone cluster into a primary cluster.
2. Install secondary Automation Suite cluster. For details, see 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 aprimary cluster of the multi-site deployment, take the following steps:

1. Add or modify the required cluster_config.json parameters on the first server node. For more details, see Advanced installation experience.

   {
     "fabric": {
       "redis": {
         "ha": true,
         "license": "xyz" //base64 encoded redis license
       }
     },
     "cluster_fqdn": "automationsuite-primary.mycompany.com",
     "multisite": {
       "enabled": true,
       "primary": true,
       "other_site_kubeconfig": xxx,  //another cluster kubeconfig
     },
     "fixed_rke_address": "automationsuite-primary.mycompany.com"
   }
   

   Note:

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

Online

Configure the infrastructure on the first server node

1. Navigate to the installer folder:

   cd /opt/UiPathAutomationSuite/{version}/installer
   

2. Run the following command on the first server node:

   ./install-uipath.sh -i cluster_config.json -o output.json -k --skip-compare-config --force-update-fqdn --accept-license-agreement
   

Configuring the infrastructure on the remaining cluster nodes

1. Navigate to the installer folder:

   cd /opt/UiPathAutomationSuite/{version}/installer
   

2. Copy the cluster_config.json file from the first server node to all the other nodes.

3. Run the following command on all the other nodes:

   ./install-uipath.sh -i cluster_config.json -o output.json -k -j <node_type> --skip-compare-config --force-update-fqdn --accept-license-agreement
   

   Note:

   Replace <node_type> with the appropriate node type:

   • server – for other server nodes
   • agent – for agent nodes
   • task-mining – for Task Mining node
   • gpu – for GPU node
   • asrobots – for Automation Suite Robots node

Configuring the fabric and services on the first server node

To configure the fabric and services on the first server node, run the following command:

./install-uipath.sh -i cluster_config.json -o output.json -f -s --skip-compare-config --force-update-fqdn --accept-license-agreement

Offline

Configure the infrastructure on the first server node

1. Navigate to the installer folder:

   cd /opt/UiPathAutomationSuite/{version}/installer
   

2. Run the following command on the first server node:

   ./install-uipath.sh -i cluster_config.json -o output.json -k --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --skip-compare-config --force-update-fqdn --accept-license-agreement
   

Configuring the infrastructure on the remaining cluster nodes

• Navigate to the installer folder:

  cd /opt/UiPathAutomationSuite/{version}/installer
  

• Copy the cluster_config.json file from the first server nodes to all other nodes.

• Run the following command on all the other nodes:

  ./install-uipath.sh -i cluster_config.json -o output.json -k -j <node_type> --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /uipath/tmp --accept-license-agreement
  

  Note:

  Replace <node_type> with the appropriate node type:

  • server – for other server nodes
  • agent – for agent nodes
  • task-mining – for Task Mining node
  • gpu – for GPU node
  • asrobots – for Automation Suite Robots node

Configuring the fabric and services on the first server node

To configure the fabric and services on the first server node, run the following command:

./install-uipath.sh -i cluster_config.json -o output.json -f -s --install-type offline --skip-compare-config --force-update-fqdn --accept-license-agreement