Re: Missing device for library media changer.
Thanks to Richard, Jeff, Richard C, and John for the helpful insights. I have passed the information to our AIX guy. I will let you know the outcome. Thanks again, Larry -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Talafous, John Sent: Tuesday, June 06, 2006 3:33 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Missing device for library media changer. Being that this environment has a few elements of virtualization involved, have the software layers and drivers that present the Quantum ATL emulation to the EMC CDL and then present this to AIX 5.3.0.4 been reviewed and verified in entirety? TSM can only see what the operating system offers. Hence, if after using the library definition technique presented by Richard, I would suggest researching software entities and how they play together. Is the EMC CDL emulation supported under AIX 5.3? You may be in a 'finger pointing' environment which could be difficult for any support line to diagnose. Larry, I understand, give me a call/email should you wish to discuss. 8-) John G. Talafous (fous) Berbee Information Networks [EMAIL PROTECTED] http://www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard van Denzel Sent: Tuesday, June 06, 2006 2:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Missing device for library media changer. Have you created the device through Smit -> Devices -> TSM Devices? Because it's not an IBM device, AIX will not recognize it by default, but it has to be created using the TSM device driver. So what's new with the ping-pong within IBM :-(, if it's a software problem they will defer you to hardware who In it's turn will send you back to software again. Met vriendelijke groet, with kind regards, Richard van Denzel -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens Mcnutt, Larry E. Verzonden: dinsdag 6 juni 2006 20:04 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] Missing device for library media changer. AIX 5.3.0.4 TSM 5.3.3.0 EMC CDL emulating a Quantum P7000 ATL We are currently running on a P650 with AIX 5.2.0.1, TSM 5.2.3.0 and the same EMC CDL library. On Sunday we tried to upgrade to a P570 AIX 5.3.0.4, TSM 5.3.3.0. We were able to get through the TSM part of the upgrade. The problem we are not able to resolve is getting AIX to "see" the device for the library media changer. On the old system this is /dev/lb0. We could see all 16 drives in AIX and in TSM. We have a PMR open and have been bounced between AIX and TSM with no answer yet. Looking for some wisdom from the list. Thanks, Larry McNutt The Timken Company - This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company / The Timken Corporation
Re: Missing device for library media changer.
Being that this environment has a few elements of virtualization involved, have the software layers and drivers that present the Quantum ATL emulation to the EMC CDL and then present this to AIX 5.3.0.4 been reviewed and verified in entirety? TSM can only see what the operating system offers. Hence, if after using the library definition technique presented by Richard, I would suggest researching software entities and how they play together. Is the EMC CDL emulation supported under AIX 5.3? You may be in a 'finger pointing' environment which could be difficult for any support line to diagnose. Larry, I understand, give me a call/email should you wish to discuss. 8-) John G. Talafous (fous) Berbee Information Networks [EMAIL PROTECTED] http://www.berbee.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard van Denzel Sent: Tuesday, June 06, 2006 2:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Missing device for library media changer. Have you created the device through Smit -> Devices -> TSM Devices? Because it's not an IBM device, AIX will not recognize it by default, but it has to be created using the TSM device driver. So what's new with the ping-pong within IBM :-(, if it's a software problem they will defer you to hardware who In it's turn will send you back to software again. Met vriendelijke groet, with kind regards, Richard van Denzel -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens Mcnutt, Larry E. Verzonden: dinsdag 6 juni 2006 20:04 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] Missing device for library media changer. AIX 5.3.0.4 TSM 5.3.3.0 EMC CDL emulating a Quantum P7000 ATL We are currently running on a P650 with AIX 5.2.0.1, TSM 5.2.3.0 and the same EMC CDL library. On Sunday we tried to upgrade to a P570 AIX 5.3.0.4, TSM 5.3.3.0. We were able to get through the TSM part of the upgrade. The problem we are not able to resolve is getting AIX to "see" the device for the library media changer. On the old system this is /dev/lb0. We could see all 16 drives in AIX and in TSM. We have a PMR open and have been bounced between AIX and TSM with no answer yet. Looking for some wisdom from the list. Thanks, Larry McNutt The Timken Company - This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company / The Timken Corporation
Re: Missing device for library media changer.
Have you created the device through Smit -> Devices -> TSM Devices? Because it's not an IBM device, AIX will not recognize it by default, but it has to be created using the TSM device driver. So what's new with the ping-pong within IBM :-(, if it's a software problem they will defer you to hardware who In it's turn will send you back to software again. Met vriendelijke groet, with kind regards, Richard van Denzel -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Namens Mcnutt, Larry E. Verzonden: dinsdag 6 juni 2006 20:04 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] Missing device for library media changer. AIX 5.3.0.4 TSM 5.3.3.0 EMC CDL emulating a Quantum P7000 ATL We are currently running on a P650 with AIX 5.2.0.1, TSM 5.2.3.0 and the same EMC CDL library. On Sunday we tried to upgrade to a P570 AIX 5.3.0.4, TSM 5.3.3.0. We were able to get through the TSM part of the upgrade. The problem we are not able to resolve is getting AIX to "see" the device for the library media changer. On the old system this is /dev/lb0. We could see all 16 drives in AIX and in TSM. We have a PMR open and have been bounced between AIX and TSM with no answer yet. Looking for some wisdom from the list. Thanks, Larry McNutt The Timken Company - This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company / The Timken Corporation
Missing device for library media changer.
AIX 5.3.0.4 TSM 5.3.3.0 EMC CDL emulating a Quantum P7000 ATL We are currently running on a P650 with AIX 5.2.0.1, TSM 5.2.3.0 and the same EMC CDL library. On Sunday we tried to upgrade to a P570 AIX 5.3.0.4, TSM 5.3.3.0. We were able to get through the TSM part of the upgrade. The problem we are not able to resolve is getting AIX to "see" the device for the library media changer. On the old system this is /dev/lb0. We could see all 16 drives in AIX and in TSM. We have a PMR open and have been bounced between AIX and TSM with no answer yet. Looking for some wisdom from the list. Thanks, Larry McNutt The Timken Company - This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company / The Timken Corporation
Re: ? Should we set Resourceutilization > 10 if appropriate ?
I have experimented with resourceutilization values above 10, but we do not use them in production. You are correct that IBM does not support them and the documentation says the highest value is 10. As far as I can tell, they don't hard code any limit. If the communication method is TCP, I have tested it at 60 and seen 50 some threads created. Although, as you say, the greater number of threads just had to wait longer and didn't produce any faster aggregate speed. If the communication method is shared mem, then the limit is 30 on Solaris. You can set resourceutilization as high as you want, but you won't start more than 30 threads. This is a consequence of the fact that dsmserv allocates a fixed memory buffer for client-server communication. This is only sufficient to sustain 30 client threads. Once clients are at/near the limit of 30, you will get a shared memory error if you try to start a client. The fixed memory buffer size used by dsmserv was coded many years ago when prevailing server memory sizes were much smaller than today. I submitted an enhancement request to increase this a few weeks ago. dsmc threads increase and decrease throughout the backup job. It starts one producer threads for each file system that it backs up. Each producer thread can start one or more consumer threads. The number of consumer threads seems to depend on how busy they are kept. As more files are found by producer thread that need to be backed up and all consumer threads are busy, then it will spin up more consumer threads. Conversely, once the demand for consumer threads subsides, it will eventually kill some of them. Resourceutilization parms above 10 offer potential benefits by starting more producer threads, assuming that the backup time is bound primarily by the time to examine all the files. This could also be achieved by starting separate dsmc backups for specified file system sets. Roy J. Martin mailto:[EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roger Deschner Sent: Tuesday, June 06, 2006 10:56 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: ? Should we set Resourceutilization > 10 if appropriate ? At one point I was tempted to do this, with a client who backs up 1tb/night. But it would not help, in fact things got slower as the numerous processes competed with each other and created worse disk I/O contention on BOTH the client and the server. Bandwidth utilization measured at the client NIC actually declined. You might have heard me whining about this problem on this list back in February of this year. What was effective, was attacking the backup performance problem at its source, by tuning the disk I/O subsystems on both the client and the server. At the server level, I had to work on both the disk storage pool which that client was backing up into, and the TSM database. There are no silver bullets here, but there might be bronze bullets - look at raising your TSM DB bufpoolsize, and also your OS' settings for disk buffers on the TSM disk storage pool volumes. More effective than that, however, was simply buying more disk drives for both the database and the storage pool, and spreading the I/O load out farther. The disk tuning worked. This client is now backing up in a reasonable time with RESOURCEUTILIZATION 10. But I watch it carefully. One of my key measures of TSM server performance is how long this huge client takes to back up. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Mon, 5 Jun 2006, James R Owen wrote: >Andy, et al. >[Is anyone out there using RESOURCEUTILZATION n w/ n > 10 ??] > >Andy Raibeck's presentation @ Oxford's 2001 TSM Symposium > http://tsm-symposium.oucs.ox.ac.uk/2001/papers/ > Raibeck.APeekUnderTheHood.PDF >includes this table showing what will result from setting: > >RESOURCEUTILIZATION n Max.Sess. ProducerSess. Threshold(Seconds) >- -- > 2 1 30 > 1 1 0 45 > 2 2 1 45 > 3 3 1 45 > 4 3 1 30 > 5 4 2 30 > 6 4 2 20 > 7 5 2 20 > 8 6 3 20 > 9 7 3 20 > 10 8 4 10 > (undocumented: > 11<=n<=100) n 0.5n10 > >and also includes these warnings: >Undocumented, internal values subject to change without notice. >RESOURCEUTILIZATION > 10 is unsupported. > >Management discourages use of undocumented/unsupported settings, but >I'm arguing that we need to specify RESOURCEUTILIZATI
Re: 3-Kinds of Tapes & Drives in 3494 ATL
-Zoltan Forray wrote: - >One other question that came to mind. > >Currently, our LM is controlled via ethernet/IP vs LTO2 libraries >which >use the SAN/a-drive path. Does the new controller improve upon this >or do >I have to go ask for another IP address ? The TSM server communicates with the library manager on the 3494 by way of a library manager daemon running on the same host as the TSM server. The TSM server will have a server to library path defined for each TSM library definition. As I noted previously, both server to library paths will use the same device specification. The configuration file for the library manager daemon specifies a mapping between device names and IP addresses for physical libraries. Since both server to library paths use the same device, the daemon will send commands for both TSM libraries to the same IP address. Unless you go out of your way to change the daemon configuration, this will be the same IP address you are using now.
Re: 3-Kinds of Tapes & Drives in 3494 ATL
Thank you. That is what I was hoping for. One other question that came to mind. Currently, our LM is controlled via ethernet/IP vs LTO2 libraries which use the SAN/a-drive path. Does the new controller improve upon this or do I have to go ask for another IP address ? Thomas Denier <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 06/06/2006 11:31 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] 3-Kinds of Tapes & Drives in 3494 ATL -Zoltan Forray wrote: - >We are getting ready to upgrade our 3494 ATL with 3592-E05 drives >(and other stuff like library manager, etc) and I am looking for >information from someone who has such a configuration. > >Currently, we share the library between our z/OS MF (3590B/J - ESCON) >and 2-AIX and 2-Linux TSM servers (3590E/K - SAN). We have two mainframe Linux TSM servers and three z/OS systems sharing a 3494. The TSM servers use both 3590 and 3592 drives and media. >I am concerned about the mix of K and whatever type tapes the 3592 >drives will use, since each TSM server will be using both types of media >(can we say 80GB DB backup on a 1TB tape..NO !) > >How do you control which processes use which drives within the same >library ? I know the device class has options for 3592 types, but >you have to define it within the same library ? Will this work ? You will have to define a separate library for the 3592 drives and media, with its own set of category values. You will have to define a path between the server and the new library. This will specify the same device as the path from the server to the current 3590 library. The common device name is what causes mount, dismount, and category change requests for both TSM libraries to be sent to the same 3494. >Does the new library manager hardware/software give us the capability >to connect with multiple links from the same TSM server, as separate >"libraries" so library definitions can separate the category codes >and we can define two libraries to each TSM server ?
Re: 3-Kinds of Tapes & Drives in 3494 ATL
-Zoltan Forray wrote: - >We are getting ready to upgrade our 3494 ATL with 3592-E05 drives >(and other stuff like library manager, etc) and I am looking for >information from someone who has such a configuration. > >Currently, we share the library between our z/OS MF (3590B/J - ESCON) >and 2-AIX and 2-Linux TSM servers (3590E/K - SAN). We have two mainframe Linux TSM servers and three z/OS systems sharing a 3494. The TSM servers use both 3590 and 3592 drives and media. >I am concerned about the mix of K and whatever type tapes the 3592 >drives will use, since each TSM server will be using both types of media >(can we say 80GB DB backup on a 1TB tape..NO !) > >How do you control which processes use which drives within the same >library ? I know the device class has options for 3592 types, but >you have to define it within the same library ? Will this work ? You will have to define a separate library for the 3592 drives and media, with its own set of category values. You will have to define a path between the server and the new library. This will specify the same device as the path from the server to the current 3590 library. The common device name is what causes mount, dismount, and category change requests for both TSM libraries to be sent to the same 3494. >Does the new library manager hardware/software give us the capability >to connect with multiple links from the same TSM server, as separate >"libraries" so library definitions can separate the category codes >and we can define two libraries to each TSM server ?
3-Kinds of Tapes & Drives in 3494 ATL
We are getting ready to upgrade our 3494 ATL with 3592-E05 drives (and other stuff like library manager, etc) and I am looking for information from someone who has such a configuration. Currently, we share the library between our z/OS MF (3590B/J - ESCON) and 2-AIX and 2-Linux TSM servers (3590E/K - SAN). I am concerned about the mix of K and whatever type tapes the 3592 drives will use, since each TSM server will be using both types of media (can we say 80GB DB backup on a 1TB tape..NO !) How do you control which processes use which drives within the same library ? I know the device class has options for 3592 types, but you have to define it within the same library ? Will this work ? Does the new library manager hardware/software give us the capability to connect with multiple links from the same TSM server, as separate "libraries" so library definitions can separate the category codes and we can define two libraries to each TSM server ?
Re: ? Should we set Resourceutilization > 10 if appropriate ?
At one point I was tempted to do this, with a client who backs up 1tb/night. But it would not help, in fact things got slower as the numerous processes competed with each other and created worse disk I/O contention on BOTH the client and the server. Bandwidth utilization measured at the client NIC actually declined. You might have heard me whining about this problem on this list back in February of this year. What was effective, was attacking the backup performance problem at its source, by tuning the disk I/O subsystems on both the client and the server. At the server level, I had to work on both the disk storage pool which that client was backing up into, and the TSM database. There are no silver bullets here, but there might be bronze bullets - look at raising your TSM DB bufpoolsize, and also your OS' settings for disk buffers on the TSM disk storage pool volumes. More effective than that, however, was simply buying more disk drives for both the database and the storage pool, and spreading the I/O load out farther. The disk tuning worked. This client is now backing up in a reasonable time with RESOURCEUTILIZATION 10. But I watch it carefully. One of my key measures of TSM server performance is how long this huge client takes to back up. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Mon, 5 Jun 2006, James R Owen wrote: >Andy, et al. >[Is anyone out there using RESOURCEUTILZATION n w/ n > 10 ??] > >Andy Raibeck's presentation @ Oxford's 2001 TSM Symposium > http://tsm-symposium.oucs.ox.ac.uk/2001/papers/ > Raibeck.APeekUnderTheHood.PDF >includes this table showing what will result from setting: > >RESOURCEUTILIZATION n Max.Sess. ProducerSess. Threshold(Seconds) >- -- > 2 1 30 > 1 1 0 45 > 2 2 1 45 > 3 3 1 45 > 4 3 1 30 > 5 4 2 30 > 6 4 2 20 > 7 5 2 20 > 8 6 3 20 > 9 7 3 20 > 10 8 4 10 > (undocumented: > 11<=n<=100) n 0.5n10 > >and also includes these warnings: >Undocumented, internal values subject to change without notice. >RESOURCEUTILIZATION > 10 is unsupported. > >Management discourages use of undocumented/unsupported settings, >but I'm arguing that we need to specify RESOURCEUTILIZATION 30 >in order to effect efficient backups for our email servers: > 4 IMAP servers, each w/4 CPUs, running linux client 5.2.3, > each backs up 15 FS sending ~200GB/night (compressed) > via 100Mb -> Gb ethernet > to our TSM 5.2.3 service's disk stgpool > >With RESOURCEUTILIZATION 10 specified, we never see more than 8 >simultaneous FS backups, and some of 8 large IMAP filesystems are >always the last backups to start, serially after other smaller FS >backups complete! Testing w/ RESOURCEUTILIZATION 30 causes one >client to start up 31 sessions enabling all 15 FS backups to start >essentially simultaneously. I expect the smaller FS backups will >complete first w/ the 8 larger IMAP FS backups completing later, but >w/ all FS backups for each client finishing faster because none will >wait to start serially after other FS backups because insufficient >backup sessions were started. > >Asking only for your own advice, recognizing IBM probably does not >allow you recommend using unsupported/undocumented optional settings: > >Is my understanding of the unsupported/undocumented setting (w/ N>10) >correct? Are we risking some unanticipated problems trying to use >RESOURCEUTILIZAION 30 to backup all four of these email servers >simultaneously? [I believe we have sufficient network bandwidth, >disk I/O capacity and CPU's for TSM clients and service.] > >Is there some important reason that IBM did not choose to document >and support N>10 for RESOURCEUTILIZATION? [The higher settings would >seem to be useful and appropriate for some high-bandwidth circumstances, >or did I miss something?] > >Is there a simple way to specify the order in which FS are selected for >backup when multi-threading is active? > >Thanks [hoping] for your advice! >-- >[EMAIL PROTECTED] (203.432.6693) >
upgrade questions
I have a question regarding the upgrade from 5.2.4 to 5.3.3 on a windows server. Anyone want to tell me it went smoothly? I hear there's a tool to estimate how long the upgrade will take, will someone point me in the right direction? About how long should I expect it to take from your experience? Brett
Reinstalling TSM Solaris client on system with Domino TDP
Since I have gotten no response to my earlier message about my constant problems with the Solaris Domino TDP client, we have decided to at least upgrade the base TSM client to 5.3.4 from 5.3.0.12. So, my question is this. Do I have to uninstall the TDP clients (6-per server x 6 servers) before I can install the latest TSM client ?
Re: TSM 5.2 and Celerra NAS
Bernaldo de Quiros, Iban 1 wrote: > Hi everybody, > > Could someone explain me how TSM works with a celerra NAS, because as > far as I know, we can not do a reclamation, and we can not move data > in the storage pool and many other things like we do in a normal > storage pool... > > I do not know how to re-use volumes... should Only set only retain > extra, and retain only in the copygroups...¿? > since nas (ndmp) backups only do full and differentials, your tapes will become empty all by themselves. No need to worry about reclamation. NDMP functionality is severely limitted, and hopefully now that IBM and NetApp are working coler together we might see better NDMP support in TSM. > Any recommendations of backup/archive policy are welcome !! > Full once a week, differentials on the other days. Keep your fulls for at least 4 versions to retain about a month of history. > Any help will be much appreciate there !! > > Thanks so much... > > Best Regards, > > Ibán Bernaldo de Quirós Márquez Technical Specialist cell: + 34 659 > 01 91 12 Sun Microsystems Iberia -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 3000Fax. +31 20 668 3167 PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16 B3F6 048A 02BF DC93 94EC "I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end." -- Douglas Adams
Re: adm login is locked!
Hello sir Thank you, you `ve been very helpfull. It`s all ok! VBRGDS, Usoltsev Alexandr a/c "Siberia Airlines" IT department, Novosibirsk E-MAIl: [EMAIL PROTECTED] Tel: +7 3832 106-858 Fax: +7 3832 106-853
TSM 5.2 and Celerra NAS
Hi everybody, Could someone explain me how TSM works with a celerra NAS, because as far as I know, we can not do a reclamation, and we can not move data in the storage pool and many other things like we do in a normal storage pool... I do not know how to re-use volumes... should Only set only retain extra, and retain only in the copygroups...¿? Any recommendations of backup/archive policy are welcome !! Any help will be much appreciate there !! Thanks so much... Best Regards, Ibán Bernaldo de Quirós Márquez Technical Specialist cell: + 34 659 01 91 12 Sun Microsystems Iberia
Re: Files stuck in disk stgpool
Roger, Why not have an additional "next" stgpool beyond your 10g tape pool with maybe one or two volumes allowed, and maxsize nolim? If a volume appears in the storage pool, then a "q content count=10" will usually be sufficient to pinpoint your more egregious nodes - you won't get many files of this size onto a single volume. If your objective is to prevent *any* tape mounts during backup, then assuming that you have sufficient random access disk storage pool, set its maxsize to nolim, and put any size filters on the subsequent pools in the heirarchy. Migration will then take care of the size filtering, and will use the "actual stored size" of the file, rather than the "size-on-client" - which is what happens during backup. [Thanks to R. Sims for that one] Regards Dave WindowsError 016: Recoverable error. System destroyed anyway. Dave Frost Technical Consultant SunGard Availability Services (UK) Limited London Technology Centre Heathrow Corporate Park Hounslow UK. TW4 6ER Tel: +44 (0) 800 2799 166 Fax: +(0) 20 8080 8112 mailto:[EMAIL PROTECTED] Keeping People and Information Connected (TM) http://www.availability.sungard.com Roger Deschner <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 05/06/2006 16:50 Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Files stuck in disk stgpool I'm looking for a strategy to attack a strange problem of stuck files and failing migration. In one heirarchy, I have a file size limit of 10g for the disk storage pool, and also a limit of 10g for the tape pool it migrates to. The idea is to prevent a client backup session from ever mounting a tape directly, which is very inefficient. We are using client compression. There exists a client somewhere, who has a 9.99gb file that is of a type that is already compressed (a jpeg photo, or a zip file, for instance). The server compares its 9.99gb size to the 10gb limit, and says "OK, back it up", and it comes down the wire into the disk storage pool. However, when it arrives, it has grown by being recompressed, so that now it is larger than 10gb. Now it's stuck in the disk stgpool, and cannot be migrated to tape. Migration processes repeatedly fail and are restarted. Things grind to a halt. This has now happened twice. My only fix is to temporarily raise the tape pool's limit to get the stuck file migrated. However, this could allow a client backup session to mount a tape. Anybody got any better ideas? Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
Re: adm login is locked!
Hot Diggety! Alexandr was rumored to have written: > I`ve installed TSM sever and client (full pack) on the same > server(AIX). > Have registred client node on the server TSM.(input correct pwd for > registred client node). All it was working well for long time. > But after long off-working time was tring connect to tivoli-server under > admin-login and have got message: > > "..ANS8056E Your administrator ID is locked. > ANS8023E Unable to establish session with server. > > ANS8002I Highest return code was 61." > > How unlocked administrator ID? > May be exist any method of restore access to server without re-install > server? You do not need to reinstall the TSM server. What TSM server version are you using? Do you have any other administrator IDs? If yes: login to another admin ID then do in dsmadmc: tsm> unlock administrator If no: login to TSM server, and use UNIX shell to do: # kill -HUP && sleep 5 \ && kill -KILL # DSMSERV_DIR=/usr/tivoli/tsm/server/bin # DSMSERV_CONFIG=/usr/tivoli/tsm/server/bin/dsmserv.opt # cd /usr/tivoli/tsm/server/bin # ./dsmserv tsm> disable sessions tsm> unlock admin tsm> halt # nohup /etc/rc.adsmserv & Then wait for the TSM server to come back up. You will be able to login in dsmadmc when it is back up. Then investigate to see why admin ID was locked. Did it expire? tsm> query admin f=d Example: tsm> query admin alex f=d Your account was locked due to either: 1. Exceeding maximum number of invalid admin sign-ons or 2. Your password expired If your password was expired, then either set a longer password expiry period or change your password more often. -Dan
