-
Table of ContentsLab Overview - HOL-1705-SDC-1 - Site Recovery
Manager: Data Center Migration andDisaster Recovery
.............................................................................................................
3
Overview of Site Recovery Manager
.......................................................................
4Lab Overview
..........................................................................................................
5Lab Guidance
..........................................................................................................
7
Module 1 - Lighting Lab: Failing over a site with Site Recovery
Manager (15 minutes,Beginner)
........................................................................................................................
14
Module Overview
..................................................................................................
15Lesson 1: Fail-over a virtual machine
....................................................................
16Lesson 2: Re-protect and fail back.
.......................................................................
38Conclusion.............................................................................................................
71
Module 2 - Executing a Disaster Recovery Plan using Site
Recovery Manager (60minutes, Beginner)
.........................................................................................................
73
Module Overview
..................................................................................................
74Lesson 1: Protect Virtual Machines using Site Recovery Manger
..........................75Lesson 2: Create a Virtual Machine
Recovery Plan................................................
88Lesson 3: Test The Recovery Plan
.........................................................................
96Lesson 4: Create Site Wide Recovery Plan
..........................................................
111Lesson 5: Review Audit Reporting in Site Recovery
Manager..............................133Lesson 6: Leverage VIN To
Ensure Dependent VMs Are Protected
Together........141Conclusion...........................................................................................................
145
Module 3 - Site Recovery Manager Advanced Topics (30 minutes,
Advanced)..............147Module Overview
................................................................................................
148Lesson 1: Virtual Machine Recovery Properties Overview
...................................149Lesson 2: Customizing the
Virtual Machine IP Address During Failover...............175Lesson
3: Virtual Machine Start-up Options
........................................................ 202Lesson
4: vSphere Replication, Advanced
Options..............................................
217Conclusion...........................................................................................................
228
Module 4 - Automating Site Recovery Manager tasks with vRealize
Orchestrator (30minutes, Advanced)
......................................................................................................
230
Module Overview
................................................................................................
231Lesson 1: vSphere Replication using vRealize Orchestrator
................................232Lesson 2: Add a Virtual Machine
to a Protection Group Using
vRealizeOrchestrator........................................................................................................
248Lesson 3: Protect a Virtual Machine Using vRealize Orchestrator
.......................257Lesson 4: Add a Virtual Machine to an
Existing Recovery Plan ...........................272Lesson 5: Test
the Recovery Plan
........................................................................
279Conclusion...........................................................................................................
297
Module 5 - SRM integration with NSX and Storage Policy Based
Protection Groups andStretched Storage (30 minutes, Advanced)
..................................................................
299
Hands-on Labs Interactive Simulation: Introduction to Site
Recovery Manager 6.1New Features
......................................................................................................
300
HOL-1705-SDC-1
Page 1HOL-1705-SDC-1
-
Conclusion...........................................................................................................
302
HOL-1705-SDC-1
Page 2HOL-1705-SDC-1
-
Lab Overview -HOL-1705-SDC-1 - Site
Recovery Manager: DataCenter Migration and
Disaster Recovery
HOL-1705-SDC-1
Page 3HOL-1705-SDC-1
-
Overview of Site Recovery ManagerVMware Site Recovery Manager is
an automation software solution that integrates withthe underlying
replication technology to provide policy-based management,
non-disruptive testing, and automated orchestration of recovery
plans. Site RecoveryManager delivers flexibility and choice, it
integrates natively with VMware vSphereReplication and also
supports a broad range of array-based replication
solutionsavailable from all major VMware storage partners.
Site Recovery Manager natively leverages the benefits of VMware
vSphere and can alsotake advantage of the Software-Defined Data
Center (SDDC) architecture, integratingwith other VMware solutions,
such as VMware NSX (network virtualization) and VMwareVirtual SAN
(hyper-converged software-defined storage).
Provision and manage storage and replication policies at the
virtual machinelevel.
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
regulatorycompliance.
Site Recovery Manager can dramatically lower the total cost of
ownership (TCO) throughmanagement and testing automation that
eliminates the complexity of manualprocesses, while enabling the
use of technology that lower capital expense for
recoveryinfrastructure.
See more at:
https://www.vmware.com/products/site-recovery-manager
HOL-1705-SDC-1
Page 4HOL-1705-SDC-1
https://www.vmware.com/products/site-recovery-manager/#sthash.5rxngITU.dpuf
-
Lab OverviewThis lab will consist of five modules addressing
topics related specifically to theimplementation of disaster
recovery and business continuity solutions in a vSphereenvironment.
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 minutesavailable 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 RecoveryManager (15 minutes, Beginner).
Module 2 - Executing a Disaster Recovery plan using Site
Recovery Manager (60minutes, 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 RecoveryManager
This module will perform a recovery of a single virtual machine
using Site RecoveryManager.
The student will use Site Recovery Manager to execute a disaster
recovery planfor a single Corp.local application.
Reprotect the single Corp.local application once it has been
recovered and thenfailback the application to the San Francisco
data center.
Module 2: Creating and Executing a Disaster Recovery Plan with
SiteRecovery Manager(60 minutes, Beginner)
The student will create a Recovery Plan and then test and
perform a recoverywithin 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
Page 5HOL-1705-SDC-1
-
The student will utilize the Advanced options within Site
Recovery Manager tocustomize 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
vRealizeOrchestrator (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
ProtectionGroups 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 havea localized manual deployed with your
lab, you may utilize this document to help guideyou through the
process:
http://docs.hol.vmware.com/announcements/nee-default-language.pdf
HOL-1705-SDC-1
Page 6HOL-1705-SDC-1
http://docs.hol.vmware.com/http://docs.hol.vmware.com/announcements/nee-default-language.pdf
-
Lab GuidanceThe lab consists of two sites, Region A and Region
B. Each Site consists of a singlecluster. Each Cluster contains 2
ESXi Hosts. Region A is the Protected Site and Region Bis 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 asecondary site
located in Reston, VA (Region B). The primary site is home to
executivemanagement, sales, accounting, human resources,
information technology (IT) andmost importantly, marketing. Due to
their success they noticed that many of their newcustomers were
located on the east coast and in order to service these new
customerswith the same level of service that they were able to
deliver to their west coastcustomers, they needed to open an office
on the east coast. They chose Reston, VA asthe location of their
secondary site. The Reston office will be a smaller version of
theprimary site located in San Francisco and will be the home to a
small sales team, a fewaccounting team members and marketing. In
order to ensure that the team located inReston is able to access
resources as quickly as they would as if they were in SanFrancisco
the company decided to invest in IT infrastructure at the Reston
office that willalso include enough infrastructure to recover all
primary applications in the event that adisaster 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 inSan Francisco (Region A) so that they can
recover VMs in Reston (Region B). They needassistance with all
aspects of Site Recovery Manager, both basic and
advancedfunctionality.
Activation Prompt or Watermark
When you first start your lab, you may notice a watermark on the
desktop indicatingthat Windows is not activated.
One of the major benefits of virtualization is that virtual
machines can be moved andrun on any platform. The Hands-on Labs
utilizes this benefit and we are able to run thelabs out of
multiple datacenters. However, these datacenters may not have
identicalprocessors, which triggers a Microsoft activation check
through the Internet.
Rest assured, VMware and the Hands-on Labs are in full
compliance with Microsoftlicensing requirements. The lab that you
are using is a self-contained pod and does nothave 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 thiswatermark.
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
Page 7HOL-1705-SDC-1
-
Hands-on Labs area, in your Expert-led Workshop, or online via
the survey comments aswe 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 5minutes for the lab startup process to
complete.
HOL-1705-SDC-1
Page 8HOL-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 corner2. Write the
text you want to paste into the console in the popup window3. 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 findingcertain keys.
HOL-1705-SDC-1
Page 9HOL-1705-SDC-1
-
To work around this, you can use the onscreen keyboard by
clicking on the quick-launchshortcut 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
Page 10HOL-1705-SDC-1
-
Unpin Alarms and Work in Progress
It is a recommendation to unpin the Alerts and Work in Progress
windows on theright-hand side of the vSphere Web Client. This will
allow you to work more easily withinthe lab providing you with more
visibility to the objects that you will be working withwithin this
lab. At any time during the lab, you can unpin Alerts and/or Work
inProgress 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 ofthese windows by selecting them on the
right-hand side of the vSphere Web Clientwindow.
HOL-1705-SDC-1
Page 11HOL-1705-SDC-1
-
Chrome Full Screen
To use the full screen option in Chrome, select the Options
button on the right-handside of the Chrome window and select the
square box located next to the Zoom option.
HOL-1705-SDC-1
Page 12HOL-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 browserand log you in automatically as
[email protected]. You can select either theRegionA or the
RegionB vCenter Web client from the task bar.
1. Verify that the following VMs have started: vr-01a and
VIN-01a. Repeat theabove process on the RegionB Web Client
verifying that the following VMs havestarted: vr-01b Your lab is
now ready for you to begin.
HOL-1705-SDC-1
Page 13HOL-1705-SDC-1
-
Module 1 - Lighting Lab:Failing over a site withSite Recovery
Manager(15 minutes, Beginner)
HOL-1705-SDC-1
Page 14HOL-1705-SDC-1
-
Module OverviewThis module will allow you to experience some of
the capabilities of Site RecoveryManager without any in-depth
configuration requirements. The module has beendesigned 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 theprimary data center to the DR location. The virtual
machine has already beenreplicated to the secondary site and is
ready to be failed over.
Lesson 2: Upon successful completion of the virtual machine
failover, you willleverage the reprotect function of Site Recovery
Manager to bring the virtualmachine back from the secondary site
with minimal administration effort.
Total time required: 15 minutes.
HOL-1705-SDC-1
Page 15HOL-1705-SDC-1
-
Lesson 1: Fail-over a virtual machineDuring this section, you
will perform a failover of an application that has already
beenprotected with Site Recovery Manager and been replicated to the
Region B data centerusing vSphere Replication.
Getting Started
Before you begin, please ensure that the Lab Status indicates
Ready. If the status isanything other than Ready, you may need to
wait a few minutes for the back groundservices 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 laband re-deploy another instance.
HOL-1705-SDC-1
Page 16HOL-1705-SDC-1
-
Launch the vSphere Web Client
The initial startup of the lab will automatically launch
separate Chrome browserwindows for both vcsa-01a.corp.local and
vcsa-01b.corp.local. The lab start up processwill also log you in
to the vSphere Web Client as [email protected].
1. Check the URL of the browser to verify that you are initially
usingvcsa-01a.corp.local for this lesson.
HOL-1705-SDC-1
Page 17HOL-1705-SDC-1
-
Maximize the View
1. If the Recent Tabs is visible at the bottom of the window,
select the thumb-tacicon in the lower right side of the vSphere Web
Client page to minimize thispane. This will help maximize the view
on the main section of the user interface.
HOL-1705-SDC-1
Page 18HOL-1705-SDC-1
-
vSphere Replication
You need to verify that the replication of the Engineering
team's Lightning Applicationvirtual machine has been configured and
that we have successfully replicated the virtualmachine to the data
center in Region B.
From the home screen of the vSphere 6.0 web client, select the
vSphere Replicationicon 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. Verifythat the vCenter server status indicates Enabled
(OK) under the vSphere Replicationcolumn.
Note: It could take up to 1 minute for the query to complete and
the statusinformation to be displayed.
HOL-1705-SDC-1
Page 19HOL-1705-SDC-1
-
Now that you have verified that replication is configured and
working between bothlocations, you need to check that the virtual
machine "lightning-01" has beensuccessfully replicated.
HOL-1705-SDC-1
Page 20HOL-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 thevSphere 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
button3. 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
Page 21HOL-1705-SDC-1
-
5. Details regarding the replication status of Lightning-vm are
displayed under theReplication Details tab. Examine these details
and verify that the Status isdisplaying OK.
HOL-1705-SDC-1
Page 22HOL-1705-SDC-1
-
VM fail-over with Site Recovery Manager
Now that you have verified that the Lightning-01 virtual machine
has been replicatedto the Region-B data center, you are ready to
fail-over this application using SiteRecovery Manager.
1. From the current page, navigate back to the home page by
clicking the Home icon atthe top of the screen.
2. Select the Home menu option from the drop down menu.
HOL-1705-SDC-1
Page 23HOL-1705-SDC-1
-
Site Recovery Manager
From the Home tab, click the Site Recovery icon to access the
Site Recovery ManagerHome page.
HOL-1705-SDC-1
Page 24HOL-1705-SDC-1
-
Recovery Plan
1. On the Site Recovery Home page, select the Recovery Plans
menu itemunder the Inventories section.
HOL-1705-SDC-1
Page 25HOL-1705-SDC-1
-
Recovery Plans Inventory List
The Recovery Plans Inventory is listed in the left menu pane.
These are all of thecurrently configured Recovery plans.
1. Select the Lightning Application Recovery Plan from the
inventory.
HOL-1705-SDC-1
Page 26HOL-1705-SDC-1
-
Authenticate to Site Recovery Manager
1. You will be prompted to enter the appropriate credentials to
authenticate to SiteRecovery Manager.
Enter the following user account information.
Username: [email protected]
Password: VMware1!
2. Click the Log Inbutton to proceed.
HOL-1705-SDC-1
Page 27HOL-1705-SDC-1
-
Lightning Recovery Plan
You are now going to start the recovery plan for the Lightning
application. In a latermodule, you will explore the various
recovery and testing options in greater detail.
With the Lightning Application Recovery Plan highlighted in the
inventory tree...
1. Select the Monitor tab.
2. Select the Recovery Steps option button.
3. Select the red circular button with the play symbol inside
it. This button launchesthe Recovery Confirmation Dialog box.
HOL-1705-SDC-1
Page 28HOL-1705-SDC-1
-
Recovery Options Selection
1. Place a check mark in the box. This check mark confirms that
you understand thatproceeding forward from this point will change
both the infrastructure and virtualmachines 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
Page 29HOL-1705-SDC-1
-
Begin VM fail-over
1. Verify that your selections from the previous screen are
correct, then click theFinish button to begin executing the
recovery of the Lightning-01 virtualmachine from the Region-A to
the Region-B data center.
HOL-1705-SDC-1
Page 30HOL-1705-SDC-1
-
Monitor Recovery Progress
You are now able to monitor the recovery of the Lightning-01 vm
as Site RecoveryManager steps through each step of the recovery
plan. The recovery process shouldtake no longer than a few
minutes.
1. Click the indicted arrows to expand the various steps to view
additional information.
HOL-1705-SDC-1
Page 31HOL-1705-SDC-1
-
Recovery Complete
1. Once the recovery plan has completed executing, you will see
that all the steps withinthe plan indicate a status of "Success"
with the over-all plan status at the top of themain window pane
displaying a "Recovery complete" message.
Let's verify that the Lightning-01 virtual machine has indeed
been powered down at theRegion-A data center and is now running on
the vSphere infrastructure located at theRegion-B data center.
HOL-1705-SDC-1
Page 32HOL-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
Page 33HOL-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 VMs folder under the RegionA01 data
center and verify thatthe Lightning-01 virtual machine is powered
off.
HOL-1705-SDC-1
Page 34HOL-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
Page 35HOL-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
Page 36HOL-1705-SDC-1
-
Validate the running status of the Lightning Applicationvm.
1. Expand the Recovered VMs folder under the RegionB01 data
center and verify thatthe Lightning-01 virtual machine is powered
on.
HOL-1705-SDC-1
Page 37HOL-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-overfrom the previous lesson. You will then proceed to fail
the Lightning application back toits original location in the
RegionA01 data center.
HOL-1705-SDC-1
Page 38HOL-1705-SDC-1
-
Site Recovery Manager
Now that you have verified that the Lightning-01 application has
been successfullyrecovered to RegionB01, you are going to begin the
process of preparing the virtualmachine 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 arealready logged into the Web client for the
vCenter at RegionB01, we will perform allactions at this site.
1. From the current page, expand the navigation menu by clicking
the Home icon atthe top of the screen.
2. Select the Site Recovery Manager menu option from the drop
down menu.
HOL-1705-SDC-1
Page 39HOL-1705-SDC-1
-
Recovery Plan
1. From the Site Recovery Manager page, select the Recovery
Plans option underthe Inventories subsection in the left hand
navigation menu.
HOL-1705-SDC-1
Page 40HOL-1705-SDC-1
-
Recovery Plan Inventory List
1. Select the Lightning Application Recovery Plan from the menu
on the leftside of the screen.
HOL-1705-SDC-1
Page 41HOL-1705-SDC-1
-
Authenticate to Site Recovery Manager
You will be prompted to authenticate to the Site Recovery
Manager instance at theRegionA01 data center from the RegionB01
data center.
Please enter the following credentials:
Username: [email protected]
Password: VMware1!
Click the log In button to access the Site Recovery Manager
UI.
HOL-1705-SDC-1
Page 42HOL-1705-SDC-1
-
Recovery Plan view
1. Select the Monitor tab from the top of Recovery Plan UI.
HOL-1705-SDC-1
Page 43HOL-1705-SDC-1
-
Lightning Application Recovery Plan
You are now going to reverse the direction of both the
replication and protection for theLightning-01 virtual machine by
executing the re-protect feature of Site RecoveryManager.
1. Ensure that the Lightning Application Recovery Plan menu item
has beenselected in the left menu.
2. Select the Monitor tab 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
Page 44HOL-1705-SDC-1
-
Re-protect a Virtual Machine
1. Place a check mark into the confirmation dialog box. (The
Force Cleanup optionshould be greyed out and not available as an
option at this time.)
2. Select Next to continue.
HOL-1705-SDC-1
Page 45HOL-1705-SDC-1
-
Re-protect Confirmation
1. Verify that the selections you made in the previous step are
correct. Then selectFinish to execute the re-protect workflow.
HOL-1705-SDC-1
Page 46HOL-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 andsynchronized in the opposite direction for the
Lightning-01 virtual machine. You canmonitor the status of the
replication of the virtual machine by navigating to the
vSphereReplication page of the vSphere Web Client.
HOL-1705-SDC-1
Page 47HOL-1705-SDC-1
-
vSphere Replication
To monitor the replication status of the Lightning-01 virtual
machine...
1. From the current page, expand the navigation menu by clicking
the Home icon atthe top of the screen.
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
Page 48HOL-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
Page 49HOL-1705-SDC-1
-
Select Target vSphere Replication Server
1. Select the Target sites menu option2. 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 Yes when prompted to reconnect.
2. Enter the credentials for the remote vSphere Replication
appliance.
Username: [email protected]
Password: VMware1!
HOL-1705-SDC-1
Page 50HOL-1705-SDC-1
-
3. Select OK to initiate the reconnect.
HOL-1705-SDC-1
Page 51HOL-1705-SDC-1
-
Verify connection status
1. If the connection to the vSphere replication server in site
RegionA01 is successful,you will see the status change to
Connected.
2. Select theMonitortab at the top of the main UI.
HOL-1705-SDC-1
Page 52HOL-1705-SDC-1
-
Monitor vSphere Replication
1. With the Monitor tab highlighted, select thevSphere
Replication button2. Select Outgoing Replications option 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 Statusindicator under the Replication Details tab
should display an OK.
Site Recovery Manager
With the replication of the Lightning-01 virtual machine
complete, you need to verifythat the Site Recovery Manager
re-protect workflow completed successfully.
1. From the current page, expand the navigation menu by clicking
the Home icon atthe top of the screen.
HOL-1705-SDC-1
Page 53HOL-1705-SDC-1
-
2. Select the Site Recovery menu option from the drop down
menu.
HOL-1705-SDC-1
Page 54HOL-1705-SDC-1
-
Recovery Plans
1. From the Site Recovery Manager page, select the Recovery
Plans option underthe Inventories subsection in the left hand
navigation menu.
HOL-1705-SDC-1
Page 55HOL-1705-SDC-1
-
Recovery Plan Inventory List
1. Select the Lightning Application Recovery Plan from the menu
on the leftside of the screen.
HOL-1705-SDC-1
Page 56HOL-1705-SDC-1
-
Recovery Plan Status Validation
The Lightning Application Recovery plan should now display a
status of "Ready". Thisindicates that the previous workflow
executed successfully and the plan is ready to beexecuted to
recover the virtual machine back to the RegionA01 data center,
which isnow 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 toverify that the information being displayed in
the UI accurately shows the protectionstatus of the Lightning-01
virtual machine.
1. Navigate back to the Web Client for the RegionA01 data center
by selecting theappropriate vSphere Web Client browser tab at the
top of the screen.
HOL-1705-SDC-1
Page 57HOL-1705-SDC-1
-
Note Verify that the URL for the Region A vCenter
(vcsa-01a.corp.local) is displayed inthe address bar.
HOL-1705-SDC-1
Page 58HOL-1705-SDC-1
-
VMs and Templates
1. From the current page, expand the navigation menu by clicking
the Home icon atthe top of the screen.
2. Select the VMs and Templates menu option from the drop down
menu.
Protected Virtual Machine status
1. Expand out the Protected VMs folder under the RegionA01 data
center and verifythat the Lightning-01 virtual machine icon is
displayed with small orange, green andblue squares on it. This icon
indicates that this particular entity in the inventory isowned and
managed by a service other than vCenter. (Sight Recovery
Manager)
This also indicates that the Lightning-01 virtual machine object
in the RegionA01 datacenter inventory is simply a placeholder
object with no connected networks and will
HOL-1705-SDC-1
Page 59HOL-1705-SDC-1
-
remain in this state until the vm is recovered by Site Recovery
Manager. You canhighlight the Lightning-01 virtual machine in the
inventory tree and view details aboutwhich service is managing this
entity on the VM summary tab.
HOL-1705-SDC-1
Page 60HOL-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 thevSphere Web client. We will utilize the Web
Client for RegionA01 as we are currentlyconnected to it.
1. From the current page, expand the navigation menu by clicking
the Home icon atthe top of the screen.
2. Select the Site Recovery Manager menu option from the drop
down menu.
HOL-1705-SDC-1
Page 61HOL-1705-SDC-1
-
Recovery Plan
1. From the Site Recovery Manager page, select the Recovery
Plans option in theleft hand navigation pane under the Inventories
menu item.
HOL-1705-SDC-1
Page 62HOL-1705-SDC-1
-
Recovery Plan Inventory List
1. Select the Lightning Application Recovery Plan from the menu
on the leftside of the screen.
HOL-1705-SDC-1
Page 63HOL-1705-SDC-1
-
Recovery Plan Status.
1. Verify that the Plan Status is displaying a Ready
notification.
HOL-1705-SDC-1
Page 64HOL-1705-SDC-1
-
Execute the Fail-Back Recovery Plan
1. To begin the process of failing the virtual machine back to
the RegionA01 datacenter, select the red button with the play
symbol.
HOL-1705-SDC-1
Page 65HOL-1705-SDC-1
-
Select Recovery Options
1. Place a check mark in the box to indicate that you understand
that movingbeyond this point could cause significant changes to the
environment.
2. Select the Planned Migration radio button. This option will
first perform agraceful shutdown of the protected virtual machine
at the source data center(RegionB01), perform a replication of all
recently changed data, then proceed tobring the recovered
Lightning-01 virtual machine at the destination data
centeronline.
3. Select the Next button to continue.
HOL-1705-SDC-1
Page 66HOL-1705-SDC-1
-
Verify Recovery Options
1. Verify that the selections you made in the previous step are
correct. Then clickthe 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
Page 67HOL-1705-SDC-1
-
Recovery Complete
1. You can monitor the status of the virtual machine recovery by
following theprogress of the steps in the Recovery Plan.
2. Upon successful completion of the recovery plan, the Plan
Status section willdisplay a Recovery Complete message.
HOL-1705-SDC-1
Page 68HOL-1705-SDC-1
-
VMs and Templates Inventory View
You can now navigate back to the VMs and Templates view in the
vSphere Web Client toverify that the Lightning-01 virtual machine
is once again running in the RegionA01 datacenter.
1. From the current page, expand the navigation menu by clicking
the Home icon atthe top of the screen.
2. Select the VMs and Templates menu option from the drop down
menu.
HOL-1705-SDC-1
Page 69HOL-1705-SDC-1
-
Verify Virtual Machine Recovery
1. Expand the RegionA01 data center inventory object and verify
that theLightning-01 virtual machine is has power on and is
operational.
2. You are also able to verify that the virtual machine has been
connected to anetwork and has a valid IP address.
3. Click the refresh button if the IP address is not
populated.
HOL-1705-SDC-1
Page 70HOL-1705-SDC-1
-
ConclusionIn this module, you successfully failed the
Lightning01 virtual machine over to therecover site at the Region-B
data center. You then proceeded to re-protect the virtualmachine
which, with minimal administrative overhead, reversed the
replication andprotection directions of the Lightning-01
application.
You concluded this module by using Site Recovery Manager to
fail-over the virtualmachine back to its original location in the
Region-A data center.
HOL-1705-SDC-1
Page 71HOL-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
hardwarefootprint, simplifying protection through VM-centric,
policy-based replication, anddecreasing operational expenses.
Non-disruptive testing enables more frequent disaster recovery
rehearsals, whichminimizes risk.
Recovery plans that can easily be updated and tested as new
workloads areprovisioned.
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 Managercan provide.
You can proceed to the next module listed below or any other
module which interestsyou most.
Module 2 - Executing a Disaster Recovery Plan using Site
Recovery Manager (60minutes, Beginner)
How to End Lab
To end your lab, click on the END button.
HOL-1705-SDC-1
Page 72HOL-1705-SDC-1
-
Module 2 - Executing aDisaster Recovery Plan
using Site RecoveryManager (60 minutes,
Beginner)
HOL-1705-SDC-1
Page 73HOL-1705-SDC-1
-
Module OverviewThe Accounting Department has recently completed
a migration of all company financialdata to a new multi-tiered
application platform. The new application consists of threevirtual
machines. Virtual machines Acct-App-01, Acct-DB-01 and
Acct-Web-01.
Once the Accounting department's virtual machines are in
production they arecompletely dependent on one another so it's
critical that they can be recoveredtogether. Failure to operate
these virtual machines together or manage them in aspecified
sequence specified by the application vendor could lead to data
loss or anunrecoverable system state.
The Accounting Department would like you to ensure that this
business criticalapplication is protected and recoverable in the
event of an anticipated or unexpectedoutage of the primary data
center.
In order to avoid being audited, the company must also be able
to provide a report onthe status of the Disaster Recovery Plan for
the application at any given time. Thisreport should detail the
recovery process and clearly identify if the execution of the
planwould 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 datacenter. You will
then test your multi-vm recovery plan and as an optional step, have
theopportunity to perform a complete site wide fail-over.
Finally, you will review Audit reports and see how vSphere
Infrastructure Navigatordisplays Site Recovery Manager
configuration information within an applicationdependency
mapping.
Total time required: 60 minutes
HOL-1705-SDC-1
Page 74HOL-1705-SDC-1
-
Lesson 1: Protect Virtual Machinesusing Site Recovery MangerThis
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 bothvcsa-01a.corp.local and vcsa-01b.corp.local.
The lab start up process will also log you inas
[email protected].
1. Check the URL of the browser to verify that you are initially
usingvcsa-01a.corp.local for this lesson.
HOL-1705-SDC-1
Page 75HOL-1705-SDC-1
-
Create a Protection Group
1. From the vCenter Home screen, select the Site Recovery
Icon.
HOL-1705-SDC-1
Page 76HOL-1705-SDC-1
-
Navigate to Protection Groups
1. Select Protection Groups.
HOL-1705-SDC-1
Page 77HOL-1705-SDC-1
-
Begin, Create Protection Group
A protection group is a collection of one or more virtual
machines that are failed overand failed back as a unit. In many
cases, a protection group consists of multiple virtualmachines that
support a service such as an accounting system. For example,
theaccounting system consists of a database server, one application
server, and one webserver. In most cases, it is not beneficial to
fail over part of a service (only one or two ofthe servers in the
example). All three virtual machines would be included in a
protectiongroup to enable failover of the services.
1. Select Objects.2. Select the Create Protection Group
icon.
HOL-1705-SDC-1
Page 78HOL-1705-SDC-1
-
Enter Protection Group Name
Creating a protection group for each application or service also
has the benefit ofselective testing. With Site Recovery Manager,
having a protection group for eachapplication enables
non-disruptive, low-risk testing of individual applications.
Applicationowners 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
Page 79HOL-1705-SDC-1
-
Remote Site Authentication
If requested, enter credentials for the target vCenter site.
1. Enter the user name [email protected] and password
VMware1!2. Select Log In.
HOL-1705-SDC-1
Page 80HOL-1705-SDC-1
-
Protection Group Type
1. Select Direction of protection RegionA01 -> RegionB01.2.
Select group type Individual VMs (vSphere Replication).3. Select
Next.
HOL-1705-SDC-1
Page 81HOL-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
Page 82HOL-1705-SDC-1
-
Verify Protection Group Configuration
1. Review and select Finish.
HOL-1705-SDC-1
Page 83HOL-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 beensuccessfully protected, placeholder virtual
machines will be visible in the vCenter Serverinventory at the
recovery site Region B. The presence of placeholders provides a
visualindication 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
Page 84HOL-1705-SDC-1
-
Region B vCenter - Verify Protection Group
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
Page 85HOL-1705-SDC-1
-
Region B - vCenter VM's and Templates
1. Select the Home Icon.2. Select VMs and Templates.
HOL-1705-SDC-1
Page 86HOL-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-01provides a visual indication to Site Recovery Manager
administrators that virtualmachines are protected. Placeholder
virtual machines have a unique icon in vSphereWeb Client and are
not powered on.
You have completed lesson 1 of module 2. It is recommended that
you now start lesson2 of module 2.
HOL-1705-SDC-1
Page 87HOL-1705-SDC-1
-
Lesson 2: Create a Virtual MachineRecovery PlanAfter you have
configured the protection group, you can create a recovery plan
forvirtual machines Acct-App-01, Acc-DB-01 and Acct-Web-01. A
recovery plancontrols every step of the recovery process, including
the order in which virtualmachines are recovered, IP address
changes, and so on. Protection groups can becreated from either
protected site. As one might expect, recovery plans are created
atthe recovery site.
HOL-1705-SDC-1
Page 88HOL-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
Page 89HOL-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
Page 90HOL-1705-SDC-1
-
Recovery Plan Name and Location
Creating a recovery plan for each application enables testing
and failover of individualapplications. Creating a recovery plan
that includes one or all of the protection groups isuseful 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
Page 91HOL-1705-SDC-1
-
Recovery Site
1. Select RegionB01.2. Select Next.
Remote Site Authentication
If requested, enter credentials for the target vCenter site.
1. Enter the user name [email protected] and password
VMware1!2. Select Log In.
HOL-1705-SDC-1
Page 92HOL-1705-SDC-1
-
Select Protection Group
A recovery plan must contain one or more protection groups. A
protection group can bepart of more than one recovery plan. In this
lesson you will use the Account Protectionsgroup to configure this
recovery plan.
1. Select the Accounting Protection Group.2. Select Next.
HOL-1705-SDC-1
Page 93HOL-1705-SDC-1
-
Recovery Plan Test Networks
One of the steps in creating a recovery plan is configuring a
test network for each of therecovery networks at the recovery site.
When testing a recovery plan, recovered virtualmachines 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 noexternal connectivity that is created
dynamically when a recovery plan is tested. This isa simple and
effective approach, but connectivity between virtual machines is
limited tothe virtual machines running on the same vSphere host.
The default setting, Isolatednetwork (auto created), can be changed
to another port group available at therecovery site.
Select Next.
HOL-1705-SDC-1
Page 94HOL-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.
You have completed lesson 2 of module 2. It is recommended that
you now start lesson3 of module 2.
HOL-1705-SDC-1
Page 95HOL-1705-SDC-1
-
Lesson 3: Test The Recovery PlanAfter creating a recovery plan,
it is beneficial to test the recovery plan to verify it worksas
expected. Site Recovery Manager features a non-disruptive testing
mechanism tofacilitate testing at any time. It is common for an
organization to test a recovery planmultiple times after creation
to resolve any issues encountered the first time therecovery 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
Page 96HOL-1705-SDC-1
-
Begin - Test Recovery Plan
1. Select Recovery Plans.
HOL-1705-SDC-1
Page 97HOL-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
Page 98HOL-1705-SDC-1
-
Replicate recent changes
For this particular test, we will not be replicating any recent
changes to the recoverysite. This is primarily to reduce the amount
of time required to complete this step in thelab environment.
1. If selected, uncheck the check box Replicate recent changes
to therecovery site.
2. Select Next.
HOL-1705-SDC-1
Page 99HOL-1705-SDC-1
-
Verify Recovery Plan Test Options
1. Verify that the options you chose in the previous step are
correct, then clickfinish to begin the test.
HOL-1705-SDC-1
Page 100HOL-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 theability to rectify the problems and
re-run the plan to ensure that all steps completewithout error.
Please note that this step can take up to 5 minutes to
complete.
HOL-1705-SDC-1
Page 101HOL-1705-SDC-1
-
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
Page 102HOL-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
Page 103HOL-1705-SDC-1
-
Region B vCenter - Verify Operational State
1. Select the vcsa-01b.corp.local vCenter.2. Select the Monitor
tab.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 >
RegionB01-COMP01 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
Page 104HOL-1705-SDC-1
-
Complete Recovery Test
1. Select the Home Icon.2. Select Site Recovery from the
dropdown menu.
HOL-1705-SDC-1
Page 105HOL-1705-SDC-1
-
Recovery Plans
1. Select the Recovery Plans.
RegionA01 Authentication
If requested, authenticate back to main site, RegionA01.
1. Enter User name: [email protected]. Enter Password:
VMware1!3. Select Log In.
HOL-1705-SDC-1
Page 106HOL-1705-SDC-1
-
Clean-Up the Recovery Plan
1. Select the Accounting Recovery Plan from the left side
menu.2. Select the Monitor tab.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
Page 107HOL-1705-SDC-1
-
Recovery Plan Clean Up Options
1. Click Next to continue.
HOL-1705-SDC-1
Page 108HOL-1705-SDC-1
-
Verify Options
1. Verify the options for the cleanup, then click Finish to
execute a cleanup of theTest Recovery.
HOL-1705-SDC-1
Page 109HOL-1705-SDC-1
-
Recovery Plan Ready
Once the clean up the test has completed, your recovery plan is
now ready forexecution either as another test, or as an actual
fail-over.
1. The Plan status field should now indicate Ready.
You have completed lesson 3 of module 2. It is recommended that
you now start lesson4 of module 2.
HOL-1705-SDC-1
Page 110HOL-1705-SDC-1
-
Lesson 4: Create Site Wide RecoveryPlanThis section will
demonstrate creating a site-wide recovery plan with multiple
protectiongroups 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 entireSan Francisco (Region A)
data center in the event of either a planned or
unplannedoutage.
HOL-1705-SDC-1
Page 111HOL-1705-SDC-1
-
Test Site-Wide Recovery Plan
1. From the RegionA01 vCenter Web Client select the Home Icon.2.
Select Site Recovery.
HOL-1705-SDC-1
Page 112HOL-1705-SDC-1
-
Recovery Plans Main Page
1. Select the Recovery Plans option under the Navigation pane on
the left side of thescreen.
HOL-1705-SDC-1
Page 113HOL-1705-SDC-1
-
Create new Recovery Plan
1. Select Objects.2. Select the Create New Recovery plan
icon.
HOL-1705-SDC-1
Page 114HOL-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
Page 115HOL-1705-SDC-1
-
Select Recovery Site
1. Select RegionB01.2. Select Next.
Log into Remote Site - RegionB
1. If requested, enter the user name [email protected]
and use thepassword VMware1!
2. Select Log In.
HOL-1705-SDC-1
Page 116HOL-1705-SDC-1
-
Select Protection Groups
1. Place a check mark next to all of the protection groups
listed. This allows you torecover all the virtual machines
associated with the protection groups by executing asingle recovery
plan.
2. Select Next.
HOL-1705-SDC-1
Page 117HOL-1705-SDC-1
-
Select Test Networks
This step is where you would define specific networks you would
want recovered virtualmachines 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
Page 118HOL-1705-SDC-1
-
Recovery Plan Confirmation
Verify that the choices you selected in the previous steps are
correct, then select Finishto complete the creation of the new
recovery plan.
HOL-1705-SDC-1
Page 119HOL-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
VMs that will be recovered as part of this recovery plan.5.
Select the green play icon in the Recovery Steps view to begin
testing the
Accounting recovery plan.
HOL-1705-SDC-1
Page 120HOL-1705-SDC-1
-
Review Recovery Plan.
1. Deselect Replicate recent changes to recovery site.2. Select
Next.
HOL-1705-SDC-1
Page 121HOL-1705-SDC-1
-
Ready To Complete Site-Wide Recovery Plan
1. Review and select Finish.
Please note that this step can take up to 5 minutes to
complete.
HOL-1705-SDC-1
Page 122HOL-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
Page 123HOL-1705-SDC-1
-
Region B vCenter - Verify Protection Group
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
Page 124HOL-1705-SDC-1
-
Region B vCenter - Inventory View
1. Select the Home icon2. Select VMs and Templates from the drop
down menu.
HOL-1705-SDC-1
Page 125HOL-1705-SDC-1
-
Region B vCenter - Verify Operational State
1. Select the vcsa-01b.corp.local vCenter.2. Select the Monitor
tab.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 VMs and verify that all listed virtual machines have
powered on atthe peer RegionB01 vCenter site.
HOL-1705-SDC-1
Page 126HOL-1705-SDC-1
-
Complete Recovery Test
1. Select the Home Icon.2. Select Site Recovery from the
dropdown menu.
HOL-1705-SDC-1
Page 127HOL-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: [email protected]. Enter Password:
VMware1!3. Select Log In.
HOL-1705-SDC-1
Page 128HOL-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.3.
Select the Cleanup icon to clean up the test and prepare the plan
for future use.
HOL-1705-SDC-1
Page 129HOL-1705-SDC-1
-
Recovery Plan Clean Up Options
1. Click Next to continue.
HOL-1705-SDC-1
Page 130HOL-1705-SDC-1
-
Recovery Plan Clean Up Options - Cont.
1. Review and select Finish.
HOL-1705-SDC-1
Page 131HOL-1705-SDC-1
-
Sit-Wide Recovery Plan - Ready
Once the clean up the test has completed, your recovery plan is
now ready forexecution either as another test, or as an actual
fail-over.
1. The Plan status field should now indicate Ready.
You have completed lesson 4 of module 2. It is recommended that
you now start lesson5 of module 2.
HOL-1705-SDC-1
Page 132HOL-1705-SDC-1
-
Lesson 5: Review Audit Reporting inSite Recovery ManagerRecovery
plan histories provide information about each run, test, or cleanup
of arecovery plan. The history contains information about the
result and the start and endtimes for the whole plan and for each
step in the plan. You can export history at anytime, but history
always contains entries only for completed operations. If an
operationis 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
Page 133HOL-1705-SDC-1
-
Begin, Create Recovery Plan
1. Select Recovery Plans.
Select the Recovery Plan
1. From the Recovery Plan menu on the left side of the page,
select the AccountingRecovery Plan.
2. Select the Monitor tab.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 thisparticular recovery plan for the time period
displayed.
HOL-1705-SDC-1
Page 134HOL-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 reportto. For this exercise, you will select the Web
Page (*.html) format option.
2. Once you have made your selection, click the generate button
to begingenerating the report for the Accounting Recovery Plan
Test.
HOL-1705-SDC-1
Page 135HOL-1705-SDC-1
-
Download Report
Once the report generation has completed, you will be presented
with the option todownload the report.
1. Click the Download Report button to continue.
HOL-1705-SDC-1
Page 136HOL-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 willautomatically be saved with the name of the recovery
plan.
2. Click the Save button to continue.
HOL-1705-SDC-1
Page 137HOL-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
Page 138HOL-1705-SDC-1
-
View Report
You can now view the exported report along with specific details
regarding each stepdefined in the recovery plan along with the
completion status of each step.
HOL-1705-SDC-1
Page 139HOL-1705-SDC-1
-
Return to Site Recovery Manager
1. In the Windows task bar at the bottom of the screen, select
the Minimized browser toreturn you to the vSphere Web client and
the Site Recovery Manager page.
You have completed lesson 5 of module 2. It is recommended that
you now start lesson6 of module 2.
HOL-1705-SDC-1
Page 140HOL-1705-SDC-1
-
Lesson 6: Leverage VIN To EnsureDependent VMs Are
ProtectedTogetherVMware vRealize Infrastructure Navigator(VIN)
automates discovery and dependencymapping of applications, and the
applications components, as they traverse the
virtualinfrastructure. This management solution renders
visualizations of the relationshipsamong application components
distributed throughout the virtual environment.Packaged as a VMware
vSphere Web Client plug-in, Infrastructure Navigator
integratesseamlessly into VMware vCenter Server to provide
continuous application discovery anddependency mapping for virtual
environments.
Integrating Site Recovery Manager (SRM) with Infrastructure
Navigator, the SRMprotection groups and SRM recovery plans of the
selected virtual machines aredisplayed in the dependency map. If a
virtual machine is part of a vApp, the vApp nameis also displayed
in the dependency map. Once SRM is integrated, the SRM
informationappears in the visual dependency map represented by a
special SRM symbol.
HOL-1705-SDC-1
Page 141HOL-1705-SDC-1
-
Begin - Site Recovery Manager and vRealize
InfrastructureNavigator
1. From the RegionA vCenter web client select the Home dropdown
menu.2. Select Hosts and Clusters.
vRealize Infrastructure Navigator - ApplicationDependencies
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 afocus area and Infrastructure Navigator is
showing a dependency map of the virtualmachines and applications
that the uses at Corp local. You will note that the above
HOL-1705-SDC-1
Page 142HOL-1705-SDC-1
-
picture is different than what you see in the lab, this is
because there is no SRMconfiguration applied in this example.
As a vCenter plug-in, Infrastructure Navigator runs within the
vSphere Web Client. Itseamlessly integrates with the vSphere Web
Client interface by adding an InfrastructureNavigator port-let to
provide application summary information based on the
contextselected in the vSphere Web Client navigation pane.
HOL-1705-SDC-1
Page 143HOL-1705-SDC-1
-
vRealize Infrastructure Navigator - ApplicationDependencies and
SRM
The dependency map is a map of relationships that displays the
services installed andrunning on a virtual machine. The dependency
map displays all virtual machinesconnected to the selected virtual
machine by incoming or outgoing dependencies.
1. Once SRM is integrated with Infrastructure Navigator, the SRM
Protection Groupsand SRM Recovery Plans for virtual machines
Acct-App-01, Acct-DB-01 andAcct-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
Page 144HOL-1705-SDC-1
-
ConclusionCongratulations on completing Module 2.
The primary features of Site Recovery Manager, creating
protection groups and recoveryplans along with testing the recovery
plans were covered in this module. The additionalitems covered in
this module were integration with vCenter Infrastructure Navigator
andaudit reporting. More details on these solutions can be found in
VMware Documentationand in other resources such as VMware Blogs and
the VMware Knowledge Base.
You've finished Module 2
Site Recovery Manager provides the following benefits:
Lower cost of disaster recovery by up to 50% by reducing the x86
hardwarefootprint, simplifying protection through VM-centric,
policy-based replication, anddecreasing operational expenses.
Non-disruptive testing enables more frequent disaster recovery
rehearsals, whichminimizes risk.
Recovery plans that can easily be updated and tested as new
workloads areprovisioned.
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 Managercan provide.
You can proceed to the next module listed below or any other
module which interestsyou most.
Module 3 - Site Recovery Manager Advanced Topics (30 minutes,
Advanced)
HOL-1705-SDC-1
Page 145HOL-1705-SDC-1
-
How to End Lab
To end your lab, click on the END button.
HOL-1705-SDC-1
Page 146HOL-1705-SDC-1
-
Module 3 - Site RecoveryManager Advanced Topics(30 minutes,
Advanced)
HOL-1705-SDC-1
Page 147HOL-1705-SDC-1
-
Module OverviewSite Recovery Manager, in addition to providing
the capability to fail-over and recovervirtual machines between
data centers, also includes a number of advanced featuresthat can
serve to enhance the recovery capabilities of the solution. In this
module, wewill 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
Page 148HOL-1705-SDC-1
-
Lesson 1: Virtual Machine RecoveryProperties OverviewIn this
lesson, we will introduce a number of the advanced options
available within SiteRecovery Manager for individual VM
recovery.
Getting Started
Before you begin, please ensure that the Lab Status indicates
Ready. If the status isanything other than Ready, you may need to
wait a few minutes for the back groundservices 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 laband re-deploy another instance.
HOL-1705-SDC-1
Page 149HOL-1705-SDC-1
-
Launch the vSphere Web Client
The initial startup of the lab will automatically launch
separate Chrome browserwindows for both vcsa-01a.corp.local and
vcsa-01b.corp.local. The lab start up processwill also log you in
to the vSphere Web Client as [email protected].
1. Check the URL of the browser to verify that you are initially
usingvcsa-01a.corp.local for this lesson.
HOL-1705-SDC-1
Page 150HOL-1705-SDC-1
-
Maximize the View
1. If the Recent Tasks window is visible, you can select the pin
icon in the lower rightside of the vSphere Web Client page to
minimize it and expand the main windowarea.
HOL-1705-SDC-1
Page 151HOL-1705-SDC-1
-
vSphere Replication
Select the "vSphere Replication" icon from the home tab on the
main page.
HOL-1705-SDC-1
Page 152HOL-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 statusinformation to be displayed.
Now that you have verified that replication is configured and
working between bothlocations, you need to reconnect the management
interface to Region B so that we canview and manage the vSphere
Replication appliance at that location.
HOL-1705-SDC-1
Page 153HOL-1705-SDC-1
-
Re-connect to Remote vSphere Replication Appliance.
1. Select the "Manage" menu button under the home tab.
HOL-1705-SDC-1
Page 154HOL-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 applianceshould be displaying a "Not Authenticated"
message.
3. Select the "Reconnect" button to initiate a connection to the
remote vSpherereplication 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.
Username: [email protected]
HOL-1705-SDC-1
Page 155HOL-1705-SDC-1
-
Password: VMware1!
3. Select "OK" to initiate the reconnect.
HOL-1705-SDC-1
Page 156HOL-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
Page 157HOL-1705-SDC-1
-
View vSphere Replication Status
1. Ensure that you have selected "Outgoing Replications" in the
left side menu2. The Status of the "Sales" virtual machines should
display "OK".
HOL-1705-SDC-1
Page 158HOL-1705-SDC-1
-
Open Site Recovery Manager
Now that we have ensured that all the Sales VMs have been
replicated, we will look atthe options available during recovery on
an individual VM basis. These options areaccessed 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
Page 159HOL-1705-SDC-1
-
View Site Information
Within Site Recovery we have two sites, RegionA01 and RegionB01.
RegionA01 is theprimary site and is associated with the vCenter
Server vcsa-01a.corp.local. RegionB01is 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
Page 160HOL-1705-SDC-1
-
Select Site
1. Select RegionA01 in the left column
2. If you are prompted for user credentials, enter the following
information.
Username: [email protected]
Password: VMware1!
3. Click the "Log In" button when done
HOL-1705-SDC-1
Page 161HOL-1705-SDC-1
-
HOL-1705-SDC-1
Page 162HOL-1705-SDC-1
-
Ensure Both Primary and Recovery Sites are Connected
The RegionA01 site is represented by the vCenter Server
vcsa-01a.corp.local. TheRegionB01 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
Page 163HOL-1705-SDC-1
-
Recovery Plans
Select the "Recovery Plans" menu item from the Navigator
menu.
HOL-1705-SDC-1
Page 164HOL-1705-SDC-1
-
View Recovery Plans
A Recovery Plan runs a series of steps that must be performed in
a specific order for agiven workflow such as a planned migration or
re-protect. You cannot change the orderor purpose of the steps, but
you can insert your own steps that display messages andrun
commands.
Site Recovery Manager executes recovery plan steps depending on
the test or recoverymethod.
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
Page 165HOL-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 page3. Select the "Virtual Machines" button
HOL-1705-SDC-1
Page 166HOL-1705-SDC-1
-
Individual Virtual Machine Recovery Options
There are 2 virtual machines within the Sales Application
Recovery Plan. These 2 VMsmake 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 themto display what the end-user requests.
Sales-DB-01: This VM is the host to multiple databases and
stores all datarelated 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 youwish to recover in up to 5 different
priority groups. VMs in Priority Group 1 will bestarted first while
VMs in Priority Group 5 will be started last. All virtual machines
thesame priority group will be powered-on before Site Recovery
Manager proceeds to thenext Priority Group to begin powering-on
those virtual machines.
To view Priority Groups:
HOL-1705-SDC-1
Page 167HOL-1705-SDC-1
-
1. Select the drop-down arrow that is populated with the number
3 next to "PriorityGroup".
HOL-1705-SDC-1
Page 168HOL-1705-SDC-1
-
Virtual Machine Dependencies
If one of the virtual machines needs to be powered-on before
other virtual machineswithin the same Priority Group, you can use
"VM Dependencies". With VMDependencies, you can specify one or many
VMs that should be powered-on before theVM that you are setting the
dependency on. Note that you can only set dependenciesfor 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 thismodule. 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 VMsrunning at the protected site before
recovering them at the recovery site. You have twooptions for
shutting down VMs, "Shutdown guest OS before power off (requires
VMwareTools)"and "Power Off".
The first option (Shutdown guest OS before power off) will
initiate a shutdown of theguest OS resulting in a clean shutdown of
the VM. In this situation, all applications arealso stopped and
shutdown properly.
HOL-1705-SDC-1
Page 169HOL-1705-SDC-1
-
The second option (Power Off) does not initiate a guest OS
shutdown and simply powersoff the VM. If a VM does not have VMware
Tools installed, the Power Off option will beused.
To view Shutdown Action options:
1. Select "Shutdown Action" menu item. We will modify the
Shutdown Action of aVM later within this module. Select "Shutdown
Action" again to minimize the"Shutdown Action" window.
HOL-1705-SDC-1
Page 170HOL-1705-SDC-1
-
Startup Action
Similar to the options that you have for Shutdown at the
protected site, you also haveoptions 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 Onthe VM. The Wait for VMware tools option is
important as any VMs dependent upon theVM being powered-on will
wait until both the VMware Tools and Additional Delay optionsare
satisfied.
Furthermore, the Recovery Plan will not proceed until both
VMware Tools and AdditionalDelay are satisfied which includes
proceeding to the next Priority Group for additionalVMs 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 theRecovery Plan within Site Recovery Manager.
Pre-Power On Steps can either be executed by the Site Recovery
Manager server or byprompting the user to perform a task or to
provide information that the user mustacknowledge 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 forsome 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
Page 171HOL-1705-SDC-1
-
2. To add a Pre Power On Step, select the Green Plus icon. The
Add Pre Power OnStep window will appear. Review the Add Pre Power
On Steps. Select Cancel toclose 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
Page 172HOL-1705-SDC-1
-
Post-Power On Steps
Post-Power On Steps are different than Pre-Power On Steps in
that they execute oncethe virtual machine and guest OS are
running.
Similar to Pre Power On Steps, you also have the option to run a
command on the SiteRecovery Manager server or by prompting the user
to perform a task or provideinformation that the user must
acknowledge before the recovery plan continues to thenext 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
Page 173HOL-1705-SDC-1
-
Lesson Conclusion
In this lesson, we reviewed the Site information within Site
Recovery Manager andensured that both Sites were connected. We then
reviewed each action available forindividual 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
Page 174HOL-1705-SDC-1
-
Lesson 2: Customizing the VirtualMachine IP Address During
FailoverDue to the proximity of Corp.local's data centers, the
networking team was unable toextend their IP network across both
Region A and Region B. Therefore, during recovery,it is a
requirement that the IP addresses of each VM being recovered are
modified tomatch the network environment at Region B.
In this lesson, we will customize the IP addresses to be used
for the Sales virtualmachines in the event that they need to be
recovered to the Region B data center dueto a planned migration of
disaster.
HOL-1705-SDC-1
Page 175HOL-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 thetop of the window.
2. Select Home.
HOL-1705-SDC-1
Page 176HOL-1705-SDC-1
-
Open Site Recovery Manager
In order to customize the IP addresses of the Sales virtual
machines, we need to connectto the Site Recovery Manager
solution.
1. Select Site Recovery from within the Home tab.
HOL-1705-SDC-1
Page 177HOL-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
Page 178HOL-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 asfollows:
Sales-DB-01 Sales-App-01
HOL-1705-SDC-1
Page 179HOL-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. Select Configure Recovery.
HOL-1705-SDC-1
Page 180HOL-1705-SDC-1
-
IP Customization
You are now ready to customize the individual properties of the
Sales-App-01 virtualmachine
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 beingrecovered via Site Recovery Manager. Later in this
lesson, we'll look at IP customizationrules.
HOL-1705-SDC-1
Page 181HOL-1705-SDC-1
-
Configure Protection
The Configure Protected Site IP Settings allows us to define the
current IP properties ofthe VM.
This setting is not used until after recovery has been
completed. In the event that weneed 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
berecovered at a moment's notice. In this case, Region B becomes
the protected site withRegion 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 seeConfigure Protection button.
HOL-1705-SDC-1
Page 182HOL-1705-SDC-1
-
Specify Protected Site IP Settings
Within the Configure Protected Site IP Settings - NIC 1, you can
use DHCP to obtain theIP address, manually enter the IP address by
choosing Use the following IPv4address or if the VM is running
VMware Tools, you can select the option to Retrievethe current IP
settings of the VM. We will use VMWare Tools to retrieve the
current IPinformation of the virtual machine. If the IP information
fails to populate, pleasemanually enter the IP information listed
below.
1. Select the Use the following IPv4 address radio button, then
select the Retrievebutton.
2.If the IP information fails to populate enter the IPv4
Address, Subnet Mask andGateway 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
Page 183HOL-1705-SDC-1
-
HOL-1705-SDC-1
Page 184HOL-1705-SDC-1
-
Configure Protected Site DNS
1. Select the DNS tab2. Select Use the following DNS server
addresses3. Enter a Preferred DNS server of: 192.168.110.104. Place
your cursor in the DNS suffixes text box and enter: corp.local5.
Select the Add button6. corp.local should now appear in the window
below the text box7. 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
Page 185HOL-1705-SDC-1
-
1. Select the Configure Recovery button to continue
HOL-1705-SDC-1
Page 186HOL-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 shownbelow.
IPv4 Address: 192.168.220.200
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.220.1
HOL-1705-SDC-1
Page 187HOL-1705-SDC-1
-
Configure Recovery Site DNS
1. Select the DNS tab2. Select Use the following DNS server
addresses3. Enter a Preferred DNS server of: 192.168.210.104. Place
your cursor in the DNS suffixes text box and enter: corp.local5.
Select the Add button6. corp.local should now appear in the window
below the text box7. Select OK
Sales App IP Confirmation
The IP Customization for the Sales-App-01 virtual machine is now
complete.
HOL-1705-SDC-1
Page 188HOL-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 toobtain an IP address on the correct
subnet after being recovered is through the use of IPcustomization
rules.
These rules apply to virtual machines failing over from the
protected sites IPv4 subnetto the recovery sites IPv4 subnet. For
example, from 10.15.23.0/24 to 10.16.24.0/24.
HOL-1705-SDC-1
Page 189HOL-1705-SDC-1
-
The IP customization rule states that during recovery Site
Recovery Manager evaluatesthe existing IP configuration of the
recovered virtual machines NICs and reconfiguresstatic 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 theold one by preserving the host bits of
the original IPv4 address, applying it to the targetsubnet. For
example, if the original protected site address is 10.15.23.55/24,
the newaddress would be 10.16.24.55/24.
If the default gateway text box is empty, Site Recovery Manager
derives the newgateway parameter from the original one by
preserving the host bits of the original IPv4address and placing it
in the target subnet. For example, if the original protected
sitegateway is 10.15.23.1, the new gateway is 10.16.24.1. If you
specify an explicit gatewayparameter, Site Recovery Manager checks
that the IPv4 address syntax is correct andapplies it exactly.
Site Recovery Manager applies DNS and other parameters as
specified. DHCP-enabledNICs are not subject to customization a