Operational Limits for NAKIVO Backup and Replication
Product version: 11.2
Last modified: 3 November 2026
Question
How many VMs can I protect with NAKIVO Backup & Replication?
How many jobs can I create in a single instance?
How many Transporters and Backup Repositories can I have?
Which limits are enforced by the product, and which limits are recommendations?
Answer
NAKIVO Backup & Replication has two types of operational limits:
-
Recommended limits: The product is tested and supported within these limits. The product allows you to add objects and start activities beyond these limits. However, exceeding them may result in performance issues or unexpected errors.
-
Enforced limits: The product does not allow you to exceed these limits.
Recommended Limits
In multi-tenant mode, the limits in the Single-tenant mode or per tenant column apply to each tenant. The limits in the Multi-tenant mode, total column apply to the whole installation.
| Item | Single-tenant mode or per tenant | Multi-tenant mode, total |
|---|---|---|
| Tenants | ||
| Number of tenants, local and remote | Not applicable | 100 |
| User Sessions | ||
| Number of active user sessions in the web UI, CLI, and API | 50 | 500 |
| Inventory | ||
| Number of top-level inventory items, such as vCenter Servers or standalone hosts | 500 | 500 per tenant |
| Number of discovered VMs | 10,000 | 10,000 per tenant |
| Number of credentials | 1,000 | 1,000 per tenant |
| Number of network mappings | 1,000 | 1,000 per tenant |
| Number of re-IP rules | 1,000 | 1,000 per tenant |
| Transporters and Scan Servers | ||
| Number of Transporters | 500 | 2,000 |
| Number of transporter pools | 10 | 100 |
| Number of Transporters in a single transporter pool | 50 | 500 |
| Number of scan servers | 500 | 2,000 |
| Backup Repositories | ||
| Number of Backup Repositories | 500 | 2,000 |
| Maximum allocated space in a single Backup Repository | 100 TB | 100 TB |
| Minimum free space in a single Backup Repository | 1 GB | 1 GB |
| Jobs and Groups | ||
| Number of jobs, including disabled jobs | 500 | 500 per tenant |
| Number of job groups | 500 | 500 per tenant |
| Number of source objects in a single job | 500 | 500 |
| Number of running jobs | 100 | 100 per tenant |
| Number of running jobs on a single Transporter | 50 | 50 |
| Number of running jobs on a single host | 10 | 10 |
| Number of running jobs on a single datastore | 10 | 10 |
| Recovery Sessions | ||
| Number of active recovery sessions (file recovery, object recovery, Flash VM Boot, and recovery sandbox) | 25 | 250 |
| Number of active recovery sessions on a single Transporter | 5 | 50 |
| Scan Sessions | ||
| Number of active ransomware scan sessions | 25 | 250 |
To work beyond the recommended limits, add CPU and RAM to the machines that host the Director and Transporters, or deploy additional Transporters. For RAM recommendations based on the number of jobs, see Scalability and UI Performance.
Enforced Limits
| Item | Limit |
|---|---|
| Number of tenants, local and remote | The maximum number of tenants set in the license |
| Number of recovery points in a single backup (backup, backup copy, and Amazon EC2 replication jobs) | 10,000 |
| Number of recovery points on a single replica VM (VMware and Hyper-V replication jobs) | 30 |
| Number of incremental recovery points in a backup chain for granular recovery, universal object recovery, and Flash VM Boot | 256 |
| Number of Backup Repositories assigned to a single Transporter with Direct Connect enabled | 10 |
| Number of items selected per source object in a file-level backup job | 200 |
Some features have their own supported maximums, for example file-level backup, real-time replication for VMware, and HPE StoreOnce Catalyst integration. For details, see Feature Requirements and Storage Integration Requirements.