Spectra T-Finity/TS1140/TSM 6.3/RHEL6
Hi! Anyone using this combination of library/drives/OS? I try using the tsm-device-driver to control the library, and lin_tape to control the drives. The library and the drives connect OK and seem to work fine by themselves. Defining paths to the drives in the library fails, because the library use only the first 10 digits in the drive S/N, while lin_tape use all 12. So there is a mismatch, and the drive is not found in the library. PMR's have been opened against IBM and Spectra.. Has anyone got a similar configuration and made i work?
export node toserver= , slow.. on AIX
Hi! This is probaly not an itsm-issue, but anyway..: both tsm-servers, 5.3.4, running on the same P650, AIX5.3-box. Shared memory is used (lo0), but performance is useless. (about 140KB/sek on average, 70KB in, 70KB out) This used to work fine on our old S7A, the numbers where usually 100MB/s and up. Has anyone running TSM on AIX seen similar behavior?
export node toserver, extremely slow
Hi! Both source ant target-servers are 5.3.2.0, running on the same P650 machine, AIX 5.3.0.0 I only get around 35-50 KB/s, and that is useless... When exporting to tape from the target-server, the export runs at 20-30 MB/s, and about the same when importing from the tape to the source-server. I did a lot of noe-movement between the servers a couple of years ago, and this was probably at TSM-level 5.2.2.5. Has anyone else seen this behavior, any ideas what to look for that could cause the export toserver to be this slow ? Tom
Qualstar TLS-412360, drive-element-numbers
Hi! We just added 4 more AIT-drives to our Qualstar-library. This (SCSI)library can hold up to 12 drives, and we use the (old) element-adresses of 500-511 for the drives. The library has to drive-bays. The left one holds the original 4 drives with element-number 500-503. The new drives were placed in the right bay with element-numbers 506-509. However, TSM insist that the new drives are at 504-507: tsm: BITshow slots qualstar PVR slot information for library QUALSTAR. Library : QUALSTAR Product Id : TLS-412360 Support module : 4 Mount count : 0 Drives : 8 Slots: 360 Changers : 1 Import/Exports : 1 Device : /dev/rmt/8lb Drive 0, element 500 Drive 1, element 501 Drive 2, element 502 Drive 3, element 503 Drive 4, element 504 Drive 5, element 505 Drive 6, element 506 Drive 7, element 507 So, I was wondering: Is this a bug, or should drives in this and/or similar SCSI-libraries be mounted without any empty drive-slots inbetween them? Server is 5.3.2.0, Solaris. .
Re: HP-UX/VxFS/ACL
Problem solved.
Turned out to be a HPUX-bug introduced by fix PHKL_31500.
Applied PHKL_32272 which addressed this kernel-bug..
I have, however, one problem resulting from this that really IS a TSM-problem.
This error caused many (= 1 mill) files to be backed together with
garbage-ACLS.
I consider trying to delete these backup-copies.
ACL's are not not used on these filesystems, so if I had a way to discover
which files were backed up because of a change in the ACL, I could make a list
and delete backup-copies based on that list.
Any ideas anyone?
On Thu, 6 Oct 2005, Tom Tann{s wrote:
Hi!
I wonder if anyone has encountered similar problems:
During incremental backup on this system, since last Thursday suddenly lots
of files got backed up that hadn't neen changed for years.
Also, at random points since then, the dsmc-process has aborted with
ANS1028S An internal program error occurred.
ACL's are not set/used on any of the affected files.
(ACL's are not used at all on this system, as far as I or the SysAdm is aware
of)
After runnimg several traces, I found that the backups made was because the
TSM-client discovered a change in the size, checksum, existance etc of the
file's ACL.
The ANS1028S are because of an
hpux/pserrno.cpp( 351): TransErrno: Unexpected error from acl(GCL_GET),
errno = 22
OS is HP-UX fhume B.11.23 U 9000/800 1279364181
TSM-client is Client Version 5, Release 3, Level 0.0
TSM-server is Server Version 5, Release 2, Level 2.5
No changes/upgrades have been made to the OS/filesystem for at least 3
months.
TSM-client 5.3.0 has been running without problems since January.
HP-UX/VxFS/ACL
Hi! I wonder if anyone has encountered similar problems: During incremental backup on this system, since last Thursday suddenly lots of files got backed up that hadn't neen changed for years. Also, at random points since then, the dsmc-process has aborted with ANS1028S An internal program error occurred. ACL's are not set/used on any of the affected files. (ACL's are not used at all on this system, as far as I or the SysAdm is aware of) After runnimg several traces, I found that the backups made was because the TSM-client discovered a change in the size, checksum, existance etc of the file's ACL. The ANS1028S are because of an hpux/pserrno.cpp( 351): TransErrno: Unexpected error from acl(GCL_GET), errno = 22 OS is HP-UX fhume B.11.23 U 9000/800 1279364181 TSM-client is Client Version 5, Release 3, Level 0.0 TSM-server is Server Version 5, Release 2, Level 2.5 No changes/upgrades have been made to the OS/filesystem for at least 3 months. TSM-client 5.3.0 has been running without problems since January.
linux image/snapshot
Hi! When trying to do a backup image I keep getting ANS1347E even though the snapshot is less than 1% utilized. Client is 5.2.2.6, server is AIX, 5.2.2.5 Has anyone using this utility come across this problem? workarounds? I also came across what seems to be described in APAR IC41453, about assigning a management-class to an image-backup. According to the APAR, this was projected to be fixed in levels 5.1.7.2 and 5.2.4.0. Does anyone know what happened to these levels? The APAR was closed in July, but I haven't seen any of these levels on the ftp-site yet..
Sun server 5.2.2.0 fails to install
Hi! When trying to install, the license acceptance tool fails. Has anyone seen this? Any suggestions on how to make it work? bit.uio.no# uname -a SunOS bit.uio.no 5.8 Generic_108528-27 sun4u sparc SUNW,Sun-Fire-480R bit.uio.no# Processing package instance TIVsmS from /usit/bit/site/tsm/tsmsrv5220 Tivoli Storage Manager/Sun Server (sparc) Version 5 Release 2 Level 2.0 Preparing License Agreement Exception in thread main java.lang.UnsatisfiedLinkError: exception occurred in JNI_OnLoad at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1414) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1330) at java.lang.Runtime.loadLibrary0(Runtime.java:744) at java.lang.System.loadLibrary(System.java:815) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:48) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1065) at java.awt.Toolkit.clinit(Toolkit.java:1086) at java.awt.Color.clinit(Color.java:183) at com.ibm.lex.lapapp.LAPConstants.clinit(LAPConstants.java:53) at com.ibm.lex.lapapp.resource.SupportedLanguages.clinit(SupportedLanguages.java:61) at com.ibm.lex.lapapp.resource.LAPResources.init(LAPResources.java:361) at com.ibm.lex.lapapp.resource.LAPResources.init(LAPResources.java:175) at com.ibm.lex.lapapp.LicenseAcceptanceProcess.initApp(LicenseAcceptanceProcess.java:426) at com.ibm.lex.lapapp.LicenseAcceptanceProcess.initialize(LicenseAcceptanceProcess.java:434) at com.ibm.lex.lapapp.LicenseAcceptanceProcess.init(LicenseAcceptanceProcess.java:87) at com.ibm.lex.lapapp.LAP.getLicenseAcceptanceProcess(LAP.java:687) at com.ibm.lex.lapapp.LAP.getStatus(LAP.java:721) at com.ibm.lex.lapapp.LAP.doLAP(LAP.java:365) at com.ibm.lex.lapapp.LAP.init(LAP.java:119) at com.ibm.lex.lapapp.LAP.main(LAP.java:752) JRE error attempting to evoke the license acceptance tool. Error code 1. Please call customer support. pkgask: ERROR: request script did not complete successfully Processing of request script failed. No changes were made to the system.
TSM-server on Solaris / 53c875-HBA
Hello tsm'ers! I've just moved an old QUalstar-tapelibrary using AIT2-drives from a TSM-server on a IBM/RS6000-server onto an server running on a Sun-box. The library/drives have been working fine on the AIX-system, but I only get half the speed on the SUn-box. The HBA's on the SUn are NCR 53C875 Fast20 Wide When connecting the drives using the TSM-device-driver, the drives avre connnected as narrow devices. If connected using the native st-driver, the drives are connected wide as they should. Is anyone running a similar configuration? Any known tricks to make this work? According to the manpages for the HBA-driver (glm), the target driver has to enable wide-xfer explicitly. The st (and sd) driver do this, but the tsm-driver obviously does not.. Tom
STK-L700/IBM-LTO-2 FC, firmware
Hello! This is not actually tsm-related, but I'll give it a try.. I was about to upgrade the firmware on the drives this morning. All I could find in the download-area was 34X0L2F.ro. 34X0L2F is the right level, but what about the .ro-extension? I was hoping to find a 34X0L2F.fmr or 34X0L2F.fmrz, similar to what I'm used to with the 3590's. AIX 5.1, Atape 8.2.5.0. Does anyone know how to use the .ro-file in this environment?
Linux 5.1.5.14-client
Hello *SM'ers! Is there a problem/bug in the libPiSNAP.so and/or libPiIMG.so? We don't use the default installation-path, but DSM_DIR, DSMI_DIR etc are set to the right paths. dsmc generated these entries in dsmerror.log: 02/19/2003 20:18:45 dlopen() of /local/tsm/bin/plugins/libPiSNAP.so failed. 02/19/2003 20:18:45 libApiDS.so: cannot open shared object file: No such file or directory. 02/19/2003 20:18:45 dlopen() of /local/tsm/bin/plugins/libPiIMG.so failed. 02/19/2003 20:18:45 libApiDS.so: cannot open shared object file: No such file or directory. DSM_DIR=/local/tsm/bin DSMI_DIR=/local/tsm/api/bin tarcil.uio.no# ls -al $DSMI_DIR/libApiDS.so -r-xr-xr-x1 root root 1884550 Feb 18 16:05 /local/tsm/api/bin/libApiDS.so tarcil.uio.no# The default installation creates a symlink, /usr/lib/libApiDS.so - /opt/tivoli/tsm/client/api/bin/libApiDS.so After creating a /usr/lib/libApiDS.so - /local/tsm/api/bin/libApiDS.so, things seem to work fine. But the DSMI_DIR should make this unneccesary, shouldn't it? So.. Has anyone else come across this? Have I missed something basically here? Any suggestions, comments, etc on this would be appreciated. Tom.
Re: Strange 3590/3494-volume-behavior..?
Yes, you were right.
After restarting the server, the volume was available for use again.
Strange..
Anyway, thanks to all who spent a few seconds in helping me out...
On Mon, 7 Jan 2002, Rainer Wolf wrote:
Hello,
mabe you just need to halt and restart the server.
I had the same phaenomen some weeks ago with volumes, that have been
written directly by clients and at the same time the log file has reached
100 % before the triggered DBbackup has ended ...
( this should not normally happen )
first I tried the same as you ( 3494/3590/tsm4.1.3.0 ) and the restart did it
... the volumes became accessible as usual.
--
Mit freundlichen Grüßen / best regards
Rainer Wolf
__
Rainer Wolf [EMAIL PROTECTED]
Tel: 0731-50-22482 Fax: 0731-50-22471
University of Ulmhttp://www.uni-ulm.de/urz
University Computing Center Albert-Einstein-Allee 11
AG Basissysteme 89069 Ulm
Tom Tann{s wrote:
Hello TSM'ers!
I have a problem with a volume in my 3494-library..
Tsm-server is 4.2.1.7, AIX.
I discovered the problem a few days ago, when trying to move data from the
volume to another stg-pool.
Tsm incists that the volume is inaccessible.
An audit also result in the same:
01/07/2002 16:57:05 ANR2321W Audit volume process terminated for volume ORA052
- storage media inaccessible.
The volume was dropped by the gripper a week or so ago, but it was
re-entered via the recovery-cell. I have inventoried the frame, audited
the library on the tsm-server. A manual mount,
mtlib -l /dev/lmcp0 -m -f/dev/rmt1 -VORA052 /mtlib -l /dev/lmcp0 -d -f/dev/rmt1
work fine.
I've even done checkout/checkin libvol.
But now I'm stuck...
ANy suggestions on where to look/what to try, would be appreciated...
Tom
tsm: SUMOq libvol 3494 ORA052
Library Name Volume Name Status OwnerLast UseHome Element
--- -- -- -
3494 ORA052Private
sumo# mtlib -l /dev/lmcp0 -qV -VORA052
Volume Data:
volume state.00
logical volume...No
volume class.3590 1/2 inch cartridge tape
volume type..HPCT 320m nominal length
volser...ORA052
category.012C
subsystem affinity...03 04 01 02 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
tsm: SUMOq vol ora052 f=d
Volume Name: ORA052
Storage Pool Name: ORATAPE
Device Class Name: BCKTAPE
Estimated Capacity (MB): 40,960.0
Pct Util: 42.1
Volume Status: Filling
Access: Read/Write
Pct. Reclaimable Space: 0.0
Scratch Volume?: No
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 35
Write Pass Number: 2
Approx. Date Last Written: 12/24/2001 05:29:05
Approx. Date Last Read: 12/11/2001 04:50:20
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location:
Last Update by (administrator): TOM
Last Update Date/Time: 01/07/2002 16:49:34
Strange 3590/3494-volume-behavior..?
Hello TSM'ers! I have a problem with a volume in my 3494-library.. Tsm-server is 4.2.1.7, AIX. I discovered the problem a few days ago, when trying to move data from the volume to another stg-pool. Tsm incists that the volume is inaccessible. An audit also result in the same: 01/07/2002 16:57:05 ANR2321W Audit volume process terminated for volume ORA052 - storage media inaccessible. The volume was dropped by the gripper a week or so ago, but it was re-entered via the recovery-cell. I have inventoried the frame, audited the library on the tsm-server. A manual mount, mtlib -l /dev/lmcp0 -m -f/dev/rmt1 -VORA052 /mtlib -l /dev/lmcp0 -d -f/dev/rmt1 work fine. I've even done checkout/checkin libvol. But now I'm stuck... ANy suggestions on where to look/what to try, would be appreciated... Tom tsm: SUMOq libvol 3494 ORA052 Library Name Volume Name Status OwnerLast UseHome Element --- -- -- - 3494 ORA052Private sumo# mtlib -l /dev/lmcp0 -qV -VORA052 Volume Data: volume state.00 logical volume...No volume class.3590 1/2 inch cartridge tape volume type..HPCT 320m nominal length volser...ORA052 category.012C subsystem affinity...03 04 01 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 tsm: SUMOq vol ora052 f=d Volume Name: ORA052 Storage Pool Name: ORATAPE Device Class Name: BCKTAPE Estimated Capacity (MB): 40,960.0 Pct Util: 42.1 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 0.0 Scratch Volume?: No In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 35 Write Pass Number: 2 Approx. Date Last Written: 12/24/2001 05:29:05 Approx. Date Last Read: 12/11/2001 04:50:20 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): TOM Last Update Date/Time: 01/07/2002 16:49:34
Re: Strange 3590/3494-volume-behavior..?
Yes, and that's why I included this, plus a few others at the bottom of my
mail
On Mon, 7 Jan 2002, Kathleen Hallahan wrote:
Have you tried q vol ORA052? If the library lost track of the tape TSM
would mark it as unavailable; to update it you'd need to type upd vol
ORA052 acc=readwrite (or acc=readonly if you don't want any more data
written to the tape).
Tom Tann{s
tom.tannas@USTo: [EMAIL PROTECTED]
IT.UIO.NOcc:
Sent by: Subject: Strange
3590/3494-volume-behavior..?
ADSM: Dist
Stor Manager
[EMAIL PROTECTED]
IST.EDU
01/07/2002
11:21 AM
Please respond
to ADSM: Dist
Stor Manager
Re: exclude syntax frustration
Did you check if the client got it right? dsmc q inclexcl and dsmc show options On Fri, 4 Jan 2002, Glass, Peter wrote: TSM seems to ignore our exclude statements, no matter which wildcard syntax we use. For example, we have filesystems called /db1/oracle, /db2/oracle, etc. through /db30/oracle that we want to exclude. We've tried: exclude /db[1-30]/oracle/.../* and exclude /db*/oracle/.../* and exclude /.../oracle/.../* without success: in each case, the backups still try to backup the files under these directories. The backups usually fail to pick up the files, because the files change during the backup, which is why we want to exclude them. Are we misunderstanding how wildcards are supposed to work with exclude statements? Or is this a product bug? Peter Glass Distributed Storage Management (DSM) Wells Fargo Services Company * 612-667-0086 * 866-407-5362 * [EMAIL PROTECTED]
LTO, import data
Hello tsm'ers. Has anyone using these drives tried to do a import node? I have HP Ultrium drives, LVD-connected to a S7A, AIX. TSM is 4.2.1.7. When running an import from these drives I only get aroung 200KB/s, until after some time the drive/scsi-bus/controller will give up. Repeated tests on the same data/tape/drive result in the same, but the amount of data imported could vary from some KB to several GB before the crash. All other operations to/from the drives work fine. Streaming, they are really fast. Not streaming, not that good..., but that's not the issue here, I hope. I had a PMR opened on this two months ago, but nothing happens.. Has anyone using the IBM LTO-drives/Atapedriver had some experience in importing data? Any hints from LTO-users, IBM,HP or whatever, would be appreceated. Tom
label/checkin libvol, vollist ignored.
Has anyone tried this? the vollist=000780 sems to be ignored... I WAS goin to label an check-in both volumes, but due to previous errors on these, the plan was to retry one volume at at time. The HP-library is a Surestore 20/700, scsi-attached. Server is AIX, 4.2.1.7 11/26/2001 20:33:27 ANR2017I Administrator TOM issued command: LABEL libvol hp search=bulk labels=bar checkin=scratch vollist=000780 11/26/2001 20:33:27 ANR0984I Process 814 for LABEL LIBVOLUME started in the BACKGROUND at 20:33:27. 11/26/2001 20:33:27 ANR8799I LABEL LIBVOLUME: Operation for library HP started as process 814. 11/26/2001 20:33:27 ANR8373I 002: Fill the bulk entry/exit port of library HP with all LTO volumes to be processed within 60 minute(s); issue 'REPLY' along with the request ID when ready. 11/26/2001 20:33:37 ANR2017I Administrator TOM issued command: REPLY 2 11/26/2001 20:33:37 ANR8499I Command accepted. 11/26/2001 20:34:27 ANR8810I Volume 000780 has been labeled in library HP. 11/26/2001 20:35:02 ANR8427I CHECKIN LIBVOLUME for volume 000780 in library HP completed successfully. 11/26/2001 20:35:51 ANR8810I Volume 000784 has been labeled in library HP. 11/26/2001 20:36:26 ANR8427I CHECKIN LIBVOLUME for volume 000784 in library HP completed successfully. 11/26/2001 20:36:26 ANR8801I LABEL LIBVOLUME process 814 for library HP completed; 2 volume(s) labelled, 2 volume(s) checked-in. 11/26/2001 20:36:26 ANR0985I Process 814 for LABEL LIBVOLUME running in the BACKGROUND completed with completion state SUCCESS at 20:36:26.
Re: How to attach HP LTO
No... The Atape-driver is only used forthe IBM-devices. All other scsi-devices, libraries an drives, use the tsm-driver. You find it in smit under devices, Tivoli Storage Manager Devices, The device-types are ADSM-SCSI-MT scsi Tivoli Storage Manager Tape Drive and ADSM-SCSI-LB scsi Tivoli Storage Manager Library Hope this helps... On Mon, 19 Nov 2001, Zlatko Krastev/ACIT wrote: You need to install Atape driver. It will suport the library and define file in /dev for you. Afterwards TSM will take care for it. Zlatko Krastev IT Consultant P.S. And please write some subject on your posts Zlatko Lei L Wang [EMAIL PROTECTED] on 19.11.2001 10:40:06 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Hi,all My customer have a HP LTO library sure store 2/20 connected with IBM AIX. They want to use TSM Manage it. But we can't see the device name in smitty and there is no device file under /dev or /etc dir. But HP engineer said they had configed the library well. How to connect with it is TSM's business. Who can config HP LTO with TSM ? Is there any one hase such experience ?
Re: TSM 4.2.1.7, 3590
Well, sorry.. I was wrong in saying we were running 4.3.2. I will check with our AIX-expert tomorrow, and have him go through the system... At least, my bos.rte is at 4.3.3.0, and, as you say, this is requiered for tsm 4.2.x. What confused me was the oslevel-command, which returns 4.3.1.0.. Some time ago our AIX-expert told me not to worry; the level is 4.3.2. Thanks for your input! Tom. On Sun, 18 Nov 2001, Zlatko Krastev/ACIT wrote: This might not be the case but also may be - you wrote AIX 4.3.2. According to http://www.tivoli.com/support/storage_mgr/ad6serv.htm you have to be at AIX 4.3.3 or later for TSM 4.2.x. I would even go to 4.3.3ML6 or ML8 for bos.?p and bos.rte.* ! Zlatko Krastev IT Consultant
TSM 4.2.1.7, 3590 - solved
Thanks to all who responded... No one actually hit the target, I got several useful hints. It turned out to be the Atape-driver that caused the problem. After realizing that I was at AIX 4.3.3, and applying the latest driver, everything works fine again.
TSM 4.2.1.7, 3590
Hello TSM'ers! Has anyone running TSM on AIX using 3494/3590 tried the 2.2.1.7-server? After applying this level last night, I can't get my 3590's to work. When trying to mount a tape, the mount fails. A server-trace show this: 18:46:46.312 58mmsflag.c(2889): Opening drive 3590_1 (/dev/rmt1) in library 34 94. 18:46:46.359 58pvrntp.c(2734): Testing readiness of drive 3590_1 (/dev/rmt1). 18:46:46.360 58psntpop.c(1568): Error performing TESTREADY operation on drive 3590_1 (/dev/rmt1); errno = 22 q mount report the usual mount point waiting... After a couple of minutes it times out: 18:47:46.374 58mmsflag.c(2941): Drive 3590_1 (/dev/rmt1) in library 3494 timed out. The tape-volume get physically mounted in the drive. Monitored by mtevent. mtlib -l /dev/lmcp0 -qM also report the volume as mounted. The tapedrive itself is online and ready.. Any hints on what to check/what could be wrong, anyone? The readme of 4.2.1.7 refer to IC32125, which has been fixed. I have not had this problem, but it seems to deal with similar problems that I see now. Could it be the the fix for IC32125 that introduce new problems? I did't commit the 4.2.1.7, so I could go back to 4.2.1.6. However, my DB is huge, so I would prefer not to do so if not absolutely neccessary AIX is 4.3.2 Atape is 5.4.4.0 atldd is 4.1.5.0 The 3590's are E1A-models, SCSI-connected directly to the server.
Re: TSM 4.2.1.7, 3590
Yes I did reboot, just in case..
There are no updates to the device-components in this release, so
rebooting shouldn't be necessary.
Also, the 3494/3590's use the atldd/Atape-drivers, not the tsm-drivers.
Anyway, thanks for the thought..
On Sat, 17 Nov 2001, J Bamford wrote:
Hi Tom
I haven't used 4.2.1.7, but did it install a new TSM devices component as
part of the upgrade.
Normally when the TSM devices are installed or upgraded on AIX they do a
bosboot that requires a reboot of the machine to take fully effect. I've
had similar device problems after install that were cleared by a reboot.
It's just a thought, but have you rebooted Aix since applying 4.2.1.7 ?
Jason Bamford
Tivoli Software EMEA
New to the forum
- Original Message -
From: Tom Tann{s [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, November 17, 2001 10:19 PM
Subject: TSM 4.2.1.7, 3590
Re: TSM 4.2.1.7, 3590
Hi. Yes I have tested the drives outside of TSM, and scsi-paths work fine. So, at least I know by now that others have it working. Thanks. Btw.. What are your levels of OS an Atape? 3590 firmware-level? Tom On Sun, 18 Nov 2001, Remco Post wrote: Hi, yes we do, we have a 3494 with 3590 E1A drives working very happy with 4.2.1.7. No problems whatsoever. We alse have scsi 3590s so our setups are quite comparable. Dit you try using mtlib or mt commands on this drive as a test to see weather or not the OS can still talk scsi to your drive(s)? The only thing we didn't do is reboot, since our tsm server doubles as a fileserver for quite a few users who use their files 24/7, this was not an option at the time we installed the fix
Re: TSM 4.2.1.6 AIX 4.3.3.0
So, once again, the actual build of the server is not in sync, as I suspected.. This has happened before, and it's very frustrating. I have seen notes on the list from Tivoli-people that they vould look into their routines, and make sure it doesn't happen again. So why do we still have to go through this? On Thu, 1 Nov 2001, Sheelagh Treweek wrote: . . I would urge anyone experiencing server problems that require a restart to resolve, to report the problems to IBM/Tivoli. They may not get the focus required to diagnose and fix otherwise. Thanks to all for the information about 421x. I opened a PMR about the licensing problems still persisting at 4216 and was told today that it will be fixed at 4127, which is being built, and that it had been accidentally omitted from 4216. Regards, Sheelagh -- Sheelagh Treweek Oxford University Computing Services Email: [EMAIL PROTECTED] Phone: +44 (0)1865 273205 Fax:-273275
Re: 4.2.1.6 (was: Re: TSM Server v4.2.1)
Hmm.. I installed the 4.2.1.6 this afternoon, and have made the same observations as Henk regarding IC30965. But luckily, the mount-point-problem seems to be gone. According to the dsmserv-binary itself (AIX) all the fixes in the README-file obviously was meant to be there.. Could it be that something was messed up when compiling the new dsmserv? Recreating the nodelock really doesn't matter However, when the problem finally is fixed it should be done to get rid of the entries from all the failed register license-commands that has been done.. On Tue, 30 Oct 2001, Henk ten Have wrote: According to the information in apar IC30965 the licensing problem is supposed to be fixed in 4.2.1.6. * RECOMMENDATION: Apply fixing PTF when available. When the * fix is applied you may need to first delete * the nodelock file then touch the nodelock * file to recreate it. Did you recreate the nodelock file as recommended in the apar? Yeppo. We did. But if you read the README, you will also read that this problem was fixed in 4.2.1.5 (I gonne hate these numbers...). And this fix disappeared in 4.2.1.6. So we still have to deal with hundreds of thousends rediculous messages every day. (besides of hundreds of thousends other rediculous messages you get every day, every typo is logged in the activitylog for example, ok, wrong example, we don't do hundred of thousends typo's every day;-) Cheers, Henk (visiting a TSM-user day on Friday in Holland, will be big fun)
Re: TSM 4.2.1
I agree. don't... I did the upgrade yesterday. (AIX 4.3.2) Only one problem discovered so far, but it's serius. Something is messed up with the allocation of mountpoins in the libraries. Clients or processes needing a mountpoint would earlier just sit and wait until one was available. In 4.2.1 it seems that if all mountpoints are in use or reserved, furter requests for mountpoints are cancelled. 10/22/2001 10:42:57 ANR8447E No drives are currently available in library 3494. 10/22/2001 10:42:57 ANR1401W Mount request denied for volume ORA168 - mount failed. When this happened, I also noticed a new message from q mount: ANR8376I Mount point reserved in device class BCKTAPE, status: RESERVED. ANR8334I 1 matches found. The other 3 drives where busy. I've just started digging into this, so it could be that I have missed something... On Mon, 22 Oct 2001, Gill, Geoffrey L. wrote: To all, For all those who are thinking of upgrading to 4.2.1, my opinion is don't. I have been up on it for 10 days and have already experienced 3 crashes. I also have a tape problem that I'm told was supposed to have been fixed. I have 2 PMR's open, both at level 2. I'm on AIX 4.3.3 and not sure if other platforms have had similar problems. I would like to hear from anyone else experiencing these or any other problems. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: TSM 4.2.1
Thanks.. I did have look at the 4.2.1.2-fix, but it didn't describe anything but the 3583-problem. Has anyone with 3494 installed the fix, and dit it solve the problem here as well? Btw.. I was also hoping that the fix for IC30965 (registering of miltiple license-files) had made it to 4.2.1. My actlogs are filled width some 1000-1800 ANR2841W's each day. IC30965 is closed. When can we expect to see a fix? On Mon, 22 Oct 2001, Jeremy Greven wrote: Geoff. I had similar problems with the upgrade. My 3583 just stopped working. period. I was getting the no mount points available while there was nothing mounted and all seemed well. There was a fix issued - both for AIX and NT to resolve this problem. 4.2.1.3 resolved the issue for NT and I believe that 4.2.1.2 resolves these issues for AIX as some have described. Both versions are available for download off of the boulder website. (service.boulder.ibm.com) Hope this helps. Jeremy Greven Senior Network Analyst Chubb Insurance Company of Canada Gill, Geoffrey L. To: [EMAIL PROTECTED] GEOFFREY.L.GILLcc: @SAIC.COM Subject: TSM 4.2.1 Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] T.EDU 10/22/2001 09:26 AM Please respond to ADSM: Dist Stor Manager To all, For all those who are thinking of upgrading to 4.2.1, my opinion is don't. I have been up on it for 10 days and have already experienced 3 crashes. I also have a tape problem that I'm told was supposed to have been fixed. I have 2 PMR's open, both at level 2. I'm on AIX 4.3.3 and not sure if other platforms have had similar problems. I would like to hear from anyone else experiencing these or any other problems. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: TSM 4.2.1
After syncronizing the tsm-db with the 3494-inventory, I still get errors
like these:
10/23/2001 00:04:16 ANR8341I End-of-volume reached for 3590 volume BU0164.
10/23/2001 00:04:20 ANR8336I Verifying label of 3590 volume BU0164 in drive
3590_2 (/dev/rmt2).
10/23/2001 00:04:39 ANR8447E No drives are currently available in library
3494.
10/23/2001 00:04:39 ANR1404W Scratch volume mount request denied - mount
failed.
All drives were busy, but the reclamation-process should just sit and
wait..
q mount..
q mount should show information about mounted volumes.
help q mount states that this is still the case.
In 4.2.1 it seems that information on the mountpoints are included also.
Earlier, this information was available only though the show mp
unsupported command.
I prefer the q mount as documented..
Why not a q mountpoint or q mount -detail/f=d or similar?
On Mon, 22 Oct 2001, Tom Tann{s wrote:
Thanks..
I did have look at the 4.2.1.2-fix, but it didn't describe anything but
the 3583-problem.
Has anyone with 3494 installed the fix, and dit it solve the problem here
as well?
Btw.. I was also hoping that the fix for IC30965 (registering of miltiple
license-files) had made it to 4.2.1.
My actlogs are filled width some 1000-1800 ANR2841W's each day.
IC30965 is closed. When can we expect to see a fix?
Import node from a shared library..
Hello! I'm not very experienced in using shared libraries, so I might have missed something here... Anyway. Export works fine. Import, however, fail with the messages (server is Storage Management Server for AIX-RS/6000 - Version 4, Release 2, Level 0.1) Has anyone else encountered this problem? 09/25/2001 14:25:04 ANR2017I Administrator TOM issued command: IMPORT NODE RIKKE.UIO.NO filesp=/uio/rikke/unipub filedata=all devclass=aittape volum=45 09/25/2001 14:25:04 ANR0984I Process 17 for IMPORT NODE started in the BACKGROUND at 14:25:04. 09/25/2001 14:25:04 ANR0609I IMPORT NODE started as process 17. 09/25/2001 14:25:04 ANR1504I IMPORT NODE: No matching domains. 09/25/2001 14:25:04 ANRD xibf.c(905): ThreadId41 Error 87 encountered in opening import stream. 09/25/2001 14:25:04 ANR0661E IMPORT NODE: Internal error encountered in accessing data storage. 09/25/2001 14:25:06 ANR0985I Process 17 for IMPORT NODE running in the BACKGROUND completed with completion state FAILURE at 14:25:06. The export ran OK: 09/25/2001 14:17:13 ANR2017I Administrator TOM issued command: EXPORT NODE RIKKE.UIO.NO filesp=/uio/rikke/unipub filedata=all devclass=aittape scratch=yes 09/25/2001 14:17:13 ANR0984I Process 15 for EXPORT NODE started in the BACKGROUND at 14:17:13. 09/25/2001 14:17:13 ANR0609I EXPORT NODE started as process 15. 09/25/2001 14:18:22 ANR0610I EXPORT NODE started by TOM as process 15. 09/25/2001 14:18:22 ANR0635I EXPORT NODE: Processing node RIKKE.UIO.NO in domain MUSPROJ. 09/25/2001 14:18:22 ANR0637I EXPORT NODE: Processing file space /uio/rikke/unipub for node RIKKE.UIO.NO fsId 40. 09/25/2001 14:20:05 ANR0617I EXPORT NODE: Processing completed with status SUCCESS. 09/25/2001 14:20:05 ANR0626I EXPORT NODE: Copied 1 node definitions. 09/25/2001 14:20:05 ANR0627I EXPORT NODE: Copied 1 file spaces, 0 archive files, 17114 backup files, and 0 space managed files. 09/25/2001 14:20:05 ANR0629I EXPORT NODE: Copied 419292883 bytes of data. 09/25/2001 14:20:05 ANR0611I EXPORT NODE started by TOM as process 15 has ended. 09/25/2001 14:20:05 ANR4006I EXPORT NODE: Volume 1 written by process is 45. 09/25/2001 14:20:05 ANR0986I Process 15 for EXPORT NODE running in the BACKGROUND processed 17116 items for a total of 419,292,883 bytes with a completion state of SUCCESS at 14:20:05.
Re: Import node from a shared library..
Yes, it is. Forgot to mention that.
I will have a look at IC31078, which seems to be addressing this.
Thank you for the quick response!
On Tue, 25 Sep 2001, Richard Cowen wrote:
Is this a SCSI shared library, and are doing the import on the client tsm
server?
If so, you may want to check:
APAR= IC31078 SER=IN INCORROUT
WHEN USING A LIBTYPE=SHARED LIBRARY, YOU ARE UNABLE TO RUN AN
EXPORT, IMPORT, DB RESTORE OR RESTORE BACKUPSET.
-Original Message-
From: Tom Tann{s [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 25, 2001 9:28 AM
To: [EMAIL PROTECTED]
Subject: Import node from a shared library..
Hello!
I'm not very experienced in using shared libraries, so I
might have missed
something here...
Anyway.
Export works fine.
Import, however, fail with the messages
library-sharing..
Hello *sm'ers! Up to now we have been running one tsm-server. Because of its size we're going to start a second instance of the server on the same box (AIX) later this week. We have two SCSI-libraries and one 3494 connected. I have been searching the manuals and the ADSM-L for information on how to configure the libraries and drives, but most, if not all, are dealing with sharing libraries between more servers on different machines and SAN-environmets. I guess this is pretty straight-forward, but if anyone have pointers to information, experience, hints, tricks etc, I would be happy to hear from you. Thanks, Tom.
Re: License problem
It's a known problem. APAR IC30965 is open on this. On Wed, 22 Aug 2001, Maurice van 't Loo wrote: Hi, When we want to register licenses on TSM 4.2.0.0, we can use a lic-file only ones, so we can't get the number of licenses higher than 66 (50 + 10 + 5 + 1) If i open the nodelock file, i see A LOT of licenses registered, but not in my q lic. A known problem? Tia, Maurice
TSM 4.2 (AIX), licensing..
Hello! I upgraded a server from 4.1 to 4.2 today. I've only managed to register one 50mgsyslan.lic whith the command register lic file=50mgsyslan.lic number=12 additional attempts toregister more result in the same.. tsm: SUMOregister license file=50mgsyslan.lic ANR2852I Current license information: ANR2827I Server is licensed to support Managed System for LAN for a quantity of 60. ANR2853I New license information: ANR2827I Server is licensed to support Managed System for LAN for a quantity of 60. tsm: SUMO (Its 60 now because I successfully registered one 10mgsyslan.lic) After several attempts I took a look at the nodelock-file, and this file seems to be updated correctly, with one entry for each of my attempts.. . . . . # Managed System for LAN 50 Licen 6fb1ea8d2ebc.a3.89.a3.25.04.00.00.00 8umtikm47qkykpffafnaa 4.2 #[admin_comment] 0 0 0 # Managed System for LAN 50 Licen 6fb1ea8d2ebc.a3.89.a3.25.04.00.00.00 8umtikm47qkykpffafnaa 4.2 #[admin_comment] 0 0 0 So... Could this be a bug, or am I missing something here?
Re: TSM 4.2 (AIX), licensing..
Oops.. I went to 4.2.0.1, and that's where I have the problem.
Thanks, guess I will call support tomorrow, then..
On Wed, 15 Aug 2001, David McClelland wrote:
Tom,
Yes, apparently this is a known bug - you should have a look at the latest
patch (4.2.0.1) , rather than the flat 4.2 version, although I'm of the
understanding that the licensing problem is still an issue here too...
There'll be a fix for this along soon - can anyone add any more to this?
Rgds,
David McClelland
---
Tivoli Storage Management Team
IBM EMEA Technical Centre,
Mail Point SGJ3, IBM, North Harbour, Portsmouth PO6 3AU, England
Internet: [EMAIL PROTECTED]
Tom Tann{s [EMAIL PROTECTED]@VM.MARIST.EDU on 15-08-2001 14:46:22
Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: TSM 4.2 (AIX), licensing..
Hello!
I upgraded a server from 4.1 to 4.2 today.
I've only managed to register one 50mgsyslan.lic whith the command
register lic file=50mgsyslan.lic number=12
additional attempts toregister more result in the same..
tsm: SUMOregister license file=50mgsyslan.lic
ANR2852I Current license information:
ANR2827I Server is licensed to support Managed System for LAN for a
quantity of 60.
ANR2853I New license information:
ANR2827I Server is licensed to support Managed System for LAN for a
quantity of 60.
tsm: SUMO
(Its 60 now because I successfully registered one 10mgsyslan.lic)
After several attempts I took a look at the nodelock-file, and this file
seems to be updated correctly, with one entry for each of my attempts..
.
.
.
.
# Managed System for LAN 50 Licen
6fb1ea8d2ebc.a3.89.a3.25.04.00.00.00 8umtikm47qkykpffafnaa 4.2
#[admin_comment] 0 0 0
# Managed System for LAN 50 Licen
6fb1ea8d2ebc.a3.89.a3.25.04.00.00.00 8umtikm47qkykpffafnaa 4.2
#[admin_comment] 0 0 0
So... Could this be a bug, or am I missing something here?
Re: TSM 4.2 (AIX), licensing..
Well, the first thing I tried was just that, to remove the old nodelock. Made no difference... On Wed, 15 Aug 2001, Valerie Fisher wrote: Tom - I had the same problem - you need to remove the nodelock file and re-register. Re-issuing the command without removing the nodelock file just increases the number.
TSM 4.2
Hello! The 4.2-clients have been available on the ftp-server since Saturday. Anyone know why the 4.2-servers still are missing? GA was on July 1. for both? The AIX-server is the one I'm waiting for..
Re: 5 GB limit on Recovery Log
I just upgraded to 4.1.3 According to show lvmfa on this server, the limit is still 5.3 GB On Wed, 16 May 2001, Prather, Wanda wrote: I've lost track - has the 5 GB limit on the size of the recovery log been lifted in the V4.1 server? The 5 GB limit is killing me here - it would be a good reason for me to upgrade
Re: Antw: 4.1.3.0-scheduling-problem
Just one more note on this...
I ran one last test this morning.
Instead of just changing the start-time of the schedule, this time I
deleted it from the server.
Client (SUMO):
05/15/2001 11:40:37.0635 : session.c (1525): sessRecvVerb(): length=000c, verb=11,
magic=a5
05/15/2001 11:40:37.0635 : session.c (1612): Length:12 Code: 0011 Type:
- AuthResult
05/15/2001 11:40:37.0636 : cusched.c ( 290): SendStartOp: Sending a CSStartOpVerb,
node: 'SUMO'
05/15/2001 11:40:37.0637 : cusched.c ( 291): scheduleName: 'TEST_2',
startDateToken: 05/15/2001 11:40:00
05/15/2001 11:40:37.0637 : session.c (1696): Send Verb: Length:29 Code: 0022
Type: CSStartOp
05/15/2001 11:40:37.0637 : session.c (1722): -
05/15/2001 11:40:37.0637 : session.c (1494): Recv Verb:
05/15/2001 11:44:50.0216 : session.c (1513): ...error-1
05/15/2001 11:44:50.0216 : session.c (1515): sessRecvVerb: Error -50 from call to
'readRtn'.
Server:
010515-114037: ANR0406I Session 1273 started for node SUMO (AIX) (Tcp/Ip
129.240.130.17(6307-6)).
010515-114037: ANRD pkthread.c(513): Run-time assertion failed:
txnP-txnInFlight,
010515-114037: Thread 100, File tmtxn.c, Line 833.
010515-114037: ANR7838S Server operation terminated.
010515-114037: ANR7837S Internal error TMTXN008 detected.
010515-114037: ANR7834S Thread 100 (tid 6409) terminating on signal 11 (Segmentation
violation).
010515-114037: ANR7834S GPR 0: 0xd0018f00, 1: 0x5c2a5ed0, 2: 0x301976a0, 3:
0x
010515-114037: ANR7834S GPR 4: 0x5c2a72e8, 5: 0x0008, 6: 0x0003, 7:
0x
010515-114037: ANR7834S GPR 8: 0x1000a817, 9: 0x1000a817, 10: 0xf0347e24,
.
.
.
.
On Mon, 14 May 2001, Tom Tann{s wrote:
Guess I'll submit an APAR tomorrow.
Did just run a trace on a client, and, as I thougt, the server sends wrong
information to the client.
05/14/2001 16:52:34.0790 : cusched.c ( 290): SendStartOp: Sending a CSStartOpVerb,
node: 'SUMO'
05/14/2001 16:52:34.0790 : cusched.c ( 291): scheduleName: 'TEST_2',
startDateToken: 05/14/2001 16:48:00
05/14/2001 16:52:34.0790 : session.c (1696): Send Verb: Length:29 Code: 0022
Type: CSStartOp
At 16:46 the schedule's startup-time was changed to 05/15/2001 16:48:00.
Anyway, thanks for suggestions.
On Mon, 14 May 2001, Michael Donabauer wrote:
Level 4.1.3.2 upgrade
[EMAIL PROTECTED] 14.05.2001 02.23 Uhr
Hello!
Whith server-level 3.7 and earlier, if a client-scheduler was scheduled to
do something whithin its queryschedperiod, and the schedule on the server
in the meantime was changed to run at a later time, the client scheduler
would report a ANS1814E and rescheduled itself.
I just upgraded to 4.1.3, and in this case, the client runs the original
scheduled task, just as if nothing was changed at the server.
Is this another case of buffers not cleared/updated on the server?
Anyone else seen this behaviour?
Tom
Re: 4.1.3.0-scheduling-problem
You are perhaps right if the action, option or object-parameters are
changed.
However, in my case, only the start-time of the schedule was changed.
This is how one of my clients reacted to this when still at server level
3.7:
.
.
05/06/2001 02:04:18 --- SCHEDULEREC QUERY BEGIN
05/06/2001 02:04:18 --- SCHEDULEREC QUERY END
05/06/2001 02:04:18 Next operation scheduled:
05/06/2001 02:04:18
05/06/2001 02:04:18 Schedule Name: DAGLIG
05/06/2001 02:04:18 Action:Incremental
05/06/2001 02:04:18 Objects:
05/06/2001 02:04:18 Options: -incrbydate
05/06/2001 02:04:18 Server Window Start: 01:00:00 on 05/07/2001
05/06/2001 02:04:18
05/06/2001 02:04:18 Command will be executed in 22 hours and 56 minutes.
05/07/2001 01:00:18
Executing scheduled command now.
05/07/2001 01:00:18 Node Name: HARALDSEN
05/07/2001 01:00:19 Session established with server SUMO: AIX-RS/6000
05/07/2001 01:00:19 Server Version 3, Release 7, Level 3.1
05/07/2001 01:00:19 Server date/time: 05/07/2001 01:00:19 Last access:
05/06/
2001 02:04:18
05/07/2001 01:00:19 ANS1814E Unable to start scheduled event 'DAGLIG'
05/07/2001 01:00:19 ANS1815E Either the window has elapsed or the schedule has been
deleted
05/07/2001 01:00:19 ANS1483I Schedule log pruning started.
05/07/2001 01:00:19 Schedule Log Prune: 2036 lines processed. 111 lines pruned.
05/07/2001 01:00:19 ANS1484I Schedule log pruning finished successfully.
05/07/2001 01:00:19 Querying server for next scheduled event.
.
.
And, schedmode is polling.
On Mon, 14 May 2001, Mark Stapleton wrote:
Tom Tann{s wrote:
Whith server-level 3.7 and earlier, if a client-scheduler was scheduled to
do something whithin its queryschedperiod, and the schedule on the server
in the meantime was changed to run at a later time, the client scheduler
would report a ANS1814E and rescheduled itself.
I just upgraded to 4.1.3, and in this case, the client runs the original
scheduled task, just as if nothing was changed at the server.
Is this another case of buffers not cleared/updated on the server?
I don't recall this behavior at all. When you make a change in a client
schedule on the server, you have to stop and restart the scheduler
service running on each client associated to that scheduler so that the
new parameters are read and obeyed by the client.
--
Mark Stapleton ([EMAIL PROTECTED])
Re: Antw: 4.1.3.0-scheduling-problem
Guess I'll submit an APAR tomorrow. Did just run a trace on a client, and, as I thougt, the server sends wrong information to the client. 05/14/2001 16:52:34.0790 : cusched.c ( 290): SendStartOp: Sending a CSStartOpVerb, node: 'SUMO' 05/14/2001 16:52:34.0790 : cusched.c ( 291): scheduleName: 'TEST_2', startDateToken: 05/14/2001 16:48:00 05/14/2001 16:52:34.0790 : session.c (1696): Send Verb: Length:29 Code: 0022 Type: CSStartOp At 16:46 the schedule's startup-time was changed to 05/15/2001 16:48:00. Anyway, thanks for suggestions. On Mon, 14 May 2001, Michael Donabauer wrote: Level 4.1.3.2 upgrade [EMAIL PROTECTED] 14.05.2001 02.23 Uhr Hello! Whith server-level 3.7 and earlier, if a client-scheduler was scheduled to do something whithin its queryschedperiod, and the schedule on the server in the meantime was changed to run at a later time, the client scheduler would report a ANS1814E and rescheduled itself. I just upgraded to 4.1.3, and in this case, the client runs the original scheduled task, just as if nothing was changed at the server. Is this another case of buffers not cleared/updated on the server? Anyone else seen this behaviour? Tom
4.1.3.0-scheduling-problem
Hello! Whith server-level 3.7 and earlier, if a client-scheduler was scheduled to do something whithin its queryschedperiod, and the schedule on the server in the meantime was changed to run at a later time, the client scheduler would report a ANS1814E and rescheduled itself. I just upgraded to 4.1.3, and in this case, the client runs the original scheduled task, just as if nothing was changed at the server. Is this another case of buffers not cleared/updated on the server? Anyone else seen this behaviour? Tom
Re: Export Question
Are you using copypools to protect your primary stg-pools? If so, q occup and auditocc report the total occupancy of both primary and copy. On Mon, 9 Apr 2001, Blaine Gilbreath wrote: I am working on an Export process and I am running into some capacity discrepancies. Below is the process that I followed. 1. Run AUDIT LICENSE 2. QUERY AUDITOCC 3. The node shows that ADSM has 845GB of data. 4. I run EXPORT NODE FILEDATA=ALL PREVIEW=YES and that shows that only 440GB will be exported. Is my database corrupt or do the numbers from the audit and the export differ? I tried calling ADSM support but, as of 4/1/01 all support even 1st level has been dropped. Regards, Blaine
Re: Strange SCSI adapter failure with AIT drives
We had similar problems for several months. After upgrading the drives to 1.08 the problems were gone. On Wed, 28 Feb 2001, Jochen Strohbeck wrote: Hi, we observed a problem related to TDSM and SONY AIT drives. Sometimes we get the following error message on a Solaris connected to a tape library: ANR8302E I/O error on drive DRIVE01 (/dev/rmt/0mt) (OP=READ, CC=205, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**, Description=SCSI adapter failure). We had three engineers from Sony here to check the situation. First we thought that the problem is related to SCSI and we attached a SCSI analyzer to log the bus activities. We were lucky to catch the situation when the error occured. In the trace we saw that in a DATA_IN_PHASE (= host READ) the AIT drive suddenly sets all SCSI signals inactive. The SONY engineers said that this is caused by a HW reset due to weak power supply. So we built in better power supplies but the problem is still there. In one case we were able to reproduce the problem with one special tape. But when we put the tape in another drive everything works fine. So I think that there might be a problem when a tape is written in one drive and read in another drive. From my point of view there is a problem reading the media. Several times we observed that the AIT makes several retries to read data from the tape. Maybe this leads to a SCSI command timeout and the error message above. Has anyone similar problems? Any suggestions? I've heard that there is a new firmware 1.08 for the AIT drives but we havn't got anything from our disti. Thanks, Jochen Strohbeck
Version 4, Release 1, Level 2, Tru64 UNIX
I have just installed the new 4.1.2 client ona a few systems. The client seems to backup up all files, event if they are previously backed up. The clients where upgraded from 3.1.0.8. The 3.1.0.8-README states: This version of the client supports ACL's and file properties. If you are updating from a version, which had no support (V2, V3.1.0.1), already backed up files may be again transferred to the server during an incremental backup. If you want to keep an additional backup copy, please increase the number of different backup versions on the ADSM or TSM server. Which was indeed true, and caused a lot of trouble back then when upgrading to 3.1.0.8. The 4.1.2-README says the same: This version of the client supports ACL's and file properties. If you are updating from a version, which had no support (V2, V3.1.0.1), already backed up files may be again transferred to the server during an incremental backup. If you want to keep an additional backup copy, please increase the number of different backup versions on the ADSM or TSM server. So I assumed when going from 3.1.0.8 this would not happen again.. Has ayone else seen this behaviour with 4.1.2? Any comments/suggestions?
export node/server-crash
Today my server crashed when finishing off a successful export-node-operation. Server is 3.7.3.1 running on AIX 4.3.1.0. Back in som early adsm-server there was a problem writing the volume-history-information if the export node-command was too long (more than 256 characters?) This was fixed, and the limit is much higher now. But what is the current limit? The export-command that caused my crash today was 547 characters long. The command-column in the sql-table volhistory is 2001 characters long, and if the internal database-columns also should hold 2001 characters, then I'm on the rong track.. However, the failing operation seems to be the write the volumehistory-record: 001229-074843: ANR1361I Output volume EXP961 closed. 001229-074904: ANR0617I EXPORT NODE: Processing completed with status SUCCESS. 001229-074904: ANR0568W Session 51 for admin TOM (Server) terminated - connection with client 001229-074904: severed. 001229-074904: ANR0891I EXPORT NODE: Copied 3 optionset definitions. 001229-074904: ANR0626I EXPORT NODE: Copied 9 node definitions. 001229-074904: ANR0627I EXPORT NODE: Copied 30 file space 0 archive files, 530952 backup 001229-074904: files, and 0 space managed files. 001229-074904: ANR0630I EXPORT NODE: Copied 77117370 kilobytes of data. 001229-074904: ANR0611I EXPORT NODE started by TOM as process 1 has ended. 001229-074904: ANR4006I EXPORT NODE: Volume 1 written by process is EXP961. 001229-074907: ANR7834S Thread 52 (tid 34bc) terminating on signal 11 (Segmentation violation). 001229-074907: ANR7834S GPR 0: 0x0001, 1: 0x550e5e70, 2: 0xf0049e1c, 3: 0x550e6474 001229-074907: ANR7834S GPR 4: 0x0001, 5: 0x0226, 6: 0x69747461, 7: 0x300169ce 001229-074907: ANR7834S GPR 8: 0xd0299f20, 9: 0x6f0a0005, 10: 0x8000, 11: 0x7f7f7f7f 001229-074907: ANR7834S GPR 12: 0xf0044300, 13: 0x, 14: 0x, 15: 0x 001229-074907: ANR7834S GPR 16: 0x, 17: 0x, 18: 0x, 19: 0x 001229-074907: ANR7834S GPR 20: 0x, 21: 0x, 22: 0x, 23: 0x0001 001229-074907: ANR7834S GPR 24: 0x, 25: 0x, 26: 0x0223, 27: 0x550e5f18 001229-074907: ANR7834S GPR 28: 0x550e6720, 29: 0x0006, 30: 0x0001, 31: 0x69747461 001229-074907: ANR7834S IAR: 0xd0180db4 LR: 0x1007b150 CONTEXT: 0x550e5af0 001229-074907:0xD0180DB4 fwrite 001229-074907:0x1007B150 WriteRecord 001229-074907:0x1007E5FC icWriteVolumeHistory 001229-074907:0x1007E738 icRefreshHistoryFiles 001229-074907:0x104BDCB0 XiExport 001229-074907:0x1000CE00 StartThread 001229-074907:0xD011035C _pthread_body 001229-074907: ANR7833S Server thread 1 terminated in response to program abort. 001229-074907: ANR7833S Server thread 2 terminated in response to program abort. . . . Has anyone seen similar problems?
TSM-SQL-question..
Hello! Any SQL-experts out there? I have no experience with sql except from the few things I have learned from the tsm-implementation. I want to query the events-table for avents for, lets say the last 24 hours. Just like with the q events, only entries since today 00:00 are displayed as default. in the q events you can add begind=today-1, begint=now-24 and similar. Is it possible to do the same in a sql-statement? I have been playing around a little, but the only way I have come up with so far is to enter the fromdate explicitely like tsm: SUMOselect SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events where SCHED ULED_START \ '2000-11-30 12:13:14' works, and I thought also the following wold works, but only returns entries from after today 00:00: tsm: SUMOselect SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events where cast((current_timestamp-SCHEDULED_START)hours as decimal) 24 What am I missing here? Any suggestions/comments on this wold be appreciated.. Tom
Re: TSM-SQL-question..
Yes, I know. This is similar to my example.
However, I want to something similar to q event begint=now-24, which is a
generic thing, rather than using the actual date/time as input.
On Fri, 1 Dec 2000, James Thompson wrote:
Here is an example that might help.
'select * from EVENTS where scheduled_start'08/01/2000' and
scheduled_start'08/31/2000'
James Thompson
From: Tom Tann{s [EMAIL PROTECTED]
Reply-To: "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: TSM-SQL-question..
Date: Fri, 1 Dec 2000 17:59:17 +0100
Hello!
Any SQL-experts out there?
I have no experience with sql except from the few things I have learned
from the tsm-implementation.
I want to query the events-table for avents for, lets say the last 24
hours.
Just like with the q events, only entries since today 00:00 are displayed
as default.
in the q events you can add begind=today-1, begint=now-24 and similar.
Is it possible to do the same in a sql-statement?
I have been playing around a little, but the only way I have come up with
so far is to enter the fromdate explicitely like
tsm: SUMOselect SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events where
SCHED ULED_START \ '2000-11-30 12:13:14'
works, and I thought also the following wold works, but only returns
entries from after today 00:00:
tsm: SUMOselect SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events where
cast((current_timestamp-SCHEDULED_START)hours as decimal) 24
What am I missing here?
Any suggestions/comments on this wold be appreciated..
Tom
_
Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
Re: TSM-SQL-question..
OK, thanks.
I thought I hade been through the list, but to quick.
Took a new round, and this entry from Andy Raybeck was what I missed
before I posted my message.
Sorry. I should have studied the list more carefully before I posted..
You are correct. the design of the SELECT * FROM EVENTS was intended
to present only events for today (just like QUERY EVENTS). However,
I agree that the design ought to be changed to reflect the SQL
standard: that is, SELECT * FROM anytable presents *all* records
in that table, not just certain ones. In the case of QUERY EVENTS,
you can query events as far back as you want, but the status may
be "uncertain" if the events go back further than your event record
retention setting. So in my opinion, SELECT * FROM EVENTS should
show you all events that are available within the event record
retention timeframe.
This is a change I am lobbying for with the server developers.
Regards,
Andy
I hope your lobbying will work!
On Fri, 1 Dec 2000, Alex Paschal wrote:
Hello, Tom. The searchable archive (www.adsm.org) has a few examples of how
to answer this question. I used "sql select time date event actlog" as my
search string, and I came up with a bunch of messages. Here are just a few;
I would recommend going to the archive yourself and searching for something
that might be more specifically suited to your needs.
http://msgs.adsm.org/cgi-bin/get/adsm9811/988.html
http://msgs.adsm.org/cgi-bin/get/adsm0010/191.html
http://msgs.adsm.org/cgi-bin/get/adsm0008/487.html
By the way, has anyone else noticed they have a "spiffy" new interface at
the web site?
Thanks,
Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail
-Original Message-
From: Tom Tann{s [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 01, 2000 10:09 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM-SQL-question..
Yes, I know. This is similar to my example.
However, I want to something similar to q event begint=now-24, which is a
generic thing, rather than using the actual date/time as input.
On Fri, 1 Dec 2000, James Thompson wrote:
Here is an example that might help.
'select * from EVENTS where scheduled_start'08/01/2000' and
scheduled_start'08/31/2000'
James Thompson
From: Tom Tann{s [EMAIL PROTECTED]
Reply-To: "ADSM: Dist Stor Manager" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: TSM-SQL-question..
Date: Fri, 1 Dec 2000 17:59:17 +0100
Hello!
Any SQL-experts out there?
I have no experience with sql except from the few things I have learned
from the tsm-implementation.
I want to query the events-table for avents for, lets say the last 24
hours.
Just like with the q events, only entries since today 00:00 are displayed
as default.
in the q events you can add begind=today-1, begint=now-24 and similar.
Is it possible to do the same in a sql-statement?
I have been playing around a little, but the only way I have come up with
so far is to enter the fromdate explicitely like
tsm: SUMOselect SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events
where
SCHED ULED_START \ '2000-11-30 12:13:14'
works, and I thought also the following wold works, but only returns
entries from after today 00:00:
tsm: SUMOselect SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events
where
cast((current_timestamp-SCHEDULED_START)hours as decimal) 24
What am I missing here?
Any suggestions/comments on this wold be appreciated..
Tom
_
Get more from the Web. FREE MSN Explorer download :
http://explorer.msn.com
mttest / AIT-2
Hello! Does anyone know where I could find som information/documentation on the mttest-utility? I'm having some trouble with som newly attached AIT-2-drives. Does anyone else have any experiense using these drives? TSM-server is 3.7.3.1 running on an AIX 4.3.1.0
