Re: TSM needs to prompt for the password but cannot prompt (resolved)
Hi Grigori, Yes, I have had tried, when I run dsmj, TSM ask user-id and password, input it, then, try to run dsmc in command, it's ok, no need password, but I found that TSM will lose uid and password if a shell process exits. But if I use gui, and do something in gui, then it will be saved. Thank you very much! Best Regards, William -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: Thursday, July 08, 2010 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM needs to prompt for the password but cannot prompt (problem) It looks you have lost saved password. Try to start dsmc or GUI on node without modifying dsm.opt and provide password ones. Maybe it will help to resolve your problem. Grigori G. Solonovitch Senior Technical Architect Information Technology Ahli United Bank Kuwait http://www.ahliunited.com.kw Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: grigori.solonovi...@ahliunited.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Thursday, July 08, 2010 5:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM needs to prompt for the password but cannot prompt (problem) Hello All, Yesterday, my linux server got hardware problem, and we fixed it, After reboot my TSM server and prepare to backup data, I get error: Node Name: NETAPP ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background. ANS2050E TSM needs to prompt for the password but cannot prompt because the process is running in the background. ANS1025E Session rejected: Authentication failure I find answer in TSM Message, and say You may use RUNASSERVICE option with PASSWORDACCESS PROMPT. Turn off RUNASSERVICE to be able to get prompted So should I modify passwordaccess generate to passwordaccess runasservice ? But why it was ok before this fix ??? Any idea? Many thanks! This is my dsm.sys: --- SErvername SHITSM01 COMMMethod TCPip TCPPort1500 TCPServeraddress 127.0.0.1 nodename NETAPP passwordaccess generate schedmode prompted TXNBYTELIMIT 5 memoryefficientbackup yes InclExcl /opt/tivoli/tsm/client/ba/bin/NETAPP/shifs01b/InclExcl.LIS SchedLogName/opt/tivoli/tsm/client/ba/bin/NETAPP/shifs01b/sched.log SchedLogRetention 7 D SchedMod PROMPTED ErrorLogName /opt/tivoli/tsm/client/ba/bin/NETAPP/shifs01b/error.log ErrorLogRetention 7 Best Regards, William Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: transfer rate terminology
Thanks for your replies. According to IBM, 3592 J1A tape drive has Compressed sustained data rate of 80 MB/s and Maximum interface burst transfer rate of 200 MB/s http://publib.boulder.ibm.com/infocenter/ts3500tl/v1r0/index.jsp?topic=/com.ibm.storage.3584.doc/ipg_3584_a69p0cti20.html When backing up a storage pool (source and destination pools are based on 3592 J1A drives), I noticed that transfer rate between two drives was more than 100MB/s for a long period of time. q proc showed that a big file (more than 200GB) was being transferred. Why the transfer rate exceeded 80MB? Many thanks, Mehdi
Re: transfer rate terminology
On Jul 8, 2010, at 3:10 AM, Mehdi Salehi wrote: Thanks for your replies. According to IBM, 3592 J1A tape drive has Compressed sustained data rate of 80 MB/s and Maximum interface burst transfer rate of 200 MB/s http://publib.boulder.ibm.com/infocenter/ts3500tl/v1r0/index.jsp?topic=/com.ibm.storage.3584.doc/ipg_3584_a69p0cti20.html When backing up a storage pool (source and destination pools are based on 3592 J1A drives), I noticed that transfer rate between two drives was more than 100MB/s for a long period of time. q proc showed that a big file (more than 200GB) was being transferred. Why the transfer rate exceeded 80MB? Because the circumstances allow streaming to occur.
Side Effects of Removing Admins
My current shop has a collective memory of bad things happening when old Admin userids are removed from TSM servers. Memories are a bit vague, and all of us have been doing TSM for a long time in a variety of shops, but the general anxiety is that removing the userids of admins who have moved on might break administrative schedules, copy groups, or some other key feature of TSM. Now, of course, we have auditors breathing down our necks that we need to clean up and secure our servers. I can't say that I blame them, but there is this pesky collective memory to deal with. I looked in both the TSM 5.5 administrative Guide and the Reference but didn't find any warnings about side effects of removing administrators. So, my question to the collective wisdom of the group is, Does anyone else remember bad side effects of removing admins in TSM, and if so, is there a corresponding clear memory of when this was fixed in ADSM/TSM, or is it still an issue? (For my first pass, I have used the CHG_ADMIN column in several tables to find out who last updated several kinds of key system resources. If an admin isn't listed in any of those tables on a server, I've gone ahead and removed him or her.) Thanks, Nick
Re: Side Effects of Removing Admins
The only side effect I have had is when you remove the admin for an AIX node. The AIX node had password issues and would not run the backup consistently. This probably has to do with how we run backups on AIX. We have not seen any problems removing people admins from TSM. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: Thursday, July 08, 2010 7:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Side Effects of Removing Admins My current shop has a collective memory of bad things happening when old Admin userids are removed from TSM servers. Memories are a bit vague, and all of us have been doing TSM for a long time in a variety of shops, but the general anxiety is that removing the userids of admins who have moved on might break administrative schedules, copy groups, or some other key feature of TSM. Now, of course, we have auditors breathing down our necks that we need to clean up and secure our servers. I can't say that I blame them, but there is this pesky collective memory to deal with. I looked in both the TSM 5.5 administrative Guide and the Reference but didn't find any warnings about side effects of removing administrators. So, my question to the collective wisdom of the group is, Does anyone else remember bad side effects of removing admins in TSM, and if so, is there a corresponding clear memory of when this was fixed in ADSM/TSM, or is it still an issue? (For my first pass, I have used the CHG_ADMIN column in several tables to find out who last updated several kinds of key system resources. If an admin isn't listed in any of those tables on a server, I've gone ahead and removed him or her.) Thanks, Nick This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
TSM Version 6.2.1 Deployment Agent
I have noticed that the TSM Version 6.2.1 Server/Admin Center pushes out the client upgrade to Windows 2008 clients, but does not install it. I believe this is a security issue as stated by the DISA STIGS for user security settings. I have noticed that the file is placed in a directory under c:\program files\tivoli\tsm\baclient successfully but doesn't install it. Does anyone have an idea of why it isn't installed. +-- |This was sent by tod.jack...@navy.mil via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Side Effects of Removing Admins
The side effect of removing admins is that any administrative schedule last touched by them will not be run if their account is removed. Run the command q sched type=admin f=d and look at the Last updated by (administrator) field. Make sure that the last admin to touch it is not the ones you are going to remove. You can change that to a different admin by just updating the schedule (making no changes) with another user. For this reason, we make sure that we create/update administrative schedules with a generic administrative account. Oh, you might also want to look at any scripts that run against your server to make sure that the admin accounts you are deleting are not in them. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: Thursday, July 08, 2010 6:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Side Effects of Removing Admins My current shop has a collective memory of bad things happening when old Admin userids are removed from TSM servers. Memories are a bit vague, and all of us have been doing TSM for a long time in a variety of shops, but the general anxiety is that removing the userids of admins who have moved on might break administrative schedules, copy groups, or some other key feature of TSM. Now, of course, we have auditors breathing down our necks that we need to clean up and secure our servers. I can't say that I blame them, but there is this pesky collective memory to deal with. I looked in both the TSM 5.5 administrative Guide and the Reference but didn't find any warnings about side effects of removing administrators. So, my question to the collective wisdom of the group is, Does anyone else remember bad side effects of removing admins in TSM, and if so, is there a corresponding clear memory of when this was fixed in ADSM/TSM, or is it still an issue? (For my first pass, I have used the CHG_ADMIN column in several tables to find out who last updated several kinds of key system resources. If an admin isn't listed in any of those tables on a server, I've gone ahead and removed him or her.) Thanks, Nick The BCI Email Firewall made the following annotations - *Confidentiality Notice: This E-Mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you have received this communication in error, please do not distribute, and delete the original message. Thank you for your compliance. You may contact us at: Blue Cross of Idaho 3000 E. Pine Ave. Meridian, Idaho 83642 1.208.345.4550 -
Re: Side Effects of Removing Admins
I think if you remove the admin that defined an admin schedule, the schedule fails. When the admin schedule runs, note it says the defining admin issues the command: ANR2750I Starting scheduled command DAILYCHECKIN ( run checkin ). (SESSION: 31664) ANR2017I Administrator XX issued command: RUN checkin (SESSION: 31664) Also things like Autovault, other 3rd party tools, and TOR may connect to the TSM server via an admin id. I've got perl scripts that do queries using an admin id. But think if you query the activity log for the last x days for the admin id and don't find it, you're good. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, July 08, 2010 9:48 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Side Effects of Removing Admins The only side effect I have had is when you remove the admin for an AIX node. The AIX node had password issues and would not run the backup consistently. This probably has to do with how we run backups on AIX. We have not seen any problems removing people admins from TSM. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: Thursday, July 08, 2010 7:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Side Effects of Removing Admins My current shop has a collective memory of bad things happening when old Admin userids are removed from TSM servers. Memories are a bit vague, and all of us have been doing TSM for a long time in a variety of shops, but the general anxiety is that removing the userids of admins who have moved on might break administrative schedules, copy groups, or some other key feature of TSM. Now, of course, we have auditors breathing down our necks that we need to clean up and secure our servers. I can't say that I blame them, but there is this pesky collective memory to deal with. I looked in both the TSM 5.5 administrative Guide and the Reference but didn't find any warnings about side effects of removing administrators. So, my question to the collective wisdom of the group is, Does anyone else remember bad side effects of removing admins in TSM, and if so, is there a corresponding clear memory of when this was fixed in ADSM/TSM, or is it still an issue? (For my first pass, I have used the CHG_ADMIN column in several tables to find out who last updated several kinds of key system resources. If an admin isn't listed in any of those tables on a server, I've gone ahead and removed him or her.) Thanks, Nick This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Side Effects of Removing Admins
Good luck with removing the admin id. My main co-admin is no longer employed with us. Thus his admin id touched lots of things. At first, I was not able to delete his id. Every time I tried to delete it, I got some kind of error that it was still in needed/in use (or something like that). From a previous post here (I think it was Richard), I was told that every node he created (that has not been modified by another admin) and I think storage pools, etc, want to keep this connection and wouldn't let me delete the admin id. I did lock the id so it could not be used. Eventually, I was able to delete it, but it took over a year. Not sure if this restriction is still in place, since it was a long time ago. Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html From: Nick Laflamme dplafla...@gmail.com To: ADSM-L@VM.MARIST.EDU Date: 07/08/2010 08:10 AM Subject: [ADSM-L] Side Effects of Removing Admins Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU My current shop has a collective memory of bad things happening when old Admin userids are removed from TSM servers. Memories are a bit vague, and all of us have been doing TSM for a long time in a variety of shops, but the general anxiety is that removing the userids of admins who have moved on might break administrative schedules, copy groups, or some other key feature of TSM. Now, of course, we have auditors breathing down our necks that we need to clean up and secure our servers. I can't say that I blame them, but there is this pesky collective memory to deal with. I looked in both the TSM 5.5 administrative Guide and the Reference but didn't find any warnings about side effects of removing administrators. So, my question to the collective wisdom of the group is, Does anyone else remember bad side effects of removing admins in TSM, and if so, is there a corresponding clear memory of when this was fixed in ADSM/TSM, or is it still an issue? (For my first pass, I have used the CHG_ADMIN column in several tables to find out who last updated several kinds of key system resources. If an admin isn't listed in any of those tables on a server, I've gone ahead and removed him or her.) Thanks, Nick
Re: Side Effects of Removing Admins
An auditor-mollifying measure could be to perform a REName Admin to change it to a 64-character name of relative gibberish, pending full extrication of the old administrator. Richard Simswith my name in everything, for job security
6.2.1.1 Linux client missing gsk rpms
Can someone with IBM can get this to the folks that packaged the latest client patches. I downloaded 6.2.1.1 for Linux, to get the fix for the /etc/issue problem. Sent it to my Linux client that discovered the problem, for verification. I was wondering why 6.2.1.1 was 15mb smaller than 6.2.1.0. Here us what my Linux guy said: 6.2.1.1 is 15mb smaller because it does not contain the gsk*.rpm files, so you have to download and untar 6.2.1.0-TIV-TSMBAC-LinuxX86.tar first, then download and untar 6.2.1.1-TIV-TSMBAC-LinuxX86.tar which overwrites the TIVsm-API.i386.rpm TIVsm-API64.i386.rpm TIVsm-BA.i386.rpm and TIVsm-HSM.i386.rpm files Considering that the gsk* libraries are mandatory, they should be with the package. Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Storage Agents - were are they?
I'm missing simething . . . I'm on a download binge getting the latest v5.5, v6.1 and v6.2 clients. I also went looking for the latest StorageAgent clients (TSM for SAN), I logged onto PassportAdvantage and went hunting for TSM for SAN versions, and found the following: v5.5 for unix and win v6.1 for unix and win I didn't find any v6.2 storageagents on PassportAdvantage, nor do I find any patch/fix levels on the regular support web site for any StorageAgent versions. The regular site has the fix/patch levels for servers and clients, but I don't see any storageagents. Now, I don't need either the v6.1 or v6.2 storageagents, but I'm confused that I can't find them on PA(base lvls) or the normal support site (fix/patch lvls). 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.
Using DB2 lanfree with TSM
Hi, Lanfree Client AIX 6.1.0.0 TSM Server AIX 5.3.0.0 Server, client and Storage Agents TSM v5.4.1.0 Sun StorageTek SL8500 with 22 Sun StorageTek T1 drives Gresham 8.1.1.0 I am trying to backup a huge DB2 database lanfree, but the archive logs should go to the LAN. - What TSM manual should I read for this ? I have found a Redbook from 2001. - We have a lot an experince with file, Oracle and SQL server lanfree, but first time with DB2, is anything different here, parameter setting maybe ? - Google in the issue suggest 2 different server stanza for backups to go lanfree and logs go LAN, but in the Redbook says it is enough to set a archive copygroup with copy destination to disk pool, which is true ? Regards, Tuncel Mutlu Bu e-posta ve muhtemel eklerinde verilen bilgiler kişiye özel ve gizli olup, yalnızca mesajda belirlenen alıcı ile ilgilidir.Size yanlışlıkla ulaşmışsa lütfen göndericiye bilgi veriniz, mesajı siliniz ve içeriğini başka bir kişiye açıklamayınız, herhangi bir ortama kopyalamayınız. Bu mesaj aksi sözleşme ile belirtilmedikçe herhangi bir finansal işlem teklifi, alımı, satımı veya herhangi bir havalenin teyidi gibi bankacılık işlemi yapılması amacını taşımamaktadır.Verilen tüm bilgilerin doğruluğu ve bütünlüğünün garantisi verilmemekte olup, önceden bildirilmeksizin değiştirilebilecektir.Bu mesajın içeriği Bankamızın resmi görüşlerini yansıtmayabileceğinden Akbank T.A.Ş. hiçbir hukuki sorumluluğu kabul etmez.
Re: Side Effects of Removing Admins
Thanks for the responses, people. Fortunately, we've been implementing centralized management slowly, and as a byproduct of that, the administrative schedules have all been updated recently by current staff members. The rest of the issues, like scripts outside of TSM that query TSM, have been anticipated and dealt with. Nick On Jul 8, 2010, at 8:58 AM, Prather, Wanda wrote: I think if you remove the admin that defined an admin schedule, the schedule fails. When the admin schedule runs, note it says the defining admin issues the command: ANR2750I Starting scheduled command DAILYCHECKIN ( run checkin ). (SESSION: 31664) ANR2017I Administrator XX issued command: RUN checkin (SESSION: 31664) Also things like Autovault, other 3rd party tools, and TOR may connect to the TSM server via an admin id. I've got perl scripts that do queries using an admin id. But think if you query the activity log for the last x days for the admin id and don't find it, you're good. W
