[BACK]Return to xfsdump.html CVS log [TXT][DIR] Up to [Development] / xfs-website.orig / manpages
File: [Development] / xfs-website.orig / manpages / xfsdump.html (download) (as text)

Revision 1.2, Tue Apr 25 00:26:32 2000 UTC (17 years, 6 months ago) by cattelan
Branch: MAIN
Changes since 1.1: +1 -1 lines 

Make the body white

<html>
<head>
<meta name="Content-Style" content="text/css">
</head>
<body bgcolor="white">
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#NOTES">NOTES</a><br>
<a href="#FILES">FILES</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<a href="#DIAGNOSTICS">DIAGNOSTICS</a><br>
<a href="#BUGS">BUGS</a><br>
<!-- Creator     : groff version 1.15  -->
<!-- CreationDate: Mon Apr 24 10:40:32 2000
 -->
<!-- Total number of pages: 4 -->
<!-- Page: 1 -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<a name="NAME"></a><h2>NAME</h2><p><font size=3>xfsdump - XFS filesystem incremental dump utility</p>
<a name="SYNOPSIS"></a><h2>SYNOPSIS</h2><p><font size=3><B>xfsdump</B> <font size=3>[ <font size=3><B>-a</B> <font size=3>] [ <font size=3><B>-b</B> <font size=3>blocksize (use with minimal rmt flag) ]</p>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="3.6923%">
</td>
<td valign="top" align="left"  width="49.2308%">
<p><font size=3>[ <font size=3><B>-c</B> <font size=3>media_change_alert_program ] [ <font size=3><B>-f</B> <font size=3>destination ... ]<br>
[ <font size=3><B>-l</B> <font size=3>level ] [ <font size=3><B>-m</B> <font size=3>force usage of minimal rmt ]<br>
[ <font size=3><B>-o</B> <font size=3>overwrite tape ] [ <font size=3><B>-p</B> <font size=3>report_interval ]<br>
[ <font size=3><B>-s</B> <font size=3>pathname ... ] [ <font size=3><B>-v</B> <font size=3>verbosity ] [ <font size=3><B>-A</B> <font size=3>]<br>
[ <font size=3><B>-B</B> <font size=3>base_id ] [ <font size=3><B>-E</B> <font size=3>] [ <font size=3><B>-F</B> <font size=3>] [ <font size=3><B>-I</B> <font size=3>[ subopt=value ... ] ]<br>
[ <font size=3><B>-J</B> <font size=3>] [ <font size=3><B>-L</B> <font size=3>session_label ] [ <font size=3><B>-M</B> <font size=3>media_label ... ]<br>
[ <font size=3><B>-O</B> <font size=3>options_file ] [ <font size=3><B>-R</B> <font size=3>] [ <font size=3><B>-T</B> <font size=3>] [ <font size=3><B>-Y</B> <font size=3>io_ring_length ]<br>
[ <font size=3><B>-</B> <font size=3>] filesystem</p>
</td>
<td valign="top" align="left"  width="47.0769%">
</td>
</tr>
</table>
<br>
<a name="DESCRIPTION"></a><h2>DESCRIPTION</h2><p><font size=3><I>xfsdump</I> <font size=3>backs up files and their attributes in a filesystem. The files are dumped to storage media, a regular file, or standard output. Options allow the operator to have all files dumped, just files that have changed since a previous dump, or just files contained in a list of pathnames.</p>
<p><font size=3>The <font size=3><I>xfsrestore</I><font size=3>(1M) utility re-populates a filesystem with the contents of the dump.</p>
<p><font size=3>Each invocation of <font size=3><I>xfsdump</I> <font size=3>dumps just one filesystem. That invocation is termed a dump session. The dump ses- sion splits the filesystem into one or more dump streams, one per destination. The split is done in filesystem inode number (ino) order, at boundaries selected to equalize the size of each stream. Furthermore, the breakpoints between streams may be in the middle of very large files (at extent boundaries) if necessary to achieve reasonable stream size equalization. Each dump stream can span several media objects, and a single media object can con- tain several dump streams. The typical media object is a tape cartridge. The media object records the dump stream as one or more media files. A media file is a self-contained partial dump. The portion of a dump stream contained on a media object can be split into several media files. This minimizes the impact of media dropouts on the entire dump stream, and speeds subtree restores.</p>
<p><font size=3><I>xfsdump</I> <font size=3>maintains an online dump inventory in <font size=3><I>/var/xfsdump/inventory</I><font size=3>. The <font size=3><B>-I</B> <font size=3>option displays the inventory con- tents hierarchically. The levels of the hierarchy are: filesystem, dump session, stream, and media file.</p>
<p><font size=3><B>-a</B> <font size=3>Specifies that files for which the Data Migration Facility (DMF) has complete offline copies be dumped as<br>
<span style=" text-indent: 0.3000in;"></span>DMF state offline (OFL). This means that the file data will not be dumped by xfsdump, resulting in a smaller<br>
<span style=" text-indent: 0.3000in;"></span>dump file. If the file is later restored the file data is still accessible through DMF.</p>
<p><font size=3><B>-b</B> <font size=3><I>blocksize<br>
<span style=" text-indent: 0.3000in;"></span></I>Specifies the blocksize to be used for the dump. This option is specified only with the minimal rmt option (see<br>
<span style=" text-indent: 0.3000in;"></span>the <font size=3><B>-m</B> <font size=3>option below). For a QIC drive , blocksize must always be 512. For other drives such as DAT or 8<br>
<span style=" text-indent: 0.3000in;"></span>mm , a blocksize of 245760 bytes works well. The same blocksize must be specified to restore the tape.<br>
<span style=" text-indent: 0.3000in;"></span>When specified , this blocksize applies to all remote tape destinations.</p>
<p><font size=3><B>-c</B> <font size=3><I>media_change_alert_program<br>
<span style=" text-indent: 0.3000in;"></span></I>Use the specified program to alert the operator when a media change is required. The alert program is typi-<br>
<span style=" text-indent: 0.3000in;"></span>cally a script to send a mail or flash a window to draw the operator's attention.</p>
<p><font size=3><B>-f</B> <font size=3><I>destination<br>
<span style=" text-indent: 0.3000in;"></span></I>Specifies a dump destination. A dump destination can be the pathname of a device (such as a tape drive), a<br>
<span style=" text-indent: 0.3000in;"></span>regular file, or a remote tape drive (see <font size=3><I>rmt</I><font size=3>(1M)). Up to 20 dump destinations can be specified, in which<br>
<span style=" text-indent: 0.3000in;"></span>case each destination receives an equal portion of the filesystem. This option must be omitted if the standard<br>
<span style=" text-indent: 0.3000in;"></span>output option (a lone <font size=3><B>-</B> <font size=3>preceding the source filesystem specification) is specified.</p>
<p><font size=3><B>-l</B> <font size=3><I>level</p>
</I>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="4.6154%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Specifies a dump level of 0 to 9. The dump level determines the base dump to which this dump is relative. The base dump is the most recent dump at a lesser level. A level 0 dump is absolute - all files are dumped. A dump level where 1 &lt;= <font size=3><I>level</I> <font size=3>&lt;= 9 is referred to as an incremental dump. Only files that have been changed since the base dump are dumped. Subtree dumps (see the <font size=3><B>-s</B> <font size=3>option below) cannot be used as the base for incremental dumps.</p>
</td>
</tr>
</table>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="3.2308%">
<p><font size=3><B>-m</p>
</B></td>
<td valign="top" align="left"  width="1.3846%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Use the minimal rmt protocol for remote tape destinations. This is used when the remote machine is a non- SGI machine. With this option, <font size=3><I>xfsdump</I> <font size=3>uses version 1 rmt protocol for all remote tape drives. This option cannot be used without specifying a blocksize to be used (see <font size=3><B>-b</B> <font size=3>option above). If all rmt destinations are SGI machines, it is preferable <font size=3><B>not</B> <font size=3>to specify this option.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="3.2308%">
<p><font size=3><B>-o</p>
</B></td>
<td valign="top" align="left"  width="1.3846%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Overwrite the tape. With this option, <font size=3><I>xfsdump</I> <font size=3>does not read the tape first to check the contents. This option<br>
may be used if <font size=3><I>xfsdump</I> <font size=3>is unable to determine the block size of a tape .</p>
</td>
</tr>
</table>
<br>
<!-- Page: 2  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<p><font size=3><B>-p</B> <font size=3><I>interval<br>
<span style=" text-indent: 0.3000in;"></span></I>Causes progress reports to be printed at the specified interval. <font size=3><I>interval is given in seconds.</I> <font size=3>The progress<br>
<span style=" text-indent: 0.3000in;"></span>report indicates how many files have been dumped, the total number of files to dump, the percentage of data<br>
<span style=" text-indent: 0.3000in;"></span>dumped, and the elapsed time.</p>
<p><font size=3><B>-s</B> <font size=3><I>pathname</I> <font size=3>...<br>
<span style=" text-indent: 0.3000in;"></span>Restricts the dump to files contained in the specified pathnames (subtrees). Up to 100 pathnames can be<br>
<span style=" text-indent: 0.3000in;"></span>specified. A <font size=3><I>pathname</I> <font size=3>must be relative to the mount point of the filesystem. For example, if a filesystem is<br>
<span style=" text-indent: 0.3000in;"></span>mounted at <font size=3><I>/d2</I><font size=3>, the <font size=3><I>pathname</I> <font size=3>argument for the directory <font size=3><I>/d2/users</I> <font size=3>is ``users''. A <font size=3><I>pathname</I> <font size=3>can be a file or a<br>
<span style=" text-indent: 0.3000in;"></span>directory; if it is a directory, the entire hierarchy of files and subdirectories rooted at that directory is dumped.<br>
<span style=" text-indent: 0.3000in;"></span>Subtree dumps cannot be used as the base for incremental dumps (see the <font size=3><B>-l</B> <font size=3>option above).</p>
<p><font size=3><B>-v</B> <font size=3><I>verbosity_level<br>
<span style=" text-indent: 0.3000in;"></span></I>Specifies the level of detail of the messages displayed during the course of the dump. The argument can be<br>
<span style=" text-indent: 0.3000in;"></span><B>silent</B><font size=3>, <font size=3><B>verbose</B><font size=3>, or <font size=3><B>trace</B><font size=3>. The default is <font size=3><B>verbose</B><font size=3>.</p>
<p><font size=3><B>-A</B> <font size=3>Do not dump extended file attributes. Unless this option is specified, extended file attributes are dumped.<br>
<span style=" text-indent: 0.3000in;"></span>Note that dumps containing extended file attributes cannot be restored with older versions of <font size=3><I>xfsre-<br>
<span style=" text-indent: 0.3000in;"></span>store</I><font size=3>(1M).</p>
<p><font size=3><B>-B</B> <font size=3><I>base_id</p>
</I>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="4.6154%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Specifies the ID of the dump session upon which this dump session is to be based. If this option is specified, the <font size=3><B>-l</B> <font size=3>(level) and <font size=3><B>-R</B> <font size=3>(resume) options are not allowed. Instead, <font size=3><B>xfsdump</B> <font size=3>determines if the current dump session should be incremental and/or resumed, by looking at the base session's level and interrupted attributes. If the base session was interrupted, the current dump session is a resumption of that base at the same level. Otherwise, the current dump session is an incremental dump with a level one greater than that of the base session. This option allows incremental and resumed dumps to be based on any previous dump, rather than just the most recent.</p>
</td>
</tr>
</table>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
<p><font size=3><B>-E</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Pre-erase media. If this option is specified, media is erased prior to use. The operator is prompted for confir- mation, unless the <font size=3><B>-F</B> <font size=3>option is also specified.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
<p><font size=3><B>-F</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Don't prompt the operator. When <font size=3><I>xfsdump</I> <font size=3>encounters a media object containing non-xfsdump data, <font size=3><I>xfs- dump</I> <font size=3>normally asks the operator for permission to overwrite. With this option the overwrite is performed, no questions asked. When <font size=3><I>xfsdump</I> <font size=3>encounters end-of-media during a dump, <font size=3><I>xfsdump</I> <font size=3>normally asks the opera- tor if another media object will be provided. With this option the dump is instead interrupted.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
<p><font size=3><B>-I</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Displays the <font size=3><I>xfsdump</I> <font size=3>inventory (no dump is performed). <font size=3><I>xfsdump</I> <font size=3>records each dump session in an online inventory in <font size=3><I>/var/xfsdump/inventory</I><font size=3>. <font size=3><I>xfsdump</I> <font size=3>uses this inventory to determine the base for incremental dumps. It is also useful for manually identifying a dump session to be restored. Suboptions to filter the inven- tory display are described later.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
<p><font size=3><B>-J</p>
</B></td>
<td valign="top" align="left"  width="1.8462%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Inhibits the normal update of the inventory. This is useful when the media being dumped to will be discarded<br>
or overwritten.</p>
</td>
</tr>
</table>
<p><font size=3><B>-L</B> <font size=3><I>session_label<br>
<span style=" text-indent: 0.3000in;"></span></I>Specifies a label for the dump session. It can be any arbitrary string up to 255 characters long.</p>
<p><font size=3><B>-M</B> <font size=3><I>media_label<br>
<span style=" text-indent: 0.3000in;"></span></I>Specifies a label for the first media object (for example, tape cartridge) written on the corresponding destina-<br>
<span style=" text-indent: 0.3000in;"></span>tion during the session. It can be any arbitrary string up to 255 characters long. Multiple media object labels<br>
<span style=" text-indent: 0.3000in;"></span>can be specified, one for each destination.</p>
<p><font size=3><B>-O</B> <font size=3><I>options_file</p>
</I>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="4.6154%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Insert the options contained in <font size=3><I>options_file</I> <font size=3>into the beginning of the command line. The options are specified just as they would appear if typed into the command line. In addition, newline characters (\n) can be used as whitespace. The options are placed before all options actually given on the command line, just after the com- mand name. Only one <font size=3><B>-O</B> <font size=3>option can be used. Recursive use is ignored. The source filesystem cannot be specified in <font size=3><I>options_file</I><font size=3>.</p>
</td>
</tr>
</table>

