Re: Error when using server-to-server communication
Thanks a lot -Original Message- From: John Raj [mailto:[EMAIL PROTECTED] Sent: Fri 6/11/2004 11:12 AM To: [EMAIL PROTECTED] Cc: Subject: Re: Error when using server-to-server communication Your LLAddress is wrong. It should be the port in which the server acccepts communication which is 1500 not 1580. John Raj. nghiatd [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COM.VN cc: Sent by: Subject: Error when using server-to-server communication ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 06/10/2004 12:35 PM Please respond to ADSM: Dist Stor Manager Hi all, I have two TSM servers (assuming their name are A and B) and I establish server-to-server communication. In A_server, I did : DEFine SERver B PAssword admin HLAddress=192.168.131.168 LLAddress=1580 COMMmethod=TCPIP URL=http://192.168.131.168:1580 NODEName=A In B_server, I did the same command but when I used 'ping server' command I got error message : ANR1705W Ping for server 'B' was not able to establish a connection Can anyone help me ? Thans so much, Nghiatd
Antwort: Re: Error when using server-to-server communication
Hi, DEFine SERver B PAssword PAssword should be SERVERPAssword as well funnily enough there is no error message when you only use password. -DEFine--SERver--server_name--SERVERPAssword--=--password Best Regards Markus Veit An: [EMAIL PROTECTED] Kopie: Thema: Re: Error when using server-to-server communication [EMAIL PROTECTED] Received : 11.06.2004 07:26 Bitte antworten an ADSM: Dist Stor Manager Your LLAddress is wrong. It should be the port in which the server acccepts communication which is 1500 not 1580. John Raj. nghiatd [EMAIL PROTECTED]To: [EMAIL PROTECTED] .COM.VN cc: Sent by: Subject: Error when using server-to-server communication ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 06/10/2004 12:35 PM Please respond to ADSM: Dist Stor Manager Hi all, I have two TSM servers (assuming their name are A and B) and I establish server-to-server communication. In A_server, I did : DEFine SERver B PAssword admin HLAddress=192.168.131.168 LLAddress=1580 COMMmethod=TCPIP URL=http://192.168.131.168:1580 NODEName=A In B_server, I did the same command but when I used 'ping server' command I got error message : ANR1705W Ping for server 'B' was not able to establish a connection Can anyone help me ? Thans so much, Nghiatd
Prevent/Allow Media Removal - 3583
Hi all, The I/O station in our 3583 has become permanently locked meaning I have to take the library offline and open the entire door to insert or remove volumes. I have done a bit of research and have found this pdf: http://www-900.ibm.com/cn/support/library/storage/download/3583%20SCSI%2 0reference%20.pdf http://www-900.ibm.com/cn/support/library/storage/download/3583%20SCSI% 20reference%20.pdf (Page 68) which states that: Prevent: The Prevent bit indicates the following: 0 allows the opening of the I/O station. 1 prevents the opening of the I/O station. This field is applicable until a power-on reset or command reset is performed, or until all initiators have issued an ALLOW MEDIUM REMOVAL command by setting the Prevent field to 0. Does anyone know: a) How to check what the bit value currently is (presumably it is set to: 1 at the moment) b) What may have caused it and c) How to set it back so I can start using the I/O station again. Many thanks. Copperfield Adams IT Department WRC Holdings Limited [EMAIL PROTECTED] This email and any files transmitted with it are confidential and intended solely for the individual(s) or entity(s) to whom it is addressed. Any views or opinions presented or expressed herein, are those of the author(s), and may not necessarily represent those of WWAV Rapp Collins Group or it's affiliates and representatives. No representation is given nor any liability accepted for the accuracy or completeness of any information contained in this email unless expressly stated to the contrary. Neither is any liability accepted for any damage or financial or personal loss howsoever caused as a result of using the information or data contained within this email. If you are not the intended recipient(s) and/or have received this email in error, you may not use, disseminate, store, forward, print or copy it, in any method or form, either digital or otherwise. You must delete it completely from your system(s) and notify the sender that you received it, so we can ensure it does not happen again. Registered Office: 1 Riverside, Manbre Road, London UK, W6 9WA. Registered in England No. 1581935.
TSM Client Installation on AIX
Hello, Can any one give me the details to configure the client in the AIX, I am Installing the Client on AIX for the first time and I dont have much knowledge on AIX too. It will be very helpful. Tnanks in Advance Regards Sujay Dinakar R. __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/
TSM on zLinux
Hi TSMers, we are looking at possible Platforms for TSM. Is there anybody out there willing to share experience (online or offline) about TSM on zLinux? I don´t seem to be able to find much about it on the list. Mit freundlichen Grüßen, Markus Engelhard IT531 Storage Recovery Deutsche Bundesbank Wilhelm-Epstein-Straße 14 60431 Frankfurt am Main Tel. +49 69 9566 -6104 email: [EMAIL PROTECTED] -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. __ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.
Re: Hey Big Blue....Why not MOVE DATA across copy pools?!?
Hi Bill, As you might expect I avoid shooting myself in the footbut compost happens. :) Any number of commands if not used properly could destroy integrity of backups, none the less they are still usefull to have. Generally speaking, I try not to think of auditorsIt is similar to the anticipation one feels prior to an enema. :) My primary pool is 40TB...backing it up to a new copypool would present a number of problems for me. Dave Nicholson Whirlpool Corporation William F. Colwell [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/10/2004 06:01 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Hey Big BlueWhy not MOVE DATA across copy pools?!? At 07:56 AM 6/10/2004, 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) No! It would not be nice - unless you like shooting yourself in the foot. Anything that lets you alter a backup destroys the integrity of the backup. Think of your auditors - if they understood how good tsm is, this command would destroy all their confidence. If you have gone to the trouble of collocating the primary pool with move nodedata commands, you can collocate the offsite pool by defining a new copypool and backing up to it. After the new pool is all offsite, delete the volumes in the old copypool with 'discarddata=yes'. I really hope this helps, Bill Colwell 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 -- Bill Colwell C. S. Draper Lab Cambridge Ma.
How do you handle retired nodes?
Hi Everyone . . . . . How do you handle retired Nodes? When a server (tsm client node) is retired, we need to keep the TSM node around until all backups are expired. This can be anywhere from a couple months to years depending on policies. This is normal, but we are going through a server consolidation project that is generating tons of retired servers. Retired nodes need to: - be around for restores - hang around until all data is expired (months or even years) - keep track of them for when they can be deleted - remember to exclude them when you are playing with lists of active nodes At first, we just disassociated the node from it's schedule and changed it's contact field to indicate it's retired status. Very quickly we found that there was no quick/easy way to tell active clients from retired clients. Next, we started to change the node name by adding a prefix to indicate the retired status. This has been good from our tsm admin point of view, but now the system admins don't know the node name for restores (or at least don't remember the new name that we tell them). This seems to be a problem categorizing nodes. TSM wants to categorize nodes by domain. It doesn't seem to have a way to categorize nodes within a domain. Question: What do you do? Thanks Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: TSM on zLinux
Hi Markus, I did the 5.2 TSM server Beta Test on a Z-Series Linux - SUSE9 Distro. z900, 3584 - LTO-2 drives, Ess (F20) storage. Let me know what you want to know. Our only issue with the whole testing was support from IBM in terms of z-Series Linux - skills seemed a bit lacking. (This might have changed in more recent times - have not persued it further, we eventually decided to go AIX on P-Series). Regards Christo - Original Message - From: Markus Engelhard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, June 11, 2004 2:45 PM Subject: TSM on zLinux Hi TSMers, we are looking at possible Platforms for TSM. Is there anybody out there willing to share experience (online or offline) about TSM on zLinux? I don´t seem to be able to find much about it on the list. Mit freundlichen Grüßen, Markus Engelhard IT531 Storage Recovery Deutsche Bundesbank Wilhelm-Epstein-Straße 14 60431 Frankfurt am Main Tel. +49 69 9566 -6104 email: [EMAIL PROTECTED] -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder E-Mails aus. Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. __ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail or of parts hereof is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses except in case of gross negligence or willful behaviour. Any e-mail messages from the Bank are sent in good faith, but shall not be binding or construed as constituting any kind of obligation on the part of the Bank.= __ E-mail Disclaimer and Company Information http://www.absa.co.za/ABSA/EMail_Disclaimer
Re: How do you handle retired nodes?
We have a domain called DISCO (short for Disconnected) where we move all the retired systems. We consider the node to have been deleted, so we keep the backup data for the RetainLast number of days (from the copygroup settings). Archive data is kept until expiration deletes it. We also change the node name, using the data of retirement in the new name. That forces the SysAdmins to have to contact us to do a restore, but then we have passwordaccess generate so they'd need a password reset anyway. Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup.
Re: Reclamation data loss scenario
Richard, You're right, of course, but in this case Bill was trying to balance risk of corrupted primary tapes vs. shortage of media. I sometimes find myself in the same situation. My recommendation was relative to that balance point. If you have the luxury of lots of tapes and library capacity, you can of course set the reuse delay for as long as you'd like. You're right about tape. I have thanked IBM several times in this forum for the idea of the copypool. It has saved us on at least three different occasions. My wife's company uses a different backup product and local drives that write one copy of each backup. She longs for TSM's functionality. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/10/2004 06:49 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Reclamation data loss scenario You really only need to set the reuse delay long enough to ensure that you have at least one good DB backup before reusing the volume. ... That reminds me of the scene in The Court Jester where a knight pushes Danny Kaye out of the spot where lightning is about to strike. :-)) Our reality is that we don't know where lightning is about to strike. You don't know that a tape and its contained data are actually good until you really need it. That's why we increase the odds by making copy storage pool tapes, and why one really needs to keep multiple generations of DB backup tapes and a Reusedelay long enough to cover all of them. Tape is tape, operators are operators, and the random elements of this universe jump out of dark recesses to surprise and humble us when we believe we've thought of everything. Be cautious, and increase your odds. Richard Sims
Re: How do you handle retired nodes?
Richard, A command line query node shows the last time the node accessed the server, so that is what I do use to see a node is active or not. But I'm not working with tons of nodes. What if you create a retired domain for each domain where you have nodes that will be retired? After moving a node to the retired domain you won't have to change its name and your sysadmins what have to change their memories. The new domains should be transparent to them. Domains are free. Bill Smoldt STORServer, Inc. -Original Message- From: Richard Rhodes [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 6:38 AM To: [EMAIL PROTECTED] Subject: How do you handle retired nodes? Hi Everyone . . . . . How do you handle retired Nodes? When a server (tsm client node) is retired, we need to keep the TSM node around until all backups are expired. This can be anywhere from a couple months to years depending on policies. This is normal, but we are going through a server consolidation project that is generating tons of retired servers. Retired nodes need to: - be around for restores - hang around until all data is expired (months or even years) - keep track of them for when they can be deleted - remember to exclude them when you are playing with lists of active nodes At first, we just disassociated the node from it's schedule and changed it's contact field to indicate it's retired status. Very quickly we found that there was no quick/easy way to tell active clients from retired clients. Next, we started to change the node name by adding a prefix to indicate the retired status. This has been good from our tsm admin point of view, but now the system admins don't know the node name for restores (or at least don't remember the new name that we tell them). This seems to be a problem categorizing nodes. TSM wants to categorize nodes by domain. It doesn't seem to have a way to categorize nodes within a domain. Question: What do you do? Thanks Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: TSM Client Installation on AIX
Hi Sujay What version of AIX are you running ??? I just installed it on a AIX 4.3 Let me know if it's that version ... I will send you the procedure Luc Beaudoin Network Administrator / TSM / SAN Hopital General Juif S.M.B.D. Tel: (514) 340-8222 ext:4318 sujay dinakar [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 2004-06-11 06:52 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:TSM Client Installation on AIX Hello, Can any one give me the details to configure the client in the AIX, I am Installing the Client on AIX for the first time and I dont have much knowledge on AIX too. It will be very helpful. Tnanks in Advance Regards Sujay Dinakar R. __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/
Upgrade server 3.7.4 to 5.2
We are looking to upgrade a Windows TSM 3.7.4 server to the latest 5.2 version. Does anyone know the pitfalls of making this leap? Is there an intermediate release I must upgrade to first? I'd appreciate any recommendations, document references, etc. Many thanks, Rod Hroblak ADP __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/
Re: How do you handle retired nodes?
At first, we just disassociated the node from it's schedule and changed it's contact field to indicate it's retired status. Very quickly we found that there was no quick/easy way to tell active clients from retired clients. Would a command like select node_name from nodes where contact like '%retired%' provide an acceptable way of identifying the retired nodes?
Insufficient space in copypool
I'm trying to run three commands: backup stg directorypool copypool backup stg diskpool copypool backup stg tapepool copypool I get errors trying to run each command: ANR1221E BACKUP STGPOOL: Process 58 terminated - insufficient space in target copy storage pool. The thing is, I've got 14 scratch tapes in that library unassigned to any media pool. Almost as if TSM won't grab any of those tapes. Is there somewhere I can start looking to see why this would happen? Thanks in advace! Mike Bantz Systems Administrator Research Systems, Inc
SQL Time Construct
Is there a tms sql time contruct that will allow me to query all the entries with a start time greater than yesterday at 18:00? Specifically the query is: tsm: ULTSMselect entity,cast((cast(sum(bytes) as decimal(20,3))/1024/1024)+.05 as decimal(10,1)) as Migrated (MB) from summary where start_timecurrent_times tamp-1 day and activity='MIGRATION' group by entity except instead of going back 1 day I would like to check since yesterday at 18:00. David
Re: Insufficient space in copypool
Mike, Somewhere to look is at the detailed info for the storage pool you are trying to backup to. q stgpool stgpool_name f=d Look at the Maximum Scratch Volumes Allowed field and see what that value is. If you are pushing this limit with volumes in the stgpool then up it. HIH Steve -Original Message- From: Mike Bantz [mailto:[EMAIL PROTECTED] Sent: 11 June 2004 14:59 To: [EMAIL PROTECTED] Subject: Insufficient space in copypool This email and any files transmitted have been checked by the MessageLabs Virus Scanning Service for the presence of computer viruses. Please exercise caution when receiving any attachment(s) from unknown sources. If in any doubt, do not open any attachment and delete the message immediately. Thank you for your co-operation. _ I'm trying to run three commands: backup stg directorypool copypool backup stg diskpool copypool backup stg tapepool copypool I get errors trying to run each command: ANR1221E BACKUP STGPOOL: Process 58 terminated - insufficient space in target copy storage pool. The thing is, I've got 14 scratch tapes in that library unassigned to any media pool. Almost as if TSM won't grab any of those tapes. Is there somewhere I can start looking to see why this would happen? Thanks in advace! Mike Bantz Systems Administrator Research Systems, Inc __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Re: SQL Time Construct
Would this work? select entity,\ cast((cast(sum(bytes) as decimal(20,3))/1024/1024)+.05 as \ decimal(10,1)) as Migrated (MB) from summary where \ time(start_time)='18:00:00' and \ cast((current_timestamp-start_time)hours as decimal(8,0))24 \ and activity='MIGRATION' group by entity On Fri, 2004-06-11 at 10:01, David E Ehresman wrote: Is there a tms sql time contruct that will allow me to query all the entries with a start time greater than yesterday at 18:00? Specifically the query is: tsm: ULTSMselect entity,cast((cast(sum(bytes) as decimal(20,3))/1024/1024)+.05 as decimal(10,1)) as Migrated (MB) from summary where start_timecurrent_times tamp-1 day and activity='MIGRATION' group by entity except instead of going back 1 day I would like to check since yesterday at 18:00. David -- Mahesh Tailor WAN/TSM/NetView Administrator Carilion Health System Information Services 37 Reserve Avenue Roanoke, VA 24016 Phone: 540.224.3929 Fax: 540.224.3954
Re: Insufficient space in copypool
That's exactly what it was - me not understanding what MAXSCRATCH means. Now I know what it means. And now my DRM is running again. :-) Thanks for the wicked quick replies!!! - mike -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Copper, Steve Sent: Friday, June 11, 2004 8:06 AM To: [EMAIL PROTECTED] Subject: Re: Insufficient space in copypool Mike, Somewhere to look is at the detailed info for the storage pool you are trying to backup to. q stgpool stgpool_name f=d Look at the Maximum Scratch Volumes Allowed field and see what that value is. If you are pushing this limit with volumes in the stgpool then up it. HIH Steve -Original Message- From: Mike Bantz [mailto:[EMAIL PROTECTED] Sent: 11 June 2004 14:59 To: [EMAIL PROTECTED] Subject: Insufficient space in copypool This email and any files transmitted have been checked by the MessageLabs Virus Scanning Service for the presence of computer viruses. Please exercise caution when receiving any attachment(s) from unknown sources. If in any doubt, do not open any attachment and delete the message immediately. Thank you for your co-operation. _ I'm trying to run three commands: backup stg directorypool copypool backup stg diskpool copypool backup stg tapepool copypool I get errors trying to run each command: ANR1221E BACKUP STGPOOL: Process 58 terminated - insufficient space in target copy storage pool. The thing is, I've got 14 scratch tapes in that library unassigned to any media pool. Almost as if TSM won't grab any of those tapes. Is there somewhere I can start looking to see why this would happen? Thanks in advace! Mike Bantz Systems Administrator Research Systems, Inc __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Re: How do you handle retired nodes?
How do you get the data into the new domain? I didn't think you could move a node between domains. Do you setup new mgt classes with just the RetainLast policy and associate the node, in the new domain, to that mgt class? (same with the archive data . . . needing a policy for it that's the same as in the origional domain). Rick Nicholas Cassimatis To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: M Subject: Re: How do you handle retired nodes? Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU 06/11/2004 08:53 AM Please respond to ADSM: Dist Stor Manager We have a domain called DISCO (short for Disconnected) where we move all the retired systems. We consider the node to have been deleted, so we keep the backup data for the RetainLast number of days (from the copygroup settings). Archive data is kept until expiration deletes it. We also change the node name, using the data of retirement in the new name. That forces the SysAdmins to have to contact us to do a restore, but then we have passwordaccess generate so they'd need a password reset anyway. Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Reclamation data loss scenario
One way Bill could take advantage of REUSEDELAY's protection AND reduce the space required in the library is to just set REUSEDEALY on the OFFSITE copy pool. I've always figured that if I'm in desperate enough straights to restore the DB back several versions, I'm desperate enough to make a trip to the vault to get tapes ;) However, in that case, you can only restore back to the last version of the DB you have offsite, and I think Bill's original post said he wanted to get back as current as possible. -Original Message- From: Tab Trepagnier [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 8:57 AM To: [EMAIL PROTECTED] Subject: Re: Reclamation data loss scenario Richard, You're right, of course, but in this case Bill was trying to balance risk of corrupted primary tapes vs. shortage of media. I sometimes find myself in the same situation. My recommendation was relative to that balance point. If you have the luxury of lots of tapes and library capacity, you can of course set the reuse delay for as long as you'd like. You're right about tape. I have thanked IBM several times in this forum for the idea of the copypool. It has saved us on at least three different occasions. My wife's company uses a different backup product and local drives that write one copy of each backup. She longs for TSM's functionality. Thanks. Tab Trepagnier TSM Administrator Laitram, L.L.C. Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/10/2004 06:49 PM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Reclamation data loss scenario You really only need to set the reuse delay long enough to ensure that you have at least one good DB backup before reusing the volume. ... That reminds me of the scene in The Court Jester where a knight pushes Danny Kaye out of the spot where lightning is about to strike. :-)) Our reality is that we don't know where lightning is about to strike. You don't know that a tape and its contained data are actually good until you really need it. That's why we increase the odds by making copy storage pool tapes, and why one really needs to keep multiple generations of DB backup tapes and a Reusedelay long enough to cover all of them. Tape is tape, operators are operators, and the random elements of this universe jump out of dark recesses to surprise and humble us when we believe we've thought of everything. Be cautious, and increase your odds. Richard Sims
Re: Insufficient space in copypool
Check the maxscratch setting in copypool. -Original Message- From: Mike Bantz [mailto:[EMAIL PROTECTED] Sent: June 11, 2004 8:59 AM To: [EMAIL PROTECTED] Subject: Insufficient space in copypool I'm trying to run three commands: backup stg directorypool copypool backup stg diskpool copypool backup stg tapepool copypool I get errors trying to run each command: ANR1221E BACKUP STGPOOL: Process 58 terminated - insufficient space in target copy storage pool. The thing is, I've got 14 scratch tapes in that library unassigned to any media pool. Almost as if TSM won't grab any of those tapes. Is there somewhere I can start looking to see why this would happen? Thanks in advace! Mike Bantz Systems Administrator Research Systems, Inc
Re: How do you handle retired nodes?
Rick, Update node nodename domain=new domain To create the domain just use copy domain old domain name new domain name You don't move the data - TSM still knows where it is. If you perform another backup from the node all the files are bound to the new management classes, but it doesn't matter if they are or not if the retention will be the same on both. Bill smoldt STORServer, Inc -Original Message- From: Richard Rhodes [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 8:42 AM To: [EMAIL PROTECTED] Subject: Re: How do you handle retired nodes? How do you get the data into the new domain? I didn't think you could move a node between domains. Do you setup new mgt classes with just the RetainLast policy and associate the node, in the new domain, to that mgt class? (same with the archive data . . . needing a policy for it that's the same as in the origional domain). Rick Nicholas Cassimatis To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: M Subject: Re: How do you handle retired nodes? Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU 06/11/2004 08:53 AM Please respond to ADSM: Dist Stor Manager We have a domain called DISCO (short for Disconnected) where we move all the retired systems. We consider the node to have been deleted, so we keep the backup data for the RetainLast number of days (from the copygroup settings). Archive data is kept until expiration deletes it. We also change the node name, using the data of retirement in the new name. That forces the SysAdmins to have to contact us to do a restore, but then we have passwordaccess generate so they'd need a password reset anyway. Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: How do you handle retired nodes?
Moving a client to a new domain is as easy as update node blah domain=newdomainname. It doesn't move any data, existing data stays in the same storage pools. (The DESTINATION in the copy groups only affects NEWLY WRITTEN data, and you won't be writing any new data with these retired nodes). And you are correct that if the mgt classes/policies in the new domain are different than the old, you can get into a mess. Just navigate in the GUI to the original domain, and pull down OPERATIONS - COPY. TSM will let you copy the whole domain, including mgmt classes, copy groups and all, to a new domain with a different name. Then update the client to that domain. Now if your retired clients are in many domains now, to get around the policy issue you may want to create a shadow domain for each one. Domain1 - RETIRED_domain1 Domain2 - RETIRED_domain2 etc. Wanda Prather Johns Hopkins University Applied Physics Laboratory 443-778-8769 Intelligence has much less practical application than you'd think - Dilbert/Scott Adams -Original Message- From: Richard Rhodes [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 10:42 AM To: [EMAIL PROTECTED] Subject: Re: How do you handle retired nodes? How do you get the data into the new domain? I didn't think you could move a node between domains. Do you setup new mgt classes with just the RetainLast policy and associate the node, in the new domain, to that mgt class? (same with the archive data . . . needing a policy for it that's the same as in the origional domain). Rick Nicholas Cassimatis To: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: M Subject: Re: How do you handle retired nodes? Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU 06/11/2004 08:53 AM Please respond to ADSM: Dist Stor Manager We have a domain called DISCO (short for Disconnected) where we move all the retired systems. We consider the node to have been deleted, so we keep the backup data for the RetainLast number of days (from the copygroup settings). Archive data is kept until expiration deletes it. We also change the node name, using the data of retirement in the new name. That forces the SysAdmins to have to contact us to do a restore, but then we have passwordaccess generate so they'd need a password reset anyway. Nick Cassimatis [EMAIL PROTECTED] He who laughs last has a good backup. - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Prevent/Allow Media Removal - 3583
Do you use the 3583 only for TSM? Did it work in the past? If this is a one-time thing, power the library off and on again. I've only had it happen once, and a power off fixed it. If it continues and you are attached to a WINDOWS host, check to make sure the Windows RSM service is disabled. If not, disable it and reboot Windows. -Original Message- From: Copperfield Adams [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 5:45 AM To: [EMAIL PROTECTED] Subject: Prevent/Allow Media Removal - 3583 Hi all, The I/O station in our 3583 has become permanently locked meaning I have to take the library offline and open the entire door to insert or remove volumes. I have done a bit of research and have found this pdf: http://www-900.ibm.com/cn/support/library/storage/download/3583%20SCSI%2 0reference%20.pdf http://www-900.ibm.com/cn/support/library/storage/download/3583%20SCSI% 20reference%20.pdf (Page 68) which states that: Prevent: The Prevent bit indicates the following: 0 allows the opening of the I/O station. 1 prevents the opening of the I/O station. This field is applicable until a power-on reset or command reset is performed, or until all initiators have issued an ALLOW MEDIUM REMOVAL command by setting the Prevent field to 0. Does anyone know: a) How to check what the bit value currently is (presumably it is set to: 1 at the moment) b) What may have caused it and c) How to set it back so I can start using the I/O station again. Many thanks. Copperfield Adams IT Department WRC Holdings Limited [EMAIL PROTECTED] This email and any files transmitted with it are confidential and intended solely for the individual(s) or entity(s) to whom it is addressed. Any views or opinions presented or expressed herein, are those of the author(s), and may not necessarily represent those of WWAV Rapp Collins Group or it's affiliates and representatives. No representation is given nor any liability accepted for the accuracy or completeness of any information contained in this email unless expressly stated to the contrary. Neither is any liability accepted for any damage or financial or personal loss howsoever caused as a result of using the information or data contained within this email. If you are not the intended recipient(s) and/or have received this email in error, you may not use, disseminate, store, forward, print or copy it, in any method or form, either digital or otherwise. You must delete it completely from your system(s) and notify the sender that you received it, so we can ensure it does not happen again. Registered Office: 1 Riverside, Manbre Road, London UK, W6 9WA. Registered in England No. 1581935.
Re: Possibly OT: How to diagnose 3494 ATL communications failures
Well, after further analysis, this topic has had some strange twists. Per some suggestions, I had IBM replace the NIC in the LM. This had absolutely no effect on the problem. I have been discussing this issue with our networking folks. Their initial review showed massive amounts of BROADCAST traffic on this subnet, which is a private, GIG-E internal network, with connections to the outside world, primarily for TSM backups traffic. I updated ATAPE, which was a bit behind. I could not see anything in the history of changes, that would address this kind of situation. Now, my networking folks have put a sniffer on this private subnet. Image my suprise when the biggest causer of broadcast traffic, is the TSM AIX server, itself ! They also said that the peak in broadcast traffic correlated to backup traffic from a box that is outside the private subnet (i.e. does not have a direct connection to the same switch). Anyone have any suggestions on why the TSM server would be doing this ? This is an AIX 5.1 TSM 5.2.1.3 system, that is *EXCLUSIVELY* used for TSM backups. Could this have anything to do with the HLADDRESS parms on the node definitions ? Possibly a bug that has been fixed in a later release of the TSM server ? *NOTHING* has changed on the AIX system for the past 6-months, when it comes to the AIX and TSM server software, itself ! The last upgrade was from AIX 4.3.3 to 5.1 and the TSM server, at the same time. Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 05/24/2004 07:41 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Possibly OT: How to diagnose 3494 ATL communications failur es This hardware/system has been in place for years, without change. My bets are on a problem with the LM itself. This weekend, the connection died, again. No non-distruptive attempts to restablish the connection with the LM, worked. Yes, both boxes could PING each other. As I told IBM, this is *NOT* a connectivity issue, in the lan/network sense. This is a the LM is not responding as an LM. The only way we got it to work was to reinitialize the LAN ports from the LM/ATL. Well, there has been change: it's gotten older! (I've become an expert on the subject.) You could be seeing the effects of a deteriorating network card or the like...which could be aggravated if the library is not on UPS or power that is otherwise conditioned. Watch out also if the library is not behind a firewall. I worry about these embedded system computers in that they rarely see any updates, and yet we know that holes in operating systems are periodically found. In the right network circumstances, odd behavior from such a system may be the result of someone trying to hack the box. me again, Richard Sims
Re: Possibly OT: How to diagnose 3494 ATL communications failur es
Sounds like more of a networking issue. You might consider some subnet routing of the traffic, so you don't blast it everywhere on your local subnet. something like route add net 172.4.0.0/16 10.23.21.2 1 Where you are trying to get traffic for the 172.4.x.x subnet routed through a router/machine 10.23.21.2 ... LOL ... JC -Original Message- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 10:41 AM To: [EMAIL PROTECTED] Subject: Re: Possibly OT: How to diagnose 3494 ATL communications failures Well, after further analysis, this topic has had some strange twists. Per some suggestions, I had IBM replace the NIC in the LM. This had absolutely no effect on the problem. I have been discussing this issue with our networking folks. Their initial review showed massive amounts of BROADCAST traffic on this subnet, which is a private, GIG-E internal network, with connections to the outside world, primarily for TSM backups traffic. I updated ATAPE, which was a bit behind. I could not see anything in the history of changes, that would address this kind of situation. Now, my networking folks have put a sniffer on this private subnet. Image my suprise when the biggest causer of broadcast traffic, is the TSM AIX server, itself ! They also said that the peak in broadcast traffic correlated to backup traffic from a box that is outside the private subnet (i.e. does not have a direct connection to the same switch). Anyone have any suggestions on why the TSM server would be doing this ? This is an AIX 5.1 TSM 5.2.1.3 system, that is *EXCLUSIVELY* used for TSM backups. Could this have anything to do with the HLADDRESS parms on the node definitions ? Possibly a bug that has been fixed in a later release of the TSM server ? *NOTHING* has changed on the AIX system for the past 6-months, when it comes to the AIX and TSM server software, itself ! The last upgrade was from AIX 4.3.3 to 5.1 and the TSM server, at the same time. Richard Sims [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 05/24/2004 07:41 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Possibly OT: How to diagnose 3494 ATL communications failur es This hardware/system has been in place for years, without change. My bets are on a problem with the LM itself. This weekend, the connection died, again. No non-distruptive attempts to restablish the connection with the LM, worked. Yes, both boxes could PING each other. As I told IBM, this is *NOT* a connectivity issue, in the lan/network sense. This is a the LM is not responding as an LM. The only way we got it to work was to reinitialize the LAN ports from the LM/ATL. Well, there has been change: it's gotten older! (I've become an expert on the subject.) You could be seeing the effects of a deteriorating network card or the like...which could be aggravated if the library is not on UPS or power that is otherwise conditioned. Watch out also if the library is not behind a firewall. I worry about these embedded system computers in that they rarely see any updates, and yet we know that holes in operating systems are periodically found. In the right network circumstances, odd behavior from such a system may be the result of someone trying to hack the box. me again, Richard Sims
database deadlock
TSM Server AIX 4.3.3 TSM Version 5.1.6.3 I've seen this error the past couple of weeks, not every day, but enough times get me wondering. It has always happens when the script runs to move drmedia from vault retrieve to courier retrieve. This causes the move to fail but I can run it again with success. The references I've been able to find on WWW don't exactly fit the situation or version. ANR0390W A server database deadlock situation has been encountered: lock request for transaction 0:1.2230998674 will be denied to resolve the deadlock. ANRD asvolacq.c(5752): ThreadId44 Error 262 getting volume name for volume 36750. ANRD asvolacq.c(3643): ThreadId44 Error 262 checking repair state for volume 36750. ANR0390W A server database deadlock situation has been encountered: lock request for transaction 0:1.2230998674 will be denied to resolve the deadlock. ANRD asvolacq.c(5752): ThreadId44 Error 262 getting volume name for volume 36750. ANRD asvolacq.c(3811): ThreadId44 Error 262 checking repair state for volume 36750. ANR6683I MOVE DRMEDIA: Volume U00010 was moved from VAULTRETRIEVE state to COURIERRETRIEVE. ANR0390W A server database deadlock situation has been encountered: lock request for transaction 0:1.2230999065 will be denied to resolve the deadlock. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 854-0975
Re: Possibly OT: How to diagnose 3494 ATL communications failures
...
Image my suprise when the biggest causer of broadcast traffic, is the TSM
AIX server, itself !
...
Zoltan - Good find!
I would like to see your network people narrow this down to get more
identifying details (protocol (TCP,UDP), port and packet type). You know
the clogging traffic is coming from the AIX system...but from what within
it?
If not from them, then consider doing an AIX iptrace, ipreport sampling of
network traffic during the client backup. You can also do 'netstat -s'
sampling and see what numbers are climbing as this is going on. AIX does
Path MTU Discovery, per its Network Options settings ('no' command) utilizing
ICMP packet attempts, which may have issues with router blocking.
'netstat -s' will show those numbers, among others.
Richard Sims
Server media mount not possible
From looking at the log below it looks like this backup failed because the backup could not mount a tape. The server logs do show migrations and reclamation running at this time. The disk pool itself is set to a size limit of 8GB. Could the reason be because, either the tape was in use during a reclamation process or because all drives were in use at the time the backup ran? Is there a way for me to see if all drives were in use at that time? It looks like TSM tries 3 times and fails instead of bumping a process, is this a correct assumption? 06/10/04 04:50:53 Normal File-- 2,358,534,824 /d1/backup/PSCONV/PSCONV_FULL_BACKUP_2004_06_09_020001.dmp.gz [Sent] 06/10/04 04:51:38 Normal File--12,157,222,912 /d1/backup/PSCONV/PSCONV_FULL_BACKUP_2004_06_10_020001.dmp ** Unsuccessful ** 06/10/04 04:51:38 ANS1114I Waiting for mount of offline media. 06/10/04 04:52:46 Retry # 1 Normal File--12,157,222,912 /d1/backup/PSCONV/PSCONV_FULL_BACKUP_2004_06_10_020001.dmp ** Unsuccessful ** 06/10/04 04:52:46 ANS1809W Session is lost; initializing session reopen procedure. 06/10/04 04:53:01 ... successful 06/10/04 04:54:06 Retry # 2 Normal File--12,157,222,912 /d1/backup/PSCONV/PSCONV_FULL_BACKUP_2004_06_10_020001.dmp ** Unsuccessful ** 06/10/04 04:54:06 ANS1809W Session is lost; initializing session reopen procedure. 06/10/04 04:54:20 ... successful 06/10/04 04:55:05 Retry # 3 Normal File--12,157,222,912 /d1/backup/PSCONV/PSCONV_FULL_BACKUP_2004_06_10_020001.dmp ** Unsuccessful ** 06/10/04 04:55:06 --- SCHEDULEREC STATUS BEGIN 06/10/04 04:55:06 Total number of objects inspected: 186,319 06/10/04 04:55:06 Total number of objects backed up: 250 06/10/04 04:55:06 Total number of objects updated: 0 06/10/04 04:55:06 Total number of objects rebound: 0 06/10/04 04:55:06 Total number of objects deleted: 0 06/10/04 04:55:06 Total number of objects expired: 27 06/10/04 04:55:06 Total number of objects failed: 0 06/10/04 04:55:06 Total number of bytes transferred: 3.27 GB 06/10/04 04:55:06 Data transfer time: 192.08 sec 06/10/04 04:55:06 Network data transfer rate:17,881.32 KB/sec 06/10/04 04:55:06 Aggregate data transfer rate: 2,661.80 KB/sec 06/10/04 04:55:06 Objects compressed by: 100% 06/10/04 04:55:06 Elapsed processing time: 00:21:30 06/10/04 04:55:06 --- SCHEDULEREC STATUS END 06/10/04 04:55:06 ANS1312E Server media mount not possible 06/10/04 04:55:06 --- SCHEDULEREC OBJECT END PEOPLESOFT-LATE-M-F 06/10/04 04:30:00 As always, thanks for the help. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 854-0975
Re: Server media mount not possible
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Gill, Geoffrey L. From looking at the log below it looks like this backup failed because the backup could not mount a tape. The server logs do show migrations and reclamation running at this time. The disk pool itself is set to a size limit of 8GB. Could the reason be because, either the tape was in use during a reclamation process or because all drives were in use at the time the backup ran? Is there a way for me to see if all drives were in use at that time? It looks like TSM tries 3 times and fails instead of bumping a process, is this a correct assumption? You could determine which drives had tapes mounted in them, but it would be a matter of piecing through the activity log looking for mounts and dismounts, which can be laborious. (This is one of those times that running DSMADMC -MOUNTMODE comes in handy.) Backups are the bottom of the job hierarchy with TSM; in other words, all other tape-related operations will take precedence over a backup if the backup is going to tape. (Restores, OTOH, are the top of the hierarchy and will preempt enough processes to get tape drives to perform its job.) A database deadlock is almost always caused by the same entry in the database being accessed by two (or more) different processes. (This is a reason why you don't want to run multiple concurrent MOVE NODEDATA or EXPORT NODE processes.) You probably had this situation going on--one more good reason not to run anything else during reclamations and inventory expirations. -- Mark Stapleton
Re: Server media mount not possible
You could determine which drives had tapes mounted in them, but it would be a matter of piecing through the activity log looking for mounts and dismounts, which can be laborious. ... There are third-party packages which do this kind of thing, to help make TSM administration a bit easier. Generally, though, it's largely a matter of spreading server administration processes and client sessions over time to minimize contention for serial resources like tape drives. Richard Sims
Add to wish list for future TSm version
Along with online db defrags and diskpool defrag/reclamation, I would really like to see a decent Client Option Set editor in the web admin gui. I had to resort to writing my own script to avoid the current one (feels like I'm back in the old line-mode TSO days on the mainframe!) Steve Schaub Systems Engineer II, Storage Systems Haworth, Inc 616-393-1457 (desk) 616-886-8821 (cell) [EMAIL PROTECTED]
Re: Add to wish list for future TSm version
Along with online db defrags and diskpool defrag/reclamation, I would really like to see a decent Client Option Set editor in the web admin gui. I had to resort to writing my own script to avoid the current one (feels like I'm back in the old line-mode TSO days on the mainframe!) I think the best solution is to follow the approach used in the Define Script command, where a File option allows whole replacement of the object from an externally edited file. I, too, hark from ye olde mainframe environment, and likewise cannot abide the thought of doing relative line number editing of live server structures, where it's far too easy to introduce an error in dissociated cause and effect. Richard Sims
How about mixed media (not drives) in an lto2 library?
I'm in the process of getting an new 3584 with LTO2 drives approved; our existing library is 3584/LTO1 SCSI. My plan is to run the two in parallel while debugging the new library/drives, and then drop the old unit off the configuration. But I plan on keeping about half the LTO1 tapes, for use in off-site copy pools. I'm planning on marking all the LTO2 tapes as 'scratch' and assigning the LTO1 tapes explicitly to selected pools that are not allowed to use scratch tapes. We have an LTO1 library in our D/R hotsite contract and don't want to renegotiate half-way into the contract. 1) Is this workable (assuming I get enough tapes in each of the copy pools)? 2) Will this work on TSM 5.1.x (currently on 5.1.6.3, need to see if it supports LTO2 yet) TIA Tom Kauffman NIBCO, Inc
Re: Add to wish list for future TSm version
Just as an FYI, TSMManager has a pretty cool and usefull Client Option Editor. Let you copy, update, etc, all GUI ! Steve Schaub [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 06/11/2004 01:36 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Add to wish list for future TSm version Along with online db defrags and diskpool defrag/reclamation, I would really like to see a decent Client Option Set editor in the web admin gui. I had to resort to writing my own script to avoid the current one (feels like I'm back in the old line-mode TSO days on the mainframe!) Steve Schaub Systems Engineer II, Storage Systems Haworth, Inc 616-393-1457 (desk) 616-886-8821 (cell) [EMAIL PROTECTED]
Re: Add to wish list for future TSm version
I would like a better user side GUI interface. This would keep down calls for simple restores. Basically, allow users to restore data they can read, to anywhere they have permissions to write to. (With auditing of course.) Also, allow an option for the end users (versus administrators) to only see data that they have permissions to read. And make it where the user would see as grayed out (or flagged appropriately) data that they should have available, but may be 'offline' for whatever reason. ... Ahhh... If wishes were nickels we would all be millionaires. :) ... Jack -Original Message- From: Steve Schaub [SMTP:[EMAIL PROTECTED] Sent: Friday, June 11, 2004 12:37 PM To: [EMAIL PROTECTED] Subject: Add to wish list for future TSm version Along with online db defrags and diskpool defrag/reclamation, I would really like to see a decent Client Option Set editor in the web admin gui. I had to resort to writing my own script to avoid the current one (feels like I'm back in the old line-mode TSO days on the mainframe!) Steve Schaub Systems Engineer II, Storage Systems Haworth, Inc 616-393-1457 (desk) 616-886-8821 (cell) [EMAIL PROTECTED]
