Revision 6c4811dc doc/admin.sgml
| b/doc/admin.sgml | ||
|---|---|---|
| 185 | 185 |
<term>remote_raid1</term> |
| 186 | 186 |
<listitem> |
| 187 | 187 |
<simpara><emphasis role="strong">Note:</emphasis> This is only |
| 188 |
valid for multi-node clusters.</simpara> |
|
| 188 |
valid for multi-node clusters using drbd 0.7.</simpara>
|
|
| 189 | 189 |
<simpara> |
| 190 | 190 |
A mirror is set between the local node and a remote one, which |
| 191 | 191 |
must be specified with the second value of the --node option. Use |
| ... | ... | |
| 195 | 195 |
</listitem> |
| 196 | 196 |
</varlistentry> |
| 197 | 197 |
|
| 198 |
<varlistentry> |
|
| 199 |
<term>drbd</term> |
|
| 200 |
<listitem> |
|
| 201 |
<simpara><emphasis role="strong">Note:</emphasis> This is only |
|
| 202 |
valid for multi-node clusters using drbd 8.0.</simpara> |
|
| 203 |
<simpara> |
|
| 204 |
This is similar to the |
|
| 205 |
<replaceable>remote_raid1</replaceable> option, but uses |
|
| 206 |
new features in drbd 8 to simplify the device |
|
| 207 |
stack. From a user's point of view, this will improve |
|
| 208 |
the speed of the <command>replace-disks</command> |
|
| 209 |
command and (in future versions) provide more |
|
| 210 |
functionality. |
|
| 211 |
</simpara> |
|
| 212 |
</listitem> |
|
| 213 |
</varlistentry> |
|
| 214 |
|
|
| 198 | 215 |
</variablelist> |
| 199 | 216 |
|
| 200 | 217 |
<para> |
| 201 | 218 |
For example if you want to create an highly available instance use the |
| 202 |
remote_raid1 disk template:
|
|
| 219 |
remote_raid1 or drbd disk templates:
|
|
| 203 | 220 |
<synopsis>gnt-instance add -n <replaceable>TARGET_NODE</replaceable><optional>:<replaceable>SECONDARY_NODE</replaceable></optional> -o <replaceable>OS_TYPE</replaceable> -t remote_raid1 \ |
| 204 | 221 |
<replaceable>INSTANCE_NAME</replaceable></synopsis> |
| 205 | 222 |
|
| ... | ... | |
| 312 | 329 |
failed, or you plan to remove a node from your cluster, and |
| 313 | 330 |
you failed over all its instances, but it's still secondary |
| 314 | 331 |
for some? The solution here is to replace the instance disks, |
| 315 |
changing the secondary node: |
|
| 332 |
changing the secondary node. This is done in two ways, depending on the disk template type. For <literal>remote_raid1</literal>: |
|
| 333 |
|
|
| 334 |
<synopsis>gnt-instance replace-disks <option>-n <replaceable>NEW_SECONDARY</replaceable></option> <replaceable>INSTANCE_NAME</replaceable></synopsis> |
|
| 316 | 335 |
|
| 317 |
<synopsis>gnt-instance replace-disks -n <replaceable>NEW_SECONDARY</replaceable> <replaceable>INSTANCE_NAME</replaceable></synopsis> |
|
| 336 |
and for <literal>drbd</literal>: |
|
| 337 |
<synopsis>gnt-instance replace-disks <option>-s</option> <option>-n <replaceable>NEW_SECONDARY</replaceable></option> <replaceable>INSTANCE_NAME</replaceable></synopsis> |
|
| 318 | 338 |
|
| 319 | 339 |
This process is a bit longer, but involves no instance |
| 320 | 340 |
downtime, and at the end of it the instance has changed its |
| ... | ... | |
| 394 | 414 |
</sect2> |
| 395 | 415 |
|
| 396 | 416 |
<sect2> |
| 397 |
<title>Instance Operating System Debugging</title>
|
|
| 417 |
<title>Instance OS definitions Debugging</title>
|
|
| 398 | 418 |
|
| 399 | 419 |
<para> |
| 400 | 420 |
Should you have any problems with operating systems support |
Also available in: Unified diff