Backup storage on the local cluster
General requirements are listed in General requirements.
To better understand how to calculate the hardware configuration for backup storage with the local cluster destination, consider the following examples with RAM and CPU reservations.
Example 1. If you have 1 physical node (1 system+metadata disk and 5 storage disks) and want use the 3+2 encoding mode with the disk failure domain, refer to the table below for the calculations. Note that this configuration has redundancy only in case of a disk failure, the node failure will lead to data unavailability and potential data loss.
Service | The only node |
---|---|
System | 4.5 GB, 3.3 cores |
Storage services |
5 storage disks and 1 metadata on system disk (each takes 0.5 GB and 0.2 cores), that is 3 GB and 1.2 cores in total |
Backup Gateway | 1 GB, 0.5 cores |
Service reservations | 7.5 GB of RAM and 4.6 cores |
Minimum hardware configuration | 12 GB of RAM and 6 cores |
Recommended hardware configuration | 16 GB1 of RAM and 6 cores |
Example 2. If you have 5 nodes (1 system disk, 1 metadata disk, and 10 storage disks) and want to use them for backup storage, refer to the table below for the calculations. Note that three nodes are used for the management node high availability, and each of them meets the requirements for the management node.
Service | Management nodes (nodes 1-3) | Secondary nodes (nodes 4-5) |
---|---|---|
System | 4.5 GB, 3.3 cores | 1.5 GB, 1.1 cores |
Storage services | 10 storage disks and 1 metadata disk (each takes 0.5 GB and 0.2 cores), that is 5.5 GB and 2.2 cores in total | 10 storage disks and 1 metadata disk (each takes 0.5 GB and 0.2 cores), that is 5.5 GB and 2.2 cores in total |
Backup Gateway | 1 GB, 0.5 cores | 1 GB, 0.5 cores |
Service reservations | 11 GB of RAM and 6 cores | 8 GB of RAM and 3.8 cores |
Minimum hardware configuration | 12 GB of RAM and 6 cores | 8 GB of RAM and 4 cores |
Recommended hardware configuration | 242 GB of RAM and 8 cores | 16 GB3 of RAM and 6 cores |