03-24-2008
lsdev -Cc tape
rmt0 Available 3A-08-00-6,0 SCSI 4mm Tape Drive
rmt1 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt2 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt3 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt4 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt5 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt6 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt7 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt8 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt9 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt10 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt11 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt12 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt13 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt14 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt15 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt16 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt17 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt18 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt19 Available 4J-08-01 LTO Ultrium Tape Drive (FCP)
rmt20 Available 4J-08-01 LTO Ultrium Tape Drive (FCP
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I find if a server contains a DDS3 or a DDS2 drive remotely ?
I checked in SMIT and I noticed the description field according to tape drives, but is there another more thorough way?
Thanks,
Luke (0 Replies)
Discussion started by: Skywlkr235
0 Replies
2. Solaris
Hi,
Can you please help me to locate tape drives on Sun Server and the capacity of the tape drive.
I am managing a Sun 4u server.
Need this urgently.
Regards,
Vivek (2 Replies)
Discussion started by: vivek_scv
2 Replies
3. BSD
Hello,
I have a little problem with backup & restoring files from tape drive.
I am adding 3 directories to my tape, and it is OK:
hades# tar -cvf /dev/nsa0 test test1 restore
a test
a test/level1
a test/myharddisk.img
a test1
a test1/level1
a test1/myharddisk.img
a test1/test.img
a... (1 Reply)
Discussion started by: d3m00n
1 Replies
4. UNIX for Advanced & Expert Users
We have a new i500 and have 4 TLO4 drives which are connected directly to 2 FC cards on the host. The host can communicate with the autochanger through whichever drive that is set as control path.
When I run inquire, all 4 drives are listed but auto changer doesn't show up. Does anyone know... (1 Reply)
Discussion started by: tecky
1 Replies
5. Filesystems, Disks and Memory
Hi,
I am a abit new in AIX system administration field. I want to gather knowledge about backup techniques. As per my knowledge we use Tape archives for taking backups. Can anyone pls explain me in detail abt tape archive? Whether these tape archives come along with the systems or we have to... (1 Reply)
Discussion started by: forumsrahul
1 Replies
6. Solaris
I have a server/domain on a m5000 running Solaris 10. It is part of a cluster.
The other cluster member sees tape drives, but this one does not.
It is zoned correctly, and I can see the drives are binded in lputil.
The st.conf, and devlink.tab are identical.
ST.CONF: -
#
# Copyright... (1 Reply)
Discussion started by: pfwhufc
1 Replies
7. Solaris
I have an HP Proliant DL380 with Intel Processors that I recently loaded Solaris 10 with latest patches on it. I'm trying to do a ufsdump to an HP DAT 40 tape drive via SCSI, but I can't get it to do anything because /dev/rmt is empty. I've tried the following with luck:
touch /reconfigure,... (7 Replies)
Discussion started by: cvaughn
7 Replies
8. Solaris
hi,
i am using Solaris 8 on a sparc box and already have 4 tape drives in a backup libaray attached to my unix server. we have recently added 2 new tape drives to the libaray and now want to get unix to see them. have it working in windows.
how do i scan for new hardware and add theses new... (5 Replies)
Discussion started by: dshakey
5 Replies
9. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 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)