Kbase 17211: Offline Backup to Tape Device Without VTA's enabled
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Offline Backup to Tape Device Without VTA's enabled
Running the probackup utility in version 7 of Progress on VMS can
yield some unexpected results. Instead of backing up the database to
a specified tape device, we will write the backup to a file which
automatically takes on the name of the specified tape device. The
actual syntax for the backup is PROGRESS/BACKUP db-name device-name.
The vms syntax to check the status of the device is show dev m. In
this case, the status will usually come up as online, which means the
device is ready to be written to. When the backup is attempted, the
file with the name of the device is created and the following message
may appear.
** Cannot find or open file <file-name>, errno = <number>. (43) P
In this case the errno was 9 which is an access violation. This may
lead you down the path of a permissions problem or the use of a wrong
device name. However, the culprit in this case is virtual terminals,
which need to be enabled in order for the backup to complete
successfully. The actual syntax of the errno=9 is invalid lexical
name. The error immediately following the 43 should be
Backup failed. (3741).
%PROGRESS-F-BADEXIT, Abnormal termination has occurred.
The <file-name> in the 43 should be the specified tape device name.
The interesting part of this is that a full vms system backup to the
same device is successful. This is because Progress requires the use
of Virtual Terminals and here's why. When a client comes in as a VTA,
this allows Progress to disconnect the client smoothly as the process
is alive for a certain amount of time (TTY-TIMEOUT).If the client
comes in on RTAn line, Progress performs $GETDVI on all clients and
if we cannot find the RTAn client we will treat the PID as disappeared
which is not desireable.(excerpt from kb15287) See this kbase for more
details on VTA's.
(*this is also true for TNAn clients which are UCX connections)
Other useful knowledgebase entries:
13011 Alternative remote connection methods when VTA's are enabled
15997 How to turn on Virtual Terminals VTAs for UCX ( from DEC )
13668 CTRL-Y not recommended to end session unless using VTAs
12783 Access violations and S/E 49 VMS servers Virtual Terminals
How to access errno listings in vms:
write sys$output F$message("message number")
or $ exit message# / $ exit %Xmessage# if the number is in hex
References to written documentation:
System Administration Guide 11-36 through 11-41.
Progress Software Technical Support Note # 17211