00 vmware saclass design lab final

8/2/2019 00 VMware SAClass Design Lab Final

1/44

VMware and EMC Solutions for

Solutions Architects Lab Guide

Education Services

October 2008


2/44

VMware and EMC Solutions for Solutions Architects

Copyright 2008 EMC Corporation. All Rights Reserved. Version 1.0 Page 2 of 44

Copyright :

Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 EMC Corporation. All RightsReserved. EMC believes the information in this publication is accurate as of its publication date. The informationis subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NOREPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THISPUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable softwarelicense.

EMC, ICDA (Integrated Cached Disk Array), and EMC2 (the EMC logo), and Symmetrix, are registeredtrademarks of EMC Corporation. EMC and SRDF are trademarks of EMC Corporation.All other trademarks used herein are the property of their respective owners.


3/44



Trademark Information:

EMCTrademarks

EMC2, EMC, Symmetrix, Celerra, CLARiiON, CLARalert, Connectrix, Dantz,

Documentum, HighRoad, Legato, Navisphere, PowerPath, ResourcePak,

SnapView/IP, SRDF, TimeFinder, VisualSAN, and where information lives are

registered trademarks and EMC Automated Networked Storage, EMC

ControlCenter, EMC Developers Program, EMC OnCourse, EMC Proven, EMC

Snap, Access Logix, AutoAdvice, Automated Resource Manager, AutoSwap,

AVALONidm, C-Clip, Celerra Replicator, Centera, CentraStar, CLARevent,

CopyCross, CopyPoint, DatabaseXtender, Direct Matrix, Direct Matrix

Architecture, EDM, E-Lab, Enginuity, FarPoint, FLARE, GeoSpan, InfoMover,MirrorView, NetWin, OnAlert, OpenScale, Powerlink, PowerVolume, RepliCare,

SafeLine, SAN Architect, SAN Copy, SAN Manager,SDMS, SnapSure, SnapView,

StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix DMX,

Universal Data Tone, and VisualSRM are trademarks of EMC Corporation. All

other trademarks used herein are the property of their respective owners.

Third PartyTrademarks

AIX is a registered trademark of International Business Machines Corporation.

Brocade, SilkWorm, SilkWorm Express, and the Brocade logo are trademarks or

registered trademarks of Brocade Communications Systems, Inc., in the United

States and/or in other countries. Compaq and the names of Compaq products

referenced herein are either trademarks and/or service marks or registered

trademarks and/or service marks of Compaq. Hewlett-Packard, HP, HP-UX,

OpenView, and OmniBack are trademarks, or registered trademarks of Hewlett-

Packard Company. McDATA, the McDATA logo, and ES-2500 are registered

trademarks of McDATA Corporation. Microsoft, Windows, and Windows NT are

either registered trademarks or trademarks of Microsoft Corporation in the United

States and/or other countries. NobleNet is a registered trademark of Rogue Wave

Software, Inc. SANbox is a trademark of QLogic Corporation. Sun, Sun

Microsystems, the Sun Logo, SunOS and all Sun-based trademarks and logos, Java,

the Java Coffee Cup Logo, and all Java-based trademarks and logos, Solaris, and

NFS, are trademarks or registered trademarks of Sun Microsystems, Inc. in the

United States and other countries. UNIX is a registered trademark of The Open

Group.

VMware, the VMware boxes logo and design, Virtual SMP, VMotion,

MultipleWorlds, GSX Server, and ESX Server are registered trademarks or

trademarks of VMware, Inc.


4/44



Document Revision History:

Rev # File Name Date1.0 VMware_SAClass_Labs.doc 1-October-2008


5/44



Lab Conventions and Symbols

The following conventions are applied throughout the Lab Exercises in this class. Where indicated symbolswill be present with the associated text:

Convention/Symbol Usage

UNDERLINED,BOLD TEXT,SMALL CAPS Primary description/overview of task(s) to be executed in theLab Exercise. Presented right at the beginning of each labexercise part.

SMALL CAPS Major Lab Task and description of the major task to beexecuted for this lab step.

Italicized Text Lab narrative or contextual information.

