Stay organized with collections
Save and categorize content based on your preferences.
Backup and DR Service uses VMware vSphere Storage APIs - Data Protection to create
backups of VMware VMs, placing these backups either in the snapshot pool of the
backup/recovery appliance or in OnVault pools, or in both.
Backup and DR uses snapshots to incrementally backup data from your VMDKs at
the VM level. After Backup and DR Service creates a backup of the current state of
all VMDKs attached to an VM, you can use it to either:
Mount that data as a new disk(s) attached to a selected VM (either the
source VM or a different physical host or VM). See Mount a VMware image.
Restore that data to either all or selected disks attached to the source
VMware VM. See Restore a VMware VM.
Clone that data to either all or selected disks attached to a new target
VMware VM. See Restore a VMware VM.
Backup and DR can be configured to store multiple copies of each snapshot
across multiple locations using OnVault that writes backups to Cloud Storage,
or StreamSnap that copies snapshots to a second backup/recovery appliance.
Backup and DR uses automatic checksums to ensure the integrity of your data after each successful backup job.
How it works: Backup and DR VMware VM snapshots
Data backup with VMware VMs follows these steps:
The first successful snapshot of a VMware VM creates a snapshot of each
virtual disk (VMDK). For each disk this is a full snapshot that contains all
of the data on the virtual disk.
The second snapshot only contains any new data or modified data since the
first snapshot. Data that hasn't changed since snapshot 1 isn't included.
Instead, snapshot 2 contains references to snapshot 1 for any unchanged data.
Snapshot 3 contains any new or changed data since snapshot 2 but won't
contain any unchanged data from snapshot 1 or 2. Instead, snapshot 3 contains
references to blocks in snapshot 1 and snapshot 2 for any unchanged data.
This repeats for all subsequent snapshots of the VMware VM. Snapshots are
always created based on the last successful snapshot taken by Backup and DR.
If an additional virtual disk is added to the VMware VM, this disk is
automatically included in the next snapshot of the VM. You can also use
include or exclude rules to control which virtual disks are included in each
backup. By default, all virtual disks are included in the Volume Inclusion Rule.
Data mount with VMware VM backups follows these steps:
Select the VMware VM and point in time that they want to work with.
Select if you want to mount to an existing host or VM, create a new
VMware VM or restore the disks of the source VMware VM.
If creating a new VMware VM, select the location variables such as which
vCenter, ESX host and datastore to be used.
Backup and DR uses snapshot technology to create new virtual disks from
the backups. When these disks are created they are attached to the host or to
the new or existing VMware VM. These virtual disks are writable, and can be
migrated to physical disks using a VMware Storage VMotion task.
Backup storage location
When you create a backup plan and apply it to a VMware VM, the policies and
profile specify where the backup is stored.
VMware VM-based backup data can be stored directly into Google Cloud Storage,
using a Direct to OnVault template in the backup plan. This works for
Google Cloud VMware Engine, though it is recommended to ensure
sufficient bandwidth exists if you are using this feature. If bandwidth is
limited, then a local snapshot policy is recommended, which retains a copy of
the backup data for a user defined period of time, and in addition to the snapshot
policy, additional OnVault policies can be enabled to store data for longer
periods of time in Google Cloud Storage bucket(s).
Each VM can have up to four OnVault policies, each specifying different
Google Cloud Storage buckets, which could be different storage classes and
different location types.
A multi-regional storage location provides the highest availability and
resilience. A regional storage location gives you more control over the
physical location of your data because you specify a single region.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 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)"]]