Abstract: . . .  Transferring(116 MB done) (iii). Clone the FlexVol volumes (on the remote storage system) In the SnapMirror relationship the destination volumes are read only, therefore, to create a clone database on a remote NetApp FAS or IBM N Series storage system, you need to create Snapsot copies of the FlexVols on the SnapMirror source storage system and update the SnapMirror relation manually. The SnapMirror update operation will replicate data including Snapshot copies . . .
. . .  described below: - 17 - Page 18 a. Bring the database offline by terminating all the application connections to the database by executing the following commands on the database server: db2 force applications all b. Create a Snapshot copy for the each volume that is used for the database by executing the following command on the SanpMirror source storage system: snap create [ VolumeName ] [ SnapName ] . . .
. . .  IBM DB2 UDB: Cloning a Database using NetApp FlexClone Technology Jawahar Lal and Roger Sanders, Network Appliance, Inc. Jeremy Brumer, IBM Toronto Lab April 30, 2006 | TR-3460 Executive Summary The ability . . .
. . .  you would execute the following command on the storage system: snap create dbdata dbdata_cl_snp01 It is recommended that you develop a naming convention and assign a meaningful name to the Snapshot copies that are created for cloning purpose. (iii). Resume normal database operations (resume writes). - 13 - Page 14 Once Snapshot copies are created, you need to resume write operations to the database by executing . . .
. . .  command on the SanpMirror source storage system: snap create [ VolumeName ] [ SnapName ] where – VolumeName identifies the name assigned to the FlexVol volume on the SnapMirror storae system that is used for the database. – SnapName identifies the name assigned to the Snapshot copy of the FlexVol volume that is used as source for the clone volume. For example, to create a Snapshot copy named dbdata_cl_snap.1 of a volume named dbdata, . . .
. . .  on /mnt/dbdata_cl and logs on /mnt/dblogs_cl file systems. Save the configuration file as /home/db2inst1/dbrelocate.cfg and execute the following command on the second database server: db2inidb database mydb as mirror relocate using /home/db2inst1/dbrelocate.cfg Next, you need to perform roll-forward recovery by executing the following commands on the database server: db2 “rollforward database [DatabaseName] to end of the logs and complete” where . . .
--3000,6,250,3186,64750