CX-Series SAN Copy for FLARE OE Version … · SAN Copy for FLARE OE Version 02.19.yyy Release Notes ... EMC CX-Series SAN Copy for FLARE OE Version 02.19.yyy Release Notes ... CX500…

1

EMC CX-Series

SAN Copy for FLARE OE Version 02.19.yyy

Release Notes P/N 300-002-755

REV A05 July 7, 2006

These release notes contain supplemental information about the following EMC products:

EMC® SAN Copy™ version 02.19.xxx.5.034 software Topics include:

Product description ................................................................................... 2 New features and changes........................................................................ 5 Environment and system requirements.................................................. 6 Fixed problems........................................................................................... 8 Known problems and limitations .......................................................... 11 Technical notes ......................................................................................... 14 Documentation......................................................................................... 29 Software media, organization, and files ............................................... 29 Installation ................................................................................................ 29 Troubleshooting and getting help ......................................................... 30

2

Product description

EMC CX-Series SAN Copy for FLARE OE Version 02.19.yyy Release Notes

Product description

EMC SAN Copy software runs on a SAN Copy storage system (storage system with SAN Copy installed), and copies data between CLARiiON® storage systems, within CLARiiON storage systems, between CLARiiON and Symmetrix® storage systems, and between CLARiiON and qualified non-EMC storage systems. SAN Copy can copy data directly from a source logical unit on one storage system to destination logical units on another, without using host resources. SAN Copy can perform multiple copies — each in its own copy session — simultaneously. The RAID type of the logical units participating in a copy session does not have to be the same; that is, the source and destination logical units can be different RAID types.

You can use SAN Copy to create full or incremental copies of a source logical unit. An incremental copy session copies only the data that has changed since the last copy session. This can significantly reduce the time needed to copy the data, thereby allowing the copy operation to be performed more frequently and more effectively. Unlike full copy sessions, the source logical unit for an incremental session can remain online during the copy process (that is, a host application can continue to send I/O to that source LU). You must, however, prepare the source logical unit prior to starting an incremental session by quiescing I/O and flushing buffers as required by your host’s operating system. Regardless of the type of copy session — full or incremental — the participating logical units must meet certain requirements.

For both full and incremental sessions, the source and destination logical units must be:

the same size, or the destination logical unit must be larger used by the same operating system owned by the same SP, for a copy within one storage system

In addition, for incremental sessions the source logical unit:

cannot be a SnapView™ snapshot

cannot be a MirrorView™ primary or secondary LU if it is in the “synchronizing” state

must reside on the SAN Copy storage system can remain online during the copy process, but the destination

logical units must be inactive (offline and/or unmounted) during the copy process. No application I/O can occur to the destination logical units during the copy session.

3

Product description


In addition, for full sessions, the source and destination logical units must be inactive (offline and/or unmounted) during the copy process. No writes to the source logical unit (unless you use replication software) and no application I/O with the destination logical unit can occur during the copy session.

SAN Copy runs in the storage-system storage processors (SPs), not on host servers. The host reserves processing resources for production applications while the SPs undertake the task of copying data.

You can use SAN Copy for the following tasks:

One-time data migration Routine copying of data for application testing Content distribution

To manage SAN Copy sessions, you can use either the UI-based Navisphere® Manager described in the EMC Navisphere Manager Administrator’s Guide (P/N 069001125), or the SAN Copy Command Line Interface described in the EMC SAN Copy Command Line Interfaces Reference (P/N 069001189).

The admhost utility is an executable program that you can run interactively via script to prepare source and destination LUs. The admhost commands can activate and deactivate SAN Copy source and destination logical units, and flush data from operating system buffers to ensure that the source logical unit is current.

Storage-system-based data-mover application

SAN Copy is a storage-system-based data-mover application that uses the storage area network (SAN) to copy data between storage systems.

Since SAN Copy runs on the storage systems, it eliminates the need to move data to and from the attached hosts, and reserves host processing resources for users and applications. Since the host is not involved in the copy process, and the data migration takes place on the SAN, the copy process is much faster than the LAN-based, host-involved copy process.

Easy-to-use web-based application

SAN Copy is an integrated part of EMC Navisphere Manager, the easy-to-use, web-based management tool for CLARiiON storage systems. Manager lets you easily configure and manage SAN Copy sessions, locally and remotely. Manager lets you select the SAN Copy source and destination logical units, create SAN Copy sessions, and then manage these sessions.

4

Product description


Use with replication software

If the storage system containing the source logical unit has device replication technology, such as EMC SnapView or EMC TimeFinder® software, SAN Copy can use a snapshot (not with the incremental feature), clone, or Symmetrix business continuation volume (BCV) as its source storage — allowing I/O with the source logical unit to continue during the copy process.

5

New features and changes


New features and changes

LU selection by specifying a port WWN and LUN combination

With this revision of SAN Copy the user can specify a LU used in the SAN Copy session by entering a combination of port WWN and the logical unit number at the time of creating the session using the Navisphere UI or the Navi CLI.

This enables SAN Copy to support the third-party storage systems, such as Hitachi 9960/9920 and IBM E20/F20, that do not provide a user interface to return the logical unit WWN.

