Re: Restoring Drive Paths
Jon, >From the Help in the TSM 5.3.3 Admin, When the destination is a drive >>-UPDate PATH--source_name--destination_name---> >--SRCType--=--+-DATAMover-+--++> '-SERVer' '-AUTODetect--=--+-No--+-' '-Yes-' >--DESTType--=--DRive--LIBRary--=--library_name-> >--++--++---> '-DEVIce--=--device_name-' '-ONLine--=--+-Yes-+-' '-No--' >--+--+>< | .-,--. | | V| | '-DIRectory--=directory_name-+-' So to put a server-connected drive back online, the command would be: UPDATE PATH server_name drive_name SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=library_name ONLINE=YES Note the two "T"s in "DestType". That threw me for a little bit. For example, to submit that same update to my LTO drive #2, connected to my "adstar" server, the command would be: UPDATE PATH ADSTAR LTODRV2 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=LTOLIB ONLINE=YES And in the syntax diagrams, you can abbreviate the commands to just the path shown in ALL CAPS in the diagram. Hope this helps. Tab Trepagnier TSM Administrator Laitram LLC "ADSM: Dist Stor Manager" wrote on 06/30/2006 07:27:16 PM: > Hello, > > I am backing my colleague up while he is on vacation. I had a tape > malfunction yesterday. I successfully removed the tape from the drive > and checked it back in as scratch (it was not an output volume) and > marked the drive online. and the put the drive online. However, the > path is down. I can't quite figure out the syntax of the UPDATE PATH > statement to update the path. Will someone take pity on me and lend me > some advice? :-) > > > With regards, > ___ > > Jon R. Adams > Infrastructure Technical Support, OSS > Premera Blue Cross > Work: 425-918-5770 / mailto:[EMAIL PROTECTED]
Re: adsm.org searches
Andy, Thanks. I searched the archives with "journal or jbb" and got 67 hits. Much better!! Tab "ADSM: Dist Stor Manager" wrote on 06/19/2006 01:43:33 PM: > I can't answer your question, but I do not use adsm.org to search the > archives. > > Try http://www.mail-archive.com/adsm-l@vm.marist.edu/ > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Development > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] > Internet e-mail: [EMAIL PROTECTED] > > IBM Tivoli Storage Manager support web page: > http://www-306.ibm. > com/software/sysmgmt/products/support/IBMTivoliStorageManager.html > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" wrote on 06/19/2006 > 11:34:17 AM: > > > What am I doing wrong? > > > > I'm trying to search adsm.org for user experiences with Journal-Based > > Backup (JBB). > > [snip] > > Thanks. > > > > Tab Trepagnier > > TSM Administrator > > Laitram, L.L.C.
adsm.org searches
What am I doing wrong? I'm trying to search adsm.org for user experiences with Journal-Based Backup (JBB). If I search for "journal" I set about 25 hits, including a couple of porn hits - on the forum site. If I search for "JBB" I get no hits at all. Ditto if I combine the two terms with "or". No hits. Is there something wrong with the search function of the site? Or is this a local PC problem? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Backing up UNC paths
We just started upgrading our TSM clients to V 5.3.4, connecting to our V 5.3.3 server. On one of our Windows clients, we've historically backed up one specific folder via a UNC path in order to make that its own filespace in TSM. That has worked perfectly for the three years or so that we ran V 5.1. Yesteday when I tried to configure the V 5.3 client to perform the same UNC backup, it wouldn't work. Even though I was signed in as domain administrator, I couldn't select any paths under "Network" in the client GUI. Nor could I specify any network paths in the client setup wizard. I tried configuring with and without Domain statements in dsm.opt file, and with/without Include statements for the UNC path. In no case could I see, specify, use, whatever, any UNC path in the client or wizard. This is a file server with about 100 Shares in Windows, any of which should have been a candidate network backup path. The manuals seem to indicate that what I'm trying should - still - work. Any ideas on why it isn't? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Multi-process reclamation - THANKS
This one is positive. TSM 5.3.3.0 on AIX 5.3 ML-4 One of the new features of TSM 5.3 is the ability to have more than one reclamation process for a storage pool. To whoever designed and implemented that, I say "Thank you." Our copypool is hosted on a 5-year old HP DLT library with four DLT8000 drives. Average sustained throughput is 8 MB/s per drive. We run maintenance weekly, including copypool reclamation. Normally that reclamation starts on Tuesday evening and runs through mid-day Thursday, re-writing about 500 GB of data to the output volumes. Last week I configured the copypool to use two reclamation processes. Reclamation started at 6 PM Tuesday as normal. When I came in Wednesday morning, it was finished and had written about 480 GB. That's 1-1/2 _DAYS_ faster than before! So, again, thanks for the great enhancement. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: File devclass change at server 5.3.x
We have now found ourselves to be victims of this change. TSM 5.3.3.0 on AIX 5.3 ML-4 For years now we've used a FILE storage pool for directories with good results. Now our directory storage pools are "full" because they've hit their MaxScratch limit, mostly by allocating volumes holding 100KB - 2 MB in a DevClass specifiying 50 MB volumes. Last night over 40 node sessions failed. I checked APAR IC48331 for an update. Aside from some workarounds that *might* offer a little relief, there isn't much there. Does anyone know of any other updated information? Or if there is an updated set of recommendations? Rarely do "upgrades" cause a 20-fold increase in system failures, but that is exactly what happened to us. Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C. Dave Frost <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 02/21/2006 08:56 AM Please respond to "ADSM: Dist Stor Manager" To: ADSM-L@VM.MARIST.EDU cc: Subject:File devclass change at server 5.3.x Hi *SMers At server version 5.3, there is an undocumented feature change to the FILE devtype (see IC48331) such that the minimum write size is now 256K. For most files, this is not a problem. However, if like us you have a disk based directory storage hierarchy (random_access -> disk-sequential_primary; disk-sequential_copypool), then this is a disaster. We used disk sequential so that we could reclaim aggregates. On average, we normally saw a total disk usage of 5-10GB max, with each full volume initially reading 100%, and containing 40,000+ directory objects per 64MB file. Now we are seeing a newly written Full volume (from reclamation) with a maximum of maybe 0.7%, and containing as many as 400 directory objects in a 64MB file. Required disk space naturally has gone through the roof. The circumventions in IC48331 have not had a terribly significant effect - a few tenths of a percent only. For the moment, we are increasing the size of the DIRS random access diskpools, not migrating out to serial disk, and ignoring the (hopefully minor) hit on fragmentation. But this still leaves the copypool. At one time, we used to backup up the DIRS pools to tape. Then we tried to reclaim a tape volume that must have been in use for more than a year, but still only had a percent or two used. After a few days of continuous reclamation we gave up, and deleted the volume, then discarded the tape. So for pure DIRS storage, tape is not a good option. So far, the only useable circurmvention we can see is to use server-to-server virtual volumes for copypool, and not to use seqential disk file for primary storage. Is there a better way? Regards Dave I think it's a beautiful day to go to the zoo and feed the ducks. To the lions. Dave Frost Technical Consultant SunGard Availability Services (UK) Limited London Technology Centre Heathrow Corporate Park Hounslow UK. TW4 6ER Tel: +44 (0) 800 2799 166 Fax: +(0) 20 8080 8112 mailto:[EMAIL PROTECTED] Keeping People and Information Connected (TM) http://www.availability.sungard.com
Re: TSM and Diskxtender - Windows
Tom, We've seen the same phenomenon. We have TSM 5.1.7 running in a Windows 2003 Sp1 file server with almost 2 million files. The file server is itself running on VMWare and connected to LUNs on our EMC Clariion SAN. 1.5 years ago, that same server had 1.7 million files, was a physical server, and used direct-attached disks. Backups took 3 hours. Now with the mix of products and technologies I've listed, backups are taking *more* than 24 hours, meaning we're backing up that server every other day. Here's the odd part: The Clariion, DiskXtender, and VMWare are all EMC products. We submitted a description of our problem to all three divisions. * DiskXtender support said they don't support installing into a virtual server; sucks to be us. * Clariion support suggested we group our ATA LUNs so that all the LUNs in any RAID group are on the same storage processor. * VMWare support suggested changing the server from a 2-way to a 1-way server and removing its affinity from processor 0. So far we've done everything recommended to us, mostly by VMWare, but it hasn't fixed anything. This problem does not just affect backups. It also affects anti-virus scheduled scans, file searches, and enumerating contents of folders with many child objects. In other words, it appears to be a directory-scanning issue, not a backup issue. I don't have an answer for you. Only my experience that what you're seeing is happening elsewhere, too. Note that we are planning to upgrade our entire TSM system to V 5.3.3+ in about a week. We'll see if that makes any difference. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 05/18/2006 03:24:16 PM: > TSM Window Client 5.2.3.4 > TSM Server 5.2.2.5 > Diskxtender 5.6 > > We have a large Windows box with millions of files on it. We utilize > the HSM components of Legato/EMC Diskxtender to migrate the unused files > to TSM media. We have the Diskxtender option set to NOT recall a file > when the accessing program is TSM. > > With all that said, the incremental backup of these millions of files > takes too long. One of my co-workers thinks he read somewhere (cannot > find again) that there is a way to have the TSM client not interface > with the TSM server for migrated files. IE, to completely skip a file > that is migrated, and not do the normal comparision to determine the > file has changed/not changed. > > Has anyone ever heard of something like this? If so - what is the > process? > > Thanks in advance... > > -Tom
Best way to integrate Microsoft VSC with TSM?
TSM Server 5.3.3 on Windows 2003 SP1 TSM Client 5.3.new on Windows XP and AIX 5.3 Data storage: 200 GB disk and IBM 3583-L18 We are planning to implement an enhanced TSM system in one of our remote offices. That scheme would involve use of Microsoft Volume Shadow Copy (VSC) on the data stored on our file servers at that site. Servers other than our file servers would rely upon traditional TSM incremental-forever backups. File versioning for restores would be done in VSC. TSM would still be used for DR via DRM and a copypool on the 3583. What is the best way to implement such a scheme? I know that TSM 5.3 uses VSC to protect the Windows OS and we plan to use that. But what about the data? And how does a restore of the VSC data recovery volume work? TIA Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Throttling back TSM client
Paul, I know it's been a while since you posted this but I wanted to share my insights. We've received the same complaints. The problem is not TSM per se, but the fact that I/O is interrupt-based and the interrupt service routines run at high-priority. This also affects any scan process, including anti-virus. For years, the AV writers set their software to scan at the lowest possible priority, only to have it create a huge impact on the machine anyway. No matter how low a priority the process runs, once it tells the storage system to read a file, that file read will run at high priority until it completes the transaction. On the network, there is another factor to consider, that was discussed recently by Intel engineers in one of the IEEE computer magazines. Incoming network data ends up being placed in memory by the NIC driver without being cached by the CPU. When the NIC generates the interrupt telling the CPU to process the received data, its absence in every level of CPU cache causes a cache miss and at today's clock cycles, a stall of several hundred cycles while the addresses and data make their way into the cache hierarchy. Since at the start of every standard TSM backup, the client receives over the network the list of files already known to TSM, that qualifies as "incoming data". Outgoing data is less of a factor since the processor is setting up the data in the various buffers. Therefore, what we've chosen to do is this: * provide a set of hourly schedules spread between 8 pm and 5 am; a PC - CAD workstation in our case - can be set to "backup no earlier than xxx". If I have an engineer who frequently works till 8 pm, I can schedule his PC to backup at 11 pm, for example. We also have a special "noon" backup schedule for docked laptops. * tune TCP window size to reduce the number of acknowledgements; * tune the client aggregation settings to minimize the number of data bursts; we have our system set to create 48 MB aggregates by default. The larger the aggregate, the fewer number of transfers will be made, but the more memory will be needed to buffer the aggregate under construction. * turn off anti-virus scanning on files "when opened for backup"; all PCs have real-time scan enabled so it isn't necessary to re-scan when backing up. Hope this helps. Tab Trepagnier TSM Administrator Laitram LLC "ADSM: Dist Stor Manager" wrote on 04/25/2006 01:13:58 PM: > We have a small number of users here who are complaining that when a > TSM backup runs on their client system, it monopolizes use of their > network card. They are looking for a way to throttle back TSM's use > of the network. Has anyone else run into this? Any ideas? The only > thing I've come up with is to configure a secondary NIC at 10MB/s and > point these users at that card. This seems crude to me, so other > ideas would be welcome. > > ..Paul > > > -- > Paul ZarnowskiPh: 607-255-4757 > Manager, Storage Systems Fx: 607-255-8521 > 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: Diskextender vs TSM HSM for Windows
Wanda, We've been using DiskXtender for a few months. It works, though it can be tricky to set up. We did not integrate it with our TSM system. Instead we redeployed a Pentium-3 server with two full pods of SCSI disks as our media store. However, according to the DiskXtender 6.0 Admin Guide dated Jan 2006, "If you already use or plan to use Tivoli Storage Manager Server (TSM) as a data storage or data backup system, File System Manager allows you to configure a TSM system as a media service so that you can migrate files from File System Manager to a TSM server. This method utilizes the storage devices supported and managed by the TSM server." So at least for now, the TSM compatible version is still being marketed. That could change at any time of course, but that's the latest info I have. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 02/20/2006 01:35:24 PM: > OTG (maker of DiskExtender) was bought by Legato. > Legato was bought by EMC. > As of now, AFAIK, the DiskExtender product that used TSM as a backstore > is no longer marketed. > > TSM for HSM is a replacement for it. > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Dearman, Richard > Sent: Monday, February 20, 2006 2:25 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Diskextender vs TSM HSM for Windows > > > I need to do some HSM on a windows systems we have and was wondering if > anyone has any experiences with these products and could provide me with > some feedback on them. > > > > Thanks in advance > > > **EMAIL DISCLAIMER*** > > This email and any files transmitted with it may be confidential and are > intended solely for the use of the individual or entity to whom they are > addressed. If you are not the intended recipient or the individual > responsible for delivering the e-mail to the intended recipient, any > disclosure, copying, distribution or any action taken or omitted to be > taken in reliance on it, is strictly prohibited. If you have received > this > e-mail in error, please delete it and notify the sender or contact > Health > Information Management 312.413.4947. > >
ISC falls over dead
TSM 5.3.2.0 on AIX 5.3.0 ML-2 on 7025-F50 ISC 6.0.1 and Admin Ctr 5.3.2 This is a test system Connecting with Internet Explorer 6 SP2 on Windows XP Pro SP2. Java runtime 1.5.0_06-b05. I installed ISC and Admin Center to give them a fair chance on our test system. Everything seems to work OK though a bit slowly. But after an hour or so of operation, the web client fails and can no longer connect. Once that happens, when I try to connect I get "Page cannot be display - cannot find server". The URL is "http://titania:8421/ibm/console"; - titania being the test server. If I do a "ps -ef" on the server it shows the ISC processes running: # ps -ef | grep -i isc root 18658 21156 0 Feb 13 - 8:48 /opt/IBM/ISC601/AppServer/java/jr e/bin/java -Dserver_port=9423 -cp startup.jar org.eclipse.core.launcher.Main -no splash -application org.eclipse.help.base.infocenterApplication -plugincustomiza tion /opt/IBM/ISC601/PortalServer/ISCEclipse/plugins/com.ibm.isc.help.doc_6.0.0/ plugin_customization.ini root 21156 1 0 Feb 13 - 0:32 /opt/IBM/ISC601/AppServer/java/bi n/java -cp /opt/IBM/ISC601/PortalServer/ISCEclipse/plugins/org.eclipse.help.base _3.0.1/helpbase.jar org.eclipse.help.standalone.Infocenter -command start -eclip sehome /opt/IBM/ISC601/PortalServer/ISCEclipse -port 9423 -noexec -plugincustomi zation /opt/IBM/ISC601/PortalServer/ISCEclipse/plugins/com.ibm.isc.help.doc_6.0. 0/plugin_customization.ini I'm new to this client - that's why I'm testing it. Why are these stoppages happening? Remember, it works OK for about an hour or so. I can get the Health Monitor, etc. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Offsite library via fiber
Andy, Others have already pointed out that 3 km might be too close, but consider this additional info: * After Katrina hit us, the entire - flooded - parish was closed by the local govenment, so our safely protected tapes were inaccessible for three weeks. Thankfully we had gotten to the point that offsite tape was "plan B". * After 9/11, most of Manhattan was declared a crime scene, so offsite resources near the WTC were inaccessible even though the buildings holding them were undamaged. Distance is your friend. And FCIP makes it easier. Tab Trepagnier TSM Administrator Laitram, L.L.C. Andy Huebner <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 02/10/2006 03:32 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Offsite library via fiber We are building that setup. We will have the first part of the offsite library in place for testing around April. We will only be 3KM away, but there are not many 3k wide tornados... Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Friday, February 10, 2006 2:54 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Offsite library via fiber We're thinking of a TSM upgrade that would include a VTL onsite library and an IBM 3584 library for copy pool tape. We would locate the 3584 in our offsite storage location and access it via fiber. The tapes would remain in the 3584 since they would already be offsite. Anyone have any experience with a setup like this? Daivd Ehresman University of Louisville This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Disk config question - Block size
Richard, We just heard from EMC that the "4 x n +1" optimization is a "myth"... being spread by their technical support staff, field service techs, and training instructors. Their engineers say that Clariion will provide optimum performance with any reasonable drive count. We use RAID-3 on ATA for TSM disk pools, and RAID-5 on Fiber and ATA for general disk storage - like data drives of our Windows file servers. Tab Trepagnier TSM Administrator Laitram, L.L.C. Richard Rhodes <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 02/10/2006 06:21 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Disk config question - Block size I would suggest you contact EMC. I believe they have information about setting up a clariion for TSM. A couple comments from things I've heard from EMC. . . . . EMC used RAID3 in their VTL, and is best for streaming when ATA drives are used, for up to about 10 concurrent read/write data streams.RAID5 is best for streaming with NON-ata drives. EMC has stated a bunch of times that you should not change the default 64k strip size without talking to EMC support (you indicated you weren't, so good). There are internal software design issues that make this optimal. rick Andy Huebner <[EMAIL PROTECTED] ONLABS.COM>To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Disk config question - Block size 02/09/2006 06:34 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> I am preparing a Clariion CX-300 for TSM disk pools. TSM will be the only system so I can tune it from end-to-end. There will be two 4+1 RAID5 groups holding the disk pools. RAID5 or RAID3 are the only choices due to the number of disks that were purchased and the amount of space that I need. The settings we are considering: Element size of 64k. This means a 256k write from TSM is one stripe. Cache block size of 16k. Larger I/Os for the disk pools larger cache blocks should work better. AIX Logical Volume block size of 64k. This will match the element size. Has anyone done this type of tuning and been able to test variations? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. - 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: Alleged LTO fragility
David, We currently have a Gen-1 3583 that would become our "offsite" library. Its online duties would be taken over by a Gen-3 3583. We like having two different libraries for online/offsite. Because LTO is currently online only, there is almost no onsite handling. The DLTs we've been sending offsite for the last five years have held up superbly. We put them in their plastic cases and then the courier gives them a 5-mile roller-coaster ride. We have NEVER had a DLT tape fail from that handling. In an ideal world, we would have the same success if we switched to LTO. Thanks. Tab "ADSM: Dist Stor Manager" wrote on 02/10/2006 12:39:05 PM: > I don't quite think an inch, but... > > 1. Why LTO-1? LTO3 is current vdersion. > > 2. The cases are somewhat fragile on older LTO1 tapes. I > think originally the two plastic halves were not "welded" together. > This led to cases where, when inserted in a drive they got stuck. > Resaon is the leader pin would get pushed slightly back when halves > of case slightly separated, and would not close back. > > I have had about 6-8 failures of this type, out of about > 400 LTO1 tapes I have had. Only had one with an LTO2 tape. > > I understand that by early LTO2, the halves were welded and possibly > continuing production of LTO1 tapes were also. > > 3. Also, what about your onsite tape handlers too! > > 4. I would suspect that in general LTO tapes are no more fragile that DLT, > unless DLT uses more durable plastic or something. > > > > David B. Longo > System Administrator > Health First, Inc. > 3300 Fiske Blvd. > Rockledge, FL 32955-4305 > PH 321.434.5536 > Pager 321.634.8230 > Fax:321.434.5509 > [EMAIL PROTECTED] > > > >>> [EMAIL PROTECTED] 02/10/06 12:51 PM >>> > This is a tape media question. > > We are considering moving from DLT8000 to LTO-1 for offsite tape storage. > > Our local IBM guys told us that LTO tapes should not be dropped more than > 1/2 inch or they risk being damaged. If you've ever watched a vault > vendor handling tapes, you know that 1/2" is pretty optimistic. > > So, is that true? Would our offsite data be at risk if our vault vendor > dropped an LTO cartridge a whole inch? > > Thanks. > > Tab Trepagnier > TSM Administrator > Laitram, L.L.C. > > ## > This message is for the named person's use only. It may > contain confidential, proprietary, or legally privileged > information. No confidentiality or privilege is waived or > lost by any mistransmission. If you receive this message > in error, please immediately delete it and all copies of it > from your system, destroy any hard copies of it, and notify > the sender. You must not, directly or indirectly, use, > disclose, distribute, print, or copy any part of this message > if you are not the intended recipient. Health First reserves > the right to monitor all e-mail communications through its > networks. Any views or opinions expressed in this message > are solely those of the individual sender, except (1) where > the message states such views or opinions are on behalf of > a particular entity; and (2) the sender is authorized by > the entity to give such views or opinions. > ##
Alleged LTO fragility
This is a tape media question. We are considering moving from DLT8000 to LTO-1 for offsite tape storage. Our local IBM guys told us that LTO tapes should not be dropped more than 1/2 inch or they risk being damaged. If you've ever watched a vault vendor handling tapes, you know that 1/2" is pretty optimistic. So, is that true? Would our offsite data be at risk if our vault vendor dropped an LTO cartridge a whole inch? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Processes calling for scratch instead of an existing FILLING tape
Bill, That used to bother me, too. I opened a PMR about six years ago about it. Then I took a close look at how our system was operating. In our case, we run maintenance processes, including copypool reclamation, weekly. Those processes often run for a day or two. If we have copypool reclamation, and storage pool backups running simultaneously, each process will attempt to manage its own set of tapes. Each process will start with a "filling" tape, but grab a scratch when that tape fills up. Our "offsite" tape library has four drives. If copypool reclamation is running when the daily storage pool backups launch, we will have three storage pool backup processes and the one reclamation process running with each using a tape. Now, suppose that two of the three storage pool backup processes complete, leaving their tapes in "filling" status, but the reclamation is still running. And then the reclamation target tape fills up. If it grabbed one of the "filling" tapes rather than a scratch, and it was still running when it came time to pull tapes for the daily vault run, then I would have to either: 1) stop the reclamation; force a dismount, pull all copypool tapes, and restart reclamation, forcing the import of a new scratch; or 2) let reclamation run, and leave "new" data copies in the library while we "believe" that all new data has gone to the vault. By having that reclamation process grab a scratch, even though there are "filling" tapes, it means that I can leave reclamation running, and leave its output tape in the library, and all the new data copies still make it to the vault. Should some disaster occur after the tape pull for the vault, then any data "lost" on that output tape would still be present in the vault at the time of the latest DB backup point by virtue of the reuse delay. Much easier to recover from the disaster, and much less risk of losing data. So I've stopped complaining about that behavior. It's a feature. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 02/07/2006 09:55:18 PM: > I've noticed that processes will fill a tape and then instead of > calling for another FILLING tape in the storage pool, it will mount > a scratch tape. I just saw this again this morning...I had a BA STG > running from onsite tape to offsite tape. There were 4 tapes in > the offsite pool...2 filling.. 1 full..and a filling tape being > written to. The current tape filled up and instead of mounting one > of the other 2 filling tapes, a new scratch tape was called for. And > one of the filling tapes was only 1.4% used! > > I search the TSM site and the archives, but I must not have the > correct search words, 'cause I can't find any hits. My TSM server is > 5.3.2.1 on AIX 5.3 ML2. > > Bill Boyer > "Growing old is mandatory, growing up is optional" - ??
Re: DB & LOG Volume layout - new
Lloyd, My experience matches yours. TSM 5.1.10.0 on AIX 5.2 on 2-way 6H1. For the last several years we've implemented our DB vols on individual disks, relying on TSM mirroring. The disks were 18 GB SCSI disks which each reported 50 MB/s streaming write performance on the outer edge. We defined four volumes per physical disk to allow the disk/controller to elevator-seek based on a previous thread on this topic a couple of years ago. Two months ago we redeployed some SSA-80 disks from our database system to our TSM system. I moved the TSM DB onto two 3-disk LVM stripe sets on the SSAs. Individual disk performance is about the same as the SCSI disks. I spread the DB across eight volumes on each stripe set, still allowing TSM to do the mirroring. Then I compared performance running Expiration. Unlike the old setup, where each disk was hammered individually as TSM walked its tables, now the I/O is evenly spread across the disks of the set. The bottom line is that I/O Wait time was cut in half. While expiration still takes approximately the same time as on the old setup, the reduction in I/O Wait time means the server has more cycles for other work. So even with a heavy workload, the server still provides very fast response time and can manage dozens of client sessions while doing expiration and reclamation at the same time. I would estimate that the increase in efficiency added at least another year to the productive life of our server. Maybe more. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 01/24/2006 01:48:15 PM: > I've been watching this thread with interest, as some of the posts > contradicted what I thought I knew. > > Using nmon, I've watched a couple of systems (AIX, TSM 5.2) running > expiration and DBbackups that have the DB vols set up according to the > "one volume per spindle" premise that appeared to have spotty "hot" disks, > that is the I/O was not distributed evenly across the different volumes. > One drive would have a lot of I/O, then another, etc. > > I've always striped them, in hardware if it was available, and using LVM > if it was not. This gave fairly even I/O, but I admit that doesn't mean > that it was the fastest method. > > I'd love to have a definitive answer here, because I've heard it both > ways, and when I've asked support, they didn't seem to know. > > I'd like someone "piled higher & deeper" to give a conclusive > answer...anyone? > > -Lloyd [ snip ]
Re: What does "updated" really mean?
Richard, Thanks. I was searching for the message number because I was worring that searching for "updating" would be like searching Google for "Windows". In reality, when I searched the V 5.1 Windows client manual for "updating" I got exactly 8 hits. The first hit was the reference cited by the replies. Tab Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/23/2006 10:19 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: What does "updated" really mean? Tab - That's documented in the client manuals, under topic "Displaying backup processing status ". Richard Sims
Re: AW: [ADSM-L] What does "updated" really mean?
Thomas, Thanks very much. That is what I would expect given our work this weekend. And although I've checked Richard's site before, I simply forgot to check it today. Monday morning and all that... Tab Thomas Rupp <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/23/2006 10:01 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject AW: [ADSM-L] What does "updated" really mean? Always first have a look at Richards fabulous TSM site: http://people.bu.edu/rbs/ADSM.funcdir Objects Updated "Total number of objects updated" element in a backup statistics summary. The Objects Updated field displays the number of files or directories whose contents did not change but whose attributes or ACLs had changed. The server updates its information about the attributes or ACLs without the objects themselves having to be sent to the server. HTH Thomas Rupp -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Tab Trepagnier Gesendet: Montag, 23. Jänner 2006 16:56 An: ADSM-L@VM.MARIST.EDU Betreff: [ADSM-L] What does "updated" really mean? Server: TSM 5.1.10.0 on AIX 5.2; client: TSM 5.1.7.0 on Windows 2003 I'm trying to understand what the client is reporting in the session summary when it reports: "01/23/2006 08:20:23 ANE4958I (Session: 47866, Node: ILOX-FS1) Total number of objects updated:673,012" I've checked the product manuals, message manuals, IBM software support site, and the forum site. What exactly is being "updated?" We made some changes to that server over the weekend so the presence of the message and its non-zero count is no surprise. But I'd still like to understand exactly what TSM is trying to tell me. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
What does "updated" really mean?
Server: TSM 5.1.10.0 on AIX 5.2; client: TSM 5.1.7.0 on Windows 2003 I'm trying to understand what the client is reporting in the session summary when it reports: "01/23/2006 08:20:23 ANE4958I (Session: 47866, Node: ILOX-FS1) Total number of objects updated:673,012" I've checked the product manuals, message manuals, IBM software support site, and the forum site. What exactly is being "updated?" We made some changes to that server over the weekend so the presence of the message and its non-zero count is no surprise. But I'd still like to understand exactly what TSM is trying to tell me. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Backup / Restore IMAGE
Boris, This is my GUESS. When reading the disk you take advantage of OS read-ahead caching so the "backup" performance is limited by the output device or its communication link. My LTO-1 drives will each swallow 20 MB/s or better depending upon compressibility. When "restoring" to the disk, especially something as large as an image file, you quickly exhaust the write cache that the OS allocates to the target disk. Our experience is once that happens you're lucky to get more than 5 MB/s per disk. This is especially bad with ATA disks. We've seen them start at 50 MB/s and then after a couple hundred MBs, drop to as low as 2 MB/s because the write-cache was full. This applies to SAN/arrays as well. Our RAID-3 LUN on our SAN could swallow over 50 MB/s with the write-cache turned on, but when we turned the cache off - details in an earlier message from me - the performance dropped to about 12 MB/s. And our SAN vendor EMC says RAID-3 is optimum for applications like TSM disk pools. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 01/12/2006 02:58:28 AM: > Hi, > > we've a windows 2003 fileserver with millions of files. On a Testsystem > (Windows 2003, 3 GB memory, 1 GB Ethernet) we've tried backup image / > restore image for one drive (69 GB). The Backup was done after 56 Minutes > (transfer rate 22 MB/sec) . The restore time for this Image was 2:32 hours > (transfer rate 8 MB/sec). > > So our question : Is it normal, that the restore for the image needs 2,5 x > longer than the backup time? > > Thanks for help and kind regards, > > Boris
Re: AW: Normal # of failures on tape libraries
I've held off replying to this but J.S.'s question prompted one. We have 12 drives spread across three libraries: an IBM 3575, 3583, and an HP 4/40 DLT. At one time we had a total of 18 drives - including those in a second 3575 and a Compaq 2-drive DLT. On the HP and the IBM 3583 we see drive failures approximately every two months. We have had occasions where as many as three different drives have failed in a single week. Only the 3575s have avoided that failure frequency; with them it's about one drive failure per year. If you take a step back and look at the big picture, it's that - in my opinion - the commercial quality tape drives are simply not designed for the pounding they get from an enterprise backup system like TSM. I'm confident that users of Veritas, etc. will report similar failure rates. When I've reported to HP Tech Support that "their" library receives 250 GB a day they exclaimed "Wow!". Imagine if you're one of the forum participants who sends TBs/day to the tapes. It seems like the older tape equipment like the 3575 were designed to take that pounding. Symptom-wise, what we see is this: - LTO: mount/dismount failures. - DLT: mount failures and poor performance; first sign of a drive wearing out is its throughput drops to 10% of its normal rate. - The few 3570 failures we've had usually caused dismount failures. And then there's the tape pickers. We are on at least our tenth in our 4-year old 3583, and on at least our third in our 4-1/2 year old HP. And when a picker fails the whole library is out of service so it's a much bigger problem. Just my two cents. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 12/22/2005 01:06:30 PM: > I agree with previous answers, and I second to "envirinmental" note: > > Is your environment fine? > Stable temperature & humidity within allowed limits, no vibrations, > dustless, pure sinus stable voltage mains? > Evere tried another tape manufacturer? > > regards > J.S. > > > > -Ursprüngliche Nachricht- > > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im > > Auftrag von Dennis Melburn W IT743 > > Gesendet: Dienstag, 13. Dezember 2005 17:31 > > An: ADSM-L@VM.MARIST.EDU > > Betreff: Normal # of failures on tape libraries > > > > Our sites use ADIC Scalar 1Ks as well as one ADIC 10K. The > > Scalar 1Ks have 4 LTO1 drives in each and the 10K has 34 > > LTO2 drives. We experience occasional failures on these > > drives and have to replace them. > > My question is, is it normal for a site that has alot of > > drives to experience drive failures about every 1-1.5 months? > > My manager is rather annoyed at the fact that it seems that > > we are constantly replacing drives even though it doesn't > > cause any downtime for our TSM servers while they are being > > replaced. If this is a normal part of having tape libraries > > then that is fine, but I don't have enough experience in this > > field to say either way, so that is why I am asking all of you. > > > > > > Mel Dennis > > > >
Re: VTS or san disk storage
Richard, I share your pain. We have an EMC Clariion CX500 SAN. We have found that AIX in general, and TSM in particular, can just "hose" the sucker. Your observations about write cache were echoed by EMC. We had to turn off write-cache on our TSM disk pool LUNs because the SAN storage processors couldn't keep up with the incoming data rate and manage the cache at the same time. In our case, it manifested itself as a total network freeze! Once our TSM server - a 2-way 6H1 - started writing to our five-disk RAID-3 LUNs, the I/O would hog the SAN so that no other servers - like our domain controllers - would get any disk access. Disk queue length on the DCs went to 50+. With the DCs locked out of the disks, they couldn't process DNS lookups, logins, etc. so our Active Directory LAN just hung. The odd thing is that all our TSM disks are in their own disk pod; the only thing shared between TSM and the remainder of the servers was the internal fiber loops and the SPs. There was no disk contention between TSM and anything else. We duplicated the problem when creating disk volumes in TSM. We duplicated the problem when our Windows-based Domino servers backed up to SAN-based disk pools. We duplicated the problem when we copied a large database from one Oracle server to another; both with data volumes on the SAN. All of this occurred at data rates of about 50-55 MB/s. We use RAID-3 for TSM disk pools and RAID-5 for everything else. With the write cache turned off we get more like 12 MB/s streaming to a five-disk RAID-3 array. So with TSM using the SAN as a major storage resource, we've had to give up performance and reliability. On the upside, at least it's only three times as expensive as tape! Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 11/29/2005 09:48:08 AM: > I have about 6TB of san disk space used for nightly backups and the > management of it is just a pain. For instance if you are using a vendor > such as HP for your san disks the compatibility with IBM equipment is > not the greatest. We use HP EMA 12000 with hsg80 san storage > controllers. TSM will max out the I/O to the san controllers then the > particular lun will hang and then the san storage controller must be > rebooted to get the lun accessible again to aix but even after the > reboot the lun is available to aix but unreadable so now I lost all the > data on that lun. I have run into this problem many times over the past > few years. HP says disable caching at the controller level which may > work but disk I/O will be extremely slow so that is not an option. > > You can attribute these problems to incompatible hardware but I would > run what ever disk storage you choose through the ringer before you > commit to it because I have had this problem with other san storage > units as well. We also keep disk storage in multiple locations across > campus via long haul san connections which mean multiple luns to manage > and many filesystems which if you are in an HACMP configuration takes > time for failover to occur and filesystem mounts to take place. > > In conclusion make sure what ever storage you choose is reliable and > able to handle the high I/O load tsm will can on it. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Paul Zarnowski > Sent: Thursday, November 24, 2005 8:40 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: VTS or san disk storage > > At 11:33 AM 11/23/2005, Dearman, Richard wrote: > >We currently use several TB of san based disk storage for our daily > >backups which gets migrated during the day to multiple tape libraries. > >The san disk administration has become a nightmare [...] > > I am curious what kind of problems you are running into. At the TSM > Symposium at Oxford this year, IBM indicated that they were going to > further develop the serial access disk support in TSM. And, TSM 5.3 > just added the ability for a SAD devclass to span multiple > filesystems. After hearing this, we have been leaning towards > investing in inexpensive disk managed by TSM rather than buying a VTL > appliance. I'm interested in other's comments about where, > specifically, they are having problems managing SAD directly by TSM. > > ..Paul > > > > -- > Paul ZarnowskiPh: 607-255-4757 > Manager, Storage Systems Fx: 607-255-8521 > 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED] > > **EMAIL DISCLAIMER*** > > This email and any files transmitted with it may be confidential and are > intended solely for the use of the individual or entity to whom they are > addressed. If you are not t
Platform change to Windows?
We are considering migrating our TSM systems from AIX to Windows 2003. I know that the experience of the forum participants is that AIX provides superior I/O performance, but where is that threshold? These are our system details. I'd like for anyone with experience with a system of similar size to share their experiences regarding Unix vs. Windows. We are currently running TSM 5.1.10 on a 2-way 6H1 with 4 GB RAM. We are considering running TSM 5.3.2 on a 2-way or 4-way 3.0 GHz Xeon with 4 GB RAM. All non-OS I/O would be via GigE network and redundant 2 Gbs fiber. TSM system details: DB: 32 GB @ 83% utilization Log:5 GB, roll-forward mode Primary data: 16 TB with one copypool (another 16 TB to manage) Nodes:175 backing up during a 10-hour window Average daily incoming data: ~ 200 GB; may be reduced via deployment of TDP Oracle Disk: 1 TB DAS, 3 TB SAN Tape: LTO-1, DLT8000, 3570XL, four SCSI drives each; libraries will be consolidated Daily copypool updates sent to vault Semi-annual exports in the 2-5 TB range Does that sound like a system that could reasonably be hosted on a modern Windows system? Is a 2-way adequate, or should we get a 4-way? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Does subfile backup reduce tape occupancy?
Like lots of users, our tape libraries are overloaded and we're looking for ways to reduce what we're keeping before spending money on new equipment. Server: TSM 5.1.10 on AIX 5.2 Clients: mostly TSM 5.1.7 on Windows XP/200x. Storage: mix of disk, 3570, and LTO Most filesystems are configured to maintain three versions. If I have a server whose current occupancy is 1000 GB, and I turn on subfile backups with the same number of versions, will the actual occupancy go down? Or will it remain the same? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Fw: Configuring JBB
Charles, For years we operated TSM with very little disk space. The trick is to use small disk pools of 5-10 GB with several volume files, and set a fairly low migration threshold - say 10-20% or so. In our case one of our disk pools was 4 GB as 20 x 200 MB volumes. We ran with HI=10, LO=0, so as soon as the clients committed 400 MB of data, migration started and sent a pretty good chunk of data to tape. We migrated data to 3570XL media with an average I/O of 8 MB/s, so migration took only about a minute or so. Because our disk pool was so small we set a MaxSize of 1 GB (25% of the disk pool) so anything bigger went straight to tape anyway. All of our production libraries have four drives each so we had enough mount points to accommodate both clients sending to tape and migrations. Tab Trepagnier TSM Administrator Laitram LLC "Bell, Charles (Chip)" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 10/11/2005 01:06 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Fw: Configuring JBB Not a dumb question at all. This shop is strapped for resources. We are looking at getting a VTL in here, but in the interim, I have a 3584 to deal with. We have 4 LTO1 and 4 LTO2 drives. We do not have enough disk to send him there, and our admin sched has recently outgrown the environment that was supporting, so a VTL will kill several birds. So to answer the question more directly, we just do not have the disk (or SANergy money) or space for FILE to put it. I am fully aware that going to tape is not helping, but I don't have many options as far as resources are concerned. Another thing of note is that I put this node in its own domain with own mgmt class to separate it out from our main domain for Wintel boxes. This was done because of the sheer data amount that they expected this server to host in the next few years (multiple TB's). Yikes! Since I have collocation turned off until the resource situation improves. I simply did not want to mix this node with the others. The node has thus far filled 40 LTO2 tapes and is constantly growing. :^( -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Tuesday, October 11, 2005 12:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fw: Configuring JBB ==> On Tue, 11 Oct 2005 12:27:10 -0500, "Bell, Charles (Chip)" <[EMAIL PROTECTED]> said: > Already scheduled for it, and planning on posing my question there if I > don't have a solution in place by then. Thanks! Might be a dumb question, but you mention > The node in question is holding onto a tape drive for 20+ hours per backup > because of the file inspection it has to do, which is why I want to get JBB > to work. I don't know why you've chosen to do this direct to tape; could you get your resources free by hitting a DISK or FILE devclass instead? The use of a tape might be slowing down your backups, dramatically. Especially with erratic streams, tape positioning time can come to dominate your backup. - Allen S. Rout Confidentiality Notice: The information contained in this email message is privileged and confidential information and intended only for the use of the individual or entity named in the address. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this information is strictly prohibited. If you received this information in error, please notify the sender and delete this information from your computer and retain no copies of any of this information.
Re: ANR9999D pkthread.c(1037): ThreadId<31> Unable to cr eate new Thread....
Jane, I know of no such limit. I'm running a 1 GB buffer pool on my 4 GB TSM AIX server with no issues. The only thing to watch is that the buffer pool is considered "process" memory by AIX. So the default MaxPerm% of 80% means that AIX allows process to have priority on 1 GB with the other 3 GB given preference for files. Because in my case, process memory is 25% + whatever AIX and TSM themselves use, quite a lot of memory would be paged out to disk. So you have to adjust MaxPerm% down to allow AIX and TSM to have enough process memory to avoid that paging activity. If you understand what's going on that should be a one-time operation. Good luck. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 07/21/2005 05:13:54 AM: > Hi - > > In the Performance Tuning Guide this states that the 'buffer pool size may > not exceed 10% of physical memory on AIX' > > Also, Recommended values are included in a table dependent on your amount of > physical memory, but max in MB is 256 assuming you have 2048MB of memory. > > They may have something that has been updated that goes up for higher > memory?? > > Jane. > > > -Original Message- > From: Henrik Wahlstedt [mailto:[EMAIL PROTECTED] > Sent: 21 July 2005 11:11 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] ANRD pkthread.c(1037): ThreadId<31> Unable to > create new Thread > > Hi, > > I´m not sure if there are some upper limit on Bufpoolsize, but 1024000 seems > rather high to me... One of our p650, aix, with 16GB of ram just use a > bufpoolsize of 786432. > > What happens if you reset bufpool to it´s original value, and re-run the > backups? > > > //Henrik > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Nielsen, Bo > Sent: den 21 juli 2005 10:54 > To: ADSM-L@VM.MARIST.EDU > Subject: ANRD pkthread.c(1037): ThreadId<31> Unable to create new > Thread > > Hi > > last night I have a couple of nodes, who failed with >Server Detected Error. > In TSM server activity log I found these message: > > 07/21/2005 03:28:03 ANRD pkthread.c(1037): ThreadId<31> Unable to create > new Thread. CreateThread error.Callchain: 104EAD79 outTextf()+1529 <- > 10007040 pkLogicAbort()+A30 <- 15E3D688 Unknown <- 10A7CC08 > outTextf()+5933B8 <- > 07/21/2005 03:28:04 (31) Context report 07/21/2005 03:28:04 (31) Thread > SessionThread (23) is a child thread related to: 31 07/21/2005 03:28:04 (23) > Generating TM Context Report: (struct=tmTxnDesc) (slots=256) 07/21/2005 > 03:28:04 (23) *** no transactions found > *** > 07/21/2005 03:28:04 (23) Generating Database Transaction Table Context: > 07/21/2005 03:28:04 (23) *** no transactions found > *** > 07/21/2005 03:28:04 (23) Generating SM Context Report: 07/21/2005 03:28:04 > (23) Session 195354: Type=Node, Id=CDKALB030 07/21/2005 03:28:04 (23) > Platform=WinNT, NodeId=254, Owner= 07/21/2005 03:28:04 (23) SessType=5, > Index=37, TermReason=0 07/21/2005 03:28:04 (23) RecvWaitTime=0.000 > (samples=0) 07/21/2005 03:28:04 (23) Backup Objects ( bytes ) Inserted: 0 ( > 0.0 ) 07/21/2005 03:28:04 (23) Backup Objects ( bytes ) Restored: 0 ( 0.0 ) > 07/21/2005 03:28:04 (23) Archive Objects ( bytes ) Inserted: 0 ( 0.0 ) > 07/21/2005 03:28:04 (23) Archive Objects ( bytes ) Retrieved: 0 ( 0.0 ) > 07/21/2005 03:28:04 (23) Last Verb ( Ping ), Last Verb State ( Sent ) > 07/21/2005 03:28:04 (23) Generating AS Vol Context Report: > 07/21/2005 03:28:04 (23) No mounted (or mount in progress) volumes. > 07/21/2005 03:28:04 (23) Generating ssSession Context Report: > 07/21/2005 03:28:04 (23) Storage Service Sessions: > 07/21/2005 03:28:04 (23) Session 134454 --> BufConfig=None, TransBufSize=0, > SplitBuf=False, WrCount=0, WrBufIsEmpty=False, > WrBufIsFull=False, SourceRc=0, SinkRc=0, AuxCreated=Fals- e, AuxBegin=False, > AuxIsSink=False, AuxIdle=False, > AuxTerminate=False > 07/21/2005 03:28:04 (23) Leased Volumes: > 07/21/2005 03:28:04 (23) (none) > 07/21/2005 03:28:04 (23) Excluded VolIds: > 07/21/2005 03:28:04 (23) (none) > 07/21/2005 03:28:04 > 07/21/2005 03:28:04 (23) Generating ssOpenSeg Context Report: > 07/21/2005 03:28:04 (23) No storage service segments found. > 07/21/2005 03:28:04 (23) Generating BF Copy Control Context Report: > 07/21/2005 03:28:04 (23) No global copy control blocks. > 07/21/2005 03:28:04 07/21/2005 03:28:05 (31) Thread SessionThread (24) is a > child thread related to: 31 > 07/21/2005 03:28:05 (24) Generating TM Context Report: (struct=tmTxnDesc) > (slots=256) > 07/21/200
Re: TSM feature
Otto, That is sometimes called "content addressable storage". And no, TSM does not include that feature. There are several products that claim to provide that feature according to ads in Storage Magazine. I have no specific knowledge or experience with any of them. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 07/15/2005 08:34:00 AM: > I think this feature is called the "not yet existing feature" > > regards. > > Lawrence Clark wrote: > > >Does anyone know the name of this feature of TSM I will attempt to > >describe below. I recall reading something about this in the past: > > > >- the ability to recognize the same file is already backed up on one > >client and avoid duplicate backups of the same file on another > >client... > > > > > > > -- > Otto Schakenbos > System Administrator > > TEL: +49-7151/502 8468 > FAX: +49-7151/502 8489 > MOBILE: +49-172/7102715 > E-MAIL: [EMAIL PROTECTED] > > Teleflex Holding GmbH > Corporate IT Europe > Fronackerstrasse 33-35 > 71332 Waiblingen > GERMANY
Re: How are TSM admins using SATA for cache pools?
Justin, "My concerns are that we will slow down the client backups when we have so many clients running in a small backup window. If we use SATA or FC ATA drive for the primary disk storage pool." We use ATA in an EMC Clariion as primary disk storage pools. We keep TSM caching turned OFF, simply because the disks are so large that caching doesn't buy us much. We have found that using EMC five-disk RAID-3 arrays for disk pools yields a consistent 40-50 MB/s when pushed by our 2-way 6H1. We use EMC PowerPath to load-balance the data paths to the LUNs. On the other hand, because the ATA hot spare is in the TSM pod, we also created a four-disk RAID-5 array. On that array, we're lucky if we peak at 18 MB/s and sustained performance is usually 12 MB/s or less. All measurements obtained via topas. EMC Clariion code is optimized for (4 x n + 1) disk arrays. I don't know about IBM's. So that's a factor in the performance difference between the two types of arrays. Our two RAID-3 arrays are 1188 GB each, and our one RAID-5 array is 891 GB. We target our file servers to the RAID-3 arrays and have not observed any performance issues. Our Domino and Oracle databases write straight to LTO-1 tape. We point small application servers and CAD workstations at the RAID-5 array, and for those clients, performance is not really an concern. If a backup takes a few minutes longer, so what? We have about 160 clients backing up between 8 pm and 6 am. We have no issues about meeting backup windows since all backups are "hot". Our largest file server has almost two million files, and a typical backup takes about five hours. Most of that is client directory scanning and we are considering using journaling when we go to TSM 5.3 in a couple months. Also, that server is now hosted by VMWare so all I/O has to pass through the VMWare kernel. We have seen a performance drop using VMWare, especially when sending to ATA disks. On last night's backup of that file server, the average network data transfer rate was just under 10 MB/s. We can live with that. I've personally seen the 6H1 swallow 70 MB/s through its NIC so I know the TSM server is not a bottleneck. Just info. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 07/12/2005 03:54:18 PM: > OK May be I was not clear what we would use the SATA or FC ATA for would > be the primary disk storage pools for nightly backup window > then next morning we would be migrating the backup data to tapes ( FC 3592 > jaguar drives ), current primary storage pools are Enterprise class > (shark disks) and our disk storage pool is currently 1.7 TB for nightly > backup that is what we call cache pool, on one TSM Server and another > TSM server we have 1.6 TB of primary storage pool, then we have a small TSM > server that has 1/2 TB of primary storage pool. In all we backup up 513 > clients nightly with the 3 TSM servers and data that is backed up runs > between 2.7 TB to 3.2 TB. in a backup window of 6 to 8 hours. We do have > about 100 > Oracle RMAN backups included in the backup window running TSM TDPO backups. > If you need more information please let me know. > > My concerns are that we will slow down the client backups when we have so > many clients running in a small backup window. > If we use SATA or FC ATA drive for the primary disk storage pool. > Thanks > > Justin Case > > > > > > > > > > Jin Bae Chi > <[EMAIL PROTECTED] > > To > Sent by: "ADSM: ADSM-L@VM.MARIST.EDU > Dist Stor cc > Manager" > <[EMAIL PROTECTED] Subject > .EDU> Re: How are TSM admins using SATA >for cache pools? > > 07/12/2005 08:24 > AM > > > Please respond to > "ADSM: Dist Stor > Manager" > <[EMAIL PROTECTED] >.EDU> > > > > > > > Justin, > > You may need to tell us more about your configuration and how much data and > how long you need to keep the data before any migration with cache turned > on/off. As you mentioned, you may not need the enterprise class stg for > these particular diskpools unless your SLA requires certain strictness in > performance. Because of the nature of SATA, write I/Os will be troublesome > in any case, so make sure that the controller have enough cache and destage > it later. Some people make mistake buying with single controller config, > but remember that you can't afford to lose it during client backups. Look > for the new SATA II which comes with a lot of fixes a
Re: DB (Image) backups
Wanda, Thanks. That much I understand. What I don't understand is "what does one DO with an image backup?" The manuals are crystal clear on how to create an image backup, but very vague on how to use them after they've been created. In other words, lets say I'm recoverying my TSM system somewhere else and I have a/some DB image backups available. HOW do I recover using one/them? Thanks. Tab "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 07/07/2005 03:21 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: DB (Image) backups If you want to continue creating DB Backups on tape, a DB SNAPSHOT should work nicely. It is just an extra, full backup that is independent of the original full/incremental DB backup series. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier Sent: Tuesday, June 28, 2005 11:06 AM To: ADSM-L@VM.MARIST.EDU Subject: DB (Image) backups We are setting up SAN replication for DR. I need some information on how to handle the TSM database. TSM 5.1.10.0 - soon to be TSM 5.3.(2?).x. AIX 5.2 ML-3 - soon to be AIX 5.3 ML-2+ For the last seven years we've backed up the TSM DB to tape and sent it offsite. When we've needed to restore the DB, we're restored from tape. Mostly works OK except a little slow. Now we have an EMC Clariion CX500 SAN and we're setting up SAN-to-SAN replication with our warm site. We will have a TSM server staged at that site but it will be OFFLINE because of a shortage of live Fiber ports in a non-DR state. Our drop-ship contract includes an FC switch. What we would like to do is backup the DB - full and incremental - to the SAN and replicate those backups to the warm site's SAN. Recovery would involve connecting the staged recovery server to the target LUN and then restore the replicated database volumes. Questions: * Would that work?? * If I wanted to continue the DB backups to tape in parallel - in other words, maintain two DB backup sequences - how would I do that? * The Backup DB command offers a Type=Image option. What does one do with a DB image? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
AIX devices under recovery scenario
TSM 5.1.10.0 (TSM 5.3 soon) on AIX 5.2 ML-3 (AIX 5.3 soon) I'm writing the procedure for our updated DR process, and I have one key question regarding AIX device definitions. We have three tape libraries: two host our primary pools and one hosts our unified copypool. With rmt0 as the server's internal drive, the AIX device definitions run like this: Primary #1: rmt1-4 Primary #2: rmt5-8 Copy: rmt9-12 -and- mt2-5 Under a DR scenario, we would have "a" library drop-shipped to our DR site. We would restore the TSM database from a replicated SAN LUN so that doesn't require any tape resources. Now we have to add the drop-shipped library to the recovery server. Since we restored the DB from our production system, it expects to find the same libraries and associated AIX devices in the PATH definitions. But those devices are no longer valid. Furthermore, once I connect the drop-shipped library to the recovery server and run cfgmgr, I end up with AIX devices at rmt1-rmt4. Those AIX devices are referenced by the definition for Primary #1. Also, since it will not be an IBM library - probably - when I create the lb/mt devices they won't match the ones associated with our production copypool. I know I can "chainsaw" my way through the TSM device and path definitions to fix this situation. But what is the BEST PRACTICE for fixing all this? Please remember that at some point, the disaster will end and we will want to shift back to our production system at our normal company site. We don't want to orphan any new data that was backed up while in DR mode. Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: DB (Image) backups
Mark, Thanks for the info. One thing I'm still not clear on is "what does one do with a database image backup?" The manuals are clear about how to create one, but less clear on how you would use it. Thanks again. Tab "ADSM: Dist Stor Manager" wrote on 06/28/2005 10:19:07 AM: > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf Of Tab Trepagnier > >We are setting up SAN replication for DR. I need some > >information on how to handle the TSM database. > > > >TSM 5.1.10.0 - soon to be TSM 5.3.(2?).x. > >AIX 5.2 ML-3 - soon to be AIX 5.3 ML-2+ > > > >Now we have an EMC Clariion CX500 SAN and we're setting up SAN-to-SAN > >replication with our warm site. We will have a TSM server > >staged at that > >site but it will be OFFLINE because of a shortage of live > >Fiber ports in a > >non-DR state. Our drop-ship contract includes an FC switch. > > > >What we would like to do is backup the DB - full and > >incremental - to the > >SAN and replicate those backups to the warm site's SAN. Recovery would > >involve connecting the staged recovery server to the target > >LUN and then restore the replicated database volumes. > > > >Questions: > >* Would that work?? > >* If I wanted to continue the DB backups to tape in parallel - in other > >words, maintain two DB backup sequences - how would I do that? > >* The Backup DB command offers a Type=Image option. What does > >one do with a DB image? > > Short answer: yes. > > There is a very important point with replication--if the replication > target runs a TSM server, the TSM server process must *not* be running > during replication. > > Virtually all replication technology is application-agnostic; i.e., the > replication process doesn't care what the data looks like--it just moves > bytes from source to target. If you replicate a TSM db to a target box, > and the target box has a hot TSM server process running against the > database, you'll corrupt it in a flash. If you want failover capability, > great pain must be taken to insure that the replication link is closed > before starting the target machine's process. > > If your replication technology is solid, you should be able to run a TSM > db backup during replication. > > -- > Mark Stapleton ([EMAIL PROTECTED]) > IBM Certified Advanced Deployment Professional > Tivoli Storage Management Solutions 2005 > IBM Certified Advanced Technical Expert (CATE) AIX > Office 262.521.5627
DB (Image) backups
We are setting up SAN replication for DR. I need some information on how to handle the TSM database. TSM 5.1.10.0 - soon to be TSM 5.3.(2?).x. AIX 5.2 ML-3 - soon to be AIX 5.3 ML-2+ For the last seven years we've backed up the TSM DB to tape and sent it offsite. When we've needed to restore the DB, we're restored from tape. Mostly works OK except a little slow. Now we have an EMC Clariion CX500 SAN and we're setting up SAN-to-SAN replication with our warm site. We will have a TSM server staged at that site but it will be OFFLINE because of a shortage of live Fiber ports in a non-DR state. Our drop-ship contract includes an FC switch. What we would like to do is backup the DB - full and incremental - to the SAN and replicate those backups to the warm site's SAN. Recovery would involve connecting the staged recovery server to the target LUN and then restore the replicated database volumes. Questions: * Would that work?? * If I wanted to continue the DB backups to tape in parallel - in other words, maintain two DB backup sequences - how would I do that? * The Backup DB command offers a Type=Image option. What does one do with a DB image? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Backup of large server (15+ Million objects)
Bill, I have a case where I want to isolate a particular directory path from the remainder of the file server. That isolated path had been permanently archived but I've since switched to backupsets. But that directory path is part of a file server with 1.7 million files. This is how I isolated it given that TSM does not support Virtual Mount Points in Windows. I created a hidden share on the top-level directory: Net Share MyFolder$=D:\MyFolder Then I added the UNC path to the DSM.OPT file Domain statement: Domain \\MyServer\MyFolder$ With that, I could assign a specific management class to that specific path: Include \\MyServer\MyFolder$\...\* SpecialMgmtClass I also excluded the physical path to avoid duplicate data copies: Exclude.Dir D:\MyFolder That caused TSM to define the UNC path as its own filespace, with which I could do anything I wanted using standard TSM functionality. In my case, that path represents approximately 10% of the entire file server. I can create "permanent" backupsets from that filespace without having to grab the entire server or archive almost 2 million files. I'm not claiming it's a perfect solution, but it is a way to break up a large file server without carving it up physically. Just be aware that backing up via UNC means passing through the network stack, so you'll take a small performance hit. And remember that the System account can't establish network connections, so you'll have to run your TSM service(s) under an account with higher priviledges. Hope this helps. Tab Trepagnier TSM Administrator Laitram LLC Bill Boyer <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 06/15/2005 11:07 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Backup of large server (15+ Million objects) >From what I'm reading and understanding (which may be 2 entirely different things!!) junction points just let me create a link between directories. Kinda like hard/soft links in Unix (ln command). Mount points let me take a drive and mount it on a directory instead of a new drive letter. I want to go the other way...take a directory and make it a drive letter or a new filesystem to TSM. Even if I could split this 15million object filespace into 3 or more separate filespaces I think I could get a backup done in a reasonable time...or even get it done! Right now it just plain doesn't finish. Mostly the scheduler service dies and the backup fails. IMAGE backups aren't an optoin with 3590E drives and "K" media. I would be here forever doing the backup and then I couldn't carry all the tapes! :-) Any ideas or suggestions?? One optoin they are looking at is just replicating this volume to another location instead of or in addition to backups (if I can get it to run). Bill -- Original message -- > Actually with both Windows 2000 and Windows 2003 you can create what is like a > mount point in Unix land. Search MS's site for "junction point" OR "mount > point". > > > Bill Boyer wrote: > This is a single drive letter, G:, so I can't separate it into multiple nodes or > even schedules. Plus virtualmountpoint is only valid for Unix's, not Windoze. > > Thanks. > Bill > > -- Original message -- > > > Hi Bill > > > > 1. Separating it into multiple TSM nodes, for example one node per > > filespace > > > > 2. Using the virtual mount point option > > > > Both theese options should decrease the time TSM spends on inspecting the > > filespaces. > > > > Best Regards > > > > Daniel Sparrman > > --- > > Daniel Sparrman > > Exist i Stockholm AB > > Propellervdgen 6B > > 183 62 TDBY > > Vdxel: 08 - 754 98 00 > > Mobil: 070 - 399 27 51 > > > > > > > > Bill Boyer > > Sent by: "ADSM: Dist Stor Manager" > > 2005-06-14 16:36 > > Please respond to > > "ADSM: Dist Stor Manager" > > > > > > To > > ADSM-L@VM.MARIST.EDU > > cc > > > > Subject > > Backup of large server (15+ Million objects) > > > > > > > > > > > > > > Windows 2000 server with TSM client 5.3.0.8. > > TSM server 5.2.2.0 on Windows2000 > > > > Configured the journal service with a larger notify buffer, but we just > > can't get the first incremental to complete. We see in the server > > activity log that the session was terminated by the client. Running in > > managed services mode. > > > > Any suggestions on backup strategies on this large of a server? > > > > Bill Boyer > > DSS, Inc. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com
Re: Re Windows 2000 client reconfiguration
Farren, >From our experience, this is the problem: "Configure a new server and copy the data across > in such a way that it doesn't look like it's changed." Our main file servers have been on five different physical machines in the eight years I've been here. Our attempts to "copy" data from one file server to another have always caused TSM to grab a new copy of the entire server. One issue is that Microsoft's tools - xcopy, ncopy, and pcopy - all "copy" permissions but not inheritance. So a folder on the source that inherits certain permissions from its parent will have the same permissions APPLIED on the copy. From Windows' perspective that is an ACL change, so TSM grabs a new copy. Worse, it means that any changes you intend to apply at the top of the directory tree dead-end at that level. You must then force the inheritance down the tree, which means ANOTHER ACL change and another copy of the file server pulled into TSM. If you're going to pull in a copy of the entire server anyway, I would recommend that you get your permissions, inheritance, auditing, etc. as close to perfect as possible BEFORE launching the first post-migration backup. And do as much with groups as possible. Adding just one user ID to the top of a directory tree will provoke a very large backup session. Good luck. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 05/12/2005 03:08:20 AM: > Morning all TSMers > > Running TSM 5.1.6.2 on a Solaris server. Attached to 1*3494 library with > two*3590H1A drives. > > I have a possible problem here. One of the sys admins for the Windows 2000 > servers has informed me that they are going to need to replace an entire > Windows 2000 server due to severe hardware issues that they have been > experiencing. No amount of support has fixed the problem and hence the > drastic move. The server has got some 820,000 files on it amounting to > approximately 450GB. > > Here is what we want to do. Configure a new server and copy the data across > in such a way that it doesn't look like it's changed. The new server will > have the exact same Node name, file system layout etc. I don't really want > to be faced with backing up the entire server all over again as we are > getting low on both tape space in the library and database space. This was > not something I had foreseen. > > From what I have been told, early tests have not been promising and TSM > still thinks files have changed even if the last change date/time etc has > not altered. Does anyone have any experience with this or any advice they > can give that may help us avoid a long backup that will hog system > resources? > > Many thanks in advance > > Farren Minns > Solaris System Admin / Oracle DBA > IT - Hosting Services > John Wiley & Sons, Ltd > > > ## > 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: Diskpool question
Another factor to consider on EMC is the RAID type. According to their white paper, "EMC Backup Storage Solutions: Backup-to-Disk Guide with IBM Tivoli Storage Manager", the preferrred RAID type is **_RAID-3_**. Our Clariion requires five or nine disks to implement that RAID level. With a pod full of SATA disks we implemented two five-disk RAID-3 arrays and one four-disk RAID-5 array for use as TSM disk pools. We consistently see 40-50 MB/s with the RAID-3 LUNs, while the RAID-5 LUN seems to max out at about 22 MB/s. I understand that drive count is a factor in all this, but I doubt that the difference of one disk's media would yield a 50% loss of performance. However, in subsequent discussions with their engineers they've stated that the Clariion internal "Flare" code is optimized for RAID groups made with (4 x n + 1) disks; meaning 5, 9, 13, etc. Using any other drive count in a RAID group compromises that optimization. At some point, we will probably remake some of our RAID groups, including that one RAID-5 array. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 05/11/2005 01:54:04 PM: > Andy Huebner wrote: > > >We use RAID 5 (5+1) on a Clariion using 146GB drives. We peak the > drives at over 55MB/sec, sustained speed is over 45MB/sec. How fast > are you reading and writing to your disks? If it is faster than > your SAN storage can read and write from RAID 5 then mirroring or > striping is a better choice, although I would not use unprotected disks. > > > >Andy Huebner > > > > -Original Message- > >From:ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf Of Luc Beaudoin > >Sent: Tuesday, May 10, 2005 7:47 AM > >To: ADSM-L@VM.MARIST.EDU > >Subject: [ADSM-L] Diskpool question > > > >My diskpool is on a SAN, I have to increase the size cause I'm taking > >about 450GB per day and my diskpool is 350GB... > > > >Is there a RAID issue for performance right now my diskpool is on a > >RAID5 ... should I still use RAID5 or there a better RAID configuration?? > > > >thanks > > > >Luc > > > > > >This e-mail (including any attachments) is confidential and may be > legally privileged. If you are not an intended recipient or an > authorized representative of an intended recipient, you are > prohibited from using, copying or distributing the information in > this e-mail or its attachments. If you have received this e-mail in > error, please notify the sender immediately by return e-mail and > delete all copies of this message and any attachments. > >Thank you. > > > > > > > > > Just for information, EMC did not optimize the FlareCode on Clariion for > RAIDGroup with even disk (3+1, 5+1, ...) so It could be better to use > 4+1, 6+1, 8+1 RAIDGroup (See Clariion Best Practises on Powerlink). We > use a 4+1 configuration and during our backup database we have a > sustained speed of 70-80 MB/s. > > Stripe on each disk is 64KB lenght, for four disk you have a full data > stripe of 256KB (4x64KB + 64KB Parity) and th default LTG size of AIX > Volume Group is 128kB.
Re: How to change the paths of Database Locations - URGENT TSM down
Naleen, We just implemented an EMC SAN a week ago, but the problem is that your PowerPath devices are not valid from Solaris' view. THAT is what you need to fix; just let TSM stay down until the EMC is right. Otherwise you will just dig yourself deeper into trouble. Run the "powermt" command; on AIX the syntax is "powermt display dev=all"; on Solaris is should be similar; and check all paths for "dead" devices and paths. Then call either Sun or EMC and resolve that/those problems. Then you should be able to start TSM with no problem. Good luck. Tab Trepagnier TSM Administrator Laitram, L.L.C. Svetoslav Tolev <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 04/07/2005 05:18 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: How to change the paths of Database Locations - URGENT TSM down Hi, First you must check is the storage avaliable. think that you can't access the storage. But if you think that the path the the volumes are wrong you can edit the file "dsmserv.dsk" where the paths are written. Regards, Svetoslav "Selva, Naleen" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 08.04.2005 00:31 Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject How to change the paths of Database Locations - URGENT TSM down Hi, We have TSM server 5.2.2 on a solaris platform All the database and logs are located on a EMC storage F.C This morning, we could not start the dsmserv as it said ANR7806W Unable to open file /dev/rdsk/emcpower13a. ANRD blkdisk.c(1452): ThreadId<0> Explanation (open error), errno=5 (I/O e error). ANR7806W Unable to open file /dev/rdsk/emcpower14a. ANRD blkdisk.c(1452): ThreadId<0> Explanation (open error), errno=5 (I/O e error). ANR0214W Database volume /dev/rdsk/emcpower13a is in the offline state - VARY ON required. ANR0214W Database volume /dev/rdsk/emcpower13d is in the offline state - VARY ON required. ANR0215W Recovery log volume /dev/rdsk/emcpower14a is in the offline state - V VARY ON required. It seems that the paths are wrong, and I would like to know how to change it. PLEASE HELP as the server is DOWN currently. Naleen Selva
Re: DR exercise
Dave, Just a few hints. First, the Redbook that Mark cited is excellent. It's big, but don't let its size scare you. It is very well organized and you can read and digest it by section. Lots of good terminology for when you call upon a DR professional. Second, in the industry, "Disaster Recovery" is generally regarded as different from "Business Continuity". DR is mostly computer/data based; while BC is the total business recovery and will require input from all stakeholders. We are a manufacturer. A fire in our data center requires we execute on DR; a major hit by a hurricane means we can't make product so we would have to execute on BC. In general, if you are focusing on "DR", you just want to avoid putting together a plan that gets in the way of "BC" should a larger disaster occur. Now, for "DR", what we've done is this. Imagine that your data center is "gone." What would you do? How would employees connect? One of the first things that leaped out at us was a recovery site. Where would you go to recover? Once there, how would you connect to the outside world? Without Internet access or some other network link, you're effectively building a "lab." If you don't already have a network link there, how long will it take to get one? Does it have the correct power, or will you find yourself trying to power a 240 VAC server on 120? And so forth... Once you have a site, you'll probably want to start building your core network, including DNS, DHCP, any required domain controllers, etc. Again, how would you do that? Are you going to re-implement your network from scratch? If no, what information and/or files do you need to expedite the network rebuild, including routers and firewalls? Basically, just think through the steps of what it would take to get everything back up and running. Pencil in the steps and think hard about any prerequisites. If your vault vendor is going to deliver 500 tapes to you, what are you going to do with them? Identify your most critical applications. Then try to define their individual components. This is a big one now that "distributed applications" are the rage. Is there a .Net application server in the mix? Is there some middle-tier server? Is there a web-server component? How do you recover those? And how do you plug those components back together to recover the overall application? We're currently implementing our first real DR process beyond "send tapes to the vault". We've been through the exercises I've described at least three times now, and are hoping to demonstrate recovery of one of our most critical apps by the start of this year's hurricane season. Just stepping through the scenarios is sobering and enlightening. And don't get hung up trying to think about recovery of every possible disaster. As I said near the beginning, "DR" is for data and computers. Don't single-handedly try to create a BC process. Good luck. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 04/04/2005 01:41:55 PM: > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > Behalf Of Dave Zarnoch > >Can anyone point me to a "well documented" DR exercise? > > > >(Lookin for some "gotchas") > > You are asking an *extremely* wide-open question, and it is doubtful > that any given DR procedure will be particularly relevant to your > situation. > > You can do one of several things: > 1. Hire a DR professional to help you create a documented procedure. > 2. Create your own DR procedures. > 3. Ask this forum more specific questions describing your particular > situations and concerns > > A good resources to begin #2 with is > > The IBM Redbook _Disaster Recovery Strategies with TSM_ > http://www.redbooks.ibm.com/abstracts/sg246844.html?Open > > -- > Mark Stapleton ([EMAIL PROTECTED]) > IBM Certified Advanced Deployment Professional > Tivoli Storage Management Solutions 2005 > Office 262.521.5627
Re: Can I exclude he WinSxS folder on Windows2003 server?
Bill, I just found your message while catching up on email. That folder holds Windows' "side-by-side" executables. Those are used by Windows for downward compatibility with older applications. So excluding them won't affect *Windows*, but whatever old application you're running that is using them will probably fail to start. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 03/29/2005 08:10:36 AM: > I have a client with a Windows2003 server with Exchange 2003 on it. > Lately he started seeing errors in his nightly non-Exchange > backups relating to a file in the C:\Windows\WinSxS folder. I've > search the archives and came up dry. No hits on IBM either. I > Google search brought up some information on package assemblies. > > > > Would it be safe to EXCLUDE.DIR the C:\WINDOWS\WINSXS directory? The > error(s) the client is getting are: > > > > 03/28/2005 03:32:13 ANS1228E Sending of object > '\\hbgexchits1\c$\WINDOWS\WinSxS\Policies\x86_policy.5.2.Microsoft. > Windows.SystemCompatible_6595b64144ccf1df_x-ww_92C6FB91\5.2.0.0.p > olicy' failed > > 03/28/2005 03:32:13 ANS4023E Error processing > '\\hbgexchits1\c$\WINDOWS\WinSxS\Policies\x86_policy.5.2.Microsoft. > Windows.SystemCompatible_6595b64144ccf1df_x-ww_92C6FB91\5.2.0.0.p > olicy': file input/output error > > 03/28/2005 03:32:44 ANS1512E Scheduled event 'BD70330' failed. > Return code = 12. > > > > > > And the backup schedule indicates failed. > > > > Bill Boyer > > "Growing old is mandatory, growing up is optional" - ??
Re: Spontaneous reclamation
Mark, Thanks for that clarification. That matches what I've seen on the "archive" side of the system. Tab "Stapleton, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 03/21/2005 12:39 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Spontaneous reclamation From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier >I think Guillaume might have figured it out. Let's say we keep five >versions of a file. If, during the night, the system picks up a sixth >version, does the oldest version scroll off immediately? Or >does it wait >for reclamation? If immediately, that is almost certainly >what happened. >But what is odd is that I've never noticed that occurrence >before despite >administering the system for the last seven years! No, the oldest version of the file doesn't just roll off. You have to run an inventory expiration to delete the pointer to the old file; once the pointer is deleted, and you meet your reclamation threshhold, the file indicated by the expired pointer will vanish when the volume it resides in is reclaimed and reused. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: Spontaneous reclamation
Richard, "The only explanation I can think of for this would be the influence of the EXPINterval server option, if that hasn't been deactivated; but I'd expect that you'd have seen evidence in the Activity Log." I just verified that ExpInterval is set to zero. I was pretty sure that it was. We've been controlling the expiration via cron scripts since ADSM 2 was first installed. And in reference to Remco's message, we check for failed processes daily. There were no failed reclamations at the end of the last maintenance cycle, so there was nothing lingering for TSM to resume. I think Guillaume might have figured it out. Let's say we keep five versions of a file. If, during the night, the system picks up a sixth version, does the oldest version scroll off immediately? Or does it wait for reclamation? If immediately, that is almost certainly what happened. But what is odd is that I've never noticed that occurrence before despite administering the system for the last seven years! Thanks. Tab
Re: Spontaneous reclamation
David, "I'll ask the obvious. Any chance you copypool reached 100% triggering a reclaim?" The reclamation ran on a primary storage pool. There is nothing *obvious* that could have pushed ONE tape over the pool's 50% reclamation threshold during the midnight to 1:00 am period when reclamation launched. Reclamation ran on that one volume only. During our maintenance cycle, which is running now, that particular pool can reclaim as many as 30 volumes. Thanks. Tab
Re: Spontaneous reclamation
Lawrence, So have I, but there was no such activity last night. Only normal backups, with the occasional migration since some of our data paths have small disk pools that function only as "mount point multipliers" and migrate to tape at 10% filled. Thanks for the tip. Tab "ADSM: Dist Stor Manager" wrote on 03/21/2005 09:37:24 AM: > I've seen reclamations kick off after deleteing nodes. > > >>> [EMAIL PROTECTED] 03/21/2005 10:17:04 AM >>> > TSM Server 5.1.9.0 on AIX 5.2 ML-4 > TSM Client mix of 5.1.6.0 and 5.1.7.0 mostly on Windows > > This morning I found a primary storage pool tape "pending" as the > result > of reclamation that launched spontaneously just after midnight. The > logs > show no evidence of anyone issuing any commands to launch that > operation. > I'm trying to figure out how that happened since we maintain pretty > tight > control over the TSM maintenance processes. > > Specifically, on our system, maintenance occurs weekly. On Monday at > 9:00 > am we run expiration which of course triggers reclamation of the > primary > pools. Expiration completes late Monday afternoon with all primary > reclamation completing sometime late Monday night to early Tuesday > morning. We leave our copypool reclaim point set at 100% throughout > this > process. On Tuesday at 6:00 pm we launch copypool reclamation, after > which the reclaim point is returned to 100%. > > That is our entire maintenance schedule. No other expirations or > reclamations are scheduled to occur at any time. > > So what could have provoked a primary tape reclamation at midnight, > approximately nine hours before the start of the regular maintenance > cycle? > > Just curious. > > Tab Trepagnier > TSM Administrator > Laitram, L.L.C.
Spontaneous reclamation
TSM Server 5.1.9.0 on AIX 5.2 ML-4 TSM Client mix of 5.1.6.0 and 5.1.7.0 mostly on Windows This morning I found a primary storage pool tape "pending" as the result of reclamation that launched spontaneously just after midnight. The logs show no evidence of anyone issuing any commands to launch that operation. I'm trying to figure out how that happened since we maintain pretty tight control over the TSM maintenance processes. Specifically, on our system, maintenance occurs weekly. On Monday at 9:00 am we run expiration which of course triggers reclamation of the primary pools. Expiration completes late Monday afternoon with all primary reclamation completing sometime late Monday night to early Tuesday morning. We leave our copypool reclaim point set at 100% throughout this process. On Tuesday at 6:00 pm we launch copypool reclamation, after which the reclaim point is returned to 100%. That is our entire maintenance schedule. No other expirations or reclamations are scheduled to occur at any time. So what could have provoked a primary tape reclamation at midnight, approximately nine hours before the start of the regular maintenance cycle? Just curious. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: review of recent addition of sata array storage pool
Steve, Thanks for sharing that and starting that thread. We're about to implement SATA storage on a SAN in about two weeks that will be used with TSM. Tab Trepagnier TSM Administrator Laitram, L.L.C.
TDP Domino PIT
TDP Domino 5.1.5 on Domino 6.5.3 on Windows 2003 We are attempting to do Point-in-Time restores of databases backed up since early 2001. If we look at the inactive backups in the TDP GUI we can see multiple versions going back through the years. If we do a point-in-time, with the PIT set to 12/31/2001, TSM reports that there are no databases to be restored. We get the same results using the Command Line client and /Pick. Over the years this has been a pretty reliable system so I don't think we've missed many backups. Any help would be appreciated. Tab Trepagnier TSM Administrator Laitram LLC
Re: Volume Reuse Parameter
Joni / Rob, I believe that is a bit risky. A Reuse Delay of zero means a tape is a candidate for reuse immediately after being emptied. If you reuse your tapes that soon, and you have to restore back to an earlier DB backup, there will be lots of files that are no longer where TSM expects to find them. You can restore them from the copypool(s), but that can take a while. In the meantime, TSM will be spitting out MILLIONS of error messages onto the console and into the Act Log. We set our Reuse Delay for primary pools to 2 days; and 5 days for copypools and any primary pools whose volumes are stored off-site. The idea is that you should have AT LEAST ONE database backup that records the new location of the files that used to be on those tapes. This has come up before on the list, and if you're "fat" with tapes, you can set it for however long you retain your database backups. Since we do daily DB backups, those delay settings ensure that we get at least two DB backups before any tapes get reused. If I find myself needing a "pending" tape prior to the reuse period elapsing, I always manually launch a DB backup before flipping its status. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 03/07/2005 03:16:02 PM: > Hi Rob, > > I believe that the primary storage pools should have a reuse parameter of 0 > and your reuse delay should be the same retention as the database backup > retention so that you can go back in history. I believe that there is > supporting info. within the TSM Admin Guide that should detail this info. > concerning storage pools. Hope that helps! > > > Joni Moyer > Highmark > Storage Systems > Work:(717)302-6603 > Fax:(717)302-5974 > [EMAIL PROTECTED] > > > > > "Rob Hefty" > <[EMAIL PROTECTED] > Y.COM> To > Sent by: "ADSM: ADSM-L@VM.MARIST.EDU > Dist Stor cc > Manager" > <[EMAIL PROTECTED] Subject > .EDU> Volume Reuse Parameter > > > 03/07/2005 04:12 > PM > > > Please respond to > "ADSM: Dist Stor > Manager" > <[EMAIL PROTECTED] >.EDU> > > > > > > > Hello all, > > I was wondering if anyone was willing to offer up any ideas on what this > parameter should be set to for tape storage pools; both primary and > copy? > > Thanks!
Re: migration and backup
Iain, I run small disk pools also, and I also had HI=0 for a while. That's not a good idea because you prevent TSM from combining data into a internal package prior to migration. We saw files as small as 1 KB migrating. That forces your TSM server to track a HUGE number of objects. Now, on our smallest disk pools (5 to 6 GB) we set HI=10 so that migration doesn't begin until 500-600 MB of data has been committed. Much better performance. We also set a 1 GB max size so that if a client sends a very large file - say 3 GB - it goes straight to tape. Tab Trepagnier TSM Administrator Laitram, L.L.C. Iain Barnetson <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 03/04/2005 04:24 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: migration and backup I'm in a similar situation where my primary stg diskpool is not big enough to contain a nights backups. I have the migration set to hi=0 lo=0. This means it's constantly migrating but I've 6 dedicated lto2 tape drives so isn't an issue for me. Regards, Iain -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of John Naylor Sent: 04 March 2005 10:17 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] migration and backup Your disk pool is way too small. It should be large enough to hold one night's backups If you can't do that, set your hi mig threshold to a low value say 10 or even lower At 80% your backup fills up the remaining 20% of your pool faster than migration can empty it. nghiatd <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 04/03/2005 10:15 Please respond to "ADSM: Dist Stor Manager" To ADSM-L@vm.marist.edu cc Subject migration and backup Hi all, I setup TSM ver 5.2 client on Win 2K that has more than 200 GB data, But TSM server machine only 20 GB hard disk. So I configure Backuppool ---> Diskpool --->Tapepool. Diskpool : 18 GB High Migration Threshold : 80 % Low Migration Threshold : 0 %. People said when migration process is started, backup process is still continuous. But I view log file ; 02/03/2005 06:22:26 Normal File--> 719,648,279 \\BILL2_200411_2.tar * Unsuccessful* 02/03/2005 06:22:26 A1114I Waiting for mount of offline media. 02/03/2005 06:55:37 Retry # 1 Normal File--> 719,648,279 \\BILL2_200411_2.tar [Sent] 02/03/2005 06:55:37 ANS1809W Session is lost; initializing session reopen procedure. 02/03/2005 06:55:53 ... successful 02/03/2005 06:56:16 Normal File--> 726,513,573 \\BILL2_200411_3.tar [Sent] So backup was stopped when migration process is started. Does anyone have idea to backup process still continue ? Nghiatd ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. Scottish Hydro-Electric, Southern Electric, SWALEC, S+S and SSE Power Distribution are trading names of the Scottish and Southern Energy Group. **
Re: Reclamation and collocation...
Allen, >From what I've seen on our system, TSM will reclaim filling tapes in primary pools if the space to be reclaimed is behind the write point of the tape. For example, suppose TSM loads a scratch tape and writes onto it until it's 75% filled. That tape is in "filling" status. Then expiration runs and most of the data already written gets purged off. The tape is still in "filling" status, and the remaining 25% is still usable. But most of the 75% already used is reclaimable space and TSM cannot use it until that tape is reclaimed. We see this on our smaller collocated tape pools. We run maintenance - expiration, reclamation, etc - weekly, so we might have multiple versions from "that" node on one tape, but the tape has not yet filled up. Once expiration runs, then we end up reclaiming the "filling" tape. For us, it looks a bit odd, but doesn't really cause any problems. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 02/22/2005 06:52:22 PM: > Greetings. > > > I've got a peeve about how TSM reclaims collocated stgpool volumes, and I > wanted to see if it is widely shared. If so, I'll try to distill it into a > sane feature request. > > > I've got a bunch of collocated stgpools now, and I find that I am frequently > reclaiming volumes which are in a FILLING state. This seems to be > counterproductive to me. > > I understand the math behind it: If pct_reclaim >= threshold, then it's a > candidate for reclamation. But my motiviation to reclaim a tape that is only > 20% written is mighty low. I'd just as soon wait another week/month/whatever, > and use the tape drive time to do other things. > > I find that reclamation occupies more tape-head time than any other activity > my TSM server does; I'm essentially never idle unless I've specifically > cleared the decks for some reason. So spending a lot of time doing "work" > that doesn't buy me anything is aggravating. > > > > So, I ask: Is there some aspect to this I'm missing? An advantage to > reclaiming a tape that's "50% reclaimable" but only 40% written? A knob that > already exists to limit reclamation to full volumes? > > Or is this same behavior irritating to you folks too? > > > > - Allen S. Rout
Cancelling a client session after a set period of time
TSM 5.1.9.0 Server on AIX 5.2 ML-4 TSM 5.1.7.0 Client on Windows 2000 SP 4 We have a large remote client that backs up over a 512 Kbs link. We turned on Subfile backup, but the client is still capturing its base files. We expect it to send about 60 GB, which will take weeks. What we need is to restrict the client session to send data only between about 5 pm and about 5 am., and then terminate. On the next day's backup, it would of course pick up where it left off. Is there a way to automate that session behavior? I didn't see anything in the Admin Reference. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Why do database restores take so long?
Wanda, Since that DB restore was almost a week ago, I don't have any live data for you. But *if I recall correctly*, each disk was about 50-60% busy. Also, the DB and log re-mirrored themselves automatically after the restore, yet I thought I saw the mirror volumes being written in parallel. Note that the DB and log are TSM-mirrored; the disks are not mirrored to each other. The TSM re-mirror operations showed 25-50 MB/s according to topas; indeed, the entire mirror-sync operation took only a few minutes to complete. I've restored data from the same DLT and it comes in at its usual average of 8 MB/s per drive (file data rate; DB backup rate is 11 MB/s), so I doubt the DLT is the culprit. Even during the DB restore, I saw rare spikes to 6 MB/s. Since the restore took 3-1/4 hours vs. a 50-minute backup means the average restore rate was 11 x 50 / 195 = 2.8 MB/s, despite periods when data was being restored as slowly as 300 KB/s. Thanks for the feedback. Tab "ADSM: Dist Stor Manager" wrote on 01/25/2005 12:23:05 PM: > What does topas report during the restore about disk device busy? > > Some things I would try, if I had enough of a test environment to try > it, is a DB restore from a disk backup instead of tape; if it takes > longer from tape, then the DLT is part of the problem. > > If topas reports a lot of disk busy during the restore, I'd try breaking > the mirror before doing the restore, and reestablishing the mirror > afterwards. Cutting the I/O in half has gotta help somewhere > > Wanda Prather > "I/O, I/O, It's all about I/O" -(me) > > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Tab Trepagnier > Sent: Friday, January 21, 2005 6:16 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Why do database restores take so long? > > > Dave, > > Our database disk system consists of four 18 GB SCSI disks in a split > (dual-bus) disk pod connected to a dual-channel LVDS adapter. The > Recovery Log in on another pair of such disks. One set of disks on one > bus holds the primary database and log volumes; two DB and one log disk. > Each DB/log volume is mirrored to an identical volume/disk on the other > bus. So the mirror read/writes occur on independent buses downstream of > the PCI slot. The database consists of four volumes per disk of about 4 > GB each. All database and log volumes are defined on JFS2 file systems. > The LVDS adapter is the IBM 64-bit dual-channel adapter called "PCI DUAL > CHANNEL ULTRA3 SCSI ADAPTER", Part Number 09P2544. > The disks are "16 Bit LVD SCSI Disk Drive (18200 MB)", Machine Type and > Model = ST318305LC which I *think* is 15K rpm. > The server is a 2-way 6H1 64-bit 600 MHz with 4 GB RAM, tuned for just > about zero paging. TSM DB buffer pool is 1 GB. > Like I said, when backing up to our HP 4/40 DLT via HVD SCSI, topas > reports a consistent 11 MB/s, such that a typical backup takes just > about > 45-50 minutes including the tape mount. > The restore took slightly over three hours; and the 3:1 ratio is not out > of line based on other responses. > > Thanks. > > Tab > > > > "ADSM: Dist Stor Manager" wrote on 01/20/2005 > 11:27:02 PM: > > > Can you provide a little more information? I would like to know: > > > > 1. What kind of disk subsystem are you restoring the data to? > > 2. How many disks, and what kind of disks are they? > > 3. How is the database laid out database volume wise? > > 4. Does the disk have write cache behind it? > > 5. What kind of controller do you have for the disk > subsystem? > > > > At 07:23 PM 1/20/2005 -0600, you wrote: > > >TSM 5.1.9.0 on AIX 5.2 ML4; DLT8000 media on SCSI > > > > > >Why do TSM database restores take so much longer than the backups? > Our > > >system backs up our 24 GB database to DLT in about 50 minutes with a > > >sustained rate of 11 MB/s reported by topas. > > > > > >Tonight I'm performing a database restore. It is occurring at an > average > > >rate of less than 1 MB/s with rare peaks no higher than 6 MBs. At > times > > >the rate is as low as 300 KB/s. > > > > > >I realize the system is writing data to disk rather than reading so > its > > >not doing as much caching, but these are new disks and I've seen them > > >stream write at better than 25 MB/s on the inner edge and as fast as > 50 > > >MB/s on the outer edge. So I doubt the disk is the problem. > > > > > >This restore has been running for almost 2-1/2 hours now and is about > 90% > &
Re: Why do database restores take so long?
Dave, Thanks for the suggestions. I do have a test system so I will look into trying turning off the JFS2 log. You provided enough hints that I should be able to figure it out. I don't think the LVDS adapter has write cache. Thanks again. Tab Dave Canan <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/21/2005 08:24 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Why do database restores take so long? One suggestion I would make here. For a restore such as this, I have seen performance improvements if you temporarily disable the jfslog (or in this case, the jfs2log) for the duration of the restore. This has the effect of not writing the data to the jfs log before it is written to the database, so it is in effect like a raw filesystem write. If you want specific procedures I can send them to you, but it is basically accomplished by unmounting the filesystem and the remounting it with the options of rw and nointegrity. After the resore is finished, you would then remount the filesystem with just the rw option so that the jfslog is once again used. I don't know if you want to try this or not, because restores of TSM databases are not generally something you can "test" unless you have a test environment. But you might want to keep this in mind if you ever need to this again. There was 1 other thing I wanted to ask. I was trying to find out whether or not the IBM PCI card (part number 09P2544) had cache on it or not. I couldn't locate specifications on it, but if it doesn't, a card on it that had embedded cache would help this situation as well. At 05:16 PM 1/21/2005 -0600, you wrote: >Dave, > >Our database disk system consists of four 18 GB SCSI disks in a split >(dual-bus) disk pod connected to a dual-channel LVDS adapter. The >Recovery Log in on another pair of such disks. One set of disks on one >bus holds the primary database and log volumes; two DB and one log disk. >Each DB/log volume is mirrored to an identical volume/disk on the other >bus. So the mirror read/writes occur on independent buses downstream of >the PCI slot. The database consists of four volumes per disk of about 4 >GB each. All database and log volumes are defined on JFS2 file systems. >The LVDS adapter is the IBM 64-bit dual-channel adapter called "PCI DUAL >CHANNEL ULTRA3 SCSI ADAPTER", Part Number 09P2544. >The disks are "16 Bit LVD SCSI Disk Drive (18200 MB)", Machine Type and >Model = ST318305LC which I *think* is 15K rpm. >The server is a 2-way 6H1 64-bit 600 MHz with 4 GB RAM, tuned for just >about zero paging. TSM DB buffer pool is 1 GB. >Like I said, when backing up to our HP 4/40 DLT via HVD SCSI, topas >reports a consistent 11 MB/s, such that a typical backup takes just about >45-50 minutes including the tape mount. >The restore took slightly over three hours; and the 3:1 ratio is not out >of line based on other responses. > >Thanks. > >Tab > > > >"ADSM: Dist Stor Manager" wrote on 01/20/2005 >11:27:02 PM: > > > Can you provide a little more information? I would like to know: > > > > 1. What kind of disk subsystem are you restoring the data to? > > 2. How many disks, and what kind of disks are they? > > 3. How is the database laid out database volume wise? > > 4. Does the disk have write cache behind it? > > 5. What kind of controller do you have for the disk subsystem? > > > > At 07:23 PM 1/20/2005 -0600, you wrote: > > >TSM 5.1.9.0 on AIX 5.2 ML4; DLT8000 media on SCSI > > > > > >Why do TSM database restores take so much longer than the backups? Our > > >system backs up our 24 GB database to DLT in about 50 minutes with a > > >sustained rate of 11 MB/s reported by topas. > > > > > >Tonight I'm performing a database restore. It is occurring at an >average > > >rate of less than 1 MB/s with rare peaks no higher than 6 MBs. At >times > > >the rate is as low as 300 KB/s. > > > > > >I realize the system is writing data to disk rather than reading so its > > >not doing as much caching, but these are new disks and I've seen them > > >stream write at better than 25 MB/s on the inner edge and as fast as 50 > > >MB/s on the outer edge. So I doubt the disk is the problem. > > > > > >This restore has been running for almost 2-1/2 hours now and is about >90% > > >complete. > > > > > >This is the fourth or fifth time I've restored the TSM database in the > > >seven years I've operated the system. I have never seen database >restores > > >exceed 1/3 the backup rate - sustained - on two different servers, >three > > >different media and going back to ADSM 3.1. > > > > > >Just curious. > > > > > >Tab Trepagnier > > >TSM Administrator > > >Laitram, L.L.C. > > > > Dave Canan > > TSM Performance > > IBM Advanced Technical Support > > [EMAIL PROTECTED] Dave Canan TSM Performance IBM Advanced Technical Support [EMAIL PROTECTED]
Re: Why do database restores take so long?
Dave, Our database disk system consists of four 18 GB SCSI disks in a split (dual-bus) disk pod connected to a dual-channel LVDS adapter. The Recovery Log in on another pair of such disks. One set of disks on one bus holds the primary database and log volumes; two DB and one log disk. Each DB/log volume is mirrored to an identical volume/disk on the other bus. So the mirror read/writes occur on independent buses downstream of the PCI slot. The database consists of four volumes per disk of about 4 GB each. All database and log volumes are defined on JFS2 file systems. The LVDS adapter is the IBM 64-bit dual-channel adapter called "PCI DUAL CHANNEL ULTRA3 SCSI ADAPTER", Part Number 09P2544. The disks are "16 Bit LVD SCSI Disk Drive (18200 MB)", Machine Type and Model = ST318305LC which I *think* is 15K rpm. The server is a 2-way 6H1 64-bit 600 MHz with 4 GB RAM, tuned for just about zero paging. TSM DB buffer pool is 1 GB. Like I said, when backing up to our HP 4/40 DLT via HVD SCSI, topas reports a consistent 11 MB/s, such that a typical backup takes just about 45-50 minutes including the tape mount. The restore took slightly over three hours; and the 3:1 ratio is not out of line based on other responses. Thanks. Tab "ADSM: Dist Stor Manager" wrote on 01/20/2005 11:27:02 PM: > Can you provide a little more information? I would like to know: > > 1. What kind of disk subsystem are you restoring the data to? > 2. How many disks, and what kind of disks are they? > 3. How is the database laid out database volume wise? > 4. Does the disk have write cache behind it? > 5. What kind of controller do you have for the disk subsystem? > > At 07:23 PM 1/20/2005 -0600, you wrote: > >TSM 5.1.9.0 on AIX 5.2 ML4; DLT8000 media on SCSI > > > >Why do TSM database restores take so much longer than the backups? Our > >system backs up our 24 GB database to DLT in about 50 minutes with a > >sustained rate of 11 MB/s reported by topas. > > > >Tonight I'm performing a database restore. It is occurring at an average > >rate of less than 1 MB/s with rare peaks no higher than 6 MBs. At times > >the rate is as low as 300 KB/s. > > > >I realize the system is writing data to disk rather than reading so its > >not doing as much caching, but these are new disks and I've seen them > >stream write at better than 25 MB/s on the inner edge and as fast as 50 > >MB/s on the outer edge. So I doubt the disk is the problem. > > > >This restore has been running for almost 2-1/2 hours now and is about 90% > >complete. > > > >This is the fourth or fifth time I've restored the TSM database in the > >seven years I've operated the system. I have never seen database restores > >exceed 1/3 the backup rate - sustained - on two different servers, three > >different media and going back to ADSM 3.1. > > > >Just curious. > > > >Tab Trepagnier > >TSM Administrator > >Laitram, L.L.C. > > Dave Canan > TSM Performance > IBM Advanced Technical Support > [EMAIL PROTECTED]
Why do database restores take so long?
TSM 5.1.9.0 on AIX 5.2 ML4; DLT8000 media on SCSI Why do TSM database restores take so much longer than the backups? Our system backs up our 24 GB database to DLT in about 50 minutes with a sustained rate of 11 MB/s reported by topas. Tonight I'm performing a database restore. It is occurring at an average rate of less than 1 MB/s with rare peaks no higher than 6 MBs. At times the rate is as low as 300 KB/s. I realize the system is writing data to disk rather than reading so its not doing as much caching, but these are new disks and I've seen them stream write at better than 25 MB/s on the inner edge and as fast as 50 MB/s on the outer edge. So I doubt the disk is the problem. This restore has been running for almost 2-1/2 hours now and is about 90% complete. This is the fourth or fifth time I've restored the TSM database in the seven years I've operated the system. I have never seen database restores exceed 1/3 the backup rate - sustained - on two different servers, three different media and going back to ADSM 3.1. Just curious. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Move media for backupsets?
Wanda, Thanks for the info. I'll look into adding that to our system. Managing backupset volumes is a pain without some extra help. Tab "ADSM: Dist Stor Manager" wrote on 01/19/2005 10:09:49 AM: > I think you are correct. > > If this is a frequent problem for you, Autovault from coderelief.com > supports ejection/vaulting of Backupsets. > > Wanda Prather > "I/O, I/O, It's all about I/O" -(me) > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Tab Trepagnier > Sent: Tuesday, January 18, 2005 5:48 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Move media for backupsets? > > > TSM 5.1.9.0 > > Is there some command(s) that would allow sequential, one-step > processing > of backupset volumes similar to the operation of the Move Media command > for storage pools? > > For example, Move Media will check out the library volume, alter its > access to read-only, set its location to the Overflow Location, and > eject > the volume from the library with just one command. And it will process > all relevant volumes if "*" is given as the volume name. So if you have > a > dozen storage pool volumes to eject, one command processes all 12 tapes > in > order. You just collect them from the library and Reply when each is > removed from the library's I/O slot. Simple. > > If those same 12 tapes are part of a Backupset, as far as I can tell, > you > must check out each tape individually, update its Location field > individually, etc. That's 24 commands for a Backupset where just one is > needed for a storage pool. > > Or am I missing something? > > Thanks in advance. > > Tab Trepagnier > TSM Administrator > Laitram, L.L.C.
Move media for backupsets?
TSM 5.1.9.0 Is there some command(s) that would allow sequential, one-step processing of backupset volumes similar to the operation of the Move Media command for storage pools? For example, Move Media will check out the library volume, alter its access to read-only, set its location to the Overflow Location, and eject the volume from the library with just one command. And it will process all relevant volumes if "*" is given as the volume name. So if you have a dozen storage pool volumes to eject, one command processes all 12 tapes in order. You just collect them from the library and Reply when each is removed from the library's I/O slot. Simple. If those same 12 tapes are part of a Backupset, as far as I can tell, you must check out each tape individually, update its Location field individually, etc. That's 24 commands for a Backupset where just one is needed for a storage pool. Or am I missing something? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Using Windows Preinstallation Environment (Windows PE)
Luc, We got it by signing up for "Software Assurance Membership" on Microsoft's server pool when we renewed our Select Licensing Agreement. Win PE is one of the "perks" you get from "server" SAM. It's probably available also as a standalone product, but I'm kinda guessing on that one. Now we just need to find the time to figure out how to use it. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" wrote on 01/17/2005 02:31:17 PM: > Hi all > > Is there anyone out there that got the LINK to download the Windows PE ... > > I want to use it for my Windows servers ... > > thanks again > > Luc
TSM 5.3 Implementation Guide
We are about to deploy our first SAN and are enhancing our DR process to use a lot more D-D. We are still at TSM 5.1 (.9.0 to be exact) and expect to jump to TSM 5.3 around version 5.3.1. Is there an Implementation Guide available - even in draft form - for TSM 5.3, or is the TSM 5.2 Imp Guide close enough to be used as a design guide? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Load tapes in "unavailable" storage pool?
Andy, Thanks for the update. I knew about that command; I use it frequently against specific volumes - that's how the ones on the shelf got to "unavailable". I thought setting it for the entire storage pool would accomplish the same thing. Have a great holiday. Tab "ADSM: Dist Stor Manager" wrote on 12/22/2004 10:12:23 AM: > Hi Tab, > > If you review the TSM Administrator's Guide, you'll see in the chapter > that talks about "Managing Storage Pools and Volumes" the following > description for storage pool access modes: > > "User operations cannot get access to volumes in the storage pool. No new > writes are permitted to volumes in the storage pool from other volumes > outside the storage pool. However, system processes (like reclamation) are > permitted to move files within the volumes in the storage pool." > > If you want to prevent access to any volumes in this pool, even for > reclamation, then you might be able to use something like this: > >update volume * access=unavailable wherestgpool=migrpool > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Development > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] > Internet e-mail: [EMAIL PROTECTED] > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" wrote on 12/22/2004 > 08:02:22: > > > TSM Server 5.1.9.0 on AIX 5.2 > > > > I am running copypool reclamation. Some of my primary tapes are stored > on > > the shelf with access = unavailable. Because there are large files that > > span tapes, I'm seeing where TSM is loading the first tape of the set, > > reaching its end, finding the second tape unavailable, and aborting > > reclamation; only to repeat the entire process a minute later and never > > moving past. > > > > In an attempt to control that behavior, I set the entire primary storage > > pool to access = unavailable. Yet when copypool reclamation restarted, > it > > again loaded the first tape of that set and repeated the process I cited > > earlier. > > > > How is that possible? I thought the whole point of setting access = > > unavailable was to tell TSM to not even TRY to use that storage pool. > Here > > are the storage pool properties: > > > > tsm: >q stg migrpool f=d > > > >Storage Pool Name: MIGRPOOL > >Storage Pool Type: Primary > >Device Class Name: DEV05 > > Estimated Capacity (MB): 14,361,230.5 > > Pct Util: 16.9 > > Pct Migr: 19.7 > > Pct Logical: 99.4 > > High Mig Pct: 100 > > Low Mig Pct: 99 > > Migration Delay: 0 > > Migration Continue: Yes > > Migration Processes: > >Next Storage Pool: > > Reclaim Storage Pool: > > Maximum Size Threshold: No Limit > > Access: Unavailable <=== > > Description: Old data pool > >Overflow Location: Local storage shelves > >Cache Migrated Files?: > > Collocate?: No > >Reclamation Threshold: 100 > > Maximum Scratch Volumes Allowed: 300 > >Delay Period for Volume Reuse: 2 Day(s) > > Migration in Progress?: No > > Amount Migrated (MB): 0.00 > > Elapsed Migration Time (seconds): 0 > > Reclamation in Progress?: No > > Volume Being Migrated/Reclaimed: > > Last Update by (administrator): TTREPAGN > >Last Update Date/Time: 12/22/2004 08:30:38 > > Storage Pool Data Format: Native > > Copy Storage Pool(s): > > Continue Copy on Error?: > > CRC Data: No > > > > tsm: > > > > > TIA > > > > Tab Trepagnier > > TSM Administrator > > Laitram, L.L.C.
Load tapes in "unavailable" storage pool?
TSM Server 5.1.9.0 on AIX 5.2 I am running copypool reclamation. Some of my primary tapes are stored on the shelf with access = unavailable. Because there are large files that span tapes, I'm seeing where TSM is loading the first tape of the set, reaching its end, finding the second tape unavailable, and aborting reclamation; only to repeat the entire process a minute later and never moving past. In an attempt to control that behavior, I set the entire primary storage pool to access = unavailable. Yet when copypool reclamation restarted, it again loaded the first tape of that set and repeated the process I cited earlier. How is that possible? I thought the whole point of setting access = unavailable was to tell TSM to not even TRY to use that storage pool. Here are the storage pool properties: tsm: >q stg migrpool f=d Storage Pool Name: MIGRPOOL Storage Pool Type: Primary Device Class Name: DEV05 Estimated Capacity (MB): 14,361,230.5 Pct Util: 16.9 Pct Migr: 19.7 Pct Logical: 99.4 High Mig Pct: 100 Low Mig Pct: 99 Migration Delay: 0 Migration Continue: Yes Migration Processes: Next Storage Pool: Reclaim Storage Pool: Maximum Size Threshold: No Limit Access: Unavailable <=== Description: Old data pool Overflow Location: Local storage shelves Cache Migrated Files?: Collocate?: No Reclamation Threshold: 100 Maximum Scratch Volumes Allowed: 300 Delay Period for Volume Reuse: 2 Day(s) Migration in Progress?: No Amount Migrated (MB): 0.00 Elapsed Migration Time (seconds): 0 Reclamation in Progress?: No Volume Being Migrated/Reclaimed: Last Update by (administrator): TTREPAGN Last Update Date/Time: 12/22/2004 08:30:38 Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No tsm: > TIA Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Does PreScheduleCmd work with Archives?
Andy, Thanks VERY much for that info. I assume the syntax in the command line is the same as in the OPT file plus leading dash: -PRESCHEDULECMD 'cmd.exe /c "d:\Oracle\database\idevhotbackup.cmd" ' Is that correct? Thanks again. Tab The problem is that OPTFILE is not a valid option in the schedule definition. You can, however, include the PRESCHEDULECMD option in the schedule definition. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence.
Does PreScheduleCmd work with Archives?
TSM Server 5.1.9.0 on AIX 5.2 TSM Client 5.1.6.0 on Windows 2000 SP4 I'm trying to launch a database archive job with a PreScheduleCmd option included in the OPT file. This is a special OPT file that is specified as an option on the schedule command line: Action: Archive Options: -optfile=C:\Progra~1\Tivoli\TSM\baclient\dsm2.opt -archmc=archtemp -subdir=yes I see no evidence that the script file referenced in the OPT file is ever being executed. This is the option: PRESCHEDULECMD 'cmd.exe /c "d:\Oracle\database\idevhotbackup.cmd" ' On a different server that also uses the PreScheduleCmd option, I get a line in the dsmsched.log showing its execution: 12/20/2004 02:11:54 Executing Operating System command or script: cmd.exe /c "D:\Program Files\Microsoft SQL Server\MSSQL\BackupDB.cmd" 12/20/2004 02:18:33 Finished command. Return code is: 0 However, on the node in question, the dsmsched.log contains no such line. It appears that it didn't even TRY to run the specified script. Permissions look OK so it's not an NT permissions thing. The syntax for calling the scripts are the same on both servers. There is nothing that I can see in the Windows client manual that says that option is valid for backups only, so it should work for archives too. Is that really the case, or am I expecting TSM to do something that it can't? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: License counts
Mark, I know about that; I put them in. But the query reports that all of them are in use: Number of Managed System for LAN in use: 148 Number of Managed System for LAN licensed: 148 THAT'S what I'm trying to understand. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Stapleton, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 12/14/2004 01:44 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: License counts From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier >As the new year approaches it's time to renew our TSM >licenses. As I understand the terms, any client that does not >connect for more than 30(?) days relinquishes its license for >use by another node. > >If I query the Nodes table, it shows that 128 nodes have >connected to our server over the last 90 days. > >If I query TSM with Q LIC, it shows we have 148 active client licenses. >Running an Audit Lic does not change the client count. > >Where are those 20 extra nodes coming from? 148 is the number of licenses that TSM was told to license when it was installed; whomever installed TSM told the machine that there were 148 client licenses (mgsyslan.lic) available. Auditing the licenses will not change this number. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
License counts
TSM Server 5.1.9.0 on AIX 5.2 TSM Clients 5.1.6.0 and 5.1.7.0; mostly Windows and a few AIX TSM for Mail / Domino 5.2 As the new year approaches it's time to renew our TSM licenses. As I understand the terms, any client that does not connect for more than 30(?) days relinquishes its license for use by another node. If I query the Nodes table, it shows that 128 nodes have connected to our server over the last 90 days. If I query TSM with Q LIC, it shows we have 148 active client licenses. Running an Audit Lic does not change the client count. Where are those 20 extra nodes coming from? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Backupset questions
I've begun using backupsets to expedite DR and to reduce the retention period of online backups. I have a couple of questions about long-term handling of backupset volumes. TSM Server 5.1.9.0 on AIX 5.2 TSM Clients mix of 5.1.6.0 and 5.1.7.0 on Windows and AIX 1. The backupsets I generated this weekend have a two-year (730 days) retention period. Because one purpose of those backupsets is DR-related, I plan to send those tapes to our offsite vault. Q: What happens on day 731 that will alert me to ask for those tapes to be returned from the vault for reuse? 2. For the last 3-1/2 years we've sent all data going off-site on DLT media. Suppose that a year from now, we change tape media. Q. What can I do with those "two-year" backupsets that still have another year before expiration? Is there an easy way to move those backupsets to another medium? Even if they span multiple tapes? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Backup options
David, I run a GigE NIC in my TSM 2-way 6H1 with all SCSI-connected storage. GigE works very well because most of the sending nodes are on 100 Mbs with a few larger servers on GigE. That prevents the recipient - the TSM server - from being the bottleneck. The CPU load scales up with the data througput, but using Topas, I have seen as much as 80 MB/s passing through the NIC during peak backup times. And while idle % was very low (~1 % or so) the server reported no difficulties and response time to TSM Admin commands like "Q PR" was instantaneous. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 11/10/2004 07:14:01 AM: > >Another option is to bump-up your ethernet... are you already running > a > >gigabit ethernet? We've actually bumped up the TSM server and the > large > >unix clients to Gigabit Ethernet, and it improved the throughput of > the > >backup. > > > > The 100 meg card in our TSM server is saturated during our backup > window. We are exploring moving to a gig ethernet. Did you see changes > in your TSM server when you went to the faster speeds? Higher cpu, > paging? What effects did you see in your disk/tape I/O? > > David
Re: Restore from 250 GB of 2 000 000 files in 1 day
Ralf, Several months ago we restored an entire file server with about one million files totalling almost 300 GB backed up via TSM's "incremental forever" strategy. At the time the data was scattered across LOTS of 3570 tapes (~ 8 MB/s) and also some LTO-1 tapes (~ 15 MB/s). We were able to run four parallel restore sessions to the target server which was running Windows 2003 on a one-way P3-Xeon. The restore took slightly over twelve hours to complete. Hope this helps and good luck. Tab Trepagnier TSM Administrator Laitram, L.L.C. "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 11/10/2004 02:31:13 AM: > Hallo, > > is its possible to restore 250 GB ( two million files) within a day? > Its an NSF mounted filesystem. Can parallel restore increase the throughput > by an NSF-mouted filesystem. > The filesystem is mounted from a EMC cellera and symmetrix. > The backup time was with 13 hours with parallel sessons. > Then the data will be migrated the LTO1 tapes in an IBM 3584. > Has any one experience with restore off many little files with high > throughput. > > best regards > > Ralf Behrendt > mailto:[EMAIL PROTECTED] > < snip...>
Re: AIX Paging Space Utilization
Curtis, I'm guessing that the restriction on Maxclient might do the trick. Shortly after updating our TSM and Oracle servers to AIX 5.2, I started using JFS2 for some of the file systems. In a very short time, I saw page file usage in the 60-70% range after YEARS of running less than 10%. I eventually tracked it down to the MaxClient% which sets the percentage of memory used for file pages and caching of JFS2. I had been setting MaxPerm% but that only applies to JFS(1). After restricting that parameter to about 30%, pagefile usage dropped to its normal range of about 5%. It is currently 4.6% as I write this. Tab Trepagnier TSM Administrator Laitram, L.L.C. Curtis Stewart <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 09/20/2004 03:50 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: AIX Paging Space Utilization We changed our settings to the following. I'll let you all know if this fixes the problem in our case. Thanks for all the advice. So far so good. After we made the changes, I stopped both instances of TSM, and the paging space was reclaimed in about 5 minutes. It's sitting at 74.3% free now, after a couple of hours. I'll give it a couple of days and report for anyone who's interested. Oh, and Richard still didn't get the size of the paging space increased. The wet noodle flogging didn't work completely, but it got the VM Tuning done! 1) Maxperm = 50% 2) Minperm = 10% 3) Maxclient = 20% 4) Strict_Maxperm = 1 Curtis [EMAIL PROTECTED]
Re: Windows unattended client upgrade scenario; how to uninstall v3 and v4 clients unattended?
Marcel, I didn't see any responses so I'm going to take a shot. In general, the application uninstall string is stored in the Registry. After all, the "Remove" button has to submit some command to Windows to cause the program to remove itself. That Registry key is the command. What's missing is the "hands off" part. Depending on the installation tool, you can try appending a "-a" or a "-q" to make it "quiet". We used that technique to script the uninstall of the RightFax client on over 100 PCs. We located the uninstall string in the Registry, patched it for silect operation, and fed it to Windows. Worked like a charm. Hope this helps, or at least points in a usable direction. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Anthonijsz, Marcel M SITI-ITIBHL" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 09/07/2004 11:38 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Windows unattended client upgrade scenario; how to uninstall v3 and v4 clients unattended? Hi all, I am currently trying to fix and align our Windows installed TSM Client base, and as we neglected this in the past, we have a variety of TSM Client versions in the field. We have about 200 NT clients that need updating. I want to create an unattended install script to seamlessly install the latest TSM client for Windows NT (5.1.7.3) or Windows 2000. (5.2.3.1). Now the install part (is..) looks easy with MSIEXEC, the difficult part is the uninstall of the v3 and v4 clients. These are the TSM Client versions we have out there: 3.7.2.0 4.1.0.0 4.2.0.0 4.2.1.20 4.2.3.0 4.2.3.4 5.1.1.0 5.1.5.0 Now all Version 5 release notes say that first we need to uninstall the V4 and V3 Client software. But how should that be done unattended All documents say : "Open the Control Panel and double click on the Add/Remove Programs icon" - but that's not what I call unattended :-(. I have searched the list, but could not find a definite answer, nor in any Tivoli documentation. Any more gotcha's I'll need to know for the upgrades? Thanks for all the wisdom, Marcel Anthonijsz Global Data Storage Manager (a.k.a. storman) Shell Information Technology International B.V. PO Box 1027, 2260 BA Leidschendam, The Netherlands T: +31-70 303 4984 F: +31-70 303 4011 E: Marcel.Anthonijsz.atsign.shell.com Internet: http://www.shell.com
Re: Export quesion
Mark, Any machine that has 3.7TB worth of files is *begging* to be broken up into multiple node names, each node responsible for backing up a portion of a physical machine. Particularly if you're using slow tape technology like DLT. I agree with you, and in fact, we've done that with our main file servers. But this is a Domino TDP node - all the databases (about 1000) and the entire history of its transaction log. I suppose I could have exported the databases and logs separately, but that would have just turned a nine-day export into two five-day exports. It should be possible for TSM to do a checkpoint at the end of every filled volume. As for our DLTs, they are slower than LTOs, but when we bought the 4/40 three years ago, it was a "Cadillac" compared to our old one-drive DLT 4000 autoloader. Our offsite tape throughput went from 2.5 MB/s to 32 MB/s. And three years ago, LTO-1 was just being introduced. We didn't think they were a suitable DR medium because of that newness. We only use DLT for offsite. Onsite we use LTO-1 and 3570, and hope to begin using a VTL by next year. Thanks for your feedback. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Stapleton, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/26/2004 06:55 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Export quesion From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier >This is an opportunity for an enhancement. I've been bit by >that situation also. > >The problem is that an export is a single transaction. Either >it fails or it succeeds. As I write this I'm holding my >breath hoping that the last 100 GB of the current _3.7 TB_ >export complete without a problem. It has been running for >eight days now and has survived two "dropped tape" >events by our 3583 LTO and is currently writing DLT # 64 in >our HP 4/40. Any machine that has 3.7TB worth of files is *begging* to be broken up into multiple node names, each node responsible for backing up a portion of a physical machine. Particularly if you're using slow tape technology like DLT. Exports have been notoriously slow to write (and read) from ADSM/TSM first iteration. (This is one reason why you can now export directly from one TSM server to another.) Did you perform a MOVE NODEDATA prior to the export? If you didn't, and the node is not collocated, you made your life far harder than it had to be. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: Export quesion
Wanda / IBM, This is an opportunity for an enhancement. I've been bit by that situation also. The problem is that an export is a single transaction. Either it fails or it succeeds. As I write this I'm holding my breath hoping that the last 100 GB of the current _3.7 TB_ export complete without a problem. It has been running for eight days now and has survived two "dropped tape" events by our 3583 LTO and is currently writing DLT # 64 in our HP 4/40. What I would like to see is for the export process to be able to resume at the end of the last completely filled tape. I don't care if it has to throw away a partially filled tape. I do care if it has to throw away 64 - or more - full tapes. As servers and data stores get larger, it just isn't practical to cancel a process running days or weeks because of a single tape I/O failure. Just a suggestion. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/26/2004 01:24 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Export quesion You will have to start the EXPORT from the beginning. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Robert Ouzen Sent: Wednesday, August 25, 2004 5:53 PM To: [EMAIL PROTECTED] Subject: Export quesion Hi to all Today I ran an export command of a few nodes and during the process after a few hours I had an error command in one cartridge (DLT8000) couldn't be read successfully and the process was abandonded: 08/25/2004 15:44:57 ANR8944E Hardware or media error on drive SRV4 (/dev/mt4) (OP=LOCATE, Error Number=5, CC=306, KEY=03, ASC=11, ASCQ=00, SENSE=F0.00.03.00.00.00.BA.16.00.00.F3.38.11.00- .00.00.00.00.81.0D.90.00.00.44.B6.00.5D.47.6D., Description=Drive or media failure). Refer to Appendix D in the 'Messages' manual for recommended action. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:44:57 ANR8359E Media fault detected on DLT volume 90 in drive SRV4 (/dev/mt4) of library SCALAR. (SESSION: 3305, PROCESS: 210) 08/25/2004 15:45:15 ANR0986I Process 210 for EXPORT NODE running in the BACKGROUND processed 504589 items for a total of 24,126,583,819 bytes with a completion state of FAILURE at 15:45:15. (SESSION: 3305, PROCESS: 210) My question is did I need to run the process from the beginning or can I continue from where it was abandonded after fixing the problem on the damage volume (move data...). Thanks in advance . Regards Robert Ouzen E-mail: [EMAIL PROTECTED] - FIGHT BACK AGAINST SPAM! Download Spam Inspector, the Award Winning Anti-Spam Filter http://mail.giantcompany.com <http://mail.giantcompany.com/>
Re: New version
Rainer, Count your blessings. I accidently - with a wild mouse - joined a date field to a text field in the MS Query tool connected to the ODBC connection and it brought down the entire TSM server on a "type mismatch error." That was TSM 5.1.9.0 on AIX 5.2 ML-2. Tab Trepagnier TSM Administrator Laitram, L.L.C. Rainer Tammer <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/23/2004 10:44 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: New version Hello, I could confirm the ODBC problem. I tried this from a 5.2.3.0 Win32 ODBC client to a 5.2.3.2 AIX server. Access 2003 on Windows is hanging and the TSM server is on 100%... Bye Rainer Tammer Richard van Denzel wrote: >Patricia, > >I've got a customer running 5.2.3.2 on AIX 5.1 ML4 and we've seen so far a >couple of strange TSM crashes and when the customer uses his ODBC coupling >then TSM goes haywire (100% CPU usage). > >So my advice, goto 5.2.2 and wait for the next patch version of 5.2.3 and >see what has been fixed. > >Richard. > > > > > >"LeBlanc, Patricia" <[EMAIL PROTECTED]> >Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> >23-08-2004 15:11 >Please respond to "ADSM: Dist Stor Manager" > >To: [EMAIL PROTECTED] >cc: >Subject:New version > > >Is anyone using TSM Server v5.2.3 (AIX platform)? I'm upgrading from >TSM server5.1.1.6 and am wondering if any bugs have been found with this >version since it's so new. > > > >
Re: D2D vs. tape backups with TSM?
Tim, "It is possible to pre-define the volumes with DEFINE VOLUME (I have not tried this)." The limitation of one file system per FILE device class affects scratch volumes only. As far back as ADSM 3.1 I had FILE volumes belonging to one DevClass defined on six different disk file systems. Your suggestion works just as one would expect. We pre-defined the FILE volumes to the storage pool and everything worked fine for years. Allowed us to spread the disk load across all those disks without using RAID. Tab Trepagnier TSM Administrator Laitram L.L.C.
Re: storage pool raid 1?
Mark, It's actually worse than that. For a striped volume with no fault-tolerance, the overall reliability is the product of the individual reliability factors. For example, if you have 10 disks and each has a 99% reliability rating, the overall reliability of a RAID-0 volume spanned across all 10 disks is 0.99 ^ 10 = 0.9044. In other words, that RAID-0 volume is just 90% reliable. I never use RAID-0 for anything critical. If all you want is a "big bucket" and loss of the data isn't that big a deal, then it's a suitable choice. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Stapleton, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/21/2004 08:41 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: storage pool raid 1? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Mike Eggleston >Sorry about the raid1, I meant raid0 (striping). I'm on AIX 5.2. I would *never* do just striping. There is no fault tolerance in that case; loss of one disk means loss of all data on all disks. -- Mark Stapleton
Re: 3582 supported on TSM 5.2.2 AIX ?
Daniel, Thanks very much for that info. We run TSM on AIX, currently TSM 5.1.9 on AIX 5.2. We have no plans to change other than TSM updates. So your info is a big relief. Tab Daniel Sparrman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/12/2004 03:04 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: 3582 supported on TSM 5.2.2 AIX ? Hi Tab It all depends on which OS you're planning on running. As long as you stick with an OS where there has existed drivers for a long time, there shouldnt be any problems(like AIX, HP/UX, Solaris and Win32/64). The problem arises when you try to move to a new platform, like Linux. The newly developed drivers doesnt support the 357X-series of hardware anymore. But, as long as you stick with a driver that has been around for some time(like the Atape driver for AIX) there shouldnt be a problem. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 TÄBY Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Tab Trepagnier <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2004-07-09 19:05 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: 3582 supported on TSM 5.2.2 AIX ? Daniel, I just read your message. We have two 3575s, an L12 and an L18. Will they still work properly after we go to TSM 5.2? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. Daniel Sparrman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/05/2004 06:30 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: 3582 supported on TSM 5.2.2 AIX ? Hi Sascha It means from, so you shouldnt have any problems using your 3582 under TSM 5.2.2.2. The only tape libraries from IBM that has gone out of support is the 3575-series of libraries. Notice that you will have to download and install the IBM Atape device driver, which you can download from ftp://ftp.software.ibm.com/storage/devdrvr/AIX. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 TÄBY Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Sascha Askani <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2004-07-05 13:18 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject 3582 supported on TSM 5.2.2 AIX ? Hi List ! I just wanted to assure that the IBM 3582 (SCSI)-Library is supported under TSM 5.2.2 (AIX) because "Supported Devices" on IBM-Website tells me: IBM 3582 Ultrium ScalableAIX HPUXSUN WIN The IBM device driver is required. 2 Drives 24 Slots 5.1.6.5 5.1.6.5 5.1.6.5 5.1.6.5 Does this mean that said library is ONLY supported under 5.1.6.5 or is it supported FROM 5.1.6.5 ON ? Thanks for your support ! Sascha Askani
Re: 3582 supported on TSM 5.2.2 AIX ?
Daniel, I just read your message. We have two 3575s, an L12 and an L18. Will they still work properly after we go to TSM 5.2? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. Daniel Sparrman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 07/05/2004 06:30 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: 3582 supported on TSM 5.2.2 AIX ? Hi Sascha It means from, so you shouldnt have any problems using your 3582 under TSM 5.2.2.2. The only tape libraries from IBM that has gone out of support is the 3575-series of libraries. Notice that you will have to download and install the IBM Atape device driver, which you can download from ftp://ftp.software.ibm.com/storage/devdrvr/AIX. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 TÄBY Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Sascha Askani <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2004-07-05 13:18 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject 3582 supported on TSM 5.2.2 AIX ? Hi List ! I just wanted to assure that the IBM 3582 (SCSI)-Library is supported under TSM 5.2.2 (AIX) because "Supported Devices" on IBM-Website tells me: IBM 3582 Ultrium ScalableAIX HPUXSUN WIN The IBM device driver is required. 2 Drives 24 Slots 5.1.6.5 5.1.6.5 5.1.6.5 5.1.6.5 Does this mean that said library is ONLY supported under 5.1.6.5 or is it supported FROM 5.1.6.5 ON ? Thanks for your support ! Sascha Askani
Re: Tier'ed library
Milton, Thanks VERY much for that info. That was exactly what I was looking for. Also, "Please note that I originally posted this to Tab instead of the list because I did not want it to seem that I was using the list to promote Sepaton." To the list: Milton is correct, but I wanted to query the forum with my "why VTL" question. Thanks again to all. Tab "Johnson, Milton" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06/16/2004 10:24 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Tier'ed library Tab, We've asked the same thing and came to the following points: 1) The $/TB is about as cheap as you can get. 2) With a VTL you can do LAN free backups. 3) To create an equiv Primary StgPool using sequential-access FILE volumes you would have to create a 200TB file system. Even using JFS2, I'm not sure you would get the same throughput as with a VTL. 4) Sepaton claims that by second quarter 2005, they will also have compression which would increase the VTL's "usable capacity". AIX does not offer a compressed JFS2 filesystem, and if it did it would have to have a serious impact on performance. 5) A tape library can be shared between systems which may/may not be relevant to you. 6) We could not think of a "technical" advantage that favored using sequential-access FILE volumes. The biggest hurtle is changing your mind set to allow the use of disks versus tape. We have come to the following conclusions: 1) If RAID-5 is that unreliable then why are we using it for our on-line databases? 2) We will not be a "tape free" environment, we would just be replacing our on-site tapes with disks. The amount of time when a backup is on disks only is very short. 3) The VTL costs are low enough so that we can have a "mirrored on-site tape pool". The mirror would be in another building and TSM would simultaneously write the backup to both stgpools. This would give a level of protection that would be very costly reproduce using physical tapes. The fact that IBM provides the service for the Sepaton VTL is an added plus in our shop. Please note that I originally posted this to Tab instead of the list because I did not want it to seem that I was using the list to promote Sepaton. H. Milton Johnson -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier Sent: Wednesday, June 16, 2004 8:48 AM To: [EMAIL PROTECTED] Subject: Re: Tier'ed library Milton, Thanks for the info. I briefly looked at Sepaton, but I had no idea they were that inexpensive. I will probably give them a second look. But one thing that I'm struggling with is "why a VTL?" Between random-access DISK volumes and sequential-access FILE volumes what does a VTL buy me that I couldn't implement using those two volume types in TSM? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Johnson, Milton" <[EMAIL PROTECTED]> 06/15/2004 03:13 PM To: "Tab Trepagnier" <[EMAIL PROTECTED]> cc: Subject:Tier'ed library Tab, We are faced with the same options and are seriously looking at Virtual Tape Libraries (VTL), an appliance that is physically a large SATA Raid Array but presents itself to TSM as a tape library. The product we are looking at is the Sepaton S2100-ES (www.sepaton.com). The things we like include: 1) It's TSM certified, meaning that it has passed the same certification the "real" tape libraries passed. 2) Cheap. We have been quoted $30K (USD) for the first 3TB and $18K (USD) for each additional 3TB. 3) Modular: Purchase the first 3Tb then expand in 3TB increments up to 200TB. After that you purchase another VTL. 4) Performance: Since it's disk based it's very fast, up to 1.6 TB/hour. Since the "tape drives" are virtual tape drives you can configure a tape library to have 200 tape drives, eliminating the tape drive bottleneck. "Tape mounts" happen instantly. 5) Because of the high performance and large number of available virtual tape drives, you should be able to reclaim the virtual tapes when they are only 25% reclaimable, instead of waiting until they are 50% reclaimable. This should allow much more efficient usage of the "tape space". We will just use our present 3494 ATL to cut off-site tapes. We haven't implemented it yet, but we are actively pursuing it. Our contact is: David Littman The More Group 47 East Grove Street Middleboro, MA 02346 [EMAIL PROTECTED] 508-946-2255 x19 H. Milton Johnson
Re: Tier'ed library
Milton, Thanks for the info. I briefly looked at Sepaton, but I had no idea they were that inexpensive. I will probably give them a second look. But one thing that I'm struggling with is "why a VTL?" Between random-access DISK volumes and sequential-access FILE volumes what does a VTL buy me that I couldn't implement using those two volume types in TSM? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Johnson, Milton" <[EMAIL PROTECTED]> 06/15/2004 03:13 PM To: "Tab Trepagnier" <[EMAIL PROTECTED]> cc: Subject:Tier'ed library Tab, We are faced with the same options and are seriously looking at Virtual Tape Libraries (VTL), an appliance that is physically a large SATA Raid Array but presents itself to TSM as a tape library. The product we are looking at is the Sepaton S2100-ES (www.sepaton.com). The things we like include: 1) It's TSM certified, meaning that it has passed the same certification the "real" tape libraries passed. 2) Cheap. We have been quoted $30K (USD) for the first 3TB and $18K (USD) for each additional 3TB. 3) Modular: Purchase the first 3Tb then expand in 3TB increments up to 200TB. After that you purchase another VTL. 4) Performance: Since it's disk based it's very fast, up to 1.6 TB/hour. Since the "tape drives" are virtual tape drives you can configure a tape library to have 200 tape drives, eliminating the tape drive bottleneck. "Tape mounts" happen instantly. 5) Because of the high performance and large number of available virtual tape drives, you should be able to reclaim the virtual tapes when they are only 25% reclaimable, instead of waiting until they are 50% reclaimable. This should allow much more efficient usage of the "tape space". We will just use our present 3494 ATL to cut off-site tapes. We haven't implemented it yet, but we are actively pursuing it. Our contact is: David Littman The More Group 47 East Grove Street Middleboro, MA 02346 [EMAIL PROTECTED] 508-946-2255 x19 H. Milton Johnson
Tier'ed library
TSM Server 5.1.9.0 on AIX 5.2 ML-2 TSM Server 5.2 media on hand We have outgrown our 3583 and 3575s, so I'm looking for a new tape library. At first I though my only choices were another standalone library like the 3583 or go with a frame system like the 3584. I have problems with both approaches. The standalone library, while cheaper, means that in 2-3 years I will have filled up yet another library now destined to collect dust in a corner. Since ADSM 2 six years ago we have use 10 different libraries or autoloaders on our system. Five of them are still in service. That is ridiculous. The frame system is just too expensive for our little company. We've obtained quotes for four and six drive configurations using LVDS and FC, and the price range is $125K - $180K. That's a LOT of money to us. So I'm thinking that a standalone library that can be expanded in tiers would be an effective way to "split the difference." Start smaller with one tier, and simply add a tier once we've outgrown it. I'm thinking four LTO-2 drives using LVDS connectivity to start. Initial *real* capacity should be about 10 TB. It should accept at least two additional tiers before maxing out. It must be supported by some variant of TSM 5.x. What has been the experience of forum users with libraries of that type? Do you have any brand/model recommendations? Models to avoid? Thanks in advance. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Reclamation data loss scenario
Richard, You're right, of course, but in this case Bill was trying to balance risk of corrupted primary tapes vs. shortage of media. I sometimes find myself in the same situation. My recommendation was relative to that balance point. If you have the luxury of lots of tapes and library capacity, you can of course set the reuse delay for as long as you'd like. You're right about tape. I have thanked IBM several times in this forum for the idea of the copypool. It has saved us on at least three different occasions. My wife's company uses a different backup product and local drives that write one copy of each backup. She longs for TSM's functionality. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06/10/2004 06:49 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Reclamation data loss scenario >You really only need to set the reuse delay long enough to ensure that you >have at least one good DB backup before reusing the volume. ... That reminds me of the scene in The Court Jester where a knight pushes Danny Kaye out of the spot where lightning is about to strike. :-)) Our reality is that we don't know where lightning is about to strike. You don't know that a tape and its contained data are actually good until you really need it. That's why we increase the odds by making copy storage pool tapes, and why one really needs to keep multiple generations of DB backup tapes and a Reusedelay long enough to cover all of them. Tape is tape, operators are operators, and the random elements of this universe jump out of dark recesses to surprise and humble us when we believe we've thought of everything. Be cautious, and increase your odds. Richard Sims
Re: Reclamation data loss scenario
Bill, You really only need to set the reuse delay long enough to ensure that you have at least one good DB backup before reusing the volume. That's why all of my onsite tapes carry a 2-day reuse delay. Being able to set a fractional amount would be ideal (we really only need about 1.25), but the feature only supports integers. The idea is that if you have to roll back to your NEWEST DB backup, everything is where TSM expects to find it. If you have to go back farther than that, then you're effectively in DR mode, and you declare your primary tapes "destroyed" and restore the volumes; as has been mentioned in the forum already. Tab Trepagnier TSM Administrator Laitram, L.L.C. Bill Mansfield <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06/09/2004 07:02 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Reclamation data loss scenario We were documenting some TSM server recovery scenarios the other day, and came up with one I haven't seen discussed before. Here's the scenario: Client backups finish, storage pool backups finish, TSM DB backup finishes, prepare run. Expiration runs. Primary tapepool reclamation reclaims tapes A and B, moving content to tape C (was scratch). Diskpool migration runs, starts moving data to tapepool tapes A and B. DISK FAILURE wipes out database and log (but not storage pools). Get new disk, restore server from TSM DB backup tape. At this point everything looks ok, but I actually have two "corrupt" tapepool tapes (A and B), and I'm not too sure the diskpool is any good either. The question is, what do we need to put in the recovery procedure to handle this? I can probably prevent it by setting reusedelay on the tapepool, but we're short on tape slots most of the time, and letting the reclaimed tapes pend until the oldest DB backup expires like we do our copypool tapes would overflow the library. I know I can audit and recover the tapes from the copypool, but the problem is I have hundreds of tapes, and insufficient time and tape drives to audit them all, and no sure way to tell which might need auditing. BTW, we've taken steps to better protect the TSM DB and Log disk, but this scenario lingers like a bad smell. Thanks in advance! Bill Mansfield
Re: Spam filters
Charlie, Thanks for the tip. I did that a couple of months ago. That eliminated *most* of the false positives from this forum, but not all of them. It still intercepts the rare message for whatever reason. Tab Charlie Hurtubise <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06/08/2004 01:08 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Spam filters Hi, One of my 234 duties, Tivoli being one of them, is the TrendMicro Virus & Spam filter on our firewall. These products allow you to build "white lists" (in our case Archive) any e-mail by from address. So I have placed all our clients and vendors etc, that allows ANY e-mail in from them. I added this newsgroup too, so no problems at my end. Allows for freedom of speech, so to say, and eliminates false-positives. Update your spam filters white list to include From: @vm.marist.edu Charlie Hurtubise Tecsys Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Tab Trepagnier Sent: Tuesday, June 08, 2004 10:05 AM To: [EMAIL PROTECTED] Subject: Spam filters Just a head's up to list participants. Our company like many uses a spam filter service to manage our email traffic. If you include anything in your message to the list that might be interpreted as sex-related or excessively commercial, there is a good chance that list members won't receive it. For example, over the last couple of days there has been a message thread whose subject included multiple "x" characters. Since in the West that is code for sex, our spam filter intercepted the original message and every reply. I'm sure we're not the only ones using such a service, so a little more thought put into what you actually write might help ensure that list participants actually receive your message. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Spam filters
Just a head's up to list participants. Our company like many uses a spam filter service to manage our email traffic. If you include anything in your message to the list that might be interpreted as sex-related or excessively commercial, there is a good chance that list members won't receive it. For example, over the last couple of days there has been a message thread whose subject included multiple "x" characters. Since in the West that is code for sex, our spam filter intercepted the original message and every reply. I'm sure we're not the only ones using such a service, so a little more thought put into what you actually write might help ensure that list participants actually receive your message. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Moving data targets
Server: TSM 5.1.9.0 on AIX 5.2 ML-2 Clients: TSM 5.1.7.0 on Windows 2000 SP3 Several months ago I reconfigured our TSM system to delay the purchase of yet another tape library, making liberal use of the MigDel parameter. Now, when the "front end" resources fill up, clients are not redirected to subsequent storage pools despite the configuration that says that they should. Specifically, the backup data path now is like this: Client -> disk -> 3575 -> LTO -> DLT -> shelf Because "disk" and "3575" are of limited capacity, I have assigned MaxSize and MigDel on both. Disk = 60 MB max size, MigDel = 2 days, MigCont = Yes, NextStg=3575 3575 = 2GB max size, MigDel = 14 days, MigCont = No, NextStg=LTO LTO accepts everything In practice, if the 3575 fills up, the client sessions "FAIL" rather than shift to the LTO. Yet, if the disk fills up, the client sessions do shift to the 3575. This is making it a real challenge to maintain reliable system operation until we decide what we want to do regarding storage expansion. Is this normal? Or have I encountered a bug? Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: TSM and LTO Throughput
Jack, I have a 3583-L72 with four LTO-1 drives connected via HVDS SCSI to a pSeries 6H1. I have two drives per SCSI chain. Depending on the type of data, I see 15 MB/s per drive consistently, and with highly-compressible data, peaks as high as 40 MB/s. That performance is perfectly adequate for our little company. One trick I implemented back when the library was collocated, was to wire the drives "odd & even". That is, drives 1 and 3 were on one chain, and drives 2 and 4 were on the other. If you watch how TSM handles reclamation on a collocated storage pool, you'll see the wisdom of that configuration. On non-collocated pools it doesn't matter, and my other three libraries are wired "high & low"; that is, drives 1 and 2 on one chain and drives 3 and 4 on the other. Tab Trepagnier TSM Administrator Laitram, L.L.C. "Coats, Jack" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/23/2004 03:38 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:TSM and LTO Throughput Ok, I have a winders 2K box with 6 SCSI-attached LTO-1's with TSM 4.2.3.1 but it has a dual xenon 1.7G set of processors, and 1G of ram with 2G of swap space. The LTO's are in a IBM 3483-L18. There are two LTO's on each of 3 separate SCSI chains (they are 160 adapters, de-tuned to 80 in the adapter BIOS, because the LTO's I have won't work at 160). But even at that two LTO-1's should not outpace a 80MB/Sec SCSI adapter. What kind of throughput are you folks seeing with SCSI attached LTO-1's? I am trying some timeing doing migrations right now. If others are interested I will report back. Why am I asking? I think I have some performance issues, just getting data to/from tape, and can't seem to figure out where to look to find answers! You guys being a 'similar user base' have some similar stats, that could tell me if I am working 'as designed' or far behind the power curve. TIA ... Jack
Re: Please help me NOT migrate
I just caught up on this thread. I've done LOTS of exporting and importing. We just exported our main file servers, Oracle, and Lotus Domino servers to create a static snapshot for legal reasons. Using TWO DLT-8000 drives writing two export jobs in parallel, it took two WEEKS to write 7-3/4 TB to 132 DLTs, with DLT drives that average 8 MB/s throughput. It isn't just the data write time. For big exports like that you have to allow for tape exchanges (our "big" library holds 39 tapes); tape accumulation (I had a stack of DLTs a foot high on my desk); the influence of regular TSM tasks on your export jobs (volume/drive/bus contention); shortage of media and *labels*; and so forth. I made it clear to the requester that the import would be performed on a rented AIX server using a rented DLT library and the data would be restored to a rented WinTel server for examination. Exports work - but large ones are not trivial. Tab Trepagnier TSM Administrator Laitram, L.L.C. Ted Byrne <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/20/2004 12:45 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Please help me NOT migrate >My recommendation is to set up a new Solaris server and slowly put new clients >on it. Then over time we will move all clients to the new server. But I >know it won't fly because it will entail buying a new tape library. Eliza, Would it be feasible to share the 3494 between servers during the transition if it comes to that? I've never done any significant export/import processing, but I can't imagine that given the total downtime to do a one-shot cutover would be acceptable given the number of nodes and volume of data that you're dealing with. My gut feeling is that the downtime for the cutover would be nothing short of horrific, but that's really a hunch on my part. Ted Ted Byrne Blacksburg, VA
Re: Occupancy of a backupset
Ray, I "point and shoot" my way through MS Query, but this is the Select command submitted to TSM: 04/16/2004 13:08:38 ANR2017I Administrator USER issued command: DEFINE CURSOR C37e23b8 SQL="SELECT OCCUPANCY.NODE_NAME, OCCUPANCY.FILESPACE_NAME, OCCUPANCY.STGPOOL_NAME, OCCUPANCY.NUM_FILES, OCCUPANCY.PHYSICAL_MB, FROM OCCUPANCY OCCUPANCY.LOGICAL_MB, OCCUPANCY.TYPE WHERE (OCCUPANCY.STGPOOL_NAME='BACKUPDISK')" In that case I'm obtaining the occupancy of my disk pool "backupdisk". The results get inserted into cell A1 of the Excel spreadsheet. I sum the data columns and enter those sums into a summary spreadsheet that graphs the results. I have a separate sheet and query for each storage pool, whereby MS Query inserts a different storage pool name after the WHERE clause. That way I can chart the growth of data in our TSM system with about 15 minutes of effort for each update. I do this weekly to compare apples to apples since our TSM system runs with a weekly maintenance schedule. Tab Trepagnier TSM Administrator Laitram, L.L.C. Ray Louvier <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/17/2004 05:22 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Occupancy of a backupset Tab, what is the select command you use for occupancy. -Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Tab Trepagnier Sent: Friday, April 16, 2004 12:36 PM To: [EMAIL PROTECTED] Subject: Occupancy of a backupset TSM 5.1.8.0 on AIX Is there a way to easily determine the size of a backupset? I track tape occupancy weekly to chart growth of our TSM system. Each Excel spreadsheet has an embedded "select from occupancy..." query. That allows me to determine how much data I have and where it is in about 5 minutes. But data in a backupset does not show up under any "occupancy" measure that I'm aware of. As I shift more archives to backupsets, I'd like some way to show that the reduction in archive space isn't real - that data is just changing form to backupsets. That way I could count the backupset data along with all the other data I'm tracking. TIA Tab Trepagnier TSM Administrator Laitram, L.L.C.
Occupancy of a backupset
TSM 5.1.8.0 on AIX Is there a way to easily determine the size of a backupset? I track tape occupancy weekly to chart growth of our TSM system. Each Excel spreadsheet has an embedded "select from occupancy..." query. That allows me to determine how much data I have and where it is in about 5 minutes. But data in a backupset does not show up under any "occupancy" measure that I'm aware of. As I shift more archives to backupsets, I'd like some way to show that the reduction in archive space isn't real - that data is just changing form to backupsets. That way I could count the backupset data along with all the other data I'm tracking. TIA Tab Trepagnier TSM Administrator Laitram, L.L.C.
Delete obsolete directories only?
TSM Server 5.1.8.0 on AIX; TSM Client 5.1.6.0 on Windows 2000 I have a situation where over time, the location of data on our network has moved from server to server. In many cases we moved the identity of the first server to the second server, but the data paths were not duplicated exactly. For example, \\server_name\d$\current_root_path\... \\*\*\old_root_path\... where "current_root_path" and "old_root_path" are peers under the same "d$" parent. Because the "old_root_path" became invalid on the first backup of the new server, all the data under it was marked inactive by TSM. No problem there. Once the RetOnly duration elapsed, all the FILES were purged from that path. Again, no problem there. But the directories were retained, probably because they were bound to "no limit" permanent management classes prior to our implementing DIRMC controls. Meaning those directories will live for the duration of the server's identity or our TSM system, whichever ends first. Those duplicate paths confuse our Help Desk. I would like to delete just the contents under "old_root_path" since there are no files under that path. But because both root paths are under the same filespace, I can't delete the filespace. I turned on the permission "node can delete backups" but that still didn't let me kill that directory tree. So, is there a way to kill the directory tree under "old_root_path" other than killing the entire filespace? TIA Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Assign management class to UNC path
Andy, Thanks for that info. I will apply 5.1.6.9 at first convenient opportunity. Tab
Re: Assign management class to UNC path
TNTFS No 17,312.2 11.6 \c$ CORP-FS4SYSTEM 3 WinNTSYSTEM No 0.0 0.0 OBJECT CORP-FS4\\corp-fs4-4 WinNTNTFS Yes486,239. 67.7 \molds$ 5 tsm: ADSTAR> --- END FILESPACE LIST - Andrew Raibeck <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/11/2004 09:53 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Assign management class to UNC path It would certainly help if you could provide some more detail specific to the problem you are seeing. For starters: - *complete* Output from "dsmc q inclexcl" (make sure to use same options file and node name as scheduler) - Copy of dsm.opt file (ditto) - Copy of output from admin command "q clo" if the node has a client options set associated with it. - Messages you see in dsmsched.log and dsmerror.log when the scheduler tries to start. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Tab Trepagnier <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/11/2004 08:38 Please respond to "ADSM: Dist Stor Manager" To [EMAIL PROTECTED] cc Subject Assign management class to UNC path Server: TSM 5.1.8.0 on AIX 4.3.3 Client: TSM 5.1.6.0 on Windows 2000 SP3 I am trying to assign a non-default management class to a UNC path of the form "\\server\share$". The UNC path is listed in a DOMAIN statement per instructions of IBM SW Support. Ordinary incremental backups work fine. Attempts to add that path as an INCLUDE in the OPT file with the management class appended cause the Windows TSM Scheduler service to fail with ANS1036S "Invalid option...". I've verified the class name. I've tried every syntax option I can think of, including: \\server\share$ \\server\share$\* \\server\share$\...\* share$ So how to I assign a non-default management class to that UNC share? Note that the "share$" is effectively a "virtual mount point" for Windows. I use it for BackupSet generation. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Assign management class to UNC path
Server: TSM 5.1.8.0 on AIX 4.3.3 Client: TSM 5.1.6.0 on Windows 2000 SP3 I am trying to assign a non-default management class to a UNC path of the form "\\server\share$". The UNC path is listed in a DOMAIN statement per instructions of IBM SW Support. Ordinary incremental backups work fine. Attempts to add that path as an INCLUDE in the OPT file with the management class appended cause the Windows TSM Scheduler service to fail with ANS1036S "Invalid option...". I've verified the class name. I've tried every syntax option I can think of, including: \\server\share$ \\server\share$\* \\server\share$\...\* share$ So how to I assign a non-default management class to that UNC share? Note that the "share$" is effectively a "virtual mount point" for Windows. I use it for BackupSet generation. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: TSM best practices manual?
Wanda, Thanks very much for the suggestions. In answer to your questions: 1. I know I have compression operating on the drives because our average tape capacity is 1.6 X uncompressed capacity on all three media. 2. Most of what we back up is server data; a little bit is OS, etc, but not much. We're a Notes and Oracle shop and we have a LOT of data from both systems. We also design and manufacture our own products, and our engineers routinely generate 100MB+ CAD files. 3. We keep five copies of user-created data, and two copies of everything else. Design data is also archived but that isn't relevant to this discussion. 4. True, but I already have FIVE libraries; I am trying to avoid buying a sixth. This is what I think I'm going to do. At present we keep everything except permanent archives online fulltime since we don't really have an "operator". We have two parallel data paths: "small clients" going to a 3575, and "large clients" going to the 3583. I'm going to recombine those paths into a single path and make liberal use of the Migration Delay feature. The idea is for the incoming data to travel: Disk --> 3575 --> 3583 --> MSL DLT --> shelf. The idea is to have data 1-2 days old on disk (radical!), data 2-10 days old on fast-access 3570, data 10-180 days old on LTO, and data older than 6-12 months on the shelf. The little MSL retains nothing but is instead just a portal. As for a "best practices" guide, I've begun browsing the TSM 5.2 Implementation Guide to see if that provides the info I'm looking for. I'm also browsing my training handout from the ADSM 3.1 Advanced Implementation course. Thanks again for the suggestions. Tab "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/28/2004 12:44 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: TSM best practices manual? Tab, I'm not sure this is an issue of TSM design - if your libraries are out of capacity in terms of SLOTS, rather than throughput, you just have "too much" data. That either means you are 1) not compressing the data as much as you can, or 2) backing up things you don't need to 3) keeping data longer/more copies than you need to 4) really in need of additional library space For 1), it's a matter of checking to make sure that your drives do have compression turned on. If you can't compress at the drive level, turn it on at the client level. For 2-4, I don't know any magic/automatic way of figuring it out. Here's what I do: dsmadmc -id=x -password=yyy -commadelimited "select CURRENT_DATE as DATE,'SPACEAUDIT',node_name as node, backup_mb, backup_copy_mb,archive_mb, archive_copy_mb from auditocc"`; Suck that into a spreadsheet and look to see which clients are taking up the most space on the server side. Then go look in detail at the management classes and exclude lists associated with the "hoggish" clients, and see what you can find out about the copies they are keeping. - Are you keeping copies of EVERYTHING on the client for a zillion versions, rather than just the important data files? - for Windows 2000, are you keeping more copies of the SYSTEM OBJECT than would likely be used? - Look at their dsmsched.log files and see what is actually being backed up. - Be suspicious of TDP clients not deleteing copies they are supposed to. (For example, if they are supposedly keeping 10 versions of a 10 GB data base, but the SELECT shows 500 GB on the server, there's something wrong.) - If it's user/group space, are there lots of .mp3 files? (exclude 'em with a clientoptionset) - Make sure you aren't backing up TEMP directories etc.. I run the query monthly and save the data so that I can compare from one month to the next. That tells me which clients are GROWING the fastest. Those are the ones to attack. With luck, you will find some things that you can do that will extend your library life a while. Maybe not. But at least you will be able to tell your management WHY you are running out of space. Hope that helps. Wanda Prather Johns Hopkins University Applied Physics Laboratory 443-778-8769 "Intelligence has much less practical application than you'd think" - Dilbert/Scott Adams -Original Message- From: Tab Trepagnier [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 10:11 AM To: [EMAIL PROTECTED] Subject: TSM best practices manual? TSM 5.1.7 on AIX 4.3.3 9 TB online, total of 24 TB managed. Our TSM tape libraries are nearing their capacity. Currently we're running a fairly simple TSM system, using little of the new functionality introduced since V 3.1. We backup to onsite tape and make copies to a copypool whose
TSM best practices manual?
TSM 5.1.7 on AIX 4.3.3 9 TB online, total of 24 TB managed. Our TSM tape libraries are nearing their capacity. Currently we're running a fairly simple TSM system, using little of the new functionality introduced since V 3.1. We backup to onsite tape and make copies to a copypool whose tapes are vaulted offsite. That's pretty much the entire system. Our current tape library fleet consists of a 3583-L72 (LTO-1), two 3575s (and L12 and an L18), an HP SureStore 4/40 (DLT 8000), and an HPaq MSL5026 (DLT 8000). Before we spend $60-80K - or more - on another tape library, I'd like to review the system's architecture to see if there is another path we can go. I've been through the TSM Admin Guide and Technical Guide, but what I'm really looking for is a description of current best practices regarding TSM system design. Is there another document that would present that info better? TIA Tab Trepagnier TSM Administrator Laitram, L.L.C.
Re: Backup of all-local -systemonject
"First, I recommend you do NOT use 5.1.6.0 on Win2K. There is a bug in registry restore." Wanda, thanks for the heads up. We have 5.1.6.0 on ALL 40 of our Win 2K servers. Looks like I have some updates in my immediate future. Thanks again! Tab Trepagnier TSM Administrator Laitram, L.L.C. "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/09/2004 09:48 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Backup of all-local -systemonject Rene, First, I recommend you do NOT use 5.1.6.0 on Win2K. There is a bug in registry restore. You should be at least 5.1.6.2 (you can see the APAR # in the README for 5.1.6.2). Second, "Domain all-local -systemobject" Works fine for me at 5.1.6.2. Did you restart the scheduler after making this change? -Original Message- From: Lambelet,Rene,VEVEY,GL-CSC [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 10:21 AM To: [EMAIL PROTECTED] Subject: Re: Backup of all-local -systemonject Hi, we have a TSM client for W2K, 5.1.6.0. TSM server is 5.1.5.4 on AIX. rene -Original Message- From: Adams, Matt (US - Hermitage) [mailto:[EMAIL PROTECTED] Sent: Friday,9. January 2004 16:13 To: [EMAIL PROTECTED] Subject: Re: Backup of all-local -systemonject What version of the client? Matt Adams Information Technology Services (ITS) 615-882.6861 [EMAIL PROTECTED] Deloitte. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lambelet,Rene,VEVEY,GL-CSC Sent: Friday, January 09, 2004 9:09 AM To: [EMAIL PROTECTED] Subject: Backup of all-local -systemonject Hi TSM'ers for W2K, could you help me, I'd like to backup all local volumes like C., D: etc. BUT without the system state ! We did not succceed with "Domain all-local -systemobject" Thanks in advance for any clue, René LAMBELET NESTEC SA GLOBE - Global Business Excellence Central Support Center SD/ESN Av. Nestlé 55 CH-1800 Vevey (Switzerland) tél +41 (0)21 924 35 43 fax +41 (0)21 924 13 69 local K4-104 mailto:[EMAIL PROTECTED] This message is intended only for the use of the addressee and may contain information that is privileged and confidential. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Re: moving a primary sequential access storage pool to another library
Joel / Doug, TSM allows you to do that without error. But your old data is accessible only if the media types match. I just updated a DLT device class to point to a 3575 Magstar library and the command succeeded. But one wonders how TSM would read the existing DLTs in the 3575. The original post didn't mention media, but we use that very technique with our offsite tape libraries. I have a two-drive DLT library that is an installed spare for the main four-drive DLT library. Our copypool is defined on the four-drive library. To use the two-drive as the host for the copypool, I just do the UPDATE DEVCLASS command and point the device class definition to the two-drive library. Everything works as though nothing happened at the storage pool level. Because the media match on both libraries, tapes written in one can be checked out and checked back into the other. Works AOK. We've tested it. All of this is why I don't build any "intelligence" into device class names. Ours are "DEV01", "DEV02", etc. I don't include any model numbers, media types, etc. Hope this helps. Tab Trepagnier TSM Administrator Laitram, L.L.C. Doug Thorneycroft <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 01/06/2004 09:44 AM Please respond to dthorneycroft To: [EMAIL PROTECTED] cc: Subject:Re: moving a primary sequential access storage pool to another library You can use the update the device class to use the new library. Update devclass devtype= format= library= mountlimit=<#> Doug Thorneycroft County Sanitation Districts of Los Angeles County (562) 699-7411 Ext. 1058 FAX (562) 699-6756 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Joel Fuhrman Sent: Monday, January 05, 2004 4:09 PM To: [EMAIL PROTECTED] Subject: moving a primary sequential access storage pool to another library Is it possible to move a primary sequential access storage pool from one library to another library with out having to copy the data? If so, how? I need to move my primary sequential access storage pools from one library to another. If I could update the device class name for the storage pool my problem would be resolved but the device_class_name is not an UPDATE STGPOOL option. Is it possible to delete the sequential access storage pool device_class_name and then re-define the same device_class_name while specifying the other library without corrupting the database?
Re: Media error
Desale, Are you sure there isn't a tape stuck in a drive or in the picker? The last entry from the log shows "Changer failure". Our 3583 experienced numerous failures, mostly due to the picker not grabbing the tape properly and leaving it stuck in the drive. At that point everything is out of sync - the library, TSM, etc. You should take the library offline, open the door, and look inside. Ensure that what TSM thinks is happening in the library matches its physical state. There is an engineering change that adds some small springs to the LTO drives to improve tape ejection. Also, the latest firmware for the library tells the picker to extend farther when grabbing a tape to help prevent "drops". The 3583 does not have a window through which to examine the inner workings of the library, so you have to take it offline and open the door to see what's happened. Because of that we've removed the screws that hold the top panel on the library. Now, if we have to look inside it, we just remove that panel and peek in. This is not recommended if you live in an area prone to earthquakes. We don't. Tab Trepagnier TSM Administrator Laitram LLC Desalegne Guangul <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 12/11/2003 02:55 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Media error Hi Everyone, I'm new to TSM and I need any help I can get from you. I 'm getting the following errors on TSM server v 5.1.6 and LTO Library 3583. I search the TSM web sites but couldn't find any help on the error below. By the way which Appendix D is the error refer to below? 12/02/2003 21:11:14 ANR8944E Hardware or media error on drive DR1 (mt2.1.0.4) (OP=LOCATE, Error Number=23, CC=0, KEY=03, ASC=14, ASCQ=00, SENSE=70.00.03.00.00.00.00.1C.00.00.00.00.14.00- .07.00.20.84.FF.FF.00.03.20.20.20.20.20.20.20.19.00.00.0- 9.FC.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.- 00.00.00.00.00.00.00.00.00.00.00.00.00.02.00.00.00.00.00- .00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.CA.9A.3B.0- 0.00.00.00.00.00.00.00, Description=An undetermined error has occurred). Refer to Appendix D in the 'Messages' manual for recommended action. 12/02/2003 21:11:14 ANR8359E Media fault detected on LTO volume 644AENL1 in drive DR1 (mt2.1.0.4) of library LTOLIB. 12/05/2003 06:00:52 ANR1401W Mount request denied for volume 648AENL1 - mount failed. 12/05/2003 06:00:52 ANR1021W Migration process 8 terminated for storage pool DISKPOOL - storage media inaccessible. 12/05/2003 06:00:52 ANR0985I Process 8 for MIGRATION running in the BACKGROUND completed with completion state FAILURE at 06:00:52. 12/05/2003 06:00:52 ANR1002I Migration for storage pool DISKPOOL will be retried in 60 seconds. 12/05/2003 06:00:57 ANR8943E Hardware or media error on library LTOLIB (OP=8401C058, CC=304, KEY=04, ASC=40, ASCQ=C0, SENSE=70.00.04.00.00.00.00.0A.00.00.00.00.40.C0.81.00.00- .00., Description=Changer failure). Refer to Appendix D in the 'Messages' manual for recommended action. 12/05/2003 06:00:59 ANR8381E LTO volume 657AENL1 could not be mounted in drive DR1 (mt2.1.0.4). 12/05/2003 06:00:59 ANR1401W Mount request denied for volume 657AENL1 - mount failed. Thanks! Desale
Re: Windows Scripts
Steve, Don't limit yourself to command scripts. Look into VB Script. The combination of VB Script (VBS) and Windows Script Host (WSH) gives you access to a much more "precise" scripting environment along with access to other Windows script interfaces such as ADO (ActiveX Data Objects), CDO (Collaborative Data Objects), etc., plus the COM components of any applications installed on your PC such as Internet Explorer or MS Office apps. All of that is unavailable via the standard Windows batch interface. I've been a big batch file writer since DOS 3.0, but I've spent the last year or so learning VBS / WSH, and the combination feels "liberating." I suggest you explore it before committing to batch files. Tab Trepagnier TSM Administrator Laitram LLC Steve Roder <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 12/11/2003 08:11 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Windows Scripts Hi All, Anyone know of a good repository of native win2k cmd scripts for doing various TSM functions? I am particularly interested in a script that checks for full copypool volumes that are inside a library, issues checkout commands (and does the reply), and updates the tapes' access to offsite. I have written this script in perl on AIX, but the Windows servers I help out with do not have perl installed, so .cmd files is what I am looking at for this. Any code, pointers, tips, reference sites would be greatly appreciated! Thanks, Steve Roder, University at Buffalo HOD Service Coordinator VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) TSM/ADSM Administrator UB DNS Team ([EMAIL PROTECTED] | (716)645-3564)
Re: Preventing re-backup of NT drive copied with scopy
Steven, Make sure that SCopy preserved the *inheritance* security properties. We've migrated Windows servers in the past using either SCopy or XCopy /O. On the target server, the files and folders had the correct permissions, but they were "applied" rather than "inherited". I'm not sure which tool caused that because we didn't discover it until much later. But that could be enough to provoke a full backup. Tab Trepagnier TSM Administrator Laitram LLC Steven Bridge <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 12/10/2003 08:29 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Preventing re-backup of NT drive copied with scopy A drive on an NT 4 fileserver which was mapped to a RAID unit containing about 120 GB of data has been copied to a new RAID unit with greater capacity. The data was copied using scopy using appropriate flags to preserve permissions and modification dates. The original drive letter was then re-assigned to the copy of the data. Unfortunately, it now looks like TSM ( client 5.1.0.1 , server 5.1.6.3 ) is backing up everything in the drive again. With a throughput of only about 1 GB an hour, it looks like it is going to take several days to complete. Is there anyway to persuade TSM that that it already has the data ? Is it because the drive itself has a new modification date that everything else underneath is seen as new ? +--+ Steven Bridge Systems Group, Information Systems, EISD University College London
Re: dsmsrvc.exe RAM usage
Bill, We use the TSM client service on several large Windows file servers. The primary factor that I know of that affects client memory usage is the size of the client aggregates. In other words, if you have TXNBYTELIMIT set very high, the TSM client must hold the files in memory while it builds the aggregate. On my servers, the idling service uses between 4 and 8 MB. During backups, especially when I had the TXNBYTELIMIT set to 128 MB, the real memory (the Windows "working set") was close to 160 MB. Luckily we have 768 MB in that machine! At this time I have a TXNBYTELIMIT of 48 MB set on all nodes. That seems a good compromise between client performance and memory usage. Tab Trepagnier TSM Administrator Laitram LLC William Rosette <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/09/2003 09:45 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: dsmsrvc.exe RAM usage Does anyone know why dsmsrvc.exe on the Win2000 boxes uses high RAM usage? Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD
