REDBOOK: Updated TSM Implementation Guide draft
A new draft version of the popular TSM Implementation Guide Redbook is now available for your enjoyment at http://www.redbooks.ibm.com/redpieces/abstracts/sg245416.html?Open , Charlotte Brooks Project Leader and Certified IT Specialist IBM TotalStorage Solutions, ITSO San Jose http://ibm.com/redbooks
Disk pool size limit
Is there a limit to how large a disk pool can be? This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you.
Re: Random Access Disk Pools
>> On Tue, 4 Apr 2006 21:30:57 +0200, Kurt Beyers <[EMAIL PROTECTED]> said: > What happens in the move data of a disk storage pool volume? Are the > aggregates moved instead of the files that they do contain? You can't reconstruct if a random-access volume is involved. RECONStruct Specifies whether to reconstruct file aggregates during data movement. Reconstruction removes empty space that has accumulated during deletion of logical files from an aggregate. This parameter is optional. If both the source and target storage pools are sequential access, the default value is YES. If either the source or target storage pool is random access, the default is NO. Possible values are: No Specifies that reconstruction of file aggregates is not performed during data movement. Yes Specifies that reconstruction of file aggregates is performed during data movement. You can only specify this option when both the source and the target storage pools are sequential-access. - Allen S. Rout
Re: Random Access Disk Pools
On Apr 4, 2006, at 3:31 PM, Andy Huebner wrote: "Show treads" will show you the thread table size and the number of active threads. ... The SHow commands are minimally documented, so what they report is not always clear. From what I've seen, the "Thread table size" value is the size of the table at the moment, not a fixed or maximum size. I would not infer anything further from the value. TSM is subject to OS limits, so depend upon those for max values. Richard Sims
Re: Random Access Disk Pools
"Show treads" will show you the thread table size and the number of active threads. Thread table size: 2944 Active threads: 1577 Our system stops accepting new connections at around 1850 active threads. The condition requires a restart of TSM to correct. TSM 5.2.2.4 AIX 5.1 M9 4 CPU with 4gig RAM Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Tuesday, April 04, 2006 10:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Let me ask again because I didn't get much feedback. How do we find the thread limit, and can people weigh in on whether they use big disk pools (50TB-200TB). The advantages/disadvantages of big disk pools versus devclass=file any gotchas either way. We are looking at buy a lot more disk and creating big diskpools to land data on and be the primary pool instead of tape. Thank in advance. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Monday, March 27, 2006 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We found the limit. There are some posts in this forum from the first of the year about the problem we ran into. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Monday, March 27, 2006 6:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We use random access pools, how do you know what your thread limit iswe've never had any issues with ours but we're thinking about adding a lot more. What's the biggest reason you do/don't use devclass=file over disk storage poolsarguments either way? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Friday, March 24, 2006 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Be careful with how many disk pool volumes you create. Each volume uses 1 thread, add this to all of the other threads in use, our TSM server would die at around 1800 active threads. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Friday, March 24, 2006 11:04 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Random Access Disk Pools I have heard in the past that random access disk pools can become fragmented and practically unusable after a while. I was wondering if anyone sees this in the real world? I posted the other day about managing predefined volumes in a file type devclass, and the only answer I got said they were using random access pools. I would MUCH rather have a random access pool, so if there is no problem with this, I will convert over to random access. Thanks for any input. TSM 5.3.2.3 on AIX 5.2.5 EMC Clarion Disk, 120 TB in 2TB LUN's Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. 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. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email. 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. 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 dis
Re: Random Access Disk Pools
Hi, What happens in the move data of a disk storage pool volume? Are the aggregates moved instead of the files that they do contain? And thus the lost space due to the fragmentation into the aggregates is not freed up? > If you're using DISK as a temporary holding pool, I'd expect > fragmentation to be irrelevant. For permanent storage, however, It'd > be huge. best regards, Kurt
Re: Random Access Disk Pools
>> On Tue, 4 Apr 2006 10:14:50 -0700, Andrew Carlson <[EMAIL PROTECTED]> said: > The speed of the random access disk pools is phenomenally better than > the file device class - not sure why though When you're writing to DISK pools, writes round-robin through the volumes. This is usually better for the underlying disk subsystem than lots of serial writes. (at least it's been so for all my disk subsystems). > It takes alot of time to predefine the volumes. We were finding it > took about 19 hours to predefine 2TB. We were able to run 8 of > those, so it ended up taking 19 hours to predefine 16TB, but that is > still a long time. I don't get the predefined volumes bit; don't see how it could be a win. My FILE strategy has been 10-20GB files, in profusion. This keeps individual operations sane in length. > My plan is to move data off of random access volumes on the weekends to > help prevent fragmentation. If you're using DISK as a temporary holding pool, I'd expect fragmentation to be irrelevant. For permanent storage, however, It'd be huge. - Allen S. Rout
AW: Random Access Disk Pools
Why don't you use random and sequential together? In our diskonly setup we use 3 types: 2% fibrechannel disk as primary pool with random access for daily backup sizelimit 2MByte 30% ATA disk as primary pool with random access volumes for backup no sizelimit migdelay=7days 68% ATA disk as primary pool with files device for migrationtarget of ATA Pool and for direct target of TDP agents and 100% ATA as copypool on remote site. (Copy is done as an extra step since we got very high CPU load) No problems since one year. Kind regards Stefan Holzwarth > -Ursprüngliche Nachricht- > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im > Auftrag von Andrew Carlson > Gesendet: Dienstag, 4. April 2006 19:15 > An: ADSM-L@VM.MARIST.EDU > Betreff: Re: Random Access Disk Pools > > Rod, > > After spending 4 weeks using file device class disk pools, I would say > use random access. Here is why: > > The speed of the random access disk pools is phenomenally better than > the file device class - not sure why though > > The volumes (from the presentation I just read from the other email) > are supposed to be picked based on filesystems with no volume > mounted. > What I found is the it selects them in collation order. This accessed > the volumes on one raid group, giving the worst performance of all. > After using a kludgy method to spread the data around, the performance > was better, but did not approach random access > > Small files were a problem in some cases. Since I was collocating, if > alot of small files were written to a volume (in this case, it was > moving my dirmc pool), there can be alot of wasted space. Apparently, > a block of 256K is written to disk no matter how much data is being > written. If alot of small files are written to a volume, space can be > wasted because the volume will fill before capacity is > reached (we were > using predefined volumes) > > It takes alot of time to predefine the volumes. We were finding it > took about 19 hours to predefine 2TB. We were able to run 8 of those, > so it ended up taking 19 hours to predefine 16TB, but that is still a > long time. > > Some portion of space is taken up by volumes that are not yet full > (with predefined volumes at least) in a file device class. > This is not > a worry with random access, but fragmented aggregates could > be a worry. > > My plan is to move data off of random access volumes on the > weekends to > help prevent fragmentation. > > If you have any other questions, please let me know. > > --- "Park, Rod" <[EMAIL PROTECTED]> wrote: > > > Let me ask again because I didn't get much feedback. How do we find > > the > > thread limit, and can people weigh in on whether they use big disk > > pools > > (50TB-200TB). The advantages/disadvantages of big disk pools versus > > devclass=file any gotchas either way. We are looking at buy a lot > > more > > disk and creating big diskpools to land data on and be the primary > > pool > > instead of tape. Thank in advance. > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf > > Of > > Andy Huebner > > Sent: Monday, March 27, 2006 11:43 AM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] Random Access Disk Pools > > > > We found the limit. There are some posts in this forum from the > > first > > of the year about the problem we ran into. > > > > Andy Huebner > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf > > Of > > Park, Rod > > Sent: Monday, March 27, 2006 6:45 AM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] Random Access Disk Pools > > > > We use random access pools, how do you know what your thread limit > > iswe've never had any issues with ours but we're thinking about > > adding a lot more. What's the biggest reason you do/don't use > > devclass=file over disk storage poolsarguments either way? > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf > > Of > > Andy Huebner > > Sent: Friday, March 24, 2006 3:37 PM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] Random Access Disk Pools > > > > Be careful with how many disk pool volumes you create. Each volume > > uses > > 1 thread, add this to all of the other threads in use, our > TSM server > > would die at around 1800 active threads. > > > > Andy Huebner > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf > > Of > > Andrew Carlson > > Sent: Friday, March 24, 2006 11:04 AM > > To: ADSM-L@VM.MARIST.EDU > > Subject: [ADSM-L] Random Access Disk Pools > > > > I have heard in the past that random access disk pools can become > > fragmented and practically unusable after a while. I was wondering > > if anyone sees this in the real world? I posted the other day about > > managing predefined volumes in a file type devclass, and the only >
Re: Data tape in limbo
At 01:49 PM 4/4/2006, David E Ehresman wrote: 'q libvol' output has no entries regarding the tape. An audit of the library succeeeds. 35S is physically in the library but can neither be checked in or checked out by TSM. If you can physically remove the tape volume from the physical library, using the library management interface, the following should work for you: remove tape from library - in a way that the library no longer knows about it. i.e., don't just reach in and pull it out, or it will remain in the library's internal inventory. checkout libvol ... checkl=no remove=no put the tape into the bulk I/O port checkin libvol ... search=bulk status=private -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Systems Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: Migrating to a Library Manager
>This can really accellerate experiments. Fortunely, I am able to experiment since the 3584 is new and not in production. So I've been able to set up a test environment to experiment with. After figuring out now to do this we get to do it on our production tsm servers with 3494 libraries. I'm taking advantage of new/expanded hardware to test this process before it goes into production. At the end, I'll have a shared 3494 (existing lib) and a shared 3584 (new, being used for this testing) between two library clients and a library manager. Thanks for the help . . . will let you know how it goes. Rick "Allen S. Rout" <[EMAIL PROTECTED]> Sent by: "ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager" cc <[EMAIL PROTECTED] .EDU> Subject Re: Migrating to a Library Manager 04/03/2006 08:10 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> >> On Mon, 3 Apr 2006 15:32:22 -0500, Bill Kelly <[EMAIL PROTECTED]> said: > 1) check the tapes out of tsm2t > 2) delete the library (and drives and paths) from tsm2t > 3) define the library (and drives and paths) in tsmlm2, and as a shared > library in tsm2t > 4) check the tapes in to tsmlm2. What he said; I've done this. Additional knob-polishing, lily-gilding, etc: Remember that you don't have to REMOVE the volumes on checkout, and that you don't have to check the label when you check them in. This can really accellerate experiments. Remember also that it's easy to get back to the state of "everything checked out, and library gone", so you can get it wrong several times, and ry again with very little cost. While this is an intimidating process since it's so uncommon, it's not really either complex or dangerous. - Allen S. Rout - 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: schedule start randomization
On Apr 4, 2006, at 12:39 PM, Prather, Wanda wrote: If you don't' want to make the users responsible for starting their backups, you can put a .bat file in the autologon.bat script that sleeps for 5 minutes, then does "dsmc incremental". That is probably the easiest solution. ... Or, take the PCs off time server synchronization and let their clocks drift... :-) That *seems* ridiculous, but we do see a surprising number of postings with client-server session pastings where the times actually are markedly different. Richard Sims
Re: Data tape in limbo
Now I notice you said it could not be checked in. What error do you get when you try to check it in? Have you had your library do an audit followed by a tsm 'audit library' command? >>> [EMAIL PROTECTED] 4/4/2006 10:17:07 AM >>> I have, most certainly, mishandled some media and need some help to put things together, if that is possible. I have a tape that is a stgpool volume but is not a library volume: q vol 35S f=d Volume Name: 35S Storage Pool Name: TAPEPOOL Device Class Name: SDLTC Estimated Capacity (MB): 327,680.0 Scaled Capacity Applied: Pct Util: 11.6 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 54.9 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 608 Write Pass Number: 1 Approx. Date Last Written: 01/18/06 11:13:29 Approx. Date Last Read: 06/21/05 08:59:31 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Volume is MVS Lanfree Capable : No Last Update by (administrator): BUBBLES Last Update Date/Time: 04/04/06 09:49:15 'q libvol' output has no entries regarding the tape. An audit of the library succeeeds. 35S is physically in the library but can neither be checked in or checked out by TSM. the volhistory says this about 35S: cat volhist.out | grep 35S 2004/02/15 21:41:06 STGNEW 0 0 0 SDLTC 35S 2004/02/24 16:17:47 STGDELETE 0 0 0 SDLTC 35S 2004/03/02 20:33:37 STGNEW 0 0 0 SDLTC 35S 2004/03/08 16:13:24 STGDELETE 0 0 0 SDLTC 35S 2004/06/23 18:00:46 STGNEW 0 0 0 SDLTC 35S Any ideas?? thank you. - Make free worldwide PC-to-PC calls. Try the new Yahoo! Canada Messenger with Voice
Re: Data tape in limbo
checkin libvol LIBNAME 35S checklabel=no status=private should find it and register it to tsm if it is physically known by the library. David >>> [EMAIL PROTECTED] 4/4/2006 10:17:07 AM >>> I have, most certainly, mishandled some media and need some help to put things together, if that is possible. I have a tape that is a stgpool volume but is not a library volume: q vol 35S f=d Volume Name: 35S Storage Pool Name: TAPEPOOL Device Class Name: SDLTC Estimated Capacity (MB): 327,680.0 Scaled Capacity Applied: Pct Util: 11.6 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 54.9 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 608 Write Pass Number: 1 Approx. Date Last Written: 01/18/06 11:13:29 Approx. Date Last Read: 06/21/05 08:59:31 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Volume is MVS Lanfree Capable : No Last Update by (administrator): BUBBLES Last Update Date/Time: 04/04/06 09:49:15 'q libvol' output has no entries regarding the tape. An audit of the library succeeeds. 35S is physically in the library but can neither be checked in or checked out by TSM. the volhistory says this about 35S: cat volhist.out | grep 35S 2004/02/15 21:41:06 STGNEW 0 0 0 SDLTC 35S 2004/02/24 16:17:47 STGDELETE 0 0 0 SDLTC 35S 2004/03/02 20:33:37 STGNEW 0 0 0 SDLTC 35S 2004/03/08 16:13:24 STGDELETE 0 0 0 SDLTC 35S 2004/06/23 18:00:46 STGNEW 0 0 0 SDLTC 35S Any ideas?? thank you. - Make free worldwide PC-to-PC calls. Try the new Yahoo! Canada Messenger with Voice
Re: Random Access Disk Pools
Rod, After spending 4 weeks using file device class disk pools, I would say use random access. Here is why: The speed of the random access disk pools is phenomenally better than the file device class - not sure why though The volumes (from the presentation I just read from the other email) are supposed to be picked based on filesystems with no volume mounted. What I found is the it selects them in collation order. This accessed the volumes on one raid group, giving the worst performance of all. After using a kludgy method to spread the data around, the performance was better, but did not approach random access Small files were a problem in some cases. Since I was collocating, if alot of small files were written to a volume (in this case, it was moving my dirmc pool), there can be alot of wasted space. Apparently, a block of 256K is written to disk no matter how much data is being written. If alot of small files are written to a volume, space can be wasted because the volume will fill before capacity is reached (we were using predefined volumes) It takes alot of time to predefine the volumes. We were finding it took about 19 hours to predefine 2TB. We were able to run 8 of those, so it ended up taking 19 hours to predefine 16TB, but that is still a long time. Some portion of space is taken up by volumes that are not yet full (with predefined volumes at least) in a file device class. This is not a worry with random access, but fragmented aggregates could be a worry. My plan is to move data off of random access volumes on the weekends to help prevent fragmentation. If you have any other questions, please let me know. --- "Park, Rod" <[EMAIL PROTECTED]> wrote: > Let me ask again because I didn't get much feedback. How do we find > the > thread limit, and can people weigh in on whether they use big disk > pools > (50TB-200TB). The advantages/disadvantages of big disk pools versus > devclass=file any gotchas either way. We are looking at buy a lot > more > disk and creating big diskpools to land data on and be the primary > pool > instead of tape. Thank in advance. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of > Andy Huebner > Sent: Monday, March 27, 2006 11:43 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Random Access Disk Pools > > We found the limit. There are some posts in this forum from the > first > of the year about the problem we ran into. > > Andy Huebner > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of > Park, Rod > Sent: Monday, March 27, 2006 6:45 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Random Access Disk Pools > > We use random access pools, how do you know what your thread limit > iswe've never had any issues with ours but we're thinking about > adding a lot more. What's the biggest reason you do/don't use > devclass=file over disk storage poolsarguments either way? > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of > Andy Huebner > Sent: Friday, March 24, 2006 3:37 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Random Access Disk Pools > > Be careful with how many disk pool volumes you create. Each volume > uses > 1 thread, add this to all of the other threads in use, our TSM server > would die at around 1800 active threads. > > Andy Huebner > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of > Andrew Carlson > Sent: Friday, March 24, 2006 11:04 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Random Access Disk Pools > > I have heard in the past that random access disk pools can become > fragmented and practically unusable after a while. I was wondering > if anyone sees this in the real world? I posted the other day about > managing predefined volumes in a file type devclass, and the only > answer I got said they were using random access pools. I would MUCH > rather have a random access pool, so if there is no problem with > this, I will convert over to random access. Thanks for any input. > > TSM 5.3.2.3 on AIX 5.2.5 EMC Clarion Disk, 120 TB in 2TB LUN's > > Andy Carlson > > --- > Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: > $8.95/month, > The feeling of seeing the red box with the item you want in > it:Priceless. > > > 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. > > > This email and an
Re: schedule start randomization
If you don't' want to make the users responsible for starting their backups, you can put a .bat file in the autologon.bat script that sleeps for 5 minutes, then does "dsmc incremental". That is probably the easiest solution. The disadvantage of that , there is no TSM server schedule for it, so you won't know if they backed up or not by looking at TSM events. But, given that they are laptops, are you going to be able to have them on a schedule you can check reliably anyway? The only other thing I can think of would be to put them in POLLING mode, and have an admin script that defines a ONETIME schedule daily. Not sure if that would work or not. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Reeves Sent: Thursday, March 30, 2006 4:16 PM To: ADSM-L@VM.MARIST.EDU Subject: schedule start randomization Is there are way to have some schedules start randomly within their start window and other start immediately? I'm trying to figure out how to get laptops to automatically backup when they have a network connection. I have a schedule with a 23 hour start time (based on someone's suggestion) and the laptop has schedmode set to polling. It connects & gets a schedule time, but since I have randomization set for my other clients, the backup time may be hours away and the laptop may no longer be connected to the network. (Server is 5.2.2 on AIX, client is 5.3 on Windows in this case.) Thanks. Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860
Re: Random Access Disk Pools
On Apr 4, 2006, at 11:38 AM, Park, Rod wrote: Let me ask again because I didn't get much feedback. How do we find the thread limit, ... As far as I know, that's a function of your operating system limits, as in: http://publib16.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/ genprogc/thread_lib.htm Richard Sims
Re: Random Access Disk Pools
See http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21218415 for comparison of disk vs devclass=file -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Tuesday, April 04, 2006 10:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Let me ask again because I didn't get much feedback. How do we find the thread limit, and can people weigh in on whether they use big disk pools (50TB-200TB). The advantages/disadvantages of big disk pools versus devclass=file any gotchas either way. We are looking at buy a lot more disk and creating big diskpools to land data on and be the primary pool instead of tape. Thank in advance. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Monday, March 27, 2006 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We found the limit. There are some posts in this forum from the first of the year about the problem we ran into. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Monday, March 27, 2006 6:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We use random access pools, how do you know what your thread limit iswe've never had any issues with ours but we're thinking about adding a lot more. What's the biggest reason you do/don't use devclass=file over disk storage poolsarguments either way? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Friday, March 24, 2006 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Be careful with how many disk pool volumes you create. Each volume uses 1 thread, add this to all of the other threads in use, our TSM server would die at around 1800 active threads. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Friday, March 24, 2006 11:04 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Random Access Disk Pools I have heard in the past that random access disk pools can become fragmented and practically unusable after a while. I was wondering if anyone sees this in the real world? I posted the other day about managing predefined volumes in a file type devclass, and the only answer I got said they were using random access pools. I would MUCH rather have a random access pool, so if there is no problem with this, I will convert over to random access. Thanks for any input. TSM 5.3.2.3 on AIX 5.2.5 EMC Clarion Disk, 120 TB in 2TB LUN's Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. 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. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email. 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: Random Access Disk Pools
Let me ask again because I didn't get much feedback. How do we find the thread limit, and can people weigh in on whether they use big disk pools (50TB-200TB). The advantages/disadvantages of big disk pools versus devclass=file any gotchas either way. We are looking at buy a lot more disk and creating big diskpools to land data on and be the primary pool instead of tape. Thank in advance. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Monday, March 27, 2006 11:43 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We found the limit. There are some posts in this forum from the first of the year about the problem we ran into. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Park, Rod Sent: Monday, March 27, 2006 6:45 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools We use random access pools, how do you know what your thread limit iswe've never had any issues with ours but we're thinking about adding a lot more. What's the biggest reason you do/don't use devclass=file over disk storage poolsarguments either way? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy Huebner Sent: Friday, March 24, 2006 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Random Access Disk Pools Be careful with how many disk pool volumes you create. Each volume uses 1 thread, add this to all of the other threads in use, our TSM server would die at around 1800 active threads. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Carlson Sent: Friday, March 24, 2006 11:04 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Random Access Disk Pools I have heard in the past that random access disk pools can become fragmented and practically unusable after a while. I was wondering if anyone sees this in the real world? I posted the other day about managing predefined volumes in a file type devclass, and the only answer I got said they were using random access pools. I would MUCH rather have a random access pool, so if there is no problem with this, I will convert over to random access. Thanks for any input. TSM 5.3.2.3 on AIX 5.2.5 EMC Clarion Disk, 120 TB in 2TB LUN's Andy Carlson --- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. 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. This email and any files transmitted with it are confidential and intended solely for the use of the addressee. If you are not the intended addressee, then you have received this email in error and any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please notify us immediately of your unintended receipt by reply and then delete this email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates will not be held liable to any person resulting from the unintended or unauthorized use of any information contained in this email or as a result of any additions or deletions of information originally contained in this email. 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: SUMMARY table tape mounts for Lan-Free
THANKS! At least I know that I'm getting all the tape mounts recorded - that helps a lot! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Sent: Saturday, April 01, 2006 12:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: SUMMARY table tape mounts for Lan-Free I just double checked my system and it did include lanfree agent TAPE MOUNTS. But from SUMMARY table it does not tell you which TAPE MOUNT is for lan-free agent, and which is for TSM Server instance. Bill On 3/28/06, Prather, Wanda <[EMAIL PROTECTED]> wrote: > > If you have a Lan-free client, > so that your library is defined as SHARED, > do the TAPE MOUNTS that show up in the SUMMARY table include the mounts > for the Lan-free agent, or just the primary TSM server instance? > > Thanks for any insight.. > > Wanda Prather > "* I/O, I/O, It's all about I/O *" -(me) >
Re: Data tape in limbo
Have you tried to manually remove the tape from the library, run an audit library, then try the check it back in. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Douglas Currell Sent: Tuesday, April 04, 2006 7:17 AM To: ADSM-L@VM.MARIST.EDU Subject: Data tape in limbo I have, most certainly, mishandled some media and need some help to put things together, if that is possible. I have a tape that is a stgpool volume but is not a library volume: q vol 35S f=d Volume Name: 35S Storage Pool Name: TAPEPOOL Device Class Name: SDLTC Estimated Capacity (MB): 327,680.0 Scaled Capacity Applied: Pct Util: 11.6 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 54.9 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 608 Write Pass Number: 1 Approx. Date Last Written: 01/18/06 11:13:29 Approx. Date Last Read: 06/21/05 08:59:31 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Volume is MVS Lanfree Capable : No Last Update by (administrator): BUBBLES Last Update Date/Time: 04/04/06 09:49:15 'q libvol' output has no entries regarding the tape. An audit of the library succeeeds. 35S is physically in the library but can neither be checked in or checked out by TSM. the volhistory says this about 35S: cat volhist.out | grep 35S 2004/02/15 21:41:06 STGNEW 0 0 0 SDLTC 35S 2004/02/24 16:17:47 STGDELETE 0 0 0 SDLTC 35S 2004/03/02 20:33:37 STGNEW 0 0 0 SDLTC 35S 2004/03/08 16:13:24 STGDELETE 0 0 0 SDLTC 35S 2004/06/23 18:00:46 STGNEW 0 0 0 SDLTC 35S Any ideas?? thank you. - Make free worldwide PC-to-PC calls. Try the new Yahoo! Canada Messenger with Voice
Data tape in limbo
I have, most certainly, mishandled some media and need some help to put things together, if that is possible. I have a tape that is a stgpool volume but is not a library volume: q vol 35S f=d Volume Name: 35S Storage Pool Name: TAPEPOOL Device Class Name: SDLTC Estimated Capacity (MB): 327,680.0 Scaled Capacity Applied: Pct Util: 11.6 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 54.9 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 608 Write Pass Number: 1 Approx. Date Last Written: 01/18/06 11:13:29 Approx. Date Last Read: 06/21/05 08:59:31 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Volume is MVS Lanfree Capable : No Last Update by (administrator): BUBBLES Last Update Date/Time: 04/04/06 09:49:15 'q libvol' output has no entries regarding the tape. An audit of the library succeeeds. 35S is physically in the library but can neither be checked in or checked out by TSM. the volhistory says this about 35S: cat volhist.out | grep 35S 2004/02/15 21:41:06 STGNEW 0 0 0 SDLTC 35S 2004/02/24 16:17:47 STGDELETE 0 0 0 SDLTC 35S 2004/03/02 20:33:37 STGNEW 0 0 0 SDLTC 35S 2004/03/08 16:13:24 STGDELETE 0 0 0 SDLTC 35S 2004/06/23 18:00:46 STGNEW 0 0 0 SDLTC 35S Any ideas?? thank you. - Make free worldwide PC-to-PC calls. Try the new Yahoo! Canada Messenger with Voice
Re: Migrating to a Library Manager
>From TSMLM2, define the library as shared and all the drives. Checkin all the >tapes as PRIVATE. >From TSM2T, define the shared library and point your device class(es) to the >shared library. Now just AUDIT LIBR CHECKL=B. This will populate the volume history on TSMLM2 with all the volume information, change the ownership to all the checked in volumes to TSM2T. Then you can do a Q LIBV on the TSMLM2 and any tape still with the ownership of TSMLM2 is probably a scratch tape. Check the volhist on TSM2T to make sure, but then just UPD LIBV STATUS=SCRATCH. The big kicker seems to the the AUDIT LIBR from the library client populating the volhist on the library manager with all the known volume information. If you look at the volhistory entry for one of those tapes you'll see that the TYPE is 'REMOTE' and the LOCATION is ''. Bill Boyer "Some days you're the bug, some days you're the windshield" - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of fred johanson Sent: Tuesday, April 04, 2006 9:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Migrating to a Library Manager AND remember to print, or otherwise save a list of PRIVATE, SCRATCH, DBB, DBS, and whatever other sorts of tapes you may have, for reference if one of your experiments goes wrong. At 08:10 PM 4/3/2006 -0400, you wrote: > >> On Mon, 3 Apr 2006 15:32:22 -0500, Bill Kelly <[EMAIL PROTECTED]> said: > > > > 1) check the tapes out of tsm2t > > 2) delete the library (and drives and paths) from tsm2t > > 3) define the library (and drives and paths) in tsmlm2, and as a > > shared library in tsm2t > > 4) check the tapes in to tsmlm2. > >What he said; I've done this. > >Additional knob-polishing, lily-gilding, etc: > >Remember that you don't have to REMOVE the volumes on checkout, and >that you don't have to check the label when you check them in. This >can really accellerate experiments. > >Remember also that it's easy to get back to the state of "everything >checked out, and library gone", so you can get it wrong several times, >and ry again with very little cost. > >While this is an intimidating process since it's so uncommon, it's not >really either complex or dangerous. > > >- Allen S. Rout Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: Migrating to a Library Manager
AND remember to print, or otherwise save a list of PRIVATE, SCRATCH, DBB, DBS, and whatever other sorts of tapes you may have, for reference if one of your experiments goes wrong. At 08:10 PM 4/3/2006 -0400, you wrote: >> On Mon, 3 Apr 2006 15:32:22 -0500, Bill Kelly <[EMAIL PROTECTED]> said: > 1) check the tapes out of tsm2t > 2) delete the library (and drives and paths) from tsm2t > 3) define the library (and drives and paths) in tsmlm2, and as a shared > library in tsm2t > 4) check the tapes in to tsmlm2. What he said; I've done this. Additional knob-polishing, lily-gilding, etc: Remember that you don't have to REMOVE the volumes on checkout, and that you don't have to check the label when you check them in. This can really accellerate experiments. Remember also that it's easy to get back to the state of "everything checked out, and library gone", so you can get it wrong several times, and ry again with very little cost. While this is an intimidating process since it's so uncommon, it's not really either complex or dangerous. - Allen S. Rout Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: TSM server automation products
We have successfully used StorServer Manager for automation for a number of years. It works well as long as your processing follows standard way TSM want's to run. At times it gets confused, but in general we have been happy with it. It's worth a look and demo try. http://www.storserver.com/main.cfm?menu=2&submenu=ssm&detail=include/SSMOverview.cfm - 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: Client Schedule Sysobj Backup Keeps Failing
Isn't it a path issue? Did you try the full path command? Ex: c:\progra~1\Tivoli\tsm\baclient\dsmc backup systemstate - Original Message - From: Dksh Cssc To: ADSM-L@VM.MARIST.EDU Sent: Tuesday, April 04, 2006 6:05 AM Subject: Client Schedule Sysobj Backup Keeps Failing Hi all , We are trying to backup DKSHH03 system state ( Windows Server 2003). However the backup seems to fail all the time. We schedule the system state backup under DKSHH03_SYSOBJ at 15:00:00 but failed. Later around 15:04:00 the backup is completed successfully but under schedule named DKSHH03_INCR. 1) Could anyone help to enlighten me why the system state backup event goes under different backup schedule name? What is the implication of such event? 2) Supposingly once a backup failed, the same backup event would NOT be re-tried again ; but why does this case happened? Here goes the dsmsched.log : 04/04/2006 15:00:06 Node Name: DKSHH03 04/04/2006 15:00:06 Session established with server KULTSM01P: AIX-RS/6000 04/04/2006 15:00:06 Server Version 5, Release 2, Level 2.0 04/04/2006 15:00:06 Server date/time: 04/04/2006 15:00:31 Last access: 04/04/2006 15:00:27 04/04/2006 15:00:06 Executing Operating System command or script: dsmc backup systemstate 04/04/2006 15:00:34 Finished command. Return code is: 12 04/04/2006 15:00:34 ANS1909E The scheduled command failed. 04/04/2006 15:00:34 ANS1512E Scheduled event 'DKSHH03_SYSOBJ' failed. Return code = 12. 04/04/2006 15:00:34 Sending results for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:00:36 Results sent to server for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:00:36 Querying server for next scheduled event. 04/04/2006 15:00:36 Node Name: DKSHH03 04/04/2006 15:00:36 Session established with server KULTSM01P: AIX-RS/6000 04/04/2006 15:00:36 Server Version 5, Release 2, Level 2.0 04/04/2006 15:00:36 Server date/time: 04/04/2006 15:01:01 Last access: 04/04/2006 15:00:33 04/04/2006 15:00:36 --- SCHEDULEREC QUERY BEGIN 04/04/2006 15:00:36 --- SCHEDULEREC QUERY END 04/04/2006 15:00:36 Next operation scheduled: 04/04/2006 15:00:36 04/04/2006 15:00:36 Schedule Name: DKSHH03_INCR 04/04/2006 15:00:36 Action:Incremental 04/04/2006 15:00:36 Objects: c:\ d:\ e:\ 04/04/2006 15:00:36 Options: -subdir=yes 04/04/2006 15:00:36 Server Window Start: 02:30:00 on 04/05/2006 04/04/2006 15:00:36 04/04/2006 15:00:36 Command will be executed in 11 hours and 29 minutes. 04/04/2006 15:04:30 Finished command. Return code is: 0 04/04/2006 15:04:30 ANS1908I The scheduled command completed successfully. 04/04/2006 15:04:30 Scheduled event 'DKSHH03_SYSOBJ' completed successfully. 04/04/2006 15:04:30 Sending results for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:04:30 Results sent to server for scheduled event 'DKSHH03_SYSOBJ'. Thanks and Warmest Regards, ___ DKSH Market Intelligence Liew Callie DKSH Corporate Shared Services Center Sdn Bhd Lot L4-E-3A, Enterprise 4, Technology Park Malaysia, 57000 Kuala Lumpur. Phone: +603 8992 2855 Fax: +603 8992 2999 [EMAIL PROTECTED] www.dksh.com -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.5/300 - Release Date: 3/4/2006
Re: errno=11 with EDT, ACSLS, TSM
Hi Neil, I am using 9840B and 9840A... I am not capturing any errors on the ACSLS about LH_TRANSPORT_BUSY... The errors do not seems to be the same... Have you checked the tapes firmware are at the latest release ¿? regards, Ibán Bernaldo de Quirós Márquez Technical Specialist cell: + 34 659 01 91 12 Sun Microsystems Iberia De: ADSM: Dist Stor Manager en nombre de Neil Schofield Enviado el: mar 04/04/2006 12:48 Para: ADSM-L@VM.MARIST.EDU Asunto: Re: [ADSM-L] errno=11 with EDT, ACSLS, TSM Iban I am using DISMOUNT RETRY_2 SLEEP_60 and this works as intended in that TSM is not aware of the retries. However these retries didn't occur in EDT 6.4, and now our acsss_event.log is filling with LH_TRANSPORT_BUSY errors. I don't know whether our problems are the same. Are you seeing the same errors as us on your ACSLS? Are you using 9840C drives? Regards Neil Find out how to protect your home from frost this winter at www.yorkshirewater.com YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD 2004 AND 2005 The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
Re: Policy and DRP question
TSM is not tape-oriented: it is stored-object-oriented. The copy storage pool contains an image of your primary pool(s) according to the policies for the objects stored in the primary pool. Your DR practices need to keep a copy of all data objects offsite, not just a fixed number of tapes. You're not preserving media - you're preserving data. Richard Sims On Apr 4, 2006, at 12:34 AM, Paul Dudley wrote: We have TSM version 5.2 I have changed the standard policy so that we now keep the 10 latest versions of each file rather than 7. I have also changed our del volhist to tod=today-10 where it was previously 7. I have been told that previously we had to keep the 7 latest copy tapes and db tapes offsite for DRP to ensure that we could recover complete servers. With the changes that I have made does this mean that we have to now keep the 10 latest tapes offsite for complete DRP?
Re: TSM server automation products
Background to my $.02 - in my former life as the main TSM admin in the frozen north of Michigan, our management was frankly too tight to "waste" money on 3rd party tools that "only" allowed me to do my job more effectively. Consequently, my only option was to code it myself. By the time I left, we had totally automated the daily processing of all admin functions, complete with tape checkin/out, with offsite tape slot management and other niceties. Beyond that, we had an entire menu of custom ad-hoc reports we could run at will, and a problem detection system that scanned all our potential problem areas in TSM every 10 minutes, generating emails, pages, and/or helpdesk tickets depending on how we setup our config file. Not too shabby, especially since it was all developed using Rexx running on our z/os mainframe (althought I was the TSM Admin, another group "owned" AIX where TSM lived, and were reluctant to give me any access beyond the bare minimum). When I moved down to sunny Tennessee, I swore I would not get locked into supporting that complex of a home-grown system ever again. I intended to use whatever was in place or the TSM Admin could convince mgmt to buy (I only deal with the Intel client side of TSM now). They bought a 3rd party tool from a vendor who shall remain nameless. When I was invited to meet with this vendor to discuss any additional reporting needs I had, I gave him printouts and source code from my most-used and I felt very needed ad-hoc report. This report presented daily session data in html and included logic to filter and/or sort the data so it could be used in a wide variety of troubleshooting scenarios. As soon as I finished my description, his reply was "I'll build you a static html report, but nothing dynamic, because I'm not interested in becoming a web developer". He was not impressed with my comment that I thought he should become interested in anything his customers were interested in buying. Needless to say, I'm back to coding. Thankfully, because Rexx is so darned portable, the move from z/os to Windows has been fairly painless, so we should have what we need relatively soon. Now if I could only rake in some of the thousands of $$$ we paid for our reporting package... My biggest drawbacks to self-developed code are: 1. I'm never satisfied, so I constantly "enhance" it, which takes time 2. Changes to TSM, such as message formats, break my code and require time to fix I personally feel that most of the arguments about self-developed code being cursed by future generations can be eased by: 1. More documentation in the code than you think you really need 2. Putting as much of the "custom" stuff in config and setup files as possible, rather than being hard-coded 3. I love the "open-source" suggestion Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-752-6574 (desk) 423-785-7347 (cell) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Monday, April 03, 2006 1:10 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM server automation products >> On Sun, 2 Apr 2006 09:52:52 +0200, Jurjen Oskam <[EMAIL PROTECTED]> said: > On Sat, Apr 01, 2006 at 09:46:00PM -0500, Allen S. Rout wrote: >> Speaking as someone buried in my own PERL up to my nose: > [snip: quite a good argument] >> I don't think I could be as effective with a third-party product as I >> am with my own stuff. I do think that the person who gets my job >> after I get hit by a truck will curse me for years. > Thanks, those are good points. But it does beg the question: how bad > is your current situation? :) I'll allude to a bit of logical pedantry by suggesting a google of 'beg the question' :) In any case, the question is an excellent one. > I mean, is it such a spaghetti that nobody, except you as the > developer, can *really* get it? Isn't *that* something you could > change, so that your successor can as effective as you are? The philosophical / design / practical problem here is very complex. I'd guess the average TSM clue of those admins writing their own automation code is at least a standard deviation higher than that of the larger TSM-admin population. How much of that clue may be implicit in the code, and how much must be explicit, accessible to a newcomer? Designing your code for maintainability is one thing, and we mostly think we're trying to do that. Designing your code so that a domain novice (or domain much-less-clued) can debug it is a totally different question. It may simply be an impossible task. Unfortunately, that's the problem we're talking about. I mean, issues of arrogance and modesty aside, I've been working with TSM since 1998, and with PERL since before 1992. The person hired after I get hit by a truck is in all probability going to be less experienced in both of these areas, perhaps profoundly so. But it gets worse: our automation code reflec
Re: errno=11 with EDT, ACSLS, TSM
Iban I am using DISMOUNT RETRY_2 SLEEP_60 and this works as intended in that TSM is not aware of the retries. However these retries didn't occur in EDT 6.4, and now our acsss_event.log is filling with LH_TRANSPORT_BUSY errors. I don't know whether our problems are the same. Are you seeing the same errors as us on your ACSLS? Are you using 9840C drives? Regards Neil Find out how to protect your home from frost this winter at www.yorkshirewater.com YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD 2004 AND 2005 The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682
Re: Client Schedule Sysobj Backup Keeps Failing
Hi, 1. WHAT IS YOURS B/A CLIENT VERSION. 2. WHAT INFORMATION ERROR.LOG PROVIDE. With Best Regards, Sandeep Jain ** Legal Disclaimer ** "This email may contain confidential and privileged material for the sole use of the intended recipient. Any unauthorized review, use or distribution by others is strictly prohibited. If you have received the message in error, please advise the sender by reply email and delete the message. Thank you." * -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dksh Cssc Sent: Tuesday, April 04, 2006 2:36 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Client Schedule Sysobj Backup Keeps Failing Hi all , We are trying to backup DKSHH03 system state ( Windows Server 2003). However the backup seems to fail all the time. We schedule the system state backup under DKSHH03_SYSOBJ at 15:00:00 but failed. Later around 15:04:00 the backup is completed successfully but under schedule named DKSHH03_INCR. 1) Could anyone help to enlighten me why the system state backup event goes under different backup schedule name? What is the implication of such event? 2) Supposingly once a backup failed, the same backup event would NOT be re-tried again ; but why does this case happened? Here goes the dsmsched.log : 04/04/2006 15:00:06 Node Name: DKSHH03 04/04/2006 15:00:06 Session established with server KULTSM01P: AIX-RS/6000 04/04/2006 15:00:06 Server Version 5, Release 2, Level 2.0 04/04/2006 15:00:06 Server date/time: 04/04/2006 15:00:31 Last access: 04/04/2006 15:00:27 04/04/2006 15:00:06 Executing Operating System command or script: dsmc backup systemstate 04/04/2006 15:00:34 Finished command. Return code is: 12 04/04/2006 15:00:34 ANS1909E The scheduled command failed. 04/04/2006 15:00:34 ANS1512E Scheduled event 'DKSHH03_SYSOBJ' failed. Return code = 12. 04/04/2006 15:00:34 Sending results for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:00:36 Results sent to server for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:00:36 Querying server for next scheduled event. 04/04/2006 15:00:36 Node Name: DKSHH03 04/04/2006 15:00:36 Session established with server KULTSM01P: AIX-RS/6000 04/04/2006 15:00:36 Server Version 5, Release 2, Level 2.0 04/04/2006 15:00:36 Server date/time: 04/04/2006 15:01:01 Last access: 04/04/2006 15:00:33 04/04/2006 15:00:36 --- SCHEDULEREC QUERY BEGIN 04/04/2006 15:00:36 --- SCHEDULEREC QUERY END 04/04/2006 15:00:36 Next operation scheduled: 04/04/2006 15:00:36 04/04/2006 15:00:36 Schedule Name: DKSHH03_INCR 04/04/2006 15:00:36 Action:Incremental 04/04/2006 15:00:36 Objects: c:\ d:\ e:\ 04/04/2006 15:00:36 Options: -subdir=yes 04/04/2006 15:00:36 Server Window Start: 02:30:00 on 04/05/2006 04/04/2006 15:00:36 04/04/2006 15:00:36 Command will be executed in 11 hours and 29 minutes. 04/04/2006 15:04:30 Finished command. Return code is: 0 04/04/2006 15:04:30 ANS1908I The scheduled command completed successfully. 04/04/2006 15:04:30 Scheduled event 'DKSHH03_SYSOBJ' completed successfully. 04/04/2006 15:04:30 Sending results for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:04:30 Results sent to server for scheduled event 'DKSHH03_SYSOBJ'. Around 15:48:00 , we manually backup the system state to verify the backup is working and successful. Thanks and Warmest Regards, ___ DKSH Market Intelligence Liew Callie DKSH Corporate Shared Services Center Sdn Bhd Lot L4-E-3A, Enterprise 4, Technology Park Malaysia, 57000 Kuala Lumpur. Phone: +603 8992 2855 Fax: +603 8992 2999 [EMAIL PROTECTED] www.dksh.com This email has been scanned for any virus infection at the sending end.
Client Schedule Sysobj Backup Keeps Failing
Hi all , We are trying to backup DKSHH03 system state ( Windows Server 2003). However the backup seems to fail all the time. We schedule the system state backup under DKSHH03_SYSOBJ at 15:00:00 but failed. Later around 15:04:00 the backup is completed successfully but under schedule named DKSHH03_INCR. 1) Could anyone help to enlighten me why the system state backup event goes under different backup schedule name? What is the implication of such event? 2) Supposingly once a backup failed, the same backup event would NOT be re-tried again ; but why does this case happened? Here goes the dsmsched.log : 04/04/2006 15:00:06 Node Name: DKSHH03 04/04/2006 15:00:06 Session established with server KULTSM01P: AIX-RS/6000 04/04/2006 15:00:06 Server Version 5, Release 2, Level 2.0 04/04/2006 15:00:06 Server date/time: 04/04/2006 15:00:31 Last access: 04/04/2006 15:00:27 04/04/2006 15:00:06 Executing Operating System command or script: dsmc backup systemstate 04/04/2006 15:00:34 Finished command. Return code is: 12 04/04/2006 15:00:34 ANS1909E The scheduled command failed. 04/04/2006 15:00:34 ANS1512E Scheduled event 'DKSHH03_SYSOBJ' failed. Return code = 12. 04/04/2006 15:00:34 Sending results for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:00:36 Results sent to server for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:00:36 Querying server for next scheduled event. 04/04/2006 15:00:36 Node Name: DKSHH03 04/04/2006 15:00:36 Session established with server KULTSM01P: AIX-RS/6000 04/04/2006 15:00:36 Server Version 5, Release 2, Level 2.0 04/04/2006 15:00:36 Server date/time: 04/04/2006 15:01:01 Last access: 04/04/2006 15:00:33 04/04/2006 15:00:36 --- SCHEDULEREC QUERY BEGIN 04/04/2006 15:00:36 --- SCHEDULEREC QUERY END 04/04/2006 15:00:36 Next operation scheduled: 04/04/2006 15:00:36 04/04/2006 15:00:36 Schedule Name: DKSHH03_INCR 04/04/2006 15:00:36 Action: Incremental 04/04/2006 15:00:36 Objects: c:\ d:\ e:\ 04/04/2006 15:00:36 Options: -subdir=yes 04/04/2006 15:00:36 Server Window Start: 02:30:00 on 04/05/2006 04/04/2006 15:00:36 04/04/2006 15:00:36 Command will be executed in 11 hours and 29 minutes. 04/04/2006 15:04:30 Finished command. Return code is: 0 04/04/2006 15:04:30 ANS1908I The scheduled command completed successfully. 04/04/2006 15:04:30 Scheduled event 'DKSHH03_SYSOBJ' completed successfully. 04/04/2006 15:04:30 Sending results for scheduled event 'DKSHH03_SYSOBJ'. 04/04/2006 15:04:30 Results sent to server for scheduled event 'DKSHH03_SYSOBJ'. Around 15:48:00 , we manually backup the system state to verify the backup is working and successful. Thanks and Warmest Regards, ___ DKSH Market Intelligence Liew Callie DKSH Corporate Shared Services Center Sdn Bhd Lot L4-E-3A, Enterprise 4, Technology Park Malaysia, 57000 Kuala Lumpur. Phone: +603 8992 2855 Fax: +603 8992 2999 [EMAIL PROTECTED] www.dksh.com
Re: errno=11 with EDT, ACSLS, TSM
Hi Neil, I was reading EDT literature and I found the following (from version 7.3): dismount retry_5 sleep_60 This parameter defines that in a dismount process EDT will try to dismount the tape 5 times between periods of 60 seconds... I will try it !! but I think that if we are having the same problem, it should work properly and if it does not work at first instance it should work in the following tries... Tell me your comments !! Best Regards, Ibán Bernaldo de Quirós Márquez Technical Specialist cell: + 34 659 01 91 12 Sun Microsystems Iberia De: ADSM: Dist Stor Manager en nombre de Neil Schofield Enviado el: lun 03/04/2006 18:34 Para: ADSM-L@VM.MARIST.EDU Asunto: Re: [ADSM-L] errno=11 with EDT, ACSLS, TSM Iban We too are having problems with something like 1% of dismounts on our externally managed libraries using EDT. I posted on it back in January but didn't see any responses. The problem started following an upgrade from EDT 6.4 to 7.4. Are you seeing any LH_ERR_TRANSPORT_BUSY errors in the acsss_event.log on the ACSLS system that correspond to the EDT errors? Are you by any chance using 9840C drives? Regards Neil Schofield Yorkshire Water Services Ltd. Find out how to protect your home from frost this winter at www.yorkshirewater.com YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD 2004 AND 2005 The information in this e-mail is confidential and may also be legally privileged. The contents are intended for recipient only and are subject to the legal notice available at http://www.keldagroup.com/email.htm Yorkshire Water Services Limited Registered Office Western House Halifax Road Bradford BD6 2SZ Registered in England and Wales No 2366682