VM Cloning
ZSphere provides two cloning methods to meet different service needs: full clone and instant full clone.
Full Clone
A full clone does not share data with the source VM. The source VM is first converted into an image file that contains the files and configuration required by the VM and is stored in image storage. The image is then pushed to data storage as an image cache from which the cloned VM is created. The cloned VM can use data storage different from that of the source VM.
A fully cloned VM is isolated from and independent of its source, so the source VM does not affect its performance. Full cloning typically consumes more storage. However, ZSphere optimizes batch full-clone operations by storing only one image cache on each data storage. This reduces storage consumption and accelerates the startup of cloned VMs.
Instant Full Clone
Instant full cloning first uses linked-clone technology to create a VM that temporarily depends on the source VM, enabling fast provisioning. A background task then merges snapshots to separate the cloned VM's data completely from the source. The cloned VM can start quickly and becomes fully independent after the merge completes, with no subsequent performance impact from the source VM.