Table of Contents - VMwareThis lab features VMware® vCloud® Suite 5.5 products from the vCloud Suite 2013 release. The focus of this lab is to work with VMware vCenter , VMware vCenter

Table of ContentsLab Overview .................................................................................................................... 2

About This Lab ........................................................................................................ 3Module 1 - Introduction to VMware vCenter Site Recovery Manager ................................5

Application Discovery and Dependencies .............................................................. 6Verify Capacity Availability .................................................................................... 15Getting Ready for Protection and Recovery ......................................................... 30

Module 2 - Using vCenter Site Recovery Manager .......................................................... 44Application Protection .......................................................................................... 45Application Recovery Test Plan.............................................................................. 54Test and Clean Up App Recovery........................................................................... 68

Module 3 - Disaster Strikes ............................................................................................. 74Disaster Strikes! Recovery from a Failed Site ....................................................... 75

Module 4 - Disaster Passed. Recover to Site A - OPTIONAL.............................................88Disaster Passed! Reprotection and Planned Migration ..........................................89

Module 5 - Troubleshooting ........................................................................................... 103Troubleshooting vCenter Infrastructure Navigator .............................................. 104Troubleshooting vCenter Site Recovery Manager................................................ 107

HOL-SDC-1318

Page 1HOL-SDC-1318

Lab Overview

HOL-SDC-1318

Page 2HOL-SDC-1318

About This LabThis lab features VMware® vCloud® Suite 5.5 products from the vCloud Suite 2013release. The focus of this lab is to work with VMware vCenter™, VMware vCenter SiteRecovery Manager™ and VMware vSphere® Replication products, enhanced by VMwarevCenter Infrastructure Navigator™ and VMware vCenter Operations Manager™.

This entire lab takes approximately 2 to 3 hours to complete. Some of this time might bespent waiting for processes to complete in the lab. Some of the modules are designatedas optional. Attempt these only if you have sufficient time available.

The lab environment consists of two distinct data center mock-ups called sites. Thesesites are used to establish a disaster recovery and a disaster avoidance scenario.

Note:

To facilitate different keyboard mappings between the US and other countries, a"Keyboard help" file is included on the desktop of the Control Center. This text filecontains all the text that is required to be entered during this lab. You can copy andpaste this text into the user and password fields mentioned in this lab.

The screen resolution for this Lab has been set in such a way as to cater to the widestrange of BYOD devices possible. A larger screen or monitor is ideal to avoid a cluttereddesktop view. Should you wish to alter the screen resolution on the Control Centerdesktop,1280x768 has been tested as a good alternative to the default setting.

Module 1 - Introduction to vCenter Site Recovery Manager (45 minutes)

• Discover application dependencies with the help of vCenter InfrastructureNavigator.

• Verify that you have sufficient capacity at the recovery site for your protectedvirtual machines with vCenter Operations Manager.

• Enable vSphere Replication (host-based) for virtual machines that will beprotected.

Module 2 - Using vCenter Site Recovery Manager (25 minutes)

• Establish a protection group for an application.• Establish a recovery plan that includes a protection plan.• Test and clean up the recovery plan.

Module 3 - Disaster Strikes (20 minutes)

• Perform a disaster recovery of My Important App.

Module 4 - Re-protect and Fail-back (OPTIONAL - 45 minutes)

HOL-SDC-1318

Page 3HOL-SDC-1318

• Re-protect My Important App from the recovery site to your protected site.• Perform a planned migration of the My Important App back to the original

protected site.• Confirm that the protected site is once again protected.

Module 5 - Troubleshooting

• vCenter Infrastructure Navigator.• vCenter Site Recovery Manager.

Lab Captain: Paul Irwin

HOL-SDC-1318

Page 4HOL-SDC-1318

Module 1 - Introduction toVMware vCenter SiteRecovery Manager

HOL-SDC-1318

Page 5HOL-SDC-1318

Application Discovery andDependenciesA two-tier application runs on the primary site that must be protected using vCenter SiteRecovery Manager. You can discover the relationship between virtual machines usingvCenter Infrastructure Navigator, part of the vSphere platform.

HOL-SDC-1318

Page 6HOL-SDC-1318

Log In to vSphere Using the VMware vSphere Client

You will use both the VMware vSphere Web Client and the classic VMware vSphere Clientduring the course of this lab. Navigate to and launch the vSphere Client by clicking theVMware vSphere Client icon on the desktop.

To connect to the primary site, referred to as the A Site, use the address vc-w12-01a.corp.local. Select Use Windows session credential and click Login.

Repeat this process to connect to the VMware vCenter Server™ at Site B with theaddress vc-w12-01b.corp.local. Minimize both vSphere Client instances.

Log In to vSphere Using the VMware vSphere Web Client

For best results, use the Google Chrome Web browser. Other browsers might work, butChrome provides the most consistent results.

1. Open Google Chrome from the desktop shortcut.

HOL-SDC-1318

Page 7HOL-SDC-1318

2. Select Site-A vSphere Web Client from the toolbar to launch the vSphere WebClient for Site A.

3. Click Proceed if prompted by the certificate warning in the browser.4. When the login screen appears, select Use Windows Session Authentication

and click Login.

HOL-SDC-1318

Page 8HOL-SDC-1318

