Revision 4677a909
| b/doc/admin.sgml | ||
|---|---|---|
| 183 | 183 |
<simpara><emphasis role="strong">Note:</emphasis> This is |
| 184 | 184 |
only valid for multi-node clusters.</simpara> |
| 185 | 185 |
<simpara> |
| 186 |
A mirror is set between the local node and a remote |
|
| 187 |
one, which must be specified with the --secondary-node |
|
| 188 |
option. Use this option to obtain a highly available |
|
| 189 |
instance that can be failed over to a remote node |
|
| 190 |
should the primary one fail. |
|
| 186 |
A mirror is set between the local node and a remote one, which |
|
| 187 |
must be specified with the second value of the --node option. Use |
|
| 188 |
this option to obtain a highly available instance that can be |
|
| 189 |
failed over to a remote node should the primary one fail. |
|
| 191 | 190 |
</simpara> |
| 192 | 191 |
</listitem> |
| 193 | 192 |
</varlistentry> |
| ... | ... | |
| 197 | 196 |
<para> |
| 198 | 197 |
For example if you want to create an highly available instance |
| 199 | 198 |
use the remote_raid1 disk template: |
| 200 |
<synopsis>gnt-instance add -n <replaceable>TARGET_NODE</replaceable> -o <replaceable>OS_TYPE</replaceable> -t remote_raid1 \
|
|
| 201 |
--secondary-node=<replaceable>SECONDARY_NODE</replaceable> <replaceable>INSTANCE_NAME</replaceable></synopsis>
|
|
| 199 |
<synopsis>gnt-instance add -n <replaceable>TARGET_NODE</replaceable><optional>:<replaceable>SECONDARY_NODE</replaceable></optional> -o <replaceable>OS_TYPE</replaceable> -t remote_raid1 \
|
|
| 200 |
<replaceable>INSTANCE_NAME</replaceable></synopsis> |
|
| 202 | 201 |
|
| 203 | 202 |
<para> |
| 204 | 203 |
To know which operating systems your cluster supports you can use: |
| b/doc/install.sgml | ||
|---|---|---|
| 810 | 810 |
To create a network mirrored instance, change the argument to |
| 811 | 811 |
the <option>-t</option> option from <literal>plain</literal> |
| 812 | 812 |
to <literal>remote_raid1</literal> and specify the node on |
| 813 |
which the mirror should reside with the |
|
| 814 |
<option>--secondary-node</option> option, like this:
|
|
| 813 |
which the mirror should reside with the second value of the
|
|
| 814 |
<option>--node</option> option, like this: |
|
| 815 | 815 |
</para> |
| 816 | 816 |
|
| 817 | 817 |
<screen> |
| 818 |
# gnt-instance add -t remote_raid1 --secondary-node node1 \ |
|
| 819 |
-n node2 -o debian-etch instance2 |
|
| 818 |
# gnt-instance add -t remote_raid1 -n node1:node2 -o debian-etch instance2 |
|
| 820 | 819 |
* creating instance disks... |
| 821 | 820 |
adding instance instance2 to cluster config |
| 822 | 821 |
Waiting for instance instance1 to sync disks. |
| ... | ... | |
| 827 | 826 |
- device sdb: 76.30% done, 72 estimated seconds remaining |
| 828 | 827 |
- device sdb: 94.80% done, 18 estimated seconds remaining |
| 829 | 828 |
Instance instance2's disks are in sync. |
| 830 |
creating os for instance instance2 on node node2.example.com
|
|
| 829 |
creating os for instance instance2 on node node1.example.com
|
|
| 831 | 830 |
* running the instance OS create scripts... |
| 832 | 831 |
* starting instance... |
| 833 | 832 |
</screen> |
| b/man/gnt-backup.sgml | ||
|---|---|---|
| 91 | 91 |
<title>IMPORT</title> |
| 92 | 92 |
<cmdsynopsis> |
| 93 | 93 |
<command>import</command> |
| 94 |
<arg choice="req">-n <replaceable>node</replaceable></arg> |
|
| 94 |
<arg choice="req">-n <replaceable>node<optional>:secondary-node</optional></replaceable></arg>
|
|
| 95 | 95 |
<arg>-s <replaceable>disksize</replaceable></arg> |
| 96 | 96 |
<arg>-o <replaceable>os-type</replaceable></arg> |
| 97 | 97 |
<arg>-m <replaceable>memsize</replaceable></arg> |
| ... | ... | |
| 171 | 171 |
<term>remote_raid1</term> |
| 172 | 172 |
<listitem> |
| 173 | 173 |
<para> |
| 174 |
Disk devices will be md raid1 arrays with one |
|
| 175 |
component (so it's not actually raid1): a drbd device
|
|
| 176 |
between the instance's primary node and the node given
|
|
| 177 |
by the option <option>--secondary-node</option>.
|
|
| 174 |
Disk devices will be md raid1 arrays with one component (so
|
|
| 175 |
it's not actually raid1): a drbd device between the instance's
|
|
| 176 |
primary node and the node given by the second value of the
|
|
| 177 |
<option>--node</option> option.
|
|
| 178 | 178 |
</para> |
| 179 | 179 |
</listitem> |
| 180 | 180 |
</varlistentry> |
| ... | ... | |
| 182 | 182 |
</para> |
| 183 | 183 |
|
| 184 | 184 |
<para> |
| 185 |
The <option>--secondary-node</option> option is used with |
|
| 186 |
the remote raid disk template type and specifies the remote |
|
| 187 |
node. |
|
| 188 |
</para> |
|
| 189 |
|
|
| 190 |
<para> |
|
| 191 | 185 |
If you do not want gnt-backup to wait for the disk mirror |
| 192 | 186 |
to be synced, use the <option>--no-wait-for-sync</option> |
| 193 | 187 |
option. |
| 194 | 188 |
</para> |
| 195 | 189 |
|
| 196 |
|
|
| 197 | 190 |
<para> |
| 198 | 191 |
Example: |
| 199 | 192 |
<screen> |
| b/man/gnt-instance.sgml | ||
|---|---|---|
| 77 | 77 |
</group> |
| 78 | 78 |
</arg> |
| 79 | 79 |
<sbr> |
| 80 |
<arg choice="req">-n <replaceable>node</replaceable></arg> |
|
| 80 |
<arg choice="req">-n <replaceable>node<optional>:secondary-node</optional></replaceable></arg>
|
|
| 81 | 81 |
<arg choice="req"><replaceable>instance</replaceable></arg> |
| 82 | 82 |
</cmdsynopsis> |
| 83 | 83 |
<para> |
| ... | ... | |
| 155 | 155 |
<term>remote_raid1</term> |
| 156 | 156 |
<listitem> |
| 157 | 157 |
<para> |
| 158 |
Disk devices will be md raid1 arrays with one |
|
| 159 |
component (so it's not actually raid1): a drbd device
|
|
| 160 |
between the instance's primary node and the node given
|
|
| 161 |
by the option <option>--secondary-node</option>.
|
|
| 158 |
Disk devices will be md raid1 arrays with one component (so
|
|
| 159 |
it's not actually raid1): a drbd device between the
|
|
| 160 |
instance's primary node and the node given by the second
|
|
| 161 |
value of the <option>--node</option> option.
|
|
| 162 | 162 |
</para> |
| 163 | 163 |
</listitem> |
| 164 | 164 |
</varlistentry> |
| ... | ... | |
| 166 | 166 |
</para> |
| 167 | 167 |
|
| 168 | 168 |
<para> |
| 169 |
The <option>--secondary-node</option> option is used with |
|
| 170 |
the remote raid disk template type and specifies the remote |
|
| 171 |
node. |
|
| 169 |
The optional second value of the <option>--node</option> is used for |
|
| 170 |
the remote raid template type and specifies the remote node. |
|
| 172 | 171 |
</para> |
| 173 | 172 |
|
| 174 | 173 |
<para> |
| ... | ... | |
| 177 | 176 |
option. |
| 178 | 177 |
</para> |
| 179 | 178 |
|
| 180 |
|
|
| 181 | 179 |
<para> |
| 182 | 180 |
Example: |
| 183 | 181 |
<screen> |
| 184 | 182 |
# gnt-instance add -t plain -s 30g -m 512 -o debian-etch \ |
| 185 | 183 |
-n node1.example.com instance1.example.com |
| 186 |
# gnt-instance add -t remote_raid1 --secondary-node node3.example.com \ |
|
| 187 |
-s 30g -m 512 -o debian-etch \ |
|
| 188 |
-n node1.example.com instance2.example.com |
|
| 184 |
# gnt-instance add -t remote_raid1 -s 30g -m 512 -o debian-etch \ |
|
| 185 |
-n node1.example.com:node2.example.com instance2.example.com |
|
| 189 | 186 |
</screen> |
| 190 | 187 |
</para> |
| 191 |
|
|
| 192 | 188 |
</refsect3> |
| 193 | 189 |
|
| 194 | 190 |
<refsect3> |
| ... | ... | |
| 275 | 271 |
<varlistentry> |
| 276 | 272 |
<term>snodes</term> |
| 277 | 273 |
<listitem> |
| 278 |
<simpara>comma-separated list of secondary-nodes for the
|
|
| 274 |
<simpara>comma-separated list of secondary nodes for the
|
|
| 279 | 275 |
instance; usually this will be just one node</simpara> |
| 280 | 276 |
</listitem> |
| 281 | 277 |
</varlistentry> |
Also available in: Unified diff