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

Provide more details in documentations on how restore works #4150

Closed
pradeepkchaturvedi opened this issue Sep 16, 2021 · 5 comments · Fixed by #4928
Closed

Provide more details in documentations on how restore works #4150

pradeepkchaturvedi opened this issue Sep 16, 2021 · 5 comments · Fixed by #4928
Assignees
Milestone

Comments

@pradeepkchaturvedi
Copy link

Velero documentation does not provide enough details in how restore works https://velero.io/docs/v1.6/how-velero-works/#restores

  1. There can be more details on what happens when during restore operation there are resource objects exists in cluster and backup both. Would restore copy objects from backup, would restore skip, would restore merge the object
  2. Would Velero restores cluster to backed up state i.e would restore delete objects create after backup
  3. If there are objects in cluster with missing annotations/labels and backup has the same objects, would Velero update the cluster resource objects and add missing annotation/labels. does Velero merges changes from backup to cluster objects. If yes, how does it resolves conflicts
  4. Does Velero checks the API version for the object and does it affects restore operation
  5. What happens if during restore required storage is missing on the target cluster, how does PVs restore affects
  6. Does Velero backup and restore objects not in namespace
@GeiserX
Copy link

GeiserX commented Jan 28, 2022

AWS added some documentation about the restore process already, ahead of Velero itself: https://aws.amazon.com/blogs/containers/backup-and-restore-your-amazon-eks-cluster-resources-using-velero/

@eleanor-millman eleanor-millman added this to the 1.9.0 milestone Feb 22, 2022
@a-mccarthy
Copy link
Contributor

@Lyndon-Li hi! just checking on this, do you have a rough idea on when you will have time to work on it? Is there anything i can help with? thanks!!

@Lyndon-Li
Copy link
Contributor

@a-mccarthy I will start this work next week. I am not sure if we have a template for this kind of document, if so, please help to share it. If not, I will try to create the document by following my own idea first then I will send it to you for your review. Thanks.

@a-mccarthy
Copy link
Contributor

@Lyndon-Li sorry for my delayed response on this, we dont have a template at the moment.

@Lyndon-Li
Copy link
Contributor

@a-mccarthy It is ok. The draft doc has been completed and shared.
Please help to review it and compose the official doc based on it. For anything more is required or any question, please just comment on the doc.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants