| 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 |
msgid "" |
| 7 |
msgstr "" |
| 8 |
"Project-Id-Version: PACKAGE VERSION\n" |
| 9 |
"POT-Creation-Date: 2020-06-06 09:24+0900\n" |
| 10 |
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" |
| 11 |
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" |
| 12 |
"Language-Team: LANGUAGE <[email protected]>\n" |
| 13 |
"Language: \n" |
| 14 |
"MIME-Version: 1.0\n" |
| 15 |
"Content-Type: text/plain; charset=UTF-8\n" |
| 16 |
"Content-Transfer-Encoding: 8bit\n" |
| 17 |
|
| 18 |
#. type: Title == |
| 19 |
#, no-wrap |
| 20 |
msgid "Troubleshooting and error recovery" |
| 21 |
msgstr "トラブルシューティングとエラーからの回復" |
| 22 |
|
| 23 |
#. type: Plain text |
| 24 |
msgid "" |
| 25 |
"This chapter describes tasks to be performed in the event of hardware or " |
| 26 |
"system failures." |
| 27 |
msgstr "" |
| 28 |
"この章では、ハードウェアやシステムに障害が発生した場合に必要な手順について説" |
| 29 |
"明します。" |
| 30 |
|
| 31 |
#. type: Title === |
| 32 |
#, no-wrap |
| 33 |
msgid "Dealing with hard drive failure" |
| 34 |
msgstr "ハードドライブの障害の場合" |
| 35 |
|
| 36 |
#. type: Plain text |
| 37 |
msgid "" |
| 38 |
"indexterm:[drive failure]indexterm:[disk failure]How to deal with hard drive " |
| 39 |
"failure depends on the way DRBD is configured to handle disk I/O errors (see " |
| 40 |
"<<s-handling-disk-errors>>), and on the type of meta data configured (see " |
| 41 |
"<<s-metadata>>)." |
| 42 |
msgstr "" |
| 43 |
"indexterm:[drive failure]indexterm:[disk failure]ハードドライブの障害への対処" |
| 44 |
"方法は、DRBDがディスクI/Oエラーを処理する方法(<<s-handling-disk-errors>>参" |
| 45 |
"照)、また設定されているメタデータの種類(<<s-metadata>>参照)によって異なりま" |
| 46 |
"す。" |
| 47 |
|
| 48 |
#. type: delimited block = |
| 49 |
msgid "" |
| 50 |
"For the most part, the steps described here apply only if you run DRBD " |
| 51 |
"directly on top of physical hard drives. They generally do not apply in case " |
| 52 |
"you are running DRBD layered on top of" |
| 53 |
msgstr "" |
| 54 |
"ほとんどの場合、ここで取り上げる手順はDRBDを直接物理ハードドライブ上で実行し" |
| 55 |
"ている場合にのみ適用されます。次に示す層の上でDRBDを実行している場合には通常" |
| 56 |
"は適用されません。" |
| 57 |
|
| 58 |
#. type: delimited block = |
| 59 |
msgid "" |
| 60 |
"an MD software RAID set (in this case, use `mdadm` to manage drive " |
| 61 |
"replacement)," |
| 62 |
msgstr "MDソフトウェアRAIDセット( `mdadm` を使用してドライブ交換を管理)" |
| 63 |
|
| 64 |
#. type: delimited block = |
| 65 |
msgid "device-mapper RAID (use `dmraid`)," |
| 66 |
msgstr "デバイスマッパRAID( `dmraid` 使用)" |
| 67 |
|
| 68 |
#. type: delimited block = |
| 69 |
msgid "" |
| 70 |
"a hardware RAID appliance (follow the vendor's instructions on how to deal " |
| 71 |
"with failed drives)," |
| 72 |
msgstr "" |
| 73 |
"ハードウェアRAID機器 (障害が発生したドライブの扱いについてはベンダーの指示に" |
| 74 |
"従ってください)" |
| 75 |
|
| 76 |
#. type: delimited block = |
| 77 |
msgid "" |
| 78 |
"some non-standard device-mapper virtual block devices (see the device mapper " |
| 79 |
"documentation)." |
| 80 |
msgstr "" |
| 81 |
"一部の非標準デバイスマッパ仮想ブロックデバイス(デバイスマッパのマニュアルを参" |
| 82 |
"照してください)" |
| 83 |
|
| 84 |
#. type: Title ==== |
| 85 |
#, no-wrap |
| 86 |
msgid "Manually detaching DRBD from your hard drive" |
| 87 |
msgstr "手動でDRBDをハードドライブから切り離す" |
| 88 |
|
| 89 |
#. type: Plain text |
| 90 |
msgid "" |
| 91 |
"indexterm:[drbdadm, detach]If DRBD is <<fp-io-error-pass-on,configured to " |
| 92 |
"pass on I/O errors>> (not recommended), you must first detach the DRBD " |
| 93 |
"resource, that is, disassociate it from its backing storage:" |
| 94 |
msgstr "" |
| 95 |
"indexterm:[drbdadm]DRBDが<<fp-io-error-pass-on,I/Oエラーを伝えるように設定" |
| 96 |
">>(非推奨)している場合、まずDRBDリソースを切り離すとよいでしょう。つまり、下" |
| 97 |
"位デバイスからの切り離しです。" |
| 98 |
|
| 99 |
#. type: delimited block - |
| 100 |
#, no-wrap |
| 101 |
msgid "# drbdadm detach <resource>\n" |
| 102 |
msgstr "# drbdadm detach <resource>\n" |
| 103 |
|
| 104 |
#. type: Plain text |
| 105 |
msgid "" |
| 106 |
"By running the `drbdadm status` or the `drbdadm dstate` command, you will " |
| 107 |
"now be able to verify that the resource is now in indexterm:[diskless " |
| 108 |
"mode]indexterm:[diskless (disk state)]indexterm:[disk state, " |
| 109 |
"Diskless]_diskless mode_:" |
| 110 |
msgstr "" |
| 111 |
"`drbdadm status` footnote:[以前は `drbdadm dstate` コマンドを推奨していまし" |
| 112 |
"た]コマンドを実行することで、現在の状態を確認することができます。" |
| 113 |
|
| 114 |
#. type: delimited block - |
| 115 |
#, no-wrap |
| 116 |
msgid "" |
| 117 |
"# drbdadm status <resource>\n" |
| 118 |
"<resource> role:Primary\n" |
| 119 |
" volume:0 disk:Diskless\n" |
| 120 |
" <peer> role:Secondary\n" |
| 121 |
" volume:0 peer-disk:UpToDate\n" |
| 122 |
"# drbdadm dstate <resource>\n" |
| 123 |
"Diskless/UpToDate\n" |
| 124 |
msgstr "" |
| 125 |
"# drbdadm status <resource>\n" |
| 126 |
"<resource> role:Primary\n" |
| 127 |
" volume:0 disk:Diskless\n" |
| 128 |
" <peer> role:Secondary\n" |
| 129 |
" volume:0 peer-disk:UpToDate\n" |
| 130 |
"# drbdadm dstate <resource>\n" |
| 131 |
"Diskless/UpToDate\n" |
| 132 |
|
| 133 |
#. type: Plain text |
| 134 |
msgid "" |
| 135 |
"If the disk failure has occurred on your primary node, you may combine this " |
| 136 |
"step with a switch-over operation." |
| 137 |
msgstr "" |
| 138 |
"ディスク障害がプライマリノードで発生した場合、スイッチオーバーと、この手順を" |
| 139 |
"組み合わせることもできます。" |
| 140 |
|
| 141 |
#. type: Title ==== |
| 142 |
#, no-wrap |
| 143 |
msgid "Automatic detach on I/O error" |
| 144 |
msgstr "I/Oエラー時の自動切り離し" |
| 145 |
|
| 146 |
#. type: Plain text |
| 147 |
msgid "" |
| 148 |
"If DRBD is <<fp-io-error-detach,configured to automatically detach upon I/O " |
| 149 |
"error>> (the recommended option), DRBD should have automatically detached " |
| 150 |
"the resource from its backing storage already, without manual intervention. " |
| 151 |
"You may still use the `drbdadm status` command to verify that the resource " |
| 152 |
"is in fact running in diskless mode." |
| 153 |
msgstr "" |
| 154 |
"DRBDが<<fp-io-error-detach,I/Oエラー時に自動的に切り離しを行うように設定>>(推" |
| 155 |
"奨オプション)されている場合、 手動での操作なしで、DRBDはすでにリソースを下位" |
| 156 |
"ストレージから自動的に切り離しているはずです。その場合でも `drbdadm status` " |
| 157 |
"コマンドを使用して、リソースが実際にディスクレスモードで実行されているか確認" |
| 158 |
"します。" |
| 159 |
|
| 160 |
#. type: Title ==== |
| 161 |
#, no-wrap |
| 162 |
msgid "Replacing a failed disk when using internal meta data" |
| 163 |
msgstr "障害が発生したディスクの交換(内部メタデータを使用している場合)" |
| 164 |
|
| 165 |
#. type: Plain text |
| 166 |
msgid "" |
| 167 |
"If using <<s-internal-meta-data,internal meta data>>, it is sufficient to " |
| 168 |
"bind the DRBD device to the new hard disk. If the new hard disk has to be " |
| 169 |
"addressed by another Linux device name than the defective disk, the DRBD " |
| 170 |
"configuration file has to be modified accordingly." |
| 171 |
msgstr "" |
| 172 |
"<<s-internal-meta-data,内部メタデータ>>を使用している場合、新しいハードディス" |
| 173 |
"クでDRBDデバイスを再構成するだけで十分です。交換したハードディスクのデバイス" |
| 174 |
"名が交換前と異なる場合は、DRBD設定ファイルを適切に変更してください。" |
| 175 |
|
| 176 |
#. type: Plain text |
| 177 |
msgid "" |
| 178 |
"This process involves creating a new meta data set, then re-attaching the " |
| 179 |
"resource: indexterm:[drbdadm, create-md]" |
| 180 |
msgstr "" |
| 181 |
"新しいメタデータを作成してから、リソースを再接続します。 indexterm:[drbdadm]" |
| 182 |
|
| 183 |
#. type: delimited block - |
| 184 |
#, no-wrap |
| 185 |
msgid "" |
| 186 |
"# drbdadm create-md <resource>\n" |
| 187 |
"v08 Magic number not found\n" |
| 188 |
"Writing meta data...\n" |
| 189 |
"initialising activity log\n" |
| 190 |
"NOT initializing bitmap\n" |
| 191 |
"New drbd meta data block successfully created.\n" |
| 192 |
msgstr "" |
| 193 |
"# drbdadm create-md <resource>\n" |
| 194 |
"v08 Magic number not found\n" |
| 195 |
"Writing meta data...\n" |
| 196 |
"initialising activity log\n" |
| 197 |
"NOT initializing bitmap\n" |
| 198 |
"New drbd meta data block successfully created.\n" |
| 199 |
|
| 200 |
#. type: delimited block - |
| 201 |
#, no-wrap |
| 202 |
msgid "# drbdadm attach <resource>\n" |
| 203 |
msgstr "# drbdadm attach <resource>\n" |
| 204 |
|
| 205 |
#. type: Plain text |
| 206 |
msgid "" |
| 207 |
"Full synchronization of the new hard disk starts instantaneously and " |
| 208 |
"automatically. You will be able to monitor the synchronization's progress " |
| 209 |
"via `drbdadm status --verbose`, as with any background synchronization." |
| 210 |
msgstr "" |
| 211 |
"新しいハードディスクの完全同期がただちに自動的に始まります。通常のバックグラ" |
| 212 |
"ウンド同期と同様、同期の進行状況を `drbdadm status --verbose` で監視すること" |
| 213 |
"ができます。" |
| 214 |
|
| 215 |
#. type: Title ==== |
| 216 |
#, no-wrap |
| 217 |
msgid "Replacing a failed disk when using external meta data" |
| 218 |
msgstr "障害の発生したディスクの交換(外部メタデータを使用している場合)" |
| 219 |
|
| 220 |
#. type: Plain text |
| 221 |
msgid "" |
| 222 |
"When using <<s-external-meta-data,external meta data>>, the procedure is " |
| 223 |
"basically the same. However, DRBD is not able to recognize independently " |
| 224 |
"that the hard drive was swapped, thus an additional step is required." |
| 225 |
msgstr "" |
| 226 |
"<<s-external-meta-data,外部メタデータ>>を使用している場合でも、手順は基本的に" |
| 227 |
"同じです。ただし、DRBDだけではハードドライブが交換されたことを認識できないた" |
| 228 |
"め、追加の手順が必要です。" |
| 229 |
|
| 230 |
#. type: delimited block - |
| 231 |
#, no-wrap |
| 232 |
msgid "" |
| 233 |
"# drbdadm attach <resource>\n" |
| 234 |
"# drbdadm invalidate <resource>\n" |
| 235 |
msgstr "" |
| 236 |
"# drbdadm attach <resource>\n" |
| 237 |
"# drbdadm invalidate <resource>\n" |
| 238 |
|
| 239 |
#. type: Plain text |
| 240 |
msgid "" |
| 241 |
"Make sure to run `drbdadm invalidate` on the node __*without*__ good data; " |
| 242 |
"this command will cause the local contents to be overwritten with data from " |
| 243 |
"the peers, so running this command on the wrong node might lose data!" |
| 244 |
msgstr "" |
| 245 |
"`drbdadm invalidate` は、必ず破棄するデータのある側のノードでを実行してくださ" |
| 246 |
"い。 このコマンドはローカルのデータを対向ノードからのデータで上書きさせます。" |
| 247 |
"つまり、このコマンドを実行すると破棄する側のノードのデータが失われます。" |
| 248 |
|
| 249 |
#. type: Plain text |
| 250 |
msgid "" |
| 251 |
"Here, the `drbdadm invalidate` command triggers synchronization. Again, sync " |
| 252 |
"progress may be observed via `drbdadm status --verbose`." |
| 253 |
msgstr "" |
| 254 |
"上記の `drbdadm invalidate` コマンドが同期をトリガーします。この場合でも、同" |
| 255 |
"期の進行状況は `drbdadm status --verbose` で確認できます。" |
| 256 |
|
| 257 |
#. type: Title === |
| 258 |
#, no-wrap |
| 259 |
msgid "Dealing with node failure" |
| 260 |
msgstr "ノード障害に対処する" |
| 261 |
|
| 262 |
#. type: Plain text |
| 263 |
msgid "" |
| 264 |
"indexterm:[node failure]When DRBD detects that its peer node is down (either " |
| 265 |
"by true hardware failure or manual intervention), DRBD changes its " |
| 266 |
"connection state from _Connected_ to _Connecting_ and waits for the peer " |
| 267 |
"node to re-appear. The DRBD resource is then said to operate in " |
| 268 |
"_disconnected mode_. In disconnected mode, the resource and its associated " |
| 269 |
"block device are fully usable, and may be promoted and demoted as necessary, " |
| 270 |
"but no block modifications are being replicated to the peer node. Instead, " |
| 271 |
"DRBD stores which blocks are being modified while disconnected, on a per-" |
| 272 |
"peer basis." |
| 273 |
msgstr "" |
| 274 |
"indexterm:[node failure]DRBDが(実際のハードウェア障害であれ手動による介入であ" |
| 275 |
"れ)対向ノードがダウンしていることを検出すると、DRBDは自身のコネクションステー" |
| 276 |
"タスを `Connected` から `WFConnection` に変更し、対向ノードが再び現れるのを待" |
| 277 |
"ちます。その後、DRBDリソースは _disconnected mode(切断モード)_ で動作します。" |
| 278 |
"切断モードでは、リソースおよびリソースに関連付けられたブロックデバイスが完全" |
| 279 |
"に利用可能で、必要に応じて昇格したり降格したりします。ただし、ブロックの変更" |
| 280 |
"は対向ノードにレプリケートされません。切断中に変更されたブロックについての内" |
| 281 |
"部情報は対向ノードごとにDRBDが格納します。" |
| 282 |
|
| 283 |
#. type: Title ==== |
| 284 |
#, no-wrap |
| 285 |
msgid "Dealing with temporary secondary node failure" |
| 286 |
msgstr "一時的なセカンダリノードの障害に対処する" |
| 287 |
|
| 288 |
#. type: Plain text |
| 289 |
msgid "" |
| 290 |
"indexterm:[node failure]If a node that currently has a resource in the " |
| 291 |
"secondary role fails temporarily (due to, for example, a memory problem that " |
| 292 |
"is subsequently rectified by replacing RAM), no further intervention is " |
| 293 |
"necessary — besides the obvious necessity to repair the failed node and " |
| 294 |
"bring it back online. When that happens, the two nodes will simply re-" |
| 295 |
"establish connectivity upon system start-up. After this, DRBD synchronizes " |
| 296 |
"all modifications made on the primary node in the meantime to the secondary " |
| 297 |
"node." |
| 298 |
msgstr "" |
| 299 |
"indexterm:[node failure]セカンダリロールでリソースを持っているノードに一時的" |
| 300 |
"に障害が生じた場合(たとえばメモリ交換で直るようなメモリの問題)には、障害が発" |
| 301 |
"生したノードを修復してオンラインに戻すだけで十分です。修正したノードを起動す" |
| 302 |
"ると、ノード間の接続が再確立され、停止中にプライマリノードに加えられた変更内" |
| 303 |
"容すべてがセカンダリノードに同期されます。" |
| 304 |
|
| 305 |
#. type: Plain text |
| 306 |
msgid "" |
| 307 |
"At this point, due to the nature of DRBD's re-synchronization algorithm, the " |
| 308 |
"resource is briefly inconsistent on the secondary node. During that short " |
| 309 |
"time window, the secondary node can not switch to the Primary role if the " |
| 310 |
"peer is unavailable. Thus, the period in which your cluster is not redundant " |
| 311 |
"consists of the actual secondary node down time, plus the subsequent re-" |
| 312 |
"synchronization." |
| 313 |
msgstr "" |
| 314 |
"この時点で、DRBDの再同期アルゴリズムの性質により、セカンダリノードのリソース" |
| 315 |
"の一貫性が一時的に失われます。この短時間の再同期の間は、対向ホストが使用でき" |
| 316 |
"ない場合でも、セカンダリノードをプライマリロールに切り替えることができませ" |
| 317 |
"ん。したがって、セカンダリノードの実際のダウンタイムとその後の再同期の間は、" |
| 318 |
"クラスタが冗長性を持たない期間になります。" |
| 319 |
|
| 320 |
#. type: Plain text |
| 321 |
msgid "" |
| 322 |
"Please note that with DRBD 9 more than two nodes can be connected for each " |
| 323 |
"resource, so for e.g. 4 nodes a single failing secondary still leaves two " |
| 324 |
"other secondaries available for failover." |
| 325 |
msgstr "" |
| 326 |
"DRBD9では各リソースに3ノード以上が接続することができます。そのため、例えば4" |
| 327 |
"ノードでは一度フェイルオーバーしてもまだ2回フェイルオーバーすることができま" |
| 328 |
"す。" |
| 329 |
|
| 330 |
#. type: Title ==== |
| 331 |
#, no-wrap |
| 332 |
msgid "Dealing with temporary primary node failure" |
| 333 |
msgstr "一時的なプライマリノードの障害に対処する" |
| 334 |
|
| 335 |
#. type: Plain text |
| 336 |
msgid "" |
| 337 |
"indexterm:[node failure]From DRBD's standpoint, failure of the primary node " |
| 338 |
"is almost identical to a failure of the secondary node. The surviving node " |
| 339 |
"detects the peer node's failure, and switches to disconnected mode. DRBD " |
| 340 |
"does _not_ promote the surviving node to the primary role; it is the cluster " |
| 341 |
"management application's responsibility to do so." |
| 342 |
msgstr "" |
| 343 |
"indexterm:[node failure]DRBDからみると、プライマリノードの障害とセカンダリ" |
| 344 |
"ノードの障害はほぼ同じです。生き残ったノードが対向ノードの障害を検出し、切断" |
| 345 |
"モードに切り替わります。DRBDは生き残ったノードをプライマリロールに _昇格しま" |
| 346 |
"せん_ 。これはクラスタ管理システムが管理します。" |
| 347 |
|
| 348 |
#. type: Plain text |
| 349 |
msgid "" |
| 350 |
"When the failed node is repaired and returns to the cluster, it does so in " |
| 351 |
"the secondary role, thus, as outlined in the previous section, no further " |
| 352 |
"manual intervention is necessary. Again, DRBD does not change the resource " |
| 353 |
"role back, it is up to the cluster manager to do so (if so configured)." |
| 354 |
msgstr "" |
| 355 |
"障害が発生したノードが修復されてクラスタに戻る際に、セカンダリロールになりま" |
| 356 |
"す。すでに述べたように、それ以上の手動による介入は必要ありません。このときも" |
| 357 |
"DRBDはリソースのロールを元に戻しません。変更を行うように設定されている場合" |
| 358 |
"は、クラス管理システムがこの変更を行います。" |
| 359 |
|
| 360 |
#. type: Plain text |
| 361 |
msgid "" |
| 362 |
"DRBD ensures block device consistency in case of a primary node failure by " |
| 363 |
"way of a special mechanism. For a detailed discussion, refer to <<s-activity-" |
| 364 |
"log>>." |
| 365 |
msgstr "" |
| 366 |
"プライマリノードに障害が発生すると、DRBDはアクティビティログというメカニズム" |
| 367 |
"によってブロックデバイスの整合性を確保します。詳細は<<s-activity-log>>を参照" |
| 368 |
"ください。" |
| 369 |
|
| 370 |
#. type: Title ==== |
| 371 |
#, no-wrap |
| 372 |
msgid "Dealing with permanent node failure" |
| 373 |
msgstr "永続的なノード障害に対処する" |
| 374 |
|
| 375 |
#. type: Plain text |
| 376 |
msgid "" |
| 377 |
"indexterm:[node failure]If a node suffers an unrecoverable problem or " |
| 378 |
"permanent destruction, you must follow the following steps:" |
| 379 |
msgstr "" |
| 380 |
"indexterm:[node failure]ノードに回復不能な問題が発生した場合やノードが永久的" |
| 381 |
"に破損した場合は、次の手順を行う必要があります。" |
| 382 |
|
| 383 |
#. type: Plain text |
| 384 |
msgid "" |
| 385 |
"Replace the failed hardware with one with similar performance and disk " |
| 386 |
"capacity." |
| 387 |
msgstr "" |
| 388 |
"障害が発生したハードウェアを同様のパフォーマンスと ディスク容量を持つハード" |
| 389 |
"ウェアと交換します。" |
| 390 |
|
| 391 |
#. type: Plain text |
| 392 |
msgid "" |
| 393 |
"Replacing a failed node with one with worse performance characteristics is " |
| 394 |
"possible, but not recommended. Replacing a failed node with one with less " |
| 395 |
"disk capacity is not supported, and will cause DRBD to refuse to connect to " |
| 396 |
"the replaced nodefootnote:[It couldn't replicate the data, anyway!]." |
| 397 |
msgstr "" |
| 398 |
"障害が発生したノードを、それよりパフォーマンスが低いものと置き換えることも可" |
| 399 |
"能ですが、お勧めはできません。障害が発生したノードを、それよりディスク容量が" |
| 400 |
"小さいものと置き換えることはできません。このような場合には、DRBDを置き換えた" |
| 401 |
"ノードへの接続は拒否されます。footnote:[結局はレプリケーションできません]" |
| 402 |
|
| 403 |
#. type: Plain text |
| 404 |
msgid "Install the base system and applications." |
| 405 |
msgstr "OSとアプリケーションをインストールします。" |
| 406 |
|
| 407 |
#. type: Plain text |
| 408 |
msgid "" |
| 409 |
"Install DRBD and copy `/etc/drbd.conf` and all of `/etc/drbd.d/` from one of " |
| 410 |
"the surviving nodes." |
| 411 |
msgstr "" |
| 412 |
"DRBDをインストールし、生き残ったノードから `/etc/drbd.conf` と、全ての `/etc/" |
| 413 |
"drbd.d/` を コピーします。" |
| 414 |
|
| 415 |
#. type: Plain text |
| 416 |
msgid "Follow the steps outlined in <<ch-configure>>, but stop short" |
| 417 |
msgstr "<<ch-configure>>に記載された手順を、" |
| 418 |
|
| 419 |
#. type: Plain text |
| 420 |
msgid "of <<s-initial-full-sync>>." |
| 421 |
msgstr "<<s-initial-full-sync>>の前まで実行します。" |
| 422 |
|
| 423 |
#. type: Plain text |
| 424 |
msgid "" |
| 425 |
"Manually starting a full device synchronization is not necessary at this " |
| 426 |
"point, it will commence automatically upon connection to the surviving " |
| 427 |
"primary and/or secondary node(s)." |
| 428 |
msgstr "" |
| 429 |
"この時点で、デバイスの完全同期を手動で開始する必要はありません。生き残ったプ" |
| 430 |
"ライマリノードへの接続時に、同期が自動的に開始します。" |
| 431 |
|
| 432 |
#. type: Title === |
| 433 |
#, no-wrap |
| 434 |
msgid "Manual split brain recovery" |
| 435 |
msgstr "スプリットブレインからの手動回復" |
| 436 |
|
| 437 |
#. type: Plain text |
| 438 |
msgid "" |
| 439 |
"indexterm:[split brain]DRBD detects split brain at the time connectivity " |
| 440 |
"becomes available again and the peer nodes exchange the initial DRBD " |
| 441 |
"protocol handshake. If DRBD detects that both nodes are (or were at some " |
| 442 |
"point, while disconnected) in the primary role, it immediately tears down " |
| 443 |
"the replication connection. The tell-tale sign of this is a message like the " |
| 444 |
"following appearing in the system log:" |
| 445 |
msgstr "" |
| 446 |
"indexterm:[split brain]ノード間の接続が可能になると、ノード間で初期ハンドシェ" |
| 447 |
"イクのプロトコルが交換されます。この時点でDRBDはスプリットブレインが発生した" |
| 448 |
"かどうかを判断できます。両方のノードがプライマリロールであるか、もしくは切断" |
| 449 |
"中に両方がプライマリロールになったことを検出すると、DRBDは即座にレプリケー" |
| 450 |
"ション接続を切断します。その場合、システムログにたとえば次のようなメッセージ" |
| 451 |
"が記録されます。" |
| 452 |
|
| 453 |
#. type: delimited block - |
| 454 |
#, no-wrap |
| 455 |
msgid "Split-Brain detected, dropping connection!\n" |
| 456 |
msgstr "Split-Brain detected, dropping connection!\n" |
| 457 |
|
| 458 |
#. type: Plain text |
| 459 |
msgid "" |
| 460 |
"After split brain has been detected, one node will always have the resource " |
| 461 |
"in a indexterm:[StandAlone (connection state)]indexterm:[connection " |
| 462 |
"state]_StandAlone_ connection state. The other might either also be in the " |
| 463 |
"_StandAlone_ state (if both nodes detected the split brain simultaneously), " |
| 464 |
"or in indexterm:[Connecting (connection state)] indexterm:[connection " |
| 465 |
"state]_Connecting_ (if the peer tore down the connection before the other " |
| 466 |
"node had a chance to detect split brain)." |
| 467 |
msgstr "" |
| 468 |
"スプリットブレインが検出されると、1つのノードは常にindexterm:[StandAlone " |
| 469 |
"(connection state)]indexterm:[connection state]_StandAlone_ の状態でリソース" |
| 470 |
"を保持します。もう一方のノードもまた _StandAlone_ 状態になる(両方のノードが同" |
| 471 |
"時にスプリットブレインを検出した場合)、または indexterm:[WFConnection " |
| 472 |
"(connection state)] indexterm:[connection state] _WFConnection_ 状態になりま" |
| 473 |
"す(一方のノードがスプリットブレインを検出する前に対向ノードが切断をした場" |
| 474 |
"合)。" |
| 475 |
|
| 476 |
#. type: Plain text |
| 477 |
msgid "" |
| 478 |
"At this point, unless you configured DRBD to automatically recover from " |
| 479 |
"split brain, you must manually intervene by selecting one node whose " |
| 480 |
"modifications will be discarded (this node is referred to as the indexterm:" |
| 481 |
"[split brain]_split brain victim_). This intervention is made with the " |
| 482 |
"following commands:" |
| 483 |
msgstr "" |
| 484 |
"DRBDがスプリットブレインから自動的に回復するように設定されていない場合は、こ" |
| 485 |
"の時点で手動で介入して、変更内容を破棄するほうのノードを選択する必要がありま" |
| 486 |
"す(このノードは _スプリットブレインの犠牲ノード_ と呼ばれる)。indexterm:" |
| 487 |
"[split brain]この介入は次のコマンドで行います。" |
| 488 |
|
| 489 |
#. type: delimited block = |
| 490 |
msgid "This is still _work in progress_." |
| 491 |
msgstr "ここは現在 _作業中_ です。" |
| 492 |
|
| 493 |
#. type: delimited block = |
| 494 |
msgid "Expect rough edges and changes." |
| 495 |
msgstr "構成の変更が行われる予定です。" |
| 496 |
|
| 497 |
#. [NOTE] |
| 498 |
#. =========================== |
| 499 |
#. The split brain victim needs to be in the connection state of |
| 500 |
#. _StandAlone_ or the following commands will return an error. |
| 501 |
#. You can ensure it is standalone by issuing: |
| 502 |
#. ---------- |
| 503 |
#. # drbdadm disconnect <resource> |
| 504 |
#. ---------- |
| 505 |
#. =========================== |
| 506 |
#. type: delimited block - |
| 507 |
#, no-wrap |
| 508 |
msgid "" |
| 509 |
"# drbdadm disconnect <resource>\n" |
| 510 |
"# drbdadm secondary <resource>\n" |
| 511 |
"# drbdadm connect --discard-my-data <resource>\n" |
| 512 |
msgstr "" |
| 513 |
"# drbdadm disconnect <resource>\n" |
| 514 |
"# drbdadm secondary <resource>\n" |
| 515 |
"# drbdadm connect --discard-my-data <resource>\n" |
| 516 |
|
| 517 |
#. type: Plain text |
| 518 |
msgid "" |
| 519 |
"On the other node (the indexterm:[split brain]_split brain survivor_), if " |
| 520 |
"its connection state is also _StandAlone_, you would enter:" |
| 521 |
msgstr "" |
| 522 |
"他方のノード(スプリットブレインのindexterm:[split brain]生存ノード)のコネク" |
| 523 |
"ションステータスも `StandAlone` の場合には、次のコマンド実行します。" |
| 524 |
|
| 525 |
#. type: delimited block - |
| 526 |
#, no-wrap |
| 527 |
msgid "" |
| 528 |
"# drbdadm disconnect <resource>\n" |
| 529 |
"# drbdadm connect <resource>\n" |
| 530 |
msgstr "" |
| 531 |
"# drbdadm disconnect <resource>\n" |
| 532 |
"# drbdadm connect <resource>\n" |
| 533 |
|
| 534 |
#. type: Plain text |
| 535 |
msgid "" |
| 536 |
"You may omit this step if the node is already in the _Connecting_ state; it " |
| 537 |
"will then reconnect automatically." |
| 538 |
msgstr "" |
| 539 |
"ノードがすでに _Connecting_ の状態の場合は自動的に再接続するので、この手順は" |
| 540 |
"省略できます。" |
| 541 |
|
| 542 |
#. type: Plain text |
| 543 |
msgid "" |
| 544 |
"Upon connection, your split brain victim immediately changes its connection " |
| 545 |
"state to _SyncTarget_, and gets its modifications overwritten by the other " |
| 546 |
"node(s)." |
| 547 |
msgstr "" |
| 548 |
"接続すると、スプリットブレインの犠牲ノードのコネクションステータスがすぐに " |
| 549 |
"_SyncTarget_ に変化し、他のノードによって変更内容が上書きされます。" |
| 550 |
|
| 551 |
#. type: Plain text |
| 552 |
msgid "" |
| 553 |
"The split brain victim is not subjected to a full device synchronization. " |
| 554 |
"Instead, it has its local modifications rolled back, and any modifications " |
| 555 |
"made on the split brain survivor(s) propagate to the victim." |
| 556 |
msgstr "" |
| 557 |
"スプリットブレインの犠牲ノードは、デバイスのフル同期の対象にはなりません。代" |
| 558 |
"わりに、ローカル側での変更がロールバックされ、スプリットブレインの生存ノード" |
| 559 |
"に対して加えられた変更が犠牲ノードに伝播されます。" |
| 560 |
|
| 561 |
#. type: Plain text |
| 562 |
msgid "" |
| 563 |
"After re-synchronization has completed, the split brain is considered " |
| 564 |
"resolved and the nodes form a fully consistent, redundant replicated storage " |
| 565 |
"system again." |
| 566 |
msgstr "" |
| 567 |
"再同期が完了すると、スプリットブレインが解決したとみなされ、2つのノードが再び" |
| 568 |
"完全に一致した冗長レプリケーションストレージシステムとして機能します。" |