https://gunkies.org/index.php?action=history&feed=atom&title=32v_1m_dump 2026-05-18T17:56:40Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=32v_1m_dump&diff=6958&oldid=prev 2009-10-26T13:55:30Z

<p>New page: DUMP(1M) UNIX Programmer&#039;s Manual DUMP(1M) == NAME == dump - incremental file system dump == SYNOPSIS == dump [ key [ argument ... ] filesystem ] == D...</p> <p><b>New page</b></p><div>DUMP(1M) UNIX Programmer's Manual DUMP(1M)<br /> <br /> <br /> <br /> == NAME ==<br /> dump - incremental file system dump<br /> <br /> == SYNOPSIS ==<br /> dump [ key [ argument ... ] filesystem ]<br /> <br /> == DESCRIPTION ==<br /> _D_u_m_p copies to magnetic tape all files changed after a cer-<br /> tain date in the _f_i_l_e_s_y_s_t_e_m. The _k_e_y specifies the date and<br /> other options about the dump. _K_e_y consists of characters<br /> from the set 0123456789fusd.<br /> <br /> f Place the dump on the next _a_r_g_u_m_e_n_t file instead of the<br /> tape.<br /> <br /> u If the dump completes successfully, write the date of<br /> the beginning of the dump on file `/etc/ddate'. This<br /> file records a separate date for each filesystem and<br /> each dump level.<br /> <br /> 0-9 This number is the `dump level'. All files modified<br /> since the last date stored in the file `/etc/ddate' for<br /> the same filesystem at lesser levels will be dumped.<br /> If no date is determined by the level, the beginning of<br /> time is assumed; thus the option 0 causes the entire<br /> filesystem to be dumped.<br /> <br /> s The size of the dump tape is specified in feet. The<br /> number of feet is taken from the next _a_r_g_u_m_e_n_t. When<br /> the specified size is reached, the dump will wait for<br /> reels to be changed. The default size is 2300 feet.<br /> <br /> d The density of the tape, expressed in BPI, is taken<br /> from the next _a_r_g_u_m_e_n_t. This is used in calculating the<br /> amount of tape used per write. The default is 1600.<br /> <br /> If no arguments are given, the _k_e_y is assumed to be 9u and a<br /> default file system is dumped to the default tape.<br /> <br /> Now a short suggestion on how perform dumps. Start with a<br /> full level 0 dump<br /> <br /> dump 0u<br /> <br /> Next, periodic level 9 dumps should be made on an exponen-<br /> tial progression of tapes. (Sometimes called Tower of Hanoi<br /> - 1 2 1 3 1 2 1 4 ... tape 1 used every other time, tape 2<br /> used every fourth, tape 3 used every eighth, etc.)<br /> <br /> dump 9u<br /> <br /> When the level 9 incremental approaches a full tape (about<br /> 78000 blocks at 1600 BPI blocked 20), a level 1 dump should<br /> be made.<br /> <br /> dump 1u<br /> <br /> After this, the exponential series should progress as unin-<br /> terrupted. These level 9 dumps are based on the level 1<br /> dump which is based on the level 0 full dump. This progres-<br /> sion of levels of dump can be carried as far as desired.<br /> <br /> == FILES ==<br /> default filesystem and tape vary with installation.<br /> /etc/ddate record dump dates of filesystem/level.<br /> <br /> == SEE ALSO ==<br /> [[32v 1m restor|restor(1)]], [[32v 5m dump|dump(5)]], [[32v 1m dumpdir|dumpdir(1)]]<br /> <br /> == DIAGNOSTICS ==<br /> If the dump requires more than one tape, it will ask you to<br /> change tapes. Reply with a new-line when this has been<br /> done.<br /> <br /> == BUGS ==<br /> Sizes are based on 1600 BPI blocked tape. The raw magtape<br /> device has to be used to approach these densities. Read<br /> errors on the filesystem are ignored. Write errors on the<br /> magtape are usually fatal.<br /> <br /> [[Category:32v man section 1]]</div>

Neozeed