diff --git a/site/content/docs/main/restic.md b/site/content/docs/main/restic.md
index 02d4e7bb5..dfa42a488 100644
--- a/site/content/docs/main/restic.md
+++ b/site/content/docs/main/restic.md
@@ -340,6 +340,7 @@ volumes will be full rather than incremental, because the pod volume's lifecycle
 - Restic scans each file in a single thread. This means that large files (such as ones storing a database) will take a long time to scan for data deduplication, even if the actual
 difference is small.
 - If you plan to use the Velero restic integration to backup 100GB of data or more, you may need to [customize the resource limits](/docs/main/customize-installation/#customize-resource-requests-and-limits) to make sure backups complete successfully.
+- Velero's restic integration backs up data from volumes by accessing the node's filesystem, on which the pod is running. For this reason, restic integration can only backup volumes that are mounted by a pod and not directly from the PVC.
 
 ## Customize Restore Helper Container
 
diff --git a/site/content/docs/v1.4/restic.md b/site/content/docs/v1.4/restic.md
index 504aea248..f5d7c39c4 100644
--- a/site/content/docs/v1.4/restic.md
+++ b/site/content/docs/v1.4/restic.md
@@ -250,6 +250,7 @@ volumes will be full rather than incremental, because the pod volume's lifecycle
 - Restic scans each file in a single thread. This means that large files (such as ones storing a database) will take a long time to scan for data deduplication, even if the actual
 difference is small.
 - If you plan to use the Velero restic integration to backup 100GB of data or more, you may need to [customize the resource limits](/docs/main/customize-installation/#customize-resource-requests-and-limits) to make sure backups complete successfully.
+- Velero's restic integration backs up data from volumes by accessing the node's filesystem, on which the pod is running. For this reason, restic integration can only backup volumes that are mounted by a pod and not directly from the PVC.
 
 ## Customize Restore Helper Container
 
diff --git a/site/content/docs/v1.5/restic.md b/site/content/docs/v1.5/restic.md
index 02d4e7bb5..dfa42a488 100644
--- a/site/content/docs/v1.5/restic.md
+++ b/site/content/docs/v1.5/restic.md
@@ -340,6 +340,7 @@ volumes will be full rather than incremental, because the pod volume's lifecycle
 - Restic scans each file in a single thread. This means that large files (such as ones storing a database) will take a long time to scan for data deduplication, even if the actual
 difference is small.
 - If you plan to use the Velero restic integration to backup 100GB of data or more, you may need to [customize the resource limits](/docs/main/customize-installation/#customize-resource-requests-and-limits) to make sure backups complete successfully.
+- Velero's restic integration backs up data from volumes by accessing the node's filesystem, on which the pod is running. For this reason, restic integration can only backup volumes that are mounted by a pod and not directly from the PVC.
 
 ## Customize Restore Helper Container