Comments on: Using LVM for MySQL Backup and Replication Setup http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/ Everything about MySQL Performance Sat, 21 Nov 2009 05:23:57 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Pet Pixels http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-651668 Pet Pixels Fri, 11 Sep 2009 11:17:35 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-651668 <strong>MySQL backups with Percona's XtraBackup...</strong> MySQL backup is sometimes very hard to do effectively. MySQL provides various options for backup, but many of them are simply unsuitable for large systems, particularly if they need to remain active during backups. Percona's XtraBackup is an open-sour... MySQL backups with Percona’s XtraBackup…

MySQL backup is sometimes very hard to do effectively. MySQL provides various options for backup, but many of them are simply unsuitable for large systems, particularly if they need to remain active during backups. Percona’s XtraBackup is an open-sour…

]]> By: frank http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-644635 frank Tue, 01 Sep 2009 12:43:43 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-644635 modprobe dm-snapshot saved my life. Thanks Frank modprobe dm-snapshot
saved my life.

Thanks
Frank

]]> By: Running MySQL on Amazon EC2 with Elastic Block Store http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-457819 Running MySQL on Amazon EC2 with Elastic Block Store Wed, 28 Jan 2009 04:07:13 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-457819 [...] Resources Feature Guide: Elastic Block StoreAmazon EC2 Developer Guide (Elastic Block Store)Amazon EC2 Getting Started Guide (running and connecting to instances)XFS file systemUbuntu and Debian AMIs for Amazon EC2MySQL snapshots and replication info [...] [...] Resources Feature Guide: Elastic Block StoreAmazon EC2 Developer Guide (Elastic Block Store)Amazon EC2 Getting Started Guide (running and connecting to instances)XFS file systemUbuntu and Debian AMIs for Amazon EC2MySQL snapshots and replication info [...]

]]> By: http://emailtoid.net/i/19c03518/bfbcf292/ http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-447158 http://emailtoid.net/i/19c03518/bfbcf292/ Fri, 16 Jan 2009 22:37:21 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-447158 Trying to decide if I want to move away from innodb hot backup. 1) I saw that I can skip the FLUSH TABLES WITH READ LOCK for my Innodb tables, but I also noticed the warning: "If you're using only Innodb tables and do not need to synchronize binary log position with backup you can skip this step." If I want to use that backup to restore a db for use as a replication slave, will that work? Will the binary log postion sync mentioned above create a problem? 2) I have a mix of MyISAM and Innodb, but mostly Innodb, is there a work around for this so I don't have to run the FLUSH TABLES WITH READ LOCK? Trying to decide if I want to move away from innodb hot backup.
1) I saw that I can skip the FLUSH TABLES WITH READ LOCK for my Innodb tables, but I also noticed the warning:
“If you’re using only Innodb tables and do not need to synchronize binary log position with backup you can skip this step.”
If I want to use that backup to restore a db for use as a replication slave, will that work? Will the binary log postion sync mentioned above create a problem?
2) I have a mix of MyISAM and Innodb, but mostly Innodb, is there a work around for this so I don’t have to run the FLUSH TABLES WITH READ LOCK?

]]> By: peter http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-446897 peter Fri, 16 Jan 2009 06:55:22 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-446897 It is Baron who replied to you, but thanks anyway. We're both Authors and I bet both glad to hear you like the book. It is Baron who replied to you, but thanks anyway. We’re both Authors and I bet both glad to hear you like the book.

]]> By: Mike http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-446456 Mike Thu, 15 Jan 2009 19:38:01 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-446456 Peter, Thanks for the quick response!! Great resource here! By the way, I have your book "High Performance MySQL 2nd Edition" in the bookshelf within reach. Definitely the best MySQL book out there presently! Thanks again!! Peter,

Thanks for the quick response!! Great resource here!

By the way, I have your book “High Performance MySQL 2nd Edition” in the bookshelf within reach. Definitely the best MySQL book out there presently!

Thanks again!!

]]> By: Baron Schwartz http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-446403 Baron Schwartz Thu, 15 Jan 2009 14:35:06 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-446403 Mike, You are correct. However, the worst-case is that the MyISAM tables would be corrupt (more likely that just their indexes would be corrupt) and need repairing. There could be missing records or half-written records depending on when you take the snapshot. And MySQL will start just fine, since a MyISAM table is "just a file" ;-) I mean you could do this: "touch /var/lib/mysql/test/thisisnotatable.{MYI,MYD,frm}" and start MySQL, and it would start fine and SHOW TABLES would show test.thisisnotatable but accessing it would cause an error. Mike,

You are correct. However, the worst-case is that the MyISAM tables would be corrupt (more likely that just their indexes would be corrupt) and need repairing. There could be missing records or half-written records depending on when you take the snapshot. And MySQL will start just fine, since a MyISAM table is “just a file” ;-)

I mean you could do this: “touch /var/lib/mysql/test/thisisnotatable.{MYI,MYD,frm}” and start MySQL, and it would start fine and SHOW TABLES would show test.thisisnotatable but accessing it would cause an error.

]]> By: Mike http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-446119 Mike Thu, 15 Jan 2009 03:56:10 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-446119 Peter, In post # 36 you make a quick "add on" statement that I want to confirm, because I think it's significant. So if you are "sure" you don't have any myisam tables and don't do DDL, and don't modify the mysql.* myisam tables, then "flush tables with read lock" is not needed? But if someone creates a couple of myisam tables that you don't know about, then those tables "may" not be consistent, right? If that case occurred in Oracle, then the instance would not start after doing a restore. But is this the case in MySQL? What is the worse case in MySQL? Does it just mean that there may be missing records in those MyISAM tables? Or could there be corrupted data that would cause database problems. In Oracle, the instance won't even start if the header "timestamps" don't match on all the tablespaces. I just want to be really clear on this! What does "inconsistent" mean for "user" (non mysql.*) tables? Thanks, Mike Peter,

In post # 36 you make a quick “add on” statement that I want to confirm, because I think it’s significant.

So if you are “sure” you don’t have any myisam tables and don’t do DDL, and don’t modify the mysql.* myisam tables, then “flush tables with read lock” is not needed? But if someone creates a couple of myisam tables that you don’t know about, then those tables “may” not be consistent, right?

If that case occurred in Oracle, then the instance would not start after doing a restore. But is this the case in MySQL? What is the worse case in MySQL? Does it just mean that there may be missing records in those MyISAM tables? Or could there be corrupted data that would cause database problems. In Oracle, the instance won’t even start if the header “timestamps” don’t match on all the tablespaces.

I just want to be really clear on this! What does “inconsistent” mean for “user” (non mysql.*) tables?

Thanks,
Mike

]]> By: 使用LVM进行MySQL备份与复制 | Since 1980 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-406770 使用LVM进行MySQL备份与复制 | Since 1980 Wed, 10 Dec 2008 10:01:22 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-406770 [...] Using LVM for MySQL Backup and Replication Setup [...] [...] Using LVM for MySQL Backup and Replication Setup [...]

]]> By: peter http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/comment-page-1/#comment-345269 peter Sat, 16 Aug 2008 05:15:01 +0000 http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/#comment-345269 Richard, Indeed you can use log file size. Moreover if you have Innodb only tables you do not have to do flush tables with read locks. Unless you do DDL or modify mysql.* tables you should be fine. Richard,

Indeed you can use log file size. Moreover if you have Innodb only tables you do not have to do flush tables with read locks. Unless you do DDL or modify mysql.* tables you should be fine.

]]>