The file format was designed as to allow to have a verbatim copy of the file on both nodes of the cluster. It is highly recommended to do so in order to keep your configuration manageable. In this example, there is a single DRBD resource called r0 which uses protocol C for the connection between its devices. The IP addresses are used to specify the networking interfaces to be used. There may be multiple resource sections in a single drbd.
|Published (Last):||20 May 2015|
|PDF File Size:||12.89 Mb|
|ePub File Size:||4.40 Mb|
|Price:||Free* [*Free Regsitration Required]|
Feedback from readers is always welcome and encouraged. Please use the DRBD public mailing list  for enhancement suggestions and corrections. Recent content additions are marked with Draft status; feedback on those sections is particularly highly appreciated.
License information The text of and illustrations in this document are licensed under a Creative Commons Attribution—Share Alike 3. Citrix is a registered trademark of Citrix, Inc. Debian is a registered trademark of Software in the Public Interest, Inc. Intel is a registered trademark of Intel Corporation. Linux is a registered trademark of Linus Torvalds. Xen is a registered trademark of Citrix, Inc. Other names mentioned in this guide may be trademarks or registered trademarks of their respective owners.
Introduction to DRBD DRBD Fundamentals Kernel module User space administration tools Resource roles DRBD Features Single-primary mode Dual-primary mode Replication modes Multiple replication transports Efficient synchronization On-line device verification Replication traffic integrity checking Split brain notification and automatic recovery Support for disk flushes Disk error handling strategies Strategies for dealing with outdated data Three-way replication Truck based replication Floating peers Building, installing and configuring DRBD Installing pre-built DRBD binary packages Packages supplied by distribution vendors Building and installing DRBD from source Downloading the DRBD sources Checking out sources from the public DRBD source repository Building DRBD from source Checking build prerequisites Preparing the kernel source tree Preparing the DRBD build tree Building DRBD userspace utilities Compiling DRBD as a kernel module Configuring DRBD Preparing your lower-level storage Preparing your network configuration Configuring your resource Example configuration The global section The common section The resource sections Enabling your resource for the first time The initial device synchronization Using truck based replication Working with DRBD Common administrative tasks Checking DRBD status Retrieving status with drbd-overview Connection states Disk states Enabling and disabling resources Enabling resources Disabling resources Reconfiguring resources Promoting and demoting resources Enabling dual-primary mode Using on-line device verification Enabling on-line verification Invoking on-line verification Automating on-line verification Configuring the rate of synchronization Permanent syncer rate configuration Temporary syncer rate configuration Configuring checksum-based synchronization Configuring replication traffic integrity checking Resizing resources Growing on-line Growing off-line Shrinking on-line Shrinking off-line Disabling backing device flushes Configuring split brain behavior Split brain notification Automatic split brain recovery policies Creating a three-node setup Device stacking considerations Configuring a stacked resource Enabling stacked resources DRBD Proxy deployment considerations License file Troubleshooting and error recovery Dealing with hard drive failure Manually detaching DRBD from your hard drive Replacing a failed disk when using internal meta data Replacing a failed disk when using external meta data Dealing with node failure Dealing with temporary secondary node failure Dealing with temporary primary node failure Dealing with permanent node failure Manual split brain recovery
Please use this content only as a guideline. However you could install the drbd package at this moment version 8. The data marked with bold italic is the one that must be replaced with actual data from your specific setup. The commands must be issued on both nodes. Next, you have to initialize the DRBD resource meta data. This need to be done before a DRBD resource can be taken online for the first time, thus only on initial device creation:.
How to Setup DRBD to Replicate Storage on Two CentOS 7 Servers
If you use the size parameter in drbd. When selecting the method you should not only base your decision on the measurable performance. In case your backing storage device has a volatile write cache plain disks, RAID of plain disks you should use one of the first two. In case your backing storage device has battery-backed write cache you may go with option 3.