To restore a Cloud SQL database from an image-level backup, Veeam Backup for Google Cloud performs the following steps:
- Creates a temporary snapshot of the Cloud SQL instance that will host the restored database.
- Deploys a worker instance within the worker project in the Google Cloud region in which the target Cloud SQL instance resides.
For more information on how to specify a project for worker instances, see Managing Worker Configurations.
- [Applies only to restore points of MySQL instances protected by Veeam Backup for Google Cloud version 4.0 and earlier] Uses native Google Cloud capabilities to import the exported data to the target Cloud SQL instance.
- Uses the worker instance to retrieve database files, triggers, stored procedures and users of the processed Cloud SQL instance from the backup file, and then imports this data to the target Cloud SQL instance.
- Removes the worker instance from Google Cloud.
- Deletes the temporary snapshot.
If Veeam Backup for Google Cloud fails to restore the database, the temporary snapshot will not be deleted automatically. You can either delete the snapshot manually or use it to revert the Cloud SQL instance to its initial state. Consider that if the target instance hosts other databases and any write operations to these databases occur during the restore process, the revert operation will result in data loss.
To learn how to restore a Cloud SQL database from an image-level backup, see Performing Database Restore.