Data Migration Tips: Part II
Now, to obtaining where I left off. Yesterday I discussed some of the pluses and minuses to host based migration methodologies and vendor supplied migration methods, utilizing internal replication functions in partnership with vendor supplied scripts. Today I’ll briefly discuss:
Hardware Virtualization
Software Virtualization
When migrating between dissimilar vendor’s storage arrays, the choice to virtualize the previous disk and possibly the new disk offers a path for migrating data. There’s 2 types of accomplishing this: hardware virtualization and software virtualization.
Hardware array virtualization is the concept of utilizing the built-in functions of your vendor’s array or an inline storage type router to provide the existing storage towards the host, from the new array or inline storage router. This allows to the technique new array or storage router’s software licensing presenting the old storage, and migrate the old storage to new internal storage for the new array, with generally only a brief interruption for the production environment during an outage window.
Careful attention needs to be paid on the grouping of application dependent disks in “consistency groups” during migration to make certain application data integrity
Built in hardware virtualization is merely offered by a fixed quantity of storage array vendors and storage router vendors
There generally is a licensing cost linked to hardware virtualization






