Search the VMware Knowledge Base (KB)
View by Article ID

Operational Limits for Site Recovery Manager 5.8 (2081158)

  • 3 Ratings

Details

Different limits apply to the numbers of virtual machines that you can protect using Site Recovery Manager, depending on whether you use array-based replication, vSphere Replication, or a combination of both.

Solution

Protection Maximums for SRM 5.8

Due to performance improvements in ESXi Server 5.5 Update 2, the protection maximums for Site Recovery Manager apply if you are running ESXi Server 5.5 Update 2 or later. If you are running an older version of ESXi Server, the protection maximums for Site Recovery Manager 5.5 still apply, as described in    Operational Limits for SRM 5.1 and 5.5 and vSphere Replication 5.1 and 5.5 (2034768)

             
Item
Maximum
Total number of virtual machines configured for protection (array-based replication and vSphere Replication combined)
5,000
Total number of virtual machines configured for protection using array-based replication
5,000
Total number of virtual machines configured for protection using vSphere Replication
500
Total number of virtual machines per protection group
500
Total number of protection groups (array-based replication protection groups and vSphere Replication protection groups combined)
250
Total number of recovery plans
250
Total number of protection groups per recovery plan
250
Total number of virtual machines per recovery plan
2,000
Total number of replicated datastores (using array-based replication)
255
 
You can run array-based protection groups alongside vSphere Replication protection groups in the same SRM Server instance. The total number of protection groups cannot exceed 250 for both replication types combined. For example, you cannot create 250 array-based replication protection groups and then create 250 vSphere Replication protection groups, as this creates 500 protection groups in total.
For example:
  • If you have 150 array-based protection groups, you can create an additional 100 vSphere Replication protection groups, to make a total of 250 protection groups.
     
    Similarly, in a setup that combines array-based replication and vSphere Replication, you can protect a maximum of 5,000 virtual machines, even if you combine replication types. The protection limit for array-based replication is 5,000 virtual machines. The protection limit for vSphere Replication is 500 virtual machines. However, the maximum number of virtual machines that you can protect by using a combination of array-based and vSphere Replication is still 5,000 virtual machines, and not 5,500.
  • If you protect 500 virtual machines with vSphere Replication, you can protect a maximum of another 4,500 virtual machines with array based replication.
  • If you protect 1,000 virtual machines with array based replication, you can protect a maximum of another 500 virtual machines with vSphere Replication.

Bidirectional Protection

If you establish bidirectional protection, in which site B serves as the recovery site for site A and at the same time site A serves as the recovery site for site B, limits apply across both sites, and not per site. In a bidirectional implementation, you can protect a different number of virtual machines on each site, but the total number of protected virtual machines across both sites cannot exceed the limits.

For example:
  • If you protect 3,000 virtual machines using array-based replication from site A to site B, you can use array-based replication to protect a maximum of 2,000 virtual machines from site B to site A. If you are using array-based replication for bidirectional protection, you can protect a total of 5,000 virtual machines across both sites.
  • If you protect 300 virtual machines using vSphere Replication from site A to site B, you can use vSphere Replication to protect a maximum of 200 virtual machines from site B to site A. If you are using vSphere Replication for bidirectional protection, you can protect a maximum of 500 virtual machines across both sites.
  • If you protect 3,000 virtual machines virtual machines using array-based replication from site A to site B and 300 virtual machines using vSphere Replication from site A to site B, you can protect a maximum of 1,700 virtual machines from site B to site A. Of these 1,700 virtual machines, you can protect a maximum of 200 by using vSphere Replication. If you are using a combination of array-based replication and vSphere Replication for bidirectional protection, you can protect a maximum of 5,000 virtual machines across both sites, of which you can protect a maximum of 500 by using vSphere Replication.

Recovery Maximums for SRM 5.8

Item
Maximum
Total number of concurrently executing recovery plans
10
Total number of concurrently recovering virtual machines (array-based replication and vSphere Replication combined)
2,000
Total number of concurrently recovering virtual machines using array-based replication
2,000
Total number of concurrently recovering virtual machines using vSphere Replication
500

For example, if you protect 5,000 virtual machines with SRM, you can recover up to 2,000 virtual machines in one recovery plan. After that plan has completed you can run another recovery plan to recover another 2,000 virtual machines. When the second plan has also completed you can recover the remaining 1,000 virtual machines.

IP Customization Maximums for Site Recovery Manager 5.8 

If you implement IP customization for recovered virtual machines, you can configure a maximum of one IP address for each NIC, using DHCP, static IPv4, or static IPv6. For static IPv4 or IPv6 addresses, you provide the following information per NIC:
  • 1 IP address
  • Subnet information
  • 1 gateway server address
  • 2 DNS servers (primary and secondary)
You also set 2 WINS addresses for DHCP or IPv4, on Windows virtual machines only.

Deployment Maximums for SRM 5.8

Item Maximum
Total number of SRM Server instances per vCenter Server in a 1:1 configuration 1
Total number of SRM Server instances per vCenter Server in a shared recovery site configuration 10

For more information about the limits of using Site Recovery Manager 5.8 in a shared recovery site configuration, also known as an N:1 configuration, see Operational Limits of Site Recovery Manager 5.8 in a Shared Recovery Site (N:1) Configuration (2081866)

Additional Information

For translated versions of this article, see:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 3 Ratings
Actions
KB: