SRMICM61

VMware Site Recovery Manager:
Install, Configure, Manage

Lab Manual
Site Recovery Manager 6.1
VMware Education Services

VMware, Inc.
www.vmware.com/education
VMware Site Recovery Manager: Install, Configure, Manage

Site Recovery Manager 6.1
Part Number EDU-EN-SRMICM61-LAB
Lab Manual
Copyright/Trademark
Copyright 2016 VMware, Inc. All rights reserved. This manual and its accompanying
materials are protected by U.S. and international copyright and intellectual property laws.
VMware products are covered by one or more patents listed at http://www.vmware.com/go/
patents. VMware is a registered trademark or trademark of VMware, Inc. in the United States
and/or other jurisdictions. All other marks and names mentioned herein may be trademarks
of their respective companies.
The training material is provided as is, and all express or implied conditions,
representations, and warranties, including any implied warranty of merchantability, fitness for
a particular purpose or noninfringement, are disclaimed, even if VMware, Inc., has been
advised of the possibility of such claims. This training material is designed to support an
instructor-led training course and is intended to be used for reference purposes in
conjunction with the instructor-led training course. The training material is not a standalone
training tool. Use of the training material for self-study without class attendance is not
recommended.
These materials and the computer programs to which it relates are the property of, and
embody trade secrets and confidential information proprietary to, VMware, Inc., and may not
be reproduced, copied, disclosed, transferred, adapted or modified without the express
written approval of VMware, Inc.
Technical review: GS Khalsa, Evelyn Baymon-Boyd, Jeff Hunter, Garth Miller
Technical editing: Shalini Pallat
Production and publishing: Ron Morton, Jen Myers
The courseware for VMware instructor-led training relies on materials developed by the
VMware Technical Communications writers who produce the core technical documentation,
available at http://www.vmware.com/support/pubs.
www.vmware.com/education
TA B L E
OF
C ONTENTS
Lab 1: Installing the Production Site Recovery Manager Components . . . . . . . . . . . . . . . . . . . . . . . 1

Lab 2: Configuring Inventory Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Lab 3: Configuring Datastores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Lab 4: Deploying and Configuring vSphere Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Lab 5: Configuring vSphere Replication for Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Lab 6: Building a Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Lab 7: Creating and Modifying a Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Lab 8: (Optional) Using the dr-ip-customizer Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Lab 9: Testing and Executing a Recovery Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Lab 10: Reprotecting and Failing Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
iii
iv
Lab 1
Installing the Production Site Recovery

Manager Components
Objective: Install the Site Recovery Manager software
and prepare other components for upcoming labs
In this lab, you will perform the following tasks:
1. Access Your Lab Server System
2. Verify That the vCenter Server Services and Platform Services Controller Services are Running
3. Verify the Production vCenter Server Inventory
4. Configure a Virtual Machine Port Group
5. Install the Site Recovery Manager Software on the Production Site
6. Verify That the Site Recovery Manager Server Service Has Started
7. Pair the Production Site with the Recovery Site
8. Verify Site Pairing for the Production and Recovery Sites
The steps in this lab are already performed on the recovery VMware vCenter Server. You use the
recovery vCenter Server system for testing, planned migrations, and recovery.
Lab 1 Installing the Production Site Recovery Manager Components
Task 1: Access Your Lab Server System

You log in to your vCenter Server system that is used to perform the lab exercises.
Use the following information from the class configuration handout:
Production vCenter Server system FQDN
Student desktop login user name
Standard lab password
1. Start a remote connection application to connect to the lab environment.
Your instructor will provide details about how to access your student desktop system in the lab
environment.
2. Use your student desktop user name and the standard lab password to log in to your Production
vCenter Server system.
Task 2: Verify That the vCenter Server Services and Platform Services
Controller Services are Running
You use the Service Control command-line tool to verify that the vCenter Server services and
VMware Platform Services Controller services are running.
1. From your vCenter Server desktop, click the Command Prompt icon on the taskbar.
2. At the command prompt, enter F:.
3. At the command prompt, enter cd "Program Files\VMware\vCenter Server\bin".
4. Enter service-control --status.
5. Verify that the State for service for the vpxd, vmware-psc-client, and vspherewebclientsvc
services is RUNNING.
6. If the status of one of these services is STOPPED, then start the service.
Enter service-control --start vpxd to start the vpxd service.

Enter service-control --start vmware-psc-client to start the vmware-pscclient service.
Enter service-control --start vspherewebclientsvc to start the
vspherewebclientsvc service.
7. Verify that the State for service for the vpxd, vmware-psc-client, and vspherewebclientsvc
services is RUNNING.
8. Close the Command Prompt window.
Task 3: Verify the Production vCenter Server Inventory

You verify that the Production vCenter Server inventory is configured properly. You use the
inventory objects to configure the VMware Site Recovery Manager software.
vCenter Server system login user name
1. On the student desktop, double-click the Production vCenter shortcut icon.
The VMware vSphere Web Client window appears.

2. Maximize the Internet Explorer window.
3. On the vSphere Web Client login page, enter the vCenter Server system login user name and the
standard lab password.

4. Click Login.
5. In the center pane, select Hosts and Clusters.
6. In the Navigator pane, expand the Production vCenter Server inventory.
The following objects must exist in the inventory:

A data center named Production
A VMware ESXi host named esxiprod.vclass.local
Resource pools named Protected Services and vSphere Replication
Resource pools in the Protected Services resource pool named Protected Application
Servers, Protected Database Servers, and Protected Web Servers
Configured virtual machines: appsvr01 in the Protected Application Servers resource pool,
dbsvr01 in the Protected Database Servers resource pool, and websvr01 in the Protected
Web Servers resource pool
7. Verify that appsvr01, dbsvr01, and websvr01 are powered off.

8. In the Navigator pane, click the VMs and Templates icon.
9. Expand the Production vCenter Server inventory and verify that the SRM Protected
Services and vSphere Replication VMs folders exist in the inventory.
10. Verify that the virtual machines are located in the SRM Protected Services folder.
Task 4: Configure a Virtual Machine Port Group

You configure a virtual machine port group to be used by VMware vSphere Replication. This
task was already performed on the recovery data center.
Virtual switch for your production network
1. At the top of vSphere Web Client, click the Home icon and select Host and Clusters from the
drop-down menu.
2. Select esxiprod.vclass.local in the inventory.
4
3. In the center pane, click the Manage tab.
4. Click the Networking tab.

5. Under Virtual switches, click the Add host networking icon.
6. On the Select connection type page of the Add Networking wizard, select the Virtual Machine
Port Group for a Standard Switch check box and click Next.
7. On the Select target device page, verify that Select an existing standard switch is clicked.
8. Verify that the Select an existing standard switch text box contains the name of the virtual
switch for your production network.

9. If the Select an existing standard switch text box does not contain the correct information,
update the information.

a. Click Browse.
b. Select the correct virtual switch and click OK.
c. Click Next.
10. On the Connection settings page, enter the network label HBR-Net and click Next.
HBR stands for Host-based Replication and this connection will be used for vSphere
Replication.
11. On the Ready to complete page, click Finish.
12. Close Internet Explorer to exit vSphere Web Client.
Task 5: Install the Site Recovery Manager Software on the Production

Site
You install the Site Recovery Manager software on the Production vCenter Server system.
Installation software location
Installer name
Setup language
Installation folder location

Email address
Production vCenter Server system IP address
1. Navigate to the location of the installation software for Production Site Recovery Manager.
2. Double-click the installer name.
3. In the Site Recovery Manager installation wizard, select the setup language and click OK.
4. On the Welcome page of the Site Recovery Manager installation wizard, click Next.
5. On the VMware Patents page, click Next.
6. On the License Agreement page, click I agree to the terms in the license agreement and click
Next.
7. On the Installation Pre-requisites page, click Next.
8. On the Destination Folder page, click Change.
9. In the Folder name text box, enter your installation folder location information.
10. Click OK.
11. Click Next.
12. On the Platform Services Controller page, enter the Production vCenter Server system fully
qualified domain name (FQDN) in the Address text box.

You must not change the default value in the HTTPS Port text box. The default value is 443.
13. Enter the vCenter Server system login user name.
14. Enter the standard lab password.
15. Click Next.
16. On the VMware vCenter Server page, verify that the vCenter Server address that appears in the
drop-down menu matches the Production vCenter Server system FQDN.

17. Click Next.
18. On the Site Recovery Manager Extension page, enter the Production vCenter Server system
FQDN in the Local Site Name text box.

19. In the Administrator E-mail text box, enter the email address.
20. In the Local Host drop-down menu, select the Production vCenter Server system IP address.
You must select the correct IP address. You can ask your instructor if you are not sure.
You must not change the default value in the Listener Port text box. The default value is 9086.
21. Click Next.
22. On the Site Recovery Manager Plug-in ID page, verify that Default Site Recovery Manager
Plug-in identifier is selected.

