diff --git a/docs/reference/data_layout.md b/docs/reference/data_layout.md
index 56b1e0b4..9bf8b7d2 100644
--- a/docs/reference/data_layout.md
+++ b/docs/reference/data_layout.md
@@ -1,6 +1,6 @@
 # Data layout
 
-The applications deployed in the stack utilize a combination of data-at-rest (_static config, files, etc_) and runtime data (_live database files_). The realtime data can't be [backed up][duplicity] with a simple copy-paste, so where we employ databases, we also include containers to perform a regular export of database data to a filesystem location.
+The applications deployed in the stack utilize a combination of data-at-rest (_static config, files, etc_) and runtime data (_live database files_). The realtime data can't be [backed up](../recipes/duplicity.md) with a simple copy-paste, so where we employ databases, we also include containers to perform a regular export of database data to a filesystem location.
 
 So that we can confidently backup all our data, I've setup a data layout as per the following example: