Q
Get started Bring yourself up to speed with our introductory content.

What you need to know before deploying VMware SRM

What are the top five things you need to know before deploying VMware SRM (Site Recovery Manager)?

1. Identical SRM servers must be installed at the protected site and recovery site. Each SRM site must also have...

its own vCenter Server.

2. The protection site SRM server must be configured with VM protection groups. These groups are a collection of virtual machines (VMs) that fail over concurrently. The protection groups are added to the recovery site and usually are recovered concurrently on the recovery SRM server.

3. Make sure the SRM-based external storage system where the replication is controlled, managed and scheduled is validated and certified by VMware. Storage systems that support vSphere SRM can protect up to 1000 VMs per cluster. VSphere replication is limited to protecting 500 VMs. Note that vSphere clusters that utilize vSphere replication, leveraging VSAN, are also based on lower-cost, off-the-shelf internal flash and hard disk drives (HDDs). Those components must also be certified and validated on VMware's hardware-compatibility matrix. Don't assume that just because a vSphere cluster is running VSAN and SRM that the host embedded storage components are on the matrix. Troubleshooting SRM issues and problems (especially performance) can be a very real exercise in frustration and lost time when unsupported components are used.

4. Be sure that recovery point objectives (RPO) and recovery time objectives (RTO) can be met by the replication methodology. Each external storage system has its own RPO and RTO capabilities and limitations. Even vSphere replication has limitations, such as a RPO best-case scenario of 15 min. If a lower RPO is required, then an external storage system that can schedule the protected groups' replication on a more frequent basis must be utilized.

5. Test frequently. Set up a representative test plan. Test at least once a quarter. Before each test, make sure the SRM environment has not changed. If it has changed, update the test to reflect the real environment. Evaluate the results of each test and make fixes to problems, issues and holes in the plan. Update the test plan.

Next Steps

Resolving five common VMware SRM error messages

How RPO, RTO influence VMware SRM business decisions

The VMware Site Recovery Manager-disaster recovery relationship

This was last published in October 2014

Dig Deeper on Disaster recovery facilities - operations

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchSolidStateStorage

SearchCloudStorage

SearchDataBackup

SearchStorage

Close