Hello to everybody....
I'm opening this new discussion cause I need assistance in understanding how vm consolidation work in vCloud.
I'm coming from a Lab manager world where linked clone, configuration and Library concepts were clear for me... but now I'm a bit confused on vCloud.
Just a quick explanation of how I use vCloud.
We've a vm (Red hat Enterprise Linux 5 and Sybase DBMS installed on it, size of the all the vmdks is 1,2 TB) that has its own vAPP (that is called Catalog vAPP). We create a vCloud Template of this vAPP and we use this template to deploy multiple copies of this vAPP on other Organizations, using linked clone feature.
Every nights the Sybase virtual machine inside the Catalog vAPP has database datas updated from a production a system thru database load feature (J-1) and every morning we deploy this vm into another template (named with the today date) and deployed again into the Organizations mentioned before.
On Saturday (chain lenght 6), we delete all the templates created during week and delete all the vAPPs except the Catalog one. After that we consolidate it (Catalog vAPP). This process used to last 10 hours on Lab Manager environment but on vCloud env It takes (the consolidation of Catalog vAPP) days (last time 96 hours).
my question is: How the consolidation process works?
How is It changed since Lab Manager?
JFI: This vCloud farm (composed by 6x ESXi Host, each one with 2x Intel X5675 Cpu and 96 GB of RAM) is connected thru Fiber channel redundant connection to a dedicated EMC NS480 Storage using a datastore composed by several META-LUNs. Taking a look at the EMC Analyzer software, there is no evidence of bottleneck on Storage Side and, with Cisco software, even of Fiber channel switches too.