Debian Codegraph @

UG9/cn/administration-drbdmanage.po

raw
1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5 #
6 #, fuzzy
7 msgid ""
8 msgstr ""
9 "Project-Id-Version: PACKAGE VERSION\n"
10 "POT-Creation-Date: 2020-03-02 15:09+0000\n"
11 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13 "Language-Team: LANGUAGE <[email protected]>\n"
14 "Language: \n"
15 "MIME-Version: 1.0\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: 8bit\n"
18
19 #. type: Title ==
20 #: administration-drbdmanage.adoc:2
21 #, no-wrap
22 msgid "DRBD Manage"
23 msgstr "DRBD Manage"
24
25 #. type: Plain text
26 #: administration-drbdmanage.adoc:6
27 msgid ""
28 "DRBD Manage will reach its EoL end of 2018 and will be replaced by LINSTOR."
29 msgstr "DRBD Manage将于2018年底结束,并将由LINSTOR取代。"
30
31 #. type: Plain text
32 #: administration-drbdmanage.adoc:12
33 msgid ""
34 "DRBD Manage is an abstraction layer which takes over management of logical "
35 "volumes (LVM) and management of configuration files for DRBD. Features of "
36 "DRBD Manage include creating, resizing, and removing of replicated volumes."
37 " Additionally, DRBD Manage handles taking snapshots and creating volumes in"
38 " consistency groups."
39 msgstr ""
40 "DRBD-Manage是一个抽象层,它接管了DRBD的逻辑卷(LVM)管理和配置文件管理。DRBD "
41 "Manage的功能包括创建、调整大小和删除复制卷。此外,DRBD Manage还处理在一致性组中创建快照和卷的操作。"
42
43 #. type: Plain text
44 #: administration-drbdmanage.adoc:17
45 msgid ""
46 "This chapter outlines typical administrative tasks encountered during day-"
47 "to-day operations. It does not cover troubleshooting tasks, these are "
48 "covered in detail in <<ch-troubleshooting>>. If you plan to use 'LVM' as "
49 "storage plugin, please see read section <<s-config-lvm>> *now*, and then "
50 "return to this point."
51 msgstr ""
52 "本章概述了日常运营中遇到的典型管理任务。它不包括故障排除任务,这些任务在<<ch-"
53 "troubleshooting>>中有详细介绍。如果您打算使用 `LVM` 作为存储插件,请参阅阅读部分<<s-config-"
54 "lvm>>,然后返回到这里。"
55
56 #. type: Title ===
57 #: administration-drbdmanage.adoc:19
58 #, no-wrap
59 msgid "Migrating resources from DRBDManage to LINSTOR"
60 msgstr "将资源从DRBDManage迁移到LINSTOR"
61
62 #. type: Plain text
63 #: administration-drbdmanage.adoc:23
64 msgid ""
65 "The LINSTOR client contains a sub-command that can generate a migration "
66 "script that adds existing DRBDManage nodes and resources to a LINSTOR "
67 "cluster. Migration can be done without downtime. If you do not plan to "
68 "migrate existing resources, continue with the next section."
69 msgstr ""
70 "LINSTOR客户机包含一个子命令,可以生成一个迁移脚本,该脚本将现有DRBDManage节点和资源添加到LINSTOR集群。迁移可以在不停机的情况下完成。如果不打算迁移现有资源,请继续下一节。"
71
72 #. type: Plain text
73 #: administration-drbdmanage.adoc:33
74 msgid ""
75 "The first thing to check is if the DRBDManage cluster is in a healthy state."
76 " If the output of `drbdmanage assignments` looks good, you can export the "
77 "existing cluster database via `drbdmanage export-ctrlvol > ctrlvol.json`. "
78 "You can then use that as input for the LINSTOR client. The client does *not*"
79 " immediately migrate your resources, it just generates a shell script. "
80 "Therefore, you can run the migration assistant multiple times and "
81 "review/modify the generated shell script before actually executing it. "
82 "Migration script generation is started via `linstor dm-migrate ctrlvol.json "
83 "dmmmigrate.sh`. The script will ask a few questions and then generate the "
84 "shell script. After carefully reading the script, you can then shutdown "
85 "DRBDManage, and rename the following files. If you do not rename them, the "
86 "lower-level drbd-utils pick up both kinds of resource files, the ones from "
87 "DRBDManage and the ones from LINSTOR."
88 msgstr ""
89 "首先要检查的是DRBDManage集群是否处于正常状态。如果 `drbdmanage "
90 "assignments` 的输出看起来不错,那么可以通过 `drbdmanage export "
91 "ctrlvol>ctrlvol.json` 导出现有的集群数据库。然后可以将其用作LINSTOR客户机的输入。客户端 *不会* 立即迁移您的资源,"
92 "它只是生成一个shell脚本。因此,您可以多次运行迁移助手,并在实际执行之前检查/修改生成的shell脚本。迁移脚本生成通过 `linstor dm-migrate ctrlvol.json dmmmigrate.sh` "
93 " 启动。脚本将提出几个问题,然后生成shell脚本。仔细阅读脚本后,可以关闭DRBDManage并重命名以下文件。如果不重命名它们,低级drbd实用程序将同时获取两种资源文件,一种来自DRBDManage,另一种来自LINSTOR。"
94
95 #. type: Plain text
96 #: administration-drbdmanage.adoc:36
97 msgid ""
98 "Obviously, you need the linstor-controller service started on one node and "
99 "the linstor-satellite service on all nodes."
100 msgstr "显然,您需要在一个节点上启动linstor controller服务,并在所有节点上启动linstor satellites服务。"
101
102 #. type: delimited block -
103 #: administration-drbdmanage.adoc:42
104 #, no-wrap
105 msgid ""
106 "# drbdmanage shutdown -qc # on all nodes\n"
107 "# mv /etc/drbd.d/drbdctrl.res{,.dis} # on all nodes\n"
108 "# mv /etc/drbd.d/drbdmanage-resources.res{,.dis} # on all nodes\n"
109 "# bash dmmigrate.sh\n"
110 msgstr ""
111 "# drbdmanage shutdown -qc # on all nodes\n"
112 "# mv /etc/drbd.d/drbdctrl.res{,.dis} # on all nodes\n"
113 "# mv /etc/drbd.d/drbdmanage-resources.res{,.dis} # on all nodes\n"
114 "# bash dmmigrate.sh\n"
115
116 #. type: Title ===
117 #: administration-drbdmanage.adoc:45
118 #, no-wrap
119 msgid "Initializing your cluster"
120 msgstr "初始化集群"
121
122 #. type: Plain text
123 #: administration-drbdmanage.adoc:47
124 msgid ""
125 "We assume that the following steps are accomplished on *all* cluster nodes:"
126 msgstr "我们假设在 *所有* 集群节点上完成以下步骤:"
127
128 #. type: Plain text
129 #: administration-drbdmanage.adoc:49
130 msgid "The DRBD9 kernel module is installed and loaded"
131 msgstr "DRBD9内核模块已安装并加载"
132
133 #. type: Plain text
134 #: administration-drbdmanage.adoc:50
135 msgid "`drbd-utils` are installed"
136 msgstr "已安装 `drbd-utils` "
137
138 #. type: Plain text
139 #: administration-drbdmanage.adoc:51
140 msgid "`LVM` tools are installed"
141 msgstr "`LVM` tools已安装"
142
143 #. type: Plain text
144 #: administration-drbdmanage.adoc:52
145 msgid "`drbdmanage` and its dependencies are installed"
146 msgstr "`drbdmanage` 及其依赖项已安装"
147
148 #. type: Plain text
149 #: administration-drbdmanage.adoc:55
150 msgid ""
151 "Note that drbdmanage uses dbus-activation to start its server component when"
152 " necessary, do not start the server manually."
153 msgstr "注意,drbdmanage在必要时使用dbus激活来启动其服务器组件,不要手动启动服务器。"
154
155 #. type: Plain text
156 #: administration-drbdmanage.adoc:62
157 msgid ""
158 "The first step is to review the configuration file of `drbdmanage` "
159 "(`/etc/drbdmanaged.cfg`) and to create an _LVM volume_ group with the name "
160 "specified in the configuration. In the following we use the default name, "
161 "which is `drbdpool`, and assume that the volume group consists of "
162 "`/dev/sda6` and `/dev/sda7`. Creating the volume group is a step that has to"
163 " be executed on *every* cluster node:"
164 msgstr ""
165 "第一步是检查 `drbdmanage` (`/etc/drbdmanaged.cfg`)的配置文件,并使用配置中指定的名称创建一个LVM卷组。在下面的代码中,我们使用默认名称 `drbdpool` ,并假设卷组由 `/dev/sda6` 和 `/dev/sda7` 组成。创建卷组是必须在 *每个* 集群节点上执行的步骤:"
166
167 #. type: delimited block -
168 #: administration-drbdmanage.adoc:65
169 #, no-wrap
170 msgid "# vgcreate drbdpool /dev/sda6 /dev/sda7\n"
171 msgstr "# vgcreate drbdpool /dev/sda6 /dev/sda7\n"
172
173 #. type: Plain text
174 #: administration-drbdmanage.adoc:72
175 msgid ""
176 "The second step is to initialize the so called control volume, which is then"
177 " used to redundantly store your cluster configuration. If the node has "
178 "multiple interfaces, you have to specify the IP address of the network "
179 "interface that DRBD should use to communicate with other nodes in the "
180 "cluster, otherwise the IP is optional. This step must only be done on "
181 "exactly one cluster node."
182 msgstr ""
183 "第二步是初始化所谓的控制卷,然后使用它来冗余地存储集群配置。如果节点有多个接口,则必须指定DRBD用于与集群中其他节点通信的网络接口的IP地址,否则IP是可选的。此步骤只能在一个集群节点上执行。"
184
185 #. type: delimited block -
186 #: administration-drbdmanage.adoc:75
187 #, no-wrap
188 msgid "# drbdmanage init 10.43.70.2\n"
189 msgstr "# drbdmanage init 10.43.70.2\n"
190
191 #. type: Plain text
192 #: administration-drbdmanage.adoc:82
193 msgid ""
194 "We recommend using 'drbdpool' as the name of your LVM volume group as it is "
195 "the default value and makes your administration life easier. If, for "
196 "whatever reason, you decide to use a different name, make sure that the "
197 "option *drbdctrl-vg* is set accordingly in `/etc/drbdmanaged.cfg`. "
198 "Configuration will be discussed in <<s-dm-set-config>>."
199 msgstr ""
200 "我们建议使用'drbdpool'作为LVM卷组的名称,因为它是默认值,使您的管理工作更轻松。无论出于什么原因,如果您决定使用不同的名称,请确保在 `/etc/drbdmanaged.cfg` 中相应地设置了选项 *drbdctrl"
201 " vg* 。配置将在<<s-dm-set-config>>中讨论。"
202
203 #. type: Title ===
204 #: administration-drbdmanage.adoc:84
205 #, no-wrap
206 msgid "Adding nodes to your cluster"
207 msgstr "向集群添加节点"
208
209 #. type: Plain text
210 #: administration-drbdmanage.adoc:86
211 msgid ""
212 "Adding nodes to your cluster is easy and requires a single command with two "
213 "parameters:"
214 msgstr "将节点添加到集群很简单,需要一个带有两个参数的命令:"
215
216 #. type: Plain text
217 #: administration-drbdmanage.adoc:88
218 msgid "A node name which *must* match the output of `uname -n`"
219 msgstr "一个节点名,*必须* 匹配 `uname-n` 的输出`"
220
221 #. type: Plain text
222 #: administration-drbdmanage.adoc:89
223 msgid "The IP address of the node."
224 msgstr "节点的IP地址。"
225
226 #. type: Block title
227 #: administration-drbdmanage.adoc:90
228 #, no-wrap
229 msgid "Note"
230 msgstr "注意"
231
232 #. type: Plain text
233 #: administration-drbdmanage.adoc:93
234 msgid ""
235 "If DNS is configured properly, the tab-completion of `drbdmanage` is able to"
236 " complete the IP of the given node name."
237 msgstr "如果DNS配置正确,则 `drbdmanage` 的tab补全可以完成给定节点名的IP。"
238
239 #. type: delimited block -
240 #: administration-drbdmanage.adoc:96 administration-drbdmanage.adoc:163
241 #, no-wrap
242 msgid "# drbdmanage add-node bravo 10.43.70.3\n"
243 msgstr "# drbdmanage add-node bravo 10.43.70.3\n"
244
245 #. type: Plain text
246 #: administration-drbdmanage.adoc:101
247 msgid ""
248 "Here we assume that the command was executed on node 'alpha'. If the 'root' "
249 "user is allowed to execute commands as 'root' on 'bravo' via `ssh`, then the"
250 " node 'bravo' will automatically join your cluster."
251 msgstr ""
252 "这里我们假设命令是在节点alpha上执行的。如果允许 `root` 用户通过 `ssh` 在 `bravo` 上以 `root` 身份执行命令,则节点 `bravo` 将自动加入集群。"
253
254 #. type: Plain text
255 #: administration-drbdmanage.adoc:105
256 msgid ""
257 "If `ssh` access with public-key authentication is not possible, `drbdmanage`"
258 " will print a join command that has to be executed on node 'bravo'. You can "
259 "always query `drbdmanage` to output the join command for a specific node:"
260 msgstr ""
261 "如果无法使用公钥身份验证进行 `ssh` 访问, `drbdmanage` 将打印必须在节点 `bravo` 上执行的连接命令。您始终可以查询 `drbdmanage` 以输出特定节点的join命令:"
262
263 #. type: delimited block -
264 #: administration-drbdmanage.adoc:109
265 #, no-wrap
266 msgid ""
267 "# drbdmanage howto-join bravo\n"
268 "# drbdmanage join -p 6999 10.43.70.3 1 alpha 10.43.70.2 0 cOQutgNMrinBXb09A3io\n"
269 msgstr ""
270 "# drbdmanage howto-join bravo\n"
271 "# drbdmanage join -p 6999 10.43.70.3 1 alpha 10.43.70.2 0 cOQutgNMrinBXb09A3io\n"
272
273 #. type: Title ====
274 #: administration-drbdmanage.adoc:112
275 #, no-wrap
276 msgid "Types of DRBD Manage nodes"
277 msgstr "DRBD管理节点的类型"
278
279 #. type: Plain text
280 #: administration-drbdmanage.adoc:115
281 msgid ""
282 "There are quite a few different types of DRBD Manage nodes; please see the "
283 "diagram below."
284 msgstr "有很多不同类型的DRBD管理节点;请参见下图。"
285
286 #. type: Block title
287 #: administration-drbdmanage.adoc:116
288 #, no-wrap
289 msgid "DRBD Manage node types"
290 msgstr "DRBD管理节点类型"
291
292 #. type: Target for macro image
293 #: administration-drbdmanage.adoc:117
294 #, no-wrap
295 msgid "images/drbdmanage-venn.svg"
296 msgstr "images/drbdmanage-venn.svg"
297
298 #. type: Plain text
299 #: administration-drbdmanage.adoc:123
300 msgid ""
301 "The rational behind the different types of nodes is as follows: Currently, a"
302 " DRBD9/DRBD Manage cluster is limited to ~30 nodes. This is the current "
303 "DRBD9 limit of nodes for a replicated resource. As DRBD Manage uses a DRBD "
304 "volume itself (i.e., the control volume) to distribute the cluster "
305 "information, DRBD Manage was also limited by the maximum number of DRBD9 "
306 "nodes per resource."
307 msgstr ""
308 "不同类型节点背后的原因是:目前,DRBD9/DRBD管理集群的节点数限制在30个左右。这是复制资源的当前DRBD9节点限制。由于DRBD "
309 "Manage使用DRBD卷本身(即控制卷)来分发集群信息,DRBD Manage也受到每个资源的DRBD9节点的最大数目的限制。"
310
311 #. type: Plain text
312 #: administration-drbdmanage.adoc:125
313 msgid ""
314 "The satellites concept relaxes that limit by splitting the cluster into:"
315 msgstr "satellite概念通过将集群划分为以下几类来放宽这一限制:"
316
317 #. type: Plain text
318 #: administration-drbdmanage.adoc:127
319 msgid "Control nodes: Nodes having direct access to the control volume."
320 msgstr "Controller节点:直接访问控制卷的节点。"
321
322 #. type: Plain text
323 #: administration-drbdmanage.adoc:129
324 msgid ""
325 "Satellite nodes: Nodes that are not directly connected to to the control "
326 "volume, but are able to receive the content of the control volume via a "
327 "control node."
328 msgstr "Satellite节点:没有直接连接到控制卷的节点,但是能够通过Controller节点接收控制卷的内容。"
329
330 #. type: Plain text
331 #: administration-drbdmanage.adoc:135
332 msgid ""
333 "In a cluster there is one special node, which we call the \"leader\". The "
334 "leader is selected from the set of control nodes and it is the only node "
335 "that writes data to the control volume (i.e., it has the control volume in "
336 "DRBD Primary role). All the other control nodes in the cluster automatically"
337 " switch their role to a \"satellite node\" and receive their cluster "
338 "information via TCP/IP, like ordinary satellite nodes. If the current leader"
339 " node fails, the cluster automatically selects a new leader node among the "
340 "control nodes."
341 msgstr ""
342 "在集群中有一个特殊的节点,我们称之为 `leader` 。从控制节点集中选择leader,它是唯一将数据写入控制卷的节点(即,它具有DRBD "
343 "Primary角色中的控制卷)。集群中的所有其他控制节点自动将其角色切换到 `Satellite节点` ,并像普通satellite节点一样通过TCP/IP接收集群信息。如果当前的leader节点失败,集群将自动在conotroller节点中选择一个新的leader节点。"
344
345 #. type: Plain text
346 #: administration-drbdmanage.adoc:137
347 #, no-wrap
348 msgid "*Control nodes* have:\n"
349 msgstr "*Control nodes* have:\n"
350
351 #. type: Plain text
352 #: administration-drbdmanage.adoc:139
353 msgid "Direct access to the control volume"
354 msgstr "直接访问控制卷"
355
356 #. type: Plain text
357 #: administration-drbdmanage.adoc:140
358 msgid "One of them is in the leader role, the rest act like satellite nodes."
359 msgstr "其中一个leader角色,其余的像satellite节点。"
360
361 #. type: Plain text
362 #: administration-drbdmanage.adoc:141
363 msgid "Local storage if it is a normal control node"
364 msgstr "本地存储(如果是正常控制节点)"
365
366 #. type: Plain text
367 #: administration-drbdmanage.adoc:142
368 msgid "No local storage if it is a pure controller"
369 msgstr "如果是纯controller,则没有本地存储"
370
371 #. type: Plain text
372 #: administration-drbdmanage.adoc:144
373 #, no-wrap
374 msgid "*Satellite nodes* have:\n"
375 msgstr "*Satellite nodes* have:\n"
376
377 #. type: Plain text
378 #: administration-drbdmanage.adoc:146
379 msgid ""
380 "No direct access to the control volume, they receive a copy of the cluster "
381 "configuration via TCP/IP."
382 msgstr "无法直接访问控制卷,它们通过TCP/IP接收集群配置的副本。"
383
384 #. type: Plain text
385 #: administration-drbdmanage.adoc:147
386 msgid "Local storage if it is a normal satellite node"
387 msgstr "本地存储(如果是普通satellite节点)"
388
389 #. type: Plain text
390 #: administration-drbdmanage.adoc:148
391 msgid "No local storage if it is a pure client"
392 msgstr "如果是纯客户端,则没有本地存储"
393
394 #. type: Block title
395 #: administration-drbdmanage.adoc:149
396 #, no-wrap
397 msgid "Cluster consisting of satellite nodes"
398 msgstr "由satellite节点组成的集群"
399
400 #. type: Target for macro image
401 #: administration-drbdmanage.adoc:150
402 #, no-wrap
403 msgid "images/satellitecluster.svg"
404 msgstr "images/satellitecluster.svg"
405
406 #. type: Plain text
407 #: administration-drbdmanage.adoc:153
408 #, no-wrap
409 msgid "*External nodes*:\n"
410 msgstr "*External nodes*:\n"
411
412 #. type: Plain text
413 #: administration-drbdmanage.adoc:155
414 msgid ""
415 "Have no access to the control volume at all (no dedicated TCP/IP connection "
416 "to a control node) and no local storage"
417 msgstr "完全没有对控制卷的访问权限(没有到控制节点的专用TCP/IP连接)并且没有本地存储"
418
419 #. type: Plain text
420 #: administration-drbdmanage.adoc:156
421 msgid ""
422 "Gets its configuration via a different channel (e.g., DRBD configuration via"
423 " `scp`)"
424 msgstr "通过不同的通道获取其配置(例如,通过 `scp` 进行DRBD配置)"
425
426 #. type: Plain text
427 #: administration-drbdmanage.adoc:157
428 msgid ""
429 "These are not the droids you are looking for, if you are not sure if you "
430 "want to use that type of nodes."
431 msgstr "如果你不确定是否要使用这种类型的节点,尽量不要使用这样的节点。"
432
433 #. type: Title ====
434 #: administration-drbdmanage.adoc:159
435 #, no-wrap
436 msgid "Adding a control node"
437 msgstr "添加controller节点"
438
439 #. type: Title ====
440 #: administration-drbdmanage.adoc:166
441 #, no-wrap
442 msgid "Adding a pure controller node"
443 msgstr "添加纯controller节点"
444
445 #. type: delimited block -
446 #: administration-drbdmanage.adoc:170
447 #, no-wrap
448 msgid "# drbdmanage add-node --no-storage bravo 10.43.70.3\n"
449 msgstr "# drbdmanage add-node --no-storage bravo 10.43.70.3\n"
450
451 #. type: Title ====
452 #: administration-drbdmanage.adoc:173
453 #, no-wrap
454 msgid "Adding a satellite node"
455 msgstr "添加satellite节点"
456
457 #. type: Plain text
458 #: administration-drbdmanage.adoc:176
459 msgid ""
460 "Here we assume that the node charlie was not added to the cluster so far. "
461 "The following command adds charlie as a satellite node."
462 msgstr "这里我们假设charlie节点到目前为止还没有添加到集群中。下面的命令将charlie添加为satellite节点。"
463
464 #. type: delimited block -
465 #: administration-drbdmanage.adoc:179
466 #, no-wrap
467 msgid "# drbdmanage add-node --satellite charlie 10.43.70.4\n"
468 msgstr "# drbdmanage add-node --satellite charlie 10.43.70.4\n"
469
470 #. type: Title ====
471 #: administration-drbdmanage.adoc:182
472 #, no-wrap
473 msgid "Adding a pure client node"
474 msgstr "添加纯客户端节点"
475
476 #. type: delimited block -
477 #: administration-drbdmanage.adoc:186
478 #, no-wrap
479 msgid "# drbdmanage add-node --satellite --no-storage charlie 10.43.70.4\n"
480 msgstr "# drbdmanage add-node --satellite --no-storage charlie 10.43.70.4\n"
481
482 #. type: Title ====
483 #: administration-drbdmanage.adoc:189
484 #, no-wrap
485 msgid "Adding an external node"
486 msgstr "添加外部节点"
487
488 #. type: delimited block -
489 #: administration-drbdmanage.adoc:193
490 #, no-wrap
491 msgid "# drbdmanage add-node --external delta 10.43.70.5\n"
492 msgstr "# drbdmanage add-node --external delta 10.43.70.5\n"
493
494 #. type: Title ===
495 #: administration-drbdmanage.adoc:197
496 #, no-wrap
497 msgid "Cluster configuration"
498 msgstr "集群配置"
499
500 #. type: Plain text
501 #: administration-drbdmanage.adoc:206
502 msgid ""
503 "Drbdmanage knows many configuration settings like the log-level or the "
504 "storage plugin that should be used (i.e., LVM, ThinLV, ThinPool, ZPool, or "
505 "ThinZpool). Executing `drbdmanage modify-config` starts an editor that is "
506 "used to specify theses settings. The configuration is split in several "
507 "sections. If an option is specified in the `[GLOBAL]` section, this setting "
508 "is used in the entire cluster. Additionally, it is possible to specify "
509 "settings per node and per site. Node sections follow a syntax of "
510 "`[Node:nodename]`. If an option is set globally and per node, the node "
511 "setting overrules the global setting."
512 msgstr ""
513 "Drbdmanage知道许多配置设置,如日志级别或应该使用的存储插件(即LVM、ThinLV、ThinPool、ZPool或ThinZpool)。执行 `drbdmanage"
514 " modify-config ` "
515 "将启动一个用于指定这些设置的编辑器。配置分为几个部分。如果在 `[GLOBAL]` 部分中指定了选项,则在整个集群中使用此设置。此外,还可以指定每个节点和每个站点的设置。节点部分遵循 `[Node:nodename]` 的语法。如果选项是全局和每个节点设置的,则节点设置将否决全局设置。"
516
517 #. type: Plain text
518 #: administration-drbdmanage.adoc:210
519 msgid ""
520 "It is also possible to group nodes into *sites*. In order to make node "
521 "'alpha' part of site 'mysite', you have to specify the 'site' option in "
522 "alpha's node section:"
523 msgstr "也可以将节点分组到 *站点* 。要使节点 `alpha` 成为站点 `mysite` 的一部分,必须在alpha的节点部分指定 `site` 选项:"
524
525 #. type: delimited block -
526 #: administration-drbdmanage.adoc:215
527 #, no-wrap
528 msgid ""
529 "# drbdmanage modify-config\n"
530 "[Node:alpha]\n"
531 "site = mysite\n"
532 msgstr ""
533 "# drbdmanage modify-config\n"
534 "[Node:alpha]\n"
535 "site = mysite\n"
536
537 #. type: Plain text
538 #: administration-drbdmanage.adoc:222
539 msgid ""
540 "It is then also possible to specify drbdmanage settings per site using "
541 "`[Site:]` sections. Lets assume that you want to set the 'loglevel' option "
542 "in general to 'INFO', for site 'mysite' to 'WARN' and for node alpha, which "
543 "is also part of site 'mysite' to DEBUG. This would result in the following "
544 "configuration:"
545 msgstr ""
546 "然后还可以使用 `[Site:]` 部分指定每个站点的drbdmanage设置。假设您希望将 `loglevel` 选项一般设置为 `INFO` ,将站点 `mysite` 设置为 `WARN` ,并将节点alpha设置为要调试的站点 `mysite` 的一部分。这将导致以下配置:"
547
548 #. type: delimited block -
549 #: administration-drbdmanage.adoc:227
550 #, no-wrap
551 msgid ""
552 "# drbdmanage modify-config\n"
553 "[GLOBAL]\n"
554 "loglevel = INFO\n"
555 msgstr ""
556 "# drbdmanage modify-config\n"
557 "[GLOBAL]\n"
558 "loglevel = INFO\n"
559
560 #. type: delimited block -
561 #: administration-drbdmanage.adoc:230
562 #, no-wrap
563 msgid ""
564 "[Site:mysite]\n"
565 "loglevel = WARN\n"
566 msgstr ""
567 "[Site:mysite]\n"
568 "loglevel = WARN\n"
569
570 #. type: delimited block -
571 #: administration-drbdmanage.adoc:234
572 #, no-wrap
573 msgid ""
574 "[Node:alpha]\n"
575 "site = mysite\n"
576 "loglevel = DEBUG\n"
577 msgstr ""
578 "[Node:alpha]\n"
579 "site = mysite\n"
580 "loglevel = DEBUG\n"
581
582 #. type: Plain text
583 #: administration-drbdmanage.adoc:241
584 msgid ""
585 "By executing `drbdmanage modify-config` without any options, you can edit "
586 "global, per site and per node settings. It is also possible to execute "
587 "'modify-config' for a specific node. In this per-node view, it is possible "
588 "to set further per-node specific settings like the storage plugin discussed "
589 "in <<s-drbdmanage-storage-plugins>>."
590 msgstr ""
591 "通过执行不带任何选项的 `drbdmanage modify-config` ,可以编辑全局、每个站点和每个节点的设置。还可以为特定节点执行 `modify-"
592 "config` 。在每个节点视图中,可以进一步设置每个节点的特定设置,如<<s-drbdmanage-storage-plugins>>中讨论的存储插件。"
593
594 #. type: Title ===
595 #: administration-drbdmanage.adoc:243
596 #, no-wrap
597 msgid "Configuring storage plugins"
598 msgstr "配置存储插件"
599
600 #. type: Plain text
601 #: administration-drbdmanage.adoc:245
602 msgid ""
603 "Storage plugins are *per* *node* settings that are set with the help of the "
604 "'modify-config' sub command."
605 msgstr "存储插件是通过 `modify-config` 子命令设置的 *每个* *节点* 设置。"
606
607 #. type: Plain text
608 #: administration-drbdmanage.adoc:248
609 msgid ""
610 "Lets assume you want to use the 'ThinLV' plugin for node 'bravo', where you "
611 "want to set the 'pool-name' option to 'mythinpool':"
612 msgstr "假设您想为节点 `bravo` 使用 `ThinLV` 插件,在这里您想将 `pool-name` 选项设置为 `mythinpool` :"
613
614 #. type: delimited block -
615 #: administration-drbdmanage.adoc:253
616 #, no-wrap
617 msgid ""
618 "# drbdmanage modify-config --node bravo\n"
619 "[GLOBAL]\n"
620 "loglevel = INFO\n"
621 msgstr ""
622 "# drbdmanage modify-config --node bravo\n"
623 "[GLOBAL]\n"
624 "loglevel = INFO\n"
625
626 #. type: delimited block -
627 #: administration-drbdmanage.adoc:256
628 #, no-wrap
629 msgid ""
630 "[Node:bravo]\n"
631 "storage-plugin = drbdmanage.storage.lvm_thinlv.LvmThinLv\n"
632 msgstr ""
633 "[Node:bravo]\n"
634 "storage-plugin = drbdmanage.storage.lvm_thinlv.LvmThinLv\n"
635
636 #. type: delimited block -
637 #: administration-drbdmanage.adoc:259
638 #, no-wrap
639 msgid ""
640 "[Plugin:ThinLV]\n"
641 "pool-name = mythinpool\n"
642 msgstr ""
643 "[Plugin:ThinLV]\n"
644 "pool-name = mythinpool\n"
645
646 #. type: Title ====
647 #: administration-drbdmanage.adoc:262
648 #, no-wrap
649 msgid "Configuring LVM"
650 msgstr "配置LVM"
651
652 #. type: Plain text
653 #: administration-drbdmanage.adoc:269
654 msgid ""
655 "More recent versions of the 'LVM tools' support detecting of file system "
656 "signatures. Unfortunately the feature set of `lvcreate` varies a lot between"
657 " distributions: Some of them support `--wipesignatures`, some support "
658 "`--yes`, and that in all possible combinations. None of them supports a "
659 "generic force flag. If `lvcreate` detects an existing file system signature,"
660 " it prompts for input and therefore halts processing. If you use modern 'LVM"
661 " tools', set this option in `/etc/lvm/lvm.conf`: "
662 "`wipe_signatures_when_zeroing_new_lvs = 0`. Drbdmanage itself executes "
663 "`wipefs` on created block devices."
664 msgstr ""
665 "`LVM tools` 的最新版本支持检测文件系统签名。不幸的是, `lvcreate` 的特性集在不同"
666 "的发行版之间有很大的不同:有些发行版支持 `--wipesignatures` ,有些发行版支持 `--yes` ,"
667 "还有一些发行版支持所有可能的组合。它们都不支持通用的force标志。"
668 "如果 `lvcreate` 检测到现有的文件系统签名,它将提示输入,并因此停止处理。"
669 "如果使用更新版本的 `LVM tools` ,请在 `/etc/lvm/lvm.conf` 中设置此选项:"
670 " `wipe_signatures_when_zeroing_new_lvs = 0`. "
671 "Drbdmanage本身会在创建的块设备上执行 `wipefs` 。"
672
673 #. type: Plain text
674 #: administration-drbdmanage.adoc:272
675 msgid ""
676 "If you use a version of 'LVM' where resources from snapshots are not "
677 "activated, which we saw for the 'LvmThinPool' plugin, also set "
678 "`auto_set_activation_skip = 0` in `/etc/lvm/lvm.conf`."
679 msgstr ""
680 "如果您使用的 'LVM' 版本,其中没有激活快照中的资源,我们会在 'LvmThinPool' 插件中看到了这个版本,那么也可以在 `/etc/lvm/lvm.conf' "
681 "中设置 `auto_set_activation_skip = 0`。"
682
683 #. type: Title ====
684 #: administration-drbdmanage.adoc:274
685 #, no-wrap
686 msgid "Configuring ZFS"
687 msgstr "配置ZFS"
688
689 #. type: Plain text
690 #: administration-drbdmanage.adoc:280
691 msgid ""
692 "For ZFS the same configuration steps apply, like setting the 'storage-"
693 "plugin' for the node that should make use of ZFS volumes. Please note that "
694 "we don't make use of ZFS as a file system, but of ZFS as a logical volume "
695 "manager. The admin is then free to create any file system she/he desires on "
696 "top of the DRBD device backed by a ZFS volume. It is also important to note "
697 "that if you make use of the ZFS plugin, all DRBD resources are created on "
698 "ZFS, but in case this node is a control node, it still needs LVM for it's "
699 "control volume."
700 msgstr ""
701 "对于ZFS,同样的配置步骤也适用,比如为应该使用ZFS卷的节点设置 `storage-plugin` 。"
702 "请注意,我们没有将ZFS用作文件系统,而是将ZFS用作逻辑卷管理器。"
703 "然后,管理员可以在ZFS卷支持的DRBD设备上自由创建所需的任何文件系统。"
704 "还需要注意的是,如果使用ZFS插件,所有DRBD资源都是在ZFS上创建的,"
705 "但是如果这个节点是controller节点,那么它的控制卷仍然需要LVM。"
706
707 #. type: Plain text
708 #: administration-drbdmanage.adoc:282
709 msgid "In the most common case only the following steps are necessary."
710 msgstr "在最常见的情况下,只需要以下步骤。"
711
712 #. type: delimited block -
713 #: administration-drbdmanage.adoc:288
714 #, no-wrap
715 msgid ""
716 "# zpool create drbdpool /dev/sdX /dev/sdY\n"
717 "# drbdmanage modify-config --node bravo\n"
718 "[Node:bravo]\n"
719 "storage-plugin = drbdmanage.storage.zvol2.Zvol2\n"
720 msgstr ""
721 "# zpool create drbdpool /dev/sdX /dev/sdY\n"
722 "# drbdmanage modify-config --node bravo\n"
723 "[Node:bravo]\n"
724 "storage-plugin = drbdmanage.storage.zvol2.Zvol2\n"
725
726 #. type: Plain text
727 #: administration-drbdmanage.adoc:294
728 msgid ""
729 "Currently it is not supported to switch storage plugins on the fly. The "
730 "workflow is: Add a new node, modify the configuration for that node, make "
731 "use of the node. Changing other settings (like the log-level) on the fly is "
732 "perfectly fine."
733 msgstr "目前不支持动态切换存储插件。工作流是:添加一个新的节点,"
734 "修改该节点的配置,利用该节点。动态更改其他设置(如日志级别)是非常好的。"
735
736 #. type: Title ====
737 #: administration-drbdmanage.adoc:296
738 #, no-wrap
739 msgid "Discussion of the storage plugins"
740 msgstr "关于存储插件的讨论"
741
742 #. type: Plain text
743 #: administration-drbdmanage.adoc:299
744 msgid "indexterm:[drbdmanage, storage plugins]"
745 msgstr "indexterm:[drbdmanage, storage plugins]"
746
747 #. type: Plain text
748 #: administration-drbdmanage.adoc:301
749 msgid "DRBD Manage has four supported storage plugins as of this writing:"
750 msgstr "DRBD Manage在撰写本文时有四个受支持的存储插件:"
751
752 #. type: Plain text
753 #: administration-drbdmanage.adoc:303
754 msgid "Thick LVM (`drbdmanage.storage.lvm.Lvm`);"
755 msgstr "Thick LVM (`drbdmanage.storage.lvm.Lvm`);"
756
757 #. type: Plain text
758 #: administration-drbdmanage.adoc:305
759 msgid ""
760 "Thin LVM with a single thin pool (`drbdmanage.storage.lvm_thinlv.LvmThinLv`)"
761 msgstr ""
762 "Thin LVM with a single thin pool (`drbdmanage.storage.lvm_thinlv.LvmThinLv`)"
763
764 #. type: Plain text
765 #: administration-drbdmanage.adoc:307
766 msgid ""
767 "Thin LVM with thin pools for each volume "
768 msgstr ""
769 "Thin LVM with thin pools for each volume "
770 "(`drbdmanage.storage.lvm_thinpool.LvmThinPool`)"
771
772 #. type: Plain text
773 #: administration-drbdmanage.adoc:309
774 msgid "Thick ZFS (`drbdmanage.storage.zvol2.Zvol2`)"
775 msgstr "Thick ZFS (`drbdmanage.storage.zvol2.Zvol2`)"
776
777 #. type: Plain text
778 #: administration-drbdmanage.adoc:311
779 msgid "Thin ZFS (`drbdmanage.storage.zvol2_thinlv.ZvolThinLv2`)"
780 msgstr "Thin ZFS (`drbdmanage.storage.zvol2_thinlv.ZvolThinLv2`)"
781
782 #. type: Plain text
783 #: administration-drbdmanage.adoc:315
784 msgid ""
785 "For ZFS also legacy plugins (without the \"2\") exist. New users, and users "
786 "that did not uses ZFS snapshots should use/switch to the newer version. An "
787 "on-the-fly storage plugin switch is supported in this particular case."
788 msgstr "对于ZFS,还存在遗留插件(不带 \"2\" )。新用户和未使用ZFS快照的用户应使用/切换到新版本。在这种特殊情况下,支持动态存储插件开关。"
789
790 #. type: Plain text
791 #: administration-drbdmanage.adoc:317
792 msgid ""
793 "Here's a short discussion of the relative advantages and disadvantages of "
794 "these plugins."
795 msgstr "下面简要讨论一下这些插件的相对优缺点。"
796
797 #. type: Block title
798 #: administration-drbdmanage.adoc:320
799 #, no-wrap
800 msgid "DRBD Manage storage plugins, comparison"
801 msgstr "DRBD管理存储插件比较"
802
803 #. type: Table
804 #: administration-drbdmanage.adoc:330
805 #, no-wrap
806 msgid ""
807 "|Topic | `lvm.Lvm` | `lvm_thinlv.LvmThinLv` | `lvm_thinpool.LvmThinPool`\n"
808 "|Pools | the VG is the pool | a single Thin pool | one Thin pool for each volume\n"
809 "|Free Space reporting | Exact | Free space goes down as per written data and snapshots, needs monitoring | Each pool carves some space out of the VG, but still needs to be monitored if snapshots are used\n"
810 "|Allocation | Fully pre-allocated 2+| thinly allocated, needs nearly zero space initially\n"
811 "|Snapshots | -- not supported -- 2+| Fast, efficient (copy-on-write)\n"
812 "|Stability | Well established, known code, very stable 2+| Some kernel versions have bugs re Thin LVs, destroying data\n"
813 "|Recovery | Easiest - text editor, and/or lvm configuration archives in `/etc/lvm/`, in the worst case `dd` with offset/length | All data in one pool, might incur running `thin_check` across *everything* (needs CPU, memory, time) | Independent Pools, so not all volumes damaged at the same time, faster `thin_check` (less CPU, memory, time)\n"
814 msgstr ""
815 "|Topic | `lvm.Lvm` | `lvm_thinlv.LvmThinLv` | `lvm_thinpool.LvmThinPool`\n"
816 "|Pools | the VG is the pool | a single Thin pool | one Thin pool for each volume\n"
817 "|Free Space reporting | Exact | Free space goes down as per written data and snapshots, needs monitoring | Each pool carves some space out of the VG, but still needs to be monitored if snapshots are used\n"
818 "|Allocation | Fully pre-allocated 2+| thinly allocated, needs nearly zero space initially\n"
819 "|Snapshots | -- not supported -- 2+| Fast, efficient (copy-on-write)\n"
820 "|Stability | Well established, known code, very stable 2+| Some kernel versions have bugs re Thin LVs, destroying data\n"
821 "|Recovery | Easiest - text editor, and/or lvm configuration archives in `/etc/lvm/`, in the worst case `dd` with offset/length | All data in one pool, might incur running `thin_check` across *everything* (needs CPU, memory, time) | Independent Pools, so not all volumes damaged at the same time, faster `thin_check` (less CPU, memory, time)\n"
822
823 #. type: Title ===
824 #: administration-drbdmanage.adoc:334
825 #, no-wrap
826 msgid "Creating and deploying resources/volumes"
827 msgstr "创建和部署资源/卷"
828
829 #. type: Plain text
830 #: administration-drbdmanage.adoc:339
831 msgid ""
832 "In the following scenario we assume that the goal is to create a resource "
833 "'backups' with a size of '500 GB' that is replicated among 3 cluster nodes."
834 " First we show how to achieve the goal in individual steps, and then show a"
835 " short-cut how to achieve it in a single step:"
836 msgstr ""
837 "在下面的场景中,我们假设目标是创建一个大小为 `500 "
838 "GB` 的资源 `备份` ,该资源在3个集群节点之间复制。首先,我们将展示如何在各个步骤中实现目标,然后展示如何在单个步骤中实现目标的捷径:"
839
840 #. type: Plain text
841 #: administration-drbdmanage.adoc:341
842 msgid "First, we create a new resource:"
843 msgstr "首先,我们创建一个新资源:"
844
845 #. type: delimited block -
846 #: administration-drbdmanage.adoc:344
847 #, no-wrap
848 msgid "# drbdmanage add-resource backups\n"
849 msgstr "# drbdmanage add-resource backups\n"
850
851 #. type: Plain text
852 #: administration-drbdmanage.adoc:347
853 msgid "Second, we create a new volume within that resource:"
854 msgstr "其次,我们在该资源中创建一个新卷:"
855
856 #. type: delimited block -
857 #: administration-drbdmanage.adoc:350
858 #, no-wrap
859 msgid "# drbdmanage add-volume backups 500GB\n"
860 msgstr "# drbdmanage add-volume backups 500GB\n"
861
862 #. type: Plain text
863 #: administration-drbdmanage.adoc:353
864 msgid ""
865 "In case we would not have used 'add-resource' in the first step, "
866 "`drbdmanage` would have known that the resource did not exist and it would "
867 "have created it."
868 msgstr "如果我们在第一步中不使用 `add resource` ,那么 `drbdmanage` 将知道该资源不存在,并且它将创建该资源。"
869
870 #. type: Plain text
871 #: administration-drbdmanage.adoc:355
872 msgid "The third step is to deploy the resource to 3 cluster nodes:"
873 msgstr "第三步是将资源部署到3个集群节点:"
874
875 #. type: delimited block -
876 #: administration-drbdmanage.adoc:358
877 #, no-wrap
878 msgid "# drbdmanage deploy-resource backups 3\n"
879 msgstr "# drbdmanage deploy-resource backups 3\n"
880
881 #. type: Plain text
882 #: administration-drbdmanage.adoc:364
883 msgid ""
884 "In this case `drbdmanage` chooses 3 nodes that fit all requirements best, "
885 "which is by default the set of nodes with the most free space in the "
886 "`drbdpool` volume group. We will see how to manually assign resources to "
887 "specific nodes in a moment."
888 msgstr ""
889 "在本例中, `drbdmanage` 选择3个最符合所有要求的节点,这是默认情况下 `drbdpool` 卷组中可用空间最大的节点集。我们稍后将看到如何手动将资源分配给特定节点。"
890
891 #. type: Plain text
892 #: administration-drbdmanage.adoc:367
893 msgid ""
894 "As deploying a new resource/volume to a set of nodes is a very common task, "
895 "`drbdmanage` provides the following short-cut:"
896 msgstr "由于将新资源/卷部署到一组节点是一项非常常见的任务, `drbdmanage` 提供了以下捷径:"
897
898 #. type: delimited block -
899 #: administration-drbdmanage.adoc:370
900 #, no-wrap
901 msgid "# drbdmanage add-volume backups 500GB --deploy 3\n"
902 msgstr "# drbdmanage add-volume backups 500GB --deploy 3\n"
903
904 #. type: Plain text
905 #: administration-drbdmanage.adoc:375
906 msgid ""
907 "Manual deployment can be achieved by *assigning* a resource to specific "
908 "nodes. For example if you decide to assign the 'backups' resource to "
909 "'bravo' and 'charlie', you should execute the following steps:"
910 msgstr ""
911 "手动部署可以通过将资源分配给特定节点来实现。例如,如果决定将 `backups` 资源分配给 `bravo` 和 `charlie` ,则应执行以下步骤:"
912
913 #. type: delimited block -
914 #: administration-drbdmanage.adoc:380
915 #, no-wrap
916 msgid ""
917 "# drbdmanage add-volume backups 500GB\n"
918 "# drbdmanage assign-resource backups bravo\n"
919 "# drbdmanage assign-resource backups charlie\n"
920 msgstr ""
921 "# drbdmanage add-volume backups 500GB\n"
922 "# drbdmanage assign-resource backups bravo\n"
923 "# drbdmanage assign-resource backups charlie\n"
924
925 #. type: Title ===
926 #: administration-drbdmanage.adoc:383
927 #, no-wrap
928 msgid "Managing snapshots"
929 msgstr "管理快照"
930
931 #. type: Plain text
932 #: administration-drbdmanage.adoc:388
933 msgid ""
934 "In the following we assume that the _ThinLV_ plugin is used on all nodes "
935 "that have deployed resources from which snapshots should be taken. For "
936 "further information on how to configure the storage plugin, please refer to "
937 "<<s-dm-set-config>>."
938 msgstr ""
939 "在下面的代码中,我们假设在所有部署了资源的节点上都使用了ThinLV插件,应该从中获取快照。有关如何配置存储插件的更多信息,请参阅<<s-dm-set-"
940 "config>>。"
941
942 #. type: Title ====
943 #: administration-drbdmanage.adoc:390
944 #, no-wrap
945 msgid "Creating a snapshot"
946 msgstr "创建快照"
947
948 #. type: Plain text
949 #: administration-drbdmanage.adoc:395
950 msgid ""
951 "Here we continue the example presented in the previous sections, namely "
952 "nodes 'alpha', 'bravo', 'charlie', and 'delta' with a resource 'backups' "
953 "deployed on the first three nodes. The name of the snapshot will be "
954 "'snap_backups', and we want the snapshot to be taken on nodes 'bravo' and "
955 "'charlie'."
956 msgstr ""
957 "在这里,我们继续前面部分中的示例,即节点 `alpha` 、 `bravo` 、 `charlie` 和 `delta` ,在前三个节点上部署了资源 `backups` 。快照的名称将为 `快照备份` ,我们希望在节点 `bravo` 和 `charlie` 上创建快照。"
958
959 #. type: delimited block -
960 #: administration-drbdmanage.adoc:398
961 #, no-wrap
962 msgid "# drbdmanage create-snapshot snap_backups backups bravo charlie\n"
963 msgstr "# drbdmanage create-snapshot snap_backups backups bravo charlie\n"
964
965 #. type: Title ====
966 #: administration-drbdmanage.adoc:401
967 #, no-wrap
968 msgid "Restoring a snapshot"
969 msgstr "还原快照"
970
971 #. type: Plain text
972 #: administration-drbdmanage.adoc:404
973 msgid ""
974 "In the following we want to restore the content of the snapshot "
975 "'snap_backups' to a new resource named 'res_backup_from_snap'."
976 msgstr "在下面,我们要将快照 `快照备份` 的内容还原到名为 `res_backup_from_snap` 的新资源。"
977
978 #. type: delimited block -
979 #: administration-drbdmanage.adoc:407
980 #, no-wrap
981 msgid ""
982 "# drbdmanage restore-snapshot res_backup_from_snap backups snap_backups\n"
983 msgstr ""
984 "# drbdmanage restore-snapshot res_backup_from_snap backups snap_backups\n"
985
986 #. type: Plain text
987 #: administration-drbdmanage.adoc:412
988 msgid ""
989 "This will create a new resource with the name 'res_backup_from_snap'. This "
990 "resource then gets automatically deployed to these nodes where currently the"
991 " resource 'backups' is deployed."
992 msgstr "这将创建名为 `res_backup_from_snap` 的新资源。然后,此资源将自动部署到当前部署资源 `备份` 的这些节点。"
993
994 #. type: Title ====
995 #: administration-drbdmanage.adoc:414
996 #, no-wrap
997 msgid "Removing a snapshot"
998 msgstr "删除快照"
999
1000 #. type: Plain text
1001 #: administration-drbdmanage.adoc:416
1002 msgid "An existing snapshot can be removed as follows:"
1003 msgstr "可以按如下方式删除现有快照:"
1004
1005 #. type: delimited block -
1006 #: administration-drbdmanage.adoc:419
1007 #, no-wrap
1008 msgid "# drbdmanage remove-snapshot backups snap_backups\n"
1009 msgstr "# drbdmanage remove-snapshot backups snap_backups\n"
1010
1011 #. type: Title ===
1012 #: administration-drbdmanage.adoc:423
1013 #, no-wrap
1014 msgid "Checking the state of your cluster"
1015 msgstr "检查集群状态"
1016
1017 #. type: Plain text
1018 #: administration-drbdmanage.adoc:429
1019 msgid ""
1020 "`Drbdmanage` provides various commands to check the state of your cluster. "
1021 "These commands start with a 'list-' prefix and provide various filtering and"
1022 " sorting options. The '--groupby' option can be used to group and sort the "
1023 "output in multiple dimensions. Additional output can be turned on by using "
1024 "the '--show' option. In the following we show some typical examples:"
1025 msgstr ""
1026 "`Drbdmanage` 提供各种命令来检查集群的状态。这些命令以 `list-` 前缀开头,并提供各种筛选和排序选项。 `--groupby` 选项可用于按多个维度对输出进行分组和排序。使用 `--show` 选项可以打开其他输出。以下是一些典型的例子:"
1027
1028 #. type: delimited block -
1029 #: administration-drbdmanage.adoc:435
1030 #, no-wrap
1031 msgid ""
1032 "# drbdmanage list-nodes\n"
1033 "# drbdmanage list-volumes --groupby Size\n"
1034 "# drbdmanage list-volumes --groupby Size --groupby Minor\n"
1035 "# drbdmanage list-volumes --groupby Size --show Port\n"
1036 msgstr ""
1037 "# drbdmanage list-nodes\n"
1038 "# drbdmanage list-volumes --groupby Size\n"
1039 "# drbdmanage list-volumes --groupby Size --groupby Minor\n"
1040 "# drbdmanage list-volumes --groupby Size --show Port\n"
1041
1042 #. type: Title ===
1043 #: administration-drbdmanage.adoc:438
1044 #, no-wrap
1045 msgid "Setting options for resources"
1046 msgstr "设置资源选项"
1047
1048 #. type: Plain text
1049 #: administration-drbdmanage.adoc:440
1050 msgid "Currently, it is possible to set the following `drbdsetup` options:"
1051 msgstr "目前,可以设置以下 `drbdsetup` 选项:"
1052
1053 #. type: Plain text
1054 #: administration-drbdmanage.adoc:442
1055 msgid "net-options"
1056 msgstr "net-options"
1057
1058 #. type: Plain text
1059 #: administration-drbdmanage.adoc:443
1060 msgid "peer-device-options"
1061 msgstr "peer-device-options"
1062
1063 #. type: Plain text
1064 #: administration-drbdmanage.adoc:444
1065 msgid "disk-options"
1066 msgstr "disk-options"
1067
1068 #. type: Plain text
1069 #: administration-drbdmanage.adoc:445
1070 msgid "resource-options"
1071 msgstr "resource-options"
1072
1073 #. type: Plain text
1074 #: administration-drbdmanage.adoc:447
1075 msgid "Additionally, it is possible to set DRBD event handler."
1076 msgstr "此外,还可以设置DRBD事件处理程序。"
1077
1078 #. type: Plain text
1079 #: administration-drbdmanage.adoc:450
1080 msgid ""
1081 "As for example _net-options_ are allowed in the 'common' section as well as "
1082 "per resource, these commands then provide the according switches."
1083 msgstr "例如,在 `common` 部分和每个资源中都允许使用 `net-options` ,然后这些命令提供相应的开关。"
1084
1085 #. type: Plain text
1086 #: administration-drbdmanage.adoc:452
1087 msgid "Setting `max-buffers` for a resource 'backups' looks like this:"
1088 msgstr "为资源 `backups` 设置 `max buffers` 如下:"
1089
1090 #. type: delimited block -
1091 #: administration-drbdmanage.adoc:455
1092 #, no-wrap
1093 msgid "# drbdmanage net-options --max-buffers 2048 --resource backups\n"
1094 msgstr "# drbdmanage net-options --max-buffers 2048 --resource backups\n"
1095
1096 #. type: Plain text
1097 #: administration-drbdmanage.adoc:458
1098 msgid "Setting this option in the common section looks like this:"
1099 msgstr "在common部分中设置此选项如下所示:"
1100
1101 #. type: delimited block -
1102 #: administration-drbdmanage.adoc:461
1103 #, no-wrap
1104 msgid "# drbdmanage net-options --max-buffers 2048 --common\n"
1105 msgstr "# drbdmanage net-options --max-buffers 2048 --common\n"
1106
1107 #. type: Plain text
1108 #: administration-drbdmanage.adoc:466
1109 msgid ""
1110 "Additionally, there is always an '--unset-' option for every option that can"
1111 " be specified. So, unsetting `max-buffers` for a resource 'backups' looks "
1112 "like this:"
1113 msgstr "此外,对于每个可以指定的选项,总是有一个 `--unset-` 选项。因此,为资源 `backups` 设置 `max buffers` 如下:"
1114
1115 #. type: delimited block -
1116 #: administration-drbdmanage.adoc:469
1117 #, no-wrap
1118 msgid "# drbdmanage net-options --unset-max-buffers --resource backups\n"
1119 msgstr "# drbdmanage net-options --unset-max-buffers --resource backups\n"
1120
1121 #. type: Plain text
1122 #: administration-drbdmanage.adoc:473
1123 msgid ""
1124 "It is possible to visualize currently set options with the 'show-options' "
1125 "subcommand."
1126 msgstr "可以使用 `show options` 子命令可视化当前设置的选项。"
1127
1128 #. type: Plain text
1129 #: administration-drbdmanage.adoc:478
1130 msgid ""
1131 "Setting _net-options_ per site is also supported. Lets assume 'alpha' and "
1132 "'bravo' should be part of site 'first' and 'charlie' and 'delta' should be "
1133 "part of site 'second'. Further, we want to use DRBD protocol 'C' within the "
1134 "two sites, and protocol 'A' between the sites 'first' and 'second'. This "
1135 "would be set up as follows:"
1136 msgstr ""
1137 "也支持为每个站点设置网络选项。假设 `alpha` 和 `bravo` 应该是站点 `first` 的一部分, `charlie` 和 `delta` 应该是站点 `second` 的一部分。此外,我们希望在两个站点中使用DRBD协议 `C` ,在站点 `first` 和 `second` 之间使用协议 `A` 。其设置如下:"
1138
1139 #. type: delimited block -
1140 #: administration-drbdmanage.adoc:483
1141 #, no-wrap
1142 msgid ""
1143 "# drbdmanage modify-config\n"
1144 "[Node:alpha]\n"
1145 "site = first\n"
1146 msgstr ""
1147 "# drbdmanage modify-config\n"
1148 "[Node:alpha]\n"
1149 "site = first\n"
1150
1151 #. type: delimited block -
1152 #: administration-drbdmanage.adoc:486
1153 #, no-wrap
1154 msgid ""
1155 "[Node:bravo]\n"
1156 "site = first\n"
1157 msgstr ""
1158 "[Node:bravo]\n"
1159 "site = first\n"
1160
1161 #. type: delimited block -
1162 #: administration-drbdmanage.adoc:489
1163 #, no-wrap
1164 msgid ""
1165 "[Node:charlie]\n"
1166 "site = second\n"
1167 msgstr ""
1168 "[Node:charlie]\n"
1169 "site = second\n"
1170
1171 #. type: delimited block -
1172 #: administration-drbdmanage.adoc:492
1173 #, no-wrap
1174 msgid ""
1175 "[Node:delta]\n"
1176 "site = second\n"
1177 msgstr ""
1178 "[Node:delta]\n"
1179 "site = second\n"
1180
1181 #. type: delimited block -
1182 #: administration-drbdmanage.adoc:498
1183 #, no-wrap
1184 msgid ""
1185 "# drbdmanage net-options --protocol C --sites 'first:first'\n"
1186 "# drbdmanage net-options --protocol C --sites 'second:second'\n"
1187 "# drbdmanage net-options --protocol A --sites 'first:second'\n"
1188 msgstr ""
1189 "# drbdmanage net-options --protocol C --sites 'first:first'\n"
1190 "# drbdmanage net-options --protocol C --sites 'second:second'\n"
1191 "# drbdmanage net-options --protocol A --sites 'first:second'\n"
1192
1193 #. type: Plain text
1194 #: administration-drbdmanage.adoc:503
1195 msgid ""
1196 "The '--sites' parameter follows a 'from:to' syntax, where currently 'from' "
1197 "and 'to' have a symetric semantic. Setting an option from 'first:second' "
1198 "also sets this option from 'second:first'."
1199 msgstr ""
1200 "`--sites` 参数遵循 `from:to` 语法,其中当前 `from` 和 `to` 具有符号语义。从 `first:second` 设置选项也从 `second:first` 设置此选项。"
1201
1202 #. type: Plain text
1203 #: administration-drbdmanage.adoc:505
1204 msgid ""
1205 "DRBD event handler can be set in the 'common' section and per resource:"
1206 msgstr "可以在 `common` 部分和每个资源中设置DRBD事件处理程序:"
1207
1208 #. type: delimited block -
1209 #: administration-drbdmanage.adoc:508
1210 #, no-wrap
1211 msgid ""
1212 "# drbdmanage handlers --common --after-resync-target /path/to/script.sh\n"
1213 msgstr ""
1214 "# drbdmanage handlers --common --after-resync-target /path/to/script.sh\n"
1215
1216 #. type: delimited block -
1217 #: administration-drbdmanage.adoc:512
1218 #, no-wrap
1219 msgid "# drbdmanage handlers --common --unset-after-resync-target\n"
1220 msgstr "# drbdmanage handlers --common --unset-after-resync-target\n"
1221
1222 #. type: delimited block -
1223 #: administration-drbdmanage.adoc:516
1224 #, no-wrap
1225 msgid ""
1226 "# drbdmanage handlers --resource backups --after-resync-target "
1227 "/path/to/script.sh\n"
1228 msgstr ""
1229 "# drbdmanage handlers --resource backups --after-resync-target "
1230 "/path/to/script.sh\n"
1231
1232 #. type: Title ===
1233 #: administration-drbdmanage.adoc:520
1234 #, no-wrap
1235 msgid "Rebalancing data with DRBD Manage"
1236 msgstr "使用DRBD Manage重新平衡数据"
1237
1238 #. type: Plain text
1239 #: administration-drbdmanage.adoc:525
1240 msgid ""
1241 "indexterm:[rebalance]Rebalancing data means moving some assignments around, "
1242 "to make better use of the available resources. We'll discuss the same "
1243 "example as for the <<s-rebalance-workflow,manual workflow>>."
1244 msgstr ""
1245 "indexterm:[rebalance]重新平衡数据意味着移动一些工作分配,以便更好地利用可用资源。我们将讨论与<<s-rebalance-"
1246 "workflow,manual workflow>>相同的示例。"
1247
1248 #. type: Plain text
1249 #: administration-drbdmanage.adoc:529
1250 msgid ""
1251 "Given is an example policy that data needs to be available on 3 nodes, so "
1252 "you need at least 3 servers for your setup."
1253 msgstr "给定的是一个示例策略,即数据需要在3个节点上可用,因此您的设置至少需要3个服务器。"
1254
1255 #. type: Plain text
1256 #: administration-drbdmanage.adoc:533
1257 msgid ""
1258 "Now, as your storage demands grow, you will encounter the need for "
1259 "additional servers. Rather than having to buy 3 more servers at the same "
1260 "time, you can _rebalance_ your data across a single additional node."
1261 msgstr "现在,随着存储需求的增长,您将需要额外的服务器。不必同时购买3台以上的服务器,您可以在一个额外的节点上 _重新平衡_ 数据。"
1262
1263 #. type: Block title
1264 #: administration-drbdmanage.adoc:534
1265 #, no-wrap
1266 msgid "DRBD data rebalancing"
1267 msgstr "DRBD数据再平衡"
1268
1269 #. type: Target for macro image
1270 #: administration-drbdmanage.adoc:535
1271 #, no-wrap
1272 msgid "images/rebalance.svg"
1273 msgstr "images/rebalance.svg"
1274
1275 #. type: Plain text
1276 #: administration-drbdmanage.adoc:539
1277 msgid ""
1278 "First, you need to add the new machine to the cluster; see <<s-dm-add-node>>"
1279 " for the commands."
1280 msgstr "首先,需要将新机器添加到集群;有关命令,请参见<<s-dm-add-node>>。"
1281
1282 #. type: Plain text
1283 #: administration-drbdmanage.adoc:541
1284 msgid "The next step is to add the assignment:"
1285 msgstr "下一步是添加分配:"
1286
1287 #. type: delimited block -
1288 #: administration-drbdmanage.adoc:544
1289 #, no-wrap
1290 msgid "# drbdmanage assign <resource> <new-node>\n"
1291 msgstr "# drbdmanage assign <resource> <new-node>\n"
1292
1293 #. type: Plain text
1294 #: administration-drbdmanage.adoc:548
1295 msgid ""
1296 "Now you need to wait for the (initial) sync to finish; you can e.g. use the "
1297 "command `drbdadm status` with (optionally) the resource name."
1298 msgstr "现在您需要等待(初始)同步完成;您可以使用命令 `drbdadm status`(可选)和资源名称。"
1299
1300 #. type: Plain text
1301 #: administration-drbdmanage.adoc:550
1302 msgid "One of the nodes that _still_ has the data will show a status like"
1303 msgstr "其中一个 _仍有_ 数据的节点将显示如下状态"
1304
1305 #. type: delimited block -
1306 #: administration-drbdmanage.adoc:553
1307 #, no-wrap
1308 msgid "replication:SyncSource peer-disk:Inconsistent done:5.34\n"
1309 msgstr "replication:SyncSource peer-disk:Inconsistent done:5.34\n"
1310
1311 #. type: Plain text
1312 #: administration-drbdmanage.adoc:556
1313 msgid "while the target node will have a state of _SyncTarget_."
1314 msgstr "而目标节点的状态为 _SyncTarget_ 。"
1315
1316 #. type: Plain text
1317 #: administration-drbdmanage.adoc:561
1318 msgid ""
1319 "When the target assignment reaches a state of _UpToDate_, you have a full "
1320 "additional copy of your data on this node; now it is safe to remove the "
1321 "assignment from another node:"
1322 msgstr "当目标分配达到 _UpToDate_ 状态时,此节点上的数据会有一个完整的附加副本;现在可以安全地从另一个节点删除该分配:"
1323
1324 #. type: delimited block -
1325 #: administration-drbdmanage.adoc:564
1326 #, no-wrap
1327 msgid "# drbdmanage unassign <resource> <old-node>\n"
1328 msgstr "# drbdmanage unassign <resource> <old-node>\n"
1329
1330 #. type: Plain text
1331 #: administration-drbdmanage.adoc:568
1332 msgid ""
1333 "And voilà - you moved one assignment, in twofootnote:[Or three, if you count"
1334 " waiting for the _UpToDate_ state.] easy steps!"
1335 msgstr "你移动了两个作业的一个 footnote:[或者三个,如果你数着等待 _UpToDate_ 状态的话。], 简单的步骤!"
1336
1337 #. type: Title ===
1338 #: administration-drbdmanage.adoc:571
1339 #, no-wrap
1340 msgid "Getting help"
1341 msgstr "得到帮助"
1342
1343 #. type: Plain text
1344 #: administration-drbdmanage.adoc:574
1345 msgid ""
1346 "The easiest way to get an overview about drbdmanage's subcommands is to read"
1347 " the main man-page (`man drbdmanage`)."
1348 msgstr "了解drbdmanage子命令的最简单方法是阅读主手册页(`man drbdmanage`)。"
1349
1350 #. type: Plain text
1351 #: administration-drbdmanage.adoc:577
1352 msgid ""
1353 "A quick way to list available commands on the command line is to type "
1354 "`drbdmanage list`."
1355 msgstr "在命令行中列出可用命令的一种快速方法是键入 `drbdmanage list` 。"
1356
1357 #. type: Plain text
1358 #: administration-drbdmanage.adoc:580
1359 msgid ""
1360 "Further information on subcommands (e.g., list-nodes) can be retrieved in "
1361 "three ways:"
1362 msgstr "有关子命令(例如列表节点)的更多信息可以通过三种方式检索:"
1363
1364 #. type: delimited block -
1365 #: administration-drbdmanage.adoc:585
1366 #, no-wrap
1367 msgid ""
1368 "# man drbdmanage-list-nodes\n"
1369 "# drbdmanage list-nodes -h\n"
1370 "# drbdmanage help list-nodes\n"
1371 msgstr ""
1372 "# man drbdmanage-list-nodes\n"
1373 "# drbdmanage list-nodes -h\n"
1374 "# drbdmanage help list-nodes\n"
1375
1376 #. type: Plain text
1377 #: administration-drbdmanage.adoc:589
1378 msgid ""
1379 "Using the 'help' subcommand is especially helpful when drbdmanage is "
1380 "executed in interactive mode (`drbdmanage interactive`)."
1381 msgstr "在交互模式(`drbdmanage interactive`)下执行drbdmanage时,使用'help'子命令尤其有用。"
1382
1383 #. type: Plain text
1384 #: administration-drbdmanage.adoc:594
1385 msgid ""
1386 "One of the most helpful features of drbdmanage is its rich tab-completion, "
1387 "which can be used to complete basically every object drbdmanage knows about "
1388 "(e.g., node names, IP addresses, resource names, ...). In the following we "
1389 "show some possible completions, and their results:"
1390 msgstr ""
1391 "drbdmanage最有用的特性之一是它丰富的tab 补全"
1392 ",它基本上可以用来完成drbdmanage所知道的每个对象(例如,节点名、IP地址、资源名等等)。在下面我们将展示一些可能的完工情况及其结果:"
1393
1394 #. type: delimited block -
1395 #: administration-drbdmanage.adoc:598
1396 #, no-wrap
1397 msgid ""
1398 "# drbdmanage add-node alpha 1<tab> # completes the IP address if hostname can be resolved\n"
1399 "# drbdmanage assign-resource b<tab> c<tab> # drbdmanage assign-resource backups charlie\n"
1400 msgstr ""
1401 "# drbdmanage add-node alpha 1<tab> # completes the IP address if hostname can be resolved\n"
1402 "# drbdmanage assign-resource b<tab> c<tab> # drbdmanage assign-resource backups charlie\n"
1403
1404 #. type: Plain text
1405 #: administration-drbdmanage.adoc:602
1406 msgid ""
1407 "If tab-completion does not work out of the box, please try to source the "
1408 "according file:"
1409 msgstr "如果tab补全完成不正常,请尝试获取相应的文件:"
1410
1411 #. type: delimited block -
1412 #: administration-drbdmanage.adoc:606
1413 #, no-wrap
1414 msgid ""
1415 "# source /etc/bash_completion.d/drbdmanage # or\n"
1416 "# source /usr/share/bash_completion/completions/drbdmanage\n"
1417 msgstr ""
1418 "# source /etc/bash_completion.d/drbdmanage # or\n"
1419 "# source /usr/share/bash_completion/completions/drbdmanage\n"