This section explains how to collect and delete cloning images.
Collecting a Cloning Image
Use the following procedure to collect cloning images:
After installing the operating system, right-click the target L-Server in the orchestration tree, select [Cloning]-[Collect] from the popup menu, and click <OK>.
Cloning images are stored in image pools.
Note
When the server type is "Physical", perform collection of cloning images after placing the server used as an L-Server into maintenance mode from the server tree.
For details, refer to the information about cloning in the "ServerView Resource Coordinator VE Setup Guide".
However, the network parameter auto-configuration function which can be configured for cloning images cannot be used for Resource Orchestrator.
When the target server of cloning image collection has a redundant NIC configured, release redundancy and then perform collection.
Point
[VMware]
When "Automatic" is specified in the [Collect a Cloning Image] dialog, it is assumed that the virtual storage resource containing the L-Server for collecting cloning images has been specified.
[Hyper-V]
Images are stored in the SCVMM library.
Specify a library which has sufficient available disk space to store the collected images.
When "Automatic" 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.
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.
Deleting a Cloning Image
Use the following procedure to delete cloning images:
Left-click the target image pool in the orchestration tree.
The [Resource List] tab is displayed.
Right-click the target cloning image in the image pool, and select [Delete] from the popup menu.
Click <OK>.
The cloning image is deleted.
[Hyper-V]
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 configuration definition file) of the target of L-Server creation is necessary. This work area is released, when collection of images is complete.
When collecting images, data disks other than the system volume are deleted.
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.
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 from an image retrieved from a template with data disks other than the system volume, the data disks other than the system volume are deleted.
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).
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, .vfd, and Unattend.xml) 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
[Hyper-V]
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]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/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 type of files, the limitations of both are valid.
For User Groups
library_share_user_group_name_deny.conf
Common to System
library_share_deny.conf
In the configuration file, library shared path names are entered on each line.
Library_shared_pathname |
Example
An example definition file is indicated below:
\\rcxvmm1.rcxvmmshv.local\MSSCVMMLibrary |
