In this blog article we will show you how to install AutoMySQLBackup on a Linux VPS. AutoMySQLBackup is very useful utility for creating daily, weekly or monthly backups of one or more MySQL databases from one of more MySQL servers. It dumps the databases and compress them in to archives.it comes with many features such as: Email notification of backups Backup Compression and Encryption Configurable backup rotation Incremental database backups As usual, log in to your server as user root ssh root@IP and execute the following command to make sure that all services ar up to […]
It goes without saying that crash recovery of busy MySQL servers
(and many other RDBMS for that matter) is not an extremely quick
process. In MySQL context, one of the worst case scenarios is
when the server is used for multi-tenant application hosting i.e.
when the MySQL instance contains hundreds or thousands of schemas
and (tens/hundreds of) thousands of tablespaces. In such
scenario, the server may spend a considerable amount of time in
the tablespace discovery phase, during which MySQL
builds a mapping between tablespace IDs and names of actual
tablespace files on disk.
MySQL 5.7 promises to put an end to tablespace discovery. The
documentation lists the following improvements introduced in
versions 5.7.5 and up:
- Elimination of file system scans prior to redo log application. The MLOG_FILE_NAME redo log …
MySQL 5.7 is GA and has over than 150 new features. One of them is a Native JSON Data Type and JSON Functions: "Allows for efficient and flexible storage, search and manipulation of schema-less data. Enhancements include a new internal binary format, support for easy integration within SQL, and index management on the JSON Documents using generated columns".
Today i want to share experience with latest Percona Server where
TokuDB and TokuBakcup plugins have been added in main
source.
So there is no other steps needed here to get and started.
But in recent discussion in our local community, there was a
question: “How about installing MySQL on CentOS minimal”.
The reason was clear, because somebody got too many errors in
fresh CentOS 7 minimal.
I want to share here full steps.
Please follow numbers:
1. Getting Source package:
[root@testing-host1 ~]# wget
https://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.27-75.0/source/tarball/percona-server-5.6.27-75.0.tar.gz
Unpacking:
tar -xvf percona-server-5.6.27-75.0.tar.gz
2. Compiling using CMAKE:
If you have read the documentation:
…
[Read more]Codership is pleased to announce the release of Galera Cluster 5.5.46 and 5.6.27 with Galera Replication library 3.13, implementing wsrep API version 25.
Galera Cluster is now available as targeted packages and package repositories for a number of Linux distributions, including Ubuntu, Red Hat, Debian, Fedora, CentOS, OpenSUSE and SLES. Obtaining packages using a package repository removes the need to download individual files and facilitates the deployment and upgrade of Galera nodes.
This and future releases will be available from http://www.galeracluster.com, while previous releases remain available on LaunchPad. The source repositories and bug tracking are now on http://www.github.com/codership.
New features and notable changes in Galera Cluster and the Galera library:
- security fix for the LogJam issue. The key length used for creating Diffie-Hellman keys has been increased to 2,048 bits.
- a …
In this blog post, we are going to show you some examples of things that can go wrong in Galera - inexplicable node crashes, network splits, clusters that won’t restart and inconsistent data. We’ll take a look at the data stored in log files to diagnose the problems, and discuss how we can deal with these.
This builds upon the previous post, where we looked into log files produced by Galera (error log and innobackup.* logs). We discussed how regular, “normal” activity looks like - from initialization of Galera replication to Incremental State Transfer (IST) and State Snapshot Transfer (SST) processes, and the respective log entries.
This is the seventeenth installment in the ‘Become a MySQL DBA’ blog series. Our previous posts in the DBA series include:
- …
With MySQL, it is relatively easy to create “point in time” restores. All you need is recent(ish) backup and a bunch of saved binary logs. You can restore the backup you have, and when it is completed, you can use mysqlbinlog utility to apply your saved binary logs to the desired state of your database.
I have created a simple go application to make your life easier. You can find it on my GitHub page.
The app works as reading its config file for the MySQL server connection credentials, a local directory where the binary logs will be kept, and the will path of the mysqlbinlog utility.
- It checks the binlogs on the remote server which able to streamed
- Checks the local directory where the binlogs are kept, to check which logs are already there
- The incomplete (file size differs local and on remote server) files will be …
Recently my colleague (by Percona) Yves Trudeau and
colleague (by industry) Marco Tusa
published their materials on Amazon Aurora. Indeed, Amazon
Aurora is a hot topic these days, and we have a stream of
customer inquiries regarding this technology. I’ve decided to
form my own opinion, and nothing is better than a personal,
hands-on experience, which I am going to share.
The materials I will refer to:
- [1] Presentation from Amazon Re:Invent: …
ScaleDB 15.10 is out. Some users have downloaded it and tested it
and we have received pretty positive feedback, but also some
requests to have more info and help on how to start. I will try
to condense here the basic steps to install and test ScaleDB ONE
for the first time.
First of all, some terminology. We have two versions: ScaleDB
ONE and ScaleDB Cluster. ScaleDB ONE is meant to be
used on a single machine (ONE = One Node Edition), whether it is
a VM, a cloud instance or a physical server, whilst ScaleDB
Cluster is the full size, multi-node cluster that everybody
expects to run for mission critical applications. This means that
the typical use cases for ScaleDB ONE are testing and
development, data marts and streaming data collection and
analysis that are limited by a single server (although you can
always replicate your data to another server using the standard
MySQL Replication). ScaleDB Cluster instead, is highly …
With MySQL it is relatively easy to create point in time restores. All you need is a recent(ish) backup, and a bunch of saved binary logs. You can restore the backup you have, and when it is completed, you can use mysqlbinlog utility to apply your saved binary logs to the desired state of your database. I […]