Synnefo » snf-ganeti » ganeti-local

      Its primary function is to try to keep running all instances

      which are marked as <emphasis>up</emphasis> in the configuration

      file, by trying to start them a limited number of times.

    </para>

    <para>

      Its other function is to <quote>repair</quote> DRBD links by

      reactivating the block devices of instances which have

      secondaries on nodes that have been rebooted.

      version (1.2) supports Xen 3.0 (also tested with 3.1).

        Exports an instance to the target node. All the instance data

        and its configuration will be exported under the

        /srv/ganeti/exports/<replaceable>instance</replaceable>

        directory on the target node.

            <arg>drbd</arg>

        <sbr>

        the instance, in gibibytes (defaults to 20 GiB).

        the instance, in mebibytes (defaults to 128 MiB).

                Disk devices will be md raid1 arrays with one

                component (so it's not actually raid1): a drbd (0.7.x)

                device between the instance's primary node and the

                node given by the second value of the

          <varlistentry>

            <term>drbd</term>

            <listitem>

              <para>

                Disk devices will be drbd (version 8.x) on top of lvm

                volumes. They are equivalent in functionality to

                <replaceable>remote_raid1</replaceable>, but are

                recommended for new instances (if you have drbd 8.x

                installed).

              </para>

            </listitem>

          </varlistentry>

        Lists the exports currently available in the default directory

        in all the nodes of the current cluster, or optionally only a

        subset of them specified by the <option>--nodes</option>

        option (use this option multiple times to select multiple

        nodes).

      <para>

      Example:

<screen>

# gnt-backup list --nodes node1 --nodes node2

</screen>

        <arg choice="req">--yes-do-it</arg>

      <para>

        Since this is a dangerous command, you are required to pass

        the argument <replaceable>--yes-do-it.</replaceable>

      </para>

              <arg>drbd</arg>

                  Disk devices will be md raid1 arrays with one

                  component (so it's not actually raid1): a drbd

                  (0.7.x) device between the instance's primary node

                  and the node given by the second value of the

                  <option>--node</option> option.

                </para>

              </listitem>

            </varlistentry>

            <varlistentry>

              <term>drbd</term>

              <listitem>

                <para>

                  Disk devices will be drbd (version 8.x) on top of

                  lvm volumes. They are equivalent in functionality to

                  <replaceable>remote_raid1</replaceable>, but are

                  recommended for new instances (if you have drbd 8.x

                  installed).

        <arg>--no-headers</arg>

        <arg>--human-readable</arg>

        <arg>--separator=<replaceable>SEPARATOR</replaceable></arg>

        <arg>--output=<replaceable>FIELDS</replaceable></arg>

        <sbr>

        The <option>--no-headers</option> option will skip the initial

        header line. The <option>--separator</option> option takes an

        argument which denotes what will be used between the output

        fields. Both these options are to help scripting.

      </para>

      <para>

        The <option>-o</option> option takes a comma-separated list of

        output fields. The available fields and their meaning are:

        <variablelist>

          <varlistentry>

            <term>node</term>

            <listitem>

              <simpara>the node name on which the volume exists</simpara>

            </listitem>

          </varlistentry>

          <varlistentry>

            <term>phys</term>

            <listitem>

              <simpara>the physical drive (on which the LVM physical

              volume lives)</simpara>

            </listitem>

          </varlistentry>

          <varlistentry>

            <term>vg</term>

            <listitem>

              <simpara>the volume group name</simpara>

            </listitem>

          </varlistentry>

          <varlistentry>

            <term>name</term>

            <listitem>

              <simpara>the logical volume name</simpara>

            </listitem>

          </varlistentry>

          <varlistentry>

            <term>size</term>

            <listitem>

              <simpara>the logical volume size</simpara>

            </listitem>

          </varlistentry>

          <varlistentry>

            <term>instance</term>

            <listitem>

              <simpara>The name of the instance to which this volume

              belongs, or (in case it's an orphan volume) the

              character <quote>-</quote></simpara>

            </listitem>

          </varlistentry>

        </variablelist>

      </para>

      <para>