<table width="100%"  rules="none"  frame="none"  cols="3">
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.9231%">
<p><font size=3><B>-R</p>
</B></td>
<td valign="top" align="left"  width="1.6923%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Resumes a previously interrupted dump session. If the most recent dump at this dump's level (<font size=3><B>-l</B> <font size=3>option) was interrupted, this dump contains only files not in the interrupted dump and consistent with the incremental level. However, files contained in the interrupted dump that have been subsequently modified are re- dumped.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.9231%">
<p><font size=3><B>-T</p>
</B></td>
<td valign="top" align="left"  width="1.6923%">
</td>
<td valign="top" align="left"  width="95.3846%">
<p><font size=3>Inhibits interactive dialogue timeouts. When the <font size=3><B>-F</B> <font size=3>option is not specified, <font size=3><I>xfsdump</I> <font size=3>prompts the operator for labels and media changes. Each dialogue normally times out if no response is supplied. This option prevents the timeout.</p>
</td>
</tr>
</table>
<br>
<!-- Page: 3  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<p><font size=3><B>-Y</B> <font size=3><I>io_ring_length<br>
<span style=" text-indent: 0.3000in;"></span></I>Specify I/O buffer ring length. <font size=3><I>xfsdump</I> <font size=3>uses a ring of output buffers to achieve maximum throughput when<br>
<span style=" text-indent: 0.3000in;"></span>dumping to tape drives. The default ring length is 3.</p>
<p><font size=3><B>-</B> <font size=3>A lone <font size=3><B>-</B> <font size=3>causes the dump stream to be sent to the standard output, where it can be piped to another utility<br>
<span style=" text-indent: 0.3000in;"></span>such as <font size=3><I>xfsrestore</I><font size=3>(1M) or redirected to a file. This option cannot be used with the <font size=3><B>-f</B> <font size=3>option. The <font size=3><B>-</B> <font size=3>must fol-<br>
<span style=" text-indent: 0.3000in;"></span>low all other options and precede the filesystem specification.</p>
<p><font size=3>The filesystem, <font size=3><I>filesystem</I><font size=3>, can be specified either as a mount point or as a special device file (for example, <font size=3><I>/dev/dsk/dks0d1s0</I><font size=3>). The filesystem must be mounted to be dumped.</p>
<a name="NOTES"></a><h2>NOTES</h2><p><span style=" text-indent: 0.1800in;"></span><font size=3><B>Dump Interruption<br>
<span style=" text-indent: 1.3000in;"></span></B>A dump can be interrupted at any time and later resumed. To interrupt, type control-C (or<br>
<span style=" text-indent: 1.3000in;"></span>the current terminal interrupt character). The operator is prompted to select one of several<br>
<span style=" text-indent: 1.3000in;"></span>operations, including dump interruption. After the operator selects dump interruption, the<br>
<span style=" text-indent: 1.3000in;"></span>dump continues until a convenient break point is encountered (typically the end of the cur-<br>
<span style=" text-indent: 1.3000in;"></span>rent file). Very large files are broken into smaller subfiles, so the wait for the end of the cur-<br>
<span style=" text-indent: 1.3000in;"></span>rent file is brief.</p>
<p><span style=" text-indent: 0.1800in;"></span><font size=3><B>Dump Resumption<br>
<span style=" text-indent: 1.3000in;"></span></B>A previously interrupted dump can be resumed by specifying the <font size=3><B>-R</B> <font size=3>option. If the most<br>
<span style=" text-indent: 1.3000in;"></span>recent dump at the specified level was interrupted, the new dump does not include files<br>
<span style=" text-indent: 1.3000in;"></span>already dumped, unless they have changed since the interrupted dump.</p>
<p><span style=" text-indent: 0.1800in;"></span><font size=3><B>Media Management</p>
</B>
<table width="100%"  rules="none"  frame="none"  cols="4">
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="9.0769%">
</td>
<td valign="top" align="left"  width="8.1538%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>A single media object can contain many dump streams. Conversely, a single dump stream can span multiple media objects. If a dump stream is sent to a media object already con- taining one or more dumps, <font size=3><I>xfsdump</I> <font size=3>appends the new dump stream after the last dump stream. Media files are never overwritten. If end-of-media is encountered during the course of a dump, the operator is prompted to insert a new media object into the drive. The dump stream continuation is appended after the last media file on the new media object.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="9.0769%">
<p><font size=3><B>Inventory</p>
</B></td>
<td valign="top" align="left"  width="8.1538%">
</td>
<td valign="top" align="left"  width="80.0000%">
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="9.0769%">
</td>
<td valign="top" align="left"  width="8.1538%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>Each dump session updates an inventory database in <font size=3><I>/var/xfsdump/inventory</I><font size=3>. <font size=3><I>xfsdump<br>
</I>uses the inventory to determine the base of incremental and resumed dumps.</p>
</td>
</tr>
</table>
<p><font size=3>This database can be displayed by invoking <font size=3><I>xfsdump</I> <font size=3>with the <font size=3><B>-I</B> <font size=3>option. The display uses tabbed indentation to present the inventory hierarchically. The first level is filesystem. The second level is session. The third level is media stream (currently only one stream is supported). The fourth level lists the media files sequentially compos- ing the stream.</p>
<p><font size=3>The following suboptions are available to filter the display. <font size=3><B>-I depth=</B><font size=3><I>n</I> <font size=3>(where <font size=3><I>n</I> <font size=3>is 1, 2, or 3) limits the hierarchi- cal depth of the display. When <font size=3><I>n</I> <font size=3>is 1, only the filesystem information from the inventory is displayed. When <font size=3><I>n</I> <font size=3>is 2, only filesystem and session information are displayed. When <font size=3><I>n</I> <font size=3>is 3, only filesystem, session and stream information are displayed. <font size=3><B>-I level=</B><font size=3><I>n</I> <font size=3>(where <font size=3><I>n</I> <font size=3>is the dump level) limits the display to dumps of that particular dump level.</p>
<p><font size=3>The display may be restricted to media files contained in a specific media object. <font size=3><B>-I mobjid=</B><font size=3><I>value</I> <font size=3>(where <font size=3><I>value</I> <font size=3>is a media ID) specifies the media object by its media ID. <font size=3><B>-I mobjlabel=</B><font size=3><I>value</I> <font size=3>(where <font size=3><I>value</I> <font size=3>is a media label) specifies the media object by its media label.</p>
<p><font size=3>Similarly, the display can be restricted to a specific filesystem. <font size=3><B>-I mnt=</B><font size=3><I>host-qualified_mount_point_pathname</I> <font size=3>(that is, hostname:pathname), identifies the filesystem by mountpoint. <font size=3><B>-I fsid=</B><font size=3><I>filesystem_id</I> <font size=3>identifies the filesys- tem by filesystem ID. <font size=3><B>-I dev=</B><font size=3><I>host-qualified_device_pathname</I> <font size=3>(that is, hostname:device_pathname) identifies the filesystem by device.</p>
<p><font size=3>More than one of these suboptions, separated by commas, may be specified at the same time to limit the display of the inventory to those dumps of interest. However, at most four suboptions can be specified at once: one to con- strain the display hierarchy depth, one to constrain the dump level, one to constrain the media object, and one to constrain the filesystem.</p>
<p><font size=3>For example, <font size=3><B>-I depth=1,mobjlabel="tape 1",mnt=host1:/test_mnt</B> <font size=3>would display only the filesystem informa- tion (depth=1) for those filesystems that were mounted on <font size=3><I>host1:/test_mnt</I> <font size=3>at the time of the dump, and only those filesystems dumped to the media object labeled "tape 1".</p>
<p><font size=3>Dump records may be removed (pruned) from the inventory using the <font size=3><I>xfsinvutil</I> <font size=3>program.</p>
<p><font size=3>An additional media file is placed at the end of each dump stream. This media file contains the inventory informa- tion for the current dump session. This is currently unused.</p>
<p><font size=3>When operating in the miniroot environment, <font size=3><I>xfsdump</I> <font size=3>does not create and does not reference the inventory<br>
</p>

