navisphere manager simulator lab guide 3.24

CLARiiON Foundations Navisphere Manager Simulator Lab

Navisphere Manager Simulator Lab Guide

Education Services

July 2007

Copyright © 2007 EMC Corporation. All Rights Reserved. Version 4.24 of 49



Copyright

Copyright © 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC, ICDA® (Integrated Cached Disk Array), and EMC2® (the EMC logo), and Symmetrix®, are registered trademarks of EMC Corporation. EMC™ and SRDF™ are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners



Trademark Information

EMC Trademarks

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 Party Trademarks

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.



Document Revision History

3.24 Navisphere Manager Simulator Lab

Guide v3.24.doc July, 2007



Table of Contents: CLARiiON Foundations - Navisphere Manager Simulator Lab

Copyright ............................................................................................................................2 Trademark Information .......................................................................................................3 Document Revision History ................................................................................................4 Table of Contents: CLARiiON Foundations - Navisphere Manager Simulator Lab............5 Lab Description...................................................................................................................6 Lab 1: Logging into the Navisphere Manager .....................................................................8 Lab 2: Navigating the Navisphere Manager User Interface ................................................9 Lab 3: Storage Management - Allocating and Assigning LUNs ........................................14 Lab 4: Configuring SnapView Snapshots .........................................................................25 Lab 5: Configuring SnapView Clones ...............................................................................28 Lab 6: San Copy Full Replicas..........................................................................................31 Lab 7: SANCopy Incremental Replicas.............................................................................34 Lab 8: Creating Synchronous Mirrors ...............................................................................36 Lab 9: Creating Asynchronous Mirrors .............................................................................40 Lab 10: Expanding LUNS - Striping ..................................................................................42 Lab 11 : Expanding LUNS - Concatenation ......................................................................44 Lab 12: LUN Migration......................................................................................................46 Summary ..........................................................................................................................48 Assessment Questions .....................................................................................................49


Lab Description

Purpose:

This lab is designed to familiarize the user with configuration and management of a CLARiiON Storage System using the Navisphere Manager Graphical User Interface (GUI). The Navisphere Manager GUI is very robust in its ability to provide the necessary information for day-to-day management of a CLARiiON data storage environment, while providing an easy to use, Windows look and feel. This lab will walk the user through the steps necessary to create and allocate data storage on a CLARiiON Storage System as well as acquaint the user with optional CLARiiON software that allows for disaster recovery and staging data for online data backups.

This lab provides step-by-step directions for configuring a CLARiiON using Navisphere Manager 6.x. The revision of Navisphere Simulator is based on Rel 24 of CLARiiON base code.

Note the Simulator does not contain the entire features/function set like the real Navisphere Manager product.

1. This simulator supports only version Jre 1.5_01. Jre above 1.5 will be supported in next release. User's have to uninstall Jre 1.6 if found on the system. 2. If no Jre is present, the Simulator installs one automatically when a user opens the application for first time.

3. Reporting wizard creates the html reports under c:\ ( root). 4. Reset option has been provided in the Simulator once installed. It appears in the menu item like this:

5. Uninstall option is also included in Simulator as shown above. 6. The read me text file is in the install folder for support of Jre 1.5_01. 7. Help file has been updated to reflect all wizard modules.




Objectives: Upon completion of this course, you will be able to: • Configure RAID Groups on a CLARiiON Storage System • Bind LUNs to RAID Groups on a CLARiiON Storage

System • Configure Storage Groups on a CLARiiON Storage System • Configure Snapshots • Create Clones • Create SANCopy Full and Incremental Sessions • Create MirrorView Synchronous and Asynchronous Images• Expand LUN to create metaLUNs • Migrate a LUN to another LUN

References: The following tools/aids/materials are required to perform the steps in this lab:

• 1 - laptop or desktop computer running either Windows NT or Windows 2003 operating system

• 1 – Copy of the Navisphere Manager Simulator software (CD or download) installed on the computer

• 1 – Copy of this Lab Document

• Internet Explorer v6.x installed on service laptop or management workstation

• Java Runtime Environment 1.5.x (will be installed if not on the computer)

• Optional - Navisphere 6.x Manager User Guide (explains some of the parameters not used in these exercises)



Lab 1: Logging into the Navisphere Manager Navisphere Manager requires a valid username and password to log in on the Manager Graphical User Interface (GUI). This is to authenticate the user and determine his authorization level for management and configuration of the CLARiiON Storage Environment.

Step Action

1 Start the Navisphere Manager interface by choosing Start – programs – Navisphere Simulation – Launch Navisphere Simulator

2 Click “OK” at the login screen ( Username: manager and Password: manager ) 3 The Enterprise Storage Window will be displayed with any CLARiiON Storage Systems in the

Domain being visible. The lab assumes there are no RAID Groups, Storage Groups, or other objects created at this time.


Lab 2: Navigating the Navisphere Manager User Interface Use these steps to learn how to navigate the Navisphere Manager User Interface (UI) software. You will be asked to navigate the Enterprise Storage window by expanding the objects that represent logical and physical components on the CLARiiON Storage Systems.

Step Action

1. From the enterprise storage Window, Expand the CX3-40-TOP66 [CX3-40] object by clicking on the “+” sign, or by double clicking the object name CX3-40-TOP66. Anytime you see a “+” sign implies you may expand the container.



2. Expand the objects where you see a “+” sign. The TASK Bar shown at the left allows the user to

perform common functions such as Binds, Mirrors, and Snap creation. It brings up a Wizard to guide the user through basic configuration tasks. The Reserved LUN Pool is free, and the Physical container shows a number of DAE3P and components in the rack. The LUN Folders container allows a way to easily organize LUNs in the array. Note again at this time there are no RAID Groups, Storage Groups, and LUNs.



3. By expanding the Physical Container you can view the DAE3P enclosures. Each DAE3P can

contain up to 15 FC or SATA disk drives. Note also the other components such as FANs, LLC’s, and Power Supplies.



4. Expand the Enclosure SPE container. Storage Processor Enclosures contain their own Power

Supplies, Fans, as well as Front ( Host side ) and Backend (disk side ) ports. Take a moment to examine the WWPNs. What speed are the Backend ports running?

5. Practice expanding and shrinking objects on the selected array.

WWPNs



6. Add a new User by clicking on Tools-Security-User Management.

Click Add to create a new user for your domain.

Create a user named Admin, with the password of password. Users can be assigned different Roles. Click the drop down box to view the choices.

Leave the global/Local at the default of global. Click OK,YES, OK and confirm the new user creation. Logout, then login with the new account name


Drop down

7. This completes the Navigating the Manager User Interface exercise.


Lab 3: Storage Management - Allocating and Assigning LUNs You will begin to create a shared configuration on the storage systems by creating all the needed components necessary to manage a CLARiiON storage array. The Wizards will guide you through the steps needed to create RAID Groups, Storage Groups, Bind LUNs, and Assign Hosts. Note that manual configuration of all steps can also be done. Use the same method to configure BOTH ARRAYS. Only the Top array will be shown. Do the same configuration on the Bottom Array

Step Action

1. Right click on the Allocate Icon under the Storage Management Task bar to launch the Storage Allocation Wizard.

Click Next after reading the Wizard dialog. A list of available servers will be displayed.

2. From the Select Servers window, Read the dialog

Click on the server w3k-240.sa4e.com

Leave the Assign LUNS to the servers radio button selected. Click Next



3. The Select Storage System window will display the available arrays. Highlight the CX3-40-TOP66

array. Click Next



4. To create a New RAID Group, click on the “New RAID Group” box.



5. Using the Dropdowns select the following;

