Filter
Top Products
Chapter 12 Cloning [Physical Servers]
This chapter explains how to use the server cloning function.
12.1 Overview
Cloning is a function used to deploy a cloning image collected from a single managed server (source server) to other managed servers
(destination servers).
This function shortens the time required for an initial installation as it can be used to install the same operating system and software on
multiple servers.
Software maintenance can also be performed quickly and easily by deploying a cloning image collected from a server on which patch
application or software addition or modification has been performed.
The information below is not copied when the cloning image is collected from the managed server; and will be automatically reconfigured
when the cloning image is deployed. This enables a single cloning image to be deployed to different servers.
- Hostname
- IP address and subnet mask for the admin LAN
- Default gateway for the admin LAN
Settings other than the above (such as those for applications and middleware) are not automatically reconfigured, please set them manually
before and after the cloning operation when necessary.
Cloning cannot be performed for Linux managed servers on which iSCSI disks have been configured.
Note
- When using ServerView Deployment Manager on the admin LAN, this function is disabled. Use the cloning function of ServerView
Deployment Manager. For details, refer to "Appendix B Co-Existence with ServerView Deployment Manager" in the "Setup Guide
VE".
- When using server cloning, regardless of the boot environment (local/SAN/iSCSI) or RAID configurations, only content from the
boot disk (first disk recognized by the BIOS on managed servers) is actually cloned.
Data disk content (second disk onwards) cannot be cloned. It is recommended to use other backup software, or copy features available
in storage systems for such purposes.
Note that all partitions (Windows drives or Linux partitions) included in the boot disk will be cloned.
Table 12.1 Cloning Target Examples
Disk Windows Drive Cloning Target
First
C: Yes
E: Yes
Second
D: No
F: No
- Because managed servers are restarted during the cloning process, it is necessary to stop all applications running on those servers
beforehand.
- The first partition must be a primary partition.
When multiple partitions exist within the disk of the cloning target, the drive letters for the drives other than the system drive may be
changed after cloning images are deployed. Change the drive letter back to the original letter, after deploying cloning images.
- Dynamic disks cannot be used.
- Cloning images can be collected with the following file systems. Note that LVM (Logical Volume Manager) partitions are not
supported.
- NTFS
- 118 -