Bold, Italicized Text Important must read instructions regarding potentiallydestructive or impacting operations.

Note - Noteworthy or important contextual information.Reference Worksheet Information relevant to the current lab instruction is located in

the student worksheet.

Complete Worksheet Information needs to be completed in the student worksheet forthe current lab instruction.

Q. Question that should be answered in the Lab Book.

Plain Text Step-by-Step Lab instructions.

Lab Exercise instructions are organized as follows:

1. MAJOR TASKAND DESCRIPTION OF THE MAJOR TASK TO BE EXECUTED FOR THAT LAB EXERCISE STEP.

a) Subtaskof the Major task. Subtasks may be executed as-is, without reference to any supportingsteps, if they provide sufficient information to the student to be able to execute the operation (basedon the students knowledge and skill set).

i. Supporting stepsto the Subtask. Supporting steps provide more detailed step-by-stepinstructions for execution of the Subtask.

a. Further/more detailed supporting steps.

When executing command line operationsin lab exercises, the following conventions apply:

courier text command line operation to be executed as written

student must supply appropriate information


6/44



Lab Exercise 2: Network and Storage Design

Purpose: To develop a best practices network design for an IP storage infrastructuresupporting a VI3 environment, and examine some of the considerations andimplementation specifics for the design.

Objectives: The following lab parts will be completed as part of this Lab Exercise:

1) Design to a set of Specific Requirements for an IP Storage NetworkInfrastructure

2) Answer Questions on Factors that influence Network Design andImplementation for an ESX IP Storage Environment

References: Classroom Connectivity Guide Student Handout

Workshop Worksheet Student Handout


7/44




Part 1: Design to a set of Specific Requirements for an IPStorage Network Infrastructure

Step Action

1 IN THIS LAB EXERCISE PART, YOU WILL BE ASKED TO DESIGN THE NETWORK INFRASTRUCTUREFOR AN IPSTORAGE ENVIRONMENT, USING A SET OF SPECIFIC REQUIREMENTS AND WORKINGWITHIN SPECIFIC CONSTRAINTS.

Following the requirements and constraints articulated in step (2) of this Lab Exercise, design a BestPractices network infrastructure for a given IP Storage environment. The intent of this exercise is toleverage the material presented in the lecture to reinforce standard best practice configurations andexamine some of the trade-offs that can be involved in designing an IP infrastructure for aniSCSI/NAS environment.

2 USING THE REQUIREMENTS AND CONSTRAINTS ARTICULATED IN THIS SECTION,COMPLETE THE DIAGRAM INSTEP (3) WITH THE ESX CONNECTIONS, PORT GROUPS, VLANS, VIRTUAL SWITCHES, PHYSICALCONNECTIVITY,FAIL SAFE NETWORKS, AND/OR CHANNELS NECESSARY TO SATISFY THE NETWORK DESIGN:

Note There may be several potential designs that could satisfy the design criteria laid out in thislab. There is no one correct answer to this lab, as such. Any design that leverages best practices,meets the design criteria, and is functionally correct is an acceptable solution to this lab.

a) The following requirements have been laid out for developing a design for an IP networkinfrastructure to support an iSCSI/NAS storage environment. Using these requirements and theconstraints indicated (e.g. port constraints), complete the diagram in Step (3) with the appropriatevirtual, logical, and physical infrastructure:

The ESX Server indicated in the diagram is part of a VI3 Cluster providing VMotion/DRS/VMware HA services.

The ESX Server supports 6 standard Network interfaces (there are no iSCSI ToE cardsinstalled in the server).

The Celerra NS-40 indicated in the diagram supports 8 CGE interfaces (4 per Data Mover).

The Data Movers are configured in an Active/Passive configuration for Redundancy.

The Microsoft Software Initiator (MSI) is being used to support iSCSI connectivity in one ormore of the Virtual Machines hosted on the ESX Server.

There are 3 Virtual LANs (VLANs) configured on the Physical Network that may be leveragedin the network design. It is a requirement of the design that Physical or Virtual Networks areused for Traffic Segregation/Isolation.


8/44



The 2 Physical Switches indicated have an Inter-Switch Link (ISL) configured.

The following IP Storage protocols are being leveraged on the IP network in the followingmanner:

iSCSI is being used to support VMFS datastores and Raw Devices for Virtual Machines

iSCSI is also being used to support Raw Devices directly presented to a set of WindowsVM Guests via the MSI (Microsoft Software Initiator)

NFS datastores are being used to host Virtual Machines on the ESX Server

A greater emphasis should be placed on Failover in the design as opposed to Load-Balancing. Load-Balancing should be implemented where practical but without sacrificing therequirement to build as much redundancy into the design as possible.

b) Using these requirements, populate the following for the diagram illustrated in Step (3) of this Lab

Exercise.

Microsoft Software Initiator, Service Console, an VMkernel connections

Virtual Switch Infrastructure

ESX Server NIC Connectivity (Virtual Switch-to-Physical Switch uplinks)

Physical Switch-to-Physical NIC Connectivity

Physical Switch Constructs (Channels/Trunks, etc.)

Protocols supported by each Link

Physical Switch-to-Celerra Interface Connectivity

Virtual Devices and Logical Interfaces configured on the Celerra


9/44


10/44




Part 2: Answer Questions on Factors that influence NetworkDesign and Implementation for an ESX IP Storage Environment

Step Action

1 IN THIS LAB EXERCISE PART,ANSWER THE QUESTIONS IN STEP (2) ON SOME OF THE FACTORSTHAT INFLUENCE DESIGN AND IMPLEMENTATION FOR AN ESXIPSTORAGE ENVIRONMENT.

2 ANSWER THE FOLLOWING QUESTIONS ON SOME OF THE FACTORS THAT INFLUENCE DESIGN AND

IMPLEMENTATION FOR AN ESXIPSTORAGE ENVIRONMENT:

a) How many Virtual Devices may be configured on a Physical Interface on a Celerra?

__________________________________________________________________________

__________________________________________________________________________

b) How many Logical Interfaces may be configured on a (i) Virtual Device, (ii) Physical Interface, ona Celerra?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

c) What are the Key Differentiators between EtherChannel and LACP?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

d) Which Infrastructure Component handles Failover in a Fail-Safe Network Configuration?

__________________________________________________________________________

__________________________________________________________________________

e) What are the Load-Balancing Options available for a Channel/Trunk at the Celerra?

__________________________________________________________________________

__________________________________________________________________________


11/44



__________________________________________________________________________

f) What are the Load-Balancing Options available for a NIC Team configured on an ESX Server?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

g) Which NIC Team Load-Balancing algorithm in ESX Server requires the configuration of 802.3ADLink Aggregation at a Physical Switch? Why?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

h) Can 802.3AD Link Aggregation be performed across Physical Switches? What are some of theCaveats?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

i) Which is the only Load-Balancing Option that may be implemented for a NIC Team supportingthe iSCSI Software Initiator on ESX Server, if Load-Balancing is desired? Why?

__________________________________________________________________________

__________________________________________________________________________

j) What must the configuration be at the (i) Celerra, (ii) the Physical Switch, and (iii) the NIC Team,and (iv) the ESX Software Initiator in order to perform iSCSI Load-Balancing between an ESXSoftware Initiator and a Celerra?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________


12/44



k) How could a similar configuration be implemented at the ESX Host using an iSCSI ToE Card(dedicated iSCSI Hardware Initiator)?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

l) Why does Fail-Safe Networking require the implementation of an Inter-Switch Link (ISL) in aDual-Switch configuration for ESX Server?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

m) What are some of items that factor into Initiator Choice at an ESX Host, when deciding between(i) a dedicated iSCSI Hardware Initiator (ToE Card), (ii) the ESX Software Initiator (iSCSId), (iii)Guest Initiators (e.g. the MSI)?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

n) Can multiple Virtual NICs be placed on the same Virtual Switch where the VNICs support anMSI/MPIO configuration? Is there any advantage to this configuration?

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________


13/44



Lab Exercise 8: Replication Manager

Purpose: To perform a snapshot backup and restore of a VMFS hosting a Windows 2003VM using Replication Manager.

Objectives: The following lab parts will be completed as part of this Lab Exercise:

