Rate this:

Virtually provisioned Thin device data can be migrated between high-performance drives and high-capacity drives. Data can be moved between storage pools configured on different drive technologies, and with different RAID protection types.

Virtual LUN VP migrations are session-based – each session may contain multiple devices to be migrated at the same time. There may also be multiple concurrent migration sessions. At the time of submission a migration session name is specified. This session name is subsequently used for the monitoring and management of the migration.

While an entire Thin device will be specified to be migrated, only Thin device extents that are allocated will be moved. Thin device extents that have been allocated, but not written to (for example, pre-allocated tracks), will be remapped to the target pool but will not cause any actual data to be copied.

New extent allocations that occur as a result of a host write to the thin device during the migration will come from the target pool.

During the migration, no changes occur to the front-end configuration of the thin device. The Symmetrix device number of the thin device remains the same, as does all mapping and masking information, and metadevice configuration. All local and remote replication relationships will also remain intact, and may actually be active during the migration.

For details and restrictions please refer to Feature document for “Symmetrix Virtual LUN VP Mobility”.

Example of how to do the migration:

In order to migrate a group of thin devices contained in the VP_ProdApp1 storage group, currently bound to a RAID 6 14+2 on SATA thin pool, to a RAID 1 on FC thin pool, the following steps would be performed:

1. Validate the migration:
symmigrate –sid 1849 –sg VP_ProdApp1 –tgt_pool –pool FC_R1_VP –name VP_migration validate

2. Establish the migration:
symmigrate –sid 1849 –sg VP_ProdApp1 –tgt_pool –pool FC_R1_VP –name VP_migration establish

3. Monitor the migration progress:
symmigrate –sid 1849 –name VP_migration query

4. Verify the migration has completed:
symmigrate –name VP_migration verify –migrated

5. Terminate the migration:
symmigrate –name VP_migration terminate

Rate this:

The following command can be used to view the device locks:

 

symdev -lock list  (Check for -L / P next to the lock)

 

L = Long lock, typically associated with SymReplicate and indicates that a long lock is normal. Before releasing lock the customer should check with replicate manager to see if they can stop the process holding the lock.

P = Persistent, cluster-type lock (ex: AIX)

 

To release the device external lock use:

 

symdev -lock # release

Rate this:

1.    symrdf -g dgname disable (Disables consistency protection for SRDF/A pairs in device group)

2.    symrdf -g dgname set mode acp_disk (This will turn on the adaptive copy write pending mode for the device group)

3.    symrdf -g dgname est (This initiates an establish for all the SRDF pairs in the device group)

4.    symrdf -g dgname query (To query a device Group)

 

Wait until the invalid track count is under 30,000 tracks

 

5.    symrdf -g dgname set mode async (Change the Copy mode to Asyncronous)

6.   symrdf -g dgname enable (Enables consistency protection for SRDF/A pairs in device group)