# Expanding Single-Node Deployments to Multi-Node Deployments

> to expand an existing single-node deployment to a multi-node deployment while retaining your existing assets

*Source: https://docs.sisense.com/main/SisenseLinux/expanding-single-node-deployments-to-multi-node-deployments.htm*

---

Last updated: June 10, 2026

|  |  |
| --- | --- |
| [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) |
| Enterprise | Cloud     On-Prem |

If you want to expand an existing single-node deployment to a multi-node deployment while retaining your existing assets, you need to take the following steps:

1. Create a backup of your the single instance including any ElastiCubes that were built on the single node.

   `si system backup -include-farm`

   See [Backing up and Restoring Sisense](https://docs.sisense.com/main/SisenseLinux/backing-up-and-restoring-sisense.md) for more information.
2. Build a multi-node instance. See [About Multi-Node Deployments](https://docs.sisense.com/main/SisenseLinux/multi-node-deployments.md) for more information.
3. Copy the backup created in Step 1 from `/opt/sisense/storage/system_backups` in the single node to the same directory in the destination node.
4. Restore the backup in the multi-node machine.  
   `si system restore -name [backup name]`

Contact Sisense Support to assist with this process.