Specify infrastructure details

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

Specify basic estimate details

  1. On the Start your estimatepage, in the On-premisecard, click Start.

    If you've completed estimation for another environment and want to start specifying details in the On-premisecost calculator, then on the results page, click Startin the On-premisecard.

  2. On the Estimate basicstab, from the Locationlist, choose a location where you want your workloads to be located.

  3. To specify infrastructure details, click Next.

Specify infrastructure details

On the Infrastructuretab, follow these steps:

  1. In the Total vCPUs to be migratedsection, in the Number of vCPUsfield, enter the number of x86 vCPUs you want to migrate to Google Cloud.

    The Data center memory requiredfield is automatically updated based on the default memory to compute ratio, which is 4:1.

  2. Optional: To edit the compute sizing default assumptions used for this estimate click Edit compute sizing details.

  3. If you're migrating non-x86 infrastructure and want to include it in your cost estimate, then in the Total vCPUs to be migratedsection, select Include non-x86 infrastructure. Then, specify non-x86 infrastructure details in the additional fields that appear.

  4. In the Storage currently in use in your data center(s)section, follow these steps:

    1. In the Total storage (TB)field, enter the total storage, in TB, that you have in your data center.

    2. In the % File Storage, % Block Storage, and % Object Storagefields, enter the percentage of total storage used by file, block, and object storage respectively.

    3. 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.

    4. Optional: To edit the storage sizing default assumptions used for this estimate, click Edit storage sizing details.

  5. In the Networkingsection, follow these steps:

    1. In the CDN data transfer out bandwidthfield, enter the amount of data transfer out bandwidth used for Google Cloud Content Delivery Network, in GB.

    2. 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.
  6. From the currency list on the right, choose the currency you want to use for your cloud cost estimate.

  7. To specify enterprise workload details, click Next.

Specify non-x86 infrastructure details

  1. If you're migrating mainframes, then in the Mainframesection, select I am migrating mainframesand follow these steps:

    1. In the Mainframe MIPS #field, enter the mainframe million instructions per second capacity.

    2. Under Mainframe Colocation or Rehosting (Emulation), choose whether you want to use Colocationor Rehostingfor your mainframes.

  2. If you're migrating Unix cores, then follow these steps:

    1. In the Number of UNIX vCPUsfield, enter the number of Unix vCPUs you want to migrate.

    2. In the UNIX vCPU distributionsection, specify the percentage distribution of the Unix cores.

    3. In the Unix infrastructure typefield, choose if you want a Managed Service Providerfor your Unix vCPUs or you want them to be Emulated.

  3. Optional: To edit the non-x86 sizing default assumptions used for this estimate, click Edit non-x86 sizing details.

What's next

Design a Mobile Site
View Site in Mobile | Classic
Share by: