Protecting your data – Part II: Preventing unwanted data changes on Group Replication members by asynchronous replication channels

Further to our earlier blog post about Fail-safe enhancements to Group Replication, where we discussed enhancements against data modification in members which are not ONLINE, we now present here additional changes to protect data from being accidentally modified by asynchronous replication channels.…

Getting started with MySQL Cluster 7.6 using MySQL Cluster Manager 1.4.6

MySQL_Cluster_Manager

MySQL Cluster 7.6 is GA!
If you’re eager to give the recently announced MySQL Cluster 7.6 GA a spin, I’ll walk you through a quick and simple way to get started using MySQL Cluster Manager 1.4.6.

Bootstrap and go!

  1. Download and install MCM and MySQL Cluster
  2. Bootstrap a cluster with MCM

    $ mcmd –bootstrap
  3. Connect to the database, and have at it

    $ mysql -h 127.0.0.1 -P 3306 -u root

That simple.…

MySQL Cluster Manager 1.4.6 released!

MySQL_Cluster_Manager
MySQL Cluster Manager 1.4.6 is now available for download from My Oracle Support.

Overview
In MCM 1.4.6, the list backups command has been extended with a new –agent option for listing agent backups created with the backup agents command.


The output can be filtered with the –backupid option:


The backupids for agent backups reflect the Unix Epoch times at which the backups were taken.…

Reading the log positions of a snapshot consistently

MySQL 8.0.11 introduced a new performance schema table named log_status, which provides consistent information about MySQL server instance log positions from replication and transactional storage engines.

Used in conjunction with other MySQL 8.0 feature (the backup lock), this new feature will allow backup tools to take backup with minimal impact in DML throughput, but ensuring consistent snapshot with respect to GTIDs, replication, binary logs and transactional storage engine logs.…

Taking advantage of new transaction length metadata

MySQL 8.0.2 introduced a small yet powerful per transaction metadata information containing the transaction length in binary logs.

MySQL binary logs are being used for many other things than MySQL replication or backup/recovery: replicate to Hadoop; replicate to other databases, such as Oracle; capture data change (CDC) and extract-transform-load (ETL); record change notification for cache invalidation; change tracking for differential backups; etc.…