VMware Hands-on Labs - HOL-1805-01-SDC


Lab Overview - HOL-1805-01-SDC - Site Recovery Manager: Data Center Migration and Disaster Recovery

Overview of Site Recovery Manager


VMware Site Recovery Manager is an automation software solution that integrates with the underlying replication technology to provide policy-based management, non-disruptive testing, and automated orchestration of recovery plans. Site Recovery Manager delivers flexibility and choice, it integrates natively with VMware vSphere Replication and also supports a broad range of array-based replication solutions available from all major VMware storage partners.

Site Recovery Manager natively leverages the benefits of VMware vSphere and can also take advantage of the Software-Defined Data Center (SDDC) architecture, integrating with other VMware solutions, such as VMware NSX (network virtualization) and VMware Virtual SAN (hyper-converged software-defined storage).

Site Recovery Manager can dramatically lower the total cost of ownership (TCO) through management and testing automation that eliminates the complexity of manual processes, while enabling the use of technology that lower capital expense for recovery infrastructure.

See more at https://www.vmware.com/products/site-recovery-manager


Lab Overview


This lab will consist of five modules addressing topics related specifically to the implementation of disaster recovery and business continuity solutions in a vSphere environment. Use the "Modules" list to determine which use case you want to complete. You may choose to complete any or all modules, keeping in mind you have 90 minutes available per session.

It is recommended to start at Module 1 and work your way through to Module 5.

Lab Module List:

Module 1: Lightning Lab: Failing over a Virtual Machine with Site Recovery Manager

This module will perform a recovery of a single virtual machine using Site Recovery Manager.

Module 2: Creating and Executing a Disaster Recovery Plan with Site Recovery Manager (60 minutes, Beginner)

Module 3: Site Recovery Manager Advanced Topics (30 minutes, Advanced)

Module 4 - Automating Site Recovery Manager tasks with vRealize Orchestrator (30 minutes, Advanced)

Module 5 - SRM integration with NSX and Storage Policy Based Protection Groups and Stretched Storage (30 minutes, Advanced)

Lab Captains: Paul Irwin and Jeff Knous

This lab manual can be downloaded from the Hands-on Labs Document site found here:

http://docs.hol.vmware.com/

This lab may be available in other languages. To set your language preference and have a localized manual deployed with your lab, you may utilize this document to help guide you through the process:

http://docs.hol.vmware.com/announcements/nee-default-language.pdf


Lab Guidance


The lab consists of two sites, Region A and Region B. Each Site consists of a single cluster. Each Cluster contains 2 ESXi Hosts. Region A is the Protected Site and Region B is the Recovery Site.

Corp is a marketing company for some of the largest software companies in the world. Their primary site is located in San Francisco, CA (Region A) and they currently have a secondary site located in Reston, VA (Region B). The primary site is home to executive management, sales, accounting, human resources, information technology (IT) and most importantly, marketing. Due to their success they noticed that many of their new customers were located on the east coast and in order to service these new customers with the same level of service that they were able to deliver to their west coast customers, they needed to open an office on the east coast. They chose Reston, VA as the location of their secondary site. The Reston office will be a smaller version of the primary site located in San Francisco and will be the home to a small sales team, a few accounting team members and marketing. In order to ensure that the team located in Reston is able to access resources as quickly as they would as if they were in San Francisco the company decided to invest in IT infrastructure at the Reston office that will also include enough infrastructure to recover all primary applications in the event that a disaster were to strike at their primary site in San Francisco.

Within this lab, we will assist the Corp IT team in setting up Site Recovery Manager in San Francisco (Region A) so that they can recover VMs in Reston (Region B). They need assistance with all aspects of Site Recovery Manager, both basic and advanced functionality.


 

Activation Prompt or Watermark

 

When you first start your lab, you may notice a watermark on the desktop indicating that Windows is not activated.  

One of the major benefits of virtualization is that virtual machines can be moved and run on any platform. The Hands-on Labs utilizes this benefit and we are able to run the labs out of multiple datacenters. However, these datacenters may not have identical processors, which triggers a Microsoft activation check through the Internet.

Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoft licensing requirements. The lab that you are using is a self-contained pod and does not have full access to the Internet, which is required for Windows to verify the activation. Without full access to the Internet, this automated process fails and you see this watermark.