1) Perform Snapshot Backup of VMFS

2) Mount and Restore Snapshot using Replication Manager

3) Re-register Virtual Machine(s) in Virtual Center

References: Workshop Worksheet Student Handout


14/44




Part 1: Replication Manager VMFS Level Recovery

Step Action

1 VMs started

o RMserver

Procedure

o Log into Navisphere

Make a small LUN (200MB) named rm-proxy-## (ESX server number)

Map LUN to your ESX server

o Log into Virtual Center

Rescan the bus

Confirm the new device is discovered

o Add RDM to RM server

Assign the new device as an RDM to RMsrv-#

Select all defaults

o Log into RMsrv-# host

Rescan bus and confirm the new device

Initialize the drive

oLaunch and log into RM client

First login

Username=Admin

Password=

It will ask you to give a new password use emc123


15/44



Discover the Proxy host

Right click on Hosts and select New Host

Make the name your RM server name (RMsrv-#)

Check enable Vmware

o Type in your Virtual center host name

o Provide your VC username/password

Select OK and create the host account

Discover SnapCache

Right click on Storage Services and select Add Storage

Provide the Navi account info

Let the wizard run and then put a check mark in the snapcache box

Select ok

Make an application set

Right click on Application Sets and select New Application Set

Give the AppSet a name (such as vmfs-snap)

Click on the + next to the Servername and then drill into the VMWareVMFS option

Select your VMFS with the W2k3 server

Click through the Wizard

Make a Job (this wizard will automatically launch when you click finish on the

AppSet wizard)

Click next

Name the Job (ex. VMFS_Snap_job)

Under Replication Technology select Snapview Snap

o WARNING: if there are any options available other than

Clariion replication options, such as Invista Clones,

Timefinder or Snapsure, notify the instructor immediately

Click through to the mount options page


16/44



o Check the mount replica box

o Next to the mount host click on the

o Enter your ESX server name (esx-67-#)

o Click through the rest of the wizard and finish the job

Run the Job

o Switch to your Virtual Center Client screen

Remove your w2k3 VM from the Inventory

Right click on your w2k3 host and select Remove from disk

Confirm that the VM files are no longer on the VMFS filesystem

Select your ESX server and then the Configuration tab

On the let select storage

Right click on your VMFS and select Browse datastore

Confirm that there is no folder with you w2k3 server name

o Switch to your RM server screen

Un mount your snapshot

Under Application Sets select your AppSet

In the right pane right click on your most recent replica and select

UnMount

Restore your snapshot

Right click on your most recent replica and select restore

Click next and then place a check in the box next to your replica

Click through and run the restore

o Switch to your Virtual Center Client

Re-Add your recovered VMs to the Inventory

Browse the restored datastore and confirm that your VM folder is

back

Open the folder and find the .vmx file


17/44



Right click on the VMX file and select Add to Inventory

Give the host the SAME NAME as the original host

Select your datacenter

Click next

Select your ESX servername

Click next

Click finish

Start your recovered virtual machine

You will get a pop-up asking if you want to create a new identifier.

Select Create. This is harmless.

Note: This pop-up will not occur if the replica had never been

mounted.

Lab 2 Replication Manager Virtual Machine Level Recovery

VM Started

o RMserver

Procedure

o Note: Lab 2 must be completed for this lab to work


Delete your w2k3-# directory off of the WindowsVMs-# datastore

First Confirm that w2k3-# is shut down

Next select your ESX server and then the Configuration tab

On the left select storage

Right click on WindowsVMs-# datastore and select Browse

Datastore

Remove the win2k3-# directory

Confirm the w2k3-# cannot start


18/44




Mount your snapshot



Mount

Click through wizard (confirm that the mount host is your ESX

server)


Recover your VM files

Open your WindowsVMs-# datastore

Open your snap-0000000#-WindowsVMs-# datastore

Right click on the w2k3# folder and select move

Select the WindowsVMs-# datastore

Start w2k3-#




19/44




Part 2: Replication Manager Virtual Machine Level Recovery

Step Action

1 VM Started

o RMserver

Procedure


Delete your w2k3-# directory off of the WindowsVMs-# datastore

First Confirm that w2k3-# is shut down

Next select your ESX server and then the Configuration tab

On the left select storage

Right click on WindowsVMs-# datastore and select Browse

Datastore

Remove the win2k3-# directory

Confirm the w2k3-# cannot start


Mount your snapshot



Mount

Click through wizard (confirm that the mount host is your ESX

server)


Recover your VM files


20/44



Open your WindowsVMs-# datastore

Open your snap-0000000#-WindowsVMs-# datastore

Right click on the w2k3# folder and select move

Select the WindowsVMs-# datastore

Start w2k3-#




21/44



Lab Exercise 10: CLARiiON Data Replication

Part 1: Data Migration with Incremental SAN Copy

1 IN THIS LAB EXERCISE PART, YOU WILL EXECUTE A SERIES OF ESXSERVER AND CLARIIONCOMMANDS TO REMOTELY REPLICATE VIRTUAL MACHINE DATA RESIDING ON A VMFS-3VOLUME USING INCREMENTAL SANCOPY.THIS SIMULATES A DATA MIGRATION ENVIRONMENT.

This lab section examines ESX Server and CLARiiON data replication using Incremental SAN Copy.Before you start the lab, please read and follow the note below.

Note Ensure that the LVM Parameters are at their default values using the Advanced Settingsoption from the Configuration tab for your ESX Server. Confirm that LVM.EnableResignature isturned off, and LVM.DisallowSnapshotLUN is turned on for your ESX Server. Check with yourpartner group to ensure that their settings have also been adjusted correctly.

Perform each of the operations indicated in this lab and verify that the output of thecommand, or the result of the operation, matches the intended output or result.

2 CREATE A FILE IS ON THE VMFS-3 VOLUME

Note The file will help you verify that the SAN Copy operations have completed successfully.a) Open Windows Explorer on your WinVM1. Right-click inside on E Drive: and create a file called

SANCopy1.txt. Insert some text data in the file. Delete any other files on the volume.b) Open the file with Notepad, and verify that the content is readable.

3 CREATE AND START THE SANCOPY SESSION

a) On your partner CLARiiON, add the LUN labeled Team x SAN Copy Dest LUN (where x is thenumber of your team) to the Storage Group labeled for SAN Copy use. Note the LUN number ofthe Destination LUN________.

b) Identify the LUN with label Team x WinVM1 App LUN. Right-click on the LUN from NavisphereManager. Choose SAN Copy > Create Session from LUN Name the Session ISC_x,where x is the LUN ID of the Team x WinVM1 App LUN. Ensure that the correct LUN isselected. Choose Incremental for the session type.

c) Choose your partner CLARiiON for the Destination storage system, and choose the LUN

labeled Team x SAN Copy Dest LUN (from step a) as the Destination LUN. Ensure that aninitial synchronization will be performed, and that the Throttle is set to 10. Link bandwidth shouldbe set to 2048.

d) Right-click the new Session, and choose Start

4 ASSIGN THE DESTINATION LUN TO THE SECOND VM ON YOUR PARTNER ESXSERVER (WINVM2)

a) Add the SAN Copy Destination LUN to the Storage Group associated with your partner ESXServer. Note the Host LUN ID for this LUN _________.

b) From the VI client, perform a Rescan from your partner ESX Server, Configuration tab,


22/44



Storage Adapters option. The new LUN should be visible once the rescan operationcompletes.

c) In Navisphere Manager, right-click the LUN you added to the Storage Group in step (a), andchoose Update Host Information When the operation completes, the LUN status shouldshow the ESX Server volume address, e.g.vmhba0:0:1. Note this value ___________.

Q. Is the VMFS Volume visible from the Storage display?

_________________________________________________________________________

d) From the Advanced Settings option in the VI Client, and the LVM display, setLVM.EnableResignature to 1 (or true) and repeat the Rescan from step (b).

e) Add the LUN to the second VM on your partner ESX Server (WinVM2), using the Summary tab,Edit Settings option. Assign it as an Existing Disk. Use the Browse button to locate the VMFS-3volume and .vmdk file.

Q. What do you notice about the volume name?

_________________________________________________________________________

f) Use the W2K3 Disk Management utility to view the WinVM2 disks on your partner ESX Server.The new LUN should be visible. If the new disk does not have a drive letter, assign one to it.

g) Verify that the file you created is visible from your partner WinVM2, and that the file content iscorrect.

5 ADD FILES TO THE VOLUME ON VM1

a) Open Windows Explorer on your WinVM1. Right-click inside the new volume (drive) you justcreated, and choose New > Text Document. Name the new file SANCopy2.txt.

b) Open the new file with Notepad, and insert some text. You should now have 2 text files in the

root folder of the volume visible to WinVM1.

6 INCREMENTALLY SYNCHRONIZE THE DESTINATION LUN

a) Deactivate the Destination LUN on your partner WinVM2 by removing the drive letter fromWindows Disk Management

b) Right-click the SAN Copy Session, and choose Startc) Once the data transfer completes, add the drive letter back to the Destination LUN.d) Ensure that the new file is visible.

7 RESTORE THE ENVIRONMENT

a) Use the VI Client to remove the Destination LUN from your partner WinVM2. WinVM2 will needto be powered down to complete this operation.b) From Navisphere Manager, remove the Destination LUN from your partner ESX Server Storage

Group.c) Destroy the Session by choosing the Remove option from the Session right-click menu.d) From Advanced Settings in the VI Client, reinstate the default value of LVM.EnableResignature

(0).


23/44



Lab Exercise 10: CLARiiON Data Replication

Part 2: Disaster Recovery with MirrorView

1 IN THIS LAB EXERCISE PART, YOU WILL EXECUTE A SERIES OF ESXSERVER AND CLARIIONCOMMANDS TO REMOTELY REPLICATE VIRTUAL MACHINE DATA RESIDING ON A VMFS-3VOLUME USING MIRRORVIEW/S.THIS SIMULATES A DISASTER RECOVERY ENVIRONMENT.

This lab section examines ESX Server and CLARiiON data replication using MirrorView/S.MirrorView/S operations may make use of the optional Write Intent Log

Perform each of the operations indicated in this lab and verify that the output of thecommand, or the result of the operation, matches the intended output or result.

2 CREATE A FILE ON THE VMFS-3 VOLUME

Note The file will help you verify that the MirrorView operations have completed successfully.a) Open Windows Explorer on your WinVM1. Navigate to Drive C: and at the root of the C: drive

create a file named MV_C.txt. Insert some text data in the file. Repeat this exercise for Drive E.naming the file MV_E.txt.

b) From the Advanced Settings option in the Configuration tab for your ESX Server, confirm thatLVM.EnableResignature is turned off, and LVM.DisallowSnapshotLUN is turned on for your ESXServer. Check with your partner group to ensure that their settings have also been adjustedcorrectly.

3 CREATE AND SYNCHRONIZE THE MIRROR, AND PROMOTE THE SECONDARY IMAGE

a) Right-click the Team x WinVMs Boot LUN from Navisphere Manager. Choose MirrorView >Create Remote Mirror Name the Mirror Mirror_x, where x is the LUN ID of the Team xWinVMs Boot LUN. Ensure that the correct LUN is selected. Choose Synchronous for themirror type, and choose to use the Write Intent Log.

b) Right-click Mirror_x, and choose Add Secondary Image Select a LUN named Team x MVBoot LUN Dest as the Secondary image, where x is the number of your team. Note the LUNnumber of the Secondary Image LUN. Ensure that an initial synchronization will be performed,and that the Synchronization Rate is set to High. Recovery Policy should be set to Automatic

(the default).c) Perform the same operations for your Team x WinVMs App LUN, selecting Team x MV App

LUN Dest as the Secondary Image.d) From your WinVM1, flush the host buffers for the C: drive and E: drive. Perform the same

operation for your WinVM2 C: drive.e) Allow the Mirrors to synchronize. This will take a minute or two.f) Power down your WinVM1 and WinVM2 virtual machines. Remove all hard disks from both

VMs.g) When the mirrors have finished synchronizing (both should indicate that they are in the

Synchronized state), promote the Secondary Images.


