OADP-3736 Need to set data-mover-prepare-timeout parameter in DPA
Closed this issue · 8 comments
We are using the OADP built-in dataMover to backup our ODF file system.
The backup worked well for small amount of file system data. When the data becomes bigger, the backup failed after 30 minutes.
The dataupload failed with status
status:
message: timeout on preparing data upload
phase: Failed
progress: {}
We looked at https://velero.io/docs/main/csi-snapshot-data-movement/#customized-data-movers, and found
After the volume is created from the CSI snapshot, Velero built-in data mover waits for Kubernetes to provision the volume, this may take some time varying from storage providers, but if the provision cannot be finished in a given time, Velero built-in data mover will cancel this DataUpload CR. The timeout is configurable through a node-agent’s parameter data-mover-prepare-timeout, the default value is 30 minutes.
We are using DPA to backup. Here is the configuration of the DPA
configuration:
nodeAgent:
enable: true
uploaderType: restic
velero:
defaultPlugins:
- openshift
- csi
- aws
We are not able to setup the data-mover-prepare-timeout from with the DPA. It seems that it is not available in DPA CRD.
@libingwang123 Thanks for reporting the issue. Currently we do not have an option to set the data-mover-prepare-timeout via DPA CR. This is probably the first time we are seeing a user needing to customize this timeout, we will definitely add the task of enabling data-mover-prepare-timeout field via DPA in our Operator Development roadmap.
@shubham-pampattiwar Thanks for the quick response.
Is there an estimated deliver date for this feature in the new OADP version?
In the meanwhile, is there any way to work this around? E.g., once datauploader is up, is there any way to edit the nodeagent injecting this parameter? Thanks.
Is there any update on this issue.
Any ETA when this will be available part of the new OADP Release ?
Note: This FLAG is already available at Velero side, but there is no way to pass it at OADP end. Hence the OADP backup timesout after 30min. Today its kind of blocking for the OADP Users.
Per https://issues.redhat.com/browse/OADP-3736 this work is aligned to OADP 1.4 release.
Thanks @kaovilai. Is there a GA date on OADP 1.4?
Hi! We need this update too! Thanks