-
Notifications
You must be signed in to change notification settings - Fork 72
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
adding data-protection deploy guide 2.0 (#189)
* adding data-protection deploy guide 2.0 Signed-off-by: Manish Jha <er.manish.jha@gmail.com> * adding data protection deploy guide incorporating ix team review Signed-off-by: Manish Jha <er.manish.jha@gmail.com>
- Loading branch information
1 parent
2dd8dbe
commit 74d696a
Showing
13 changed files
with
97 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,97 @@ | ||
# Data Protection | ||
|
||
Through Tanzu Mission Control, you can run backup and restore operations to protect your Kubernetes data. | ||
|
||
Before you enable Data Protection on a Workload cluster, please ensure you have met the following prerequisites | ||
|
||
- You have an active Tanzu Mission Control subscription. | ||
|
||
- The workload cluster which you want to protect is registered or attached in the Tanzu Mission Control portal. | ||
|
||
- You have created a credential for Data Protection as per instructions provided in the Tanzu Mission Control [documentation](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-4F349EE4-9C64-4243-84FF-D287F497A3D0.html) | ||
|
||
- You have created a Target Location for Data Protection as per instructions provided in the Tanzu Mission Control [documentation](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-using/GUID-867683CE-8AF0-4DC7-9121-81AD507EDB3B.html) | ||
|
||
For more information about protecting the data resources in your Kubernetes clusters, see Data Protection in [VMware Tanzu Mission Control Concepts](https://docs.vmware.com/en/VMware-Tanzu-Mission-Control/services/tanzumc-concepts/GUID-C16557BC-EB1B-4414-8E63-28AD92E0CAE5.html) | ||
|
||
**Enable Data Protection on Workload cluster** | ||
|
||
To enable Data Protection on a Workload cluster, locate the cluster in the Tanzu Mission Control portal and click on the Overview tab. Under Data protection, click on the Enable Data Protection option. | ||
|
||
![](img/tko-data-protection/tko-dp01.png) | ||
|
||
Click on the Enable button in the confirmation dialog page. | ||
|
||
![](img/tko-data-protection/tko-dp02.png) | ||
|
||
It takes roughly 5-10 minutes to enable data protection on a Kubernetes cluster. Tanzu Mission Control creates a namespace named Velero and installs Velero related Kubernetes objects in the workload cluster. | ||
|
||
<!-- /* cSpell:disable */ --> | ||
``` | ||
root@arcas [ ~ ]# kubectl get all -n velero | ||
NAME READY STATUS RESTARTS AGE | ||
pod/restic-nfbpl 1/1 Running 0 44s | ||
pod/restic-q57nk 1/1 Running 0 44s | ||
pod/restic-sj954 1/1 Running 0 44s | ||
pod/velero-57cdf5f99f-7fn4b 1/1 Running 0 71s | ||
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE | ||
daemonset.apps/restic 3 3 3 3 3 <none> 45s | ||
NAME READY UP-TO-DATE AVAILABLE AGE | ||
deployment.apps/velero 1/1 1 1 71s | ||
NAME DESIRED CURRENT READY AGE | ||
replicaset.apps/velero-57cdf5f99f 1 1 1 72s | ||
``` | ||
<!-- /* cSpell:enable */ --> | ||
|
||
**Configure Backup** | ||
|
||
After enabling data protection, click on the Create Backup option to configure backup for the workload cluster. | ||
|
||
![](img/tko-data-protection/tko-dp03.png) | ||
|
||
TMC Data Protection allows you to create backups of the following types: | ||
|
||
- All resources in a cluster. | ||
- Selected namespaces in a cluster. | ||
- Specific resources in a cluster identified by a given label. | ||
|
||
![](img/tko-data-protection/tko-dp04.png) | ||
|
||
Select the target location where the backup will be stored. | ||
|
||
![](img/tko-data-protection/tko-dp05.png) | ||
|
||
Configure the backup schedule and hit Next. | ||
|
||
![](img/tko-data-protection/tko-dp06.png) | ||
|
||
Specify the backup retention period and hit Next. | ||
|
||
![](img/tko-data-protection/tko-dp07.png) | ||
|
||
Specify a name for the backup schedule and click on Create button. | ||
|
||
![](img/tko-data-protection/tko-dp08.png) | ||
|
||
Backup configuration might take some time depending on the Kubernetes objects that you have provisioned in the workload cluster. When the backup is configured for the first time, Tanzu Mission Control takes a backup immediately. After that backups are taken as per the backup schedule configured. | ||
|
||
![](img/tko-data-protection/tko-dp09.png) | ||
|
||
**Restore Backup** | ||
|
||
To restore the Kubernetes data from the backup, select the backup image and click on the Restore button. | ||
|
||
![](img/tko-data-protection/tko-dp10.png) | ||
|
||
Select the resources that you want to restore. | ||
|
||
![](img/tko-data-protection/tko-dp11.png) | ||
|
||
Specify a name for the restore task and click on the Restore button. | ||
|
||
![](img/tko-data-protection/tko-dp12.png) | ||
|
||
If you have backed up persistent volumes, the restore process may take some time. The backup is restored in the same cluster that it was retrieved from. |