And even if they can be, they are critical enough that the whole “if it ain’t broke, don’t fix it” thing comes into play. Many of our clients have legacy systems and applications that cannot be virtualized. It’s definitely not as crazy as it used to be, but plenty of migration work is still done regularly. At any given time I’m involved with a couple of migration projects. Many of these clients are implementing Unified VNX models and we also need to have a data migration strategy for NAS (moving from another NAS platform or a physical file server to a VNX/Isilon).
Robocopy emcopy block changes cifs how to#
However, there are still plenty of clients with physical hosts, and they need to figure out how to get the data from an older array to the new one (VNX/VMAX). What used to require a lot of planning and create a lot of anxiety has been reduced to a few clicks and no downtime! Data migration projects I’ve been involved in have declined significantly over the years, and I’m not complaining-because doing data migrations is not how I like to spend my nights and weekends.
We simply stand up the new array and present the LUNs to the ESX cluster and the VMware dudes take over from there. It is true that VMware Storage vMotion has greatly changed the data migration landscape. By Prashant Shah Data, Migration, Storage, ToolsĪ blog post about data migration in 2014?!? Isn’t everything virtualized and Storage vMotion the way to go? And these days, if the topic doesn’t have the word “cloud” in it, is it even worth talking about?
0 kommentar(er)