This cosmetic issue has no effect on your lab. If you have any questions or concerns, please feel free to use the support made available to you either at VMworld in the Hands-on Labs area, in your Expert-led Workshop, or online via the survey comments as we are always looking for ways to improve your hands on lab experience.

 

 

Lab Ready State

 

Before beginning the lab, verify that the lab setup tasks have completed successfully. The Lab Status shown on the Control Center desktop should say Ready with date and time.

If the Lab Status is indicating something other than Ready, please wait at least 5 minutes for the lab startup process to complete.

 

 

Copy and Paste

 

During the lab, you may wish to copy and paste text to the console.

  1. Click the SEND TEXT link in the top-left corner
  2. Write the text you want to paste into the console in the popup window
  3. Click SEND (be sure that you have selected the application - and the field inside the application - you want to paste into)
  4. Check that the text has been sent to the application (final result is shown)

 

 

Non-US Keyboard

 

If you have a Non-US keyboard, there is a chance that you will have difficulty finding certain keys.

To work around this, you can use the onscreen keyboard by clicking on the quick-launch shortcut pinned to the taskbar of the Control Center - or by going to Start> Programs> Accessories> Ease of Access> On-Screen Keyboard

 

 

 

Unpin Alarms and Work in Progress

 

It is a recommendation to unpin the Alerts and Work in Progress windows on the right-hand side of the vSphere Web Client. This will allow you to work more easily within the lab providing you with more visibility to the objects that you will be working with within this lab.  At any time during the lab, you can unpin Alerts and/or Work in Progress to view the contents of those windows.

  1. To unpin Alerts and Work in Progress, select the Pin button.

After unpinning Alerts and Works in Progress, you can always view the contents of these windows by selecting them on the right-hand side of the vSphere Web Client window.

 

 

Chrome Full Screen

 

To use the full screen option in Chrome, select the Options button on the right-hand side of the Chrome window and select the square box located next to the Zoom option.

 

Module 1 - Lightning Lab: Failing over a site with Site Recovery Manager (15 minutes, Beginner)

Module Overview


This module will allow you to experience some of the capabilities of Site Recovery Manager without any in-depth configuration requirements. The module has been designed to allow you to complete all required actions in 15 minutes or less.

This Module contains the following lessons:

Total time required: 15 minutes.


Lesson 1: Fail-over a virtual machine


During this section, you will perform a failover of an application that has already been protected with Site Recovery Manager and been replicated to the Region B data center using vSphere Replication.


 

Getting Started

 

Before you begin, please ensure that the Lab Status indicates Ready. If the status is anything other than Ready, you may need to wait a few minutes for the back ground services within the lab to complete their startup routine.

If after 5 minutes the lab is still indicating a status other than Ready, please end the lab and re-deploy another instance.

 

 

vSphere Replication

 

You need to verify that the replication of the intro-app-01 virtual machine has been configured and that we have successfully replicated the virtual machine to the data center in Region B.

  1. From the Home Icon of the vSphere 6.5 web client
  2. Select the vSphere Replication icon.

 

 

VM fail-over with Site Recovery Manager

 

Now that you have verified that the intro-app-01 virtual machine has been replicated to the Region-B data center, you are ready to fail-over this application using Site Recovery Manager.

1. From the current page, select the Home icon at the top of the screen.

2. Select the Site Recovery menu option from the drop down menu.

 

Lesson 2: Re-protect and fail back.


In this lesson you will configure re-protection of the application that was failed-over to the RegionB01 data center in the previous lesson. This lesson will conclude with you failing the intro-app-01 application back to its original location in the RegionA01 data center.


 

Site Recovery Manager

 

Now that you have verified that the intro-app-01 virtual machine has been successfully recovered to RegionB01, you are going to begin the process of preparing the virtual machine to be failed back to the RegionA01 data center using Site Recovery Manager.

This process can be accomplished from either vCenter Server. However, because we are already viewing the Web client for the vCenter at RegionB01, we will perform all actions at this site.

  1. From the current page, expand the navigation menu by clicking the Home icon at the top of the screen.
  2. Select the Site Recovery menu option from the drop down menu.

 

 

