OADP-1668: Volumesnapshot related CR’s namely Volumesnapshot and VolumeSnapshotcontent are not being included by the OADP Version of Velero server in the backup bundle

[vjaincatalogic]

Only developers will use GitHub issues for development purposes

agree

[vjaincatalogic]

I attach the backup bundle here:
test-backup-8-csi-volumesnapshotclasses.json.gz
test-backup-8-csi-volumesnapshotcontents.json.gz
test-backup-8-csi-volumesnapshots.json.gz
test-backup-8-logs.gz
test-backup-8-podvolumebackups.json.gz
test-backup-8-resource-list.json.gz
test-backup-8-volumesnapshots.json.gz

[kaovilai]

Thanks for your report. tracking in JIRA

[kaovilai]

@vjaincatalogic is this from building from source? or are you using official releases?

[vjaincatalogic]

@kaovilai , Yes this is from official release. I'm not building from source. I used the official oadp-operator from market place.

[kaovilai]

Can you verify version?

[vjaincatalogic]

oadp version is v1.1.3

[shubham-pampattiwar]

@vjaincatalogic I do see volumesnapshotcontent being backed up from the bundle content you provided. Could you provide more details on:

• backup CR used
• DPA CR used + DPA CR status
• velero logs
• volume-snapshot-mover logs
• VolumeSnapshotBackup CR and its status (This would in application ns)

[vjaincatalogic]

Hi @shubham-pampattiwar, I will provide you all these details but currently the cluster was deleted and it will take me some time to get back to you.

[vjaincatalogic]

backup Bundle:
backup_bundle.tar.gz

I provide you the first three, backup CR used, DPA CR used + DPA CR status, velero logs
requested.tar.gz

volume-snapshot-mover logs and VolumeSnapshotBackup CR and its status , I'm not able to find as I had not used Volume Snapshot Mover, IS it the reason, I'm not able to see the volumesnapshot in backup bundle in my BSL?

[shubham-pampattiwar]

@vjaincatalogic Which type of OADP backup are you trying to take here ? Native CSI backup or Datamover CSI backup ?

[draghuram]

@shubham-pampattiwar, this was CSI backup. By "Datamover" CSI backup, do you mean Restic or Kopia backup?

[kaovilai]

"Datamover" CSI backup, do you mean Restic or Kopia backup?

We means our own implementation of "Data Mover" in OADP v1.1 which takes CSI snapshots, and make a restic copy of data from snapshot to S3. This is an OADP specific capability which upstream will have with vmware-tanzu/velero#5968

See doc at
https://access.redhat.com/documentation/en-us/openshift_container_platform/4.10/html-single/backup_and_restore/index#oadp-using-data-mover-for-csi-snapshots_backing-up-applications

TL;DR: we do not mean restic or kopia.

[kaovilai]

If you do not have enable: true here then you did not use our Data Mover.

apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
metadata:
  name: velero-sample
  namespace: openshift-adp
spec:
  features:
    dataMover:
      enable: true

[vjaincatalogic]

Hi @shubham-pampattiwar / @kaovilai , SO I understood my DataProtectionApplication is not having this dataMover enabled, but is it required for CSI VolumeSnapShots and without OADP dataMover, we will not see the VolumeSnapShot data in BackupStorageLocation?

[kaovilai]

Should not be required.

[vjaincatalogic]

In that case, I'm just confirming from the OADP,
OADP team got all the information required to investigate on this issue and OADP team is still investigating?

[kaovilai]

At this time we are not requesting any more information. This issue is still open to investigation.

[vjaincatalogic]

Hi Team, Any Updates on this issue?

[weshayutin]

We had to push it out further. Tracked in OADP-1669

[vjaincatalogic]

Hi, I retried the complete flow with OADP version - 1.1.4 as well but still the same issue, I see that volumesnapshot is null,
test-backup-11-csi-volumesnapshotclasses.json.gz
test-backup-11-csi-volumesnapshotcontents.json.gz
test-backup-11-csi-volumesnapshots.json.gz
test-backup-11-logs.gz
test-backup-11-podvolumebackups.json.gz
test-backup-11-resource-list.json.gz
test-backup-11-volumesnapshots.json.gz
test-backup-11.tar.gz
velero-backup.json.gz

Dataprotectionapp manifest:
dataprotection.yaml.gz
velero.log.gz
backup.yaml.gz

[kaovilai]

Still looking into it. Thanks for the details!

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kaovilai]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[kaovilai]

/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.