diff --git a/docs/_static/img/backup/rep1.png b/docs/_static/img/backup/rep1.png
new file mode 100644
index 00000000000..ed9120a18da
Binary files /dev/null and b/docs/_static/img/backup/rep1.png differ
diff --git a/docs/_static/img/backup/rep2.png b/docs/_static/img/backup/rep2.png
new file mode 100644
index 00000000000..5ca02f0a009
Binary files /dev/null and b/docs/_static/img/backup/rep2.png differ
diff --git a/docs/manual/Quick-Start Guides/14-backup-restore.md b/docs/manual/Quick-Start Guides/14-backup-restore.md
index 9d3010f7f72..0a551d3fc65 100644
--- a/docs/manual/Quick-Start Guides/14-backup-restore.md
+++ b/docs/manual/Quick-Start Guides/14-backup-restore.md
@@ -43,18 +43,17 @@ If you want to ensure TrueTool automatically gets updated and/or (re)installed a
##### Exporting Backups
The above only creates only a backup of the kubernetes objects and a snapshot of the `PVC` and `ix_volume` storage.
+These backups are saved under the same ix_applications dataset.
+
It does not protect these against, for example, deletion of datasets or save them on an external system.
We **highly** advice making both an internal backup (seperate dataset on the same system) *and* an offsite backup.
One could create a normal recursive(!) replication of the `ix-volumes` dataset using the SCALE GUI, with the following few special tricks by editing the replication after creation:
-1. Exclude the docker images:
+To do so, setup the following replication task:
-
-
-2. Include any snapshots made by the above backup task
-
-
+
+
It's also important to ensure you keep regular config backups of the SCALE system itself, preferably right after the Apps backup above).
However this is not part of this guide and we will assume you've done so yourself.