23. Click Next.
24. On the Certificate Type page, verify that Automatically generate a certificate is selected.
25. Click Next.
26. On the Generate Certificate page, enter VMware in the Organization text box.
27. In the Organization Unit text box, enter VMware.
28. Click Next.
29. On the Database Server Selection page, select Use the embedded database server.
30. Click Next.
31. On the Embedded Database Configuration page, configure the database.
Option
Action
Data Source Name
Enter production in the text box.
Database User Name
Enter administrator in the text box.
Database Password
Enter vmware in the text box.
You must not change the Database Port text box value from the default value of 5678. You
must not change the Connection Count text box value from the default value of 5. You must
also not change the Max. Connections text box value from the default value of 20.
32. Click Next.
33. On the Site Recovery Manager Service Account Page, verify that the default Use Local System
account check box is selected and click Next.

34. On the Ready to Install the Program page, click Install.
35. When the installation is complete, click Finish to exit the installation wizard.
Task 6: Verify That the Site Recovery Manager Server Service Has
Started
You verify that the Site Recovery Manager server service has started to show that the Site Recovery
Manager software installed successfully.
1. From your Site Recovery Manager server desktop, click the Start button select Administrative
Tools.
The Administrative Tools window opens.
2. Double-click Services.
3. Find VMware vCenter Site Recovery Manager Server in the Name column.
4. Verify that the Status column shows Running.
5. Find VMware vCenter Site Recovery Manager Embedded Database in the Name column.
6. Ensure that the Status column shows Running.
7. Close the Services window.
8. Close the Administrative Tools window.
9. Double-click the Production vCenter shortcut icon on the student desktop.
The vSphere Web Client Internet Explorer window opens.

10. Maximize the vSphere Web Client Internet Explorer window.
11. Use the vCenter Server system login user name and the standard lab password to log in to
vSphere Web Client.

12. In the center pane, verify that Site Recovery appears under Inventories on the Home tab.
13. Leave the browser window open for the next task.
8
Task 7: Pair the Production Site with the Recovery Site

You configure a connection between the production and recovery sites. The Site Recovery Manager
software is preinstalled on the recovery site
Recovery vCenter Server system FQDN
1. In vSphere Web Client, click the Home icon and select Site Recovery from the drop-down
menu.
2. In the Navigator pane, click Sites.

3. In the Navigator pane, click production.vclass.local.
4. In the Guide to configuring SRM panel in the center pane, select 1. Pair sites.
You might need to unpin the Recent Tasks pane to view the entire center pane.
5. In the Pair Site Recovery Manager Servers dialog box, enter your Recovery vCenter Server
system FQDN in the PSC address text box.

You must not change the default value of 443 in the port text box.
6. Click Next.
7. In the Select vCenter Service pane, enter your vCenter Server system login user name and the
standard lab password.

8. Click Finish.
9. In the Security Alert warnings dialog box, click Yes to connect.
You must click Yes twice for each prompt to accept the certificates.
Task 8: Verify Site Pairing for the Production and Recovery Sites
You verify that the site pairing is complete.
1. In the center pane, scroll down to reveal the Paired Site panel.
2. Under Paired Site, verify that the recovery site is listed to the right of the Name field.
3. Verify that the statuses of the Client and Server connections appear as Connected.
4. In the Navigator pane, select recovery.vclass.local.

5. In the Paired Site pane, verify that the production site is listed to the right of the Name field.
6. Verify that the statuses of the Client and Server connections appear as Connected.
7. Leave vSphere Web Client open for the next lab.
10
Lab 2
Configuring Inventory Mappings

Objective: Configure inventory mappings between the
protected site and the recovery site in Site Recovery
Manager
2. Configure Resource Mappings on the Production Site
3. Configure Folder Mappings on the Production Site
4. Configure Network Mappings

You log in to your VMware vCenter Server system that is used to perform the lab exercises.
1. If you are already logged in to your student desktop, go to task 2.
2. Ask your instructor how to access your vCenter Server system.
For example, your instructor might ask you to use Remote Desktop Connection with the vCenter
Server system fully qualified domain name (FQDN) to access your vCenter Server system.
Lab 2 Configuring Inventory Mappings
11
3. Log in to your Production vCenter Server system with your student desktop login user name
and the standard lab password.

4. Double-click the Production vCenter shortcut icon on your desktop.
5. Use the vCenter Server system login user name and the standard lab password to log in to
VMware vSphere Web Client.
Task 2: Configure Resource Mappings on the Production Site

You configure resources that virtual machines use when they fail over to the recovery site.
menu.
3. In the Navigator pane, click production.vclass.local.
4. Click the Summary tab.
5. Under Guide to configuring SRM, select 2.1 Create resource mappings.
6. In the Create Resource Mapping dialog box, expand the production site and the VMware
ESXi host.
7. Select the Protected Services resource pool check box.
8. Expand the recovery site and the ESXi host.
9. Select the Recovered Services resource pool.
10. Click Add mappings.
11. On the production site, expand Protected Services.
12. Select the Protected Application Servers resource pool check box.
13. On the recovery site, expand Recovered Services.
14. Select the Recovered Application Servers resource pool.
12
16. Under Protected Services on the production site, select the Protected Database Servers
resource pool check box.

17. Under Recovered Services on the recovery site, select the Recovered Database Servers
resource pool.

19. Under Protected Services on the production site, select the Protected Web Servers resource
pool check box.

20. Under Recovered Services on the recovery site, select the Recovered Web Servers resource
pool.
22. Click Next.
23. On the Prepare reverse mappings page, click Finish.
24. Click the Manage tab.
25. Click the Resource Mappings tab.
26. Verify that the new resource mappings appear correctly
Task 3: Configure Folder Mappings on the Production Site

You configure the folder that virtual machines use when they fail over to the recovery site.
2. Under Guide to configuring SRM, select 2.2 Create folder mappings.
3. In the Create Folder Mapping dialog box, click Prepare mappings manually.
4. Click Next.
13
5. Expand the production site.

6. Select the SRM Protected Services folder check box.
7. Expand the recovery site.
8. Select the SRM Recovered Services folder.
10. Click Next.
13. Click the Folder Mappings tab.
14. Verify that the new folder mappings appear correctly.
Task 4: Configure Network Mappings

You configure networks that virtual machines use when they fail over to the recovery site.
2. Under Guide to configuring SRM, select 2.3 Create network mappings.
3. In the Create Network Mapping dialog box, click Prepare mappings manually.
4. Click Next.
5. In the Create Network Mapping dialog box, expand the production site.
6. On the production site, select the Prod-Net port group.
7. Expand the recovery site.
8. On the recovery site, select the Prod-Net port group.
14
10. On the production site, select the HBR-Net port group.

11. On the recovery site, select the HBR-Net port group.
13. On the production site, select the Internal port group.
14. On the recovery site, select the Internal port group.

16. Click Next.
17. On the Select test networks page, click Next.
20. Click the Network Mappings tab.
21. Verify that the new network mappings appear correctly.
15
16
Lab 3
3
Configuring Datastores
Objective: Configure inventory mappings between the
protected site and the recovery site in Site Recovery
Manager
2. Create Placeholder Datastores on the Recovery Site for Recovery
3. Create a Placeholder Datastore on the Production Site for Failback
4. Build Recovery Datastores

Lab 3 Configuring Datastores
17

For example, your instructor might ask you to use Remote Desktop Connection with the
vCenter Server system fully qualified domain name (FQDN) to access your vCenter Server
system.

5. Use the vCenter Server system login user name and standard lab password to log in to VMware
vSphere Web Client.
Task 2: Create Placeholder Datastores on the Recovery Site for

Recovery
You configure a placeholder datastore in VMware Site Recovery Manager after you create it in
VMware vSphere. You create the placeholder datastore on the recovery site.
Storage type
Storage LUN for placeholder virtual machines
1. In vSphere Web Client, click the Home icon and select Storage from the drop-down menu.
2. In the Navigator pane, expand the recovery.vclass.local vCenter Server.
3. In the Navigator pane, right-click the Recovery data center and select Storage > New
Datastore.
4. On the Location page of the New Datastore wizard, click Next.
5. On the Type page, select the VMFS storage type and click Next.
6. On the Name and device selection page, enter RecoveryPlaceholder in the Name text box.
7. From the Select a host to view its accessible disks/LUNs drop-down menu, select
esxirec.vclass.local.
8. Select the storage LUN for placeholder virtual machines and click Next.
9. On the Partition configuration page, click Next.
18
11. In the Recent Tasks pane, verify that the Create VMFS datastore task completes with a status of
Completed.
You might need to click Recent Tasks at the bottom-left of vSphere Web Client to view the
Recent Tasks pane if it is minimized.
12. In the Navigator pane, expand the Recovery data center and verify that the
RecoveryPlaceholder datastore exists.

