.TH "GCLOUD_ALLOYDB_BACKUPS_CREATE" 1 .SH "NAME" .HP gcloud alloydb backups create \- creates a new AlloyDB backup within a given project .SH "SYNOPSIS" .HP \f5gcloud alloydb backups create\fR \fIBACKUP\fR \fB\-\-cluster\fR=\fICLUSTER\fR \fB\-\-region\fR=\fIREGION\fR [\fB\-\-async\fR] [\fB\-\-tags\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-kms\-key\fR=\fIKMS_KEY\fR\ :\ \fB\-\-kms\-keyring\fR=\fIKMS_KEYRING\fR\ \fB\-\-kms\-location\fR=\fIKMS_LOCATION\fR\ \fB\-\-kms\-project\fR=\fIKMS_PROJECT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR] .SH "DESCRIPTION" Creates a new AlloyDB backup within a given project. .SH "EXAMPLES" To create a new backup, run: .RS 2m $ gcloud alloydb backups create my\-backup \-\-cluster=my\-cluster \e \-\-region=us\-central1 .RE To create a new cross\-region backup, run: .RS 2m $ gcloud alloydb backups create \e projects/my\-project/locations/us\-west1/backups/my\-backup \e \-\-cluster=my\-cluster \-\-region=us\-central1 .RE .SH "POSITIONAL ARGUMENTS" .RS 2m .TP 2m \fIBACKUP\fR 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. .RE .sp .SH "REQUIRED FLAGS" .RS 2m .TP 2m \fB\-\-cluster\fR=\fICLUSTER\fR AlloyDB cluster ID .TP 2m \fB\-\-region\fR=\fIREGION\fR The region of the cluster to backup. .RE .sp .SH "OPTIONAL FLAGS" .RS 2m .TP 2m \fB\-\-async\fR Return immediately, without waiting for the operation in progress to complete. .TP 2m \fB\-\-tags\fR=[\fIKEY\fR=\fIVALUE\fR,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as \f5=\fR. Example: \f5123/environment=production,123/costCenter=marketing\fR .TP 2m 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. .TP 2m \fB\-\-kms\-key\fR=\fIKMS_KEY\fR ID of the key or fully qualified identifier for the key. To set the \f5kms\-key\fR attribute: .RS 2m .IP "\(em" 2m provide the argument \f5\-\-kms\-key\fR on the command line. .RE .sp This flag argument must be specified if any of the other arguments in this group are specified. .TP 2m \fB\-\-kms\-keyring\fR=\fIKMS_KEYRING\fR The KMS keyring of the key. To set the \f5kms\-keyring\fR attribute: .RS 2m .IP "\(em" 2m provide the argument \f5\-\-kms\-key\fR on the command line with a fully specified name; .IP "\(em" 2m provide the argument \f5\-\-kms\-keyring\fR on the command line. .RE .sp .TP 2m \fB\-\-kms\-location\fR=\fIKMS_LOCATION\fR The Google Cloud location for the key. To set the \f5kms\-location\fR attribute: .RS 2m .IP "\(em" 2m provide the argument \f5\-\-kms\-key\fR on the command line with a fully specified name; .IP "\(em" 2m provide the argument \f5\-\-kms\-location\fR on the command line. .RE .sp .TP 2m \fB\-\-kms\-project\fR=\fIKMS_PROJECT\fR The Google Cloud project for the key. To set the \f5kms\-project\fR attribute: .RS 2m .IP "\(em" 2m provide the argument \f5\-\-kms\-key\fR on the command line with a fully specified name; .IP "\(em" 2m provide the argument \f5\-\-kms\-project\fR on the command line; .IP "\(em" 2m set the property \f5core/project\fR. .RE .sp .RE .sp .SH "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 \fB$ gcloud help\fR for details. .SH "NOTES" These variants are also available: .RS 2m $ gcloud alpha alloydb backups create .RE .RS 2m $ gcloud beta alloydb backups create .RE