vSphere Replication

 

To monitor the replication status of the intro-app-01 virtual machine...

  1. From the current page, expand the navigation menu by clicking the Home icon at the top of the screen.
  2. Select the vSphere Replication menu option from the drop down menu.

 

 

Virtual Machine Fail-back with Site Recovery Manager

 

You are now going to navigate back to the Site Recovery Manager UI to execute the fail-back process on the intro-app-01 virtual machine.

This process can be accomplished from the vSphere Web Client from either vCenter Server. We will utilize the Web Client for RegionA01 as we are currently connected to it.

  1. From the current page, expand the navigation menu by clicking the Home icon at the top of the screen.
  2. Select the Site Recovery Manager menu option from the drop down menu.

 

Conclusion


In this module, you successfully failed the intro-app-01 virtual machine over to the recover site at the RegionB01 data center. You then re-protected the virtual machine which, with minimal administrative overhead, reversed the replication and protection directions of the intro-app-01 application.

You concluded this module by using Site Recovery Manager to fail-over the virtual machine back to its original location in the RegionA01 data center.


 

You've finished Module 1

 

Congratulations on completing Module 1.

Site Recovery Manager provides the following benefits:

Hopefully, this module has shown you some to the benefits that Site Recovery Manager can provide.

You can proceed to the next module listed below or any other module which interests you most.

Module 2 - Executing a Disaster Recovery Plan using Site Recovery Manager (60 minutes, Beginner)

 

 

How to End Lab

 

To end your lab, click on the END button.  

 

Module 2 - Executing a Disaster Recovery Plan using Site Recovery Manager (60 minutes, Beginner)

Module Overview


The Accounting Department has recently completed a migration of all company financial data to a new multi-tiered application platform. The new application consists of three virtual machines. Virtual machines Acct-App-01, Acct-DB-01 and Acct-Web-01.

Once the Accounting department's virtual machines are in production they are completely dependent on one another so it's critical that they can be recovered together. Failure to operate these virtual machines together or manage them in a specified sequence specified by the application vendor could lead to data loss or an unrecoverable system state.

The Accounting Department would like you to ensure that this business critical application is protected and recoverable in the event of an anticipated or unexpected outage of the primary data center.

In order to avoid being audited, the company must also be able to provide a report on the status of the Disaster Recovery Plan for the application at any given time. This report should detail the recovery process and clearly identify if the execution of the plan would be successful or not.

You will also have the opportunity to create a site wide recovery plan to permit a fail-over of all virtual machines in the event of a catastrophic failure of the primary data center. You will then test your multi-vm recovery plan and as an optional step, have the opportunity to perform a complete site wide fail-over.

Finally, you will review Audit reports and see how you can utilize vRealize Log Insight and the SRM content pack to assit with monitoring your disaster recover plan.

Total time required: 60 minutes


Lesson 1: Protect Virtual Machines using Site Recovery Manger


This lesson will focus on creating a protection group containing two virtual machines.


 

Getting Started

 

The initial startup of the lab will automatically launch the Chrome browser for both vcsa-01a.corp.local and vcsa-01b.corp.local. The lab start up process will also log you in as administrator@corp.local.

  1. Check the URL of the browser to verify that you are initially using vcsa-01a.corp.local for this lesson.

 

Lesson 2: Create a Virtual Machine Recovery Plan


After you have configured the protection group, you can create a recovery plan for virtual machines Acct-App-01, Acc-DB-01 and Acct-Web-01. A recovery plan controls every step of the recovery process, including the order in which virtual machines are recovered, IP address changes, and so on. Protection groups can be created from either protected site. As one might expect, recovery plans are created at the recovery site.


 

Getting Started

 

  1. Check the URL of the Web browser to verify that you are using the RegionA01 vCenter vcsa-01a.corp.local for this lesson.

 

 

Begin - Create a Recovery Plan

 

  1. From the vcsa-01a.corp.local vCenter web client select the Home icon.
  2. Select Site Recovery.

 

 

Completed Accounting Recovery Plan

 

  1. When complete you should see the new Accounting Recovery Plan listed.

You have completed lesson 2 of module 2. It is recommended that you now start lesson 3 of module 2.

 

Lesson 3: Test The Recovery Plan


After creating a recovery plan, it is beneficial to test the recovery plan to verify it works as expected. Site Recovery Manager features a non-disruptive testing mechanism to facilitate testing at any time. It is common for an organization to test a recovery plan multiple times after creation to resolve any issues encountered the first time the recovery plan was tested.


 

Test a Recovery Plan

 

  1. From the RegionA01 vcsa-01a.corp.local vCenter web client select the Home icon.
  2. Select Site Recovery.

 

 

Region B vCenter - Verify Test Recovery

 

  1. Minimize the vcsa-01a.corp.local vCenter Web Client and Maximize the vcsa-01b.corp.local vCenter Web Client.
  2. Verify that the vcsa-01b.corp.local vCenter Web Client is rendered for this part of the lesson.

 

Lesson 4: Create Site Wide Recovery Plan


This section will demonstrate creating a site-wide recovery plan with multiple protection groups that are already a part of other recovery plans.

With the successfull test completion of the Accounting Protection Group and Recovery Plan, you have been asked to ensure that Rainpole Corp. will be able to recover their entire San Francisco (Region A) data center in the event of either a planned or unplanned outage.


 

Create Site-Wide Recovery Plan

 

  1. From the RegionA01 vcsa-01a.corp.local vCenter web client select the Home icon.
  2. Select Site Recovery.

 

 

Initiate Site-Wide Recovery Plan

 

  1. Select the Site-Wide Recovery Plan in the left menu pane.
  2. Select the Monitor Tab.
  3. Select the Recovery Steps button.
  4. Expand the Power on Priority 3 VMs Recovery step to view the list of all the VMs that will be recovered as part of this recovery plan. 
  5. Select the green play icon in the Recovery Steps view to begin testing the Accounting recovery plan.

 

 

Verify Protection Group - Region B vCenter

 

  1. Minimize the vcsa-01a.corp.local vCenter Web Client and Maximize the vcsa-01b.corp.local vCenter Web Client.
  2. Verify that the vcsa-01b.corp.local vCenter Web Client is rendered for this part of the lesson.

 

 

Cleanup The Recovery Test

 

  1. Select the Home Icon.
  2. Select Site Recovery from the dropdown menu.

 

Lesson 5: Review Audit Reporting in Site Recovery Manager


Recovery plan histories provide information about each run, test, or cleanup of a recovery plan. The history contains information about the result and the start and end times for the whole plan and for each step in the plan. You can export history at any time, but history always contains entries only for completed operations. If an operation is in progress, the history appears after the operation completes.


 

Select Recovery Plan

 

  1. From the RegionA01 vcsa-01a.corp.local vCenter web client select the Home icon.
  2. Select Site Recovery.

 

Lesson 6: Leverage Log Insight to provide real-time SRM monitoring


The Site Recovery Manager (SRM) Content pack for VMware vRealize Log Insight collects, imports, and analyzes logs to provide real-time answers to problems related to systems, services, and applications, and derive important insights that are related to SRM.

In this Module you will explore Log Insight and the SRM content pack to assit with monitoring your disaster recover plan to ensure that the SDDC environment is functioning as expected.


 

Getting Started with the Log Insight Management Pack for SRM

 

  1. From the vcsa-01a.corp.local web client select a new browser tab to open a new page

 

Conclusion


Congratulations on completing Module 2.

The primary features of Site Recovery Manager, creating protection groups and recovery plans along with testing the recovery plans were covered in this module. The additional items covered in this module were integration with vRealize Log Insight and audit reporting. More details on these solutions can be found in VMware Documentation and in other resources such as VMware Blogs and the VMware Knowledge Base.


 

You've finished Module 2

 

Site Recovery Manager provides the following benefits:

Hopefully, this module has shown you some to the benefits that Site Recovery Manager can provide.

You can proceed to the next module listed below or any other module which interests you most.

 

 

How to End Lab

 

To end your lab, click on the END button.  

 

Module 3 - Site Recovery Manager Advanced Topics (30 minutes, Advanced)

Module Overview


