VMware vSAN continuously enhance the feature set to provide the best hyperconverged infrastructure (HCI) to host virtualized Microsoft SQL Server (SQL Server) workloads. In addition to the long-existing capabilities to host SQL Server Always On Availability Groups or to provide support for iSCSI targets, the new feature, recently introduced in VMware vSAN 6.7 Update 3, – SCSI-3 Persistent Reservations (SCSI3-PRs) native support – makes it possible to host SQL Server Failover Cluster Instances on WSFC on VMDK on vSAN.
SCSI-3 Persistent Reservations (SCSI3-PRs) native support on VMware vSAN
SCSI3-PRs native support enables customers to create a new or move an existing Windows Server Failover Cluster (WSFC) with up to 6 nodes and 64 shared disks to VMware vSAN. SCSI3-PRs commands, used by WSFC to claim the ownership of a shared disk, are transparently passed to a VMDK and are arbitrated on the vSAN layer to simulate a dedicated LUN. To facilitate the ability to use direct SCSI commands, it’s required to set the SCSI bus sharing on a vSCSI controller of a VM, node of a cluster, hosting clustered VMDK(s), to physical. Consult this great technical article for more details on how to prepare vSAN for a WSFC deployment. For now, the support for shared VMDK for WSFC is for on-premises VMware vSAN and VMware Cloud on AWS. Support for clustered VMDKs on VMFS for on-premises versions of vSphere is yet to be introduced. Stay tuned for our announcements in this area.
Migrating existing WSFC to VMware vSAN
For many customers actively using or just planning to use VMware vSAN the question “how to migrate my current clustered SQL Server workload to vSAN platform” is a key in the journey to adopt an HCI solution. VMware supports the ability to cold migrate SQL Server FCI configurations using physical RDMs (regardlessof the underlying storage protocol – FC, iSCSI or FCoE) to VMware vSAN. The migration does not require complex operations and consists of the following steps:
- Preparing a WSFC cluster hosting SQL Server FCI with physical RDMs for a cold migration – you need to shut down the WSFC cluster and power-off all nodes of the cluster;
- Executing cold migration of the first node of the cluster to a datastore backed by vSAN (vSAN 6.7 Update 3 is required). During this step physical RDM(s) will be converted to VMDK(s) on VMware vSAN;
- Migrating of other nodes, if non-shared disks should be migrated as well. Before the migration, all VMs hosting remaining (non-migrated) nodes of the cluster should be reconfigured: shared pRDMs should be removed from the VM configuration;
- Adding back clustered disk resources using VMDKs from the first migrated VM;
- Validating cluster functionality and starting the cluster on VMware vSAN;
- Applying configuration and performance optimization recommendations for SQL Server workloads and vSAN.
Refer to the document SQL Server Failover Cluster Instance on VMware vSAN™ Native for more technical details and the enhanced migration procedure.
Support for SCSI3 persistent reservations and ability to host WSFC on VMware vSAN provides a flexibility and add design choices for customers looking to host high available SQL Server solutions on the hyperconverged infrastructure. This blog article and the migration documents cited above provides all necessary technical details and guidelines how to prepare, create or migrate, and maintain a SQL Server Failover Cluster Instances on VMware vSAN.
This blog post would not be possible without all hard work done by Tony Wu (Sr. Solution Architect, Storage Product Marketing, VMware Inc).