1. Advanced Technical Support (ATS) Americas © 2007 IBM Corporation What is FlashCopy? FlashCopy® is an “instant” T0 (Time 0) copy where the source and target volumes are immediately available for processing with full r/w access after the relationship has been established. It is a hardware solution that is software invoked. FlashCopy can be invoked by DS CLI, the DS Storage Manager (GUI) or TPC for Replication. For System i, the Copy Services Toolkit or Backup Recovery and Media Service (BRMS) can be used. The FlashCopy is a set of tracks that consists of an entire LUN.  Request copy from source to target  FlashCopy relationship created  Target available for r/w  BACKGROUND COPY/NOCOPY  Tracks copied from source to target  COPY copies all tracks  NOCOPY copies tracks updated on source  Attempts to r/w data already copied  Read/write to volume that I/O is issued to  Attempts to read a target track not already copied obtains data from source  Attempts to write a source track not already copied is intercepted and source track copied to target before update occurs Note: BACKGROUND COPY will physically copy all tracks from source to target while NOCOPY will only physically copy tracks that are updated on the source. DS6000/DS8000 FlashCopy in Open Environments Quick Reference This document covers: What is FlashCopy®? Types of FlashCopy in Open Invoking FlashCopy functions FlashCopy source and target placement DS CLI March 2007 source target Reads target source Writes FlashCopy source and target placement Same Cluster Same DA Same Rank FlashCopy Establish Performance SameDoesn’t matter No Background Copy Performance SameDifferentNo FlashCopy impact to Application SameDoesn’t matter No DS CLI The examples shown in this trifold are DS CLI commands. For more detail on these commands, refer to the IBM® System Storage™ DS8000™ Command-Line Interface User’s Guide (SC26-7916) or the IBM System Storage DS6000™ Command- Line Interface User’s Guide (GC26-7922). Latest version of the DS8000 DS CLI manual: http://www- 1.ibm.com/support/docview.wss?rs=1114&context=H W2B2&dc=DA400&q1=ssg1*&uid=ssg1S7001162&l oc=en_US&cs=utf-8&lang=en Latest version of the DS6000 DS CLI manual: http://www- 1.ibm.com/support/docview.wss?rs=1112&context=H W2A2&dc=DA400&q1=ssg1*&uid=ssg1S7001159&l oc=en_US&cs=utf-8&lang=en DS8000 uCode level/DS CLI level cross reference: http://www- 1.ibm.com/support/docview.wss?uid=ssg1S1002949 &rs=555 DS6000 uCode level/DS CLI level cross reference (click on your uCode level): http://www- 1.ibm.com/support/search.wss?q=ssg1*&tc=HW2A2 &rs=1112&dc=D400&dtm Download DS CLI: ftp://ftp.software.ibm.com/storage/ds8000/updates/D S8K_Customer_Download_Files/CLI

2. Advanced Technical Support (ATS) Americas © 2007 IBM Corporation  Inband FlashCopy Inband FlashCopy allows FlashCopy requests to be issued remotely through an existing PPRC link. mkremoteflash –dev storage_image_id conduit LSS_ID source_volume_ID:target_volume_ID resyncremoteflash –dev storage_image_id conduit LSS_ID -record source_volume_ID:target_volume_ID lsremoteflash –dev storage_image_id conduit LSS_ID source_volume_ID:target_volume_ID For remote flash, -dev is remote subsystem and –conduit is LSS in local subsystem with LSS specifying the LSS with the PPRC primary.  Fast Reverse Restore enabled FlashCopy Typically used in a Global Mirror environment. mkflash –dev storage_image_id –record – tgtinhibit -nocp source_volume_ID:target_volume_ID Fast Reverse Restore After confirming revert/commit requirement and acting upon it reverseflash –dev storage_image_id –fast source_volume_ID:target_volume_ID Types of FlashCopy in Open  Full volume copy with either COPY or NOCOPY Data on the entire volume is available for r/w on both the source and target. COPY will physically copy all source tracks to target and NOCOPY will only physically copy updated tracks on source. mkflash –dev storage_image_id source_volume_ID:target_volume_ID mkflash –dev –nocp storage_image_id source_volume_ID:target_volume_ID  Background NOCOPY to COPY Although it is a remove flash command, the relationship is maintained and starts the BACKGROUND COPY. rmflash –dev storage_image_id –cp source_volume_ID:target_volume_ID  Persistent FlashCopy A persistent relationship is maintained even after the BACKGROUND COPY completes otherwise it would be withdrawn. To remove a persistent relationship, manually withdraw it. If persistent is not specified, the FlashCopy relationship is withdrawn after the BACKGROUND COPY completes. Persistent is used automatically when establishing an Incremental FlashCopy or Fast Reverse Restore Enabled (Global Mirror) FlashCopy relationship. mkflash –dev storage_image_id –persist source_volume_ID:target_volume_ID  Multiple relationships A single source volume can have up to 12 targets, of which only one can be incremental.  Consistency group FlashCopy FlashCopy Consistency Groups provides a mechanism for achieving consistent data copy across multiple volumes and disk subsystems without requiring that application I/O be quiesced. Once a pair is established, I/O queue full is returned to the server when writes are issued preserving the order of dependent writes. The freeze lasts 2 minutes or until the unfreeze command is issued. mkflash –dev storage_image_id –freeze source_volume_ID:target_volume_ID unfreezeflash –dev storage_image_id source_LSS_ID Freeze is a volume level command and unfreeze is a LSS level command. Before issuing unfreeze, make sure that there are no other consistency groups being formed in that LSS. Incremental FlashCopy Incremental FlashCopy provides the capability to only background copy tracks that have been changed since the last increment was taken. An incremental flash can be performed in either direction. Initial establish: mkflash –dev storage_image_id –record source_volume_ID:target_volume_ID To create a new increment after establishing the initial relationship: resyncflash –dev storage_image_id –record source_volume_ID:target_volume_ID To reverse the increment: reverseflash –dev storage_image_id –record source_volume_ID:target_volume_ID When -record is specified, persistence is automatically set. To keep the incremental relationship maintained, specify –record on each new incremental flash. Otherwise, the relationship will be withdrawn after the BACKGROUND COPY completes. © International Business Machines Corporation, 2007. IBM, and FlashCopy are registered trademarks and DS6000 and DS8000 are of International Business Machines in the U.S. and other countries. Other company, product, or service names may be trademarks or service marks of others. IBM reserves the right to change specifications or other product information without notice. This publication may include typographic errors and technical inaccuracies. The content is provided as is, without express or implied warranties of any kind, including the implied warranties of merchantability or fitness for a particular purpose.