Recover connections, schedules, and validation

Connections

• A connection stores an encrypted connection string or Firebase Firestore service-account configuration for a single protected data source.
• Connection strings are encrypted with a dedicated key, separate from other integration secrets.
• MySQL backups use mysqldump-compatible artifacts and support validation and restore workflows equivalent to PostgreSQL backups.
• Firebase Firestore backups use managed Firestore exports to the Google Cloud Storage outputUriPrefix in the encrypted Firebase configuration.
• The number of protected connections allowed depends on your plan.

Schedules and retention

• Automated schedules use a five field cron expression and require the Pro plan or higher.
• Each schedule has a retention window, capped by your plan's maximum retention days.
• Backups run against a shared platform storage bucket by default, or a storage destination you provide.

Validation tiers

• Tier one always runs: it confirms the backup archive or Firestore export manifest is not corrupt.
• Tier two, available on the Business plan, restores or imports the backup into a dedicated scratch target for a stronger guarantee.
• A failed validation raises an alert so you find out before you need the backup, not during a recovery.

Related documentation