menu.
14. In the Navigator pane, select Sites.

15. In the Navigator pane, select recovery.vclass.local.
17. Under Guide to configuring SRM, select 3. Configure placeholder datastore.
You might need to minimize the Recent Tasks pane to view the Guide to configuring SRM
panel.
18. In the Configure Placeholder Datastore dialog box, select the RecoveryPlaceholder datastore
and click OK.

20. Click the Placeholder Datastores tab.
21. Verify that the placeholder is created.
Task 3: Create a Placeholder Datastore on the Production Site for

Failback
You configure a placeholder datastore in Site Recovery Manager for future failback operations after
you create it in vSphere. You create the placeholder datastore on the production site.
Storage type
Storage LUN for placeholder virtual machines
1. In vSphere Web Client, click the Home icon and select Storage from the drop-down menu.
2. In the Navigator pane, expand the production.vclass.local vCenter Server.
3. In the Navigator pane, right-click the Production data center and select Storage > New
Datastore.
19
6. On the Name and device selection page, enter FailbackPlaceholder in the Name text box.
7. From the Select a host to view its accessible disks/LUNs drop-down menu, select
esxiprod.vclass.local.
8. Select the storage LUN for placeholder virtual machines and click Next.
11. In the Recent Tasks pane, verify that the Create VMFS datastore task completes with a status of
Completed.
You might need to click Recent Tasks at the bottom-left of vSphere Web Client to view the
Recent Tasks pane if it is minimized.
12. In the Navigator pane, expand the Production data center and verify that the
FailbackPlaceholder datastore exists.

You might need to refresh the Web page by clicking the refresh icon at the top of vSphere Web
Client.
menu.
14. In the Navigator pane, select Sites.
15. In the Navigator pane, select production.vclass.local.
17. Under Guide to configuring SRM, select 3. Configure placeholder datastore.
You might need to minimize the Recent Tasks pane to view the Guide to configuring SRM
panel.
18. In the Configure Placeholder Datastore dialog box, select the FailbackPlaceholder datastore
and click OK.

20. Click the Placeholder Datastores tab.
21. Verify that the placeholder is created.
Client.
20
Task 4: Build Recovery Datastores

You configure a recovery datastore in Site Recovery Manager for future failover operations after
you create it in vSphere. You create the recovery datastore on the recovery site.
Storage type
LUN for single virtual machine replication
LUN for multiple virtual machine replication
1. In vSphere Web Client, click the Home icon and select Storage.
2. In the Navigator pane, expand the recovery.vclass.local vCenter Server.
3. In the Navigator pane, right-click the recovery data center and select Storage > New Datastore.
6. On the Name and device selection page, enter HighPriorityVMs in the Name text box.
7. Select esxirec.vclass.local from the Select a host to view its accessible disks/LUNs drop-
down menu.
8. Select the storage LUN for single virtual machine replication and click Next.
11. Verify that the new datastore appears in the inventory.
Client.
12. In the Navigator pane, right-click the recovery data center and select Storage > New Datastore.
14. On the Type page, select the storage type and click Next.
15. On the Name and device selection page, enter Recovery-VMFS in the Name text box.
16. Select esxirec.vclass.local from the Select a host to view its accessible disks/LUNs drop-
down menu.
17. Select the storage LUN for multiple virtual machine replication and click Next.
21
20. Verify that the new datastore appears in the inventory.
Client.
22
Lab 4
Deploying and Configuring vSphere

Replication
4
Objective: Deploy and configure the vSphere Replication

components to operate with Site Recovery Manager
2. Configure the Production vCenter Server Managed IP Address
3. Deploy a vSphere Replication Management Appliance to the Production Site
4. Register the vSphere Replication Appliance with vCenter Single Sign-On
5. (Optional) Deploy a vSphere Replication Server to the Recovery Site
6. (Optional) Register the vSphere Replication Server on the Recovery Site
7. Configure a vSphere Replication Connection
Except for pairing VMware vSphere Replication management appliances, all other steps in this
lab are already performed on the recovery site.
Lab 4 Deploying and Configuring vSphere Replication
23

and the standard lab password

vSphere Web Client.
Task 2: Configure the Production vCenter Server Managed IP Address

You configure the vCenter Server managed IP address for proper operation of vCenter Extension
vService. vCenter Extension vService is used by the vSphere Replication appliance and the vSphere
Replication server.
Production vCenter Server system IP address
1. In vSphere Web Client, click the Home icon and select vCenter Inventory Lists.
2. In the Navigator pane, select vCenter Servers.
3. In the Navigator pane, select the production.vclass.local vCenter Server.
5. In the vCenter Server Settings - General page, click Edit.
6. In the Edit vCenter Server Settings dialog box, select Runtime settings.
7. Set the vCenter Server managed address to the Production vCenter Server system IP address.
You do not need to reboot the vCenter Server system.

24
8. Click OK.
9. Leave vSphere Web Client open for the next task.
Task 3: Deploy a vSphere Replication Management Appliance to the

Production Site
You deploy the vSphere Replication appliance on the Production VMware ESXi host. The
vSphere Replication management appliance is already deployed on the recovery site.
vSphere Replication appliance OVF file
vSphere Replication appliance FQDN
vSphere Replication appliance datastore

vSphere Replication appliance password
vSphere Replication appliance IP address
vSphere Replication appliance netmask
vSphere Replication appliance gateway address
vSphere Replication appliance DNS servers
NTP server IP address
1. In vSphere Web Client, click the Home icon and select Hosts and Clusters.
2. Expand production.vclass.local.
3. Expand Production.
The production ESXi host esxiprod.vclass.local appears.

4. Expand esxiprod.vclass.local.
5. In the Navigator pane, right-click vSphere Replication and select Deploy OVF Template.
6. On the Select source page of the Deploy OVF Template wizard, click Local File.
7. Click Browse and navigate to the installation software location.
The Open file dialog box might be minimized in the taskbar. You can maximize the window by
clicking it in the taskbar.
8. Select the vSphere Replication appliance OVF file and click Open.
9. Click Next.
25
10. On the Review details page, click Next.

11. On the Accept License Agreements page, click Accept and click Next.
12. On the Select name and folder page, enter the vSphere Replication appliance FQDN in the
Name text box.

You must ensure that you have changed the name of the machine.
13. In the Select a folder or datacenter pane, expand the inventory and select the vSphere
Replication VMs folder.

14. Click Next.
15. On the Select configuration page, select 2vCPU from the Configuration drop-down menu and
click Next.
16. From the Select virtual disk format drop-down menu, select Thin Provision.
You must verify that Thin Provision is selected. Otherwise you might encounter issues in later
labs.
17. On the Select storage page, select the vSphere Replication appliance datastore
18. Click Next.
19. On the Setup networks page, select HBR-Net from the Destination drop-down menu if it is not
already selected.
20. Select Static - Manual from the IP allocation drop-down menu.
21. In the Destination:HBR-Net - Protocol settings dialog box, enter the vSphere Replication
appliance DNS servers in the DNS servers text box.

22. In the Gateway text box, enter the vSphere Replication appliance gateway address.
23. In the Netmask text box, enter the vSphere Replication appliance netmask address and click Next.
24. Under Application on the Customize template page, enter the vSphere Replication appliance
password in the Enter password text box and the Confirm password text box.
25. In the NTP Servers text box, enter the NTP server IP address.
26. Expand Networking Properties.
27. In the Management Network IP Address text box, enter the vSphere Replication appliance IP
address.
NOTE
In this step, you must provide the IP address of the vSphere Replication appliance, not the
vCenter Server IP address. Failure to provide the correct IP address might result in
redeployment of the appliance.
26
28. Click Next.

29. On the vService bindings page, click Next.
30. On the Ready to complete page, select the Power on after deployment check box and click
Finish.
31. Click the Monitor tab.
32. Click the Tasks tab.
33. Under the Task Name field, monitor the progress of the deployment operation.
The appliance takes approximately 5 minutes to boot and start all of its services.
Task 4: Register the vSphere Replication Appliance with vCenter

Single Sign-On

vSphere Replication appliance user name
vSphere Replication appliance password
1. In vSphere Web Client, click the Home icon and select vSphere Replication from the drop-
down menu.
2. In the center pane, click the Home tab.
It might take 10 to 15 seconds for the statuses of the vSphere Replication appliances to refresh.
The production.vclass.local appliance reports a configuration issue.
3. In the center pane, select production.vclass.local.
4. On the Home tab, click the Configure link.
A new browser tab opens.

