This ticket is related to running datamover aka datamovement cases on OADP upstream.

This ticket aims to provide missing information that will close OADP-5267 and verify that ephermal storage issues no longer reproduces on the latest upstream of OADP.

This ticket requires:

• installing OADP upstream latest with 3.5T bucket and re-running an existing case of datamover 500G, and running two additional cases for 1.5T and 3T for datamover.

In addition to verifying that ephermal storage issue does not reproduce, please collect the upload rate to the bucket for backup and download rate from the bucket for (restore) by collecting the network transfer rate from the observability graphs.

Cases to run:

• re-running existing 4.1.2  backup-vbd-datagen-single-ns-1pod-500gb-cephrbd
• creating new case for 1.5T
  use 2.1.6.9 backup-kopia-pvc-util-2-1-6-9-cephrbd-swift-1.5t as an example and make a new case  4.1.6.9 called backup-vbd-datagen-single-ns-1pod-1500gb-cephrbd please also create the relevant restore
• use 2.2.9.9 backup-kopia-pvc-util-2-2-9-9-cephrbd-swift-3t as an example and make a new case  4.2.9.9  called  backup-vbd-datagen-single-ns-1pod-3000gb-cephrbd please also create the relevant case for restore

You should run:

1. 500G
   4.1.2 (backup x twice)
   4.1.2 (restore x twice)
   clean
2. 1.5 T
   4.1.6.9 (backup x twice)
   4.1.6.9 (restore x twice)
   clean
3. 3.0 T
   4.2.9.9 (backup x twice)
   4.2.9.9 (restore x twice)

Please create a sumary table which shows
amount of data (duration) and upload / download rate to minio namespace