MirrorView and SAN Copy Configuration and Management SRG R29

7/23/2019 MirrorView and SAN Copy Configuration and Management SRG R29

1/124

MirrorView and SAN Copy

Configuration and Management

Student Guide

EMC Education Services

November 2009


2/124


3/124

Copyright 2009 EMC Corporation. Do not Copy - All Rights Reserved.

2009 EMC Corporation. All rights reserved.

MirrorView and SAN Copy Configuration andManagement

MirrorView and SAN Copy Configuration andManagement

Welcome to MirrorView and SAN Copy Configuration and Management.


4/124


2009 EMC Corporation. All rights reserved. Course Introduction - 2

Revision History

Rev Number Course Date Revisions

3.24.0.1 January 2007 Complete

3.26.0.1 September 2007 Complete

4.28.0.1 September 2008 Complete

4.29 October 2009 Complete

4.28.5 February 2009 Complete

Copyright 2009 EMC Corporation. All rights reserved.

These materials may not be copied without EMC's written consent.

EMC believes the information in this publication is accurate as of its publication date. The information is subject tochange 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 , EMC, EMC ControlCenter, AdvantEdge, AlphaStor, ApplicationXtender, Avamar, Captiva, CatalogSolution, Celerra, Centera, CentraStar, ClaimPack, ClaimsEditor, ClaimsEditor, Professional, CLARalert,CLARiiON, ClientPak, CodeLink, Connectrix, Co-StandbyServer, Dantz, Direct Matrix Architecture, DiskXtender,DiskXtender 2000, Document Sciences, Documentum, EmailXaminer, EmailXtender, EmailXtract, enVision,eRoom, Event Explorer, FLARE, FormWare, HighRoad, InputAccel,InputAccel Express, Invista, ISIS, MaxRetriever, Navisphere, NetWorker, nLayers, OpenScale, PixTools, Powerlink, PowerPath, Rainfinity, RepliStor,ResourcePak, Retrospect, RSA, RSA Secured, RSA Security, SecurID, SecurWorld, Smarts, SnapShotServer,SnapView/IP, SRDF, Symmetrix, TimeFinder, VisualSAN, VSAM-Assist, WebXtender, where information lives,xPression, xPresso, Xtender, Xtender Solutions; and EMC OnCourse, EMC Proven, EMC Snap, EMC StorageAdministrator, Acartus, Access Logix, ArchiveXtender, Authentic Problems, Automated Resource Manager,AutoStart, AutoSwap, AVALONidm, C-Clip, Celerra Replicator, CLARevent, Codebook Correlation Technology,Common Information Model, CopyCross, CopyPoint, DatabaseXtender, Digital Mailroom, Direct Matrix, EDM, E-Lab, eInput, Enginuity, FarPoint, FirstPass, Fortress, Global File Virtualization, Graphic Visualization, InfoMover,Infoscape, MediaStor, MirrorView, Mozy, MozyEnterprise, MozyHome, MozyPro, NetWin, OnAlert, PowerSnap,QuickScan, RepliCare, SafeLine, SAN Advisor, SAN Copy, SAN Manager, SDMS, SnapImage, SnapSure,SnapView, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix DMX, UltraFlex, UltraPoint,UltraScale, Viewlets, VisualSRM are trademarks of EMC Corporation.

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


5/124



Course Objectives

Upon completion of this course, you will be able to:

Explain SAN Copy concepts

Configure and manage SAN Copy

Explain MirrorView/S and MirrorView/A concepts

Configure and manage MirrorView/S and MirrorView/A

Use EMC Navisphere Manager, Navisphere Secure CLI

and admhost in a practical environment

The objectives for this course are shown here. Please take a moment to review them.

NOTE: All information in both the slides and Appendix are used in the creation of examsto support the EMC Proven Professional Program. It is highly recommended ALL

materials be reviewed in preparation for the exams.


6/124



Course Introduction

This course is aimed at IT and support personnel who are or will: Manage CLARiiON remote replication with MirrorView or SAN Copy

Architect and position customer solutions with MirrorView or SAN Copy To understand the content and successfully complete this course, a

student should have knowledge and skills associated with the following: CLARiiON models, components, management options and features

Data integrity and availability features found in a CLARiiON storage platform

CLARiiON performance, storage configuration and provisioning concepts

PowerPath performance, transparent recovery and availability features in an opensystems host environment

SAN terminology, features, architecture, theory of operations, and managementincluding Fibre Channel and IP Storage networks concepts and EMC Connectrix

switches SnapView operation, terminology and performance

Basic MirrorView and SAN Copy operation

A list of specific prerequisite courses can be found in EMC Education ServicesLearning Management System

The course assumes the student has base knowledge and has met the prerequisites detailed

