Cross-Region Backups

  ┌─aws-us-east-1 (source)─────┐              ┌─aws-us-west-2 (dest)───┐
  │                            │░             │                        │░
  │  ┌──────────────────────┐  │░             │  ┌──────────────────┐  │░
  │  │    my-namespace      │  │░ ──────────▶ │  │ my-namespace-copy│  │░
  │  └──────────────────────┘  │░             │  └──────────────────┘  │░
  │                            │░             │            ▲           │░
  └────────────────────────────┘░             └────────────┼───────────┘░
   ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░              ░░░░░░░░░░░░│░░░░░░░░░░░░░
                                                           │
                                     ──copy_from_namespace─┘

┌─aws-us-east-1 (source)──────┐
│  ┌───────────────────────┐  │░
│  │    my-namespace       │  │░
│  └───────────────────────┘  │░
└─────────────────────────────┘░
 ░░░░░░░░░░░░░│░░░░░░░░░░░░░░░░░
              ▼
┌─aws-us-west-2 (dest)────────┐
│  ┌───────────────────────┐  │░
│  │  my-namespace-copy    │  │░
│  └───────────────────────┘  │░
└─────────────┬───────────────┘░
 ░░░░░░░░░░░░░│░░░░░░░░░░░░░░░░░
              │
──copy_from_namespace

turbopuffer supports efficient namespace copies across regions via copy_from_namespace for geo-redundancy, disaster recovery, and accidental deletion protection. We don't currently offer automated backups. Historically, customers have rebuilt from their primary data source when needed, but cross-region copies are now often a better option.

Copies are performed entirely server-side, so there's no data transfer through your infrastructure. They're billed at up to a 75% write discount and create fully writable namespaces you can use however you like. Cross-region copies also bill returned bytes for the logical size copied. Storage is billed at standard rates, but since you're not querying backup namespaces, they're cheap to keep around, making daily or weekly snapshots practical. Copies work across regions and across cloud providers (e.g., AWS to GCP).

CMEK encryption

To encrypt the backup with a customer managed encryption key (CMEK), specify an encryption key in the encryption parameter. The key must be available in the destination region.

Specifying an encryption key is mandatory if the source namespace has CMEK encryption enabled.

Running Backups on Schedule

To maintain up-to-date backups, run cross-region copies on a regular schedule. Here's an example script (run via cron or any scheduler) that backs up all namespaces matching a prefix. It appends the date to each backup namespace name and automatically cleans up backups older than 7 days:

See Limits for copy throughput estimates.

Recovering a Namespace

Backup namespaces are fully functional. You can either point your application to the namespace in the backup region directly, or copy it to a new namespace in your preferred region as shown below:

For more details on copy_from_namespace, see the write documentation.