Changes to the incremental session source are now tracked at a finer granularity. This means that, for some workloads, less data needs to be transferred to the destination during each incremental update.

Multidomain management support has been added to Navisphere in this release.

SAN Copy is now supported for VMware attaches.

6

Environment and system requirements



Hardware

This revision of SAN Copy software runs on CX-series (CX400, CX500, CX600, and CX700) storage systems.

Storage systems SAN Copy can copy to/from

AX100 AX150 CX200 CX300 CX400 CX500 CX600 CX700 Symmetrix 8x30 Series Symmetrix DMX Series Symmetrix 3832 Symmetrix 3x30 Symmetrix 3700 Qualified non-EMC storage systems, as listed in the EMC Support

Matrix As of Release 02.19.xxx.5.034, SAN Copy no longer supports copying to/from FC4500, FC5300, FC4700 and FC4700-2 storage arrays.

Storage-system software

This version of EMC SAN Copy requires FLARE™ Operating Environment Version 02.19. In addition, the Access Logix™ and SAN Copy enablers must be installed.

7



Navisphere Management Software

SAN Copy is compatible with the following minimum revisions of EMC Navisphere Management Software:

Navisphere Host Agent 6.19.x.x.x Navisphere CLI 6.19.x.x.x Navisphere Manager 6.19.x.x.x Navisphere SP Agent 6.19.x.x.x

8

Fixed problems


Fixed problems

Visit the EMC Powerlink™ Issue Tracker website at http://Powerlink.EMC.com for the most recent updates and information on previous SAN Copy releases.

Issues fixed in update 02.19.xxx.5.034

Problem description Detail

SAN Copy. The SP running a SAN Copy session may panic after copying all the data but before the session status changes to completed. [137050]

Frequency of occurrence: Rarely during a specific event. Effect: SP running SAN Copy session panics. Prevention/resolution: This software update handles this situation properly.

SAN Copy. The SP running an incremental SAN Copy session may panic if the size of data being copied is less than the total of the size of the data buffers used for that session. The total number of data buffers and the size of the data buffer are logged in the system event viewer. [135506, 136724, 137417, 137451, 146329]

Frequency: Rarely during a specific event. Effect: SP running incremental SAN Copy session panics. Prevention/resolution: This software update handles this situation properly.

SAN Copy. During the transfer of a SAN Copy session from one SP to the other SP, the current owner SP may panic if SAN Copy encounters an internal error. [145424]

Frequency of occurrence: Rarely during a specific event. Effect: The SP currently owning the SAN Copy session panics. Prevention/resolution: Fixed in this update.

SAN Copy. A SANCopy session is started on a MetaLUN component (while not supported, the GUI allows this). CPM fails to layer SAN Copy on the component LUN (which it is supposed to do) but Admin leaves the parent MetaLUN quiesced, which results in a DU for the MetaLUN.

[140118]

Frequency of occurrence: Always, during a specific (unsupported) event Effect: MetaLUN is inaccessible Prevention/resolution: Fixed in this update

http://powerlink.emc.com/

9

Fixed problems




SAN Copy. In a heavy trespassing environment, a storage processor may panic and reboot. [131111, 136672]

Frequency of occurrence: Infrequent Effect: One or both SP’s may panic and reboot. Prevention/resolution: This software update handles this situation properly; however, the excessive trespassing condition should be addressed.

SAN Copy. SAN Copy logs as errors SCSI data overruns to the system event log under certain situations. [133320,]

Frequency of occurrence: Frequent Effect: The system event log contains messages that incorrectly indicated an error condition when no error condition existed. Prevention/resolution: Data overruns not related to I/O should not be logged. This software update ensures this condition is not logged in the system event log.

SAN Copy. The granularity for an incremental SAN Copy descriptor may be set incorrectly causing the storage-system-to-storage-system communication channel to hang. [132464, 132791]

Frequency of occurrence: Infrequent. Effect: The storage processor may hang and a reboot may be required. Prevention/resolution: When using Navisphere 6.19 CLI to create an incremental SAN Copy descriptor on an 0216 storage system, the granularity of the descriptor would be set to an incorrect value. The updated software will verify the version of the software on the storage system and set the correct granularity value. This issue is fixed in the corresponding Navisphere CLI update 6.19.2.

SAN Copy. Incremental SAN Copy did not work properly on LUNs larger than 2 TB. [129383]

Frequency of occurrence: Frequent Symptom: The storage system would become unmanaged. Prevention/resolution: Fixed in this update.



SAN Copy. A copy session that was stopped may continue to display an active status. [127953]

Frequency of occurrence: Very infrequent Symptom: A copy session may continue to display an active status even after the session is stopped. The session will stop and not progress further; however an incorrect status may be displayed. Prevention/resolution: The new software correctly displays the stopped status.

10

Fixed problems



SAN Copy. Starting incremental SAN Copy sessions during an NDU commit to FLARE OE Version 02.19.yyy and later may cause the SP to panic. [129900]

Frequency of occurrence: Infrequent Symptom: The SP may panic if an incremental SAN Copy session is started while attempting to commit FLARE OE Version 02.19.yyy or later. Prevention/resolution: The new software starts incremental SAN Copy sessions while committing FLARE OE Version 02.19.yyy or later.



SAN Copy. Having SAN Copy enabled on the storage system can cause the storage processor to become unmanaged. [130364]

Frequency of occurrence: Very frequent Symptom: Having SAN Copy enabled on the storage system causes a memory leak, which can cause the Navisphere Agent to exceed its memory threshold. If the Agent exceeded this threshold, it will stop, causing the SP to become unmanaged. Prevention/resolution: The new software fixes this memory leak, thereby preventing the SP to become unmanaged.

Issues fixed in previous releases

Navisphere now appropriately reports an error when attempting to remove a mirror if it is the source or destination of an active SAN Copy session (84047, 84048).

Navisphere timeout when SAN Copy operations were performed under certain SAN configurations has been resolved (89971).

Two problems in which SAN Copy sessions start but never complete have been resolved (91098, 90313).

The problem in which SAN Copy re-copies data to the non-failed destinations on starting a partially complete session that was modified to remove the failed destination has been resolved (94813).

Two problems that resulted in poor performance of incremental SAN Copy sessions have been resolved (99921, 98781).

11

Known problems and limitations



This section identifies known issues with this release. It also includes important warnings associated with this product, its connectivity, and its compatibility.

Visit the EMC Powerlink Issue Tracker website at http://Powerlink.EMC.com for the most recent updates and information on previous SAN Copy releases.


SAN Copy using Navisphere CLI. User is wrongly permitted to change the source LU to be larger than the destination LUs. (82585)

Frequency: Always Effect: SAN Copy session would eventually fail because destination LUs are too small. Resolution: No workaround for this. When modifying a copy descriptor via Navisphere CLI, make sure that any destination LUs are always the same size or larger than the source LU, as SAN Copy does not verify that the selected LU’s size is valid.

Able to create session with inactive snapshot. Snapshots will always be accessible via verify. A session can be created with either an active or inactive snapshot. However, the snapshot LU must be active to start the session. Otherwise, the session will fail. (80957)

Frequency: Always Effect: If snapshot is inactive, SAN Copy will fail. Resolution: Ensure that the snapshot is active during the SAN Copy session.

Stale information returned on the completion of an incremental session. After an incremental session has completed, the marked status, mark time, blocks modified since mark and number of blocks to copy are all incorrect. (93383)

Frequency: Always Effect: None Resolution: These values will be updated within a minute, or can be updated immediately using the Update Now feature.

Incorrect “session status” displayed. If there is not enough memory available to start a SAN Copy session, the session will fail. However, the session status will not accurately indicate this and instead will display that either a source or all destinations have failed. (97376)

Frequency: Always Effect: Incorrect session status displayed. Resolution: Look at the failure status of the session to identify this as a resource failure as opposed to a source or all destinations failure.


12




Incorrect latency and bandwidth values displayed. On a fibre connection, the measured latency and effective bandwidth values of an incremental SAN Copy session may be incorrect. (95223)

Frequency: Intermittent Effect: Incorrect displayed values for measured latency and effective bandwidth. Resolution: No workaround for this.

Completion time displayed during auto-recovery of a copy session. The completion time displayed during the auto-recovery of a copy session is the time at which the previous copy was detected to have failed. This completion time does not indicate that the session currently being auto-recovered has completed. (98608)

Frequency: Always Effect: There is a completion time displayed during the auto-recovery of a copy session. Resolution: No workaround for this.

Issue with deleting an incremental SAN Copy within 60 seconds. The deletion of an incremental SAN Copy descriptor within 60 seconds after the completion of the last update may introduce instability in the storage system and may cause the SP to bugcheck at a later time. (98598)

Frequency: Infrequent Effect: Wait 60 seconds after the last incremental transfer is complete before destroying the SAN Copy descriptor. Resolution: Fixed in next release.

Auto-recovery of paused sessions. Auto recovery will not resume any previously paused sessions when the SP comes back up.(102685)

Frequency: Always Effect: If the SP goes down while there are paused sessions, these will not be resumed automatically. They will fail with a Terminated on Reboot status. Resolution: These sessions can be resumed manually.

Modifying a copy session to replace a failed destination. The modify can fail and leave the session in a state where it is impossible to replace the failed destination. (113299)

Frequency: Always Effect: If the only destination of a session fails and this session is modified to replace it with a new destination, the modify will fail. Resolution: 1. Modify the copy session to a full session

and then back to an incremental session. 2. Once the modify is successful, add your

new destination to the session. 3. Once the adding of the destination is

successful, remove the one that previously failed.

13




A resumed copy session may fail to auto-restart after an SP reboot. A copy session that is resumed after being paused may fail to restart after an SP reboot if the SP rebooted immediately after the session was resumed. (121394)

Frequency: Always Effect: Copy session status will be A session was active when the Storage Processor (SP) rebooted. The session may be restarted Resolution: The copy session can be resumed after the SP has recovered from the reboot.

Starting a copy session with destinations on a remote storage system or performing an update connections command can cause the SP to panic or become unmanaged. This happens in a fabric environment that involves multiple HBAs (typically six or more) that fail to respond to a login request from SAN Copy. (122270)

Frequency: Variable Effect: The storage processor will panic or will become unmanaged. Resolution: Fixed in next release.

Performing an NDU with active SAN Copy sessions can cause the SP to panic or become unmanaged. (127957)

Frequency: Variable Effect: The storage processor will panic or will become unmanaged. Resolution: All active SAN Copy sessions must be stopped prior to the upgrade being performed.

If an LU larger than 2 TB is participating in an incremental SAN Copy session, Navisphere can time out and at least one SP becomes unmanageable. (129247)

Frequency: Increases with the size of the LU. Effect: The storage processor will become unmanaged. Resolution: LUs that are used for incremental SAN Copy should be kept smaller than 2 TB.

14

Technical notes


Technical notes

This section contains information that will help with the installation, use, and management of the storage system. It provides generic information that applies to all platforms and platform-specific information.

Generic notes (apply to all platforms)

Incremental SAN Copy session on a secondary mirror You can create an incremental SAN Copy session on a secondary LU of a synchronous MirrorView session, only if the mirror state is “consistent” or “in sync.”

Handling a source failure of an incremental SAN Copy session

If a source LU failure causes the SAN Copy session to fail due to the reserved snapshot session stopping (not active), use the following steps to recover the incremental SAN Copy session:

1. Fix your source LU. 2. Modify the incremental SAN Copy session to a full session. 3. Modify this full session back to an incremental session. 4. Start the SAN Copy session. Note this will perform a full copy.

Performance of incremental sessions

For best performance of incremental copies on a Fibre Channel connection, enter a bandwidth of 2048 when creating the copy session, and modify the latency to 0.5 ms in the session properties.

Destroying a mirror operation

Do not destroy a mirror if there is an active copy session on the primary mirror LU. Either let the copy session complete, or stop it before destroying the mirror.

Binding LUs using the “block count” option

Prior to Release 12, if the SAN Copy destination LUs are on a CLARiiON storage system, bind them using the MB or GB option for sizing, or if using the “block count” option, make sure that the count is a multiple of the stripe size; otherwise the resulting host-usable LU size may be smaller than is requested, due to a software issue in pre-Release 12 FLARE code (83787, 84085).

15

Technical notes


Terminal server not supported with admhost

Make sure terminal server is not running on the system. When using terminal server, admhost will have a problem assigning drive letters to the activated disks.

Admhost LU_activate command

Before starting a session, verify that the destination LU has a file system and the same number of partitions mounted as the source LU before starting a copy session. The LU_activate command cannot refresh the data properly if no file system is mounted on the destination LU. If there is no file system on the destination LU and you have already run the copy session, reboot the host to properly refresh the data.

Admhost LU_activate command

EMC recommends that you disable the recycle bin for the destination LU prior to starting a copy session to avoid data corruption.

Maximum number of SAN Copy sessions SAN Copy and MirrorView/A sessions consume the same space, so the total number of SAN Copy sessions that can be created and stored depends on the number of destinations with which each session is created, as well as the number of MirrorView/A sessions that are stored.

• The total amount of space available for storing SAN Copy and/or MirrorView/A sessions is 200 KB per SP.

• Space occupied by a SAN Copy or MirrorView/A session with one source and one destination is 448 B.

• Additional space used by adding a destination to the copy session is 72 B (only applies to SAN Copy).

MirrorView ports

If MirrorView (inclusive of MirrorView/Synchronous and/or MirrorView/Asynchronous) is installed on the storage system, then SAN Copy cannot use the MirrorView port. However, if MirrorView is not installed on the storage system, then SAN Copy can use all ports.

SAN Copy session with FC4500

When creating a copy session with either the source or the destination(s) on an FC4500, select either the source and/or the destination(s) as follows:

Using the SAN Copy UI: Using the SAN Copy wizard, select the source by going to the Select Storage Sources window, and choose

16

Technical notes


the host that is connected to the storage system in which the source logical units reside. Similarly, select the destinations by going to the Destination Storage dialog box and selecting the host connected to the storage system in which the destination logical units reside.

Obtaining an LU WWN using Navisphere CLI: Use the following commands to select the source and/or destination LUs (if they are mounted on the attached host) and to create a SAN Copy session:

1. Obtain the WWN of the source and/or destination(s) that will participate in the copy session, by using the following command:

navicli –h <hostname> LUmapinfo

Where hostname is the IP address of the host that has access to the source and/or destination(s).

2. After obtaining the WWNs, use them in the following command to create the SAN Copy session:

navicli -h <hostname> -create –name <name> -srcwwn <srcwwn> –destwwn <destwwns> -throttle

Where hostname is the IP address of the SP that will run the copy session and the srcwwn and destwwns are the source and destination worldwide names, respectively.

SAN Copy sessions with FC4500 and FC5300

For a copy session that will have the destination(s) on the FC4500 and/or the FC5300, make sure that the destination is at least 0.1 percent larger than the source.

Transferring copy sessions and LU trespass

If you need to transfer a copy session to run on the peer SP, make sure of the following:

