Workload VM backup solutions

Protecting application data in virtual machines (VMs) is a key requirement for business-critical applications running on Google Cloud VMware Engine.

This page provides different options and considerations for deploying backup infrastructure that protects your VMs and data in VMware Engine.

You can continue to use the same backup tools that you use on-premises to back up your VMware VMs and data in VMware Engine.

Supported backup solutions

Google provides Backup and DR Service as a backup solution for workloads on Google Cloud. Third-party agent-based backup solutions can interoperate with VMware Engine if they provide application-level backups and are certified by application vendors (for example, RMAN for Oracle).

Backup solutions that can interoperate with VMware Engine must comply with the VMware vStorage API for Data Protection (VADP) protocol standard and be certified by VMware for vSAN. VMware Engine has validated the following backup solutions for compliance:

• Cohesity DataPlatform
• Dell EMC Data Protection Solution
• Veeam Backup & Replication
• Commvault Backup & Recovery
• Rubrik Cloud Data Management

Backup solution considerations

Consider the following questions before you design your backup solution and implement a deployment model in VMware Engine.

Deciding on a backup technology

You can use either an agent-based or a VADP-based backup approach. We recommend using a VADP-based approach when migrating workloads from on-premises environments because it requires fewer changes. It also provides flexibility in the choice of location for backup repositories.

An agent-based backup approach for migrated VMs requires additional configuration if a Layer 2 network is stretched from an on-premises environment to VMware Engine or if you want to change the location of the primary backup repository during migration.

Determining the number of data copies to store

You must assess the overall backup requirements, objectives, and your enterprise policies. Include the requirements for storing backups in specific locations like on premises, off premises, your recovery time objective (RTO), and recovery point objective (RPO).

Determining where to store backup data

There are several places where you can store backup data (backup repository). Each location offers a different combination of storage cost, recovery time objective (RTO), number of copies, and network outbound data transfer charges. Base your choice on the application requirements, costs, and capabilities of your backup software.

Consider the following main choices and their key aspects relevant for storing backups of VMs and data: