Hello Jens, Wednesday, March 27, 2002, 2:43:22 PM, you wrote:
We have tried to use DRBD with MySQL/EXT3/NFS and some other applications. Generally it works rather good, showing rather nice performance. The only problem we had was problem with EXT3 corruption, which was in earlier (2-3 months) versions. So You should test carefully how it will work with your environment, including the processes of fallback/recover during the notable load. Also the problem with MySQL is you will need to check the tables before using them if you're using MYISAM, therefore using INNODB or BDB will help to recover mysql quite fast. Also you may note with MySQL replication you may execute "select" queries on Slave, which is really nice solution for statistical scripts which may execute long selects or database backup. In case with DRBD you will miss it. On other side in this case you will not have any need to care about some features which have trouble with replication - like "load data infile", variables etc. Also a good thing with DRBD you will not have to store and track replication log files and the setup will not require to take MySQL down to copy the snapshot of database. JV> has anyone used DRDB (http://www.linbit.com/) instead of the standard MySQL JV> replication? JV> DRDB implements a virtual disk mirrored across a local disk and a disk in a JV> remote stand-by server. JV> On first thought, it adds some complexity to setup, but it can also JV> replicate information not written to MySQL but e.g. directly to the JV> filesystem. JV> Any thoughts on this? -- Best regards, Peter mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
