Clone a Template to a Template

You can clone a template to a template after you have created one. Templates are primary copies of virtual machines that allow you to create virtual machines that are ready to use. You can make changes to the template while keeping the original in working order, such as installing additional software in the guest operating system.

Prerequisites of Clone a Template to a Template

First of all need to verify that you have the following permissions –

Virtual Machine >Provisioning – Clone template on the source template in virtual machine 

Virtual machine >Inventory – Create from an existing file in the same folder as the template.

Datastore > Allocate space on all datastores where the template will be created.

Clone a Template to a Template
Image shows Clone a Template to a Template

Procedure to Clone a Template to a Template

  • Start the Clone Template to Template wizard.
OptionDescription
From a valid parent object of a
virtual machine
a. Right-click any inventory object that is a valid parent object of a virtual
machine and select New Virtual Machine.
b. Select Clone template to template and click Next.
c. On the Select a template to clone page, browse to the template that you
want to clone or accept the default one.
From a templateRight-click a template and select Clone to Template.
Clone a Template to a Template
  • Enter a unique name for the template and choose the data center or folder where it will be deployed on the Select a name and folder page. Next should be selected.

The name of the files and folders on the disk is determined according to the template name. The template files are named win16tmp.vmdk, win16tmp.nvram, and so on if the template is named win16tmp. The names of the files in the datastore do not change when you change the template name.

Folders are used to store virtual machines and templates for various groups within an organization, and they can be assigned permissions. You can put all virtual machines and templates in a datacenter and organize them differently if you prefer a flatter hierarchy.

  • Choose a host or cluster resource for the template on the Select a compute resource page.

The results of the compatibility checks are displayed in the Compatibility pane.

  • Select the datastore or datastore cluster where the virtual machine configuration files and all virtual disks will be stored on the Select storage page. Next should be selected.
OptionDescription
Clone a virtual machine that has
vPMem hard disks
a. Choose the type of storage for the template by selecting the Standard,
the PMem, or the Hybrid radio button.
If you select the Standard mode, all virtual disks will be stored on a
standard datastore.
If you select the PMem mode, all virtual disks will be stored on the host local PMem datastore. Configuration files cannot be stored on a PMem
datastore and you must also select a regular datastore for the
configuration files of the virtual machine.
If you select the Hybrid mode, all PMem virtual disks remain stored on a
PMem datastore. Non-PMem disks are affected by your choice of a VM
storage policy and datastore or datastore cluster.
For more information about persistent memory and PMem storage, see
the vSphere Resource Management guide.
b. (Optional) From the Select virtual disk format drop-down menu, select a
new virtual disk format for the template or keep the same format as the
source virtual machine.
c. (Optional) From the VM Storage Policy drop-down menu, select a virtual
machine storage policy or leave the default one.
d. Select a datastore or a datastore cluster.
e. Select the Disable Storage DRS for this virtual machine check box if you
do not want to use storage DRS with the virtual machine.
f. (Optional) Turn on the Configure per disk option to select a separate
datastore or a datastore cluster for the template configuration file and
for each virtual disk.
Clone a virtual machine that does
not have vPMem hard disks
a. Select the disk format for the virtual machine virtual disks.
Same format as source uses the same disk format as the source virtual
machine.
The Thick Provision Lazy Zeroed format creates a virtual disk in a
default thick format. Space required for the virtual disk is allocated when
the virtual disk is created. Data remaining on the physical device is not
erased during creation, but is zeroed out later, on demand, on first write
from the virtual machine.
Thick Provision Eager Zeroed is a type of thick virtual disk that supports
clustering features such as Fault tolerance. Space required for the virtual
disk is allocated at a creation time. In contrast to the flat format, the data
remaining on the physical device is zeroed out when the virtual disk is
created. It might take much longer to create disks in this format than to
create other types of disks.
The Thin Provision format saves storage space. At first, a thin
provisioned disk uses only as much datastore space as the disk initially
needs. If the thin disk needs more space later, it can expand to its
maximum capacity allocated to it.
b. (Optional) Select a VM storage policy or leave the default one.
c. Select a datastore or a datastore cluster.
d. (Optional) Turn on the Configure per disk option to select a separate
datastore or a datastore cluster for the template configuration file and
for each virtual disk
Clone a Template to a Template
  • Review the template settings on the Ready to finish page before clicking Finish.

In the Recent Tasks pane, you can see how far the clone task has progressed. When the task is finished, the template is added to the inventory.

Read more Virtualizations

Leave a Comment

Your email address will not be published.