VLUN migration migrates one STD to another STD (thick devices) and in case of Thin devices, it migrates the tdev from one Pool to another.

You can check TF clone or some host based migration tool to migrate from std to thin.

regards,

Saurabh

Hi Hamilton00 and dHappy New Year.

As Rohilla said the VLUN migration migrates one thin device from one Thin Pool to another.

To migrate a thick to a thin and what tool or method you are going to use it depends of the O.S.

If you want to do the migraiton on a Unix host and has Veritas Volume manager, then use the host mirror copy procedure to do the migration.

If you are on ESX enviroment via Storage vMotion you can do the migration.

On windows machine i don't remember if you can you use the PPME to do that migration.

On Storage based you can use TimeFinder Clone or SRDF and it depends again from the Enguinity code that your Storages uses. 

Have you guys checked the symmigrate and its features. It might supported if the code is supported to do Thick to Thin data move.

Regards,

Periyakaruppan N (Peri),

Hi Hamilton00

With Enginuity version 5874 and higher, TimeFinder supports thick-to-thin and

thin-to-thick source-target device pairs, which can be used for local thick-to-thin

migration.

Yes, I better want to watch and make sure each steps. Happy new year J

Regards,

Periyakaruppan N (Peri),

Hi Peri and Happy New Year,

the symmigrate command is being used by the GUI of VLUN migration through SMC.

Through SMC everything is done by the GUI automatically, but if you want to use the symmigrate command via CLI, then you have to do all the steps on your own. (create the target device, create the migration txt file, validate the command, name the migration session, establish the migration session, etc).

Zikas wrote: On Storage based you can use TimeFinder Clone or SRDF and it depends again from the Enguinity code that your Storages uses.

how are you going to use SRDF to perform an "inside of array" migration ?

It depends on the OS, clustering.

Sounds like I'll need to use host based options like Storage vMotion for ESXi and PPME hostcopy for Windows. I haven't used TimeFinder Clone but I assume there is a point where the host has to be offline to perform the cutover. With the host based options there is no downtime for the applications.

Ok sorry then. SRDF has nothing to do within the same arrays.