VMware Site Recovery Manager 5.5 Guide

5.5Guide

 

This is a Site Recovery Manager 5.5 Guide to help understand the design, installation, operation and architecture of setting up VMware SRM 5.5

 

SRM 5.5 Architecture

SRM 5.5 Installation

SRM 5.5 Site Configuration

SRM 5.5 VM Replication Configuration

SRM 5.5 Array Replication Configuration

SRM 5.5 Virtual Appliance Replication

SRM 5.5 Protection Groups

SRM 5.5 Recovery Plans

SRM 5.5 Bulk IP Customizations

SRM 5.5 Test Recovery

SRM 5.5 Recovery

SRM Gotchas

Official Documentation Links

SRM 5.5 Release Notes

SRM 5.5 Compatibility Matrix

SRM 5.5 Documentation Center

SRM Port Numbers 

SRM Product Page

Additional Resources

Follow these people on Twitter if you are looking for some great resources to learn more about SRM.

@Mike_Laverick Author of “Administering VMware Site Recovery Manager”  BLOG:  mikelaverick.com

@vmKen Senior Technical Marketing Director for VMware DRBC products BLOG: blogs.vmware.com/vsphere/uptime/

VMware Communities SRM

Home Lab

Its one thing to read how to do something, but another to get your hands on the technology.  I have a post on this site dedicated to showing how you can build an SRM site all within a single host with nested ESXi hosts.

Poor Mans SRM Lab

 

Filed Under: SRM

2 Responses to VMware Site Recovery Manager 5.5 Guide

  1. Eric,

    Great job on the SRM guide. SRM is great product and I appreciate you putting this key information on your blog as a reference for someone like me who has not had a chance to do hands on.

    We are about to start implementing VMware vSphere in our other data center and would like to leverage this data center as a DR site, however I still have some concerns.

    Mainly, it seems like when implementing SRM between the two data centers, going with the spanned layer 2 vlans is the way to go, if one has that option. This would potentially mitigate a lot of administrative overhead with re-IPing VMs. But what if re-IPing VMs is not enough? Quite often, client endpoints or DNS records have to be updated to point to the new IP address,

    Testing recovery plan, in a bubble network may be somewhat of a challenge when certain workloads depend on AD services, which for one reason or the other may not be part of the recovery plan. Not sure if anything can be done with network isolation rules, etc.

    Finally, Duncan and Frank (VMware) wrote a piece on vSphere Metro Storage Clusters (vMSC) http://bit.ly/VS4XGE, which could also potentially be an option for some.

    Greg

Leave a reply