RAID Group ID: 0 Number of Disks: 5 RAID Type: RAID 5 ( Note the Supported RAID Types ) Expansion/Defragmentation Priority: Medium Disk Selection: Automatic Click Apply, YES, OK Click Cancel to exit

Once the RAID Group is created, highlight the group.

Click Next



6. From the LUN Properties window

Read the dialog, then select;

Number of LUNS; 2 Automatically assign LUN IDs as LUN names Checked (default) LUN Name - blank Sequence Number; blank Note the RAID type

User Capacity; 2 GB Click Next



7. From the Summary Window

Read the dialog and verify the creation of the LUNs.

Click Finish - Watch the screen Note the operation created a default storage group, connected the server to the storage group, and added the LUNS to the SG What are the storage groups called? From the Results Window Read the dialog

Click Finish



8. Expand CX3-40-TOP66 RAID Groups and Storage Groups to view the completed operations.

Examine the Results What did the wizard name the Storage Group?



9. Create the following RAID Groups WITHOUT the Wizard

Right click on the CX3-40-TOP66 array > Create RAID Group Supply the following parameters for the group;

RAID Group ID; 1 Number of Disks; 5 RAID Type; RAID 5 Expansion/Defragmentation Priority; Medium Disk Selection; Automatic Click Apply, Yes, OK

RAID Group ID; 2 Number of Disks; 5 RAID Type; RAID 5 Expansion/Defragmentation Priority; Medium Disk Selection; Automatic Click Apply, Yes, OK

RAID Group ID; 3 Number of Disks; 6 RAID Type; RAID 1/0 Expansion/Defragmentation Priority; Medium Disk Selection; Automatic Click Apply, Yes, OK Click cancel to exit Verify the RAID Groups have been created as shown below.



10.

11. Bind LUNs

Right click on the RAID Group 1 > Bind LUN

Use the following properties for the LUN

LUN ID - 2

Default Owner – SPA

LUN size – 2 GB

Number of LUNs - 2 Click Apply, Yes, OK

Click Cancel

12. Once the RAID Group and LUNs have been created and verified, create a Storage Group and assign the

LUN/s to the group.

Click on the Assign Icon under the Storage Management Task Bar

Click Next to Welcome Screen.

Click the box for Server w3k-241.sa4e.com

Click Next

Select the CX3-40-TOP66 array and click Next



13. Add LUNs to a Storage Group Expand SPA, check the box for each of the LUNs you want to add. (LUNs 2 and 3 ) to move them to the “Selected LUNs” Window.

Click Next

Click Finish

Click Finish again 14. Verify both the Host and LUNs are created.


15. Use the previous method shown above to bind an additional 4 LUNS for RAID Groups

2 and 3. Each RAID Group will contain 4 LUNS with the parameters below.

RAID Group 2 Bind 2 LUNS of 2GB (LUNs 4, 5 ) Bind 2 LUNs of 4GB ( LUNs 6, 7 )

RAID Group 3 Bind 2 LUNS of 2GB (LUNs 8, 9 ) Bind 2 LUNs of 4GB ( LUNs 10, 11 ) Verify the configuration It should appear the same as the slide below.


16.




Lab 4: Configuring SnapView Snapshots

Step Action

1. A snapshot is a virtual LUN and when activated, it allows a secondary server to view a point-in-time copy (SnapView session) of a source LUN. An active snapshot is a composite of a source LUN and reserved LUN data that lasts until you destroy the snapshot. Each snapshot is linked to a source LUN(s). If the storage system loses power while the SnapView session is running and you have an AX-series system or are running SnapView version 6.24 or later, both the session and snapshot would survive the storage system power failure, since all sessions run in persistent mode. If you have an earlier version of SnapView and did not start your session in persistent mode, the session is lost and the snapshot becomes inactive.

Writes to an active snapshot from a secondary server are stored in the reserved LUN pool until the snapshot is deactivated. When a secondary server deactivates the snapshot, the software destroys all writes made to the snapshot.

