Reference

Limits

Cloud quota, API throttling, storage, snapshot, and recovery limits that affect Easy Hybrid DR scale.

Product: Easy Hybrid DR
Version: v2.3.1
Release status: GA
Documentation status: Published
Last updated: Updated May 28, 2026
Reading time: 1 min read

Cloud-native disaster recovery scale is heavily influenced by provider quotas, API throttling behavior, and storage provisioning limits. Large-scale failovers, parallel recovery operations, snapshot bursts, volume provisioning, cross-region copy operations, and mass VM power-on orchestration should be planned against these limits before production use.

How Datamotive handles limits

Easy Hybrid DR is designed to operate within cloud-provider limits using parallel orchestration, retry-aware workflows, backpressure-aware replication, horizontal scaling, and adaptive concurrency management.

AWS service usage

AWS service	Datamotive usage
EC2 APIs	VM creation, power operations, and orchestration.
EBS APIs	Snapshot and volume operations.
EBS Direct APIs	Block-level snapshot writes and reads.
IAM APIs	Access and orchestration.
VPC APIs	Network provisioning.

Important AWS scalability limits

AWS resource or API	Typical default limit	Notes
EBS snapshots per Region	100,000	Adjustable.
Concurrent OpenSnapshot for Write operations	100 per account	Adjustable with AWS support request.
EBS volume attachments per instance	Instance dependent, typically 28 on Nitro	Recovery consideration.
EBS volume size	64 TiB maximum	Per volume.
Regional EC2 vCPU quotas	Varies by VM family	Frequently requires increase.
EBS Direct API throughput	Account and API limited	Important for parallel recovery.

AWS API throttling behavior

AWS uses token-bucket throttling for EC2 and EBS APIs. Throttling occurs per API operation, limits vary by API type, read operations usually have higher limits, and mutating APIs are throttled more aggressively.

API	Operation type
CreateSnapshot	Storage mutation
CreateVolume	Storage mutation
AttachVolume	Compute/storage mutation
RunInstances	Compute mutation
StartInstances	Compute mutation
DescribeVolumes	Read operation
DescribeSnapshots	Read operation

Typical throttling responses include HTTP 429, RequestLimitExceeded, and ThrottlingException.

AWS EBS Direct API considerations

Parameter	Typical behavior
Block size	512 KB
API throughput scaling	Based on concurrency
Parallel API calls	Strongly recommended
Snapshot write throughput	Limited by account and API quotas

Under optimal conditions, approximately 1000 PutSnapshotBlock operations per second can produce roughly 500 MB/s throughput per snapshot workflow.

AWS quota increase guidance

Quota	Recommendation
Regional vCPU quotas	Increase before DR onboarding.
EBS snapshot quotas	Increase for long retention periods.
EBS volume quotas	Increase for large recoveries.
Snapshot write limits	Increase for cross-region DR.
ENI/IP quotas	Validate during recovery planning.

Quota increases can be requested using AWS Service Quotas, AWS Enterprise Support, or AWS Support Center.

Azure service usage

Azure service	Datamotive usage
Azure Resource Manager (ARM)	Resource orchestration.
Azure Compute APIs	VM provisioning and operations.
Azure Managed Disk APIs	Disk and snapshot operations.
Azure Networking APIs	NIC and network provisioning.
Azure Subscription Quotas	Regional compute allocation.

Important Azure scalability limits

Azure resource or API	Typical default limit	Notes
Managed Disks per subscription/region	50,000 per disk type	Adjustable.
Incremental snapshots per disk	500	Important for retention planning.
Regional vCPU quotas	Subscription dependent	Frequently requires increase.
VM family quotas	Region and family specific	Common DR bottleneck.
ARM API requests	Subscription and region throttled	Critical for parallel recovery.
Concurrent disk operations	Compute/provider throttled	Recovery consideration.

Azure ARM API throttling

Azure Resource Manager applies throttling at multiple levels: subscription, region, resource provider, service principal, and API operation type.

API category	Examples
VM APIs	VM creation and power operations.
Disk APIs	Managed disk creation.
Snapshot APIs	Snapshot creation and deletion.
Network APIs	NIC and IP provisioning.
Page Blob APIs	Read and write content.

Typical throttling symptoms include HTTP 429 responses, Retry-After headers, delayed provisioning, and intermittent API failures.

Azure quota increase guidance

Quota	Recommendation
Regional vCPU quotas	Mandatory for enterprise DR.
VM-family quotas	Required for target recovery VM sizes.
Managed disk quotas	Increase for large environments.
NIC quotas	Validate during DR planning.
Public IP quotas	Validate if public recovery is required.

Quota increases can be requested using Azure Portal, Azure Quota APIs, or Microsoft Support.

Practical operational considerations

In large recovery environments, practical scale is often constrained more by API orchestration behavior than raw infrastructure capacity.

Common bottlenecks include API throttling, subscription quota exhaustion, disk provisioning concurrency, snapshot finalization delays, VM-family quota exhaustion, and network provisioning limits. These are especially important during mass failover events, parallel recovery testing, regional evacuations, and large VDI recovery operations.

Datamotive operational recommendations

Area	Recommendation
Quotas	Increase quotas before production onboarding.
DR testing	Perform periodic scale testing.
Recovery design	Use staged recovery orchestration for massive failovers.
API handling	Use retry-aware orchestration.
Scaling	Use multiple Replication Engines for large environments.
Monitoring	Continuously monitor throttling behavior.
Networking	Pre-plan subnet and IP capacity.

Related docs

Was this page helpful?