Based on the infrastructure data that you have about your current on-premises environment, enter your best estimates for CPU, memory, and storage. Enter the total aggregate count of memory across all systems in the data center. Also, specify the total aggregate storage footprint, including all direct-attached storage (DAS) and network-attached storage (NAS).
Before you begin
- Complete the steps to start a cost estimate.
Specify basic estimate details
On the Start your estimate page, in the On-premise card, click Start.
If you've completed estimation for another environment and want to start specifying details in the On-premise cost calculator, then on the results page, click Start in the On-premise card.
On the Estimate basics tab, from the Location list, choose a location where you want your workloads to be located.
To specify infrastructure details, click Next.
Specify infrastructure details
On the Infrastructure tab, follow these steps:
In the Total vCPUs to be migrated section, in the Number of vCPUs field, enter the number of x86 vCPUs you want to migrate to Google Cloud.
The Data center memory required field is automatically updated based on the default memory to compute ratio, which is 4:1.
Optional: To edit the compute sizing default assumptions used for this estimate click Edit compute sizing details.
If you're migrating non-x86 infrastructure and want to include it in your cost estimate, then in the Total vCPUs to be migrated section, select Include non-x86 infrastructure. Then, specify non-x86 infrastructure details in the additional fields that appear.
In the Storage currently in use in your data center(s) section, follow these steps:
In the Total storage (TB) field, enter the total storage, in TB, that you have in your data center.
In the % File Storage, % Block Storage, and % Object Storage fields, enter the percentage of total storage used by file, block, and object storage respectively.
Under Storage location, select the locations where you want your storage to be located. If you select multiple locations, then new fields appear where you need to specify the percentage distribution of storage for every location.
Optional: To edit the storage sizing default assumptions used for this estimate, click Edit storage sizing details.
In the Networking section, follow these steps:
In the CDN data transfer out bandwidth field, enter the amount of data transfer out bandwidth used for Google Cloud Content Delivery Network, in GB.
Select how you want to calculate your networking costs:
- If you select Percentage of total compute cost, then specify the networking costs you expect to have as a percentage of your compute costs.
- If you select Monthly network bandwidth, then specify your estimated networking bandwidth per month in TB, and the percentage of the external network traffic, excluding the data center traffic.
From the currency list on the right, choose the currency you want to use for your cloud cost estimate.
To specify enterprise workload details, click Next.
Specify non-x86 infrastructure details
If you're migrating mainframes, then in the Mainframe section, select I am migrating mainframes and follow these steps:
In the Mainframe MIPS # field, enter the mainframe million instructions per second capacity.
Under Mainframe Colocation or Rehosting (Emulation), choose whether you want to use Colocation or Rehosting for your mainframes.
If you're migrating Unix cores, then follow these steps:
In the Number of UNIX vCPUs field, enter the number of Unix vCPUs you want to migrate.
In the UNIX vCPU distribution section, specify the percentage distribution of the Unix cores.
In the Unix infrastructure type field, choose if you want a Managed Service Provider for your Unix vCPUs or you want them to be Emulated.
Optional: To edit the non-x86 sizing default assumptions used for this estimate, click Edit non-x86 sizing details.
What's next
- To continue with your estimate, see how to specify workload and license details.
- Optional: To review the default assumptions that are used to calculate your cloud cost estimate, see how to review the default assumptions.