Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Layanan Pencadangan dan DR menggunakan VMware vSphere Storage API - Data Protection untuk membuat
pencadangan VM VMware, dengan menempatkan pencadangan ini di kumpulan snapshot
aplikasi pencadangan/pemulihan atau di kumpulan OnVault, atau di keduanya.
Pencadangan dan DR menggunakan snapshot untuk mencadangkan data secara bertahap dari VMDK Anda di
tingkat VM. Setelah Layanan Pencadangan dan DR membuat cadangan status saat ini dari semua VMDK yang terpasang ke VM, Anda dapat menggunakannya untuk:
Pasang data tersebut sebagai disk baru yang terpasang ke VM yang dipilih (baik VM sumber maupun host atau VM fisik yang berbeda). Lihat Memasang image VMware.
Pulihkan data tersebut ke semua atau disk yang dipilih yang terpasang ke VM VMware
sumber. Lihat Merestorasi VM VMware.
Clone data tersebut ke semua atau disk yang dipilih yang terpasang ke VM VMware target baru. Lihat Merestorasi VM VMware.
Pencadangan dan DR dapat dikonfigurasi untuk menyimpan beberapa salinan dari setiap snapshot
di beberapa lokasi menggunakan OnVault yang menulis cadangan ke Cloud Storage,
atau StreamSnap yang menyalin snapshot ke appliance pencadangan/pemulihan kedua.
Pencadangan dan DR menggunakan checksum otomatis untuk memastikan integritas data Anda setelah setiap tugas pencadangan berhasil.
Cara kerjanya: Pencadangan dan DR snapshot VM VMware
Pencadangan data dengan VM VMware mengikuti langkah-langkah berikut:
Snapshot pertama VM VMware yang berhasil akan membuat snapshot dari setiap
virtual disk (VMDK). Untuk setiap disk, ini adalah snapshot lengkap yang berisi semua
data di disk virtual.
Snapshot kedua hanya berisi data baru atau data yang dimodifikasi sejak
snapshot pertama. Data yang tidak berubah sejak snapshot 1 tidak disertakan.
Sebagai gantinya, snapshot 2 berisi referensi ke snapshot 1 untuk data yang tidak berubah.
Snapshot 3 berisi data baru atau yang diubah sejak snapshot 2, tetapi tidak akan
berisi data yang tidak berubah dari snapshot 1 atau 2. Sebagai gantinya, snapshot 3 berisi
referensi ke blok dalam snapshot 1 dan snapshot 2 untuk data yang tidak berubah.
Proses ini akan berulang untuk semua snapshot VM VMware berikutnya. Snapshot
selalu dibuat berdasarkan snapshot terakhir yang berhasil diambil oleh Pencadangan dan DR.
Jika disk virtual tambahan ditambahkan ke VM VMware, disk ini
otomatis disertakan dalam snapshot VM berikutnya. Anda juga dapat menggunakan
aturan sertakan atau kecualikan untuk mengontrol disk virtual yang disertakan dalam setiap
pencadangan. Secara default, semua disk virtual disertakan dalam Aturan Penyertaan Volume.
Pemasangan data dengan pencadangan VM VMware mengikuti langkah-langkah berikut:
Pilih VM VMware dan titik waktu yang ingin digunakan.
Pilih apakah Anda ingin memasang ke host atau VM yang ada, membuat VM VMware baru, atau memulihkan disk VM VMware sumber.
Jika membuat VM VMware baru, pilih variabel lokasi seperti vCenter, host ESX, dan datastore yang akan digunakan.
Pencadangan dan DR menggunakan teknologi snapshot untuk membuat disk virtual baru dari
cadangan. Saat dibuat, disk ini akan dilampirkan ke host atau VM VMware baru atau yang sudah ada. Disk virtual ini dapat ditulis, dan dapat
dimigrasikan ke disk fisik menggunakan tugas VMware Storage VMotion.
Lokasi penyimpanan cadangan
Saat Anda membuat rencana pencadangan dan menerapkannya ke VM VMware, kebijakan dan
profil akan menentukan tempat cadangan disimpan.
Data cadangan berbasis VM VMware dapat disimpan langsung ke Google Cloud Storage, menggunakan template Direct to OnVault dalam rencana pencadangan. Hal ini berfungsi untuk
Google Cloud VMware Engine, meskipun sebaiknya pastikan
bandwidth yang tersedia memadai jika Anda menggunakan fitur ini. Jika bandwidth terbatas, sebaiknya gunakan kebijakan snapshot lokal, yang mempertahankan salinan data pencadangan selama jangka waktu yang ditentukan pengguna, dan selain kebijakan snapshot, kebijakan OnVault tambahan dapat diaktifkan untuk menyimpan data selama jangka waktu yang lebih lama di bucket Storage Google Cloud .
Setiap VM dapat memiliki hingga empat kebijakan OnVault, yang masing-masing menentukanGoogle Cloud Bucket penyimpanan yang berbeda, yang dapat berupa class penyimpanan yang berbeda dan jenis lokasi yang berbeda.
Lokasi multi-regional storage memberikan ketersediaan dan
ketahanan tertinggi. Lokasi penyimpanan regional memberi Anda lebih banyak kontrol atas
lokasi fisik data karena Anda menentukan satu region.
[[["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\u003eBackup and DR Service utilizes VMware vSphere Storage APIs to create backups of VMware VMs, storing them in either the snapshot pool of the backup/recovery appliance, OnVault pools, or both.\u003c/p\u003e\n"],["\u003cp\u003eThe service uses snapshots to incrementally back up VMDK data at the VM level, where subsequent snapshots only contain new or modified data and reference unchanged data from previous snapshots.\u003c/p\u003e\n"],["\u003cp\u003eBacked up data can be mounted to create a new VMware VM or as new disks attached to a VM, restored to the source VMware VM, or cloned to a new target VMware VM.\u003c/p\u003e\n"],["\u003cp\u003eBackup data can be stored in Google Cloud Storage via OnVault policies, offering options for multi-regional, dual-region, or regional locations, and allowing up to four different OnVault policies per VM.\u003c/p\u003e\n"],["\u003cp\u003eWhen backing up older Windows Server OS versions in Google Cloud VMware Engine VMs, the system is supported, however the support team cannot assist with any OS related problems, that will require the OS vendor for support.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for VMware VMs\n\nBackup and DR Service uses VMware vSphere Storage APIs - Data Protection to create\nbackups of VMware VMs, placing these backups either in the snapshot pool of the\nbackup/recovery appliance or in OnVault pools, or in both.\n| **Note:** Only backing up old Windows server OS versions inside the Google Cloud VMware Engine VM is supported. Installing a Backup and DR Service agent won't let you back up support team cannot assist with OS boot-up issues or other OS-related problems. In such cases, you must contact the OS vendor for support.\n\nBackup and DR uses snapshots to incrementally backup data from your VMDKs at\nthe VM level. After Backup and DR Service creates a backup of the current state of\nall VMDKs attached to an VM, you can use it to either:\n\n- Mount that data to create a new VMware VM. See\n [Mount a VMware image](/backup-disaster-recovery/docs/access-data/mount-vmware-image).\n\n- Mount that data as a new disk(s) attached to a selected VM (either the\n source VM or a different physical host or VM). See [Mount a VMware image](/backup-disaster-recovery/docs/access-data/mount-vmware-image).\n\n | **Note:** OnVault pools pointing to backup vaults don't support mount operations.\n- Restore that data to either all or selected disks attached to the source\n VMware VM. See [Restore a VMware VM](/backup-disaster-recovery/docs/restore-data/restore-vm).\n\n- Clone that data to either all or selected disks attached to a new target\n VMware VM. See [Restore a VMware VM](/backup-disaster-recovery/docs/access-data/clone-image-of-a-vm).\n\nBackup and DR can be configured to store multiple copies of each snapshot\nacross multiple locations using OnVault that writes backups to Cloud Storage,\nor StreamSnap that copies snapshots to a second backup/recovery appliance.\nBackup and DR uses automatic checksums to ensure the integrity of your data after each successful backup job.\n\nHow it works: Backup and DR VMware VM snapshots\n-----------------------------------------------\n\nData backup with VMware VMs follows these steps:\n\n1. The first successful snapshot of a VMware VM creates a snapshot of each\n virtual disk (VMDK). For each disk this is a full snapshot that contains all\n of the data on the virtual disk.\n\n2. The second snapshot only contains any new data or modified data since the\n first snapshot. Data that hasn't changed since snapshot 1 isn't included.\n Instead, snapshot 2 contains references to snapshot 1 for any unchanged data.\n\n3. Snapshot 3 contains any new or changed data since snapshot 2 but won't\n contain any unchanged data from snapshot 1 or 2. Instead, snapshot 3 contains\n references to blocks in snapshot 1 and snapshot 2 for any unchanged data.\n\nThis repeats for all subsequent snapshots of the VMware VM. Snapshots are\nalways created based on the last successful snapshot taken by Backup and DR.\nIf an additional virtual disk is added to the VMware VM, this disk is\nautomatically included in the next snapshot of the VM. You can also use\ninclude or exclude rules to control which virtual disks are included in each\nbackup. By default, all virtual disks are included in the Volume Inclusion Rule.\n\nData mount with VMware VM backups follows these steps:\n\n1. Select the VMware VM and point in time that they want to work with.\n\n2. Select if you want to mount to an existing host or VM, create a new\n VMware VM or restore the disks of the source VMware VM.\n\n3. If creating a new VMware VM, select the location variables such as which\n vCenter, ESX host and datastore to be used.\n\n4. Backup and DR uses snapshot technology to create new virtual disks from\n the backups. When these disks are created they are attached to the host or to\n the new or existing VMware VM. These virtual disks are writable, and can be\n migrated to physical disks using a VMware Storage VMotion task.\n\nBackup storage location\n-----------------------\n\nWhen you create a backup plan and apply it to a VMware VM, the policies and\nprofile specify where the backup is stored.\n\nVMware VM-based backup data can be stored directly into Google Cloud Storage,\nusing a Direct to OnVault template in the backup plan. This works for\nGoogle Cloud VMware Engine, though it is recommended to ensure\nsufficient bandwidth exists if you are using this feature. If bandwidth is\nlimited, then a local snapshot policy is recommended, which retains a copy of\nthe backup data for a user defined period of time, and in addition to the snapshot\npolicy, additional OnVault policies can be enabled to store data for longer\nperiods of time in Google Cloud Storage bucket(s).\n\nOnVault backups can be stored in a\n[Cloud Storage multi-regional location](/storage/docs/locations#location-mr),\na [Cloud Storage dual-region location](/storage/docs/locations#location-dr),\nor a [Cloud Storage regional location](/storage/docs/locations#location-r).\n\nEach VM can have up to four OnVault policies, each specifying different\nGoogle Cloud Storage buckets, which could be different storage classes and\ndifferent location types.\n\nA multi-regional storage location provides the highest availability and\nresilience. A regional storage location gives you more control over the\nphysical location of your data because you specify a single region.\n\nThe VMware administrator's guide\n--------------------------------\n\n- [Backup and DR for VMware VMs](/backup-disaster-recovery/docs/concepts/vmware-intro)\n\n- [Configure Google Cloud VMware Engine for Backup and DR protection](/backup-disaster-recovery/docs/configuration/prepare-vmware)\n\n- [Add vCenter and ESX server hosts to the management console](/backup-disaster-recovery/docs/configuration/add-vcenter-host)\n\n- [Discover and protect VMware VMs](/backup-disaster-recovery/docs/configuration/discover-and-protect-vms)\n\n- [Apply a backup template to protect a VM](/backup-disaster-recovery/docs/create-plan/apply-backup-template-to-manage-a-VM)\n\n- [Configure application settings for VMware VMs](/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm)\n\n- [Restore a VMware VM](/backup-disaster-recovery/docs/restore-data/restore-vm)\n\n- [Mount a VMware image](/backup-disaster-recovery/docs/access-data/mount-vmware-image)\n\n- [Clone an image of a VMware VM](/backup-disaster-recovery/docs/access-data/clone-image-of-a-vm)\n\n- [Create LiveClone workflows](/backup-disaster-recovery/docs/access-data/create-liveclone-workflows)\n\n- [Move VM management between two backup/recovery appliances](/backup-disaster-recovery/docs/configuration/supported-vmware)"]]
