Site Recovery Manager (SRM) Lab Manual

Introduction

In this lab you will pair up with another student in order to simulate the setup and configuration tasks for VMware Site Recovery Manager

Activate the Site Recovery Add On

Important Instructions for Site Recovery Exercises

PLEASE BE AWARE THAT THESE EXERCISES MUST BE PERFORMED FROM THE ASSIGNED HORIZON DESKTOP YOUR INSTRUCTORS ASSIGNED OR THE JUMP HOST THAT YOU WILL CREATE AS PART OF THE LAB. IF YOU TRY TO PERFORM SOME OF THE EXERCISES OUTSIDE OF THE HORIZON SESSION OR THE JUMP HOST AS INSTRUCTED, YOU WILL EXPERIENCE SOME FAILURES.

Activate Site Recovery

SRM1

  1. Click on the Add Ons tab
  2. Under the Site Recovery Add On, Click the ACTIVATE button

    SRM2

  3. In the pop up window Click ACTIVATE again

    SRM3

What is VMware Site Recovery

SRM4

VMware Site Recovery brings VMware enterprise-class Software-Defined Data Center (SDDC) Disaster Recovery as a Service to the AWS Cloud. It enables customers to protect and recover applications without the requirement for a dedicated secondary site. It is delivered, sold, supported, maintained and managed by VMware as an on-demand service. IT teams manage their cloud-based resources with familiar VMware tools without the difficulties of learning new skills or utilizing new tools and processes.

Wait until the Site Recovery Add On has been activated. This process should take ~10 minutes to complete.

VMware Site Recovery is an add-on feature to VMware Cloud on AWS. VMware Cloud on AWS integrates VMware’s flagship compute, storage, and network virtualization products: VMware vSphere, VMware vSAN, and VMware NSX along with VMware vCenter Server management. It optimizes them to run on elastic, bare-metal AWS infrastructure. With the same architecture and operational experience on-premises and in the cloud, IT teams can now get instant business value via the AWS and VMware hybrid cloud experience.

The VMware Cloud on AWS solution enables customers to have the flexibility to treat their private cloud and public cloud as equal partners and to easily transfer workloads between them, for example, to move applications from DevTest to production or burst capacity. Users can leverage the global AWS footprint while getting the benefits of elastically scalable SDDC clusters, a single bill from VMware for its tightly integrated software plus AWS infrastructure, and on-demand or subscription services like VMware Site Recovery Service. VMware Site Recovery extends VMware Cloud on AWS to provide a managed disaster recovery, disaster avoidance and non-disruptive testing capabilities to VMware customers without the need for a secondary site, or complex configuration.

VMware Site Recovery works in conjunction with VMware Site Recovery Manager and VMware vSphere Replication to automate the process of recovering, testing, re-protecting, and failing-back virtual machine workloads. VMware Site Recovery utilizes VMware Site Recovery Manager servers to coordinate the operations of the VMware SDDC. This is so that, as virtual machines at the protected site are shut down, copies of these virtual machines at the recovery site startup. By using the data replicated from the protected site these virtual machines assume responsibility for providing the same services.

SRM5

VMware Site Recovery can be used between a customers datacenter and an SDDC deployed on VMware Cloud on AWS or it can be used between two SDDCs deployed to different AWS availability zones or regions. The second option allows VMware Site Recovery to provide a fully VMware managed and maintained Disaster Recovery solution. Migration of protected inventory and services from one site to the other is controlled by a recovery plan that specifies the order in which virtual machines are shut down and started up, the resource pools to which they are allocated, and the networks they can access.

VMware Site Recovery enables the testing of recovery plans, using a temporary copy of the replicated data, and isolated networks in a way that does not disrupt ongoing operations at either site. Multiple recovery plans can be configured to migrate individual applications or entire sites providing finer control over what virtual machines are failed over and failed back. This also enables flexible testing schedules. VMware Site Recovery extends the feature set of the virtual infrastructure platform to provide for rapid business continuity through partial or complete site failures.

Create a Cross SDDC VPN

We will be setting up an IPSEC VPN connection between your VPC and the VPC of the person you were paired with. Each student needs to complete the steps for your SDDC.

SRM6

  1. Navigate back to ALL SDDCs and click on VIEW DETAILS for the paired student’s SDDC. For example, if you are Student-1, you will view the details for the Student-2 SDDC.

    SRM7

  2. Click on the Networking & Security

    SRM8

    In the Management Gateway section, make a note of the VPN Public IP and the Infrastructure Subnet CIDR

    SRM9

Create a Policy Based VPN

Navigate back to the VIEW DETAILS section of YOUR SDDC to create the VPN to the Paired Student’s SDDC

On the Networking & Security tab

  1. Click VPN on the left-hand menu under Network
  2. Click Policy Based
  3. Click on ADD VPN

    SRM10

    Note that all workloads deployed in the module will be deployed to the Demo-Net Network Segment that was created in the Working with your SDDC module

    Fill in the following information:

  4. Enter Student # MGMT GW (where # is your peer’s student number) in the Name field
  5. Select Public IP for Local IP Address
  6. Enter the VPN Public IP address of the persons Management Gateway you were paired with for Remote Public IP
  7. Enter the paired student’s Demo-Net Network Segment CIDR 10.10.x.0/24 where X is the paired student’s number and enter the paired student’s Infrastructure Subnet CIDR you noted earlier in the Remote Networks field
  8. Click the Local Networks field and select both Demo-Net and Infrastructure Subnet
  9. Enter VMware1! in the Preshared Key field
  10. Click SAVE

    SRM11

    When both you and the person you were paired with have completed these steps you should see the status of the VPN turn to Success

Deploy a Windows Jump Host

DRaaS requires a form of private connectivity, not just between the two sites (SDDCs in this workshop environment) but also between the Site Recovery UI and the location you open it from. As a result, accessing Site Recovery over the internet via public IP will not work. To address this, we will create a Windows Jump Host in our SDDC and RDP to that jump host to work with Site Recovery.

Create a New Content Library

JumpHost1

From your SDDC copy the cloudadmin password and click OPEN VCENTER

JumpHost2

Enter the cloudadmin credentials and click LOGIN

JumpHost3

In the vSphere Client, click the Menu dropdown and click Content Libraries

JumpHost4

Click the + to add a new Content Library

JumpHost5

  1. Enter Windows-Content-Library in the Name field
  2. Click NEXT

JumpHost6

  1. Click the radio button next to Subscribed content library
  2. Enter https://s3-us-west-2.amazonaws.com/s3-vmc-iso/lib.json in the Subscription URL field
  3. Click NEXT

JumpHost7

If you get a warning, click YES

JumpHost8

  1. Select Workload Datastore for the storage location
  2. Click NEXT

JumpHost9

  1. Click FINISH

Deploy a VM from Content Library

JumpHost12

Click on your Windows-Content-Library that you just created

JumpHost13

Click OVF & OVA Templates (wait a few seconds if all of the templates aren’t listed, particularly the Windows2012r2 template)

JumpHost11

  1. Right-click on the Windows10 template
  2. Select New VM from This Template…

If you do not have the menu item to deploy a New VM from this template, Click the ACTIONS dropdown menu for the content library and click Synchronize (shown below) and wait until the sync is complete.

JumpHost10

Deploy a Windows VM

JumpHost14

  1. Enter Jump Host for the Virtual machine name
  2. Select the Workloads folder
  3. Click NEXT

JumpHost15

  1. Select the Compute-ResourcePool
  2. Click NEXT

JumpHost16

  1. Click NEXT

JumpHost17

  1. Select the WorkloadDatastore
  2. Click NEXT

JumpHost18

  1. Select Demo-Net from the Destination Network dropdown list (this network was created in the Working With Your SDDC module)
  2. Click NEXT

JumpHost19

  1. Click FINISH

Request a Public IP for the Jump Host

JumpHost20

Navigate to the Jump Host VM you just deployed, power it on and note the IP Address

JumpHost21

  1. Back in your SDDC, navigate to Networking & Security
  2. Click Public IPs in the left-hand navigation menu
  3. Click REQUEST NEW IP
  4. Enter Jump Host in for the Notes
  5. Click SAVE

JumpHost22

  1. Note the Public IP that was just provided
  2. Click NAT in the left-hand navigation menu

Create a NAT rule for the Jump Host

JumpHost23

  1. Click ADD NAT RULE
  2. Enter To Jump Host in the Name field
  3. Enter the noted Public IP in the Public IP field (it should be pre-populated)
  4. Enter the noted internal IP Address for your Jump Host VM in the Internal IP field
  5. Click SAVE

Create a Compute Gateway FW Rules to allow RDP to the Jump Host VM

JumpHost24

  1. Click Gateway Firewall in the left-hand navigation menu
  2. Click Compute Gateway
  3. Click ADD RULE

JumpHost25

