The backup configuration and schedule is defined via the MySQLCluster resource's backups field. The schedule is specified in cron format and determines how frequently TungstenBackup resources are created and thus, how frequently backups are taken. If retention is specified, then successful TungstenBackup resources are deleted when count exceeds the value in keep.

An example YAML file is available in the examples directry called tungsten_v1alpha1_mysqlcluster_with_backup.yaml and the specific backup properties are shown below:

...
spec:
  configuration:
    customPasswordSecret: tungsten-passwords-sample-secret
  backup:
    configurationRef:
      name: tungstenbackupconfiguration-sample
    schedule: "* * * * *"
    keep: 5
...

The name refers to the name given in the BackupConfiguration

The lifecycle of a backup operation can be tracked through the TungstenBackup resource's status field. The possible states are Pending, Processing, Succeeded, and Failed.