Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
rsync will not be able to synchronize from a "failed" disk, drbd already has done so. Dan in Atlanta From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Robinson, Eric Sent: Wednesday, June 12, 2013 6:20 PM To: Dirk Bonenkamp - ProActive Cc: drbd-user at lists.linbit.com Subject: Re: [DRBD-user] drbd+mysql+innodb Hi Dirk - Thanks for the feedback. I do need some clarification, though. DRBD replicates disk block changes to a standby volume. If the primary node suddenly fails, the cluster manager promotes the standby node to primary and starts the MySQL service. Logically, this seems exactly the same as simply rsyncing the data to the new server and starting the MySQL service. Why would it work with DRBD but not with rsync? Thanks for your patience while I explore this. Note: we have over 500 separate MySQL database instances using MyISAM. I am totally not stoked about the idea of using 300% more disk space and gobs more memory. -- Eric Robinson From: Dirk Bonenkamp - ProActive [mailto:dirk at proactive.nl] Sent: Wednesday, June 12, 2013 7:24 AM To: Robinson, Eric Cc: drbd-user at lists.linbit.com<mailto:drbd-user at lists.linbit.com> Subject: Re: [DRBD-user] drbd+mysql+innodb Hi Eric, We did the same conversion about a year ago. We run MySQL with InnoDB on a DRDB back-end. There's alot of stuff that's different between MyISAM and InnoDB, but the DRBD thing is the same. What you say about backups is correct, but this hasn't anything to do with DRBD. DRDB will do fine, some other quick non-DRDB things: - MySQL tuning is (even more) essential with InnoDB. - InnoDB tables use (a lot) more diskspace than MyISAM, our disk usage was nearly 300% of MyISAM's usage for the same dataset. - If you want performance, you want to be able to load your dataset in memory. Kind regards, Dirk Op 12-6-2013 15:44, Robinson, Eric schreef: We have been a MyISAM shop forever but we are considering switching to innodb. There is scant information available on using innodb with drbd. Are there special considerations and pitfalls? I have been told that it is not possible to backup innodb by doing a simple rsync of the data directory to another server like we can do with myisam. If that is true, what does that say about using innodb with drbd, which does essentially the same thing? -- Eric Robinson Disclaimer - June 12, 2013 This email and any files transmitted with it are confidential and intended solely for 'drbd-user at lists.linbit.com<mailto:drbd-user at lists.linbit.com>'. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com<mailto:drbd-user at lists.linbit.com> http://lists.linbit.com/mailman/listinfo/drbd-user -- [cid:image001.gif at 01CE67AC.9C400440]<http://www.proactive.nl> T 023 - 5422299 www.proactive.nl<http://www.proactive.nl> [cid:image002.gif at 01CE67AC.9C400440]<http://nl.linkedin.com/in/dirkbonenkamp> [My status]<skype:dirkbonenkamp?call> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130613/03418e37/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 3966 bytes Desc: image001.gif URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130613/03418e37/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1965 bytes Desc: image002.gif URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130613/03418e37/attachment-0001.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 755 bytes Desc: image003.png URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130613/03418e37/attachment.png>