We will add a rule that will allow us to connect to our jump host via RDP

  1. Enter RDP to Jump Host in the Name field
  2. Hover over the Destinations field and click the pencil icon

JumpHost26

We will add a group that contains our jump host’s internal IP address

  1. Click “ADD GROUP”

JumpHost27

  1. Enter Jump Host in the Name field
  2. Click Set Members

JumpHost28

  1. Click IP/MAC Addresses
  2. Click in the IP/MAC Addresses field and enter the interal IP of your jump host
  3. Click APPLY

JumpHost29

Note that under Compute Members it now shows 1 IPs/MACS

  1. Click SAVE
  2. Click APPLY

JumpHost30

  1. Hover over the Services field and click the pencil icon

JumpHost31

  1. Enter RDP into the Search field
  2. Click the checkbox next to RDP
  3. Click APPLY

JumpHost32

  1. Click PUBLISH to publish this new rule

JumpHost33

We will add another rule that will allow outbound traffic from our jump host

  1. Click ADD RULE
  2. Enter Jump Host Outbound into the Name field
  3. Select the Jump Host group you created previously for Sources
  4. Click PUBLISH

JumpHost34

  1. Click Management Gateway
  2. If your vCenter Inbound rule does not have ICMP ALL under Services, modify the rule to allow that service and PUBLISH the rule when complete.

JumpHost37

  1. Click Settings for your SDDC
  2. Click the > arrow next to vCenter FQDN
  3. Click EDIT

JumpHost38

  1. Select the Private IP in the Resolution Address dropdown
  2. Click SAVE

JumpHost36

Open REMOTE DESKTOP CONNECTION from YOUR desktop. Do not open it from within the virtual desktop.

  1. Enter the Public IP Address that was allocated for your jump host
  2. Log in with Administrator/VMware1!
  3. Click Connect (Click YES if you get a certificate error)

Install Firefox or Chrome into the Windows VM

JumpHost39

Internet Explorer does not work well, so you’ll need to download and install Firefox or Chrome into your Jump Host VM.

If Server Manager does not automatically open, open it.

  1. Click Local Server
  2. Click On next to IE Enhanced Security Configuration

JumpHost40

  1. Click the radio button next to Off under Administrators
  2. Click the radio button next to Off under Users
  3. Click OK

Test Connectivity

Download and install Firefox or Chrome in your Jump Host

Open your browser and enter the FQDN, found under Settings, for your vCenter server in your SDDC

Open another tab and enter the FQDN for the vCenter for your paired SDDC

If you can navigate to both vCenters via their FQDN’s, all connectivity is established correctly. The remainder of the work can be completed from your Remote Desktop connection to your Jump Host.

If you have issues connecting to the VMware Cloud on AWS console from your RDP session, connect to it from your Horizon desktop.

Prepare and Pair Site Recovery

Firewall Rules for Site Recovery

We will need to create Management Gateway firewall rules to allow for additional management gateway traffic including Site Recovery and vSphere Replication traffic. This needs to be done in both SDDCs.

SRMNew1

  1. In your SDDC, click Networking & Security
  2. Click Gateway Firewall in the left-hand navigation menu
  3. Click Management Gateway
  4. Add the additional four rules that are shown above. Ask your instructor if you need assistance with creating the management gateway firewall rules.
  5. Click PUBLISH

VMware Site Recovery - Site Pairing

SRM18

You will be pairing to the other SDDC that is in your workshop organization. Before beginning, each student needs to navigate to their partner’s SDDC and save the vCenter FQDN and cloudadmin password.

  1. Click Settings for your partner’s SDDC

    The username on both sides (yours and your peer) will always be cloudadmin@vmc.local

  2. Copy your partner’s cloudadmin password and save it to notepad
  3. Copy your partners vCenter FQDN. Before saving it to notepad, change the format from what is displayed to what will be used, as shown below:

    DISPLAYED:

     https://vcenter.sddc-xx-xxx-xx-xx.vmc.vmware.com/ui
    

    USED:

     vcenter.sddc-xx-xxx-xx-xx.vmc.vmware.com
    

SRM16

