Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
www.vmware.com/education
TA B L E
OF
C ONTENTS
iii
iv
Lab 1
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.
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
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.
services is RUNNING.
8. Close the Command Prompt window.
drop-down menu.
2. Select esxiprod.vclass.local in the inventory.
4
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
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.
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
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
Option
Action
Database Password
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
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.
Use the following information from the class configuration handout:
Production vCenter Server system FQDN
vCenter Server system login user name
Standard lab password
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.
13. Leave the browser window open for the next task.
8
menu.
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
You must click Yes twice for each prompt to accept the certificates.
10. Leave the browser window open for the next task.
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.
10
Lab 2
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
menu.
2. In the Navigator pane, click Sites.
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.
15. Click Add mappings.
12
16. Under Protected Services on the production site, select the Protected Database Servers
resource pool.
pool.
21. Click Add mappings.
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
3. In the Create Folder Mapping dialog box, click Prepare mappings manually.
4. Click Next.
Lab 2 Configuring Inventory Mappings
13
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.
9. Click Add mappings.
14
15
16
Lab 3
3
Configuring Datastores
Objective: Configure inventory mappings between the
protected site and the recovery site in Site Recovery
Manager
In this lab, you will perform the following tasks:
1. Access Your Lab Server System
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
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.
3. Log in to your Production vCenter Server system with your student desktop login user name
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.
10. On the Ready to complete page, click Finish.
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
menu.
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
Datastore.
4. On the Location page of the New Datastore wizard, click Next.
Lab 3 Configuring Datastores
19
5. On the Type page, select the VMFS storage type and click Next.
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.
9. On the Partition configuration page, click Next.
10. On the Ready to complete page, click Finish.
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
menu.
14. In the Navigator pane, select Sites.
15. In the Navigator pane, select production.vclass.local.
16. Click the Summary tab.
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
You might need to refresh the Web page by clicking the refresh icon at the top of vSphere Web
Client.
20
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.
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 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.
9. On the Partition configuration page, click Next.
10. On the Ready to complete page, click Finish.
11. Verify that the new datastore appears in the inventory.
You might need to refresh the Web page by clicking the refresh icon at the top of vSphere Web
Client.
12. In the Navigator pane, right-click the recovery data center and select Storage > New Datastore.
13. On the Location page of the New Datastore wizard, click Next.
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.
18. On the Partition configuration page, click Next.
19. On the Ready to complete page, click Finish.
Lab 3 Configuring Datastores
21
You might need to refresh the Web page by clicking the refresh icon at the top of vSphere Web
Client.
21. Leave vSphere Web Client open for the next lab.
22
Lab 4
Except for pairing VMware vSphere Replication management appliances, all other steps in this
lab are already performed on the recovery site.
23
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.
3. Log in to your Production vCenter Server system with your student desktop login user name
8. Click OK.
9. Leave vSphere Web Client open for the next task.
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.
Lab 4 Deploying and Configuring vSphere Replication
25
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
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
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.
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.
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.
24. If the status does not appear as Enabled (OK), consult your instructor.
28
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
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
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
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.
30. Click the Monitor tab.
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.
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.
3. On the Home tab of the vSphere Replication window, click Manage.
4. Click the vSphere Replication tab.
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.
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.
33
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.
17. Click the Summary tab.
18. Under vSphere Replication on the Summary tab, verify that Target sites shows that one site is
connected.
34
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.
21. Leave vSphere Web Client open for the next lab.
35
36
Lab 5
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 5 Configuring vSphere Replication for Virtual Machines
37
3. Log in to your Production vCenter Server system with your student desktop login user name
down menu.
2. In the Navigator pane, expand production.vclass.local > Production > esxiprod.vclass.local >
minutes.
13. Click Next.
14. On the Ready to complete page, click Finish.
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
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.
21. Click the Home icon and select vSphere Replication from the drop-down menu.
22. In the center pane, select production.vclass.local.
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.
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.
39
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
minutes.
24. Click Next.
25. On the Ready to complete page, click Finish.
26. Click the Monitor tab.
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.
If the yellow highlighted Answer a question message appears, select I copied it.
32. Verify that appsvr01 is powered on.
40
33. In the Navigator pane, right-click websvr01 and select Power > Power On.
If the yellow highlighted Answer a question message appears, select I copied it.
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.
36. Click the Home icon and select vSphere Replication from the drop-down menu.
37. In the center pane, select production.vclass.local.
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.
41
42
Lab 6
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
43
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.
3. Log in to your Production vCenter Server system with your student desktop login user name
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.
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.
18. Click the Related Objects tab.
19. Click the Virtual Machines tab.
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.
24. Click the Summary tab.
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.
26. Leave vSphere Web Client open for the next task.
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.
Storage Policies.
19. On the appsvr01: Manage VM Storage Policies page, select SPPG VM Storage Policy from
47
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.
6. In the Location list, select recovery.vclass.local - production.vclass.local.
7. Click Next.
8. On the Protection group type page, select production.vclass.local > recovery.vclass.local
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.
15. Click the Related Objects tab.
16. Click the Storage Policies tab.
17. Validate that this storage policy is the same policy created in task 4.
18. Click the Virtual Machines tab.
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.
23. Leave vSphere Web Client open for the next task.
menu.
2. In the Navigator pane, click Sites.
3. In the Navigator pane, select the production.vclass.local production site.
Groups panel.
Lab 6 Building a Protection Group
49
15. Click the Home icon and select VMs and Templates from the drop-down menu.
16. In the Navigator pane, expand recovery.vclass.local > Recovery > SRM Recovered Services.
17. Verify that the placeholder virtual machines for your application server and Web server exist.
18. Leave vSphere Web Client open for the next lab.
50
Lab 7
You log in to your VMware 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
vCenter Server system login user name
Standard lab password
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 7 Creating and Modifying a Recovery Plan
51
3. Log in to your Production vCenter Server system with your student desktop login user name
Network Recovery Network and select Internal from each drop-down menu.
You must not change this value for the HBR-Net row.
52
Recovery icon.
5. In the VM Recovery Properties - dbsvr01 dialog box, select 1 (will be started first) from the
down menu.
9. Click OK.
10. Select your websvr01 Web server in the list of virtual machines and click the Change the VM
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
You might need to scroll right to see the dependencies. You can drag and rearrange the columns
to view more information.
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.
19. Leave vSphere Web Client open for the next lab.
55
56
Lab 8
This optional lab takes approximately 1 hour to complete. You can perform this lab only if you have
extra time.
You log in to your VMware 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
vCenter Server system login user name
Standard lab password
57
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.
3. Log in to your Production vCenter Server system with your student desktop login user name
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
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
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.
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
29. Change the fourth field on the two added lines from 0 to 1.
30. Modify the first added line.
a. In the ninth field, enter the appsvr01 IP address at the protected site that you recorded.
b. In the tenth field, enter the subnet mask 255.255.255.0.
31. Modify the second added line.
a. Copy the appsvr01 IP address at the protected site that you recorded.
b. Change the last three numbers in the IP address to 211.
c. In the ninth field, enter the changed appsvr01 IP address.
d. In the tenth field, enter the subnet mask 255.255.255.0.
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.
34. Change the fourth field on the two added lines from 0 to 1.
35. Modify the first added line.
a. In the ninth field, enter the websvr01 IP address at the protected site that you recorded.
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.
63
64
Lab 9
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 9 Testing and Executing a Recovery Plan
65
3. Log in to your Production vCenter Server system with your student desktop login user name
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.
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.
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 >
68
56. Record the datastore on which this virtual machine is located. __________
57. Click the Networks tab.
58. Record the network to which this virtual machine is connected. __________
59. In the Navigator pane, expand recovery.vclass.local > Recovery > esxirec.vclass.local >
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.
menu.
2. In the Navigator pane, select Recovery Plans under Inventories.
3. Right-click the Recover 3-tier applications recovery plan and select Cleanup.
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.
7. Click the Monitor tab.
8. Click the Recovery Steps tab.
Lab 9 Testing and Executing a Recovery Plan
69
24. In the Navigator pane, expand recovery.vclass.local > Recovery > esxirec.vclass.local >
virtual machine.
This virtual machine is now a placeholder virtual machine.
36. Click the Related Objects tab.
37. Click Datastores.
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.
menu.
2. In the Navigator pane, select Recovery Plans under Inventories.
3. Right-click the Recover 3-tier applications recovery plan and select Run.
alter the virtual machines and infrastructure of both the protected and recovery
datacenters.
5. Leave Planned migration selected and click Next.
6. On the Ready to complete page, click Finish.
7. Click the Recover 3-Tier applications plan.
8. Click the Monitor tab.
72
17. In the Export History Report dialog box, select Web Page (*.html).
18. Click Generate Report.
19. Click Download Report and save the report to your desktop.
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.
23. Go to your desktop.
24. Double-click the downloaded report file to open it.
25. Scroll through the report to view its contents.
26. Record the shutdown order of each of the virtual machines __________.
Services.
31. Verify that your application server, database server, and Web server virtual machines at the
73
33. In the Navigator pane, expand recovery.vclass.local > Recovery > SRM Recovered Services.
34. Verify that your application server, database server, and Web server virtual machines are
powered on.
35. Click the appsvr01 virtual machine.
36. Click the Related Objects tab.
37. Click the Datastores tab.
38. Verify that the appsvr01 virtual machine is using the datastore specified in your recovery plan.
39. Click the Networks tab.
40. Verify that the appsvr01 virtual machine is connected to the production network.
41. Click the dbsvr01 virtual machine.
42. Click the Related Objects tab.
43. Click the Datastores tab.
44. Verify that the dbsvr01 virtual machine is using the datastore specified in your recovery plan.
45. Click the Networks tab.
46. Verify that the dbsvr01 virtual machine is connected to the production network.
47. Click the websvr01 virtual machine.
48. Click the Related Objects tab.
49. Click the Datastores tab.
50. Verify that the websvr01 virtual machine is using the datastore specified in your recovery plan.
51. Click the Networks tab.
52. Verify that the websvr01 virtual machine is connected to the production network.
53. Leave vSphere Web Client open for the next lab.
74
Lab 10
You log in to your VMware 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
vCenter Server system login user name
Standard lab password
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.
10
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.
75
3. Log in to your Production vCenter Server system with your student desktop login user name
menu.
2. In the Navigator pane, select Recovery Plans under Inventories.
3. Right-click your recovery plan and select Reprotect.
Services.
76
16. Verify that your application server, database server, and Web server virtual machines are
17. In the Navigator pane, expand recovery.vclass.local > Recovery > SRM Recovered Services.
18. Verify that your application server, database server, and Web server virtual machines are
powered on.
19. Select the appsvr01 application server.
20. Click the Related Objects tab.
21. Click the Datastores tab.
22. Verify that appsvr01 is on the storage designated for recovery.
23. Click the Networks tab.
24. Verify that the virtual machines are connected to the production network.
25. Select the dbsvr01 database server.
26. Click the Related Objects tab.
27. Click the Datastores tab.
28. Verify that dbsvr01 is on the storage designated for recovery.
29. Click the Networks tab.
30. Verify that the virtual machines are connected to the production network.
31. Select the websvr01 Web server.
32. Click the Related Objects tab.
33. Click the Datastores tab.
34. Verify that websvr01 is on the storage designated for recovery.
35. Click the Networks tab.
10
36. Verify that the virtual machines are connected to the production network.
77
menu.
2. In the Navigator pane, select Recovery Plans under Inventories.
3. Right-click the Recover 3-tier applications recovery plan in the Recovery Plans list and select
Test.
The Test wizard appears.
4. On the Confirmation Options page, click Next.
5. On the Ready to complete page, click Finish.
6. On the right side of vSphere Web Client, monitor the Alarms pane and verify that the alarm you
78
15. Click the Run Recovery Plan icon (the triangle in a red circle) to start the recovery process.
permanently alter the virtual machines and infrastructure of both the protected and
recovery datacenters check box.
17. Click Next.
18. On the Ready to complete page, click Finish.
19. Click the Monitor tab.
20. Click the Recovery Steps tab.
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. __________
25. Click the Home icon and select VMs and Templates.
26. In the Navigator pane, expand production.vclass.local > Production > SRM Protected
Services.
27. Verify that your application server, database server, and Web server virtual machines at the
10
35. Record the datastore on which this virtual machine is located. __________
79
Your virtual machines should be on their original datastore. Your virtual machines should be
connected to the Production network.
43. In the Navigator pane, expand recovery.vclass.local > Recovery > SRM Recovered Services.
44. Verify that your application server, database server, and Web server virtual machines at the
Reprotect.
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.
55. Click the Home icon and select VMs and Templates.
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.
57. In the Navigator pane, expand recovery.vclass.local > Recovery > SRM Recovered Services.
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