Ãâó :
http://danuri.tistory.com/1 http://oss.linbit.com/drbd/ http://www.drdb.orgDRBD(Distributed Replicated Block Device)DRBD¸¦ ½±°Ô ¼³¸íÇÏÀÚ¸é ³×Æ®¿öÅ© ±â¹ÝÀÇ RAID 1(Mirroring)À» ±¸ÇöÇØ ³õÀº °ÍÀ̶ó°í º¸¸é µÈ´Ù.
³×Æ®¿öÅ©·Î ¹°¸®ÀûÀ¸·Î ¶³¾îÁø µÎ´ëÀÇ ¼¹öÀÇ Çϵåµð½ºÅ© OR ÆÄƼ¼ÇÀ» ¹Ì·¯¸µ ±¸¼ºÀ» ÇÑ°ÍÀÌ´Ù.
Ŭ·¯½ºÅ͸µ ±¸¼º¿¡ LVS ¹æ½ÄÀº À¥¼¹öÀÏ°æ¿ì ½Ã½ºÅÛÀÌ Á×À»°æ¿ì ´Ù¸¥ ½Ã½ºÅÛÀÌ Ä¿¹ö°¡ °¡´ÉÇÏ°ÚÁö¸¸ ¹®Á¦´Â Ç×»ó ÀÏÁ¤ÇÏ°Ô µ¿±âÈ µÇ¾î¾ß ÇÏ´Â µ¥ÀÌŸº£À̽º³ª ÆÄÀÏ/À̹ÌÁö ¼¹ö°¡ Á×¾úÀ»°æ¿ì ÀÌ´Ù.
¹°·Ð µ·À» ¸¹ÀÌ µé¿©¼ ½ºÅ丮Áö µÎ°³ »ç¼ ÀÌÁßÈ ¼Ö·ç¼Ç ±¸¸ÅÇÏ¿© »ç¿ëÇÒ ¼ö µµ ÀÖÁö¸¸ ¼ÒÇÁÆ®¿þ¾îÀûÀ¸·Î Çѹø 󸮸¦ ÇØ º¼ ¼ö ÀÖ´Â ¹æ¹ýÀ» ã¾Æ º¼ ¼öµµ ÀÖ´Ù. ±× ÇØ´äÁßÀÇ Çϳª·Î DRBD ¸¦ »ç¿ë ÇÒ ¼ö ÀÖ´Ù.
DRBD ´Â ½ºÅ丮Áö ÀÌÁßȶó°í »ý°¢Çصµ µÈ´Ù.
ÀÌ°Ô ÆÄÀÏ º£À̽º·Î ¿òÁ÷ÀÌ´Â°Ô ¾Æ´Ï¶ó ºí·° ·¹º§¿¡¼ º¹Á¦°¡ µÈ´Ù.
½ÉÇÃÇÑ ±¸¼ºÀ» »ý°¢ÇØ
º¸¸é,
DRBD¸¦ ÀÌ¿ëÇÏ¿© ½ºÅ丮Áö¿ëÀ¸·Î ÇÏµå ¿ë·®ÀÌ Å« ¼¹ö µÎ´ë¸¦ »ç¿ëÇϴµ¥ Heartbeat ¸¦ ÀÌ¿ëÇÏ¿© Active/Standby ÇüÅ·Π±¸¼ºÀ» ÇÑ´Ù. DRBD script Á¦¾î¸¦ Heartbeat ¿¡°Ô ¸Â°Ü µÎ°í °¡»ó ¾ÆÀÌÇǸ¦ ÇÑ°³ »ç¿ëÇÏ¿© ¿ÜºÎ¿¡¼´Â °¡»ó ¾ÆÀÌÇÇ·Î Á¢±ÙÀ» ÇÑ´Ù. ±×¸®°í ¿©±â µ¥ÀÌŸ¿¡ Á¢±ÙÀ» À§ÇØ NFS ¸¦ ÀÌ¿ëÇÏ¿© ¿ÜºÎ¿¡¼´Â »ç¿ëÀ» ÇÏ°ÔÇÑ´Ù. ¹°·Ð ÃßÈÄ ÆÛÆ÷¸Õ½ºµîÀ» °í·ÁÇÏ¿© open-iscsi, gnbd µî »óȲ¿¡ ¸Â°Ô »ç¿ëÀ» ÇÏ°Ô µÉ °ÍÀÌ´Ù. ÀÌ·¸°Ô ¸¸µé¾î ³õÀ¸¸é ÃÖ¼ÒÇÑ ½ºÅ丮Áö ¼¹ö°¡ ÇÑ´ë Á×´õ¶óµµ ´Ù¸¥ ÇÑ´ëÀÇ ¼¹ö°¡ º¹Á¦µÈ µ¿ÀÏÇÑ ³»¿ëÀÇ ÄÁÅÙÃ÷¸¦ °¡Áö°í Áö¼ÓÀûÀÎ ¼ºñ½º°¡ °¡´ÉÇÏ°Ô µÈ´Ù. ¹°·Ð ÃÖ¼ÒÀÇ ºñ¿ëÀ¸·Î ¸»ÀÌ´Ù.
Mysql ÀÇ °æ¿ì DRBD¸¦ °ø½ÄÀûÀ¸·Î Áö¿øÀ» ÇÏ°í ÀÖ¾ú´Ù.
http://mysql.com/drbdMysql Enterprise ¿ëÀ¸·Î HA ±¸¼º½Ã ÇϳªÀÇ ¹æ¹ýÀ¸·Î »ç¿ëÀ» ÇÏ°í ÀÖ¾ú´Ù.
DRBD ´Â linbit ȸ»ç¿¡¼ °ø½Ä ±â¼ú Áö¿øÀ» À¯·á·Î ÇÏ°í ÀÖ´Ù.
http://www.linbit.com/en/products-services/drbd/drbd-support/drbd-support/³ëµå´ç 1³â¿¡ ÃÖ¼Ò 300¸¸¿ø ÀÌ»óÀÇ ºñ¿ëÀÌ´Ù. º¸Åë silver Á¤µµ ¹Þ°í ÇÑ´ë·Î´Â ¿î¿µÀÌ ¾ÈµÇ¹Ç·Î µÎ ´ëÀÇ ¼¹ö¸¦ »ç¿ëÇÑ´Ù°í ÇÏ¿´À»¶§ 600*2 ÇÏ¿© 1200¸¸¿øÀÌ´Ù. °í ºÎ°¡°¡Ä¡ ±â¼ú Áö¿øÀÌ´Ù.
DRBD is a block device which is designed to build high availability clusters.
This is done by mirroring a whole block device via (a dedicated) network. You
could see it as a network raid-1.
DRBD takes over the data, writes it to the local disk and sends it to the other
host. On the other host, it takes it to the disk there.
The other components needed are a cluster membership service, which is supposed
to be heartbeat, and some kind of application that works on top of a block
device.
Each device (DRBD provides more than one of these devices) has a state, which
can be 'primary' or 'secondary'. On the node with the primary device the
application is supposed to run and to access the device (/dev/drbdX; used to be
/dev/nbX). Every write is sent to the local 'lower level block device' and to
the node with the device in 'secondary' state. The secondary device simply
writes the data to its lower level block device. Reads are always carried out
locally.
If the primary node fails, heartbeat is switching the secondary device into
primary state and starts the application there. (If you are using it with a
non-journaling FS this involves running fsck)
If the failed node comes up again, it is a new secondary node and has to
synchronise its content to the primary. This, of course, will happen whithout
interruption of service in the background.
And, of course, we only will resynchronize those parts of the device that
actually have been changed. DRBD has always done intelligent resynchronization
when possible. Starting with the DBRD-0.7 series, you can define an "active
set" of a certain size. This makes it possible to have a total resync time of
1--3 min, regardless of device size (currently up to 16TB), even after a hard
crash of an active node.
The ChangeLogs can be found here:
http://git.drbd.org/?p=drbd-8.0.git;a=blob;f=ChangeLog;hb=HEAD http://git.drbd.org/?p=drbd-8.3.git;a=blob;f=ChangeLog;hb=HEAD http://git.drbd.org/ The DRBD Homepage is
http://www.drbd.org/.