From c59c52e6f684840b25e51f2fda76e32639e70566 Mon Sep 17 00:00:00 2001 From: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com> Date: Mon, 25 Jan 2021 11:52:27 -0500 Subject: [PATCH] Update docs to clarify backup location and relationship with other data (#3309) * Clarify backup location information in the docs * Update wording a bit Signed-off-by: Abigail McCarthy --- site/content/docs/main/locations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/docs/main/locations.md b/site/content/docs/main/locations.md index d1ac04151..41c070244 100644 --- a/site/content/docs/main/locations.md +++ b/site/content/docs/main/locations.md @@ -7,7 +7,7 @@ layout: docs Velero has two custom resources, `BackupStorageLocation` and `VolumeSnapshotLocation`, that are used to configure where Velero backups and their associated persistent volume snapshots are stored. -A `BackupStorageLocation` is defined as a bucket, a prefix within that bucket under which all Velero data is stored, and a set of additional provider-specific fields (AWS region, Azure storage account, etc.) The [API documentation][1] captures the configurable parameters for each in-tree provider. +A `BackupStorageLocation` is defined as a bucket or a prefix within a bucket under which all Velero data is stored and a set of additional provider-specific fields (AWS region, Azure storage account, etc.). Velero assumes it has control over the location you provide so you should use a dedicated bucket or prefix. If you provide a prefix, then the rest of the bucket is safe to use for multiple purposes. The [API documentation][1] captures the configurable parameters for each in-tree provider. A `VolumeSnapshotLocation` is defined entirely by provider-specific fields (AWS region, Azure resource group, Portworx snapshot type, etc.) The [API documentation][2] captures the configurable parameters for each in-tree provider.