AIX doesn't detect smc1 media changer in ts3200 tape library
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 times , rebooted the server and rebooted the tape Library with no luck untill now.
Code:
root@host/ # lsdev -Cc tape
rmt0 Available 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Available 07-00-02 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Available 07-00-02 IBM 3573 Tape Medium Changer (FCP)
I ran tests via taputil tool it seems everything is okay except that smc1 show up
Code:
root@host/ # /usr/bin/tapeutil -f /dev/rmt0 status
Querying tape parameters...
Trace.................... Off
Trace Hookword........... 326
Minimum Block Size....... 1
Maximum Block Size....... 16777215
Maximum SCSI Xfer........ 1048576
Physical Write Protect... No
Logical Write Protect.... No
Autoload................. No
Compression.............. Yes
Buffered Mode............ Yes
Trailer Labels........... No
Rewind Immediate......... No
Block Size............... 0
Record Space Mode........ SCSI
Volume Logging........... No
Volume ID................ UNKNOWN
Capacity Scaling......... 100%
Medium Type.............. 00
Density Code............. 46
ACF Mode................. N/A
Retain Reservation....... No
Alternate Pathing........ No
Emulate Autoloader....... No
Read SILI bit............ Yes
Reservation Type......... reserve_6
Reservation Key.......... 0xa00310754e8d3dea
I generated my shared library in 64bit on AIX, but when I ran ldd, it says:
Could not load program libmylib.so:
Could not load module libmylib.so.
The module has an invalid magic number.
Anyone knows how to list library dependencies with 64bit shared library on AIX?
If you... (1 Reply)
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)
Dear all,
I have created a KornShell script containing swiches with getopts (command line switches). Normally, my script should work like this:
$ ./myscript.ksh -a 12 -b 4 -c 78
The switch a was selected with the argument 12
The switch b was selected with the argument 4
The switch c was... (3 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)
Hi all,
Is it possible to boot from SMS menu boot devices into TS3200 FC tape library in case of an mksysb recovery on system p550 - 520 power6.
please note the library is fibre channel (1 Reply)
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)
Hi.
I have 2 libraries (overland + data domain).
My AIX 7.1 detect all "rmt" of the overland but none of the data domain.
I have the Atape driver 12.3.9.
During cfgmgr, I have this message :
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support... (2 Replies)
Hi, AIXers :)
Recently i'm playing around with cpio command, when i try to list out content from LTO2 Tape media using
command:
#cpio -itvc < /dev/rmt1
it's stopped at particular path
100777 root 1042591 Mar 24 10:09:05 2012 /home/uv/bin/usd
and there was an error thrown out:
... (2 Replies)
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)
I have Ubuntu 16.04 (dual boot with Windows 10) and a HP Spectre x360 laptop.
I have recently bought a Dell Ultrasharp U2515H monitor, which I connect via a Dell docking station.
When I plug the docking station to my laptop on Windows, both monitors are detected and everything works fine.
... (23 Replies)
Discussion started by: twelth_hour
23 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)