The exercise will have you create a Snapshot on a CLARiiON array.

2. Right click on Replication Tab from the Task Bar

Click on the Configure SnapView Snapshots Icon to launch the Wizard.

Read the dialog

Click Next

Select w3k-240.sa4e.com as the Production Server

Click Next

Select the CX3-40-TOP66 Storage array

Click Next

3. From the Select Storage LUNs Window

Expand the Storage Groups container

Expand SG_W3k-240.sa4e.com container

Click the box for LUN 0 to move it to the selected LUNs window.

Click Next Read the screen and take the defaults for storage overhead parameters

Click Next From the “Select Snapshot LUN names window” take the defaults. The wizard provide names for the newly created LUNS

Click Next From the “ Assign Snapshot to a Server window” take the defaults and select w3-241

Click Next

Read the Summary screen window, click Finish

Read the Results window. Click Finish



4. Expand the container for “Reserved LUN Pool” the wizard created two LUNS

Expand the Private LUN container. Do you see any reserved LUNs?

Expand SPB container under the LUN Folders container. What state does the Source LUN show?( LUN 0)

Expand the Storage Group container for w3k-240. What is the status the LUN 0?

Expand the Storage Group container for w3-241

Expand the Snapshots container look in the snapshot names.

5. Under Storage Group container, w3k-240, right click LUN_0 and select SNAPVIEW > START SNAPVIEW SESSION

Call the session ‘Snap” highlight the LUN from the Selected LUNs window, Click OK

Click YES to the next window click OK to confirm

Expand the Snapshot container > snapshot names , and right click on the LUN name. Select

“ Activate Snapshot”

Click on the session name click OK , Click YES to activate the snapshot and OK to confirm.

Check the status of the containers from step 4, it should change

Look at the Reserved LUN Pool. Is there a change?

6. Expand the Snapshot container > sessions names , and right click on the LUN 0 name. Select

“ Stop Session” read the message and confirm the changes.

Check the Reserved LUN Pool, did it free the LUN?

Expand the Snapshot container > snapshot names , and right click on the LUN name. Select

“ Deactivate Snapshot” read the message and confirm the changes

Right click on the Snapshot again and select Destroy. Did you receive a message?

The snapshot was assigned to server w3-241, right click on the SG_w3-241 and select LUNS

Click on the snapshot LUN 0 and remove it from the group

From the Snapshot container try to destroy the snapshot again. Did it work?

Example is shown below


7.

8. End of Exercise




Lab 5: Configuring SnapView Clones A clone is a complete copy of a source LUN. You specify a source LUN when you create a clone group. The copy of the source LUN begins when you add a clone LUN to the clone group. The software assigns each clone a clone ID. This ID remains with the clone until you remove the clone from its group.

While the clone is part of the clone group and unfractured, any production write requests made to the source LUN are simultaneously copied to the clone. Once the clone contains the desired data, you can fracture the clone. Fracturing the clone separates it from its source LUN, after which you can make it available to a secondary server.

Step Action

1. The next steps will take you through the creation of Clones using the Wizard

2. Right click on LUN 1 > click on the Properties > type in Exchange_DB_LUN 1 for the LUN Name

Click Configure SnapView Clones Icon from the task bar

Select Next from the Welcome screen

Select w3k-240.sa4e.com for the Production Server

Click Next

Select CX3-40-TOP66 from the Storage System Screen

Click Next

From the Select Storage LUNs Window

Expand the Storage Groups container

Expand SG_W3k-240.sa4e.com container

Click the box for Exchange_DB_LUN 1

Click Next

From the “Select Clone LUN Names” window Click Next

Ffrom the “RAID configuration” window Click Next

Select server w3-241

Click next Read the Summary Screen

Click Finish Read the Results window

Click Finish


3. Examine the following for Clone status;

Expand the LUNS Folder > Expand the Private LUNs Container. Did any new LUNS get created?

