I really appreciate everyone's input but everyone misunderstood the question I was really asking. It's my fault for mentioning rsync. I fully understand the difference between how rsync works and how drbd works. We use them both all the time. But the real question is more high level. We have been told that even if you stop the mysql service, you still cannot backup an innodb database by simply copying the files from one server to another. We have been told that the mysql service will not start properly on the new server even if you make a 100% exact copy of all the files from the old server. If that is true, I don't understand how using drbd can work with innodb tables, since it basically just makes a copy of the files to another server. Am I asking the question right?
-- Eric Robinson ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Adam Goryachev Sent: Wednesday, June 12, 2013 6:58 PM To: [email protected] Subject: Re: [DRBD-user] drbd+mysql+innodb On 13/06/13 10:37, Dan Barker wrote: rsync will not be able to synchronize from a "failed" disk, drbd already has done so. Dan in Atlanta From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Robinson, Eric Sent: Wednesday, June 12, 2013 6:20 PM To: Dirk Bonenkamp - ProActive Cc: [email protected]<mailto:[email protected]> 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. I think the real issue with rsync is that it will start copying the file, but new writes may come in during the copy process, therefore the destination copy is not a point in time copy of the source. This is the same issue with using rsync for disk images of VM's that are running during the rsync. As explained, this is not an issue for DRBD replication, because at any instant in time, the replica (destination copy) is an exact copy of the source at some point in time, even if it is not the latest point in time. Regards, Adam -- Adam Goryachev Website Managers www.websitemanagers.com.au<http://www.websitemanagers.com.au> Disclaimer - June 12, 2013 This email and any files transmitted with it are confidential and intended solely for 'Adam Goryachev',[email protected]. 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. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
_______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
