From: Lukas Wagner <l.wagner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 1/2] docs: document notification-mode and merge old notification section
Date: Thu, 25 Apr 2024 14:30:24 +0200 [thread overview]
Message-ID: <20240425123025.310887-1-l.wagner@proxmox.com> (raw)
This new section describes how the notification-mode parameter works.
The section also contains also parts of the old notification section
from the maintenance chapter, reusing the description of the
`notify` and `notify-user` parameters.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
docs/maintenance.rst | 26 --------------------------
docs/notifications.rst | 42 ++++++++++++++++++++++++++++++++++++++++++
docs/storage.rst | 4 ++--
3 files changed, 44 insertions(+), 28 deletions(-)
diff --git a/docs/maintenance.rst b/docs/maintenance.rst
index 6dbb6941..1dd17ad0 100644
--- a/docs/maintenance.rst
+++ b/docs/maintenance.rst
@@ -272,32 +272,6 @@ datastores, backup groups or snapshots. To do this, navigate to the **Content**
tab of the datastore and either click *Verify All* or select the *V.* icon from
the **Actions** column in the table.
-.. _maintenance_notification:
-
-Notifications
--------------
-
-Proxmox Backup Server can send you notification emails about automatically
-scheduled verification, garbage-collection and synchronization tasks results.
-
-By default, notifications are sent to the email address configured for the
-`root@pam` user. You can instead set this user for each datastore.
-
-.. image:: images/screenshots/pbs-gui-datastore-options.png
- :target: _images/pbs-gui-datastore-options.png
- :align: right
- :alt: Datastore Options
-
-You can also change the level of notification received per task type, the
-following options are available:
-
-* Always: send a notification for any scheduled task, independent of the
- outcome
-
-* Errors: send a notification for any scheduled task that results in an error
-
-* Never: do not send any notification at all
-
.. _maintenance_mode:
Maintenance Mode
diff --git a/docs/notifications.rst b/docs/notifications.rst
index 4f9b01b7..e5ec74b7 100644
--- a/docs/notifications.rst
+++ b/docs/notifications.rst
@@ -211,3 +211,45 @@ Permissions
In order to modify/view the configuration for notification targets,
the ``Sys.Modify/Sys.Audit`` permissions are required for the
``/system/notifications`` ACL node.
+
+.. _notification_mode:
+
+Notification Mode
+-----------------
+
+To ensure a smooth transition from the old, purely email based system to
+the new configurable notification system introduced in Proxmox Backup Server 3.2,
+datastore options, tape backup jobs and tape restore jobs gain a new option:
+``notification-mode``. This option must be set to ``notification-system``
+to opt in to the new notification system. If the option is not set, or
+set to ``legacy-sendmail``, Proxmox Backup Server will use the old
+system.
+
+Starting with Proxmox Backup Server 3.2, a datastore created in the UI will
+automatically opt in to the new notification system. If the datastore is created
+via the API or the ``proxmox-backup-manager`` CLI, the ``notification-system``
+option has to be set explicitly.
+
+The ``legacy-sendmail`` mode will be deprecated and removed in a later
+release of Proxmox Backup Server.
+
+Settings for ``legacy-sendmail`` notification mode
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If ``notification-mode`` is set to ``legacy-sendmail``, Proxmox Backup Server
+will send notification emails via the system's ``sendmail`` command to the email
+address configured for the user set in the ``notify-user`` option
+(falling back to ``root@pam`` if not set)
+
+For datastores, you can also change the level of notification received per task
+type via the ``notify`` option.
+
+* Always: send a notification for any scheduled task, independent of the
+ outcome
+
+* Errors: send a notification for any scheduled task that results in an error
+
+* Never: do not send any notification at all
+
+The ``notify-user`` and ``notify`` options are ignored if ``notification-mode``
+is set to ``notification-system``.
diff --git a/docs/storage.rst b/docs/storage.rst
index 4444c423..f1e15d52 100644
--- a/docs/storage.rst
+++ b/docs/storage.rst
@@ -314,7 +314,7 @@ Options
There are a few per-datastore options:
-* :ref:`Notifications <maintenance_notification>`
+* :ref:`Notification mode and legacy notification settings <notification_mode>`
* :ref:`Maintenance Mode <maintenance_mode>`
* Verification of incoming backups
@@ -419,7 +419,7 @@ remote-source to avoid that an attacker that took over the source can cause
deletions of backups on the target hosts.
If the source-host became victim of a ransomware attack, there is a good chance
that sync jobs will fail, triggering an :ref:`error notification
-<maintenance_notification>`.
+<Notification Events>`.
It is also possible to create :ref:`tape backups <tape_backup>` as a second
storage medium. This way, you get an additional copy of your data on a
--
2.39.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2024-04-25 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 12:30 Lukas Wagner [this message]
2024-04-25 12:30 ` [pbs-devel] [PATCH proxmox-backup 2/2] ui: datastore options: link to 'notification-mode' section Lukas Wagner
2024-04-25 12:41 ` [pbs-devel] [PATCH proxmox-backup 1/2] docs: document notification-mode and merge old notification section Gabriel Goller
2024-04-25 12:45 ` Lukas Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240425123025.310887-1-l.wagner@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox