No HBAs?
I have a P3000 library with 4 DLT7000 tape drives that are on my san. The TSM server (5.3 on AIX 5.3) sees them and is happy. The Win2003 storage agent (with an LSI 929x 2gb hba and 5.3 stg agt) sees the 4 tape drives, but I am getting the following errors. From actlog: 11/30/2005 08:57:14 ANR0408I Session 1156 started for server BULLZEYE_STORAGNT (Windows) (Tcp/Ip) for event logging. (SESSION: 1156) 11/30/2005 08:57:14 ANR1792W (Session: 1156, Origin: BULLZEYE_STORAGNT) HBAAPI vendor library failed to load or is missing. (SESSION: 1156) From Storage Agent: C:\Program Files\Tivoli\TSM\storageagenttsmdlst Tivoli Storage Manager -- Device List Utility Licensed Materials - Property of IBM 5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Computer Name: BULLZEYE OS Version: 5.2 OS Build #: 3790 TSM Device Driver: TSMScsi - Running No HBAs were detected. Reason: Unable to load HBA vendor library. TSM Name ID LUN Bus Port SSN WWN TSM Typ e Device Identifier mt0.1.0.40104- - GENERIC TAPEQUANTUM DLT7000 R138 mt0.2.0.40204- - GENERIC TAPEQUANTUM DLT7000 R138 mt0.3.0.40304- - GENERIC TAPEQUANTUM DLT7000 R138 mt0.4.0.40404- - GENERIC TAPEQUANTUM DLT7000 R138 Completed in: 0 days, 0 hours, 0 minutes, 1 seconds. Any ideas? Thanks again for everyone's help. DW
Atape Driver's Alternate Pathing and TSM
I am trying to take advantage of the Atape driver's Alternate Pathing feature. When I do a lsdev -Cc tape I see: rmt0 Available 0A-08-02-PRI IBM 3592 Tape Drive (FCP) rmt1 Available 0A-08-02-PRI IBM 3592 Tape Drive (FCP) rmt2 Available 0A-08-02-PRI IBM 3592 Tape Drive (FCP) rmt3 Available 0A-08-02-PRI IBM 3592 Tape Drive (FCP) rmt4 Available 0A-08-02-ALT IBM 3592 Tape Drive (FCP) rmt5 Available 0A-08-02-ALT IBM 3592 Tape Drive (FCP) rmt6 Available 0A-08-02-ALT IBM 3592 Tape Drive (FCP) rmt7 Available 0A-08-02-ALT IBM 3592 Tape Drive (FCP) smc0 Available 0A-08-02 IBM 3584 Library Medium Changer (FCP) But when I do a backup to the primary drives and then disconnect the cable to test a failure, the alternate drive(s) do not take over. Within TSM I have 4 drives (rmt0-3 defined). Am I missing a step? Thanks for your help. DW
Basic to Extended Edition
I am trying to set up a new TSM 5.3 server. No matter what I do it seems I am stuck in the Basic Edition of TSM. I have registered the Extended Edition and I can't figure out how to get TSM to run in the Extended Edition. The installation media was for Extended Edition. Did I forget to do something? Thanks. Dw tsm: TSMq lic Last License Audit: 03/07/05 15:49:10 Is Tivoli Storage Manager for Data Retention in use ?: No Is Tivoli Storage Manager for Data Retention licensed ?: No Is Tivoli Storage Manager Basic Edition in use: Yes Is Tivoli Storage Manager Basic Edition licensed: Yes Is Tivoli Storage Manager Extended Edition in use: No Is Tivoli Storage Manager Extended Edition licensed: Yes Server License Compliance: Valid =lslpp -l|grep tsm tivoli.tsm.devices.aix5.rte tivoli.tsm.license.cert5.3.0.0 COMMITTED IBM Tivoli Storage Manager tivoli.tsm.license.rte 5.3.0.0 COMMITTED IBM Tivoli Storage Manager 32 tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server tivoli.tsm.server.com 5.3.0.2 COMMITTED IBM Tivoli Storage Manager tivoli.tsm.server.rte 5.3.0.2 COMMITTED IBM Tivoli Storage Manager 32 tivoli.tsm.server.webcon 5.3.0.2 COMMITTED IBM Tivoli Storage Manager Web tivoli.tsm.devices.aix5.rte tivoli.tsm.server.com 5.3.0.2 COMMITTED IBM Tivoli Storage Manager tivoli.tsm.server.rte 5.3.0.2 COMMITTED IBM Tivoli Storage Manager 32
RMT vs MT block sizes
Does anyone know where or if you can change the block size for the mt devices? Via smit or chdev I can change the rmt devices, but no matter what I set the rmt device block size to the mt devices are built with a 1024 block size. tsmserver:/=lsattr -El rmt0 block_size 64 BLOCK size (0=variable length)True delay 45 Set delay after a FAILED command True density_set_1 0 DENSITY setting #1True density_set_2 0 DENSITY setting #2True extfm yesUse EXTENDED file marks True location Location LabelTrue lun_id 0x1Logical Unit Number IDFals e mode yesUse DEVICE BUFFERS during writes True node_name 0x10068d02efc0 FC Node Name Fals e res_supportno RESERVE/RELEASE support True ret_error no RETURN error on tape change or reset True rwtimeout 144Set timeout for the READ or WRITE command True scsi_id0x110efSCSI ID Fals e var_block_size 0 BLOCK SIZE for variable length supportTrue ww_name0x10068d02efc0 FC World Wide NameFals e tsmserver:/=lsattr -El mt0 FCPORT_ID 0x110efFC Port ID True LUNMAP_ID 0x1Mapped LUN ID of the device True PRODUCT_ID DLT7000Product ID of the deviceFalse WW_NAME0x10068d02efc0 WW Name of the Port False block_size 1024 Block Size True Thanks DW
GigE Conversion
We just upgraded our TSM server and a few clients with GigE adapters. When I FTP a file from client to server, I am seeing approximately 65MB/sec. When I backup the client I am only seeing 11 MB/sec. Is there a setting that I forgot to set/adjust? Thanks for any help. DW Server AIX 5.1 ML4 TSM 5.2.3 Client Win2003 server TSM 5.2.3
Re: GigE Conversion
The file size that I tested was 500MB. While the backup is running at 11 MB/sec I used FTP to send another large file down the same pipes and it transfered at 49 MB/sec. So I know that the pipes between server and client will handle the load. I have adjusted the TCPWINDOWSIZE to 64 on the server and 63 on the client according to the Tuning Guide. I also increased the client's TCPBUFFSIZE from 16 to 32. When I backed up on the 100MB network we were seeing 7-8MB/sec, so we have increased performance a little. There is no client compression. Thanks for all of your input. DW
Re: GigE Conversion
The Windows client is backing up to a disk storage pool on a Clariion array. There is no other activity on the TSM server. Thanks. DW
TSM Server forcing compression?
Why is the TSM server forcing compression on for my aix client? Is it because it is the same box as the server? I am using COMMMETHOD of TCPIP not SHAREDMEM, so I assume that the data is being sent across the lan like any other client. from the baclient: Node Name: NY_AIX1 Session established with server NY_AIX1: AIX-RS/6000 Server Version 5, Release 2, Level 3.0 Data compression forced on by the server client is as 5.2.3 as well. Aix is 5.2.0.4 Thanks DW
Re: TSM Server forcing compression?
Thanks Mark. It was set to compress there. DW -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dameon White Why is the TSM server forcing compression on for my aix client? Is it because it is the same box as the server? I am using COMMMETHOD of TCPIP not SHAREDMEM, so I assume that the data is being sent across the lan like any other client. When you run Q NODE NY_AIX1 F=D, what is the compression parameter set to? -- Mark Stapleton
Internal error in Windows Installer
I am trying to upgrade my 5.1.5.0 client code to 5.1.6.0 and I keep getting this error: -2147220998: Internal error in Windows Installer The box is WinNT 4.00.1381 I was able to upgrade the client code code from 4.2.1.11 to 5.1.5.0 successfully only when I used the base TSM 5.1.5.0 client code CD. Thanks for any help. DW
[no subject]
My TSM server is 4.2.3.0 on AIX 4.3.3 I am seeing inaccurate values for elapsed processing time for multiple os platforms, multiple os levels, and multiple tsm client levels. I have included one example. Has anyone else seen similar inaccuracies? If looking to see how long my backup took, I assume I should start disregarding the elapsed processing time that TSM is reporting. Does anyone know of a more accurate place one should find such data? 02/27/03 21:00:02 ANR2561I Schedule prompter contacting filesvr01 (session 36725) to start a scheduled operation. 02/27/03 21:00:03 ANR0406I Session 36726 started for node filesvr01 (HPUX) (Tcp/Ip 10.172.69.2(54195)). 02/27/03 21:00:04 ANR0406I Session 36728 started for node filesvr01 (HPUX) (Tcp/Ip 10.172.69.2(54196)). 02/27/03 21:25:56 ANR0403I Session 36728 ended for node filesvr01 (HPUX). 02/27/03 21:25:58 ANE4952I (Session: 36726, Node: filesvr01) Total number of objects inspected: 62,102 02/27/03 21:25:58 ANE4954I (Session: 36726, Node: filesvr01) Total number of objects backed up: 218 02/27/03 21:25:58 ANE4958I (Session: 36726, Node: filesvr01) Total number of objects updated: 0 02/27/03 21:25:58 ANE4960I (Session: 36726, Node: filesvr01) Total number of objects rebound: 0 02/27/03 21:25:58 ANE4957I (Session: 36726, Node: filesvr01) Total number of objects deleted: 0 02/27/03 21:25:58 ANE4970I (Session: 36726, Node: filesvr01) Total number of objects expired: 1 02/27/03 21:25:58 ANE4959I (Session: 36726, Node: filesvr01) Total number of objects failed: 0 02/27/03 21:25:58 ANE4961I (Session: 36726, Node: filesvr01) Total number of bytes transferred: 109.31 MB 02/27/03 21:25:58 ANE4963I (Session: 36726, Node: filesvr01) Data transfer time: 1,454.74 sec 02/27/03 21:25:58 ANE4966I (Session: 36726, Node: filesvr01) Network data transfer rate: 76.95 KB/sec 02/27/03 21:25:58 ANE4967I (Session: 36726, Node: filesvr01) Aggregate data transfer rate: 72.02 KB/sec 02/27/03 21:25:58 ANE4968I (Session: 36726, Node: filesvr01) Objects compressed by: 0% 02/27/03 21:25:58 ANE4964I (Session: 36726, Node: filesvr01) Elapsed processing time: 00:00:54 02/27/03 21:25:58 ANR2507I Schedule FILESVR_BU for domain DALLAS started at 02/27/03 21:00:00 for node filesvr01 completed successfully at 02/27/03 21:25:58. 02/27/03 21:25:58 ANR0403I Session 36726 ended for node filesvr01 (HPUX). Thanks for your patience as I rant. Dameon
Innaccurate Elapsed Processing Time
Sorry about the omitted Subject line. Andy, There are several nodes that are 4.1.2.x that are having the issues. But, there are also several Win2k nodes with client code 4.2.2.0 that are also experiencing this issue Dameon. You do not indicate which version of the TSM client you are running. This is important, as the elapsed processing time is being reported to the servr by the client. There was a problem back in version 4.1.2 where elapsed processing time was not being reported correctly (it was too short, as you are seeing). The APAR number is IC29212. Maybe this is the problem. You can find more info on this by going to http://www.ibm.com and entering the APAR number as a search argument (top of the page). Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply) The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. Dameon White [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02/28/2003 08:59 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject: My TSM server is 4.2.3.0 on AIX 4.3.3 I am seeing inaccurate values for elapsed processing time for multiple os platforms, multiple os levels, and multiple tsm client levels. I have included one example. Has anyone else seen similar inaccuracies? If looking to see how long my backup took, I assume I should start disregarding the elapsed processing time that TSM is reporting. Does anyone know of a more accurate place one should find such data? 02/27/03 21:00:02 ANR2561I Schedule prompter contacting filesvr01 (session 36725) to start a scheduled operation. 02/27/03 21:00:03 ANR0406I Session 36726 started for node filesvr01 (HPUX) (Tcp/Ip 10.172.69.2(54195)). 02/27/03 21:00:04 ANR0406I Session 36728 started for node filesvr01 (HPUX) (Tcp/Ip 10.172.69.2(54196)). 02/27/03 21:25:56 ANR0403I Session 36728 ended for node filesvr01 (HPUX). 02/27/03 21:25:58 ANE4952I (Session: 36726, Node: filesvr01) Total number of objects inspected: 62,102 02/27/03 21:25:58 ANE4954I (Session: 36726, Node: filesvr01) Total number of objects backed up: 218 02/27/03 21:25:58 ANE4958I (Session: 36726, Node: filesvr01) Total number of objects updated: 0 02/27/03 21:25:58 ANE4960I (Session: 36726, Node: filesvr01) Total number of objects rebound: 0 02/27/03 21:25:58 ANE4957I (Session: 36726, Node: filesvr01) Total number of objects deleted: 0 02/27/03 21:25:58 ANE4970I (Session: 36726, Node: filesvr01) Total number of objects expired: 1 02/27/03 21:25:58 ANE4959I (Session: 36726, Node: filesvr01) Total number of objects failed: 0 02/27/03 21:25:58 ANE4961I (Session: 36726, Node: filesvr01) Total number of bytes transferred: 109.31 MB 02/27/03 21:25:58 ANE4963I (Session: 36726, Node: filesvr01) Data transfer time: 1,454.74 sec 02/27/03 21:25:58 ANE4966I (Session: 36726, Node: filesvr01) Network data transfer rate: 76.95 KB/sec 02/27/03 21:25:58 ANE4967I (Session: 36726, Node: filesvr01) Aggregate data transfer rate: 72.02 KB/sec 02/27/03 21:25:58 ANE4968I (Session: 36726, Node: filesvr01) Objects compressed by: 0% 02/27/03 21:25:58 ANE4964I (Session: 36726, Node: filesvr01) Elapsed processing time: 00:00:54 02/27/03 21:25:58 ANR2507I Schedule FILESVR_BU for domain DALLAS started at 02/27/03 21:00:00 for node filesvr01 completed successfully at 02/27/03 21:25:58. 02/27/03 21:25:58 ANR0403I Session 36726 ended for node filesvr01 (HPUX). Thanks for your patience as I rant. Dameon
ACSLS or Native TSM manager
We just bought a used STK L700 with 4 DLT7000 drives. We have TSM 5.1.5.2 on AIX and I am confused as to why/if I would need to use ACSLS to manage the library? Does ACSLS provide any features not available with TSM's native library manager? We will want to share this L700 with another TSM server and I can't see why native scsci library won't be a good choice? Any advice? Dameon
System Objects and Cleanup Backupgroups
My TSM server is at 4.2.3.0 and we want to upgrade to 5.1.x of TSM. But we have over 50 million orphaned SYSTEM OBJECTS that we have been trying to delete via the CLEANUP BACKUPGROUPS command. We tried to upgrade with the orphans and after 72 hours we backed out. Now we are tryng to delete the orphans, but the problem is that we are only cleaning up 10k-25k per night. At this rate we will not be able to upgrade to 5.1.x for at least 10-15 years. Does anyone have any idea how I can get out of this situation? Can I delete the SYSTEM OBJECT filespaces all together and gamble that I won't have to restore the registry that day? Will deleting the good system objects help with the orphans? Thanks. Dameon
Windows OS Level
Does anyone have a x-ref of Windows OS level to TSM's OS level in the node table. I think NT 4 is oslevel=4.0 and win2k is oslevel=5. How about xp,98, or 95? Thanks for your help. Dameon
