We are cloning a SQL database from a physical server to a VMware virtual server.
The clone process creates a RDM on the virtual server, a VMDK with a semi-random name each time it runs.
The problem is that when the RDM is created, it is only assigned the initiators for the VMware host server the VM is assigned to. This makes it impossible to use VMotion to relocate the virtual SQL server if there's a problem with the host. So, high availability is not possible.
Is there a way during the clone process to specify an initiator group for the new cloned LUN?
Or, is it possible through a Powershell script to, after the clone, modify the cloned LUN so it includes an initiator group or a list of the other initiators in the VMware cluster?
