A clone is a copy of an existing virtual machine. When the cloning operation is complete, the clone is a separate virtual machine. The resulting clone is an independent copy of a virtual machine and shares nothing with the source virtual machine after the cloning operation. Ongoing operation of a clone is entirely separate from the source virtual machine.
- Cloning is not supported for customers who leverage virtual machines with the multi-vNIC feature
- Source machines must not be domain joined.
- Cloning is not supported for customers using our Managed Operating System Services
Customers using the clone function for Windows Servers should carefully review the Microsoft Sysprep for Server Roles technet article. Sysprep is a component of creating a clone and as such certain OS Roles are not supported in the clone process.
Additional attached disks from the source server are not automatically attached to the clone. If these disks are intended to be attached to the clone then this is a manual process on the guest operating system.
Cloning is not supported from powered off servers. The source server must be powered on in order to clone as a new virtual machine.
Navigate to the Virtual Machine you wish to clone. From the "action" menu, select the "clone" option.
The Clone Server form is used to input critical data points (server name, administrator password, network VLAN, storage type) for the resulting virtual machine clone.
Customers can monitor the Queue for status of the Clone process or wait for email notification.
Q: Can I clone a server with a snapshot in place?
A: Yes this is a supported function. However there are a couple of nuances to understand when executing such an action:
- The source server will be powered off during the clone operation
- The existing snapshot on the source machine will remain intact
- The cloned server will not have a snapshot. It will be a clone of the current state of the source server, including any changes post snapshot