If your host has failover software installed on it, and your copy session is using the LU(s) mounted on this host, make sure that you unmount the LU(s) before manually trespassing it to the peer SP. If you manually trespass the LU while it is still mounted, then the failover software will trespass it back when you try to unmount it; therefore, the copy session will fail to start as the LU(s) have trespassed back to the original SP.

Copying to a destination larger than the source

If you copy data to a destination LU that is larger than the source LU, some operating systems may not be able to take advantage of the added capacity of the destination LU.

17

Technical notes


In addition, if your destination LU is larger than your source LU, the copy will succeed, but some applications and/or operating systems may not work properly with the destination LU. You must understand how your host software deals with unused data past the logical end of the copied LU to predict the results.

Bad block errors

A bad block is an unreadable block on the LU. The unreadable block is due to an incomplete write to the disk. Although bad blocks are rare, they can occur anywhere on an LU. If they occur in data or metadata, most operating systems will detect them and log errors, which will cause applications to fail. If a bad block occurs in a file system’s free space or in a database’s free space, the host does not detect the bad block and it is harmless.

If SAN Copy encounters a bad block during a copy session, the copy session will fail since it cannot read the source. If that happens, then use either one of the following:

• Copy the data using a host-based utility such as FTP. • Correct the bad block by successfully writing to it. However,

writing to it may be impossible if it is in free space. Instead, you can use a host-based utility to back up the data from the LU with bad blocks. Then reformat or unbind/bind the LU and restore the data from the backup host.

18

Technical notes


Platform-specific notes (alphabetically by platform)

SAN Copy with AIX

If the LUs in the copy session are mounted on an AIX host, the creation of the session could fail if the LUs are not unmounted properly and exported. Use the following procedure to unmount LUs that will be used in a SAN Copy session. If you cannot unmount the source LU due to continued host access, then take a snapshot or clone of that LU and use it as the source of the SAN Copy session.

On the host attached to the LU do the following:

umount filesystem-name

varyoffvg volume-group-name

exportvg volume-group-name

SAN Copy and mounting AIX LUs

After a SAN Copy session has completed, the destinations are an exact replica of the source LU; therefore, they also include any host specific data that was on the source LU. Use the following procedure when mounting the LUs on another host:

If the host mounting the destinations after the copy session completes has PowerPath software running, use hdiskpower instead of hdisk in the following first two commands.

chdev -l hdisk[n] -a pv=yes

importvg -y volume-group-name hdisk[n]

mount filesystem-name

SAN Copy with Microsoft Cluster Server

Before you create or start a SAN Copy session whose source or destination LUs are on a remote storage system and in use by a Microsoft Cluster Server (MSCS) system, you must take those LUs offline so that the SAN Copy session can access them. To take the LUs involved offline, follow the instructions below. Note that these actions are in addition to other actions that are necessary for using SAN Copy sessions on Windows LUs.

1. Locate the Microsoft Cluster Server disk group resource that includes the LUs that will be used in the SAN Copy operation.

19

Technical notes


2. Use the Microsoft Cluster Administrator to take the disk group offline by right-clicking on the disk group and selecting Take Offline. The LU(s) on the storage system that are part of this disk group(s) are now available to use as SAN Copy sources or destinations. Verify that the Clusdisk.sys driver is disabled.

3. Perform the SAN Copy operation.

When the SAN Copy operation has completed, use the Microsoft Cluster Administrator to bring the disk group(s) back online by right-clicking the disk group and selecting Bring Online.

If you cannot take the remote source LU offline, then take a snapshot or clone of that LU and use it as the source of the SAN Copy session.

SAN Copy with other clustered systems

For clustered systems other than Microsoft, the following restrictions apply:

• If a SAN Copy source LU is in a cluster and on a remote storage system, it must always be a snapshot, clone, or BCV.

• A SAN Copy destination LU cannot be part of a cluster. • A SAN Copy destination LU cannot be added to a cluster.

SAN Copy with Solaris

During the format process, Solaris writes a label on each LU. This label includes a vendor ID specific to the manufacturer of that LU, and geometry information specific to the vendor, LU size, and other LU characteristics. Solaris reads this information whenever the disk is opened, either for raw I/O or by a mount command. If the disk is partitioned, then Solaris uses the geometry information in the label to determine the locations of partitions.

20

Technical notes


When SAN Copy copies an LU, it copies all its blocks, including those which compose the label. After the copy, values in the label may be incorrect with respect to the destination LU. The Solaris format command uses this label and may display incorrect information for the destination LU. For example:

• After copying between storage systems with different vendor IDs, the label will indicate the destination LU has the same vendor ID as the source LU. For example, if you copy a Symmetrix LU to a CLARiiON LU, the format command will imply the CLARiiON LU is actually a Symmetrix LU. Although harmless, this anomaly may be confusing when viewing LUs with the format command. However, using the inquiry subcommand with the format command will correctly identify the destination LU, and can resolve the confusion.

• The destination LU will have a partition table specific to the geometry of the source LU. If the destination LU has different geometry due to a difference in either size or manufacturer, do not use the autoconfigure option in the format type submenu on this LU. Using this command will effectively destroy the partition table, making all data on this LU unusable.

SAN Copy sessions with VERITAS DMP

If you mount the LUs in the SAN Copy session on a host with VERITAS DMP, then you must quiesce I/O to those LUS before starting the SAN Copy session.

SAN Copy with Windows 2000 and Windows Server 2003

Prior to starting a SAN Copy session, disable the indexing service on the destination drive from the Control Panel > Administrative Tools > Services > Indexing Service panel. This action is recommended to avoid data inconsistencies on the destination LU once the SAN Copy session has completed.

• Admhost with Windows Server 2003

A backup host reboot is required to properly dismount the stale disk volume mount point if the session is stopped without deactivating its snapshot first using admhost.

21

Technical notes


SAN Copy support for non-EMC storage systems

EMC support for non-CLARiiON storage systems is limited to the SAN Copy application. EMC does not support the non-EMC software tools necessary to provide LU access or Fibre Channel network access.

In addition to copying data within and between CLARiiON storage systems, or between CLARiiON and Symmetrix storage systems, SAN Copy supports copying data between CLARiiON and non-EMC storage systems. Either the source logical unit or the destination logical units can reside on the non-EMC storage systems. Supported non-EMC storage systems are listed in the EMC Support Matrix. For incremental sessions, the source LU must be on the CLARiiON SAN Copy storage system (that is, you can migrate incremental changes to a non-EMC storage system, but not from it).

SAN Copy does not support FC-over-IP connections to non-EMC storage systems.

SAN Copy configuration requirements for non-EMC storage systems

The SAN Copy configuration requirements for non-EMC storage systems are the same as those for CLARiiON systems.

No EMC software is required on hosts that are attached to non-EMC storage systems.

Non-EMC storage systems must be connected to the SAN using supported switches and switch firmware revision levels as documented in the EMC Support Matrix.

SAN Copy supports the same hosts and host operating systems for non-EMC storage systems as it does for EMC systems.

You must zone the ports on the non-EMC storage systems so that the SAN Copy storage system has visibility to the LUs that will participate in the SAN Copy session. Use native switch software tools or non-EMC storage-system software tools to configure zoning.

Only storage devices that SAN Copy supports (as listed in the ESM) can be in the same zone with any port of a CLARiiON storage system that runs SAN Copy.

You will still need to follow the host-to-storage-system zoning requirements documented in the SAN Copy for Navisphere Administrator’s Guide.

22

Technical notes


Use non-EMC storage-system software tools to obtain the World Wide Name (WWN) of any logical units on the non-EMC storage system that will participate in the SAN Copy session. Navisphere Manager can then use the WWNs to provide the SAN Copy storage system with access to the logical units.

Troubleshooting

If you encounter problems using SAN Copy with a non-EMC storage system, try the following:

Verify with the EMC Support Matrix that you are using the correct versions of hardware and software.

Verify the zoning configurations. Verify that SAN Copy has access to the LUs. Try to reproduce the problem by using a host to access the non-EMC

storage system and LUs. If the problem still exists, follow the standard field process for

problem escalation.

Non-EMC storage system-specific notes (alphabetically by platform)

SAN Copy with Compaq HSG80 Use the following procedure to obtain the LU WWN on Compaq HSG80 storage systems.

You must have a local connection to get the LU WWN on the Compaq HSG80 storage system. The maintenance port located on either of the two controllers provides a way to connect a maintenance terminal.

To obtain the LU WWN, from the maintenance port display information for all the units (units meaning LUs) known to the subsystem. Then select the unit that will be used as the SAN Copy source or destination. The unit WWN is displayed in format (xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx), which must be converted to xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx for entry into Navisphere Manager or Navisphere CLI.

Follow this checklist if CLARiiON cannot access the units on HSG80 storage system:

1. Be sure to check the online connections on HSG80. Make sure the connection identifiers of both the CLARiiON SPs are in online state (OL). If the connection identifier for CLARiiON is not in the list of online connections, then add a new connection for each of the two SPs.

23

Technical notes


2. Check the permissions on the unit that will be either the source or destination of SAN Copy session on the HSG80. If all the online connections want to have access to this unit then the permission should be ALL; otherwise only the specific connection identifier should be given access rights.

3. If HSG80 is set up in multibus failover mode, make sure that the unit to be used in SAN Copy session can be accessed from both the controllers.

4. Check if the connection table is unlocked on both the controllers.

5. Check if the connection identifiers have management rights added for explicit use only. Enable appropriate management rights for CLARiiON connection identifiers.

6. Finally, sometimes a restart of both the controllers on HSG80 helps; this will refresh all the connection and other system tables.

7. Make sure that the SAN Copy initiator has access to LUN 0 (D0 or D100) if it exists.

SAN Copy with Compaq MSA 1000 Use the following procedure to obtain the LU WWN on Compaq MSA 1000 storage systems.

You must have a local connection to get the LU WWN on the Compaq MSA 1000 storage system. The maintenance port located on either of the two controllers provides a way to connect a maintenance terminal.

To obtain the LU WWN, from the maintenance port display information for all the units (units meaning LUs) known to the subsystem. Then select the unit that will be used as the SAN Copy source or destination. The unit WWN is displayed in format (xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx), which must be converted to xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx for entry into Navisphere Manager or Navisphere CLI.

