<para>Keeping an updated full backup of the MDT is especially important because a permanent failure of the MDT file system renders the much larger amount of data in all the OSTs largely inaccessible and unusable.</para>
</note>
<warning condition='l23'>
- <para>In Lustre 2.0 through 2.2, the only successful way to backup and restore an MDT is to do a device-level backup as is described in this section. File-level restore of an MDT is not possible before Lustre 2.3, as the Object Index (OI) file cannot be rebuilt after restore without the OI Scrub functionality. <emphasis role='bold'>Since Lustre 2.3</emphasis>, Object Index files are automatically rebuilt at first mount after a restore is detected (see <link xl:href='http://jira.whamcloud.com/browse/LU-957'>LU-957</link>), and file-level backup is supported (see <xref linkend='dbdoclet.50438207_21638'/>).</para>
+ <para>In Lustre 2.0 through 2.2, the only successful way to backup and
+ restore an MDT is to do a device-level backup as is described in this
+ section. File-level restore of an MDT is not possible before Lustre 2.3,
+ as the Object Index (OI) file cannot be rebuilt after restore without
+ the OI Scrub functionality.
+ <emphasis role='bold'>Since Lustre 2.3</emphasis>, Object Index files
+ are automatically rebuilt at first mount after a restore is detected
+ (see <link xl:href='http://jira.hpdd.intel.com/browse/LU-957'>LU-957</link>),
+ and file-level backup is supported
+ (see <xref linkend='dbdoclet.50438207_21638'/>).</para>
</warning>
<para>If hardware replacement is the reason for the backup or if a spare storage device is available, it is possible to do a raw copy of the MDT or OST from one block device to the other, as long as the new device is at least as large as the original device. To do this, run:</para>
<screen>dd if=/dev/{original} of=/dev/{newdev} bs=1M</screen>
<title><indexterm><primary>backup</primary><secondary>OST file system</secondary></indexterm><indexterm><primary>backup</primary><secondary>MDT file system</secondary></indexterm>Making a File-Level Backup of an OST or MDT File System</title>
<para>This procedure provides an alternative to backup or migrate the data of an OST or MDT at the file level. At the file-level, unused space is omitted from the backed up and the process may be completed quicker with smaller total backup size. Backing up a single OST device is not necessarily the best way to perform backups of the Lustre file system, since the files stored in the backup are not usable without metadata stored on the MDT and additional file stripes that may be on other OSTs. However, it is the preferred method for migration of OST devices, especially when it is desirable to reformat the underlying file system with different configuration options or to reduce fragmentation.</para>
<note>
- <para>Prior to Lustre 2.3, the only successful way to perform an MDT backup and restore is to do a device-level backup as is described in <xref linkend='dbdoclet.50438207_71633'/>. The ability to do MDT file-level backups is not available for Lustre 2.0 thru 2.2, because restoration of the Object Index (OI) file does not return the MDT to a functioning state. <emphasis role='bold'>Since Lustre 2.3</emphasis>, Object Index files are automatically rebuilt at first mount after a restore is detected (see <link xl:href='http://jira.whamcloud.com/browse/LU-957'>LU-957</link>), so file-level MDT restore is supported.</para>
+ <para>Prior to Lustre 2.3, the only successful way to perform an MDT
+ backup and restore is to do a device-level backup as is described in
+ <xref linkend='dbdoclet.50438207_71633'/>. The ability to do MDT
+ file-level backups is not available for Lustre 2.0 thru 2.2, because
+ restoration of the Object Index (OI) file does not return the MDT to
+ a functioning state. <emphasis role='bold'>Since Lustre 2.3</emphasis>,
+ Object Index files are automatically rebuilt at first mount after a
+ restore is detected (see
+ <link xl:href='http://jira.hpdd.intel.com/browse/LU-957'>LU-957</link>),
+ so file-level MDT restore is supported.</para>
</note>
<para>For Lustre 2.3 and newer with MDT file-level backup support, substitute <literal>mdt</literal> for <literal>ost</literal> in the instructions below.</para>
<orderedlist>
</listitem>
</itemizedlist>
<para>Download the Lustre I/O kit (<literal>lustre-iokit</literal>)from:</para>
- <para><link xl:href="http://downloads.whamcloud.com/">http://downloads.whamcloud.com/</link></para>
+ <para><link xl:href="http://downloads.hpdd.intel.com/">http://downloads.hpdd.intel.com/</link></para>
</section>
</section>
<section xml:id="dbdoclet.50438212_51053">
<para>Lustre 2.4 and beyond requires a version of e2fsprogs that supports quota (i.e. newer
or equal to 1.42.3.wc1) to be installed on the server nodes using ldiskfs backend
(e2fsprogs isn't needed with ZFS backend). In general, we recommend to use the latest
- e2fsprogs version available on http://downloads.whamcloud.com/public/e2fsprogs.</para>
+ e2fsprogs version available on <link xl:href="http://downloads.hpdd.intel.com/e2fsprogs/">http://downloads.hpdd.intel.com/public/e2fsprogs/</link>.</para>
+
<para>The ldiskfs OSD relies on the standard Linux quota to maintain accounting information
on disk. As a consequence, the Linux kernel running on the Lustre servers using ldiskfs
backend must have <literal>CONFIG_QUOTA</literal>, <literal>CONFIG_QUOTACTL</literal> and
<literal>tcpdump</literal> and can read packet dumps generated by
it. There are plug-ins available to dissassemble the LNET and
Lustre protocols. They are located within the <link
- xl:href="http://git.whamcloud.com/">Lustre git repository</link>
+ xl:href="http://git.hpdd.intel.com/">Lustre git repository</link>
under <literal>lustre/contrib/wireshark/</literal>. Installation
instruction are included in that directory. See also <link
xl:href="http://www.wireshark.org/">Wireshark Website</link> for
.PHONY: push
push:
- git push ssh://review.whamcloud.com:29418/doc/manual HEAD:refs/for/master
+ git push ssh://review.hpdd.intel.com:29418/doc/manual HEAD:refs/for/master
.PHONY: clean
clean:
system.</para>
<section remap="h2">
<title>About this Document</title>
- <para>This document is maintained by Intel in Docbook format. The canonical version is available at <link xl:href="http://wiki.whamcloud.com/display/PUB/Documentation">http://wiki.whamcloud.com/display/PUB/Documentation</link>. </para>
+ <para>This document is maintained by Intel in Docbook format. The
+ canonical version is available at
+ <link xl:href="http://wiki.hpdd.intel.com/display/PUB/Documentation">http://wiki.hpdd.intel.com/display/PUB/Documentation</link>. </para>
<section remap="h2">
<title>UNIX Commands</title>
<section remap="h2">
<title>Related Documentation</title>
<para>The documents listed as online are available at:</para>
- <para><link xl:href="http://wiki.whamcloud.com/display/PUB/Documentation">http://wiki.whamcloud.com/display/PUB/Documentation</link></para>
+ <para><link xl:href="http://wiki.hpdd.intel.com/display/PUB/Documentation">http://wiki.hpdd.intel.com/display/PUB/Documentation</link></para>
<informaltable frame="all">
<tgroup cols="4">
<colspec colname="c1" colwidth="25*"/>
<para>These web sites provide additional resources:</para>
<itemizedlist>
<listitem>
- <para> Documentation <link xl:href="http://wiki.whamcloud.com/display/PUB/Documentation">http://wiki.whamcloud.com/display/PUB/Documentation</link></para>
+ <para> Documentation <link xl:href="http://wiki.hpdd.intel.com/display/PUB/Documentation">http://wiki.hpdd.intel.com/display/PUB/Documentation</link></para>
</listitem>
<listitem>
- <para> Support <link xl:href="http://www.whamcloud.com/">http://www.whamcloud.com/</link></para>
+ <para> Support <link xl:href="http://www.hpdd.intel.com/">http://www.hpdd.intel.com/</link></para>
</listitem>
<listitem>
- <para> Training <link xl:href="http://www.whamcloud.com/">http://www.whamcloud.com/</link></para>
+ <para> Training <link xl:href="http://www.hpdd.intel.com/">http://www.hpdd.intel.com/</link></para>
</listitem>
</itemizedlist>
</section>
<title><indexterm><primary>e2scan</primary></indexterm>
e2scan</title>
<para>The e2scan utility is an ext2 file system-modified inode scan program. The e2scan program uses libext2fs to find inodes with ctime or mtime newer than a given time and prints out their pathname. Use e2scan to efficiently generate lists of files that have been modified. The e2scan tool is included in the e2fsprogs package, located at:</para>
- <para><link xl:href="http://downloads.whamcloud.com/public/e2fsprogs/latest/">http://downloads.whamcloud.com/public/e2fsprogs/latest/</link></para>
+ <para><link xl:href="http://downloads.hpdd.intel.com/public/e2fsprogs/latest/">http://downloads.hpdd.intel.com/public/e2fsprogs/latest/</link></para>
<section remap="h5">
<title>Synopsis</title>
<screen>e2scan [options] [-f file] block_device</screen>
<secondary>features</secondary>
</indexterm>Lustre Features</title>
<para>Lustre file systems run on a variety of vendor's kernels. For more details, see the
- <link xl:href="http://wiki.whamcloud.com/display/PUB/Lustre+Support+Matrix">Lustre Support
+ <link xl:href="http://wiki.hpdd.intel.com/display/PUB/Lustre+Support+Matrix">Lustre Support
Matrix</link> on the Intel Lustre community wiki.</para>
<para>A Lustre installation can be scaled up or down with respect to the number of client
nodes, disk storage and bandwidth. Scalability and performance are dependent on available
git://git.whamcloud.com / doc / manual.git / commitdiff