1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 18:45:13 +00:00
gcloud-help/gcloud/alpha/alloydb/clusters/restore
2023-02-15 10:13:15 +00:00

120 lines
4.4 KiB
Text

NAME
gcloud alpha alloydb clusters restore - restore an AlloyDB cluster from a
given backup
SYNOPSIS
gcloud alpha alloydb clusters restore CLUSTER --region=REGION [--async]
[--network=NETWORK]
[--backup=BACKUP
| --point-in-time=POINT_IN_TIME --source-cluster=SOURCE_CLUSTER]
[--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
--kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Restore an AlloyDB cluster from a given backup.
EXAMPLES
To restore a cluster from a backup, run:
$ gcloud alpha alloydb clusters restore my-cluster \
--region=us-central1 --backup=my-backup
POSITIONAL ARGUMENTS
CLUSTER
AlloyDB cluster ID
REQUIRED FLAGS
--region=REGION
Regional location (e.g. asia-east1, us-east1). See the full list of
regions at https://cloud.google.com/sql/docs/instance-locations.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--network=NETWORK
Network in the current project that the instance will be part of. To
specify using a network with a shared VPC, use the full URL of the
network. For an example host project, 'testproject', and shared
network, 'testsharednetwork', this would be of the
form:--network=projects/testproject/global/networks/testsharednetwork
RestoreCluster source types.
At most one of these can be specified:
Restore a cluster using a specific backup as the source.
--backup=BACKUP
AlloyDB backup ID
Restore a cluster from a source cluster at a given point in time.
--point-in-time=POINT_IN_TIME
Point in time to restore to, in RFC 3339 format. For example,
2012-11-15T16:19:00.094Z.
This flag argument must be specified if any of the other arguments
in this group are specified.
--source-cluster=SOURCE_CLUSTER
Source cluster name.
This flag argument must be specified if any of the other arguments
in this group are specified.
Key resource - The Cloud KMS (Key Management Service) cryptokey that will
be used to protect the cluster. The 'AlloyDB Service Agent' service
account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'.
The arguments in this group can be used to specify the attributes of this
resource.
--kms-key=KMS_KEY
ID of the key or fully qualified identifier for the key. To set the
kms-key attribute:
▸ provide the argument --kms-key on the command line.
This flag argument must be specified if any of the other arguments in
this group are specified.
--kms-keyring=KMS_KEYRING
The KMS keyring of the key. To set the kms-keyring attribute:
▸ provide the argument --kms-key on the command line with a fully
specified name;
▸ provide the argument --kms-keyring on the command line.
--kms-location=KMS_LOCATION
The Google Cloud location for the key. To set the kms-location
attribute:
▸ provide the argument --kms-key on the command line with a fully
specified name;
▸ provide the argument --kms-location on the command line.
--kms-project=KMS_PROJECT
The Google Cloud project for the key. To set the kms-project
attribute:
▸ provide the argument --kms-key on the command line with a fully
specified name;
▸ provide the argument --kms-project on the command line;
▸ set the property core/project.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist. These variants are also available:
$ gcloud alloydb clusters restore
$ gcloud beta alloydb clusters restore