MySQL备份和同步时使用LVM

核心提示： Low Overhead It is simply file copy so overhead to the server is minimal.低开销 只是文件拷贝，因此对服务器的开销很细微，MySQL备份和同步时使用LVM(2)，Easy to Integrate Do you wan

Low Overhead It is simply file copy so overhead to the server is minimal.

低开销 只是文件拷贝，因此对服务器的开销很细微。

Easy to Integrate Do you want to compress backup ? Backup it to tape, FTP or any network backup software - it is easy as you just need to copy files.

容易保持完整性 想要压缩备份文件吗？把它们备份到磁带上，FTP或者网络备份软件 -- 十分简单，因为只需要拷贝文件即可。

Fast Recovery Recovery time is as fast as putting data back and standard MySQL crash recovery, and it can be reduced even further. More on this later.

快速恢复 恢复的时间和标准的MySQL崩溃恢复或数据拷贝回去那么快，甚至可能更快，将来会更快。

Free No extra commercial tools as Innodb Hot Backup are required to perform backup.

免费 无需额外的商业软件，只需Innodb热备工具来执行备份。

Are there any downsides ?

有什么缺点吗？

Need to have snapshot campatibility - this is obvious one.

需要兼容快照 -- 这是明显的。

May need root access In some organizations DBA and System Administrator are different people from different departmnents which might not like to trade access rights between each other.

需要超级用户(root) 在某些组织，DBA和系统管理员来自不同部门不同的人，因此权限各不一样。

Hard to predict downtime I mentioned this solution is often hot backup, but bad thing it is hard to estimate when it is hot and when it is not - FLUSH TABLES WITH READ LOCK may take quite a while to complete on systems with long queries.