Skip to content

Commit 442f21d

Browse files
committedNov 20, 2020
[#174847306] back up whenever it is an action: TAS4K8s: New Velero-based Backup and Restore topic
1 parent 330f5af commit 442f21d

5 files changed

+10
-10
lines changed
 

‎bandr-backup-auto.html.md.erb

+2-2
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@ To back up <%= vars.app_runtime_short %> manually, see
1515

1616
## <a id='overview'></a> Overview
1717

18-
To backup <%= vars.app_runtime_short %> using automation:
18+
To back up <%= vars.app_runtime_short %> using automation:
1919

2020
1. [Create and Configure a Service Account for Backing Up](#backup-service-account)
2121
1. [Automate Your Velero Backup](#backup-create-script)
22-
1. [Review the Automates Velero Backup](#backup-review-automated)
22+
1. [Review the Automated Velero Backup](#backup-review-automated)
2323

2424
## <a id='prerequisites'></a> Prerequisites
2525

‎bandr-backup-manual.html.md.erb

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ See [Configuring Back Up and Restore for <%= vars.app_runtime_short %>](bandr-co
3232

3333
To back up <%= vars.app_runtime_short %> Tanzu Postgres Instances:
3434

35-
1. Start a velero backup:
35+
1. Start a Velero back up:
3636

3737
```
3838
velero create backup BACKUP-NAME \

‎bandr-configuration.html.md.erb

+4-4
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This topic provides an overview of how to configure back up and restore for
1414

1515
After installing <%= vars.app_runtime_short %>,
1616
install and configure Velero in your environment
17-
to enable <%= vars.app_runtime_short %> backup and restore
17+
to enable <%= vars.app_runtime_short %> back up and restore
1818
functions.
1919
See [Install and Configure Velero and Back Up Components]
2020
(#setup-backup-comp) below.
@@ -25,7 +25,7 @@ The following are required for <%= vars.app_runtime_short %> back up and restore
2525

2626
### <a id='prerequisites-general'></a> General Prerequisites
2727

28-
The following are required before configuring backup and restore for <%= vars.app_runtime_short %>:
28+
The following are required before configuring back up and restore for <%= vars.app_runtime_short %>:
2929

3030
* A <%= vars.app_runtime_short %> installation configured to use
3131
an external Tanzu Postgres Pod for the CCDB and UAA databases.
@@ -43,7 +43,7 @@ For more information, see [Supported Kubernetes Distributions]
4343

4444
The following are additional requirements for configuring back up and restore for <%= vars.app_runtime_short %> on vSphere:
4545

46-
* The vSphere backup and restore user account must meet additional requirements:
46+
* The vSphere back up and restore user account must meet additional requirements:
4747
* vSphere CSI driver user requirements.
4848
For more information on the vSphere CSI Driver requirements, see [vSphere Roles and Privileges]
4949
(https://vsphere-csi-driver.sigs.k8s.io/driver-deployment/prerequisites.html#roles_and_privileges)
@@ -69,7 +69,7 @@ in _Velero Plugin for vSphere_ in GitHub.
6969
Velero and an Iaas specific Velero plugin must be installed to back up and restore <%= vars.app_runtime_short %>.
7070

7171
The Velero plugin requires specific IaaS permissions to enable
72-
disk snapshotting, storage bucket read/write permissions and other backup and restore features.
72+
disk snapshotting, storage bucket read/write permissions and other back up and restore features.
7373

7474
To set up back up components:
7575

‎bandr-restore-manual.html.md.erb

+2-2
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ Cloud Foundry state from the backup, and then compare it to the live, restored s
198198
<p class="note"><strong>Note:</strong> The Cloud Foundry state from the backup is not a
199199
complete snapshot and should only be used as an aid to verifying the data.
200200
The validation follows the Cloud Foundry constructs of “users, orgs, spaces, and apps”
201-
to measure what data was in Cloud Foundry during a backup.
201+
to measure what data was in Cloud Foundry during a back up.
202202
</p>
203203

204204
After your restore has completed, follow the steps
@@ -238,7 +238,7 @@ To validate a completed restore:
238238
backup_1 Completed 2020-03-24 14:12:29 +0000 UTC 21d default &lt;none&gt;
239239
</pre>
240240

241-
1. To generate a snapshot of the Cloud Foundry state at the time of the backup:
241+
1. To generate a snapshot of the Cloud Foundry state at the time of the back up:
242242

243243
```
244244
tanzu-application-service/config/_ytt_lib/github.com/pivotal/cf-for-k8s-disaster-recovery/backup-metadata/bin/get-backup-metadata.sh BACKUP-NAME OUTPUT-FILENAME

‎installing-tas-for-kubernetes.html.md.erb

+1-1
Original file line numberDiff line numberDiff line change
@@ -381,7 +381,7 @@ stored in the `cf_admin_password` key in the `configuration-values/_generated-va
381381

382382
To validate Velero installation:
383383

384-
1. Use kubectl to confirm the backup and restore components have been installed successfully:
384+
1. Use kubectl to confirm the back up and restore components have been installed successfully:
385385

386386
```
387387
kubectl get pods -n cf-system -l app=cf-metadata

0 commit comments

Comments
 (0)
Please sign in to comment.