1 Version 4.0 -- 1/15/89 console
______________________________________________________________________
NAME: console
FUNCTION:
Operator's utility for dumping to or loading from a tape drive.
SYNTAX:
console
Note that the console program must be running and DSCONSOLE must
be defined in the environment before a DUMP or LOAD can proceed.
See also following COMMENTS.
console Version 4.0 -- 1/15/89 2
______________________________________________________________________
MESSAGES:
Here are console's prompts when writing to tape (dumping a
database or transaction log), and explanations of them:
Mount first tape: mount tape on drive device_name.
Type n to quit, otherwise ok when mounted.
device_name - physical tape device name
Change tape: mount tape on drive device_name.
Type n to quit, otherwise ok when mounted.
device_name - physical tape device name
Tape on device_name has restricted access - expires day <day> of
19<year>.
3 Version 4.0 -- 1/15/89 console
______________________________________________________________________
Type n if you want to change tape, otherwise ok to use this
one.
device_name - physical tape device name
date - given as day (1 through 366) within year, e.g., day
100 of 1986
It is usually best only to write tapes that are not marked
for restricted access, and that have not expired.
Access is never restricted if the tape was created by
SQL Server. If your site has an ANSI tape format initializa-
tion program, it may have given the tape restricted access.
This prompt allows the operator to override an error and
rewrite the tape with unrestricted access.
The expiration date written onto a tape is calculated as the
console Version 4.0 -- 1/15/89 4
______________________________________________________________________
creation date plus the configurable tape retention period.
The expiration date helps prevent tapes from being inadver-
tently overwritten.
Remove the tape - type anything when done.
Press the ENTER key, or type anything and then press ENTER.
Here are console's prompts when reading from tape (loading a
database or transaction log), and explanations of them:
Mount first tape: mount tape_name volume_number on drive
device_name.
Type n if no tapes are available, otherwise ok when mounted.
Change tape: mount tape_name volume_number on drive device_name.
Type n if no tapes are available, otherwise ok when mounted.
5 Version 4.0 -- 1/15/89 console
______________________________________________________________________
tape - usually name of the DUMP, first 17 characters of data-
base name
volume_number - tape volume sequence number
device_name - physical tape device name, e.g. /dev/rmt4
Tape tape_name volume_number mounted instead of tape_name
volume_number.
Type n if you want to change tape, otherwise ok to use this
one.
The first tape name and volume number are read from the tape
that was mounted. The second tape name and volume number
refer to the tape that was expected to be mounted. Mounting
a tape out of sequence or with a different tape name is usu-
ally an error, but an operator might have a good reason to
override this error and use the tapes in the order mounted.
console Version 4.0 -- 1/15/89 6
______________________________________________________________________
Creation dates on device_name differ: date on this tape is day
<day> of 19<year>. Date on previous tape is day <day> of
19<year>.
Type n if you want to change tape, otherwise ok to use this
one.
device_name - physical tape device name
dates - given as day (1 through 366) within year, eg. day 100
of 1986.
Mounting tapes that were made on different days as part of
the same LOAD is usually an error, but an operator might have
a good reason to do so.
COMMENTS:
o The console program is a process that supports DUMP and LOAD
for tape drives. Relevant commands include DUMP DATABASE, DUMP
7 Version 4.0 -- 1/15/89 console
______________________________________________________________________
TRANsaction, LOAD DATABASE, and LOAD TRANsaction.
o The console program prompts the operator for information relat-
ing to mounting and unmounting tape drives.
o The console program can be started each time SQL Server is
started, and left running in background continuously. It must
be brought into foreground before a DUMP or LOAD.
o The DSCONSOLE environment variable must be defined before you
can use console for a DUMP or LOAD to tape.
o If the console program dies for any reason, the operator is
prompted to restart it.
o Do not attempt to stop the console utility with ^C or any other
interrupt signal from the operating system. Instead, put con-
sole in background when it is not needed. If SQL Server is
shut down, console automatically dies.
console Version 4.0 -- 1/15/89 8
______________________________________________________________________
o Since the console terminal prints prompts and messages for the
operator, you may want to run it on a terminal located close to
the tape unit.
This terminal must be attached to the machine on which
SQL Server was started.
o Most of the console program's messages are self-explanatory.
To abort a DUMP or LOAD to tape, type ``n'' in response to any
prompt to mount a new tape.
o If two tapes (i.e., two DUMPs/LOADs) are being used at once,
only one ``console'' is needed. The program will print mes-
sages one at a time, waiting for a response before going to the
next prompt. For this reason, the messages include the name of
the physical drive to which they pertain.
o Make sure that the tape you are using is not write-protected.