Download, and configure the veeam_azure_email_report.sh script. That’s it! Let’s move on to the next thing.
I am using an advanced SMTP package called s-nail, so let’s go ahead and install it: apt-get install s-nailĪs we do not want them to go to SPAM, we will use an external mail server to send these emails, to do this, we will edit the local configuration file of the package: vi ~/.mailrcĪnd add the following to the file, which was probably empty, change the server, user and pass with your own: set smtp-use-starttls The second one is related to the ability to send emails. We will need two small system requirements before we continue, first will be JQ, which is a package that helps us parsing the JSON, let’s go and install it, yum install if CentOS: apt-get install jq Small system requirements before we continue
This entry is quite new, as I have never done any HTML Report from Bash, it was quite good, and great learning curve, tons of echos on the code, a diagram look like this:Īs we can see, the shell script will download the metrics from Veeam Backup for Azure using the RESTful API, which will then put together into a nice HTML Report, and send it after to the Backup Admin. IF you follow all the steps on this post, you will have something similar to this on your email every day: Rest assured, after a few hours today, I have taken the truly impressive Veeam Backup for Azure RESTful API, and built the Report for you. This HTML Report is quite important, as, with the Cloud offerings, we tend to protect those workloads with an improved RPO, like doing Snapshots more often, even a few Backups per day, etc. If you have been using Veeam Backup and Replication for quite some time, and you have deployed Veeam Backup for Azure, you might be missing the HTML Daily Report that can help to understand quickly how everything went.
Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GVP v2.Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM).The rule does not have any effect on the backup report. No ticket is created if the backup completes within the window. This rule will create a ticket if the backup is still running at the end of the backup window. Select Timed Event and set start time to the scheduled start, and end time to the end of the backup window.
If required, an additional event rule can be added to generate a ticket if the backup has not completed within a specified period.Įvent Source: Veeam Agent or Veeam Backup as applicable In some cases it is useful to know if a backup has not completed within the desired timeframe – for example a backup still running when business hours start could impact system performance. Monitoring backups that are taking too long