10 More Discussions You Might Find Interesting
1. AIX
Good day!
Need help in checking my AIX 7.1 box.
After we have finished zoning our TS3200 and TS3310 tape libraries, we installed the Atape driver,
# lslpp -L |grep tape
Atape.driver 11.7.7.0 C F IBM AIX Enhanced Tape and
devices.fcp.tape.rte 7.1.3.15 C ... (0 Replies)
Discussion started by: alainken3
0 Replies
2. AIX
I am trying to use this command to eject the tape
mt -f /dev/rmt/0 unload
but it gives me error
mt -f /dev/rmt/0 unload
mt: 0511-575 unload is not a recognized subcommand.
Usage: mt Subcommand
Valid subcommands are:
weof
eof
fsf
bsf
... (5 Replies)
Discussion started by: filosophizer
5 Replies
3. Solaris
hi all
please tell me how can i connect SunFire V240 to a SL24 tape library.
is there any slots which i can connect?
can i connect through SCSI port? (1 Reply)
Discussion started by: nikhil kasar
1 Replies
4. Solaris
I am a solaris noob. I have a SPARC enterprise T5120 server which i am trying to connect 1 StorEdge 3300 and 1 StorageWorks MSL2024 tape library. Each device is connecting to 1 pci card on the server. I can see the array when i run the format command but i can't seem to detect the tape library.
... (2 Replies)
Discussion started by: M_Owen
2 Replies
5. AIX
Hi all,
I have a problem here
root@host1 / # lsdev -Cc tape
rmt0 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Defined 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Defined 07-00-02 IBM 3573 Tape Medium Changer (FCP)
root@host1 / # cfgmgr -l fcs2
Method error... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
6. AIX
Hi all,
I'm having a problem here my environment as follows.
AIX 5.3 TL 10 running on a P6 p520 sever with 3 fibre channel cards and Tivoli Storage Manager TSM 5.4 and TS3200 Tape Library with 2 drives and 2 media changers.
My problem as follows smc1 doesn't show up , I ran cfgmgr multiple... (6 Replies)
Discussion started by: h@foorsa.biz
6 Replies
7. AIX
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)
Discussion started by: filosophizer
3 Replies
8. 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
9. 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
10. HP-UX
Hi All,
Hoping that you'll be able to help out on - I've a problem occuring in our backups that's driving me up the wall.
I've got an HP-UX Visualise 6500 as below:
================================
root # uname -a
HP-UX <NAME> B.11.00 A 9000/785 2005956095 two-user license... (2 Replies)
Discussion started by: geralex
2 Replies
LEARN ABOUT HPUX
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)