01-29-2009
Configuration issue with Tape Library in Solaris 10
Env:
Server : Sparc Ultra-80
OS: Solaris 10
Direct SCSI connection to Library. Terminator connected at the Tape End.
Problem: Unable to see any device file related to Robotic /dev/rsst0.
Unable to see any device file /dev/rmt.
------------
Messages while the machine boots
sst0: No response from target 5, lun 0
/dev/rdsk/c0t0d0s5 is clean
/dev/rdsk/c0t0d0s6 is clean
sst1: No response from target 5, lun 0
sst2: No response from target 5, lun 0
Any ideas ?
thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I picked up this library but I cannot get the device to actuate.
How do I make this work with Solaris 7? (2 Replies)
Discussion started by: n9ninchd
2 Replies
2. Solaris
I seem to have an issue with Apache configurationon our Sun solaris Server.
Since there are 2 my_app instances running in parallel, the perl modules in my_app_perl_libs are getting shared
between them, even though they are in different directories (/u01/my_app and /u01/my_app8).
This is because... (1 Reply)
Discussion started by: rahulrathod
1 Replies
3. Solaris
I have been working on this one for a few days. Any help/advice would be greatly appreciated.
Hardware
Machine: Sun Blade 2000
Tape Drives: HP Ultrium LTO2 002 (x2) (Inside an L40)
Software
OS: Solaris 8
st.conf uncommented lines:
probe-scsi-all reports both drives.
/dev/rmt is... (2 Replies)
Discussion started by: lucesean
2 Replies
4. AIX
Hello every body, I have one tape library 3583 but I can't install this some body have ben installed??
when I tray to install it, the output is the next:
Method error (/etc/methods/cfgAtape):
0514-022 The specified connection is not valid.
some Idea??
thanks
greetings (5 Replies)
Discussion started by: xanatos
5 Replies
5. AIX
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)
Discussion started by: Shrek
0 Replies
6. Solaris
Hi all ,
Anybody has an installation manual for Sun StorageTek C4 tape library . i am trying to do the installation on a Sun Fire V245 .
Thanks a million
cheers
ppass (4 Replies)
Discussion started by: ppass
4 Replies
7. Solaris
Hello,
i am trying to get following configuration up running, but get no access to the library roboter.
Server: SunOS 5.10 Generic_138889-03 i86pc i386 i86pc
DELL TL-2000: 1 Tape: IBM ULT3580-HH4 and Robot: 3573-TL,
connected via ISCSI Bridge (build into the TL)
... (1 Reply)
Discussion started by: austin73
1 Replies
8. SCO
Dear All,
I have a tape drive which has worked for offer 3yrs properly on SCO Openserver Release = 3.2v5.0.5. I tried to clean it all invain. I did a fresh installation of unix of the same OS and did the configuration still didn't bear fruits. The tape is a scsi and the configuration is as... (4 Replies)
Discussion started by: njoroge
4 Replies
9. Emergency UNIX and Linux Support
Hi All,
We have patched our solaris 10 u4 server with lustarter patch in order to get it prepared for solaris live upgrade.The patch installation went pretty fine and we did reboot the server after patching.But after patching we have noticed O.S is not able to detect tape library.Not sure what... (22 Replies)
Discussion started by: sahil_shine
22 Replies
10. Solaris
Hi,
Our environment is SUN Solaris. We have purchased HP EML 103e tape library. Can you please let me know do I need to install any Driver of newly added Tape Library to see from the Solaris Host? or how can i see the tape library from my Solaris hosts.
Thanks,
Hassan (0 Replies)
Discussion started by: M_Hassan
0 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)