In addition to discovery capabilities, Movere has a world-class capability for Sizing and Pricing devices for the Cloud. During AD and inventory scans, we can identify all devices in an environment, including physical and virtual devices across Windows, SQL, and Linux platforms. With Actual Resource Consumption (ARC) scanning, we are able to understand the demands on the server over time. Algorithms then calculate the requirements with different levels of confidence and turn them into the Cloud VM target profiles. So, the customer gains the confidence to say “Server B can move to a 2 core 8GB VM because Movere measured its workload over a period of time”. This is unlike many other tools which use an average or "as-is" provisioned data – which leads to paying massively over what is actually required.
Movere looks at a number of parameters during ARC scanning:
- CPU utilization
- RAM utilization
It then calculates the “headroom” (in other words “the unused bit”) and then uses that intelligence to identify the target profile. It could be any item which has the lowest “headroom” and is therefore driving the recommended cloud size. It is quite common to see a relatively small specification server moved to a more expensive profile in order to accommodate the high throughput or IOPS demands of the machine.
Movere isn’t looking into the future, so we cannot guarantee they will be exactly what is required. But the customer can be confident that based on what is recorded during the ARC scanning phase, a statistically correct profile has been given. The breakdown of all of those statistics is available on the ARC\Landscape\Device Summary view:
However, there is no substitute for judgement e.g. because of annual seasonal factor and for close monitoring after migration.
The primary views are:
- Summary\Cloud Readiness\Azure\VM Sizing
- Summary\Cloud Readiness\Azure\VM Pricing
Begin with sizing – it effectively shows the environment as calculated in the cloud, mapping each device to a profile.
It is important to check that all the devices are present. Movere uses CPU performance information to calculate the CPU requirement (there is a big difference between a Pentium and a Core i7). So, if there are devices missing from this view, it is possible that Movere does not recognise the CPU. If that is the case, the device will be showing in the Devices view as ARC scanned= yes but ARC sized = no and it will not have an Azure Profile.
Take note too of the sizing options. Different datacenters have different Cloud VM’s available, so it is important to select the Azure / AWS Region.
Confidence relates to the statistical analysis of the ARC data. 99% effectively ensures that 99% of the observed requirements would be covered and so will be more expensive. (You could be paying for a single incident where the application got into a loop!).
Finally, the data source is very important. ARC is clearly a better data set to use for sizing as it is based on actual experience. (However, it is interesting to screen grab the Inventory profiles and then the ARC profiles to see the difference).
This is the money shot! You have the same sizing options as in Sizing and again, grabbing views between Inventory and ARC data literally shows you how much you will save having used Movere. Here, each of the profiles has a price for the datacenter selected and can be displayed in a variety of formats by making choices under “Pricing Options”
Selecting a “Commit” which doesn’t include Pay As You Go options e.g. “1yr All UP Front Reserved” will cause the user interface to highlight in yellow target profiles which are not available. If there are specific sizes that you do not want to be included in Movere's recommendations, you will need to export the data from Movere and perform this adjustment outside of Movere.
Support for B-series sizes is on our roadmap and will be added in a future release. Similarly, you will need to manually assign these sizes outside of Movere.