First, we understand the process by which MCS creates VMS under XenDesktop, as follows:
1. Create a VM template as the Master vm
2. Executive Snapshot
3.Full copy Snapshot as base disk, one copy of base disk per SR (recommended for each SR plan to accommodate 25 VMS)
4. Create diff disk and identity disk for each VM
So
The 4th is the object that we want to analyze, because the VMS out of the final MCs are linked to the master image, The space occupied is created 2 a disk: Diff disk and ID disk.
We're going to discuss the following
MCS analysis that occupies the size of the XenServer storage space:
Let's look at the first scenario (file storage):
on storage that supports thin provisioning, MCS generates 10 VMS, each with 25G OS space, 10G is OS-occupied, 3G data changes,
then the total space required for the final 40GB, such as:
That means that the diff disk on the file store only takes up the amount of space that actually changes.
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/54/83/wKioL1SFTC-Dl1znAAGvVxjpS3M268.jpg "/>
Second scenario (Block storage):
No thin provisioning storage supported on XenServer, the same scenario, using a total space size of 275GB, such as:
That is, the size of the diff disk on the block storage is equal to the original size of the base disk.
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/54/85/wKiom1SFS52yVa-gAAG3ycfrTVM772.jpg "/>
Therefore, the Citrix xendesktop architecture design on XenServer is more recommended for NFS-type storage.
Note: XenServer supports thin provisioning feature storage including local EXT3 and NFS Share
Thin provisioning on block based shared SR temporarily unsupported in XenServer , because thin provisoning need EXT3, this system is not used to configure cluster file system, which is why only local disk support thin Provisioning function, cannot support share SR.
This article comes from the "ELVIS's blog" blog, please be sure to keep this source http://virtualelvis.blog.51cto.com/1383159/1587545
XenDesktop MCS Technology Storage Space Utilization analysis in Xenserve environment