Machine Creation Services (MCS) Storage Considerations
Article ID: CTX218082
Updated On:
Description
The purpose of this article is to provide basic guidance on proper considerations for storage capacity required for Machine Creation Services (MCS) deployments.
Instructions
Refer to Citrix Documentation: MCS storage considerations
Environment
Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.
Issue/Introduction
Machine Creation Services Storage Considerations
Additional Information
Calculators and Tools
- A few equations have been developed, but none will be exhaustive and inclusive of every possible scenario. See this discussion, for Example.
- (number of defined storages in selected hosting connection * number of max. expected updates until complete reboot of machine catalog and 12h wait time * actual image size * number of machine catalogs using this image) + (number of max. CCU * 15% from image size) + (number of vm´s * 16 MB) (+ for VMware (number of vm´s * VM swap file *2 ))
- Hardware and Storage Calculator - This link is a little older, but useful for older versions of XenApp and XenDesktop (Currently Citrix Virtual Apps and Desktops).
Reference articles and blogs (Links)
- Storage must be properly planned out in any VDI environment considering all the consumers of that storage solution.
- It is best to over-shoot any calculations you have made since it is much easier to provision the extra storage up front than it is to repair a site that has been affected by storage related issues.
Was this article helpful?
Yes
No
Powered by
