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

Back up non-cloud persistent volumes #19

Closed
kstewart opened this issue Aug 9, 2017 · 7 comments
Closed

Back up non-cloud persistent volumes #19

kstewart opened this issue Aug 9, 2017 · 7 comments
Assignees
Milestone

Comments

@kstewart
Copy link

kstewart commented Aug 9, 2017

It would be awesome if we could back up any type of volume, not just aws ebs, gce pd, and azure managed disks. Something like https://github.com/appscode/stash might be interesting to leverage or partner

@ncdc ncdc added this to the v0.5.0 milestone Sep 5, 2017
@ncdc ncdc removed this from the v0.5.0 milestone Oct 12, 2017
@ncdc
Copy link
Contributor

ncdc commented Mar 14, 2018

Question from @akgunjal in #377 (comment):

Ideally we would want to take backup of our data from the containers onto the object storage. ... But does this feature also allow to restore the data from object storage back inside the container to the directory of user's choice?

@skriss any comments?

@ncdc ncdc added this to the v0.8.0 milestone Mar 14, 2018
@skriss
Copy link
Contributor

skriss commented Mar 14, 2018

@akgunjal the current thinking is that you'd be able to back up the contents of any volume mounted into the container, and restore it to the same mountPath.

Are you asking specifically about being able to restore into a different directory? Would love to hear more about that use case if so, to see if it makes sense to include in the design.

@akgunjal
Copy link

@skriss : The use-case is we take backup of any directory from inside the container onto object storage. Then restore this onto any other container in any path. This can be some other mount path or even local directory in the container. Basically its copy of data from backup location on the directory chosen by user.

@ncdc
Copy link
Contributor

ncdc commented Mar 14, 2018

@akgunjal would you likely take a backup now, and then after several days/months pass, potentially do a restore? Or is this more like an immediate copy?

@sandaymin123
Copy link

@ncdc Please see products like http://duplicity.nongnu.org/ that allow any set of files or directories to be backed up to object storage. Ideally, it would be nice to have this flexiblity including encrypted backups that are either full and incremental

@ncdc
Copy link
Contributor

ncdc commented Mar 14, 2018

@sandaymin123 thanks, we're planning on using something similar - restic. This will allow you to back up any directories to whatever restic supports (which is mostly object storage).

@akgunjal
Copy link

@ncdc : The restore may be done after several days/months and may not be immediate restore after taking backup.

@skriss skriss modified the milestones: v0.8.0, v0.9.0 Apr 19, 2018
@skriss skriss mentioned this issue May 18, 2018
4 tasks
@ncdc ncdc closed this as completed in #508 Jun 6, 2018
dymurray pushed a commit to dymurray/velero that referenced this issue Apr 16, 2019
…lidation-exception

Revert "Fix backup location validation to coexist with registry dir."
alromeros pushed a commit to alromeros/velero that referenced this issue Oct 25, 2024
Make sure that backup and restore has unique name for each test,
and that all backups are removed after tests.

Signed-off-by: Bartosz Rybacki <[email protected]>
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

5 participants