Red Hat OpenShift

Storware Backup & Recovery supports backup for OpenShift using OADP in backup process.

Prior to adding OpenShift as a new Hypervisor Manager, you must install the OADP operator, version 1.3 or higher, from the Operator Hub within the OpenShift cluster.

Adding Openshift Hypervisor Manager

URL - URL of the Openshift API e.g. api.your.cluster.local:6443
Username - login of user with cluster-admin role
OADP project name - project name where OADP Operator was installed (openshift-adp by default)
Storage class name for OADP - specify storage class that will be used for OADP setup, if this field is empty, default storage class will be used (optional)

The Openshift Nodes should appear in Storware Backup & Recovery after indexing the cluster.

Note:

Metadata is backed up using OADP operator. All of the OADP resources required during backups and restores will be automatically created, such as: DataProtectionApplication, BackupStorageLocation, VolumeSnapshotLocation
Persistent volumes are primarily backed up using volume snapshots providing crash consistency.
Whether specific persistent volume can be snapshotted is determined by searching for existing VolumeSnapshotClass with a driver corresponding to the storage class of the persistent volume. Which means that if the storage class of the persistent volume does not use CSI driver or the proper volume snapshot class is not already present, export of this volume will be performed without snapshotting mechanism. Block volumes can be exported only with volume snapshots.

Persistent volumes restore

There are two ways of restoring the volume content.

The user should deploy an automatic provisioner which will create persistent volumes dynamically. If Helm is installed, the setup is quick and easy https://github.com/helm/charts/tree/master/stable/nfs-server-provisioner.
The user should manually create a pool of volumes. Storware Backup & Recovery will pick one of the available volumes to restore the content.

Limitations

Only backups of Deployments, DeploymentConfigs and StatefulSets (persistent volumes and metadata) are currently supported.
If Storage Class used by volume do not support snapshots, all deployment pods will be paused during the backup operation - this is required to achieve consistent backup data.
For a successful backup, Deployment/DeploymentConfig/StatefulSet should have an app label assigned appropriately.

PreviousKubernetes NextProxmox VE

Last updated 2 months ago

Adding Openshift Hypervisor Manager

URL - URL of the Openshift API e.g. api.your.cluster.local:6443

Username - login of user with cluster-admin role

OADP project name - project name where OADP Operator was installed (openshift-adp by default)

Storage class name for OADP - specify storage class that will be used for OADP setup, if this field is empty, default storage class will be used (optional)

The Openshift Nodes should appear in Storware Backup & Recovery after indexing the cluster.

Note:

Metadata is backed up using OADP operator. All of the OADP resources required during backups and restores will be automatically created, such as: DataProtectionApplication, BackupStorageLocation, VolumeSnapshotLocation
Persistent volumes are primarily backed up using volume snapshots providing crash consistency.
Whether specific persistent volume can be snapshotted is determined by searching for existing VolumeSnapshotClass with a driver corresponding to the storage class of the persistent volume. Which means that if the storage class of the persistent volume does not use CSI driver or the proper volume snapshot class is not already present, export of this volume will be performed without snapshotting mechanism. Block volumes can be exported only with volume snapshots.

Persistent volumes restore

There are two ways of restoring the volume content.

The user should deploy an automatic provisioner which will create persistent volumes dynamically. If Helm is installed, the setup is quick and easy https://github.com/helm/charts/tree/master/stable/nfs-server-provisioner.

The user should manually create a pool of volumes. Storware Backup & Recovery will pick one of the available volumes to restore the content.

Limitations

Only backups of Deployments, DeploymentConfigs and StatefulSets (persistent volumes and metadata) are currently supported.

If Storage Class used by volume do not support snapshots, all deployment pods will be paused during the backup operation - this is required to achieve consistent backup data.

For a successful backup, Deployment/DeploymentConfig/StatefulSet should have an app label assigned appropriately.