[Complete Tutorial] How to Clone a VM in VMware ESXi

Managing virtual environments often requires duplicating existing setups. Whether you need to test a new software patch or deploy multiple identical servers, knowing how to clone VM in VMware ESXi is a vital skill. This process saves you the time and effort of installing an operating system from scratch.

This tutorial is designed for both beginners and experienced system administrators. We will explore three reliable ways to replicate your virtual machines: using the Host Client, the SSH command line, and vCenter. By the end of this guide, you will be able to perform a clone in VMware ESXi 8 or older versions with confidence.

What Does Cloning a VM in VMware ESXi Mean

A virtual machine clone is an exact duplicate of an existing VM. This copy includes everything from the operating system and installed applications to the specific hardware configurations and data files. Essentially, it allows you to create a functional “twin” of your server without the need for manual installation.

It is important to understand how a clone differs from other common VMware features:

• Clone: This is an independent copy of a VM. Once created, it functions separately from the original source.
• Snapshot: A snapshot is a “point-in-time” save of a VM’s state. It is primarily used for quick rollbacks before making risky updates and depends on the original disk files to work.
• Template: A template acts as a master image that cannot be powered on. It serves as a gold standard for creating many identical VMs across your infrastructure.

Understanding these differences helps you choose the right tool for your specific task. Whether you’re cloning a VM in VMware ESXi 7.0 or ESXi 8, the goal is usually to create a standalone copy for testing or production.

Method 1 – Clone a VM Using ESXi Host Client

If you are using a standalone host without vCenter, you can manually copy files to achieve a clone. This is the most common way for users learning how to clone VM in VMware ESXi when working with a single server. This method is simple and suitable for beginners.

1. Power off the VM: Shut down the source virtual machine to make sure all data is saved correctly.
2. Open Datastore Browser: Click on “Storage” in the left menu, select your datastore, and click “Datastore browser.”
3. Create a New Folder: Create a new folder in the datastore named after your new cloned VM.
4. Copy VM Files: Navigate to the original VM’s folder, select the .vmx and .vmdk files, and copy them to the new folder.
5. Register the VM: Go to the “Virtual Machines” section, click “Create / Register VM,” and choose “Register an existing virtual machine.”
6. Select the File: Browse to the new folder, select the .vmx file you just copied, and complete the wizard.
7. Choose “I Copied It”: When you first power on the new VM, VMware will ask if you moved or copied it; select “I copied it” to generate a new unique ID.

Method 2 – Clone a VM Using SSH and vmkfstools

There are times when the Host Client is unavailable or slow due to large file sizes. In these cases, using the Command Line Interface (CLI) via SSH is a faster and more professional way of cloning a VM in VMware ESXi 7.0 or 8.0.

1. Enable SSH: Go to the ESXi Host Client, right-click “Host,” select “Manage,” then “Services,” and start the SSH service.
2. Log in via SSH: Use a tool like PuTTY to log into your ESXi host with your root credentials.
3. Create a New Directory: Navigate to your datastore and create a new folder for your clone using the mkdir command.
4. Clone the Disk: Run the command vmkfstools -i /vmfs/volumes/source/old.vmdk /vmfs/volumes/destination/new.vmdk. This “cloning” command creates a fresh copy of the virtual disk.
5. Copy the Config File: Copy the .vmx file from the old folder to the new one using the cp command.
6. Register the VM: Go back to the Host Client and register the new .vmx file as a virtual machine.

This method is highly efficient for admins who prefer automation. It is the most direct way to handle the process when you need to clone a VM in VMware ESXi without using a graphical interface.

Method 3 – Clone a VM Using vCenter

vCenter is a centralized management tool used to control multiple ESXi hosts from a single interface. If your environment uses vCenter, cloning a VM is much easier because it includes a built-in “Clone” wizard that automates the entire process.

1. Locate the VM: Log in to the vSphere Client, find your virtual machine in the inventory, and right-click it.
2. Start the Wizard: Select “Clone” and then “Clone to Virtual Machine.”
3. Name the Clone: Enter a name for the new VM and select a folder or data center location.
4. Select Resources: Choose the ESXi host and the datastore where the new VM will be stored.
5. Clone Options: Choose whether to customize the operating system or the VM’s hardware settings.
6. Review and Finish: Check your settings on the summary page and click “Finish” to start the automated cloning process.

This method is the preferred way for admins managing large environments. It is the most user-friendly approach to cloning a VM in VMware ESXi 7.0 or 8.0 because it handles file copying and registration for you automatically.

Best Practices When Cloning VMware VMs

Following these best practices will help you safely clone VM in VMware ESXi 7.0 and 8.0, while avoiding data issues and network conflicts.

Power Off the Source VM Before Cloning

Always shut down the source virtual machine before you begin cloning. This ensures all files and data are in a stable, consistent state and prevents disk corruption.

Rename the Cloned VM Right Away

Give your new virtual machine a clear and unique name immediately after creation. This prevents confusion between the original VM and its copy in your inventory.

Update Network Settings to Avoid Conflicts

Check and adjust the IP address and network configuration for the cloned VM. Duplicate network identities can cause outages or connection problems on your local network.

Verify Hardware Settings for the New VM

Confirm CPU, memory, and storage allocations match what the cloned VM needs. Using incorrect hardware settings can lead to poor performance or boot failures.

Reset System Identifiers for Windows VMs

Use guest customization or Sysprep when cloning Windows virtual machines. This creates new unique IDs and stops issues with duplicate computer accounts.

VM Cloning Isn’t Enough: Better Protection with i2Backup

While learning how to clone a VM in VMware ESXi is useful for duplication and testing, it is not a complete data protection strategy. A major drawback of cloning a VM in VMware ESXi is that it often requires shutting down the source machine to ensure data consistency, which can cause unacceptable downtime in 24/7 production environments.

i2Backup offers a more resilient alternative by running background backups without interrupting your VMs. Unlike cloning, this solution does not require you to power off your virtual machines, keeping your operations running smoothly while protecting your data from hardware failures and accidental loss.

Key Features of i2Backup

• Agentless VM Backup: i2Backup provides agentless VM backup at scale without installing agents for data protection and VM migration. It uses native virtualization platform APIs for seamless backup, replication, and migration with zero production impact.
• Broad Compatibility Across Platforms: i2Backup is fully compatible with Windows, Linux, Unix systems, mainstream databases (e.g. oracle, MySQL, SQL Server, IBM DB2, etc.), and virtualization environments (VMware, Hyper-V, etc.).
• Multi-dimensional Protection: i2Backup employs write-once-read-many (WORM) compliant storage to make backups immutable, preventing unauthorized changes or deletion.
• Light-fast Recovery, Zero Downtime: Built on cutting-edge transmission technologies, information2’s enterprise backup solution i2Backup ensures timely and fast recovery in the event of data disaster or server failure.
• Flexible Scheduling: Allows you to configure backup schedules on demand to fit your business rhythm, such as hourly, weekly, monthly, yearly, etc. After schedules are configured, the enterprise backup software i2Backup will run tasks automatically.

In conclusion, it is important to remember that cloning is meant for duplication, while i2Backup is built for protection. Using both techniques together ensures your VMware environment is both flexible and secure.

FAQ

Q1: Can I clone a running VM in VMware ESXi?
If you are using vCenter, you can clone a running VM because the system handles the data consistency for you. However, if you are using a standalone Host Client, it is best to power off the machine first. This prevents data corruption and ensures that the cloned virtual disk is an exact, stable copy.

 

Q2: What is the difference between cloning and exporting a VM?
Cloning creates an internal copy of the VM that stays within your VMware environment. Exporting converts the VM into a portable OVF or OVA file. You usually export a VM when you need to move it to a different physical location or a separate network.

 

Q3: Does cloning a VM in VMware ESXi 8 change the IP address?
No, the cloning process creates an exact “twin,” including the network configuration. After you finish how to clone a VM in VMware ESXi, you need to manually log into the new machine to change its IP address. This step is necessary to avoid network conflicts on your local area network.

 

Q4: Do I need vCenter to clone a VM?
You do not strictly need vCenter, but it makes the task much faster. Without vCenter, you should use the manual file copy method in the Host Client or use the SSH command line. Both of these manual methods are effective for users who are managing a single ESXi host.

Conclusion

In this guide, we covered three different ways to handle your virtualization needs. Whether you prefer the visual steps of the Host Client, the speed of the SSH command line, or the automation of vCenter, you now have the tools to clone VM in VMware ESXi successfully.

The right method depends on your specific environment. While cloning a VM in VMware ESXi 7.0 or 8.0 is perfect for creating quick copies for testing, remember that it is not a substitute for a real backup. By combining these cloning techniques with a professional solution like i2Backup, you can ensure your virtual environment is both highly flexible and fully protected. Always remember to follow best practices, such as renaming your clones and updating network settings, to keep your infrastructure organized.