Turbo replication

Go to examples

Turbo replication is a Cloud Storage premium feature designed to asynchronously replicate newly written Cloud Storage objects associated with any write, rewrite, copy, or compose operation—regardless of object size—to a separate region within a target of 15 minutes. Available for dual-region buckets, turbo replication offers a shorter, more predictable recovery point objective (RPO), helping to reduce data loss exposure.

Business continuity and disaster recovery

Turbo replication provides geo-redundancy for your Cloud Storage data within a target 15-minute window. While traditional storage models often rely on primary and secondary geographic locations, geo-redundancy simplifies the disaster recovery process by eliminating the need for users to redirect network usage between primary and secondary locations.

Cloud Storage uses Cloud Load Balancing to serve dual-region buckets from multiple regions. As a result, in the case of a regional outage, turbo replication is designed to substantially reduce the risk of data loss exposure to data written within the target of the last 15 minutes.

While dual-region storage and turbo replication help support business continuity and disaster recovery (BCDR) efforts, administrators should plan and implement a full BCDR architecture that's appropriate for their workload.

For more information, see Step-by-step guide to designing disaster recovery for applications in Google Cloud.

Should you use turbo replication?

Turbo replication provides the following benefits, backed by the Cloud Storage SLA:

  • Provides faster geo-redundancy for data in your dual-region buckets. Turbo replication reduces the risk of data loss exposure by targeting replication to a separate region within 15 minutes. While Cloud Storage dual- and multi-region buckets include a default replication behavior that asynchronously replicates newly written objects to a separate region—often most objects within minutes—turbo replication is designed to offer a shorter, more predictable replication target of 15 minutes.

  • Helps support uninterrupted service following a regional outage. Cloud Storage always understands the current state of the bucket and will transparently serve objects from either region as required. As a result, dual-region buckets are designed to have an RTO of zero and temporary regional failures are normally invisible to users.

Available regions

Turbo replication is available for the dual-region buckets ASIA1, EUR4, and NAM4.

For more information, see Cloud Storage bucket locations.

For pricing information, see Detailed pricing example.

Restrictions

The following restrictions apply when using turbo replication:

  • Turbo replication is only available for dual-region buckets.

  • A bucket's geographic location is non-editable metadata set at bucket creation. If you want to use turbo replication for data stored in a region or multi-region bucket, you must transfer the data to a dual-region bucket. For more information, see Moving and renaming buckets.

Feature limitations

Turbo replication is designed to replicate newly written objects associated with any write, rewrite, copy or compose operation to a separate region within a target of 15 minutes. Some exceptions apply:

  • After an existing bucket has turbo replication enabled, there may be a 10-second propagation delay for newly written objects.

  • After you enable turbo replication on a bucket, new write operations are replicated across regions within a target of 15 minutes. Writes that began prior to service activation replicate across regions at the default replication rate. It is generally safe to assume that the entire bucket begins to meet the target of 15-minute replication within 48 hours of enabling turbo replication.

  • While in Preview, objects created through compose operations may not begin the objective of 15-minute replication until 48 hours from the last component-piece upload. This applies to compose operations that began before and after service activation.

  • While in Preview, objects created as a result of multi-part upload operations are not yet supported. When available, turbo replication charges apply.

  • While in Preview, bucket-level operations are not yet supported through the XML API, including the following requests. When available, turbo replication charges apply:

    • Checking a bucket's replication status.

    • Creating a new bucket with turbo replication enabled.

    • Activating and deactiving the service.

Cloud Storage SLA

The turbo replication Service Level Objectives (SLOs) described in the Cloud Storage SLA have been published during Preview for reference only and will become effective once turbo replication becomes generally available.

What's next