Follow this checklist if CLARiiON cannot see the units on MSA 1000 storage system:

1. Be sure to check the online connections on MSA 1000. Make sure the connection identifiers of both the CLARiiON SPs are in online state. If the connection identifiers for CLARiiON are not in the list of online connections, then add a new connection for each of the two SPs.

24

Technical notes


2. Check the permissions on the unit that will be either the source or destination of the SAN Copy session on the MSA 1000. ACL can be enabled /disabled for giving access permissions to specific connections for specific units.

3. Check the volume status of the unit to be used in SAN Copy session.

4. Finally, sometimes a restart of both the controllers on MSA 1000 helps; this will refresh all the connection and other system tables.

SAN Copy with HP StorageWorks EVA 3000 /EVA 5000 Use the following procedure to obtain the LU WWN on HP StorageWorks EVA 3000/EVA 5000.

You must have command view EVA installed on the management appliance of the EVA storage system.

To obtain the LU WWN, from the command view EVA, display information for all the virtual disks (virtual disks meaning LUs) known to the subsystem. Then select the virtual disk that will be used as the SAN Copy source or destination. The virtual disk World Wide LU Name is displayed in format (xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx), which must be converted to xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx for entry into Navisphere Manager or Navisphere CLI.

Follow this checklist if CLARiiON cannot see the virtual disks on EVA 3000 or EVA 5000 storage system:

1. The CLARiiON SP to be used as the initiator of SAN Copy session should be added as one of the hosts accessing the EVA storage system. The appropriate port WWN of the CLARiiON SP has been identified while adding this SP as one of the host.

2. Be sure that the CLARiiON SP added in step 1 has been given access rights for the virtual disk to be used in SAN Copy sessions.

3. Check the operational state of the virtual disk to be used in SAN Copy session.

4. If the virtual disk is set in “Preferred Presentation Mode” with one of the two controllers, then make sure that the CLARiiON SP used in step 1 is zoned appropriately with the primary controller for this virtual disk.

25

Technical notes


SAN Copy with IBM FAStT200, FAStT500, FAStT600, FAStT700 and FAStT900 storage systems Use the following procedure to obtain the LU WWN on an IBM FAStT storage system:

You must have a copy of IBM FAStT Storage Manager Client installed on a management station that has been attached to the FAStT storage system through Direct-management method or host-agent management method. Please refer to IBM FAStT storage installation and support documents for more details.

From the IBM FAStT Storage Manager Client interface, locate the logical drive that is mapped to the LU to be used as the destination or the source of a SAN Copy session. The LU WWN will be showing as part of the properties information of the logical drive. If it is 32 consecutive digits xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, you need to add “:” between every two digits to convert to xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx format for entry into Navisphere Manager or Navisphere CLI.

For example, if you see the following worldwide name information from the properties of a logical drive:

World-wide name: 600A0B80000F18930000012B3F7C12F0

Then 60:0A:0B:80:00:0F:18:93:00:00:01:2B:3F:7C:12: F0 will be the WWN of the LU that can be entered into Navisphere.

In addition, the IBM FAStT storage system must allow host access from the CLARiiON storage system for all logical drives that will be involved in SAN Copy sessions; otherwise, the CLARiiON will not be able to read from or write to the logical drive. This can be done through IBM FAStT Storage Manager Client interface. Please refer to IBM FAStT storage documents for more details.

SAN Copy with Sun StorEdge T3 storage systems Use the following procedure to obtain the LU WWN on a Sun StorEdge T3 storage system:

You must have a network connection to the Sun T3 and some SNMP client software to obtain volume WWN (volume meaning LU) from the storage system. One popular and free SNMP utility is snmpget, which is part of the standard installation of many Linux distributions and can be found as part of a larger SNMP software package for a variety of other operating systems, including Solaris, at http://www.net-snmp.org/. On Windows systems, the snmpwalk utility from the Windows Resource Kit may be used.

http://www.net-snmp.org/

26

Technical notes


LU WWN information can be found at the following location in the MIB:

.iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.2.1.4.

To this, the desired LU must be appended. For example, to retrieve the LU WWN for LU zero on a T3 storage system named “t3one” using snmpget, the following command would be used:

$ snmpget t3one public \ .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.2.1.4.0

This would return:

enterprises.42.2.28.2.2.4.2.1.4.0 = "0103001060020F2000000AB93F7DCA7F0002BE05"

To get the same information using snmpwalk:

C:\>snmputil walk t3one public \ .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.2.1.4.0

This would return:

Variable = .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.2.1.4.0.0 Value = String 0103001060020F2000000AB93F7DCA7F0002BE05 Variable = .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.2.1.4.0.1 Value = String 0103001060020F2000000AB93F7DD0A700079AAA End of MIB subtree.

The snmputil command will return LU WWNs for all LUs on the T3, as previously shown.

To convert the values returned by SNMP into WWNs suitable for SAN Copy, there are two more steps. First, remove the first eight digits. The WWN should now begin with “60.” Second, group the digits in pairs and insert colons between them. There will be 16 pairs of digits and 15 colons. In the preceding example, the SNMP value 0103001060020F2000000AB93F7DCA7F0002BE05 would translate to the WWN 60:02:0F:20:00:00:0A:B9:3F:7D:CA:7F:00:02:BE:05.

