23. 09. 2025
NetEye
With NetEye version 4.42, we’re excited to introduce a clustered solution for MariaDB – MariaDB Galera – designed to enhance the high availability of all NetEye services. This improvement significantly increases the reliability of services that depend on the database, such as Icinga 2, Icinga Web 2, Grafana, Keycloak, and others.
Thanks to this new architecture, database downtime is now drastically reduced. Unlike previous versions that relied on a single MariaDB instance, the new setup allows multiple instances to work collaboratively, providing a more resilient database service.
It’s important to note that with this change, the PCS resource previously used for backup management is no longer required and will be removed. Therefore, updating the backup configuration is essential to ensure compatibility with MariaDB Galera.
For further details on this feature, please refer to the delivery notes: NetEye 4.42 Release Notes | www.neteye-blog.com.
Configuring the Backup
At the end of this upgrade, you’ll need to modify the backup configuration, as the standard backup we usually set up for clients no longer works since we’ve removed the PCS resource. This applies to both single nodes as well as clusters. Obviously, if it’s a virtual single node, the backup might have been skipped, leaving management to the Hypervisor that handles the virtual machine.
When configuring the backup, we start from this project available in our Bitbucket repository:
siwuerthphoenix / cluster_backup – Bitbucket
To correctly configure the backup for the MariaDB Galera cluster, you need to locally download the branch that’s compatible with MariaDB Galera from Galera siwuerthphoenix / cluster_backup – Bitbucket using the GUI by selecting the branch and downloading the package locally:
Once done, open the downloaded file.
Unzip the archive into a temporary folder and extract the two required files:
backup.shlocated in the main foldermariadb_backup.shlocated in thescripts/folder
At this point, if you’re on a cluster, you need to verify the node where the backup resource is running using the command:
pcs status | grep backup
Once the node is identified, back up the existing files and then overwrite them.
After this, you can proceed to manually launch the backup by retrieving the execution line directly from the crontab using the command:
crontab -l
You’ll find something like the following (as per the README):
## NetEye Backup Cluster
0 1 * * * if [ -f "/neteye/shared/backup/backup.sh" ]; then /neteye/shared/backup/backup.sh -a -c -d /cifs/backup/neteye-cluster-backup -e -g -I -l -m -n -o -p -r -s -t /data/tmp -v -w -z > /root/backup_cluster_output.txt 2>&1; fi
Take the customized command that each client has configured, launch it manually, and wait for the backup to complete.
In Conclusion…
Currently, apart from this modification, I have not made any other customizations. When the upgrade is performed by a consultant, this activity should already be done or have been planned. The above is intended for clients who proceed with updates and upgrades on their own.
Enjoy your new backup!
These Solutions are Engineered by Humans
Did you find this article interesting? Does it match your skill set? Our customers often present us with problems that need customized solutions. In fact, we’re currently hiring for roles just like this and others here at Würth Phoenix.
Franco Federico
Hi, I’m Franco and I was born in Monza. For 20 years I worked for IBM in various roles. I started as a customer service representative (help desk operator), then I was promoted to Windows expert. In 2004 I changed again and was promoted to consultant, business analyst, then Java developer, and finally technical support and system integrator for Enterprise Content Management (FileNet). Several years ago I became fascinated by the Open Source world, the GNU\Linux operating system, and security in general. So for 4 years during my free time I studied security systems and computer networks in order to extend my knowledge. I came across several open source technologies including the Elastic stack (formerly ELK), and started to explore them and other similar ones like Grafana, Greylog, Snort, Grok, etc. I like to script in Python, too. Then I started to work in Würth Phoenix like consultant. Two years ago I moved with my family in Berlin to work for a startup in fintech(Nuri), but the startup went bankrupt due to insolvency. No problem, Berlin offered many other opportunities and I started working for Helios IT Service as an infrastructure monitoring expert with Icinga and Elastic, but after another year I preferred to return to Italy for various reasons that we can go into in person 🙂 In my free time I continue to dedicate myself to my family(especially my daughter) and I like walking, reading, dancing and making pizza for friends and relatives.
Author
Latest posts by Franco Federico
12. 06. 2025
NetEye, Unified Monitoring
From Monitoring to SOC
17. 02. 2025
Unified Monitoring
Monitoring Printer Logs
10. 12. 2024
Log-SIEM
Let’s Discover ES|QL
18. 10. 2024
DevOps
My Laptop Is Broken …. What Can I Do?