This document provides an overview of virtual machine (VM) backup and restore operations in Google Distributed Cloud (GDC) air-gapped environments. It outlines the different methodologies and the distinction between GDC console and API capabilities.
This document is for developers in platform administrator or application operator groups that manage VM backup operations. For more information, see Audiences for GDC air-gapped documentation.
GDC supports the ability to back up and restore VM-based and container-based workloads. GDC VM backup supports the backup and restoration of multiple VM or VM disk snapshots. Backups are managed through backup plans, which let you schedule regular backups or create backups manually. You can restore entire VMs, creating a new instance with the same configuration and disk state as the backup, or restore disk snapshots.
GDC backup for VMs offer the following features:
- Support for different VM instance configurations and sizes.
- Customer data stored in primary storage in the form of Kubernetes persistent volumes and VM disk images.
- Local snapshots for VM disks.
Backup and restoration process
You can back up and restore your Distributed Cloud data in the GDC console or the API.
To back up and restore VM and container workloads, follow these general steps:
- Create a backup repository.
- Create a backup plan that references the backup repository:
- Either let the backup plan automatically create scheduled backups or manually create a backup.
- Back up VMs or back up disks in the form of snapshots.
- Restore VMs or snapshots based on the backups.
Backup repository overview
Before you create backups or snapshots, you must create a backup repository. A backup repository contains configuration information, for example, the bucket name, region, and storage endpoint. The backup repository name is provided as an input parameter when you create a VM backup plan.
For more information, see Create a backup repository.
VM backup resources
The VM backup system in GDC consists of these key custom resources (CRs):
BackupRepository: The location where the backup data is stored. This resource is manageable through the API and the GDC console.VirtualMachineBackupPlanTemplate: Defines the backup repository used. This resource is manageable through the API and the GDC consoleVirtualMachineBackupPlan: Defines a scheduled, recurring backup strategy. This resource specifies the backup schedule, the scope of VMs to be backed up, and the retention policy for the backups. This resource is only manageable through the API.VirtualMachineBackupRequest: Triggers an immediate backup. This resource can be used for both one-off manual backups and to manually initiate a backup defined in aVirtualMachineBackupPlan. This resource is manageable through the API and the GDC console, but you can only trigger a backup plan using the API.VirtualMachineRestoreRequest: Restores a VM from a backup. This resource is manageable through the API and the GDC console.
Plan backups
You can create a backup plan and perform backup and restore functions using either the API or the GDC console. All backup methods are supported through the API, while on-demand, manual backups are the only backup types the GDC console supports.
Scheduled backups (API only)
This method involves the creation of a VirtualMachineBackupPlan resource,
which references a VirtualMachineBackupPlanTemplate. You can define a
recurring backup schedule, the scope of VMs to include, and a retention policy.
For more details, see Create a scheduled backup plan to back up and restore VMs.
On-demand backups (GDC console and API)
This method uses a VirtualMachineBackupRequest resource that directly references
a VirtualMachineBackupPlanTemplate. You can perform a one-time backup of a
specific VM or VM disk. For more details, see Create a manual backup.
Manual trigger of a defined backup plan (GDC console and API)
This method uses a VirtualMachineBackupRequest resource that references an existing
VirtualMachineBackupPlan. It immediately triggers a backup of all VMs defined
in the scope of the referenced plan. This backup method is useful for taking an
ad hoc backup of a group of VMs that are part of a scheduled plan.
For more information, see Create a manual backup.
Restore backups
You can restore VM workloads or disk snapshots for backups you create manually or as part of the scheduled backup plans:
For scheduled backup plan restoration, see Create a backup restore or Create a fine-grained restore
For VM workloads, the restoration process creates a new VM with the same configuration and disk state as the backup. For more information, see Create a VM from a backup.
For disk snapshots, the restore creates a new disk with the same configuration and disk state as the snapshot. For more information, see Restore from a snapshot.