Tell it to store the information about the RDM with the VM.Select the Raw LUN that you want to use.Pick Raw Device Map as the new disk type.Technically we would not have to mount them to the primary node, but I’m doing it that way just to keep things organized. Next we will add each of the new RDM Disks to our primary cluster node.
I wont dive deep into this step as it would be different for each SAN vendor, but in summary, create your new LUNs as needed and add them to the storage group that is presented to your VMware hosts, after that rescan all of your VMware HBA’s and verify that the VMware hosts can see the LUNs. Present the new LUNsīecause the SQL servers are virtual machines using RDM’s I needed to create 3 new LUNs on the new SAN and present them to the VMware servers. UPDATE:įor an even easier way to do a migration or move check out my new article, its automated and only takes about 30 minutes. As it turned out the cluster that needed to be migrated was using shared VMDK files instead of RDM’s so I was able to just migrate the VMDK’s but I thought I would share the plan for migrating a cluster using RDM disks just in case someone else runs into this situation. After doing a bunch of reading and testing I developed the plan listed below. During a recent SAN installation I ran into a Microsoft SQL cluster that needed to be migrated from an old SAN to a new SAN.
0 kommentar(er)
