To protect your applications from a zonal outage, use Hyperdisk Balanced High Availability volumes to synchronously replicate data across two zones in the same region. You can also use Hyperdisk Balanced High Availability volumes in scenarios that require write access to the same volume multiple zones. This document describes the features of Hyperdisk Balanced High Availability.
You can specify up to 100,000 IOPS and 2,400 MiB/s of throughput for a single Hyperdisk Balanced High Availability volume. Hyperdisk Balanced and Hyperdisk Balanced High Availability are the only Hyperdisk types you can use as a boot disk.
To create a new Hyperdisk Balanced High Availability volume, see Create and manage regional disks.
For more information about Hyperdisk and the other Hyperdisk types, see About Hyperdisk.
Machine series support
You can use Hyperdisk Balanced High Availability with the following machine series:
Use cases
Use Hyperdisk Balanced High Availability for any application that requires high availability and resilience to zonal outages, such as the following:
- High performance workloads that require fast failover
- Workloads that require concurrent write access to data from instances that are in different zones
- Workloads with regulatory requirements for data replication in two locations
- Microsoft SQL Server Failover Cluster Instances (FCI)
Disaster protection for Hyperdisk Balanced High Availability volumes
You can back up a Hyperdisk Balanced High Availability volume with instant snapshots and standard snapshots. Snapshots back up the data on a Hyperdisk Balanced High Availability volume at a specific point in time.
To protect your data in the unlikely event of an outage, you can enable replication across multiple zones and multiple regions for Hyperdisk Balanced High Availability volumes.
Synchronous replication across multiple zones
Zonal replication, also referred to as synchronous replication, of a Hyperdisk Balanced High Availability volume creates replicas of the volume's data in two zones. If there's a temporary outage in one zone, the replica in the other zone ensures the data is still available. To learn more about zonal replication, see About synchronous replication.
Asynchronous replication across multiple regions
You can protect your data in the unlikely event of a regional outage by enabling
Asynchronous Replication. Asynchronous Replication maintains a copy of the data on your
volume in another region. For example, to protect a
Hyperdisk Balanced volume in us-west1,
you can use Asynchronous Replication to replicate the volume to a secondary volume in
the us-east4 region. If the volume in us-west1
became unavailable, then you could use the secondary volume in us-east4.
Baseline performance
Hyperdisk Balanced High Availability volumes include, at no extra charge, up to 3,000 IOPS and 140 MiB/s of throughput. You're billed for provisioned throughput that exceeds 140 MiB/s and provisioned IOPS that exceeds 3,000 IOPS.
About provisioned performance for Hyperdisk Balanced High Availability
You don't have to provision performance when you create Hyperdisk volumes. If you don't provision performance, Compute Engine creates the volume with default values that you can modify later. For details about default values, see Default IOPS and throughput values.
If you know your performance needs, you can specify IOPS and throughput limits for a Hyperdisk Balanced High Availability volume when you create the volume, and you can change the provisioned values after the volume has been created. You can't specify an IOPS or throughput level if you don't specify a size.
Size and performance limits
The following limits apply to the size, IOPS, and throughput values you can specify for a Hyperdisk Balanced High Availability volume.
- Size: between 4 GiB and 64 TiB. The default size is 100 GiB.
- IOPS: between 3,000 and 100,000 IOPS. For volumes less than 320 GiB, the range of IOPS values you can specify varies by size. For details, see Limits for configurable IOPS.
- Throughput: between 140 and 2,400 MiB/s of throughput, but the throughput value depends on how much IOPS you provision. For details, see Limits for provisioned throughput.
Limits for configurable IOPS
You can choose the IOPS limit for a Hyperdisk Balanced High Availability volume according to the following limits. The minimum and maximum limits vary by size, as follows
- Minimum configurable IOPS:
- 4 or 5 GiB volumes: IOPS is fixed at 2,000 and 2,500 IOPS, respectively.
- 6 GiB-64 TiB: at least 3,000 IOPS.
- Maximum configurable IOPS:
- 6-249 GiB volumes: varies according to this formula, where
xis the volume's size in GiB:MIN (500x or 3,000). - 250 GiB-64 TiB volumes: at most 100,000 IOPS.
- 6-249 GiB volumes: varies according to this formula, where
The following table lists the limits for configurable IOPS for common volume sizes. If a size isn't listed, use the previously mentioned formula to calculate the maximum configurable IOPS.
| Size (GiB) | Configurable IOPS values |
|---|---|
| 4 | 2,000 |
| 5 | 2,500 |
| 10 | 3,000-5,000 |
| 50 | 3,000-25,000 |
| 150 | 3,000-75,000 |
| 249 | 3,000-95,000 |
| 250 or more | 3,000-100,000 |
Limits for configurable throughput
Volumes with 4-5 GiB of capacity have a fixed throughput value of
140 MiB/s.
For larger volumes, you can provision additional throughput. The range of supported
throughput values depends on the provisioned IOPS, based on the following formulas.
P is the provisioned IOPS value.
- Minimum configurable throughput:
MAX (140, P/256)MiB/s - Maximum configurable throughput:
MIN (2400 MiB/s, P/4)MiB/s
The following table lists the limits for some provisioned IOPS values and the corresponding throughput ranges. If a size isn't listed, use the formula to calculate the allowable values.
| Provisioned IOPS | Configurable throughput (MiB/s) |
|---|---|
| 2,000 | 140-500 |
| 2,500 | 140-625 |
| 3,000 | 140-750 |
| 4,000 | 140-1,000 |
| 8,000 | 140-2,000 |
| 32,000 | 140-2,400 |
| 50,000 | 156-2,400 |
| 64,000 | 250-2,400 |
| 3,000-100,000 | 140-2,400 |
| 3,000-100,000 | 250-2,400 |
Default IOPS and throughput values
If you don't specify an IOPS or throughput limit when you create a Hyperdisk Balanced High Availability volume,
Compute Engine assigns default values. The assigned value is based on the
following formulas, where x is the volume's size.
- Default IOPS:
- Volumes 6 GiB or less:
500xIOPS - Volumes 6 GiB and 26.666667 TiB:
6x + 3,000IOPS - Volumes larger than 26.666667 TiB: 100,000 IOPS
- Volumes 6 GiB or less:
- Default throughput
- Volumes 6 GiB or less:
140MiB/s - Volumes larger than 6 GiB:
1.5x + 140MiB/s
- Volumes 6 GiB or less:
- Default size: 100 GiB
Change the provisioned performance or size
You can change the provisioned performance and size of a Hyperdisk Balanced High Availability volume at most once every 4 hours. To learn how to modify size or performance, see Modify a Hyperdisk volume.
Performance limits when attached to an instance
This section lists the performance limits for Hyperdisk Balanced High Availability. You can specify up to 100,000 IOPS and 2,400 MiB/s of throughput for a single Hyperdisk Balanced High Availability volume.
The following table lists the maximum performance that Hyperdisk Balanced High Availability volumes can achieve for each supported instance. A Hyperdisk Balanced High Availability volume's performance when it's attached to an instance can't exceed the limits for the instance's machine type. The performance limits are also shared across all Hyperdisk Balanced High Availability volumes attached to the same instance, regardless of each volume's provisioned performance.
Achieve higher performance with multiple Hyperdisk Balanced High Availability volumes
Certain instances can exceed the maximum performance for a single Hyperdisk Balanced High Availability volume— 100,000 IOPS or 2,400 MiB/s. An instance can achieve these higher limits if you attach multiple Hyperdisk Balanced High Availability volumes to the instance.
If an instance's performance limit in the following table exceeds
100,000 IOPS or 2,400 MiB/s, then the instance can achieve that
limit only if you attach multiple Hyperdisk Balanced High Availability volumes.
For example, the performance limit for a c4a-*-72 instance using Hyperdisk Balanced High Availability
is 240,000 IOPS and 5,000 MiB/s. To achieve this maximum performance
you must attach at least two Hyperdisk Balanced High Availability volumes to the instance.
The performance limits also apply to custom machine types.
| Instance machine type | Maximum IOPS | Maximum throughput (MiB/s) |
|---|---|---|
c3-*-4 |
25,000 | 400 |
c3-*-8 |
50,000 | 600 |
c3-*-22 |
100,000 | 600 |
c3-*-44 |
100,000 | 600 |
c3-*-88 |
100,000 | 2,500 |
c3-*-176 |
100,000 | 2,500 |
c3-*-192 |
100,000 | 2,500 |
c3d-*-4 |
25,000 | 400 |
c3d-*-8 |
50,000 | 600 |
c3d-*-16 |
100,000 | 600 |
c3d-*-30 |
100,000 | 600 |
c3d-*-60 |
100,000 | 1,200 |
c3d-*-90 |
100,000 | 1,200 |
c3d-*-180 |
100,000 | 1,200 |
c3d-*-360 |
100,000 | 1,200 |
c4a-*-1 |
25,000 | 400 |
c4a-*-2 |
50,000 | 800 |
c4a-*-4 |
50,000 | 800 |
c4a-*-8 |
50,000 | 1,000 |
c4a-*-16 |
80,000 | 1,600 |
c4a-*-32 |
120,000 | 2,400 |
c4a-*-48 |
160,000 | 3,300 |
c4a-*-64 |
240,000 | 4,400 |
c4a-*-72 |
240,000 | 5,000 |
m3-*-32 |
100,000 | 1,900 |
m3-*-64 |
100,000 | 2,500 |
m3-*-128 |
100,000 | 2,500 |
n4-*-2 |
15,000 | 240 |
n4-*-4 |
15,000 | 240 |
n4-*-6 |
15,000 | 240 |
n4-*-8 |
15,000 | 480 |
n4-*-10 |
15,000 | 480 |
n4-*-12 |
15,000 | 480 |
n4-*-14 |
15,000 | 480 |
n4-*-16 |
80,000 | 1,200 |
n4-*-18 |
80,000 | 1,200 |
n4-*-20 |
80,000 | 1,200 |
n4-*-22 |
80,000 | 1,200 |
n4-*-24 |
80,000 | 1,200 |
n4-*-26 |
80,000 | 1,200 |
n4-*-28 |
80,000 | 1,200 |
n4-*-30 |
80,000 | 1,200 |
n4-*-32 |
100,000 | 1,600 |
n4-*-34 |
100,000 | 1,600 |
n4-*-36 |
100,000 | 1,600 |
n4-*-38 |
100,000 | 1,600 |
Regional availability for Hyperdisk Balanced High Availability
Hyperdisk Balanced High Availability is available in the following regions:
- Changhua County, Taiwan—
asia-east1 - Tokyo, Japan—
asia-northeast1 - Osaka, Japan—
asia-northeast2 - Jurong West, Singapore—
asia-southeast1 - Mumbai, India—
asia-south1 - Sydney, Australia—
australia-southeast1 - St. Ghislain, Belgium—
europe-west1 - London, England—
europe-west2 - Frankfurt, Germany—
europe-west3 - Eemshaven, Netherlands—
europe-west4 - Milan, Italy—
europe-west8 - Paris, France—
europe-west9 - Turin, Italy—
europe-west12 - Madrid, Spain—
europe-southwest1 - Doha, Qatar—
me-central1 - Dammam, Saudi Arabia—
me-central2 - Tel Aviv, Israel—
me-west1 - Montréal, Québec—
northamerica-northeast1 - Toronto, Ontario—
northamerica-northeast2 - Queretaro, Mexico—
northamerica-south1 - Osasco, São Paulo, Brazil—
southamerica-east1 - Council Bluffs, Iowa—
us-central1 - Moncks Corner, South Carolina—
us-east1 - Ashburn, Virginia—
us-east4 - Columbus, Ohio—
us-east5 - Dallas, Texas—
us-south1 - The Dalles, Oregon—
us-west1 - Las Vegas, Nevada—
us-west4
Share a Hyperdisk Balanced High Availability volume between VMs
To enable workload clustering and rapid high-availability (HA) failover with a recovery time objective of less than one second, you can attach the same Hyperdisk Balanced High Availability volume to multiple instances. When you attach a Hyperdisk Balanced High Availability volume to multiple instances at the same time, each instance maintains write access to the volume. To attach a volume to multiple instances, each instance must be in the same zone as the volume's replicas.
To learn more, see Share a disk between VMs.
Pricing
You're billed for the total provisioned size, IOPS, and throughput of your Hyperdisk Balanced High Availability volumes until you delete them. Charges incur even if the volume isn't attached to any instances or if the instance is suspended or stopped. For more information, see Disk pricing.
Limitations for Hyperdisk Balanced High Availability
- You can't create a machine image from a Hyperdisk Balanced High Availability volume.
- You can't back up a Hyperdisk Balanced High Availability volume that's in multi-writer mode with snapshots or images. You must disable multi-writer mode first.
- You can change a Hyperdisk volume's size and performance every at most once every 4 hours.