Notifies the Backup Server that the operator performed the requested volume handling during a dump or load.
sp_volchanged session_id, devname, action [, fname [, vname]]
identifies the Backup Server session that requested the volume change. Use the @session_id parameter specified in the Backup Server’s volume change request.
is the device on which a new volume was mounted. Use the @devname parameter specified in the Backup Server’s volume change request. If the Backup Server is not located on the same machine as the Adaptive Server, use the form:
device at backup_server_name
indicates whether the Backup Server should abort, proceed with, or retry the dump or load.
is the file to be loaded. If you do not specify a file name with sp_volchanged, the Backup Server loads the file = filename parameter of the load command. If neither sp_volchanged nor the load command specifies which file to load, the Backup Server loads the first file on the tape.
is the volume name that appears in the ANSI tape label. The Backup Server writes the volume name in the ANSI tape label when overwriting an existing dump, dumping to a brand new tape, or dumping to a tape whose contents are not recognizable. If you do not specify a vname with sp_volchanged, the Backup Server uses the dumpvolume value specified in the dump command. If neither sp_volchanged nor the dump command specifies a volume name, the Backup Server leaves the name field of the ANSI tape label blank.
During loads, the Backup Server uses the vname to confirm that the correct tape has been mounted. If you do not specify a vname with sp_volchanged, the Backup Server uses the dumpvolume specified in the load command. If neither sp_volchanged nor the load command specifies a volume name, the Backup Server does not check the name field of the ANSI tape label before loading the dump.
The operator changes the tape, then issues the command:
sp_volchanged 8, "/dev/nrmt4", RETRY
The following message from Backup Server indicates that a mounted tape’s expiration date has not been reached:
Backup Server: 4.49.1.1: OPERATOR: Volume to be overwritten on
'/dev/rmt4' has not expired: creation date on this volume is Sunday, Nov. 15, 1992, expiration date is Wednesday, Nov. 25, 1992.
Backup Server: 4.78.1.1: EXECUTE sp_volchanged
@session_id = 8,
@devname = '/auto/remote/pubs3/SERV/Masters/testdump',
@action = { 'PROCEED' | 'RETRY' | 'ABORT' }
If the Backup Server detects a problem with the currently mounted volume, it requests a volume change:
On OpenVMS systems – the Backup Server sends volume change messages to the operator terminal on the machine on which it is running. Use the with notify = client option of the dump or load command to route other Backup Server messages to the terminal session on which the dump or load request initiated.
On UNIX systems – the Backup Server sends messages to the client that initiated the dump or load request. Use the with notify = operator_console option of the dump or load command to route messages to the terminal where the Backup Server was started.
After mounting another volume, the operator executes sp_volchanged from any Adaptive Server that can communicate with the Backup Server performing the dump or load. The operator does not have to log into the Adaptive Server on which the dump or load originated.
On OpenVMS systems – the operating system—not the Backup Server—requests a volume change when it detects the end of a volume or when the specified drive is offline. The operator uses the OpenVMS REPLY command to reply to these messages.
On UNIX systems – the Backup Server requests a volume change when the tape capacity has been reached. The operator mounts another tape and executes sp_volchanged. Table 8-22 illustrates this process.
Sequence |
Operator, using isql |
Adaptive Server |
Backup Server |
|---|---|---|---|
1 |
|
||
2 |
|
||
3 |
|
||
4 |
|
||
5 |
|
||
6 |
|
||
7 |
|
||
8 |
|
|
Any user can execute sp_volchanged.
Commands dump database, dump transaction, load database, load transaction
