Reading tape and redirecting output to a file. In this case, the operating system showed that the tape itself is damaged.
This doesn't need to be the case. If the tape was written with another blocksize (default blocksize depend on hardware, so we do not know what yours is) then trying to read will result in a "tape damaged" - in fact it is, in a way, because it was formatted differently.
Hi,
I' using a sun solaris server, I would like to known if there is the possibility to control how many space is free on a tape and how I can delete a single file on a tape.
Thanks
DOMENICO (3 Replies)
Hi there: I'm new here
Can anyone help me:
I have DS15 Alpha server : Unix 5.1B
Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit.
What is the exact comman to mount the DLTape IV??
How do i make backuo @ copy file to the tape?
Thanx to all (0 Replies)
I am having my 14 Aix 5.3 servers on bladecenters connected with my Tape Library.
I had a backup scheduled on tape library but after taking backup successfully,
Now,
Question 1:-
I wanted to restore backup but tape library could not recognize the tape and I get I/O error in TSM. I think it... (0 Replies)
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Hi all,
I would like to know what would happen if the tape (media) is not placed on the drive and a tar command is executed to backup on the tape.
My problem is that tar command hanged for multiple days instead of throwing the error,
Is it valid behaviour?
I was unable to test the... (4 Replies)
hello,
I am facing this problem when trying to prepare AIX 5.3 for Veritas Backup:
Veritas Software is not able to communicate properly with our tape library
When we tried to run these commands here's the output
# cfgmgr -l fscsi0
# cfgmgr -l fscsi2
# cfgmgr -l fscsi1
cfgmgr:... (3 Replies)
I could not delete the tape in AIX
This is the steps which i used .. but still it did not deleted .. !
server/root>lscfg -l rmt0
rmt0 U789D.001.DQD298Y-P1-C5-T2-L6-L0 Other SCSI Tape Drive
server/root>
server/root>
server/root>lsdev -l rmt0 -F parent
scsi3... (3 Replies)
Hello,
We need to make a copy of a backup tape, using the 2 tape recorders in IBM 3582 Tape Library
We tried tu use "tcopy", it seems to work fine (no error messages) but we aren't sure if we can rely on it.
my question is how to check if the copy succeded or not, but i also want to know... (3 Replies)
I am using a 4mm tape to backup my Unix system. However, I wanted to make a copy all of the files and archive headers (or just the archive headers if that's possible) created on one of my tapes to another 4mm tape. I only have one tape drive. Is there a command that will complete such task? ... (1 Reply)
Discussion started by: acoco
1 Replies
LEARN ABOUT REDHAT
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 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)