Epic Goal

• The goal for this epic to track the work needed to bring data mover to GA. The primary piece of work to accomplish this is to get upstream velero changes merged such that the way we are currently handling asynchronous operations is an officially supported mechanism in upstream velero.

Why is this important?

• It will bring significant UX improvements to the data mover workflow when upstream velero has a native way to handle asynchronous operations such as data mover. Should hopefully improve performance and debuggability for all users.

Scenarios

1. User wants to take a backup with OADP 1.2 and expect it to be able to be restored in a future version.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Upstream Velero supports running asynchronous operations natively and we have integrated that into our fork.

Dependencies (internal and external)

1. Velero
2. Volsync

Open questions::

1. How do we properly lock OADP to specific volsync versions for releases in the future? With volysnc as a cluster scoped operator we can't use OLM for dependency management.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>. For QE- 1 - Regression tests, All the existing tests should pass for datamover, 2 - Parallel backup new test for async data mover, Check Phases. 3 - performance test cases

• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>