GK devices aren't migrated. What you would do instead is simply present new GK devices from your target VMAX array and make the swap. They aren't migrated because there is no data stored on them - they are really just used for dedicated array communication from the host. There is no significant data from one array's GK's that needs to be migrated to another array. It makes the "migration" easier in that you just present new GK's from the new array and run a discover to see the new array.
I have same issue as well but this one is quite different, I need to replace the current gatekeeper and allocate new one from the same array.
What needs to be done from the server end. becaue from storage side allocation is straight forward. but for vm windows server what step should be done to use the new gatekeeper.
echolaughmk
2 Intern
•
522 Posts
794
2
Posted April 22nd, 2015 16:00
Hi,
GK devices aren't migrated. What you would do instead is simply present new GK devices from your target VMAX array and make the swap. They aren't migrated because there is no data stored on them - they are really just used for dedicated array communication from the host. There is no significant data from one array's GK's that needs to be migrated to another array. It makes the "migration" easier in that you just present new GK's from the new array and run a discover to see the new array.
HTH,
-K