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

Incorrect behavior when backing up two similar volumes #81

Closed
fleeto opened this issue Jan 4, 2020 · 2 comments
Closed

Incorrect behavior when backing up two similar volumes #81

fleeto opened this issue Jan 4, 2020 · 2 comments

Comments

@fleeto
Copy link
Contributor

fleeto commented Jan 4, 2020

I have two PVCs ("data1" and "data2"), I was trying to make a copy for them with k8up, each of them has only one text file named "data.txt" in it.

I'd restore the snapshot into S3, and I got only one file in it
backup-default-data2-2020-01-04T16_27_03Z.tar.gz
:

data
└── data2
    └── data.txt
@Kidswiss
Copy link
Contributor

Kidswiss commented Jan 6, 2020

Hi @fleeto

A restore will only restore the very last snapshot in the backup repository. So it's correct that only one PVC was restored. If you don't pass a snapshot ID it will restore the very last snapshot it can find in the repository. Each PVC will create its own snapshot, so this is expected behaviour.

Currently there are two ways to get the list of snapshots:

  • use restic itself with the right variables to the repository (https://restic.readthedocs.io/en/latest/)
  • using the webhook endpoints, which will require a custom webhook receiver to interpret the output. We're planning on delivering this bundled with k8up in the future.

@fleeto
Copy link
Contributor Author

fleeto commented Jan 9, 2020

Thank u

@fleeto fleeto closed this as completed Jan 9, 2020
cimnine added a commit that referenced this issue Aug 5, 2021
Make parsing restic output resilient to non-json output
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants