Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Berdasarkan data infrastruktur yang Anda miliki tentang lingkungan lokal saat ini, masukkan estimasi terbaik untuk CPU, memori, dan penyimpanan. Masukkan
jumlah gabungan total memori di semua sistem
di pusat data. Selain itu, tentukan total jejak penyimpanan gabungan,
termasuk semua direct-attached storage (DAS)
dan network-attached storage (NAS).
Di halaman Mulai estimasi, di kartu On-premise, klik
Mulai.
Jika Anda telah menyelesaikan estimasi untuk lingkungan lain dan ingin mulai menentukan detail di kalkulator biaya On-premise, lalu di halaman hasil, klik Mulai di kartu On-premise.
Di tab Estimate basics, dari daftar Location, pilih lokasi
tempat Anda ingin workload berada.
Untuk menentukan detail infrastruktur, klik Berikutnya.
Menentukan detail infrastruktur
Di tab Infrastruktur, ikuti langkah-langkah berikut:
Di bagian Total vCPU yang akan dimigrasikan, di kolom Jumlah vCPU, masukkan jumlah vCPU x86 yang ingin Anda migrasikan Google Cloud.
Kolom Memori pusat data yang diperlukan diperbarui secara otomatis berdasarkan
rasio memori default terhadap komputasi, yaitu 4:1.
Opsional: Untuk mengedit asumsi default ukuran komputasi
yang digunakan untuk estimasi ini, klik Edit detail ukuran komputasi.
Jika Anda memigrasikan infrastruktur non-x86 dan ingin menyertakannya dalam estimasi biaya, di bagian Total vCPU yang akan dimigrasikan, pilih Sertakan infrastruktur non-x86. Kemudian,
tentukan detail infrastruktur non-x86
di kolom tambahan yang muncul.
Di bagian Penyimpanan yang saat ini digunakan di pusat data Anda, ikuti
langkah-langkah berikut:
Di kolom Total penyimpanan (TB), masukkan total penyimpanan, dalam
TB, yang Anda miliki di pusat data.
Di kolom % File Storage, % Block Storage, dan % Object Storage, masukkan persentase total penyimpanan yang digunakan oleh penyimpanan file, blok, dan objek.
Di bagian Storage location, pilih lokasi tempat Anda ingin
penyimpanan berada. Jika Anda memilih beberapa lokasi, kolom baru akan muncul tempat Anda perlu menentukan persentase distribusi penyimpanan untuk setiap lokasi.
Di bagian Networking, ikuti langkah-langkah berikut:
Di kolom CDN data transfer out bandwidth, masukkan jumlah
bandwidth transfer keluar data yang digunakan untuk Google Cloud
Jaringan Penayangan Konten, dalam GB.
Pilih cara menghitung biaya jaringan:
Jika Anda memilih Persentase dari total biaya komputasi, tentukan biaya jaringan yang diperkirakan sebagai persentase dari biaya komputasi.
Jika Anda memilih Bandwidth jaringan bulanan, tentukan
perkiraan bandwidth jaringan per bulan dalam TB, dan persentase
traffic jaringan eksternal, tidak termasuk traffic pusat data.
Dari daftar mata uang di sebelah kanan, pilih mata uang yang ingin Anda gunakan untuk estimasi biaya cloud.
Untuk menentukan detail beban kerja perusahaan, klik Berikutnya.
Menentukan detail infrastruktur non-x86
Jika Anda memigrasikan mainframe, di bagian Mainframe, pilih Saya memigrasikan mainframe dan ikuti langkah-langkah berikut:
Di kolom Mainframe MIPS #, masukkan kapasitas mainframe million instructions per second.
Di bagian Mainframe Colocation or Rehosting (Emulation), pilih apakah
Anda ingin menggunakan Colocation atau Rehosting untuk mainframe Anda.
Jika Anda memigrasikan core Unix, ikuti langkah-langkah berikut:
Di kolom Number of UNIX vCPUs, masukkan jumlah vCPU Unix yang ingin Anda migrasikan.
Di bagian Distribusi vCPU UNIX, tentukan distribusi persentase core Unix.
Di kolom Unix infrastructure type, pilih apakah Anda menginginkan
Managed Service Provider untuk vCPU Unix atau Anda ingin vCPU tersebut
Diemulasi.
Opsional: Untuk mengedit asumsi default ukuran non-x86
yang digunakan untuk estimasi ini, klik Edit detail ukuran non-x86.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[],[],null,["# Specify infrastructure details\n\nBased on the infrastructure data that you have about your current on-premises\nenvironment, enter your best estimates for CPU, memory, and storage. Enter the\ntotal aggregate count of memory across all systems\nin the data center. Also, specify the total aggregate storage footprint,\nincluding all [direct-attached storage (DAS)](https://en.wikipedia.org/wiki/Direct-attached_storage)\nand [network-attached storage (NAS)](https://en.wikipedia.org/wiki/Network-attached_storage).\n\nBefore you begin\n----------------\n\n- Complete the steps to [start a cost estimate](/migration-center/docs/estimate/start-estimation).\n\nSpecify basic estimate details\n------------------------------\n\n1. On the **Start your estimate** page, in the **On-premise** card, click\n **Start**.\n\n If you've completed estimation for another environment and want to start\n specifying details in the **On-premise** cost calculator, then on the\n results page, click **Start** in the **On-premise** card.\n2. On the **Estimate basics** tab, from the **Location** list, choose a location\n where you want your workloads to be located.\n\n3. To specify infrastructure details, click **Next**.\n\nSpecify infrastructure details\n------------------------------\n\nOn the **Infrastructure** tab, follow these steps:\n\n1. In the **Total vCPUs to be migrated** section, in the **Number of vCPUs**\n field, enter the number of x86 vCPUs you want to migrate to Google Cloud.\n\n The **Data center memory required** field is automatically updated based on\n the default memory to compute ratio, which is 4:1.\n2. Optional: To edit the [compute sizing default assumptions](/migration-center/docs/estimate/review-defaults#compute_sizing_default_assumptions)\n used for this estimate click **Edit compute sizing details**.\n\n3. If you're migrating non-x86 infrastructure and want to include it in your\n cost estimate, then in the **Total vCPUs to be migrated** section, select\n **Include non-x86 infrastructure** . Then,\n [specify non-x86 infrastructure details](#specify_non-x86_infrastructure_details)\n in the additional fields that appear.\n\n4. In the **Storage currently in use in your data center(s)** section, follow\n these steps:\n\n 1. In the **Total storage (TB)** field, enter the total storage, in\n TB, that you have in your data center.\n\n 2. In the **% File Storage** , **% Block Storage** , and **% Object Storage**\n fields, enter the percentage of total storage used by file, block, and\n object storage respectively.\n\n 3. Under **Storage location**, select the locations where you want your\n storage to be located. If you select multiple locations, then new fields\n appear where you need to specify the percentage distribution of storage\n for every location.\n\n 4. Optional: To edit the [storage sizing default assumptions](/migration-center/docs/estimate/review-defaults#storage_sizing_default_assumptions)\n used for this estimate, click **Edit storage sizing details**.\n\n5. In the **Networking** section, follow these steps:\n\n 1. In the **CDN data transfer out bandwidth** field, enter the amount\n of data transfer out bandwidth used for Google Cloud\n Content Delivery Network, in GB.\n\n 2. Select how you want to calculate your networking costs:\n\n - If you select **Percentage of total compute cost**, then specify the networking costs you expect to have as a percentage of your compute costs.\n - 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.\n6. From the currency list on the right, choose the currency you want to use for\n your cloud cost estimate.\n\n7. To specify enterprise workload details, click **Next**.\n\n### Specify non-x86 infrastructure details\n\n1. If you're migrating mainframes, then in the **Mainframe** section,\n select **I am migrating mainframes** and follow these steps:\n\n 1. In the **Mainframe MIPS #** field, enter the mainframe million instructions\n per second capacity.\n\n 2. Under **Mainframe Colocation or Rehosting (Emulation)** , choose whether\n you want to use **Colocation** or **Rehosting** for your mainframes.\n\n2. If you're migrating Unix cores, then follow these steps:\n\n 1. In the **Number of UNIX vCPUs** field, enter the number of Unix vCPUs you\n want to migrate.\n\n 2. In the **UNIX vCPU distribution** section, specify the percentage\n distribution of the Unix cores.\n\n 3. In the **Unix infrastructure type** field, choose if you want a\n **Managed Service Provider** for your Unix vCPUs or you want them to be\n **Emulated**.\n\n3. Optional: To edit the [non-x86 sizing default assumptions](/migration-center/docs/estimate/review-defaults#non-x86_sizing_default_assumptions)\n used for this estimate, click **Edit non-x86 sizing details**.\n\nWhat's next\n-----------\n\n- To continue with your estimate, see how to [specify workload and license details](/migration-center/docs/estimate/enterprise-workloads).\n- Optional: To review the default assumptions that are used to calculate your cloud cost estimate, see how to [review the default assumptions](/migration-center/docs/estimate/review-defaults)."]]