Verify the vCenter Infrastructure Navigator Settings

We need to confirm that vCenter Infrastructure Navigator is properly connected to thevCenter Server instance. On the Home tab of the vSphere Web Client, clickInfrastructure Navigator inventory to go to the vCenter Infrastructure Navigatorhome screen.

HOL-SDC-1318

Page 9HOL-SDC-1318

vCenter Infrastructure Navigator Settings

Click the Settings tab.

Your display should be similar to the figure, with all services displaying a green checkmark icon. vCenter Infrastructure Navigator allows you to toggle discovery on or off, andallows you to toggle integration with vCenter Site Recovery Manager (if installed) on oroff.

If your display does not match the figure, you might need to troubleshoot your vCenterInfrastructure Navigator installation using the procedure outlined in "Module - 5Troubleshooting" in this lab.

HOL-SDC-1318

Page 10HOL-SDC-1318

My Important App

Navigate to the VMs and Templates view of the vSphere Web Client for Site A.

1. Select the Home icon at the top of the screen2. Select the VMs and Templates icon.

HOL-SDC-1318

Page 11HOL-SDC-1318

Navigate to Discovered Information.

You can now view the information that vCenter Infrastructure Navigator has discovered.

You can learn more about this application by inspecting the virtual machines involved,but this lesson first focuses on the overall view.

1. Click the Datacenter Site A section of the hierarchy (second from the top itemin the left pane).

2. Click the Summary tab.3. The display shows the CPU, memory, and storage consumed by the

infrastructure. It also indicates that vCenter Infrastructure Navigator hasdiscovered some services that are running. To find out which of these servicesbelong to My Important App, click Show in Inventory.

HOL-SDC-1318

Page 12HOL-SDC-1318

Application Services

This display shows the virtual machines by name and which services they are running.www01 and db01 are My Important App. Notice that www01 is running an Apache Webserver and that db01 is running a MySQL database.

HOL-SDC-1318

Page 13HOL-SDC-1318

Application Dependencies Map

1. Expand the My Important App folder in the left hand pane, and click either ofthe My Important App virtual machines.

2. Click the Manage tab.3. Click Application Dependencies.

Here you can confirm that the two virtual machines are working together. There aremany different ways to visualize this in the vSphere Web Client. Explore the variousviews you can select from the virtual machine folder level, the data center level, and theroot level of the hierarchy on the left.

HOL-SDC-1318

Page 14HOL-SDC-1318

Verify Capacity AvailabilityThis section uses vCenter Operations Manager to confirm that there is sufficientcapacity at Site B prior to replicating our Important App virtual machines there. This willbe done by running a what-if scenario to determine what the resource utilization impactwill be if it is necessary to enact the disaster recovery plan.

Log In to vCenter Operations Manager

1. Open a new tab in the Chrome browser, and click the bookmark labeled vCenterOperations Manager from the bookmark tool bar. If you are presented with acertificate error screen, click Proceed to continue.

2. Enter the Administrator credentials to log-in.

Username: Administrator

Password: VMware1!

HOL-SDC-1318

Page 15HOL-SDC-1318

Navigate to Site B

Note: If you do not see a view like the one depicted above, close the tab for vCenterOperations Manager and re-open it again.

By default when you log in to vCenter Operations Manager, you are presented with thedashboard World view. This view shows the status of the entire environment.

You need to navigate to Cluster Site B as this is where the recovered workloads from MyImportant App will run in the event of a disaster failover.

In the left pane, select vc-w12-01b.corp.local > Data Center Site B> Cluster SiteB.

HOL-SDC-1318

Page 16HOL-SDC-1318

Cluster Site B Operations

The next step is to verify that sufficient CPU, memory and storage capacity is availableat Site B.

1. With Cluster Site B selected in the tree, select the Operations tab.2. Select the Workload (gear-shaped) icon.

HOL-SDC-1318

Page 17HOL-SDC-1318

Compute Resources

This view shows the current resource demands for workloads running at Site B andshows the CPU, memory, disk and network utilization.

Notice that sufficient compute resources are available.

HOL-SDC-1318

Page 18HOL-SDC-1318

Storage Resources

Scroll down to the bottom of this view and expand the STORAGE sub-section. Move thecursor over the graphic of the datastore to get additional information on availablestorage capacity.

The next step is to determine what the impact will be to Site B if it is needed for failoverof My Important App.

HOL-SDC-1318

Page 19HOL-SDC-1318

What-If Scenario

This step runs a what-if scenario on Cluster Site B. vCenter Operations Manager will takethe provided information and display the predicted resource utilization with the twovirtual machines from My Important App running in Site B.

1. Click the Planning tab.2. Click Summary.3. Click New what-if scenario.

HOL-SDC-1318

Page 20HOL-SDC-1318

Step 1

Follow the steps in the wizard to build out the what-if scenario.

Select Cluster or Host Capacity Usage - Trend and click Next.

HOL-SDC-1318

Page 21HOL-SDC-1318

Step 2

Select Virtual machines and click Next.

HOL-SDC-1318

Page 22HOL-SDC-1318

Step 3

You can define the compute resources that the virtual machines will need, or you canuse an existing virtual machine in the inventory as the template.

Choose the second option. You will use the www01 and db01 virtual machines as thetemplates.

