mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-16 12:22:03 +00:00
gcloud: Thu Jan 19 00:56:33 UTC 2023
This commit is contained in:
parent
348d9760ee
commit
1248f773ec
1462 changed files with 51835 additions and 5402 deletions
85
gcloud/alloydb/backups/create
Normal file
85
gcloud/alloydb/backups/create
Normal file
|
|
@ -0,0 +1,85 @@
|
|||
NAME
|
||||
gcloud alloydb backups create - creates a new AlloyDB backup within a given
|
||||
project
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alloydb backups create BACKUP --cluster=CLUSTER --region=REGION
|
||||
[--async]
|
||||
[--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING
|
||||
--kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
Creates a new AlloyDB backup within a given project.
|
||||
|
||||
EXAMPLES
|
||||
To create a new backup, run:
|
||||
|
||||
$ gcloud alloydb backups create my-backup --cluster=my-cluster \
|
||||
--region=us-central1
|
||||
|
||||
POSITIONAL ARGUMENTS
|
||||
BACKUP
|
||||
AlloyDB backup ID
|
||||
|
||||
REQUIRED FLAGS
|
||||
--cluster=CLUSTER
|
||||
AlloyDB cluster ID
|
||||
|
||||
--region=REGION
|
||||
The region of the cluster to backup. Note: both the cluster and the
|
||||
backup have to be in the same region.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--async
|
||||
Return immediately, without waiting for the operation in progress to
|
||||
complete.
|
||||
|
||||
Key resource - The Cloud KMS (Key Management Service) cryptokey that will
|
||||
be used to protect the backup. 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 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 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
|
||||
These variants are also available:
|
||||
|
||||
$ gcloud alpha alloydb backups create
|
||||
|
||||
$ gcloud beta alloydb backups create
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue