The tables below can be used to calculate the required disk space for backups.
Example:
A Server Edition deployment has 2500 users with 150 nodes and 500 hunt groups. The Primary Server is an R620 machine.
From the server disk usage table, the Primary Server occupies 170 GB of space. A solution backup requires 189 GB. The total is 359 GB.
Since the server disk capacity is 600 GB, the Primary Server has the capacity to act as the backup server.
Server | R620 | DL360 | DL120 | R210 | OVA (default) | OVA (max supported) [1] | UCM |
Nominal disk capacity (GB) | 600 | 300 | 250 | 500 | 100 | 166 | 32 |
Max solution users | 2,500 | 2,000 | 1,500 | 1,500 | 750 | 2,500 | 50 |
Requires disk size increase.
Solution | Max No. of users | 100 | 750 | 1500 | 2000 | 2500 |
Max No. of nodes | 5 | 50 | 100 | 125 | 150 | |
Max No. of groups | 20 | 150 | 300 | 400 | 500 | |
Primary / Secondary max disk usage (no backup, one-X collocated) (GB) | 75 | 100 | 130 | 150 | 170 | |
Expansion max disk usage (no backup) (GB) | 48 | 48 | 48 | 48 | 48 | |
one-X standalone max disk usage (no backup) (GB) | 49 | 49 | 49 | 49 | 49 | |
Solution Max backup size (GB) | Configuration only | 2 | 13 | 25 | 31 | 37 |
All data | 35 | 78 | 127 | 158 | 189 |
No. of VMPro users | 20 | 50 | 100 | 150 |
No. of Hunt Groups | 4 | 12 | 20 | 30 |
Application Server max disk usage (GB) | 117 | 117 | 117 | 118 |
Max backup size config only (GB) | 1 | 1 | 1 | 1 |
Max backup size all data (GB) | 30 | 32 | 34 | 37 |