May 24, 2012

Post: How would you compress your MySQL Backup

backup impact on server performance may well be). We also assume backup is done on physical level here (cold backup, slave backup, innodb hot backup or snapshot backupall archivers it is possible to use parallel compression to get

Post: Using LVM for MySQL Backup and Replication Setup

MySQL backups are great ? There are number of reasons: Almost Hot backup In most cases you can perform this type of backup while your application is running. No need to shut down server

Post: Faster MySQL failover with SELECT mirroring

MySQL Cluster, which is more special-purpose, this is probably the best general-purpose way to getto get good performance after a failover. You need to use some technique to mirror the read-only workload to the passive server

Post: How SHOW SLAVE STATUS relates to CHANGE MASTER TO

to get the “snapshot” – shutting down MySQL Server and copying data, using LVM, Using Innodb Hot Backup Tool, Using another Slave, using backup image etc but in all the cases you have to

Post: Should you move from MyISAM to Innodb ?

get to deal with recovering tables on the crash or partially executed statements. Table locks is no more problem, hot backupsservers. It is important the team understands Innodb and knows how to handle it, or be able to learn it. It is also important to

Post: Side load may massively impact your MySQL Performance

to spare. We’re using Percona Servermysql-password=msandbox –mysql-socket=/tmp/mysql_sandbox5516.sock prepare Running Sysbench and MySQLDump. Note we run them in the loop to see how

Post: Estimating Replication Capacity

to work. Get the log file which will include all queries MySQL server ran with their times and run mk-query-digest with filter tohow fast do you need to be able to recover from backups and how