Add note about non-destrutive restore #4885
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Abigail McCarthy <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #4885 +/- ##
==========================================
- Coverage 41.25% 41.20% -0.05%
==========================================
Files 204 204
Lines 18041 18041
==========================================
- Hits 7442 7434 -8
- Misses 10047 10054 +7
- Partials 552 553 +1
Continue to review full report at Codecov.
|
a-mccarthy
added
the
kind/changelog-not-required
reasonerjt
reviewed
May 18, 2022
| @@ -38,6 +38,8 @@ By default, backup storage locations are created in read-write mode. However, du | |||
|
|
|||
| You can optionally specify restore hooks to be executed during a restore or after resources are restored. For example, you might need to perform a custom database restore operation before the database application containers start. [More about restore hooks][11]. | |||
|
|
|||
| During a restore, Velero is non-destructive. That means that Velero will never overwrite a pre-existing resource which has the same name as a resource in the backup it is restoring. Similarly, if a persistent volume exists, Velero will not overwrite the data in it. This behavior is by design, so that you don't have to worry about accidentally overwriting your cluster's state when using Velero. | |||
There was a problem hiding this comment.
This is not exactly true for v1.9+
A contributor from redhat recently added an option so that some resources can be overwritten:
#4851 (comment)
There was a problem hiding this comment.
thanks for bringing this up, I'll close this PR and address this with the changes in PR #4928
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Abigail McCarthy [email protected]
Thank you for contributing to Velero!
Please add a summary of your change
Adds a note to the How Velero Works page about non-destructive nature of restores.
Also fixes some minor formatting issues on the restore reference page.
Does your change fix a particular issue?
Fixes ##4571
Please indicate you've done the following:
/kind changelog-not-requiredas a comment on this pull request.site/content/docs/main.