Posts

This is a Site Recovery Manager 5.8 Guide to help understand the design, installation, operation and architecture of setting up VMware SRM 5.8 SRM 5.8 Architecture SRM 5.8 Installation SRM 5.8 Upgrade from SRM 5.5 SRM 5.8 Site Setup SRM 5.8 Array Based Replication SRM 5.8 Protection Groups SRM 5.8 Recovery Plan SRM 5.8 IP Customization SRM 5.8 Customizing your Recovery Plan SRM 5.8 Test Recovery SRM 5.8 Failover Recovery SRM 5.8 with Automation SRM 5.8 Alarms SRM 5.8 Troubleshooting Official Documentation Links Site Recovery Manager 5.8 Documentation Center Site Recovery Manager 5.8 Compatibility Matrix Site Recovery Manager 5.8 Release Notes Site Recovery Manager 5.8 vCO Plug-in Download Site Recovery Manager 5.8 Download Site Recovery Manager 5.8 Storage Replication Adapters Additional Resources If you want some great resources to continue learning VMware Site Recovery Manager, I suggest checking out these resources: ...

“Your disaster recovery plan is only as good as it’s last test.” “If you haven’t tested your DR plan, then you don’t have a DR plan.” These are all statements I’ve heard in the industry from CIOs and directors, and lucky for us VMware Site Recovery Manager has a test functionality built in for us to leverage without fear of affecting our production workloads. Run a Test Open up one of your recovery plans and click the monitor tab. Here you’ll have several buttons to choose from as well as seeing the list of recovery steps. To run a “Test” recovery click the green arrow button. ...

A terrible thing has happened and it’s time to failover your datacenter to your disaster recovery site. Well, maybe you’re just migrating your datacenter to a new one, but this is always a bit of a tense situation. Luckily we’ve had the opportunity to test the failovers many, many times before so we can be confident in our process. Go to the Recovery Plan and click the monitor tab. Click the “BIG RED BUTTON” (yeah, it’s not that big, but it has big consequences). ...

Some companies have built out their disaster recovery site with a stretched layer 2 network or even a disjoint layer 2 network that shares the same IP addresses with their production sites. This is great because VMs don’t need to change IP Addresses if there is a failover event. This post goes over what options we have if you need to change IP Addresses during your failover. Network mappings SRM 5.8 has a wonderful new way to manage IP Addresses between datacenters. Prior to SRM 5.8 each VM needed to be manually updated with a new IP Address or done in bulk with a CSV template (show later in this post) if you had to re-IP your VMs. Now with SRM 5.8 we can do a network mapping to make our lives much easier. This is one of the best new features of SRM 5.8 in my opinion. ...

A recovery plan is the orchestration piece of Site Recovery Manager and likely the main reason for purchasing the product. All of the setup that’s been done prior to creating the recovery plans is necessary but the recovery plan is where magic happens. When we go to the Recovery Plans menu in Site Recovery, we’ll see the option to click the notepad with the “+” sign on it to create a new recovery plan. ...

SRM Sites and resource mappings are all done. It’s time to create some Protection Groups for our new VMware Site Recovery Manager deployment. A protection group is a collection of virtual machines that should be failed over together. For instance, you may want all of your Microsoft Exchange servers to fail over together, or you may want a Web, App, Database Tier to all failover at the same time. It is also possible that your main goal for SRM is to protect you in the event of a catastrophic loss of your datacenter and you’re concerned with every VM. It still a good idea to create multiple protection groups so that you can fail over certain apps in the event of an unforeseen issue. Think about it, if your mail servers crashed but the rest of your datacenter is fine, would it make sense to just fail over the mail servers, or the entire datacenter? Just failing over the mail servers would make sense if they are in their own protection group. ...

If you plan to use Array Based Replication for your SRM implementation, you’ll need to install and configure your Storage Replication Adapter on your SRM Servers. The SRA is used for SRM to communicate with the array to do things like snapshots, and mounting of datastores. Pair the Arrays Once your SRAs have been installed in both your sites and you’ve gotten the arrays replicating, you’ll want to pair the arrays in SRM so that they can be used for protection Groups. Open the “Array Based Replication” tab in the “Site Recovery” menu of the web client. Click the Add button. ...

In the previous post we installed VMware Site Recovery Manger and now we need to do our Site Setup. If you notice, now that SRM has been installed, the vSphere Web Client now has a Site Recovery menu in it. (If it doesn’t, log out and back in) From here, we can go into the new SRM menus. Site Pairing Once you’ve gotten to the SRM Menus, we’ll want to click on Sites to configure our Sites. ...

SRM Installation Prerequisites Database Prerequisites Before you are able to install SRM, you’ll need a database to store configuration files. Create a database on your SQL Server to house the configuration information. Note: You’ll need a database server in both the protected site and recovery site; one for each SRM Server. Pre-create the SQL Database and assign your SRM Service account AT LEAST the ADMINISTER BULK OPERATIONS, CONNECT, AND CREATE TABLE permissions. Ensure the SRM database schema has the same name as the database user account. The SRM database service account should be the database owner of the SRM database The SRM database schema should be the default schema of the SRM database user. On your SRM Servers, install the SQL Server native client for your version of SQL Server. Create an ODBC connection to the SRM database on your SRM Servers. Select the SQL Native Client appropriate for your database server. ...

VMware Site Recovery Manager consists of several different pieces that all have to fit together, let alone the fact that you are working with two different physical locations. The following components will all need to be configured for a successful SRM implementation: 2 or more sites 2 or more Single Sign On Servers 2 or more vCenter Servers 5.5 2 or more SRM Servers Storage – Either storage arrays with replication, or 2 or more Virtual Replication Appliances Networks It’s worth noting that SSO, vCenter, and SRM could all be installed on the same machine, but you’ll need this many instances of these components. ...