Clumio Service Limits
This article highlights current Clumio Service Limits. These limits apply to Clumio operations including, but not limited to, the backup and restore services. We are constantly evaluating and improving our service limits. If you have any questions please reach out to [email protected].
Note: We publish service limits for only generally available features inside Clumio.
These limits pertain to only AWS today. Contact Clumio support if you have specific questions about other datasource limits.
Service Limits
Inventory service limits
The Clumio Inventory service gathers all the information in the customer environment to enable the service to protect an asset. Inventory service will merely present information in the Clumio UI, what exists in the customer environment(s). For protection limits, please see the relevant data source section below.
Inventory service limits capture the upper limit of the Clumio Inventory service. This includes, but is not limited to, EC2 instances, RDS instances, AWS tags, etc.
| AWS Entity | Clumio Limit |
| EC2 Instances | 20,000 |
| EBS Volumes | 20,000 |
| RDS Instances | 1,300 |
| S3 | 30 billion objects |
| AWS Tags | 38,000 |
AWS Connection Limits
Clumio Connection Service offers customers the ability to integrate with their AWS accounts. The following section covers the limits associated with connecting accounts in to Clumio. These limits apply to all deployment methods.
These limits apply to how many different AWS Accounts and Regions can be connected into Clumio. So, below, you can have (number of accounts X number of regions) a total of account region combination connected into Clumio. You will see them as individual environments under the AWS>Environments tab.
| Operation | Clumio Limit |
| Number of Accounts connected | No Hard Limit |
| Number of Regions connected | 16 |
AWS EBS Limits
| AWS Entity | Clumio Limit |
| Max EBS Volume Size | 16TB |
| EBS Concurrent Restores (per AWS Connection) | 5 tasks |
| EBS Concurrent Backups (per AWS Connection) | 30 tasks |
AWS Limits here
AWS EC2 Limits
| AWS Entity | Clumio Limit |
| EC2 Size | 16TB x 15 EBS Volumes attached |
| EC2 Concurrent Restores (per AWS Connection) | 5 tasks |
| EC2 Concurrent Backups (per AWS Connection) | 30 tasks |
AWS Limits here
AWS MS SQL on EC2 Limits
| AWS Entity | Clumio Limit |
| Maximum database backup size | 30 TB |
| MS SQL Concurrent Backups/Restores (per MS SQL host/EC2 instance) | 10 tasks |
Microsoft recommends a maximum of 35 databases per SQL instance.
AWS RDS Limits
| AWS Entity | Clumio Limit |
| Maximum RDS Instance Size | 16TB-64TB (Dependent on DB engine) |
| RDS Concurrent Restores (Per Data Plane) | 5 tasks at a time (5 in queue) |
| RDS Concurrent Rolling Backups (Per Data Plane) | 5 tasks at a time (5 in queue) |
| RDS Granular Backups (Per Data Plane) | 5 tasks at a time (5 in queue) |
- Rolling Backups for RDS instances are full backups for any instances with a provisioned size under 500 GB.
- Beyond 500 GB, Clumio performs an incremental backup using a snapshot preserved in the source account.
AWS Limits here
AWS DynamoDB Limits
| AWS Entity | Clumio Limit |
| Maximum parallel backup tasks | 50 Tasks (Securevault Standard) |
| Maximum parallel restore tasks | 10 Tasks (Securevault Standard) |
| Max Backup Size | 50 TB/table (Securevault Standard) |
| Max Restore Size | 50 TB/table (Securevault Standard) |
| GRR - CSV output | 5 Million Records |
AWS Limits here
AWS S3 Limits
| AWS Entity | Clumio Limit |
| Max single object restore size (from Cold tier) | 5TB |
| Number of buckets that can be added in a PG in a single Go via UI | 25 |
| Max number of objects backed up in a single micro-backup | 80K |
| Max number of objects backed up by continuous backup in one hour | 20M |
| Number of local containers for a single bucket with continuous backup enabled | 100 |
| Number of buckets added to a single PG with continuous backup enabled | 100 |
AWS Limits here
Contact [email protected] with any questions or clarifications.
Updated 3 months ago