Site Recovery Manager, in addition to providing the capability to fail-over and recover virtual machines between data centers, also includes a number of advanced features that can serve to enhance the recovery capabilities of the solution. In this module, we will explore a number of these features.

Lesson 1: Virtual Machine Recovery Properties Overview

Lesson 2: Customizing the Virtual Machine IP Address During Failover

Lesson 3: Virtual Machine Start-up Options

Lesson 4: vSphere Replication, Advanced Options


Lesson 1: Virtual Machine Recovery Properties Overview


In this lesson, we will introduce a number of the advanced options available within Site Recovery Manager for individual VM recovery.


 

Getting Started

 

Before you begin, please ensure that the Lab Status indicates Ready. If the status is anything other than Ready, you may need to wait a few minutes for the back ground services within the lab to complete their startup routine.

If after 5 minutes the lab is still indicating a status other than Ready, please end the lab and re-deploy another instance.

 

 

vSphere Replication

 

  1. From the current screen, select the Home icon at the top of the screen of the vSphere web client for vcsa-01a.corp.local
  2. Select the vSphere Replication menu item from the drop down list.

 

 

Open Site Recovery Manager

 

Now that we have ensured that all the Sales VMs have been replicated, we will examine the various configuration options available during recovery on an individual VM basis. These options are accessed through the Site Recovery Manager UI.

  1. From the current screen, select the Home icon at the top of the window.  A drop-down list will appear.
  2. Select Site Recovery from the drop-down list.

 

 

Recovery Plans

 

Select the Recovery Plans menu item from the Navigator menu under the Inventories section.

 

 

Individual Virtual Machine Recovery Options

 

There are 2 virtual machines within the Sales Application Recovery Plan.  These 2 virtual machines are part of a multi-tiered sales application. The 2 VMs are as follows:

You will now examine the individual recovery properties for these virtual machines. 

  1. Select the sales-app-01 VM
  2. Select Actions
  3. Select Configure Recovery from the drop down menu

 

 

Lesson Conclusion

In this lesson, we reviewed the Site information within Site Recovery Manager and ensured that both Sites were connected.  We then reviewed each action available for individual VM recovery.  Those actions included:

 

Lesson 2: Customizing the Virtual Machine IP Address During Failover


Due to budget constraints, the networking team was unable to extend their IP network across both Region A and Region B.  Therefore, during recovery, it is a requirement that the IP addresses of each VM being recovered are modified to match the network environment at Region B.

In this lesson, we will customize the IP addresses to be used for the Sales virtual machines in the event that they need to be recovered to the Region B data center due to a planned migration of disaster.


 

Getting Started

 

We will start from the vSphere Web Client homepage on vcsa-01a.corp.local.  

  1. From the current view within the vSphere web client, select the Home Icon at the top of the main window.
  2. Select the Site Recovery option from the drop down menu.

 

 

Select Sales Recovery Plan

 

  1. Highlight Sales Application recovery plan in the left menu pane.
  2. Select the Related Objects tab.
  3. Select the Virtual Machines button.

You should now see both Sales virtual machines in the main part of the UI.  They are as follows:

 

 

Customize IP Address for the App Server

 

Let's start by customizing the IP address of the sales-app-01 virtual machine. 

  1. Highlight the sales-app-01 virtual machine.
  2. Select the Actions tab.
  3. Select Configure Recovery from the available menu options.

 

 

IP Customization Rules

 

Another way to ensure that a virtual machine, or a group of virtual machines, is able to obtain an IP address on the correct subnet after being recovered is through the use of IP customization rules.

These rules apply to virtual machines failing over from the protected sites IPv4 subnet to the recovery sites IPv4 subnet.  For example, from 10.15.23.0/24 to 10.16.24.0/24.

The IP customization rule states that during recovery Site Recovery Manager evaluates the existing IP configuration of the recovered virtual machines NICs and reconfigures static IPs found on the 10.15.23.0/24 subnet for the 10.16.24.0/24 subnet.

If the rule matches, Site Recovery Manager derives the new static IPv4 address from the old one by preserving the host bits of the original IPv4 address, applying it to the target subnet. For example, if the original protected site address is 10.15.23.55/24, the new address would be 10.16.24.55/24.

