...
| Requirement | Explanation | Example |
|---|---|---|
| Type | NFS | The type of fileshare |
| IP-Address | The IP-Address of the NFS share | 10.10.100.10 |
| Path | The path to the backup directory | /srv/jtel-backup |
| NFS Version | The NFS Version | NFSv4.1 |
| Retention daily backup | How long daily backups are kept on the share until they are deleted. If left empty, infinite. | 14 |
| Retention weekly backup | How long weekly backups are kept on the share until they are deleted. If left empty, infinite. | 95 |
| Retention monthly backup | How long monthly backups are kept on the share until they are deleted. If left empty, infinite. | 165 |
Sizing
| Info |
|---|
Reminder: The Backup Storage drive in the tables below is not should not be part of the actual stack vmVM, but should be external. |
VM Sizing
Up to 20 Concurrent Agents
| Sizing | CPU Cores | RAM | Storage | Backup Storage |
|---|---|---|---|---|
| Minimal (only recommended for systems with low load or testing purposes) | 4 | 16 GB | 500 GB256GB | |
| Optimal (recommended for normal operations) | 8 | 32 GB | 1 TB | 500GB |
Up to 60 Concurrent Agents
| Sizing | CPU Cores | RAM | Storage | Backup Storage |
|---|---|---|---|---|
| Minimal (only recommended for systems with low load) | 8 | 32 GB | 1 TB | 500GB |
| Optimal (recommended for normal operations) | 16 | 64 GB | 2 TB1TB |
Up to 200 Concurrent Agents
| Sizing | CPU Cores | RAM | Storage | Backup Storage |
|---|---|---|---|---|
| Minimal (only recommended for systems with low load) | 16 | 64 GB | 2 TB1TB | |
| Optimal (recommended for normal operations) | 32 | 128 GB | 4 TB2TB |
Over 200 Concurrent Agents
Bespoke calculation based on exact system requirements.
Backup Storage Sizing and Retention Policy
The backup storage, which should be external to the VM itself, will need to be sized accordingly, and also you will need to implement a rotation and retention strategy.
WORM
We do highly recommend the usage of WORM storage with appropriately configured policies. Since the backup is content based,
In all cases you will need to consult your data protection officers to determine what are reasonable retention policies for your business.
Retention Policy
We recommend implementing a retention and rotation scheme. This is an example only, for exact retention policies please discuss with your data protection officer.
- Daily backups, retained for example for 14 days
- Weekly backups, copied from daily backups as required, retained, for example, for 12 weeks
- Monthly backups, copied from weekly backups as required, retained, for example, for 24 months
Sizing
| Warning |
|---|
It is impossible to calculate the exact size of backup storage required, as this is a function of:
We recommend you use a storage system which allows for dynamic growth wherever possible. The following are guidelines only! |
To determine the actual size of the backup storage you require, you should regularly examine your backup storage. In daily, you will find 2 files created each day:
- One sql.gz file - this contains the database backup
- One tar.bz2 file - this contains the data directory files backup
The naming of the files follows the following convention:
<instance_name>_<version>_<date>_<time>_<machine_name>.sql.gz<instance_name>_<version>_<date>_<time>_<machine_name>.tar.bz2
For example:
cmyacd.jtel.online_3.44.1_2026-05-15-020000+0200_cmyacd-debian-vm.sql.gzcmyacd.jtel.online_3.44.1_2026-05-15-020000+0200_cmyacd-debian-vm.tar.bz2
Adding up the size of these two files, and considering some growth thereof, will give you an approximate size of what each day's backup will need.
Use your retention policy to calculate the final sizing of the backup storage.
Here are some examples, using approximate sizes of data observed in the field:
| SizingStorage | DB Backup Size | File System Backup Size | Daily Backup Size | Example retention policy above | Calculated Minimum Backup Size | Actual Backup Size (Including Spare Capacity for Growth) |
|---|---|---|---|---|---|---|
| Up to 20 Concurrent Agents | 50 MB | 100 MB | 150 MB | 150 MB * ( 14 + 12 + 24 ) | 7.5 GB | 15 GB150 MB per retained backup |
| Up to 60 Concurrent Agents | 100 MB | 400 MB | 500 MB | 500 MB * ( 14 + 12 + 24 ) | 25 GB | 50 GB500 MB per retained backup |
| Up to 200 Concurrent Agents | 300 MB | 1.2 GB | 1.5 GB | 1.5 GB per retained backup * ( 14 + 12 + 24 ) | 75 GB | 150 GB |
| Over 200 Concurrent Agents | Bespoke calculation based on exact system requirements. |
...
Storage Sizing and i/o Performance
Sizing
The system writes a considerable amount of data and logs to disk during high load conditions. It is important, that the underlying disk system on the container host provides enough performance and does not get saturated under load.
...