/usr/share/doc/drbd-doc/users-guide/s-using-truck-based-replication.html is in drbd-doc 8.4~20151102-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 | <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6. Using truck based replication</title><link rel="stylesheet" type="text/css" href="default.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="home" href="drbd-users-guide.html" title="The DRBD User’s Guide" /><link rel="up" href="ch-configure.html" title="Chapter 5. Configuring DRBD" /><link rel="prev" href="s-initial-full-sync.html" title="5.5. The initial device synchronization" /><link rel="next" href="p-work.html" title="Part III. Working with DRBD" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">5.6. Using truck based replication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="s-initial-full-sync.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Configuring DRBD</th><td width="20%" align="right"> <a accesskey="n" href="p-work.html">Next</a></td></tr></table><hr /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="s-using-truck-based-replication"></a>5.6. Using truck based replication</h2></div></div></div><p>In order to preseed a remote node with data which is then to be kept
synchronized, and to skip the initial device synchronization, follow
these steps.</p><p>This assumes that your local node has a configured, but disconnected
DRBD resource in the Primary role. That is to say, device
configuration is completed, identical <code class="literal">drbd.conf</code> copies exist on both
nodes, and you have issued the commands for
<a class="link" href="s-initial-full-sync.html" title="5.5. The initial device synchronization">initial resource promotion</a> on your local node — but the remote node is not connected yet.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
On the local node, issue the following command:
</li></ul></div><pre class="screen"># drbdadm new-current-uuid --clear-bitmap <resource></pre><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Create a consistent, verbatim copy of the resource’s data <span class="emphasis"><em>and its
metadata</em></span>. You may do so, for example, by removing a hot-swappable
drive from a RAID-1 mirror. You would, of course, replace it with a
fresh drive, and rebuild the RAID set, to ensure continued
redundancy. But the removed drive is a verbatim copy that can now be
shipped off site. If your local block device supports snapshot
copies (such as when using DRBD on top of LVM), you may also create
a bitwise copy of that snapshot using <code class="literal">dd</code>.
</li><li class="listitem">
On the local node, issue:
</li></ul></div><pre class="screen"># drbdadm new-current-uuid <resource></pre><p>Note the absence of the <code class="literal">--clear-bitmap</code> option in this second
invocation.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Physically transport the copies to the remote peer location.
</li><li class="listitem">
Add the copies to the remote node. This may again be a matter of
plugging a physical disk, or grafting a bitwise copy of your shipped
data onto existing storage on the remote node. Be sure to restore
or copy not only your replicated data, but also the associated DRBD
metadata. If you fail to do so, the disk shipping process is moot.
</li><li class="listitem">
Bring up the resource on the remote node:
</li></ul></div><pre class="screen"># drbdadm up <resource></pre><p>After the two peers connect, they will not initiate a full device
synchronization. Instead, the automatic synchronization that now
commences only covers those blocks that changed since the invocation
of <code class="literal">drbdadm --clear-bitmap new-current-uuid</code>.</p><p>Even if there were <span class="emphasis"><em>no</em></span> changes whatsoever since then, there may still
be a brief synchronization period due to areas covered by the
<a class="link" href="s-activity-log.html" title="17.3. The Activity Log">Activity Log</a> being rolled back on the new
Secondary. This may be mitigated by the use of
<a class="link" href="s-resync.html#p-checksum-sync">checksum-based synchronization</a>.</p><p>You may use this same procedure regardless of whether the resource is
a regular DRBD resource, or a stacked resource. For stacked resources,
simply add the <code class="literal">-S</code> or <code class="literal">--stacked</code> option to <code class="literal">drbdadm</code>.</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="s-initial-full-sync.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch-configure.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="p-work.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">5.5. The initial device synchronization </td><td width="20%" align="center"><a accesskey="h" href="drbd-users-guide.html">Home</a></td><td width="40%" align="right" valign="top"> Part III. Working with DRBD</td></tr></table></div></body></html>
|