Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snapshot data is different after restoring the zfs-localpv backup #207

Closed
w3aman opened this issue Sep 11, 2020 · 1 comment
Closed

Snapshot data is different after restoring the zfs-localpv backup #207

w3aman opened this issue Sep 11, 2020 · 1 comment
Labels
kind/documentation Improvements or additions to documentation
Milestone

Comments

@w3aman
Copy link
Contributor

w3aman commented Sep 11, 2020

What happened:

I provisioned the zfs-localpv and busybox application is consuming it. I dumped some data and after that i took the volume snapshot. So suppose i took the snapshot S1 of data D1.
Now more data is dumped say D2. Now volume is having D1+D2 data in total.
After that backup is created. So it should be consisiting of total data of D1+D2 and one volume snapshot S1 of D1 data.

When backup is restored in some different namespace, Application mount point have the total data and we have successfully restored the vol-snapshot S1 also in that namespace.
But when we try to clone that snapshot, my clone volume is having data total D1+D2 data but clone should be consisting of data on which snapshot was taken i.e. data D1. it should not have the data which was dumped after taking the snapshot.

Here looks like while taking the backup snapshot was backed up with whole data upto the backup start time, instead of only that data for which snapshot was created.

@pawanpraka1 pawanpraka1 added the kind/documentation Improvements or additions to documentation label Sep 11, 2020
@pawanpraka1 pawanpraka1 added this to the v1.0.0 milestone Sep 11, 2020
@pawanpraka1
Copy link
Contributor

pawanpraka1 commented Sep 11, 2020

it is a limitation here, we can do either these two things

  1. exclude the volumesnapshot during backup/restore
  2. if we are restoring the snapshot, it may not point to the same data as the source snapshot.

Velero does not know the point of time when snapshot was taken, so it can not create the sbpashot with the exact same data. We can exclude the volumesnaoshot while taking the backup

velero backup create my-backup --snapshot-volumes --include-namespaces=velero-ns --exclude-resources=volumesnapshots --volume-snapshot-locations=aws-cloud-default --storage-location=default

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants