This is my first post in 2019, and Im starting with a MySQL
solution. In MySQL world, implementing a better backup strategy
to meet all of your requirement is still a challenging thing. The
complexity depends on your RPO and RTO. Percona has many tools to
help DBAs in many scenarios. Xtrabackup is one of …

In this three-part blog series, we will explain the details and
functionality of a High Availability (HA) framework for MySQL
hosting using MySQL semisynchronous replication and the
Corosync plus Pacemaker
stack. In Part I, we’ll walk you through the basics of High
Availability, the components of an HA framework, and then
introduce you to the HA framework for MySQL.

What is High Availability?

The availability of a computer system is the percentage of time
its services are up during a period of time. It’s generally
expressed as a series of 9′s. For example, the table below shows
availability and the corresponding downtime measured over one
year.

Want to setup InnoDB Cluster and be prepared for a Disaster
Recovery scenario? Get ready:

Here’s a way to set up InnoDB Cluster using the 3 environments,
on Oracle Linux 7.2, 5.7.19 MySQL Commercial Server, MySQL Shell
8.0.3 DMR, MySQL Router. As this is the first blog post for a
complete disaster recovery scenario of InnoDB Cluster, we’ll also
be installing MySQL Enterprise Backup.

If you’re new to InnoDB Cluster then I’d highly recommend looking
at the following to understand how it works and what Group
Replication, Shell & Router are.:

Equally important as backing up data in a MySQL database is the
ability to restor data.

Most books on the subject emphasize the importance of backing up
your data regularly (and rightly so), but restoring the data is
an often-overlooked aspect of this process. Backed-up files are
useless if they can’t be accessed. Accordingly, you should
regularly restore your files from backup to make certain they can
be used in an emergency. In fact, it might not be too much to say
that a backup job isn’t complete until you’ve confirmed that the
backup files can be restored. Besides the peace of mind you’ll
achieve, it pays to be thoroughly familiar with the process,
because you certainly don’t want to waste time learning the
restore procedure after the system goes down.

In this post I will share a recovery scenario of a MySQL database
restore from the binary logs. Recently someone accidentally
dropped an important MySQL database and the backup was not
present! As we know the the binary log contains DMLs to table
data and that’s where our hope lies. Luckily the binary log
retention […]

Percona XtraBackup is a great backup tool with lots of nice
features to make online and consistent backups, although the
variety of options can be a bit overwhelming. s9s_backup tries to
make it simpler for users, it creates an easy to use interface
for XtraBackup features such as full backups, incremental
backups, streaming/non-streaming, and parallel compression.

Backups are organized into backup sets, consisting of a full
backup and zero or more incremental backups. s9s_backup manages
the LSNs (Log Sequence Number) of the XtraBackups. The backup set
can then be restored as one single unit using just one command.

You’ve probably had some troubles with the shared InnoDB
tablespace stored in the ibdata file. Especially when it has
grown for some reasons and reached a critical size.

This behavior occurs in some cases, due to excessive rollback
segments growth or during a migration from a unique shared
tablespace to a file-per-table configuration for example.

In this post, I would like to explain how to shrink the ibdata
file after an unwanted file growth in a file-per-table
configuration.
Note that the process could be done without Trite but the tool
avoids to write the script used to transport tables yourself.

Sometimes the best way to repair data issues and problems within
a MySQL database is to restore only some of the tables from a
backup. For example, suppose that some data was accidentally
deleted from one table due to a software error, then the easiest
way to recover the lost data might be to restore only one table
from a backup. Previously this kind of partial restore was not
supported by MySQL Enterprise Backup (MEB). However, MEB 3.11
introduces support for selective restore from backups created
with the --use-tts option (or TTS backups).

TTS backups are backups that are created with the transportable tablespaces feature of InnoDB.
These backups consist of InnoDB tables that …

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.