2.11.0 (latest) 2.10.3 2.7.0 2.6.2 2.5.0 2.4.0 2.3.0 2.2.1 2.1.2 2.0.2 1.3.5 1.2.3 1.1.2 1.0.3 Reference documentation and code samples for the Google BigQuery Reservation V1 Client class FailoverMode.

The failover mode when a user initiates a failover on a reservation
determines how writes that are pending replication are handled after the
failover is initiated.

Protobuf type `google.cloud.bigquery.reservation.v1.FailoverMode`

## Namespace

Google \\ Cloud \\ BigQuery \\ Reservation \\ V1

## Methods

### static::name

| **Parameter** ||
|---|---|
| **Name** | **Description** |
| `value` | `mixed` |

### static::value

| **Parameter** ||
|---|---|
| **Name** | **Description** |
| `name` | `mixed` |

## Constants

### FAILOVER_MODE_UNSPECIFIED

    Value: 0

Invalid value.

Generated from protobuf enum `FAILOVER_MODE_UNSPECIFIED = 0;`

### SOFT

    Value: 1

When customers initiate a soft failover, BigQuery will wait until all
committed writes are replicated to the secondary. This mode requires both
regions to be available for the failover to succeed and prevents data loss.

Generated from protobuf enum `SOFT = 1;`

### HARD

    Value: 2

When customers initiate a hard failover, BigQuery will not wait until all
committed writes are replicated to the secondary. There can be data loss
for hard failover.

Generated from protobuf enum `HARD = 2;`