Backup

Enterprise

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For subscription inquiries, please reach out to sales@baculasystems.com.

The plugin can backup a number of OpenShift Resources including: Deployments, Pods, Services or Persistent Volume Claims, check chapter openshiftresources for a complete list.

The backup will create a single (.yaml) file for any OpenShift Resource which is saved. For PVC Data backup functionality the OpenShift Plugin generates a data archive as a single <pvcname>.tar archive file. The resources are organized inside the Bacula catalog to facilitate browsing and restore operations. In the Bacula catalog, OpenShift resources are represented as follows:

  • /@openshift/namespaces/<namespace>.yaml - Namespace definition

  • /@openshift/namespaces/<namespace>/<resource>/<name>.yaml - Resource definitions in the namespace

  • /@openshift/namespaces/<namespace>/persistentvolumeclaim/<pvcname>.tar - PVC Data backup in the selected namespace

  • /@openshift/persistentvolumes/<pvname>.yaml - Persistent Volume definition

  • /@openshift/storageclass/<scname>.yaml - Storage Class definition

All supported OpenShift Resources will be saved if no filter options are set. You may limit which resources are saved using filtering options described in chapter openshiftbackupparameters. By default, if no filter options are set, all supported OpenShift Resources will be saved. To see the OpenShift Resources that may be filtered, a listing mode is available. This mode is described in chapter openshiftresourcelisting.

Read more:

See also

Next articles:

Go back to: OpenShift: Operations.