2015-09-22 12:41 PM
I have completed several LUN transitions from 7 Mode to Cluster Mode using the 7 Mode Transition Tool successfully, but this past weekend we had a failure. The Windows cluster hosting the LUNs that I was trying to migrate is the only one that already has a few LUNs on cdot, as well as 7-mode LUNs I'm trying to transition. The 7MTT choked when it saw that the IQN already existed, so it didn't map the 7-mode LUNs. I mapped them manually before restarting the Windows hosts, but then we had LUN ID conflicts between the 7-mode and cdot LUNs. I had to rollback to transition.
I believe I have a resolution to this problem, but would love to get feedback from any of you that might have a comment. Here's what I'm planning to do:
Anyone see a gap or flaw in this plan? Any recommendations?
2015-09-29 12:58 PM
Thanks. So if I remove the cdot LUNs and the initiator groups and then remap them after the other LUNs transition, are you indicating that won't resolve my issue? We'll still potentially have a conflict due to the signature? If so, how can I strip the existing signature off of the cdot LUNs?
2015-10-01 03:42 AM
Windows is writing a serial to the LUNs, it's not the Netapp LUN serial.
1) create the snapmirror, let it be in sync
1a) stop the Windows cluster and make sure that's not starting if server is rebooted
2) shutdown the server
3) unmap the LUNs
4) update, quiesce and break the snapmirror
5) map the LUNs on the destination filer
6) start the server
7) rediscover the disk in windows
You don't need 7MTT or SnapDrive for this.
Just pure comandline :-)