Prior to the release of Velero 1.12, OADP 1.1 and 1.2 integrated an OADP-specific Data Mover based on Volsync into OADP and the OADP-installed Velero version. This took the form of some modifications to Velero core and the Velero CSI plugins, a new VSM plugin, and a separate VSM controller that used Volsync to store Volume data in the BackupStorageLocation. In addition to this, DPA and installation support for the OADP Data Mover was included in the OADP operator.

In order to integrate VBDM into OADP, all of the above legacy OADP Data Mover parts will be removed from the OADP operator, the OADP Velero build, and the OADP build of the Velero Plugin for CSI.

Goals

• Enable Velero Built-in Data Mover (VBDM) in OADP.

• Remove support for the legacy Volsync-based OADP Data Mover.  

VolumeMode Block Support

Goals

• Create components and workflows for Velero to move data based on volume snapshots

• Create components and workflows for Velero built-in data mover

• Create the mechanism to support data mover plugins from third parties

• Implement CSI snapshot data movement on file system level

• Support different data accesses, i.e., file system level and block level

• Support different snapshot types, i.e., CSI snapshot, volume snapshot API from storage vendors

• Support different snapshot accesses, i.e., through PV generated from snapshots, and through direct access API from storage vendors

• Reuse the existing Velero generic data path as creatd in Unified Repository design

OpenShift Virtualization defaults to block mode volumes. 

These block mode volumes can now be supported by OADP.  

Performance enhancements and improvements will be considered in future releases. 

Requires a privileged node-agent

Performance

OADP-1.2.x allows a user to configure maxConcurrentBackupVolumes and maxConcurrentRestoreVolumes. 

The DataMover feature in OADP-1.3.x allows one volume to be copied off the cluster per worker node.   

Future releases of OADP-1.3.x will allow a user to configure more than one volume per worker node.

CPU and Memory Notes:

DataMover with kopia can be very performance but CPU and memory intensive.  

When the appropriate resources are provided data movement can be more than twice as fast as OADP-1.2.  Performance testing is on-going.

Test plan

https://polarion.engineering.redhat.com/polarion/#/project/OADP/workitem?id=OADP-415