Back up and restore AlloyDB Omni

Select a documentation version:

This page provides an overview of data backup and restore solutions available to AlloyDB Omni database clusters.

Because AlloyDB Omni is PostgreSQL compatible, various backup solutions developed and supported by the PostgreSQL community are also available to AlloyDB Omni databases. In general, any solution that allows you to back up from and restore to a PostgreSQL cluster running in a Docker container will also work with AlloyDB Omni.

The way that you set up and operate backup and restore features depends on whether you operate AlloyDB Omni on individual servers using the alloydb command-line tool, or whether you run AlloyDB Omni using the AlloyDB Omni Operator. The following sections explore these options in further detail.

Single-server backup solutions

If you run AlloyDB Omni in a container on individual servers, then Google recommends using either Barman or pgBackRest, depending on your needs and preferences.

Both of these open source solutions provide the following:

  • Essential data backup and restore features, including point-in-time recovery
  • Compatibility with the containerized PostgreSQL-compatible databases that AlloyDB Omni uses

Barman has the following distinct features:

  • Backups stored in a separate backup server that you manage
  • The option for cascading backup servers
  • Near-zero-data-loss backups using streamed data changes
  • The option for zero-data-loss backups using synchronous streaming

For more information, see Set up Barman for AlloyDB Omni.

pgBackRest has the following distinct features:

  • Parallelized backup jobs
  • Full, incremental, or differential backups
  • Encrypted backups
  • Backup compression and checksums
  • The option to restore only specific databases

For more information, see Set up pgBackRest for AlloyDB Omni.

Kubernetes backup solutions

If you have deployed AlloyDB Omni onto a Kubernetes cluster, then the AlloyDB Omni Operator provides backup and restore methods without the need for any further configuration.

For more information, see Back up and restore in Kubernetes.

What's next