From c6d568ad1248154151999eab8a6df3092fbf65e9 Mon Sep 17 00:00:00 2001 From: Abigail McCarthy Date: Tue, 17 May 2022 23:02:28 -0400 Subject: [PATCH] Make updates from review Signed-off-by: Abigail McCarthy --- site/content/docs/main/migration-case.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/site/content/docs/main/migration-case.md b/site/content/docs/main/migration-case.md index 027083eab..afb3a3e2a 100644 --- a/site/content/docs/main/migration-case.md +++ b/site/content/docs/main/migration-case.md @@ -58,8 +58,8 @@ This scenario steps through the migration of resources from Cluster 1 to Cluster velero backup-location create bsl --provider aws --bucket velero-migration-demo --config region=us-east-2 --access-mode=ReadOnly ``` - Make sure to configure the `BackupStorageLocations` as read-only - by using the `--access-mode=ReadOnly` flag for `velero backup-location create`. See `velero backup-location –help` for more information about the available flags for this command. + Its recommended that you configure the `BackupStorageLocations` as read-only + by using the `--access-mode=ReadOnly` flag for `velero backup-location create`. This will make sure that the backup is not deleted from the object store by mistake during the restore. See `velero backup-location –help` for more information about the available flags for this command. ``` velero snapshot-location create vsl --provider aws --config region=us-east-2