HOL-SDC-1318

Page 23HOL-SDC-1318

Step 4

1. Select Datacenter A from the drop down menu.2. Place a check mark next to db01 and www01.3. Click Next to continue.

HOL-SDC-1318

Page 24HOL-SDC-1318

Step 5

You can optionally increase the virtual machine count for each of the two virtualmachines. This could prove useful at a later date if you want to expand the deploymentof My Important App. For now, accept the defaults and click Next to continue.

HOL-SDC-1318

Page 25HOL-SDC-1318

Step 6

Verify the information and click Finish

HOL-SDC-1318

Page 26HOL-SDC-1318

Viewing the Results

View the results of the what-if scenario you just created.

1. Select Views.2. Select Capacity.3. Select Cluster or Host Capacity Usage.4. Select the Table view option.

HOL-SDC-1318

Page 27HOL-SDC-1318

Results

The Table view allows you to determine the resource impact to the cluster. Scroll downto view CPU, memory and disk utilization information before and after the two VMs areadded.

This verifies that sufficient resources are available for the disaster recovery plan.

HOL-SDC-1318

Page 28HOL-SDC-1318

HOL-SDC-1318

Page 29HOL-SDC-1318

Getting Ready for Protection andRecoveryThis section prepares the virtual machines in My Important App for protection andrecovery with vCenter Site Recovery Manager.

HOL-SDC-1318

Page 30HOL-SDC-1318

Is This Application Protected?

Navigate back to the vSphere Web Client for Site A.

From the Application Services tab, you can determine whether vCenter Site RecoveryManager is properly managing these virtual machines and protecting them with theother site.

1. Select My Important App in the vSphere Web Client.2. Click the Manage tab and select Application Services.

This page lists the virtual machines in this folder along with the associated vCenter SiteRecovery Manager protection group and recovery plan. These are currently emptybecause the My Important App virtual machines are not replicated or protected. Thenext steps show how to enable replication of the virtual machines to the alternate site.

Check Replication

1. Navigate back to the Home screen of the Web client by clicking the Home icon.

2. Select vSphere Replication.

HOL-SDC-1318

Page 31HOL-SDC-1318

3. Select the Home tab on the vSphere Replication page.

4. Verify that the vCenter server VC-W12-01A.corp.local is highlighted in the mainscreen, and click Manage.

HOL-SDC-1318

Page 32HOL-SDC-1318

Enable Replication

From vSphere Replication:

1. Navigate to Target Sites.2. Highlight VC-W12-01B.corp.local.

If the status displayed is Connected, proceed to the next step.

If the status is Disconnected, right-click the target site VC-W12-01B.corp.local in thetable and select Reconnect site. Supply your vCenter Site Recovery Manageradministrative credentials, which are the same as your vCenter Server credentials:

User name: administrator

Password:VMware1!

After a short delay, the table refreshes and the target site is connected.

HOL-SDC-1318

Page 33HOL-SDC-1318

Replicate Virtual Machines

In the vSphere Web Client, navigate to Home > vCenter > VMs and Templates.

1. Select db01from My Important App.2. Click Actions.3. Select All vSphere Replication Actions > Configure Replication.

HOL-SDC-1318

Page 34HOL-SDC-1318

Choose the Target Site

Complete this process for each virtual machine in My Important App for www01 anddb01.

Select VC-W12-01B.corp.local as the target site and click Next.

HOL-SDC-1318

Page 35HOL-SDC-1318

Choose vSphere Replication Server

1. Select vSphere Replication Server.2. Highlight vr-l-01b and click Next.

HOL-SDC-1318

Page 36HOL-SDC-1318

Choose the Target Datastore Location

Select ds-site-b-nfs02 as the target datastore location and click Next.

HOL-SDC-1318

Page 37HOL-SDC-1318

Replication Options

Click Next.

HOL-SDC-1318

Page 38HOL-SDC-1318

Choose the Recovery Settings

For this lab, keep the defaults for the Recovery Point Objective (RPO) and Point intime Instances. These tools can be used for more complex disaster recovery plans thatyou create for your production environment. Click Next.

HOL-SDC-1318

Page 39HOL-SDC-1318

Complete Replication and Repeat Once

Select Finish to complete the replication configuration for db01. Repeat the previous 6steps for www01. Notice that the figure shows db01

HOL-SDC-1318

Page 40HOL-SDC-1318

Verify Replication

Open the vSphere C# client connected to VC-W12-01A. In the Recent Tasks pane atthe bottom of the page, notice that both virtual machines from My Important App havebeen configured for replication.

HOL-SDC-1318

Page 41HOL-SDC-1318

Access Site Recovery Manager Snap-In

1. To access the vCenter Site Recovery Manager Plug-in, select Home in thenavigation bar.

2. Under Solutions and Applications, select the Site Recovery snap-in.

If you are prompted to authenticate, enter the administrator credentials.

User name:administrator

Password:VMware1!

View Replication Progress

To monitor the replication progress of db01 and www01:

1. Select vSphere Replication from the menu on the lower left.2. Select the vSphere replication appliance vr-l-01b under vc-w12-01b.corp.local.3. Select the Virtual Machines tab.

Notes:

HOL-SDC-1318

Page 42HOL-SDC-1318

• To display the replication progress you must view the destination site and not thesite of origin.

• The initial full replication can take approximately 25 minutes to complete. You can continue withcreation of the protection groups and recovery plans sections while you wait for replication tocomplete.

Important:Do not begin the test failover step until replication is complete.

HOL-SDC-1318

Page 43HOL-SDC-1318

Module 2 - Using vCenterSite Recovery Manager

HOL-SDC-1318

Page 44HOL-SDC-1318

Application ProtectionThis module shows how to create and assign vCenter Site Recovery Manager protectionpolicies to My Important App.

HOL-SDC-1318

Page 45HOL-SDC-1318

Create a Protection Group

To protect an application, you first need to make vCenter Site Recovery Manager awareof it by creating a protection group using the vCenter Site Recovery Manager plug-in.

Connect to the C# client and select Home> Solutions and Applications> SiteRecovery plug-in. Enter your credentials when prompted:

User name:Administrator

Password:VMware1!

1. After connecting, there will be a slight delay, after which you can selectProtection Groups.

2. Click Create a Protection Group to begin.

Create the Protection Group

Identify the site to work with and the type of group based on replication.

HOL-SDC-1318

Page 46HOL-SDC-1318

The protected site is vc-w12-01a.corp.local.This lab uses vSphere replicationtechnology, so select vSphere Replication (VR) as the type and click Next.

HOL-SDC-1318

Page 47HOL-SDC-1318

Select Virtual Machines

Identify the virtual machines to include in the group. Only the virtual machinesprotected by vSphere Replication are available. Non-replicated virtual machines cannotbe protected by vCenter Site Recovery Manager without first being replicated to anothersite. Select the check box for each virtual machine, www01 and db01, and click Next.

If you do not see both virtual machines, it is probably because both were not set toreplicate in the earlier lesson. Go back and enable replication for both of the virtualmachines.

HOL-SDC-1318

Page 48HOL-SDC-1318

Name the Protection Group

Type a name for the protection group and click Next. The specific name is notimportant, but it is used later.

HOL-SDC-1318

Page 49HOL-SDC-1318

Confirm Settings

Review your selections. Click Back to make changes or Finish to proceed.

HOL-SDC-1318

Page 50HOL-SDC-1318

Confirm Protected Status

To confirm the protected status of your app, select the new protection group and noticethe OK status of your virtual machines.

HOL-SDC-1318

Page 51HOL-SDC-1318

View Protected Virtual Machines at Site B

You can view the results on the second site by logging into the C# client (or Web client)for vc-w12-01b.corp.localand viewing the inventory. Notice two new virtual machineswith special icons which denote that these placeholder virtual machines are protected.

Optional - View Protected Virtual Machines in Web Client

Switching back to the Web client, notice that vCenter Infrastructure Navigator hasupdated the table with the recently configured protection group created in vCenter SiteRecovery Manager.

The table view shows all the virtual machines in the selected folder.

HOL-SDC-1318

Page 52HOL-SDC-1318

Additional Application Dependency Information

If you change to an individual virtual machine view, the vCenter Site Recovery Managericon and the name of the Protection group are displayed in the virtual machine graphic.

HOL-SDC-1318

Page 53HOL-SDC-1318

Application Recovery Test PlanAdding replicated virtual machines to a protection group is not enough to make themdisaster ready. With many possible protection groups, vCenter Site Recovery Managerdoes not know how to interact with those virtual machines until a recovery plan iscreated.

The recovery plan provides a recovery steps script, or runbook, of steps to manage thevirtual machines.

Create Recovery Plan

1. From the vCenter Site Recovery Manager plug-in, select the Recovery Plans tab.2. Click the Create Recovery Plan link.

HOL-SDC-1318

Page 54HOL-SDC-1318

Create Recovery Plan - Recovery Site

1. Identify the recovery site. This is the site where the virtual machines will berecovered to (not from). The recovery site for this lab is vc-w12-01b.corp.local.

2. Click Next.

HOL-SDC-1318

Page 55HOL-SDC-1318

Select Protection Group

1. Select the protection group you want this recovery plan to include. In a real-worldscenario, there can be many protection groups included in a single recovery plan.This lab, however, includes only the one you built earlier.

2. Click Next.

HOL-SDC-1318

Page 56HOL-SDC-1318

Network Selection

1. You can apply advanced controls over how networking is managed during the testof a recovery plan. There are multiple options, but for this lab select the defaultAuto setting.

2. Click Next.

HOL-SDC-1318

Page 57HOL-SDC-1318

Name the Plan

Name the recovery plan and click Next.

HOL-SDC-1318

Page 58HOL-SDC-1318

Verify the Settings

Review your selections. Click Back to make changes or Finish to continue.

Edit Recovery Plan - Add Non-Critical Virtual Machine

Now that a protection group is connected to a recovery plan, you can see the runbookthat vCenter Site Recovery Manager has built. In the simplest use cases, the process iscomplete and the virtual machines are protected. However, for this lab, there are someadditional steps.

You might have noticed that there are two test/dev virtual machines running at thesecondary site. If a disaster occurs, you want to dedicate the capacity of Site B torunning My Important App. You can instruct vCenter Site Recovery Manager to suspendall non-critical workloads so that your recovered applications have sufficient computecapacity to run.

