Air Cleaner User Manual

Note: The tapeutil command is a sample program that come with the IBM
Atape.driver file set. This is the device driver that controls IBM Magstar
®
tape devices. This is not a SysBack command.
#!/bin/ksh
DEVICE=$1
HOST=$2
TAPE=$3
case $TAPE in
2) tapeutil -f /dev/smc0 move 23 10
tapeutil -f /dev/smc0 move 11 23
;;
3) tapeutil -f /dev/smc0 move 23 11
tapeutil -f /dev/smc0 move 12 23
;;
4) tapeutil -f /dev/smc0 move 23 12
tapeutil -f /dev/smc0 move 13 23
;;
5) tapeutil -f /dev/smc0 move 23 13
tapeutil -f /dev/smc0 move 14 23
;;
esac
When performing remote backups, the user who will be running your program or
script is the sbnet user. You will need to accommodate this accordingly if there are
commands in your program or script that require root user authority. Also, the
read and execute permissions on your program or script must be set to allow the
sbnet user to run it.
Error Handling Settings
This section provides options for controlling the way read errors are handled when
reading from SysBack backup media. Although SysBack itself provides a reliable
backup, the media on which the backup is placed can sometimes become corrupt.
The fields have the following meanings:
Number of data read errors before read failure
Default=50. When SysBack encounters a read error from the media device
driver, by default, it attempts to read up to the number of times specified
in the Maximum number of retries on read errors field. If SysBack is
unable to read the data, a read error is produced, and SysBack either skips
the missing data entirely or pads the missing data with NULL bytes, as
defined by the Pad missing data with NULLs after sync errors field.
This option enables you to specify the maximum number of read errors
that are produced before the backup fails. Specify any number up to 32768
in this field or use a zero (0) to indicate that the reading fails after the first
read error.
Number of data sync errors before read failure
Default=50. The backup is read for each buffer, defined by the buffer size
of the backup. At the beginning of each buffer is a special key that ensures
that the data is being read at the correct point. A “data sync” error occurs
when the key is not encountered or the key has an incorrect sequence
number.
When a sync error occurs, SysBack either skips the missing data altogether
or pad the missing data with NULL bytes, as defined by the Pad missing
data with NULLs after sync errors field.
Chapter 16. Utilities 16-25