Re: dsm.sys
On 10/23/2015 3:18 PM, David Ehresman wrote: On AIX, can I put dsm.sys in a directory other than the ba install directory? If so, how do I point to it? su cd /[installdirectory] ln -s /[yourlocaldirectory]/dsm.sys ln -s /[yourlocaldirectory]/dsm.opt jim.o...@yale.edu (c#203.494.9201)
Re: tsm server failes to start in foreground!!
Login as TSM/DB2 instance owner to run db2start: [see 4th message line from failure below] ANR0151W Database manager fails to start. For more information about the failure, issue the db2start command. jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030) On 10/22/2014 11:00 AM, Tim Brown wrote: TSM service fails to start, tried running in foreground. Any ideas!! C:\Program Files\Tivoli\TSM\serverdsmserv -k server1 ANR7800I DSMSERV generated at 16:13:56 on Oct 19 2012. Tivoli Storage Manager for Windows Version 6, Release 3, Level 3.000 Licensed Materials - Property of IBM (C) Copyright IBM Corporation 1990, 2011. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file c:\program files\tivoli\tsm\server1\dsmserv.opt. ANR4726I The ICC support module has been loaded. ANR0990I Server restart-recovery in progress. ANR0151W Database manager fails to start. For more information about the failure, issue the db2start command. ANRD_2785511358 RdbStartInstance(rdbinst.c:1310) Thread0: Add codes to msg DB_DATABASE_S- TART_FAILED sqlCode -1397. ANRD Thread0 issued message from: ANRD Thread0 07FEEAA09839 OutDiagToCons()+159 ANRD Thread0 07FEEAA033BC outDiagfExt()+fc ANRD Thread0 07FEEA7D72FB RdbStartInstance()+41b ANRD Thread0 07FEEA73B522 dbiInit()+152 ANRD Thread0 07FEEA20D35D AdmServerMonitorThread()+73d ANRD Thread0 07FEEA20EAAB admStartServer()+cb ANRD Thread0 07FEEA1F3474 adsmMain()+e84 ANRD Thread0 00013FE0111B main()+9b dsmserv.c:241 ANRD Thread0 00013FE028DA __tmainCRTStartup()+11a crtexe.c:555 ANRD Thread0 76CD652D BaseThreadInitThunk()+d ANRD Thread0 76E0C521 RtlUserThreadStart()+21 ANR0172I rdbdb.c(1650): Error encountered performing action InstanceStop. ANR0162W Supplemental database diagnostic information: -1032:SQLSTATE 57019: The statement was not successful, because of a problem with a resource. :-1032 (SQL1032N No start database manager command was issued. SQLSTATE=57019 Tim Brown
Re: TSM 7.1 usage of volumes for dedupe
Martha, !!Maybe your volumes are *not* really empty: retry with... Query CONtent [volname] FOLLOWLinks=Yes[especially for deduplicated content] See Help Query CONtent for details ... including default: FOLLOWLinks=No jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030) On 10/22/2014 1:05 PM, Martha M McConaghy wrote: Yup, they are really empty. /data0/0D57.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full tsm: TSMPRIMESERVERq content /data0/0D57.BFS Session established with server TSMPRIMESERVER: Linux/x86_64 Server Version 7, Release 1, Level 1.0 Server date/time: 10/22/2014 12:54:58 Last access: 10/22/2014 11:36:27 ANR2034E QUERY CONTENT: No match found using this criteria. ANS8001I Return code 11. Martha On 10/22/2014 12:08 PM, Michael Roesch wrote: Hi Martha, have you run query content on some of the volumes to see, if they are really empty? Michael On Wed, Oct 22, 2014 at 5:47 PM, Martha M McConaghy martha.mccona...@marist.edu wrote: We just installed TSM 7.1 during the summer and have been working on migrating our backups over from our old v5.5 system. We are using deduplication for our main storage pool and it seems to work great. However, I'm concerned about how it is using the volumes in the storage pool. Since we never ran v6, I don't know if this is normal or if we have stumbled upon a bug in 7.1. So, I figured I'd ask on the list and see if any of you have some insight. Our dedupe storage pool is dev class FILE, of course. It is set up to acquire new scratch volumes as it needs over time. Originally, I had the max scratch vols allowed at 999, which seemed reasonable. After about a month, though, we hit that max and I had to keep raising it. When I query the volumes belonging to this pool, I see many, many of them in full status, with pct util=0: Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status --- -- - - /data0/0B55.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0B8F.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0BCF.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0BD6.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C16.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C2A.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C63.BFS DEDUPEPOOL FILE 49.9 G 100.0 Full /data0/0C72.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C79.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C84.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C8C.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C93.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0C9A.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0CA1.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full /data0/0CB3.BFS DEDUPEPOOL FILE 50.0 G 0.0 Full Literally, hundreds of them. I run reclamations, but these volumes never get touched nor reclaimed. Seems to me that they should. I've gone over the admin guide several times, but have found nothing touching on this. We just applied the 7.1.1.0 updates, but that has not helped either. If I do a move data on each, they will disappear. However, more will return to take their place. Anyone seen this before, or have any suggestions? Martha -- Martha McConaghy Marist: System Architect/Technical Lead SHARE: Director of Operations Marist College IT Poughkeepsie, NY 12601 -- Martha McConaghy Marist: System Architect/Technical Lead SHARE: Director of Operations Marist College IT Poughkeepsie, NY 12601
Re: Deduplication number of chunks waiting in queue continues to rise?
Sergio and Wanda, Thanks for your posts! I opened PMR 10702,L6Q,000 a couple weeks ago for slow performance [recently completely fell off the cliff!] with our SRV3 TSM v6.3.4.200 service that *was* successfully doing client+server deduplication for 72TB BackupDedup STGpool on NetApp FC [soon to be 3par] FC disks. I did not previously know about this command... SHow DEDUPDelinfo now shows 7M enqueued dedupdel chunks @ SRV3 TSM. I just requested escalation to consider whether TSMv6.3.4.207 efix will help us. Thanks again... hoping to re-post with better performance results soon! jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030) On 12/20/2013 10:38 AM, Sergio O. Fuentes wrote: Wanda, In trying to troubleshoot an unrelated performance PMR, IBM provided me with an e-fix for the dedupdel bottleneck that it sounds like you're experiencing. They obviously will want to do their due-diligence on whether or not this efix will help solve your problems, but it has proved very useful in my environment. They even had to compile a solaris e-fix for me, cause it seems like I'm the only one running TSM on Solaris. The e-fix was very simple to install. What you don't want to do is go to 6.3.4.2, unless they tell you to because the e-fix is for that level (207). Don't run on 6.3.4.2 for even a minute. Only install it to get to the e-fix level. Dedupdel gets populated by anything that deletes data from the stgpool, I.e. move data, expire inv, delete filespace, move nodedata, etc. We run client-side dedupe (which works pretty well, except when you run into performance issues on the server) and so our identifies don't run very long, if at all. It might save you time to run client-side dedupe. BTW, when I finally got this efix and TSM was able to catch-up with the deletes and reclaims as it needed to, I got some serious space space back in my TDP Dedup pool. It went from 90% util to 60% util (with about 10TB of total capacity). What finally really got me before the fix was that I had to delete a bunch of old TDP MSSQL filespaces and it just took forever for TSM to catch up. I have a few deletes to do now, and I'm a bit wary because I don't want to hose my server again. I would escalate with IBM support and have them supply you the e-fix. 6.3.4.3 I don't think is slated for release any time within the next few days, and you'll just be struggling to deal with the performance issue. HTH, Sergio On 12/19/13 11:35 PM, Prather, Wanda wanda.prat...@icfi.com wrote: TSM 6.3.4.00 on Win2K8 Perhaps some of you that have dealt with the dedup chunking problem can enlighten me. TSM/VE backs up to a dedup file pool, about 4 TB of changed blocks per day I currently have more than 2 TB (yep, terabytes) of volumes in that file pool that will not reclaim. We were told by support that when you do: SHOW DEDUPDELETEINFO That the number of chunks waiting in queue has to go to zero for those volumes to reclaim. (I know that there is a fix at 6.3.4.200 to improve the chunking process, but that has been APARed, and waiting on 6.3.4.300.) I have shut down IDENTIFY DUPLICATES and reclamation for this pool. There are no clients writing into the pool, we have redirected backups to a non-dedup pool for now to try and get this cleared up. There is no client-side dedup here, only server side. I've also set deduprequiresbackup to NO for now, although I hate doing that, to make sure that doesn't' interfere with the reclaim process. But SHOW DEDUPDELETEINFO shows that the number of chunks waiting in queue is *still* increasing. So, WHAT is putting stuff on that dedup delete queue? And how do I ever gain ground? W **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 443-718-4900 (o)
? Best TSMv6 DB Config: 4 * 300GB or 6 * 200GB (LUN=PV=LV=FS) ?
Seeking your experienced advice or reasoned opinion: We have a TSMv5.5.7 service with very fragmented 500GB DB @ 76% utilized but only 8% reduceable. As soon as possible we will start TSMv5-v6 migration to new 1200GB DB and 200GB Log. Another TSMv6 service with 800GB DB @ ~50% utilized performs well using 4 * 200GB LUNs = PVs = LVs = JFS2 FileSpaces (with 1 each per 200GB LUN on fast NetApp disk.) For this TSMv5-v6.3.3 conversion, using same fast disk, which TSMv6 DB config is better practice? a) 6 * 200GB LUNs (LUN = PV = LV = FileSpace) b) 4 * 300GB LUNs ... We might eventually need to incrementally grow this TSMv6 DB up to twice initial size adding similar sized LUNs! -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
Re: Replaced LTO Drive in 3584LTO Tapes not recognized by TSM database
Open a dsmadmc -console window to see what happens on your TSM service while you try to do the restore, or use Query ACTlog... to capture the results after the fact. Perhaps you need to do UPDate Volume ... ACCess=READWrite because some became UNAVailable while their LIBVolume(s) where inaccessible? Call my cell# if you want to talk... jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030) On 11/20/2012 6:45 PM, Tim Brown wrote: deleted drive paths and drives deleted library path and library defined library and path defined drives and paths tried to define DEVCLASS (LTODEVCLASS) already existed, tried updating Checkin in tapes using CHECKL=BARCODE Still not able to do a test restore of a file, get message DATA UNAVAILABLE any ideas TIVOLI TSM SERVER Ver 6.2.1 Windows 2008 Server R2 Standard Did I miss something simple, I have done this before without issues? Marc Kalipolites Systems Network Administrator Dutchess County OCIS 503 Haight Avenue Poughkeepsie, NY 12603 Phone: (845)486-2450 Email: mkalipoli...@dutchessny.govmailto:mkalipoli...@dutchessny.gov
? TSM client for Mac OS X 10.8 (Mountain Lion) ?
IBM/Tivoli, ? What TSM client for Mac OS X 10.8 (Mountain Lion) ? ? When will it be available ? We have HIPPA backup requirements for new computers running Mac OS X 10.8. Thanks in advance for your prompt assistance. -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
Re: Any other ideas?
Is your new library from SpectraLogic? If so, perhaps library is doing MLM pre-scan/autodiscovery of 2000 tapes. Takes a long. time to pre-scan 2000 tapes. Pre-scan process dominates library processing until it completes. You can turn that off under Config/MLM or stop it under Maint/MLM. -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030) On 2/12/2012 6:22 AM, Stef Coene wrote: On Sunday 12 February 2012 09:33:40 you wrote: Hi, We just upgrade a customer from one library to another library. With the new library did the customer also buy approx 2000 new LTO-5 Tapes. But now when we are labeling them in TSM it takes forever to run label libvol. Sure it runs automatic without our help, but still. We have 5 LTO-5 empty tape drives that could be used for labeling at the same time, but the process only using 1 drive at the time. I just wonder if anyone else out their have an idea for next time how we label tapes much faster and time effective? You can set the library to autolabel. So when it loads a tape and TSM does not find a label on it, it will write the label. stef
Re: Storage pool using scratch volumes instead of empty volumes
Steve, does this command also list your empty volumes: q v stg=exosatapool stat=emp acc=reado,unav -- jim.o...@yale.edu On 12/22/2011 4:23 AM, Copper, Steve wrote: ... My question is: Why is this migration process creating scratch volumes in my filesystems when I have 666 (not made up,current figure!) empty volumes assigned to the storage pool? This has only recently started happening - before it would only create scratch volumes when it had run out of Empty volumes. ... Snip of q vol stgpool=exosatapool and grep'd for Empty /sata_vol_71/sata5058.d- EXOSATAPOOL SATACLASS 20.0 G 0.0 Empty /sata_vol_71/sata5059.d- EXOSATAPOOL SATACLASS 20.0 G 0.0 Empty /sata_vol_71/sata5060.d- EXOSATAPOOL SATACLASS 20.0 G 0.0 Empty /sata_vol_71/sata5061.d- EXOSATAPOOL SATACLASS 20.0 G 0.0 Empty ...
Re: strategy for migrating to new library strategy
On 2/9/2011 9:30 AM, Richard Rhodes wrote: We will be shortly be helping with a DataDomain (DD) installation, and we are looking for how best to move the primary pool from the old tape pool to the DD. The DD will be used as a NAS device via a file type pool. 2) use migration chg DISK nextpool to DD chg TAPE nextpool to DD migration from TAPE to DD current: DISK-TAPE transition: DISK-DD-TAPE migrate TAPE to DD to clear out old pool final: DISK-DD Migration runs process automatically. Better: Simultaneously and automatically... Use Migration to move from DISK to DD, as above. Use Reclamation to move from TAPE to DD. UPDate STGpool TAPE RECLAIMSTGpool=DD REClaim=[%%] RECLAIMPRocess=[##] Adjust ## and %% as appropriate, reducing %% until done. -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
? minimal workable TSMv6.2 Library Manager space allocations ?
Are you running a simple TSMv6 Library Manager (LM) service? I am trying to configure a minimal TSMv6.2 LM service and wondering, what are minimal workable TSMv6.2 DB, Log, and Archlog allocations? We're running an active TSMv5.5 LM service under AIX6.1 for some years now using 1GB each for DB and Log space! [See further below, if interested] I thought these allocations were reasonably generous for TSMv6.2 migration: DB01= 2GB DB02= 2GB Log = 4GB [Active Log] Archlog = 8GB [Archive Log] but apparently Active Log space is insufficient; DSMSERV LOADFORMAT fails w/ ANR0370E rdbicbck.c(772) During the format operation, the server cannot create files in one or more directories that you specified for ACTIVELOGDIR. Ensure that the file system where the directory is located has sufficient space. TSMv6.2: Planning to install server: Capacity planning: Active log space: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.srv.install.doc/c_srv_inst_active_log_space.html says: ... The default size of the active log is 16,384 MB (16 GB). Under normal server operations, you are likely to need an active log that is larger than the default. The maximum size of the active log is 131,072 MB (128 GB). The minimum size of the active log is 2048 MB (2 GB). ... But, that 2GB minimum size seems to be unworkable w/ TSMv6.2: TSMv6.2: ANR Messages: Help for ANR0370E: http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.msgs.server.doc/msgs_server336.html says: ... * Check that space is available to the directories that you specified for ACTIVELOGDIR,ARCHIVELOGDIR, and ARCHFAILOVERLOGDIR. Ensure that the amount of space meets requirements. For example, the directory for ACTIVELOGDIR must have at least 8 GB space available. ... Increasing Active Log allocation 8GB, the error goes away, so the ANR0370E message advice is apparently correct! So... How would you configure DB, Log, ArchLog space for this TSMv6.2 LM service? Here's what our TSMv5.5.5 LM Service looks like: [Our LM TSM shares 3 tape libraries w/ 16*LTO2 + 60*LTO3 + 16*LTO5 drives w/ seven active Library Client TSM Backup/Recovery services, and also runs a gaggle of weeknightly differential NDMP backups and weekend DR+full NDMP backups for Oracle DBs and VMware guests on NetApps.] tsm: MGRq db Session established with server MGR: AIX-RS/6000 Server Version 5, Release 5, Level 5.0 Server date/time: 12/02/2010 21:42:31 Last access: 12/02/2010 14:52:13 Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 1,0201,020 0 288 4,096 261,120 186,853 71.6 71.6 tsm: MGRq log Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 1,016 764 252 544 4,096 195,07255,255 28.3 69.7 tsm: MGRq stg Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.0 M0.00.090 70 BACKUPL3NLTO3N 64,810 G 34.8 BACKUPL3NDR LTO3NDR 31,804 G9.3 BACKUPL3NDX LTO3NDR 155,767 G 73.3 BACKUPPOOL DISK 0.0 M0.00.090 70 SPACEMGPOOL DISK 0.0 M0.00.090 70 tsm: MGR Thanks for any advice you care to share. -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
? how to change TSM V6 UID ?
I want to change/rename the user that owns a TSM v6 service. Is there an easy way to do that, or do we need to (unre)install? -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
? linux TSM 6.2 using 10GE iSCSI ... to backup HPC ?
?Are you: doing TSM backups to iSCSI disk/tape? w/10GE? w/TSM6.? Scanning ADSM-L archives, actual TSM experience w/iSCSI seems scarce! Recently, Gary Bowers recommends DirectIO No in dsmserv.opt w/ iSCSI, and in 2007 Ben Bullock had iSCSI poor performance (w/o that setting?) Most other iSCSI threads are questions answered by theory/opinion. We hope to backup HPC (primarily Gene Sequencing Experiments) w/TSM 6.2. HPC infrastructure: RHEL linux clusters using Panasus PanFS iSCSI disk array via 10Gb ethernet To best integrate TSM into their infrastructure, the HPC group wants to backup to iSCSI disk/tape storage via 10GE w/ TSM v6.2 running on RHEL. Our current TSM experience is w/ AIX6.1, TSMv5.5.4.2, FC disk/tape, so we're really trying to shoot the moon w/ this new HPC TSM config. !But, hey! It's all going to be new, so why not ...totally different? Please advise, if you have relevant experience/facts, (or theories/opinions, as you believe appropriate;-) FYI, here's how we hope this can work: Because TSM does not support Panasus PanFS, we will use tar to copy completed GeneSeqExprmnts onto (iSCSI) EXT3 FS space @ RHEL linux hosting both TSM 6.2 server and client. TSM client will backup GSE tarballs from EXT3 FS w/ dsmc incremental via ShrMem to TSM 6.2 server, directly onto (iSCSI) LTO5 tape w/compression. Other PanFS volumes will backup via dsmc incremental from NFS mounts @ TSM client via ShrMem to (iSCSI) sequential file STGpool space w/ dedup enabled. (We also hope to use TSM client dedup effectively!-) Thanks for any advice! -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
LM TSM v5.5.4.2 upgrade fixes tape mount failures w/ v5.5.4 or v5.5.4.1
If your LibMgr TSM v5.5.4 / v5.5.4.1 is busy, you probably have APAR IC65967 causing many unnecessary tape mount failures w/ ANR9730W errors @ LM TSM and ANR1401W errors @ LC TSM. After being plagued for the last month with these failures [failing GENerate BackupSets and other long running processes], we did an emergency v5.5.4.2 upgrade yesterday. Before the upgrade, we had 100 mounts failing within an hour! Since the upgrade, we've had only two failed mounts during the last 19 hours. We like our AIX 6.1 LM TSM v5.5.4.2 (latest patch) upgrade! See also: http://www-01.ibm.com/support/docview.wss?uid=swg21414813 -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
Re: date check in a select [using days(...) function]
I use this variant: [?equivalent to M.Green's?] select node_name, reg_time from nodes- where days(current_timestamp)-days(reg_time)30 -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030) Michael Green wrote: Try this: select node_name, reg_time from nodes where cast((current_timestamp-reg_time)days as decimal)30 -- Warm regards, Michael Green On Thu, Feb 11, 2010 at 6:46 PM, Richard Rhodes rrho...@firstenergycorp.com wrote: What's the best way to write a date check like this?I'm looking for any nodes registered after some number of days (the 30 is just an example). dsmadmc -se=$i -id=$adminid -password=$adminpwd -tab -noc EOD select node_name, reg_time from nodes where reg_time \ 30 days EOD ANR2916E The SQL data types TIMESTAMP and INTERVAL DAY(9) are incompatible for operator ''. | .V select node_name, reg_time from nodes where reg_time 30 days Thanks Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: SQL Query ...associated w/ management class
Lindsay Morris wrote: Right, we did some magic on the dsmc client... But I see this question here repeatedly: how can I list all of my backup files? And the answer is always Don't do that, or tread carefully like Richard just said. ... So why are people wanting to do this? Hey, you lurkers who think about doing this: will you speak up and say why, please? What are you really after, reducing wasted storage? tuning up retention policies? What? lind...@tsmworks.com A.Lurker responds Yes to both of the above, e.g., Upon finding DONT_DOIT policy in effect @ (inherited) NoClue TSM: tsm: NOCLUEq co dont_doit act* PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- DONT_DOIT ACTIVESPECIAL STANDARD30 30 999 999 DONT_DOIT ACTIVESTANDARD STANDARD 42 30 60 tsm: NOCLUE [names changed, but unfortunately, this is not imaginary!] The now responsible TSM v5.5 SysAdm wants to know (who,what,howmuch) will be affected if we eliminate SPECIAL Mgmt Class, but would *not* dare to select node_name, filespace_name, filespace_id, HL_name, LL_name,- count(LL_name) as #InActive, sum(file_size) as NoAggr(MB)- from backups,contents where state='Inactive'- and days(current_time)-days(deactivate_date)30- and backups.object_id=contents.object_id- and aggregated='No'- /* because actual filesize isn't always available, but it should be! */ group by node_name, filespace_name, filespace_id, HL_name, LL_name The potential TSM v6.1.5 SysAdm wonders if, with the new DB2 basis, this/similar selection could actually return accurate information within the time that a reasonable person would be willing to wait? -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
?anyone using TSM to backup Panasus PanFS?
Yale uses Panasus PanFS, a massive parallel storage system, to store research data generated from HPC clusters. In considering feasibility to backup PanFS using TSM, we are concerned about whether TSM is appropriate to backup and restore: 1. very large volumes, 2. deep subdirectory hierarchy with 100's to 1000's of sublevels, 3. large numbers of files within individual subdirectories, 4. much larger numbers of files within each directory hierarchy. Are there effective maximum limits for any of the above, beyond which TSM becomes inappropriate to effectively perform backups and restores? Please advise about the feasibility and any configuration recommendation(s) to maximize PanFS backup and restore efficiency using TSM. Thanks for your help. -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
? Best practices for TSM to backup MS DPM server ?
Our Windows Systems group prefers to use MS DPM for Exchange and Sharepoint backup and recovery. If your site is doing the same, we would like to talk with you about Best Practices for TSM backup of MS DPM and what you have learned. Please reply to... -- jim.o...@yale.edu (w#203.432.6693, c#203.494.9201, h#203.387.3030)
Re: volumes in a collocation group?
I believe Paul meant to say: Nodes not assigned to a specific collocation group are treated as if *each* is in *its* own private collocation group (i.e., collocation by node.) -- jim.o...@yale.edu Paul Zarnowski wrote: Nodes not assigned to a specific collocation group are treated as if they were in their own private collocation group. At 12:15 AM 3/15/2009, Larry Clark wrote: Paul, A question occurred to me.. If you have a subset of nodes defined to collocation groups, but a number of nodes not defined to collocation groups, will TSM attempt to avoid putting files not in a collocation group on volumes that have collocation groups nodes...as distinct from your explanation of filling volumes for collocations group members? Larry Clark
pmr48580,L6Q: incorrect Est.Capacity for tape STGpool and Volumes when Volume status=EMPty
TSM Support, We have a new BackupL3R STGpool w/ 10 new LTO3 volumes explicitly defined. Despite having Est.Capacity=400G defined for the LTO3R DEVclass, the empty (available) STGpool and Volumes incorrectly show Est.Capacity=0.0 M Volumes with STATus=PENDing similarly incorrectly show Est.Capacity=0.0 M Please ask TSM development to correct these erroneous query results. Thanks for your help. -- jim.o...@yale.edu (203.432.6693) tsm: QUAARKq stat Storage Management Server for AIX-RS/6000 - Version 5, Release 5, Level 1.0 ... tsm: QUAARKq stg backupl3r Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool Pct Pct --- -- -- - - --- --- BACKUPL3RLTO3R0.0 M0.00.0 100 99 tsm: QUAARKq v stat=emp Volume Name Storage Device EstimatedPct Volume Pool NameClass Name Capacity Util Status --- -- - - F00640L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00641L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00642L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00643L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00644L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00645L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00646L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00647L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00648L3 BACKUPL3RLTO3R 0.0 M0.0 Empty F00649L3 BACKUPL3RLTO3R 0.0 M0.0 Empty G00263L3 BACKUPL3 LTO30.0 M0.0 Empty G00438L3 BACKUPL3 LTO30.0 M0.0 Empty G00623L3 BACKUPL3 LTO30.0 M0.0 Empty tsm: QUAARKq dev lto3r Device DeviceStorageDevice Format Est/Max Mount ClassAccess PoolType Capacity Limit Name StrategyCount (MB) ----------- LTO3RSequential 1LTO ULTRI-409,600.DRIVES UM3C0 tsm: QUAARK
?how to force NDMP LAN-free backups to fill one tape before writing on another?
I am trying to force NDMP LAN-free backups to keep the same tape mounted and serially reuse it when a NetApp filer needs to write multiple backups. We have just implemented our first NDMP LAN-free backups w/ TSM v5.5.1.1, w/ a single NetApp filer backing up 16 VirtualFS from nightly snapshots, e.g., DEFine VIRTUALFSmapping netapp-01 /x.snap /vol/volx /.snapshot/nightly.0 I was disappointed to find that DEVType=NAS requires MOUNTRetention=0: e.g., DEFine DEVclass LTO3N LIBRary=bec3584 DEVType=NAS ESTCAPacity=800G - MOUNTRetention=0 MOUNTWait=5 [that forces a tape dismount after each NDMP backup, right?] We use LTO1 scratch tapes in our 3584 library so I defined 10 * LTO3 volumes into our new BackupL3N STGpool: DEFine STGpool BackupL3N LTO3N POoltype=PRimary DATAFOrmat=NETAPPDump - COLlocate=Group [=default setting] MAXSCRatch=0 The filer wrote NDMP backups on all 10 tapes, so I did MOVE DATA's to collocate all of the backups back onto a single tape and tried: UPDate STGpool BackupL3N COLlocate=Node Same results: NDMP backups on all 10 tapes again! Help? [or is that just how NDMP backups work?] -- [EMAIL PROTECTED] (203.432.6693)
select...where...like '$1%' is *invalid* w/ TSM v5.5.1
After TSM v5.5.1 upgrade, the following command syntax is invalid: select...where...like '$1%' This syntax was accepted in TSM scripts through TSM v5.5.0.3, but our local scripts are broken after the upgrade. Maybe I'm just too tired; is there a more appropriate technique to concatenate $1 and % to enable these scripted comparisons? -- [EMAIL PROTECTED] (203.432.6693)
Re: select...where...like '$1%' is *invalid* w/ TSM v5.5.1 [workaround]
After too much (st,gr,f)umbling, here are v5.5.1 syntactical workarounds:
select...where...like '$1%' [valid syntax *until* v5.5.1]
can be replaced with:
select...where...like '$1'||'%'
or select...where...like concat('$1','%')
and
select...where...like upper('%$1%') [also *formerly* valid]
can be replaced with:
select...where...like upper('%$1'||'%')
or select...where...like upper('%'||'$1'||'%')
or select...where...like upper(concat('%$1','%'))
but*not*select...where...like upper(concat('%','$1','%')) [invalid]
[concat only works on 2 operands]
--
[EMAIL PROTECTED] (203.432.6693)
Richard Sims wrote:
Jim -
I don't have a 5.5 to test, but I would try the construct:
... LIKE CONCAT($1, '%')
and see if that is accepted.
Richard Sims
On Jul 13, 2008, at 7:48 AM, James R Owen wrote:
After TSM v5.5.1 upgrade, the following command syntax is invalid:
select...where...like '$1%'
This syntax was accepted in TSM scripts through TSM v5.5.0.3,
but our local scripts are broken after the upgrade.
Maybe I'm just too tired; is there a more appropriate technique to
concatenate $1 and % to enable these scripted comparisons?
--
[EMAIL PROTECTED] (203.432.6693)
Re: when will 5.5.1 client be released? [mid July?]
We are currently running an efix dsmserv v5.5.0.3 + testfix for IC56999. IBM level 2 support told us that v5.5.1 will be delayed about 2 weeks in order to include the fix for IC56999. That's very good decision: IC56999 was a severe performance problem for a busy UNIX TSM service! Backup performance is back to our normal expectations with the efix. The v5.5.1 client README files posted near the end of June also talk about a delay of 2 weeks. -- [EMAIL PROTECTED] (203.432.6693) Schaub, Steve wrote: I had expected to see it by now, is there an ETA? Steve Schaub Systems Engineer, Windows Blue Cross Blue Shield of Tennessee 423-535-6574 (desk) 423-785-7347 (mobile) Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer: http://www.bcbst.com/email_disclaimer.shtm
Re: Backing up NT4
WinNT4 BAclient v5.1.6.0 works OK w/ AIX 5.3 TSMservice v5.5.0.3. -- [EMAIL PROTECTED] (203.432.6693) Evans, Bill wrote: Yep, this is what we are planning on trying. I'll update if not successful. Thank you, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thorneycroft, Doug Sent: Wednesday, June 18, 2008 1:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backing up NT4 Depending on what needs to be backed up on the machine, it might be easiest to share the drives/directories needing backup and backup the share from another node. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Norman Bloch Sent: Wednesday, June 18, 2008 1:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Backing up NT4 did you try ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintena nce/client/v5r1/Windows/WinNT/v518/ ? Evans, Bill [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 18/06/2008 22:02 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Backing up NT4 We just upgraded to TSM 5.5 server on AIX 3.5, is there a client for NT4 that will connect? An hour of searching on IBM and Google did not help. Thank you, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER 206.667.4194 ~ [EMAIL PROTECTED]
3494 tape libraries and 3590 drives available to take from New Haven, CT, USA
In case someone might be interested to take and reuse... Yale University recently decommissioned 4 * IBM 3494 tape libraries and will recycle them for scrap metal before June 30th, unless some other institution would like to take and reuse them. The libraries and 3590 drives were maintained by IBM and are serviceable, but resellers were not interested. Does anyone need/want any of this: 4 * 3494 L12 frames w/ single gripper robotics 5 * 3494 D12 frames 2 * 3494 D14 frames 12 * 3494 S10 frames 10 * 3590 H1A FC drives 12 * 3590 E1A SCSI drives Library frames have been separated but drives still remain installed. All of the hardware is freely available, but you would need to pack and remove it from our floor. Your institution would need to sign an affidavit officially taking responsibility for the proper disposal of any hardware taken from Yale, in accordance with Federal regulations. If interested, please reply to or call... -- [EMAIL PROTECTED] (203.432.6693)
Re: Upgrading TSM on an AIX server running multiple TSM instances
Orville, Can you clarify exactly what is the problem with multiple TSM service instances running from a shared dsmserv binary? AFAIK, IBM/Tivoli does not suggest to copy and run a separate executable for each TSM instance. We have not seen any problems sharing the same executable among several TSM instances. Do you use this technique to allow production TSM services to continue running while you upgrade the default installation TSM service? Have you used this technique to safely run different maintenance levels of TSM service simultaneously on the same AIX host? If so, have you experienced any problems doing this? Did you ever need to copy additional files to the running directories for the other TSM services? I'm also looking for advice: how best to make an inoperative AUTOSRVR entry in /etc/inittab? We leave the tiny default TSM service in the installation directory for upgrade processing, and never want it to start up automatically, but the upgrade process recreates the entry if it has been removed. -- [EMAIL PROTECTED] (203.432.6693) Orville Lantto wrote: The reason to have separate binaries for each instance is that the process in AIX is tied to the binary file and holds it open. Orville L. Lantto From: ADSM: Dist Stor Manager on behalf of Loon, E.J. van - SPLXM Sent: Tue 1/22/2008 02:55 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Upgrading TSM on an AIX server running multiple TSM instances Hi Orville! Thank you very much for you help! I read the technote (1052631) Richard pointed out. That doesn't mention copying the dsmserv executable. Any reason why you choose to do so? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orville Lantto Sent: maandag 21 januari 2008 19:11 To: ADSM-L@VM.MARIST.EDU Subject: Re: Upgrading TSM on an AIX server running multiple TSM instances You do not really need a full install of the TSM server code in both locations. Just a separate directory, separate config files, a separate copy of the dsmserv binary and a the appropriate environment to run it in. export DSMSERV_DIR=/usr/tivoli/tsm/server/bin export DSMSERV_CONFIG=/usr/tivoli/tsm/server/instance2/dsmserv.opt Our upgrade procedure is to do the primary install and copy the dsmserv binary to each instance directory. Done. Orville L. Lantto From: ADSM: Dist Stor Manager on behalf of Loon, E.J. van - SPLXM Sent: Mon 1/21/2008 06:11 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Upgrading TSM on an AIX server running multiple TSM instances Hi *SM-ers! I'm running two TSM server instances on an AIX host. Upgrading them from 5.3 to 5.4.0.0 works fine. I installed the 5.4.0.0 code through smitty, changed the /usr/tivoli/tsm/server path to the second instance and install the 5.4.0.0 code here, using the force (-F) flag. Both instances are on 5.4.0.0 at that point. Now I'm trying the same trick for the upgrade to 5.4.2.0. Upgrading the first instance works fine, but since this is an update, the -F flage is not allowed by smitty during the upgrade of the second instance: Force Apply Failures The following is a list of fileset updates. Updates cannot be specified from the command line when the force flag (-F) is used in combination with the apply flag (-a). Maybe an AIX expert (and I now there are plenty of them on this list) can help me with this one? Thank you VERY much in advance Kindest regards, Eric van Loon KLM Royal Dutch Airlines ** For information, services and offers, please visit our web site: http://www.klm.com http://www.klm.com/ http://www.klm.com/ . This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** ** For information, services and offers, please visit our web site: http://www.klm.com http://www.klm.com/ . This e-mail and any attachment may contain confidential and
Re: Fw: DISASTER: How to do a LOT of restores?
Roger, You certainly want to get a best guess list of likely priority#1 restores. If your tapes really are mostly uncollocated, you will probably experience lots of tape volume contention when you attempt to use MAXPRocess 1 or to run multiple simultaneous restore, move nodedata, or export node operations. Use Query NODEData to see how many tapes might have to be read for each node to be restored. To minimize tape mounts, if you can wait for this operation to complete, I believe you should try to move or export all of the nodes' data in a single operation. Here are possible disadvantages with using MOVe NODEData: - does not enable you to select to move only the Active backups for these nodes [so you might have to move lots of extra inactive backups] - you probably can not effectively use MAXPROC=N (1 nor run multiple simultaneous MOVe NODEData commands because of contention for your uncollocated volumes. If you have or can set up another TSM server, you could do a Server-Server EXPort: EXPort Node node1,node2,... FILEData=BACKUPActive TOServer=... [Preview=Yes] moving only the nodes' active backups to a diskpool on the other TSM server. Using this technique, you can move only the minimal necessary data. I don't see any way to multithread or run multiple simultaneous commands to read more than one tape at a time, but given your drive constraints and uncollocated volumes, you will probably discover that you can not effectively restore, move, or export from more than one tape at a time, no matter which technique you try. Your Query NODEData output should show you which nodes, if any, do *not* have backups on the same tapes. Try running a preview EXPort Node command for single or multiple nodes to get some idea of what tapes will be mounted and how much data you will need to export. Call me if you want to talk about any of this. -- [EMAIL PROTECTED] (w#203.432.6693, Verizon c#203.494.9201) Roger Deschner wrote: MOVE NODEDATA looks like it is going to be the key. I will simply move the affected nodes into a disk storage pool, or into our existing collocated tape storage pool. I presume it should be possible to restart MOVE NODEDATA, in case it has to be interrupted or if the server crashes, because what it does is not very different from migration or relcamation. This should be a big advantage over GENERATE BACKUPSET, which is not even as restartable as a common client restore. A possible strategy is to do the long, laborious, but restartable, MOVE NODEDATA first, and then do a very quick, painless, regular client restore or GENERATE BACKUPSET. Thanks to all! Until now, I was not fully aware of MOVE NODEDATA. B.T.W. It is an automatic tape library, Quantum P7000. We graduated from manual tape mounting back in 1999. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Tue, 22 Jan 2008, Nicholas Cassimatis wrote: Roger, If you know which nodes are to be restored, or at least have some that are good suspects, you might want to run some move nodedata commands to try to get their data more contiguous. If you can get some of that DASD that's coming real soon, even just to borrow it, that would help out tremendously. You say tape but never library - are you on manual drives? (Please say No, please say No...) Try setting the mount retention high on them, and kick off a few restores at once. You may get lucky and already have the needed tape mounted, saving you a few mounts. If that's not working (it's impossible to predict which way it will go), drop the mount retention to 0 so the tape ejects immediately, so the drive is ready for a new tape sooner. And if you are, try to recruit the people who haven't approved spending for the upgrades to be the picker arm for you - I did that to an account manager on a DR Test once, and we got the library approved the next day. The thoughts of your fellow TSMers are with you. Nick Cassimatis - Forwarded by Nicholas Cassimatis/Raleigh/IBM on 01/22/2008 08:08 AM - ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/22/2008 03:40:07 AM: We like to talk about disaster preparedness, and one just happened here at UIC. On Saturday morning, a fire damaged portions of the UIC College of Pharmacy Building. It affected several laboratories and offices. The Chicago Fire Department, wearing hazmat moon suits due to the highly dangerous contents of the laboratories, put it out efficiently in about 15 minutes. The temperature was around 0F (-18C), which compounded the problems - anything that took on water became a block of ice. Fortunately nobody was hurt; only a few people were in the building on a Saturday morning, and they all got out safely. Now, both the good news and the bad news is that many of the damaged computers were backed up to our large TSM system. The good news is that their data can be restored. The bad news is that their data can be restored. And so now it must
Re: Fw: DISASTER: How to do a LOT of restores? [like Steve H said, but...]
value should be investigated and discussed -- even if you only use it for the purpose we're discussing here. If you know you're in a DR scenario and you're going to be restoring multiple systems, why wouldn't you do create an ACTIVEDATA pool and do a COPY ACTIVEDATA instead of a MOVE NODE? OK, here's another question. Is it assumed that the ACTIVEDATA pool have node-level collocation on? Can you use group collocation instead? Then maybe I and my friend could both get what we want? Just throwing thoughts out there. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Maria Ilieva Sent: Tuesday, January 22, 2008 10:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fw: DISASTER: How to do a LOT of restores? The procedure of creating active data pools (assuming you have TSM version 5.4 or more) is the following: 1. Create FILE type DISK pool or sequential TAPE pool specifying pooltype=ACTIVEDATA 2.Update node's domain(s) specifying ACTIVEDESTINATION=created active data pool 3. Issue COPY ACTIVEDATA node_name This process incrementaly copies node's active data, so it can be restarted if needed. HSM migrated and archived data is not copied in the active data pool! Maria Ilieva --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of James R Owen Sent: Tuesday, January 22, 2008 9:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fw: DISASTER: How to do a LOT of restores? Roger, You certainly want to get a best guess list of likely priority#1 restores. If your tapes really are mostly uncollocated, you will probably experience lots of tape volume contention when you attempt to use MAXPRocess 1 or to run multiple simultaneous restore, move nodedata, or export node operations. Use Query NODEData to see how many tapes might have to be read for each node to be restored. To minimize tape mounts, if you can wait for this operation to complete, I believe you should try to move or export all of the nodes' data in a single operation. Here are possible disadvantages with using MOVe NODEData: - does not enable you to select to move only the Active backups for these nodes [so you might have to move lots of extra inactive backups] - you probably can not effectively use MAXPROC=N (1 nor run multiple simultaneous MOVe NODEData commands because of contention for your uncollocated volumes. If you have or can set up another TSM server, you could do a Server-Server EXPort: EXPort Node node1,node2,... FILEData=BACKUPActive TOServer=... [Preview=Yes] moving only the nodes' active backups to a diskpool on the other TSM server. Using this technique, you can move only the minimal necessary data. I don't see any way to multithread or run multiple simultaneous commands to read more than one tape at a time, but given your drive constraints and uncollocated volumes, you will probably discover that you can not effectively restore, move, or export from more than one tape at a time, no matter which technique you try. Your Query NODEData output should show you which nodes, if any, do *not* have backups on the same tapes. Try running a preview EXPort Node command for single or multiple nodes to get some idea of what tapes will be mounted and how much data you will need to export. Call me if you want to talk about any of this. -- [EMAIL PROTECTED] (w#203.432.6693, Verizon c#203.494.9201) Roger Deschner wrote: MOVE NODEDATA looks like it is going to be the key. I will simply move the affected nodes into a disk storage pool, or into our existing collocated tape storage pool. I presume it should be possible to restart MOVE NODEDATA, in case it has to be interrupted or if the server crashes, because what it does is not very different from migration or relcamation. This should be a big advantage over GENERATE BACKUPSET, which is not even as restartable as a common client restore. A possible strategy is to do the long, laborious, but restartable, MOVE NODEDATA first, and then do a very quick, painless, regular client restore or GENERATE BACKUPSET. Thanks to all! Until now, I was not fully aware of MOVE NODEDATA. B.T.W. It is an automatic tape library, Quantum P7000. We graduated from manual tape mounting back in 1999. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Tue, 22 Jan 2008, Nicholas Cassimatis wrote: Roger, If you know which nodes are to be restored, or at least have some that are good suspects, you might want to run some move nodedata commands to try to get their data more contiguous. If you can get some of that DASD that's coming real soon, even just to borrow it, that would help out tremendously. You say tape but never
Re: TSM v5.5 feedback: [TSM 5.5 works well for our busy LibMgr TSM on AIX 5.3]
Look *out*! There might be *D A N G E R* ahead [or maybe not;*] [there's a smiley for you, Mark S:-), and SomeMoreS @ the bottom] After consolidating tape library management at a new TSM service [moved from two production TSM backup services a few days before Charlotte announced IBM's RedPaper showing another way to do it], we upgraded that TSM service to 5.5.0 (from 5.3.4.2 and have seen no problems running (on AIX 5.3) since Saturday, 1/12/2008 00:05. Our upgraded LibMgr TSM service manages two IBM 3584 libraries, each sharing 3+4*LTO1, 8+8*LTO2, and 8+16*LTO3 drives to five other production TSM backup services (all still running 5.3.4.2) on three other AIX 5.3 systems. [Client groups are starting to test backups and restores w/upgraded TST TSM also running there. No bad news, so far... will send an update if we find a problem.] TSM 5.5.0 better manages usage of our various LTO drives even when we have more mount requests scheduled than we have drives. Sometimes, with TSM 5.3, available drives were unusable because drives were reserved inappropriately for processes that required two drives, but could only get one! That bug seems to be fixed. If you use TSM library sharing and have not yet setup your library manager to run as a separately upgradeable TSM service, you might consider doing that to enable a staged lower-risk TSM 5.5 upgrade. -- [EMAIL PROTECTED] (203.432.6693) NEVER... NEVER... can leave you living with yesterday's problems !-( Maybe, is sometimes OK, but who knows what will uncover tomorrow ?-) ( M ( E ( L ( T ( E ( D ( ) M ) A ) R ) S ) M ) A ) L ) L ) O ) W ) Upgrades are like fruit: mostly good, unless you bite into a bug... [or a big bug pops out and bites you back, and then you have to run cleanup backupgroup for a month to remove N**N bogus system objects!] Stapleton, Mark wrote: From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Just wanted to know if anyone's made the jump. We got in a new server and will be moving from v5.3.1.2 to 5.4 or 5.5. Just wanted to know what your thoughts were on migrating? The upgrades from 5.3.X upward should go smoothly. Follow the instructions in the relevant TSM server installation guide. The first maintenance level for TSM server 5.5 has yet to appear, and I NEVER install base code of anything in a production environment. 80% of bugs are in base code. In a similar vein, I NEVER install a patch level of TSM in a production environment unless I'm trying to fix a specific problem associated with that patch. Patches are not nearly as thoroughly tested as maintenance levels. In other words, you should be installing 5.4.2.0 on your TSM server. TSM server 5.3.X.X goes out of support on 30 April 2008. Use and abuse. -- Mark Stapleton CDW Berbee System engineer 7145 Boone Avenue North, Suite 140 Brooklyn Park MN 55428-1511 763-592-5963 www.berbee.com
Re: ANR8833E - Does 5.4.3 = 5.5 ? [No, TSM 5.5 is better!]
Zoltan, Look again at that APAR doc: IBM - IC54107: TSM ANR8833E DURING CHECKIN LIBVOL FOR SOME VOLUMES http://www-1.ibm.com/support/docview.wss?uid=swg1IC54107 My reading is that APAR IC54107 affects only TSM 5.3 and 5.4. If correct, that is why it is not listed as an APAR fixed in TSM 5.5. So, I believe, you would best upgrade to TSM 5.5 -- [EMAIL PROTECTED] (203.432.6693) John Monahan wrote: Zoltan Forray/AC/VCU wrote on 11/27/2007: We have been having an intermittant problem with ANR8833E errors, which are addressed in apar: IC54107: TSM ANR8833E DURING CHECKIN LIBVOL FOR SOME VOLUMES. However, the apar says: projected to be fixed in level 5.3.6.1, 5.3.7, and 5.4.3. Since I haven't seen anything higher than 5.4.1.2 and 5.5 server is out, can I assume the problem is fixed in 5.5 ? Is there a 5.4.2/5.4.3 release expected ? APARs fixed in 5.5 are listed here: http://www-1.ibm.com/support/docview.wss?uid=swg21288273 IC54107 is not on the list. __ John Monahan Consultant Logicalis, Inc. 5500 Wayzata Blvd Suite 315 Golden Valley, MN 55416 Office: 763-417-0552 x109 Mobile: 952-221-6938 Fax: 763-417-0554 [EMAIL PROTECTED] http://www.us.logicalis.com This email may contain confidential information. If you received it in error, please delete it and notify the sender.
Re: Improvement and cahges for TSM Server 5.4.X
Curtis, If you had read the context more carefully, you would see that Richard's skimpy comment referred *not* to the TSM 5.4 enhancements but rather to IBM/Tivoli's documentation of those enhancements: Is there any documentation on that ?? I found the lipstick on a pig analogy inappropriate, but mad funny! [the ugly sort of humor that all/most/some/few/none laugh about in private?] Does anybody know the real source? -- [EMAIL PROTECTED] (203.432.6693) Curtis Preston wrote: Skimpy? Really? I think that the ability to collocate active data is the coolest new feature I've seen since collocation. A user who can buy enough SATA disk to hold all their active files should get a HUGE benefit from this feature. Don't you think so? (This is why it's funny that someone on this list a while ago accused me of being the anonymous source that referred to that feature as lipstick on a pig.) --- W. Curtis Preston Author of O'Reilly's Backup Recovery and Using SANs and NAS VP Data Protection GlassHouse Technologies -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Tuesday, May 01, 2007 10:51 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Improvement and cahges for TSM Server 5.4.X On May 1, 2007, at 1:45 PM, Luc Beaudoin wrote: Hi all I'm looking for a red book or red paper that explain all the changes and new features in TSM 5.4 Is there any documentation on that ?? Hi, Luc - IBM is a bit behind on that... There is http://www-306.ibm.com/software/tivoli/products/storage-mgr/ enhancements-v5.4.html but very skimpy compared to its predecessors. There is no TSM 5.4 Technical Guide yet. Mostly, the changes are outlined in the front of the respective manuals. Richard Sims
Re: 10 Gbit ethernet [backups to remote data centers]
Keith, I can't speak about 10Gb, but we use fibre-extended 1Gb ethernets between our A B data centers. TSM clients @ A backup over the 1Gb network to a TSM service @ B. Their backups are stored on disks and tapes @ B. Similarly TSM clients @ B backup to a TSM service @ A. Works well for us. -- [EMAIL PROTECTED] (203.432.6693) Orville Lantto wrote: Can 10 Gbit Ethernet go 60 miles? How are you writing to the remote tape devices? Orville L. Lantto Glasshouse Technologies, Inc. From: ADSM: Dist Stor Manager on behalf of Lawrence Clark Sent: Wed 4/25/2007 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 10 Gbit ethernet Well, On the IBM SP we ran backups over the internal switch which was 17GB(yte) if I recall. And we currently have fibre attachements to drives, so I don't know why the speed of the NIC should be a concern. The operation of the NIC is under the OS, not TSM. [EMAIL PROTECTED] 04/25/07 4:41 PM Is anyone running TSM over 10 Gbit ethernet? Is there any question that it would be supported? We have two data centers about 60 miles apart. We are planning to send backup files from each data center to a 3584 ATL in the other via a 10 Gbit ethernet link. The server hardware would be HP DL585- G2's with Myricom 10 Gbit NICs and 2.6 Ghz AMD processors. The operating system would be Redhat EL 4. If anyone else has experience with TSM and 10 Gbit ethernet we would be glad to hear about it. Thank you, Keith Arbogast Indiana University The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain information that is confidential, privileged, and/or otherwise exempt from disclosure under applicable law. If this electronic message is from an attorney or someone in the Legal Department, it may also contain confidential attorney-client communications which may be privileged and protected from disclosure. If you are not the intended recipient, be advised that you have received this message in error and that any use, dissemination, forwarding, printing, or copying is strictly prohibited. Please notify the New York State Thruway Authority immediately by either responding to this e-mail or calling (518) 436-2700, and destroy all copies of this message and any attachments.
Re: LAN-free: does that have any meaning on the server??
Allen, Good news: Your I/O is LAN-free because your 3292 drives are FC connected. Bad news: For LAN-free backups, the TSM StgAgent drives the tape I/O. For tape-tape reclamation the TSM Server drives the tape I/O. All of the I/O is going through and driven by the host server subject to its bus and CPU limitations. -- [EMAIL PROTECTED] (203.432.6693) No free lunch (except served by others at a soup kitchen.) No server-free tape I/O unless some other server is driving it. Allen S. Rout wrote: Greetings, all. I'm contemplating some upgrades to my TSM infrastructure, and trying to determine where I think the bottleneck will move. I'm adding tape drives, and intend to do a huge load of reclamation Real Soon Now. So, my question is: Does tape-to-tape copy which the TSM server deems local actually touch the server bus at all? For example; if I have 32 3592 drives (shush; let me dream), sufficient SAN fabric to keep them all fed, and sufficient reclamation work to keep them occupied, all totally devoted to reclamation: Is my -server- doing I/O work, or just bookkeeping? The tape IO management stuff (or lack thereof) leaves me feeling adrift, when compared to the superb support for disk IO evaluation I've grown to love out of NMON. I feel like I understand my disk IO intimately, but really wonder what's going on with the tapes. I've tried to work this out by calculating the 'negative space', but when I'm doing lots of tape work, I'm also beating the snot out of my database, so I'm not sure where to blame the IOWAIT. Anyone got a clue to spare? - Allen S. Rout
?'s about Backup of Cyrus email, LTO3 vs 3592 tapes, and using Copy tapes
Happy New Year to All! @Yale, we will do several conversions soon/later during 2007: email: from U.Washington IMAP servers to Cyrus IMAP servers. tapes: from 3494 w/ 3590 drives to 3584 w/ LTO2-3 and/or 3592's. TSM:from server 5.2.3 to 5.3.4, and then to 5.4? Copies: ?using Copy tapes for all/some/no client Backups? 1. We seek experience/advice from sites using TSM to backup Cyrus servers: Email currently accounts for 1/3 - 1/2 of the 5 TB of backups received nightly across all of our TSM servers. We anticipate that the IMAP-Cyrus conversion will significantly reduce TB's backed up, but significantly increase the number of files backed up and, thus, our TSM database sizes. Has Cyrus - increased TSM database size been a problem at your site? Did you adjust any TSM client/server settings specifically for Cyrus backups? 2. LTO3 vs 3592 Tape Performance: (and TCO?) We also expect to replace aging 3590 tapes and drives with LTO3 and/or 3592 technology. If you have experience to recommend one/another technology, we are interested. We expect either LTO3 or 3592 technology will be satisfactory for large files, but wonder about performance for restoring someone's Cyrus email directories: perhaps several thousands of discrete, small email files scattered variously across several/many large tapes? Do 3592 tapes perform significantly better than LTO3 for many small files? 3. Use Copy Tapes?: (or NOT?) Several years ago, Yale's IT management decided that we could and would afford the loss of backup data if a tape becomes unreadable because the risk of unable to restore is perceived to be very small and manageable: The probability of a client needing to restore data (failed disk/user error) is itself very small. The simultaneous probability that a tape is unable to restore that data is much smaller. If a tape becomes unreadable, whatever backups are lost are either inactive or will be recreated with the next client backup after the damaged tape is discovered and deleted. We backup to Copy tapes all Archives (might be deleted from client) and any Backups that remain 24h on unmirrored disk (BackupPool) space. Otherwise, we do NOT use Copy tapes for most of our TSM services. In actual practice, this (Almost) No Copy Tapes policy has NOT hurt us for several years now, but management is now reconsidering whether/not to apply this policy for backups from some/all of our more important clients, and is also considering the greater potential data loss with much larger capacity tapes. We welcome your experience and considered advice regarding Copy tapes. 4. Attached file: (and replies?) Attached is a txt file detailing topics we think might be of interest. We've included Yale's information and some questions. Please send back to the list if your reply is of general interest. Otherwise, reply directly to me if you are interested to discuss any of this with us. We may want to schedule some time to talk on the phone. If you prefer that, please include phone#(s) and preferred time(s). Thank you for your time and consideration. -- [EMAIL PROTECTED] (203.432.6693) [jim (dot) owen (at) yale (dot) edu] Questions for TSM Contacts Backing Up Cyrus IMAP Servers: For each physical TSM service host machine: (1) hardware (2) operating system (3) # of CPU processors @Yale: Three IBM P650 (7028-6M2) servers, AIX, ea. w/ 4 CPU proc's. For each logical TSM service: (1) number of clients (2) amount backed up nightly (3) database size @Yale: (ws = workstation/personal computer client) TSMs1a: 3050 ws + 250 server clients, ~1TB/n, 270GB TSMdb TSMs1b: 11 server + 4 UWemail clients, ~1TB/n, 80GB TSMdb TSMs2a: 635 ws clients, ~100GB/n, 60GB TSMdb TSMs2b: 330 server + 4 UWemail clients, ~2TB/n, 80GB TSMdb TSMs3: 1420 ws + 75 server + 2 UWemail clients, ~1TB/n, 180GB TSMdb Disk backup STGpools: (1) make/model of disk hardware (2) RAID type (3) usable GB (4) Do you use a VTL or TSM Sequential Files? @Yale: TSMs1,2* backup STGpools are on SAN attached Shark 800 arrays. About 7TB total RAID5 (146gb, 10K) storage pool space on Sharks. TSMs3 backup STGpool resides on mirrored SSA disk. We are interested in, but not using VTL or TSM Sequential Files. Tape storage: (1) make/model of library, drives, tapes (2) TB of primary tape storage (3) TB of copy tape storage (4) What subset of clients have copy tapes? (5) How do you collocate? @Yale: Two IBM 3494 libr's, each w/ 6 * 3590E drives (will phase out) Two IBM 3494 libr's w/ 4 and 6 * 3590H drives (will phase out) Two IBM 3584 libr's, ea. w/ 4 * LTO1 + 8 * LTO2 drv's (to expand) Total 160TB of primary tape storage Total 42TB of copy tape storage (mostly @ TSMs3 service) WS client backups collocated by node Server and UWemail client backups mostly collocated by filespace Network environment: (1) Do you backup over public network, private network, LAN free?
? Should we set Resourceutilization 10 if appropriate ?
Andy, et al. [Is anyone out there using RESOURCEUTILZATION n w/ n 10 ??] Andy Raibeck's presentation @ Oxford's 2001 TSM Symposium http://tsm-symposium.oucs.ox.ac.uk/2001/papers/ Raibeck.APeekUnderTheHood.PDF includes this table showing what will result from setting: RESOURCEUTILIZATION n Max.Sess. ProducerSess. Threshold(Seconds) - -- default 2 1 30 1 1 0 45 2 2 1 45 3 3 1 45 4 3 1 30 5 4 2 30 6 4 2 20 7 5 2 20 8 6 3 20 9 7 3 20 10 8 4 10 (undocumented: 11=n=100) n 0.5n10 and also includes these warnings: Undocumented, internal values subject to change without notice. RESOURCEUTILIZATION 10 is unsupported. Management discourages use of undocumented/unsupported settings, but I'm arguing that we need to specify RESOURCEUTILIZATION 30 in order to effect efficient backups for our email servers: 4 IMAP servers, each w/4 CPUs, running linux client 5.2.3, each backs up 15 FS sending ~200GB/night (compressed) via 100Mb - Gb ethernet to our TSM 5.2.3 service's disk stgpool With RESOURCEUTILIZATION 10 specified, we never see more than 8 simultaneous FS backups, and some of 8 large IMAP filesystems are always the last backups to start, serially after other smaller FS backups complete! Testing w/ RESOURCEUTILIZATION 30 causes one client to start up 31 sessions enabling all 15 FS backups to start essentially simultaneously. I expect the smaller FS backups will complete first w/ the 8 larger IMAP FS backups completing later, but w/ all FS backups for each client finishing faster because none will wait to start serially after other FS backups because insufficient backup sessions were started. Asking only for your own advice, recognizing IBM probably does not allow you recommend using unsupported/undocumented optional settings: Is my understanding of the unsupported/undocumented setting (w/ N10) correct? Are we risking some unanticipated problems trying to use RESOURCEUTILIZAION 30 to backup all four of these email servers simultaneously? [I believe we have sufficient network bandwidth, disk I/O capacity and CPU's for TSM clients and service.] Is there some important reason that IBM did not choose to document and support N10 for RESOURCEUTILIZATION? [The higher settings would seem to be useful and appropriate for some high-bandwidth circumstances, or did I miss something?] Is there a simple way to specify the order in which FS are selected for backup when multi-threading is active? Thanks [hoping] for your advice! -- [EMAIL PROTECTED] (203.432.6693)
Re: Still huge problems with Mac OSX client 5.2.3.12
Farren, Is there some reason that you can't upgrade to the latest Mac TSM client: 5.3.2.? All/most of our OSX backup complaints were fixed with Mac TSM client 5.3.2.0. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Still huge problems with Mac OSX client 5.2.3.12
Farren, I don't have time now to look at the IBM/Tivoli web site for you, but we are using TSM clients 5.3.2.x with TSM servers 5.2.3.x here. I would expect any TSM client 5... to work with any TSM server 5... Unless you know/find otherwise on their website, I would download and try it. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Hi Well sadly we are still running TSM Server 5.1.6.2 as I'm still waiting for new server hardware to arrive to do the upgrade. It's been a struggle to get the money for the new kit hence I'm a little behind the times. I don't think a 5.3 client would work on a 5.1 server (though I could be wrong). Farren |-+---| | James R Owen | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 02/12/2005 09:22 |Subject| | | Re: [ADSM-L] Still huge | | Please respond to | problems with Mac OSX | | ADSM: Dist Stor| client 5.2.3.12 | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Farren, Is there some reason that you can't upgrade to the latest Mac TSM client: 5.3.2.? All/most of our OSX backup complaints were fixed with Mac TSM client 5.3.2.0. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views
?? What character escapes wildcards % and _ for SELECTing literal % or _ ??
[Hey: If you're really in a hurry, skip to the next page, and see (@), but you might miss some fun(ny, perhaps even useful?) stuff!] I just accidentally discovered [!much to my surprise!] that... The underscore _ character is the SQL SELECT standard wildcard to match any single character in the specified position, e.g., select node_name from nodes where node_name like '_A_' [lists all nodes w/ names 3 characters long w/ 'A' in the middle. [Probably] we all[ready] know [or have discovered] that... The percent % character is the SQL SELECT standard wildcard to match zero or more characters [but NOT a NULL string!] select node_name from nodes where node_name like '%-%' [lists all nodes w/ hyphenated names, and also bizarre names like '-', '+-', '1-0', '.-.', '...---...' (morse code!), etc.] Now, what I really want is a list of nodes w/ names including a literal underscore _ character so I first tried... select node_name from nodes where node_name like '%_%' [which seems to be exactly equivalent to...] select node_name from nodes where node_name like '%' [Both list all existing nodes (because node_name can't be null!)] Then I borrowed an Oracle DBA's SQL ref.manual and found... The backslash / character is the SQL SELECT standard escape used preceding a wildcard to match that (following) character literally. (@) So, I tried again... tsm: TSTselect node_name from nodes where node_name like '%\_%' ANR2034E SELECT: No match found using this criteria. ANS8001I Return code 11. tsm: TSTselect node_name from nodes where node_name like '%_OB' NODE_NAME -- xx_OB y-OB z_OB aaa_OB _OB OB tsm: TST[names partially changed to protect the innocent] !!!What to do???[Please, don't say there's no escape!] ITSM 5.2.3.0 w/ AIX 5.2 -- [EMAIL PROTECTED] (203.432.6693)
Re: Tape Stuck in Remote Status, but no longer used by library sharer; what to do?
Thanks again, Richard! Others, see also note (below) from APAR IC40865. NOTE: The local fix describes a command that should only be used if a REMOTE volume no longer has valid data on it and can be considered a scratch volume. Once executed, any server could use the volume to overwrite any existing data. Use caution whenever you delete any volume history entry. Before invoking this command ensure that the libvolume is *NOT* used in *ANY* way by *ANY* remote (Library Sharing) TSM! DELete VOLHistory TODate=TODAY Type=REMOTE VOLume=z12345 FORCE=Yes removed the bogus REMOTE record from the LibMgr TSM's VolHistory for tape Z12345 which was no longer used by any LibSharer TSM. -- [EMAIL PROTECTED] (203.432.6693) Richard Sims wrote: Jim - This may not be of much help, but the Delete command in APAR description IC40865 may help in some cases. Richard Sims On May 20, 2005, at 5:47 PM, James R Owen wrote: Andy, et al. I have no solution, but found your email thread as I'm looking to solve exactly the same problem. It's a tough nut to crack! We have 6 tapes in a shared 3584 w/ exactly that problematic status: The Library Mgr TSM's VolHistory shows tape as PRIVATE,REMOTE owned by other TSM, but the other TSM's VolHist has long since finished with the tapes: two were obsolete DBB backups (probably cancelled/aborted) the other four show UNKNOWN in the devclass field (dunno why) I believe these tapes are stuck in a crack in the Share Library reality and are essentially lost unless someone knows now to remove the useless and inappropriate REMOTE records from the Library Mgr's VolHistory. If that can be accomplished, then we can UPDate LIBVolume STATUS=SCRatch to fix the problem. I've tried CHECKOut LIBVolume... at the Library Mgr TSM, but that didn't help. The Library Sharer TSM can not do the CHECKOut LIBVolume because the library is unknown. I think the tapes have fallen into a crack in TSM's reality. Anybody else have a better grip on this? If not, I'll open a PMR. -- [EMAIL PROTECTED] (203.432.6693) Andrew Carlson wrote: On Fri, 20 May 2005 09:27:39 -0500, Ochs, Duane [EMAIL PROTECTED] wrote: You can do a delete volume ## discard=yes. This will delete all references to data on that volume from the TSM database. I had the volume checked in. The volume now shows up in q libv: tsm: TSMLIBMq libv 3584lib 110544 Library Name Volume Name Status Owner Last Use Home Device Element Type --- -- -- - --- -- 3584LIB 110544 Private TSMJ 1,0953592 But, since the volume does not show up in TSMJ (actually it was a database backup tape), I cannot delete it. Any ideas? -- Andy Carlson - Senior Technical Specialist BJC Healtcare
Re: Tape Stuck in Remote Status, but no longer used by library sharer; what to do?
Andy, et al. I have no solution, but found your email thread as I'm looking to solve exactly the same problem. It's a tough nut to crack! We have 6 tapes in a shared 3584 w/ exactly that problematic status: The Library Mgr TSM's VolHistory shows tape as PRIVATE,REMOTE owned by other TSM, but the other TSM's VolHist has long since finished with the tapes: two were obsolete DBB backups (probably cancelled/aborted) the other four show UNKNOWN in the devclass field (dunno why) I believe these tapes are stuck in a crack in the Share Library reality and are essentially lost unless someone knows now to remove the useless and inappropriate REMOTE records from the Library Mgr's VolHistory. If that can be accomplished, then we can UPDate LIBVolume STATUS=SCRatch to fix the problem. I've tried CHECKOut LIBVolume... at the Library Mgr TSM, but that didn't help. The Library Sharer TSM can not do the CHECKOut LIBVolume because the library is unknown. I think the tapes have fallen into a crack in TSM's reality. Anybody else have a better grip on this? If not, I'll open a PMR. -- [EMAIL PROTECTED] (203.432.6693) Andrew Carlson wrote: On Fri, 20 May 2005 09:27:39 -0500, Ochs, Duane [EMAIL PROTECTED] wrote: You can do a delete volume ## discard=yes. This will delete all references to data on that volume from the TSM database. I had the volume checked in. The volume now shows up in q libv: tsm: TSMLIBMq libv 3584lib 110544 Library Name Volume Name Status Owner Last Use Home Device Element Type --- -- -- - --- -- 3584LIB 110544 Private TSMJ 1,0953592 But, since the volume does not show up in TSMJ (actually it was a database backup tape), I cannot delete it. Any ideas? -- Andy Carlson - Senior Technical Specialist BJC Healtcare --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless.
? TSM STGpools on Nexsan ATABeast or EqualLogic PS200 or similar ?
Hi all, Are you using a Nexsan ATABeast or EqualLogic PS200 or similar box of disks for TSM STGpool space?? If so, we would like to talk with you about your experiences. We are now considering moving 40TB of TSM backups from 3590E tapes to sequential files on one/more of these boxes (or perhaps onto the vendor's box that you like best?) If you have experience to share, please reply directly, with your phone# and best time(s) to call, and we'll call you back. Thanks for your help. I'll summarize what we learn, back to the list. -- [EMAIL PROTECTED] (203.432.6693)
? replace aging 3590 tapes/drives w/ LTO ?
We're looking for experienced advice considering whether to a)upgrade our 3590 E1A drives to H1A drives and reuse our aging 3590 tapes for net gain of 50% more tape space b)discard 3494 and 3590 technology and replace w/ LTO-2 or LTO-3 drives and media, expanding our existing 3584 ATL's currently filled w/ LTO-1 media and mixed LTO-1/2 drives. If you have considered or done one of these conversions, we would like to hear from or talk with you. If you don't feel like writing a reply, please send me a phone# and we'll try to call you. Yale University started using 3590 tapes 8 years ago in 1996. We now have two 3494 ATL's, each w/ six 3590 E1A drives, and about 4000 J tape cartridges, most of them 6-8 years old. The warranted life of a 3590 cartridge is 10 years, so... we are wondering what other sites are thinking/doing about your aging 3590 media and hardware. To date, our actual 3590 media failures are insignificant: about 40-50 tapes over the 8 years or 1-2% real failed media. [But how much longer can we expect them to last: 5-10 yrs?] That's eliminating all of the false failures where the 3590 drive actually was at fault; if the tape passes an AUDit Volume and doesn't get errors on another drive, we UPDate the volume back to ReadWrite status and keep on using it, unless it fails again! We also re-attach leader blocks, if they get pulled off, and continue to using the tape if it loads OK. We've only had to fix 6 of those, but 3 became detached during the past 2 weeks! We've had a rough two weeks with one of our 3494 ATL's, but problems seem to occur in fits and spurts. After a few months w/ no problems, we've called IBM 8 times during the past week to service 3590 problems in our busiest 3494 (but had no problems w/ the other one!) During the busiest hours of each afternoon (migrating small clients' backups from disk to collocated 3590 tapes) each of the six 3590 drives mounts (and dismounts) 20 tapes/hr or 120 tapes/hr for the 3494 robot. The library is typically that busy for 5-7 hours each day, then much less busy for the rest of the day and night, mostly doing 3590 tape reclamations. Please advise, if you have experience to share. Thanks for your help. -- [EMAIL PROTECTED] (203.432.6693)
? how to protect LTO media shipped offsite to Iron Mountain ?
How do you protect LTO media shipped offsite to Iron Mountain? We currently ship all backupsets offsite to Iron Mountain on 3590 J cartridges w/ no noticeable problems; we just pack as many tapes as will fit tightly into one of Iron Mountain's metal shipping cases. We've been told that LTO cartridges are much more susceptible to damage and have never ejected or shipped any of them offsite. I'm thinking any ejected LTO tapes should at least be put back into their original plastic cases before being packed (how?) into a Iron Mountain shipping case, but what do you do? Have you had any problems shipping LTO tapes offsite? Thanks for sharing your experience and advice. -- [EMAIL PROTECTED] (203.432.6693)
? appropriate Throughput Thresholds w/ 10-100Mb TSM clients?
Recently, the AIX 5.1 host for our busiest TSM 5.2.3.0 service, has been running at 100% CPU for most of the night, some mornings and even into some afternoons. We have discovered a few of our clients (using inappropriate network settings, typically Auto-Dectect instead of matching the network switch...) have poor performing, very long running backup sessions that are exhausting the CPU. TSM provides two server options: ThroughputTimeThreshold = MMM [seconds] ThroughputDataThreshold = NNN [KB/sec] to be set causing the TSM service to cancel any client session that does not perform better than NNN KB/sec after MMM seconds. Has anyone determined appropriately conservative settings for these options with TSM client network connections varying from 10Mb,Half-Duplex up to 100Mb,Full-Duplex? We're aiming to kill the network mis-matched clients and don't want to suffer with them for too long, but we don't want to kill a client that might be legitimately slowly progressing through a huge directory. Please respond if you've already solved this problem satisfactorily at your site. Thanks for your help. -- [EMAIL PROTECTED] (203.432.6693)
?Linux TSM service to backup 100 clients to disk-tape?
Hi Linux TSM Sys.Admins! None of you responded to my previous query, so I'm trying again. We are considering to use RedHat EL 3.0 on IA32/64 platform (rather than AIX on p-series) to host an additional I/O intensive TSM service (to split our current service and handle half of future growth.) We are hoping to build based upon others' experiences. Are you already using or actively planning to use Linux (RedHat EL 3?) to host an I/O intensive TSM service similar to any described under the recent ADSM-L thread, Sizing an AIX platform and tape libraries? If not, do you have a Linux TSM service backing up 100 clients to disk - tape storage? Please describe what you have and what limits you think might apply to your set up (or reply w/ a phone# if you would rather just talk.) Thanks for any advice you care to share! -- [EMAIL PROTECTED] (203.432.6693) = = = from my previous posting= = = We believe we are approaching the maximum that can be achieved w/ TSM:v5.2.1.3 OS: AIX 5.1 (64bit) CPU:IBM 7025-6F1 w/ 4 * 750Mhz proc's + 3GB RAM SAN:1 Gb w/ EMC Symmetrix 8830 LAN:1 Gb Ethernet ATL:IBM 3494 w/ 6 * 3590E drives IBM 3584 w/ 4 * 3580 LTO1 + 2 * 3580 LTO2 drives This configuration is successfully supporting our current ITS TSM service (see details below), but we believe we either need a major performance boost or to split this load onto an additional host platform: Linux, Win*, or must we remain w/ AIX for I/O performance? to handle expected additional growth. Which platform have you chosen (or would you choose) for similar TSM service? Yale ITS TSM Service: Active Clients: 2400 = 3d, 2500 = 7d, 2700 = 35days Servers:151 WinNT,2K* 105 Linux 20 Solaris 9 AIX 7 SQL-BT (Oracle) 3 Mac 2 TDP's: MSSQL,MSexchg: 2 + 1 [new]2 Personals: 2549 WinNT,2K*,XP 2230 Win98,ME26 Mac183 Linux 50 Solaris 5 AIX,DEC*X,HPUX,IRIX: 1 ea. [new] 51 Expected growth: +500-600 clients for several years +20% data for existing clients/year? TSM DB: 75.7% of 160GB BAckup DB w/ LTO1 HCmpr. takes 2.3h EXPIre Inv examines ~6M obj, deletes ~1M obj. in 8-9h Disk STGpools: 600 + 180GB Nightly Backup Period: 15:30-08:00+ Weeknight Backup Load: 500-650GB+ Thanks for any experience/insight you are willing to share with us! -- [EMAIL PROTECTED] (203.432.6693)
?Can Linux or (Win?) replace AIX for I/O intensive TSM service?
?Can Linux (or Win?) replace AIX for hosting an I/O intensive TSM service? After scanning the past year's ADSM-L postings including Linux in the subject I have the impression that a few people are playing with Linux hosting a TSM service, but real I/O intensive TSM services are still mainly hosted by AIX. ?Is anyone already using or actively planning to use Linux (RedHat EL 3.0?) to host an I/O intensive TSM service similar to any described under the recent ADSM-L thread, Sizing an AIX platform and tape libraries? We believe we are approaching the maximum that can be achieved w/ TSM:v5.2.1.3 OS: AIX 5.1 (64bit) CPU:IBM 7025-6F1 w/ 4 * 750Mhz proc's + 3GB RAM SAN:1 Gb w/ EMC Symmetrix 8830 LAN:1 Gb Ethernet ATL:IBM 3494 w/ 6 * 3590E drives IBM 3584 w/ 4 * 3580 LTO1 + 2 * 3580 LTO2 drives This configuration is successfully supporting our current ITS TSM service (see details below), but we believe we either need a major performance boost or to split this load onto an additional host platform: Linux, Win*, or must we remain w/ AIX for I/O performance? to handle expected additional growth. Which platform have you chosen (or would you choose) for similar TSM service? Yale ITS TSM Service: Active Clients: 2400 = 3d, 2500 = 7d, 2700 = 35days Servers:151 WinNT,2K* 105 Linux 20 Solaris 9 AIX 7 SQL-BT (Oracle) 3 Mac 2 TDP's: MSSQL,MSexchg: 2 + 1 [new]2 Personals: 2549 WinNT,2K*,XP 2230 Win98,ME26 Mac183 Linux 50 Solaris 5 AIX,DEC*X,HPUX,IRIX: 1 ea. [new] 51 Expected growth: +500-600 clients for several years +20% data for existing clients/year? TSM DB: 75.7% of 160GB BAckup DB w/ LTO1 HCmpr. takes 2.3h EXPIre Inv examines ~6M obj, deletes ~1M obj. in 8-9h Disk STGpools: 600 + 180GB Nightly Backup Period: 15:30-08:00+ Weeknight Backup Load: 500-650GB+ Thanks for any experience/insight you are willing to share with us! -- [EMAIL PROTECTED] (203.432.6693)
Re: Expiration of SQL BackTrack Filespaces
Rob, Like David said, etc... During SQL-BT setup, you should have created a MC for SQL-BT backups w/ Backup CopyGroup w/ VerExists=1 VerDeleted=0 RetExtra=0 RetOnly=0. SQL-BT incorporates datime values in its TSM backup filenames so that each backup filename is unique; if you setup SQL-BT to keep 10 versions, you might have 11 dbf backups (uniquely named Active TSM backup files) until SQL-BT dtoexpire processing runs. Then, SQL-BT expires a backup version by marking the appropriate TSM backup files Inactive. During the next TSM EXPIre Inventory processing, these Inactive backup files are deleted immediately (because your SQL-BT-MC B-CG has VerD=0.) Some tape space can be reclaimed immediately (during EXPIre Inventory processing) iff your tape STGpool is collocated by filespace and one/more tape(s) no longer contain(s) any Active SQL-BT backups. Otherwise, you have to run tape reclamation processing for that STGpool to recover the partially available tapes for reuse. -- [EMAIL PROTECTED] (203.432.6693) David Longo wrote: It handles expiration like Oracle RMAN (in general). The expiration is done by the client, not the normal versioning of TSM. The SQL-BT setup and config should have info on setting up Management Class on TSM for this. I have SQL-BT version 4.2 on AIX Sybase Client. The config on SQL-BT allows you to specify how many versions you want to keep, and SQL-BT expires old version each day when it does a backup. Whether the data went to TSM disk pool first and then to tape or directly to tape has no bearing at all on the expiration. [EMAIL PROTECTED] 01/21/04 10:39AM Hello all, How does TSM handle the expiration of SQL Backtrack filespaces if the data was originally written directly to tape, thus never existing on hard disk? We have a situation where these filespaces are not expiring and are not even being marked as inactive yet they are in a MC that is set to retain only ten versions. TSM Server: 5.1.5.5 OS Version: AIX 5.1 SQL BT Version: 3.4.10 TIA, Rob
Error 2 deleting row from table Expiring.Objects [was Re: Auditdb timing]
Gretchen, et al. We have been working with IBM level 2 support on this same problem. We discovered it while trying to delete a SYSTEM OBJECT filespace, but the problem first appears during the SYSTEM OBJECT backups. We currently have 3 errors recurring nightly: tsm: ITSq act begind=-1 se=.c( 05/26/2003 20:02:57 ANR0104E imbkins.c(3632): Error 2 deleting row from table Expiring.Objects. 05/26/2003 20:37:47 ANR0104E imbkins.c(3632): Error 2 deleting row from table Expiring.Objects. 05/26/2003 21:20:04 ANR0104E imbkins.c(3632): Error 2 deleting row from table Expiring.Objects. 05/27/2003 13:38:28 ANR2017I Administrator OWEN issued command: QUERY ACTLOG begind=-1 se=.c( tsm: ITSq act begind=-1 se=ANR0530W 05/26/2003 20:02:57 ANR0530W Transaction failed for session 16941 for node X (WinNT) - internal server error detected. 05/26/2003 20:37:47 ANR0530W Transaction failed for session 17040 for node X (WinNT) - internal server error detected. 05/26/2003 21:20:04 ANR0530W Transaction failed for session 17623 for node T (WinNT) - internal server error detected. 05/27/2003 13:44:00 ANR2017I Administrator OWEN issued command: QUERY ACTLOG begind=-1 se=ANR0530W Node X is WinNT 5.00 (Win2K) running TSM client v4.1.2.12. Node T is WinNT 5.00 (Win2K) running TSM client v5.1.5.15. These nodes and two others similar to T already have OLDSYS-XX (renamed SYSTEM OBJECT) filespaces that can not be deleted without manually recreating missing bitfile object IDs for one or more objects. The first time around, IBM level-2 support directed me through the following iterative manual process: [*5 filespaces * 3-7 missing BFOs] try to delete the OLDSYS* filepsace loop: while delete filespace fails w/ missing BFO for object# show invo 0 object# [typically found] show bfo 0 object# [not found; caused del fi failure] manually add table row, populate all the fields, check it, etc. try to delete the OLDSYS* filespace end loop Here's hoping that IBM will develop a cleanup for... or simply automate the fixing of... missing Expiring.Object BFOs. I forwarded Gretchen's and Henk's emails to IBM level-2 support. Run these queries to see if this problem lurks on your TSM service: Query ACTlog BEGINDay=-1 SEarch=.c( Query ACTlog BEGINDay=-1 SEarch=ANR0530W Good luck! [Here's hoping this is the last of SYSTEM OBJECT problems.] -- [EMAIL PROTECTED] (203.432.6693) Gretchen L. Thiele wrote: I've been plagued by a few problems when deleting accounts. So far, it seems like Win2K or WinXP clients (SYSTEM OBJECTs are involved again!) are prone to this error: 05/27/2003 09:00:56 ANR2017I Administrator XX issued command: DELETE FILESPACE ZZ * 05/27/2003 09:00:56 ANR0984I Process 185 for DELETE FILESPACE started in the BACKGROUND at 09:00:56. 05/27/2003 09:00:56 ANR0800I DELETE FILESPACE * (fsId=6) for node ZZ started as process 185. 05/27/2003 09:00:56 ANR0802I DELETE FILESPACE * (fsId=6) (backup/archive data) for node ZZ started. 05/27/2003 09:00:57 ANR0104E imutil.c(7761): Error 2 deleting row from table Expiring.Objects. 05/27/2003 09:00:57 ANRD imfsdel.c(1872): ThreadId25 Error 19 deleting group leader 0 176658713. I've tried a number of things - renaming the filespace, moving the node data and then auditing the tape, deleting the filespace specifically - but it's really a database 'corruption' and can only be fixed by an audit (per support). Gretchen Thiele Princeton University
can a mgmtclass be specified for SYSTEM OBJECT sysfiles?
Andy, Is it possible to specify a mgmtclass for SYSTEM OBJECT sysfiles? We have tested and successfully implemented exclude.systemobject sysfiles for 350 Win2K/XP clients [no active/inactive sysfile backups remain for these clients], but we have an additional 650 Win2k/XP clients that are still actively backing up ~2200 sysfiles/client daily. The active policy set for these nodes contains two management classes with the following backup copygroup settings: PolicyPolicyMgmt Copy Versions Versions Retain Retain DomainSet Name Class Group Data DataExtraOnly NameName NameExists Deleted Versions Version - - - - --- YOD ACTIVEEXPIRING STANDARD 100 0 YOD ACTIVESTANDARD STANDARD 21 35 60 Before I exclude sysfiles from backup, I would like to specifically include them to backup with our EXPIRING management class so that sysfiles will be eligible for immediate deletion by EXPIre Inventory processing the next day after I exclude them from backup, rather than having to wait for the STANDARD RETOnly=60 days to pass. Adding the following line to dsm.opt: Include SYSTEM OBJECT sysfiles expiring does not generate any error, but I doubt that it's doing what I had hoped! Is it possible to assign a specific mgmtclass for SYSTEM OBJECT sysfiles? -- [EMAIL PROTECTED] (203.432.6693)
?Can LTO replace 3590E tape for busy TSM backup/restore service?
??? Do you have experience w/ or plans for replacing 3590E with LTO tapes for a busy enterprise TSM backup service? Is LTO performance OK ??? We expect to double business for one of our TSM services over next 4 years. Last year, for space and cost savings, future enhancements, etc... we bought new LTO (100GB/tape) libraries to use for Copy STGpools, replacing existing 3590E (20GB/tape) Copy STGpools which made all of those 3590E tapes available to expand our primary STGpools.) Now, we are considering whether we can use LTO tapes for new primary tape STGpools or should we continue to expand our existing 3590E tape STGpools? We have performance concerns about using LTO tapes for primary STGpools! Our current environment: --- TSM v4.2.3.2+ (upgrading to v5... soon, before 5/2003) AIX v4.3.3 (upgrading to v5... soon, before 5/2003) IBM 7025-6F1 w/ 2*600Mhz CPUs and 1GB memory IBM 3494 w/ 6 3590E drives for 1700 primary backup tapes IBM 3584 w/ 4 3580 LTO drives for 300 copy + 10 TSM DB backup tapes 2700 active clients (100 Servers, 2500 Win*,Mac,Linux,etc. PC's) backup 5-600GB/night (some 1-4GB files, mostly much smaller files!) TSM DB: 74-76% of 120GB TSM LOG: 12GB (w/ LOGM=R needs 1 full + 1-2 incr.DB bkups daily) Our expectations for next 4 years: - clients: +25%/year, @+4 years = +2800 clients: +100 S, +2700 PC's backups: +25-50%/year, @+4 years = 2-4 * current backup load! how: ??? replicate another or super-size current TSM service? Our current LTO tape experience: --- We use LTO tapes ONLY for an online Copy STGpool and TSM DB backups. LTO seems to be ~100% faster than 3590E tape for TSM Backup DB... LTO can be 30-50% slower than 3590E tape for TSM BAckup STGpool... w/ EMC SAN disks or 3590E tapes - LTO vs 3590E Copy tapes. LTO can be 30-50% slower than 3590E tape for our online Copy STGpool reclaiming LTO Copy tape - LTO Copy tape vs 3590E - 3590E. Do you see similar or better performance? Our concerns about replacing 3590E w/ LTO tapes for primary STGpools: We are worried about start/stop and seeking performance using large capacity LTO tapes for restoration or reclamation of aggregated small/medium-sized files on semi-collocated tapes. [We use collocation, but currently have 350/1700 filling 3590E tapes available for 2700 clients, so we often have multiple clients' backups sharing the same 3590E tape. This problem could be much worse with 100GB LTO tapes as we might have only 70/320 filling LTO tapes.] Even w/ full-collocation, we believe restoration/reclamation of a highly active client's aggregated backups of many small/medium-sized files might involve substantial start/stop and seeking operations and would probably perform poorly on LTO when compared to 3590E tapes. Are our concerns warranted? -- In IBM's 2003-01-28 announcement of new Ultrium 2 LTO technology, the last paragraph under the heading Product Positioning states: For mission-critical data protection, optimized for enterprise multi-mode and host attachment, high-cycle and start/stop intensive tape applications, consider the proven IBM TotalStorage Enterprise Tape Drive 3590 or the IBM TotalStorage Enterprise Automated Tape Library 3494. Are TSM restores and reclamation of aggregated files start/stop intensive? Has anyone done TSM performance comparisons of LTO vs 3590E for: --- - DR or FS restore from (semi-collocated) tapes? - primary (semi-collocated) tape-tape reclamation? Thank you for any experienced advice you will share with us. -- [EMAIL PROTECTED] (203.432.6693)
Re: TSM 4.2.1.30 scheduler dies intermittently....
My coworker says there's a known problem with Norton AV 7.5 and TSM 4.2 that can cause the TSM scheduler to stop; could that be your problem? Check w/ Tivoli Support. -- [EMAIL PROTECTED] (203.432.6693) Andrew Raibeck wrote: You should contact IBM support if you are having this kind of problem. I am not aware of any problems that could cause what you are seeing. If you haven't already done so, take a look at the Application and System Event logs to see if anything abnormal was logged. You also might check the dsmerror.log file, the dsmwebcl.log file (if using the CAD to manage the scheduler), and the server activity log from the time the client backup began through the time it terminated, to see if anythere there might shed some light on the problem. 4.2.1.30 is the latest patch level. Normally we don't steer customers to patches from the web site because the patches should only be applied (in theory) at the direction of IBM service or development to resolve specific problems. However, due to substantial problems at the 4.2.1.0 level, we do not recommend that users install that level; so when we issued 4.2.1.20, we did more extensive testing of that client code than is usual for a patch. That is why the web site points to it. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS 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. Keith Kwiatek [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 04/10/2002 08:15 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:TSM 4.2.1.30 scheduler dies intermittently Hello, I have 900 tsm total TSM clients. Everything has been running fine, but I have 20 new clients that have installed TSM 4.2.1.30 on their win2000 machines. The tsm scheduler starts fine, and at the correct time begins a backup. But sometimes the scheduler just dies. Doesn't leave errors messages. I look at the end of the dsmsched.log and I can see that it was in the process of backing up (files are being sent'), but then it just ends. The last entry is just a file being sent to the server, and then nothing. The scheduler is stopped in services. The machine is not being powered down. There is no power managment. These are experienced users. One curious thing is that Tivoli now has 4.2.1.20 as the latest win2000 client -whereas I had downloaded tsm 4.2.1.30 not too long ago (??) Why are they going backwards? Any and all help is appreciated!! Keith
Re: HELP - Solaris backup problem!
Dwight, You thought correctly: specify domain in dsm.opt, not in dsm.sys! But, the default domain is all_local fs, so normally one doesn't need to specify domain... anyway! Perhaps your automatic backups are not being run by a priviledged user or you have some client schedule(s) that include a domain option? Check to ensure that - dsmc schedule command is invoked by root @ clients w/ missing fs backups - schedules with which clients are associated do not restrict domain Otherwise, unless you get better responses, I would check w/ TSM support. Good luck! -- [EMAIL PROTECTED] (203.432.6693) Dwight R. Wood wrote: My dsm.sys has the inclexcl defined, however, I thought the domain statements should be in the dsm.opt file. Do I need to have the domain statements in the dsm.sys or the dsm.opt? Anyone? From: Cross, Ric [EMAIL PROTECTED] Reply-To: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: HELP - Solaris backup problem! Date: Mon, 30 Jul 2001 10:48:41 -0400 Try adding the inclexcl and domain parameters to your dsm.sys file : inclexcl /opt/tivoli/tsm/client/ba/bin/inclexcl.lst domain / /usr /home /apps /tmp /apps/b2b /usr/local/source My inclexcl.lst looks like this : exclude /opt/tivoli/tsm/client/.../*.log exclude /.../core exclude.fs /tmp We did run into some problems with the Sun backups but it's been too long to remember the specifics ... just know they were inclexcl and domain related. Ric Cross Lead Integration Engineer WorldCrest 1600 RiverEdge Parkway, Suite 100 Atlanta, Georgia 30328 -Original Message- From: Dwight R. Wood [mailto:[EMAIL PROTECTED]] Sent: Monday, July 30, 2001 10:26 AM To: [EMAIL PROTECTED] Subject: HELP - Solaris backup problem! Has anyone experienced this before: I have many Solaris 2.6 and 2.7 machines getting backed up to a TSM server on Solaris (4.1.2). Each night the backups run with a 'completed' report. But I have run into a HUGE problem. When the backup runs automatically at night, it misses almost the entire file system. I have a machine that has missed the /, /opt, /usr /var directories every time it runs. But when I run a manual backup, 'dsmc inc', everything gets backed up. And the include/exclude file has nothing in it to exclude these directories. Does anyone know of this problem? Any info would be helpful. Thanks! Dwight Wood _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
TSM vs AIX mirroring vs SSA RAID w/ FastWriteCache
Andy, Would you please update us again on the issue of mirroring vs RAID for TSM log and database volumes. Looking back in the ADSM-L logs, I believe your most recent recommendation (June, 1998) was to continue using TSM mirroring w/ Sequential Writes to protect against "partial page writes" which could be propagated to the other mirror(s) if using operating system or hardware mirroring. Have circumstances changed/improved since then? We are specifically interested in the following circumstances: 1. An IBM consultant has recommended using SSA RAID 1 or 10 mirroring w/ 6225 (4-P) SSA 160 SerialRaid Adapters w/ FastWriteCache enabled to protect and optimize performance of our Oracle database. Can we safely use the same to protect and optimize performance of TSM log and database volumes, eliminating the need for TSM mirroring? (Our current understanding is that FastWriteCache w/ battery- protected cache memory will eliminate the "partial page write" problem. Is our understanding correct?) 2. Has anything improved w/ AIX logical volume mirroring to lessen or solve the problem of "partial page write propagation?" 3. If we must continue to use TSM mirroring, what are the performance implications? Management wants to know how much of a "performance hit" we incur by continuing to protect our TSM DB (raw logical) volumes w/ TSM vs AIX vs RAID1 mirroring. a. Does TSM optimize page reading across TSM-mirrored volumes? b. Are there any other performance mitigations that TSM-mirroring offers that we might not have considered? 4. Our 50-60GB TSM database is currently TSM-mirrored on 3 pairs of 18GB + 1 pair of 9GB SSA disks, each containing a single Raw Logical Volume. We believe we know "what we can't/shouldn't do w/ RLV's so that we don't damage the TSM volumes" and we continue to believe that RLV's are simpler more efficient than JFS files for TSM volumes. a. Has TSM changed since ADSM v3.1 such that we should convert from RLV's to use JFS file volumes for efficiency? b. If so, should we define 1 JFS file/disk or another configuration? c. If/When our TSM DB grows 60-70GB are we better off w/ 4 * 18GB SSA 160 disks or 8 * 9GB (older SSA) disks. Thank you so much for your help and consideration! -- [EMAIL PROTECTED] (203.432.6693)
Re: Cleaning Carts (Recyclable?)
Do you remember the "continuous" cloth toweling that once was dispensed "one area per pull" for wiping hands, etc. in the public toilet lavatory facilities of American bus, train, and gas stations? (Yeah, I'm over 50...) Who knows? Suppose the janitor doesn't have a clean roll, so he recycles the same roll through the dispenser again. Are you feeling lucky (or yucky?) My guess is that a cleaner cartridge is like a rope in having a "working load" rating that is lower than the "breaking point." If you find that 3590 cleaning cartridges rated for 100 swipes can actually clean effectively for substantially more swipes, please post your results back to the list. (We are currently saving our used cartridges, in case you get good results !;*) Allen Barth wrote: Richard is correct in once a "cart" is ejected from the 3494, the vol info is deleted from the 3494 database. However, both our operators and I have re-inserted 'used up, ejected' cleaner carts and the 3494 happily uses them again. So the question then becomes "Are these cleaner carts doing anything usefull?" -- [EMAIL PROTECTED] (203.432.6693)
Re: backup of /tmp on AIX 4.3.2, TSM client 4.1.1
Try: dsmc incremental -subdir=yes /tmp/sumpin/ That works w/ AIX 4.3.2 ADSM client v3.1.0.7! Is the TSM client v4.1.x "Broken, As Designed"? Richard Sims wrote: We have a situation where we need to backup /tmp/sumpin and can't get this overridden no matter what we do with include statements or client option sets. Can anyone help? The product should allow the customer to do this if the customer wants to, though the developers will not allow us to do it. What we have left is 'dsmc Archive /tmp/sumpin', which does work. Richard Sims, BU -- [EMAIL PROTECTED] (203.432.6693)