IMPORTANT NOTE: Only one person can do the Site Pairing exercise. Please decide between you and your partner who performs this step.

  1. Navigate to the SDDC of the student that will do the site pairing and click Add Ons
  2. Click OPEN SITE RECOVERY (If necessary, login with the cloudadmin credentials for that SDDC)

    SRM17

  3. Click NEW SITE PAIR

    SRM19

  4. Enter the vCenter FQDN of your partner’s SDDC in the format vcenter.sddc-xx-xxx-xx-xx.vmc.vmware.com in the PSC host name field
  5. Enter cloudadmin@vmc.local in the User name field
  6. Enter the cloudadmin password of your partner’s SDDC into the Password field
  7. Click NEXT

    SRM20

  8. Click the top-level checkbox to select all Services
  9. Click NEXT

    SRM21

  10. Click FINISH

    SRMNew2

  11. Click VIEW DETAILS

    SRMNew3

  12. Enter cloudadmin@vmc.local for the User name
  13. Enter the cloudadmin password for your partner’s SDDC for the Password
  14. Click LOG IN

    SRMNew4

Once logged in to your partner’s SDDC, you will see the Site Pair Summary

Configure Mappings

Configure Network Mappings

SRM22

  1. Click Network Mappings in the left pane of the Site Recovery page
  2. Click + NEW

    SRM23

  3. Select Prepare mappings manually
  4. Click NEXT

    SRM24

  5. Expand SDDC Datacenter on both sides
  6. Expand VMC Networks on both sides
  7. Click the checkbox next to Demo-Net on the left
  8. Click the radio button next to Demo-Net on the right
  9. Click ADD MAPPINGS

    SRM24-a

  10. Click the checkbox next to sddc-cgw-network-1 on the left
  11. Click the radio button next to sddc-cgw-network-1 on the right
  12. Click ADD MAPPINGS

    SRM24-b

  13. Ensure both network mappings have been created
  14. Click NEXT

    SRM25

    DO NOT select anything in Reverse Mappings

  15. Click NEXT

    SRM26

  16. Click NEXT

    SRM27

  17. Click FINISH

Folder mappings

SRM28

  1. Select Folder Mappings in the left pane
  2. Click *+ NEW

    SRM29

  3. Select Prepare mappings manually
  4. Click Next

    SRM30

  5. Expand vcenter… on both sides
  6. Expand SDDC-Datacenter on both sides
  7. Click the checkbox next to Workloads on the left
  8. Click the radio button next to Workloads on the right
  9. Click ADD MAPPINGS

    SRM30-a

  10. Click NEXT

    SRM31

    DO NOT select any Reverse mappings

  11. Click NEXT

    SRM32

  12. Click FINISH

Resource Mappings

SRM33

  1. Click Resource Mappings in the left pane
  2. Click + NEW

    SRM34

  3. Expand SDDC-Datacenter on both sides
  4. Expand Cluster-1 on both sides
  5. Click the checkbox next to Compute-ResourcePool on the left
  6. Click the radio button next to Compute-ResourcePool on the right
  7. Click ADD MAPPINGS

    SRM34-a

  8. Click NEXT

    SRM35

    DO NOT select any reverse mappings

  9. Click NEXT

    SRM36

  10. Click FINISH

Storage Policy Mappings

SRM37

  1. Select Storage Policy Mappings in the left pane
  2. Click + NEW

    SRM38

  3. Select Prepare mappings manually
  4. Click NEXT

    SRM39

  5. Click the checkbox next to vSAN Default Storage Policy on the left
  6. Click the radio button next to vSAN Default Storage Policy on the right
  7. Click ADD MAPPINGS

    SRM39-b

  8. Click NEXT

    SRM40

  9. Click the checkbox next to vSAN Default Storage Policy for Reverse mappings
  10. Click NEXT

    SRM41

  11. Click FINISH

Placeholder Datastores

SRM42

  1. Select Placeholder Datastores in the left pane
  2. Click + NEW

    SRM43

  3. Click the checkbox next to WorkloadDatastore
  4. Click ADD

    SRM43-a

For Placeholder Datastores, you must select a datastore at each side, so you’ll repeat the same steps for the other vCenter.

  1. Click the vCenter entry for the vCenter that you are paired with
  2. Click + NEW

    SRM43-b

  3. Click the checkbox next to WorkloadDatastore
  4. Click ADD

Create VMs to use with Site Recovery

You will now create four VMs to use for Site Recovery.

Navigate back to the vSphere client for YOUR SDDC

If you need to log back in to your SDDC thru the VMC console, use the cedxx@vmware-hol.com userid provided to you at the beginning and the password of VMware1!