To do this, you need to edit the recovery plan.

1. Select the Recovery Plans menu option in the left pane.2. Select the recovery plan you just created under the All Recovery Plans folder at

the top of the left pane.

HOL-SDC-1318

Page 59HOL-SDC-1318

3. Navigate to the Recovery Steps tab.4. Click Add a Non-Critical VM.

HOL-SDC-1318

Page 60HOL-SDC-1318

Select Non-Critical Virtual Machine

A simple inventory of the recovery site is displayed. Select both of the low priorityvirtual machines and click OK.

Note: Do not select the other virtual machine (vr-l-01b), as that is the virtual replicationappliance and pausing it breaks the replication between sites.

HOL-SDC-1318

Page 61HOL-SDC-1318

Verify Additional Step

The recovery plan now has a new step. When this plan is run, the low priority virtualmachines are suspended in favor of running the protected virtual machines.

Edit Recovery Plan - Application Recovery Settings

Advanced IP Options

Note: The following steps focus on Application Dependency during recovery. Should youwish to explore the additional IP customization options available with vCenter SiteRecovery Manager, consider taking lab HOL-SDC-1305 - "Business Continuity andDisaster Recovery in Action."

Setting up a recovery plan is the first step in getting site virtual machines protected.The runbook that is created by that task is fully customizable. You can make changes tothe default runbook to discover more about how flexible vCenter Site Recovery Managercan be.

HOL-SDC-1318

Page 62HOL-SDC-1318

For separate runbooks are created for each recovery plan. You can switch between themby changing the view when on the Recovery Steps tab of the recovery plan. Each setof steps can be edited and modified independently, allowing for greater flexibility duringtesting, cleanup, recovery, and re-protecting.

HOL-SDC-1318

Page 63HOL-SDC-1318

Advanced Configuration

1. To configure virtual machine dependencies, expand step 7 in the plan and right-click the www01 virtual machine.

2. Select Configure from the menu.

HOL-SDC-1318

Page 64HOL-SDC-1318

Configure Virtual Machine Dependencies

1. Click VM Dependencies for virtual machine www01. You can tie this virtualmachine to others and effectively set boot orders.

2. Click Add.

HOL-SDC-1318

Page 65HOL-SDC-1318

Specify the Dependency

1. Select the db01 virtual machine from the All Protection Groups list (notice thatonly a virtual machine in a protection group is offered).

2. Click Add to commit the change.

HOL-SDC-1318

Page 66HOL-SDC-1318

Confirm Dependency Settings

Now the db01 virtual machine will start before the www01 virtual machine. This is whatyou want because the Web server depends on the database server, as observedpreviously in vCenter Infrastructure Navigator.

Click OK to complete this step.

Important: Confirm that the initial full replication of db01 and www01 are completebefore proceeding to testing of the recovery plan.

HOL-SDC-1318

Page 67HOL-SDC-1318

Test and Clean Up App RecoveryThe final step is to test the recovery plan non-destructively to establish that it will workif a disaster occurs.

Test the Recovery Plan

Click the Test icon or link to begin testing your recovery plan.

HOL-SDC-1318

Page 68HOL-SDC-1318

Replicate Recent Changes

1. The option is available to replicate all changes from the protected site to therecovery site to confirm that the most recent data is present at the recovery site.For the purpose of this lab, and due to the fact that you just finished replicatingthe virtual machines, Deselect this option if it is selected.

2. Click Next to continue.

HOL-SDC-1318

Page 69HOL-SDC-1318

Verify Information

1. Verify that the information is correct.2. Click Start.

HOL-SDC-1318

Page 70HOL-SDC-1318

Successful Test - Site A

A successful test results in this notice about the test and cleanup options.

Notice that the runbook steps are listed as Success in green. The Test link in the mainpanel is dimmed. You cannot test again until you have reversed the process byperforming a cleanup.

HOL-SDC-1318

Page 71HOL-SDC-1318

Successful Test - Site B

If you check Site B, notice that some things are different. My Important App virtualmachines are running and the low priority virtual machines are suspended, as therunbook indicated.

Cleanup

The cleanup process is the reverse of the test process. Select Cleanup in the recoveryplan summary window, accepting the default values, and click Start.

HOL-SDC-1318

Page 72HOL-SDC-1318

Recovery Plan Cleaned Up

When the brief cleanup process is complete, the recovery plan returns to its normalstate, ready for more editing, testing, or use. Notice that vCenter Site Recovery Managerdoes not initiate any actions automatically. An administrator must trigger (and confirm)these stages manually. vCenter Site Recovery Manager does not declare a disaster stateon its own.

HOL-SDC-1318

Page 73HOL-SDC-1318

Module 3 - DisasterStrikes

HOL-SDC-1318

Page 74HOL-SDC-1318

Disaster Strikes! Recovery from aFailed SitePreparedness is the key. This section deals with a site outage and recovery of MyImportant App to the protection site.

A disaster has struck the primary site, causing a loss of communication with MyImportant App. You must recover it to the secondary site to continue normal operations.Follow these steps to declare a disaster and failover.

Trigger Site Outage

Start the simulated disaster by running a VMware vSphere PowerCLI™ script to take outthe primary site. Double-click the highlighted shortcut on the desktop of your labsession.

