Red Hat Openshift Virtualization

Storware Backup & Recovery supports backup for OpenShift using OADP operator. Metadata of Virtual Machines is exported using OADP operator, volume data is exported using side pod using custom OpenShift Virtualization Plugin docker image. The backup supports both full and incremental types. Incremental backup does not require previous snapshots to remain in OpenShift.

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

Log in to the web interface and add a new OpenShift Hypervisor Manager:

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

  • Username - login of a user with the 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.

Using own image registry for OpenShift Virtualization Plugin

Storware Backup & Recovery use quay.io as default image registry for OpenShift Virtualization Plugin docker image. You can use your own registry to store the plugin image.

  1. Download OpenShift Virtualization Plugin from Storware repository.

  2. Upload it to your image registry host.

  3. Import image to your registry. Example:

  4. Edit /opt/vprotect/node.properties file and change value for openshift.virtualization.sidepod.image parameter. Example:

  5. Restart vprotect-node service.

Limitations

  • For a successful backup, Virtual Machine should have an app label assigned appropriately.

  • Hot-plugged disks are not supported.

  • Backup of disks: CDROM and LUN is not supported.

  • Storage class used for disk should support snapshots.

Supported features

Supported backup strategies: Helper pod

Helper pod

Minimal version

4.10

The last snapshot is kept on the system for incremental backups

Yes

Access to OS required

No

Proxy VM required

No

Full backup

Supported

Incremental backup

Not supportd

Restore

Supported

File-level restore

Not supported

Volume exclusion

Supported

Quiesced snapshots

Supported **

Snapshots management

Not supported

Pre/post command execution

Supported ***

Access to VM disk backup over iSCSI

Not supported

Name-based policy assignment

Supported

Tag-based policy assignment

Supported

Power-on after restore

Supported

StatfuSet

Supported

* When using Ceph RBD as Persistent Volume

** Deployment pause

*** Only 'post'

Network requirements

Connection URL: https://API_HOST:6443

Source
Destination
Ports
Description

Node

API IP/FQDN

6443/tcp

API access

Openshift Workers

Node

9000/tcp

S3 connection for metadata transfer

Node

Plugin helper pod (via route)

30000-32767/tcp

data transfer

Last updated