Skip to main content

GCP Sql Admin Backup Run

A GCP Sql Admin Backup Run resource represents a single automatic or on-demand backup operation performed for a Cloud SQL instance. It records metadata such as the backup’s start and end timestamps, status (e.g. SUCCESSFUL, FAILED, RUNNING), backup type (automated or on-demand), storage location, encryption details and size. Observing these objects lets you verify that your instances are being backed up as expected and that every deployment has a recent, valid restore point.
Official documentation: https://cloud.google.com/sql/docs/mysql/admin-api/rest/v1/backupRuns#BackupRun

Supported Methods​

  • GET: Get a gcp-sql-admin-backup-run by its "instances|backupRuns"
  • LIST
  • SEARCH: Search for gcp-sql-admin-backup-run by its "instances"

gcp-sql-admin-instance​

Every backup run is scoped to exactly one Cloud SQL instance. The instance field in the backup run identifies the parent gcp-sql-admin-instance, so Overmind links the two to show which database the backup belongs to.

gcp-cloud-kms-crypto-key​

If the Cloud SQL instance uses Customer-Managed Encryption Keys (CMEK), the backup’s diskEncryptionConfiguration points to the KMS key used. Overmind therefore links a backup run to the relevant gcp-cloud-kms-crypto-key, enabling you to trace encryption dependencies and verify key rotation and access policies.