Symmetrix V-Max Series Architecture and Design Solutions Enabler and Feature Reference Guide

April 2009

Copyright

Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 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. 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.

Third Party Trademarks

Document Revision History

Rev #
1.0 First Draft

Description
April 2009

Date

Table of Contents

Copyright ...........................................................................................................2 Trademark Information ......................................................................................3 Document Revision History ...............................................................................4 Table of Contents ..............................................................................................5 Array Controls .......................................................................................................6 Managing Configuration Changes .....................................................................6 Storage Provisioning using Initiator Groups ......................................................7 Enhanced Virtual LUN Technology ...................................................................8 Business Continuity ..............................................................................................9 SRDF/A and the Consistency Exempt Option ...................................................9 SRDF Extended Distance Protection (EDP)....................................................10 SRDF/Star with R22 Dual Secondary Device..................................................11 Creating an R22 Device...............................................................................11 TimeFinder ......................................................................................................12 Clone Emulation ..........................................................................................12 Snap Recreate.............................................................................................12 Open Replicator for Symmetrix .......................................................................13

Array Controls
Managing Configuration Changes
Solutions Enabler 7.0 running on the Next Generation Symmetrix Series with Enginuity 5874 handles configuration changes differently from previous versions of Solutions Enabler. The following is a list of changes in the configuration change feature of Solutions Enabler 7.0: Up to four concurrent configuration change sessions are allowed to run at the same time, when they are non-conflicting. This means that multiple parallel configuration change sessions can run at the same time as long as the changes do not include any conflicts on the following: o device back-end port o device front-end port o device o global Devices and metadevices can be created and mapped in one command. This eliminates the need to perform multiple configuration changes when provisioning new storage. SE 7.0 with Enginuity 5773 Step Configuration File Create Devices create dev count=40, size=20000 cyl, emulation=fba, config=2-Way-Mir; map dev 600:627 to dir 8G:0 starting lun=07; Map Devices map dev 600:627 to dir 8H:0, starting lun=10; SE 7.0 with Enginuity 5874 Step Configuration File create dev count=10, size=80000 cyl, Create and emulation=fba, Map Devices config=2-Way-Mir, mapping to dir 8G:0 starting lun=07, mapping to dir 8H:0 starting lun=10; The Symmetrix array manages its own less restrictive device locking. A session ID identifies each running session on the array. o The new -session_id option can be used with the abort operation to specify a particular configuration change session. If session id is not known, running an abort will list the sessions and prompt for the id to abort.

Storage Provisioning using Initiator Groups

A new command, symaccess, provides all the storage provisioning requirements for Symmetrix V-Max arrays with Enginuity 5874. With symaccess, the following functions are no longer included: There is no device masking database. There is no initialization, backup, or restore. With the symaccess command, all groups and views are backed up to a file, and can be restored from a backup file. SE 7.0 with Enginuity 5773 Action Command symmaskdb -sid SymmID init -file BackupFilename Backup [-vcmdb_type <3 | 4| 5>] Database symmask sid 814 wwn 20000000c920b484 add devs Mask 0030:0034 dir 16A -p 0 Devices symmask refresh Refresh Masking Database SE 7.0 with Enginuity 5874 Action Command symaccess -sid 234 -type initiator -wwn Create 210000e08b04daac -name initexample create Initiator Group symaccess -sid 234 -type storage devs 0026 -name Create storexample create Storage Group Create Port symaccess -sid 234 -type port -dirport 7E:1 -name portexample create Group Backup File symaccess -sid 234 -f backup_filename backup Restore File symaccess -sid 234 -f backup_filename restore Volume visibility and the LUN offset on an initiator are no longer supported. Heterogeneous host types are no longer supported. The HBA flags option is supported.

Enhanced Virtual LUN Technology

Enhanced Virtual LUN Technology allows storage administrators to quickly move an applications data to other storage within the same array. A migration can change the protection level and disk type of FBA, CKD, and iSeries Symmetrix devices. A migration can use the storage of existing devices that do not contain live data or unconfigured disk space. Virtual LUN migration is from source devices to equally-sized target devices, or disks with free space equal to the source devices. A migration will not disrupt hosts or internal applications. A virtual LUN migration may be initiated in the following circumstances: Traditional data management involves moving data to a lower tier as it ages and becomes less critical to the business. Protection might change as the data ages. Emerging tiered storage configurations include moving data continuously during its lifecycle, either to optimize price/performance or respond to cyclical business changes. A virtual LUN migration can be performed online or offline. Solutions Enabler 7.0 includes a new command, symmigrate, to perform virtual LUN migrations. The Symmetrix Optimizer license is required to use enchanced Virtual LUN technology. SE 7.0 with Enginuity 5874 Operation Description validate Verifies that the information provided is currently allowed. No changes will be made to the device(s) and the command can optionally output a file containing device pairs (using configured space). establish Starts a new session and begins the Synchronizing process. query Queries for the status of sessions. verify Verifies that a session is in a specified state. list Lists all the sessions for a given Symmetrix array, or for all Symmetrix arrays. terminate Terminates a session and removes it from the Symmetrix array. Example: Migrate to Unconfigured Space symmigrate name mig_01 g Exchg01 tgt_unconfigured tgt_dsk_grp 1 tgt_raid6 tgt_prot 6+2 establish Example: Migrate to Configured Space symmigrate name mig_01 g Exchg01 tgt_configured tgt_dsk_grp 1 tgt_raid6 tgt_prot 6+2 establish

Business Continuity
SRDF/A and the Consistency Exempt Option
The consistency exempt option (-cons_exempt) provides the ability to dynamically add and remove device pairs from an active SRDF/A session without affecting the state of the session, or the reporting of RDF pair states for devices that are not the target of the operation. Prior to Solutions Enabler version 7.0, the SRDF/A session had to be deactivated in order to add or remove device pairs. The consistency exempt option is provided for an SRDF/A environment to indicate that the devices should be temporarily considered exempt from the consistency requirements of the group. This allows the group to be dynamically expanded or decreased without deactivating the SRDF/A session. When adding or removing device pairs in an active session, devices are placed in a consistency exempt state and are excluded from the groups consistency check. The consistency exempt state will automatically be removed after the devices have been resumed and fully synchronized, and two full cycle switches have occurred, or they have been removed from the group. The -cons_exempt option is used with the createpair, movepair, half_movepair, and suspend commands. SE 7.0 with Enginuity 5874 Command Description symrdf createpair The SRDF pair(s) become consistency exempt in the SRDF group in the current SRDF/A group in which they are created symrdf movepair The SRDF pair(s) become consistency exempt in the target SRDF group into which they are moved symrdf suspend Device pair(s) become consistency exempt in their current SRDF group For example, if the device pair has to be moved from an active SRDF/A group, this device pair alone can be suspended with consistency exempt, without affecting all the other devices

SRDF Extended Distance Protection (EDP)

Enginuity 5874 supports SRDF/Extended Distance Protection (SRDF/EDP) that is primarily intended to streamline a Cascaded SRDF linkage out to the remote site with a more direct (diskless) connection. Diskless cascaded SRDF support allows replication between the source (site A) and remote target (site C) without the need for SRDF BCVs or any replication at the middle Symmetrix array site. The introduction of a diskless (DLDEV) cascaded SRDF linkage means that the R21 device is a new type of I/O connection device which does not have any local mirrors. Since the device has no local disk space allocated to store the user data, it therefore reduces the cost of having disk storage in the R21 Symmetrix array. SE 7.0 with Enginuity 5874 Action Command create dev count=10, size = 8 GB, Create DLDEV with emulation= FBA, symconfigure config= DLDEV, dynamic_capability = dyn_rdf; List DLDEV symdev list -sid 234 dldev with symdev List DLDEV symrdf list -diskless_rdf with symrdf The symconfigure command supports various control (creation, configuration, convert, and delete) operations of a diskless device, using the following device type designations: DLDEV RDF1+DLDEV RDF2+DLDEV RDF21+DLDEV You cannot create an RDF21+DLDEV device directly. Use the add rdf mirror command with symconfigure to create R21 diskless devices.

SRDF/Star with R22 Dual Secondary Device

With Enginuity 5874 and Solutions Enabler V7.0, Star configurations with concurrent R2 RDF sites are possible. Similar to concurrent R1 devices that are referred as R11 devices, concurrent R2 devices are referred to as R22 devices. It is based on a new concurrent R2 feature that allows an R2 device to have two RDF mirrors. Each R2 mirror is paired with a different R1 mirror and only one of the R2 mirrors can be RW on the link at a time. The primary intended use for R22 devices is to simplify failover situations in Star configurations and to improve the Star environment resiliency. The use of R22 devices in a Star environment significantly reduces the amount of steps involved in some of the long running commands (such as reconfigure, switch, connect) thus enabling the command sequences to finish quicker. While designed primarily for SRDF/Star, R22 devices can be used for both concurrent and cascaded operations. In order to use the R22 feature, the Star compatibility mode must be set to v70 (the default value.) If set to v70, this option enables the new Star State Tracking feature which is required to support R22 devices. Critical control operations are detailed in the EMC Solutions Enabler Symmetrix SRDF Family CLI Version 7.0 Product Guide P/N 300-000-877 REV A11.

Creating an R22 Device

You cannot create an SRDF R22 Symmetrix logical volume directly. It must be done in two steps. The add rdf mirror operation of the symconfigure command can be used to create SRDF R22 logical volumes. The procedure for configuring SRDF pairs of an R22 device is the same as configuring any concurrent device. Before using add rdf mirror the device must be RDF1 and RDF2 capable. The command file syntax for symconfigure to create an SRDF R22 Symmetrix logical volume in two steps is as follows: From Site A add rdf mirror to dev 0130 ra_group = 04, mirror_type = RDF1, remote_dev = 01D0, invalidate = R2, start_copy = no, rdf_mode = sync; From Site C add rdf mirror to dev 00A8 ra_group = 06, mirror_type = RDF2, remote_dev = 01D0, invalidate = R2, start_copy = no, rdf_mode = async;

TimeFinder
Clone Emulation
Starting with Enginuity release level 5874, all TimeFinder/Mirror functions are performed through TimeFinder/Clone software using a process called Clone Emulation. When running in Emulation Mode, TimeFinder/Clone transparently performs TimeFinder/Mirror commands and executes scripts that were written for Solutions Enabler up through version 6.5.2 running on Symmetrix arrays using Enginuity release levels 5773 and earlier.

Snap Recreate
Starting with Enginuity 5874, snap sessions can be recreated on an existing virtual device (VDEV) in preparation to activate a new point-in-time image. Snap recreate is only valid when issued against sessions that have been previously activated. This process makes it more convenient to reuse a virtual device to acquire a new point-in-time image. Since the recreate operation replaces the previous point-in-time image with a new one, the used tracks in the SAVE devices that were associated with the previous session are freed during the processing of this command. Recreating a virtual snap copy session requires the following steps: 1. Create a snap session. symsnap -g ProdDB create DEV001 vdev ld VDEV005 2. Activate a snap session. symsnap -g ProdDB activate DEV001 vdev ld VDEV005 3. Recreate a snap session. symsnap -g ProdDB recreate DEV001 vdev ld VDEV005 4. Activate a snap session. symsnap -g ProdDB activate DEV001 vdev ld VDEV005 5. Repeat the Recreate/Activate a snap session, as necessary. 6. Terminate the snap session when no longer needed. (Refer to page 87.) symsnap -g ProdDB terminate DEV001 vdev ld VDEV005 The Snap recreate functionality is supported with the symsnap query and symsnap verify commands. For example: symsnap g TestDg query multi symsnap g TestDg verify -recreated

Open Replicator for Symmetrix

With Enginuity 5874 Open Replicator leverages TimeFinder/Snap. There are two key reasons for providing this functionality. First, Open Replicator operations may impact production I/O if being done from production volume. Second, all volumes in the replication configuration must be visible to the remote devices, which may cause a lot of configuration changes for the production devices. If we, instead, use a TimeFinder/Snap of the production volume and present the Snap for Open Replicator operations we save the extensive reconfiguration while simultaneously reducing costs associated with using full volume copies of production data. ORS Setup: 1. Create the snap session. symsnap f snap sid 111 nop create 2. Create the ORS session. symrcopy f ors sid 111 nop create diff copy -cold 3. Activate the SNAP session. This command creates PIT. symsnap f snap sid 111 nop activate not_ready 4. Activate the ORS session. ORS copy begins at this time. symrcopy f ors sid 111 nop activate 5. Allow ORS session copy to complete. 6. Recreate the snap session. symsnap f snap sid 111 nop recreate 7. Recreate the ORS Session symrcopy f ors sid 111 nop recreate 8. Activate the SNAP session. This command creates PIT. symsnap f snap sid 111 nop activate not_ready 9. Activate the ORS Session. ORS copy begins at this time. symrcopy f ors sid 111 nop activate 10. Terminate the ORS session. symrcopy f ors sid 111 nop terminate 11. Terminate the snap session. symrcopy f snap sid 111 nop terminate