- Resource: BackupSchedule
- BackupScheduleSpec
- CrontabSpec
- CreateBackupEncryptionConfig
- EncryptionType
- FullBackupSpec
- IncrementalBackupSpec
- Methods
Resource: BackupSchedule
BackupSchedule expresses the automated backup creation specification for a Spanner database. Next ID: 10
JSON representation |
---|
{ "name": string, "spec": { object ( |
Fields | |
---|---|
name |
Identifier. Output only for the [backupSchedules.create][DatabaseAdmin.CreateBackupSchededule] operation. Required for the |
spec |
Optional. The schedule specification based on which the backup creations are triggered. |
retention |
Optional. The retention duration of a backup that must be at least 6 hours and at most 366 days. The backup is eligible to be automatically deleted once the retention period has elapsed. A duration in seconds with up to nine fractional digits, ending with ' |
encryption |
Optional. The encryption configuration that will be used to encrypt the backup. If this field is not specified, the backup will use the same encryption configuration as the database. |
update |
Output only. The timestamp at which the schedule was last updated. If the schedule has never been updated, this field contains the timestamp when the schedule was first created. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
Union field backup_type_spec . Required. Backup type spec determines the type of backup that is created by the backup schedule. Currently, only full backups are supported. backup_type_spec can be only one of the following: |
|
full |
The schedule creates only full backups. |
incremental |
The schedule creates incremental backup chains. |
BackupScheduleSpec
Defines specifications of the backup schedule.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field schedule_spec . Required. schedule_spec can be only one of the following: |
|
cron |
Cron style schedule specification. |
CrontabSpec
CrontabSpec can be used to specify the version time and frequency at which the backup should be created.
JSON representation |
---|
{ "text": string, "timeZone": string, "creationWindow": string } |
Fields | |
---|---|
text |
Required. Textual representation of the crontab. User can customize the backup frequency and the backup version time using the cron expression. The version time must be in UTC timzeone. The backup will contain an externally consistent copy of the database at the version time. Allowed frequencies are 12 hour, 1 day, 1 week and 1 month. Examples of valid cron specifications: * |
time |
Output only. The time zone of the times in |
creation |
Output only. Schedule backups will contain an externally consistent copy of the database at the version time specified in A duration in seconds with up to nine fractional digits, ending with ' |
CreateBackupEncryptionConfig
Encryption configuration for the backup to create.
JSON representation |
---|
{
"encryptionType": enum ( |
Fields | |
---|---|
encryption |
Required. The encryption type of the backup. |
kms |
Optional. The Cloud KMS key that will be used to protect the backup. This field should be set only when |
kms |
Optional. Specifies the KMS configuration for the one or more keys used to protect the backup. Values are of the form The keys referenced by
|
EncryptionType
Encryption types for the backup.
Enums | |
---|---|
ENCRYPTION_TYPE_UNSPECIFIED |
Unspecified. Do not use. |
USE_DATABASE_ENCRYPTION |
Use the same encryption configuration as the database. This is the default option when encryptionConfig is empty. For example, if the database is using Customer_Managed_Encryption , the backup will be using the same Cloud KMS key as the database. |
GOOGLE_DEFAULT_ENCRYPTION |
Use Google default encryption. |
CUSTOMER_MANAGED_ENCRYPTION |
Use customer managed encryption. If specified, kmsKeyName must contain a valid Cloud KMS key. |
FullBackupSpec
This type has no fields.
The specification for full backups. A full backup stores the entire contents of the database at a given version time.
IncrementalBackupSpec
This type has no fields.
The specification for incremental backup chains. An incremental backup stores the delta of changes between a previous backup and the database contents at a given version time. An incremental backup chain consists of a full backup and zero or more successive incremental backups. The first backup created for an incremental backup chain is always a full backup.
Methods |
|
---|---|
|
Creates a new backup schedule. |
|
Deletes a backup schedule. |
|
Gets backup schedule for the input schedule name. |
|
Gets the access control policy for a database or backup resource. |
|
Lists all the backup schedules for the database. |
|
Updates a backup schedule. |
|
Sets the access control policy on a database or backup resource. |
|
Returns permissions that the caller has on the specified database or backup resource. |