You create a new backup medium or change the data for a backup medium that already exists.
The properties of the backup medium defined in this way are stored in the log file dbm.mdf of the Database Manager.
The directory in which you want to create the backup medium must already exist. The backup medium is not created physically until it is first used for a backup.
You must have the server authorization Backup.
medium_put <medium_name> <location> <type> <backup_type> [<size>] [<block_size>] [<overwrite>] [<autoloader>] [<os_command>] [<tool_type>]
Options
Option |
Description |
<medium_name> |
The name of the backup medium may comprise a group name and a member name. These are separated by an oblique. <medium_name> ::= [<group_name>/]<member_name> To create a group of parallel back media, execute the DBM command several times over. To assign the media to the same group, always enter the same <group_name>, with a different <member_name> for each medium. |
<location> |
The name of the device/file with which it can be addressed through operating system functions. The system assigns version numbers to version files for log backups of the type FILE. Note the standards for different types (<type>) of backup media under different operating systems: Standards for backup media of type PIPE on UNIX: You can select any path you want. If you enter a relative path, the backup medium is stored in the working directory of the database instance ([<path>/]<file_name>). on Microsoft Windows: The path must comply with this convention: \\.\pipe\<pipe_name>. Standards for backup media of type FILE on UNIX: You can enter an absolute or relative path. An absolute path must start with a slash (/). If you enter a relative path, it is interpreted as relative to the working directory of the database instance. on Microsoft Windows: You must enter an absolute path as follows: \\<computer_name>\<share>\[<path>\]<file_name> or with the drive: <drive>:\[<path>]\<file_name> If you enter a relative path, it is interpreted as relative to the working directory of the database instance.
Standards for backup media of type TAPE on UNIX: You must enter an absolute path. on Microsoft Windows: The path must comply with this convention: \\.\tape<running_number>.
Standards for the backup tool NSR: Enter an absolute pathname. This must be identical for both the backup and restore operations. Note that parts of the path name that represent only links are replaced with the actual directory or file name by NetWorker. |
<type> |
Type of the Backup Medium Possible values for backups are: TAPE | FILE | PIPE | UNKNOWN Possible values for log backups are: FILE | PIPE | UNKNOWN Specify TAPE for backups to a non-rewindable tape, FILE for backups to a file, and PIPE for backups to a pipe. If you enter one of these media types, the system checks that your entries are correct. If you want to avoid this check, enter the type UNKNOWN. Note, however, that log backups are only possible to files and pipes. Otherwise, you receive an error message when you save. The system default is UNKNOWN. |
<backup_type> |
Backup type for which the backup medium is to be used: Possible values are: DATA | PAGES | LOG | AUTO Enter DATA for a complete backup, PAGES for an incremental backup, LOG for an interactive log backup and AUTO for an automatic log backup. Note: There can be only one backup medium of type AUTO. If a backup medium for this backup type already exists and you define another medium of type AUTO, then the system changes the backup type of the existing medium to the backup type LOG. |
<size> |
Maximum number of pages which can be written to the backup medium. The default value of the system is 0, that is, the size of the medium is not limited. The system will keep backing up to this medium until either the backup is complete, or the operating system does not allow further backups to this medium because it is full. If this happens, you receive an error message and can then continue the backup using another backup medium. |
<block_size> |
Number of
pages transferred when the medium is accessed. This value is only evaluated
for the media type TAPE. |
<overwrite> |
Obligatory
only for the media type FILE and only for
data backups. It defines the behavior if the file already exists. YES | NO If you enter YES and the file already exists, it is overwritten by the new backup. If you enter NO and the file already exists, the backup fails. This entry is not interpreted for log backups. The system default is NO. |
<autoloader> |
Details of whether the device changes the medium automatically: only relevant on Microsoft Windows Possible values are: YES | NO The system default is NO. |
<os_command> |
Operating system command to be executed before saving to a continuation medium (backup_replace) or restoring a continuation medium (recover_replace). |
<tool_type> |
Backup tool to be used. Possible values are: NONE: no backup
tool is used. If you use UNIX and you enter the value NONE with PIPE as the <type>, the pipe must be created before the backup process starts. If you use Microsoft Windows, the pipe must not yet exist. If you enter a value other than NONE, you must enter 0 for <type> PIPE and for <size>. If you use either UNIX or Microsoft Windows, the pipe must not exist before the backup process begins. For NSR, note the additional information listed under <location>. The system default is NONE. |
OK
In the event of errors, see Reply Format