Hol 1705 SDC 1

HOL-1705-SDC-1
Table of Contents
Lab Overview - HOL-1705-SDC-1 - Site Recovery Manager: Data Center Migration and
Disaster Recovery ............................................................................................................. 3
Overview of Site Recovery Manager ....................................................................... 4
Lab Overview .......................................................................................................... 5
Lab Guidance .......................................................................................................... 7
Module 1 - Lighting Lab: Failing over a site with Site Recovery Manager (15 minutes,
Beginner) ........................................................................................................................ 14
Module Overview .................................................................................................. 15
Lesson 1: Fail-over a virtual machine .................................................................... 16
Lesson 2: Re-protect and fail back. ....................................................................... 38
Conclusion............................................................................................................. 71
Module 2 - Executing a Disaster Recovery Plan using Site Recovery Manager (60
minutes, Beginner) ......................................................................................................... 73
Module Overview .................................................................................................. 74
Lesson 1: Protect Virtual Machines using Site Recovery Manger .......................... 75
Lesson 2: Create a Virtual Machine Recovery Plan................................................ 88
Lesson 3: Test The Recovery Plan ......................................................................... 96
Lesson 4: Create Site Wide Recovery Plan .......................................................... 111
Lesson 5: Review Audit Reporting in Site Recovery Manager.............................. 133
Lesson 6: Leverage VIN To Ensure Dependent VMs Are Protected Together....... 141
Conclusion........................................................................................................... 145
Module 3 - Site Recovery Manager Advanced Topics (30 minutes, Advanced).............. 147
Module Overview ................................................................................................ 148
Lesson 1: Virtual Machine Recovery Properties Overview ................................... 149
Lesson 2: Customizing the Virtual Machine IP Address During Failover............... 175
Lesson 3: Virtual Machine Start-up Options ........................................................ 202
Lesson 4: vSphere Replication, Advanced Options.............................................. 217
Conclusion........................................................................................................... 228
Module 4 - Automating Site Recovery Manager tasks with vRealize Orchestrator (30
minutes, Advanced) ...................................................................................................... 230
Module Overview ................................................................................................ 231
Lesson 1: vSphere Replication using vRealize Orchestrator ................................ 232
Lesson 2: Add a Virtual Machine to a Protection Group Using vRealize
Orchestrator........................................................................................................ 248
Lesson 3: Protect a Virtual Machine Using vRealize Orchestrator ....................... 257
Lesson 4: Add a Virtual Machine to an Existing Recovery Plan ........................... 273
Lesson 5: Test the Recovery Plan ........................................................................ 282
Conclusion........................................................................................................... 300
Module 5 - SRM integration with NSX and Storage Policy Based Protection Groups and
Stretched Storage (30 minutes, Advanced) .................................................................. 302
Hands-on Labs Interactive Simulation: Introduction to Site Recovery Manager 6.1
New Features ...................................................................................................... 303
HOL-1705-SDC-1 Page 1
HOL-1705-SDC-1
Conclusion........................................................................................................... 305
HOL-1705-SDC-1
Lab Overview -
HOL-1705-SDC-1 - Site
Recovery Manager: Data
Center Migration and
Disaster Recovery
HOL-1705-SDC-1
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).
Provision and manage storage and replication policies at the virtual machine
level.
Setup centralized recovery plans in minutes.
Enable individual tenants to provision disaster protection through pre-defined
policies.
Perform fully automated orchestration of site failover and planned migrations and
failback with a single click.
Perform automated testing of recovery plans in an isolated network to avoid
impacting production applications.
Test recovery plans as frequently as needed without disruption to ensure
predictability of recovery time objectives (RTO) and to simplify regulatory
compliance.
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
HOL-1705-SDC-1
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 (15 minutes, Beginner).
Module 2 - Executing a Disaster Recovery plan using 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)
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.
The student will use Site Recovery Manager to execute a disaster recovery plan
for a single Corp.local application.
Reprotect the single Corp.local application once it has been recovered and then
failback the application to the San Francisco data center.
Module 2: Creating and Executing a Disaster Recovery Plan with Site

Recovery Manager(60 minutes, Beginner)
The student will create a Recovery Plan and then test and perform a recovery
within Site Recovery Manager.
Include multiple Protection Groups within a single Recovery Plan.
Perform a test of the Recovery Plan.
Review the reports available within Site Recovery Manager for auditing purposes.
Learn how vRealize Infrastructure Navigator integrates with Site Recovery
Manager.
Module 3: Site Recovery Manager Advanced Topics (30 minutes, Advanced)
HOL-1705-SDC-1
The student will utilize the Advanced options within Site Recovery Manager to
customize their Disaster Recovery Plan.
Review the properties of Virtual Machines during a Recovery.
Customize the IP Address of Virtual Machines during a Recovery.
Modify the Start-Up options of Virtual Machines.
Build User Prompts within the Recovery Plan that require action of the user
executing the Recovery.
Review the options available within vSphere Replication for individual Virtual
Machine replication.
Provide a new user within the Corp.local organization permission to manage Site
Recovery Manager.
Module 4 - Automating Site Recovery Manager tasks with vRealize

Orchestrator (30 minutes, Advanced)
Perform vSphere Replication using vReailze Orchestrator.

Using vRealize Orchestrator the student will protect a virtual machine by adding it
to a Protection Group and Recovery Plan and then performing test recovery.
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
HOL-1705-SDC-1
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
HOL-1705-SDC-1
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.
Is the Lab Ready
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.
If the Lab Status is indicating something other than Ready, please wait at least 5
minutes for the lab startup process to complete.
HOL-1705-SDC-1
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.
HOL-1705-SDC-1
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
HOL-1705-SDC-1
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.
HOL-1705-SDC-1
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.
HOL-1705-SDC-1
Manual Startup
If you experience any difficulties with the below process be sure to use the Help >
Raise hand feature on the console to request assistance.
Both vCenter Web clients for RegionA and RegionB will render via the Chrome browser
and log you in automatically as administrator@corp.local. You can select either the
RegionA or the RegionB vCenter Web client from the task bar.
1. Verify that the following VMs have started: vr-01a and VIN-01a. Repeat the
above process on the RegionB Web Client verifying that the following VMs have
started: vr-01b Your lab is now ready for you to begin.
HOL-1705-SDC-1
Module 1 - Lighting Lab:

Failing over a site with
Site Recovery Manager
(15 minutes, Beginner)
HOL-1705-SDC-1
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:
Lesson 1: You will perform a planned migration of a virtual machine from the
primary data center to the DR location. The virtual machine has already been
replicated to the secondary site and is ready to be failed over.
Lesson 2: Upon successful completion of the virtual machine fail-over, you will
leverage the re-protect function of Site Recovery Manager to bring the virtual
machine back from the secondary site with minimal administration effort.
Total time required: 15 minutes.
HOL-1705-SDC-1
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.
HOL-1705-SDC-1
Launch the vSphere Web Client
The initial startup of the lab will automatically launch separate Chrome browser
windows for both vcsa-01a.corp.local and vcsa-01b.corp.local. The lab start up process
will also log you in to the vSphere Web Client 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.
HOL-1705-SDC-1
Maximize the View
1. If the Recent Tabs is visible at the bottom of the window, select the thumb-tac
icon in the lower right side of the vSphere Web Client page to minimize this
pane. This will help maximize the view on the main section of the user interface.
HOL-1705-SDC-1
vSphere Replication
You need to verify that the replication of the Engineering team's Lightning Application
virtual machine has been configured and that we have successfully replicated the virtual
machine to the data center in Region B.
From the home screen of the vSphere 6.0 web client, select the vSphere Replication
icon in the Inventories section of the main window pane.
Verify replication connectivity status for each location
Select the Home tab at the top of the main vSphere Replication window pane. Verify
that the vCenter server status indicates Enabled (OK) under the vSphere Replication
column.
Note: It could take up to 1 minute for the query to complete and the status
information to be displayed.
HOL-1705-SDC-1
Now that you have verified that replication is configured and working between both
locations, you need to check that the virtual machine "lightning-01" has been
successfully replicated.
HOL-1705-SDC-1
Identify replicated virtual machines
1. To ensure that we view all replications outbound from the Region A data center,
highlight vcsa-01a.corp.local in the vCenter Column of the main section of the
vSphere Replication page.
2. Select the Monitor button from the Home tab menu options.
Locate the specified replicated virtual machine
1. Select the Monitor tab.

2. Select the vSphere Replication button
3. Select the Outgoing Replications menu option in the left hand navigation pane
of the main section of the page.
4. Locate Lightning-01 and highlight the virtual machine by clicking to the
right of the vm name under the Virtual Machine column.
HOL-1705-SDC-1
5. Details regarding the replication status of Lightning-vm are displayed under the
Replication Details tab. Examine these details and verify that the Status is
displaying OK.
HOL-1705-SDC-1
VM fail-over with Site Recovery Manager
Now that you have verified that the Lightning-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, navigate back to the home page by clicking the Home icon at
the top of the screen.
2. Select the Home menu option from the drop down menu.
HOL-1705-SDC-1
From the Home tab, click the Site Recovery icon to access the Site Recovery Manager
Home page.
HOL-1705-SDC-1
Recovery Plan
1. On the Site Recovery Home page, select the Recovery Plans menu item
under the Inventories section.
HOL-1705-SDC-1
Recovery Plans Inventory List
The Recovery Plans Inventory is listed in the left menu pane. These are all of the
currently configured Recovery plans.
1. Select the Lightning Application Recovery Plan from the inventory.
HOL-1705-SDC-1
Authenticate to Site Recovery Manager
1. You will be prompted to enter the appropriate credentials to authenticate to Site

