Using VMware Converter to convert Microsoft Cluster (MSCS) nodes to virtual machines (1002661)

Details

This article describes the procedure of converting Microsoft Cluster (MSCS) nodes to a set of virtual machines with VMware Converter.

Solution

To convert Microsoft Cluster (MSCS) nodes to a set of virtual machines:
 
Warning: This is only supported on VMware Server and VMware ESX. Unexpected results may occur if attempted within another VMware product.
Note: Before following this procedure, consult VMware documentation on setting up Microsoft Clustering Services within a virtual machine.
  1. Use VMware Converter to convert the operating system drive of each node and the operating system partition of each drive.
  2. If your data or quorum drive is already on a SAN LUN, map it as a physical disk in VMware Server, or a RDM in VMware ESX.  
  3. If your data or quorum drive is not on a SAN LUN:

    1. Create virtual disks for the data and quorum drives manually as per the instructions in the documentation for your VMware product.
    2. Clone the data to the new virtual disks. Clone the data using a method that copies all files and directories and preserves all permissions. Some methods for cloning the data are: 

      Robocopy http://technet.microsoft.com/en-us/magazine/cc160891.aspx
      ViceVersa http://www.tgrmn.com/
      Ghost http://www.symantec.com/business/products/overview.jsp?pcid=2247&pvid=865_1
      Acronis http://www.acronis.com/
      DoubleTake http://www.doubletake.com/
      NetBackup http://www.symantec.com/business/products/overview.jsp?pcid=2244&pvid=2_1

      Note: VMware does not endorse or recommend any particular third party utility, nor is the list above meant to be exhaustive. 

      THE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.


      Based on VMware KB 
      1002661
  • 0 Los Usuarios han Encontrado Esto Útil
¿Fue útil la respuesta?

Artículos Relacionados

Hardware and firmware requirements for 64-bit guest operating systems

PurposeThis article explains the host machine hardware and firmware requirements for installing...

Logging in to the vCenter Server 5.0 Web Client fails with the error: unable to connect to vCenter Inventory Service

DetailsAfter upgrading from vCenter Server 4.1 to 5.0, you experience these symptoms:Cannot log...

Multiple network entries in vCenter Server 5.0.x after migrating virtual machines from a virtual switch to a virtual distributed switch

SymptomsAfter migrating virtual machines from a virtual switch to a virtual Distributed...

Minimum requirements for the VMware vCenter Server 5.x Appliance

PurposeIf you are using the VMware vCenter Server Appliance, beginning with vSphere 5.0 you can...