Difference between revisions of "Drbd"
(Created page with "{{Entry |Name=drbd |Short description=Block device for building high-availability clusters |Full description='drbd' is a block device for building high-availability clusters. DRB...") |
(New version) |
||
| Line 3: | Line 3: | ||
|Short description=Block device for building high-availability clusters | |Short description=Block device for building high-availability clusters | ||
|Full description='drbd' is a block device for building high-availability clusters. 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 an application that works on top of a block device (ie, a filesystem and fsck). Each device has either a 'primary' or 'secondary' state. The application should run and access the device on the node with the primary device. Every write is sent to the local 'lower level block device' and to the node with the device in 'secondary' state. The secondary device then writes the data to its lower level block device. If the primary node fails, heartbeat is switching the secondary device into primary state and starts the application there. If the failed node comes up again, it is a new secondary node and will synchronise its content to the primary node whithout interruption of service in the background. Only those parts of the device that actually have been changed will resync. | |Full description='drbd' is a block device for building high-availability clusters. 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 an application that works on top of a block device (ie, a filesystem and fsck). Each device has either a 'primary' or 'secondary' state. The application should run and access the device on the node with the primary device. Every write is sent to the local 'lower level block device' and to the node with the device in 'secondary' state. The secondary device then writes the data to its lower level block device. If the primary node fails, heartbeat is switching the secondary device into primary state and starts the application there. If the failed node comes up again, it is a new secondary node and will synchronise its content to the primary node whithout interruption of service in the background. Only those parts of the device that actually have been changed will resync. | ||
| + | |Homepage URL=http://www.drbd.org/ | ||
|User level=none | |User level=none | ||
| − | |||
| − | |||
| − | |||
| − | |||
|Computer languages=C | |Computer languages=C | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|Keywords=synchronize,device,secondary,node,block,cluster,heartbeat,high availability,membership service,primary | |Keywords=synchronize,device,secondary,node,block,cluster,heartbeat,high availability,membership service,primary | ||
| − | | | + | |Version identifier=9.0.1-1 |
| − | |Last review by= | + | |Version date=2016/02/03 |
| − | |Last review date= | + | |Version status=stable |
| + | |Version download=http://oss.linbit.com/drbd/9.0/drbd-9.0.1-1.tar.gz | ||
| + | |Last review by=Alejandroindependiente | ||
| + | |Last review date=2017/03/13 | ||
|Submitted by=Database conversion | |Submitted by=Database conversion | ||
|Submitted date=2011-04-01 | |Submitted date=2011-04-01 | ||
| − | | | + | |Status= |
| − | | | + | |Is GNU=No |
| − | | | + | |License verified date=2005-02-02 |
| − | | | + | }} |
| + | {{Project license | ||
| + | |License=GPLv2orlater | ||
| + | |License verified by=Janet Casey | ||
|License verified date=2005-02-02 | |License verified date=2005-02-02 | ||
| − | |||
}} | }} | ||
{{Person | {{Person | ||
| + | |Real name=Philipp Reisner | ||
|Role=Maintainer | |Role=Maintainer | ||
| − | |||
|Email=philipp.reisner@linbit.com | |Email=philipp.reisner@linbit.com | ||
|Resource URL= | |Resource URL= | ||
}} | }} | ||
{{Person | {{Person | ||
| + | |Real name=Lars Ellenberg | ||
|Role=Contributor | |Role=Contributor | ||
| − | |||
|Email=l.g.e@web.de | |Email=l.g.e@web.de | ||
|Resource URL= | |Resource URL= | ||
| Line 59: | Line 55: | ||
|Internet-application=tool | |Internet-application=tool | ||
|Software-development=small-specific-development-task | |Software-development=small-specific-development-task | ||
| − | |Use=internet-application,software-development | + | |Use=internet-application, software-development |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
| + | {{Featured}} | ||
Revision as of 12:39, 13 March 2017
drbd
http://www.drbd.org/
Block device for building high-availability clusters
'drbd' is a block device for building high-availability clusters. 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 an application that works on top of a block device (ie, a filesystem and fsck). Each device has either a 'primary' or 'secondary' state. The application should run and access the device on the node with the primary device. Every write is sent to the local 'lower level block device' and to the node with the device in 'secondary' state. The secondary device then writes the data to its lower level block device. If the primary node fails, heartbeat is switching the secondary device into primary state and starts the application there. If the failed node comes up again, it is a new secondary node and will synchronise its content to the primary node whithout interruption of service in the background. Only those parts of the device that actually have been changed will resync.
Licensing
License
Verified by
Verified on
Notes
Leaders and contributors
| Contact(s) | Role |
|---|---|
| Philipp Reisner | Maintainer |
| Lars Ellenberg | Contributor |
Resources and communication
| Audience | Resource type | URI |
|---|---|---|
| Help | mailto:drbd-announce@lists.linbit.com | |
| Support | mailto:drbd-user@lists.linbit.com | |
| Developer | mailto:drbd-dev@lists.linbit.com | |
| Ruby (Ref) | https://rubygems.org/gems/drbd | |
| Debian (Ref) | https://tracker.debian.org/pkg/drbd |
Software prerequisites
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.