This is an archive version of the document. To get the most up-to-date information, see the current version.Data Protection
With Veeam Backup for Google Cloud, you can protect Google Cloud resources in the following ways:
- Create cloud-native snapshots of VM instances
A cloud-native snapshot includes point-in-time snapshots of persistent disks attached to the processed VM instance. Snapshots of persistent disks (also referred to as PD snapshots) are taken using native Google Cloud capabilities.
- Create image-level backups of VM instances
In addition to cloud-native snapshots, you can protect your VM instances with image-level backups. An image-level backup captures the whole image of the processed VM instance (including OS data, application data and so on) at a specific point in time. The backup is saved as multiple files to a storage bucket in the native Veeam format.
- Create cloud-native snapshots of Cloud SQL instances
A cloud-native snapshot is a point-in-time snapshot of the processed Cloud SQL instance. Snapshots of Cloud SQL instances are taken using native Google Cloud capabilities. By default, cloud-native snapshots are stored in the multi-region that is located geographically close to the region in which the source instance resides.
Note |
Cloud-native snapshots of Cloud SQL instances are referred to as backups in Google Cloud documentation. However, since all 'backups' of a Cloud SQL instance are automatically deleted after you remove the instance itself, 'backups' of Cloud SQL instances are referred to as snapshots in this guide. In terms of Veeam logic, backups are independent files that are stored in repositories and that are not affected by any actions performed with the source instances whatsoever. |
- Create image-level backups of Cloud SQL instances
In addition to cloud-native snapshots, you can protect your Cloud SQL instances with image-level backups. An image-level backup captures the whole image of the processed Cloud SQL instance (including the instance configuration, databases, triggers, stored procedures and users) at a specific point in time. The backup is saved as multiple files to a storage bucket in the native Veeam format.
Note |
Veeam Backup for Google Cloud allows you to protect MySQL and PostgreSQL instances only. SQL Server instances are not supported. For more information on types of Cloud SQL instances, see Google Cloud documentation. |
To schedule data protection tasks to run automatically, create backup policies. For VM instances and Cloud SQL instances residing in any of the regions added to the backup policies, you can also take cloud-native snapshots manually when needed — for more information, see the Veeam Backup for Google Cloud User Guide, sections Creating VM Snapshots Manually and Creating SQL Snapshots Manually. To learn how to backup works, see the Veeam Backup for Google Cloud User Guide, section How Backup Works.
Additional Data Protection Options
You can create an additional layer of protection for your VM using the following Veeam Backup & Replication functionality:
- Create copies of image-level backups
Backup copy jobs allow you to create and keep multiple copies of the same backed-up data in different locations. To learn how to create backup copy jobs, see Creating Backup Copy Jobs.
- Store copies of image-level backups on tapes
Backup to tape jobs allow you to keep backed-up data on tape devices. To learn how to create backup to tape jobs, see Copying Backups to Tapes.
In This Section