5. If a certificate warning appears, click Continue to this website (not recommended).
6. On the vSphere Replication Appliance (VAMI) page, enter the vSphere Replication appliance
user name and password.

27
You use the Virtual Appliance Management Interface (VAMI) to register the endpoint and the
certificate of the vSphere Replication management server with the vCenter Lookup Service, and also
to register the vSphere Replication solution user with the VMware vCenter Single Sign-On
administration server.
7. Click Login.
You are logged in to the vSphere Replication appliance.

8. Click the System tab.
9. Click Time Zone.
10. In the System Time Zone drop-down menu, select US/Pacific.
11. Under Actions, click Save Settings.
12. Click the VR tab.
13. Click Configuration.
14. In the Startup Configuration window, verify that the LookupService Address text box matches
the Production vCenter Server system FQDN.

15. Verify that the SSO administrator text box matches the vCenter Server System login user name.
16. In the Password text box, enter the standard lab password.
You might need to scroll down to view this text box.

17. Under Actions, click Save and Restart Service.
18. In the Confirm SSL Certificate dialog box, click Accept.
The vSphere Replication appliance service takes approximately 2 minutes to start.

Configuration is complete when the Successfully saved the configuration message appears.
19. Under Service Status, verify that the VRM service status is running.
20. In the top-right corner of vSphere Web Client, click the Logout user root link.
21. Close the vSphere Replication Appliance tab.
22. In vSphere Web Client, click the Refresh icon.
It might take approximately 2 minutes for the status to change.

23. Verify that the status of vSphere Replication for the production.vclass.local vCenter Server
appears as Enabled (OK).
24. If the status does not appear as Enabled (OK), consult your instructor.
28
Task 5: (Optional) Deploy a vSphere Replication Server to the

Recovery Site
You deploy an additional vSphere Replication server on the recovery site to load balance replication
tasks. Minimal virtual machines are replicated in the labs. The vSphere Replication management
appliance that you deployed in the previous task can replicate up to 200 machines without an
additional vSphere Replication server.
vSphere Replication server OVF file
vSphere Replication server FQDN
vSphere Replication server datastore
vSphere Replication server password

vSphere Replication server IP address
vSphere Replication server netmask
vSphere Replication server gateway address
vSphere Replication server DNS servers
1. Click the Home icon and select vSphere Replication from the drop-down menu.
2. In the vCenter Server column, select recovery.vclass.local.
The status of the vSphere Replication appliance might take a few seconds to refresh.
3. On the Home tab of the vSphere Replication window, click Manage.
4. Click the vSphere Replication tab.
5. Select the Replication Servers link.
6. Click the Deploy new vSphere Replication server from an OVF template icon.
This icon might not display correctly on some versions of VMware Site Recovery Manager.
7. On the Select source page of the Deploy OVF Template wizard, click Local File.
29
8. Click Browse and navigate to the installation software location.
The Open file dialog box might be minimized in the taskbar. You can click it in the taskbar to
maximize it.
9. Select the vSphere Replication server OVF file and click Open.
10. Click Next.
11. On the Review details page, click Next.
12. On the Select name and folder page, enter the vSphere Replication server FQDN in the Name
text box.
You must ensure that you changed the name of the machine.
13. In the Select a folder or datacenter dialog box, expand the inventory to select the vSphere
Replication VMs folder and click Next.

14. On the Select a resource page, expand esxirec.vclass.local to select the vSphere Replication
resource pool and click Next.

15. From the Select virtual disk format drop-down menu, select Thin Provision.
You must verify that Thin Provision is selected. Otherwise you might encounter issues in later
labs.
16. On the Select storage page, select the vSphere Replication server datastore.
17. Click Next.
18. On the Setup networks page, verify that Management Network is set to HBR-Net.
19. From the IP allocation drop-down menu, select Static - Manual.
20. Under Destination:HBR-Net - Protocol settings, verify that the DNS servers text box contains
the IP address of the vSphere Replication server DNS servers.

21. In the Gateway text box, verify that the gateway is the vSphere Replication server gateway
address.
22. In the Netmask text box, verify that the netmask is the vSphere Replication server netmask
address.
23. Click Next.
24. Under Application on the Customize template page, enter the vSphere Replication server
password in the Enter password text box and Confirm password text box.
25. In the NTP Servers text box, enter the NTP Server IP address.
26. Expand Networking Properties.
30
27. In the Management Network IP Address text box, enter the vSphere Replication server IP
address.
NOTE
You must provide the IP address of the vSphere Replication server, not the vCenter Server IP
address.
28. Click Next.
29. On the Ready to complete page, select Power on after deployment and click Finish.
31. Click the Tasks link.
You must monitor the progress of the deployment operation until it completes. Your vSphere
Replication server does not yet appear in the vSphere Replication panel because you must
register the server.
32. Click the Home icon and select VMs and Templates.
33. Verify that your vSphere Replication server was created and booted successfully.
You might need to wait for 5 minutes and refresh vSphere Web Client before the virtual
machine appears.
a. In the Navigator pane, expand recovery.vclass.local > Recovery > vSphere Replication
VMs.
b. Select your vSphere Replication server.
The vSphere Replication server appliance that you deployed should be present in the
vSphere Replication VMs folder.
c. In the center pane, click the Summary tab and verify that your vSphere Replication server
is powered on.
31
d. In the center pane, verify that the VMware Tools status is Running.
If the VMware Tools status is Running, the server has booted successfully.
Task 6: (Optional) Register the vSphere Replication Server on the

Recovery Site
You register your vSphere Replication server appliance with the vCenter Server system at the
recovery site.
vSphere Replication server FQDN
2. On the Home tab of the vSphere Replication window, click recovery.vclass.local.
NOTE
You must not click the name because that opens vCenter Server. You must click only the
appropriate row on the vCenter list to select it.
5. Select Replication Servers.
6. Click the Register a virtual machine as a vSphere Replication Server icon.
7. In the Register vSphere Replication Server dialog box, expand the recovery data center.
8. Expand the vSphere Replication VMs folder.
9. Select your vSphere Replication server FQDN.
10. Click OK.
32
11. On the vSphere Replication tab, verify that your vSphere Replication server appears.
12. Log out of vSphere Web Client.

Task 7: Configure a vSphere Replication Connection

You configure a connection between the vSphere Replication appliances at each site.

vCenter Server System login user name
Recovery vCenter Server system FQDN
1. Use the vCenter Server System login user name and the standard lab password to log in to
vSphere Web Client.

NOTE
You must log out and log back in to ensure that the changes made to vSphere Replication
correctly take effect.
2. In vSphere Web Client, click the Home icon and select vSphere Replication from the drop-
down menu.
3. In the center pane of the vSphere Replication window, select production.vclass.local.

6. At the top of the center pane, select Actions > All vSphere Replication Actions > Connect to
Target Site to open the Connect to Target Site dialog box.

33
7. Select Connect to a remote site.

8. Enter the Recovery vCenter Server system FQDN in the Platform Services Controller
address of the remote site text box.

9. Log in using the vCenter Server System login user name and standard lab password.
10. Under Select a vCenter Server to connect to, select recovery.vclass.local.
You must ensure that recovery.vclass.local is selected.

11. Click OK.
12. Click the Target Sites link.
NOTE
The connection process might take a minute to complete.

13. Monitor the progress of the configuration task in the Recent Tasks pane.
The Recent Tasks pane might be minimized at the bottom-left corner of vSphere Web Client.
You must click the Recent Tasks link to maximize the window.
You might also need to click Refresh.
14. Click the Home icon and select vCenter Inventory Lists from the drop-down menu.
15. In the Navigator pane, expand Resources and select vCenter Servers.
16. Under vCenter Servers, select the production.vclass.local vCenter Server system.
18. Under vSphere Replication on the Summary tab, verify that Target sites shows that one site is
connected.
34
19. Expand Target Sites to verify that recovery.vclass.local appears as Connected.
20. Reconnect the recovery site if it has a status of Not Connected or Not Authenticated.
a. Click the Manage tab.
b. Click the vSphere Replication tab.
c. Under Replication Servers, right-click your vSphere Replication appliance and select
Reconnect.
35
36
Lab 5
Configuring vSphere Replication for

Virtual Machines
Objective: Configure vSphere Replication to replicate

virtual machines to mapped datastores
2. Configure Replication for a Single Virtual Machine
3. Configure Replication for Multiple Virtual Machines

Lab 5 Configuring vSphere Replication for Virtual Machines
37

vSphere Web Client.
Task 2: Configure Replication for a Single Virtual Machine

You configure replication for your database server virtual machine.
1. In vSphere Web Client, click the Home icon and select Hosts and Clusters from the drop-
down menu.
2. In the Navigator pane, expand production.vclass.local > Production > esxiprod.vclass.local >
Protected Services > Protected Database Servers.

