Fork me on GitHub

Differences

This shows you the differences between two versions of the page.

developer:email_reporting [2010/02/11 03:29]
henri
developer:email_reporting [2010/02/11 03:32] (current)
henri
Line 4: Line 4:
 Currently there a variety of situations when emails are not sent. With the default LBackup example configuration emails are only sent out if the backup has actually started. If a machine is not available for backup then this will not generate an email report. For automated notifications regarding these situations you should schedule the lmail program at a specific interval to report the status of the backups. Another possibility is to enable more verbose email reporting within the LBackup configuration file. Currently there a variety of situations when emails are not sent. With the default LBackup example configuration emails are only sent out if the backup has actually started. If a machine is not available for backup then this will not generate an email report. For automated notifications regarding these situations you should schedule the lmail program at a specific interval to report the status of the backups. Another possibility is to enable more verbose email reporting within the LBackup configuration file.
 \\ \\ \\ \\
 +
 +==== Email Reporting on Every Backup Run ====
 +There is a configuration option which you may set so that every time a backup configuration is executed an email is sent out regardless of the success or failure of the backup. Please examine the example lbackup configuration included in the ''/lbackup'' directory.
 +
  
 ===== Email Locking ===== ===== Email Locking =====
Line 17: Line 21:
 \\ \\  \\ \\ 
  
-==== Email Reporting on Every Backup Run ==== 
-There is a configuration option which you may set so that every time a backup configuration is executed an email is sent out regardless of the success or failure of the backup. Please examine the example lbackup configuration included in the ''/lbackup'' directory.