Recovery Manager.
Enter the following user account information.
Username: Administrator@corp.local
Password: VMware1!
2. Click the Log Inbutton to proceed.
HOL-1705-SDC-1
Lightning Recovery Plan
You are now going to start the recovery plan for the Lightning application. In a later
module, you will explore the various recovery and testing options in greater detail.
With the Lightning Application Recovery Plan highlighted in the inventory tree...
2. Select the Recovery Steps option button.
3. Select the red circular button with the play symbol inside it. This button launches
the Recovery Confirmation Dialog box.
HOL-1705-SDC-1
Recovery Options Selection
1. Place a check mark in the box. This check mark confirms that you understand that
proceeding forward from this point will change both the infrastructure and virtual
machines at both the protected and recovery sites.
2. Of the two Recovery Types available, select the Planned Migrationoption.
3. Click the Next button to continue.
HOL-1705-SDC-1
Begin VM fail-over
1. Verify that your selections from the previous screen are correct, then click the
Finish button to begin executing the recovery of the Lightning-01 virtual
machine from the Region-A to the Region-B data center.
HOL-1705-SDC-1
Monitor Recovery Progress
You are now able to monitor the recovery of the Lightning-01 vm as Site Recovery
Manager steps through each step of the recovery plan. The recovery process should
take no longer than a few minutes.
1. Click the indicted arrows to expand the various steps to view additional information.
HOL-1705-SDC-1
Recovery Complete
1. Once the recovery plan has completed executing, you will see that all the steps within
the plan indicate a status of "Success" with the over-all plan status at the top of the
main window pane displaying a "Recovery complete" message.
Let's verify that the Lightning-01 virtual machine has indeed been powered down at the
Region-A data center and is now running on the vSphere infrastructure located at the
Region-B data center.
HOL-1705-SDC-1
Browse virtual machine inventory
From the current screen...
1. Select the home icon at the top of the Web client page.
2. From the drop down menu, select the VMs and Templates menu item.
HOL-1705-SDC-1
Verify virtual machine status at the RegionA01 data center
In the Inventory tree on the left side of the screen...
1. Expand the Protected VM's folder under the RegionA01 data center and verify that
the Lightning-01 virtual machine is powered off.
HOL-1705-SDC-1
Access Region-B vCenter - Verify Test Recovery
1. Select the other vSphere Web Client Chrome browser from the task bar.
2. In the browser URL, verify that the vcsa-01b.corp.local is rendered for this part of
the lesson.
HOL-1705-SDC-1
Navigate to the VMs and Templates view
From the Home view of the vSphere web client, select the VMs and Templates icon.
HOL-1705-SDC-1
Validate the running status of the Lightning Application

vm.
1. Expand the Recovered VM's folder under the RegionB01 data center and verify
that the Lightning-01 virtual machine is powered on.
HOL-1705-SDC-1
Lesson 2: Re-protect and fail back.

In this lesson you will configure re-protection of the application that that was failed-over
from the previous lesson. You will then proceed to fail the Lightning application back to
its original location in the RegionA01 data center.
HOL-1705-SDC-1
Now that you have verified that the Lightning-01 application 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 logged into 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
2. Select the Site Recovery Manager menu option from the drop down menu.
HOL-1705-SDC-1
Recovery Plan
1. From the Site Recovery Manager page, select the Recovery Plans option under
the Inventories subsection in the left hand navigation menu.
HOL-1705-SDC-1
Recovery Plan Inventory List
1. Select the Lightning Application Recovery Plan from the menu on the left
side of the screen.
HOL-1705-SDC-1
Authenticate to Site Recovery Manager
You will be prompted to authenticate to the Site Recovery Manager instance at the
RegionA01 data center from the RegionB01 data center.
Please enter the following credentials:
Password: VMware1!
Click the log In button to access the Site Recovery Manager UI.
HOL-1705-SDC-1
Recovery Plan view
1. Select the Monitortab from the top of Recovery Plan UI.
HOL-1705-SDC-1
Lightning Application Recovery Plan
You are now going to reverse the direction of both the replication and protection for the
Lightning-01 virtual machine by executing the re-protect feature of Site Recovery
Manager.
1. Ensure that the Lightning Application Recovery Plan menu item has been
selected in the left menu.
2. Select the Monitortab at the top of the main section of the page.
3. Select the Recovery Steps button below the Monitor tab.
4. Click on the Re-protect button (Shield with lightning bolt icon) below the
Description field on the main page.
HOL-1705-SDC-1
Re-protect a Virtual Machine
1. Place a check mark into the confirmation dialog box. (The Force Cleanup option
should be greyed out and not available as an option at this time.)
2. Select Next to continue.
HOL-1705-SDC-1
Re-protect Confirmation
1. Verify that the selections you made in the previous step are correct. Then select
Finish to execute the re-protect workflow.
HOL-1705-SDC-1
Monitor the status of the re-protect workflow
1. Monitor the progress of the re-protect workflow.
This step could take a few minutes while the storage replication is reversed and
synchronized in the opposite direction for the Lightning-01 virtual machine. You can
monitor the status of the replication of the virtual machine by navigating to the vSphere
Replication page of the vSphere Web Client.
HOL-1705-SDC-1
vSphere Replication
To monitor the replication status of the Lightning-01 virtual machine...
2. Select the vSphere Replication menu option from the drop down menu.
Select Source vCenter Server
From the Home tab on the vSphere Replication page...
1. Insure that the Home tab is selected.
HOL-1705-SDC-1
2. Select vcsa-01b.corp.local as the source vCenter server.

3. Select the Manage tab from the top menu options.
HOL-1705-SDC-1
Select Target vSphere Replication Server
1. Select the Target sites menu option

2. Highlight the RegionA01 vSphere Replication appliance. The status of the
appliance should be displaying a "Not Authenticated" message.
3. Select the Reconnect button to initiate a connection to the remote vSphere
replication appliance in RegionA01.
Re-connect to the target vSphere Replication appliance
1. Select Yeswhen prompted to reconnect.
2. Enter the credentials for the remote vSphere Replication appliance.
Password: VMware1!
HOL-1705-SDC-1
3. Select OK to initiate the reconnect.
HOL-1705-SDC-1
Verify connection status
1. If the connection to the vSphere replication server in site RegionA01is successful,

you will see the status change to Connected.
2. Select theMonitortab at the top of the main UI.
HOL-1705-SDC-1
Monitor vSphere Replication
1. With the Monitor tab highlighted, select thevSphere Replication button

2. Select Outgoing Replicationsoption from the center menu.
3. Highlight the Lightning-01 virtual machine in the main section of the UI.
4. On the Replication Details tab at the bottom of the main screen, monitor the
progress of the replication of the Lightning-01 virtual machine.
Upon completion of the replication of the Lightning-01 virtual machine, the Status
indicator under the Replication Details tab should display an OK.
With the replication of the Lightning-01 virtual machine complete, you need to verify
that the Site Recovery Manager re-protect workflow completed successfully.
HOL-1705-SDC-1
2. Select the Site Recovery menu option from the drop down menu.
HOL-1705-SDC-1
Recovery Plans
1. From the Site Recovery Manager page, select the Recovery Plans option under
the Inventories subsection in the left hand navigation menu.
HOL-1705-SDC-1
side of the screen.
HOL-1705-SDC-1
Recovery Plan Status Validation
The Lightning Application Recovery plan should now display a status of "Ready". This
indicates that the previous workflow executed successfully and the plan is ready to be
executed to recover the virtual machine back to the RegionA01 data center, which is
now the recovery site for the application.
Select RegionA01 vSphere Web Client
You can now navigate to the VM's and Templates view in the vSphere Web Client to
verify that the information being displayed in the UI accurately shows the protection
status of the Lightning-01 virtual machine.
1. Navigate back to the Web Client for the RegionA01 data center by selecting the
appropriate vSphere Web Client browser tab at the top of the screen.
HOL-1705-SDC-1
Note Verify that the url for the Region A vCenter (vcsa-01a.corp.local) is displayed in
the address bar.
HOL-1705-SDC-1
VMs and Templates
2. Select the VMs and Templates menu option from the drop down menu.
Protected Virtual Machine status
1. Expand out the Protected VM's folder under the RegionA01 data center and verify
that the Lightning-01virtual machine icon is displayed with small orange, green and
blue squares on it. This icon indicates that this particular entity in the inventory is
owned and managed by a service other than vCenter. (Sight Recovery Manager)
This also indicates that the Lightning-01 virtual machine object in the RegionA01 data
center inventory is simply a placeholder object with no connected networks and will
HOL-1705-SDC-1
remain in this state until the vm is recovered by Site Recovery Manager. You can
highlight the Lightning-01 virtual machine in the inventory tree and view details about
which service is managing this entity on the VM summary tab.
HOL-1705-SDC-1
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 Lightning-01 virtual machine.
This process can be accomplished from either vCenter Server, accessed through the
vSphere Web client. We will utilize the Web Client for RegionA01 as we are currently
connected to it.
2. Select the Site Recovery Manager menu option from the drop down menu.
HOL-1705-SDC-1
Recovery Plan
1. From the Site Recovery Manager page, select the Recovery Plans option in the
left hand navigation pane under the Inventories menu item.
HOL-1705-SDC-1
side of the screen.
HOL-1705-SDC-1
Recovery Plan Status.
1. Verify that the Plan Status is displaying a Ready notification.
HOL-1705-SDC-1
Execute the Fail-Back Recovery Plan
1. To begin the process of failing the virtual machine back to the RegionA01 data
center, select the red button with the play symbol.
HOL-1705-SDC-1
Select Recovery Options
1. Place a check mark in the box to indicate that you understand that moving
beyond this point could cause significant changes to the environment.
2. Select the Planned Migration radio button. This option will first perform a
graceful shutdown of the protected virtual machine at the source data center
(RegionB01), perform a replication of all recently changed data, then proceed to
bring the recovered Lightning-01 virtual machine at the destination data center
online.
3. Select the Next button to continue.
HOL-1705-SDC-1
Verify Recovery Options
1. Verify that the selections you made in the previous step are correct. Then click
the Finish button to begin the Planned migration / fail-back workflow.
Please note that this step could take up to 5 minutes to complete.
HOL-1705-SDC-1
Recovery Complete
1. You can monitor the status of the virtual machine recovery by following the
progress of the steps in the Recovery Plan.
2. Upon successful completion of the recovery plan, the Plan Status section will
display a Recovery Complete message.
HOL-1705-SDC-1
VMs and Templates Inventory View
You can now navigate back to the VMs and Templates view in the vSphere Web Client to
verify that the Lightning-01 virtual machine is once again running in the RegionA01 data
center.
2. Select the VMs and Templates menu option from the drop down menu.
HOL-1705-SDC-1
Verify Virtual Machine Recovery
1. Expand the RegionA01 data center inventory object and verify that the
Lightning-01 virtual machine is has power on and is operational.
2. You can also verify that the virtual machine has been connected to a network and
has a valid IP address.
HOL-1705-SDC-1
Conclusion
In this module, you successfully failed the Lightning01 virtual machine over to the
recover site at the Region-B data center. You then proceeded to re-protect the virtual
machine which, with minimal administrative overhead, reversed the replication and
protection directions of the Lightning-01 application.
You concluded this module by using Site Recovery Manager to fail-over the virtual
machine back to its original location in the Region-A data center.
HOL-1705-SDC-1
You've finished Module 1
Congratulations on completing Module 1.
Site Recovery Manager provides the following benefits:
Lower cost of disaster recovery by up to 50% by reducing the x86 hardware

