Table of ContentsView in Frames

Checking the status of a dump backup

During a lengthy dump session, you are advised to monitor the progress and check the status of the session. This helps you to determine if the backup is proceeding as expected.

Step

  1. To check the status of a dump command, enter the following command:
    stat show dump

    The output of the stat show dump command displays the following statistics about the data set and progress:

    • The number of directories that will be dumped
    • The number of files that will be dumped
    • The number of NT STREAMS
    • The number of ACLs
    • The average directory size
    • The average file size

    The following are the progress statistics listed by the command:

    • The number of directories dumped in Phase 3
    • The amount of directory data, in KB, currently written to tape in Phase 3
    • The number of inodes dumped in Phase 4
    • The amount of inode data, in KB, currently written to tape in Phase 4

    Example

    The following is an example of the stat show dump command output:

    filer1>stat show dump
    dump:id_0:p1-ino:6097
    dump:id_0:p1-dir:412
    dump:id_0:p1-str-ino:0
    dump:id_0:p1-str-dir:0
    dump:id_0:p1-acl:0
    dump:id_0:p3-dir:413
    dump:id_0:p3-write:487
    dump:id_0:p4-ino:1962
    dump:id_0:p4-write:135043

    Statistics shown in the preceding example are as follows:

    • id_0 is the instance name for dump statistics.

      The number part of the instance name specifies the dump ID.

    • p1-ino shows the total number of regular inodes that will be dumped.
    • p1-dir shows the total number of directory inodes that will be dumped.
    • p1-str-ino shows the total number of NT stream inodes that will be dumped.
    • p1-str-dir shows the total number of NT stream directories that will be dumped.
    • p1-acl shows the total number of ACL inodes that will be dumped.
    • p3-dir shows the total number of directory inodes that have been written in Phase 3.
    • p3-write shows the total number of kilobytes (KB) of directory tape data that have been written in Phase 3.
    • p4-ino shows the total number of inodes that have been dumped in Phase 4.
    • p4-write shows the total number of kilobytes (KB) of inode tape data that have been written in Phase 4.

Example

The following is an example of statistics shown in the backup log:

dmp ... /vol/compat/(3) Start (Level 0)
...
dmp ... /vol/compat/(3) End (126 MB)
dmp ... /vol/compat/(3) Log_msg (reg inodes: 1574 other inodes: 1061 dirs: 200 nt dirs: 54 nt inodes: 204 acls: 49)
dmp ... /vol/compat/(3) Log_msg (Phase 1 time: 261)
dmp ... /vol/compat/(3) Log_msg (Phase 3: directories dumped: 255)
dmp .. /vol/compat/(3) Log_msg (Phase 3: wafl directory blocks read: 291)
dmp ... /vol/compat/(3) Log_msg (Phase 3: average wafl directory blocks per inode: 1)
dmp ... /vol/compat/(3) Log_msg (Phase 3: average tape blocks per inode: 2)
dmp ... /vol/compat/(3) Log_msg (Phase 3 throughput (MB sec): read 0 write 0)
dmp ... /vol/compat/(3) Log_msg (Percent of phase3 time spent for: reading inos 0% dumping ino 93%)
dmp ... /vol/compat/(3) Log_msg (Percent of phase3 dump time spent for: convert-wafl-dirs 4% lev0-ra 1%)
dmp ... /vol/compat/(3) Log_msg (Phase 3 averages (usec): wafl load buf time 27 level 0 ra time 62)
dmp ... /vol/compat/(3) Log_msg (Phase 4: inodes dumped: 2839)
dmp ... /vol/compat/(3) Log_msg (Phase 4: wafl data blocks read: 55502)
dmp ... /vol/compat/(3) Log_msg (Phase 4: average wafl data blocks per inode: 19)
dmp ... /vol/compat/(3) Log_msg (Phase 4: average tape data blocks per inode: 75)
dmp ... /vol/compat/(3) Log_msg (Phase 4 throughput (MB sec): read 51 write 50)
dmp ... /vol/compat/(3) Log_msg (Percent of phase4 time spent for: reading inos 3% dumping inos 94%)
dmp ... /vol/compat/(3) Log_msg (Tape write times (msec): average: 0 max: 1863)
dmp ... /vol/compat/(3) Log_msg (Tape changes: 1)

Statistics shown in the backup log example are as follows:

  • reg inodes, other inodes, dirs, nt dirs, nt inodes, acls—The total number of regular inodes, other inodes such as symlinks or char devices, directory inodes, NT STREAMS inodes, and ACL inodes that will be dumped.
  • Phase 3:directories dumped —The total number of directory inodes dumped in Phase 3.
  • Phase 3: wafl directory blocks read—The total number of WAFL directory blocks read.
  • Phase 3: average wafl directory block per inode—The average size of directories that were dumped.
  • Phase 3: average tape blocks per inode—The average number of dump tape blocks (1K) for each directory inode.
  • Phase 3 throughput (MB sec) —The read and write throughputs, in MBps, for Phase 3.
  • Percent of phase3 time spent for: reading inos and dumping inos—An indication of where time is spent in Phase 3.
  • Percent of phase3 dump time spent for: convert-wafl-dirs and lev0-ra—An indication of where time is spent in Phase 3.
  • Phase 3 averages (usec): wafl load buf time and level 0 ra time—An indication of how long it takes to read a WAFL directory block and how long it took to read ahead for these blocks.
  • Phase 4: inodes dumped—The total number of inodes dumped in Phase 4.
  • Phase 4: wafl data blocks read—The total number of WAFL data blocks read.
  • Phase 4: average wafl data blocks per inode—An indication of the average size of files that were dumped.
  • Phase 4: average tape data blocks per inode—The average number of dump tape blocks (1K) for each inode.
  • Phase 4 throughput (MB sec)—The read and write throughputs, in MBps, for Phase 4.
  • Percent of phase4 time spent for: reading inos and dumping inos—An indication of where time is spent in Phase 4.
  • Percent of phase4 dump time spent for:wafl read iovec and lev0-ra—An indication of where time is spent in Phase 4.
  • Phase 4 averages (usec): wafl read iovec time and level 0 ra time—An indication of how long it takes to read a file block and how long it took to read ahead for these blocks.
  • Tape write times (msec): average and max—An indication of how long it took to write out a tape block.
  • Tape changes—The number of tape changes.