Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Gunakan petunjuk ini untuk meng-clone image mesin virtual.
Dari konsol pengelolaan Layanan pencadangan dan DR, klik
Pengelola Aplikasi>Aplikasi.
Halaman Applications akan terbuka.
Pilih aplikasi dengan image yang ingin Anda clone,
lalu pilih Access dari daftar dialog di sudut kanan
halaman Applications.
Halaman Akses akan terbuka dan mencantumkan image cadangan menggunakan tampilan ramp linimasa.
Jenis image yang mendukung pembuatan clone mencakup OnVault, snapshot, dan snapshot jarak jauh—image StreamSnap.
Pilih gambar, lalu pilih Clone dari daftar operasi akses.
Halaman Clone akan terbuka.
Masukkan nama untuk VM yang ingin Anda clone di VM Name.
Pilih vCenter dari drop-down VCENTER untuk VM yang ingin Anda clone.
Pilih host ESX dari drop-down Choose Server tempat Anda ingin meng-clone VM.
Pilih penyimpanan data dari drop-down Penyimpanan data yang memiliki
penyimpanan yang diperlukan.
Jika Anda perlu mengubah penyediaan volume untuk image clone
untuk alokasi ruang image, tentukan salah satu pilihan
di bagian Jenis Penyediaan.
Setelan Asli: Setelan penyediaan default gambar.
Tipis: Volume dengan kapasitas virtual yang berbeda dari kapasitas
nyatanya—ukuran kapasitas logis yang lebih besar daripada
kapasitas fisik sebenarnya yang ditetapkan ke volume.
Tebal: Volume yang menggunakan jumlah kapasitas yang dialokasikan sepenuhnya—tebal—yang direset ke nol sebelum data baru ditulis.
Lazy Tebal: Volume yang menggunakan kapasitas yang dialokasikan sepenuhnya—tebal—, tetapi hanya ruang yang digunakan yang awalnya direset ke nol.
Sisa ruang yang tidak dialokasikan akan direset ke nol selama penulisan pertama ke ruang tersebut.
Masukkan nama unik untuk clone baru di kolom Label.
Pilih satu atau beberapa volume dari Pilih Volume yang Akan Dikloning.
Secara default, semua volume dipilih, dan volume pertama tidak dapat dibatalkan pemilihannya. Untuk sistem file individual, hanya ada satu volume.
Tentukan Datastore dan Jenis Penyediaan untuk setiap volume yang ingin Anda pasang—lihat langkah 9 dan 10.
Tugas dikirim untuk meng-clone image ke host yang dipilih.
Setelah tugas clone selesai, image tidak tersedia di tampilan
Kelola pemasangan aktifPengelola Aplikasi karena tidak bergantung pada alat backup/pemulihan. VM baru harus
dikelola dari klien vSphere.
Panduan administrator VMware
Halaman ini adalah salah satu dari serangkaian halaman khusus untuk melindungi dan memulihkan
VM VMware dengan Backup dan DR.
Anda dapat menemukan informasi tambahan di:
[[["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-08-18 UTC."],[[["\u003cp\u003eThis guide details the process of cloning a virtual machine (VM) image, starting with selecting the desired application image from the App Manager.\u003c/p\u003e\n"],["\u003cp\u003eCloning involves choosing from supported image types like OnVault, snapshot, and remote snapshot, followed by specifying a name, vCenter, ESX host, and datastore for the cloned VM.\u003c/p\u003e\n"],["\u003cp\u003eUsers can customize the cloned image's storage provisioning type, such as original setting, thin, thick, or thick lazy, to manage space allocation.\u003c/p\u003e\n"],["\u003cp\u003eThe process allows for the selection of multiple volumes to be cloned, and allows each volume to have their own datastore and provisioning types, with the first volume assumed to be the boot volume by default.\u003c/p\u003e\n"],["\u003cp\u003eOnce completed, the cloned VM is managed directly through the vSphere client rather than through the App manager, and the clone job is submitted to the chosen host.\u003c/p\u003e\n"]]],[],null,["# Clone an image of a VMware VM\n\nUse these instructions to clone an image of a virtual machine.\n\n1. From the Backup and DR Service management console, click\n **App Manager** \\\u003e **Applications**.\n\n The **Applications** page opens.\n2. Select the application with the image you want to clone,\n then choose **Access** from the dialog list at the right\n corner of the **Applications** page.\n\n The **Access** page opens listing backup images using the timeline ramp view.\n Image types that support clone creation include OnVault, snapshot, and\n remote snapshot---StreamSnap images.\n3. Select an image and then select **Clone** from the list of access\n operations.\n\n The **Clone** page opens.\n4. Enter a name for the VM that you want to clone in **VM Name**.\n\n5. Select a vCenter from the **VCENTER** drop-down for the\n VM you want to clone.\n\n6. Select an ESX host from the **Choose Server** drop-down where you want to\n clone the VM.\n\n7. Select a datastore from the **Datastore** drop-down that has the required\n storage available.\n\n | **Note:** A clone is a full copy of the VMware VM written to the specified datastores including all configuration files.\n8. If you need to change the volume provisioning for the clone image\n for space allocation of the image, specify one of the selections\n under **Provisioning Type**.\n\n | **Note:** The management console maintains thin and thick provisioning of the original host while cloning or restoring an image.\n - **Original Setting**: Default provisioning setting of the image.\n - **Thin**: A volume with a virtual capacity that differs from its real capacity---a logical capacity size that is larger than the actual physical capacity that is assigned to the volume.\n - **Thick**: A volume that uses a fully allocated---thick---amount of capacity that is reset to zero prior to new data being written.\n - **Thick Lazy**: A volume that uses a fully allocated---thick---amount of capacity, but only the used space is initially reset to zero. The remaining unallocated space is reset to zero during the first write to that space.\n9. Enter a unique name for the new clone in the **Label** field.\n\n10. Select a single volume or multiple volumes from **Select Volumes To Clone**.\n By default all volumes are selected, and the first volume cannot be\n deselected. For an individual file system there may be only one volume.\n\n Specify the **Datastore** and **Provisioning Type** for each volume you\n want to mount---see steps 9 and 10.\n | **Note:** Backup and DR assumes that the first volume of the VM is the boot volume. If the first volume is not the boot volume, contact customer support for assistance.\n\n A job is submitted to clone the image to the selected host.\n\n When the clone job is complete, the image is not available in the\n [Manage active mounts](/backup-disaster-recovery/docs/access-data/manage-active-mounts) view of the **App Manager** as it is not\n dependent on the backup/recovery appliance. The new VM needs to be\n managed from the vSphere client.\n\nThe VMware administrator's guide\n--------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nVMware VMs with Backup and DR.\nYou can find additional information at:\n\n- [Backup and DR for VMware VMs](/backup-disaster-recovery/docs/concepts/vmware-intro)\n- [Configure Google Cloud VMware Engine for Backup and DR protection](/backup-disaster-recovery/docs/configuration/prepare-vmware)\n- [Add vCenter and ESX server hosts to the management console](/backup-disaster-recovery/docs/configuration/add-vcenter-host)\n- [Discover and protect VMware VMs](/backup-disaster-recovery/docs/configuration/discover-and-protect-vms)\n- [Apply a backup template to protect a VM](/backup-disaster-recovery/docs/create-plan/apply-backup-template-to-manage-a-VM)\n- [Configure Application settings for VMware VMs](/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm)\n- [Restore a VMware VM](/backup-disaster-recovery/docs/restore-data/restore-vm)\n- [Mount a VMware image](/backup-disaster-recovery/docs/access-data/mount-vmware-image)\n- [Clone an image of a VMware VM](/backup-disaster-recovery/docs/access-data/clone-image-of-a-vm)\n- [Create LiveClone workflows](/backup-disaster-recovery/docs/access-data/create-liveclone-workflows)\n- [Move VM management between two backup/recovery appliances](/backup-disaster-recovery/docs/configuration/supported-vmware)"]]