Expand RAID Group 1 > Private LUNS

Expand Storage Group w3k-240 . What is the Source LUNs status?

Expand the SnapView container and all containers in the tree. Examine the state of the clone group and it members.

Right click on the Clone Group, 01000…, and the clone to see the available options.

4. Example




5. Manual creation of a Clone

Add a second Clone to the existing Group

Right click on the Clone group name ( Exchange_DB_LUN 1_CloneGroup) select “ADD Clone” Expand the SPs and note the available LUNs. Are they different and RAID Types?

Select LUN 9, take the defaults, click Apply, Yes, OK , Cancel Examine the Clone Group again. Note the RAID Types that make up the Clone group. What does this tell youadding a Clone?

6. Right Click on the Clone group name and select Destroy Clone Group. Did you receive a message? Right click on the Clone ( 010000…. ) and select remove. Do this for both clones. Right click on the Clone group name again and select Destroy Clone Group.

7. End of Exercise


Lab 6: San Copy Full Replicas Step Action

1. San Copy will copy data to LUNS on the same array or between 2 arrays over distance.

San Copy uses CLARiiON ports that are zoned together to make a San Copy Connection. LUNs on both arrays should appear in the Storage Groups that have the San Copy connections setup.

Right click on the SG_w3k-240 storage group on the CX3-40-Top array.

Select SAN Copy > Connections”

2. In your connection window, note the “SAN Copy Connection” box. It should show the remote array and an SP. The

box from “Ports to Connect” will show ports that are properly zoned. You can select a different System by using the drop down arrow next to it. For each port that is unchecked, CHECK it, then APPLY. Repeat this for ALL ports. Use the drop down and check the other ports. You should have connections to 2 ports on the remote array. Expand the San Copy Connections to validate. DO THE SAME ON CX3-40-BOTTOM > Storage Group SG_w3-241



3. Validate the Connections have been made. The example shows Storage Group SG_w3k-240.

Examine Storage Group SG_w3-241 on CX3-40-BOTTOM as well.


4. On CX3-40-TOP array Expand storage Group SG_w3k-240

Right click on LUN 0 > Properties

Rename LUN 0 to SANCopy_Primary_LUN 0

On CX3-40-BOTTOM array Expand Storage Group SG_w3k-241

Right click on LUN 2 > Properties

Rename LUN 0 to SANCopy_Secondary_LUN 2

5. From the Task Bar, select Replication > Configure SANCopy

From the Welcome screen Click Next

From the “Select SANCopy Storage System” window select CX3-40-TOP

From the “Select Session Type” window select Full > Next

From the “Select Storage Sources” window select SANCopy_Primary_LUN 0 > Next

From the “Select Storage Destinations for Storage Sources” right click LUN 0 under the “ID” column choose Select Destination Storage

Use the dropdown from the “Storage Destination” select CX3-40-BOTTOM and note the available LUNs

(It is possible to copy to the SAME array)

Select SANCopy_Seconday_LUN 2 > OK then Next

From the “Sessions Names” window Click Next

Summary Click Finish, OK



6. Expand the SAN Copy Sessions container. The session will appear as a Full session under the owning SP of the LUN you selected. (SPB)

7. Start the session and wait until it completes.

Click OK and validate the session has a status of “Completed” under “San Copy Sessions”.

Right click on the Session Name > Remove

8. You have created, started, and removed a San Copy Full session


Lab 7: SANCopy Incremental Replicas Step Action

1. Much like MirrorView/A , San Copy Incremental uses the Reserved LUN Pool. Next, you will create a San Copy Incremental Session. Follow the process used to create a Full SANCopy replica except choose