3. Right-click your database server virtual machine dbsvr01 and select All vSphere Replication
Actions > Configure Replication.

4. On the Replication type page, click Next.
5. On the Target site page, select the recovery site recovery.vclass.local and click Next.
6. On the Replication Server page, click Next.
7. On the Target location page, click the Edit link.
8. On the Select Target Location page, select the HighPriorityVMs datastore.
9. Click OK.
10. On the Target Location page, ensure that the Target VM location appears as [HighPriorityVMs]
and click Next.

11. On the Replication options page, click Next.
12. On the Recovery settings page, move the Recovery Point Objective (RPO) slider to 15
minutes.
13. Click Next.
15. Monitor the progress of the configuration task in the Recent Tasks pane.
The Recent Tasks pane might be minimized at the bottom-left corner of vSphere Web Client.
Clicking the Recent Tasks link maximizes the window.
16. Right-click your dbsvr01 database server virtual machine and select Power > Power On.
17. In the Navigator pane, select dbsvr01.
38
18. In the center pane, click the Summary tab.
If the yellow highlighted Answer a question message appears, select I copied it.
19. Verify that dbsvr01 is powered on.
20. Verify that the status of VMware Tools is Running.
The status of VMware Tools might take a few seconds to refresh after power on.
23. In the Home pane, click the Monitor icon.
24. Select Outgoing Replications.
25. Monitor the Status column and wait until the replication status changes to OK.
26. In the Target Location column, verify that the target location of the replicated virtual machine is
recovery.vclass.local.
Task 3: Configure Replication for Multiple Virtual Machines
You configure the replication of your application server and Web server virtual machines.
1. Click the Home icon and select VMs and Templates from the drop-down menu.
2. In the Navigator pane, expand production.vclass.local > Production.
3. In the Navigator pane, select the SRM Protected Services folder.
4. In the center pane, click the Related Objects tab.
5. Click the Virtual Machines tab.
6. Click the State column heading to sort the virtual machines by state.
7. Select your appsvr01 application server.
8. Ctrl+click the websvr01 Web server virtual machine.
Both appsvr01 and websvr01 are selected.

9. Right-click websvr01 and select All vSphere Replication Actions > Configure Replication.
10. In the Configure Replication warning dialog box, select Yes to start the Configure Replication
for 2 Virtual Machines wizard.

11. On the Validation page, click Next.
12. On the Replication type page, click Next.
13. On the Target site page, select the recovery.vclass.local.
39
14. Click Next.

15. On the Replication server page, click Select vSphere Replication server.
NOTE
If you did not deploy and register the VMware vSphere Replication server to the recovery
site in the previous lab, you can go to step 17.
You do not need to change the vSphere Replication server in this lab. However, by doing so,
you offload additional replications for load balancing purposes to the vSphere Replication
server.
16. Select the VRSprod.vclass.local vSphere Replication server.
17. Click Next.
18. On the Target location page, select the Edit for all link.
19. Select the Recovery-VMFS datastore.
20. Click OK.
21. On the Target Location page, verify that the Target VM location for both the websvr01 and
appsvr01 virtual machines is listed as [Recovery-VMFS] and click Next.

22. On the Replication options page, click Next.
23. On the Recovery settings page, move the Recovery Point Objective (RPO) slider to 30
minutes.
24. Click Next.
27. Click Tasks.
28. Monitor the progress of the configuration task until it is completed.
29. In the center pane, click the Summary tab
The virtual machines appsvr01 and websvr01 have a Replication Status of Not Active because
they are not powered on.
30. In the Navigator pane, expand SRM Protected Services.
31. In the Navigator pane, right-click appsvr01 and select Power > Power On.
32. Verify that appsvr01 is powered on.
40
33. In the Navigator pane, right-click websvr01 and select Power > Power On.
Verify that websvr01 is powered on.
34. In the Navigator pane, select appsvr01.
35. Verify that the status of VMware Tools is shown as Running.
38. Click the Monitor icon.
39. Click vSphere Replication.
40. In the Outgoing Replications list, monitor the replication operations until the status changes to
OK.
You might need to click Refresh to view the latest status.

41
42
Lab 6
Building a Protection Group

Objective: Build a protection group
2. Create a Protection Group for an Individual Virtual Machine
3. Create a Storage Policy Protection Group
4. Create and Assign a Storage Policy to a Virtual Machine by Using Storage tags
5. (Optional) Create a Storage Policy Protection Group
6. Edit a Protection Group

Lab 6 Building a Protection Group
43


5. Use the vCenter Server system login user name and standard lab password to log in to the
Task 2: Create a Protection Group for an Individual Virtual Machine

You configure a protection group for your database server virtual machine.
1. In vSphere Web Client, click the Home icon and select Site Recovery from the drop-down menu.
3. In the Navigator pane, select the production.vclass.local production site.
5. In the center pane, scroll down to reveal the Guide to configuring SRM pane and click the 5.
Create a protection group link.

6. On the Name and location page of the Create Protection Group wizard, enter Protect
database server in the Name text box.

7. In the Location list, select recovery.vclass.local - production.vclass.local.
8. Click Next.
9. On the Protection group type page, select production.vclass.local -> recovery.vclass.local
under Direction of protection.

10. On the Protection group type page, select Individual VMs (vSphere Replication) under
Protection group type.

11. Click Next.
12. On the Virtual machines page, select the dbsvr01 database server check box.
13. Click Next.
15. Click the Related Objects tab.
16. Click the Protection Groups tab.
44
17. In the Navigator pane, select the recovery.vclass.local recovery site.

18. In the Protection Groups panel, verify that your protection group is created.
20. In the Navigator pane, expand recovery.vclass.local > Recovery > SRM Recovered Services.
21. Verify that a placeholder virtual machine for dbsvr01 exists.
Task 3: Create a Storage Policy Protection Group

You create a tag and assign it to a datastore that contains the application, database, and Web server
virtual machines as part of the prerequisite steps to create a storage policy protection group (SPPG).
1. In vSphere Web Client, click the Home icon and select Tags from the drop-down menu.
2. In the center pane, click the Items tab.
3. In the center pane, click the New tag icon.
4. On the New Tag page, enter SPPG-VMs in the Name text box.
5. In the Description text box, enter Datastores containing SPPG VMs.
6. Select New Category from the Category drop-down menu.
7. In the Category Name text box, enter Prod-SPPG-VMs.
8. Deselect the All objects check box.
The Associable Objects Types options become available.

9. In Associable Object Types, select Datastore.
10. Under Tag, enter Datastores containing SPPG VMs in the Description text box.
11. Click OK.
12. In the center pane, verify that the new tag is created.
13. Click the Categories tab.
14. In the center pane, verify that the new tag is created.
45
15. Click the Home icon and select Storage from the drop-down menu.
16. In the Navigator pane, expand production.vclass.local > Production.
17. Click the esxiProdLocal1 datastore.
20. Verify that the application, database, and Web server virtual machines are located in this datastore.
21. In the Navigator pane, right-click esxiProdLocal1 and select Tags > Assign Tag.
22. On the esxiProdLocal1 - Assign Tag page, select SPPG-VMs under Tag Name.
23. Click Assign.
25. In the center pane, expand the Tags pane.
You must verify that the assigned tag is SPPG-VMs and the category is Prod-SPPG-VMs.
Task 4: Create and Assign a Storage Policy to a Virtual Machine by

Using Storage tags
You create and assign a storage policy to a datastore by using storage tags as part of the prerequisite
steps to create a SPPG.
1. In vSphere Web Client, click Home and select Policies and Profiles from the drop-down menu.
2. In the Navigator pane, click the VM Storage Policies icon.
3. Under the Objects tab in the center pane, click the Create a new VM storage Policy icon.
The Create New VM Storage Policy wizard appears.

46
4. On the Name and description page, enter SPPG VM Storage Policy in the Name text box.
5. In the Description text box, enter VM policy for SPPGs in SRM.
6. Click Next.
7. On the Rule-Sets page, click Next.
8. On the Rule-Set 1 page, click Add tag-based rule.
9. From the Categories drop-down menu, select Prod-SPPG-VMs.
The SPPG-VMs tag appears.

10. Select the SPPG-VMs check box.
11. Click OK.
12. Click Next.
13. On the Storage compatibility page, click Next.
15. On the Objects tab, verify that the VM Storage Policy SPPG VM storage policy is listed.
17. In the Navigator pane, expand production.vclass.local > Production > SRM Protected Services.
18. Right-click the appsvr01 application server virtual machine and select VM Policies > Edit VM
Storage Policies.
19. On the appsvr01: Manage VM Storage Policies page, select SPPG VM Storage Policy from
the VM storage policy drop-down menu.

