Does anyone know how to move tapes within a library to the load port using NetBackup? robtest will not work with NetBackup running, and I would like to have a script move the tapes to be sent offsite to the load port for easier removal. (2 Replies)
:confused:
Hello!!
I am a new UNIX user, and I need to back up some files, I have some old ones and I have been trying to delete the old information with 'mt erase' but I don't be sure if it works, and 'mt resert' but the it gave a message suggesting me to use 'scsiha -r' (but the last one... (1 Reply)
Hey Folks,
Can somebody please explain what the crack is with this problem.
I have a backup folder in /var which contains 4 rsync'd server folders:
server08
server15
server16
server18
They all contain the etc folder from the server, and other important data I need to backup.
To... (2 Replies)
I am trying to find a way of copying a system DAT tape onto another DAT tape for security reasons. I have tried searching the net for commands but so far I have been unsuccessful. (2 Replies)
Hi Community,
I've a V440 Sun Server with 2 device tape of 72GB. I have to backup a folder of 80 GB, so I have to use 2 tapes of 72GB (144 GB);
If I use vxdump command which are the options that I have to use?
When the first tape finishes does the system stop the backup?
Please help me... (1 Reply)
I have a B180L controller running HP-UX 10.2 with an internal DDS2 tape drive and an external Surestore DDS (24gb) tape drive. I want to make duplicate copies of ignite tapes from one tape drive to another. What is the best way to do this? (1 Reply)
Discussion started by: garyb
1 Replies
LEARN ABOUT XFREE86
butc_logs
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 ALSOtapeconfig(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)