UiPath Documentation
automation-suite
2.2510
true
Automation Suite on EKS/AKS installation guide

Disaster recovery - Installing the secondary cluster

Install secondary cluster in multi-site Active/Passive deployment on EKS/AKS.

Important:

Active/Passive mode is currently available only for EKS.

To install the secondary Automation Suite cluster in an Active/Passive deployment, take the following steps.

  1. Generate or copy the input.json file from the primary Automation Suite cluster. For details, refer to Generating or copying the configuration file of the primary cluster.
  2. Update the input.json file with the parameters specific to the secondary Automation Suite cluster.
  3. Resume the Automation Suite installation.
  4. Switch off inactive products if you use an Active/Passive configuration.

Generating or copying the configuration file of the primary cluster​

Generate a new input.json file or copy it from the primary cluster.

uipathctl manifest get-revision >> /path/to/new/input.json
uipathctl manifest get-revision >> /path/to/new/input.json

Updating the configuration file​

Update the input.json file with the parameters specific to the secondary Automation Suite cluster by taking the following steps:

  1. Turn off the unsupported products.

    Set all the products that are not supported in multi-site to false.

    • For an Active/Passive configuration, disable the products that do not support Active/Passive. For details on Active/Passive support at product level, refer to the table in Disaster recovery - Active/Passive.
    Note:

    Make sure that you enable the platform service as shown in the following example:

    "platform": {
      "enabled": true
    },
    "platform": {
      "enabled": true
    },
    
  2. Update the input.json file with the parameters specific to the secondary cluster. You must provide the kubeconfig of the primary cluster, as it is required for the secondary cluster to access the configurations made on the primary cluster.

    "fqdn" : "<global traffic manager fqdn>"
    "cluster_fqdn": "<fqdn of the secondary cluster>",
    
    "multisite": {
        "enabled": true,
        "primary": false,
        "other_kube_config": "[base64 encoded kubeconfig]"
     }
    "fqdn" : "<global traffic manager fqdn>"
    "cluster_fqdn": "<fqdn of the secondary cluster>",
    
    "multisite": {
        "enabled": true,
        "primary": false,
        "other_kube_config": "[base64 encoded kubeconfig]"
     }
    

    For details, refer to Advanced installation experience.

Resume the installation​

Once the parameters in the previous step are provided or modified in the input.json, you can resume the installation. For details, refer to Installing Automation Suite.

Note:

You must perform the Automation Suite installation using the uipathctl installer. Note that you do not need to generate a new input.json.

Switching off inactive products​

Important:

This step is required. Skipping it may cause some services to fail.

If you deployed Automation Suite in Active/Passive mode, switch off the inactive products using the following command.

uipathctl cluster maintenance enable
uipathctl cluster maintenance enable

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated