UiPath Automation Suite Backup FAQ

UiPath Automation Suite backup FAQ.

UiPath officially supports NFS (Network File System) server for cluster backup to centralized and shared storage for storing backup data. NFS allows multiple servers or nodes within a cluster to access and write data to a common storage location. It is possible to set up the NFS server on any machine and any OS of your choice or alternatively use any PaaS service offered by cloud providers.

The Setting up the external NFS server document provides the instructions specific to configuring the NFS server on the RHEL operating system( Adjust the documentation version as per the setup).

  • For the whole UiPath Automation suite recovery, do we just need cluster state data, etcd, object store etc all directories backup at NFS or only cluster state data backup is sufficient?

UiPath: Our backup solution takes backup of cluster state data, etcd, object store(internal only). If the user is using an external object store, they need to take the backup of the external object-store. Yes, NFS server data is good enough to restore the cluster with the exception of is external object store and SQL server.

  • Is it necessary to take database backup also, to recover the environment-related data (for example – Users, Roles, licenses, packages published, Audit logs etc)

UiPath: Yes, it is required to take the backup of the SQL server as well otherwise restore will fail.

  • Share a common article for the environment covering the backup-recovery process for the whole environment?

UiPath: See Setting up the external NFS server .

  • The whole environment backup and recovery is tested and supported by UiPath?

UiPath: Yes.

  • Suppose a customer has a DU GPU node and task mining node too. Do they need any backup from those servers too?

UiPath: These nodes are used to run some jobs. So they don't need to take any explicit backup of these nodes.

Note:

  • With version 22.10, customers simply need to configure the backup on any of the server nodes. Enabling the snapshot backup. This eliminates the necessity to take node-specific backups.
  • Additionally, ensure to use the correct retention settings, check document Configuring the cluster snapshot .
    • Example: if the backup retention is set to 1 year, it is important to note that your cluster backup data will only be valid for that duration. After that period, you won't be able to use this data for restoring the cluster.
  • Also, the user can not change cluster FQDN, SQL server host URL, or credentials during restore, external object store credentials during restore. So they should take the backup of these resources as well.
​​​​​​