简体   繁体   English

备份和恢复多个MySQL数据库(InnoDB和MyISAM)

[英]Backup & recovery of multiple MySQL databases (InnoDB & MyISAM)

I am working on nightly and hourly backups of MySQL Databases. 我正在每天和每小时备份MySQL数据库。 There are multiple MySQL databases which are either InnoDB or MyISAM (Note: Each database is either InnoDB or MyISAM for a reason). 有多个MySQL数据库,它们是InnoDB或MyISAM(注意:由于某种原因,每个数据库都是InnoDB或MyISAM)。 With the 2 different types I want to make sure I am grabbing everything that is needed for backup and recovery. 我想使用2种不同的类型来确保我掌握了备份和恢复所需的一切。 Here is my current plan 这是我目前的计划

Nightly -mysqldump of each DB which is stored locally and remotely. 每个数据库的每晚-mysqldump,本地和远程存储。

Hourly -flush binary logs and store them locally and remotely. 每小时-刷新二进制日志并将其本地和远程存储。

Weekly -expire binary logs older than a week. 每周-过期的二进制日志超过一周。

I feel like I am grabbing everything that is needed for the MyISAM databases but I am concerned about the InnoDB databases and the log files (ib_logfile0, ib_logfile1, ibdata1) they create. 我感觉好像在抓取MyISAM数据库所需的所有内容,但是我担心InnoDB数据库及其创建的日志文件(ib_logfile0,ib_logfile1,ibdata1)。 Should I backup these files? 我应该备份这些文件吗? Nightly? 每晚? Hourly? 每小时一次? Both? 都? Do I really need them if I am already doing the above nightly and hourly backups? 如果我已经进行了上述每晚和每小时的备份,我真的需要它们吗?

You should try SQLyog -- MySQL GUI . 您应该尝试使用SQLyog-MySQL GUI It's sja component makes scheduling backups/synchronization pretty smooth for users, and it also available in a Community Edition. 它的sja组件使用户的备份/同步安排非常顺利,并且在Community Edition中也可以使用。

Disclaimer: I work for Webyog, Inc -- The publishers of SQLyog. 免责声明:我为Webyog,Inc工作-SQLyog的发行商。

Edit: I'd also like to add that I find it very reliable and fail-safe and use to manage production servers. 编辑:我还想补充一点,我发现它非常可靠且具有故障保护功能,可用于管理生产服务器。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM