Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

butc_logs(5) [osf1 man page]

BUTC_LOGS(5)							AFS File Reference						      BUTC_LOGS(5)

NAME
butc_logs - Message logs from the Tape Coordinator process DESCRIPTION
The Backup System Tape Coordinator (butc) process generates two log files per device, one for error messages and one for actions. Error Message Log The TE_device_name file logs error messages generated by the Backup System Tape Coordinator that controls the tape device or backup data file indicated by device_name. As the Tape Coordinator initializes, it creates the file in ASCII format in the /var/lib/openafs/backup directory. If there is an existing file, the Tape Coordinator renames it to TE_device_name.old>, overwriting the existing TE_device_name.old> file if it exists. For a tape device, the Tape Coordinator derives the variable device_name portion of the filename from the device pathname listed in the local /var/lib/openafs/backup/tapeconfig file, by stripping off the initial "/dev/" string and replacing any other slashes in the name with underscores. For example, the filename for a device called /dev/rmt/4m is TE_rmt_4m. Similarly, for a backup data file the Tape Coordinator strips off the initial slash ("/") and replaces any other slashes in the name with underscores. For example, the filename for a backup data file called /var/tmp/FILE is TE_var_tmp_FILE. The messages in the file describe the error and warning conditions the Tape Coordinator encounters as it operates. For instance, a message can list the volumes that are inaccessible during a dump operation, or warn that the Tape Coordinator is overwriting a tape or backup data file. The messages also appear in the /var/lib/openafs/backup/TL_device_name file, which traces most of the Tape Coordinator's actions. Action Log The TL_device_name file logs the actions performed by the Backup System Tape Coordinator that controls the tape device or backup data file indicated by device_name. It also records the same error and warning messages written to the TE_device_name file. As the Tape Coordinator initializes, it creates the file in ASCII format in the /var/lib/openafs/backup directory. If there is an existing file, the Tape Coordinator renames it to TL_device_name.old, overwriting the existing TL_device_name.old file if it exists. For a tape device, the Tape Coordinator derives the variable device_name portion of the filename from the device pathname listed in the local /var/lib/openafs/backup/tapeconfig file, by stripping off the initial "/dev/" string and replacing any other slashes in the name with underscores. For example, the filename for a device called /dev/rmt/4m is TL_rmt_4m. Similarly, for a backup data file the Tape Coordinator strips off the initial slash ("/") and replaces any other slashes in the name with underscores. For example, the filename for a backup data file called /var/tmp/FILE is TL_var_tmp_FILE. SEE ALSO
tapeconfig(5), butc(8) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 BUTC_LOGS(5)

Check Out this Related Man Page

BACKUP_DELHOST(8)					       AFS Command Reference						 BACKUP_DELHOST(8)

NAME
backup_delhost - Deletes a Tape Coordinator entry from the Backup Database SYNOPSIS
backup delhost -tapehost <tape machine name> [-portoffset <TC port offset>] [-localauth] [-cell <cell name>] [-help] backup delh -t <tape machine name> [-p <TC port offset>] [-l] [-c <cell name>] [-h] DESCRIPTION
The backup delhost command deletes the indicated Tape Coordinator entry from the Backup Database. It is then impossible to submit backup operations to that Tape Coordinator, even if it is still running. To keep configuration information consistent, also remove the corresponding entry from the /var/lib/openafs/backup/tapeconfig file on the Tape Coordinator machine. To list the Tape Coordinator machines and port offsets defined in the Backup Database, issue the backup listhosts command. OPTIONS
-tapehost <tape machine name> Specifies the hostname of the machine housing the Tape Coordinator to delete. -portoffset <TC port offset> Specifies the port offset number of the Tape Coordinator to delete. If omitted, it defaults to 0. If provided, it is an integer between 0 (zero) and 58510, and must match the port offset number assigned to the same combination of Tape Coordinator and tape device or file in the /var/lib/openafs/backup/tapeconfig file on the Tape Coordinator machine indicated by the -tapehost argument. -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more details, see backup(8). -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8). -help Prints the online help for this command. All other valid options are ignored. EXAMPLES
The following command deletes the Backup Database entry for the Tape Coordinator with port offset 2 on the Tape Coordinator machine "backup3.abc.com": % backup delhost -tapehost backup3.abc.com -portoffset 2 PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. SEE ALSO
backup(8), backup_addhost(8), backup_listhosts(8) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 BACKUP_DELHOST(8)
Man Page