SRM70

  1. From YOUR SDDC vSphere Client, Click Menu

  2. Click Content Libraries

    SRM71

  3. Click the Windows-Content-Library

    SRM72

  4. Click Templates

  5. Click OVF & OVA Templates

  6. Right-click the Windows2012r2 template

  7. Click New VM from This Template…

    SRM73

  8. Enter CRM-APP-xx where xx is your student ID number

  9. Select Workloads

  10. Click NEXT

    SRM74

  11. Select Compute-ResourcePool
  12. Click NEXT

    SRM75

  13. Click NEXT

    SRM76

  14. Select WorkloadDatastore
  15. Click NEXT

    SRM77

  16. Select Demo-Net from teh Destination Network dropdown listbox
  17. Click NEXT

    SRM78

  18. Click FINISH

    REPEAT the steps above three more times and create VMs named CRM-DB-xx, FIN-APP-xx, and FIN-DB-xx where xx is your Student ID number

    SRM79

  19. After you have created all four of your VMs, navigate to the VMs in the vSphere Client and Power On all four VMs.

Using Site Recovery

We will use Site Recovery to replicate the VMs we want to protect, create protection groups for those VMs, and create and test recovery plans. Navigate back to Site Recovery for your SDDC

Replicate VMs to Recovery Site


SRM100

We will use Site Recovery to Navigate back to Site Recovery for your SDDC

  1. Click Replications from the top menu bar
  2. Click + NEW

    SRM101

  3. Select ALL FOUR of the VMs you created previously
  4. Click NEXT

    SRM102

  5. Ensure Auto-assign vSphere Replication Server is selected
  6. Click NEXT

    SRM103

  7. Select WorkloadDatastore
  8. Click NEXT

    SRM104

  9. Leave all defaults for the RPO and click NEXT

    SRM105

  10. Select Do not add to protection group now
  11. Click NEXT

    SRM106

  12. Click *FINISH

    SRM107

  13. Click Refresh until all VMs show a status of OK (this may take a couple of minutes)

Create Protection Groups and Recovery Plans

We will create 2 Protection Groups, one for our CRM application and one for our Finance application. A VM can only belong to one Protection Group, but a Protection Group can belong to more than one Recovery Plan.

SRM108

  1. Click Protection Groups
  2. Click + NEW*

    SRM109

  3. Enter CRM-PG-XX where XX is your Student ID for Name
  4. Click NEXT

    SRM110

  5. Select *Individual VMs (vSphere Replication)
  6. Click NEXT

    SRM111

  7. Select both your CRM VMs
  8. Click NEXT

    SRM112

    We will create a Recovery Plan that will just recover our CRM application

  9. Select Add to new recovery plan
  10. Enter CRM-RP-XX where XX is your Student ID for the Recovery Plan Name
  11. Click NEXT

    SRM113

  12. Click FINISH

    SRM114

  13. Repeat steps 2 thru 12 above for the FIN VMs to create the FIN-PG-XX protection group

If you get a Not configured error when creating the protection groups, ensure under Site Pair that you have configured Placeholder Datastores for each side. Once that is done, you will need to Restore all Placeholder VMs for each protection group

Create a Recovery Plan for All Applications

We will create another Recovery Plan that will recover all of our applications. As stated before, a VM can only belong to one Protection Group, but a Protection Group can belong to more than one Recovery Plan.

SRM115

  1. Click Recovery Plans
  2. Click + NEW*

    SRM116

  3. Enter ALL-APPS-RP-XX where XX is your Student ID for Name
  4. Click NEXT

    SRM117

  5. Select Protection groups for individual VMs or datastore groups
  6. Select both the CRM and FIN Protection Groups
  7. Click NEXT

    SRM118

  8. Click NEXT

    SRM119

  9. Click FINISH

    SRM120

  10. You should now have three Recovery Plans, one just for the CRM app, one just for the FIN app, and one for all apps.

Perform a Recovery Test

SRM121

  1. Click the radio button next to the CRM-RP-XX Recovery Plan where XX is your Student ID
  2. Click TEST

    SRM122

  3. Click NEXT

    SRM123

  4. Click FINISH

    SRM124

  5. Click the CRM-RP-XX Recovery Plan where XX is your Student ID

    SRM125

  6. Click Recovery Steps

    SRM126

  7. Note the status of the test

    SRM127

  8. Ensure the status shows Test complete
  9. Click CLEANUP to cleanup the activity and return the environment to its normal state

    SRM128

  10. Click NEXT

    SRM129

  11. Click FINISH

    SRM130

  12. Note the status of the cleanup until it is complete

    SRM131

Once the cleanup is complete, the Recovery Plan is in a Ready status and is ready for a test or a recovery.

Updated:

Leave a Comment