Können wir mal drüber reden
Karl, wissen wir selber, oder ? Achim > -Ursprüngliche Nachricht- > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Auftrag von > Tab Trepagnier > Gesendet: Freitag, 22. Juli 2005 19:39 > An: ADSM-L@VM.MARIST.EDU > Betreff: Re: ANRD pkthread.c(1037): ThreadId<31> Unable to cr eate > new Thread > > > Jane, > > I know of no such limit. I'm running a 1 GB buffer pool on my 4 GB TSM > AIX server with no issues. The only thing to watch is that the buffer > pool is considered "process" memory by AIX. So the default MaxPerm% of > 80% means that AIX allows process to have priority on 1 GB with the other > 3 GB given preference for files. Because in my case, process memory is > 25% + whatever AIX and TSM themselves use, quite a lot of memory would be > paged out to disk. So you have to adjust MaxPerm% down to allow AIX and > TSM to have enough process memory to avoid that paging activity. If you > understand what's going on that should be a one-time operation. > > Good luck. > > Tab Trepagnier > TSM Administrator > Laitram, L.L.C. > > > "ADSM: Dist Stor Manager" wrote on 07/21/2005 > 05:13:54 AM: > > > Hi - > > > > In the Performance Tuning Guide this states that the 'buffer pool size > may > > not exceed 10% of physical memory on AIX' > > > > Also, Recommended values are included in a table dependent on your > amount of > > physical memory, but max in MB is 256 assuming you have 2048MB of > memory. > > > > They may have something that has been updated that goes up for higher > > memory?? > > > > Jane. > > > > > > -Original Message- > > From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] > > Sent: 21 July 2005 11:11 > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] ANRD pkthread.c(1037): ThreadId<31> Unable to > > create new Thread > > > > Hi, > > > > I´m not sure if there are some upper limit on Bufpoolsize, but 1024000 > seems > > rather high to me... One of our p650, aix, with 16GB of ram just use a > > bufpoolsize of 786432. > > > > What happens if you reset bufpool to it´s original value, and re-run the > > backups? > > > > > > //Henrik > > > > > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > > Nielsen, Bo > > Sent: den 21 juli 2005 10:54 > > To: ADSM-L@VM.MARIST.EDU > > Subject: ANRD pkthread.c(1037): ThreadId<31> Unable to create new > > Thread > > > > Hi > > > > last night I have a couple of nodes, who failed with > >Server Detected Error. > > In TSM server activity log I found these message: > > > > 07/21/2005 03:28:03 ANRD pkthread.c(1037): ThreadId<31> Unable to > create > > new Thread. CreateThread error.Callchain: 104EAD79 outTextf()+1529 <- > > 10007040 pkLogicAbort()+A30 <- 15E3D688 Unknown <- 10A7CC08 > > outTextf()+5933B8 <- > > 07/21/2005 03:28:04 (31) Context report 07/21/2005 03:28:04 (31) Thread > > SessionThread (23) is a child thread related to: 31 07/21/2005 03:28:04 > (23) > > Generating TM Context Report: (struct=tmTxnDesc) (slots=256) 07/21/2005 > > 03:28:04 (23) *** no transactions found > > *** > > 07/21/2005 03:28:04 (23) Generating Database Transaction Table Context: > > 07/21/2005 03:28:04 (23) *** no transactions found > > *** > > 07/21/2005 03:28:04 (23) Generating SM Context Report: 07/21/2005 > 03:28:04 > > (23) Session 195354: Type=Node, Id=CDKALB030 07/21/2005 03:28:04 (23) > > Platform=WinNT, NodeId=254, Owner= 07/21/2005 03:28:04 (23) SessType=5, > > Index=37, TermReason=0 07/21/2005 03:28:04 (23) RecvWaitTime=0.000 > > (samples=0) 07/21/2005 03:28:04 (23) Backup Objects ( bytes ) Inserted: > 0 ( > > 0.0 ) 07/21/2005 03:28:04 (23) Backup Objects ( bytes ) Restored: 0 ( > 0.0 ) > > 07/21/2005 03:28:04 (23) Archive Objects ( bytes ) Inserted: 0 ( 0.0 ) > > 07/21/2005 03:28:04 (23) Archive Objects ( bytes ) Retrieved: 0 ( 0.0 ) > > 07/21/2005 03:28:04 (23) Last Verb ( Ping ), Last Verb State ( Sent ) > > 07/21/2005 03:28:04 (23) Generating AS Vol Context Report: > > 07/21/2005 03:28:04 (23) No mounted (or mount in progress) volumes. > > 07/21/2005 03:28:04 (23) Generating ssSession Context Report: > > 07/21/2005 03:28:04 (23) Storage Service Sessions: > > 07/21/2005 03:28:04 (23) Session 134454 --> BufConfig=None, > TransBufSize=0, > > SplitBuf=False, WrCount=0, WrBufIsEmpty=False, > > WrBufIsFull=False, SourceRc=0, SinkRc=0, AuxCreated=Fals- e, > AuxBegin=False, > > AuxIsSink=False, AuxIdle=False, > > AuxTerminate=False > > 07/21/2005 03:28:04 (23) Leased Volumes: > > 07/21/2005 03:28:04 (23) (none) > > 07/21/2005 03:28:04 (23) Excluded VolIds: > > 07/21/2005 03:28:04 (23) (none) > > 07/21/2005 03:28:04 > > 07/21/2005 03:28:04 (23) Generating ssOpenSeg Context Report: > > 07/21/2005 03:28:04 (23) No storage service segments found. > > 07/21/2005 03:28:04 (23) Generating BF Copy Control Context Report: > > 07/21/2005 03:28:04 (23) No global copy control blocks. > > 07/21/2005 03:28:04 07/21/2005 03:28:05 (31) Thread S
RMAN question
Hi All, Iam new to TSM and even more newer to TDP (RMAN). Can anyone please help me in diagnosing as to how RMAN purging works and how does it deal with partial/incomplete backups.. Iam facing a problem currently as the TSM occupancy for one of our TDP clients has increased by over 1TB in past 5 days wheres the database itself hasn't grown to that extent.. rgds, Aleem
Re: tape usage
Hi, After backups have run and expiration has occurred, you will notice the PCT_RECLAIMABLE value for tapes increase, along with tapes moving to a 'pending' state where data has completely expired from the tape. 'pending' tapes will move to 'scratch' after the reuse delay for the storage pool has passed, at this point your count of scratch tapes will increase. Matt. -- Matthew Warren. [EMAIL PROTECTED] [EMAIL PROTECTED] http://tsmwiki.com/tsmwiki/MatthewWarren -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Rosette Sent: Friday, July 22, 2005 5:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: tape usage Hello TSMer's I have a 3494 tape library that is maxed out. We have taken out the last 60 day usage tapes. We are not decreasing our big backups (Oracle DB's) from 15 versions to 7 versions. The question I ask y'all is the one they ask me. How can I tell that I have received extra tapes back from cutting the version in half? Thank You again in advance for the answer, Bill Rosette WWJD ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Powergen Retail Ltd is authorised and regulated by the Financial Services Authority for the sale and service of general insurance products. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Replaced tape drive now device type 'unknown'
We have 3 AIT-2 drives within a Qualstar 412600 library. After having a drive replaced, 'q dri' is now showing it as device type 'UNKNOWN' rather than '8MM' - and the define path command is failing with : << Message number 8972 not available for language /USR/LIB/NLS/MSG/EN_US/ >> Usually when a drive is replaced, I delete the path and drive and recreate these ( since TSM 5.2 ? ) as the serial number of the drive no longer matches. Up to now this has always worked. The drive was detected OK by AIX and I have been able to use tar directly from AIX to write and read from a tape manually inserted. I have removed and recreated the TSM device 'mt1' but still the problem re-occurs. Is this due to the tape drive failing to respond correctly to some SCSI enquiry commnd that TSM is submitting ? lscfg returns same output from a 'good' and a 'bad' drive : lscfg -vl rmt0 rmt0 U0.1-P1-I1/Z1-A1 Other SCSI Tape Drive ManufacturerSONY Machine Type and Model..SDX-500C Serial Number... Device Specific.(Z3) 'q dri f=d' shows a serial number for the 'good' drives. Is there any way of persuading TSM to use this drive ? Or is there something wrong with this drive ? Using TSM 5.2.3 on AIX 5.2 . +--+ Steven Bridge Systems Group, Information Systems, EISD University College London
Re: Multiple versions of TSM server on one AIX host
Okay, I got no responses to the original posting, so I thought I'd try this: if anyone is successfully running multiple TSM servers at different maintenance levels on a single AIX host, would you post some details on your setup? TSM server startup scripts, relevant dsmserv.opt entries, directory structure, and anything else that's required to accomplish this? Thanks very much, Bill -- Forwarded message -- Date: Wed, 20 Jul 2005 13:34:20 -0500 (CDT) From: Bill Kelly <[EMAIL PROTECTED]> To: ADSM discussion list Subject: Multiple versions of TSM server on one AIX host Hi, Currently running TSM server 5.2.3.0 on AIX 5.2. We've been running multiple TSM servers on a single AIX host with no problems. We use the DSMSERV_CONFIG and DSMSERV_DIR variables to point to different dsmserv.opt files and server directories, respectively. What I'm trying to do now is set things up to run a test TSM server at a newer maintenance level than the production TSM servers, again all on the same AIX host. I seem to be stuck in the area of the message repository. My (limited) understanding of this is that the installation of the TSM server puts two files in the /usr/lib/nls/msg/en_US directory - dsmserv.cat and dsmserv.hlp. These files differ for each version of the server code, and so I have to ensure that each TSM server gets the correct version of the message repository files. I figured I'd start by getting a test TSM server looking at a separate copy of the 5.2.3.0 message repository. Once I have the mechanism in place and working, I can move the test server to the new (5.3.1.2) version. Based on past postings to this list, here's what I've tried: - in the test TSM server's dsmserv.opt file, specify 'LANG en_US_tsm5230' - in /usr/lib/nls/loc, create the following link: en_US_tsm5230 -> /usr/lib/nls/loc/en_US - in /usr/lib/nls/msg, create a new directory 'en_US_tsm5230' containing copies of the 5.2.3.0 dsmserv.cat and dsmserv.hlp files When I start the test TSM server, I'm getting the following message: ANRW Failure opening message repository for locale en_US_tsm5230(-1). Using default message repository. Any ideas as to what I'm doing wrong? Am I even on the right track?? Or is there another/better way to accomplish my goal? Thanks in advance, Bill Bill Kelly Auburn University OIT 334-844-9917
Re: Replaced tape drive now device type 'unknown'
Steven, I had the same kind of problem on a TSM 5.3.1 server recently (other hardware, but same behaviour), and had to restart the application in order to get the drive recognized ... If you can afford some minutes downtime, worth to give it a try ;-) Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steven Bridge Sent: Monday, 25 July, 2005 16:40 To: ADSM-L@VM.MARIST.EDU Subject: Replaced tape drive now device type 'unknown' We have 3 AIT-2 drives within a Qualstar 412600 library. After having a drive replaced, 'q dri' is now showing it as device type 'UNKNOWN' rather than '8MM' - and the define path command is failing with : << Message number 8972 not available for language /USR/LIB/NLS/MSG/EN_US/ >> Usually when a drive is replaced, I delete the path and drive and recreate these ( since TSM 5.2 ? ) as the serial number of the drive no longer matches. Up to now this has always worked. The drive was detected OK by AIX and I have been able to use tar directly from AIX to write and read from a tape manually inserted. I have removed and recreated the TSM device 'mt1' but still the problem re-occurs. Is this due to the tape drive failing to respond correctly to some SCSI enquiry commnd that TSM is submitting ? lscfg returns same output from a 'good' and a 'bad' drive : lscfg -vl rmt0 rmt0 U0.1-P1-I1/Z1-A1 Other SCSI Tape Drive ManufacturerSONY Machine Type and Model..SDX-500C Serial Number... Device Specific.(Z3) 'q dri f=d' shows a serial number for the 'good' drives. Is there any way of persuading TSM to use this drive ? Or is there something wrong with this drive ? Using TSM 5.2.3 on AIX 5.2 . +--+ Steven Bridge Systems Group, Information Systems, EISD University College London
TSm label issue
Maybe somebody here can help me out Stupid question But here goes. I have made some old tapes scratch I tried to use one this morning. Tsm took a while said it was writing then dropped the process. The tape now comes up as Empty when I do a q vol Any help would be appreciated - Music from EMI This e-mail including any attachments is confidential and may be legally privileged. If you have received it in error please advise the sender immediately by return email and then delete it from your system. The unauthorised use, distribution, copying or alteration of this email is strictly forbidden. If you need assistance please contact us on +44 20 7795 7000. This email is from a unit or subsidiary of EMI Group plc. Registered Office: 27 Wrights Lane, London W8 5SW Registered in England No 229231. -
Windows Server 2003 RESTORE PROBLEM ANS4005E
TSM Server AIX 5.2.4.0 / AIX 5.3 TSM B/A Client for Windows 5.2.2 Windows Server 2003 v 5.02 I am receiving the following error trying to restore SYSTEMSTATE. I get same error from GUI and cmd line. Any suggestions would be appreciated... tsm> q systemstate Size Backup DateMgmt Class A/I File ----- --- 488,430,629 B 11/22/2004 22:07:34DEFAULT A FULL SYSTEM STATE\SYSS TATE tsm> restore systemstate -verbose Restore System State using shadow copy... Restore System State: 'System Files'. Restore System State: 'Registry'. Restore System State: 'Active Directory'. Restore System State: 'System Volume'. Restore System State: 'COM+ Database'. ** Interrupted ** ANS1114I Waiting for mount of offline media. Restoring 1,612 SYSTEM STATE\adsm.sys\xml.state\COMPDB.xml [Done] Restoring 1,746 SYSTEM STATE\adsm.sys\xml.state\NTDS.xml [Done] Restoring 4,638 SYSTEM STATE\adsm.sys\xml.state\REGISTRY.xml [Done] Restoring 427,062 SYSTEM STATE\adsm.sys\xml.state\SYSFILES.xml [Done] Restoring 2,330 SYSTEM STATE\adsm.sys\xml.state\SYSVOL.xml [Done] Restoring 3,034 SYSTEM STATE\adsm.sys\xml.state\tsm.xml [Done] ANS1899I * Examined 1,000 files * ANS1899I * Examined 2,000 files * Total number of objects restored: 6 Total number of objects failed: 0 Total number of bytes transferred:431.66 KB Data transfer time:0.42 sec Network data transfer rate:1,022.89 KB/sec Aggregate data transfer rate: 1.41 KB/sec Elapsed processing time: 00:05:05 ANS4005E Error processing '': file not found< any ideas on this? Thanks in advance!!
Re: Windows Server 2003 RESTORE PROBLEM ANS4005E
Try searching the IBM web site (www.ibm.com) using criteria: +ANS4005E +restore and you'll probably find at least one hit that is applicable. 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] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" wrote on 2005-07-25 11:35:19: > TSM Server AIX 5.2.4.0 / AIX 5.3 > > TSM B/A Client for Windows 5.2.2 > > Windows Server 2003 v 5.02 > > I am receiving the following error trying to restore SYSTEMSTATE. I get > same error from GUI and cmd line. Any suggestions would be appreciated... > > > tsm> q systemstate > Size Backup DateMgmt Class A/I File > ----- --- >488,430,629 B 11/22/2004 22:07:34DEFAULT A FULL SYSTEM > STATE\SYSS > TATE > tsm> restore systemstate -verbose > Restore System State using shadow copy... > Restore System State: 'System Files'. > > Restore System State: 'Registry'. > > Restore System State: 'Active Directory'. > > Restore System State: 'System Volume'. > > Restore System State: 'COM+ Database'. > > ** Interrupted ** > ANS1114I Waiting for mount of offline media. > Restoring 1,612 SYSTEM STATE\adsm.sys\xml.state\COMPDB.xml > [Done] > > Restoring 1,746 SYSTEM STATE\adsm.sys\xml.state\NTDS.xml [Done] > Restoring 4,638 SYSTEM STATE\adsm.sys\xml.state\REGISTRY.xml > [Done] > > Restoring 427,062 SYSTEM STATE\adsm.sys\xml.state\SYSFILES.xml > [Done] > > Restoring 2,330 SYSTEM STATE\adsm.sys\xml.state\SYSVOL.xml > [Done] > > Restoring 3,034 SYSTEM STATE\adsm.sys\xml.state\tsm.xml [Done] > ANS1899I * Examined 1,000 files * > ANS1899I * Examined 2,000 files * > > Total number of objects restored: 6 > Total number of objects failed: 0 > Total number of bytes transferred:431.66 KB > Data transfer time:0.42 sec > Network data transfer rate:1,022.89 KB/sec > Aggregate data transfer rate: 1.41 KB/sec > Elapsed processing time: 00:05:05 > ANS4005E Error processing '': file not found< any ideas > on this? > > > > > Thanks in advance!!
problems defining path dell 136t
Hey all, Just wondering if anyone has come across an issue defining a Dell Powervault 136T Library within TSM (v5.2.1.2)? I've managed to define the library no problem but the path keeps having I/O failures when trying to be defined. The library has the latest firmware v3.33, trying the latest drivers v7.0 (dell, dated 15/11/2004), and it's running on a win 2003 OS. The TSM Device Driver (tsmscsi.sys v5.2.3.5122 & tsmscsi.exe v5.2.2.2056) sees the library and all the drives no problem. A noteable problem is when trying to run the Device Wizard it does not see the devices at all. Any thoughts? Thanks everyone! Curt Watts PS. RSM is turned off and shouldn't be a factor. ___ Curt Watts Network Analyst, Capilano College [EMAIL PROTECTED]
Re: problems defining path dell 136t
Possible connection: I have a customer that just upgraded the firmware to latest levels on his Dell PowerVault 128T, and he could no longer access his drives. I haven't heard from him, but I mentioned that he might have to back off on the firmware level. Again, I don't know if yours is the same problem, but it sounds similar. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 IBM Certified Advanced Technical Expert (CATE) AIX Office 262.521.5627 >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On >Behalf Of Curt Watts >Sent: Monday, July 25, 2005 6:40 PM >To: ADSM-L@VM.MARIST.EDU >Subject: problems defining path dell 136t > >Hey all, > >Just wondering if anyone has come across an issue defining a Dell >Powervault 136T Library within TSM (v5.2.1.2)? I've managed to define >the library no problem but the path keeps having I/O failures when >trying to be defined. > >The library has the latest firmware v3.33, trying the latest drivers >v7.0 (dell, dated 15/11/2004), and it's running on a win 2003 OS. > >The TSM Device Driver (tsmscsi.sys v5.2.3.5122 & tsmscsi.exe >v5.2.2.2056) sees the library and all the drives no problem. >A noteable >problem is when trying to run the Device Wizard it does not see the >devices at all. > >Any thoughts? > >Thanks everyone! > >Curt Watts > > > >PS. RSM is turned off and shouldn't be a factor. > >___ >Curt Watts >Network Analyst, Capilano College >[EMAIL PROTECTED] >
