diff --git a/images/screenshot/gui-cluster-backup-edit-01-general.png b/images/screenshot/gui-cluster-backup-edit-01-general.png
new file mode 100644
index 0000000..ece894c
Binary files /dev/null and b/images/screenshot/gui-cluster-backup-edit-01-general.png differ
diff --git a/images/screenshot/gui-cluster-backup-edit-02-retention.png b/images/screenshot/gui-cluster-backup-edit-02-retention.png
new file mode 100644
index 0000000..06a006e
Binary files /dev/null and b/images/screenshot/gui-cluster-backup-edit-02-retention.png differ
diff --git a/images/screenshot/gui-cluster-backup-edit-03-template.png b/images/screenshot/gui-cluster-backup-edit-03-template.png
new file mode 100644
index 0000000..8f70b27
Binary files /dev/null and b/images/screenshot/gui-cluster-backup-edit-03-template.png differ
diff --git a/images/screenshot/gui-cluster-backup-edit-04-advanced.png b/images/screenshot/gui-cluster-backup-edit-04-advanced.png
new file mode 100644
index 0000000..b9ca95b
Binary files /dev/null and b/images/screenshot/gui-cluster-backup-edit-04-advanced.png differ
diff --git a/images/screenshot/gui-cluster-backup-overview.png b/images/screenshot/gui-cluster-backup-overview.png
new file mode 100644
index 0000000..b63e2b0
Binary files /dev/null and b/images/screenshot/gui-cluster-backup-overview.png differ
diff --git a/vzdump.adoc b/vzdump.adoc
index f0a7131..35b5c53 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -228,12 +228,16 @@ encryption of backups, see xref:storage_pbs_encryption[the corresponding section
 Backup Jobs
 -----------
 
+[thumbnail="screenshot/gui-cluster-backup-overview.png"]
+
 Besides triggering a backup manually, you can also setup periodic jobs that
 backup all, or a selection of virtual guest to a storage. You can manage the
 jobs in the UI under 'Datacenter' -> 'Backup' or via the `/cluster/backup` API
 endpoint. Both will generate job entries in `/etc/pve/jobs.cfg`, which are
 parsed and executed by the `pvescheduler` daemon.
 
+[thumbnail="screenshot/gui-cluster-backup-edit-01-general.png", float="left"]
+
 A job is either configured for all cluster nodes or a specific node, and is
 executed according to a given schedule. The format for the schedule is very
 similar to `systemd` calendar events, see the
@@ -241,17 +245,22 @@ xref:chapter_calendar_events[calendar events] section for details. The
 'Schedule' field in the UI can be freely edited, and it contains several
 examples that can be used as a starting point in its drop-down list.
 
+[thumbnail="screenshot/gui-cluster-backup-edit-02-retention.png"]
+
 You can configure job-specific xref:vzdump_retention[retention options]
 overriding those from the storage or node configuration, as well as a
 xref:vzdump_notes[template for notes] for additional information to be saved
 together with the backup.
 
+[thumbnail="screenshot/gui-cluster-backup-edit-03-template.png", float="left"]
 Since scheduled backups miss their execution when the host was offline or the
 pvescheduler was disabled during the scheduled time, it is possible to configure
 the behaviour for catching up. By enabling the `Repeat missed` option (in the
 'Advanced' tab in the UI, `repeat-missed` in the config), you can tell the
 scheduler that it should run missed jobs as soon as possible.
 
+[thumbnail="screenshot/gui-cluster-backup-edit-04-advanced.png"]
+
 There are a few settings for tuning backup performance (some of which are
 exposed in the 'Advanced' tab in the UI). The most notable is `bwlimit` for
 limiting IO bandwidth. The amount of threads used for the compressor can be