Re: Cache Hit % below 99%
It didn't help. The fact that Joni reset the bufferpool statistics is what changed the hit percentage. Jim Sporer At 03:32 PM 1/20/2005 +, you wrote: ? For a long time I have believed (fairly sure originally told by IBM) that the method is to increase the buffpool size untill cache hit goes over 99% Talking to a colleague, we really don't see how reducing bufpool size can increase the cache hit% Can anyone explain what we are missing? Thanks, Matt. _-'-_ -|- -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Thursday, January 20, 2005 2:51 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Cache Hit % below 99% Hello! I just wanted to thank everyone for suggestions and help with this matter! I changed the bufpoolsize to 419430, which is 10% of the physical memory, and then reset the bufpool and now my cache hit % is 100%. At this point, until I see otherwise, I am going to conclude that I had the bufpoolsize setting too high at 524288. I will continue to monitor the cache hit % of the database, but I believe the problem to be solved. Thank you again! Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] "Curtis Stewart" <[EMAIL PROTECTED] AWSON.COM> To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Re: Cache Hit % below 99% 01/20/2005 09:33 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] .EDU> What is your buffpool setting? Run "query option" and look for the buffpoolsize. Look in the dsmserv.opt file and read the comments about this parameter, then look in the server manual for this too. [EMAIL PROTECTED] Joni Moyer <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 01/20/2005 07:19 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Cache Hit % below 99% Hello All! I have noticed that the cache hit % is below 99%. This is a newly defined TSM 5.2.2.5 server on an AIX 5.2 OS. Are there any special parameters/definitions that could contribute to the percentage being so low? Thanks! Available Space (MB): 24,576 Assigned Capacity (MB): 19,484 Maximum Extension (MB): 5,092 Maximum Reduction (MB): 15,000 Page Size (bytes): 4,096 Total Usable Pages: 4,987,904 Used Pages: 45,207 Pct Util: 0.9 Max. Pct Util: 0.9 Physical Volumes: 3 Buffer Pool Pages: 131,072 Total Buffer Requests: 132,692 Cache Hit Pct.: 95.15 Cache Wait Pct.: 0.00 Backup in Progress?: No Type of Backup In Progress: Incrementals Since Last Full: 0 Changed Since Last Backup (MB): 0.73 Percentage Changed: 0.41 Joni Moyer Highmark Storage Systems Work:(717)302-6603 Fax:(717)302-5974 [EMAIL PROTECTED] ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: Moving clients between TSM servers
We had the same sorts of problems moving clients from server to server. We found that length of time had more to do with the number of files moved than the amount of data moved. We did the exports by filespaces. That way if we had an error we didn't have to start over at the beginning. Jim At 10:17 AM 1/20/2005 -0500, you wrote: I am looking for suggestions on how to handle moving large TSM clients between TSM servers and maybe some corrections to my understanding of how EXPORT/IMPORT handles error situations. I need to move TSM clients from my zOS server (being phased out) to my AIX TSM server. The problem is, some of these systems have > 1TB of data to move. When I tried to move a 500GB client (250GB actual since the copypool data is not moved), the export/import ran for >40 hours before failing on a tape drive failure (190GB moved). My understandings are that: 1. During the E/I the client is locked/can not be performing backups on *EITHER* system. This means the client has to go without *ANY* backups for the duration. This is generally not acceptable ! 2. If the E/I fails like it did, I have no recourse but to delete what was successfully sent, and then start all over again. Doing a MERGE FILESPACES is only going to save me the issue of it creating multiple duplicate directories with the same name +1. It still will work through all 40+ 3590 tapes. So, how do you handle situations like this ? If 190GB took 2-days, 1TB will take > week with me praying for no tape drive failures (or TSM server crashes like it did earlier in the week with a U301 abend/known problem). The zOS server only has access to a 100MB connection. Both TSM servers are 5.2.3.4. I will be upgrading to 5.3 as soon as I can.
Re: DBtape won't go to scratch status
Run an AUDIT LIBRARY libname CHECKLABEL=BARCODE. Jim Sporer At 09:14 AM 12/14/2004 -0500, you wrote: Richard, The Dbbackups are being pruned, see the following. We have Delete Volhistory set Schedule Name DELETE_VOLHIST_DBDACK Description - Command delete volhistory type=dbbackup todate=today-14 Priority 5 Start date 2002-06-18 Start time 08:57:00 Duration 1 Duration units HOURS Period 1 Period units DAYS Day of Week ANY Expiration - Active? YES Last Update Date/Time 2004-04-28 07:36:44.00 Last Update by (administrator) Managing profile - The date on the tape shows 12/23/03 it show have been pruned a long time ago. Don, We have Reclamation set. I have not tried running a move data yet Schedule Name TAPE_RECLAIM_ON Description reclaim tapes Command UPD STG TAPEPOOL RECLAIM=20 Priority 5 Start date 2002-06-17 Start time 09:00:00 Duration 12 Duration units HOURS Period 1 Period units DAYS Day of Week ANY Expiration - Active? YES Last Update Date/Time 2004-12-03 15:15:17.00 Last Update by (administrator) Managing profile - Thanks Richard, Don and Jin Richard Sims wrote: > On Dec 13, 2004, at 2:16 PM, Timothy Hughes wrote: > > > Hello all, > > > > Not sure If I wrote about this one before, I do know I had this > > problem before but was never able to get it resolved. > > > > > > I have a couple tapes that are in Dbackup and I would like to change > > to > > scratch status I tried using update library volume using the TSM Gui > > and > > received the following message > > > > ANR8443E UPDATE LIBVOLUME: Volume N00275 in library IBM3494R > > cannot be assigned a status of SCRATCH. > > > > The DBbackup volume has a date of 12/23/03. So that data is not valid > > > > Anyone ever had a tape problem like this? > > > > Dbbackup volumes are pruned via DELete VOLHistory ... Type=DBBackup . > The most recent dbbackup volume is not deleteable, to assure that > you have *something* to recover with. > > Richard Sims
Message ANR8443E During Checkin
I am running TSM version 5.2.2.4 on aix. I have a 3494ATL using a library manager. I have a volume with a label of Z00217. When I try to delete this volume I get message ANR8443E. The history of this tape is I had a tsm server installed on machine one, named TSM1 and Z00217 was the latest TSM database backup tape for that server. I recreated the TSM1 server on a new machine and since then I have done a database backup for TSM1 so Z00217 is no longer the latest database backup. Since I recreated the TSM1 server Z00217, never existed in the volume history file. When I did a q libvol from the library manager Z00217 showed up as a database backup tape which it should. I thought I could make this a scratch tape by doing a "checkout libvol library Z00217 remove=no" and then "checkin libvol library Z00217 status=scratch" but that is when I got the ANR8443E message. I checked the volume in as private and TSM1 was assigned as the owner. Since tsm server TSM1 never knew anything about this tape the library manager must still be keeping track of the tape. Any suggestions on how I can make this volume scratch? Jim Sporer
Re: Tape Drive Serial #'s (WAS: Adding 3592's to a 3494)
I would think using UPD DR library drive SERIAL=AUTODETECT would do the same thing. Jim Sporer At 05:57 PM 10/27/2004 -0400, you wrote: Yes, for SCSI libraries, TSM now records the serial # of the tape drives. If you have a SCSI library, look at your devconfig file. (EVERYBODY: You DO know where your devconfig file is, yes?) If not, run q opt to find the location. In your devconfig, you will see the DEFINE DRIVE and DEFINE PATH statements that were logged when you originally set up your TSM drives, BUT you will see that TSM has added the SN# and WWN for the drives (assuming the drives are a type that can send that info back in response to a TSM query). TSM started doing this in 5.1, and it is not just a 359x issue. The caveat is just what Ben pointed out: if you swap out a drive, the SN# and the WWN no longer match what TSM has recorded in the DEFINE DRIVE, and TSM won't talk to the new drive until you redefine it. If your CE replaces a drive: 1) copy your devconfig to a safe place under another name. 2) Use the TSM admin GUI to delete the path for the removed drive 3) Use the TSM admin GUI to delete the drive 4) COPY the original DEFINE DRIVE command from the devconfig copy, MINUS the WWN and SN#, and paste it back into a command window. 5) COPY the original DEFINE PATH command form the devconfig copy, and paste it back into a command window. That will recreate your drive definition without having to think too much about it! TSM will go out and pick up the replacement SN# and WWN on its own. There is also a SERIAL# and WWN parm on the UPDATE DRIVE command, but I haven't played with those. People with Windows TSM servers don't even have to do either, you can delete the path and drive, then use the device configuration wizard to add it back. 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 Robert Clark Sent: Wednesday, October 27, 2004 5:22 PM To: [EMAIL PROTECTED] Subject: Re: Adding 3592's to a 3494 We're running a similar config, so I'm curious about the list response on this one as well. One additional question: I think I saw a message about TSM being able to keep track of tape drives by their serial numbers. Anyone have a pointer to docs on how this feature works, and what the caveats are, if any? Thanks, [RC] "Ben Bullock" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: Dist cc: Stor Manager" Subject: Re: Adding 3592's to a 3494 <[EMAIL PROTECTED] > 10/27/2004 01:55 PM Please respond to "ADSM: Dist Stor Manager" |---| | [ ] Secure E-mail | |---| Matthew (and others in the group), Just this week we put in our 2 test 3592 drives and started playing with them. These are sweet. So far they are running a little over 2X the speed of the 3590E drives, and we have yet to test the capacity. We've been able to test out the alternate pathing, dynamic load balancing, etc.. It's all through a SAN, so we have tested the zoning, etc. Failovers work as expected with no interruption to the TSM server at all. Very nice. AIX 5.2, TSM 5.2.1.3, Atape 9.0.7.0, atldd 5.5.1.0, 3592 drives, 3490 library. All has gone smoothly until we went to simulate a failed drive where we would swap it out for a new one. It didn't go well, with TSM or the OS not able to see the new drive correctly. When I tried to 'cfgmgr' it back in, it gave me these errors: root:># cfgmgr Method error (/usr/lib/methods/cfgppa_isa -l ppa0 ): 0514-038 Error loading kernel extension. Method error (/etc/methods/cfgtsmdd -l mt0 ): 0514-051 Device to be configured does not match the physical device at the specified connection location. Method error (/etc/methods/cfgtsmdd -l mt1 ): 0514-051 Device to be configured does not match the physical device at the specified connection location. I had to remove these 2 "mt" devices to get it to stop erroring. That's a new one to me... I have 2 questions: 1: During the installation of the tape drives the IBM CE asked if we wanted "hard" or "soft" addressing. His instructions say to do HARD, but then his support folks said "soft", what should it be? I'll be calling this in to IBM, but was curious if anybody here had an answer. 2: On our switch we are zoning the drives and FC adapters by WWN. Doing it this way, am I going to have to totally remove and recreate a dr
Re: Message ANR9613W
Mark, Thanks for the hint. We installed the 64 bit base release of tsm and then put the 5.2.2.4 32 bit maintenance release on over the top of that. That is probably why moving the 32 bit dsmlicense file from the old machine corrected the problem. I opened a problem with TSM support on this issue and was told it was unlikely we would cause a problem with the TSM data base. We reinstalled the base release and the 64 bit maintenance and that resolved the problem. I agree with you that it would be easy for the maintenance installer to check for this situation and prevent us from doing something this dumb. Jim At 02:43 PM 10/6/2004 -0500, you wrote: Jim, I just had a customer do an upgrade similar to what you describe and they had the same problem. It turned out that they installed both the 32 bit and 64 bit code on the machine. This is obviously not a good thing! BTW, you will probably notice you can't register any licenses either. When I called IBM support to make sure that this could be cleaned up by just doing an uninstall and then reinstall just the correct filesets they gave me some interesting info. First of all make a DB backup if possible. Also, hopefully you have a backup of the DB from right before you migrated. There is a slight chance that the TSM DB could have gotten corrupted, that is the reason for the DB backups. Then you can simply uninstall all of the TSM filesets and reinstall just the correct ones for EITHER 32 bit OR 64 bit, refer to the README file for the exact filesets. They, also pointed out that the other way to cause this problem is to have a mismatch, again 32 vs. 64 bit, between the TSM code and the license code, so check for that as well. But, either way the answer is backup the DB (CYA) and then uninstall and reinstall. We did not experience any TSM DB corruption, but we had the server running for a very short period of time with almost no activity before we caught the problem and got it fixed. IMHO, IBM should fix their LPP's so that you can not inadvertently install conflicting filesets! Let us know how you make out. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ======= Jim Sporer wrote: We were running TSM server version 5.2.2.4 on an AIX 5.1 machine. Yesterday we moved the TSM server to a new AIX machine running AIX 5.2. We installed TSM server version 5.2.2.4 on the new machine so the only difference was we are running AIX 5.2. We restored the TSM database to the new server and that went ok. We started the server and got message "ANR9613W error loading the ./dsmlicense for licensing function: Exec format error". At that point client nodes could not perform backups because of a licensing issue, ANR0439W was the message we were getting. I did a search on the message ANR9613W at IBM.COM and one of the hits was something about using a down level C library, xlc.rte 5.0.2.1. We are using xlc.rte 6.0.0.0 on the new aix machine. I decided to move the ./dsmlicense file from the old machine to the new machine and when I restarted the TSM server it came up without the error. Has anybody seen anything like this? Jim Sporer
Re: Message ANR9613W
Mark, Thanks for the info. Yes, I was unable to register licenses after getting the message. The 32 to 64 bit stuff is interesting because we did go from the 32 bit TSM on one machine to 64 bit on the other machine. I will be contacting IBM support to see if we can get this resolved. I'd hate to mess up my database. Jim At 02:43 PM 10/6/2004 -0500, you wrote: Jim, I just had a customer do an upgrade similar to what you describe and they had the same problem. It turned out that they installed both the 32 bit and 64 bit code on the machine. This is obviously not a good thing! BTW, you will probably notice you can't register any licenses either. When I called IBM support to make sure that this could be cleaned up by just doing an uninstall and then reinstall just the correct filesets they gave me some interesting info. First of all make a DB backup if possible. Also, hopefully you have a backup of the DB from right before you migrated. There is a slight chance that the TSM DB could have gotten corrupted, that is the reason for the DB backups. Then you can simply uninstall all of the TSM filesets and reinstall just the correct ones for EITHER 32 bit OR 64 bit, refer to the README file for the exact filesets. They, also pointed out that the other way to cause this problem is to have a mismatch, again 32 vs. 64 bit, between the TSM code and the license code, so check for that as well. But, either way the answer is backup the DB (CYA) and then uninstall and reinstall. We did not experience any TSM DB corruption, but we had the server running for a very short period of time with almost no activity before we caught the problem and got it fixed. IMHO, IBM should fix their LPP's so that you can not inadvertently install conflicting filesets! Let us know how you make out. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ======= Jim Sporer wrote: We were running TSM server version 5.2.2.4 on an AIX 5.1 machine. Yesterday we moved the TSM server to a new AIX machine running AIX 5.2. We installed TSM server version 5.2.2.4 on the new machine so the only difference was we are running AIX 5.2. We restored the TSM database to the new server and that went ok. We started the server and got message "ANR9613W error loading the ./dsmlicense for licensing function: Exec format error". At that point client nodes could not perform backups because of a licensing issue, ANR0439W was the message we were getting. I did a search on the message ANR9613W at IBM.COM and one of the hits was something about using a down level C library, xlc.rte 5.0.2.1. We are using xlc.rte 6.0.0.0 on the new aix machine. I decided to move the ./dsmlicense file from the old machine to the new machine and when I restarted the TSM server it came up without the error. Has anybody seen anything like this? Jim Sporer
Re: Message ANR9613W
Richard, That doesn't quite explain what happened. I installed TSM on system-new and tried to move from system-old to system-new. When I tried to start system-new, I got the ANR9613W message. I then moved dsmlicense from system-old to system-new and started the server without the error message. I think what I did was what your notes said I shouldn't do and yet it worked. Jim Jim - From my programming notes: Exec format error Typically, you compiled a program on a system running at a higher level of the operating system than the system on which you try to run the program. Unless the special measures are taken when a developer compiles an application, the linker designates some libraries to be bound to the application and loaded with the application only at run time. Many of these libraries change from version to version on AIX. An application compiled on one version of AIX will store pointers to the locations of the functions in the dynamically bound libraries. If the compiled application is moved to a different version of AIX, the functions will not be at the address to which the pointers refer, and the system will send an "Exec format error". My guess would be that the license file is inappropriate to that server. Richard Sims
Message ANR9613W
We were running TSM server version 5.2.2.4 on an AIX 5.1 machine. Yesterday we moved the TSM server to a new AIX machine running AIX 5.2. We installed TSM server version 5.2.2.4 on the new machine so the only difference was we are running AIX 5.2. We restored the TSM database to the new server and that went ok. We started the server and got message "ANR9613W error loading the ./dsmlicense for licensing function: Exec format error". At that point client nodes could not perform backups because of a licensing issue, ANR0439W was the message we were getting. I did a search on the message ANR9613W at IBM.COM and one of the hits was something about using a down level C library, xlc.rte 5.0.2.1. We are using xlc.rte 6.0.0.0 on the new aix machine. I decided to move the ./dsmlicense file from the old machine to the new machine and when I restarted the TSM server it came up without the error. Has anybody seen anything like this? Jim Sporer
Re: Empty Virtual volumes
As long as the volumes have an access mode of OFFSITE they will not return to the scratch pool. Update the access mode to readwrite and the volumes will return to the scratch pool. Jim Sporer At 12:18 AM 9/29/2004 -0500, you wrote: On the dev class? Yes it's two minutes. Should it be increased? ray On Tue, 28 Sep 2004, Coats, Jack wrote: > Is there a retention set? > > -Original Message- > From: -ray [mailto:[EMAIL PROTECTED] > Sent: Monday, September 27, 2004 8:02 PM > To: [EMAIL PROTECTED] > Subject: Empty Virtual volumes > > > Anyone ever seen this? Using virtual volumes, my primary server keeps EMPTY > volumes around... not sure if they are created empty or become empty through > reclamation. Shouldn't they be deleted after reclamataion? Or at > least reused? It's filling up maxscratch on the stgp and causing the > offsite backup to fail. Thanks for any info... > > ray =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Ray DeJean http://www.r-a-y.org > Systems EngineerSoutheastern Louisiana University > IBM Certified Specialist AIX Administration, AIX Support > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > > GABRIEL.BFS.096054236OFFSITE OFFSITE102,400.0 > 87.2 Full > GABRIEL.BFS.096080476OFFSITE OFFSITE 39,008.9 > 87.2 Full > GABRIEL.BFS.096099232OFFSITE OFFSITE 13,074.7 > 95.5 Full > GABRIEL.BFS.096103300OFFSITE OFFSITE102,399.9 > 80.5 Full > GABRIEL.BFS.096120825OFFSITE OFFSITE102,399.9 > 81.7 Full > GABRIEL.BFS.096131325OFFSITE OFFSITE 21,769.1 > 98.2 Full > 0.0 Empty > GABRIEL.BFS.096274546OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096277043OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096277409OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096279634OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096321175OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096321480OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096325921OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096329386OFFSITE OFFSITE 0.0 > 0.0 Empty > GABRIEL.BFS.096332046OFFSITE OFFSITE 0.0 > 0.0 Empty > > ...etc... > -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ray DeJean http://www.r-a-y.org Systems EngineerSoutheastern Louisiana University IBM Certified Specialist AIX Administration, AIX Support =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Gui Admin for 2nd Instance of TSM
Did you run "dsmserv runfile dsmserv.idl" on the second instance of the tsm server? Jim Sporer At 02:46 PM 9/16/2004 -0400, you wrote: Hello, We are setting up a 2nd instance of TSM on the same server. The http is set in the config file to 1581. We can sign into the web gui on the 2nd instance, can use the command line. But, the left hand-side, Server Administration drop down menu is coming up with 'Page cannot be found error'. Any idea's? Background Info: Operating System- AIX, Version 5.1 TSM Server Version 5.2.3 Nancy Backhaus Enterprise Systems [EMAIL PROTECTED] Phone: (716) 887-7979 Cell: (716) 609-2138 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: Relabel of 3592
Have you tried the dsmlabel command with the -overwrite option? Jim Sporer At 06:40 PM 9/16/2004 +0200, you wrote: Hello *SMers, I have some 3494 with 3592 drives, but unfortunately a new set of tapes was sent with the wrong labels. We relabelled the tapes on the outside, but they were also initialised. There is no possibility to "label libv", as some of the labels are already known to the TSM-Server - they overlap with labels in another library. One solution is to erase the tapes with tapeutil - 2 hours per tape, I have 200 of these little bastards. The other solution is to send the tapes back to the supplier. Any other hints to get rid of the label on the tapes? -- Michael PrixUnter den Eichen 7 System Engineer D-65195 Wiesbaden Mobil: +49-151-14738412 Tel: +49-611-18135-34 -- Michael Prix "User brauchen eh keine Programme... die sollen ihre Lochkarten abgeben und danach kriegen sie den Ausdruck ins Fach."
Re: Active / Inactive data script
Troy, I don't know much about sql either but you could get that information by doing a query occupancy for the node. That would give you all of the data stored for that node and then use a export node filedata=allactive preview=yes to determine how much of the data is active. Jim Sporer At 09:57 AM 9/7/2004 -0500, you wrote: What I would like to have is two (hopefully) simple scripts. Both would take a node name as a parameter. One script would return the total amount of active data being held by TSM for that node. The other would return total inactive data for that node. If it could be condensed into one script that would output both pieces of info, all the better. Unfortunately, an SQL scripter I am not. Confidentiality Notice follows: The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. 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. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately by replying to this email. Thank you.
Re: Hey Big Blue....Why not MOVE DATA across copy pools?!?
Have you changed the access mode for the volumes to offsite? Jim At 07:56 AM 6/10/2004 -0400, you wrote: I already performed the move data from the primary pool to another primary pool. I guess TSM cant figure out that the primary copies are in a different primary storage pool than where they were origianlly backed up from. A "DELETE FILES node filespace STG=stgpool" sure would be niceor a "DELETE NODEDATA STG=stgpool". (sigh) Dave Nicholson Whirlpool Corporation "Stapleton, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06/09/2004 10:44 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: Hey Big BlueWhy not MOVE DATA across copy pools?!? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David Nicholson >I tried a MOVE DATA for offsite data...it did not go after the >data in the primary pool...it wanted to mount the volume in the copy >pool...which was offsite. >Am I missing something? Something is wrong. MOVE DATA will only call for offsite volumes if the required files are not available in the primary pool. Do you have volumes in unavailable status? -- Mark Stapleton
Re: D2D backup with TSM
Eric, The fragmentation occurs because of aggregates. The files within the aggregates expire but the space isn't freed up until all the files in an aggregate expire. Jim Sporer At 11:14 AM 6/2/2004 +0200, you wrote: Hi Jim! > I know that this will involve running reclamation on the ATA storage pool but we felt using a DISK device class would waste to much storage because of fragmentation. Why did you think fragmentation was a waste of space? If a file expires, the space it allocated on a diskpool becomes free space, so it shouldn't be considered wasted. I can imagine that when a lot of little files expire, one gets a lot of fragmented free space, which could have impact on the specific disks performance in the long run. Funny to see that a lot of people (including us) are thinking about SATA storage for their backups. There doesn't seem to be anybody with real hands-on experience however... Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Jim Sporer [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 01, 2004 21:37 To: [EMAIL PROTECTED] Subject: Re: D2D backup with TSM We are going to try disk only backups using ATA storage. We've decided to use use a FILE device class for the ATA storage pool and do the backups directly to the ATA storage pool. We will back up the data to a copy storage pool defined on a 3494 tape library. I know that this will involve running reclamation on the ATA storage pool but we felt using a DISK device class would waste to much storage because of fragmentation. Jim Sporer University of Wisconsin At 10:05 PM 5/28/2004 -0400, you wrote: >We recently had a presentation from EMC. During this presentation >they discussed their new DL700 >virtual tape library. It got people talking about a long >term strategy of moving to a all disk based backup system. So we >started thinking of the pros and cons of how to go about setting up TSM >for a disk based backup system. > >Here are some initial thought on ways to configure TSM for D2D >backups. We would be very interested in your thoughts/comments. I >doubt we are the only people thinking about this topic. > >1)Purchase a very large disk system (ata drives?) and put storage pools on >them. > - use a standard DISK device pool for backups > - how to reclaim space? do you even need to? > - fragmentation problems? > - multiple node access concurrently > - use a FILE device based pool > - single node access per disk file volume > - need to run reclamation > - still stage to disk and migrate to FILE device based pool? > - use a tape copy pool for offsite and backup > - use a offsite disk pool somehow > - iscsi over lan or fc if close enough (enough throughput?) > - other? > - must use client compression to get data compressed > - we mostly don't do this today > >2) Purchase a virtual tape system like the DL700 > (bundle of a EMC Clariion and a FalconStor vts appliance) > - provides compression for data > - appliance is responsible for layout and use of disk space > - can copy a virtual tape to a real physical tape for offsite storage > > >Thanks > >Rick ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: D2D backup with TSM
We are going to try disk only backups using ATA storage. We've decided to use use a FILE device class for the ATA storage pool and do the backups directly to the ATA storage pool. We will back up the data to a copy storage pool defined on a 3494 tape library. I know that this will involve running reclamation on the ATA storage pool but we felt using a DISK device class would waste to much storage because of fragmentation. Jim Sporer University of Wisconsin At 10:05 PM 5/28/2004 -0400, you wrote: We recently had a presentation from EMC. During this presentation they discussed their new DL700 virtual tape library. It got people talking about a long term strategy of moving to a all disk based backup system. So we started thinking of the pros and cons of how to go about setting up TSM for a disk based backup system. Here are some initial thought on ways to configure TSM for D2D backups. We would be very interested in your thoughts/comments. I doubt we are the only people thinking about this topic. 1)Purchase a very large disk system (ata drives?) and put storage pools on them. - use a standard DISK device pool for backups - how to reclaim space? do you even need to? - fragmentation problems? - multiple node access concurrently - use a FILE device based pool - single node access per disk file volume - need to run reclamation - still stage to disk and migrate to FILE device based pool? - use a tape copy pool for offsite and backup - use a offsite disk pool somehow - iscsi over lan or fc if close enough (enough throughput?) - other? - must use client compression to get data compressed - we mostly don't do this today 2) Purchase a virtual tape system like the DL700 (bundle of a EMC Clariion and a FalconStor vts appliance) - provides compression for data - appliance is responsible for layout and use of disk space - can copy a virtual tape to a real physical tape for offsite storage Thanks Rick
Re: Database volumes
Look at the "define dbvolume" and "define dbcopy" commands. It looks like you haven't defined the volumes for use by TSM yet or if you did you got some kind of error during the processing of the commands. Jim Sporer At 03:08 PM 12/4/2003 +0100, you wrote: Hi all and thank you in advance for your help We hace a volum group named tsmvg dedicated only to TSM (Database, Recovery log and sorage Poolls. the output of the command : "lsvg -l tsmvg " gives: tsmvg : LV NAME TYPELPs PPs PVsLV STATE MOUNT POINT db1ajfs16 16 1 open/syncd N/A db2ajfs16 16 1 open/syncd N/A db3ajfs16 16 1 open/syncd N/A db4ajfs16 16 1 open/syncd N/A db5ajfs16 16 1 closed/syncd N/A db6ajfs16 16 1 closed/syncd N/A db7ajfs16 16 1 closed/syncd N/A db8ajfs16 16 1 closed/syncd N/A db1bjfs16 16 1 open/syncd N/A db2bjfs16 16 1open/syncd N/A db3bjfs 16 16 1open/syncd N/A db4bjfs 16 16 1open/syncd N/A db5bjfs 16 16 1 closed/syncd N/A db6bjfs 16 16 1 closed/syncd N/A db7bjfs1616 1 closed/syncd N/A db8bjfs1616 1 closed/syncd N/A log1a ... log2a ... log1b ... log2b ... .. but the output of " query dbv" gives only four volumes: db1a, db2a, db3a, db4a and theirs copies (miroring) : db1b, db2b, db3b, db4b (all have LV STATE = open/syncd ). I wonder why volumes db5a,6a,7a,8a and db5b,6b,7b,8b (LV STATE=closed/syncd) don't appear in the output of the command " query dbv !? what's the difference between " open/syncd " and " closed/syncd " Are they database volumes again but desactivated for the moment? Thany you very much for any help Les noms de domaine les moins chers du marché : 6,49 euros HT sur http://www.lycos.fr/pro .
Re: Storage pool util incorrectly reported
What is your maxscratch set to? Jim Sporer At 03:11 PM 11/10/2003 -0600, you wrote: While this error isn't causing any problems on the server, it is setting off our system monitoring agent which is quite irritating. The prime pool is reporting itself to be 100% utilized which it is not and the estimated capacity is at 0% (same thing for the DRM pool). I tried updating the device 3590 with an estimated capacity of 120GB's and restarting TSM, that didn't do it. I must have some option not set so that TSM can't properly calculate this value, what might it be? My other servers are correct, but I can't seem to find the difference between them. Thanks in advance! My environment: TSM 4.2.4.1 for Solaris IBM 3494 library with 4 drives assigned to this server Output of q stg: tsm: TSM3.USSNTC6>q stg Storage Device Estimated Pct Pct High Low Next Stora- Pool Name Class Name CapacityUtil Migr Mig Mig ge Pool (MB) Pct Pct --- ---- - - --- --- ARCHIVEPOOL DISK 0.0 0.0 0.0 90 70 BACKUPPOOL DISK204,000.0 0.0 0.0 0 0 I013590PRIME I013590DRM1 3590 0.0 100.0 I013590PRIME3590 0.0 100.0 81.7 100 99 SPACEMGPOOL DISK 0.0 0.0 0.0 90 70 Michael French Savvis Communications IDS01 Santa Clara, CA (408)450-7812 -- desk (408)239-9913 -- mobile
Re: 3494 Library and dual gripper?
Al, We have the HA feature on our 3494 without dual grippers. Jim Sporer At 02:24 PM 10/24/2003 -0500, you wrote: Our dual gripper is used 6% of the time, but we also have an HA setup (2 accessors) which requires dual grippers. You do lose storage slots at the top and bottom as noted, but the thing I don't understand is why the top 2 slots of the I/O door aren't blocked out like the shelves because the bottom gripper can't reach these either. Just one of those odd observations. -Al Richard Foster <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/24/03 06:58 AM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: 3494 Library and dual gripper? > A dual gripper shaves some seconds off the overall time. It may be worth pointing out that a dual gripper loses you some library tape slots - 10% of them, in fact. The upper gripper cannot reach the lowest 2 slot levels, nor can the lower gripper reach the highest 2 levels. Therefore these 4 levels are lost (and are physically blanked off in our library). It's an open question why IBM chose to do it that way, because it was surely possible to program the control PC to use the appropriate gripper for these levels. Probably that nice warm feeling of redundancy. Richard Foster *** NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential or privileged information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and delete the e-mail and attached documents. Thank you. ***
Re: APAR IC36566 for MVS Server 5.1.7???
Shannon, You don't have control over what TSM writes in the volume history file and TSM thinks it has an lrecl up to 1028. Jim At 03:03 PM 9/16/2003 -0500, you wrote: Hi Jim, Yes I realize that the error is from a record that is too long but what I don't understand is why the Generate Backupset command would be written to the VolHist file in the first place. Since it is not a Volume record I can't figure out what would trigger it to be written to the Volume History. Thanks, Shannon e-mail [EMAIL PROTECTED]
Re: APAR IC36566 for MVS Server 5.1.7???
Shannon, Just a guess, but it looks like the record it is trying to write is longer than 133 bytes and that's causing the error. Jim Sporer At 01:44 PM 9/16/2003 -0500, you wrote: I have 2 questions I cannot find the answer for and I was hoping someone on the list could lead me in the right direction. My environment; TSM Sever 4.2.2MVS OS/390 2.10 2 TSM NW6 Client's 5.1.6.0 1. The first is that I have recently started doing Backup Sets on a few clients(listed above) instead of Archive's. Everything went fine but I started noticing the following error in the TSM Server activity log; ANRD ICVOLHST(4792): ThreadId<280> Error Writing to output File. ANR4510E Server could not write sequential volume history information to 'ADSM.PRT.FILE'. The 'ADSM.PRT.FILE' is one of 2 volhist files I have defined in the TSM Server Options file. This one is defined as; Data Set Name . . . : ADSM.PRT.FILE General Data Volume serial . . . : MVSXXX Device type . . . . : 3390 Organization . . . : PS Record format . . . : FBA Record length . . . : 133 Block size . . . . : 13566 This is what I use for printing a hard copy of the VOLHIST to take offsite once a week. Everytime the Volume History file changes, this file automatically gets updated. I also have another file called ADSM.VOLUME.HIST01defined as; Data Set Name . . . : ADSM.VOLUME.HIST01 General Data Volume serial . . . : MVSXXX Device type . . . . : 3390 Organization . . . : PS Record format . . . : VB Record length . . . : 1028 Block size . . . . : 6144 This is also a VOLHIST file that gets updated every time there is a change but this one is defined so that MVS would be able to read it in if we were to lose a Disk Volume. I should mention we do Full Volume Backups of all our MVS Disk Volumes every evening after the TSM client backups are done. When I looked in the ADSM.PRT.FILE after discovering the above error I find the following; 2003/09/12 02:53:25 STGNEW 0 0 0 CART3590 101060 2003/09/12 02:53:29 STGNEW 0 0 0 CART3590 101037 2003/09/12 03:32:57 STGNEW 0 0 0 CART3590 100778 2003/09/12 03:47:19 STGNEW 0 0 0 CART3590 100753 2003/09/12 04:08:24 STGNEW 0 0 0 CART3590 100998 * generate backupset ENGSNDS ENGSNDS_BACKUPSET SCRATCH=YES DEVCLASS=CART3590 RETENTION= DESC="Create Backupset for ENGSNDS to r Bottom of Data** For some reason TSM is putting the 'Generate Backupset' command line in the Volume History print file. The next time the VOLHIST changed it could no longer write ADSM.PRT.FILE. I deleted the last line and everything was fine again until I issued another Generate Backupset for a different Node client. Again I noticed the errors and the exact same thing happened, the print VOLHIST file was updated with the command while the disk file was not. Does anyone know how or what would cause this? If I continue with Generating Backupsets, I will have to get rid of the ADSM.PRT.FILE and will not be able to print a hard copy for OFFSITE. Besides that, it is just plain strange! 2. This one is for MVS'ers who are at TSM Server 5.1.7. I cannot get the Mainframe system programmer to upgrade my TSM Server because of one APAR IC36566 in which he got the following email response from his IBM Support person; "Action taken: Hi Bruce, It is Boris, I came back from vacation and will take back the pmr. The update from developer is "IC36566 is ready in 5.1.8 and 5.2.1. I will go ahead sysroute it for MVS." I don''t see the APAR is updated or new one opened yet but they are aware that all platforms are effected. I checked when these release will be out for MVS and the timeframe is October. Let me know if you have more concerns. Thanks, Boris Action plan: Waiting for feedback." The system programmer will not put in the new version until he gets a fix PTF for MVS, and I haven't even heard of any other MVSer's having problems with this APAR in the first place. Trying to find something on APAR IC36566 at IBM website is quite a trick, so far I have seen nothing that connects it to the MVS TSM server. In the meantime our department is getting charged by IBM for having 2 versions of TSM Server for MVS(4.2.2 plus 5.1.7) even though we are still only using 4.2.2, and we are paying maintenance for 5.1.7 even though we aren't supported because we are still on 4.2.2. I have been ready for months to upgrade, all the clients are at the 5.1.6 level, I even had a small test environment on our OS/390 that I was able to do a small amount of testing on. Has anyone heard of this APAR affecting an MVS OS/390 TSM Server? If anyone has a
Re: DB restore questions
Geoff, Try adding a TODATE= to the RESTORE command. The manual says the TODATE is required if you want to do a point in time restore with a volume history file. I suspect TSM is trying to read the recovery log to do a roll forward restore with out the TODATE parameter. Jim At 09:43 PM 7/3/2003 -0700, you wrote: Ok, I'm working on a test to restore the DB on my test server. At the moment I've hit a wall and wonder if someone can shed some light. The server is an H50, AIX5.1 TSM 5.1.7, the library is an automated 3494, the drives are fiber attached 3590's. I installed AIX5.1, TSM 5.1.7, which is what was on it before. I've formatted DB and log space. I have the volhist file, devconf, dsmserv.opt and dsmserv.dsk I saved. I did notice the tape drives came up in a different order so I changed the devconf file. I decided to fly by night and create DB and logs with a name I would dream up just in case I was the one who got whacked and someone else needed to do this without much help. Not sure if that is an issue. I put the files back where they belong, the library is available because mtlib commands work. The question is why do I get this output when trying to restore? I looked up the error and it doesn't make sense because the db is formatted and there. The size of the file is large enough, 15GB, to restore a db backup that really has nothing in it except 2 computers I've been backing up to test. # dsmserv restore db vol=U01936 dev=3590 commit=YES ANR7800I DSMSERV generated at 08:09:53 on Jun 4 2003. Tivoli Storage Manager for AIX-RS/6000 Version 5, Release 1, Level 7.0 Licensed Materials - Property of IBM 5698-ISE (C) Copyright IBM Corporation 1999,2002. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR0900I Processing options file dsmserv.opt. ANR7811I Direct I/O will be used for all eligible disk files. ANR8200I TCP/IP driver ready for connection with clients on port 1500. ANR0259E Unable to read complete restart/checkpoint information from any database or recovery log volume. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Version 3 ADMIN GUI
I recently installed TSM server 5.1.6.5 on AIX. Most thing work when I use the version 3 admin GUI but when I click on the Storage Pools icon I get a ANS1026E error message. I know the GUI is no longer supported but I was wondering if anybody else has seen the problem and figured out a way around it. Jim Sporer
Re: EXPORT NODE to SERVER question/issue....
The data does go into the archive pool. The specific archive pool is determined by the policy domain and management class. More info can be obtained in the following redbook. The ADSM Server-to-Server Implementation and Operation redbook goes into this subject. Jim Sporer At 08:45 AM 6/3/2003 -0400, you wrote: H.. Thanks for the details. One question, you specifically said the "data ends up in your archive storage pool as a single file". Is this true about the ARCHIVE pool ? Why the ARCHIVE pool ?Which ARCHIVE pool ?Can I control this ? If this really is true, this is probably the cause of my problem since I have a very SMALL archive pool on the receiving server since I don't do much if any archiving there ! Jim Sporer <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 06/02/2003 05:16 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: EXPORT NODE to SERVER question/issue When you do a server to server export the data ends up in your archive storage pool as a single file. If for some reason the export fails before completion you lose everything. We had some rather large nodes that we exported that took upwards of 10 to 15 hours. We would occasionally have network problems that would require us to start from scratch. To get around the problem we started doing the exports by filespace. Jim Sporer At 04:07 PM 6/2/2003 -0400, you wrote: >I am now on my fourth attempt to do an EXPORT NODE to SERVER, from my zOS >TSM server (5.1.6.4) to our AIX TSM server (5.1.6.2). > >The reason I am on my fourth attempt is that it seems to >quit/drop-dead/whatever for no apparent reason I can fathom. > >The last attempt, while the final status said "SUCCESSFULL", further >digging for an error message found one that said "INCOMPLETE" (not sure >why a previous "failure" still registers as "successfull" but I am not >concerned about this, right now). > >Eventhough each attempt seems to move some data, nothing seems to appear >on the receiving end. > >My question(s): > >1. Where is the stuff being imported/exported going if it doesn't seem >to appear on the other end ? >2. If it actually does send some files across and I run the EXPORT >again, does it just skip the files previously sent ? >3. What if an *EXACT* copy of the file(s) I am export/importing already >exists on the receiving end ? Does it ignore it ?
Re: EXPORT NODE to SERVER question/issue....
When you do a server to server export the data ends up in your archive storage pool as a single file. If for some reason the export fails before completion you lose everything. We had some rather large nodes that we exported that took upwards of 10 to 15 hours. We would occasionally have network problems that would require us to start from scratch. To get around the problem we started doing the exports by filespace. Jim Sporer At 04:07 PM 6/2/2003 -0400, you wrote: I am now on my fourth attempt to do an EXPORT NODE to SERVER, from my zOS TSM server (5.1.6.4) to our AIX TSM server (5.1.6.2). The reason I am on my fourth attempt is that it seems to quit/drop-dead/whatever for no apparent reason I can fathom. The last attempt, while the final status said "SUCCESSFULL", further digging for an error message found one that said "INCOMPLETE" (not sure why a previous "failure" still registers as "successfull" but I am not concerned about this, right now). Eventhough each attempt seems to move some data, nothing seems to appear on the receiving end. My question(s): 1. Where is the stuff being imported/exported going if it doesn't seem to appear on the other end ? 2. If it actually does send some files across and I run the EXPORT again, does it just skip the files previously sent ? 3. What if an *EXACT* copy of the file(s) I am export/importing already exists on the receiving end ? Does it ignore it ?
Re: virtual volumes on target server - when do they go away?
delete filespace nodename ADSM.SERVER type=server That should get rid of the filespace. Jim Sporer At 07:15 PM 6/2/2003 +0200, you wrote: I've been testing a "remote Copypool" setup, and now want to clean up ... As the last thing on the (temporary) source server, I deleted all virtual volumes, and checked via RECONCILE VOLUMES that they were all (logically) gone. On the target server though, I still have the non-empty archive filespace ADSM.SERVER belonging to the source node (TYPE=SERVER), which can't be deleted via DELETE FILESPACE. So far, a few expirations have been run on the target server without changing things. Will the contents of the ADSM.SERVER filespace eventually go away, and if so, when? Wolfgang J. Moeller, Tel. +49 551 201-1516/-1510, [EMAIL PROTECTED] GWDG, D-37077 Goettingen, F.R.Germany |Disclaimer: No claim intended! http://www.gwdg.de/~moeller/ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Tape Library Sharing 2nd Time
Since I didn't get an answer the first time I sent this I assume nobody has ever done it. Does anybody have an opinion on whether it can be done this way or must I copy all of the data? Jim Sporer X-Sender: [EMAIL PROTECTED] X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 18 Mar 2003 15:21:47 -0600 To: [EMAIL PROTECTED] From: Jim Sporer <[EMAIL PROTECTED]> Subject: Tape Library Sharing Cc: JAMES J SPORER <[EMAIL PROTECTED]> I have a 3494 ATL that is shared between two TSM servers. Right now the Library is partitioned, meaning I have a separate set of private and scratch categories for each of the servers. I would like to change the library so one of the TSM servers is the primary library manager. Can I do this using the following steps? 1) Set up server to server communication between the library manager server and the library client server on both TSMs. 2) Update the library manager server library to shared=yes. 3) On the library client TSM checkout all tapes with the remove=no option. 4) delete the 3590 drives on the library client TSM. 5) delete the library on the library client TSM. 6) define the library on the library client TSM (define library libraryname libtype=shared primarylibmanager=primarytsm) 7) define the 3590 drives on the library client. We are running TSM 4.2.1.7. 8) issue the checkin command on the library client for the volumes checked out in step 3. (checkin libvol libraryname status=private checklabel=barcode search=yes) I have a question about step 8. Do I issue the checkin command on the primary library manager or the library client. If I issue the checkin on the primary library manager how does the primary library manager know that the tapes belong to the library client? Jim Sporer
Tape Library Sharing
I have a 3494 ATL that is shared between two TSM servers. Right now the Library is partitioned, meaning I have a separate set of private and scratch categories for each of the servers. I would like to change the library so one of the TSM servers is the primary library manager. Can I do this using the following steps? 1) Set up server to server communication between the library manager server and the library client server on both TSMs. 2) Update the library manager server library to shared=yes. 3) On the library client TSM checkout all tapes with the remove=no option. 4) delete the 3590 drives on the library client TSM. 5) delete the library on the library client TSM. 6) define the library on the library client TSM (define library libraryname libtype=shared primarylibmanager=primarytsm) 7) define the 3590 drives on the library client. We are running TSM 4.2.1.7. 8) issue the checkin command on the library client for the volumes checked out in step 3. (checkin libvol libraryname status=private checklabel=barcode search=yes) I have a question about step 8. Do I issue the checkin command on the primary library manager or the library client. If I issue the checkin on the primary library manager how does the primary library manager know that the tapes belong to the library client? Jim Sporer
Re: Database backup strategy?
Matt, We do a full backup once a week and incrementals every other day. Our full backups take about 2 hours and the incrementals only take an hour or less depending on the activity for that day. If you don't save any time by doing the incrementals then you are better off doing fulls. It takes less time to restore the database from a full than using incrementals. When we first started using incrementals I had it set up to do 30 incrementals and then a full. Wouldn't you know on day 29 we lost the database and I had to restore using 30 tapes. That's when I changed it to weekly. Jim Sporer At 10:49 AM 3/13/2003 -0500, you wrote: I'm curious about the type and frequency of database backups that people do. I've inherited a TSM environment set up by sombeody else and I'm trying to make sense out of it. The original setup did two backups every day, a full and a snapshot. The full stayed onsite and the snapshot went offsite. (We use DRM, and the MOVE DRM * SOURCE=DBS sent the snapshot offsite and left the full alone). That seemed like overkill, so I changed the "onsite" backup to do a full backup on Sunday and an incremental other days. But at two hours for a full backup, and almost as long for an incremental, I'm wondering if we're still spending more time than necessary backing up our database. Does anybody else see the need for two daily backups? I think the likeliihood of a disaster requiring a database restore is so slim that a single offsite copy might be enough, especially since our "offsite vault" is less than a 5-minute walk (which raises another issue, but thats what we're living with). Does anybody mess with full/incremental database backups? Or, if I'm only going to do one backup a day, would it make more sense to do a full every day, to simplify things if I do have a disaster and need to restore? -- Matt Simpson -- OS/390 Support 219 McVey Hall -- (859) 257-2900 x300 University Of Kentucky, Lexington, KY 40506 <mailto:[EMAIL PROTECTED]> mainframe -- An obsolete device still used by thousands of obsolete companies serving billions of obsolete customers and making huge obsolete profits for their obsolete shareholders. And this year's run twice as fast as last year's.
Re: Admin schedules
I don't think the migration was caused by an Admin schedule. Maybe you filled up the storage pool and that caused the migration. Jim Sporer At 12:23 PM 3/10/2003 -0600, you wrote: Environment: Server: RS/6000-AIX5.1 TSM V4.2.1.9 Client: NT4-Service pack 6, Win2k-SP1, TSM V4.2.1.9 Novell - Netware 6 TSM V5.1.5.0 SP2-AIX5.1 TSM V4.2.1.9 Hi *SM'ers , I have an admin schedule setup that does my disk migration to primary tape at 8:15am every day. I had a weird problem with that schedule starting up at 2:35am in the middle of backups. Has anyone else had unexpected results with the TSM admin schedules before? It usually runs fine, Thanks, Tommy Templeton
Re: DB Backup question re: Incremental vs. Full
I've never done that but I wouldn't think it matters. The volhist file keeps track of where these backups are. Jim Sporer At 02:48 PM 2/4/2003 -0500, you wrote: > -Original Message- > From: Alan Davenport > Sent: Tuesday, February 04, 2003 10:54 AM > To: ADSM (E-mail) > Subject: DB Backup question re: Incremental vs. Full > > Hello List, > > I'm relisting this since I goofed the first time. > > I have a question on Incremental database backups. If I take a > full database backup to device class "A" one day can I take an INCREMENTAL > backup to device class "B" the next day or must the incremental backup go > to the same device class as the full backup? > > TSM 5.1.5.4 on OS/390. > > Alan Davenport > Senior Storage Administrator > Selective Insurance Co. of America > [EMAIL PROTECTED] > (973) 948-1306 >
Re: label/checkin libvolume
Can't you just do a checkout with remove=no and then label the tapes? Jim Sporer At 01:16 PM 1/13/2003 -0800, you wrote: > -Original Message- > From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 13, 2003 11:58 AM > To: [EMAIL PROTECTED] > Subject: Re: label/checkin libvolume > > Well, TSM doesn't want to label them while they are PRIVATE > and TSM doesn't > really know what is going on... > You might be able to do a del vol against them to get them > back to scratch, > then do your label libvol Dwight- Thank you for the reply. I did try deleting them, but they are not part of a storage pool, so they cannot be "deleted" (and there is no "delete libvolume" command). I updated a couple of the volumes to scratch, just as a test. After updating them, I tried: "label libvol search=yes checkl=barcode checkin=scr overwrite=yes volrange=,". However, TSM reports 0 volumes labelled and exits with "Success". The only other thing I can think to do is to go to the library and physically remove them. Once removed, audit the library to show TSM that they are no longer in the library. Then, load them back in and check them in correctly. Any other ideas? Thanks. Peter
Re: OSX Mac Client Question
Yes, IBM does have a ways to go with the Tivoli Storage Manager client for Mac OS X. It does work, and the last couple updates have taken care of very critical problems. The major problem that remains is that the Scheduler (which is the agent that communicates with the server and facilitates scheduled backups) is an interactive application and cannot run in the background. This means that you have to be logged in at the console as an admin user in order for the Scheduler to work. If this is the type of machine where there's only one or two admins, and you're comfortable using something like a screensaver password to protect the console, then TSM can work quite well. The reason for this issue is that IBM essentially carbonized the old Mac OS version, keeping the single user paradigm. The client is being completely rewritten by IBM, and a version that has a scheduler capable of running as a background process will be available this year. Jim Sporer At 04:00 PM 1/13/2003 +, you wrote: Hi TSMers I've just installed the latest client release for a Mac OSX machine. I can run backups/restores no problem and can run the scheduler manually. When I run the scheduler as a daemon though, the dsmsched.log file shows that the daemon contacted the server for the next schedule, but then it says 'Scheduler stopped'. Is this correct? I would expect to see something like 'Schedule will be refreshed in 1 hour'. Anyone out there have experience with the OSX clients? Thanks Farren Minns - John Wiley & Sons Ltd
Re: K-cartridges besides J-cartridges
There is a difference between the J and K tapes and the 3590 drives need to support the extended length tapes. If the drives are new there is no problem but older 3590E drives may need an upgrade to support the extended length tapes. Check with your CE. Jim Sporer At 11:12 PM 12/10/2002 +0100, you wrote: Hello, AIX 5.1, TSM 4.2.1.19, IBM 3494 library, 3590E-drives At the moment we use about 900 J-cartridges in our library. Is it possible to checkin K-cartridges and use them besides the J-cartridges. During upgrade from our drives from 3590B to 3590E we changed status of our volumes to read-only because of different tracks used on tape. As far as I know is the only difference between J and K the length of the tape, so I guess there will be no problem. I'm wondering if someone is using both J and K cartridges and if there encounter any problems. Thanx, Brian. _ Chatten met je online vrienden via MSN Messenger. http://messenger.msn.nl/
Re: Netware 6 and web interface issues
Zoltan, If this netware client was defined a very long time ago, it may not have an administrative client defined for it which is required for web interface. Administrative clients are now automatically created when the node is defined but that wasn't always the case. Jim Sporer At 04:41 PM 11/14/2002 -0500, you wrote: First attempts at installing and using 5.1.5 client on a Netware 6 server. Trying to use the web interface for backups. Wont show what is on the drives and keeps getting an error. Checked the logs and found: 11/14/2002 16:22:02 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:02 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:06 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:06 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:08 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:08 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:14 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:14 ANS1876E Unable to connect to target service. NetWare SMS return code = . 11/14/2002 16:22:21 Error -50 sending ht request 11/14/2002 16:22:21 Error writing to http socket. Also, my server (z/OS V4.2.2.13) keeps recording: 11/14/2002 4:23:18 PM ANR0423W Session 8346 for administrator SYSOP ( ) refused - administrator name not registered. 11/14/2002 4:27:38 PM ANR0423W Session 8388 for administrator CSERVE3.VCU.EDU ( ) refused - administrator name not registered. What gives with the ( ) and the SYSOP stuff since that is not what is being used for an administrator ID ?? I did check the ADSM.ORG archives for the ANS1876E message and only found references to V5 Netware servers. I did mention to the Novell person about the TSA libraries but they are supposed to be up to date Any suggestions ?
Re: restore hangs
Your Q SE command shows it has only been in the recvW state for 2 seconds. Are you sure it isn't doing anything? Jim Sporer At 12:56 PM 10/29/2002 -0600, you wrote: I'm probably annoying the hell out of you all, but I'm really stuck, and I need someones help. Running ADSM serv 3.1 on AIX 4.3.3 with 3575 tape library. I'm trying to restore a filesystem. I first tried running dsm on the client, the process starts, and it starts restoring the directory structure (or whatever its doing), but after a minute or two it just hangs. The restore is not active anymore, and it changes its state to "restorable", and the Sess State changes from Run to RecvW: adsm> q se Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 2 Tcp/Ip Run 0 S 697.2 K 102 Admin AIX ALAZAREV 1,572 Tcp/Ip Run 0 S4.7 K 421 Admin AIX ALAZAREV 1,573 Tcp/Ip RecvW2 S2.2 M 615 Node AIX HERA.ITG.UIUC.EDU adsm> q rest SessRestoreElapsedNode NameFilespace NumberState Minutes Name --------- --- -1Restartable 2HERA.ITG.UIUC.EDU /home/mac/- tate Now, from previous posts help, I also tried using the incremental restore. On the client command line I ran the following command: #dsmc restore "home/mac/tate/*" -replace=no -subdir=yes This has the exact same result as the other restore. It goes for a minute or two and then it hangs, and becomes a restartable session with a state of RecvW. BTW, the dsmadmc -console windows shows absolutetly NO errors. It puts two tapes into the drives, takes them out, then just sits there. NO errors! Does anyone have any ideas? If I should give more info please let me know. I'm totally stuck, and everyone is getting pissed at me. Thanks in advance, Alex ------ Alex Lazarevich | Systems | Imaging Technology Group [EMAIL PROTECTED] | (217)244-1565 | www.itg.uiuc.edu ------
Re: Help deleteing filespace
Try, delete filespace itgc2ashare 4 nametype=FSID or this delete filespace itgc2ashare \\itcf2ashare\c$ nametype=unicode There is an apar open about the server not being able to recognize unicode filespace names. Not sure if the problem is fixed or not. Jim Sporer At 10:29 AM 10/28/2002 -0500, you wrote: Hello! I need some assistance in deleteing 2 filespaces. Here is what I see: If I do a 'q filespace itgc2ashare f=d' I get the following results: Node Name: ITGC2ASHARE Filespace Name: \\itgc2ashare\c$ Hexadecimal Filespace Name: FSID: 1 Platform: WinNT Filespace Type: NTFS Is Filespace Unicode?: No Capacity (MB): 7,797.1 Pct Util: 50.2 Last Backup Start Date/Time: 10/27/2002 17:30:27 Days Since Last Backup Started: 1 Last Backup Completion Date/Time: 10/27/2002 17:34:11 Days Since Last Backup Completed: 1 Last Full NAS Image Backup Completion Date/Time: Days Since Last Full NAS Image Backup Completed: Node Name: ITGC2ASHARE Filespace Name: \\itgc2ashare\d$ Hexadecimal Filespace Name: FSID: 2 Platform: WinNT Filespace Type: NTFS Is Filespace Unicode?: No Capacity (MB): 165,591.8 Pct Util: 60.7 Last Backup Start Date/Time: 10/27/2002 17:34:07 Days Since Last Backup Started: 1 Last Backup Completion Date/Time: 10/27/2002 18:37:08 Days Since Last Backup Completed: 1 Last Full NAS Image Backup Completion Date/Time: Days Since Last Full NAS Image Backup Completed: Node Name: ITGC2ASHARE Filespace Name: SYSTEM OBJECT Hexadecimal Filespace Name: FSID: 3 Platform: WinNT Filespace Type: NTFS Is Filespace Unicode?: No Capacity (MB): 0.0 Pct Util: 0.0 Last Backup Start Date/Time: Days Since Last Backup Started: Last Backup Completion Date/Time: Days Since Last Backup Completed: Last Full NAS Image Backup Completion Date/Time: Days Since Last Full NAS Image Backup Completed: Node Name: ITGC2ASHARE Filespace Name: \\itcf2ashare\c$ Hexadecimal Filespace Name: 5c5c69746366326173686172655c 324 FSID: 4 Platform: WinNT Filespace Type: NTFS Is Filespace Unicode?: Yes Capacity (MB): 7,993.3 Pct Util: 57.3 Last Backup Start Date/Time: 10/20/2002 17:31:23 Days Since Last Backup Started: 8 Last Backup Completion Date/Time: 10/20/2002 17:40:49 Days Since Last Backup Completed: 8 Last Full NAS Image Backup Completion Date/Time: Days Since Last Full NAS Image Backup Completed: Node Name: ITGC2ASHARE Filespace Name: \\itcf2ashare\d$ Hexadecimal Filespace Name: 5c5c69746366326173686172655c 424 FSID: 5 Platform: WinNT Filespace Type: NTFS Is Filespace Unicode?: Yes Capacity (MB): 165,372.2 Pct Util: 49.9 Last Backup Start Date/Time: 10/20/2002 17:34:49 Days Since Last Backup Started: 8 Last Backup Completion Date/Time: 10/20/2002 18:22:02 Days Since Last Backup Completed: 8 Last Full NAS Image Backup Completion Date/Time: Days Since Last Full NAS Image Backup Completed: But, when I try and delete the filespace with name "\\itcf2ashare\c$" or " \\itcf2ashare\d$" Commd: delete filespace itgc2ashare \\itcf2ashare\c$ I get the following: ANR0852E DELETE FILE
Re: Export/Import with virtual volumes
On TEST2 issue the command DELETE FILESPACE TEST1 * TYPE=SERVER Jim Sporer At 02:51 PM 9/27/2002 -0400, you wrote: >I've been playing around with export/import using server-2-server virtual >volumes with some success. We have be migrating one of our clients off OS390 >to AIX TSM server..so I wanted to be prepared. > >I was able to export from TEST1 to TEST2, and then import into TEST2 with no >problems. But now I want to delete the virtual volumes since I'm done with >them. I did a DEL VOLH T=EXPORT TOD=TODAY and it reported that 2 volumes >were deleted. But when I query on TEST2 I still see the archive objects in >the storage pool. The DEL VOLH seems to have removed the Volumehistory >records, but didn't delete the archive objects. > >I ran RECONCILE VOLUMES and it said no problems. I ran EXPIRE INVENTORY on >both servers and nothing was expired. > >How do I make sure that the archive objects related to the export volumes >are deleted from the TEST2 server? > >Bill Boyer >DSS, Inc.
Re: TSM Encryption
Hello Jim Follow up question, Can you ask if there is anyway for us to get clients that do stronger encryption, eg tripledes? If not, are there plans in the future to offer strong encryption? This relates to the HIPAA requirements that are coming. Thanks again. Jim Sporer At 10:32 AM 9/26/2002 -0700, you wrote: >Jim, > >The TSM Backup/Archive client uses 56-bit DES encryption. > >Thanks, >Jim Smith >TSM Development > > >>> >Does anyone know what level of encryption is done when using the INCLUDE >ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? >Jim Sporer >[EMAIL PROTECTED]
Re: TSM Encryption
Jim, Thanks for the info. Jim Sporer At 10:32 AM 9/26/2002 -0700, you wrote: >Jim, > >The TSM Backup/Archive client uses 56-bit DES encryption. > >Thanks, >Jim Smith >TSM Development > > >>> >Does anyone know what level of encryption is done when using the INCLUDE >ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? >Jim Sporer >[EMAIL PROTECTED]
TSM Encryption
Does anyone know what level of encryption is done when using the INCLUDE ENCRYPTION option in your dsm.opt file? Is it DES, triple DES or what? Jim Sporer [EMAIL PROTECTED]
Re: Moving Stgpools question
Set the pool you want to move the data to as the next storage pool and then use migration to move the data to that pool. Jim Sporer At 12:50 PM 8/29/2002 -0400, you wrote: >I have several storage pools in my environment and I would like to consolidate >them all into one storage pool (same dev type). My question is , is there any >easy way to do this or do I have to do a "move data $volume >stg=newstgpool" for >each volume of every storage pool? I guess I could write a script to do it >but I >was hoping there was a was to move a full storage pool with one commandAny >help would be appreciated.. > >Dave Gratton >IBM Global Services
ANR8376I Message
When I do a Query Mount command I get two ANR8376I messages about mount points reserved in device class: status: RESERVED. We are running TSM version 4.2.1.7 and using a 3494 that we are sharing between two TSM servers. I was curious if somebody knows what that message means. We have 6 3590 tape drives and in spite of getting that message on one of the TSM servers I can still use all 6 tape drives on the other TSM server, so how can two tape drives be reserved on the other TSM server? Jim Sporer
Re: Mac OS X client
This is what UC Berkeley thinks about the new client. http://wssg.berkeley.edu/public/tsm_osx_issues.html Jim Sporer At 02:16 PM 6/12/2002 -0600, you wrote: >*SMers, > >Well, I haven't seen a lot of flames about the TSM 5.1 Mac OS X client at >this ADSM/TSM Forum Listserv, and frankly, I'm surprised. > >I have an undergraduate computer science student working summers here for >us, who does web development, and knows his way around Mac OS in >general. Here's what he proposes for our "disclaimer" for the the Mac OS >X client before releasing it to our Mac population. I'm pretty astounded >that IBM/Tivoli let this one out the door: > > More Information Regarding the TSM Client for Mac OS X > > Before you download the TSM Client for Mac OS X, please read > more in-depth information about the shortcomings of the Client. > > The Scheduler May Not Work > We have had mixed success with running the Scheduler for Mac OS > X. Sometimes it will work and sometimes it will not. To make sure that your > computer backs up correctly, we recommend that you backup your > computer manually. > > So, now that you have to run manual backups, there is something > you need to know about that as well... > > You Will Always Be Asked for an Administrator Password > The TSM Client is going to require your Administrator name and > password every time you run it. Why is this? Well, the TSM Client runs as a > root process in order to backup all the files on your computer > properly (running as a root process means that the TSM Client does not > have to deal > with file permissions among other things). The way Mac OS X > allows for a program to run as a root process is to ask the user for an > Administrator password every time a program wants to run as a > root process. Thus, you get asked for that password every time you run the TSM > Client. It's crummy, we know. Hopefully this will be fixed in a > later release of the TSM Client for OS X. > > And last but not least, there are some serious problems with > the OS X client... > > Filenames Greater Than 32 Characters Will Not be Backed Up > The OS X TSM Client will NOT backup files that have names > longer than 32 characters. Make sure that all your important documents have > filenames that are 32 characters or less (that includes any > file extensions like .txt). > > Filenames with Special Characters Will Not be Backed Up > Also, the OS X TSM Client will NOT backup files that have > special characters in them. This means that files with accents, umlauts, > tildes, and > the like in their name will not be backed up. For example, a > file named "Piñon Forest Pictures" will not be backed up. Make sure that your > important documents do not have special characters in their names. > > The System Directory Will Not be Backed Up > The OS X TSM Client will not backup Mac OS X's System > directory. This means that if something happens to your OS X System > directory or any > of the files in it, you must reinstall Mac OS X to restore > files in the System directory to proper working condition. Make sure that > any important > documents are not saved in the System directory. > > If you still wish to use the Mac OS X TSM Client, please > proceed to the download page. > >=== > >I wonder if any others out there have had similar experiences, and >further, whether IBM/Tivoli intends to address these problems? > >Thanks. Regards to all. John Bremer
Re: how can I setup a admin account which only allow three commands
Julie, You could set up scripts that initiate dsmadmc to do the commands. Jim Sporer At 11:14 AM 5/9/2002 +1000, you wrote: >Dear all, > >Question 1: >I need setup a admin account which only allow our new operator to run only >three commands: > q req > checki vol > checko vol > reply # > >However, the lowerest authority with the above commands must be used. > > >Any comments will be appreciated > >Thanks in advance > > >Julie Xu > >Unix/Network Administrator >Information Technology Directorate >University of Westen Sydney, Campbelltown >Campbelltown NSW 2560 > >Phone: 61 02 4620-3098 >Mobile: 0416 179 868 >Email: [EMAIL PROTECTED]
Re: ANS1312E
Joni, I would do a Q volume * access=unav to see if you have any tapes marked unavailable. If so change them to read/write and try the backup again. Jim Sporer At 01:26 PM 4/23/2002 -0400, you wrote: >Hello! > >I was notified that a server's file backup that was going directly to tape >was getting the following error messages: > > Node Name: CHSU087 >Session established with server ADSMB: MVS > Server Version 4, Release 1, Level 3.0 > Server date/time: 04/22/02 20:46:23 Last access: 04/22/02 20:44:49 > >Normal File--> 104,865,792 /u05/oradata/p31a/admi01a.dbf ** >Unsuccessful ** >ANS1114I Waiting for mount of offline media. >Retry # 1 Normal File--> 104,865,792 /u05/oradata/p31a/admi01a.dbf >** Unsuccessful ** >ANS1228E Sending of object '/u05/oradata/p31a/admi01a.dbf' failed >ANS1312E Server media mount not possible > >I was also viewing the activity log and I saw the following error messages: > >04/23/2002 13:08:54 ANR0525W Transaction failed for session 64616 for >node >CHSU087 (SUN SOLARIS) - storage media inaccessible. > >04/23/2002 13:08:54 ANR0525W Transaction failed for session 64614 for >node >CHSU087 (SUN SOLARIS) - storage media inaccessible > >The tape drives were not all in use. The system was not in tape drive >allocation. And the maximum mount point is 10. Does anyone have any >suggestions as to what may be done? The customer has tried several times >to backup this file without success. One last question: How do I know >what tape a file is on? Is there a query that could tell me, for example, >what tape the above file would be located on? > >Thank you in advance for any help > >Joni Moyer >Associate Systems Programmer >[EMAIL PROTECTED] >(717)975-8338
Re: downlevel client code - has anybody found a workaround?
Gretchen, I had a similar problem and reported it tsm support. They said I should contact TSM support and they could fix the problem by patching the TSM database. Not a very elegant solution. It has something to do with the 4.2.1 client and unicode support I believe. Jim Sporer At 09:46 AM 4/8/2002 -0400, you wrote: >Server: v4.2.1.11 (AIX 4.3.3) >Client: v4.2.1.0 (Win2K), and later patch levels as well > >I am getting hit hard by the problem with the Windows client >(or is it a server problem?) resetting the platform and the >version so that an earlier operating system can't access the >account. > >Case 1: Client backs up Win2K box with current TSM client, >decides to revert back to Win98 with the same client, but >can't access the data because the operating system is not >as current (perceived by the server as being downlevel). > >Case 2: Client backs up a Mac with a current TSM client, >administrator is asked to restore files, but uses a Win2K >box to 'impersonate' the Mac (which they thought was a >Windows box) to get the files. Mac can no longer access >the account, because it is now downlevel. > >Case 3: Dual boot Win2K/Linux box, client backs up Linux >side first, then does Win2K, goes back to Linux and gets >the downlevel message. > >Note that cases 2 and 3 are *not* trying to do a cross >platform restore. In case 2, it was a mistake by the >admin, and in case 3, it is our policy to use one account >for one computer - less 'stuff' to remember. This is >going to be a huge problem for us. Looking through the >archives, I haven't seen anybody's resolution to this. >Other than exporting, deleting and importing the node >in case 2 (who needs to do an emergency restore), I can't >see a way out of this. > >Is this 'working as designed'? It never used to be this >awkward. Any ideas? > >Gretchen Thiele >Princeton University
Re: Multiple TSM Servers on Same Machine
Thanks Becky and Kelly for the info. Kelly, why would I need san attached drives for option 2, if both TSM servers are running on the same machine? Jim At 04:49 PM 3/14/2002 -0600, you wrote: >We ran option 1 for a long time both with twintailed scsi and a san but have >now mostly switched to option 2. We shared all of the drives and frequently >ran into problems where tsmsvr1 had a drive and tsmsvr2 tried for awhile to >use it and then marked it unavailable until I marked it online. With 1 you >definitely need different catagories and you have to be careful. It makes >it easier if you use 100's for one and 200's for the other because I want to >say the number above the scratch is automatically saved for the same systems >private or vice versa and it can get you in trouble. The best explaination >I have run into on how to set up the library manager is in the LTO Open >Redbook and you just modify what you need for 3494. > >Good luck >Becky > >-Original Message- >From: Kelly J. Lipp [mailto:[EMAIL PROTECTED]] >Sent: Thursday, March 14, 2002 4:28 PM >To: [EMAIL PROTECTED] >Subject: Re: Multiple TSM Servers on Same Machine > > >Two ways to set this up: > >1. Two separate TSM server sharing the library: use different categories and >be careful. >2. Have one of the servers act as the library manager. The second asks the >first for resources and tape mounts, etc. The first server knows about all >of scratch volumes, same categories. See library sharing documentation. >You also need a license for this option. > >Option 1 with the 3494 is probably the way to go. Unless you have SAN >attached drives. Then use 2 so you can share the drives between the two >servers. > >IMHO. > >Kelly J. Lipp >Storage Solutions Specialists, Inc. >PO Box 51313 >Colorado Springs, CO 80949 >[EMAIL PROTECTED] or [EMAIL PROTECTED] >www.storsol.com or www.storserver.com >(719)531-5926 >Fax: (240)539-7175 > > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of >Jim Sporer >Sent: Thursday, March 14, 2002 3:16 PM >To: [EMAIL PROTECTED] >Subject: Multiple TSM Servers on Same Machine > > >I am in the process of setting up a second TSM server on the same >machine. I was curious if there are others doing that with a 3494 >ATL. From what I can tell you can share the 3494 atl resources between >the two servers, meaning the tapes and the drives by specifying a >primarylibrarymanager. Do you use the same scratch and private categories >for the tapes used by both servers? >Jim Sporer
Multiple TSM Servers on Same Machine
I am in the process of setting up a second TSM server on the same machine. I was curious if there are others doing that with a 3494 ATL. From what I can tell you can share the 3494 atl resources between the two servers, meaning the tapes and the drives by specifying a primarylibrarymanager. Do you use the same scratch and private categories for the tapes used by both servers? Jim Sporer
Re: TSM 5.1
Matt, No, that isn't what it does, but it would be more useful if it worked that way. Jim Sporer At 03:01 PM 3/12/2002 -0500, you wrote: >Can it be used to do both a MIGRATE and a COPY? Ie, as it moves from disk >to tape, it is also writing to a 2nd tape that is a part of the COPYPOOL >which will go offsite? That would make it more in line with other >mainframe copy products. Dual write, one for onsite and one for offsite. >Matt > >-Original Message- >From: Andy Carlson [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, March 12, 2002 2:07 PM >To: [EMAIL PROTECTED] >Subject: Re: TSM 5.1 > >#2 is not the panacea that it sounds like. The dual writes to the >copypool's happens during session data transfer to disk pool - thus, you >must have a tape drive per session doing the dual write. > >Andy Carlson |\ _,,,---,,_ >[EMAIL PROTECTED]ZZZzz /,`.-'`'-. ;-;;,_ >BJC Health System |,4- ) )-,_. ,\ ( `'-' >St. Louis, Missouri'---''(_/--' `-'\_) >Cat Pics: http://andyc.dyndns.org/animal.html > >On Tue, 12 Mar 2002, Richard L. Rhodes wrote: > > > We had a meeting with IBM last week where they described some of the > > new features of 5.1 - coming within a few weeks. > > > > 1) multi session restore > > 2) simultaneous writes to copy pools (more than one) > > 3) a "move nodedata" command > > 4) lan-free backup/restore (I thought it already had this) > > 5) hpux lan-free > >
Re: License registration in TSM V4
No, I didn't. Jim At 04:24 PM 1/15/2002 -0500, you wrote: >Did you have to restart the TSM server in order to do this? > >-Original Message----- >From: Jim Sporer [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, January 15, 2002 12:31 PM >To: [EMAIL PROTECTED] >Subject: Re: License registration in TSM V4 > > >I just deleted the nodelock file and then reran all of my register license >commands and everything was ok. >Jim Sporer > >At 10:33 AM 1/15/2002 -0500, you wrote: > >I tried doing this but then got an error message in the actlog (and no new > >licenses registered) saying that I have an invalid license file. > > > >-Original Message- > >From: Seay, Paul [mailto:[EMAIL PROTECTED]] > >Sent: Tuesday, January 15, 2002 1:55 AM > >To: [EMAIL PROTECTED] > >Subject: Re: License registration in TSM V4 > > > > > >Just delete the extras from: > >/usr/tivioli/tsm/server/bin/nodelock > > > >It may require a server cycle. I have never done this before, but seem to > >remember someone saying do this. I think you can actually delete the file > >and redo it if you want. > > > >-Original Message- > >From: Kleynerman, Arthur [mailto:[EMAIL PROTECTED]] > >Sent: Monday, January 14, 2002 3:22 PM > >To: [EMAIL PROTECTED] > >Subject: License registration in TSM V4 > > > > > >Hello all, > > > >I accidentally registered more licenses than needed and I would like to >know > >whether there is a way to undo that. Any help is appreciated. > > > >Thanks, > >Arthur > > > > > >--- > > > >The information contained in this e-mail message, and any attachment > >thereto, is confidential and may not be disclosed without our express > >permission. If you are not the intended recipient or an employee or agent > >responsible for delivering this message to the intended recipient, you are > >hereby notified that you have received this message in error and that any > >review, dissemination, distribution or copying of this message, or any > >attachment thereto, in whole or in part, is strictly prohibited. If you > >have received this message in error, please immediately notify us by > >telephone, fax or e-mail and delete the message and all of its attachments. > >Thank you. > > > >Every effort is made to keep our network free from viruses. You should, > >however, review this e-mail message, as well as any attachment thereto, for > >viruses. We take no responsibility and have no liability for any computer > >virus which may be transferred via this e-mail message. > > >--- > >The information contained in this e-mail message, and any attachment >thereto, is confidential and may not be disclosed without our express >permission. If you are not the intended recipient or an employee or agent >responsible for delivering this message to the intended recipient, you are >hereby notified that you have received this message in error and that any >review, dissemination, distribution or copying of this message, or any >attachment thereto, in whole or in part, is strictly prohibited. If you >have received this message in error, please immediately notify us by >telephone, fax or e-mail and delete the message and all of its >attachments. Thank you. > >Every effort is made to keep our network free from viruses. You should, >however, review this e-mail message, as well as any attachment thereto, >for viruses. We take no responsibility and have no liability for any >computer virus which may be transferred via this e-mail message.
Re: License registration in TSM V4
I just deleted the nodelock file and then reran all of my register license commands and everything was ok. Jim Sporer At 10:33 AM 1/15/2002 -0500, you wrote: >I tried doing this but then got an error message in the actlog (and no new >licenses registered) saying that I have an invalid license file. > >-Original Message- >From: Seay, Paul [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, January 15, 2002 1:55 AM >To: [EMAIL PROTECTED] >Subject: Re: License registration in TSM V4 > > >Just delete the extras from: >/usr/tivioli/tsm/server/bin/nodelock > >It may require a server cycle. I have never done this before, but seem to >remember someone saying do this. I think you can actually delete the file >and redo it if you want. > >-Original Message- >From: Kleynerman, Arthur [mailto:[EMAIL PROTECTED]] >Sent: Monday, January 14, 2002 3:22 PM >To: [EMAIL PROTECTED] >Subject: License registration in TSM V4 > > >Hello all, > >I accidentally registered more licenses than needed and I would like to know >whether there is a way to undo that. Any help is appreciated. > >Thanks, >Arthur > > >--- > >The information contained in this e-mail message, and any attachment >thereto, is confidential and may not be disclosed without our express >permission. If you are not the intended recipient or an employee or agent >responsible for delivering this message to the intended recipient, you are >hereby notified that you have received this message in error and that any >review, dissemination, distribution or copying of this message, or any >attachment thereto, in whole or in part, is strictly prohibited. If you >have received this message in error, please immediately notify us by >telephone, fax or e-mail and delete the message and all of its attachments. >Thank you. > >Every effort is made to keep our network free from viruses. You should, >however, review this e-mail message, as well as any attachment thereto, for >viruses. We take no responsibility and have no liability for any computer >virus which may be transferred via this e-mail message.
V4.2.1.7 Hanging
We have been running the v4.2.1.7 version of the TSM server for about a month. A couple of weeks ago we started experiencing server hangs and were able to determine that a particular Query Event command was causing the hang. The query is a rather complicated query that is generated by a Perl script scheduled by kron. We have been running the script for several years and it has never caused a problem before. We took the script out of kron and ran it manually and it worked just fine. I reported the problem to TSM Support but was wondering if anyone else was experiencing server hangs with the V4.2.1.7 code? Jim Sporer
Re: Moving Log Volumes on 3.1
Stu, Sure you can do that. Format the new volume you want to use for the database, then add the volume to the data base and extend it. Delete the current volumes one at a time by reducing the data base by the size of the volume you are deleting and then just delete it. TSM will move the data off the volume before deleting it. Use the same procedure for the log files. Jim At 12:01 PM 1/3/2002 -0500, you wrote: >Jim > >Can I create one volume for each through this process? I understand that I >need to have equiv. or better size for the new volumes prior to mirroring, >but there are currently 4 log volumes and 3 database volumes. I want to >amalgamate them and have one of each properly sized, then mirror, then >delete the originals and then recreate and mirror just the one volume of >each. > >Make sense? I think it does to me ;o) > >Stu > >-----Original Message- >From: Jim Sporer [mailto:[EMAIL PROTECTED]] >Sent: Thursday, January 03, 2002 11:41 AM >To: [EMAIL PROTECTED] >Subject: Re: Moving Log Volumes on 3.1 > > >Stu, >Creating mirrors is good way to move your log volumes and database. Format >your log volumes, the same size as your current logs, then add them as >mirrors. When the log volume mirror is in synch you can delete the current >log volumes. >Jim Sporer > >At 02:29 PM 12/26/2001 -0500, you wrote: > >Hi > > > >I have recently taken over an ADSM implementation. It is not configured >the > >way I believe it should be and I want to make some adjustments. At some > >point I hope to have the necessary funds to upgrade the version too as I > >believe we are out of date here. > > > >Anyhow, I have ADSM 3.1 at level 2.9 and a configuration such that I have > >logs and database on same hard drive. I have another hard drive I wish to > >put in the machine and ultimately want to end up with some semblance of > >correct configuration. I wish to have a duplicate copy of DB and logs on > >both hard drives. At present there is no ADSM mirroring set up and such, >if > >I can move the logs I think I'm golden. > > > >My question therefore, is how I go about moving the log volumes safely > >without jeopardising the installation. Once they are moved I will >implement > >a mirror of the respective DB/LOGS on the opposing disks. > > > >Any and all help is appreciated. > > > >Thanks > > > >Stu
Re: Moving Log Volumes on 3.1
Stu, Creating mirrors is good way to move your log volumes and database. Format your log volumes, the same size as your current logs, then add them as mirrors. When the log volume mirror is in synch you can delete the current log volumes. Jim Sporer At 02:29 PM 12/26/2001 -0500, you wrote: >Hi > >I have recently taken over an ADSM implementation. It is not configured the >way I believe it should be and I want to make some adjustments. At some >point I hope to have the necessary funds to upgrade the version too as I >believe we are out of date here. > >Anyhow, I have ADSM 3.1 at level 2.9 and a configuration such that I have >logs and database on same hard drive. I have another hard drive I wish to >put in the machine and ultimately want to end up with some semblance of >correct configuration. I wish to have a duplicate copy of DB and logs on >both hard drives. At present there is no ADSM mirroring set up and such, if >I can move the logs I think I'm golden. > >My question therefore, is how I go about moving the log volumes safely >without jeopardising the installation. Once they are moved I will implement >a mirror of the respective DB/LOGS on the opposing disks. > >Any and all help is appreciated. > >Thanks > >Stu
Re: Incremental forever -- any problems?
He must be talking about the TSM database. Jim At 10:19 AM 12/18/2001 -0500, you wrote: >??? Wrong. TSM does not take full backups automatically. > >-Original Message- >From: prakash mathur [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, December 18, 2001 12:08 AM >To: [EMAIL PROTECTED] >Subject: Re: Incremental forever -- any problems? > > >Hi >As per documents you can take 32 incremental backups only and if you keep on >taking incremental after that 33rd backup is > >taken as full automatically. Even if you have not taken full backup it is >taken by default. > >P.C.Mathur > > >From: Jeff Bach > > >Reply-To: "ADSM: Dist Stor Manager" > >To: [EMAIL PROTECTED] > >Subject: Re: Incremental forever -- any problems? > >Date: Mon, 17 Dec 2001 13:20:06 -0600 > > > >Once you have the basics covered (bare-metal, disaster recovery, make sure > >to keep the correct data) > > > >To restore faster, goals should be > > > >1. Multiple threads (how can I use 5 tape drives restoring data at > >once) > > Solutions: two copies of all data, break up client > >restore, multithreaded API restore, increase amount of hardware, >collocation > >by filespace > >2. Minimize time WAITING for tape mounts and spinning through tapes. > > Solutions: collocation by node, full backups, > >separate data into separate storage pools > >3. Eliminate database bottle necks > > Solutions: Increase database cache, spread across > >more spindles, create separate database instances, more paths to spindles > >4. Push the throughput bottleneck down to the client > > Solution: cache data to disk, bigger server, Gigabit > >ethernet on server, switched network, multiple threads on restore > > > >Jeff Bach > >Home Office Open Systems Engineering > >Wal-Mart Stores, Inc. > > > >WAL-MART CONFIDENTIAL > > > > > > -Original Message- > > From: Prather, Wanda [SMTP:[EMAIL PROTECTED]] > > Sent: Monday, December 17, 2001 10:18 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Incremental forever -- any problems? > > > > We have the opposite situation - we have fast robotics and use > >collocation. > > With collocation on fast tape, it doesn't matter whether you are > >doing 2 > > weeks or 2 years of data, a restore takes the same amount of time. > > > > Doing periodic fulls doesn't "refresh" anything, from TSM's point of > >view - > > the original backups are still in the TSM DB and still available, > >even if > > they are 5 years old. If you do periodic fulls, you have to > >retransmit > > everything over the network again, and you have to adjust your > >policies to > > make sure you allow those redundant versions to be kept; you > >increase the > > size of your DB and the amount of reclaims you have to do. > > > > Doing periodic "fulls" would do nothing whatever for us, except bog > >down the > > network. > > > > I suggest you try doing a large restore to test your own > >capabilities. If > > you can't restore in a timely fashion, FIRST figure out what your > >bottleneck > > is before you decide to "fix" it by doing full backups. > > > > Then if you find out you still can't do restores in a timely > >fashion, at > > least check out the use of BACKUPSETS. They give you all the > >client's > > active data on one tape, without retransmitting all the data, and > >without > > creating an extra zillion entries in your DB. > > > > > > > > -Original Message- > > From: Tim Melly [mailto:[EMAIL PROTECTED]] > > Sent: Monday, December 17, 2001 10:46 AM > > To: [EMAIL PROTECTED] > > Subject: Re: Incremental forever -- any problems? > > > > > > Adam, > > > > We were only doing incrementals and we had a situation where we had > >to > > restore a > > Novell server. > > The restore had to go through two years worth of incremental tapes > >to > > complete > > the restore. I would > > strongly recommend doing periodic fulls (and colocation) unless you > >have a > > SLA > > which allows for extremely long restores. > > > > Regards, Tim > > NAFTA IS Technical Operations > > (203) 812-3469 > > [EMAIL PROTECTED] > > > > > > > > Adam J Boyer > > >[EMAIL PROTECTED] > > @FRB.GOV> cc: > > Sent by: Subject: Incremental > >forever -- > > any problems? > > "ADSM: Dist > > Stor Manager" > > > RIST.EDU> > > > > > > 12/17/2001 > > 09:31 AM > > Please > > respond to > > "ADSM: Dist > > Stor Manager" > > > > > > > > > > > > > > Hey, > > > > Our management is wondering if it's safe to just do incrementals > > forever, or whether we should try to do a forced full every few > >months > > to keep things fresh. Our experience has been that the incremental > > system works great-- we once restored a whole raid 5 array, with > >many > > files from years ago. But, nonetheless, I'd appreciate any stories > >or > > testaments to help build a case. > > > > Thanks much, > > adam > > > > > >** > >This email and any files transmitted with it are confidential > >and intended solely for the individual or entity to > >whom they
Re: dsmadmc OS/390 TSO Abends After UserID/Password
Do you get a message about a dd card missing? That is generally the problem when you get an abend at that location. Jim Sporer At 03:42 PM 12/17/2001 +0100, you wrote: >Hi all > >On our OS/390 TSO system we tried to start > >dsmadmc -consolemode > >dsmadmc asks for the userID and password. After the userID was entered dsmadmc >abends with code 000C1000: > >* >ADSTAR Distributed Storage Manager >Command Line Administrative Interface - Version 3, Release 1, Level 0.7 >(C) Copyright IBM Corporation, 1990, 1999, All Rights Reserved. > >Enter your user id: >t096058 > >Enter your password: > > >T096058 abending: MVS Abend code 000C1000 generated at location 8004 > >CPU 0 General Registers at Entry to Abend: >R00 = 023C 22094F88 223B27B8 2220569A >R04 = 00073058 22094EE4 223B21D8 >R08 = 0008 22094268 A2053BBE >R12 = 00059000 22094EF0 A22056E4 > >CPU 0 Access Registers at Entry to Abend: >A00 = 7F91E010 >A04 = >A08 = >A12 = 016FFC18 81369972 > >Calling Trace for Current Task: > > 13 *-* "DSMADMC -CONSOLEMODE" >+++ RC(-194) +++ >* > >Does anyone know how to solve this problem? > >Thanks a lot, >Regards >Werner Nussbaumer
Re: Export Node
We moved from OS/390 to an AIX machine. We moved each client using server to server export. We had about 400 clients to move and It took us about 3 months to move all of the clients to the new machine. We would do one to several clients each day depending on the size of the clients. Jim Sporer At 11:38 AM 12/13/2001 +0100, you wrote: >Hi, > >we want to move from our OS/390 TSM server to a Solaris TSM server. What's >the best practical way to get our "old" data to the new server? > >mfg / regards > >andreas rensch > >When all else fails, read the instructions.
Re: TSM 4.2.1.7 Upgrade-
I didn't have that particular problem but I did have problems with mounting tapes in the atl after installing 4.2.1.7. After talking to the support center I installed the latest versions of Atape(6.1.9.0) and Atldd(5.0.7.0) and haven't had a problem since. Jim Sporer At 07:29 AM 12/6/2001 +1300, you wrote: >Mountretention only looks at idle tapes. >A process/session requesting a tape should normally take over a tape resource >if it's idle, regardless. > >This is a possible issue of the 8 legged variety. > >Cheers, Suad >-- > > >On Wed, Dec 05, 2001 at 11:22:11AM -0500, William Boyer wrote: > > Check the MOUNTRETENTION in the device class. > > > > -Original Message- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of > > Suad Musovich > > Sent: Wednesday, December 05, 2001 4:12 AM > > To: [EMAIL PROTECTED] > > Subject: Re: TSM 4.2.1.7 Upgrade- > > > > > > Upgraded to 4.2.1.7 (AIX) from 4.2.0.1 this morning and it went well. > All of > > the > > old problems seemed to go away, but... > > > > I just had a wierd thing happen. > > > > We have 6 drives in our library and 5 drives in use (1 move data and 3 > > backuppool > > migrations). > > > > Then the move data and one of the migrations gets cancelled by a "higher > > priority operation" requesting the tape drives. The thing was, there was no > > process > > or session wanting a tape drive, or the tapes. > > > > >From the 2 remaining migrations, 1 was operating normally and the > other was > > "waiting > > for a mount point". > > > > A "q mount" showed there was 5 idle mounts. I had to manually dismount a > > tape to > > get it to recognise the free drive. The process has then requested and > > mounted a > > subsequent tape. > > > > Has anyone seen this one ? > > > > Cheers, Suad > > -- > > > > On Mon, Dec 03, 2001 at 02:24:24PM -0500, [EMAIL PROTECTED] wrote: > > > If upgrading on AIX: > > > > > > The migration as per documentation does not work and produces errors > > during > > > install: > > > > > > Tivoli.tsm.server.rte.config [388]: 27002 IOT/Abort trap(coredump) > > > Tivoli.tsm.server.webadmin.config[44]:17383 IOT/Abort trap(coredump) > > > > > > Tivoli recommended solution: remove backlevel lpps and re-install 4.2.x > > > level. > > > Hence it really is a 4.x install, not a migration. > > > > > > License bug: When registering licenses, they don't show up as registered > > > with a q license command > > > in TSM 4.2.0. Recommendation is to upgrade to 4.2.1 (if client > > compatiblity > > > allows) and then > > > apply APAR. > > > -Original Message- > > > From: Dan Lee [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, December 03, 2001 1:48 PM > > > To: [EMAIL PROTECTED] > > > Subject: TSM 4.2.1.7 Upgrade- > > > > > > > > > Looking for anyone who has upgradeed to 4.2.1.X or greater. > > > > > > We are upgrading this weekend and we would like any information that > might > > > make the process go smooth > > > > > > Thanks > > > > > > Dan Lee > > > Associate Systems Programmer > > > Mutual of Omaha > > > I/S Midrange Services > > > 402-351-8377
Re: 4.2.1.7 Server and DRM
Curt, That is interesting because when I installed 4.2.1.6 the DRM.lic file disappeared on me. We went back to the cd for 4.2.0 and copied the DRM.lic file from there. Not sure why the file disappears but it did for us also. Jim Sporer At 09:51 AM 11/19/2001 -0500, you wrote: >Installed the 4.2.1.7 server yesterday on AIX 4.3.3 server. Going through >and checking/verifying all of license info is back and working correctly. We >are failing on the DRM license which we really did purchase. Don't seem to >have the DRM.lic file to correct this. We went from 4.1.x.x to 4.2.0 to >4.2.0.1 to 4.2.1.7. Somewhere in all of that it appears we have lost the >file. Was I supposed to install something "extra". Understand this is a >feature that you need to purchase. Does it now come on a separate CD? > >Curt Magura >Lockheed Martin EIS >Gaithersburg, Md. >301-240-6305
Re: upgrading tape density
The high density drives will never write a tape in low density. They can read the low density tapes. Jim Sporer At 01:20 PM 11/15/2001 -0600, you wrote: >Hello, > >** TSM 4.1 -- AIX 4.3.3.0 -- 3494 Library ** > >We upgraded our 3590B drives to 3590E1A drives. We've also started using >the double density tapes (K). > >If I am not mistaken, once the tape has been labeled it will remain at the >density that it was labeled at. So, if I labeled a tape with the old >3590B drives and the low density tape and this tape gets used and >eventually becomes scratch again, will it ever be re-labeled at the higher >density so that we are getting our moneys worth out of our upgrades? > >I thought about using a script that would do a 'trap' and watch for tapes >becoming scratch and then just relabel them at that point. Anyone been in >this situation before? > >thanks for your time. >-shawn > >Shawn L. Bierman >Unix Technical Support Analyst II >Methodist Healthcare >Information Systems >(901) 516-0143 (office) >(901) 516-0043 (fax)
Re: 4.2.1.6 (was: Re: TSM Server v4.2.1)
Henk, According to the information in apar IC30965 the licensing problem is supposed to be fixed in 4.2.1.6. * RECOMMENDATION: Apply fixing PTF when available. When the * fix is applied you may need to first delete * the nodelock file then "touch" the nodelock * file to recreate it. Did you recreate the nodelock file as recommended in the apar? Jim Sporer At 04:41 PM 10/30/2001 +0100, you wrote: >On 30-Oct-01 Suad Musovich wrote: > > You are both dyslexic 4.2.1.6 > >Hmm...like TSM you mean? > >Anyway, running 4.2.1.6 now for 4 hours, I must admit, we don't see any >"mount failed" anymorebut we see now a complete new set of _wonderful_ >messages: > >ANRD asvolmnt.c(519): ThreadId<51> Mount point deadlock possible. > >ANR1092W Space reclamation terminated for volume 000827 - internal server >error >detected. > >ANR1227E BACKUP STGPOOL: Process 44 terminated - internal server error >detected. > >Oh, and btw, the reg lic problems (ANR2841W) are not solved in 4.2.1.6, but >were solved in 4.2.1.5 as Tivoli told us (4.2.1.3, 4.2.1.4 and 4.1.2.5 >were only >available for special(?) customers.) > >Cheers, >Henk (waiting for 4.2.1.X, X>6)
Re: tsm 4.2.1 licensing
I used a 'reg lic file=50mssyslan.lic number=20' trying to get 1000 clients license. I then did a 'query license' and it told me I only had 50 clients licensed. I think there is something messed up with the licensing for version 4.2.1. Jim Sporer At 12:32 PM 10/18/2001 -0700, you wrote: >Same result.. > >tsm: TSM>reg lic file=mgsyslan.lic number=1 >ANR2852I Current license information: >ANR9634E REGISTER LICENSE: No license certificate files were found with >the ./mgsyslan.lic specification. >ANS8001I Return code 3. > >tsm: TSM>reg lic file=1mgsyslan.lic >ANR2852I Current license information: >ANR2853I New license information: > >Activity log is complaining about the license files: > >10/18/01 12:22:14 ANR2017I Administrator GWICHMAN issued command: >REGISTER > LICENSE file=mgsyslan.lic number=1 > >10/18/01 12:22:14 ANR2852I Current license information: > >10/18/01 12:22:14 ANR9634E REGISTER LICENSE: No license >certificate files > were found with the ./mgsyslan.lic >specification. >10/18/01 12:22:14 ANR2017I Administrator GWICHMAN issued command: >ROLLBACK >10/18/01 12:22:46 ANR2017I Administrator GWICHMAN issued command: >REGISTER > LICENSE file=1mgsyslan.lic > >10/18/01 12:22:46 ANR2852I Current license information: > >10/18/01 12:22:46 ANR9626E Invalid license certificate file: > > ./1mgsyslan.lic. > >10/18/01 12:22:46 ANR2853I New license information: > >10/18/01 12:23:29 ANR2017I Administrator GWICHMAN issued command: >QUERY >more... ( to continue, 'C' to cancel) > > ACTLOG > >Perhaps I mishandled the upgrade. I went from 4.1.2 -> 4.2.0 -> 4.2.1 > > > >Gerald Wichmann >System Engineer >StorageLink >408-844-8893 (v) >408-844-9801 (f) > > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of >Joshua S. Bassi >Sent: Thursday, October 18, 2001 1:21 PM >To: [EMAIL PROTECTED] >Subject: Re: tsm 4.2.1 licensing > >Instead of doing it the old way, licensing now works by doing: > >'reg lic file=mgsyslan.lic number=1' (or however many you are trying to >license. > > >-- >Joshua S. Bassi >Independent IT Consultant >IBM Certified - AIX/HACMP, SAN, Shark >Tivoli Certified Consultant- ADSM/TSM >Cell (408)&(831) 332-4006 >[EMAIL PROTECTED] > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of >Gerald Wichmann >Sent: Thursday, October 18, 2001 11:19 AM >To: [EMAIL PROTECTED] >Subject: tsm 4.2.1 licensing > >Is there a trick to licensing or why does tsm come back with this when I >attempt to add a license: > >tsm: TSM>reg lic file=1mgsyslan.lic >ANR2852I Current license information: >ANR2853I New license information: > >tsm: TSM> > >And of course, no license gets added.. ? > >Gerald Wichmann >System Engineer >StorageLink >408-844-8893 (v) >408-844-9801 (f)
Re: OS390 Database
If the space on the new volume is the same as the space on the old volume you can add the new volume as mirror and then delete the old volume when the mirror is in sync. Jim Sporer At 09:33 AM 10/2/2001 -0400, you wrote: >If you check the ADSM-L archives, I just asked this question, not 2-weeks >ago. > >The answer I got back was, basically, DONT DO IT ! One response I got >was, when this was done, TSM DB was trashed and he had to do a complete >restore. > >There is a section in the book on how to do this. The basic jist is to >create/format/add the new DB and then do a DELETE of the DB volumes you >want to get rid of (I suggest 1-at-a-time). TSM will then move the >contents of the DB volumes you are deleting, to other DB volumes in the >"pool". > >Make sure you have at least 1 good FULL backup of the DB. >=== >Zoltan Forray >Virginia Commonwealth University >University Computing Center >e-mail: [EMAIL PROTECTED] >voice: 804-828-4807 > > > > >GERARD PRATO <[EMAIL PROTECTED]> >Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> >10/02/2001 08:53 AM >Please respond to "ADSM: Dist Stor Manager" > > > To: [EMAIL PROTECTED] > cc: > Subject:OS390 Database > > >I have a question for OS390 users. I would like to know if I can use HSM >to move TIVOLI database from one disk pack to another disk pack? Will >this create a problem for TIVOLI. I am currently running TIVOLI 3.7.4 with >OS390 R2.10. > > > >Enterprise Software Programmer >Broward County Florida >Mr. Gerard Prato >[EMAIL PROTECTED]
Re: EtherChannel Performance
Look at /usr/lpp/bos/README for information on etherchannel. Jim Sporer At 04:22 PM 9/25/2001 +0400, you wrote: >Hi, > >We have AIX 4.3.3 on a P660, TSM Server 4.2 and TDP for R/3 V3.2. We want to >be able to backup/restore 200Gbytes/Hour using 4 parallel 3590E's. To do >this >we will be putting in a Cisco Gigabit switch. My questions are > >1) Will a single Gigabit without compression be able to meet this? I >calculate >gigabit at 50-60% utilization. > >2) To improve availability we are considering Etherchannel. Can you mix >100Base T >and Gigabit? If yes, will the connection still work if you lose either? > >Kind regards > >Mike Wiggan, >Infrastructure Integration Specialist >Petroleum Devlopment Oman LLC >([EMAIL PROTECTED]) > > > > > >-Original Message- >From: Jeff Bach [mailto:[EMAIL PROTECTED]] >Sent: 25 September 2001 00:24 >To: [EMAIL PROTECTED] >Subject: Re: Etherchannel and EBU backups. > > >The original question was what can you do and with what setup. > > > >HP client OS, Informix Database, 100 Base T on the client to four Gigabits >autoport aggregated together on the server(4.3.3 AIX and 4.1.3 TSM) . The >database backup is configured and runs 6 onbar processes at the same time >for the backup. Client compression on. EMC client disk storage. 1 SSA >array server with each session going to a separate disk drive. > >Results:131 Gigs per hour. (59 Gigs in 27 minutes) No server CPU, >memory, or database constraint. > >I use 4 Gigabit ethernets on the server using autoport aggregation. I use >Gigabit to be able to scale the number of clients. > >Jeff Bach >Home Office Open Systems Engineering >Wal-Mart Stores, Inc. > >WAL-MART CONFIDENTIAL > > > -Original Message- > From: Eric Winters [SMTP:[EMAIL PROTECTED]] > Sent: Sunday, September 23, 2001 12:04 AM > To: [EMAIL PROTECTED] > Subject:Re: Etherchannel and EBU backups. > > I've had some feedback re my attached note explaining that whilst it >will > work, all four sessions would operate through a single interface on >the > client and a single interface at the TSM server end, not improving >my > throughput a jot. > > Forgetting Etherchannel for a moment, is there any way that an >EBU/TDP for > Oracle can direct individual parallel sessions to different TSM >servers? I > don't see how - as I understand it the entire database instance is >sent > with optionally multiple parallel sessions to a single TSM server. >Of > course I don't really want to backup to separate servers, but I do >want to > backup to 4 different IP addresses. Can I do this? > > Regards, > > Eric Winters > I > > > I'm interested in determining if etherchannel and EBU/TDP for >Oracle, might > be effective in reducing backup times. > > Client system: AIX 4.3.3, uses Oracle 7 and backs up using EBU via >TDP for > Oracle 2.1 > Server system: AIX 4.3.3 and TSM Server 3.7 > > Network interfaces today are 100 MB ethernet, a single adapter in >each > system. > > Proposal is to speed up backups by using 4 ethernet adapters in both >the > client and the server and use Etherchannel. 4 parallel sessions >would be > set in the EBU script. A much larger database will be implemented >shortly > and etherchannel looks attractive, providing TDP for Oracle will use >4 > concurrent sessions, which I think it should. > > Can anyone confirm that the above should be a workable solution? Is >anyone > doing this? > > > Thanks people, > > Eric Winters > > >** >This email and any files transmitted with it are confidential >and intended solely for the individual or entity to >whom they are addressed. If you have received this email >in error destroy it immediately. >**
Re: volume status being changed erroneously
Maybe the tapes don't have proper internal labels. Look at the LABEL LIBVOLUME command. Jim Sporer At 10:11 AM 9/24/2001 -0500, you wrote: >TSM Gurus, > >I found several reference to my problem in the archive but, did not find an >explanation or a real fix for it. If I over looked it, I will shamefully >take the time-out chair in the corner. > >Our TSM environment is relatively new (< 6 mos). We are running 4.1.3 >server on AIX 4.3.3 ML6 with a 3583 LTO library. > >The clients are all 4.1.3 AIX and NT. A few TDP clients for Exchange, M$SQL >and DB2 on AIX. > >The problem is that I keep seeing several of my scratch volumes' status >being changed from "scratch" to "private" and the "last use" column is >blank. The first time I noticed this it was suggested, by our Business >Partner, that the tapes were probably checked in improperly. I checked them >out and then back in as scratch. Within the last two weeks I recall seeing >several consecutively labeled volumes again with a status of "private" and >no "last use".Again I changed their status back to scratch. This >morning I see the same thing with the same group of tapes. I also happened >to catch it in the activity log, stating that there were I/O errors on these >volumes and the status change was to prevent re-access. > >If it were one or two tapes, I could accept it. But the fact that these >seven tapes represent roughly 30% of the library's current population AND >the fact that they are consecutively numbered AND have never previously been >used, to me can't be explained as coincidental. The tapes and the labels >arrived separately. So we can dismiss a error at the factory. > >Any help would be greatly appreciated! > >Thanks > >David Taylor >Senior Software Systems Engineer >West Bend Mutual Insurance >(262) 335-7077 >[EMAIL PROTECTED] > > > >** >This email and any files transmitted with it are confidential and >intended solely for the use of the individual or entity to whom they >are addressed. If you have received this email in error please notify >the system manager. > >This footnote also confirms that this email message has been swept by >MIMEsweeper for the presence of computer viruses. > >www.mimesweeper.com >**
Re: TSM OS/390 DB "volumes"
It's so easy to move using TSM processes, why would you want to use some other utility. The good thing about using TSM to do the move is you don't even have to take the TSM server down. All you have to do is allocate and format the new volume, then add it as a mirror and delete the old volume. Jim Sporer At 11:54 AM 9/18/2001 -0400, you wrote: >Is there anything internal for a OS/390 TSM DataBase "volume" (i.e. the >VSAM LINEAR d/s), that prevents me from moving it using a standard system >utility ? > >Could I move the linear d/s, using FDR or DSS or are there internal >location-type pointers that would destroy the DB if pyhsically moved using >non-TSM processes ? > >=== >Zoltan Forray >Virginia Commonwealth University >University Computing Center >e-mail: [EMAIL PROTECTED] >voice: 804-828-4807
Re: Defrag Database
No, it doesn't. Jim Sporer At 09:42 AM 9/17/2001 -0700, you wrote: >I just had a thought. If you defined new dbvols and deleted the previous >dbvols, that would move the db data over to the new volume. Could that >possibly defrag the db at the same time? I would expect so because the >manual says you can cancel the delete dbvol process, but some of the data >may have moved. It makes sense to me that this implies it moves db objects, >not just vast tracts of raw dbspace. Any thoughts? > >(Andy? Are you out there? Any chance on developer feedback on this one?) > >Alex > >-Original Message- >From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]] >Sent: Monday, September 17, 2001 2:06 AM >To: [EMAIL PROTECTED] >Subject: Re: Defrag Database > > >Hi Maurice! >An online defrag utility is on all our wish lists for some time! >The only way to defrag your database is a offline dump and reload... Note >that this is quite a lengthy process! >Kindest regards, >Eric van Loon >KLM Royal Dutch Airlines > > >-Original Message- >From: Maurice van 't Loo [mailto:[EMAIL PROTECTED]] >Sent: Monday, September 17, 2001 09:22 >To: [EMAIL PROTECTED] >Subject: Defrag Database > > >Hi, > >*** ---> Q DB F=D > >Available Space (MB): 3.320 >Assigned Capacity (MB): 3.320 >Maximum Extension (MB): 0 >Maximum Reduction (MB): 20 >Pct Util: 43,2 >Max. Pct Util: 52,0 >Physical Volumes: 13 > >Because the database is around 50% utililized, i want to reduce the >database, the by the spacetrigger made volumes can be deleted. > >Is there a way to "defrag" the database? > >Tia, >Maurice > > >** >This e-mail and any attachment may contain confidential and privileged >material intended for the addressee only. If you are not the addressee, you >are notified that no part of the e-mail or any attachment may be disclosed, >copied or distributed, and that any other action related to this e-mail or >attachment is strictly prohibited, and may be unlawful. If you have received >this e-mail by error, please notify the sender immediately by return e-mail, >and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its >subsidiaries and/or its employees shall not be liable for the incorrect or >incomplete transmission of this e-mail or any attachments, nor responsible >for any delay in receipt. >** > >"WorldSecure " made the following > annotations on 09/17/01 09:29:03 >-- > >[INFO] -- Content Manager: >The information contained in this communication is confidential and >intended solely for the use of the individual to whom it is addressed and >others authorized to receive it. If you are not the intended recipient, >any disclosure, copying, distribution or taking of any action in reliance >on the contents of this information is prohibited. If you have received >this communication in error, please immediately notify the sender by phone >if possible or via email message. > >==
Re: dsmserv.opt file documentation
Look in Appendix B. Jim Sporer At 11:15 AM 9/13/2001 -0500, you wrote: >Friends, Is there somewhere that I can find documentation on the various >options that could be included in the dsmserv.opt file? I can't find >anything in the admin reference. TIA - > >George Lesho >AFC Enterprises >Storage/System Admin
Re: Deleting Log Volumes
Define the new logs as mirrors and then delete the old logs. Jim Sporer At 11:07 AM 8/20/2001 -0400, you wrote: >HI, > >I hope someone out there can help. I am trying to move to new Recovery Log >volumes. I've attempted to add a log volume and get the following msg: >ANR2452E DEFINE LOGVOLUME: Maximum recovery log capacity exceeded. > >How do I now move to new volumes when I can't define new ones? The existing >log is at the 5 GB limit. > > > >Blue Cross Blue Shield of Florida, Inc., and its subsidiary and >affiliate companies are not responsible for errors or omissions in this >e-mail message. Any personal comments made in this e-mail do not reflect >the views of Blue Cross Blue Shield of Florida, Inc.
Re: TSM Tape Retention Time Limitation?
0 means remove the tape as soon as TSM is done with it. Jim Sporer At 09:43 AM 8/9/2001 +0100, you wrote: > minutes is the maximum setting for mountretention. 0 probably means >'never remove tape', although perhaps someone could confirm this.. > > > >-Original Message- >From: Paul CC Lo [mailto:[EMAIL PROTECTED]] >Sent: 09 August 2001 09:33 >To: [EMAIL PROTECTED] >Subject: TSM Tape Retention Time Limitation? >Importance: High > > >Is there a limitation for TSM device class to set the mout retention to > minutes? Do we have any option to set the mount retention to be >longer or to disable this function to remain the tape in the tape drive? > >Best Regards > >Paul Lo > > >http://www.phoenixitgroup.com >**Internet Email Confidentiality Footer*** > >Phoenix IT Group Limited is registered in England and Wales under company >number 3476115. Registered Office: Technology House, Hunsbury Hill Avenue, >Northampton, NN4 8QS > >Opinions, conclusions and other information in this message that do not >relate to the official business of our firm shall be understood as neither >given nor endorsed by it. > >No contracts may be concluded on behalf of our firm by means of email >communications. > >Confidentiality: Confidential information may be contained in this message. >If you are not the recipient indicated (or responsible for delivery of the >message to such person), you may not take any action based on it, nor should >you copy or show this to anyone; please reply to this email and highlight >the error to the sender, then delete the message from your system. > >Monitoring of Messages: Please note that we reserve the right to monitor and >intercept emails sent and received on our network. >Warning: Internet email is not 100% secure. We ask you to understand and >observe this lack of security when emailing us. We do not accept >responsibility for changes made to this message after it was sent > >Viruses: Although we have taken steps to ensure that this email and any >attachments are free from any virus, we advise that in keeping with good >computing practice the recipient should ensure they are actually virus free.
Re: Cache Hit Pct.
That's curious because it resets mine. I am running v4.1.1.0 of TSM on AIX. Maybe it has something to do with what version of TSM you are running. Jim Sporer At 01:23 PM 6/21/2001 -0500, you wrote: >I run expiration everyday at 5pm but it doesn't seem to reset my bufpool >statistics. Unless my bufpool statistics are just very low. > >-Original Message- >From: Jim Sporer [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 21, 2001 1:21 PM >To: [EMAIL PROTECTED] >Subject: Re: Cache Hit Pct. > > >The selftunebufpoolsize only adjusts your bufferpool size when you run >expiration. If you are like us and only run expiration once a week it >isn't much help. Part of the selftunebufpoolsize process involves >resetting the bufpool statistics, but again this only happens when you run >expiration. >Jim Sporer > > At 01:07 PM 6/21/2001 -0500, you wrote: > >My Buffpoolsize is set to 65536 and SelfTunebufpoolsize is set to yes as > >well. So I would assume it would tune itself to the right value. I'm > >thinking maybe the reset of buffpool stattistics will help. Is resetting >of > >the buffpool statistics something that need to be don everyday. In order >to > >get a true value each day. > > > > > >-Original Message- > >From: George Lesho [mailto:[EMAIL PROTECTED]] > >Sent: Thursday, June 21, 2001 12:45 PM > >To: [EMAIL PROTECTED] > >Subject: Re: Cache Hit Pct. > > > > > >Richard, Your cache hit percentage is too low at 95.6 percent and as you > >have pointed out, should be around 98 percent of above. To change the > >percentage of your cache hits, increase by doubling, the size of your > >BUFPOOL parameter in your dsmserv.opt file on your TSM server: > > > >entry from my dsmserv.opt file: > >BUFPOOLSIZE 16384 > > > >You should then wait a day or two and see what it rises to. Each time, you > >will need to reset the associated statistics with > >the "reset bufpool". You can then check your cache hit percentage using the > >"q db f=d" command: > > > >tsm: AFCOPS2>q db f=d > > > > Available Space (MB): 13,172 > > Assigned Capacity (MB): 11,420 > > Maximum Extension (MB): 1,752 > > Maximum Reduction (MB): 1,780 > > Page Size (bytes): 4,096 > > Total Usable Pages: 2,923,520 > > Used Pages: 1,441,070 > > Pct Util: 49.3 > > Max. Pct Util: 50.1 > > Physical Volumes: 3 > > Buffer Pool Pages: 4,096 > > Total Buffer Requests: 31,549,306 > > Cache Hit Pct.: 98.94 > >Cache Wait Pct.: 0.00 > >Backup in Progress?: Yes > > Type of Backup In Progress: Full > > Incrementals Since Last Full: 0 > >Changed Since Last Backup (MB): 0.52 > > Percentage Changed: 0.01 > >Last Complete Backup Date/Time: 06/20/01 12:02:59 > > > > > >Hope this is what you were looking for... I suspect your TSM server is > >running a tad slow... just don't overdo upping the > >bufpool size and wait for at least a day to let the new bufpool size have a > >chance to show a true value for the cache hit > >percentage > > > >George Lesho > >Storage/System Admin > >AFC Enterprises > > > > > > > >) > > > > > > > > > >"Dearman, Richard" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 06/21/2001 11:04:01 > >AM > > > >Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > >Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > >To: [EMAIL PROTECTED] > >cc: > >Fax to: > >Subject: Cache Hit Pct. > > > > > >Anyone know of a good way to raise Cache Hit Pct to above 98%. I continue > >to get 95.6% and I tried the performance tuning setting an still get cann't > >get it above 98%. Tivoli manuals state that Cache Hi Pct should remain > >above 98%. > > > >Thanks > >***EMAIL DISCLAIMER** > >This e-mail 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 o
Re: Cache Hit Pct.
The selftunebufpoolsize only adjusts your bufferpool size when you run expiration. If you are like us and only run expiration once a week it isn't much help. Part of the selftunebufpoolsize process involves resetting the bufpool statistics, but again this only happens when you run expiration. Jim Sporer At 01:07 PM 6/21/2001 -0500, you wrote: >My Buffpoolsize is set to 65536 and SelfTunebufpoolsize is set to yes as >well. So I would assume it would tune itself to the right value. I'm >thinking maybe the reset of buffpool stattistics will help. Is resetting of >the buffpool statistics something that need to be don everyday. In order to >get a true value each day. > > >-Original Message- >From: George Lesho [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 21, 2001 12:45 PM >To: [EMAIL PROTECTED] >Subject: Re: Cache Hit Pct. > > >Richard, Your cache hit percentage is too low at 95.6 percent and as you >have pointed out, should be around 98 percent of above. To change the >percentage of your cache hits, increase by doubling, the size of your >BUFPOOL parameter in your dsmserv.opt file on your TSM server: > >entry from my dsmserv.opt file: >BUFPOOLSIZE 16384 > >You should then wait a day or two and see what it rises to. Each time, you >will need to reset the associated statistics with >the "reset bufpool". You can then check your cache hit percentage using the >"q db f=d" command: > >tsm: AFCOPS2>q db f=d > > Available Space (MB): 13,172 > Assigned Capacity (MB): 11,420 > Maximum Extension (MB): 1,752 > Maximum Reduction (MB): 1,780 > Page Size (bytes): 4,096 > Total Usable Pages: 2,923,520 > Used Pages: 1,441,070 > Pct Util: 49.3 > Max. Pct Util: 50.1 > Physical Volumes: 3 > Buffer Pool Pages: 4,096 > Total Buffer Requests: 31,549,306 > Cache Hit Pct.: 98.94 >Cache Wait Pct.: 0.00 >Backup in Progress?: Yes > Type of Backup In Progress: Full > Incrementals Since Last Full: 0 >Changed Since Last Backup (MB): 0.52 > Percentage Changed: 0.01 >Last Complete Backup Date/Time: 06/20/01 12:02:59 > > >Hope this is what you were looking for... I suspect your TSM server is >running a tad slow... just don't overdo upping the >bufpool size and wait for at least a day to let the new bufpool size have a >chance to show a true value for the cache hit >percentage > >George Lesho >Storage/System Admin >AFC Enterprises > > > >) > > > > >"Dearman, Richard" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 06/21/2001 11:04:01 >AM > >Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > >Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > >To: [EMAIL PROTECTED] >cc: >Fax to: >Subject: Cache Hit Pct. > > >Anyone know of a good way to raise Cache Hit Pct to above 98%. I continue >to get 95.6% and I tried the performance tuning setting an still get cann't >get it above 98%. Tivoli manuals state that Cache Hi Pct should remain >above 98%. > >Thanks >***EMAIL DISCLAIMER** >This e-mail 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) 996-3941. >***EMAIL DISCLAIMER** >This e-mail 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) 996-3941.
Re: How to migrate TSM from OS/390 onto AIX
We used server to server to export the nodes to an AIX TSM server. We had a 20gig database with several hundred nodes that we migrated. We did the migration a node at a time over a 4 month period. We would lock the node, do the export, then import on the AIX server, add the node to a schedule, and then notify the customer that he needed to change the ip address for the TSM server. You need a lot of patience because if you get an error there is no way to restart the export where you left off. For some of our larger nodes we ended up exporting them a filespace or several filespaces at a time. Jim Sporer At 10:49 AM 6/8/2001 +0200, you wrote: >Hello, > >we will stop our mainframe by end of the year. TSM will be migrated from >OS/390 to AIX. > >I have a 15 GB DB, about 2500 primary volumes as 3590 cartridges. > >How should we proceed: > >- export / import DB: using which media ?, server to server ? >- same question for the stg pools: can AIX read the OS/390 cart or do we >have to export / import between both. If yes export onto what media ? >- no export but keep a mini-mainframe for the time to expire old backups ? > >Thanks for any advices, > >René Lambelet >Nestec S.A. / Informatique du Centre >55, av. Nestlé CH-1800 Vevey (Switzerland) >*+41'21'924'35'43 7+41'21'924'28'88 * K4-117 >email [EMAIL PROTECTED] >Visit our site: http://www.nestle.com > > This message is intended only for the use of the addressee and > may contain information that is privileged and confidential.
Re: Multiple TSM* Servers On Same Machine
I do it to run a test TSM server on the same machine. Jim Sporer At 11:08 AM 5/10/2001 -0400, you wrote: >The reason I would do it would be to keep the database size down. > >At 11:41 AM 5/9/2001 -0400, >[EMAIL PROTECTED] wrote: > >Why would one put multiple TSM servers on a single machine?
Re: MediaW problem
Also check your maximum filesize for the storage pool. If the clients contain a file that exceeds the maximum file size then the data will go to the next storage pool which is probably tape. Jim Sporer At 03:51 PM 4/4/2001 -0400, you wrote: >Do a "q stg" when this happens and see what the "Pct Util" and Pct Migr" >is for the disk storage pools in question. If Pct Util is anywhere near >say 90% when a bunch of clients are sending data then some of them WILL >start trying to go directly to tape. > >Why you say? Example: you have 10GB storage pool that is 90% full. 2 >clients each start to send a new 1 GB file. Immeadiately the Pct Util >would be theoretically 110% as space is allocated for the size of the >file, but it will take some time for the file to be completely transfered. > >So one of them will not be able to get it's space as we can't be over 100% >and it will therefore attempt to go directly to tape. Ciomplictate this >with many clients and many different size files (And probably a few fudge >factors) and you will get these results. > >We have seen backups start to go to tape when our stg pool was about 90% + >full with a handfull of clients sending 2GB files. > >If you are getting about 90% full anytime then you probably need to either: > >1. Spread out the backups so not as many machines are going to the server >at once. > >2. Increase the disk space available to the disk storage pools that are >being filled. > > >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.5525 >[EMAIL PROTECTED] > > > >>> [EMAIL PROTECTED] 04/04/01 03:01PM >>> >I run my backups at night around 10:30pm. I have around 50 servers doing >incrementals concurrently at this time. I noticed that about half are >experiencing MEDIAW when I do a "q session". They seem to be waitng to for >a tape to load in my library for them to write to but the storage pool that >these clients write to first is disk based then when it fills to 90% it >should migrate to tape. My question is, if they are suppose to be going to >disk storage pool first and it isn't full then why are they waiting for >tape. Which is what I am assuming is happening. > >Thanks >Richard >***EMAIL DISCLAIMER** >This e-mail 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) 996-3941. > > > >"MMS " made the following > annotations on 04/04/01 15:51:47 >-- >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. > >==
Re: WG: TSM Client for OS X
We are in a similar position here at the University of Wisconsin with OS X. By the way this is the information I have on the latest mac client ptfs. IBM has provided a fix for the restore problems I was having with the Mac 4.1.2 client. Everything seems to work great now. The fix is available in the form of a new Mac installer at: ftp://service.software.ibm.com/storage/tivoli-storage-management/patches/client/v4r1/Mac/v412/ Jim Sporer At 02:56 PM 3/27/2001 -0500, you wrote: >K! I've got a thousand Macs, all of them headed for OS X >this summer. I heard that the Mac developer left and there was >some scrambling to get out a new Mac client that could actually >*restore* (thanks for that!), but to not support OS X would >be devastating for us. > >If it hasn't been mentioned on the list already, there is a >new Mac client in the patches subdir that solved a lot of our >restore problems, on both VM and AIX servers. > >Gretchen Thiele >Princeton University
Re: Backup sets on MVS
Generate the backupset and then ftp the file to the aix or nt machine. Jim Sporer At 12:24 PM 3/5/2001 -0600, you wrote: >Is anyone running TSM on MVS and successfully generating and then using backup >sets for your clients? It's my understanding that backup sets need to be >generated on sequential media that is compatible/readable by the client. The >sequential device classes I have defined are 3590 tape - which is not >compatible >with my NT and AIX clients. Any suggestions on how I can generate a >backup set >from MVS that would be readable by an NT or AIX client? What are other people >doing? > >Thanks - your comments and suggestions are appreciated, > >Cheri Howard >Lead Software Systems Analyst >920-730-4700, ext. 4166 >[EMAIL PROTECTED] >Aid Association for Lutherans (AAL) >4321 N. Ballard Road, Appleton, WI 54919-0001 >http://www.aal.org
Re: URGENT ? ABOUT DB RESTORE
I assume you do not have a functional adsm server and that is why you are restoring the db, so you cannot do a move media or checkin but you don't need to do that. As long as you have a current volume history file, device configuration file and the tape has been inserted in the atl, you can issue the restore db command that Ruddy gave you and adsm will find the proper tape. Jim Sporer At 07:07 PM 2/22/2001 +0200, you wrote: >No arguments to give. > >If your volhist is still present and not corrupted, if you tape has been >moved back via MOVE MEDIA and if your tape has been checked in, just >type: > >dsmserv restore db todate=xx:xx: totime=xx:xx > >and the TSM server will use the volume corresponding to the tape just >back from off-site. > >Ruddy > >-Original Message- >From: Steve Hicks [mailto:[EMAIL PROTECTED]] >Sent: jeudi 22 février 2001 17:35 >To: [EMAIL PROTECTED] >Subject: Re: URGENT ? ABOUT DB RESTORE > > >What would the syntax be? dsmserv restore db ... >I've tried dsmserv restore db movemedia=6239 and I get and invalid >argument >error. > > > > > > Ruddy STOUDER > > [EMAIL PROTECTED] > SLINK.COM>cc: > > Sent by: "ADSM: Subject: Re: URGENT ? >ABOUT DB RESTORE > Dist Stor Manager" > > <[EMAIL PROTECTED] > > EDU> > > > > > > 02/22/01 11:23 AM > > Please respond to > > "ADSM: Dist Stor > > Manager" > > > > > > > > >tRY / > >1) MOVE MEDIA ... To bring the tape back on-site in the TSM database >2) CHECKIN ... STATUS=PRIVATE to get the tape back in the library > >Ruddy > >-Original Message- >From: Steve Hicks [mailto:[EMAIL PROTECTED]] >Sent: jeudi 22 février 2001 17:11 >To: [EMAIL PROTECTED] >Subject: URGENT ? ABOUT DB RESTORE > > >Need to restore out TSM database but the volume that the DB backup in on >is >listed as VAULT. I have the tape in the automated library, how do I >check >it in to restore from it??
Re: NOTINQLIB
The q vol command will only give you information about storage pool volumes, not scratch volumes. Jim Sporer At 07:55 AM 1/4/2001 -0600, you wrote: >I have eight volumes that are mounted in the tape library and when i run q >libv >they show up with a status of scratch and its blank under last use and it >gives >me a home element for the volume. > >When I run a q vol XXX on the same volume number I get no response and it >should tell me that its readwrite etc, but doesn't. Can anyone help me as to >what is going on. > >Thanks, > >Gene
Re: Export to another ADSM server using the same 3494 library
Nick, The way we do it is using the exit cbruxent. When you insert tapes into the 3494, this mainframe OAM exit gets control and we use it to determine which tapes get assigned to the mainframe and which tapes get ignored and assigned a x'ff', insert code. We have a data set that the exit reads to determine which tapes are assigned to the mainframe and which are ignored. When we export data to tapes we eject them from the atl, update the data set and then put them back in the atl. At that point they have a x'ff' so they can be checked into the aix adsm and used for the import. Jim Sporer >Hello all, > I hope you can help me, we have two ADSM environments, one on OS390 > and the >other on AIX both sharing the same IBM 3494 library. We are trying to >export all >of our data from OS390 to the the AIX ADSM server and are encountering a few >problems. I have exported some policy information which has worked succesfully >on OS390. The problem is when I try to import the information to the AIX >server, >I get an error about the category the tape is assigned to in the 3494 >library - >it still recognises it as a mainframe assigned tape. >Our categories on the AIX server are 301 for private and 300 for scratch. How >can I modify the category for all exported OS390 tapes so I can then re-assign >them to the 301 private category on our AIX server thus allowing me to import >succesfully? > >Any help would be appreciated. > >many thanks, >Nick > > >* >This e-mail is confidential and intended solely for the use of the >individual to whom it is addressed. Any views or opinions presented >are solely those of the author and do not necessarily represent >those of Honda of the UK Manufacturing Ltd. > >If you are not the intended recipient please notify the sender >immediately by return e-mail and then delete this message from your >system. Also be advised that any use, disclosure, forwarding, >printing or copying of this e-mail if sent in error is strictly >prohibited. Thank you for your co-operation. >*
Re: Remove license
Below is an excerpt from the README.LIC file included in your installation directory. Jim Sporer The function of the license files are the same as documented, except for a numeric value added to the front of the names to indicate the quantity for that license type. The NUMBER= option on the REGISTER LICENSE command is still supported. The additional license files were added to help minimize the number of license statements in the nodelock file. The nodelock file contains an entry for each license file registered. When the NUMBER= option is used on the REGISTER LICENSE command, it will put that many entries in the nodelock file for that particular license file being registered. For performance purposes, you should register the license files using the increments to minimize the number of license files that are registered. If you do not minimize the number of license statements in your nodelock file and run into performance problems with the license manager component of the TSM server as a result, you can delete the nodelock file and re-register the licenses using the appropriate license increments to reduce the number of entries in the nodelock file. At 07:56 AM 12/20/2000 +0100, you wrote: >Petr Pøerost wrote: > > > > Hello , > > after install of 4.1.2 fix my server is licensed for completely everythink > > :-) , please , can somebody help me > > with removing licenses not in use ( TSM server 4.1.2 W2K ) ? > > > > Regards > > > > Petr Prerost > > e-mail [EMAIL PROTECTED] > >Petr, > >according to a posting from Brian Furphy <[EMAIL PROTECTED]> as of 1998, >Aug 28: > > Mohamed, > > When registered, the licenses are stored in a file named NODELOCK in the > DSMSERV_DIR environment variable, if specified, or in the current directory > that the server was started from. > > You will need to remove this file from it's current directory or change it's > name to start the REGister LICense process again. Run the Query LICense > command to confirm the change worked. For 17 clients you'll need to specify > the following enrolment certificate files to accomplish your goal, > (1CLIENT.LIC, 5CLIENT.LIC & 10CLIENT.LIC - use each one time). > > ADSMingly yours > Brian Furphy > >Hth, >-- > > > >Horst SCHERZER e-Mail: [EMAIL PROTECTED] >Zentraler Informatikdienst Uni Wien Fax:(+43 1) 4277 x14053 >Universitaetsstr.7 Phone: (+43 1) 4277 x9140 >A-1010 Vienna, Austria URL: http://mailbox.univie.ac.at/~sc >
Re: TSM v4.1.1 migrate install: "No device definitions are saved"????
We have a 3494 ATL with 6 3590 drives in it. When we upgraded from adsm 3.1.2.50 to v4.1.1.0 the library manager device did not get deleted but the 6 3590 drives did get deleted. We needed to run configuration manager to get the 3590 drives back. Jim Sporer At 09:22 PM 12/14/2000 -0500, you wrote: >We are planning the TSM server v4.1.1 install. > >We will be doing a migrate install on AIX 4.3.3.0, TSM 3.7.3.0. > >In the README for v4.1 migrate install section (pp 1), it states: >" For a Migrate Install > > o No device definitions are saved. Record all of your current definitions >because you will have to redefine all devices after the installation of >Version 4.1." > >To those of you who have already installed v4.1., does this really mean you >will have to redefine all devices?? or, what?? > > >From a practical point of view, will all of your devices go away after the >v4.1.1 install?? > >Please shed some light on this. > >TIA. > > >Ken Sedlacek > > >Network Specialist > > >Direct: 864-322-4260 Mobile: 864-444-8375 > > >Kyrus Corporation - http://www.kyrus.com > > >or [EMAIL PROTECTED] > > > > > > Kyrus IT Support (Internal: 4399) (Greenville: 864-322-4399) (Toll-Free: >888-413-4399)
Re: tape drive needs cleaning
I'm surprised you don't get more of these errors. We get at least two or three a day. Our service people tell us it is normal. Jim Sporer At 09:22 AM 12/11/2000 -0800, you wrote: >We have an ibm h70 running aix 4.3.3 and TSM 3.7.3. It s hooked up to an ibm >3494 with two magstar 3590 drives. A month ago we saw some tape drive needs >cleaning messages in the aix error report. They repeated today.. > >IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION >E507DCF9 1210101500 I H rmt1 TAPE DRIVE NEEDS CLEANING >D1A1AE6F 1210101500 I H rmt1 TAPE SIM/MIM RECORD > >I m wondering if this is normal? To my knowledge the 3494 should be cleaning >itself as it does have cleaning tapes and is all configured to do so >automatically. > >Gerald Wichmann >Systems Engineer >Sansia System Solutions >408-844-8893 work >408-884-9801 fax
V4.1.1.0 Library Sharing
I recently installed TSM V4.1.1.0 for AIX and was looking at the library sharing feature. The documentation was a little sketchy and it talked about san sharing of a 3494 over a scsi connection. The information about the 3494 was in the README.SRV file, not in the Administrator's Guide. From what I was reading the feature is suppose to allow you to share the tape drives in a 3494 between two ADSM servers. If a drive is allocated to one server the second server would allocate a different drive if one is available and wait if one is not. So if I wanted to, I could have two adsm servers and they could share a 3494 ATL with 6 3590 drives, all 6 drives would be allocated to both ADSM servers and the servers could figure out which drives to use. I would use a different set of tapes for each ADSM server with different scratch and private categories. Am I interpreting the documentation correctly? Jim Sporer
Re: Client ver 3.7.2 - no SA software
Use the command "set accounting on" to start recording the smf information. The smf record type is 42 with a subtype of 14. Check the ADSM or TSM Administrator's Guide for the content and format of the records. Jim Sporer At 11:32 AM 11/15/2000 -0500, you wrote: >Can you give me more specifics ? > >Is this an options ?What SMF type records ? Are these records mapped >somewhere ? > > > >For OS390 the same information in dsmaccnt.log, is written in smf records. >Jim Sporer
Re: Client ver 3.7.2 - no SA software
For OS390 the same information in dsmaccnt.log, is written in smf records. Jim Sporer At 09:20 AM 11/15/2000 -0500, you wrote: >I guess I should have clarified my environment. > >This is OS/390 2.5. There is no dsmaccnt.log. > >And as I mentioned to Maria, I am not going through a proxy. I go directly >to the OS/390 box. > > > > > "France, Don G > (Pace)" To: [EMAIL PROTECTED] > [EMAIL PROTECTED]>Subject: Re: Client ver > 3.7.2 - no SA software > Sent by: > "ADSM: Dist > Stor Manager" > <[EMAIL PROTECTED] > IST.EDU> > > > 11/15/00 01:20 > AM > Please respond > to "ADSM: Dist > Stor Manager" > > > > > > >Yep... we see the same phenomenon for some customer environments. Maria's >suggestion may fix your browser-admin experience. > >Just a suggestion, though - sounds like you're wanting to do some "more >than >casual" administering - so, I recommend a couple things: (a) use the >dsmaccnt.log file to extract the 4961 info (and other session stats) and/or >(b) use the admin command-line interface and run server scripts or macros >to >accomplish frequently-repeated tasks... some folks run shell scripts which >perform daily queries using dsmadmc and store the results in a flat file >which might then be displayed via an internal web page. > > >Don France > >Technical Architect - Unix Engineering/P.A.C.E. >San Jose, CA >mailto:[EMAIL PROTECTED] >PACE - http://www.pacepros.com >Bus-Ph: (408) 257-3037 > > > -Original Message- >From: Maria Paz Gimeno [mailto:[EMAIL PROTECTED]] >Sent: Friday, November 10, 2000 3:42 AM >To: [EMAIL PROTECTED] >Subject:RV: Re: Client ver 3.7.2 - no SA software > >The problem with speed in the admin web interface could be related to your >proxy, >if you have one. >We have a similar problem in a customer, the administrative web interface >was very slow, >and when we removed for the TSM server address to go thought the proxy, >the response time was much much faster. >It is just one idea >Regards >Maria > >- Original Message - >From: Zoltan Forray/AC/VCU <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Thursday, November 09, 2000 5:39 PM >Subject: Re: Client ver 3.7.2 - no SA software > > >There are too many things, in the WWW interface that do not work like the >SA gui or are simply not available. > >For instance, I collect data transfer statistics. I do this by going to the >SA GUI client, SERVER ACTIVITY LOG, select all 4961 messages and then >SELECT / PRINT them to a file that is imported into a spreadsheet. > >Can't do this with the WWW interface. The output is wrapped (if you just >cut/paste). No option to print to a file or with COMMA DELIM, etc. > >Also, did I mention it is dog-slow !!! I have tried using the WWW >interface and after waiting 20 minutes (this is of course, after clicking >through 8-levels to find something) for a query to return (and don't even >think about suggesting our network is the issue. We run 1GB ethernet, FDDI, >ATM, etc. Speed is not an issue), I jumped into the SA GUI program and the >same query/info came back almost immediately !!!. > > > >You may use any web browser like Netscape to administrate the server, the >address is default to dns of your server followed by port 1580, in my case >it >is http://pu01:1580/. Then you'll get a nice GUI. > >Regards >Werner Nussbaumer > >-Original Message- >From: GEOFFREY.L.GILL [mailto:[EMAIL PROTECTED]] >Sent: Donnerstag, 9. November 2000 16:01 >To: ADSM-L >Subject: Re: Client ver 3.7.2 - no SA software > > >Sadly the SA GUI is gone, I'm not sure I ever read why it was taken out >unless they are just trying to simplify things. I also liked it. > >I did try a test though. I installed the 3.1.08 version on a computer and >upgraded to a newer version without removing. Since the new version does >not >install in the same directory structure as before I was able to keep the SA >GUI and it seemed to work. I doubt Tivoli would support you if you had >problems since 3.1 is going off support soon. > >Geoff Gill >NT Systems Support Engineer >SAIC >Computer Systems Group >E-Mail: [EMAIL PROTECTED] >Phone: (858) 826-4062 >Pager: (888) 997-9614 > > > >-Original Message--
Re: 3590 tape drives
And write. Jim Sporer At 10:46 AM 10/27/2000 -0400, you wrote: >Per IBM they can read both. > > >>> [EMAIL PROTECTED] 10/27/00 10:05AM >>> >Hy experts ! > >A question about tape-drives : > >we have in our tape-library (IBM 3494) Magstar 3590 Modell E drives (E1A). >Because they were bought one year ago, they don' t have the facility to >read/write the extended-length-cartridges, so we use the normal cartridges >with 20 GB uncompressed. > >Now we plan to upgrade those drives (IBM-upgrade-Kit) so that they can >handle the extended-length-cartridges (40GB uncompressed). > >My question now : are the drives with this feature able to handle >(read/write) the old format cartridges (20 GB), or can they only read those >40 GB-cartridges. > >Thanks a lot > >Chr. Pilgram
Re: recovering copypools
Use a delete volume discardata=yes, to delete the tapes from the copypool and adsm will recreate the tapes the next time you backup your primary storage pools. Jim Sporer At 03:54 PM 10/12/2000 -0400, you wrote: >Anyone had any experience with recovering copypool (offsite) data. > >Apparently the manager of our offsite storage location has lost several >tapes that ADSM considers part of the offsite copypool. > >upd vol xxx access=destroyed only works for primary storage pools > >How do I tell ADSM that tapes/data in the copy pool has been lost? > >Thanks, >Tom Fluker >Viasystems Technologies
Re: TSM Using Scratch instead of Filling Tapes
That is the way adsm works if your storage pool is collocated. The order of search for a tape is first a tape that already contains data for the node, and next an empty scratch tape. To force adsm to put more than one node on a tape you need to restrict the number of tapes available to the storage pool with the maxscratch parameter. Jim Sporer At 09:32 AM 10/10/2000 -0400, you wrote: >AIX 4.3.1, TSM 3.7.3.0, IBM3494, (2) IBM3590B1A > >Right now I have 50 tapes in my onsite tape pool and 22 of them are in a >'Filling' state. It seems that TSM is more often selecting a scratch tape >instead of a 'Filling' tape. These 'Filling' tapes aren't reclaimed, and I >was trying to consolidate by doing MOVE DATA commands. I would do a MOVE >DATA for a tape that was only <1% used, when that was completed, I issued >another MOVE DATA command for a different tape. The first MOVE DATA called >for a scratch, and the second one did also. Right now I have a limited >number of 3590 tapes and the turn around to get more is a couple weeks. So, >I'm trying to limp along with what I have. Right now my library has 22 >'Filling' and 28 'Full' tapes. I can't do my copypool'n or DB backups. If I >do a MOVE DATA on a 'Filling' tape right now, it calls for an existing tape >as output and when done the input tape goes scratch. If I were to issue >anothe r MOVE DATA, it calls for the scratch tape I just freed up wiht the >first MOVE DATA. So, I have to MOVE DATA to get a scratch tape, and then do >a BA STG for my copypool to grab the scratch. Then I can do another MOVE >DATA to free up another scratch tape. > >Has anyone seen this type of behavior out of TSM before? Last night before >my nightly backups I had 2 scratch, 20 'Filling' and 28 'Full' tapes in the >library. This morning I have 22 'Filling' and 28 'Full'. Why isn't TSM >calling for 'Filling' tapes instead of scratch?!?!?!?!?!?! > >Bill Boyer >DSS, Inc. >"I haven't lost my mind -- it's backed up on tape somewhere." - ???
Re: backup copy pools
What is your mountlimit set to for the device class 3590tape? Jim Sporer At 09:12 AM 9/18/2000 -0500, you wrote: >I am trying to backup my disk pool to a tape pool. I need to run multiple >session to get a decent backup time but I can't seem to get it to run >multiple sessions. Any advice? > >AIX - 4.3.3 >ADSM Server - 3.1.2.40 > >adsm> q sch dr_pr1 t=a f=d > > Schedule Name: DR_PR1 >Description: >Command: ba stg db_dpool dr_pr1db1 maxpr=3 > Priority: 7 >Start Date/Time: 09/11/00 23:00:00 > Duration: 1 Hour(s) > Period: 1 Day(s) >Day of Week: Any > Expiration: >Active?: Yes >Last Update by (administrator): ADMIN > Last Update Date/Time: 09/14/00 17:21:43 > Managing profile: > > >adsm> q stg db_dpool f=d > >Storage Pool Name: DB_DPOOL >Storage Pool Type: Primary >Device Class Name: DISK > Estimated Capacity (MB): 373,632.0 > Pct Util: 25.1 > Pct Migr: 25.1 > Pct Logical: 100.0 > High Mig Pct: 1 > Low Mig Pct: 1 > Migration Delay: 0 > Migration Continue: Yes > Migration Processes: 6 >Next Storage Pool: DB_TPOOL > Reclaim Storage Pool: > Maximum Size Threshold: No Limit > Access: Read/Write > Description: >Overflow Location: >Cache Migrated Files?: No > Collocate?: >Reclamation Threshold: > Maximum Scratch Volumes Allowed: >Delay Period for Volume Reuse: > Migration in Progress?: Yes > Amount Migrated (MB): 337,662.00 >Elapsed Migration Time (seconds): 155,146 > Reclamation in Progress?: > Volume Being Migrated/Reclaimed: > Last Update by (administrator): ADMIN >Last Update Date/Time: 09/18/00 03:00:02 > > > >adsm> q stg dr_pr1db1 f=d > >Storage Pool Name: DR_PR1DB1 >Storage Pool Type: Copy >Device Class Name: 3590TAPE > Estimated Capacity (MB): 200,478,940.6 > Pct Util: 0.4 > Pct Migr: > Pct Logical: 99.7 > High Mig Pct: > Low Mig Pct: > Migration Delay: > Migration Continue: > Migration Processes: >Next Storage Pool: > Reclaim Storage Pool: > Maximum Size Threshold: > Access: Read/Write > Description: >Overflow Location: >Cache Migrated Files?: > Collocate?: No >Reclamation Threshold: 100 > Maximum Scratch Volumes Allowed: 9,999 >Delay Period for Volume Reuse: 0 Day(s) > Migration in Progress?: > Amount Migrated (MB): >Elapsed Migration Time (seconds): > Reclamation in Progress?: No > Volume Being Migrated/Reclaimed: > Last Update by (administrator): ADMIN >Last Update Date/Time: 09/10/00 18:56:26 > > > >Thanks in advance >Becky Davidson >Data Manager/AIX Administrator >EDS/Earthgrains >voice: 314-259-7589 >fax: 314-877-8589 >email: [EMAIL PROTECTED]