<!-- Page: 4  -->
<!-- left  margin: 100 -->
<!-- right margin: 750 -->
<p><font size=3>database. Thus incremental and resumed dumps are not allowed.</p>

<table width="100%"  rules="none"  frame="none"  cols="4">
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="6.1538%">
<p><font size=3><B>Labels</p>
</B></td>
<td valign="top" align="left"  width="11.0769%">
</td>
<td valign="top" align="left"  width="80.0000%">
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="6.1538%">
</td>
<td valign="top" align="left"  width="11.0769%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>The operator can specify a label to identify the dump session and a label to identify a media object. The session label is placed in every media file produced in the course of the dump, and is recorded in the inventory.</p>
</td>
</tr>
</table>
<p><font size=3>The media label is used to identify media objects, and is independent of the session label. Each media file on the media object contains a copy of the media label. An error is returned if the operator specifies a media label that does not match the media label on a media object containing valid media files. Media labels are recorded in the inventory.</p>

<table width="100%"  rules="none"  frame="none"  cols="4">
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="17.0769%">
<p><font size=3><B>UUIDs</p>
</B></td>
<td valign="top" align="left"  width="1.0000%">
</td>
<td valign="top" align="left"  width="80.0000%">
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="17.0769%">
</td>
<td valign="top" align="left"  width="1.0000%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>UUIDs (Universally Unique Identifiers) are used in three places: to identify the filesystem being dumped (using the filesystem UUID, see <font size=3><I>xfs</I><font size=3>(4) for more details), to identify the dump session, and to identify each media object. The inventory display (<font size=3><B>-I</B><font size=3>) includes all of these.</p>
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="17.0769%">
<p><font size=3><B>Dump Level Usage</p>
</B></td>
<td valign="top" align="left"  width="1.0000%">
</td>
<td valign="top" align="left"  width="80.0000%">
</td>
</tr>
<tr valign="top" align="left">
<td valign="top" align="left"  width="2.7692%">
</td>
<td valign="top" align="left"  width="17.0769%">
</td>
<td valign="top" align="left"  width="1.0000%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3>The dump level mechanism provides a structured form of incremental dumps. A dump of level <font size=3><I>level</I> <font size=3>includes only files that have changed since the most recent dump at a level less than <font size=3><I>level</I><font size=3>. For example, the operator can establish a dump schedule that involves a full dump every Friday and a daily incremental dump containing only files that have changed since the previous dump. In this case Friday's dump would be at level 0, Saturday's at level 1, Sunday's at level 2, and so on, up to the Thursday dump at level 6.</p>
</td>
</tr>
</table>
<p><font size=3>The above schedule results in a very tedious restore procedure to fully reconstruct the Thursday version of the filesystem; <font size=3><I>xfsrestore</I> <font size=3>would need to be fed all 7 dumps in sequence. A compromise schedule is to use level 1 on Saturday, Monday, and Wednesday, and level 2 on Sunday, Tuesday, and Thursday. The Monday and Wednes- day dumps would take longer, but the worst case restore requires the accumulation of just three dumps, one each at level 0, level 1, and level 2.</p>
<p><span style=" text-indent: 0.1800in;"></span><font size=3><B>Miniroot Restrictions</p>
</B>
<table width="100%"  rules="none"  frame="none"  cols="2">
<tr valign="top" align="left">
<td valign="top" align="left"  width="20.0000%">
</td>
<td valign="top" align="left"  width="80.0000%">
<p><font size=3><I>xfsdump</I> <font size=3>is subject to the following restrictions when operated in the miniroot environment:<br>
non-restartable, no incrementals, no online inventory, synchronous I/O.</p>
</td>
</tr>
</table>
<br>
<a name="FILES"></a><h2>FILES</h2><p><font size=3>/var/xfsdump/inventory dump inventory database</p>
<a name="SEE ALSO"></a><h2>SEE ALSO</h2><p><font size=3>rmt(1M), xfsrestore(1M), xfsinvutil(1M), attr_get(2).</p>
<a name="DIAGNOSTICS"></a><h2>DIAGNOSTICS</h2><p><font size=3>The exit code is 0 on normal completion, non-zero if an error occurs or the dump is terminated by the operator.</p>
<p><font size=3>The message ``xfsdump: WARNING: unable to open directory: ino N: Invalid argument'' can occur with filesys- tems which are actively being modified while <font size=3><I>xfsdump</I> <font size=3>is running. This can happen to either directory or regular file inodes - affected files will not end up in the dump, files below affected directories will be placed in the <font size=3><I>orphan- age</I> <font size=3>directory by <font size=3><I>xfsrestore</I><font size=3>.</p>
<a name="BUGS"></a><h2>BUGS</h2><p><font size=3><I>xfsdump</I> <font size=3>does not dump unmounted filesystems.</p>
<p><font size=3>The dump frequency field of <font size=3><I>/etc/fstab</I> <font size=3>is not supported.</p>
<p><font size=3><I>xfsdump</I> <font size=3>uses the alert program only when a media change is required.</p>
<p><font size=3><I>xfsdump</I> <font size=3>requires root privilege (except for inventory display).</p>
<p><font size=3><I>xfsdump</I> <font size=3>can only dump XFS filesystems.</p>
<p><font size=3>The media format used by <font size=3><I>xfsdump</I> <font size=3>can only be understood by <font size=3><I>xfsrestore</I><font size=3>.</p>
<p><font size=3><I>xfsdump</I> <font size=3>does not know how to manage CD-ROM or other removable disk drives.</p>
<p><font size=3>When the minimal rmt option is specified, <font size=3><I>xfsdump</I> <font size=3>applies it to all remote tape destinations. The same blocksize (specified by the <font size=3><B>-b</B> <font size=3>option) is used for all these remote drives.</p>
<p><font size=3><I>xfsdump</I> <font size=3>can become confused when doing incremental or resumed dumps if on the same machine you dump two XFS filesystems and both filesystems have the same filesystem identifier (UUID). Since <font size=3><I>xfsdump</I> <font size=3>uses the filesys- tem identifier to identify filesystems, <font size=3><I>xfsdump</I> <font size=3>maintains one combined set of dump inventories for both filesytems instead of two sets of dump inventories. This scenario can happen only if <font size=3><I>dd</I> <font size=3>or some other block-by-block copy program was used to make a copy of an XFS filesystem. See <font size=3><I>xfs_copy</I><font size=3>(1M) and <font size=3><I>xfs</I><font size=3>(4) for more details.<br>
</p>
</body>
</html>