20. Click Apply to all.
21. Click OK.
22. In the Navigator pane, click appsvr01.
24. Click the Policies tab.
25. Verify that the listed virtual machine objects match the VM Storage Policy SPPG VM storage
policy and the compliance status is listed as Compliant.

47
Task 5: (Optional) Create a Storage Policy Protection Group

You create an SPPG using the storage policy created in the previous task. You apply an SPPG to
virtual machines and delete the SPPG.
menu.
2. In the Navigator pane, click Protection Groups under Inventories.
3. Click the Objects tab.
4. On the Objects tab, click the Create Protection Group icon.
5. On the Create Protection Group page, enter Prod-SPPG in the Name text box.
7. Click Next.
8. On the Protection group type page, select production.vclass.local > recovery.vclass.local
under Direction of Protection.

9. Under Protection group type, select Storage policies (array-based replication).
10. Click Next.
11. On the Storage Policies page, select SPPG VM Storage Policy.
12. Click Next.
13. Click Finish.
NOTE
An SPPG is created with an amber warning symbol. The lab infrastructure does not use arraybased replication. So you cannot replicate the virtual machines from the production site to the
recovery site.
14. In the center pane, double-click the Prod-SPPG protection group.
16. Click the Storage Policies tab.
17. Validate that this storage policy is the same policy created in task 4.
48
19. Validate that appsvr01 is the same virtual machine to which you applied SPPG VM Storage
Policy to in task 4.
NOTE
A red issue icon is displayed on the virtual machine because protection is not configured for the
virtual machine. The lab infrastructure does not use array-based replication. So you cannot
replicate the virtual machines from the production site to the recovery site.
20. In the Navigator pane, right-click Prod-SPPG and select Delete Protection Group.
21. In the Delete Protection Group warning dialog box, click Yes.
22. Verify that the only protection group listed is the Protect database server protection group.
Task 6: Edit a Protection Group

You edit the protection group created in task 1 by adding two virtual machines. You also rename the
protection group.
menu.
3. In the Navigator pane, select the production.vclass.local production site.
4. Click the Related Objects tab

5. Click the Protection Groups tab.
6. Right-click the Protect database server protection group and select Edit Protection Group.
7. On the Name and location page of the Edit Protection Group wizard, enter Protect 3-tier
applications in the Name text box.

8. Click Next.
9. On the Protection group type page, click Next.
10. On the Virtual machines page, select the appsvr01 application server virtual machine and the
websvr01 Web server virtual machine.

11. Click Next.
12. On the Ready to complete page, click Next.
13. On the Apply changes page, wait for the operations to complete and click Finish.
14. Verify that the task completes and that your renamed protection group appears in the Protection
Groups panel.
49
17. Verify that the placeholder virtual machines for your application server and Web server exist.
50
Lab 7
Creating and Modifying a Recovery Plan

Objective: Create and modify a recovery plan to fail over
virtual machines in a protection group
2. Create a Recovery Plan
3. Configure Virtual Machine Recovery Properties
4. Create a Site Recovery Manager Alarm
Lab 7 Creating and Modifying a Recovery Plan
51

5. Use the vCenter Server system login user name and standard lab password to log in to the
Task 2: Create a Recovery Plan

You configure a recovery plan for a three-tier application.
Recovery test network
1. In vSphere Web Client, click the Home icon and select Site Recovery.
3. In the Navigator pane, select the production site production.vclass.local.
5. Under Guide to configuring SRM, select 6. Create a recovery plan.
You might need to scroll down to reveal the pane.

6. On the Name and location page of the Create Recovery Plan wizard, enter Recover 3-tier
applications in the Name text box.

8. Click Next.
9. On the Recovery site page, select recovery.vclass.local.
10. Click Next.
11. On the Protection groups page, select the Protect 3-tier applications check box.
12. Click Next.
13. On the Test networks page, double-click Auto on the rows for Internal, Prod-Net, and VM
Network Recovery Network and select Internal from each drop-down menu.
You must not change this value for the HBR-Net row.
52
14. Click Next.

17. On the Related Objects tab, click Recovery Plans.
18. Verify that the recovery plan appears on the Recovery Plans tab.
Task 3: Configure Virtual Machine Recovery Properties

You modify the default virtual machine recovery properties and place virtual machines in different
priority groups. You also assign a virtual machine dependency.
1. In the Recovery Plans panel, click the Recover 3-tier applications link.
The Summary tab of the recovery plan opens.

2. In the center pane, click the Related Objects tab.
4. Select the dbsvr01 database server in the list of virtual machines and click the Configure
Recovery icon.
5. In the VM Recovery Properties - dbsvr01 dialog box, select 1 (will be started first) from the
Priority Group drop-down menu.

6. Click OK.
7. Select your appsvr01 application server in the list of virtual machines and click the Change the
VM Recovery Settings icon.

8. In the VM Recovery Properties - appsvr01 dialog box, select 2 from the Priority Group drop-
down menu.
9. Click OK.
10. Select your websvr01 Web server in the list of virtual machines and click the Change the VM
Recovery Settings icon.

53
11. In the VM Recovery Properties - websvr01 dialog box, select 2 from the Priority Group drop-
down menu.
12. In the VM Recovery Properties - websvr01 dialog box, expand VM Dependencies.
13. In the VM Dependencies pane, click Configure.
14. In the Configure VM Dependencies - websvr01 dialog box, select the appsvr01 check box and
click OK.
15. In the VM Recovery Properties - websvr01 dialog box, click OK.
16. On the Virtual Machines tab of the recovery plan, verify that the priorities and dependencies
are set properly.

a. Verify that dbsvr01 has priority 1.
b. Verify that appsvr01 has priority 2.
c. Verify that websvr01 has priority 2.
d. Verify that websvr01 has appsvr01 set as dependency.
You might need to scroll right to see the dependencies. You can drag and rearrange the columns
to view more information.
Task 4: Create a Site Recovery Manager Alarm

You create a VMware Site Recovery Manager alarm definition. The alarm sends an email
notification when a recovery plan test begins.
Email address for alarm
1. Click the Home icon and select vCenter Inventory Lists from the drop-down menu.
2. In the Navigator pane, select vCenter Servers.
3. In the Navigator pane, click the production.vclass.local vCenter Server.
54
5. Click the Alarm Definitions tab.

6. In the Alarm Definitions pane, click the + sign to add a definition.
7. On the General page of the New Alarm Definition wizard, enter Recovery Plan test in
the Alarm Name text box.

8. In the Description text box, enter This alarm triggers and sends email when
SRM testing is in progress.

9. In the Monitor drop-down menu, select vCenter Server.
10. Click Next.
11. On the Triggers page, click the + sign under Trigger if ANY of the following events occur.
12. Click Added license and enter Recovery to see the options.
13. Select the Recovery Plan Execute Test Begin (production.vclass.local) alarm definition from
the drop-down menu.

NOTE
The alarms that appear accompanied by production.vclass.local indicate alarms that are related
to Site Recovery Manager for the production.vclass.local server.
14. Click Next.
15. On the Actions page, click the + sign.
16. Under the Actions column, select Send notification email.
17. Under Configuration, enter the email address for the alarm.
18. Click Finish.
55
56
Lab 8
(Optional) Using the dr-ip-customizer

Program
Objective: Use dr-ip-customizer to modify network
settings
2. Generate a .csv File and Add Network Settings
3. Apply the .csv File
This optional lab takes approximately 1 hour to complete. You can perform this lab only if you have
extra time.
Lab 8 (Optional) Using the dr-ip-customizer Program
57

system.

vSphere Web Client.
Task 2: Generate a .csv File and Add Network Settings

You use the dr-ip-customizer program to generate a .csv file containing recovery options settings.
You modify the .csv file and add the protected site and the recovery site IP addresses of your
application server, database server, and Web server.
1. In vSphere Web Client, click the Home icon and select VM and Templates from the drop-
down menu.
2. In the Navigator pane, expand production.vclass.local > Production > SRM Protected
Services
3. Select the appsvr01 application server.
4. In the center pane, click the Summary tab.
5. Record the IP address of appsvr01. __________
6. In the Navigator pane, select the dbsvr01 database server.
7. Record the IP address of dbsvr01. __________
8. Select the websvr01 Web server.
9. Record the IP address of websvr01. __________
10. From your vCenter Server system desktop, click the Windows Command Prompt window in the
taskbar.
11. At the command prompt, enter F:.
58
12. At the command prompt, enter cd "\Program Files\VMware\VMware vCenter Site
Recovery Manager\bin" on a single line.

