Hello all,
I have a couple of questions around linked clones:
Firstly, is there a rule of thumb around how many linked clones you can make from a single parent VM?
Secondly, to patch VM's that are linked do I simply need to power on the original VM, make the changes, power it off and then make a new snapshot and then modify the desktop pool?
Regards,
Ashley
Do you mean the clones or the snapshots?
The clones scale really well as they are duplicated per Datastore but shared across different pools. Its most likely too early days to tell if there is a rule of thumb on how many is to many, probably more than you would use.
For the snapshots on the master, there is probably a limit somwhere. However these are merged into the Replica so its a once of hit to merge them, rather than being an ongoing problem. If it effects anything it effects the management and performance of your Parent and Replica creation only. I would suspect you don't want too many.
Are you having issues?
Correct on the second process. You then need to decide when you are going to recompose the machines in the pool.
Rodos
Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/
Thanks for the information. I don't have any issues but I was wondering from a sizing perspective.
You are most welcome. Consider the use of the helpful or correct buttons as a reward. ![]()
Hello all,
I have a couple of questions around linked clones:
Firstly, is there a rule of thumb around how many linked clones you can make from a single parent VM?
as Rodos says the jury is still out on that one, the Linked Clone concept is too new in the VDI space. .Personally I have created over a 100 linked clones per LUN with no noticable degredation is perfromance. I am still scalling up. however I do not want to go to much higher densities per LUN due to disk space limitations, remember you can only have a maximum 2TB VMFS partition ber LUN and I am not going to start playing about with Extents
Secondly, to patch VM's that are linked do I simply need to power on the original VM, make the changes, power it off and then make a new snapshot and then modify the desktop pool?
yep it is that simple. remember that you will need to refresh the desktops and that means an outage
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth
VMware Communities User Moderator
Blog: www.planetvm.net
I just deployed VMware view 3.1.1 with linked clone technology on my production environment. I haven’t had any issues – it is critical that you carefully review all the best practices and then do pilot deployment to understand user experience before Go-Live.
“Firstly, is there a rule of thumb around how many linked clones you can make from a single parent VM?”
This assumption is not true – VMware recommends 64 virtual machines per replica not per parent VM. Remember each replica is tied to a snapshot- so you can have one Golden Master image with 3 snapshots and create 3 different despot pools each pointing to its own unique replica which interns point to its own unique snapshot. You can have multiple replicas in a single LUN. Just make sure you have enough spindles (underlying physical disks) when you create your lun. Generally, I recommend having more than 4 spindles per LUN. This way you will not experience any bottle necks in the storage I/O subsystem.
“Secondly, to patch VM's that are linked do I simply need to power on the original VM, make the changes, power it off and then make a new snapshot and then modify the desktop pool?”
Yes you are absolutely right about this – just use the recomposition technology to link your desktop pools to the updated snapshot.
If you found this answer useful please consider the use of the Helpful or correct buttons to award points.
Hi Ashley.
We usually recommend up to 64 linked clones per lun for best performance.
When it comes to real-world deployments I think 50 is a nice and round number to start with and then go from there.
Best regards,
Linjo
If you find this information useful, please award points for "correct" or "helpful".
Also it should be mentioned that your VM density per LUN can vary based on specific factors in your environment. 64 is a base recommendation. If for example you have VMs with a high amount of I/O you may even want to have a lower density. It also depends on how many spindles you have per LUN.
Also for completeness in this thread I recently fielded a question about snapshots per VM:
In the VI 3 admin guide it says
the following on page 250:
“Although you can take snapshots up to 32 levels, the amount of time it takes to commit
or delete those snapshots increases as the levels get deeper. The required time is directly
proportional to the amount of data (committed or deleted) and the virtual machine’s
RAM size. “
