| blob | 10303c00f3160042f2a15e8221517232a857ff74 |
1 '\" te
2 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
3 .\" Copyright 1989 AT&T
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH UFSDUMP 1M "April 9, 2016"
8 .SH NAME
9 ufsdump \- incremental file system dump
10 .SH SYNOPSIS
11 .LP
12 .nf
13 \fB/usr/sbin/ufsdump\fR [\fIoptions\fR] [\fIarguments\fR] \fIfiles_to_dump\fR
14 .fi
16 .SH DESCRIPTION
17 .LP
18 \fBufsdump\fR backs up all files specified by \fIfiles_to_dump\fR (usually
19 either a whole file system or files within a file system changed after a certain
20 date) to magnetic tape, diskette, or disk file.
21 .sp
22 .LP
23 The \fBufsdump\fR command can only be used on unmounted file systems, or those
24 mounted read-only. Attempting to dump a mounted, read-write file system might
25 result in a system disruption or the inability to restore files from the dump.
26 Consider using the \fBfssnap\fR(1M) command to create a file system snapshot if
27 you need a point-in-time image of a file system that is mounted.
28 .sp
29 .LP
30 If a filesystem was mounted with the logging option, it is strongly
31 recommended that you run \fBufsdump\fR as the root user. Running the command as
32 a non-root user might result in the creation of an inconsistent dump.
33 .sp
34 .LP
35 \fIoptions\fR is a single string of one-letter \fBufsdump\fR options.
36 .sp
37 .LP
38 \fIarguments\fR may be multiple strings whose association with the options is
39 determined by order. That is, the first argument goes with the first option
40 that takes an argument; the second argument goes with the second option that
41 takes an argument, and so on.
42 .sp
43 .LP
44 \fIfiles_to_dump\fR is required and must be the last argument on the command
45 line. See \fBOPERANDS\fR for more information.
46 .sp
47 .LP
48 With most devices \fBufsdump\fR can automatically detect the end-of-media.
49 Consequently, the \fBd\fR, \fBs\fR, and \fBt\fR options are not necessary for
50 multi-volume dumps, unless \fBufsdump\fR does not understand the way the device
51 detects the end-of-media, or the files are to be restored on a system with an
52 older version of the \fBrestore\fR command.
53 .SH OPTIONS
54 .LP
55 The following options are supported:
56 .sp
57 .ne 2
58 .na
59 \fB\fB0\(mi9\fR\fR
60 .ad
61 .sp .6
62 .RS 4n
63 The "dump level." All files specified by \fIfiles_to_dump\fR that have been
64 modified since the last \fBufsdump\fR at a lower dump level are copied to the
65 \fIdump_file\fR destination (normally a magnetic tape device). For instance, if
66 a "level \fB2\fR" dump was done on Monday, followed by a "level \fB4\fR" dump
67 on Tuesday, a subsequent "level \fB3\fR" dump on Wednesday would contain all
68 files modified or added since the "level \fB2\fR" (Monday) backup. A "level
69 \fB0\fR" dump copies the entire file system to the \fIdump_file\fR.
70 .RE
72 .sp
73 .ne 2
74 .na
75 \fB\fBa\fR \fIarchive_file\fR\fR
76 .ad
77 .sp .6
78 .RS 4n
79 Archive file. Archive a dump table-of-contents in the specified
80 \fIarchive_file\fR to be used by \fBufsrestore\fR(1M) to determine whether a
81 file is in the dump file that is being restored.
82 .RE
84 .sp
85 .ne 2
86 .na
87 \fB\fBb\fR \fIfactor\fR\fR
88 .ad
89 .sp .6
90 .RS 4n
91 Blocking factor. Specify the blocking factor for tape writes. The default is 20
92 blocks per write for tapes of density less than 6250BPI (bytes-per-inch). The
93 default blocking factor for tapes of density 6250BPI and greater is 64. The
94 default blocking factor for cartridge tapes (\fBc\fR option) is 126. The
95 highest blocking factor available with most tape drives is 126. Note: the
96 blocking factor is specified in terms of 512-byte blocks, for compatibility
97 with \fBtar\fR(1).
98 .RE
100 .sp
101 .ne 2
102 .na
103 \fB\fBc\fR\fR
104 .ad
105 .sp .6
106 .RS 4n
107 Cartridge. Set the defaults for cartridge instead of the standard half-inch
108 reel. This sets the density to 1000BPI and the blocking factor to 126. Since
109 \fBufsdump\fR can automatically detect the end-of-media, only the blocking
110 parameter normally has an effect. When cartridge tapes are used, and this
111 option is \fInot\fR specified, \fBufsdump\fR will slightly miscompute the size
112 of the tape. If the \fBb\fR, \fBd\fR, \fBs\fR or \fBt\fR options are specified
113 with this option, their values will override the defaults set by this option.
114 .RE
116 .sp
117 .ne 2
118 .na
119 \fB\fBd\fR \fIbpi\fR\fR
120 .ad
121 .sp .6
122 .RS 4n
123 Tape density. Not normally required, as \fBufsdump\fR can detect end-of-media.
124 This parameter can be used to keep a running tab on the amount of tape used per
125 reel. The default density is 6250BPI except when the \fBc\fR option is used for
126 cartridge tape, in which case it is assumed to be 1000BPI per track. Typical
127 values for tape devices are:
128 .sp
129 .ne 2
130 .na
131 \fB1/2 inch tape\fR
132 .ad
133 .sp .6
134 .RS 4n
135 6250 BPI
136 .RE
138 .sp
139 .ne 2
140 .na
141 \fB1/4 inch cartridge\fR
142 .ad
143 .sp .6
144 .RS 4n
145 1000 BPI The tape densities and other options are documented in the
146 \fBst\fR(7D) man page.
147 .RE
149 .RE
151 .sp
152 .ne 2
153 .na
154 \fB\fBD\fR\fR
155 .ad
156 .sp .6
157 .RS 4n
158 Diskette. Dump to diskette.
159 .RE
161 .sp
162 .ne 2
163 .na
164 \fB\fBf\fR \fIdump_file\fR\fR
165 .ad
166 .sp .6
167 .RS 4n
168 Dump file. Use \fIdump_file\fR as the file to dump to, instead of
169 \fB/dev/rmt/0\fR. If \fIdump_file\fR is specified as \fB\(mi\fR, dump to
170 standard output.
171 .sp
172 If the name of the file is of the form \fImachine\fR\fB:\fR\fIdevice,\fR the
173 dump is done from the specified machine over the network using \fBrmt\fR(1M).
174 Since \fBufsdump\fR is normally run by root, the name of the local machine must
175 appear in the \fB/.rhosts\fR file of the remote machine. If the file is
176 specified as \fIuser\fR\fB@\fR\fImachine\fR\fB:\fR\fIdevice,\fR \fBufsdump\fR
177 will attempt to execute as the specified user on the remote machine. The
178 specified user must have a \fB\&.rhosts\fR file on the remote machine that
179 allows the user invoking the command from the local machine to access the
180 remote machine.
181 .RE
183 .sp
184 .ne 2
185 .na
186 \fB\fBl\fR\fR
187 .ad
188 .sp .6
189 .RS 4n
190 Autoload. When the end-of-tape is reached before the dump is complete, take the
191 drive offline and wait up to two minutes for the tape drive to be ready again.
192 This gives autoloading (stackloader) tape drives a chance to load a new tape.
193 If the drive is ready within two minutes, continue. If it is not, prompt for
194 another tape and wait.
195 .RE
197 .sp
198 .ne 2
199 .na
200 \fB\fBL\fR \fIstring\fR\fR
201 .ad
202 .sp .6
203 .RS 4n
204 Sets the tape label to \fIstring\fR, instead of the default \fBnone\fR.
205 \fIstring\fR may be no more than sixteen characters long. If it is longer, it
206 is truncated and a warning printed; the dump will still be done. The tape label
207 is specific to the \fBufsdump\fR tape format, and bears no resemblance to
208 \fBIBM\fR or \fBANSI\fR-standard tape labels.
209 .RE
211 .sp
212 .ne 2
213 .na
214 \fB\fBn\fR\fR
215 .ad
216 .sp .6
217 .RS 4n
218 Notify all operators in the \fBsys\fR group that \fBufsdump\fR requires
219 attention by sending messages to their terminals, in a manner similar to that
220 used by the \fBwall\fR(1M) command. Otherwise, such messages are sent only to
221 the terminals (such as the console) on which the user running \fBufsdump\fR is
222 logged in.
223 .RE
225 .sp
226 .ne 2
227 .na
228 \fB\fBN\fR \fIdevice_name\fR\fR
229 .ad
230 .sp .6
231 .RS 4n
232 Use \fIdevice_name\fR when recording information in \fB/etc/dumpdates\fR (see
233 the \fBu\fR option) and when comparing against information in
234 \fB/etc/dumpdates\fR for incremental dumps. The \fIdevice_name\fR provided can
235 contain no white space as defined in \fBscanf\fR(3C) and is case-sensitive.
236 .RE
238 .sp
239 .ne 2
240 .na
241 \fB\fBo\fR\fR
242 .ad
243 .sp .6
244 .RS 4n
245 Offline. Take the drive offline when the dump is complete or the end-of-media
246 is reached and rewind the tape, or eject the diskette. In the case of some
247 autoloading 8mm drives, the tape is removed from the drive automatically. This
248 prevents another process which rushes in to use the drive, from inadvertently
249 overwriting the media.
250 .RE
252 .sp
253 .ne 2
254 .na
255 \fB\fBs\fR \fIsize\fR\fR
256 .ad
257 .sp .6
258 .RS 4n
259 Specify the \fIsize\fR of the volume being dumped to. Not normally required, as
260 \fBufsdump\fR can detect end-of-media. When the specified size is reached,
261 \fBufsdump\fR waits for you to change the volume. \fBufsdump\fR interprets the
262 specified size as the length in feet for tapes and cartridges, and as the
263 number of 1024-byte blocks for diskettes. The values should be a little smaller
264 than the actual physical size of the media (for example, 425 for a 450-foot
265 cartridge). Typical values for tape devices depend on the \fBc\fR option, for
266 cartridge devices, and the \fBD\fR option for diskettes:
267 .sp
268 .ne 2
269 .na
270 \fB1/2 inch tape\fR
271 .ad
272 .sp .6
273 .RS 4n
274 2300 feet
275 .RE
277 .sp
278 .ne 2
279 .na
280 \fB60-Mbyte 1/4 inch cartridge\fR
281 .ad
282 .sp .6
283 .RS 4n
284 425 feet
285 .RE
287 .sp
288 .ne 2
289 .na
290 \fB150-Mbyte 1/4 inch cartridge\fR
291 .ad
292 .sp .6
293 .RS 4n
294 700 feet
295 .RE
297 .sp
298 .ne 2
299 .na
300 \fBdiskette\fR
301 .ad
302 .sp .6
303 .RS 4n
304 1422 blocks (Corresponds to a 1.44-Mbyte diskette, with one cylinder reserved
305 for bad block information.)
306 .RE
308 .RE
310 .sp
311 .ne 2
312 .na
313 \fB\fBS\fR\fR
314 .ad
315 .sp .6
316 .RS 4n
317 Size estimate. Determine the amount of space that is needed to perform the dump
318 without actually doing it, and display the estimated number of bytes it will
319 take. This is useful with incremental dumps to determine how many volumes of
320 media will be needed.
321 .RE
323 .sp
324 .ne 2
325 .na
326 \fB\fBt\fR \fItracks\fR\fR
327 .ad
328 .sp .6
329 .RS 4n
330 Specify the number of tracks for a cartridge tape. Not normally required, as
331 \fBufsdump\fR can detect end-of-media. The default is 9 tracks. The \fBt\fR
332 option is not compatible with the \fBD\fR option. Values for Sun-supported tape
333 devices are:
334 .sp
335 .ne 2
336 .na
337 \fB60-Mbyte 1/4 inch cartridge\fR
338 .ad
339 .sp .6
340 .RS 4n
341 9 tracks
342 .RE
344 .sp
345 .ne 2
346 .na
347 \fB150-Mbyte 1/4 inch cartridge\fR
348 .ad
349 .sp .6
350 .RS 4n
351 18 tracks
352 .RE
354 .RE
356 .sp
357 .ne 2
358 .na
359 \fB\fBT\fR \fItime_wait\fR\fB[hms]\fR\fR
360 .ad
361 .sp .6
362 .RS 4n
363 Sets the amount of time to wait for an \fBautoload\fR command to complete. This
364 option is ignored unless the \fBl\fR option has also been specified. The
365 default time period to wait is two minutes. Specify time units with a trailing
366 \fBh\fR ( for hours), \fBm\fR (for minutes), or \fBs\fR (for seconds). The
367 default unit is minutes.
368 .RE
370 .sp
371 .ne 2
372 .na
373 \fB\fBu\fR\fR
374 .ad
375 .sp .6
376 .RS 4n
377 Update the dump record. Add an entry to the file \fB/etc/dumpdates,\fR for each
378 file system successfully dumped that includes the file system name (or
379 \fIdevice_name\fR as specified with the \fBN\fR option), date, and dump level.
380 .RE
382 .sp
383 .ne 2
384 .na
385 \fB\fBv\fR\fR
386 .ad
387 .sp .6
388 .RS 4n
389 Verify. After each tape or diskette is written, verify the contents of the
390 media against the source file system. If any discrepancies occur, prompt for
391 new media, then repeat the dump/verification process. The file system
392 \fImust\fR be unmounted. This option cannot be used to verify a dump to
393 standard output.
394 .RE
396 .sp
397 .ne 2
398 .na
399 \fB\fBw\fR\fR
400 .ad
401 .sp .6
402 .RS 4n
403 Warning. List the file systems that have not been backed up within a day. This
404 information is gleaned from the files \fB/etc/dumpdates\fR and
405 \fB/etc/vfstab\fR. When the \fBw\fR option is used, all other options are
406 ignored. After reporting, \fBufsdump\fR exits immediately.
407 .RE
409 .sp
410 .ne 2
411 .na
412 \fB\fBW\fR\fR
413 .ad
414 .sp .6
415 .RS 4n
416 Warning with highlight. Similar to the \fBw\fR option, except that the \fBW\fR
417 option includes all file systems that appear in \fB/etc/dumpdates\fR, along
418 with information about their most recent dump dates and levels. File systems
419 that have not been backed up within a day are highlighted.
420 .RE
422 .SH OPERANDS
423 .LP
424 The following operand is supported:
425 .sp
426 .ne 2
427 .na
428 \fB\fIfiles_to_dump\fR\fR
429 .ad
430 .sp .6
431 .RS 4n
432 Specifies the files to dump. Usually it identifies a whole file system by its
433 raw device name (for example, \fB/dev/rdsk/c0t3d0s6\fR). Incremental dumps
434 (levels \fB1\fR to \fB9\fR) of files changed after a certain date only apply to
435 a whole file system. Alternatively, \fIfiles_to_dump\fR can identify individual
436 files or directories. All named directories that may be examined by the user
437 running \fBufsdump\fR, as well as any explicitly-named files, are dumped. This
438 dump is equivalent to a level \fB0\fR dump of the indicated portions of the
439 filesystem, except that \fB/etc/dumpdates\fR is not updated even if the
440 \fB-u\fR option has been specified. In all cases, the files must be contained
441 in the same file system, and the file system must be local to the system where
442 \fBufsdump\fR is being run.
443 .sp
444 \fIfiles_to_dump\fR is required and must be the last argument on the command
445 line.
446 .RE
448 .sp
449 .LP
450 If no \fIoptions\fR are given, the default is \fB9uf\fR \fB/dev/rmt/0\fR
451 \fIfiles_to_dump\fR.
452 .SH USAGE
453 .LP
454 See \fBlargefile\fR(5) for the description of the behavior of \fBufsdump\fR
455 when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
456 .SH EXAMPLES
457 .LP
458 \fBExample 1 \fRUsing \fBufsdump\fR
459 .sp
460 .LP
461 The following command makes a full dump of a root file system on \fBc0t3d0\fR,
462 on a 150-MByte cartridge tape unit \fB0\fR:
464 .sp
465 .in +2
466 .nf
467 example# ufsdump 0cfu /dev/rmt/0 /dev/rdsk/c0t3d0s0
468 .fi
469 .in -2
470 .sp
472 .sp
473 .LP
474 The following command makes and verifies an incremental dump at level \fB5\fR
475 of the \fBusr\fR partition of \fBc0t3d0\fR, on a 1/2 inch reel tape unit
476 \fB1,\fR:
478 .sp
479 .in +2
480 .nf
481 example# ufsdump 5fuv /dev/rmt/1 /dev/rdsk/c0t3d0s6
482 .fi
483 .in -2
484 .sp
486 .SH EXIT STATUS
487 .LP
488 While running, \fBufsdump\fR emits many verbose messages. \fBufsdump\fR returns
489 the following exit values:
490 .sp
491 .ne 2
492 .na
493 \fB\fB0\fR\fR
494 .ad
495 .sp .6
496 .RS 4n
497 Normal exit.
498 .RE
500 .sp
501 .ne 2
502 .na
503 \fB\fB1\fR\fR
504 .ad
505 .sp .6
506 .RS 4n
507 Startup errors encountered.
508 .RE
510 .sp
511 .ne 2
512 .na
513 \fB\fB3\fR\fR
514 .ad
515 .sp .6
516 .RS 4n
517 Abort \(mi no checkpoint attempted.
518 .RE
520 .SH FILES
521 .ne 2
522 .na
523 \fB\fB/dev/rmt/0\fR\fR
524 .ad
525 .sp .6
526 .RS 4n
527 default unit to dump to
528 .RE
530 .sp
531 .ne 2
532 .na
533 \fB\fB/etc/dumpdates\fR\fR
534 .ad
535 .sp .6
536 .RS 4n
537 dump date record
538 .RE
540 .sp
541 .ne 2
542 .na
543 \fB\fB/etc/group\fR\fR
544 .ad
545 .sp .6
546 .RS 4n
547 to find group \fBsys\fR
548 .RE
550 .sp
551 .ne 2
552 .na
553 \fB\fB/etc/hosts\fR\fR
554 .ad
555 .sp .6
556 .RS 4n
557 to gain access to remote system with drive
558 .RE
560 .sp
561 .ne 2
562 .na
563 \fB\fB/etc/vfstab\fR\fR
564 .ad
565 .sp .6
566 .RS 4n
567 list of file systems
568 .RE
570 .SH SEE ALSO
571 .LP
572 \fBcpio\fR(1), \fBtar\fR(1), \fBdd\fR(1M), \fBdevnm\fR(1M), \fBfssnap\fR(1M),
573 \fBprtvtoc\fR(1M), \fBrmt\fR(1M), \fBshutdown\fR(1M), \fBufsrestore\fR(1M),
574 \fBvolcopy\fR(1M), \fBwall\fR(1M), \fBscanf\fR(3C), \fBufsdump\fR(4),
575 \fBattributes\fR(5), \fBlargefile\fR(5), \fBst\fR(7D)
576 .SH NOTES
577 .SS "Read Errors"
578 .LP
579 Fewer than 32 read errors on the file system are ignored.
580 .SS "Process Per Reel"
581 .LP
582 Because each reel requires a new process, parent processes for reels that are
583 already written hang around until the entire tape is written.
584 .SS "Operator Intervention"
585 .LP
586 \fBufsdump\fR requires operator intervention on these conditions: end of
587 volume, end of dump, volume write error, volume open error or disk read error
588 (if there are more than a threshold of 32). In addition to alerting all
589 operators implied by the \fBn\fR option, \fBufsdump\fR interacts with the
590 operator on \fBufsdump\fR's control terminal at times when \fBufsdump\fR can no
591 longer proceed, or if something is grossly wrong. All questions \fBufsdump\fR
592 poses \fImust\fR be answered by typing \fByes\fR or \fBno\fR, as appropriate.
593 .sp
594 .LP
595 Since backing up a disk can involve a lot of time and effort, \fBufsdump\fR
596 checkpoints at the start of each volume. If writing that volume fails for some
597 reason, \fBufsdump\fR will, with operator permission, restart itself from the
598 checkpoint after a defective volume has been replaced.
599 .SS "Suggested Dump Schedule"
600 .LP
601 It is vital to perform full, "level \fB0\fR", dumps at regular intervals. When
602 performing a full dump, bring the machine down to single-user mode using
603 \fBshutdown\fR(1M). While preparing for a full dump, it is a good idea to clean
604 the tape drive and heads. Incremental dumps should be performed with the system
605 running in single-user mode.
606 .sp
607 .LP
608 Incremental dumps allow for convenient backup and recovery of active files on a
609 more frequent basis, with a minimum of media and time. However, there are some
610 tradeoffs. First, the interval between backups should be kept to a minimum
611 (once a day at least). To guard against data loss as a result of a media
612 failure (a rare, but possible occurrence), capture active files on (at least)
613 two sets of dump volumes. Another consideration is the desire to keep
614 unnecessary duplication of files to a minimum to save both operator time and
615 media storage. A third consideration is the ease with which a particular
616 backed-up version of a file can be located and restored. The following
617 four-week schedule offers a reasonable tradeoff between these goals.
618 .sp
619 .in +2
620 .nf
621 Sun Mon Tue Wed Thu Fri
622 Week 1: Full 5 5 5 5 3
623 Week 2: 5 5 5 5 3
624 Week 3: 5 5 5 5 3
625 Week 4: 5 5 5 5 3
626 .fi
627 .in -2
628 .sp
630 .sp
631 .LP
632 Although the Tuesday through Friday incrementals contain "extra copies" of
633 files from Monday, this scheme assures that any file modified during the week
634 can be recovered from the previous day's incremental dump.
635 .SS "Process Priority of ufsdump"
636 .LP
637 \fBufsdump\fR uses multiple processes to allow it to read from the disk and
638 write to the media concurrently. Due to the way it synchronizes between these
639 processes, any attempt to run dump with a \fBnice\fR (process priority) of
640 `\(mi5' or better will likely make \fBufsdump\fR run \fIslower\fR instead of
641 faster.
642 .SS "Overlapping Partitions"
643 .LP
644 Most disks contain one or more overlapping slices because slice 2 covers the
645 entire disk. The other slices are of various sizes and usually do not overlap.
646 For example, a common configuration places \fBroot\fR on slice 0, \fBswap\fR on
647 slice 1, \fB/opt\fR on slice 5 and \fB/usr\fR on slice 6.
648 .sp
649 .LP
650 It should be emphasized that \fBufsdump\fR dumps one \fBufs\fR file system at a
651 time. Given the above scenario where slice 0 and slice 2 have the same starting
652 offset, executing \fBufsdump\fR on slice 2 with the intent of dumping the
653 entire disk would instead dump only the \fBroot\fR file system on slice 0. To
654 dump the entire disk, the user must dump the file systems on each slice
655 separately.
656 .SH BUGS
657 .LP
658 The \fB/etc/vfstab\fR file does not allow the desired frequency of backup for
659 file systems to be specified (as \fB/etc/fstab\fR did). Consequently, the
660 \fBw\fR and \fBW\fR options assume file systems should be backed up daily,
661 which limits the usefulness of these options.