SRM 5.8 Site Setup

SRM 5.8 Site Setup

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.

SRM58SiteSetup1

 

Site Pairing

Once you’ve gotten to the SRM Menus, we’ll want to click on Sites to configure our Sites.

SRM58SiteSetup2

Note: If you see the error below, this means that you’ve got an SSL Certificate mismatch between the SRM Server and the vCenter server.  If you use custom SSL certificates for vCenter, you must use them on your SRM Installation as well.

SSLError

 

Assuming all your installations have gone well, you’ll see a screen like the one below.  Click the “Pair Site” link to get started with the site configuration.

SRM58SiteSetup3-CertInstalled

Enter the vCenter information for the remote vCenter.  This will pair your site with the opposite site and create a relationship between them.

If you are using the default VMware certificates, you’ll need some login information entered.

SRM58SiteSetup4

If you are using custom SSL certificates from a certificate Authority, login information is not needed.

SRM58SiteSetup5

Once Site Pairing is done, you’ll see two sites in the SRM Sites menu

SRM58SiteSetup6

 

Resource Mapping

Now that the sites are paired, we can setup mappings for the relationships between the two sites.  This includes Resource Pools, Folders, and Networks.

Open up one of your sites and you’ll see a helpful “Guide to Configuring SRM” menu.  We’ll go right down the list by selecting the Create resource mappings.

SRM58_mapping1

Select a relationship between the protected network and the recovery network.  Once you’ve created your relationship click the Add Mappings button to add it to your mapping list.  When done, you can click the check box to create the same mapping in the reverse direction for fail back operations.  You can select a many to one relationship here, but if you do, you won’t be able to select the Reverse Mapping option.  Click OK.

SRM58_mapping2

Now we can click the “Create folder mappings” link in the guide to create a relationship for the virtual machine folders.  Repeat the process we did for resources, only this time for virtual machine folders.  The same rules apply for many to one relationships.  Click OK.

SRM58_mapping3

The next mapping we’ll need to do is for networking.  Map a network in the protected site to a recovery network.  Don’t worry about IP Addressing yet, we can customize this later, but you’ll need to know what network the virtual machines will map to during a failover.

SRM58_mapping4

 

Placeholder Datastores

The next section of the “SRM Configuration Guide” is to create placeholder datastores.  These datastores hold the configuration information for the virtual machines that are to be failed over.  Think of this as a .vmx file that is registered with vCenter without disks.  During a failover this virtual machine becomes active and the replicated virtual disks are attached to it.  This datastore should not be a replicated datastore, and does not need to be very large to store these files.

Configure the placeholder datastore.  Select one or more datastores to house the virtual machine files.  Click OK.

SRM58_PlaceholderDS

Once done, you’ll want to go to the other site and configure a datastore for it as well.  This is so the mappings are already done if you fail over and want to fail back.

SRM58_PlaceholderDS-Site2

 

Summary

We’ve now installed SRM and configured the sites.  We can now start looking at setting up replication and protection groups in the next post.

 

 

4 Responses to SRM 5.8 Site Setup

  1. Hello.
    I need to add 4 SRM servers in my Windows vCenter 5.5 U2 server. We are also getting the Certificate mismatch erro on 2 of the 4 SRM servers. We are using custom certificates. Can you explain what you mean with

    “If you use custom SSL certificates for vCenter, you must use them on your SRM Installation as well”
    The vcenter servers have different common names. SRM servers are sharing the same common name. Example: SRM

    • Sure thing.
      If you are using ssl certificates from a certificate authority on your vCenter, then SRM must also use them. No mixing and matching of self-signed certs that came from VMware and your own CA. It sounds like you are using your own CA so you must also create SSL Certs for your SRM Servers, which it also sounds like you are doing.
      It’s fine for your vCenters to use a different common name. But pairs of SRM Servers should have the same Common Name, Example SRM.

      • Thanks for sharing. I’am using certificates from a certificate authority for vCenter and SRM. In used the same certificates when SRM 5.1 was installed.We had no problems at that time.
        Regarding the certificate chain error I managed to pair the SRM servers. I seams to work, but I don’t like to see an error in my production environment. VMware is looking into this problem. they had no problem with 2 SRM servers. But are having the same problem when adding the 3th and 4th SRM server.

  2. Are you aware that using local disks for storage the placeholder datastore configuration will create issues??? I have seen an issue where in testing we have created a placeholder datastore on local disk and using VR we have replicated a VM to another ESXI hosts local disk but fail to power on!

Leave a reply