From dd5a4927e70da64517c3ea222f9fd87da0092d25 Mon Sep 17 00:00:00 2001 From: Lukas Wagner Date: Wed, 14 Feb 2024 10:07:38 +0100 Subject: [PATCH] vzdump: remove usage examples involving 'notification-{target, policy}' 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 --- 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 -failure. - - # 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 ifdef::manvolnum[] include::pve-copyright.adoc[] endif::manvolnum[] -