shown here. Please see PowerLink (http://powerlink.emc.com) for additional information on the

CLARiiON family of arrays.


7/124



Class Introductions

Name

Company

Region

Role

CLARiiON experience?

SAN Copy experience?

MirrorView experience?


8/124



The Environment

Locations

Restrooms

Cafeteria coffee

Network / Phone Access

Smoking Area

First Aid

Water cooler

Hours of Class

9:00am 5:00pm, please be on time Lunch

50 percent lecture 50 percent class exercises and labs

Mornings start with a lecture at 9:00 A.M. and there is an hour long break at lunch time, usually

taken at noon. There are also two 15-minute breaks, one taken in each of the morning and

afternoon sessions. The instructor will set the exact times at the beginning of class.


9/124



Classroom Etiquette

The following must not be in use during lecture:

Cell phones (set to vibrate if possible)

Laptops (must be closed during lecture)

PDAs

Other reading material

If the phone rings, answer it asyou step out of class

Food and drink allowed in classroom, but not lab

You must inform the instructor of any and all absencesfrom classroom sessions. Excessive absences will resultin non-certification. Also inform your lab partner


10/124



Agenda:

Day 1

Introduction

Module 1: SAN Copy and Incremental SAN Copy

Lesson 01 SAN Copy and Incremental SAN Copy Features

Lesson 02 Managing SAN Copy with Navisphere Manager

Lesson 03 Managing SAN Copy with Navisphere Secure CLI

Lesson 04 Using admhost with SAN Copy

Lab Exercise 1: Create and Test a Local SAN Copy Session

Lab Exercise 2: Create and Test a Remote SAN Copy Session

Lab Exercise 3: Create and Test an Incremental SAN Copy Session


11/124



Agenda:

Day 1 (continued)

Module 02 MirrorView/A and MirrorView/S

Lesson 01 MirrorView/S and MirrorView/A Features

Lesson 02 MirrorView Consistency Groups

Lesson 03 Managing MirrorView with Navisphere Manager

Lesson 04 Managing MirrorView with Navisphere Secure CLI

Lesson 05 Using MirrorView with SnapView

Lab Exercise 4: Create a Synchronous Remote Mirror

Lab Exercise 5: Promote and Test a Secondary Mirror Image

Lab Exercise 6: Create and Test an Asynchronous Mirror

Lab Exercise 7: Create and Test a MirrorView/A Consistency Group Lab Exercise 8: Create a MirrorView/A Mirror with the Navisphere TaskBar

MirrorView Wizard


12/124


13/124


2009 EMC Corporation. All rights reserved. Module 1: SAN Copy and Incremental SAN Copy - 1

Module 1: SAN Copy and Incremental SAN Copy

Upon completion of this module, you will be able to:

Configure and manage SAN Copy with NavisphereManager

Configure and manage SAN Copy with NavisphereSecure CLI

Use admhost in conjunction with SAN Copy

The objectives for this module are shown here. Please take a moment to read them.


14/124



Lesson 1: SAN Copy and Incremental SAN Copy

Features

Upon completion of this lesson, you will be able to:

Explain the features of SAN Copy and Incremental SANCopy

Discuss the requirements for using SAN Copy andIncremental SAN Copy in a CLARiiON environment

Remote Replication Enhancements

The objectives for this lesson are shown here. Please take a moment to read them.


15/124



Overview of SAN Copy and Incremental SAN Copy

Bulk data transfer

CLARiiON to/from CLARiiON, Symmetrix, and other vendor storage

Source LUN may be a point in time copy

SnapView Clone, SnapView Snapshot, Symmetrix point in time copy

SAN-based (FC or iSCSI) data transfer

Offloads host traffic no host-to-host data transfer

Higher performance less traffic

OS independent

Secure

Full or incremental copies

SAN Copy allows fast bulk transfer of data between CLARiiON and Symmetrix systems (other

vendor systems are not discussed here) over FC, and transfer between CLARiiONs over iSCSI.

The (full mode) SAN Copy Source LUN is likely to be a point in time copy because of the way

SAN Copy functions when full data copies are used. If Incremental mode is used, then the

source LUN may be the production LUN, and can be online.

Some of the key benefits supplied by the EMC SAN Copy software are shown here. One of the

key benefits is the off-load of host traffic, with an associated increase in copy performance. Data

is copied directly from one storage system to the other, with no host involvement in the copy

process. Copies can be performed without regard to the host operating system, again because no

hosts are involved in the copy. Because ownership of the logical units or volumes does not have

to be shared, host operating system security is not compromised.

SAN Copy requires no special software to be loaded on the peer storage systems. In addition,

unlike MirrorView/S, it does not use a special protocol. This makes SAN Copy efficient and

fast.


16/124



SAN Copy Requirements and Recommendations

A SAN Copy CLARiiON must be involved in any transfer

SAN Copy CLARiiON ports must be accessible toattached storage system ports

Navisphere Agent should be installed on any host thatowns Symmetrix SAN Copy volumes

Hosts that own Symmetrix volumes may need to be in aportal configuration

LUNs must be made available to SAN Copy ports

SAN Copy cannot share an SP port with MirrorView

Either the source logical unit, destination logical units, or both must reside on a SAN Copy storage

system, a CLARiiON running SAN Copy software.

You must correctly zone (for FC connections) or connect (for iSCSI connections) SAN Copy ports to

peer storage system ports in order for SAN Copy to have access to those systems.

In order for Navisphere Manager to provide the drive letter/file system mapping of participating

Symmetrix volumes, the Navisphere Host Agent must be installed on the hosts that own the volumes, and,

if that host is not also connected to a CLARiiON in the domain, it must be in a portal configuration. If

installing the host agent is not possible, the user may manually enter the WWN of the Symmetrix volume.

Another option may be to install the host agent for as long as is required to set up the SAN Copy

Sessions, then remove the host agent. The same may be done with the portal configuration.

You must make logical units participating in a SAN Copy session accessible to the participating SAN

Copy port; this will involve FC zoning or creating iSCSI connections as well as the use of LUN masking

software.

SAN Copy cannot share an SP port with MirrorView. Both SAN Copy and Incremental SAN Copy may

share ports with host I/O, though the performance impact must be carefully considered.

Zone or connect at least one port from each SP of the SAN Copy storage system to peer storage system

ports participating in SAN Copy sessions.

For FC connections, create a single zone that includes a SAN Copy port and multiple peer ports, create

multiple zones with a single SAN Copy port and a single peer port, or a create a mixture of both zone

types. For iSCSI connections, create the required connection sets.


17/124


If performance is the primary concern, zone or connect multiple SAN Copy ports to a peer

storage system. SAN Copy allows multiple sessions to share a single port, but, if there are

multiple ports available, SAN copy will spread multiple sessions across the available SAN Copy

ports to maximize total throughput.

You must make logical units participating in a SAN Copy session accessible to the participating

SAN Copy port.

Access Logix is required on the SAN Copy storage system and any other CLARiiON storage

systems involved in a SAN Copy session. A LUN masking method will need to be used on any

non-CLARiiON storage system participating in a SAN Copy Session.

The SAN Copy port(s) must be added to the storage group on the non-controlling CLARiiON.

This applies regardless of whether the LUN(s) on the non-controlling CLARiiON are used as

source or destination LUNs for a SAN Copy session.

San Copy ports display in Navisphere much the same as any attached host. The SAN Copy port

will be identified by the storage system name rather than the Storage Processor network name,

the owning Storage Processor, and also the ports World Wide Name.


18/124



SAN Copy Features

Multiple Sessions can run concurrently

A Session may have multiple destinations

Sessions can be queued, paused, resumed and aborted

Checkpoints are written at user-specified intervals

A throttle mechanism allows transfer speed adjustment

User can choose connection type

FC, iSCSI, or Fibre Preferred (which tries FC, then iSCSI)

Major features of SAN Copy include the ability to run concurrent sessions. This allows multiple

source LUNs to be simultaneously transferring data to multiple destination LUNs. The number

of Sessions running concurrently is set at the SP level, but will not exceed the limit for the

storage system model. See the Release Notes for the current limits for each model.

Queued SAN Copy sessions are sessions that have been created but are not active or paused;

typically, they are waiting for another Session to complete before they can start transferring

data, because the storage system is already actively transferring data for the maximum permitted

number of sessions. Note that queued sessions are marked (see explanation later), which implies

that COFW activity can be present for that session. Control over an active session is in the hands

of the administrator. It is possible to pause and later resume a session or abort a session before

completion.

The management tools allow the user full control to create and modify sessions as seen fit, and

to change certain Session parameters.

Checkpoints are written to disk at administrator-defined time intervals. The feature allows SAN

Copy to resume an interrupted session from the last checkpoint, rather than having to restart the

session from the beginning.

The speed of a SAN Copy transfer, and therefore the resources used by the SAN Copy session,

can be controlled through the use of a throttle value, which ranges from 1 (slow) to 10 (fast).


19/124


This is the only mechanism that will adjust transfer speed; setting the speed of the network to a

lower value than is actually available will not slow down the transfer rate.

SAN Copy allows simple user control over the connection type. A useful feature is the Fibre

Preferred option, which will try to use FC connections between the storage systems involved in

a session, then try iSCSI connections if no FC connections exist. Note that this does not implythat a session will automatically switch over from one connection type to another in the event of

a failure; the failover is a manual process.


20/124



Incremental SAN Copy Features

Incremental copy

Changed data tracked at 2 kB granularity; COFW still 64 kB

Data transferred at 2 kB granularity

Map of tracked changes stored persistently

Mark and Unmark operation

Affects state of ISC SnapView Session

Modify Incremental Copy Session Properties

Turn on/off incremental tracking

Link Bandwidth & Latency

Sync Required (full copy)

Resume to only failed destinations

Incremental SAN Copy only copies changes to the destination(s). Changes are tracked by means

of bitmaps, and, if required, a COFW process will be performed (both operations require that a

Reserved LUN is assigned to the Source LUN.)

Networks with speeds starting at T1 connections are supported. SAN Copy will perform a

certain amount of optimization, depending on network speed and latency.

Incremental SAN Copy shares the chunk size with SnapView, 64 KB, so that a COFW copies

64 kB of data to the Reserved LUN. When the changed data must be copied to the secondary,

only the 2 kB sub-chunks that have changed are actually copied. This makes the link

utilization much more efficient.

The mark and unmark processes start and end the point in time copy process; the tracking of

changes continues, though, and the ISC SnapView Session continues to run. SAN Copy is aware

of which copies have succeeded and can resume to failed destinations only.


21/124



Additional Features

ISC-specific statistics

Time last marked

Time copy started

Blocks to copy in next incremental update

Auto-Recovery (all SAN Copy Sessions)

SP Reboot

LUN trespass

Additional reporting functionality is present for Incremental SAN Copy. SAN Copy can recover

from SP reboots and LUN trespasses; the process is discussed later.


22/124



SAN Copy Parameters

Buffer size

Default 1024 blocks (512 kB), maximum 2048 blocks (1024 kB)

Number of buffers per copy Default 4, maximum 16

Number of Concurrent Copies per SP

CLARiiON model dependent

Copy Session initial contents

Source and Destination WWNs, Initial Throttle value, User-assigned name

Some contents can be modified

Destinations, Throttle value

Copy Session status

Completion status (success or nature of failure)

Time of completion

Number of consecutive blocks copied before failure

SAN Copy performance can be affected by some of the configurable parameters.

The default buffer is size is 1024 blocks, with a maximum size of 2048 blocks. This, inconjunction with the number of buffers per session, will have an effect on the overall

performance of a SAN Copy session.

The buffer size and number of buffers may be changed, but in the absence of detailed

performance analysis, should be left at the default values. Incremental SAN Copy will calculate

the required values for incremental sessions, based on link bandwidth and latency.

Performance is also affected by the number of concurrent copies. The contention for resources

will increase as the number of active copy sessions increases.

See the SAN Copy Release Notes for the latest information about SAN Copy limits.

The values stored in the PSM for when a session is created include both the source and

destination World Wide Names (Fibre) or IQNs (iSCSI) and the initial throttle value and session

name, both of which are user defined.

The throttle value and destinations (add/remove) may be modified after creation by the user. A

name is supplied by SAN Copy and may be changed at Session creation time.

After the session is started the first time, the PSM LUN entries for the session will be updated

with the completion status, the time of completion and, in the case of a failure, the number of

blocks transferred before the failure.


23/124



Host Buffer Issues

Most OS maintain buffers associated with data on LUNs

The host doesnt know when SAN Copy reads or writes aLUN, and doesnt flush or refresh the buffers

Most UNIX systems have mount/unmount/flushcommands which can be used to manage the buffers

Example: The Solaris sync command will flush host buffers

Windows has no such commands, so we supply a host-

based utility called admhost admhost commands are identical to three of the

commands supplied with admsnap, but with differentnames

The host buffer issues mentioned here are similar to those encountered when using SnapView;

some of the discussion may already be familiar to you.

When a SAN Copy session starts, the integrity of the Source LUN is vital. This can only be

guaranteed if the host has committed all write buffers to the source LUN.

On Unix systems this can be forced through the flush/unmount/mount commands. The unmount

command flushes host buffers, then unmounts the specified filesystem, making it inaccessible to

the host; the mount command makes the filesystem accessible through a specified mount point.

Unix hosts also have a sync command, which flushes host buffers without unmounting the

filesystem.

Windows hosts have no such commands, but a Windows host-based command line utility,

admhost, is provided with SAN Copy to accomplish these actions. Admhost is similar to the

Windows host-based command line utility, admsnap, that is provided with SnapView.


24/124



SAN Copy Session Creation Process Flow

Configure SAN Copy Connections

Not needed for local copy

Physical connections cabling and zoning must be in place

CLARiiONs in same domain, or multi-domain management in use

Portal configured if required

LUN masking configured

Create Session

Designate source storage system and LUN

Choose Session type Full or Incremental Designate destination storage system(s) and LUN(s)

Session Name

Throttle Value

The SAN Copy session can be set to copy data between 2 LUNs in a single CLARiiON, between

CLARiiONs, and between a CLARiiON and a non-CLARiiON storage system. While there are

many similarities when setting up these different sessions, there are also some differences. In

the interest of clarity, each of these session types will be covered in full. The creation of a SAN

Copy session involves a number of steps.

If the source and destination LUN(s) are located in different storage systems, the source storage

system must be connected to the destination storage system(s) as an initiator.

CLARiiONs in the same domain, or in different domains managed through Navisphere

Managers multi-domain management feature, can communicate with each other, and share

information about LUNs; all LUNs that may be used for SAN Copy purposes will be displayed

in the dialogs. If one of the storage systems is not a CLARiiON, then management will be vastlysimpler if a portal is configured, and the host that owns the LUNs or volumes used for San Copy

is added to the portal.

Access Logix, in the form of a Storage Group, will be used to perform LUN masking on the

CLARiiON, and make LUNs available to the SAN Copy CLARiiON. If the storage system is

not a CLARiiON, then LUN masking must be configured in the manner required by the storage

system vendor; Symmetrix systems, for example, will use the Volume Logix feature to perform

the masking.

The source LUN and destination LUN are easily selected. The destination must be at least aslarge as the source. Each session requires a unique name and the priority of copy traffic can be

set with the throttle value


25/124



Running an Incremental SAN Copy Session

User creates an Incremental SAN Copy Session

Default initial copy is a full copy

User quiesces (freezes) Source LUN

User starts the ISC Session (ISC marks the Session)

User unquiesces (thaws) Copy Source LUN

ISC Session completes (ISC unmarks Session)

Subsequent copies are Incremental

Start next ISC copy

Full copy to any new destinations

Incremental copy to existing destinations

The procedure for creation of an Incremental SAN Copy Session is shown above. The quiesce

helps to ensure consistency of the Source LUN data.

All copies following the first will be incremental. If an additional destination is added at any

time, a full copy will be performed to that destination only; subsequent copies will be

incremental.


26/124



SAN Copy Operation

SP port becomes an initiator (looks like an HBA to SAN)

Source LUN should be read-only during full copy Can be a point in time copy

Source LUN may be R/W for ISC Sessions

Read from Source LUN, write to destination(s)

Start n reads from Source LUN (n = # Buffers)

When any read completes, write to destination

When any write completes, start another read

For SAN Copy to operate correctly, the Storage Processor port must become an initiator and

register with the non-SAN Copy storage system.

While a full copy session is operational, the source LUN should be put into read-only mode. If

this is unacceptable, a Snapshot, Clone, or other point in time copy can be created from the

source LUN and used as the source for the SAN Copy session.

Data is read from the source and written to the destinations. SAN Copy will initiate a number of

reads equal to the number of buffers allocated for the session.

When any read to the buffer is complete, SAN Copy writes the data to the destination LUN.

When the write is complete and the buffer is empty, SAN Copy refills the buffer with another

read from the source.


27/124



Create/Start Model

User creates and stores a Copy Session for each copyoperation

SAN Copy stores Copy Session parameters persistently

SAN Copy assigns Session an ID that is unique acrossboth SPs

Once stored, Session can be started any number of times

After first start, Session also contains status of most

recent completion

Each Session is specific to one SP

It cannot be started on the peer without transferring it

When the user creates a SAN Copy session, the SAN Copy software stores that information

persistently in the PSM LUN. It is the softwares responsibility to create a unique identifier for

the session and this ID must be unique in the storage system. After the session is created and

stored it may be started any number of times. The sessions status will be updated upon each

completion, after it is started for the first time. When creating a Session, an owning SP is

specified and the Session cannot be started on the peer SP without first transferring the Session

to the peer SP; this is a manual operation.

Note that once a Session has been created, domain and portal information is no longer required

by SAN Copy, and the domain and/or portal may be removed.


28/124



SAN Copy Failover

Sessions do not automatically failover

If the owning SP fails or the Source LUN is trespassed, the Session

fails

If a Destination SP fails or destination LUN is trespassed, theSession terminates (to that destination)

Sessions can be manually transferred to the peer SP

Only if not active

Once transferred, they may be manually started or resumed

The Session start fails unless the SP it is transferred to has

connectivity to the destination SP, and access to the source anddestination LUNs

They do not automatically transfer back when the failure is rectified

When a source LUN is not available through the sessions owning Storage Processor, the session

will fail. This will happen if the Storage Processor fails or the Source LUN is trespassed to the

peer Storage Processor.

The Session may be manually transferred from the owning SP to the peer SP only if the Session

is not active, possibly because it has failed. Because the Session has failed, it must be manually

restarted or resumed from the last checkpoint. Before the Session can be started on the peer SP,

the same restrictions apply to the peer as to the original owning SP, namely that the peer SP

must have connectivity with the destination SP and access to both the source and destination

LUNs.


29/124



Incremental SAN Copy and SnapView

SnapView tracks changes (persistently) and providesMark/Unmark capabilities

ISC requires SAN Copy and SnapView to be licensed

SnapView licensed for system use

SAN Copy licensed for user

On SAN Copy storage system (not non-controlling system)

SnapView Integration presented through SAN Copy UI

SnapView usage somewhat hidden to user Automatic creation of Snapshots and SnapView Sessions during

SAN Copy Session creation

Requires prior provisioning of Reserved LUNs

Produces SnapView error messages

Though SnapView is required for Incremental SAN Copy use, it is largely hidden from view

when used as part of SAN Copy. The SAN Copy software will automatically license SnapView

for internal use; a user SnapView license is not required to take advantage of ISC features.

Snapshots and Sessions used by SAN Copy are treated as private, or reserved, and cannot be

managed by the user. If the SnapView UI is licensed for use, then the SnapView objects are

visible to the end user, but not manageable.


30/124



ISC SnapView Snapshot

Modified SnapView Snapshot always activated

Created for and used by Incremental SAN Copy Session Name = SANCopy_

Counts as one of the 8 maximum Snapshots allowed perSource LUN

Displayed to user as protected

Cannot be a Storage Group member

SnapView management operations prohibited

Destroyed with Incremental SAN Copy Session or whenIncremental feature is turned off

SAN Copy uses a Snapshot as shown. It is treated as private and not manageable by the user,

though it is visible to the user if the SnapView UI is licensed.


31/124



ISC SnapView Session

Associated with ISC Snapshot

Name = SANCopy_

Modified SnapView Session - always Persistent

Counts as one of the 8 maximum Sessions allowed perSource LUN

Operates in one of two modes

Marked (tracks changes and performs COFW)

Unmarked (only tracks changes)

Destroyed with Incremental SAN Copy Session or whenIncremental feature is turned off

Not user-manageable

Sessions are treated in a similar way. Sessions and their Snapshots will be destroyed when a

Session is destroyed, or when the user disables the incremental feature for a SAN Copy Session.

This means that the Reserved LUN allocated to the ISC Session when it is created will not be

released until the Session is destroyed, or the incremental feature turned off. Note that the

modified SnapView Session used by ISC never stops, even if errors such as a full Reserved

LUN Pool occur.


32/124



DeltaMaps

Bitmaps used for tracking changes for incrementalupdates (maintained by SnapView)

Stored in Reserved LUN (persistent)

One pair per Incremental SnapView Session

Transfer - contains changed chunks for current update cycle

Tracking - used for tracking changes for next update cycle

DeltaMap roles are swapped during mark

DeltaMap data is merged during unmark

64 kB COFW granularity

Transfer granularity is 2 kB

DeltaMaps are discussed in the animated slides, and their usage is illustrated there. Note that the

merging of DeltaMaps means that all bits that are set (in a 1 state) are copied to the tracking

DeltaMap.

The difference between the size of the COFW granularity and transfer granularity means that

ISC uses the link efficiently.


33/124



ISC Internal Operation

User creates an ISC Session

SnapView bound into Source LUN stack

ISC SnapView Session started

Sufficient Reserved LUN Pool space must be available for tracking

ISC SnapView Snapshot created/activated

User marks ISC Session (or Auto Mark occurs)

SnapView swaps DeltaMaps, starts COFW

User unmarks ISC Session (or Auto Unmark occurs)

SnapView merges DeltaMaps, stops COFW

Clears Reserved LUN Pool entries (COFW data)

Much of the Incremental SAN Copy operation revolves around the use of SnapView, as shown

above. The operations are user transparent, though the SnapView objects are visible to the user.

The Reserved LUN must be at least 0.2% of the size of the Source LUN. If it is not, there is

insufficient space for the map area, and Navisphere will not allow the ISC session to start. An

error message will be displayed upon this failure.


34/124



ISC Internal Operation (continued)

User starts ISC Session

SAN Copy bound into ISC Snapshot stack

SnapView fills read buffer with appropriate data

SAN Copy copies data to destinations

Incremental Copy Session Completes

Auto Unmark (no more COFW, but still tracking changes)

User removes ISC Session

ISC SnapView Session stopped (destroyed)

ISC Snapshot destroyed

SnapView potentially unbound from Source LUN stack

The notes above are a continuation of the previous slide, again illustrating the close relationship

between SAN Copy and SnapView.

Note one important change, introduced in Release 19, the COFW process uses chunks which are

64 kB in size, as is the case with a normal SnapView Session. Data to be transferred across the

link, however, is tracked in 2 kB extents. This means that only the 2 kB extents which actually

changed, and therefore caused the COFW, will be transferred. This enhancement allows the link

to be used more efficiently.

When an ISC Session is removed (destroyed), SnapView will be unbound from the Source LUN

stack if no ordinary SnapView Sessions are running on that Source LUN.


35/124



ISC Restrictions

Failed destination(s) can only resume or remove

Modify ISC Session Cannot change ISC Session name or Source LUN Cannot clear Initial Sync Required property Cannot set Initial Sync Required property if marked

Mark or unmark ISC Session No failed destinations Cannot mark if ISC Session not allowing COFW

Start ISC Session

No failed destinations Add destination

Session must be unmarked

No failed destinations

Snapshots of Snapshots are not allowed, which means that the Source of an Incremental SAN

Copy operation may not be a Snapshot. It may, however, be a Clone or a FLARE LUN.

The Snapshot and Session used by an ISC Session is private, and therefore not user manageable.

Because of the incremental nature of ISC, it requires that all destinations be in the same state

before updates can occur, hence the restrictions shown above.


36/124



Failures and Trespasses

Trespass ISC Copy Source LUN

ISC SnapView Session and SnapView Snapshot trespassed

ISC Session is NOT trespassed Manually transfer ISC Session, then manually resume ISC Session

SP Failure

No auto-trespass of ISC Session

SAN Copy Session auto resumed on SP reboot

Destination Failure

Continue copying to non-failed destinations

Resume copies to failed destinations, or remove destinations

Reserved LUN Pool Errors

COFW error

Active ISC Session fails, and SnapView Session becomes unmarked

Continue tracking changes in DeltaMap

Trespasses of a Source LUN cause the SnapView portion of ISC to trespass, but do not affect the

SAN Copy portion of the ISC session.

Failed destinations need to be brought to the same state as other destinations before incremental

updates can be made, as noted earlier. If they cannot be updated, then removing them from the

destination list is the only other choice.

Errors related to the Reserved LUN Pool are generally related to incorrect provisioning of space.

Note that unlike standard SnapView Sessions, these sessions do not terminate if they run out of

space in the RLP; instead, the COFW process is terminated (and the resources freed up), but

tracking of changes continues.


37/124



Auto Recovery on an SP Reboot

On an SP reboot SAN Copy will automatically try toresume copy sessions failed due to SP failure, every 180seconds up to 5 times

The copy sessions will be marked failed due to SP rebootif SAN Copy is unable to recover them after the 5 retries

The copy session status will indicate auto-recoveryprogress with this message

Auto Recovery of a copy session is in progress

The only operation that can be performed on a copysession with auto-recovery in progress is STOP

An SP may become unavailable because it has rebooted or because it has failed.

SAN Copy tries to ensure that a Session will survive an SP reboot by allowing sufficient timefor a reboot to have completed before finally giving up, and calling a failure. During the period

it allows, 15 minutes, it will try to resume the session by retrying 5 times at 3 minute intervals.


38/124



Remote Replication Enhancements San Copy

Enhancement Benefits

Replication Roles

Provides fine-grained access control of replication tasks

Roles: Local Replication, Replication, and ReplicationRecovery

Roles can have local or global scope

Replication Limits Doubled SnapView SnapShot / SAN Copy limits

New 8 Gb/s and 10 Gb/s I/O Module

GUI / VirtualProvisioning

Thin Replication is applicable with SAN Copy

SAN Copy wizard has changes to support Thin LUNs

Dialogs that help to configure SAN Copy now allow ThinLUNs/Thin Pools as options when applicable

Menu actions for Thin LUNs will include SAN Copyactions

In FLARE Release 29, a new set of replication roles have been developed to provide the

customer with greater control of CLARiiON array replication. These roles are:

Local Replication - which provides SnapView operations only (no recovery) a role that

would restrict someone to start/stop SnapView operations

Replication - which provides SnapView, MirrorView, and SAN Copy operations (no

recovery)

Replication Recovery - which provides SnapView, MirrorView, and SAN Copy operations

plus recovery

These replication roles can have local or global scope. In order to assign a global scope to a

user, all systems in the Domain must be running FLARE release 29. LDAP role mappings are

also supported. Replication roles can see (but not manage) objects outside of their control. Thisnew feature facilitates coordination of user access to data and operations. It also introduces a

finer granularity of security.

Replication Limits have doubled SnapView SnapShot / SAN Copy limits in Flare 29.

Changes have been implemented to the Navisphere GUI for the SAN Copy wizard to support

Thin LUNs. Dialogs that help to configure SAN Copy now allow Thin LUNs/Thin Pools as

options when applicable. Menu actions for Thin LUNs will include SAN Copy actions.

Thin Replication is applicable with SAN Copy.


39/124



Security New Replication Roles: Flare 29 & Higher Provides fine-grained access control of

replication tasks:

Local Replication SnapView operations only

(no recovery) Replication SnapView, MirrorView, and SAN

Copy operations (no recovery)

Replication Recovery SnapView, MirrorView,and SAN Copy operations plus recovery

Replication roles can have local or globalscope

In order to assign a global scope to a user allsystems in the Domain must be running Flare 29or above.

LDAP role mapping also supported Replication Roles can see (but not manage)

objects outside their control

Ensures that the view is not restricted

Facilitates coordination of user access to dataand operations

Replication Roles

Three new roles were introduced in FLARE 29 to provide fine-grained access control of

replication tasks:

Local Replication SnapView operations only (no recovery)

Replication SnapView, MirrorView, and SAN Copy operations (no recovery)

Replication Recovery SnapView, MirrorView, and SAN Copy operations plus recovery

Global Replication roles are only supported in a complete FLARE 29 environment, meaning all

arrays in the domain must be at FLARE 29. Global Replication roles (or LDAP mappings

thereof) cannot be created in domains that contain Pre-FLARE 29 systems. You must first

remove all Pre-FLARE systems from the domain. On the same note, Pre-FLARE 29 systems

cannot be added to domains that define global replication accounts. You would have to first

remove all global replication roles and LDAP replication mappings.

Note: All previous security roles are still in effect in Flare 29.


40/124



LocalReplication Replication Replication/RecoverySANCopyStartasession No Yes YesStopasession No Yes YesPauseasession No Yes YesResumeasession No Yes YesMarkasession No Yes YesUnmarkasession No Yes YesVerifyasession No Yes YesThrottleasession No Yes Yes

Replication Roles San Copy Operations

The chart shown here describes the Replication Roles for San Copy Operations.


41/124



SAN COPY Increased Replication Limits

CX4-120 CX4-240 CX4-480 CX4-960R28 R29 R28 R29 R28 R29 R28 R29

SAN CopyIncremental SAN Copy Sources 128 256 128 256 256 512 512 512

CX4-120 CX4-240 CX4-480 CX4-960

R28 R29 R28 R29 R28 R29 R28 R29

SANCopySANCopyDestinationspersource 50 50 50 50 100 100 100 100ConcurrentSANCopySessionsperarray

8 8 8 8 16 16 16 16

IncrementalSANCopySessionsperSource

8 8 8 8 8 8 8 8

Replication Limits NOT Increased

Replication Limits with FLARE 29

Doubled SnapView snapshot limits, and by extension, SAN Copy

Expands usage of SnapView and SAN Copy

Limits not increased on CX4-960


42/124



8 Gb/s FC and 10 Gb/s iSCSI I/O Module

SAN Copy SAN Copy

Greater bandwidth Sequential I/O

Large Block I/O

10 Gb/s 8 Gb/s

IP SAN FC SAN

8 Gb/s

10 Gb/s

In 8 Gb/s or 10 Gb/s point-to-point environments IOPS processing can be similar to 4 Gb/s or 1

Gb/s environments. Certain replication products may be able to take advantage of this increased

bandwidth an thus increased IOPS processing speed.

The nature of the I/O (sequential vs. random) and (large vs. small block) will affect how much

IOPS processing increases can be achieved. SAN Copy processing has the most to gain simply

because of how it functions. Full or Incremental SAN Copies are in effect sequential I/O

operations which could be large block in nature. For example, a hospital using SAN Copy is

storing medical imaging data for backup. The larger 8 Gb/s or 10 Gb/s bandwidth could provide

significant improvement in IOPS performance.


43/124



Virtual Provisioning & San Copy: Planning and

Design

Supported with SAN Copy in FLARE 29

Where does Thin Replication apply? Ideally where both the source and destinations are Thin

Permits mixed LUN types for added flexibility

Traditional LUN > Thin LUN

Thin LUN > Traditional LUN

The exception to this case is Pull copies

Where the source is on the remote array, the Copy will not beprovisioned as Thin

SAN Copy can only perform a traditional copy when the source islocated on a remote system

In CLARiiON FLARE Release 29, support has been added in SAN Copy to support thin LUNs.

SAN Copy thin replication applies when both the source and destinations are thin LUNs. The

exception would be pull copies where the source is on the remote array the copy will not be

provisioned as Thin LUN. SAN Copy can only perform a traditional copy when the source is

located on a remote system.

The ideal combination for using Virtual Provisioning with SAN Copy is to have source and

destination be thin LUNs. The following scenarios will result in a fully provisioned Thin LUNwhich could be an undesirable circumstance:

1st scenario - when creating a copy session with Traditional source LUN and a Thin LUN

destination.

2nd scenario - when creating a PULL copy session. 3rd scenario - when creating a copy session with Thin destination on pre-R29 array


44/124



Virtual Provisioning & San Copy Wizard changes SAN Copy wizard supports Thin LUNs (R29)

If the destination array (and theSource array) support SAN Copy onThin LUNs, then Thin LUNs will showup as a destination possibilities

Thin LUNs will nowbe an option for aSAN Copy source

For the Navisphere GUI, the SAN Copy wizard has changes to support Thin LUNs. Dialogs that

help to configure SAN Copy now allow Thin LUNs/Thin Pools as options when applicable.

Menu actions for Thin LUNs will include SAN Copy actions.

For the Navisphere CLI, no changes to sancopy Secure CLI command syntax.


45/124



Lesson 2: Managing SAN Copy with Navisphere

Manager


Configure SAN Copy objects with Navisphere Manager

Manage SAN Copy objects with Navisphere Manager

The objectives for this lesson are shown here. Please take a moment to review them.


46/124



Configuring SAN Copy Connections

Before you can use SAN Copy to copy data between storage systems, SAN Copy ports must have access toparticipating logical units in the peer storage systems. To make this happen, you must register each selected SAN

Copy port to ports of the peer storage systems. Once the registration process is complete, you can connect the SANCopy port to a Storage Group on the peer CLARiiON storage system.

Each SAN Copy port acts like a host initiator and, therefore, can connect to only one Storage Group at a time in astorage system.

To select available ports, do the following:

In the Storage tree, navigate to the storage system in which the Storage Group to which you want to connect(the peer) resides, and double-click the storage system icon.

Expand the Storage Groups icon, right-click the icon for the Storage Group to which you want to connect, andthen click SAN Copy > Connections

The SAN Copy Connections dialog box opens.

In SAN Copy System, select the storage system/SP entry that includes the SAN Copy port you want to connect

to the Storage Group. Ports to connect lists all available SAN Copy ports for the selected SAN Copy storage system and SP.

SAN Copy displays only those SAN Copy ports that are in the same zone or connection group as the SP portsof the Storage Groups storage system.

Select all the SAN Copy ports that you want to connect to the selected Storage Group, and click OK.

The storage group in the destination storage system should display the established SAN Copy connections inaddition to the hosts and LUNs in the storage group.

The Tools > SAN Copy > Connections Summary option will also show all current SAN Copy connections.

Note iSCSI connections will appear here as well. A Fibre preferred connection will search for a fibre connectionpath to the remote LUN first and an iSCSI connection path second.


47/124



SAN Copy Settings

The SAN Copy > Settings option allows configuration of the number of concurrent sessions

per SP, number of buffers per session, buffer size, and checkpoint interval.

The memory configured here will be used by SAN Copy when running full as well as

incremental sessions. Note that the buffer size, by default 512 kB, ( 1024 blocks) is smaller than

the default LUN write-aside value, which means that SAN Copy writes will hit write cache.

Note: The Cache Write Aside Size sets the size of the largest write request (in blocks) that will

be stored in write cache prior to being written to disk. Write requests that are less than or equal

to this value are written to cache. Write requests that are larger than this value are written

directly to disk. Valid values are 16 through 65534. For example, if the cache write aside size

has been set to 1023, all write requests equal to or less than 1023 will be written to cache. Write

requests larger than 1023 will be written directly to disk.


48/124



Session Creation Wizard Start

To create a CLARiiON to CLARiiON SAN Copy session, right-click the storage system on

which you want to create the session. This storage system must have the SAN Copy software

installed, click SAN Copy, and then click Create Session.

The first wizard screen to appear is a summary of the steps the wizard will take the user through

in the creation of the session. Read the wizard summary and click Next.


49/124



Choose Session Type

The Select Session Type window lets you select the type of session; full copy or incremental

copy.


50/124



Select Source LUN / Volume

The Select Storage Sources window lets you select the source storage from which you want to

copy data. If the Session is an Incremental Session, only a CLARiiON may be a Source storage

system.

If the storage system containing the source LUN/volume runs EMC SnapView or EMC

TimeFinder, SAN Copy can use a snapshot or clone/BCV as its source logical unit, allowing I/O

with the source logical unit to continue during the copy process.

In Storage Source, select a storage system in which the logical units from which you want to

copy data reside.

In Select Storage Source for Move, select the logical units from which you want to copy data.

If you select more than one source logical unit, SAN Copy creates a session for each sourcelogical unit. If necessary, you can enter the World Wide Name (WWN) of the source logical

unit. Click Next to open the Select Storage Destination for Storage Sources window.


51/124



Select Destination LUN / Volume

In the Select Storage Destination for Storage Sources window, right click the icon for a source logical unit, and thenclick Select Destination Storage to open the Select Destination Storage dialog box.

This wizard window allows the selection of the destination storage to which the source data will be copied. In Storage Destination, select a storage system in which the destination logical units reside.

Once a storage system is selected, Available Storage lists all logical units in the destination storage systems thathave the same or greater user capacity as the source logical unit.

From Available Storage, select the logical units that will be used as destination storage, and click the rightarrow to move them into Selected Storage.

Once the destination logical units have been selected for use, click OK to close the Select Destination Storagedialog box and return to the wizard.

With both the source storage and destination storage selected, click the Verify Connections checkbox and clickNext.

If the destination and source Storage Processor ports can not communicate, an error will be displayed. If they cancommunicate, a message box will be displayed. Click OK to proceed to the Session Name screen.

The initial steps for creating a full copy session from CLARiiON to Symmetrix are similar to those seen in theCLARiiON to CLARiiON session, and are not shown here. The first difference appears when destination storagemust be selected.

With the Navisphere Agent from the Symmetrix host system added to a portal, Navisphere Manager is able to viewthe volumes the Symmetrix is presenting to that host system. These volumes may be used in a SAN Copy session.The actual data flow between the CLARiiON LUNs and Symmetrix volumes during a SAN Copy session will passdirectly through the SAN and by-pass the attached host. This is possible because the CLARiiON ports registered asinitiators with the Symmetrix. To select Symmetrix volumes as destinations simply highlight the volumes and clickthe Right Arrow button.

Once all the desired destination logical units have been selected for use, click OK to close the Select DestinationStorage dialog box and return to the wizard.


52/124



Select Link Bandwidth

The link bandwidth value is entered here. Note that throttling cannot be performed by specifying

a link value lower than that which is actually in use.


53/124



Edit Session Name and Throttle Value

Use this Wizard window to edit the name and throttle value for any new session.

The throttle value controls the I/O rate for an active SAN Copy session. You can set the sessionthrottle to a value between 1 and 10 where 1 is the lowest I/O rate and 10 the is highest. Thedefault throttle value setting is 6.

A session name can not exceed 64 characters. The default session name is a combination of thevolume name and storage ID.

In the Session Names list, select the session whose properties you want to change.

Click Edit to open the Edit Session dialog box.

Enter a new name and throttle value, and then click Next to open the Summary window.

The Summary window provides a summary of each SAN Copy session that you want to create.

For a CLARiiON to CLARiiON copy session, the Source Storage Info and the DestinationStorage Info should list separate CLARiiON storage systems. Ownership of both of theinvolved LUNs is not restricted to both being SPA or SPB. As long as the SP ports are zoned toeach other and the source port has registered with the destination storage system database as aninitiator, communication should be possible.

If you want to change any of the session information, click Back until you reach the wizardwindow that lets you can change the session property.

If the session summary is accurate, click Finish to create the sessions.


54/124



Session Operations and Status

SAN Copy places an icon for any new sessions in the Storage tree. To view any new sessions,

do the following:

In the Storage tree, expand the icon for the SAN Copy storage system.

Expand the SAN Copy Sessions icon, and then the icon for the SP to which the session is

assigned.

Creating a session does not start the session. To start a new session, re-start one that has

completed, or one that has been stopped using the Stop button or due to a fault, do the following:

In the Storage tree, navigate to the icon for the session you want to start.

Right-click the icon and then click Start.

SAN Copy asks you to confirm the start of the session, and when you click OK, the copy sessionbegins.

It is also possible to pause a session either directly from the pop-up menu (as here) or from the

status screen. With the status screen open, clicking on Pause will cause the session to pause.

Confirmation and Success boxes will be displayed and the session will be paused.

The status dialog shows the current status of the Session, and allows management operations.

This Session has completed; if it was partially complete, the Stop and Pause buttons would be

active. Once paused, with the session status window open, clicking Resume will allow the

session to complete. Again, Navisphere displays Confirmation and Success boxes.


55/124



Lesson 3: Managing SAN Copy with Navisphere

Secure CLI


Configure SAN Copy objects with Navisphere Secure CLI

Manage SAN Copy objects with Navisphere Secure CLI

Many commands are common to SAN Copy in Full Copy Mode and Incremental SAN Copy.

Commands that are unique to one or the other will be called out.


56/124



Managing SAN Copy with Secure CLI (1)

Command syntax

naviseccli [-h | -address] sancopy

-create

Create a new Session

-destinfo

Display information about destination LUNs for an active Session

-duplicate

Make a copy of a Session (copy descriptor)

-info

Display information about copy descriptors

Note that the Secure CLI examples assume that a security file has already been created;

username, password and scope are not specified on the command line.

The commands perform the same function as their GUI equivalents.

The create command is lengthy, with a number of switches. A Session name must be specified,

along with information about source and Destination LUNs, and whether this is an incremental

Session. Other options allow the Session to be started, and specify whether an initial full copy is

required.

The info and destinfo commands display status information; info shows full information about a

Session, including Source and Destination LUNs, while destinfo shows status information about

Destination LUNs. The all switch with destinfo will show additional information, such as

whether the Session is incremental or full.

Duplicate allows an identical copy of a full Session to be created. This can then be edited to fit a

particular need.


57/124




-mark

(ISC only) Mark a Session; starts COFW activity

-modify

Modify a copy descriptor

-pause

Pause an active Session

-remove

Remove (destroy) a Session

-resume

Resume a Session if paused, from the pause point; if stopped orfailed, from the latest checkpoint

The commands match their GUI counterparts exactly. Note that resume starts from the pause

point if the Session was paused, from the most recent checkpoint if the Session was stopped or

failed, and will restart from the beginning if checkpoints have been disabled.

The modify command allows a number of Session parameters to be changed; these include

changing the Session type and name (full Sessions only), and adding or removing destinations.


58/124




-settings

Change SAN Copy environmental parameters

-start

Start a Session

Options copywholelun, nomark [new|all]

-stop

Stop an active Session

-throttle Change the I/O rate of a Session

The settings command allows changing the global SAN Copy parameters; number and size of

buffers, number of concurrent Sessions allowed per SP, and checkpoint interval.

The start command has options specific to ISC. The copywholelun option starts a Session that

copies the full content of the Source LUN to the destinations. The nomark option, which may be

used with copywholelun, allows the copy to proceed without a mark (the bulk copy option),

either to new destinations only, or to all destinations.

Stop and throttle work in the same manner as their GUI counterparts.


59/124




-transfer

Transfer a Session to the peer SP

-unmark

(ISC only) Unmark a Session; stops COFW activity

-updateconnections

Updates connection and registration information

-verify

Verifies that SAN Copy can access a LUN/volume

Transferring a Session is a manual process; Sessions do not trespass. Note that the update

connections and verify commands perform the same function as the GUI menu option and

dialog checkbox, respectively.


60/124



Lesson 4: Using admhost with SAN Copy


Use admhost to perform SAN Copy host operations

The objectives for this lesson are shown here. Please take a moment to review them.


61/124



admhost Commands (Windows only)

admhost lun_activate

Can assign drive letters

Re-discovers deactivated LUNs

admhost lun_deactivate

Flushes host buffers, then makes LUN invisible to OS

admhost lun_flush

Flushes host buffers

admhost lun_list Displays mapping information

The admhost utility is an executable program that you can run interactively or via script. It runs

on the following Microsoft Windows platforms: Windows NT, and Windows 2000/2003.

The admhost commands can activate and deactivate a copy logical unit, flush data from

operating system buffers to ensure that the source logical unit is current, and list logical unit

mapping information on the host.

The admhost commands perform several functions in SAN Copy sessions. The commands and

functions are:

admhost lun_activate which can be used to assigns drive letters (NT/2K/2K3 only) and re-

discover deactivated LUNs.

admhost lun_deactivate which can be used to flush data from host buffers to maintain LUN

currency and then make the LUN invisible to the host.

admhost lun_flush which can be used to which can be used to flush data from host buffers to

maintain LUN currency.

admhost lun_list which can be used to query the storage systems and display current LUN to

drive letter mapping. This can be especially useful when the Navisphere agent is not present;

the agent would otherwise inform Navisphere of the mapping


62/124



admhost lun_activate

admhost lun_activate [-l lun-worldwidenamed drive-letter]

Examples:admhost lun_activate

Scanning for new devices.

Completed scanning for new devices.

admhost lun_activate -l

60:06:01:EF:74:60:00:00:CD:BD:FE:45:77:9D:D6:11 -d v:

Scanning for new devices.

Successfully assigned v: to CLARiiON LUN

60:06:01:EF:74:60:00:00:CD:BD:FE:45:77:9D:D6:11

Completed scanning for new devices.

On a Windows host, the admhost lun_activate command tells the operating system to scan for

new copy LUNs and to mount each one (make it available to Windows). The software assigns a

drive letter to every new device it finds. Use admhost lun_activate on the hosts connected to

both the source and destination LUNs after a copy completes to make the LUN available/visible

to the hosts. If you omit switches, lun_activate simply scans for new devices and assigns drive

letters to any new LUNs that have a proper file system type on them. The software assigns the

drive letters according to the next available drive letter on Windows.


63/124



admhost lun_deactivate

admhost lun_deactivate o drive-letter

Example:

admhost lun_deactivate -o F:

Deactivated the device on F:

On a Windows host, lun_deactivate flushes all host buffers, unmounts the LUN, and removes

the drive letter assigned by lun_activate. It essentially dismounts a mounted LUN. With

Windows, use lun_deactivate (or flush) command on the host that holds the destination LUN

before starting a copy session.


64/124



admhost lun_flush

admhost lun_flush o [[-d drive-letter] | physicaldriven]

Examples:

admhost lun_flush -o F:

Flushed F:.

admhost lun_flush -o \\.\PhysicalDrive1

Flushed PhysicalDrive1.

On a Windows host, the admhost flush command flushes all data and clears all buffers.

However, unlike lun_deactivate, it does not remove the drive letter, and allows reads from the

LUN to continue. Use flush or lun_deactivate for a source LUN before starting a SAN Copy

session to ensure that all cached data has been written to disk.


65/124



admhost lun_list

admhost lun_list [-l lun-worldwide-name] | [-d [drive-letter] | [

physicaldriven]] [-a [driveletter] | [physicaldrive]]

Examples:

admhost lun_list or admhost lun_list -a driveletter

F: => 60:06:01:EF:74:60:00:00:A2:0D:40:24:C2:B5:D6:11

H: => 60:06:01:EF:74:60:00:00:CD:BD:FE:45:77:9D:D6:11

admhost lun_list -a driveletter -d F:

F: => 60:06:01:EF:74:60:00:00:A2:0D:40:24:C2:B5:D6:11

admhost lun_list -a physicaldrive

\\.\PhysicalDrive1 => 60:06:01:EF:74:60:00:00:A2:0D:40:24:C2:B5:D6:11

\\.\PhysicalDrive2 => 60:06:01:EF:74:60:00:00:CD:BD:FE:45:77:9D:D6:11

On a Windows host, lun_list displays the mapping information of the host devices such as drive

letters or physical drives and their corresponding LUN worldwide names (WWNs).

You can use lun_list with the -l switch to display the current drive letter mapped to the specified

LUN WWN or use the -d switch to display the LUN WWN mapped to the specified drive.

Using lun_list and lun_activate in sequence, you can obtain the lun wwn info and change the

drive letter currently mapped to the desired drive with lun_activate.


66/124



admhost Usage (Windows)

Follow these steps for full SAN Copy sessions

Quiesce Source LUN writes

admhost lun_deactivate o

On host(s) which has Destination(s) mounted, if any

admhost lun_flush o

On host which has Source LUN mounted

Can lun_deactivate instead, if no need for read-only access

Start Copy Session

Wait for copy to complete

admhost lun_activateOn all hosts mounting Source or Destination(s)

To avoid conflicts with access to the destination LUN or volume, the admhost lun_deactivate command should be

issued against the destination LUN. This will flush all data from the host using the destination and take it off line.

The destination LUN is then exclusively available to the Source LUN as a destination. This step should beperformed for full SAN Copy sessions as well as Incremental SAN Copy sessions. Note that the lun_deactivate

command performs the same function as removing the drive letter from the Windows Disk Management console; it

is easier to script, and thus more readily used.

For full SAN Copy sessions, but not for Incremental SAN Copy sessions, the following is true:

When copying the data from the source to the destination, it is essential that the state of that data be known. The

Source LUN should be quiesced and an admhost lun_flush command issued against it. This will force the host

attached to the Source LUN to commit all buffers to the LUN.

The session can now be started and data flow will take place. While the session is active, the source LUN will be

put into read-only mode. If write access is required during the SAN Copy session, a Snapshot or Clone should be

created of the source LUN and the Snapshot or Clone used as the SAN Copy source.

After the completion of the SAN Copy session, the admhost lun_activate command should be issued against both

the source and destination LUNs to bring them back on-line

Note again that the foregoing applies to full SAN Copy sessions only Incremental SAN Copy uses a Reserved

Snapshot as the source for all data copying activity, and does not require that the Source LUN be taken offline, or

even that the buffers be flushed. The advantage Incremental SAN Copy offers, therefore, is that host access to the

Production LUN is not impacted during the session.


67/124



Unix Buffer Management with Native Commands

Follow these steps for full SAN Copy sessions

Quiesce Source LUN writes

Unmount destination device(s)

On host(s) which has Destination(s) mounted, if any

Flush source device

On host which has Source mounted

Can (unmount, mount) if flush unsupported

Can unmount instead, if no need for read-only access

Start Copy Session

Wait for copy to complete Mount Source and Destination(s)

UNIX hosts present the same risks as Windows hosts with regard to data corruption. However,

the commands needed by a UNIX host to manage the host buffers are built into the operating

system. You may use the unmount and mount commands to achieve the same effects as the

admhost commands used on the Windows hosts.

Note again that the foregoing, as with Windows hosts, applies to full SAN Copy sessions only.

Incremental SAN Copy uses a Reserved Snapshot as the source for all data copying activity, and

does not require that the Source LUN be taken offline, or even that the buffers be flushed. The

advantage which Incremental SAN Copy offers, therefore, is that host access to the Production

LUN is not impacted during the session.


68/124



LAB

EXERCISES: San Copy

Incremental San Copy

Lab Exercise


69/124



Module Summary

Key points covered in this module:

Configuration and management of SAN Copy withNavisphere Manager

Configuration and management of SAN Copy withNavisphere Secure CLI

Using admhost in conjunction with SAN Copy

These are the key points covered in this module. Please take a moment to review them.


70/124


71/124


2009 EMC Corporation. All rights reserved. Module 2: MirrorView/A and MirrorView/S - 1

Module 2: MirrorView/A and MirrorView/S

Upon completion of this module, you will be able to:

Describe MirrorView/S and MirrorView/A connectivity options

Explain the operation of the MirrorView/S Fracture Log

Explain the operation of the MirrorView/S Write Intent Log

Explain how MirrorView/S and MirrorView/A make remote copies ofLUNs

List the required steps in MirrorView/S and MirrorView/Aadministration

Describe how MirrorView/S, or MirrorView/A, and SnapView can beused together

Describe Consistency Group functionality

The objectives for this module are shown here. Please take a moment to read them.


72/124



Lesson 1: MirrorView/S and MirrorView/A Features


Explain the features of MirrorView/S and MirrorView/A

Discuss the requirements for using MirrorView/S andMirrorView/A in a CLARiiON environment

Remote Replication Enhancements

The objectives for this lesson are shown here. Please take a moment to read them.


73/124



MirrorView/S and MirrorView/A Overview (1)

Optional storage system-based software

1 or 2 Remote Mirror(s) for disaster recovery 1 or 2 remote images for MirrorView/S

1 remote image only for MirrorView/A

Snapshot(s) or Clones of mirrored data accessible

MirrorView and SAN Copy Configuration and Management SRG R29

Documents

Transcript of MirrorView and SAN Copy Configuration and Management SRG R29