Home
AdministeringIn addition to administering the database server, you can tune performance, replicate data, and archive data.
Backup and Restore GuideThe HCL OneDB™ Backup and Restore Guide describes how to use the HCL® OneDB® ON-Bar and ontape utilities to back up and restore database server data. These utilities enable you to recover your databases after data is lost or becomes corrupted due to hardware or software failure or accident.
ontape backup and restore system
Configure ontapeYou configure the ontape utility by setting configuration parameters for backups of storage spaces and logical logs.
Set configuration parameters for the ontape utilityThe ontape utility uses eight configuration parameters in the onconfig file. Two of the configuration parameters specify filter programs for transforming data during backup and restore; the other six are used to create storage-space and logical-log backups.
Set the tape-device parameters
Specify /dev/null for a tape deviceA best practice is to not use /dev/null as the device when backing up. However, if you decide that you do not need to recover transactions from the logical log, you can specify /dev/null as a tape device for logical-log backups

Specify /dev/null for a tape device

A best practice is to not use /dev/null as the device when backing up. However, if you decide that you do not need to recover transactions from the logical log, you can specify /dev/null as a tape device for logical-log backups

When you specify /dev/null as a backup tape device, you can avoid the overhead of a level-0 backup that is required after some operations, such as changing the logging status of a database. Obviously, you cannot restore storage spaces from a backup to /dev/null.

When you specify the tape device as /dev/null, block size and tape size are ignored. If you set the LTAPEDEV configuration parameter either to or from /dev/null, you must restart the database server for the new setting to take effect.

Important: When you set the LTAPEDEV configuration parameter to /dev/null, the database server marks the logical-log files as backed up as soon as they become full, effectively discarding logical-log information.