UNSOLVED
- i thought the fancy schmancy V-Max will be able to do anything and everything, definitely being able to migrate device one the fly, considering Optimizer can do that. Maybe storage anarchist can write about that on his blog. Sorry for sounding cynical but this is disappointing, this migrator limitation, not being able to SRDF between thick R1 on DMX and thin R2 on V-max. So how do i migrate from DMX3/4 to V-max thin architecture ..i guess Open replicator.
This is indeed disappointing ! Even on a Clariion you can migrate to anywhere you'd like. I would use migration to even out hot spots (therefore you need to migrate from R5(31) to R5(31) for example) and why is there a disk group limitation ? I can certainly imagine migrating within the same disk group.
Weird.
Time for an RFE ?
Boom1
131 Posts
360
1
Posted March 4th, 2010 17:00
you cannot migrate in same disk group with same protection.
this is the limitation mention in document.
Restrictions
◆ You cannot migrate protected devices to an unprotected protection type.
Migrations of unprotected source devices to unprotected target are supported.
◆ You cannot migrate to the same protection type (RAID 5 (3+1) to RAID 5 (3+1)
and the same disk group number (disk group 1 to disk group 1). The desired
protection type or disk group number must be different from what exists on the
source devices.
◆ Device types not supported:
• VDEVs (TimeFinder Snap)
• Thin devices
• DATA devices
• Vault devices/SFS/VCM
• SAVE devices