Send to Kindle

Hi guys, today let’s learn about how to have a consistent backup (snapshot)
First of all, in what situations do we use a snapshot?

1. Lets say that your production server now will have a replica, how do you do the first load of data in this slave? what was the master bin log position when you started the backup, during the backup process, does anyone wrote any query to db?

2. In case you want to implement an incremental backup strategy, you can take a snapshot once a week and in case you need to restore you server, you just restore the snapshot and apply the binary logs.

Then, let’s start.

To grantee this data integrity we will need 2 sessions open on master, first one to lock all databases, second one to do the copy

Then, let’s go:

Session 1:

FLUSH TABLES WITH READ LOCK;
SHOW MASTER STATUS;

You will receive an output like this:

Setting up MASTER and SLAVE replication in MySQL. MASTER The replication master must have binary logging enable and needs to have a unique server ID. 1. Turn on binary logging. Edit /etc/my.cnf and make the following entries in the section [mysqld]. [mysqld] log-bin=mysql-bin server-id=1 2. Restart mysql. root@test:~# /etc/init.d/mysqld restart 3. Create Access Create an [...]

First conference of the year is always a bit of a thrash for me. This time I have and RMOUG Training Days back to back. So I went to upgrade MySQL on my presentation laptop and got a pleasant surprise.

The MySQL 5.6 upgrade included not only the server but connectors and workbench

I had planned to install 5.6, the connectors, the docs, and Workbench separately as I packed. Low and behold. the upgrade did all the work for me. Very cool!

Except the packing. That I still got to do! See you in Miami and Denver.

This was nice to see all the MySQL ecosystem in the same very crowded room : Oracle, Percona, MariaDB, SkySQL. We definitely need this kind of open event. MySQL Connect (owned by Oracle) or Percona Live (owned by Percona) are 2 great events but they do not gather the same variety of speakers and attendees. [...]

Oracle launches MySQL 5.6. IBM expands PureData line. And more

For 451 Research clients: IBM adds to PureData family with new Netezza-based system for analytics bit.ly/UXhZ8G

— Matt Aslett (@maslett) February 6, 2013

For 451 clients: Panopticon illuminates real-time visual analysis business, rides SAP’s HANA coattails bit.ly/YQpemt By Krishna Roy

— Matt Aslett (@maslett) February 5, 2013

Oracle Announces General Availability of MySQL 5.6 mwne.ws/XTC2Se

— Matt Aslett (@maslett) February 5, …

Extract from THE SCALE-OUT BLOG by Robert Hodges (CEO, Continuent)http://scale-out-blog.blogspot.com Data management is undergoing a revolution. Many businesses now depend on data sets that vastly exceed the capacity of DBMS servers. Applications operate 24x7 in complex cloud environments using small and relatively unreliable VMs. Managers need to act on new information from those systems in

In a world driven by computers, most companies rely on systems that are entirely built around databases. Losing data, or even as little as losing the full control over it, could bring any business down. Frequently databases hold sensitive information such as personal details, transaction statements, credit card data – among many other things. This is also why running certain types of databases is regulated in many countries by local as well as international laws – especially in Europe.

What is at stake?

• Availability. When a database or data disappear, business stops. Assuming you have working backups you can restore from, this is the least of all concerns.
• Confidentiality. Your secrets, private information of your customers and anything else that you decided not to make publicly available may be leaked.
• Privacy. Personal …

Thousands of new online and mobile apps launch every day…but what happens when demand climbs and databases can’t keep up?

  Matt Aslett of 451 Research will discuss:

Scaling-out your MySQL databases New high availability strategies Centrally managing a distributed MySQL environment

Matt is the Research Director for Data Management and Analytics at 451 Research, covering operational and analytic databases, with a [...] Read More

The MySQL team seems to have a very peculiar idea about defaults and compatibility. Recently, I wrote about an annoying warning that cannot be removed. And previously, I noticed that MySQL 5.6 mixes warnings, info lines and errors in the same bunch of excessive chattiness.

With MySQL 5.5.30 came another headache. When I run a mysqldump of the 'mysql' schema, I get this warning:

$. mysqldump mysql > m.sql
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.

OK. No big deal. What if I tell the little troublemaker that I DON'T WANT the events table?

$ mysqldump --skip-events mysql > m.sql
-- Warning: Skipping the data of table …

MySQL 5.6 is the latest production-ready release of the most popular opensource database management system on the planet ie. MySQL.