footprint, simplifying protection through VM-centric, policy-based replication, and
decreasing operational expenses.
Non-disruptive testing enables more frequent disaster recovery rehearsals, which
minimizes risk.
Recovery plans that can easily be updated and tested as new workloads are
provisioned.
Flexibility to protect nearly any workload that runs in a virtual machine.
Automated customization of virtual machines to further improve recovery times
and reduce risk.
Detailed reporting to easily satisfy regulatory requirements for documentation of
data protection and disaster recovery plans.
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.
HOL-1705-SDC-1
Module 2 - Executing a
Disaster Recovery Plan
using Site Recovery
Manager (60 minutes,
Beginner)
HOL-1705-SDC-1
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 and 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 vSphere Infrastructure Navigator
displays Site Recovery Manager configuration information within an application
dependency mapping.
Total time required: 60 minutes
HOL-1705-SDC-1
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.
HOL-1705-SDC-1
Create a Protection Group
1. From the vCenter Home screen, select the Site Recovery Icon.
HOL-1705-SDC-1
Navigate to Protection Groups
1. Select Protection Groups.
HOL-1705-SDC-1
Begin, Create Protection Group
A protection group is a collection of one or more virtual machines that are failed over
and failed back as a unit. In many cases, a protection group consists of multiple virtual
machines that support a service such as an accounting system. For example, the
accounting system consists of a database server, one application server, and one web
server. In most cases, it is not beneficial to fail over part of a service (only one or two of
the servers in the example). All three virtual machines would be included in a protection
group to enable failover of the services.
1. Select Objects.
2. Select the Create Protection Group icon.
HOL-1705-SDC-1
Enter Protection Group Name
Creating a protection group for each application or service also has the benefit of
selective testing. With Site Recovery Manager, having a protection group for each
application enables non-disruptive, low-risk testing of individual applications. Application
owners can test disaster recovery plans, as needed.
1. In the Name field, enter "Accounting Protection Group".

2. Enter a description "Accounting department protection group".
3. Select Next.
HOL-1705-SDC-1
Remote Site Authentication
If requested, enter credentials for the target vCenter site.
1. Enter the user name administrator@corp.local and password VMware1!

2. Select Log In.
HOL-1705-SDC-1
Protection Group Type
1. Select Direction of protection RegionA01 -> RegionB01.

2. Select group type Individual VM's (vSphere Replication).
3. Select Next.
HOL-1705-SDC-1
Select Group Members
1. Select virtual machines Acct-Web-01, Acct-App-01 and Acct-DB-01.

2. Select Next.
HOL-1705-SDC-1
Verify Protection Group Configuration
1. Review and select Finish.
HOL-1705-SDC-1
Competed Accounting Protection Group
1. When complete you should see the new Accounting Protection Group listed.
After a protection group has been created and the virtual machines have been
successfully protected, placeholder virtual machines will be visible in the vCenter Server
inventory at the recovery site Region B. The presence of placeholders provides a visual
indication to Site Recovery Manager administrators that virtual machines are protected.
Placeholder virtual machines have a unique icon in vSphere Web Client.
HOL-1705-SDC-1
Region B vCenter - Verify Protection Group
the lesson.
HOL-1705-SDC-1
Region B - vCenter VM's and Templates
1. Select the Home Icon.

2. Select VM's and Templates.
HOL-1705-SDC-1
Region B - vCenter VM's and Templates cont.
1. Expand the RegionB01 Datacenter and select the Recovered VM's Folder.
The presence of placeholders for VM Acct-App-01, Acct-DB-01 and Acct-Web-01

provides a visual indication to Site Recovery Manager administrators that virtual
machines are protected. Placeholder virtual machines have a unique icon in vSphere
Web Client and are not powered on.
You have completed lesson 1 of module 2. It is recommended that you now start lesson
2 of module 2.
HOL-1705-SDC-1
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.
HOL-1705-SDC-1
Create a Recovery Plan
1. From the RegionA01 vCenter web client select the Home icon.
2. Select the Site Recovery.
HOL-1705-SDC-1
Begin, Create Recovery Plan
1. Select Recovery Plans.
Create Recovery Plan - Cont.
1. Select the Objects Tab.

2. Select the CreateRecovery Plans button.
HOL-1705-SDC-1
Recovery Plan Name and Location
Creating a recovery plan for each application enables testing and failover of individual
applications. Creating a recovery plan that includes one or all of the protection groups is
useful when testing or failing over all applications at a site.
1. Enter Name: "Accounting Recovery Plan".

2. Enter description "Accounting department Recovery Plan".
3. Select Next.
HOL-1705-SDC-1
Recovery Site
1. Select RegionB01.
2. Select Next.
1. Enter the user name administrator@corp.local and password VMware1!

2. Select Log In.
HOL-1705-SDC-1
Select Protection Group
A recovery plan must contain one or more protection groups. A protection group can be
part of more than one recovery plan. In this lesson you will use the Account Protections
group to configure this recovery plan.
1. Select the Accounting Protection Group.

2. Select Next.
HOL-1705-SDC-1
Recovery Plan Test Networks
One of the steps in creating a recovery plan is configuring a test network for each of the
recovery networks at the recovery site. When testing a recovery plan, recovered virtual
machines are connected to a corresponding test network, as defined in a recovery plan.
By default, Site Recovery Manager uses an isolated network - a virtual switch with no
external connectivity that is created dynamically when a recovery plan is tested. This is
a simple and effective approach, but connectivity between virtual machines is limited to
the virtual machines running on the same vSphere host. The default setting, Isolated
network (auto created), can be changed to another port group available at the
recovery site.
Select Next.
HOL-1705-SDC-1
Complete Recovery Plan
1. Select Finish.
Completed Accounting Recovery Plan
1. When complete you should see the new Accounting Recovery Plan listed.
3 of module 2.
HOL-1705-SDC-1
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 vCenter Web Client select the Home Icon.
2. Select Site Recovery.
HOL-1705-SDC-1
Begin - Test Recovery Plan
HOL-1705-SDC-1
Initiate Recovery Plan Test
1. Select the Accounting Recovery Plan in the left side object list.
2. Select the green play icon in the Recovery Steps view to begin testing the
Accounting recovery plan.
HOL-1705-SDC-1
Replicate recent changes
For this particular test, we will not be replicating any recent changes to the recovery
site. This is primarily to reduce the amount of time required to complete this step in the
lab environment.
1. If selected, uncheck the check box Replicate recent changes to the

recovery site.
2. Select Next.
HOL-1705-SDC-1
Verify Recovery Plan Test Options
1. Verify that the options you chose in the previous step are correct, then click
finish to begin the test.

HOL-1705-SDC-1
Monitor the Recovery Plan Test progress
1. Verify that the Accounting application VMs power on the correct order.
If any errors are encountered during the test phase of a recovery plan, you have the
ability to rectify the problems and re-run the plan to ensure that all steps complete
without error.
Please note that this step can take up to 5 minutes to complete.

HOL-1705-SDC-1
Region B vCenter - Verify Test Recovery
the lesson.

HOL-1705-SDC-1
Region B vCenter - VM's and Inventory View
1. Select the Home icon.

2. Select VMs and Templates from the drop down menu.

HOL-1705-SDC-1
Region B vCenter - Verify Operational State
1. Select the vcsa-01b.corp.local vCenter.

3. Select vSphere Replications.
4. Select Incoming Replications and verify the Acct-App-01, Acct-DB-01 and
Acct-Web-01 have a status of OK.
5. Expand out the Navigation tree, vcsa-01b.corp.local > RegionB01 >
Recovered VM's > Recovered VMs and verify that the Acct-App-01,Acct-
DB-01 and Acct-Web-01 virtual machines have powered on at the peer
RegionB01vCenter site.

HOL-1705-SDC-1
Complete Recovery Test

2. Select Site Recovery from the dropdown menu.

HOL-1705-SDC-1
Recovery Plans
1. Select the Recovery Plans.
RegionA01 Authentication
If requested, authenticate back to main site, RegionA01.
1. Enter User name: administrator@corp.local.

2. Enter Password: VMware1!
3. Select Log In.

HOL-1705-SDC-1
Clean-Up the Recovery Plan
1. Select the Accounting Recovery Plan from the left side menu.
3. Select the Recovery Steps tab for the Accounting Recovery Plan.
4. Select the Cleanup icon to clean up the test and prepare the plan for future use.

HOL-1705-SDC-1
Recovery Plan Clean Up Options
1. Click Next to continue.

HOL-1705-SDC-1
Verify Options
1. Verify the options for the cleanup, then click Finish to execute a cleanup of the
Test Recovery.

HOL-1705-SDC-1
Recovery Plan Ready
Once the clean up the test has completed, your recovery plan is now ready for
execution either as another test, or as an actual fail-over.
1. The Plan status field should now indicate Ready.
4 of module 2.

HOL-1705-SDC-1
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 completion the testing 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.

HOL-1705-SDC-1
Test Site-Wide Recovery Plan
1. From the RegionA01 vCenter Web Client select the Home Icon.

HOL-1705-SDC-1
Recovery Plans Main Page
1. Select the Recovery Plans option under the Navigation pane on the left side of the
screen.

HOL-1705-SDC-1
Create new Recovery Plan
1. Select Objects.
2. Select the Create New Recovery plan icon.

HOL-1705-SDC-1
Name the Recovery Plan
1. Enter a name Site-Wide Recovery Plan.

2. Enter description Recovery plan for the entire RegionA datacenter.
3. Select Next.

HOL-1705-SDC-1
Select Recovery Site
2. Select Next.
Log into Remote Site - RegionB
1. If requested, enter the user name administrator@corp.local and use the

password VMware1!
2. Select Log In.

HOL-1705-SDC-1
Select Protection Groups
1. Place a check mark next to all of the protection groups listed. This allows you to
recover all the virtual machines associated with the protection groups by executing a
single recovery plan.
2. Select Next.

HOL-1705-SDC-1
Select Test Networks
This step is where you would define specific networks you would want recovered virtual
machines connect to when you are executing a test of the Recovery Plan.
1. Leave all setting at their default values and click Next to continue.

HOL-1705-SDC-1
Recovery Plan Confirmation
Verify that the choices you selected in the previous steps are correct, then select Finish
to complete the creation of the new recovery plan.

HOL-1705-SDC-1
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
VM's 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.

HOL-1705-SDC-1
Review Recovery Plan.
1. Deselect Replicate recent changes to recovery site.

2. Select Next.

HOL-1705-SDC-1
Ready To Complete Site-Wide Recovery Plan

