If you are a DBA or system administrator, you should already be familiar with Percona Xtrabackup, the free hot backup tool for MariaDB and MySQL, and you probably use it to take onsite backups of your production databases.
But what if the backup server is inaccessible because of an outage, or the data has been corrupted? Offsite backups should also be part of a complete disaster recovery strategy.
Nagios, one of the most popular hardware, network, and application monitoring tools, can also handle advanced MariaDB monitoring. With Nagios you can monitor the MariaDB server and its performance, as well as individual MariaDB databases and the information in them.
This new blog series will be about how to easily automate common MariaDB administration tasks using Ansible. We will showcase how to automatically install and configure software such as MariaDB server, MariaDB Galera and MaxScale with ease in reproducible environments.
When I started my career in early nineties, the Internet, the open source software movement and the Linux operating system were in their infancy and MariaDB and MySQL did not exist. Today open source is a mainstream software delivery mechanism, and web applications are built upon open source stacks which include Linux and MariaDB. Sybase was the first relational database I worked with - a then leading relational technology in early nineties.
Applications are often built on top of single MySQL-compliant database instance but often there is a need for more performance and/or availability than what one database instance can provide. Adding slaves or replacing standalone database server with full-fledged MySQL-compliant cluster often requires changes to the application.
My relationship with Colt Engine, the Italian Joomla! Provider started in March 2011, when SkySQL was still a very “young” company and they got in touch with me to have more details on our new company. Since then many things happened on both the SkySQL (and then MariaDB) and the Colt Engine side. During the last two years they become a strong contributor to the MaxScale project (this will be better explained in a blog post later).
MariaDB MaxScale is now RC and together with all the MariaDB team that has been involved in the project we need to thank all the companies that agreed to become part of the MaxScale Beta Test Plan. This major step in the MaxScale life (read more here) had an important impact on the MaxScale QA process.
We have asked some companies to help us in testing MaxScale in “real” environments with different custom settings, different configurations and with traffic load as close to reality as possible.
This time of the year it is traditional, at least in the UK, to look back and reflect on the year that is coming to a close. Since we have just produced the release candidate for MaxScale and are looking forward to the GA release early in the New Year, it seems like a good time to reflect on the events that have bought us to this stage in the story of MaxScale.
One of the nice things about the "plug and play" approach of MaxScale is that people constantly find ways of using it that were not originally envisaged when we designed MaxScale. One such configuration that I have heard of from multiple sources is using monitoring outside of MaxScale itself. This post will discuss a little about how monitoring works and how it can be moved outside of MaxScale. In particular a simplified example will be presented which shows how to use the notification mechanism in Galera to control MaxScale's use of the nodes in a Galera cluster.
Enterprise software has a tough task: deliver compelling features and functions while meeting production grade service levels. Our job is to bring you the innovations of MariaDB packaged in a form that inspires confidence. Thats what MariaDB Enterprise is all about, and we’re excited to bring you a new edition of our flagship product.