diff --git a/content/post/18-create-nas-server-with-truenas.md b/content/post/18-create-nas-server-with-truenas.md
index 691dfa3..95fbf47 100644
--- a/content/post/18-create-nas-server-with-truenas.md
+++ b/content/post/18-create-nas-server-with-truenas.md
@@ -142,12 +142,24 @@ I create another dataset: `media`, and a child `photos`. I create a NFS share fr
 On my current NFS server, the files for the photos are owned by `root` (managed by *Immich*). Later I'll see how I can migrate towards a root-less version. For now I set, in `Advanced Options`, the `Maproot User` and `Maproot Group` to `root`. This is equivalent de the attribute `no_squash_root`, the local `root` of the client stays `root` on the server, not a best practice:
 ![NFS share permission in TrueNAS](img/truenas-dataset-photos-nfs-share.png)
 
+At the end, my datasets tree in my `storage` pool look like this:
+- backups
+	- `duplicati`: [Duplicati](https://duplicati.com/) storage backend
+	- `proxmox`: future Proxmox Backup Server
+- `cloud`: `Nextcloud` datas
+- `files`:
+- `media`
+	- `downloads`
+	- `photos`
+	- `videos`
+
+### Data protection
+
+Now let's configure some data protection features, here is the `Data Protection` tab:
+![Data protection features in TrueNAS](img/truenas-data-protection-tab.png)
 
 
 
-
-### data protection
-
 ## Use of TrueNAS
 
 ### Firewall rule
diff --git a/static/img/truenas-data-protection-tab.png b/static/img/truenas-data-protection-tab.png
new file mode 100644
index 0000000..75285a7
Binary files /dev/null and b/static/img/truenas-data-protection-tab.png differ