Moving backing files of Microsoft Clustering Service cluster virtual machines using Raw Device Mappings

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

This article provides steps to move the underlying backing files of an MSCS virtual machine between datastores.

For more information, see Microsoft Clustering on VMware vSphere: Guidelines for Supported Configurations (1037959).

Note: This article is intended for use with RDM based clusters and not shared VMDK clusters.

Symptoms:

• You cannot perform a VMware vMotion or a VMware Storage vMotion operation on Microsoft Cluster (MSCS) virtual machines with a shared disk configuration.
• Virtual machines with SCSI bus sharing enabled cannot be vMotioned or Storage vMotioned while powered on.
• A cold migration of a virtual machine with Raw Device Mapping (RDM) results in the RDM being copied to a new VMDK file.

Environment

VMware ESX 4.1.x
VMware vSphere ESXi 6.5
VMware ESXi 4.0.x Embedded
VMware vSphere ESXi 7.0.0
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.0
VMware vCenter Server 5.0.x
VMware vSphere ESXi 6.7
VMware vCenter Server 6.7.x
VMware ESXi 4.1.x Installable
VMware ESXi 4.0.x Installable
VMware vCenter Server 4.1.x
VMware vCenter Server 6.5.x
VMware vSphere ESXi 6.0
VMware vCenter Server 7.0.x
VMware vCenter Server 5.1.x
VMware vCenter Server 6.0.x
VMware ESXi 4.1.x Embedded
VMware vCenter Server 4.0.x
VMware ESX 4.0.x

Resolution

Caution: Before performing the proceeding steps, take a full backup of all virtual machines.

Note: VMware recommends performing these steps in a maintenance window as the virtual machines are inaccessible during this time.

To move the underlying backing files of an MSCS virtual machine between datastores:

1. Shutdown the virtual machine 1.
2. Remove (but do not delete) the RDM pointers from virtual machine 1.
3. Cold migrate virtual machine 1 to the destination datastore.
4. Shutdown the virtual machine 2.
5. Create new RDM pointers on virtual machine 1.
6. Power on virtual machine 1.
7. Verify operating system and application functionality of virtual machine 1.
8. Remove and delete the RDM pointers from virtual machine 2.
9. Cold migrate virtual machine 2 to the destination datastore.
10. Add existing RDM pointers (created in step 5) to virtual machine 2.
11. Power on virtual machine 2.
12. Verify cluster functionality.
13. End maintenance window.

Additional Information

vMotion and Storage vMotion are not supported on Microsoft Cluster (MSCS) virtual machines with a shared disk configuration.

Microsoft Cluster Service (MSCS) support on ESXi/ESX
Migrating virtual machines with Raw Device Mappings (RDMs)
Guidelines for Microsoft Clustering on vSphere
使用裸设备映射移动 Microsoft 群集服务群集虚拟机的后备文件

Impact/Risks:

Before performing the steps in this article, a full backup of all virtual machines must be taken and verified first.

Always fully document RDM mappings. For more information about recreating RDM mappings, see:

• Microsoft Cluster Service (MSCS) support on ESXi/ESX (1004617)
• Migrating virtual machines with Raw Device Mappings (RDMs) (1005241)
• Microsoft Clustering on VMware vSphere: Guidelines for Supported Configurations (1037959)