bak scantape(8dfs)

Synopsis

bak scantape [-dbadd] [-tcid tc_number] [-help]

Options

-dbadd
Adds the information extracted from the tape to the Backup Database if the tape is completely undamaged and the Backup Database does not already contain an entry with the same dump ID number.

-tcid tc_number
Specifies the Tape Coordinator ID (TCID) of the Tape Coordinator for the tape drive containing the tape. If omitted, it defaults to 0 (zero).

-help
Prints the online help for this command. All other valid options specified with this option are ignored.

Description
The bak scantape command reads the tape in the drive controlled by the Tape Coordinator indicated by -tcid, extracting information from the tape label and from the fileset header of each fileset on the tape. It does not extract actual data from the filesets, though the information it does extract is needed to restore the data using the Backup System.

The Tape Coordinator displays the information about each fileset in its monitoring window as it extracts the information. The Tape Coordinator checks for damage to the tape medium by checking for the presence of special markers it expects to find at the start and end of each fileset. If the Tape Coordinator does not find an expected marker, it concludes that the tape medium is damaged, and the command aborts.

If the -dbadd option is provided, the program creates a Backup Database entry for the tape and records the extracted information in the entry. It is not possible to extract information about only specific filesets on a tape. Because only data about all of the filesets on a tape can be extracted, this command works only if a tape is completely undamaged.

The Tape Coordinator does not require that the issuer insert all of the tapes containing a dump set unless a fileset is split across two tapes. In that case, it automatically prompts for the tape with the next-highest index to extract complete information about the fileset. If -dbadd is used, information from both tapes is added to the database.

If a tape contains only complete filesets, the Tape Coordinator reads the tape and prompts

Are there more tapes? (y/n)

If the issuer responds n, the command exits, adding the information from the tape to the Backup Database if -dbadd is used. If the issuer responds y, the Tape Coordinator prompts for the tape with the next highest index.

Privilege Required
The issuer must be listed in the admin.bak files on all Backup Database machines.

Cautions
Using the -dbadd option with this command introduces the possibility that two database entries will appear almost the same; you will need to track which physical tape corresponds to which entry.

Database entries are identified by three elements: the tape name, the dump level pathname, and a dump ID number, which is unique for every dump set. This command creates a database entry for the dump set on the tape as long as its dump ID number is different from any existing entry's ID number, even if the entry has the same tape name and dump level name as an existing entry.

Output
The bak scantape command first displays the following information from the label of the tape:

name
The tape label, in the format fileset_family_name.dump_level.index.

createTime
The date and time at which the Backup System started executing the dump operation that created this dump set.

cell
The cell in which the dump set was created.

size
The tape's capacity in kilobytes (not the amount of data on the tape). The value comes from the tape label and is derived from bak labeltape or the TapeConfig file rather than from a measurement of the tape.

dump path
The dump level used in creating the dump set.

dumpID
The dump ID number of the dump on the tape.

useCount
The number of times data has been dumped to this tape.

The command then displays an entry for each fileset. The entries appear in the order in which the filesets are encountered on the tape. If a fileset is split across two tapes, there is a separate entry for both fragments. Each entry includes the following information:

fileset name
The name of the fileset, with a .backup or .readonly extension if appropriate.

fileset ID
The fileset ID number of the fileset.

dumpSetName
The dump set to which the fileset belongs.

dumpID
The dump ID number of the dump set named by dumpSetName.

level
The depth in the dump hierarchy of the dump level used in creating the dump set. A value of 0 (zero) indicates a full dump set. A value of 1 or greater indicates an incremental dump set made at the indicated depth in the hierarchy. The value reported is for the entire dump, not necessarily for the fileset itself (for example, it is possible for an individual fileset to be dumped at a higher level if it was omitted from a previous dump set).

parentID
The dump ID number of dumpSetName's parent dump set (a parent dump set is a dump set made at the level that serves as the parent for a dump level). This should be 0 (zero) if level is 0 (zero).

endTime
Should always be 0 (zero); it is for internal use only.

clonedate
The date and time at which the fileset was created. For a backup or read-only fileset, this represents the time when it was cloned from its read/write source fileset. For a read/write fileset, it indicates when the Backup System accessed the fileset to include it in dumpSetName.

The following error message (usually preceded by other, more specific messages) indicates that the program has not encountered one of the markers it expects to find at the start and end of each fileset and has concluded that the tape is damaged. No data from this tape can be incorporated into the Backup Database.

aborting - this dump cannot be processed correctly

Examples
The following command shows the output from a tape's label and for the first fileset on the tape:

$ bak scantape

Tape label

- - - -

name = guests.monthly.1

createTime = Fri Nov 22 05:59:31 1990

cell = /.../abc.com

size = 20103324 Kbytes

dump path = /monthly

dump id = 729369701

useCount = 1

- End of tape label -

- fileset -

fileset name: user.guest10.backup

fileset ID 0,,112262

dumpSetName: guests.monthly

dumpID 729369701

level 0

parentID 0

endTime 0

clonedate Fri Nov 22 05:36:29 1991

Related Information
Commands: bak deletedump(8dfs)

bak dump(8dfs)

bak restoredisk(8dfs)

bak restoreft(8dfs)

kill (see the bak(8dfs) reference page for information about the kill command)