This section describes the volume change prompts that appear while you are dumping a database or transaction log. Each prompt includes the possible operator actions and the appropriate sp_volchanged response.
Mount the next volume to search.
When appending a dump to an existing volume, the Backup Server issues this message if it cannot find the end-of-file mark.
The operator can |
By replying |
|---|---|
Abort the dump |
sp_volchanged session_id, devname, abort |
Mount a new volume and proceed with the dump |
sp_volchanged session_id, devname, proceed [, fname [, vname]] |
Mount the next volume to write.
The Backup Server issues this message when it reaches the end of the tape. This occurs when it detects the end-of-tape mark, dumps the number of kilobytes specified by the capacity parameter of the dump command, or dumps the high value specified for the device in the sysdevices system table.
The operator can |
By replying |
|---|---|
Abort the dump |
sp_volchanged session_id, devname, abort |
Mount the next volume and proceed with the dump |
sp_volchanged session_id, devname, proceed[, fname [, vname]] |
Volume on device devname has restricted
access (code access_code).
Dumps that specify the init option overwrite any existing contents of the tape. Backup Server issues this message if you try to dump to a tape with ANSI access restrictions without specifying the init option.
The operator can |
By replying |
|---|---|
Abort the dump |
sp_volchanged session_id, devname, abort |
Mount another volume and retry the dump |
sp_volchanged session_id, devname, retry [, fname [, vname]] |
Proceed with the dump, overwriting any existing contents |
sp_volchanged session_id, devname, proceed[, fname [, vname]] |
Volume on device devname is expired
and will be overwritten.
Dumps that specify the init option overwrite any existing contents of the tape. During dumps to single-file media, Backup Server issues this message if you have not specified the init option and the tape contains a dump whose expiration date has passed.
The operator can |
By replying |
|---|---|
Abort the dump |
sp_volchanged session_id, devname, abort |
Mount another volume and retry the dump |
sp_volchanged session_id, session_id, retry [, session_id [, session_id]] |
Proceed with the dump, overwriting any existing contents |
sp_volchanged session_id, session_id, proceed[, session_id [, session_id]] |
Volume to be overwritten on ’devname’ has
not expired: creation date on this volume is creation_date, expiration
date is expiration_date.
On single-file media, the Backup Server checks the expiration date of any existing dump unless you specify the init option. The Backup Server issues this message if the dump has not yet expired.
The operator can |
By replying |
|---|---|
Abort the dump |
sp_volchanged session_id, session_id, abort |
Mount another volume and retry the dump |
sp_volchanged session_id, session_id, retry [, session_id [, session_id]] |
Proceed with the dump, overwriting any existing contents |
sp_volchanged session_id, session_id, proceed [, session_id [, session_id]] |
Volume to be overwritten on ’devname’ has
unrecognized label data.
Dumps that specify the init option overwrite any existing contents of the tape. Backup Server issues this message if you try to dump to a new tape or a tape with non-Sybase data without specifying the init option.
The operator can |
By replying |
|---|---|
Abort the dump |
sp_volchanged session_id, session_id, abort |
Mount another volume and retry the dump |
sp_volchanged session_id, session_id, retry [, session_id [, session_id]] |
Proceed with the dump, overwriting any existing contents |
sp_volchanged session_id, session_id, proceed [, session_id [, session_id]] |
