![]() The VMware disk reallocation worked for us also going from 80gig to 110gig for 10.5. If you shut the image down and increase from 110 to at least 112G, the boot process grows the common partition out.Īs a standard, any of our 10x installs for large clients, we are growing the disk out to 120G just to be safe. doesn't leave much space for those 500 moh sources. I'm running around with a tac case to address a stock 9x or 10x 7.5 to 10k user build that results with a 110G disk. The resize cop file is for 9x only, 10 has it built in. I wonder what the difference is between expanding and installing on 120G from the beginning, since there is the report of it only growing the common partition. While testing my moh problem, I used an 8.6 ova to deploy the old 10k template, made the one OS tweak to the image, then installed 10.5(2) on it. So if you really need to go from a 2500 user deployment to a 7500 user one you should DRS, rebuild, restore so your active and inactive partitions get sized accordingly. If you need to extend the user capacity of your system, you must migrate from a single-disk to a multi-disk virtual machine The disk space requirements are specified in the Readme file for the OVA template.Įxpanding the disk size to add space to the common partition will not increase the user capacity of your system. You need to change the disk size changes only if you need additional space to complete the upgrade. The feature is there because some versions of UCM require more space available in that partition than others. It’s expected that only the common partition grows if you expand the vDisk. Next message (by thread): (no subject). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |