Rapid Provisioning of Virtual Machines Using SAN Copy Overview
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager, System Center 2012 - Virtual Machine Manager
Rapid provisioning provides a method for deploying new virtual machines to storage arrays without the requirement for copying virtual machines over the network. Virtual Machine Manager (VMM) enables you to take advantage of your storage area network (SAN) infrastructure for cloning virtual machines, and use a VM template to customize the guest operating system. You can use rapid provisioning to deploy stand-alone virtual machines and virtual machines that are deployed as part of a service.
Rapid provisioning through SAN copy enables you to quickly create virtual machines from a SAN copy-capable template. You can create a SAN copy-capable template from a virtual hard disk that resides on a storage logical unit that supports SAN copy through cloning or snapshots. When you create a new virtual machine by using the SAN copy-capable template, VMM quickly creates a read-write copy of the logical unit that contains the virtual hard disk, and places the virtual machine files on the new logical unit.
When VMM deploys a virtual machine by using rapid provisioning through SAN copy, VMM uses a SAN transfer instead of a network transfer. During a SAN transfer, a SAN copy of the logical unit that contains the virtual machine is created and is assigned to the destination host or host cluster. Because the files for a virtual machine are not actually moved over the network when you transfer a virtual machine over a SAN, it is much faster than a transfer over a standard network.
Any storage that is accessible by the provisioned computer may be partitioned during the provisioning process even if a specific disk is selected to be used as the operating system disk. In this case data will be lost. To guarantee the use of a specific boot volume, use deep discovery and do not restart the computer before the deployment of the operating system completes.
Methods for rapid provisioning using SAN copy
You can use either of the following methods to create a SAN copy-capable template.
The outlined methods provide a high-level overview of the workflow, and assume that the prerequisites are met. Links to more detailed procedures for each method are provided. The prerequisites are described in Prerequisites for rapid provisioning using SAN copy, later in this topic.
Method 1: Create a SAN copy-capable template from a new virtual machine
From a storage pool that is managed by VMM and allocated to the host group where the target host resides, create and assign a storage logical unit to the host.
You can also use your storage array vendor’s management tools to create and assign the logical unit.
Create a virtual machine with a blank virtual hard disk file on the logical unit.
Install and customize the guest operating system and the applications that you want. Generalize the image by using Sysprep.exe with the /generalize and the /oobe options to generalize the associated virtual hard disk. For more information about Sysprep, see Sysprep Command-Line Options.
Use the Create VM Template Wizard to create a SAN-copy capable template from the virtual machine.
When you create the template, VMM transfers the logical unit that includes the virtual hard disk file from the host to the library through a SAN transfer. The library indexes the virtual hard disk file during the next refresh.
You can then create and deploy new virtual machines by using the SAN copy-capable template. When you deploy a new virtual machine, VMM creates a clone or snapshot of the logical unit that contains the virtual hard disk file, by using a disk that is allocated from the managed storage pool. VMM automatically unmasks the new logical unit to the host.
For detailed steps, see How to Create a SAN Copy-Capable Template from a New Virtual Machine.
Method 2: Create a SAN copy-capable template from an existing virtual machine
Create a logical unit from a storage pool that is managed by VMM and allocated to the host group where the library server resides. Assign the logical unit to the library server.
If you want to perform this procedure entirely within VMM, you must add the library server as a managed Hyper-V host. This action enables you to assign the logical unit to the library server. If you do not want to make the library server a managed Hyper-V host, you can use your array vendor’s management tools to register the logical unit to the library server.
On the library server, mount the logical unit to a folder path in the library share.
If the storage is managed by VMM, you can mount the logical unit to a folder path in the library share at the same time that you assign the logical unit to the library server.
Copy the existing virtual hard disk file (that has been generalized by using Sysprep) to the folder path where you mounted the logical unit.
Create a SAN-copy capable template by using the virtual hard disk file.
You can then create and deploy new virtual machines by using the SAN copy-capable template. When you do, VMM creates a clone or snapshot of the logical unit, which automatically creates a new logical unit from the storage pool. VMM automatically unmasks the new logical unit to the host.
For detailed steps, see How to Create a SAN Copy-Capable Template from an Existing Virtual Machine.
Prerequisites for rapid provisioning using SAN copy
Before you begin, ensure that the following prerequisites are met:
The storage array must support the new storage management features in VMM.
The storage array must support cloning or snapshots, and the cloning or snapshots feature must be enabled.
This might require additional licensing from your storage vendor.
The storage pool that you want to use for rapid provisioning must be under VMM management. To meet this requirement, you must add the Storage Management Initiative Specification (SMI-S) provider for the array, discover storage pools, classify the storage, and set the preferred allocation method for the storage array to either snapshot or cloning.
The storage pool that you want to use for rapid provisioning must be allocated to the host group where you want to use rapid provisioning of virtual machines.
The Hyper-V hosts that you want to use as placement destinations must be members of the host group. Additionally, the following prerequisites must be met:
If you want to create a SAN-copy capable template from a new virtual machine, the host where you create the virtual machine must also be a member of this host group.
If you want to create a SAN-copy capable template from an existing virtual machine, and want to create and assign the logical unit from the library server, the library server must be a member of this host group. Therefore, the library server must be a Hyper-V host. (If you do not want to add the library server as a host, you can assign the logical unit out-of-band by using your storage array vendor’s management tools.)
As of VMM in System Center 2012 R2, if you want to use rapid provisioning to deploy generation 2 virtual machines, you must choose a host with an operating system that supports them. Generation 2 virtual machines are supported as of Windows Server 2012 R2.
For more information about generation 2 virtual machines, see Understanding Generation 1 and Generation 2 Virtual Machines in VMM.
All Hyper-V hosts that you want to use for rapid provisioning and the library server must have access to the storage array. Also, they must use the same type of SAN connectivity. For SAN migrations to succeed, you cannot have some hosts that connect to the array through Fibre Channel and others that connect through iSCSI. Configuration varies, depending on your storage hardware.
For specific configuration information, see your storage array vendor’s documentation.
Configuration typically includes the following:
The Multipath I/O (MPIO) feature must be added on each host that will access the Fibre Channel or iSCSI storage array. You can add the MPIO feature through Server Manager. If the MPIO feature is already enabled before you add a host to VMM management, VMM will automatically enable MPIO for supported storage arrays by using the Microsoft provided Device Specific Module (DSM). If you already installed vendor-specific DSMs for supported storage arrays, and then add the host to VMM management, the vendor-specific MPIO settings will be used to communicate with those arrays.
If you add a host to VMM before you add the MPIO feature, you must manually configure MPIO to add the discovered device hardware IDs. Or, you can install vendor-specific DSMs.
For more information, including information about how to install MPIO, see Support for Multipath I/O (MPIO).
If you are using a Fibre Channel storage area network (SAN), each host that will access the storage array must have a host bus adapter (HBA) installed. Additionally, ensure that the hosts are zoned accordingly so that they can access the storage array.
If you use an iSCSI SAN, ensure that iSCSI portals have been added and that the iSCSI initiator is logged into the array. Additionally, ensure that the Microsoft iSCSI Initiator Service on each host is started and set to Automatic. For information about how to create an iSCSI session on a host through VMM, see How to Configure Storage on a Hyper-V Host in VMM.
For information about supported storage arrays, how to bring storage under VMM management, how to configure the preferred capacity allocation method for a managed storage array, and how to allocate storage to a host group, see Configuring Storage in VMM.
In This Section
Use the following steps to deploy a virtual machine by using rapid provisioning.
|Step 1: Use either of the following instructions:
- How to Create a SAN Copy-Capable Template from a New Virtual Machine
- How to Create a SAN Copy-Capable Template from an Existing Virtual Machine
|Describes how to create a SAN copy-capable template from either a new or existing virtual machine. Includes scenario-specific prerequisites.|
|Step 2: How to Deploy a New Virtual Machine from the SAN Copy-Capable Template||Describes how to create and deploy the new virtual machine by using the SAN copy-capable template.|