mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-09 10:56:49 +00:00
108 lines
3.7 KiB
Text
108 lines
3.7 KiB
Text
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] [--tags=[KEY=VALUE,...]]
|
|
[--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
|
|
|
|
To create a new cross-region backup, run:
|
|
|
|
$ gcloud alloydb backups create \
|
|
projects/my-project/locations/us-west1/backups/my-backup \
|
|
--cluster=my-cluster --region=us-central1
|
|
|
|
POSITIONAL ARGUMENTS
|
|
BACKUP
|
|
The AlloyDB backup to create. This must either be the backup ID
|
|
(myBackup) or the full backup path
|
|
(projects/myProject/locations/us-central1/backups/myBackup). In the
|
|
first case, the project and location are assumed to be the same as the
|
|
cluster being backed up. The second form can be used to create
|
|
cross-region and cross-project backups.
|
|
|
|
REQUIRED FLAGS
|
|
--cluster=CLUSTER
|
|
AlloyDB cluster ID
|
|
|
|
--region=REGION
|
|
The region of the cluster to backup.
|
|
|
|
OPTIONAL FLAGS
|
|
--async
|
|
Return immediately, without waiting for the operation in progress to
|
|
complete.
|
|
|
|
--tags=[KEY=VALUE,...]
|
|
List of tags KEY=VALUE pairs to bind. Each item must be expressed as
|
|
<tag-key-namespaced-name>=<tag-value-short-name>.
|
|
|
|
Example: 123/environment=production,123/costCenter=marketing
|
|
|
|
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 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
|
|
These variants are also available:
|
|
|
|
$ gcloud alpha alloydb backups create
|
|
|
|
$ gcloud beta alloydb backups create
|
|
|