low IO period is recommended.

LUN migration can be applied on a per-LUN basis to migrate any public LUN to another public LUN or metaLUN. The LUN or metaLUN to which the source LUN or metaLUN will be migrated can have different characteristics than the source e.g. different RAID type etc. There are White Papers available on PowerLink

Hi Daveo

Do you have any idea of time taken for this process. Eg. Migrate 500Gig Lun.Are we talking about hours (1-3 or 6-8).

regards

dharshana

Hi,
Sure you can use LUN migration to move LUNs across Raid Groups. You can set priority (low, medium and high) to avoid impact on performance. Low and medium are good choices.

Anyway, for 500GB you will get dozens of hours until process is complete. LUN Migration is a slow copy I/O in I/O out block to block. Doesnt matter since is transparent to systems and users.

Until is not finished you can cancel migration but it will take also a long time to stop transitioning.

Regards from Spain,
Fernando.

My experience has been 10 GB an hour... I have done this twice on my CX 500, 100GB RAID 5 LUN to RAID 5 LUN took 9.5 hours.

This is correct: I've seen 60GB in 6 hours !
This comes down to 3MB/s, so that's why you don't want to start this during production hours, unless the lun isn't heavily used anyway. 500GB ? I'd start the migration on friday, right after work, so to speak (depending on your business of course)

Hi Darsh,
There is absolutely nothing to worry about the LUN migration, Make sure the target LUN will be the same size as your source. Just right click on the source LUN click on the migrate and select the target LUN. Once the migration is completed the target LUN gets the LUN ID of the source. I have did migration from Raid 1 to Raid 5 with out any problems. If its a clone private LUN, you need to take both the clone private LUN's out and then migrate. It all happens in the back end and nothing to worry about stopping the I/O.

Yep Very user friendly ! Who knows when they'll implement this in ECC or SymCLI or whatever..... I sure can imagine customers (we host customer hosts on our DMX's) want to migrate from expensive storage to cheaper storage on the fly....

Hi All

Thanks for your feed back, it¿s been really helpful. I did initiate the Migration with priority set to medium and returned with 52 Hours. I changed to ASAP and returned with 2 hours. Completed up to 92% in three hours and rest 8% was frozen for few hours. Finally I decided to stop the migration and it did stop with out any issues.

Thanks for your help.

Regards

You should indeed watch out for using the ASAP option as it is a high prio setting as you noticed.