HOL-1705-SDC-1
Site Wide Recovery Plan Complete
Once finished the Site-Wide recovery Plan status will change to Test complete.

HOL-1705-SDC-1
the lesson.

HOL-1705-SDC-1
Region B vCenter - Inventory View
1. Select the Home icon


HOL-1705-SDC-1
Region B vCenter - Verify Operational State

3. Select vSphere Replications.
4. Select Incoming Replications and verify that all virtual machine indicate a
status of OK.
5. Expand out the Navigation tree, vcsa-01b.corp.local > RegionB01 >
Recovered VM's > Recovered VMs and verify that all listed virtual machines
have powered on at the peer RegionB01 vCenter site.

HOL-1705-SDC-1

2. Select Site Recovery from the dropdown menu.

HOL-1705-SDC-1
Recovery Plans
1. Select the Recovery Plans.
RegionA01 Authentication
If requested, authenticate to back to main site, RegionA01.
1. Enter User name: administrator@corp.local

3. Select Log In.

HOL-1705-SDC-1
Clean-Up the Recovery Plan
1. Select the Site-Wide Recovery Plan from the left side menu.
2. Select the Recovery Steps tab for the Accounting Recovery Plan.

HOL-1705-SDC-1
1. Click Next to continue.

HOL-1705-SDC-1
Recovery Plan Clean Up Options - Cont.

HOL-1705-SDC-1
Sit-Wide Recovery Plan - Ready
1. The Plan status field should now indicate Ready.
5 of module 2.

HOL-1705-SDC-1
Lesson 5: Review Audit Reporting in

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 Region A vCenter web client select the Home icon.
2. Select Site Recovery from the drop done.

HOL-1705-SDC-1
Begin, Create Recovery Plan
Select the Recovery Plan
1. From the Recovery Plan menu on the left side of the page, select the Accounting
Recovery Plan.
3. Then select the History Button near the top of the main section of the page.
This list displays all of the details regarding actions that were performed on this
particular recovery plan for the time period displayed.

HOL-1705-SDC-1
Select Report
1. Select the Accounting Recovery Plan.

2. Highlight the most recent Test entry for the selected recovery plan.
3. Click on the Export Report button to launch the Export Report Wizard.
Report Format
1. From the drop down menu, select the format you would like to export the report
to. For this exercise, you will select the Web Page (*.html) format option.
2. Once you have made your selection, click the generate button to begin
generating the report for the Accounting Recovery Plan Test.

HOL-1705-SDC-1
Download Report
Once the report generation has completed, you will be presented with the option to
download the report.
1. Click the Download Report button to continue.

HOL-1705-SDC-1
Specify location
Specify a location to save the downloaded report to.
1. Select the Desktop as the location to save the report to. The file will
automatically be saved with the name of the recovery plan.
2. Click the Save button to continue.

HOL-1705-SDC-1
Close Report Generator
1. Click the Close button to close the report Generation wizard.
Main Console
Minimize the current browser window.
1. Locate the exported html file you just created on the desktop of the Control Center.
Double click the file to open the report.

HOL-1705-SDC-1
View Report
You can now view the exported report along with specific details regarding each step
defined in the recovery plan along with the completion status of each step.

HOL-1705-SDC-1
Return to Site Recovery Manager
1. In the Windows task bar at the bottom of the screen, select the Minimized browser to
return you to the vSphere Web client and the Site Recovery Manager page.
6 of module 2.

HOL-1705-SDC-1
Lesson 6: Leverage VIN To Ensure

Dependent VMs Are Protected
Together
VMware vRealize Infrastructure Navigator(VIN) automates discovery and dependency
mapping of applications, and the applications components, as they traverse the virtual
infrastructure. This management solution renders visualizations of the relationships
among application components distributed throughout the virtual environment.
Packaged as a VMware vSphere Web Client plug-in, Infrastructure Navigator integrates
seamlessly into VMware vCenter Server to provide continuous application discovery and
dependency mapping for virtual environments.
Integrating Site Recovery Manager (SRM) with Infrastructure Navigator, the SRM
protection groups and SRM recovery plans of the selected virtual machines are
displayed in the dependency map. If a virtual machine is part of a vApp, the vApp name
is also displayed in the dependency map. Once SRM is integrated, the SRM information
appears in the visual dependency map represented by a special SRM symbol.

HOL-1705-SDC-1
Begin - Site Recovery Manager and vRealize Infrastructure

Navigator
1. From the RegionA vCenter web client select the Home dropdown menu.
2. Select Hosts and Clusters.
vRealize Infrastructure Navigator - Application

Dependencies
1. Expand the RegionA01 Datacenter > RegionA01-COMP01 Cluster.

2. Select the Acct-App-01 virtual machine.
3. Select Manage.
4. Select the Application Dependencies tab.
In the above figure 5, the vCenter navigation pane has the Acct-App-01 selected as a
focus area and Infrastructure Navigator is showing a dependency map of the virtual
machines and applications that the Accounting department uses at Corp local. You will

HOL-1705-SDC-1
note that the above picture is different than what you see in the lab, this is because
there is no SRM configuration applied in this example.
As a vCenter plug-in, Infrastructure Navigator runs within the vSphere Web Client. It
seamlessly integrates with the vSphere Web Client interface by adding an Infrastructure
Navigator port-let to provide application summary information based on the context
selected in the vSphere Web Client navigation pane.

HOL-1705-SDC-1
vRealize Infrastructure Navigator - Application

Dependencies and SRM
The dependency map is a map of relationships that displays the services installed and
running on a virtual machine. The dependency map displays all virtual machines
connected to the selected virtual machine by incoming or outgoing dependencies.
1. Once SRM is integrated with Infrastructure Navigator, the SRM Protection Groups
and SRM Recovery Plans for virtual machines Acct-App-01, Acct-DB-01 and
Acct-Web-01 are now displayed as part of the dependency map.
You have completed module 2. It is recommended that you now start module 3.

HOL-1705-SDC-1
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 vCenter Infrastructure Navigator 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.

minimizes risk.
provisioned.
and reduce risk.
can provide.
you most.
Module 3 - Site Recovery Manager Advanced Topics (30 minutes, Advanced)

HOL-1705-SDC-1
How to End Lab

HOL-1705-SDC-1
Module 3 - Site Recovery

Manager Advanced Topics
(30 minutes, Advanced)

HOL-1705-SDC-1
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

HOL-1705-SDC-1
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.

HOL-1705-SDC-1
Launch the vSphere Web Client
The initial startup of the lab will automatically launch separate Chrome browser
windows for both vcsa-01a.corp.local and vcsa-01b.corp.local. The lab start up process
will also log you in to the vSphere Web Client as administrator@corp.local.

HOL-1705-SDC-1
Maximize the View
1. If the Recent Tasks window is visible, you can select the pin icon in the lower right
side of the vSphere Web Client page to minimize it and expand the main window
area.

HOL-1705-SDC-1
vSphere Replication
Select the "vSphere Replication" icon from the home tab on the main page.

HOL-1705-SDC-1
Verify Replication Connectivity Status
1. Select the "Home" tab at the top of the main vSphere Replication window pane.
2. Verify that the "vSphere Replication" status indicates "Enabled (OK)"
Note: It could take up to 1 minute for the query to complete and the status
information to be displayed.
Now that you have verified that replication is configured and working between both
locations, you need to reconnect the management interface to Region B so that we can
view and manage the vSphere Replication appliance at that location.

HOL-1705-SDC-1
Re-connect to Remote vSphere Replication Appliance.
1. Select the "Manage" menu button under the home tab.

HOL-1705-SDC-1
Select Target vSphere Replication Server
1. Select the "Target sites" menu option
2. Highlight the "RegionB01" vSphere Replication appliance. The status of the appliance
should be displaying a "Not Authenticated" message.
3. Select the "Reconnect" button to initiate a connection to the remote vSphere

replication appliance in RegionA01.
Re-connect to the target vSphere Replication appliance
1. Select "Yes" when prompted to reconnect.
2. Enter the credentials for the remote vSphere Replication appliance.

HOL-1705-SDC-1
Password: VMware1!
3. Select "OK" to initiate the reconnect.

HOL-1705-SDC-1
Verify Connectivity to RegionB01
1. Verify that the status for RegionB01 shows "Connected"
2. Select the "Monitor" tab at the top of the main page.

HOL-1705-SDC-1
View vSphere Replication Status
1. Ensure that you have selected "Outgoing Replications" in the left side menu
2. The Status of the "Sales" virtual machines should display "OK".

HOL-1705-SDC-1
Open Site Recovery Manager
Now that we have ensured that all the Sales VMs have been replicated, we will look at
the 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.

HOL-1705-SDC-1
View Site Information
Within Site Recovery we have two sites, RegionA01 and RegionB01. RegionA01 is the
primary site and is associated with the vCenter Server vcsa-01a.corp.local. RegionB01
is the recovery site and is associated with vCenter Server vcsa-01b.corp.local.
Let's make sure that both sites are connected and able to communicate with each other.
1. Now that we are within Site Recovery, choose Sites from Navigator

HOL-1705-SDC-1
Select Site
1. Select RegionA01 in the left column
2. Ifyou are prompted for user credentials, enter the following information.
Password: VMware1!
3. Click the "Log In" button when done

HOL-1705-SDC-1

HOL-1705-SDC-1
Ensure Both Primary and Recovery Sites are Connected
The RegionA01 site is represented by the vCenter Server vcsa-01a.corp.local. The

RegionB01 site is represented by the vCenter Server vcsa-01b.corp.local.
1. Select RegionA01 within Navigator.

2. Ensure that both "Client Connection"and "Server Connection" are displaying
"Connected"across both sites.
3. When finished, click on "Site Recovery" in Navigator to go back to the Site
Recovery homepage.

HOL-1705-SDC-1
Recovery Plans
Select the "Recovery Plans" menu item from the Navigator menu.

HOL-1705-SDC-1
View Recovery Plans
A Recovery Plan runs a series of steps that must be performed in a specific order for a
given workflow such as a planned migration or re-protect. You cannot change the order
or purpose of the steps, but you can insert your own steps that display messages and
run commands.
Site Recovery Manager executes recovery plan steps depending on the test or recovery
method.
Some steps run during all recoveries

Some steps run only during test recoveries.
Some steps are always skipped during test recoveries.
1. Select the "Sales Application Recovery Plan" from the list of available plans.

HOL-1705-SDC-1
Recovery Plan Objects
1. With the Sales Application Recovery Plan selected in the Navigator Menu...
2. Select the "Related Objects" tab on top of the main page
3. Select the "Virtual Machines" button

HOL-1705-SDC-1
Individual Virtual Machine Recovery Options
There are 2 virtual machines within the Sales Application Recovery Plan. These 2 vm's
make up the primary sales application for Corp.local. The 2 VMs are as follows:
Sales-App-01: This VM accepts requests from the end-user and processes them
to display what the end-user requests.
Sales-DB-01: This VM is the host to multiple databases and stores all data
related to both current and past sales campaigns.
Now let's examine the individual recovery properties for these virtual machines.
1. Select the "Sales-App-01" VM.

2. Select "Actions".
3. Select "Configure Recovery".
Priority Groups
Within Site Recovery Manager, you have the option place a virtual machine that you
wish to recover in up to 5 different priority groups. VMs in Priority Group 1 will be
started first while VMs in Priority Group 5 will be started last. All virtual machines the
same priority group will be powered-on before Site Recovery Manager proceeds to the
next Priority Group to begin powering-on those virtual machines.
To view Priority Groups:

HOL-1705-SDC-1
1. Select the drop-down arrow that is populated with the number 3 next to "Priority
Group".

HOL-1705-SDC-1
Virtual Machine Dependencies
If one of the virtual machines needs to be powered-on before other virtual machines
within the same Priority Group, you can use "VM Dependencies". With VM
Dependencies, you can specify one or many VMs that should be powered-on before the
VM that you are setting the dependency on. Note that you can only set dependencies
for virtual machines within the same Priority Group.
To view the VM Dependencies options:
1. Select "VM Dependencies". We will add a VM Dependency later within this

module. Select "VM Dependencies" again to minimize the "VM Dependencies"
window.
Shutdown Action
During a Recovery, Site Recovery Manager will do it's best effort to power off VMs
running at the protected site before recovering them at the recovery site. You have two
options for shutting down VMs, "Shutdown guest OS before power off (requires VMware
Tools)"and "Power Off".
The first option (Shutdown guest OS before power off) will initiate a shutdown of the
guest OS resulting in a clean shutdown of the VM. In this situation, all applications are
also stopped and shutdown properly.

HOL-1705-SDC-1
The second option (Power Off) does not initiate a guest OS shutdown and simply powers
off the VMs. If a VM does not have VMware Tools installed, the Power Off option will be
used.
To view Shutdown Action options:
1. Select "Shutdown Action" menu item. We will modify the Shutdown Action of a
VM later within this module. Select "Shutdown Action" again to minimize the
"Shutdown Action" window.

HOL-1705-SDC-1
Startup Action
Similar to the options that you have for Shutdown at the protected site, you also have
options for how the VM will be started at the recovery site.
For Startup Action, you have the option to either Power On the VM or Do Not Power On
the VM. The Wait for VMware tools option is important as any VMs dependent upon the
VM being powered-on will wait until both the VMware Tools and Additional Delay options
are satisfied.
Furthermore, the Recovery Plan will not proceed until both VMware Tools and Additional
Delay are satisfied which includes proceeding to the next Priority Group for additional
VMs to be powered-on within the Recovery Plan.
To view Startup Action options:
1. Select "Startup Action". Review the available options. Select "Startup Action"
again to minimize the "Startup Action" window.
Pre-Power On Steps
Pre-Power On Steps are manual or automatic steps that you can take outside of the
Recovery Plan within Site Recovery Manager.
Pre-Power On Steps can either be executed by the Site Recovery Manager server or by
prompting the user to perform a task or to provide information that the user must
acknowledge before the Recovery Plan continues to the next step.
Remember that for Pre-Power On Steps, the virtual machine has not yet powered-on,
therefore you cannot perform a step that requires the VM(s) to be powered-on.
The Timeout provides you with a mechanism to continue with the Recovery Plan if for
some reason the step does not execute properly or is not acknowledged.
To view the Pre Power On Step options:
1. Select Pre Power On Steps.

HOL-1705-SDC-1
2. To add a Pre Power On Step, select the Green Plus icon. The Add Pre Power On
Step window will appear. Review the Add Pre Power On Steps. Select Cancel to
close the Add Pre Power On Step window.
3. Select Pre Power On Steps again to minimize the Pre Power On Steps window.

HOL-1705-SDC-1
Post-Power On Steps
Post-Power On Steps are different than Pre-Power On Steps in that they execute once
the virtual machine and guest OS are running.
Similar to Pre Power On Steps, you also have the option to run a command on the Site
Recovery Manager server or by prompting the user to perform a task or provide
information that the user must acknowledge before the recovery plan continues to the
next step.
To view the Post Power On Step options:
1. Select Post Power On Steps.

2. To add a Post Power On Step, select the Green Plus icon. The Add Post Power On
Step window will appear. Review the Add Post Power On Step.
3. Select Cancel to close the Add Post Power On Step window.
4. Select Cancel to close the VM Recovery Properties window for the Sales-
DB-01 virtual machine.

HOL-1705-SDC-1
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 include:
Priority Groups
VM Dependencies
Shutdown Action
Startup Action
Pre-Power On Steps
Post-Power On Steps

HOL-1705-SDC-1
Lesson 2: Customizing the Virtual

Machine IP Address During Failover
Due to the proximity of Corp.local's data centers, 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 is 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.

HOL-1705-SDC-1
Getting Started
We will start from the vSphere Web Client homepage.
1. If you are not on the vSphere Web Client homepage, select the Home Icon at the
top of the window.
2. Select Home.

HOL-1705-SDC-1
Open Site Recovery Manager
In order to customize the IP addresses of the Sales virtual machines, we need to connect
to the Site Recovery Manager solution.
1. Select Site Recovery from within the Home tab.

HOL-1705-SDC-1
Open Recovery Plans
Next, we need to manage the Sales virtual machines so that they can be customized.
1. Select the Recovery Plans menu item under the Inventories section.

HOL-1705-SDC-1
Sales Application Recovery Plan
1. Select the Sales Application Recovery Plan.

2. Select the Related Objectstab.
3. Select Virtual Machines.
You should now see both Sales virtual machines in the main part of the UI. They are as
follows:
Sales-DB-01
Sales-App-01

HOL-1705-SDC-1
Customize IP Address for the App Server
Let's first customize the IP address of the Sales-App Server.
1. Highlight the Sales-App-01 virtual machine.

2. Right click the Sales-App-01 virtual machine to open the Actions drop-down
menu.
3. SelectConfigure Recovery.

HOL-1705-SDC-1
IP Customization
You are now ready to customize the individual properties of the Sales-App-01 virtual
machine
1. Select IP Customization.
2. From the IP customization mode drop-down list, select Manual IP customization.
In this instance, we're going to manually set the IP address for the VM when being
recovered via Site Recovery Manager. Later in this lesson, we'll look at IP customization
rules.

HOL-1705-SDC-1
Configure Protection
The Configure Protected Site IP Settings allows us to define the current IP properties of
the VM.
This setting is not used until after recovery has been completed. In the event that we
need to recover our virtual machines to the recovery site, we will inevitably need to re-
protect them to ensure that they are always in a state of protection, ready to be
recovered at a moment's notice. In this case, Region B becomes the protected site with
Region A becoming the recovery site.
1. Expand the IP Settings - NIC 1 menu item.

2. Select Configure Protection buttonat the bottom of the page.
Note: You may need to move the VM Recovery Properties window up in order to see
Configure Protection button.

HOL-1705-SDC-1
Specify Protected Site IP Settings
Within the Configure Protected Site IP Settings - NIC 1, you can use DHCP to obtain the
IP address, manually enter the IP address by choosing Use the following IPv4
address or if the VM is running VMware Tools, you can select the option to Retrieve
the current IP settings of the VM. We will use VMWare Tools to retrieve the current IP
information of the virtual machine. If the IP information fails to populate, please
manually enter the IP information listed below.
1. Select the Use the following IPv4 address radio button, then select the Retrieve
button.
2.If the IP information fails to populate enter the IPv4 Address, Subnet Mask and
Gateway fields with the information shown below.
IPv4 Address: 192.168.120.200
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.120.1

HOL-1705-SDC-1

HOL-1705-SDC-1
Configure Protected Site DNS
1. Select the DNS tab

2. Select Use the following DNS server addresses
3. Enter a Preferred DNS server of: 192.168.110.10
4. Place your cursor in the DNS suffixes text box and enter: corp.local
5. Select the Add button
6. corp.local should now appear in the window below the text box
7. Select OK when completed
Configure Recovery
Now you need to configure the IP settings for the virtual machine when it is recovered.

HOL-1705-SDC-1
1. Select the Configure Recovery button to continue

HOL-1705-SDC-1
Configure Recovery Site IP Settings
1. Select the Use the following IPv4 address radio button.
2.Enter the IPv4 Address, Subnet Mask and Gateway fields with the information shown
below.
IPv4 Address: 192.168.220.200
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.220.1

HOL-1705-SDC-1
Configure Recovery Site DNS
1. Select the DNS tab

2. Select Use the following DNS server addresses
3. Enter a Preferred DNS server of: 192.168.210.10
4. Place your cursor in the DNS suffixes text box and enter: corp.local
5. Select the Add button
6. corp.local should now appear in the window below the text box
7. Select OK
Sales App IP Confirmation
The IP Customization for the Sales-App-01 virtual machine is now complete.

HOL-1705-SDC-1
1. Select OK to apply the changes to the recovery plan for this virtual machine.
Note: You will see a pop-up window stating that Protected VM successfully reconfigured.
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.

HOL-1705-SDC-1
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 NICs 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 that says Site Recovery to go back to
the Site Recovery Manager homepage

HOL-1705-SDC-1
Sites
IP Customization Rules are created within the Network Mappings section of Site
Recovery Manager.
1. Select the Sites menu option from the Navigator menu.

HOL-1705-SDC-1
Network Mappings
1. Select the RegionA01 Site from the left menu bar
2. Select the Manage tab
3. Select the Network Mappings button to display the configured network mappings
between both Site Recovery Manager sites.

HOL-1705-SDC-1
Select Network Mapping
Select the network mapping to which you would like to add an IP Customization. (There
is only one Network mapping listed)
1. Highlight the VM-RegionA01-vDS-COMP network

2. Right-click the selected network, and from the drop down menu, select the Add IP
Customization Rule option.

HOL-1705-SDC-1
Add IP Customization Rule
Enter the following information into the IP Customization Rule creation form.
1. Rule Name: VM-Region-vDS-COMP Recovery

2. For the RegionA01 Site, enter the following for Subnet mask: 192.168.120.0/
24
3. For the RegionB01 Site, enter the following for Subnet mask: 192.168.220.0/
24
4. Gateway: 192.168.220.1
5. DNS addresses; 192.168.210.10
6. DNS suffixes: corp.local
7. Select the OKbutton when complete