13. To generate a .csv file, enter dr-ip-customizer.exe --cfg "F:\Program
Files\VMware\VMware vCenter Site Recovery Manager\config\vmwaredr.xml" --cmd generate --out C:\srm.csv --uri https://
172.20.10.91:443/lookupservice/sdk on a single line.
14. When the program asks Do you trust this server (Y/N), enter y.
15. When prompted to enter the user name and password, enter your vCenter Server system login
user name and the standard lab password.

17. Click the Windows File Explorer icon in the taskbar.
18. Double-click the Local Disk C icon.
19. Find the srm.csv file that you created in step 15.
20. Right-click the srm.csv file and select Open with.
21. In the How do you want to open this type of file (.csv)? window, select NotePad.
srm.csv opens in Notepad.
22. Find the two lines in the file that refer to dbsvr01.
23. Copy the two lines and paste them under the existing dbsvr01 entries.
59
24. Change the fourth field on the two added lines from 0 to 1.
In this type of file, the spaces between the commas are fields.
25. Modify the first added line.

a. In the ninth field, enter the dbsvr01 IP address at the protected site that you recorded.
b. In the tenth field, enter the subnet mask 255.255.255.0.
The 1 and the IP address should have five commas between them. The subnet mask should
be followed by six commas. You must not add or remove commas.
26. Modify the second added line.
a. Copy the dbsvr01 IP address at the protected site that you recorded.
b. Change the last three numbers in the IP address to 212.
You only modify the last octet (the last three numbers) in the IP address because the lab
network infrastructure is flat. For example, if the existing IP address for dbsvr01 is
172.20.11.201, change it to 172.20.11.212.
c. In the ninth field, enter the changed dbsvr01 IP address.
d. In the tenth field, enter the subnet mask 255.255.255.0.
27. Find the two lines in the file that refer to appsvr01.
28. Copy the two lines and paste them below the existing appsvr01 entry.
60
a. In the ninth field, enter the appsvr01 IP address at the protected site that you recorded.
a. Copy the appsvr01 IP address at the protected site that you recorded.
c. In the ninth field, enter the changed appsvr01 IP address.
32. Find the two lines in the file that refer to websvr01.
33. Copy the two lines and paste them below the existing websvr01 entry.
a. In the ninth field, enter the websvr01 IP address at the protected site that you recorded.

a. Copy the websvr01 IP address at the protected site that you recorded.
c. In the ninth field, enter the changed websvr01 IP address.
61
The image shows an example of the file after all changes are made.
The three virtual machines might not be listed in the same order in your file.
37. In Notepad, select File > Save.
38. Close Notepad.
Task 3: Apply the .csv File

You apply the .csv file that configures the IP information for recovery of the application server,
database server, and Web server.
1. Return to the Command Prompt window.
2. To upload the modified srm.csv file, enter dr-ip-customizer.exe --cfg
"F:\Program Files\VMware\VMware vCenter Site Recovery

Manager\config\vmware-dr.xml" --cmd apply --csv C:\srm.csv --uri
https://172.20.10.91:443/lookupservice/sdk on a single line.
4. When prompted to enter the user name and password, enter your vCenter Server login user
name and standard lab password.

6. To verify that the IP address information was configured, return to vSphere Web Client.
7. Click the Home icon and select Site Recovery from the drop-down menu.
8. Under Inventories in the Navigator pane, select Recovery Plans.
62
9. Select Recover 3-tier applications in the Recovery Plans list.

10. In the center pane, click the Related Objects tab
12. Select dbsvr01.
13. Click the Change the VM Recovery Settings icon.
14. In the VM Recovery Properties dialog box, click the IP Customization tab.
15. Click IP Settings - NIC 1.
16. Verify the IP settings for dbsvr01.
17. Click Cancel.
18. Select appsvr01.
22. Verify the IP settings for appsvr01.
23. Click Cancel.
24. Select websvr01.
28. Verify the IP settings for websvr01.
29. Click Cancel.
30. If the IP address settings are incorrect, edit and save the srm.csv file to include the correct
values and reapply the file.

31. Close the Command Prompt window.
63
64
Lab 9
Testing and Executing a Recovery Plan

Objective: Test and execute a recovery plan
2. Test a Recovery Plan
3. Clean Up the Recovery Plan Test
4. Perform a Planned Migration

system.
Lab 9 Testing and Executing a Recovery Plan
65
and the standard lab password

vSphere Web Client.
Task 2: Test a Recovery Plan

You test the recovery plan that you created and modified.
Your vCenter Server system FQDN
vCenter Server system user name
Recovery test network
menu.
2. In the Navigator pane, select Recovery Plans under Inventories.
3. In the Navigator pane, select Recover 3-tier applications in the Recovery Plans list.
4. At the top of the center pane, select Actions > Test.
The Test - Recover 3-tier applications wizard appears.

5. On the Confirmation Options page, click Next.
6. On the Ready to complete page, review the settings and click Finish.
7. Click the Monitor tab and monitor the steps in your recovery plan.
66
8. Expand the steps so that all substeps appear, such as the substeps to power on the virtual
machines.
The recovery test takes several minutes to complete.
9. Verify that your database server starts first as part of the priority group 1.
10. Verify that your application server starts before the Web server as part of the priority group 2.
11. After the test is complete, click the History tab.
12. Select the test operation and click the Export report for selected history item icon.
The Export History Report dialog box appears.

13. Select Web Page (*.html).
14. Click Generate Report.
15. Click Download Report and save the report to your desktop.
16. Click Close.
17. Go to your desktop.
18. Double-click the downloaded report file to open it.
19. Scroll through the report to view its contents.
20. Verify that the status of each recovery step is shown as Success in the Results column.
21. Close the browser window.
22. Return to vSphere Web Client.
23. Click the Home icon and select Hosts and Clusters from the drop-down menu.
24. In the Navigator pane, expand production.vclass.local > Production > Protected Services >
Protected Application Servers.

25. Select your appsvr01 application server.
26. Click the Related Objects tab in the center pane.

27. Click the Datastores tab.
28. Record the datastore on which this virtual machine is located. __________
29. Click the Networks tab.
67
30. Record the network to which this virtual machine is connected. __________
31. In the Navigator pane, expand recovery.vclass.local > Recovery > esxirec.vclass.local >
Recovered Services > Recovered Database Servers.

32. Select dbsvr01.
35. Record the datastore on which the database server virtual machine is located. __________
37. Record the network to which the application server virtual machine is connected. __________
Protected Web Servers.

39. Select your websvr01 Web server.
Recovered Services > Recovered Web Servers.

46. Select websvr01.
49. Record the datastore on which the application server virtual machine is located. __________
Protected Database Servers.

53. Select your database server dbsvr01.
68
Recovered Services > Recovered Application Servers.

60. Select appsrv01.
63. Record the datastore on which the application server virtual machine is located. __________
Your virtual machines at the recovery site should be on the storage designated for recovery.
Your virtual machines should be connected to the recovery test network.
Task 3: Clean Up the Recovery Plan Test

You clean up the recovery plan test.
menu.
3. Right-click the Recover 3-tier applications recovery plan and select Cleanup.
The Cleanup - Recovery 3-tier applications wizard appears.

5. On the Ready to complete page, review the settings and click Finish.
6. In the Navigator pane, click the Recover 3-tier applications recovery plan.
8. Click the Recovery Steps tab.
69
9. From the View drop-down menu, select Cleanup Steps.
10. After the cleanup is complete, click the History tab.

11. Select the cleanup operation and click the Export report for selected history item icon.
12. In the Export History Report dialog box, select Web Page (*.html).
15. In the Confirm Save As dialog box, click Yes to replace the existing file.
16. In the Export History Report pane, click Close.
20. Record the timestamp of the Power off Recovery Step for each virtual machine. __________
All the timestamps should be the same.
21. Close the browser tab

23. Click the Home icon and select Hosts and Clusters from the drop-down menu.
70
Recovered Services > Recovered Application Servers.

25. Under the Recovered Application Servers resource pool, select the application server appsvr01
placeholder virtual machine.

This virtual machine is now a placeholder virtual machine.
27. Click Datastores.
28. Verify that the appsvr01 placeholder virtual machine is on the RecoveryPlaceholder datastore.
29. Click Networks.
The virtual machine is not connected to a network.

30. Under the Recovered Database Servers resource pool, select the dbsvr01 database server
placeholder virtual machine.

33. Verify that the dbsvr01 placeholder virtual machine is on the RecoveryPlaceholder datastore.
34. Click Networks.

35. Under the Recovered Web Servers resource pool, select the websvr01 Web server placeholder
virtual machine.
38. Verify that the websvr01 placeholder virtual machine is on the RecoveryPlaceholder datastore.
39. Click Networks.
71
Your application server, database server, and Web server virtual machines are reverted back to
placeholder virtual machines.
Task 4: Perform a Planned Migration

You perform a planned migration.
menu.
3. Right-click the Recover 3-tier applications recovery plan and select Run.
The Recovery wizard appears.

4. On the Confirmation Options page, click I understand that this process will permanently
alter the virtual machines and infrastructure of both the protected and recovery
datacenters.
5. Leave Planned migration selected and click Next.
7. Click the Recover 3-Tier applications plan.
The planned migration process takes several minutes to complete.

10. Expand the recovery steps so that all substeps are displayed.
11. Verify that the virtual machines at the production site (the protected site) are shut down, starting
with the lower priority virtual machines.

12. Verify that your database server powers on first.
13. Verify that your application server starts before your Web server.
14. After the migration is complete, click the History tab.
15. Select the Recovery operation from the list
16. Click the Export report for selected history item icon.
72
17. In the Export History Report dialog box, select Web Page (*.html).
20. In the Confirm Save As dialog box, click Yes to replace the existing file.
21. In the Export History Report pane, click Close.
22. Click Close.
26. Record the shutdown order of each of the virtual machines __________.
27. Close the browser window.

Services.
31. Verify that your application server, database server, and Web server virtual machines at the
production site (the protected site) are powered off.

32. Right-click a virtual machine and select Power.
You do not have the option to power on this virtual machine.

73
34. Verify that your application server, database server, and Web server virtual machines are
powered on.
35. Click the appsvr01 virtual machine.
38. Verify that the appsvr01 virtual machine is using the datastore specified in your recovery plan.
40. Verify that the appsvr01 virtual machine is connected to the production network.
41. Click the dbsvr01 virtual machine.
44. Verify that the dbsvr01 virtual machine is using the datastore specified in your recovery plan.
46. Verify that the dbsvr01 virtual machine is connected to the production network.
47. Click the websvr01 virtual machine.
50. Verify that the websvr01 virtual machine is using the datastore specified in your recovery plan.
52. Verify that the websvr01 virtual machine is connected to the production network.
74
Reprotecting and Failing Back

Objective: Use vSphere Replication to perform a
reprotect and a failback
2. Perform a Reprotect
3. Fail Back to the Original Protected Site
Lab 10
Lab 10 Reprotecting and Failing Back
10
system.
75

vSphere Web Client.
Task 2: Perform a Reprotect

The reprotect operation protects your recovery site, which is where your virtual machines are
running. Your virtual machines are running at the recovery site as a result of the planned migration
that you performed in the previous lab.
menu.
3. Right-click your recovery plan and select Reprotect.
The Reprotect wizard appears.

4. On the Confirmation Options page, select the I understand that this operation cannot be
undone check box.

5. Click Next.
7. In the Navigator pane, select the Recover 3-tier applications recovery plan.
9. Click the Recovery Steps tab to monitor the reprotect operation.
10. Expand the recovery steps so that the substeps appear.
11. When the Reprotect process is completed, click the Summary tab.
12. Record the site that is the protected site. __________
13. Record the site that is the recovery site. __________
Services.
76
identified as placeholder virtual machines.

You might need to refresh the screen to see the placeholder virtual machines.
powered on.
19. Select the appsvr01 application server.
22. Verify that appsvr01 is on the storage designated for recovery.
24. Verify that the virtual machines are connected to the production network.
25. Select the dbsvr01 database server.
28. Verify that dbsvr01 is on the storage designated for recovery.
31. Select the websvr01 Web server.
34. Verify that websvr01 is on the storage designated for recovery.
10
77
Task 3: Fail Back to the Original Protected Site

You fail back to the original protected site. The failback process consists of performing a recovery
plan test, a cleanup, a planned migration, and a reprotect.
menu.
3. Right-click the Recover 3-tier applications recovery plan in the Recovery Plans list and select
Test.
The Test wizard appears.
6. On the right side of vSphere Web Client, monitor the Alarms pane and verify that the alarm you
created in lab 7 is triggered.

You might need to refresh the screen to see the triggered alarm.
10. After the test completes successfully, click the Cleanup recovery plan (broom) icon.
The Cleanup wizard appears.

13. Click the History tab to verify that the test has completed.
78
15. Click the Run Recovery Plan icon (the triangle in a red circle) to start the recovery process.
The Recovery wizard appears.

This recovery process is for failing back to the original production site.
16. On the Confirmation Options page, select the I understand that this process will
permanently alter the virtual machines and infrastructure of both the protected and
recovery datacenters check box.
17. Click Next.
21. Monitor the process of the recovery.
22. After the recovery completes, click the Summary tab.
23. Record the site that is the protected site. __________
24. Record the site that is the recovery site. __________
Services.
protected site are powered on.

28. Select your appsvr01 application server and click the Related Objects tab.
29. Click the Datastores button.
31. Click the Networks button
32. Record the network on which this virtual machine is connected. __________
33. Select your dbsvr01 database server and click the Related Objects tab.
10
79

38. Select your websvr01 Web server and click the Related Objects tab.
Your virtual machines should be on their original datastore. Your virtual machines should be
connected to the Production network.
recovery site (the protected site) are powered off.

45. Right-click one of these virtual machines and select Power.
You cannot power on this virtual machine.

46. Click the Home icon and select Site Recovery from the drop-down list.
48. Right-click the Recover 3-tier applications recovery plan in the Recovery Plans list and select
Reprotect.
The Reprotect wizard appears.

49. On the Confirmation Options page, select I understand that this operation cannot be undone
check box and click Next.

80
54. After the reprotect operation completes successfully, click the Summary tab.
The production site is now the protected site and recovery site is the recovery site.
You might need to click the refresh button in vSphere Web Client to see the updated
information.
56. In the Navigator pane, expand Production.vclass.local > Production > SRM Protected
Services.
The application server, database server, and Web server are powered on at the protected site.
The application server, database server, and Web server are placeholder virtual machines at the
recovery site.
You might need to click the refresh button in vSphere Web Client to see the correct placeholder
virtual machine icons.
10
81
82

SRMICM61

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SRMICM61

Transféré par

Droits d'auteur :

Formats disponibles

VMware Site Recovery Manager:

Install, Configure, Manage

VMware Education Services

VMware Site Recovery Manager: Install, Configure, Manage

Lab 1: Installing the Production Site Recovery Manager Components . . . . . . . . . . . . . . . . . . . . . . . 1

VMware Site Recovery Manager: Install, Configure, Manage

VMware Site Recovery Manager: Install, Configure, Manage

Installing the Production Site Recovery

Lab 1 Installing the Production Site Recovery Manager Components

Task 1: Access Your Lab Server System

vCenter Server system.

Enter service-control --start vpxd to start the vpxd service.

Lab 1 Installing the Production Site Recovery Manager Components

Task 3: Verify the Production vCenter Server Inventory

The VMware vSphere Web Client window appears.

standard lab password.

The following objects must exist in the inventory:

Lab 1 Installing the Production Site Recovery Manager Components

7. Verify that appsvr01, dbsvr01, and websvr01 are powered off.

Task 4: Configure a Virtual Machine Port Group

Lab 1 Installing the Production Site Recovery Manager Components

3. In the center pane, click the Manage tab.

4. Click the Networking tab.

switch for your production network.

update the information.

Task 5: Install the Site Recovery Manager Software on the Production

vCenter Server system login user name

qualified domain name (FQDN) in the Address text box.

drop-down menu matches the Production vCenter Server system FQDN.

FQDN in the Local Site Name text box.

Lab 1 Installing the Production Site Recovery Manager Components

Plug-in identifier is selected.

Data Source Name

Enter production in the text box.

Database User Name

Enter administrator in the text box.

Enter vmware in the text box.

account check box is selected and click Next.

Lab 1 Installing the Production Site Recovery Manager Components

The vSphere Web Client Internet Explorer window opens.

vSphere Web Client.

Lab 1 Installing the Production Site Recovery Manager Components

Task 7: Pair the Production Site with the Recovery Site

2. In the Navigator pane, click Sites.

system FQDN in the PSC address text box.

standard lab password.

Lab 1 Installing the Production Site Recovery Manager Components

9. In the Security Alert warnings dialog box, click Yes to connect.

4. In the Navigator pane, select recovery.vclass.local.

Lab 1 Installing the Production Site Recovery Manager Components

Configuring Inventory Mappings

Task 1: Access Your Lab Server System

and the standard lab password.

VMware vSphere Web Client.

Task 2: Configure Resource Mappings on the Production Site

Lab 2 Configuring Inventory Mappings

resource pool check box.

18. Click Add mappings.

pool check box.

Task 3: Configure Folder Mappings on the Production Site

5. Expand the production site.

Task 4: Configure Network Mappings

Lab 2 Configuring Inventory Mappings

10. On the production site, select the HBR-Net port group.