Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Praktik terbaik migrasi
Halaman ini menyajikan beberapa praktik terbaik untuk memigrasikan instance virtual machine (VM) VMware ke cloud pribadi Anda menggunakan Google Cloud VMware Engine.
Merencanakan project migrasi
Sebelum memigrasikan VM VMware ke cloud pribadi Anda, rencanakan migrasi sebagai berikut:
Identifikasi personel, termasuk:
Pemangku kepentingan pelanggan
Sponsor dan pemilik program
Tim teknis yang bertanggung jawab atas migrasi
Pemangku kepentingan untuk sistem dan aplikasi dalam cakupan
Manajer Akun Teknis (TAM), Partner Engineering
Manager (PEM), atau Customer Engineer (CE) Google yang relevan
Pastikan vSphere, vCenter, HCX, dan, jika berlaku, NSX-T on-premise
memenuhi kompatibilitas pembuatan versi minimum dengan
versi komponen VMware Engine.
Identifikasi VM dengan persyaratan memori, CPU, atau penyimpanan yang melebihi
spesifikasi jenis node saat ini atau yang dapat menyebabkan pertentangan jika
digabungkan dengan VM besar lainnya.
Misalnya, server database mungkin memerlukan memori dalam jumlah besar atau
server penyimpanan file mungkin memerlukan datastore besar.
Kembangkan strategi pra- dan pasca-migrasi untuk konten yang tidak dapat
dimigrasikan karena hardware atau pemberian tag yang persisten, seperti ISO yang di-mount, tag
NSX-T, perangkat passthrough yang menggunakan
DirectPath I/O,
disk multi-penulis,
dan RDM fisik. Contoh strateginya adalah mempertimbangkan untuk mengonversi
RDM fisik ke
mode kompatibilitas virtual.
Pilih migrasi massal.
Pertimbangkan persyaratan dan batasan terkait.
Menggunakan VMware HCX untuk migrasi
Saat menggunakan HCX untuk migrasi,
pertimbangkan rekomendasi berikut:
Meskipun topologi jaringan datar didukung untuk deployment HCX Connector dan HCX Service Mesh, untuk menghindari masalah pemilihan rute dan error konektivitas, siapkan profil jaringan HCX Management dan HCX Uplink di jaringan dan VLAN terpisah.
Pastikan lingkungan VMware Anda memiliki versi HCX terbaru. Untuk mengetahui informasi
selengkapnya, lihat
Prosedur Update Layanan HCX.
Tim SRE mengelola pencadangan HCX Manager, tetapi tidak mengelola pencadangan HCX Connector.
Appliance layanan HCX, termasuk HCX-IX dan HCX-NE, tidak memerlukan
pencadangan individual. HCX Manager yang dipulihkan akan terhubung kembali ke perangkat layanan
yang ada yang dibuat dalam durasi pencadangan. Jika aplikasi
layanan tidak lagi berfungsi, HCX Manager akan men-deploy VM
aplikasi baru berdasarkan konfigurasi yang dicadangkan.
Untuk VM yang berkomunikasi ke atau dari cloud pribadi melalui ekstensi HCX L2, konfigurasikan setelan MTU terbaik berdasarkan konfigurasi endpoint VPN. Hal ini sangat penting jika aplikasi
tidak dapat mengontrol ukuran payload maksimum.
Google merekomendasikan setelan MTU 1350 byte hingga 1390 byte atau lebih rendah untuk antarmuka VM
yang memungkinkan transfer data dengan cara berikut:
Dari endpoint lokal ke cloud pribadi dan sebaliknya
Dari VM di satu cloud pribadi ke VM di cloud pribadi lain melalui
ekstensi L2
Pelajari arsitektur referensi, diagram, tutorial, dan praktik terbaik tentang Google Cloud. Kunjungi Cloud Architecture Center untuk
mengetahui informasi selengkapnya.
[[["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-04 UTC."],[],[],null,["# Migration best practices\n========================\n\nThis page presents some best practices for migrating VMware virtual machine (VM)\ninstances to your private cloud by using Google Cloud VMware Engine.\n\nPlan the migration project\n--------------------------\n\nBefore migrating VMware VMs to your private cloud, plan the migration as follows:\n\n- Identify the personnel, including the following:\n\n - Customer stakeholders\n - Program sponsor and owner\n - The technical team responsible for the migration\n - The stakeholders for in-scope systems and applications\n - The relevant Google Technical Account Manager (TAM), Partner Engineering Manager (PEM), or Customer Engineer (CE)\n- Assess the [source environment](/vmware-engine/docs/workloads/classic-console/howto-migrate-workloads#assess_the_source_environment).\n\n- Create a plan that defines the following:\n\n - the migration strategy\n - the architecture of the new environment\n - the goals and success criteria, including the UAT and QA scripts\n - the roles and responsibilities\n - the communication model, including daily standups, status reporting, escalation paths, chat rooms\n - the data that cannot be migrated and related strategies\n - milestones and timings\n- Ensure alignment with all stakeholders.\n\nEvaluate migration options\n--------------------------\n\nTo evaluate the different migration options for VMware Engine,\nconsider the following options:\n\n- Consider planning the migration in waves.\n\n - Factor in application dependencies and mappings.\n - Group VMs based on their maintenance schedule.\n - To avoid multiple power cycles, identify the VMs with pending system updates and align the schedule with the migration switchover reboots.\n- Establish a backup and DR strategy for VMs. Consider using\n [Google Cloud Backup and DR](/backup-disaster-recovery/docs) and\n [VMware Engine Protected](/vmware-engine/docs/concepts-vmware-engine-protected).\n\n- Ensure that vSphere, vCenter, HCX, and, if applicable, NSX-T on-premises\n meet the minimum versioning compatibility with\n [VMware Engine component versions](/vmware-engine/docs/concepts-vmware-components#vmware_component_versions).\n\n- Identify VMs with memory, CPU, or storage requirements that exceed the\n specification of the current node type or that might cause contention if\n combined with other large VMs.\n\n For example, database servers might require large amounts of memory or\n file storage servers might require large datastores.\n- Develop pre- and post-migration strategies for content that cannot be\n migrated due to persistent hardware or tagging, such as mounted ISOs, NSX-T\n tags, passthrough devices that use\n [DirectPath I/O](https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-networking/GUID-BF2770C3-39ED-4BC5-A8EF-77D55EFE924C.html),\n [multi-writer disks](https://core.vmware.com/blog/migrating-vms-shared-or-multi-writer-disks),\n and physical RDMs. An example strategy might be to consider converting\n physical RDMs to\n [virtual compatibility mode](https://knowledge.broadcom.com/external/article?legacyId=1006599).\n\n- Assess and evaluate [migration methods](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-8A31731C-AA28-4714-9C23-D9E924DBB666.html).\n\n Prefer [bulk migration](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-20EA2946-57CD-4A87-AE25-866E5336AEA9.html#GUID-20EA2946-57CD-4A87-AE25-866E5336AEA9).\n Consider the related requirements and restrictions.\n\nUse VMware HCX for migrations\n-----------------------------\n\nWhen using [HCX for migration](/vmware-engine/docs/workloads/howto-migrate-vms-using-hcx),\nconsider the following recommendations:\n\n- Although a flat network topology is supported for HCX Connector and HCX\n Service Mesh deployments, to avoid routing problems and connectivity\n errors, set up HCX Management and the HCX Uplink [network profiles](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-getting-started/GUID-AB56D9A9-7E2C-436F-9E20-445E447E300F.html)\n on separate networks and VLANs.\n\n- Ensure that your VMware environment has the latest HCX versions. For more\n information, see\n [HCX Service Update Procedures](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-77111C61-EC4C-4C8C-8340-5828CC4D489D.html).\n\n- Be sure to configure\n [HCX backups and restore operations](https://docs.vmware.com/en/VMware-HCX/4.9/hcx-user-guide/GUID-50C416BC-5415-42AB-AA7A-3A5CB46A60C7.html),\n as required.\n\n The SRE team manages HCX Manager backups, but not HCX Connector backups.\n\n HCX service appliances, including HCX-IX and HCX-NE, don't require\n individual backups. A restored HCX Manager reconnects to existing service\n appliances that were created within the backup duration. If the service\n appliances are no longer functional, the HCX Manager deploys new appliance\n VMs based on the backed-up configuration.\n- When stretching a Layer 2 network by using HCX network extensions, enable\n TCP Flow Conditioning. For related information, see\n [Traffic engineering features provided in HCX](https://blogs.vmware.com/cloud/2020/01/16/traffic-engineering-hcx-enterprise/).\n\n- For VMs that communicate to or from a private cloud over an HCX L2\n extension, configure the best MTU setting based on VPN endpoint\n configurations. This is especially important in cases where an application\n isn't able to control the maximum payload size.\n\n Google recommends an MTU setting of 1350 bytes to 1390 bytes or lower for VM\n interfaces that allow data transfer in the following ways:\n - From an on-premises endpoint to a private cloud and conversely\n - From a VM in one private cloud to a VM in another private cloud over an L2 extension\n\n For additional guidance on calculating encapsulation overhead, see\n [MTU considerations](/network-connectivity/docs/vpn/concepts/mtu-considerations)\n and [VMware NSX-T VPNs](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-A8B113EC-3D53-41A5-919E-78F1A3705F58.html).\n\nWhat's next\n-----------\n\n- Read about best practices for [compute](/vmware-engine/docs/best-practices-compute), [networking](/vmware-engine/docs/best-practices-networking), [security](/vmware-engine/docs/best-practices-security), [storage](/vmware-engine/docs/best-practices-storage), and [costs](/vmware-engine/docs/best-practices-costs).\n- Try out VMware Engine. Visit [features, benefits, and use\n cases](/vmware-engine/docs/overview) for more information.\n- Explore reference architectures, diagrams, tutorials, and best practices about Google Cloud. Visit [Cloud Architecture Center](/architecture) for more information."]]
