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.

Sign up for GitHub

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

Better wording for Velero chapter #873

Merged
merged 9 commits into from
Jun 22, 2020
Merged

Better wording for Velero chapter #873

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
f2d3d3d
Decrease sub-chapter usage
Jun 9, 2020
068740d
Add full stop
Jun 9, 2020
3f40a4e
Consolidate velero deployment into one doc
Jun 9, 2020
a351b1f
Enhance velero usercase doc
Jun 9, 2020
5f4618e
Decrease sub-chapter usage
Jun 9, 2020
9e1614b
Language and formatting edits.
nkoranova Jun 17, 2020
ddaf98a
Merge remote-tracking branch 'upstream/maintenance/CaaS4' into issue-865
Jun 18, 2020
5d50883
Fix one more typo.
nkoranova Jun 22, 2020
b2f5599
Merge branch 'issue-865' of https://github.com/jenting/doc-caasp into…
nkoranova Jun 22, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add full stop 
Signed-off-by: JenTing Hsiao <jenting.hsiao@suse.com>
  • Loading branch information
JenTing Hsiao committed Jun 9, 2020
commit 068740d550010a091ca0c52500618496d561ba1c
16 changes: 8 additions & 8 deletions adoc/admin-velero-disaster-recovery.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,22 +9,22 @@ data migration and data protection by backing up {kube} cluster resources and pe

The major functions include:

* Backup {kube} resources and persistent volumes for supported storage providers
* Restore {kube} resources and persistent volumes for supported storage providers
* Backup {kube} resources and persistent volumes for supported storage providers.
* Restore {kube} resources and persistent volumes for supported storage providers.
* When backing up persistent volumes w/o supported storage provider, Velero leverages link:https://github.com/restic/restic[restic] as an agnostic solution to back up this sort of persistent volumes under some known limitations.

User can leverage these fundamental functions to achieve user stories:

* Backup whole {kube} cluster resources then restore if any {kube} resources loss
* Backup selected {kube} resources then restore if the selected {kube} resources loss
* Backup selected {kube} resources and persistent volumes then restore if the {kube} selected {kube} resources loss or data loss
* Backup whole {kube} cluster resources then restore if any {kube} resources loss.
* Backup selected {kube} resources then restore if the selected {kube} resources loss.
* Backup selected {kube} resources and persistent volumes then restore if the {kube} selected {kube} resources loss or data loss.
* Migrate the backup to other clusters for any purpose like migrates production cluster to develop cluster for testing.

Velero consists of below components:

* A Velero server that runs on your {kube} cluster
* A `restic` deployed on each worker nodes that run on your {kube} cluster (optional)
* A command-line client that runs locally
* A Velero server that runs on your {kube} cluster.
* A `restic` deployed on each worker nodes that run on your {kube} cluster (optional).
* A command-line client that runs locally.

== Limitations

Expand Down