<?xml version='1.0' encoding='utf-8'?>
<chapter xmlns="http://docbook.org/ns/docbook"
-xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US"
-xml:id="backupandrestore">
+ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en-US"
+ xml:id="backupandrestore">
<title xml:id="backupandrestore.title">Backing Up and Restoring a File
System</title>
<para>This chapter describes how to backup and restore at the file
<itemizedlist>
<listitem>
<para>
- <xref linkend="dbdoclet.backup_file"/>
+ <xref linkend="backup_file"/>
</para>
</listitem>
<listitem>
<para>
- <xref linkend="dbdoclet.backup_device"/>
+ <xref linkend="backup_device"/>
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
- <xref linkend="dbdoclet.backup_lvm_snapshot"/>
+ <xref linkend="backup_lvm_snapshot"/>
</para>
</listitem>
</itemizedlist>
<para>It is <emphasis>strongly</emphasis> recommended that sites perform
periodic device-level backup of the MDT(s)
- (<xref linkend="dbdoclet.backup_device"/>),
+ (<xref linkend="backup_device"/>),
for example twice a week with alternate backups going to a separate
device, even if there is not enough capacity to do a full backup of all
of the filesystem data. Even if there are separate file-level backups of
it is needed), and only needs good linear read/write performance. While
the device-level MDT backup is not useful for restoring individual files,
it is most efficient to handle the case of MDT failure or corruption.</para>
- <section xml:id="dbdoclet.backup_file">
+ <section xml:id="backup_file">
<title>
<indexterm>
<primary>backup</primary>
<literal>lustre_rsync</literal> is run, the user must specify a set of
parameters for the program to use. These parameters are described in
the following table and in
- <xref linkend="dbdoclet.50438219_63667" />. On subsequent runs, these
+ <xref linkend="lustre_rsync" />. On subsequent runs, these
parameters are stored in the the status file, and only the name of the
status file needs to be passed to
<literal>lustre_rsync</literal>.</para>
</section>
</section>
</section>
- <section xml:id="dbdoclet.backup_device">
+ <section xml:id="backup_device">
<title>
<indexterm>
<primary>backup</primary>
<primary>backup</primary>
<secondary>OST and MDT</secondary>
</indexterm>Backing Up an OST or MDT</title>
- <para>If backing up an MDT, substitute <literal>mdt</literal> for
- <literal>ost</literal> in the instructions below.</para>
+ <para>The below examples show backing up an OST filesystem. When backing
+ up an MDT, substitute <literal>mdt</literal> for <literal>ost</literal>
+ in the instructions below.</para>
<orderedlist>
<listitem>
<para><emphasis role="bold">Umount the target</emphasis></para>
will be immediately although there may be I/O errors reading
from files that are present on the MDT but not the OSTs, and files that
were created after the MDT backup will not be accessible or visible. See
- <xref linkend="dbdoclet.lfsckadmin" />for details on using LFSCK.</para>
+ <xref linkend="lfsckadmin" />for details on using LFSCK.</para>
</section>
- <section xml:id="dbdoclet.backup_lvm_snapshot">
+ <section xml:id="backup_lvm_snapshot">
<title>
<indexterm>
<primary>backup</primary>
</section>
</section>
</chapter>
+<!--
+ vim:expandtab:shiftwidth=2:tabstop=8:
+ -->