Backups for OpenShift


The OpenShift feature is deprecated. For similar functionality, use Kubernetes.

For comprehensive information about deprecated features, see End-of-Life, Deprecated and Extended Support - Features.

Commvault backs up OpenShift applications that are included in a VM group for an OpenShift hypervisor.

You can perform backups automatically based on the configuration for a hypervisor or VM group, or manually for a VM group or a specific application.

The first backup of an application is always a full backup. By default, all subsequent backups are incremental, capturing any changes to application data since the last backup.

You can recover application data, even when the most recent backup was incremental.

Backups run based on the following options:

  • Initial full backup: When you use Guided setup to set up the Virtualization solution, use the Back up now option to perform a backup for the default VM group.

  • Scheduled incremental backups: The server backup plan that is assigned to a VM group includes a schedule for ongoing incremental backups. Those backups are performed automatically based on the schedule, without requiring any user action.

  • Manual backups: You can perform on-demand backups for a VM group or for a specific application.

If backups cannot start immediately, the backup jobs are queued.

What Is Backed Up

  • YAML configuration for each application (container specification or manifest)

  • Applications that have persistent volume claims (PVCs)

  • Persistent volumes, secrets, and configuration maps that are associated with an application

What Is Not Backed Up

  • Containers that are running


    For restores, Commvault re-instantiates applications from the original container platform selection, restores volumes, and reattaches volumes to containers. For this reason, Commvault does not back up or restore running containers.

  • Applications that do not have PVCs

  • Services, routes, and provisioned services that are associated with an application

  • Custom Resource Definitions (CRDs)

  • Container images

  • Image registry

  • etcd cluster configuration and state (per node)

  • API objects