Skip to content

Commit 0728e85

Browse files
committed
Initial Version.
1 parent ef65eea commit 0728e85

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

EKS/PV-Migrate-with-Trident-Protect/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ kubectl apply -f trident-application.yaml
205205
```
206206

207207
### Run Backup for Application
208-
Before you can migrate the data to a new store class you must back up the data first. You do that by first creating a backup configuration file named `trident-backup.yaml` with the following contents:
208+
Before you can migrate the data to a different store class you must back up the data first. You do that by first creating a backup configuration file named `trident-backup.yaml` with the following contents:
209209

210210
```markdown
211211
apiVersion: protect.trident.netapp.io/v1
@@ -242,7 +242,7 @@ kubectl get backup -n <APP NAMESPACE> <APP BACKUP NAME>
242242
- If status is `Failed` the error message will give you a clue as to what went wrong. If you need more information, try using `kubectl describe` instead of `kubectl get` to get more information.
243243

244244
## Perform the migration
245-
To restore the backup to a storage class, you first need to create a restore configuration file named `trident-restore-diff-sc.yaml` with the following contents:
245+
To restore the backup to a different storage class, you first need to create a restore configuration file named `trident-restore-diff-sc.yaml` with the following contents:
246246

247247
```markdown
248248
apiVersion: protect.trident.netapp.io/v1

0 commit comments

Comments
 (0)