HOL-1705-SDC-1

HOL-1705-SDC-1
Confirm IP Customization
1. Highlight the VM-RegionA01-vDS-COMP network mapping to view the IP

Customization Rule that you just created and is now associated with this network.
2. Select the back arrow in Navigator Menulabeled Site Recovery to return to the Site
Recovery Manager homepage.

HOL-1705-SDC-1
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, select the Recovery Plans menu option.

HOL-1705-SDC-1

3. Select Virtual Machines.
You should now see both Sales virtual machines in the main part of the UI. They are as
follows:
Sales-DB-01
Sales-App-01

HOL-1705-SDC-1
Sales Database VM
Let's customize the IP address of the Sales-DB-01 Server.
1. Highlight the Sales-DB-01 virtual machine.

2. Right click the Sales-DB-01 virtual machine to open the Actions drop-down menu.
3. SelectConfigure Recovery.

HOL-1705-SDC-1
Use IP Customization Rule
1. Select IP Customization.
2. Select the Select an IP customization mode drop-down list.
3. Select Use IP customization rules is applicable.
4. Select OK at the bottom of the dialog box to complete the configuration
The Sales-DB-01 virtual machine IP customization is now complete. Because this virtual
machine resides on the VM-RegionA01-vDS-COMPnetwork, it will use the IP
Customization Rule we created for the that mapped network segment to modify the IP
Address of the VM during a recovery.
Lesson Review
Both our Sales VMs will now use a customized IP address during recovery. We used two
different methods to customize the IP address, the first being manual where we
manually entered what the IP address will be using during recovery and second, using

HOL-1705-SDC-1
an IP customization rule that can be applied to all virtual machines that reside on a
particular portgroup.
In the next lesson, we will modify the start-up order for each VM.

HOL-1705-SDC-1
Lesson 3: Virtual Machine Start-up

Options
In this lesson, we will configure the power-on options for the Sales virtual machines
within Site Recovery Manager. The options we will configure include:
Priority Groups
VM Dependencies
Startup Actions

HOL-1705-SDC-1
Getting Started
Let's start by navigating to the Site Recovery Manager main page if you're not already
there.
1. Select the Home icon at the top of the vSphere Web Client and a drop-down
menu will appear.
2. Choose Site Recovery from the menu.

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

HOL-1705-SDC-1
1. Select the Sales Application Recovery Plan from the Navigator menu on the left.

HOL-1705-SDC-1
Sales-App-01 VM

2. Select the Virtual Machinesbutton.
3. Highlight theSales-App-01 virtual machine.
4. Right-click on the Sales-App-01 VM and select Configure Recovery.
Modify Priority Group
We need to modify the Priority Group for the Sales App virtual machine so that it powers
on after the Sales Database virtual machine. We will modify the settings of the Sales-
DB-01 VM in just a few minutes.
1. Change the Priority Group of the Sales-App-01 VM from 3 to 4.
Virtual Machines in Priority Groups 1, 2 or 3 will now be powered-on before the Sales-
App-01 VM.

HOL-1705-SDC-1
We also know that the Application server is dependent upon the Database server. If the
Sales-App-01 VM powers on first in our Recovery Plan, our Sales Application will not
work correctly.
In order to ensure the correct start up sequence for the 2 virtual machines in the Sales
Application Recovery Plan, we will set a dependency on the Sales-App-01 VM in the
next step.

HOL-1705-SDC-1
VM Dependencies
1. Select VM Dependenciesmenu option

2. Select the Configure button.

HOL-1705-SDC-1
Configure App VM Dependency
1. Select the Sales-DB-01 virtual machine from the list.

2. Select OKto proceed.

HOL-1705-SDC-1
VM Dependency Alert
You will notice a yellow triangle with an exclamation mark appear next to the Sales-
DB-01 virtual machine. This indicates that there is an error in our configuration.
The reason this warning appeared is because only virtual machines in the same Priority
Group can have a dependency on one another. Since the Sales-DB-01virtual machine
is still in the default Priority Group 3 and the Sales-App-01 virtual machine is now in
group 4, we receive an error.
Also notice the message just below the VM Dependency window:
VM dependencies are ignored if the VMs are not in the same priority group. If VM
dependencies fail, a warning will be displayed, but the recovery plan will
continue.
Modify Startup Action
Since the Sales-App-01 VM is the last VM to be powered-on in the Sales Application

Recovery Plan, let's modify the Startup Action of the VM.
1. Uncheck Wait for VMware Tools.

2. UncheckAdditional delay before running Post Power On steps and
starting dependent VMs.
3. Select OKto return to the Sales Application Recovery Plan so that we can modify
the power on options of our other Sales virtual machine.

HOL-1705-SDC-1
As soon as the Sales-App-01 VM is powered-on, the recovery plan will continue to the
next step in the plan.

HOL-1705-SDC-1
Sales Database VM
1. Highlight the Sales-DB-01 virtual machine.

2. Right-click on the Sales-DB-01 virtual machine and select Configure Recovery.

HOL-1705-SDC-1
Modify Priority Group
We're going to modify the Priority Group of the Sales-DB-01 virtual machine.
1. Select the Priority Group drop-down and select the option 4.
The Sales-DB-01 virtual machine will now be powered-on after all VMs in Priority
Groups 1, 2 and 3 are powered-on and any Startup Actions have been satisfied.

HOL-1705-SDC-1
Startup Action
1. Select the Startup Actionmenu item

2. Since the Application server is dependent upon the Database server running, we
will leave the Wait for VMware Tools option selected with a value of 5 minutes.
This will ensure that the Recovery Plan will not advance to the next step until
either VMware Tools is responding on the Sales-DB-01 virtual machine or the
timeout value is reached.
3. Review the options selected then select OKat the bottom of the screen to
continue.
Check VM Dependency error
When we first created the VM Dependency for the Sales-App-01 virtual machine, we saw
an error within the VM Dependency window.

HOL-1705-SDC-1
This was caused when we selected a VM as a dependency that was not in the same
Priority Group. We have since modified the Priority Group for theSales-DB-01virtual
machinefrom Priority Group 3 to Priority Group 4, the same as the Sales-App-01 virtual
machine.
You will now verify that the change you made has resolved the error condition.

2. Select the Virtual Machinesbutton.
3. Highlight theSales-App-01 virtual machine.
4. Right-click on the Sales-App-01 VM and select Configure Recovery.

HOL-1705-SDC-1
VM Dependency Error Resolved
1. Expand the VM Dependencies menu item. Notice that the yellow triangle with
an exclamation mark is no longer present and has been replaced with the
traditional vSphere virtual machine icon. By placing theSales-DB-01 virtual
machine in Priority Group 4, we resolved the error.
2. Select OKto close the VM Recovery Properties window for the Sales-App-01
virtual machine.
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 and each with enough time for the necessary services
to start on each VM.

HOL-1705-SDC-1
Lesson 4: vSphere Replication,

Advanced Options
In this lesson, we will review some of the advanced options within vSphere Replication.
These options include:
Point-in-Time Recovery
Guest OS Quiescing
Replication Compression
We have already setup replication for the two virtual machines that make up the Sales
Application. We will use these 2 VM's to explore and configure the advanced options
listed above.

HOL-1705-SDC-1
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
VM's and Templates menu in the vSphere Web client.
We are going to use the Sales-DB-01 virtual machine for this lesson.
1. Select the Homeicon at the top of the vSphere Web client page.
2. Select the VMs and Templatesmenu option from the drop down list.

HOL-1705-SDC-1
Select the Sales Database VM
1. From the Navigator menu, expand the Protected VMs folder.

2. Select Sales-DB-01 virtual machine from the listed VMs.

HOL-1705-SDC-1
vSphere Replication Actions
1. Right-click on the Sales-DB-01 virtual machine.

2. From the Drop down menu, navigate to the last entry in the list and select All
vSphere Replication Actions
3. Select the Reconfigure option from the sub menu.
Because we have already configured replication for the virtual machine, the Configure
Replication option is greyed out but the Reconfigure option is available for us to
select.

HOL-1705-SDC-1
vSphere Replication Server
When configuring vSphere replication for a virtual machine for the first time, you will be
presented with an identical configuration menu as what you currently see.

HOL-1705-SDC-1
For this particular lab environment, there is a single vSphere Replication server
configured for each of the 2 vSphere / Site Recovery Manager sites. You are currently
looking at the vSphere replication server (vr-01b.corp.local) for the Region B site as
this is the destination or the target for the replication.
You can see that the vSphere Replication server is currently responsible for 4 virtual
machine replication instances. We will not make any modifications at this time.
1. Select the Nextbutton to continue.
Target Location
1. Click the arrow next to the Sales-DB-01 virtual machine to expand the Target
location information.
We have selected the RegionB01-ISCSI01-COMP01 data store as the target storage

location for our replicated virtual machine.
To ensure that the virtual machine has access to the correct storage tier and capabilities
at the replicated site, we have the option to specify any pre-configured VM storage

HOL-1705-SDC-1
policies that exist at the Region B site. For this particular example we have chosen a
Default VM Storage Policy.
We have also specified that replicated virtual machine disk should be Thin provisioned
to conserve data store capacity.
We are not going to make any changes at this time, Select Next at the bottom of the
configuration window to continue.
Guest OS Quiescing
The Replication Options window provides us with the option for Guest OS Quiescing and
Network Compression.
vSphere Replication guarantees crash consistency amongst all the disks that belong to a
virtual machine. If you use quiescing, you might obtain a higher level of consistency.
The available quiescing types are determined by the virtual machine's operating
system.
For Microsoft based guest operating systems that support quiescing, vSphere
Replication will utilize VMware Tools to initiate Microsoft Volume Shadow Copy Service
(VSS) to quiesce the guest OS. The following Microsoft guest operating systems are
supported for guest OS quiescing:
Windows Server 2003

Windows Server 2008
Windows Server 2012
Windows Vista
Windows 7
Windows 8
Windows 10
Certain Linux based operating systems are also supported with guest OS quiescing and
leverage VMware tools.

HOL-1705-SDC-1
LES 11 Service Pack 2

RHEL 5.5
RHEL 5.9
RHEL 6.4
RHEL 7.0
DO NOT SELECT NEXT TO PROCEED TO THE NEXT STEP.
Additional details can be found at the following VMware Documentation Page:

https://www.vmware.com/support/vsphere-replication/doc/vsphere-replication-compat-
matrix-6-1.html

HOL-1705-SDC-1
Network Compression
For network compression, vSphere Replication will compress the data to be replicated
and then uncompress it once it arrives at it's destination. This can be useful if you have
limited bandwidth between your primary and secondary sites. Additional CPU resources
are required at both the source and destination locations in order to compress and un-
compress the replication data.
We have enabled network compression for the Sales-DB-01 virtual machine.
Select Next to continue within the Reconfigure Replication window for the Sales-DB-01
VM.
Additional information on how to calculate the bandwidth requirements for vSphere

Replication can be found here: http://kb.vmware.com/kb/2037268
Recovery Settings
The Recovery Settings window allows you to define the Recovery Point Objective (RPO)
and the number of Point in Time instances for the replicated virtual machine.

HOL-1705-SDC-1
You can set the RPO to as low as 15 minutes or to as high as 24 hours. If you happen
to be using VMware VSAN as your underlying storage platform, you can
further reduce your RPO down to 5 minutes. The lower the RPO, the more often
replication will occur for the virtual machine, lowering the risk of potential data loss. A
lower RPO is not guaranteed as limited bandwidth could cause the RPO to be higher
than what is defined in the Recovery Settings window of the VM.
Point in Time instances allows you to define how many replicated instances of a virtual
machine you would like to keep. These instances are in reality, snapshots of the virtual
machine that are replicated to the target site. You have the capability to retain up to 24
point in time copies of a replicated virtual machine.
This capability allows you to select a specific point in time snapshot of a virtual machine
once it has been recovered to the target site. Recovering to a point in time as opposed
to the most recent replicated version of the VM can be useful if data corruption occurs
or if a threat such as a virus or malware is replicated.
We will not make any changes to the settings of this virtual machine.
1. Select Nextto continue.

HOL-1705-SDC-1
Ready to Complete
Review the settings in the Ready to Complete window and then select Finish.
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.

HOL-1705-SDC-1
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.

minimizes risk.
provisioned.
and reduce risk.
can provide.
you most.
Module 4 - Automating Site Recovery Manager tasks with vRealize Orchestrator (30
minutes, Advanced)

HOL-1705-SDC-1
How to End Lab

HOL-1705-SDC-1
Module 4 - Automating
tasks with vRealize
Orchestrator (30 minutes,
Advanced)

HOL-1705-SDC-1
Module Overview
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:
Lesson 1: vSphere Replication using vRealize Orchestrator.

Lesson 2: Add a Virtual Machine to a Protection Group Using vRealize
Orchestrator.
Lesson 3: Protect a Virtual Machine Using vRealize Orchestrator.
Lesson 4: Add a Virtual Machine to an Existing Recovery Plan.
Lesson 5: Test the Recovery Plan.
Total time required: 30 minutes

HOL-1705-SDC-1
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 the web browser and select the vRealize Orchestrator Client located on
desktop.

HOL-1705-SDC-1
Log in to the vSphere Orchestrator Client
Once the vRealize Orchestrator client renders the Host name and user name will already
be displayed.
1. Enter password VMware1!

2. Select Login.
Not if the entries for Host and User name are blank you can use the following.
Host: vro-01a.corp.local
User Name: Administrator@corp.local

HOL-1705-SDC-1
Change vRealize Orchestrator Role
1. From the drop-down menu select Design.

HOL-1705-SDC-1
Expand the vSphere Replication Folder
1. Select the Workflow view icon on the top toolbar.

2. Expand the Library folder.
3. Expand the vSphere Replication> Configure Replication folder.

HOL-1705-SDC-1
Start The Replication Workflow
What is a vRealize Orchestrator workflow?
Workflows combine actions, decisions, and results that, when performed in a particular
order, complete a specific task or a specific process in a virtual environment such as
performing vSphere Replication and Site Recovery Manager tasks. Workflows accept
inputs according to their function. You can create workflows that run according to
defined schedules, or that run if certain anticipated events occur. Information can be
provided by you, by other users, by another workflow or action, or by an external
process such as a Web service call from an application.
As you work throughout this lesson you will be entering workflow attributes and
parameters as variables to allow the workflow to perform the desired Replication or Site
Recovery task. Keep in mind that the workflows we are using to demonstrate this
functionality are OOB and can be modified to meet your requirements.
1. Select and right click on Configure Replication.

2. Select Start workflow.

HOL-1705-SDC-1

HOL-1705-SDC-1
Start Workflow - Configure Replication
1. Select Site.
2. A new selection window will open, expand vSphere Replication.
3. Select site RegionA01.
4. Select Select.
5. The selection windows will close, select Next.
Virtual Machine to Replicate
1. Select Source VM.

2. A new selection window will open, expand the
path https://vcsa-01a.corp.local:443/sdk> Datacenters > RegionA01.
3. Expand the path VM > Protected VMs.
4. Select the Sales-Web-01 virtual machine.
5. Select Select.

HOL-1705-SDC-1
Note: Disregard the "Mandatory field not set" error while entering the
information.

HOL-1705-SDC-1
Target Site
1. Select Site.
2. A new selection window will open, expand RegionsA01
4. Select Select.

HOL-1705-SDC-1
Target Datastore
1. Select Target Datastore.

2. A new selection window will appear, Select RegionsB01-ISCSI01-CMOMP01
datastore.
3. Select Select.
4. Select Next.
Replication Settings
There are optional Replication settings that can be taken advantage of, such as support
for Microsoft Volume Shadow Copy Service (VSS) and Linux file system quiescing
improves reliability of recovered virtual machines. Recovery point objectives (RPOs)
range from 15 minutes to 24 hours and can be configured on a per virtual machine basis
and Network isolation and compression help secure replicated data and further reduce
network bandwidth consumption.
1. Select Yes, to enable Network compression.

HOL-1705-SDC-1
2. Review workflow details and then select Submit.

HOL-1705-SDC-1
Completed Relocation Workflow Status
1. Once the workflows is complete we should see a green checkmark next to the
completed workflow indicating that it has competed successfully.

HOL-1705-SDC-1
Verify Replication From vCenter
1. Minimize the vSphere Orchestrator Client.

2. Maximize the vCenter Client Web Browser.

HOL-1705-SDC-1
Verify Replication From vCenter - Cont.
1. From the RegionA vCenter Web Client, select the Home button.
2. Select Hosts and Clusters from the Home selection dropdown.
3. From the Navigator expand vcsa-01a.corp.local > RegionA01>
RegionA01-COMP01.
4. Select Sales-Web-01
Verify Replication From vCenter - Cont.
Replication Process

HOL-1705-SDC-1
Utilizing a vRealize Orchestrator workflow, vSphere Web Client configures replication for
a virtual machine. Replication for one or more virtual machines can be selected and
configured via the same workflow. When configuring replication, an administrator
specifies items such as the virtual machine storage policy, RPO, VSS or Linux file system
quiescing, and network compression of replication traffic. Virtual machine snapshots are
not used as part of the replication process unless VSS quiescing is enabled.
The target location for vSphere Replication can be within the same vCenter Server
environment, in another vCenter Server environment with vSphere Replication
deployed, or a vCloud Air Disaster Recovery virtual data center.
1. From the Navigator expand vcsa-01a.corp.local > RegionA01> Protected

VMs and Select Sales-Web-01.
2. Select the Summary tab.
3. To see the virtual machine Replication information, you may have to use the scroll
bar on the right side of the Summary page.
4. Within the summary window review the VM Replication information. The
replication full sync will take a few minutes to complete, once finished the status
will change to OK (Green Check). Once the full sync is complete and you can
proceed to the next lesson.
2 of module 4.

HOL-1705-SDC-1

HOL-1705-SDC-1
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.
Log in to the vSphere Orchestrator Client
Once the vRealize Orchestrator client renders the Host name and user name will already
be displayed.
1. Enter password VMware1!

HOL-1705-SDC-1
Not if the entries for Host and User name are blank you can use the following.
Host: vro-01a.corp.local
User Name: Administrator@corp.local

HOL-1705-SDC-1
Change vRealize Orchestrator Role
1. From the Role selector at the top select Design from the dropdown.

HOL-1705-SDC-1
Browse SRM Workflow Library
1. Select the workflow button on the top toolbar.

2. Expand the Library folder.
3. Expand the SRM folder.
4. Expand the Protection Groups folder.

HOL-1705-SDC-1
Expand SRM Folder
1. Select and right click on the workflow Add Replicated VM to vSphere

Replication Protection Group.
2. Select Start workflow.
Select Replication Protection Group
1. Select vSphere Protection Group.

HOL-1705-SDC-1
2. A new selection windows will appear, expand the SRM, ReggionA10,

Protection Groups folders.
3. Select Sales Protection Group.
4. Select Select.

HOL-1705-SDC-1
Select Virtual Machine
1. Select VM
2. A new selection window will appear, Select Sales-Web-01
3. Select Select.

HOL-1705-SDC-1
Verify and Submit Workflow
1. Verify sections and select Submit.

HOL-1705-SDC-1
Workflow Complete
1. Once the workflow is complete we should see a green checkmark next to the
completed workflow indicating that it has competed successfully.
3 of module 4.

HOL-1705-SDC-1
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.

HOL-1705-SDC-1
Begin - Remote Authentication
1. From the vCenter Home screen, select the VMs and Templates Icon.

HOL-1705-SDC-1
In some cases, Site Recovery Manger and vCenter Replication vRealize Orchestrator
workflows need to authenticate with the remote site to gain access or permission to
make a change. Normally, this authentication workflow would be added to any workflow
but it was separated in this lesson for demonstration purposes.
1. Select and right click on VM Sales-Web-01.

2. Select All vRealize Orchestrator Actions.
3. Select the Login Remote Site workflow.

HOL-1705-SDC-1

HOL-1705-SDC-1
Delegation Permission
Select Approve.

HOL-1705-SDC-1
Remote Site Parameters
1. To add the Local Site, select the Green Plus Sign.

HOL-1705-SDC-1
Select Remote Site
1. A new selection window will open. select the Filter tab

2. Select RegionA01.
3. Select OK, the section window will close.

HOL-1705-SDC-1
Remote Site Credentials
1. Enter User Name Administrator@corp.local.

2. Enter the password VMware1!
3. Select Next.

HOL-1705-SDC-1
Verify and Finish
1. Insure Run now is Selected.

2. Select Finish.

HOL-1705-SDC-1
Logon Remote Site - Complete
1. You can check vCenter Recent tasks to verify that the Logon Remote Site
Workflow has completed successfully.

HOL-1705-SDC-1
Protect A Virtual Machine Workflow
1. From the vCenter Navigator, select the Host and Cluster icon.
2. Expand the RegionA01-COMP01 datacenter and cluster and locate the VM Sales-
Web-01.
3. Select and right click on Sales-Web-01.
5. Select the workflow Protect Virtual Machine.

