• Discover On-Prem VMs for Migrations to VMware Cloud

    The first step in cost modeling for on-premise virtual machines to VMware Cloud on AWS is to discover the on-prem VMs – their configuration and usage information.
    Download the free Akasia Remote Collector and run it in your local environment to discover your on-prem VMs and their characteristics. Upload the data to Akasia Infrastructure Modeler to start the cloud planning exercise.

  • Mapping on-prem VMs to VMware Cloud Hosts

    Once the on-prem VMs have been discovered, they are mapped in the most optimal manner to VMware Cloud Hosts such that the number of hosts is the minimum possible to save costs. Our mapping algorithm takes care of ensuring there is enough headroom in the VMware Cloud Hosts to accommodate spikes in usage for the VMs that are placed in the hosts.

  • Adding AWS Services and Migration Costs

    Once you have clarity on how many hosts and clusters are needed to accommodate your on-prem VMs, the next step is to add AWS services that are needed to complete your VMware Cloud on AWS deployment; and add costs for migration to get a holistic model for your VMware Cloud costs.

  • View Bill of Materials and Costs Projection

    The final report from AIM gives you the detailed costs for VMware Cloud that includes cost for the hosts determined from the on-prem to VMware Cloud mapping exercise, the network and IO costs, additional AWS services and migration costs. You can see the cost savings from right-sizing your VMs before you migrate them to VMware Cloud.

    The AIM report gives you a bill of materials – the exact number of VMware Cloud hosts and the on-prem VMs mapped to them as well as part numbers for the AWS services you need. This becomes a starting point for your migration to VMware Cloud.

  • Case Study: EC2 vs. VMC

    A partner modeled costs for the identical set of 1443 VMs for both EC2 and VMC. They found some interesting metrics. Click here to view the full case study.