HP Capacity Advisor 7.2 User Guide

By studying this table and the key, you may have already concluded:
• None of the servers meet an acceptable level of fitness as described by the headroom rating.
• Two servers (tornado and orthus) would require additional CPU and additional memory to
host all 10 of the legacy servers.
• One server (vse02) might have enough memory, but would require more CPU. Also, the
demands on network and disk I/O would exceed resource capacity.
• The remaining server (hypv2) could have more memory and CPU added, but would still be
short on network and disk I/O.
• The 10 selected legacy servers will not fit on any one of the hosts present in the scenario.
At this point, you could do one of several things:
• Add another existing system having more memory and CPU and small use of network and
disk I/O to the scenario.
• Create a “what-if” system in the scenario that is sized to accommodate the ten legacy servers.
• Put fewer legacy servers on one of the systems already in the scenario.
This example will continue with the third option — putting fewer legacy servers on one of the
systems already in the scenario.
By cancelling the “Manually Change Servers to be VMs” operation, you can return to the scenario
editor System tab to try this operation again; this time selecting five of the legacy servers, with this
result:
Task: Plan server consolidation 139