If the default gateway text box is empty, Site Recovery Manager derives the new gateway parameter from the original one by preserving the host bits of the original IPv4 address and placing it in the target subnet. For example, if the original protected site gateway is 10.15.23.1, the new gateway is 10.16.24.1.

If you specify an explicit gateway parameter, Site Recovery Manager checks that the IPv4 address syntax is correct and applies it exactly.

Site Recovery Manager applies DNS and other parameters as specified. DHCP-enabled NICs are not subject to customization as their network configuration remains unchanged during recovery.

Let's create an IP Customization Rule to be used for our sales-db-01 virtual machine.

  1. Select the Back arrow within Navigator menu to go back to the Site Recovery Manager homepage.

 

 

Configure IP Address for Database Server

 

We have one more virtual machine to configure IP Customization for, the Sales Database server.

  1. From the Navigator menu for RegionA01, select the Recovery Plans menu option.

 

 

Lesson Review

Both Sales virtual machines have now been configured to use a customized IP address during recovery.  

We used two different methods to customize the IP addresses used when the virtual machine is recovered. The first being a more individualized approach where you manually entered the IP address to be used during recovery. The second method you created an IP customization rule that was applied to all virtual machines residing or leveraging a particular portgroup mapping on the protected site.

In the next lesson, we will modify the start-up order for each virtual machine.

 

Lesson 3: Virtual Machine Start-up Options


In this lesson, we will configure the power-on options for the Sales application virtual machines within Site Recovery Manager.  The options we will configure include:


 

Getting Started

 

Let's start by navigating to the Site Recovery Manager main page. Ensure you are working within the RegionA01data center on vCenter vcsa-01A.corp.local.

  1. From your current location within the vSphere Web Client, select the Home icon at the top of the page.
  2. Choose the Site Recovery option from the drop down menu.

 

 

Recovery Plans

 

  1. Select Recovery Plans from the Navigator menu under the Inventories sub-section.

 

 

Lesson Review

In this lesson, we modified the Startup order of our VMs to ensure that our Sales Application starts correctly.  The Database server is powered-on first followed by the Application server. We used a combination of Priority Groups and VM Dependencies to start the VMs in the correct order allowing enough time for the necessary services to start on each VM.

 

Lesson 4: vSphere Replication, Advanced Options


In this lesson, we will review some of the advanced options within vSphere Replication.  These options include:

We have already setup replication for the two virtual machines that are a part of the Sales Application. We will use these 2 VMs to explore and configure the advanced replication options listed above.


 

Getting Started

 

vSphere Replication for each virtual machine is managed on a per-VM basis. To manage the vSphere replication properties of a virtual machine, you need to navigate to the VMs and Templates menu in the vSphere Web client.

We are going to use the sales-db-01 virtual machine for this lesson.

  1. From the current view within the vSphere web client on vcsa-01a.corp.local, select the Home icon at the top of the page.
  2. Select the VMs and Templates menu option from the drop down list.

 

 

Lesson Review

The Advanced options available within vSphere Replication gives you the flexibility to manage each individual VM separately based upon specific application requirements.  You can configure or make modifications to the replication settings of a virtual machine from within the vSphere Web Client.

 

Conclusion


In this module, you explored some of the advanced recovery capabilities available to you when you use Site Recovery Manager to protect and recover your virtual machines.


 

You've finished Module 3

 

Site Recovery Manager provides the following benefits:

Hopefully, this module has shown you some to the benefits that Site Recovery Manager can provide.

You can proceed to the next module listed below or any other module which interests you most.

Module 4 - Automating Site Recovery Manager tasks with vRealize Orchestrator (30 minutes, Advanced)

 

 

How to End Lab

 

To end your lab, click on the END button.  

 

Module 4 - Automating Site Recovery Manager tasks with vRealize Orchestrator (30 minutes, Advanced)

Module Overview


There have been a number of enhancements to the programmatic interaction with Site Recovery Manager (SRM) 6.5. These take a few forms, primarily: exposure of a number of new options in the SRM API and significant enhancements to the vRealize Orchestrator (vRO) plug-in for SRM to take advantage of these. The new functions available through the API and vRO plug-in are listed below.

