Shulou(Shulou.com)06/03 Report--

The purpose of deploying vSphere is to run virtual machines on it, so as to realize server virtualization. However, a new virtual machine is obviously very troublesome, so it is more convenient to deploy virtual machines through cloning, and a certain backup effect can also be achieved. The replica virtual machine has the same virtual hardware, installed software and other properties of the original virtual machine.

VCenter supports two types of clones: full and linked clones.

1. A full clone is a backup that is completely independent of the original virtual machine. It does not share any resources with the original virtual machine and can be used separately from the original virtual machine.

2. Link cloning needs to share the same virtual disk file with the original virtual machine, and cannot run independently from the original virtual machine. However, the use of shared disk files can greatly shorten the time to create cloned virtual machines, and at the same time save valuable physical disk space. By linking clones, you can easily create a separate virtual machine for different tasks.

Case environment:

Cloning a virtual machine needs to be stored on an external shared storage device, so you need to transfer the virtual machine to a shared device, you can refer to a previously written article:

Https://blog.51cto.com/14227204/2419879

Refer to the article before the migration.

The previous point is that it is a bit verbose and useless, if the reader in front of the screen does not want to see it, you can turn directly to the following to see the template deployment.

First, transfer the virtual machine file to an external shared device:

Start cloning after the transfer is complete:

What I am cloning here is the Linux virtual machine. There is no need to customize the operating system if you want to clone the Linux virtual machine. Here is just a demonstration of this feature. This is generally used for Windows cloning. The following figure shows the configuration required by the window system to create a new specification:

I feel a little troublesome here. Here is the second method to solve the problem that the system cannot be used because of the same SID after the virtual machine is cloned:

Bring your own software in the Windows system

The path is: C:\ windows\ system32\ sysprep\ sysprep.exe

This software can repackage the system and change the SID number.

If you clone a virtual machine in this way, the first virtual machine will be damaged due to too many clones, and then the cloned virtual machine will be equivalent to cloning a bad virtual machine. So we generally need to convert the first virtual machine into a template to deploy the virtual machine (note: the virtual machine can be converted into a template only when the virtual machine is turned off! )

After you have finished making the template, start deploying:

Wait for the deployment to be completed:

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.