This section explains how to collect and delete cloning images.
Collection of a cloning image
Use the following procedure to collect cloning images:
After installing an OS, stop the target L-Server.
Right-click the target L-Server in the orchestration tree, and select [Cloning]-[Collect] from the popup menu.
Click the [OK] button.
A given cloning image (identified by its name attribute) can be managed by image version.
If a cloning image is created using VM management software, it can be used as is.
Note
If an L-Server is created with a specified Windows image, when deploying the image use Sysprep, provided by Microsoft, to reconfigure the properties unique to the server. By executing Sysprep, the user information and OS setting information are reset.
For details on Sysprep, refer to the information provided by Microsoft.
If stopping or restarting of the manager is performed during execution of Sysprep, the operation being executed will be performed after the manager is started.
Until the process being executed is completed, do not operate the target resource.
When using MAK license authentication for activation for the following OSs, Sysprep can be executed a maximum of three times.
Microsoft(R) Windows Server(R) 2008 R2
Microsoft(R) Windows Server(R) 2008
Microsoft(R) Windows(R) 7
Microsoft(R) Windows Vista(R)
Since Sysprep is executed when creating L-Server with images specified or when collecting cloning images, collection of cloning images and creation of L-Servers with images specified cannot be performed more than four times. Therefore, it is recommended not to collect cloning images from L-Servers that have had cloning images deployed, but to collect them from a dedicated master server. The number is also included in the count when Sysprep is performed when a template is created using SCVMM.
When using System Center 2012 Virtual Machine Manager or later version as VM management software, only cloning images with high-availability attributes can be used in Resource Orchestrator.
Point
Images are stored in the SCVMM library.
Specify a library that has sufficient disk space available to store the collected images.
When [Automatic selection] is specified in the [Collect a Cloning Image] dialog, selection is made from libraries registered with SCVMM, but collection of images may fail, as the available disk space of libraries is not managed by SCVMM.
Resource Orchestrator uses SCVMM templates for collection of images.
When collecting images from L-Servers, a template is created using a name with the version number added to the image name. When retrieving the template created by the user as an image, the template is treated as an image.
In order to collect images of L-Servers, a work area equal to the size of the disk (the system volume, all data disks, snapshot, and system configuration file) of the target of L-Server creation is necessary. This work area is released, when collection of images is complete.
When collecting images, collecting only system volumes, or images including data disks can be selected.
In Resource Orchestrator, the virtual hard disk of the primary channel (0) of the IDE device is managed as the system volume.
DVD drives other than the secondary channel (0) of the IDE device are deleted. A DVD drive is added to the secondary IDE channel (0) even if there is no DVD drive in the image. If DVD drives other than this drive exist, they are deleted.
Collection of images cannot be collected, when there are snapshots. Collect images after deleting snapshots. When creating checkpoints from the SCVMM management console or creating snapshots from Hyper-V manager, collection of images will fail.
Collection of cloning images fails, until the merge process of snapshot files is completed, even if the snapshots are deleted.
Collect cloning images after until the merge process is complete.
When the host of Hyper-V is Windows Server 2008 R2, the merge process is performed only when the virtual L-Server has been stopped.
When retrieving SCVMM templates created by users using SCVMM, manage them as follows:
The template name is the image name.
The virtual hard disk of the primary channel (0) of the IDE device is managed as a system volume.
When creating an L-Server using an image which contains data disks other than system volumes, creation of an L-Server including data disks or excluding data disks can be selected.
When creating an L-Server from an image with no system volume, an L-Server with no system volume will be created.
On L-Servers created by retrieving an image from a template where DVD drives are connected to somewhere other than the secondary IDE channel (0), these DVD drives will be deleted.
When L-Servers are created from an image retrieved from a template not connected to a DVD drive, the DVD drive will be added to the secondary IDE channel (0).
Collecting Images of Linux VM Guests
When using SCVMM, System Center 2012 SP1 or later, images cannot be collected from Linux VM guests. This specification is for SCVMM.
Therefore, create a template on SCVMM referring to the procedure described at the following URL: After that, register the created template in Resource Orchestrator as an image.
http://technet.microsoft.com/en-us/library/hh427282.aspx |
However, it is necessary to satisfy all following conditions in order to use the created template in Resource Orchestrator.
Install the integration service (ICs) on the Linux VM guest which is used as the source for the template.
Install the Linux guest agent of SCVMM on the Linux VM guest which is used as the source for the template.
Configure high-availability in the hardware configuration of the template
Select an OS for the VM guest from the [Operating System], selecting [Create new Linux operating system customization settings] from [Guest OS Profile] in the operating system configuration of the template
When creating an L-Server specifying the image of a Linux VM guest, each parameter of the L-Server cannot be customized.
Access Control Configuration File of Image Storage Location
By specifying unavailable library shared path names in the access control configuration file of the image storage destination in advance, cloning image storage destinations can be controlled based on user groups.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
The configuration files can be divided into definitions that are available for each user group and definitions that are common to the system. When there are both types of files, the limitations of both are valid.
For User Groups
library_share_user group name_deny.conf
Common on System
library_share_deny.conf
In the configuration file, library shared path names are entered on each line.
Library_shared_path_name |
Example
An example configuration file is indicated below:
\\rcxvmm1.rcxvmmshv.local\MSSCVMMLibrary |
Deleting Cloning Images
Use the following procedure to delete cloning images:
Select the target image pool on the orchestration tree.
The [Resource List] tab is displayed.
Right-click the cloning image to be deleted, and select [Delete] from the popup menu.
Click the [OK] button.
The cloning image is deleted.
When SCVMM template creation requirements are not met, or configuration changes are performed outside Resource Orchestrator, collection of images may fail.
When deleting cloning images, the corresponding templates in the SCVMM library are deleted.
When deleting these templates, related files (such as .vhd and .vfd) will remain in the SCVMM library as only template definition files are deleted.
When these related files are unnecessary, delete them individually from SCVMM.
Information
By creating the following setting file beforehand, when deleting cloning images, the related files that have no dependencies with other templates can be deleted at the same time.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\vm
delete_image_all_files_scvmm
It is not necessary to describe content in the configuration file.
As in the case of deletion of related files from the SCVMM management console, only the related files are deleted from the SCVMM library. The folder where the related files are stored will remain.