Site Outage Process Running

Observe that services and resources are being removed from the primary site assystems fail.

HOL-SDC-1318

Page 75HOL-SDC-1318

If Script Generates Errors

If the disaster script generates errors as shown in the figure, wait for the script to finishrunning and then rerun it again from the desktop shortcut.

HOL-SDC-1318

Page 76HOL-SDC-1318

Primary Site Crushed Under Meteors

If everything goes well (or very badly, as planned), a set of failure messages isdisplayed, including loss of connectivity to Site A. That site is down now, but fortunatelyyou have a tested recovery plan to start things again.

Allow this process to complete. The command window closes when all steps havefinished.

HOL-SDC-1318

Page 77HOL-SDC-1318

Connect to Secondary Site

Connect to the secondary site with your lab credentials if you are not alreadyconnected. Launch the vSphere C# client and connect to vc-w12-01b.corp.local.

User name:corp\administrator

Password:VMware1!

HOL-SDC-1318

Page 78HOL-SDC-1318

Verify Inventory

Notice that the Important App virtual machines are in inventory in the same protectedstate as before. vCenter Site Recovery Manager does not declare a disaster by itself. Ahuman operator must declare the disaster and invoke the recovery plan manually. To dothat, you must connect to the vCenter Site Recovery Manager service on the secondarysite.

HOL-SDC-1318

Page 79HOL-SDC-1318

Connect to the vCenter Site Recovery Manager Plug-in

Log in to vCenter Site Recovery Manager using your lab credentials.

User name:administrator

Password: VMware1!

HOL-SDC-1318

Page 80HOL-SDC-1318

Primary Site Is Down

Because the vCenter Site Recovery Manager service on the primary site is down, it willnot respond.

Click through the error and select Cancel when prompted to authenticate again.

Select the Recovery Plans tab and choose the only available recovery plan (the oneyou created earlier).

HOL-SDC-1318

Page 81HOL-SDC-1318

Begin the Recovery Process

Navigate to your recovery plan and click the Recovery icon or link.

HOL-SDC-1318

Page 82HOL-SDC-1318

Confirm the Recovery Action

1. Execute the recovery plan. You must agree that this is a permanent change byselecting the check box.

2. Notice that you only have one option for recovery, Disaster Recovery.3. Click Next.

HOL-SDC-1318

Page 83HOL-SDC-1318

Verify Selection

Click Start to initiate the recovery.

HOL-SDC-1318

Page 84HOL-SDC-1318

Review Results of Disaster Recovery

Switch your view to the Recovery Steps tab to monitor the progress of the tasks beingexecuted in the runbook.

HOL-SDC-1318

Page 85HOL-SDC-1318

Recovery Completed

When the recovery plan is complete, a message is displayed indicating that the planwas unable to complete all tasks in the runbook list because some of those stepsrequire the other site to be available.

This is OK, because this is a disaster scenario.

Notice that the Suspend Non-critical VMs step is green and that the Power OnPriority 3 VMs step is green. At this point, review the inventory.

HOL-SDC-1318

Page 86HOL-SDC-1318

My Important Apps Recovered!

Switching the view to VMs & Templates of vCenter, notice that in the inventory thatthe important functions have completed. The Important App is running again and thelow priority virtual machine is suspended.

At this point, My Important App has been recovered to Site B and is once againfunctional and accessible.

HOL-SDC-1318

Page 87HOL-SDC-1318

Module 4 - DisasterPassed. Recover to Site A

- OPTIONAL

HOL-SDC-1318

Page 88HOL-SDC-1318

Disaster Passed! Reprotection andPlanned MigrationNote: This is an optional module that you can complete if you have sufficient time.

In this module you will recover the primary data center and return the application to theoriginal operation.

The simulated disaster only affected the power grid and not the site itself. All of Site A'ssystems are intact so you can return things to normal. However, it is not as easy as justpowering things on and returning to business as usual. The virtual machines will havechanged in the time it took to recover the primary site. Perhaps a lot of time has passedand thousands of transactions have occurred.

The recovery site is now the operational site and the original site must be viewed as thenew recovery site.

Go through the steps of restoring the original primary site to a working state andsynchronizing the sites again. Then turn the protection relationship around so that theoriginal site can safely be used again.

Apply Anti-Meteor Script to Recover Primary Site

To reverse the disaster scenario, run the highlighted script Disaster Passed! on thedesktop of the Control Center.

Meteors Removed

You will see a series of steps to reverse the damage done in the last lesson, returningthe primary site to availability. This includes a reboot of the VMware ESXi™ hosts toforce a rapid inventory discovery. This process might take a few extra minutes, so waituntil the process completes.

