does anyone know how I can make an automatic backup of files to a tape drive under UNIX. I have so many commands, I don't know which goes where. I have commands for the task scheduler, Cron and other unix commands. Please help. Very Urgent. Thanks (3 Replies)
I am trying to install a tape drive on this system (Unix 7.1.1)
where will I start?
1. Do I need to load the driver on the on board scsi? How?
2. Is there a driver for the tape drive itself?
Things done:
1. Terminated the device on the controller board. (4 Replies)
I'm attempting to read a tape in a 4mm drive (AIX 4.3) using the following command...
tar tvf /dev/rmt0
...and I keep getting the following error message:
tar: 0511-193 An error occurred while reading from the media.
There is not enough memory available now.
I've googled this error... (2 Replies)
I replaced a HP Superstore Dat 40 with another HP Superstore Dat 40, but my backupedge software keeps putting up error code 1 (device not found) I have tried reinstaling the drive as DAT Alad stp 0 6 0 0. I'm not a computer expert but willing to have a go. I went into Backupedge to try and format a... (2 Replies)
Dear all,
I have ultriam3 tape. It is connected my LPAR. I have that the Sl.Nos. and slot number. but run the cfmgr i am not getting the tape drive.
I have fired the command lsdev -Cc tape but no reply.
how will i configure the tape in LPAR?
Please suggest. It is very urgent. (3 Replies)
Hi all,
I have solaris 10 sparc running and working very well
but i have problem with external SCSI tape drive DAT 72 problem
it seems to me the tape drive is manufactured by SUN microsystems
when i ran ls -l /dev/rmt/0
it reveals the following output
bash-3.00# mt -f /dev/rmt/0... (2 Replies)
Hi,
i installed a unix tape drive on my alphaserver. when i use a mt command it tells me there is no tape or device.
I have used the hardware manager and it shows the tape is present.
Can anyone help me understand why it cannot pick up the tape as a default? (1 Reply)
Hi,
I'm at AIX 5.3.
My EOD program is giving following error while writing to tape:
Can't write output
cpio: Media Surface error
Failed on Shell-script
cd /; cpio -ocB 2 >> /autoline/misc/logs/bk.CopyToTape < /autoline/work/BACKUP.01022 1>/dev/rm0
I have tried with several new tapes,... (2 Replies)
I've had a scsi hard drive, scsi tape drive, and cd rom working off an adaptec 29160 controller. Everything worked great until a few days ago. I begin getting tar format errors (running sco 5.0.6) on the tape drive and occasionally the entire system would hang up while trying to access data on... (0 Replies)
Hi,
The problem I have is I want to restore my AIX machine. I have created a mksysb tape from my tape drive rmt0 and I changed the bootlist using this command "bootlist -m normal rmt0 hdisk0".
However, when I display the bootlist "bootlist -om normal", it shows '-' hdisk0. I googled and... (2 Replies)
Discussion started by: AixNoob87
2 Replies
LEARN ABOUT DEBIAN
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)