When it comes to Backup, we know, things get serious.
In an ever-changing IT and CyberSec landscape, whether it’s your company’s data or your customer’s, careful planning of this process is critical.
The (minimal) best practice of 3-2-1 we all know, right?
Let’s start with live data on Server, copy to local NAS and further copy to Cloud for example.
If you use Synology NAS, the obvious choice is Hyper Backup: integrated, free, does the job. Are we good? In my opinion, NOPE! Now let me explain.
Backups, if you want to live professionally serene, have to be actively kept under control and if there is a hiccup or degradation in the process, it has to be managed and the management has to be foolproof.
That is why I have always found email notifications, as in the case of Hyper Backup, limited: they have to be organized and filtered with high risk of missing some…in short anything but foolproof or error free.
Zabbix and Synology integration
If you are reading this article you are probably already familiar with
Zabbix.
The moment you decide to do the right thing by monitoring your Synology NAS the native Template Synology DiskStation is a great place to start to keep tabs on its health via SNMP.
However, when you look for something more, like info on Hyper Backup, you won’t find SNMP specifics, in fact to be honest I couldn’t find any whatsoever!
So, by putting together some little DSM Web Api documentation, DevTools-Fu on the web interface, and a lot of patience I created a basic Hyper Backup Monitoring Template that you can find on my
GitHub.
Zabbix Hyper Backup Template
Let’s start by configuring a dedicated user in DSM.
The user can be a simple member of the users group to which, through the Delegate menu, we will assign the Hyper Backup management
role. In this way it is also possible to harden its access by explicitly denying it Applications permissions.
If your version of DSM does not support delegation by role the user should be added to the administrators group (sigh) with the flags you see in the image, I would then limit if possible the DSM By IP access.
Let’s move on to the Zabbix Template and see the MACROs present
Among these we will need to set at the Host level:
- {$SYNO.REST.USER}
- {$SYNO.REST.PASSWORD}
All we have to do is apply the Template to the Host and wait for data collection via Discovery:
- Hyper Backup Task {#TASK_NAME} last result
- Hyper Backup Task {#TASK_NAME} last run
- Hyper Backup Task {#TASK_NAME} next run
- Hyper Backup Task {#TASK_NAME} status
Zabbix Hyper Backup Trigger
The preset Triggers are individual on a Task basis and absolutely generic, just to make sure the data is processed and the Tasks are completed successfully
My advice is of course to modify or add them according to your specific needs and if you have any improving ideas let me know in the comments or collaborate on GitHub.