If you want to monitor the process, open a client connection to vc-w8-01a (Web or C#)and observe as hosts return to inventory and virtual machines boot up.

Allow this process to complete. The command window closes when all steps havefinished.

HOL-SDC-1318

Page 89HOL-SDC-1318

Note: Confirm that the ESXi hosts have rebooted in Site A and the virtual machineshave been restarted before continuing. This could take a few minutes to complete.

HOL-SDC-1318

Page 90HOL-SDC-1318

Reconnect the vSphere Replication Appliance

The following steps are similar to those in Module 1 where you connected the vSphereReplication Appliance from Site A to the appliance in Site B, In this case, you will do thesame, but in the reverse direction.

Log in to the vSphere Web Client for vc-12-01b.corp.local.

1. From the home screen, navigate to vSphere Replication.2. Select the Home tab.3. Highlight vc-12-01b.corp.local and click Manage.4. When the Manage tab opens, select Target Sites from the menu on the left.5. Right-click VC-W12-01A.corp.local and select Reconnect site.

Enter the credentials for Site A when prompted.

User name:Administrator

Password: VMware1!

When the status shows connected, you can proceed to the next step.

HOL-SDC-1318

Page 91HOL-SDC-1318

HOL-SDC-1318

Page 92HOL-SDC-1318

Run Recovery Again

The next step requires you to switch from the vSphere Web Client to thevSphere C# client.

When Site A has restarted, vCenter Site Recovery Manager indicates that you must runthe recovery process again to synchronize the sites. You can do this by selectingRecovery from the vCenter Site Recovery Manager plug-in.

Notice that the virtual replication appliance from Site A has just returned from an off-linestate and must re-sync. The state of virtual machines at the original site is unknown atthis point.

HOL-SDC-1318

Page 93HOL-SDC-1318

Run Recovery Again to Re-Sync

Click Next.

HOL-SDC-1318

Page 94HOL-SDC-1318

Verify Selection

Click Start to begin the process.

HOL-SDC-1318

Page 95HOL-SDC-1318

Re-Sync Complete - Reprotect Site

After the sites are in sync, you can perform a reprotection action. This process restoresthe protection and recovery steps used to protect the original site, but applies the logicto the two sites in reverse directions.

Note: If you are moving quickly through this lab, you might be able to trigger thereprotect before Site A is ready for it. For best results, allow the Important Apps to bootup completely (or, if they are powered off, leave them that way) before attempting toreprotect. The error you might encounter is related to storage being locked by thebooting virtual machines, which virtual replication cannot override to re-synchronize.

HOL-SDC-1318

Page 96HOL-SDC-1318

Agree to the Actions

Select the agreement box and click Next.

HOL-SDC-1318

Page 97HOL-SDC-1318

Verify Actions

Click Start to begin the process.

If you see some errors in vSphere Client about restarting replication, you can trigger theprocess manually by right-clicking on each virtual machine and configuring replicationas if it were the first time. Activities in a lab scenario can happen much more quicklythan in a real-world scenario, so sometimes it helps to push the software in the rightdirection.

Check on Replication

Allow enough time for replication to complete during the re-synchronization. This stepcan take about 25 minutes to complete.

Note; If you are unable to see the status of the virtual machine replication, you mightneed to log out and back into the vSphere C# client for Site B. After you log back in,select the Site Recovery Manager plug-in icon and enter the Administrator credentialswhen prompted.

User name: Administrator

Password: VMware1!

Follow these steps to navigate to the Replication Status view.

1. Select the vSphere Replication tab.

HOL-SDC-1318

Page 98HOL-SDC-1318

2. Select the vSphere Replication appliance at site A (vr-l-01a).3. Select the Virtual Machines tab.

Primary Site Now Protection Site

Looking at the vSphere C# Client for Site A, notice that the My Important App virtualmachines are now displaying the protected status icons. The relationship between sitesA and B has turned around to point in the opposite direction.

HOL-SDC-1318

Page 99HOL-SDC-1318

Everything Back to Normal (on Site B)

After the reprotect process is complete, the vCenter Site Recovery Manager view returnsto what looks like in the normal, unused state, except that it still shows the formerrecovery site. Roles have been completely reversed, so the site that was a protectedsite is now a recovery site and vice versa. Standard vCenter Site Recovery Manager userules apply, including testing the runbook steps and setting custom runbook steps asneeded.

Optional- Recover Site B to Site A

If time allows (check your lab count-down timer, if you have 10 more minutes), you canrun through the process of fully returning Site A to its original role of primary site byrunning the recovery plan one more time, from Site B to Site A. Select the check box toagree to the changes.

A planned migration is a way of using vCenter Site Recovery Manager to migrate virtualmachines between known operational sites in a controlled, testable, reversible manner.

HOL-SDC-1318

Page 100HOL-SDC-1318

It is only available when both sites are connected and running vCenter Site RecoveryManager.

HOL-SDC-1318


Site A Recovered!

When fully reversed, the Site A and Site B clients look just like they did at the beginningof this lab.

HOL-SDC-1318


Module 5 -Troubleshooting

HOL-SDC-1318


Troubleshooting vCenter InfrastructureNavigatorThis section provides information on getting vCenter Infrastructure Navigator workingfor your lab.

vCenter Infrastructure Navigator Does Not Respond toWeb Client

If you receive this message in the vCenter Infrastructure Navigator Home section, orget messages that the map could not be loaded, you must start or restart vCenterInfrastructure Navigator.

HOL-SDC-1318


Locate and Power Cycle vCenter Infrastructure Navigator

Shut down the guest operating system of the highlighted virtual machine in the ClusterSite A vCenter Server. Allow the virtual machine to power down completely, that is,until the green arrow disappears from the virtual machine. If the virtual machine isalready powered off, proceed to the next step.

Power on the virtual machine from the same view and proceed with the lab for at least 5minutes. You can then return to working with vCenter Infrastructure Navigator.

Correct vCenter Infrastructure Navigator Operation

vCenter Infrastructure Navigator shows this information when it is working properly.

If this view shows the application discovery state as green, but vCenter Site RecoveryManager Integration as red or disconnected, the likely cause is that the vCenter SiteRecovery Manager service on vc-w12-01a is not running. If this lab was very recentlycreated, the vCenter Site Recovery Manager service might not have started yet, as it is

HOL-SDC-1318


a delayed-start Windows service. Wait another five minutes for the vCenter SiteRecovery Manager service to start up. vCenter Infrastructure Navigator will recovernormally.

HOL-SDC-1318


Troubleshooting vCenter Site RecoveryManagerThis section will help you get vCenter Site Recovery Manager up and running if issuesarise.

Is the Service Running?

If you get a report that the vCenter Site Recovery Manager service cannot be reached,the most likely solution is that the Windows Service is not running.

HOL-SDC-1318


Start or Restart the Service

From within your lab, use a Remote Desktop Connection to open a session with thevCenter Server reported in the error. Select Start> Administrative Tools> Servicesand scroll down to VMware vCenter Site Recovery Manager. Note whether theservice is running and start the service if it is not.

HOL-SDC-1318


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

Lab SKU: HOL-SDC-1318

Version: 20141126-112111

HOL-SDC-1318


http://hol.vmware.com/

Table of ContentsLab OverviewAbout This Lab

Module 1 - Introduction to VMware vCenter Site Recovery ManagerApplication Discovery and DependenciesLog In to vSphere Using the VMware vSphere ClientLog In to vSphere Using the VMware vSphere Web ClientVerify the vCenter Infrastructure Navigator SettingsvCenter Infrastructure Navigator SettingsMy Important AppNavigate to Discovered Information.Application ServicesApplication Dependencies Map

Verify Capacity AvailabilityLog In to vCenter Operations ManagerNavigate to Site BCluster Site B OperationsCompute ResourcesStorage ResourcesWhat-If ScenarioStep 1Step 2Step 3Step 4Step 5Step 6Viewing the ResultsResults

Getting Ready for Protection and RecoveryIs This Application Protected?Check ReplicationEnable ReplicationReplicate Virtual MachinesChoose the Target SiteChoose vSphere Replication ServerChoose the Target Datastore LocationReplication OptionsChoose the Recovery SettingsComplete Replication and Repeat OnceVerify ReplicationAccess Site Recovery Manager Snap-InView Replication Progress

Module 2 - Using vCenter Site Recovery ManagerApplication ProtectionCreate a Protection GroupCreate the Protection GroupSelect Virtual MachinesName the Protection GroupConfirm SettingsConfirm Protected StatusView Protected Virtual Machines at Site BOptional - View Protected Virtual Machines in Web ClientAdditional Application Dependency Information

Application Recovery Test PlanCreate Recovery PlanCreate Recovery Plan - Recovery SiteSelect Protection GroupNetwork SelectionName the PlanVerify the SettingsEdit Recovery Plan - Add Non-Critical Virtual MachineSelect Non-Critical Virtual MachineVerify Additional StepEdit Recovery Plan - Application Recovery SettingsAdvanced ConfigurationConfigure Virtual Machine DependenciesSpecify the DependencyConfirm Dependency Settings

Test and Clean Up App RecoveryTest the Recovery PlanReplicate Recent ChangesVerify InformationSuccessful Test - Site ASuccessful Test - Site BCleanupRecovery Plan Cleaned Up

Module 3 - Disaster StrikesDisaster Strikes! Recovery from a Failed SiteTrigger Site OutageSite Outage Process RunningIf Script Generates ErrorsPrimary Site Crushed Under MeteorsConnect to Secondary SiteVerify InventoryConnect to the vCenter Site Recovery Manager Plug-inPrimary Site Is DownBegin the Recovery ProcessConfirm the Recovery ActionVerify SelectionReview Results of Disaster RecoveryRecovery CompletedMy Important Apps Recovered!

Module 4 - Disaster Passed. Recover to Site A - OPTIONALDisaster Passed! Reprotection and Planned MigrationApply Anti-Meteor Script to Recover Primary SiteMeteors RemovedReconnect the vSphere Replication ApplianceRun Recovery AgainRun Recovery Again to Re-SyncVerify SelectionRe-Sync Complete - Reprotect SiteAgree to the ActionsVerify ActionsCheck on ReplicationPrimary Site Now Protection SiteEverything Back to Normal (on Site B)Optional- Recover Site B to Site ASite A Recovered!

Module 5 - TroubleshootingTroubleshooting vCenter Infrastructure NavigatorvCenter Infrastructure Navigator Does Not Respond to Web ClientLocate and Power Cycle vCenter Infrastructure NavigatorCorrect vCenter Infrastructure Navigator Operation

Troubleshooting vCenter Site Recovery ManagerIs the Service Running?Start or Restart the Service

Conclusion

Documents

Table of Contents - VMwareThis lab features VMware® vCloud® Suite 5.5 products from the vCloud Suite 2013 release. The focus of this lab is to work with VMware vCenter , VMware vCenter