[pve-devel] [PATCH docs] vzdump: remove usage examples involving 'notification-{target, policy}'

Lukas Wagner l.wagner at proxmox.com
Wed Feb 14 10:07:38 CET 2024

Also clarify in one example that using `--mailto` will bypass the
notification system (at least from the user's perspective).

Signed-off-by: Lukas Wagner <l.wagner at proxmox.com>
 vzdump.adoc | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/vzdump.adoc b/vzdump.adoc
index 24a3e80..b5bbac7 100644
--- a/vzdump.adoc
+++ b/vzdump.adoc
@@ -555,14 +555,12 @@ Use rsync and suspend/resume to create a snapshot (minimal downtime).
  # vzdump 777 --mode suspend
 Backup all guest systems and send notification mails to root and admin.
+Due to `mailto` being set and `notification-mode` being set to `auto` by
+default, the notification mails are sent via the system's `sendmail`
+command instead of the notification system.
  # vzdump --all --mode suspend --mailto root --mailto admin
-Backup guest 777 and notify via the `notify-admins` notification target on
- # vzdump 777  --notification-target notify-admins --notification-policy failure
 Use snapshot mode (no downtime) and non-default dump directory.
  # vzdump 777 --dumpdir /mnt/backup --mode snapshot
@@ -592,4 +590,3 @@ file system, using pipes

More information about the pve-devel mailing list