Data is an essential part of running a Moodle environment. Should the IT operations team lose data accidentally, then it could lead to a huge loss. So, to protect valuable information, sysadmins need to back up their Moodle database.

Backups are one of the most important things to take care of while managing a database. In this blog we are going to look into how to backup your Moodle database using ClusterControl.

ClusterControl provides you with centralized backup management for the Moodle databases, and it provides you with hot backups of large datasets, point in time recovery, in-transit data encryption, data integrity via automatic restore verification, cloud backups (AWS, Google and Azure) for Disaster Recovery, retention policies to ensure compliance, and …

Large replication topologies are quite common nowadays, and this kind of architecture often requires a quick method to rebuild a replica from another server.

The Clone Plugin, available since MySQL 8.0.17, is a great feature that allows cloning databases out of the box. It is easy to rebuild a replica or to add new nodes to a cluster using the plugin. Before the release of the plugin, the best open-source alternative was Percona XtraBackup for MySQL Databases.

In this blog post, we compare both alternatives for cloning purposes. If you need to perform backups, Percona XtraBackup is a better tool as it supports compression and incremental backups, among other features not provided by the plugin. The plugin supports compression only for network transmission, not for storage.

But one of the plugin’s strong points is simplicity. …

In this article, we are going to see how to set up a MySQL Database instance on Microsoft Azure Cloud.

The post MySQL in Azure first appeared on dasini.net - Diary of a MySQL experts.

We are pleased to announce the release of MySQL Cluster 8.0.23, the latest GA, along with 7.6.17, 7.5.21, 7.4.31, and 7.3.32. MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: In-Memory storage – Real-time performance (with optional checkpointing to disk)Transparent Auto-Sharding – Read & write scalabilityActive-Active/Multi-Master geographic replication99.999% High Availability with […]

The expected version 8.0.23 of MySQL has been released yesterday \o/

For new features and resolved bugs, I recommend Geir‘s traditional blog post announcing the release.

Of course, as usual, this release contains contributions from our great Community and let me thanks all the contributors on behalf of the MySQL Team.

MySQL 8.0.23 includes contributions from Daniel Black, Vilnis Termanis, Venkatesh Prasad Venugopal, Daniël van Eeden, Cai Yibo, Kamil Holubick, Shaohua Wang, Krunal Bauskar, Tzachi Zidenberg, Cédric Luthi, Brian Yue, Hope Lee and Facebook.

Thank you all for your great contributions. MySQL is an Open Source project, GPL, …

MySQL Server 8.0.22 and 5.7.33, new versions of the popular Open Source Database Management System, have been released. These releases are recommended for use on production systems. For an overview of what’s new, please see http://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html For information on installing the release on new servers, please see the MySQL installation documentation at http://dev.mysql.com/doc/refman/8.0/en/installing.html http://dev.mysql.com/doc/refman/5.7/en/installing.html […]

Connector/J version 8.0.23 came out with several bug fixes related to date-time types support. They provide more flexibility for configuring time zone handling and allow migration from Connector/J 5.1 with much less effort.

Problems with migration from Connector/J 5.1 to Connector/J 8.0 were caused by the early decision that Connector/J 8.0 should always try to preserve an instant point on the time-line while Connector/J 5.1 does it optionally and, by default, preserves the original visual representation.

For example, the following code will store different results with Connector/J 5.1 and Connector/J 8.0 in case the client and server time zones are different:

Statement st = conn.createStatement();
st.executeUpdate("CREATE TABLE t1 (ts TIMESTAMP)");

PreparedStatement ps = conn.prepareStatement("INSERT INTO t1 VALUES (?)");
ps.setTimestamp(1, Timestamp.valueOf("2020-01-01 12:00:00"));
ps.executeUpdate();

If the client …

As of today a new version of MySQL NDB Cluster is available.

First of all this release fixes various bugs, enhancing the stability and robustness of cluster further.

Already in 8.0.21 MySQL the NDB team started to remove racially insensitive terminology from its configuration files, command line options, documentation and source code. In 8.0.23 we now hope to have finalized this work.

Automated thread configuration is a new feature added. If enabled it will automatically run NDB with the ideal number of threads based on the number of physical cores and cpus of the data node’s host system. This feature needs to be activated in the configuration.

NDB comes with the latest version of our MySQL SQL front-end servers. Often also NDB users benefit from all its great new features and fixes as well. More details about it can be found in the …

Starting with the 8.0.23 release, Connector/Node.js will be deprecating support for End-of-life Node.js engine versions. Support for these versions will eventually be removed on subsequent releases which will focus on compatibility with the available LTS versions at the date of each release.

Why now?

Up until now, the minimum Node.js engine version compatible with Connector/Node.js was version 4.2.0. This is a fairly old release that has reached End-of-life status in 2018 and, of course, hasn’t been maintained since then. This is also the case for the next two major Node.js versions – v6 and v8 – and will soon (April 30, 2021) be the case for Node.js v10. So, as of today, the oldest LTS version available is effectively Node.js v12, and the …

Dear MySQL users,

MySQL Connector/ODBC 8.0.23 is a new version in the MySQL Connector/ODBC
8.0 series, the ODBC driver for the MySQL Server.

The available downloads include both a Unicode driver and an ANSI driver
based on the same modern codebase. Please select the driver type you
need based on the type of your application – Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with the latest MySQL server version 8.0.

This release of the MySQL ODBC driver is conforming to the ODBC 3.8
specification. It contains implementations of key 3.8 features,
including self-identification as a ODBC 3.8 driver, streaming of out (for
binary types only), and support of the SQL_ATTR_RESET_CONNECTION
connection attribute (for the Unicode driver only).

The release is now available in source and binary form for a number …