These intervals are specified by a Cron expression. The first backup is performed when the schedule is first created, and subsequent backups happen at the schedule’s specified interval. The schedule operation allows you to back up your data at recurring intervals. The odds of capturing inconsistent information are low, but it is possible. If Kubernetes objects are being created or edited at the time of backup, they might not be included in the backup. Note that cluster backups are not strictly atomic. Need to tell a database to flush its in-memory buffers to disk before taking a snapshot. You can optionally specify hooks to be executed during the backup. Uploads a tarball of copied Kubernetes objects into cloud object storage.Ĭalls the cloud provider API to make disk snapshots of persistent volumes, if specified. Velero is ideal for the disaster recovery use case, as well as for snapshotting your application state, prior to performing system operations on your cluster (e.g. You can back up or restore all objects in your cluster, or you can filter objects by type, namespace, and/or label. Velero also includes controllers that process the custom resources to perform backups, restores, and all related operations. Each Velero operation – on-demand backup, scheduled backup, restore – is a custom resource, defined with a KubernetesĬustom Resource Definition (CRD) and stored inĮtcd.

Drive snapshot 1.4