These functions along with the functions previously exposed provide programmatic access to almost the full range of SRM functionality. This makes it that much easier to manage and maintain SRM programmatically, saving time and improving accuracy and efficiency. Additionally, SRM 6.5 now fully supports unattended/silent installation and upgrades. This makes the deployment of SRM much faster and easier, saving time and money.

In this module you will use the VMware vRealize Orchestrator plug-in for vSphere Replication and Site Recovery Manager to leverage pre-created workflows to extend the automation capabilities for certain vSphere Replication and Site Recovery Manager operations.

Topics Covered in this lab:

Total time required: 30 minutes


Lesson 1: vSphere Replication using vRealize Orchestrator


The VMware vRealize Orchestrator plug-in for vSphere Replication allows VMware administrators to simplify the management of their vSphere Replication infrastructure by leveraging the workflows provided by vRealize Orchestrator. The vRealize Orchestrator plug-in for vSphere Replication extends automation capabilities for certain vSphere Replication operations by including them in vRealize Orchestrator workflows.

In this lesson you will use pre-built out-of-the-box workflows that cover certain existing vSphere Replication actions.


 

Getting Started

 

  1. Minimize both vCenter web browsers and select the vRealize Orchestrator Client located on desktop.

 

 

Configure Replication Using vRealize Orchestrator

 

  1. From the drop-down menu select Design.

 

 

Verify Replication From vCenter

 

  1. Minimize the vSphere Orchestrator Client.
  2. Maximize the vcsa-01a.corp.local vCenter Web Browser.

 

Lesson 2: Add a Virtual Machine to a Protection Group Using vRealize Orchestrator


This lesson will demonstrate how to use vRealize Orchestrator to add a virtual machine to a protection group.


 

Getting Started

 

  1. Minimize the web browser and select the vRealize Orchestrator Client located on desktop.

Note: You can proceed to the next step if you are already logged into to the vRO client.

 

Lesson 3: Protect a Virtual Machine Using vRealize Orchestrator


This lesson will demonstrate how to protect a virtual machine using a vCenter context action, vRealize Orchestrator workflow.


 

Getting Started

 

If you have just finished Lesson 2 minimize the vRealize Orchestrator client and maximize the Google Chrome browser for the vCenter Web Client vcsa-01a.corp.local

  1. Check the URL of the browser to verify that you are using vcsa-01a.corp.local for this lesson.

 

 

Protect A Virtual Machine Workflow

 

  1. Under the vcsa-01a.corp.local vcenter, expand the RegionA01 datacenter and RegionA01-COMP01 cluster and locate the VM Sales-Web-01.
  2. Select and right click on Sales-Web-01.
  3. Select All vRealize Orchestrator plugin Actions.
  4. Select the workflow Protect Virtual Machine.

 

Lesson 4: Add a Virtual Machine to an Existing Recovery Plan


This lesson will demonstrate how to use vRealize Orchestrator to add a virtual machine to an existing recovery plan.


 

Begin - Add a Virtual Machine to an Existing Recovery Plan

 

  1. From the RegionA01 vcsa-01a.corp.local vCenter Home screen, select the Hosts and Clusters Icon.

 

Lesson 5: Test the Recovery Plan Using vRealize Orcestrator


In this lesson you will test the Accounting Recovery Plan using vRealize Orchestrator workflows from the recovery site RegionB01 to ensure that the recovery plan completes successfully.

In a production environment there are two vRealize Orchestrator instances configured, one instance configured as part of the production vCenter (RegionA01) and the other instance configured as part of the recovery site vCenter (RegionB01). This architecture would provide the capability to use automation from both sites.


 

Getting Started

 

  1. Minimize the web browser and select the vRealize Orchestrator Client located on desktop.

 

 

Begin - Test Recovery Plan

 

  1. Verify that you are connected to the vro-01b.corp.local vRealize Orchestrator server.
  2. From the drop-down menu select Design.

 

 

Recovery Plan Clean-Up

 

  1. Minimize the active vSphere Orchestrator Client.
  2. Maximize the vcsa-01a.corp.local vCenter web client browser.

 

Conclusion


You have learned in this module that VMware vCenter Orchestrator plug-in for Site Recovery Manager allows Site Recovery Manager administrators to simplify the management of their Site Recovery Manager infrastructure by extending the robust workflow automation platform of vRealize Orchestrator.


 

You've finished Module 4

 

Site Recovery Manager provides the following benefits:

Hopefully, this module has shown you some to the benefits that Site Recovery Manager can provide.

You can proceed to the next module listed below or any other module which interests you most.

Module 5 - SRM integration with NSX and Storage Policy Based Protection Groups and Stretched Storage (30 minutes, Advanced)

 

 

How to End Lab

 

To end your lab, click on the END button.  

 

Module 5 - SRM integration with NSX and Storage Policy Based Protection Groups and Stretched Storage (30 minutes, Advanced)

Hands-on Labs Interactive Simulation: Introduction to Site Recovery Manager New Features


VMware has expanded the capabilities of Site Recovery Manager with the new version 6.5 release, which delivers unprecedented levels of protection and functionality as well as new use cases through the addition of capabilities such as storage policy based protection groups, support for stretched storage with orchestrated vMotion, and enhanced integration with VMware NSX.


 

Storage Policy Based Protection Groups

Site Recovery Manager 6.5 adds a new type of protection group; the storage policy-based protection groups. Storage policy-based protection groups use vSphere storage profiles to identify protected datastores and virtual machines. They automate the process of protecting and unprotecting virtual machines and adding and removing datastores from protection groups. Storage profile-based protection groups enable deep integration with virtual machine provisioning tools like VMware vRealize Automation. This combination makes it easier than ever to deploy and protect virtual machines.

Storage policy-based protection groups utilize vSphere tags in combination with vSphere storage policy based management to enable automated policy based protection for virtual machines. Storage policy-based management enables vSphere administrators to automate the provisioning and management of virtual machines storage to meet requirements like performance, availability and protection. vSphere tags allow for the ability to attach metadata to vSphere inventory, in this case datastores, which makes these objects more sortable, searchable and possible to associate with storage policies.

When any virtual machine, new or existing, is associated with that policy and placed on the replicated datastore, Site Recovery Manager protection is automatic. If a virtual machine is disassociated from that policy and/or moved off the datastore it is automatically unprotected. The same happens for datastores and the virtual machines on them.

 

 

Stretched Storage and Orchestrated vMotion

In prior versions of Site Recovery Manager customers had to make a choice between using Site Recovery Manager or vSphere Metro Storage Clusters/Stretched Storage to provide a multisite solution that was optimized for either site mobility or disaster recovery without being able to attain the benefits of both solutions simultaneously. Site Recovery Manager now supports using cross-vCenter vMotion in combination with stretched storage, thereby combining the benefits of Site Recovery Manager with the advantages of stretched storage.

The integration of stretched storage with Site Recovery Manager allows customers to achieve what was previously only possible with vSphere Metro Storage Clusters:

 

 

Enhanced Integration with VMware NSX

NSX supports creating Universal Logical Switches, which allow for the creation of layer-2 networks that span vCenter boundaries. This means that when utilizing Universal Logical Switches with NSX there will be a virtual port group at both the protected and recovery site that connect to the same layer-2 network

When virtual machines are connected to port groups that are backed by Universal Logical Switches, Site Recovery Manager will automatically recognize this and not require manual network mapping between the protected and recovery locations. Site Recovery Manager intelligently understands that it is logically the same network on both sites and thereby automatically links the protected and recovery networks.

 

 

Interactive Simulation

This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.

  1. Click here to open the interactive simulation. It will open in a new browser window or tab.
  2. When finished, click the “Return to the lab” link to continue with this lab.

The lab continues to run in the background. If the lab goes into standby mode, you can resume it after completing the module.

 

Conclusion


SRM has tight integration with vSphere and NSX, offers an integrated storage replication option, and can manage and test recovery plans. It’s capable of orchestrating recovery for multiple failure scenarios including Partial Application Failure, Full Application Failure, and Site Failure.


 

You've finished Module 5

 

Conclusion

Thank you for participating in the VMware Hands-on Labs. Be sure to visit http://hol.vmware.com/ to continue your lab experience online.

Lab SKU: HOL-1805-01-SDC

Version: 20180724-125737