You display the properties of the specified backup template.
See also:
Concepts of the Database System, Backup Templates and Data Carriers
You have the server authorization Backup or DBInfoRead.
medium_get <medium_name>
OK
<medium_name> <location> <type> <backup_type> <size> <block_size> <overwrite> <autoldr> <oscmd> <date_created> <date_modified> <tool_type>
Values for the Reply Fields
Value |
Description |
<medium_name> |
Name of the backup template; may comprise a group name and a member name, separated by a slash. These are separated by a slash. |
<location> |
Name of the device/file with which it can be addressed through operating system functions. |
<type> |
Type of the backup template. Possible values are: TAPE | FILE | NO-REWIND | PIPE | AUTOLOADER | UNKNOWN |
<backup_type> |
Type of backup for which the backup template is to be used. Possible values are: DATA | PAGES | LOG |
<size> |
Maximum number of pages that can be written to the data carrier. |
<block_size> |
Number of pages transferred when the data carrier is accessed. |
<overwrite> |
Indicates whether the data carrier can be overwritten (for the FILE template type only). Possible values are: NO | YES |
<autoldr> |
Indicates whether the device changes the
data carrier automatically. Possible values are: |
<oscmd> |
Operating system command to be executed before saving to a succeeding data carrier (backup_replace) or restoring a succeeding data carrier (recover_replace). |
<date_created> |
Date on which the backup template was created |
<date_modified> |
Date on which the backup template was changed |
<tool_type> |
Type of the backup tool. Possible values are: NONE | BACK | NSR | TSM NONE: No automatic
backup tool is used |
In the event of errors, see Reply Format.