27

Technical notes


SAN Copy with Sun StorEdge T3+ storage systems Use the following procedure to obtain the LU WWN on a Sun StorEdge T3 + storage system:

You must have a network connection to the Sun T3+ and some SNMP client software to obtain WWN of host addressable unit (either a volume or slice exported as an LU to a particular host) from the storage system. One popular and free SNMP utility is snmpget, which is part of the standard installation of many Linux distributions and can be found as part of a larger SNMP software package for a variety of other operating systems, including Solaris, at http://www.net-snmp.org/. On Windows systems, the snmpwalk utility from the Windows Resource Kit may be used.

LU WWN information can be found at the following location in the MIB:

.iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.3.1.7.

To this, the desired LU must be appended. For example, to retrieve the LU WWN for LU zero on a T3+ storage system named “t3plusone” using snmpget, the following command would be used:

$ snmpget t3plusone public \ .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.3.1.7.0 This would return:

enterprises. 42.2.28.2.2.4.3.1.7.0.0.0 = "0103001060020F2000003E6E4002E75E000EF695"

To get the same information using snmpwalk:

C:\>snmputil walk t3plusone public \ .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.3.1.7.0 This would return:

Variable = .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.3.1.7.0.0.0 Value = String 0103001060020F2000003E6E4002E75E000EF695 Variable = .iso.org.dod.internet.private.enterprises.42.2.28.2.2.4.3.1.7.0.0.1 Value = String 0103001060020F2000003E6E400D8EA500055491 End of MIB subtree.

http://www.net-snmp.org/

28

Technical notes


The snmputil command will return LU WWNs for all host addressable units (either volume or slice exported as LU to a particular host) on the Sun StorEdge T3+, as previously shown.

To convert the values returned by SNMP into WWNs suitable for SAN Copy, there are two more steps. First, remove the first eight digits. The WWN should now begin with “60.” Second, group the digits in pairs and insert colons between them. There will be 16 pairs of digits and 15 colons. In the preceding example, the SNMP value 0103001060020F2000003E6E400D8EA500055491 would translate to the WWN 60:02:0F:20:00:00:3E:6E:40:0D:8E:A5:00:05:54:91.

SAN Copy with Hitachi 9920/9960 and IBM E20/F20 Storage Systems The following information is required in order to use an LU on the Hitachi 9920/9960 and IBM E20/F20 storage systems for a SAN Copy session:

The WWN of the fiber port for the Hitachi/IBM storage system that is connected to the CLARiiON storage system for establishing the SAN Copy connection through the SAN switch.

The fiber port WWN could be obtained through the SAN switch configuration.

The LU number

The Navisphere UI and Navisphere CLI allow the user to specify an LU on the Hitachi/IBM storage system by entering these values during the creation of a SAN Copy session.

Using the Storage Management UI or CLI on the Hitachi/IBM storage system, create a mapping between the CLARiiON storage system (host) and the connected fibre port. Also map the Hitachi/IBM storage system’s LUs involved in the SAN Copy session to the CLARiiON host. An LU number will be assigned to each logical unit mapped to the CLARiiON host.

29

Documentation


Documentation

The following documents apply to this release of EMC SAN Copy. All manuals are included on the EMC CLARiiON Storage System Hardware and Software Documentation CD, P/N 053-001-477.

Part number Publication

069001188 EMC SAN Copy Administrator's Guide

069001189 EMC SAN Copy Command Line Interfaces Reference

300-001-504 EMC CLARiiON Software Installation Guide

Documentation updates

This section describes changes to the SAN Copy documentation suite that do not appear in this version of the documentation:

EMC SAN Copy Installation Guide (P/N 069001187)

If you are installing SAN Copy software on a CX500 or CX700 storage system, ignore the requirement for installing the SAN Copy UI on the storage system. The SAN Copy UI is installed on these storage systems at the factory.

Software media, organization, and files

The following table lists the applicable software media for this product release:

Product CD part number Description

SAN Copy 053-001-219 SAN Copy Enabler 01.01.5.002 CD-ROM

Installation

IMPORTANT - When you install new software on a storage system, do not remove or reboot an SP while installation is in progress. If you do, you risk leaving the storage system in a transient state where it cannot be restarted. Please wait for the entire upgrade process to complete and automatically reboot the SPs.

30

Troubleshooting and getting help


Troubleshooting and getting help

This section provides specific instructions for contacting EMC Customer Support and obtaining additional information about EMC products.

Where to get help

EMC support, product, and licensing information can be obtained as follows.

Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support For technical support, go to EMC WebSupport on Powerlink. To open a case on EMC WebSupport, you must be a WebSupport customer. Information about your site configuration and the circumstances under which the problem occurred is required.

Copyright © 2005-2006 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.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

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


CX-Series SAN Copy for FLARE OE Version … · SAN Copy for FLARE OE Version 02.19.yyy Release Notes ... EMC CX-Series SAN Copy for FLARE OE Version 02.19.yyy Release Notes ... CX500…

Documents