HOL-1705-SDC-1
1. Select Approve.
Workflow Parameters - Protection Group
1. Select the green Plus sign (+)

2. Select Next.

HOL-1705-SDC-1
1. A new selection window will open. select the Filter tab.

2. Select the Sale App Protection Group.
3. Select OK, the section widow will close.

HOL-1705-SDC-1
Verify Workflow Parameters
1. Select Next.

HOL-1705-SDC-1
Start or Schedule Workflow
1. Insure Run now is selected.

2. Select Finish.

HOL-1705-SDC-1
Verify Virtual Machine Protection
1. You can check vCenter Recent tasks to verify that the Protect Virtual
Machine Workflow has completed successfully.
4 of module 4.

HOL-1705-SDC-1
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 vCenter Home screen, select the VMs and Templates Icon.
Add Protection Group to Recovery Plan
1. Select the Protected VMs folder.

HOL-1705-SDC-1

3. Select Add Protected Group to Recovery Plan.
1. Select Approve.

HOL-1705-SDC-1
Workflow Parameters - Recovery Plan

2. Select Next.

HOL-1705-SDC-1

3. Select OK, the section window will close.

HOL-1705-SDC-1
Workflow Parameters - Protection Group

2. Select Next

HOL-1705-SDC-1

2. Select the Sales App Protection Group.
3. Select OK, the section windows will close.
NOTE: If you did not complete Module 2 of this lab you can substitute the
"Sales App Protection Group" for step 2.

HOL-1705-SDC-1
Verify Workflow Parameters
Select Next.

HOL-1705-SDC-1
Start or Schedule Workflow
1. Insure Run now is selected.

2. Select Finish.

HOL-1705-SDC-1
Verify Workflow Completion
1. You can check vCenter Recent tasks to verify that the Add Protection Group
to Recovery Plan workflow has completed successfully.
5 of module 4.

HOL-1705-SDC-1
Lesson 5: Test the Recovery Plan

In this lesson you will test the Accounting Recovery Plan that was modified using
vRealize Orchestrator workflows 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 workflow automation from both sites, but our lab
environment only has one vRealize Orchestrator instance configured as part of the
RegionA01 vCenter environment which will prohibit you from running the Recovery Plan
workflow from the Region B site. In this lesson you will perform test of the recovery plan
using the Site Recovery Manager UI.

HOL-1705-SDC-1
Test the Recovery Plan
1. From the RegionA01 vCenter Web Client select the Home icon.

HOL-1705-SDC-1
Begin - Test Recovery Plan

HOL-1705-SDC-1
1. Select the Sales Application Recovery Plan in the left side object list.
Site Authentication
If requested, authenticate to remote site, RegionB01.

3. Select Log In.

HOL-1705-SDC-1
Initiate Recovery Plan Test
1. Insure the Sales Application Recovery Plan in the left side object list is still
selected.
2. Select Monitor.
3. Select Recovery Steps.
4. Select the Play icon in the Recovery Steps view to begin testing the Site-Wide
recovery plan.

HOL-1705-SDC-1
Select Test Recovery Options
1. Uncheck Replicate recent changes to recovery site.

2. Select Next

HOL-1705-SDC-1
Verify Test Recovery Options
1. Verify that the options you chose in the previous step are correct, then select
finish to begin the test.

HOL-1705-SDC-1
Monitor the progress
You are able to monitor the progress of the Test recovery from the Recovery Steps
window of the Accounting Recovery Plan.
1. Verify that the Accounting application VMs have powered on.
If any errors are encountered during the test phase of a recovery plan, you have the
ability to rectify the problems and re-run the plan to ensure that all steps complete
without error.

HOL-1705-SDC-1
the lesson.

HOL-1705-SDC-1
RegionB01 vCenter - Inventory View
Navigate to the VMs and Templates View within vCenter.
1. Select the Home icon at the top of the page.
Verify Operational State of the VMs

2. Expand out the Recovered VMs folder and verify that the Sales-App-01 and
Sales-DB-01 and Sales-Web-01 virtual machines have powered on at the peer
RegionB01vCenter site.
4. Select vSphere Replication.

HOL-1705-SDC-1
5. Select Incoming Replications to review status.

HOL-1705-SDC-1
1. Return to the Site Recovery page by selecting the Home Icon.

2. Select Site Recovery drop down menu.

HOL-1705-SDC-1
Recovery Plans
1. Select the Recovery Plans option for the left side menu.

HOL-1705-SDC-1
Accounting Recovery Plan
1. Select the Sales Application Recovery Plan from the left side menu.
Site Authentication

3. Select Log In.

HOL-1705-SDC-1
Recovery Plan ready
1. Insure the Sales Application Recovery Plan in the left side object list is still
selected.
3. Select the Recovery Steps tab.

HOL-1705-SDC-1
1. Select Next to continue.

HOL-1705-SDC-1
Verify options
1. Verify the options for the cleanup, then click finish to execute a cleanup of the
Test Recovery.

HOL-1705-SDC-1
Verify Recovery Plan Ready Status
When the Recovery Plan cleanup is finished the plan status will indicate Ready.
You have completed module 4. It is recommended that you now start module 5.

HOL-1705-SDC-1
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.

minimizes risk.
provisioned.
and reduce risk.
can provide.
you most.
Module 5 - SRM integration with NSX and Storage Policy Based Protection Groups and
Stretched Storage (30 minutes, Advanced)

HOL-1705-SDC-1
How to End Lab

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

HOL-1705-SDC-1
Hands-on Labs Interactive Simulation:

Introduction to Site Recovery Manager
6.1 New Features
VMware has expanded the capabilities of Site Recovery Manager with the new version
6.1 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.1 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
Prior to Site Recovery Manager 6.1 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 6.1 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.

HOL-1705-SDC-1
The integration of stretched storage with Site Recovery Manager 6.1 allows customers
to achieve what was previously only possible with vSphere Metro Storage Clusters:
Planned maintenance downtime avoidance Orchestrated cross-site vMotion and

recovery plans allow for workload migration transparent to app owners or end
users
Zero-downtime disaster avoidance Utilizing the ability to live migrate workloads
using cross-site vMotion and the planned migration workflow in Site Recovery
Manager 6.1, customers can avoid downtime instead of recovering from it
This new functionality augments the other features of Site Recovery Manager,
which can be used with or without stretched storage:
Non-disruptive automated testing enables customers to test and verify recovery
plans as frequently as desired without any disruption to production systems or
replication
Automated recovery plan orchestration all steps of the failover and failback are
handled with minimal required interaction
Management Resiliency having an active vCenter at each site helps ensure that
vCenter and its management and integration functionality is readily available
when needed
Enhanced Integration with VMware NSX
NSX 6.2 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 6.1 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
Due to the nature of the Hands on labs, it's not possible to show all of the features of
Site Recovery Manager. This portion of the lab is presented as a Hands-on Labs -
Interactive Simulation. This simulation will enable you to navigate 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 at the top right.
Be aware, that the lab continues to run, in the background. If it takes too long to
complete the simulation, the lab may go into standby mode, and you have to resume it
after completing the module.

HOL-1705-SDC-1
Conclusion
SRM has tight integration with vSphere and NSX, offers an integrated storage replication
option, and can manage and test recovery plans. Its capable of orchestrating recovery
for multiple failure scenarios including Partial Application Failure, Full Application Failure,
and Site Failure.
Site Recovery Manager 6.1 introduces a new set of enhancements and features that
enable new levels of automation, control and protection, ranging from policy based
protection to support for and integration with stretched storage.
Key take aways from this module that are provided by Site Recovery Manager 6.1:
Storage policy-based management to simplify the process of adding and

removing protection to virtual machines
Support for stretched storage solutions combined with cross-vCenter vMotion
allows companies to achieve application mobility without incurring downtime,
while taking advantage of all the benefits of Site Recovery Manager
Enhancements to and integration with NSX 6.2 that simplify both the creation and
execution of recovery plans and accelerate recovery time
Use of Site Recovery Manager 6.1 enables rapid recovery time objectives through easy
non-disruptive testing and rapid automation of recovery plans, and helps you eliminate
the complexity of managing disaster recovery. Site Recovery Manager 6.1 removes the
risk and worry from disaster recovery.

HOL-1705-SDC-1
How to End Lab
To end your lab click on the END button.

HOL-1705-SDC-1
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-1705-SDC-1
Version: 20161024-101145

Hol 1705 SDC 1

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Hol 1705 SDC 1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hol 1705 SDC 1

Uploaded by

Copyright:

Available Formats

HOL-1705-SDC-1

Overview of Site Recovery Manager

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

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

Lab Module List:

Module 2: Creating and Executing a Disaster Recovery Plan with Site

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

Module 4 - Automating Site Recovery Manager tasks with vRealize

Perform vSphere Replication using vReailze Orchestrator.

Lab Captains: Paul Irwin and Jeff Knous

Activation Prompt or Watermark

Is the Lab Ready

Copy and Paste

1. Click the SEND TEXT link in the top-left corner

Unpin Alarms and Work in Progress

It is a recommendation to unpin the Alerts and Work in Progress windows on the

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

Chrome Full Screen

Module 1 - Lighting Lab:

This Module contains the following lessons:

Total time required: 15 minutes.

Lesson 1: Fail-over a virtual machine

Launch the vSphere Web Client

Maximize the View

Verify replication connectivity status for each location

Identify replicated virtual machines

Locate the specified replicated virtual machine

1. Select the Monitor tab.

VM fail-over with Site Recovery Manager

Site Recovery Manager

Recovery Plans Inventory List

1. Select the Lightning Application Recovery Plan from the inventory.

Authenticate to Site Recovery Manager

1. You will be prompted to enter the appropriate credentials to authenticate to Site

Enter the following user account information.

2. Click the Log Inbutton to proceed.

Lightning Recovery Plan

1. Select the Monitor tab.

2. Select the Recovery Steps option button.

Recovery Options Selection

2. Of the two Recovery Types available, select the Planned Migrationoption.

3. Click the Next button to continue.

Monitor Recovery Progress

Browse virtual machine inventory

From the current screen...

Verify virtual machine status at the RegionA01 data center

In the Inventory tree on the left side of the screen...

Access Region-B vCenter - Verify Test Recovery

Navigate to the VMs and Templates view

Validate the running status of the Lightning Application

Lesson 2: Re-protect and fail back.

Site Recovery Manager

Recovery Plan Inventory List

Authenticate to Site Recovery Manager

Please enter the following credentials:

Recovery Plan view

1. Select the Monitortab from the top of Recovery Plan UI.