Incremental Select the same Source LUN ( SANCopy_Primary_LUN 0 and Destination LUNs (SANCopy_Secondary_LUN 2)

When the Link Initialization screen appears, use the dropdown to view the choices. Take the default

Select Next

From the Session Name screen, highlight the name and select “EDIT”

Append _inc to the session name See Example below (w3k-240.sa4e.com:0_inc)

Click OK > Next

Summary Screen Finish > OK



2. Expand and examine the following containers to view the LUNS/names created during the session.

Reserved LUN Pool

LUN Folders ( SPB)

RAID Group 0

Storage Group SG_w3k-240

Snapview > Snapshots and Sessions > Reserved Sessions

SANCopy Sessions > SPB Incremental

3. Right click on the session> Status > The differences here show an incremental session has a “MARK” associated with it. Incremental San Copy will transfer only changes that have occurred on the source since the last session. Once the session completes, check out the status again to make sure it shows complete.

Highlight each tab to view the details

Note: Manual creation of SANCopy sessions follows the same process. Right click on the LUN you want to copy and follow the screens.

4. Right click on the session> Status > Click Start Session.

5. Completed session.

Remove all San Copy sessions

Right click on each session and click REMOVE. Validate all session are gone.

6. Congratulations you have created San Copy Sessions for both Full and Incremental copies and removed them

from the array.



Lab 8: Creating Synchronous Mirrors A remote mirror consists of a primary image and up to two secondary images. The production image (the one mirrored) is called the primary image; the copy image is called the secondary image. MirrorView/S supports up to two remote images. Each image resides on a separate storage system. The primary image receives I/O from a server called the production server; a separate storage system maintains the secondary image. This storage system can optionally have a failover/standby computer connected to it or can be connected to its own computer system. Both storage systems can be in different domains, which you manage with the User Interface (UI). The client that is managing the storage system containing the primary images can fail over to the secondary image if the primary image becomes inaccessible. In the previous labs, you created RAID Groups, Storage Groups attached hosts, and created Clones and Snaps. CLARiiONs arrays support two (2) types of mirrors - Synchronous and Asynchronous. The creation of RAID Groups Storage Groups and LUNs should have already been done on BOTH ARRAYS.

Step Action

1. Right click on the CX3-40_Top array > MirrorView > Manage MirrowView Connections The connections should Enabled , if not , select the connection from the right panel and click Enable . Click OK

Add LUN 5 to Storage group w3k-240 on CX3-40-Top array. Right click > Properties> Rename the LUN 5 to MVS_Source_LUN5

Click on the configure MirrorView Icon from the Task bar

Click Next from the welcome screen

From the Select Servers screen , Highlight w3k-240.sa4e.com

Click Next

Select cx3-40-TOP from the Select Primary Storage Screen




Click Next

From the Select Storage LUN Screen

Expand Storage Group w3k-240.sa4e.com

Check the box for MVS_Source_LUN 5

Click Next

From the Select Secondary Storage System

Select cx3-40-BOTTOM

Click Next

From the Select Mirror Type window Read the dialog for the Mirror types

Choose the default radio button for Synchronous

Click Next From the Attribute screen Click next

From the Configuration screen select highlight MVS_Source_LUN 5

Click Next From the RAID Configuration screen Take the defaults, Click Next

From the Select Servers Screen, leave the defaults and Select w3-241. Click Next

Read the Summary Screen Click finish

Read the Results Screen click Finish


2. Expand and examine the following containers on the Primary ( cx3-40-top) and Secondary (cx3-40-BOTTOM) arrays

Private LUNs

SPs

Storage Group

Remote Mirrors

Note: The write intent log keeps track of writes that have not yet been made to the remote image for the mirror. It allows for fast recovery when the primary storage system fails. When the primary fails and is recovered, the write intent log is used to synchronize the data on the remote image. Otherwise, a full resynchronization would be required for the remote image.




3. In situations where you must replace the primary storage system due to a catastrophic failure, you

can use a promotion to access data on the secondary storage system. To recover and restore I/O access, you must promote a secondary mirror image to the role of primary mirror image, so that a server can access it.

4. On the Primary array open the Remote Mirrors container and expand out all options. Right click on the Secondary Image name and note the options. Click Promote, read the next 2 screen. Did the Primary and Secondary Mirrors switch states? Try promoting the Primary image Promote the secondary image back to Primary Right click on the secondary image and Fracture the mirror. Did the state change? Right click on the secondary image and “Remove” it Right click on the Mirror Name and Destroy the Mirror.

End of Exercise



Lab 9: Creating Asynchronous Mirrors Step Action

1. Creating an Asynchronous Mirror is very similar to a Synchronous Mirror.

Use the same procedures except select “Asynchronous” for the Mirror type.

Add LUN 8 to SG_W3k-240 Storage Group. Rename LUN 8 to MVA_Source_LUN 8

2. Note the difference on the “Primary LUNs” status MirroredSnapshot Active. MirrorView/A uses snapshots to keep track of changed data on the source LUN. Check out the following containers by expanding each one and note their contents. Also, verify the mirror has been created on the secondary array under remote mirrors

SPs

Reserved LUN Pool ( should have a “Allocated” LUN on the owning SP)

RAID Group

Storage Group

SnapView> Snapshot Names> Reserved Snapshot > Reserved Sessions


3. Manual Creation of a Mirror

Open Storage Group SG_w3-241 Right click on LUN 2 > Properties > Rename to MVS_Source_LUN 2 Right Click on the LUN > MirrowView > Create Remote Mirror Use the parameters shown in the screen (use the drop down to change from Asyn) Click OK, Yes, OK

Under Remote Mirrors check the status of the newly created Mirror

Right click to “Add Secondary Image”

From the screen insure the secondary array is CX3-40-BOTT

Select LUN 5 > Select OK, Yes, OK

Check the status of all array and Mirrors

Destroy the Secondary Image, then the Mirror, from the “Remote Mirrors Container”

Click on the secondary mirror image > Remove

Click on the Mirror Name > Remove

You have created and destroyed both Synchronous and Asynchronous mirrors.

Congratulations! Next you will create San Copy sessions.




Lab 10: Expanding LUNS - Striping Expanding LUNs on a CLARiiON is how you can increase the capacity of an existing LUN You must first create a LUN to use for the base metaLUN. MetaLUNs can be created using two methods, Striping and Concatenation. The lab will take you through the striping method.

Step Action

1 Click on the Expand Icon from the Task Bar

Click Next to the Welcome Expand Wizard window

From the “Select Server window” check server w3k-240

Click Next

Select the CX3-40-TOP66 array

Click Next

From the “Select LUN to Expand window” select Exchange_DB_LUN 0

Click Next

From the “Select Expansion Type window” Select the default of “Stripe Expansion”

Click Next

From the “Select Unused LUN window” select LUN 4

Click Next

From the “Specify metaLUN Capacity window” take the default of maximum capacity

Click Next

From the “Specify new LUN settings window” click Next

From the “Summary window” verify the capacity is correct ( 4GB). click Finish

Click finish from the “Results window”


2. Expand the LUN Folders container. A striped metaLUN consists of a single Component with a number of LUNS

that comprise the metaLUN. Available LUNS are the same size and RAID Type of the “base or source” LUN. Right click on the metaLUN to view the properties. Expand the Private LUNs container, RAID Group container where that the LUN is contained under, and the Storage Group in which the LUN is in. Note the numbers to the right of the LUNs are assigned by the wizard. These will be different depending on the array model.

3. End of Exercise




Lab 11 : Expanding LUNS - Concatenation Expanding LUNs on a CLARiiON is how you can increase the capacity of an existing LUN You must first create a LUN to use for the base metaLUN. MetaLUNs can be created using two methods, Striping and Concatenation. The lab will have you create a metaLUN usng concatenation.

Step Action

1. Expand the SG-w3k-240.sa4e.com storage group. Right click on SANCopy_Primary_LUN 0 and click Expand Click Next from the Welcome Screen Click the radio button for Concatenation, Click Next From the “Select Unused LUN window” select LUN 11 Click Next From the “Specify metaLUN Capacity window” take the default of maximum capacity Click Next From the “Specify new LUN settings window” take the defaults. Click Next From the “Summary window” verify the capacity is correct ( 4GB). Click Finish From the “Results window” Click Finish Verify the settings from the Summary window


2. Expand the LUN Folders container. Expand LUN 1. A concatenated metaLUN consists of multiple

components with a number of LUNS that comprise the metaLUN. Available LUNS can be different sizes and RAID Types than the “base or source” LUN. Right click on the metaLUN to view the properties. Expand the Private LUNs container, RAID Group container where that the LUN is contained under, and the Storage Group in which the LUN is in. Note the numbers to the right of the LUNs are assigned by the wizard. These will be different depending on the array model.

3

4. End of Exercise




Lab 12: LUN Migration The LUN migration feature lets you move the data in one LUN or metaLUN to another LUN or metaLUN. You might do this to change the type of drive the data is stored on (for example, from more economical ATA to faster FC, or vice-versa), to select a RAID type that better matches the data usage, and/or recreate a LUN with more disk space.

Step Action

1. Expand RAID Group 2 Right click on LUN 6 and check the properties. Verify the LUN size Right click on LUN 6 again and click Migrate Expand both SP’s to view available LUNs. Note they may be from different RAID Groups. Select LUN 10 click Next , click OK to start the Migration. Right clicking on the properties of LUN 6 will now show a “migration” tab on the upper right side of the window, click on the tab to show the status. After migration completes verify the following; Under which RAID Group does LUN 6 reside? Where is LUN 10? What is the RAID Type for LUN 6? Where has LUN 10 gone? Verify the settings from the Summary window


2.

3 End of Exercise




Summary In this lab, you used Navisphere Manager to configure two CLARiiON Storage Systems. In the process of implementing the configuration you:

• Configured RAID Groups on two CLARiiON Storage Systems to allow for binding LUNs of a particular RAID type

• Bound LUNs on the new RAID Groups to create disk resources for the host computers and implement the RAID protection for data

• Populated Storage Groups with host computer and LUNs to allow the host computers access to disk resources create on the CLARiiON Storage Systems

• Created a Clone within one of the CLARiiON Storage Systems to allow for easy backup of the data without impacting the production LUNs performance

• Created SnapShots for multiple LUNs to facilitate easy backups without the high resource overhead required by Clones

• Created MirrorView Synchronous and Asynchronous Mirror Replicas • Created San Copy Full and Incremental Replicas • Created Striped and Concatenated metaLUNs • Migrated an existing LUN to another LUN



Assessment Questions Please answer the following questions. 1. When creating a RAID Group, what are you doing to the disks involved?

A. Changing the domain name B. Creating a disk group that can be bound into a specific RAID Type using the

Bind LUN process C. Selecting the domain RAID settings to allow the Storage System to vary the RAID information sent to the Management GUI at shortened intervals

D. Configuring SP-A and SP-B exclusive RAID type settings 2. When is a disk is available to a attached host ?

A. When a LUN is bound B. When a RAID Group is created C. When the disk is bound and in a Storage Group

3. The Host Computer is typically placed into a single Storage Group?

True False

4. Which two CLARiiON replication methods use resources from the RLP?

A. MV/S-MVA B. MV/A-SANCopy Full C. MVA- SANCopy Incremental

5. Which San Copy method copies the entire contents of the source disk to the destination disk?

A. San Copy Incremental B. San Copy Full

6. Which statement is true when creating a Clone?

A. Source and Destination LUNS must be the same size and RAID Type B. Destination LUN can be the same size or larger than the Source C. Source and Destination LUNS must be the same size but different RAID Types

navisphere manager simulator lab guide 3.24

Documents