24/44



Q. Are the primary images now on the remote (partner) CLARiiON?

_________________________________________________________________________

Q. Are the mirrors synchronized and in a normal state?

_________________________________________________________________________

4 ASSIGN THE NEW PRIMARY IMAGES TO YOUR VMS

a) Add the new Primary Images to the Storage Group associated with your partner ESX Server.b) From the VI client, perform a Rescan from your partner ESX Server Configuration tab,

Storage Adapters option.

Are the mirrors synchronized and in a normal state?

_________________________________________________________________________

c) From the Advanced Settings display in the VI Client, set LVM.DisallowSnapShotLUN to 0(false).

d) Perform a rescan from your ESX Server. The new LUNs should be visible once the rescanoperation completes.

e) In Navisphere Manager, right-click the LUNs you added to the Storage Group in step (a), andchoose Update Host Information When the operation completes, the LUN status shouldshow the ESX Server canonical address, e.g.vmhba0:0:1. Note this value for each LUN

________________.f) Add the boot LUN to your WinVM2, and add the boot LUN and application LUN to your WinVM1

using the Summary tab, Edit Settings option. Assign the volumes with the Existing Disk option.

Use the Browse button to locate the VMFS-3 volumes and .vmdk files.

Q. What do you notice about the volume names? If they are not identical to the volume namespreviously assigned to your WinVM1 and WinVM2, why is this the case?

_________________________________________________________________________

g) Use the W2K3 Disk Management utility to view the new disks on WinVM1 and WinVM2. Assigndrive letters if required. The volume labels should be the ones originally assigned to the LUN.

h) Verify that the file you created on the application disk is visible from WinVM1, and that the filecontent is correct.

5 ADD FILES TO THE VOLUME ON WINVM1

a) Open Windows Explorer on your WinVM1. Right-click inside the C: drive volume you created,and choose New > Text Document. Name the new file MV2_E.txt. Repeat this exercise fordrive E.

b) Open the new files with Notepad, and insert some text. You should now have 2 text files in theroot folder of the application volume visible to WinVM1.

6 FLUSH THE HOST BUFFERS, AND ALLOW THE MIRRORS TO SYNCHRONIZE

a) Flush the WinVM1 and WinVM2 host buffers. Either admsnap or admhost can be used to


25/44



perform this operationb) Ensure that the Mirrors are synchronized.

7 PROMOTE THE MIRRORS

a) Ensure that the Mirrors are synchronized.b) Right-click the Secondary images, and choose Promotec) The primary images should now be on your CLARiiON

Q. Was there a potential problem with consistency during this operation? Why/why not?

_________________________________________________________________________

Q. If you were dealing with multiple LUNs associated with an application, what would you do?

_________________________________________________________________________

9 REACTIVATE THE VMFS VOLUME

a) Use Windows Disk Management on your WinVM1 and WinVM2 to add drive letters to theVMFS_AppDisk1 volume and the boot volumes

b) Ensure that files, including the new file you created, are visible on the volumes

10 RESTORE THE ENVIRONMENT

a) From Navisphere Manager, remove the secondary mirror images from your ESX Server StorageGroup.

b) Destroy the Mirrors by fracturing the Secondary Images and removing them, then choosing thedestroy option from the mirror right-click menu.


26/44



Lab Exercise 11: Site Recovery Manager

Part 1: Disaster Recovery with SRM

1

St. Louis Lab configuration

(2) Virtual Center 2.5 Servers

(2) ESX 3.5 servers Celerra Simulator 5.6

1 loaded on each ESX server

Converted from VMware workstation image

Storage (not required for Celerra demo) CX3-20

CX700


27/44



2

3 Lab Diagram

VirtualCenter1 VirtualCenter2

ESX1 ESX2

CelerraSIM 1

CelerraSIM 2

iSCSI Lun iSCSI LunReplicatorV2

Win2k3 VM

Production DR Site

Note: The iSCSI

lun is presented to

the ESX server,

thenformattedVMFS. The VM

was created on

this datastore

Celerra Configuration

8GB lun created on primary Celerra Replicated to remote Celerra using nativeiSCSI replication via ReplicatorV2

iSCSI lun from primary Celerra wasmasked to the production ESX server

iSCSI lun from remote Celerra (replicationtarget) was masked to the DR ESX server

Formatted VMFS iSCSI lun on production.Loaded win2k3.


28/44



4

5

Active VM on Production Side

VM is built on Celerra iSCSI lun presented to ESX and formatted as a VMFS datastore

Verify Replication

Either from the GUI or CLI nas_replicate list- All ReplicatorV2 sessions are managed through the nas_replicate command


29/44



6

7

Configure SRM on Production

1. Make connection with remote site

2. Configure Arrays3. Verify Inventory Mappings

4. Create Protection Groups

* You will configure your Recovery Plan onthe remote site

Install SRM components

1. Install SRM

2. Install SRA

- Restart VMware Site Recovery Managerservice after installing plugins

3. Install/enable SRM plugin from within VC

* Install on both VirtualCenter servers


30/44



8

9Configure Arrays

This is where SRM interacts with the Celerra SRA scripts

- Add the source Celerra CS IP and login credentials

Connect to remote site

Enter DR VirtualCenter site IP and credentials.


31/44



10

11

Verify the datastores are found on the source array

- Add the Destination Celerra CS IP and login credentials


32/44



12

13

Configure Protection Group(s)

Create Protection group(s) on the primary site- 1 protection group per datastore

Inventory Mappings

Verify/Configure Inventory mappings for the local site


33/44



14

15 Select remote datastore for placeholderconfiguration

A placeholder is created on the DR site, select the local datastore on the DR site to

accommodate the configuration files.- The VM is added to the DR sites inventory

Select desired datastore group


34/44



16

17

The recovery priority determines the order in which the VMs are brought up on the DR site

Machine priority can be changed

Low

Medium

High

Dont Power On

* Edit the virtual machines settings from

within the protection group


35/44



18

19

Create a name for the Recovery Plan

Remote Site Configuration

Configure Recovery Plan

Select protection groups from protected site

Run Recovery Plan

For demonstration purposes


36/44



20

21

Response times

If VMware tools is installed

This field defines how long to wait after the firstmachine in the plan to powers on before proceeding

to the next virtual machine in the plan.

Maximum time to wait for a response

If the first virtual machine in the recovery plan fails to

signal that it has powered on, this field defines themaximum length of time to wait before proceeding tothe next machine in the recovery plan.

Select Protection Groups

You may select multiple Protection Groups (created on the primary site)


37/44



22

23

Suspend machines at local DR site

May want to power off any test/development VMs to accommodate higher priority VMsduring an outage.

Set response times


38/44



24

25

Run Recovery Plan

Confirm that you wish to proceed running the Recovery Plan

Recovery Plan Demo Run

We will perform a failover with a live VM

No interaction is performed on the host VM

Lun masking has been performed on the RemoteCelerra, Remote site was presented read-only luns

Failback is manual

You can reverse the SRM configuration

OR

Manually failback replication and discover hosts/storage

Replication restart is manual


39/44



26

27

Host VM is forcefully powered off.

- The step fails due to in-proper shutdown

Wait for host shutdown timer.

* In our scenario, the remote host is not shutdown gracefully.


40/44



28

29

Powering on machine at Remote Site

The SRM powers on VMs in the included Protection groups- Will power on high priority machines first, then medium, and finally low priority VMs

Replication is failing over

The SRM uses the Celerra SRA to fail over the iSCSI replication session at the remoteCelerra


41/44



30

31

Windows starts up in crash-consistent mode

Timeouts are expected for our test, the VM was not shutdown properly and theProduction site was still running


42/44



32

33

Celerra Replication Status

Replication has been failed over to the remote Celerra by SRM

VM succesfully failed over and running onremote storage/ESX hardware


43/44



34

35

Confirm replication reversal

Start Replication

Reverse replication direction by starting replication from the remote Celerra

-This process is manual and can be done through the GUI or CLInas_replicate -start


44/44


36

End of Lab Exercise.

Replications are now active

nas_replicate -list

00 vmware saclass design lab final

Documents