<refmeta>
<refentrytitle>amfetchdump</refentrytitle>
<manvolnum>8</manvolnum>
+&rmi.source;
+&rmi.version;
+&rmi.manual.8;
</refmeta>
<refnamediv>
<refname>amfetchdump</refname>
<refpurpose>extract backup images from multiple &A; tapes.</refpurpose>
</refnamediv>
+<refentryinfo>
+&author.jstange;
+&author.ian;
+</refentryinfo>
<!-- body begins here -->
<refsynopsisdiv>
<cmdsynopsis>
<command>amfetchdump</command>
<arg choice='opt'>-pcClawns</arg>
<arg choice='opt'>-d <replaceable>device</replaceable></arg>
- <arg choice='opt'>-o <replaceable>directory</replaceable></arg>
- <arg choice='opt'>-i <replaceable>logfile</replaceable></arg>
+ <arg choice='opt'>-O <replaceable>directory</replaceable></arg>
<arg choice='opt'>-b <replaceable>blocksize</replaceable></arg>
<arg choice='plain'><replaceable>config</replaceable></arg>
<arg choice='plain'><replaceable>hostname</replaceable></arg>
</arg>
</arg>
</arg>
+ <arg choice='plain' rep='repeat'><group><arg choice='plain'>-o </arg><replaceable>configoption</replaceable></group></arg>
</cmdsynopsis>
</refsynopsisdiv>
<listitem><para> Restore from this tape device instead of the default.</para></listitem>
</varlistentry>
<varlistentry>
- <term><option>-o</option>
+ <term><option>-O</option>
<replaceable>directory</replaceable></term>
<listitem><para>Output restored files to this directory, instead of to the
current working directory.</para></listitem>
<listitem><para>Assume that all tapes are already available, via tape changer or
otherwise, instead of prompting the operator to ensure that all tapes
are loaded.</para></listitem>
- </varlistentry>
- <varlistentry>
- <term><option>-i</option> <replaceable>filename</replaceable></term>
-<listitem><para>Generate an inventory of all dumps "seen" on the
-tapes we search, for later use as a log.</para></listitem>
</varlistentry>
<varlistentry>
<term><option>-w</option></term>
piece as an individual file and reassembles them only after all have
been restored.</para>
-<note>This requires at least double the size of your dump in free
-disk space, in order to build the final assembled dumpfile.</note>
+<note><para>This requires at least double the size of your dump in free
+disk space, in order to build the final assembled dumpfile.</para>
+</note>
<para>This behavior is implicitly invoked in circumstances where knowing the
location of all dumps on tape in advance is not possible, such as when
value will usually be autodetected, and should not normally need
to be set.</para></listitem>
</varlistentry>
+
+ <varlistentry>
+ <term><emphasis remap='B'>-o</emphasis> <replaceable>configoption</replaceable></term>
+ <listitem>
+<para>See the "<emphasis remap='B'>CONFIGURATION OVERRIDE</emphasis>"
+ section in <citerefentry><refentrytitle>amanda</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
+ </listitem>
+ </varlistentry>
+
</variablelist>
</refsect1>
<para>Here's a simple case, restoring all known dumps of the host
vanya to the current working directory.</para>
-<!-- .RS -->
-<literallayout remap='.nf'>
+<programlisting>
$ amfetchdump SetA vanya
-</literallayout> <!-- .fi -->
+</programlisting>
<para>A more likely scenario involves restoring a particular dump from
a particular date. We'll pipe this one to &gnutar; as well, to
automatically extract the dump.</para>
-<!-- .RS -->
-<literallayout remap='.nf'>
+<programlisting>
$ amfetchdump -p SetA vanya /home 20051020 | gtar -xvpf -
-</literallayout> <!-- .fi -->
+</programlisting>
-<para>In a situation where all of our dump logs have been wiped out,
-we could also use amfetchdump to inventory our tapes and recreate an
-imitation of those logs, which we'll send to <emphasis
-remap="I">stdout</emphasis> for casual perusal.
-<!-- .RS -->
-<literallayout remap='.nf'>
-$ amfetchdump -i - SetA
-</literallayout> <!-- .fi -->
-</para>
-
-<para>Note that you can specify a restore while in inventory mode, and
-<command>amfetchdump</command> will continue searching for more dumps
-from this host even after successfully restoring a dump, inventorying
-all the while. If your backup searcher has been trashed, this is a
-handy way to recover what you have.
-<!-- .RS -->
-<literallayout remap='.nf'>
-$ amfetchdump -i /var/amanda/log SetA backupserver
-</literallayout> <!-- .fi -->
-</para>
</refsect1>
<refsect1><title>CAVEATS</title>
-<command>Amfetchdump</command> is dependent on accessing your server's config,
+<para><command>Amfetchdump</command> is dependent on accessing your server's config,
tape changer, and (normally) dump logs. As such, it's not necessarily
the most useful tool when those have all been wiped out and you
desperately need to pull things from your tape. Pains have been taken
<citerefentry><refentrytitle>amrestore</refentrytitle><manvolnum>8</manvolnum></citerefentry>
or
<citerefentry><refentrytitle>dd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-instead.
-</refsect1>
-
-<refsect1><title>AUTHOR</title>
-<para>John Stange, &email.jstange;, National Academies Press</para>
-<para>Ian Turner, &email.itt;: XML-conversion</para>
+instead.</para>
</refsect1>
<refsect1><title>SEE ALSO</title>
<para><citerefentry><refentrytitle>amanda</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>amadmin</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>amrestore</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
-<citerefentry><refentrytitle>tar</refentrytitle><manvolnum>1</manvolnum></citerefentry>
-<citerefentry><refentrytitle>restore</refentrytitle><manvolnum>8</manvolnum></citerefentry></para>
+<citerefentry><refentrytitle>tar</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
+<citerefentry><refentrytitle>restore</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
+<ulink url="http://wiki.zmanda.com"/>
+</para>
</refsect1>
</refentry>
projects / debian / amanda / blobdiff