Re: : TSM Running out of Scratch Tapes
If your tapes have been marked UNAVAILABLE because they were temporarily unavailable to TSM for whatever reason, but are otherwise undamaged and available, you could use SET VOLUME ... ACCESS=READWRITE to get them back. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Monday, July 08, 2013 2:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] : TSM Running out of Scratch Tapes Dears , We are facing problem as the TSM scratch tapes are running out , also the tapes becoming unavailable . Please advise , how to handle this issue . Thanks , Adeel D I S C L A I M E R The information in this email and in any files transmitted with it, is intended only for the addressee and may contain confidential and/or privileged material. Access to this email by anyone else is unauthorized. If you receive this in error, please contact the sender immediately and delete the material from any computer. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of the company.
Re: Client owner admin password for Exchange TDP
As one data point: we always set TDP client passwords to never expire. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Tuesday, April 30, 2013 8:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Client owner admin password for Exchange TDP Exchange backups for 2010 require TDP 6.4.0.0 and use of dsmcad. What we've seen happen is that the TDP password will expire and reset itself with PASSWORDACCESS GENERATE, but the client owner password doesn't change with PASSWORDACCESS GENERATE, and so the backup fails. Are we doing something wrong, or is everybody else just setting the client owner admin password to never expire? Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
Re: TDP Exchange 2010 scheduled backups fail rc=1819
We saw RC=1819 when the scheduler was started using the local system account, and the local system account did not have access to the Exchange system. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill Boyer Sent: Tuesday, January 15, 2013 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819 Windows 2008 R2 server running Exchange 2010. Installed the agent and my Exchange admin gave me a userid with the permissions. Running the backup while logged in as the user works fine, but when I run it as a scheduled backup I get RC=1819. The TSM Scheduler service is configured to run as the same domain userid I used to successfully backup while logged on. Never seen this one before. Scheduler fails with the same userid that works if I logon locally. My Windows guy is stumped, too. Any ideas? Bill Boyer DSS, Inc. (610) 927-4407 Enjoy life. It has an expiration date. - ??
Re: TDP Exchange 2010 scheduled backups fail rc=1819
I suppose you're not using a client acceptor service that somehow slipped past you? (Grasping at straws) - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill Boyer Sent: Tuesday, January 15, 2013 1:12 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819 The TSM Scheduler service is running under the domain userid in the organization Management group. If I logon as that userid I can run the backups. But running them as a scheduled task fails. That's what's strangesame userid... works logged on...fails as service. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Tuesday, January 15, 2013 11:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819 Also, remember that the account used for the scheduler has to be a member of the Exchange Security Group Organization Management, which in our case is a security group in our root domain. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark, Margaret Sent: Tuesday, January 15, 2013 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819 We saw RC=1819 when the scheduler was started using the local system account, and the local system account did not have access to the Exchange system. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill Boyer Sent: Tuesday, January 15, 2013 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819 Windows 2008 R2 server running Exchange 2010. Installed the agent and my Exchange admin gave me a userid with the permissions. Running the backup while logged in as the user works fine, but when I run it as a scheduled backup I get RC=1819. The TSM Scheduler service is configured to run as the same domain userid I used to successfully backup while logged on. Never seen this one before. Scheduler fails with the same userid that works if I logon locally. My Windows guy is stumped, too. Any ideas? Bill Boyer DSS, Inc. (610) 927-4407 Enjoy life. It has an expiration date. - ??
Re: -snapdiff incremental backups on Windows and include/exclude
We run snapdiff backups using 6.2.4 client, 6.2.3.1 server, Ontap 7.3.3, and exclude and exclude.dir work as expected. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Monday, December 03, 2012 10:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] -snapdiff incremental backups on Windows and include/exclude Do: include exclude exclude.dir Work when you are doing an incremental with -snapdiff ? (Netapp Vfiler, TSM 6.4 client on Win2K8, Ontap 8.1, TSM 6.3.0 server on Win2K8) Thanks! Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
Re: NetApp for Primary Disk Pool
We have been using NetApp storage for TSM primary disk pools for about a year now. The only problem we experienced was when we first configured the storage, and it did not mount automatically after a reboot. (It does now.) It isn't obviously slower than the attached storage, but since we must have the space, I haven't looked too carefully... - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Mayhew, James Sent: Monday, August 27, 2012 1:28 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] NetApp for Primary Disk Pool BUMP... Does anyone have thoughts on this? From: Mayhew, James Sent: Thursday, August 23, 2012 6:42 PM To: 'ADSM-L@vm.marist.edu' Subject: NetApp for Primary Disk Pool Hello All, We are considering using a NetApp V6210 with some attached shelves as a block storage TSM primary disk pool. Do any of you have any experience using NetApp storage as a TSM primary disk pool? If so, how was your experience with this solution? Did you have any performance issues? How was it with sequential workloads? Any insight that you all can provide is greatly appreciated. Best Regards, James Mayhew Storage Engineer HealthPlan Services E-mail: jmay...@healthplan.com _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ CONFIDENTIALITY NOTICE: If you have received this email in error, please immediately notify the sender by e-mail at the address shown.This email transmission may contain confidential information.This information is intended only for the use of the individual(s) or entity to whom it is intended even if addressed incorrectly. Please delete it from your files if you are not the intended recipient. Thank you for your compliance.
Re: Select or Query help
Well, since you asked for any suggestions... It seems to me you could get this report using a command like select archive_date,filespace_name from archives a,file_name from contents c where archive_date = current_timestamp - 1 days and a.node_name = c.node_name and a.filespace_name = c.filespace_name or select backup_date,filespace_name from backups b,file_name from contents c where backup_date = current_timestamp - 1 days and b.node_name = c.node_name and b.filespace_name = c.filespace_name However, I haven't tested these commands, and I'm not about to. On our system, any such command would run forever and probably die before it completed. I have long since given up trying to use select statements using either the contents or backups tables, they are way too big. If this report is not produced regularly, maybe it's because your predecessor gave up too! P.S. HL_NAME and LL_NAME are not what you need... those are the IP address and port number for a client. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Geoff Gill Sent: Thursday, July 12, 2012 9:13 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Select or Query help Good day all, Below is a section of a file I was sent. I'm told the person who did this is long gone and nobody knows what command he used to get it. I was hoping someone might recognize it and help recreate it since I'm not sure we'll even be able to contact that person for help. There are no headers for the columns but they seem obvious. You can see from the output the date, file://server/drive, file\path and filename. The filename and data in the file seems to indicate that this command is run to output one specific dates worth of data of every file a specific node backed up. If anyone has any siggestions I would be eternally grateful because I'm being hammered to get an answer so I can run it and get the data. 2011-10-17 \\bpsnt91\c$ \DOCUMENTS AND NTUSER.DAT 02:36:24.00 SETTINGS\AFSADEV\ 2011-10-17 \\bpsnt91\c$ \DOCUMENTS AND NTUSER.DAT.LOG 02:36:24.00 SETTINGS\AFSADEV\ 2011-10-17 \\bpsnt91\c$ \DOCUMENTS AND NTUSER.INI 02:36:24.00 SETTINGS\AFSADEV\ Thank You Geoff Gill
Re: Select or Query help
Yes, I was. I don't dare to select them from the archives or backups tables to see what they really are, so I should have kept my mouth shut! Sorry about that. Can you supply an example of what is in the HL_NAME and LL_NAME fields? - Margaret -Original Message- From: Richard Sims [mailto:r...@bu.edu] Sent: Thursday, July 12, 2012 11:00 AM To: Clark, Margaret Subject: Re: Select or Query help On Jul 12, 2012, at 1:41 PM, Clark, Margaret wrote: ... P.S. HL_NAME and LL_NAME are not what you need... those are the IP address and port number for a client. Hi, Margaret - You may be thinking of HL_ADDRESS and LL_ADDRESS. Richard
Changed SQL behavior under server 6.2.3.1
Using TSM server 6.2.3.1, the following SQL command no longer works: select node_name from nodes where node_name not in (select node_name from filespaces) It still works correctly if you take out the not. Any ideas? - Margaret
Re: Changed SQL behavior under server 6.2.3.1
The error I get is this: ANR2034E SELECT: No match found using this criteria. Needless to say, I know I have a few nodes registered for which there are no filespaces, and this negative result is wrong. I don't actually care about this particular command, but there's other stuff I'd like to do using the where ... not in (select ...), if I could only get it to work. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Alex Paschal Sent: Thursday, June 21, 2012 11:41 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Changed SQL behavior under server 6.2.3.1 Hi, Margaret. What error are you getting? Taking a stab in the dark, explicitly using NODES and FILESPACES in your predicate can cause unexpected results (http://www-01.ibm.com/support/docview.wss?uid=swg21380830). I would guess failing with the addition of the word NOT could be construed as an unexpected result. You might retry using the AS keyword. This particular problem is listed as fixed in 6.2.4.0. Alex On 6/21/2012 9:55 AM, Clark, Margaret wrote: Using TSM server 6.2.3.1, the following SQL command no longer works: select node_name from nodes where node_name not in (select node_name from filespaces) It still works correctly if you take out the not. Any ideas? - Margaret
Re: Why are my temp files being backed up?
What you show here is not a log of files being backed up, but being expired. If you had just modified the options file to add the exclusion, you'd see a log like this. If that's the case, then check the log again tomorrow. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, April 17, 2012 11:00 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Why are my temp files being backed up? Windows 2003 server - 6.3 client. This machine is very memory constrained. 43M files. Using journaling and MEMORYEFFICIENT DISKCACHEMETHOD. When I use the CLI and do a q inclexcl, I see: snippage Exclude All *\temp\* Server more snippage Exclude All *\...\Temp\...\* Server So I know the cloptset is working. Nothing in the dsm.opt: NODENAME ACIPENSER.VCU.EDU TCPSERVERADDRESS TSMLINUX8.UCC.VCU.EDU PASSWORDACCESS GENERATE SCHEDLOGR 30 D ERRORLOGR 30 D *MEMORYEFFICIENT YES MEMORYEFFICIENT DISKCACHEMETHOD diskcachelocation g:\tsm_cache *SNAPSHOTPROVIDER VSS VERBOSE Yet I see entries like: 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26194-1656.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26195-1656.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26196-4900.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26197-1656.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26198-4900.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26199-4900.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26200-1656.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26201-4900.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26202-1656.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26203-1656.mem [Sent] 04/17/2012 04:20:18 Retry # 1 Expiring--0 \\acipenser\c$\Documents and Settings\wshuart\Local Settings\Temp\list26204-1656.mem [Sent] in the dsmsched.log file? What am I missing? I am also dealing with some kind of memory issue eventhough I am using memoryefficient: 04/15/2012 18:24:54 ANS1030E The operating system refused a TSM request for memory allocation. 04/15/2012 18:24:54 ANS1512E Scheduled event 'RESEARCH-COMPUTING' failed. Return code = 12. 04/16/2012 17:08:01 ANS1814E Unable to start the scheduled event 'ACIPENSER.SQL.DAILY' 04/16/2012 17:08:01 ANS1815E Either the window has elapsed or the schedule has been deleted 04/16/2012 18:29:55 ANS1999E Incremental processing of '\\acipenser\i$' stopped. 04/16/2012 18:29:56 ANS1030E The operating system refused a TSM request for memory allocation. 04/16/2012 18:29:56 ANS1512E Scheduled event 'RESEARCH-COMPUTING' failed. Return code = 12. Any thoughts on this?
Re: TSM 6.2.3 DB2 Deadlock
We had this back in February, when a reorg deadlocked with a migration. Get help right away, and while you're waiting, check APAR: IC81261 - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: Monday, April 16, 2012 8:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 6.2.3 DB2 Deadlock I find my DB2 database in a deadlock condition. It's been deadlocked for about 40 hours. It's run fine for many, many months until this weekend. Running on Windows 2008 R2. During node backup, migration kicked in (as it does frequently). But, apparently, migration is trying to move a file that a node is backing up? Anyone have a suggestion? I've opened a PMR but don't have a response yet. I hesitate to halt/restart the TSM service without some guidance. Harold Vandeventer Systems Programmer State of Kansas - Department of Administration - Office of Information Technology Services harold.vandeven...@da.ks.gov (785) 296-0631
Re: Monitoring/Admin Center on VM Server?
Yes, we are. We use a VM to run the TIP (administration center) and the old Operational Reporting. No problems. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: Friday, April 06, 2012 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Monitoring/Admin Center on VM Server? Is anyone using a VM as the server for TSM Monitoring/Admin Center/Common Reporting roles? We're considering placing a VM at a distant site in a DR type role instead of physical hardware. It would be easy to move a VM image compared to driving out to rack a physical server. Our VMCenter managers will have the fun job to drive and set hardware. Thanks. Harold Vandeventer Systems Programmer State of Kansas - Department of Administration - Office of Information Technology Services harold.vandeven...@da.ks.gov (785) 296-0631
Re: Slow TSM DB Backup Update #3
We have applied a similar fix, and it not only speeds up the database backups, but inventory expiration as well. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lamb, Charles P. Sent: Tuesday, March 20, 2012 7:58 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Slow TSM DB Backup Update #3 Hi... IBM has a fix for slow TSM DB Backups. It is called loopback TCP address problem referenced to PMR #54435,379,000. TSM DB backups will run as fast as before you performed the AIX V6.1.7.x/V7.1.x.x O/S upgrade.
Re: TSM 6.2 server restarts
While we were running 6.2.2.0, we had one unpleasant occasion when the tape drives started dropping offline one by one, and then I was unable to connect to the server to log in. The Linux admins said the error message indicated that the AIX box had run itself out of memory, and recommended that I hunt through the APARs fixed in the latest server releases to see if any memory leaks had been fixed. We had to reboot to get TSM running again. I really couldn't say whether periodic server restarts (as opposed to reboots) would have prevented the incident. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: Thursday, March 15, 2012 12:59 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 6.2 server restarts We have fairly recently started running a TSM 6.2.2.0 server under zSeries Linux. Some of my co-workers have brought up the idea of scheduling periodic restarts of the server code for performance reasons. Are other TSM 6.2 sites seeing any sign of performance problems resulting from long periods of continuous operation? Thomas Denier
Re: Ang: [ADSM-L] TDP 6.3 and Exchange 2010?
A few additional comments (things we found out the hard way): For Data Protection for Exchange to work, the TSM Client Agent must be installed. The *TDP clients need to be set up using USERID=NONE, after which we set the proxy access using server commands like this: register admin ExchangeServerTDP ExchangeServer1 passexp=0 register admin ExchangeServer1 ExchangeServer1 passexp=0 grant authority ExchangeServerTDP class=node authority=owner node=ExchangeServerTDP grant authority ExchangeServer1 class=node authority=owner node=ExchangeServer1 grant proxynode target=ExchangeServerTDP agent=ExchangeServer1 - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [BS] Sent: Monday, March 12, 2012 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010? I've not looked for a Redbook, we fought the initial setup for several days, using PMRs to get through several of the steps. The TSM server is 6.2.3.0, running on Windows 2008 R2. The major points that I recall: Created a new Domain, with only one Mgmt Class, thus the default. In that domain: Created a nodename that is used at the BA-Client. Let's call this ExchangeServer1. Created a second nodename that is used at the TDP-Client. Let's call this ExchangeServerTDP. ExchangeServerTDP displays ExchangeServer1 as a Proxy Authority: Via the AdminCenter GUI, open ExchangeServerTDP, click Proxy Authority, add ExchangeSever1. Both nodes (ExchangeServerTDP and ExchangeServer1) were given client owner authority level in the TSM server Administrators list. Created two schedules: one for C:\EXCFULL.CMD; one for C:\EXCINCR.CMD. Assigned the schedules to ExchangeServerTDP. I didn't do all the TDP install and VSS setup testing; that was done by the Exchange Server admin. I can only work with the TSM Server side details. The TDP install apparently created the excfull.cmd and excincr.cmd files as examples for customization. I recall the Exchange Admin was impressed by the 6.3 TDP GUI and how some initial testing for VSS setup was fairly easy. Our knees were very bloody getting through all of it; and at the moment scheduled backup appears to be successful only if the TDP Scheduler Service has logon as set to a domain account that has Exchange permissions. We've not seen that as a requirement in the setup guide. Recall the phrase: Your mileage may vary! Good luck with it. Harold Vandeventer Systems Programmer State of Kansas - Department of Administration - Office of Information Technology Services harold.vandeven...@da.ks.gov (785) 296-0631 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sheridan, Peter T. Sent: Monday, March 12, 2012 1:27 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010? Do any of you have a runbook or set of procedures to follow to get TSM setup to backup Exchange 2010 ? I have see the manual/power shell script, etc.. but am still struggling with the setup. Thanks in advance for any help, Pete. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Daniel Sparrman Sent: Monday, March 12, 2012 9:39 AM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010? Hi That wont work since you will need domain-level administrator rights to backup Exchange 2010. Either create a new account with domain-level administrator rights and the role Administrator in Exchange, or use your existing Administrator account. Local System doesnt have domain-level administrator rights. Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Vandeventer, Harold [BS] Sänt av: ADSM: Dist Stor Manager Datum: 03/12/2012 15:35 Ärende: [ADSM-L] TDP 6.3 and Exchange 2010? Is anyone using TDP 6.3 to run VSS backup against Exchange 2010 DAG? We're fighting a problem where a scheduled backup is reported as successful from the TSM server perspective, but according to the TDP/Exchange manager the backup never runs. He doesn't see any corresponding backup history in the TDP GUI. Setting the TDP Scheduler service to Log On As a domain account (not Local System) seems to let scheduled backup work, but the TDP/Exchange manager wants to avoid password change polices by using Local System as he has for years with Exchange 2007. We've got a PMR open, with no progress other than try a domain account. Harold Vandeventer
Re: TSM 6.2 SQL statement
This works on 6.2.3.1: select volume_name,stgpool_name,access,pct_utilized,est_capacity_mb, cast(day(current_timestamp-last_write_date) as decimal) as Days, status,access,last_write_date,substr(char(last_write_date),1,19) as Last Write from volumes where status='FILLING' and access!='UNAVAILABLE' and access='OFFSITE' and 60 cast(day(current_timestamp-last_write_date) as decimal) - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Wednesday, March 07, 2012 1:40 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 6.2 SQL statement We run this and other SQL statements that return dates in the form of days. This SQL query works on 5.4, but does not work on 6.2. I am hoping one of the more SQL savvy admins can quickly help me with this so I can fix the rest of the queries we use. The lines that don't work and I do not know how to translate are: (current_timestamp - last_write_date)days as Days and cast((current_timestamp - last_write_date)days as decimal(6,0)) \ 60 \ select volume_name, \ stgpool_name, PCT_UTILIZED, EST_CAPACITY_MB, \ (current_timestamp - last_write_date)days as Days, \ status, access, last_write_date, \ cast ((last_write_date) as date) as Last Write \ from volumes \ where status = 'FILLING' \ and access != 'UNAVAILABLE' and access = 'OFFSITE' \ and cast((current_timestamp - last_write_date)days as decimal(6,0)) \ 60 \ order by last_write_date Thanks, Andy Huebner 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: Slow TSM DB Backup
We upgraded to server 6.2.3.1 in January, and database backup times got a lot worse; half-hour DB backups increased to a minimum of 40 minutes, with one in four taking 3-4 hours or more. When we upgraded, we took the default REORGBEGINTIME 6, REORGDURATION 24. We subsequently reduced the REORGDURATION, and made certain that database backups only take place outside the reorg window. We have completed only five database backups since then; one of the five still took over three hours. I'm still monitoring and hoping for the best. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lamb, Charles P. Sent: Thursday, March 01, 2012 7:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Slow TSM DB Backup Hi. We are experiencing slow TSM DB backup process on both of our TSM systems using AIX V6.1.7.x, TSM V6.2.3.100, Atape v12.4.1.0. The issues began immediately after we upgraded from AIX v5.3.12.3 to AIX v6.1.7.x. We have created a performance PMR#53387,379,000 with TSM support. With 100GB data in a DB2 database, we are seeing 30 to 60sec waits between .1/.2GB database transfers to IBM LTO4 tape drives via TSM q se screen. It is taking a very long time to complete a TSM DB backup. Before the AIX upgrade, the full DB backup took about 10 minutes; now we are seeing backups of hours in length. Anybody having these types of issues??
Re: Slow TSM DB Backup
Should have mentioned: we upgraded to AIX 6.1 TL 7.1 at the same time as the upgrade to TSM server 6.2.3.1. We upgraded to AIX 6.1 TL 7.0 on Jan 12th, and of eleven database backups before adding the 7.1 patches, two were exceptionally long - unprecedentedly long at that time, between 5 and 6 hours. We're up to one long database backup out of the last six now, since resetting REORGDURATION and making sure DB backup is not during the reorg window. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lamb, Charles P. Sent: Thursday, March 01, 2012 7:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Slow TSM DB Backup Hi. We are experiencing slow TSM DB backup process on both of our TSM systems using AIX V6.1.7.x, TSM V6.2.3.100, Atape v12.4.1.0. The issues began immediately after we upgraded from AIX v5.3.12.3 to AIX v6.1.7.x. We have created a performance PMR#53387,379,000 with TSM support. With 100GB data in a DB2 database, we are seeing 30 to 60sec waits between .1/.2GB database transfers to IBM LTO4 tape drives via TSM q se screen. It is taking a very long time to complete a TSM DB backup. Before the AIX upgrade, the full DB backup took about 10 minutes; now we are seeing backups of hours in length. Anybody having these types of issues??
Re: Slow TSM DB Backup
No, we're still using 11.6.0.0. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lamb, Charles P. Sent: Thursday, March 01, 2012 1:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Slow TSM DB Backup Margaret.. Are you using the latest Atape driver which just released on 27 Feb 2012?? Atape V12.4.1.0 It did somewhat help, however, the TSM DB backup takes us 1 1/2 for full, TSM DB snapshot takes us 2 1/2hrs with our 100GB of data in our 340GB DB2 database. They were about 10-15 minutes in length before we performed the AIX migration from V5.3.12.3 to V6.1.7.3. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark, Margaret Sent: Thursday, March 01, 2012 2:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Slow TSM DB Backup Should have mentioned: we upgraded to AIX 6.1 TL 7.1 at the same time as the upgrade to TSM server 6.2.3.1. We upgraded to AIX 6.1 TL 7.0 on Jan 12th, and of eleven database backups before adding the 7.1 patches, two were exceptionally long - unprecedentedly long at that time, between 5 and 6 hours. We're up to one long database backup out of the last six now, since resetting REORGDURATION and making sure DB backup is not during the reorg window. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lamb, Charles P. Sent: Thursday, March 01, 2012 7:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Slow TSM DB Backup Hi. We are experiencing slow TSM DB backup process on both of our TSM systems using AIX V6.1.7.x, TSM V6.2.3.100, Atape v12.4.1.0. The issues began immediately after we upgraded from AIX v5.3.12.3 to AIX v6.1.7.x. We have created a performance PMR#53387,379,000 with TSM support. With 100GB data in a DB2 database, we are seeing 30 to 60sec waits between .1/.2GB database transfers to IBM LTO4 tape drives via TSM q se screen. It is taking a very long time to complete a TSM DB backup. Before the AIX upgrade, the full DB backup took about 10 minutes; now we are seeing backups of hours in length. Anybody having these types of issues??
Re: ADMIN password exp errors during proxy backups
Do the backups actually fail? We used to get messages like this (before upgrading to 6.2.3.1 server) but not on successive nights, and no backups failed. It's a warning, not an error message; when we had them, it looked to me as if the warning was given whenever the password had to be updated. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bos, Karel Sent: Tuesday, February 21, 2012 7:11 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] ADMIN password exp errors during proxy backups Hi, Running for years TSM backup services we got used to do reg node XXX us=none and use password expiration on almost all our backup stuff. Nowadays we get VSS backups so first thing we ran into was the proxy stuff needing administrators to run. OK, no issue just reg the clients without us=none. After a while we run in the newest feature. NODE passwords get reset after expiration completely automatically (like it should) BUT the administrator connected to that node (and used by the VSS backups) DO NOT, resulting in: ANR0470W Session # for administrator USER_ID refused - administrator password has expired. http://www-01.ibm.com/support/docview.wss?uid=swg21460596 Above mention link pretty much tells me we CANT use password expiration anymore on any of the VSS backups or any proxy backup for that matter. Or do I overlook something? Kind regards, Karel Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien de integriteit van het bericht niet veilig gesteld is middels verzending via internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos toegezonden. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Nederland B.V. group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request. Atos Nederland B.V. / Utrecht KvK Utrecht 30132762
Re: TSM 5.5 : NAS share folder backup from TSM client
Check the account that is used to run the client acceptor (or scheduler if the client acceptor service is not used). It that account does not have the appropriate privileges, you will see this behavior. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lakshminarayanan, Rajesh Sent: Wednesday, February 15, 2012 10:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 5.5 : NAS share folder backup from TSM client Hi , I have a situation where my share folder backup through ba-client fails with ANS5174E A required NT privilege is not held error message. Share folder from NAS server is mounted to a windows 2003 Standard Edition(SP2) server. Profile(tsm domain profile) which is used to perform tsm backup is used to mount the share folder to windows server and it has read write privilege to the share folder. I am able to create delete a file from the share folder using the tsm profile. I am surprised why my backup fails with this error message when I have the needful privilege. Even at the NAS end I have full permission on this particular share folder. I raised a support call and they suggest me to look at the permission in the windows server. I have checked it and it look fine. has any one encountered this issue before, do share me how this can be fixed. Or Do I need to follow the NAS backup approach, if so Can I perform the backup through LAN instead of attaching a tape drive to NAS server. below are my environment details Server -- TSM server (5.5.5.0) in AIX (6100-04-01-0944). Client -- TSM ba-client (5.5.2.12) in Windows 2003 Standard edition (SP2) NAS server -- QNAP TS-809U-RP Turbo Regards, Rajesh Lakshminarayanan
Re: Need some support for snapdiff RFE's
It would be helpful if snapdiff backups updated the BACKUP_START field, even if we have to resign ourselves to nothing recorded as BACKUP_END. Is there a reason why that can't be done? - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Pete Tanenhaus Sent: Tuesday, February 14, 2012 10:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Need some support for snapdiff RFE's Actually this really isn't correct, a snapshot differential backup will detect deleted files and will expire them on the TSM server. Periodic full progressive incremental backups are recommended because less complete backups such as snapdiff, incremental by date, and JBB can never be as comprehensive as a full progressive given that a full progressive examines every file on the local file system and every file in the TSM server inventory. Note that less complete implies that changes processed by a full progressive might be missed by other less complete backup methods, and this is the reasoning behind recommending periodic full progressive incrementals. JBB is somewhat better in that in makes every attempt to detect conditions which indicate that the change journal is out of sync with what has previously been backed up and to automatically force the full progressive incremental backup instead of requiring the user to manually schedule it. For reasons that require a very detailed explanation (let me know if you are interested), the current snapdiff implementation doesn't have the robustness or resiliency that JBB does and therefore really requires manually scheduling full progressive incremental backups via the CreateNewBase option. Hope this helps ... Pete Tanenhaus Tivoli Storage Manager Client Development email: tanen...@us.ibm.com tieline: 320.8778, external: 607.754.4213 Those who refuse to challenge authority are condemned to conform to it | | From: | | --| |Paul Zarnowski p...@cornell.edu | --| | | To:| | --| |ADSM-L@vm.marist.edu | --| | | Date: | | --| |02/14/2012 07:12 AM | --| | | Subject: | | --| |Re: Need some support for snapdiff RFE's | --| | | Sent by: | | --| |ADSM: Dist Stor Manager ADSM-L@vm.marist.edu | --| Grant, The time stamps are not updated, because a snapdiff incremental does not deactivate deleted files. You need to do periodic 'createnewbase' to do this, which walks the file system and updates the time stamps. ..Paul On Feb 14, 2012, at 12:32 AM, Grant Street gra...@al.com.au wrote: Hello Just thought I would plug two snapdiff RFE's(Request For Enhancement) that I created on the IBM developer works site. I am trying to garner some support for these in the hope that they will be implemented in the future. I have seen that some of you have had
Re: Need some support for snapdiff RFE's
The reason we use snapdiff is to avoid walking the file system. Running a periodic 'createnewbase' is just not going to happen. We're just stuck with no time stamp. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul Zarnowski Sent: Tuesday, February 14, 2012 4:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Need some support for snapdiff RFE's Grant, The time stamps are not updated, because a snapdiff incremental does not deactivate deleted files. You need to do periodic 'createnewbase' to do this, which walks the file system and updates the time stamps. ..Paul On Feb 14, 2012, at 12:32 AM, Grant Street gra...@al.com.au wrote: Hello Just thought I would plug two snapdiff RFE's(Request For Enhancement) that I created on the IBM developer works site. I am trying to garner some support for these in the hope that they will be implemented in the future. I have seen that some of you have had experience with Netapp snapdiff backups and you may have similar beliefs. Define snapdiff and other snap options on a per filesystem basis rather than per backup command When running an incremental backup be able to define the snapdiff or other snap option on a per filesystem basis rather than for the whole backup incremental job. http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfeCR_ID=1 2858 Snapdiff to update last backup fields in filespace data Could you please update the TSM snapdiff client to update the lastbackup information of filespaces when a query filespace f=d is issued. This would be the obvious behaviour and would be inline with the documented meaning of the columns http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfeCR_ID=1 3145 TIA Grant
Re: Firewall problem
You doubtless checked the DNSLOOKUP option, and set it the same way on all your servers. Is it possible that the DNS for the problem client is also the only DNS that is also behind the firewall? - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Richard Rhodes Sent: Monday, February 06, 2012 3:47 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Firewall problem Hi Everyone, We have six TSM v5.5.5 instances (on AIX) named TSM1 to TSM6. All six instances handle backups for nodes that are behind firewalls, although only five work. The six instances are on separate servers, so each has it's own IP address and firewall rules. The firewall rules are all identical so we can put any node on any TSM server. We cannot get firewall backups to work to our TSM5 instance. Since it was brought up a couple years ago we have fought to get firewall backups to work but have failed. Nodes out behind a firewall are able to contact the TSM server, a sessions is established, then it is immediately disconnected. This repeats over and over as the node retries. You can sometimes see 50 or more sessions - all hung - for a firewalled node. We've done everything we can think of: check/double/triple checked FW rules, talked with IBM support, run traces for them, check AIX setup, checked TSM5 setup, compared anything related to TSM5 to the other working instances. If we move the node to one of our other TSM instances it worked just fine!! In all, we firgured this HAD to be a firewall setup problem of some kind. This past weekend we move TSM5 (and TSM6 also) to new servers/lpars. The new servers had to have new IP addresses and run a newer AIX v6. We've done this upgrade for the other TSM servers already. With new IP addresses we had to create new FW rules. We figured that with a whole new setup FW backups would have to work - we're kicking it real hard NOPE - it didn't help! The only thing that didn't change in this server swing was the actual TSM instance. It seems our FW backup problem on this one instance HAS to be in TSM itself. Question: Is there any setting in TSM that could explain failing backups for firewalled servers? 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: TDP for Databases 6.3 -- Documentation
Hi, Carol. I had hoped to be able to tell you today whether or not our problem of TSM snapshots being left behind had been fixed by the 6.2.4 client. Unfortunately the FAS administrator was out yesterday, so the leftover snapshots were not cleared before last night's backup. He has cleaned up the TSM snapshots this morning, so tomorrow, I will let you know how it went. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Carol Trible Sent: Tuesday, October 25, 2011 2:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Databases 6.3 -- Documentation The TSM V6.3 information center is currently being hosted on a section of ibm.com that is experiencing intermittent outages. The ibm.com support team is investigating. Two other methods for accessing V6.3 documentation are provided below: 1. There is a downloadable version of the information center at ftp://public.dhe.ibm.com/storage/tivoli-storage-management/techprev/infocenter/ . Instructions for downloading it are available at http://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/Downloadable +V6.3+information+center . 2. PDF versions of the books are available at the IBM Publications Center at http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss. Carol Trible IBM Tivoli Storage Manager Development tri...@us.ibm.com
Re: Recovering orphaned tape from Library Server
How about this? DELete VOLHistory TODate=TODAY-8 Type=REMOTE VOLUME=TE0105 FORCE=YES - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger Deschner Sent: Thursday, October 06, 2011 2:37 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Recovering orphaned tape from Library Server I'm not having much luck recovering a tape which seems to be orphaned. It's a library manager setup, with both Library Server and Library Client at TSM 6.2.30. The Library Client had mounted this tape to run a database backup, but the backup failed with a tape I/O error. So it didn't make it into the Library Client's Volume History File. I reran the DB backup, which worked the second time using a different tape. The Library Client knows nothing of the first tape anymore. However, the Library Server still has it listed in its Volume History File as Volume Type REMOTE, with a date more than 8 days ago. Q LIBVOL shows: Library Name: LIBE Volume Name: TE0105 Status: Private Owner: ADSM-4 (That's the name of the Library Client) Last Use: DbBackup Home Element: 1,105 Device Type: LTO Cleanings Left: Media Type: LTO-4 On the Library Server system, I tried UPDATE LIBVOL STATUS=SCRATCH, and DELETE VOLHISTORY TYPE=ALL TODATE=TODAY-8 to no avail. That didn't remove it from the VolHist file. It seems stuck in limbo. This tape has nothing useful on it - an old and incomplete database backup. How can I recover it? I'd hate to hand-edit the VolHist file. Roger Deschner University of Illinois at Chicago rog...@uic.edu ==I have not lost my mind -- it is backed up on tape somewhere.=
Re: BACKUP STGPOOL and collocation
I have observed that for primary storage pools where the tape volumes have been DEFINEd to belong to that pool, MOVE DATA to consolidate tapes belonging to the same collocation group has unexpected results. The database reliably selects the volume copied FROM as the primary candidate for the next tape to be written TO for that collocation group, resulting in a ping-pong effect... This behavior can be subverted by using DELETE VOLUME after MOVE DATA, and assigning the volume to another pool. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas Denier Sent: Wednesday, August 03, 2011 9:03 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] BACKUP STGPOOL and collocation We have a new TSM 6.2.2.0 server running under mainframe Linux. It has a primary storage pool on file devices and a copy pool on TS1120 tape. The tape library is located in a different building than the server and its clients, so we do not eject and vault copy pool volumes. We normally run storage pool backups with 'maxproc=4', but occasionally use 'maxproc=5'. Backup storage pool operations do not seem to be following the documented rules for collocation. The server currently has 7 collocation groups. Yesterday morning, the copy pool had 25 volumes in filling status, with one collocation group having 5 volumes in filling status. I executed 'move data' commands to consolidate some of the volumes. After the storage pool backups this morning I found 6 new filling volumes, all for collocation groups that already had filling volumes with free space. I have verified that the copy pool specifies collocation by group, that every node is assigned to a collocation group, and that every filling volume has read/write access. Am I misreading the documentation regarding volume usage in collocated storage pools?
Re: snapdiff advice
Back in March, I watched a recorded presentation about DB2 reorgs within TSM server 6.2.2.0, and discovered that OnTap will only allow snapdiff backups to work correctly with releases 7.3.3 and 8.1, NOT 8.0. Apparently OnTap 7.3.3 and 8.1 contain the File Access Protocol (FAP), but 8.0 does not, so snapdiff would fail. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David Bronder Sent: Monday, June 27, 2011 1:24 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] snapdiff advice Hi folks. I'm trying to get snapdiff backups of our NetApp (OnTAP version 8.0.1P5) working so I can move away from everybody's favorite NDMP backups... So far, I'm not having much luck. I don't know whether I'm just Doing It Wrong (tm) or if something else is going on. In particular, on both Windows 2008 R2 (6.2.3.0) and RHEL 5.6 (6.2.2.0), I'm getting failures like the following, depending on the dsmc invocation: ANS1670E The file specification is not valid. Specify a valid Network Appliance or N-Series NFS (AIX, Linux) or CIFS (Windows) volume. ANS2831E Incremental by snapshot difference cannot be performed on 'volume-name' as it is not a NetApp NFS or CIFS volume. (These are shares at the root of full volumes, not Q-trees. I'm using a CIFS share for the Windows client, and an NFS share for the Linux client, with the correct respective permission/security styles. TSM server is still 5.5, but my understanding is that that should be OK.) For those of you who have snapdiff working, could you share any examples of how you're actually doing it? E.g., your dsmc invocation, how you're mounting the share (must a Windows share be mapped to a drive letter?), or anything relevant in the dsm.opt or dsm.sys (other than the requisite testflags if using an older OnTAP). Or anything else you think is useful that the documentation left out. (Also of interest would be how you're scheduling your snapdiff backups, and how you have that coexisting with local filesystems on the client running the snapdiff backups.) Thanks, =Dave -- Hello World.David Bronder - Systems Admin Segmentation Fault ITS-EI, Univ. of Iowa Core dumped, disk trashed, quota filled, soda warm. david-bron...@uiowa.edu
Re: Expiration causes backups to hang
We had a somewhat similar problem almost a year ago, which was caused by Windows 2008 TSM clients older than the 6.2 release: IC66810: 6.1.2 AND 6.1.3 TSM WINDOWS CLIENTS WITH DEFAULT SYSTEM STATE WRITERS ON WIN 7 AND 2008 R2 MAY GET FULL SYSTEM STATE BACKUPS The problem went away when the clients were upgraded to 6.2.1.0 (now I'd use 6.2.2.0). - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hans Christian Riksheim Sent: Wednesday, April 13, 2011 1:18 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Expiration causes backups to hang Hi, anyone else have this problem? Running 6.2.2 on AIX 6.1. Submitting a PMR on this in parallell. When I say hang I mean a complete hang. All incoming backups stops. Traffic is resumed when we cancel expiration. Hans Chr.
Re: Scripts Doubling up
I made a mistake. I imagined the processes columns in the output from select * from syscat.columns would sort into tables by default; they didn't. When I tried select * from processes using Servergraph, I didn't notice that the titles stretched way off my screen. I think I'll just go back to lurking... - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Howard Coles Sent: Thursday, March 17, 2011 8:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Scripts Doubling up I'm not sure how you're pulling that syscat columns information. However, Here's a sample from the select statement that David offered: PROCESS_NUM: 1810 PROCESS: Migration START_TIME: 2011-03-17 10:09:45.00 FILES_PROCESSED: 40 BYTES_PROCESSED: 33943646208 STATUS: Disk Storage Pool ORADSKPOOL, Moved Files: 43, Moved Bytes: 33,945,214,976, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 27,689,148,416 Current output volume(s): B00404L4. See Ya' Howard Coles Jr., RHCE, CNE, CDE John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark, Margaret Sent: Wednesday, March 16, 2011 6:03 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Scripts Doubling up Not on our 6.2.2.0 server, it doesn't! - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David E Ehresman Sent: Wednesday, March 16, 2011 12:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Scripts Doubling up But at v6.2.2.0, a select * from processes does show a STATUS field. David Clark, Margaret mcl...@sddpc.org 3/16/2011 2:52 PM Syscat columns doesn't show a STATUS in the PROCESSES table any more. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Howard Coles Sent: Tuesday, March 15, 2011 6:51 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Scripts Doubling up Ladies and Gents, got another weird issue. TSM 6.2.2.1 Running the following script works when I preview it in the ISC: select process_num from processes where process='Backup Storage Pool' and status LIKE '%Pool AIXDSKPOOL%' if (rc_ok) goto reschedule backup stg aixpripool aixcppool maxproc=2 wait=no update sched daily_aix_proc type=admin cmd='RUN DAILY03_AIX_MIGSTG' starttime=now+00:30 active=yes exit reschedule: update schedule daily_aix_proc type=admin starttime=now+00:05 active=yes exit However, when it runs on its own apparently the select and if statement are no longer working. I have found the backup process running on the primary tape pool at the same time the diskpool backup is running. I haven't had time to redo all the scripts, but this should still function from all the tests I ran. My question is, what is wrong with the above script that it wouldn't work, at least for now, as written? Oh, here's the part of the previous script that kicks off the disk pool backup: backup stg aixdskpool aixcppool maxproc=2 wait=no update sched daily_aix_proc type=admin cmd='RUN DAILY02_AIX_BAKPRI' starttime=now+00:30 active=yes This process has worked very well, as we have 5 storage pools, that vary in length for each of the processes that run against them, (backup disk, backup primary tape, reclaim offsite, reclaim onsite, etc). See Ya' Howard Coles Jr. John 3:16!
Re: Scripts Doubling up
Syscat columns doesn't show a STATUS in the PROCESSES table any more. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Howard Coles Sent: Tuesday, March 15, 2011 6:51 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Scripts Doubling up Ladies and Gents, got another weird issue. TSM 6.2.2.1 Running the following script works when I preview it in the ISC: select process_num from processes where process='Backup Storage Pool' and status LIKE '%Pool AIXDSKPOOL%' if (rc_ok) goto reschedule backup stg aixpripool aixcppool maxproc=2 wait=no update sched daily_aix_proc type=admin cmd='RUN DAILY03_AIX_MIGSTG' starttime=now+00:30 active=yes exit reschedule: update schedule daily_aix_proc type=admin starttime=now+00:05 active=yes exit However, when it runs on its own apparently the select and if statement are no longer working. I have found the backup process running on the primary tape pool at the same time the diskpool backup is running. I haven't had time to redo all the scripts, but this should still function from all the tests I ran. My question is, what is wrong with the above script that it wouldn't work, at least for now, as written? Oh, here's the part of the previous script that kicks off the disk pool backup: backup stg aixdskpool aixcppool maxproc=2 wait=no update sched daily_aix_proc type=admin cmd='RUN DAILY02_AIX_BAKPRI' starttime=now+00:30 active=yes This process has worked very well, as we have 5 storage pools, that vary in length for each of the processes that run against them, (backup disk, backup primary tape, reclaim offsite, reclaim onsite, etc). See Ya' Howard Coles Jr. John 3:16!
Re: Scripts Doubling up
Not on our 6.2.2.0 server, it doesn't! - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David E Ehresman Sent: Wednesday, March 16, 2011 12:04 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Scripts Doubling up But at v6.2.2.0, a select * from processes does show a STATUS field. David Clark, Margaret mcl...@sddpc.org 3/16/2011 2:52 PM Syscat columns doesn't show a STATUS in the PROCESSES table any more. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Howard Coles Sent: Tuesday, March 15, 2011 6:51 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Scripts Doubling up Ladies and Gents, got another weird issue. TSM 6.2.2.1 Running the following script works when I preview it in the ISC: select process_num from processes where process='Backup Storage Pool' and status LIKE '%Pool AIXDSKPOOL%' if (rc_ok) goto reschedule backup stg aixpripool aixcppool maxproc=2 wait=no update sched daily_aix_proc type=admin cmd='RUN DAILY03_AIX_MIGSTG' starttime=now+00:30 active=yes exit reschedule: update schedule daily_aix_proc type=admin starttime=now+00:05 active=yes exit However, when it runs on its own apparently the select and if statement are no longer working. I have found the backup process running on the primary tape pool at the same time the diskpool backup is running. I haven't had time to redo all the scripts, but this should still function from all the tests I ran. My question is, what is wrong with the above script that it wouldn't work, at least for now, as written? Oh, here's the part of the previous script that kicks off the disk pool backup: backup stg aixdskpool aixcppool maxproc=2 wait=no update sched daily_aix_proc type=admin cmd='RUN DAILY02_AIX_BAKPRI' starttime=now+00:30 active=yes This process has worked very well, as we have 5 storage pools, that vary in length for each of the processes that run against them, (backup disk, backup primary tape, reclaim offsite, reclaim onsite, etc). See Ya' Howard Coles Jr. John 3:16!
Re: Windows 2000 client
We have been on TSM server 6.n since August 21st 2009, currently at 6.2.2.0. Our oldest clients are at 5.1.5.0; we have several clients at 5.3.2.0 and 5.3.4.0. None of them has had a problem. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ochs, Duane Sent: Friday, January 14, 2011 12:37 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows 2000 client Good day everyone, My TSM servers are currently at 5.5.4 and I'd like to get migrated to 6.2 this year. I have some W2K clients that cannot be retired at this time and I found that 5.5 clients are the oldest supported by 6.2 Is anyone out there using the TSM 5.3 client on W2k and any version of TSM server 6.* Any helpful ideas would be appreciated. Thanks, Duane Follow Quad/Graphics in social mediahttp://www.qg.com/socialmedia http://facebook.com/quadgraphics http://www.youtube.com/user/QuadGraphicsVideos http://linkedin.com/companies/8199
Snapdiff with 6.2.2.0 client
When we started using snapdiff backups, the documentation said it was compatible with any release of OnTap above 7.2. We committed to using snapdiff with our OnTap 7.3.3 FAS, and by using the arcane options TESTFLAG SNAPDIFFONTAPFAP and TESTFLAG SNAPDIFFNAMEFILTEROFF, it mostly worked. We settled down to cope with dsmcsvc crashes about once a week, after Tivoli support told us (post-hoc, mind you) that our configuration would not be supported until the release of the 6.2.2.0 client. That glorious day has come, and yesterday I took out the testflags and ran tests with the new client. It seems to have worked, although each volume has produced this warning: ANS4089W File server fas13 has been upgraded to Data ONTAP version '7.3.3'. Perform a full incremental backup by specifying option createnewbase=migrate as soon as possible. I hope I can safely ignore this warning, since we haven't in fact upgraded, but I did experiment with the CREATENEWBASE option. I tried CREATENEWBASE MIGRATE (the usual syntax) and CREATENEWBASE=MIGRATE (you never know), and CREATENEWBASE YES after a finding a single hit using a Famous Search Engine (the hit was for AIX; we are using Windows). No matter what, the Client Acceptor would not run. Does anyone have information to share? - Margaret Clark San Diego Data Processing Corporation
Re: Snapdiff with 6.2.2.0 client
Thanks for trying, but I found that too (and tried it, and couldn't make it work). I was hoping someone from the beta-test group would have unpublished information. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Cameron Hanover Sent: Tuesday, December 14, 2010 10:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Snapdiff with 6.2.2.0 client According to http://www-01.ibm.com/support/docview.wss?uid=swg21417529 During snapshot difference incremental backup of N-Series or NetApp volumes, if files are skipped due to any reason, such as Tivoli Storage Manager server media mount being unavailable, these files might not be backed up during subsequent backups either, unless the files have been modified. Such files will be logged to the TSM error log. You can back them up manually or perform a snapshot difference backup with the option createnewbase set to yes. - Cameron Hanover chano...@umich.edu Necessity is the plea for every infringement of human freedom. It is the argument of tyrants; it is the creed of slaves. --William Pitt, House of Commons, 11/18/1783 On Dec 14, 2010, at 10:40 AM, Clark, Margaret wrote: When we started using snapdiff backups, the documentation said it was compatible with any release of OnTap above 7.2. We committed to using snapdiff with our OnTap 7.3.3 FAS, and by using the arcane options TESTFLAG SNAPDIFFONTAPFAP and TESTFLAG SNAPDIFFNAMEFILTEROFF, it mostly worked. We settled down to cope with dsmcsvc crashes about once a week, after Tivoli support told us (post-hoc, mind you) that our configuration would not be supported until the release of the 6.2.2.0 client. That glorious day has come, and yesterday I took out the testflags and ran tests with the new client. It seems to have worked, although each volume has produced this warning: ANS4089W File server fas13 has been upgraded to Data ONTAP version '7.3.3'. Perform a full incremental backup by specifying option createnewbase=migrate as soon as possible. I hope I can safely ignore this warning, since we haven't in fact upgraded, but I did experiment with the CREATENEWBASE option. I tried CREATENEWBASE MIGRATE (the usual syntax) and CREATENEWBASE=MIGRATE (you never know), and CREATENEWBASE YES after a finding a single hit using a Famous Search Engine (the hit was for AIX; we are using Windows). No matter what, the Client Acceptor would not run. Does anyone have information to share? - Margaret Clark San Diego Data Processing Corporation
Re: Snapdiff with 6.2.2.0 client
Thank you, Frank and Andy! ADSM-L scores again! - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Andrew Raibeck Sent: Tuesday, December 14, 2010 1:01 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Snapdiff with 6.2.2.0 client Just to supplement Frank's response, you can also use TSM itself to get help on messages, commands and options: Information about the new ANS4089W message can be found by running: dsmc help ans4089w Information about the new CREATENEWBASE option can be found by running: dsmc help createnewbase Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2010-12-14 15:05:38: From: Frank Ramke/Knoxville/i...@ibmus To: ADSM-L@vm.marist.edu Date: 2010-12-14 15:07 Subject: Re: Snapdiff with 6.2.2.0 client Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Hello Margaret, I am not sure why search engines have not found it yet, perhaps because they are pdf files. Look in the section called New for Version 6.2.2 in the following: Windows PDF: http://www-01.ibm.com/support/docview.wss?uid=swg27019824 UNIX PDF: http://www-01.ibm.com/support/docview.wss?uid=swg27019825 The reason the cad is failing is that the CREATENEWBASE option is not valid in dsm.opt or dsm.sys files. You can add it as a command line only option, or in you case, as an option to the scheduler. We did that by design, it would not be good to accidentally leave that option set to yes in you option file. It would cause snapdiff to continually create a new base, defeating the purpose of this type of backup. Anyway, let me know if you have trouble getting to the doc. I will be glad to answer any questions you may still have with the option usage. Frank Ramke TSM Development From: Clark, Margaret mcl...@sddpc.org To: ADSM-L@vm.marist.edu Date: 12/14/2010 10:39 AM Subject:Snapdiff with 6.2.2.0 client Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu When we started using snapdiff backups, the documentation said it was compatible with any release of OnTap above 7.2. We committed to using snapdiff with our OnTap 7.3.3 FAS, and by using the arcane options TESTFLAG SNAPDIFFONTAPFAP and TESTFLAG SNAPDIFFNAMEFILTEROFF, it mostly worked. We settled down to cope with dsmcsvc crashes about once a week, after Tivoli support told us (post-hoc, mind you) that our configuration would not be supported until the release of the 6.2.2.0 client. That glorious day has come, and yesterday I took out the testflags and ran tests with the new client. It seems to have worked, although each volume has produced this warning: ANS4089W File server fas13 has been upgraded to Data ONTAP version '7.3.3'. Perform a full incremental backup by specifying option createnewbase=migrate as soon as possible. I hope I can safely ignore this warning, since we haven't in fact upgraded, but I did experiment with the CREATENEWBASE option. I tried CREATENEWBASE MIGRATE (the usual syntax) and CREATENEWBASE=MIGRATE (you never know), and CREATENEWBASE YES after a finding a single hit using a Famous Search Engine (the hit was for AIX; we are using Windows). No matter what, the Client Acceptor would not run. Does anyone have information to share? - Margaret Clark San Diego Data Processing Corporation
Re: MSG ANR4724E
No idea about ANR4724E, but has the client's network connection been set to auto-negotiate? That would account for the extended execution time. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Andrelli Sent: Thursday, September 23, 2010 9:34 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] MSG ANR4724E I have an issue while backing up a Windows client. I occasionally (about once every 3 weeks) receive the following message: ANR4724E During the backup of node JDCDCA (10) filespace JDCDCA\SystemState\NULL\System State\SystemState (1) a deletion activity occurred. (SESSION: 66148) We have two glaring configuration issues that we are working to correct, but I wanted to see if anyone else had noticed something along these lines. Our problems are: 1. Some recent network reconfiguration caused the backups on this client to extend from less than 10 minutes to almost 4 hours (since backups run through the midnight hours, they still completed within the allotted window and no one paid attention to the extended duration). This happened once before recently, but has been resolved (and we never received ANR4724E on that system). With a 4-hour backup window, it is entirely conceivable that something has been deleted during that timespan, BUT? However, we have 2 other Windows clients also caught up in the re-configuration issue that run about the same 4-hour duration and have never generated error message ANR4724E. 2. The system times on the server and client differ by 10 minutes 32 seconds. I don?t have access authority that would let me check the time discrepancies between the server and the other clients. As an old mainframe sysprog, 10 SECONDS difference between machines could be disastrous, never mind 10 MINUTES. Am I over-reacting to this discrepancy? Is it really a conceivable trouble point, or can TSM handle it? Since the problem is only sporadic, resolving both of these configuration issues is no proof that either was the cause of the problem. Even without fixing them, we could go for another 3-4 weeks without seeing a problem. But I?d appreciate finding out if anyone else has hit this type of situation before.
Re: long time for client backup
I bet you've got a lot of little files on at least one of the drives. The three hours is used comparing all those little darlings with the TSM server's idea of things, before anything gets backed up at all. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Tim Brown Sent: Thursday, September 09, 2010 11:41 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] long time for client backup Client backup starts 8:30PM, It takes 3 hours to get to first processed message ANS1898I * Processed 500 files * I restarted the server, no difference, It happens to be a Windows 2003 cluster. Any idea why it takes so long. 09/08/2010 20:33:09 --- SCHEDULEREC OBJECT BEGIN NT_WKD_OFFCL 09/08/2010 20:30:00 09/08/2010 20:33:11 Incremental backup of volume '\\office\d$' 09/08/2010 20:33:11 Incremental backup of volume '\\office\q$' 09/08/2010 20:33:11 Incremental backup of volume '\\office\e$' 09/09/2010 00:32:24 ANS1898I * Processed 500 files * 09/09/2010 00:32:25 ANS1898I * Processed 1,000 files * Tim Brown Systems Specialist - Project Leader Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: tbr...@cenhud.com mailto:tbr...@cenhud.com Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255
Re: Expiration question
A bit late, but I don't recall any previous responses to this... It will do no good to cancel a running expiration process. When you start again, expiration picks up exactly where it left off. Trying to cancel it just prolongs the agony. No idea about the retries, sorry. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, August 23, 2010 7:32 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Expiration question I have 2-issues with expiration processing. First, on my 5.5.4.2 server - we stopped expiration for more than a week, to perform recovery of a large SAN failure. Now, expiration has been running since 08/17 and still running. Expired over 24M objects out of 29M examined. Didn't know if I should be concerned. It seems to be working OK and the numbers keep changing so it isn't stuck. Didn't know if I should fully cancel it (vs cancel expiration) and restart or just leave it along. Never had an expire run so long! Second, I am mildly concerned about the expiration processing/messages from my 6.1.3.4 server: 355 Expiration Processed 69 nodes, examined 734917 objects, deleting 733029 backup objects, 0 archive objects, 0 DB backup volumes, 0 recovery plan files; 1087 objects have been retried and 801 errors encountered. Why the errors and so many? I don't recall any errors from expiration from any of the 5.5.x servers? What about the retried? Retried what? Speaking of 6.1, anyone have any issues upgrading 6.1.3.x to 6.1.4.1? I realize there are some big changes in 6.1.4.x and am concerned about effecting my only 6.1 production server but I am seeing a lot of problems purportedly fixed in 6.1.4.1. I was never able to upgrade a test 6.1.x server to 6.2.x. Things got so farged up I had to have it wiped and rebuilt (couldn't upgrade to 6.2 and couldn't remove it successfully). 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
Re: unable to view/delete tsm 5.5 custom maintenance scripts using 6.2 admin center
It's not very clear, is it? You need Administrative Schedules on the Server Properties page. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Timothy Hughes Sent: Wednesday, June 02, 2010 8:38 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] unable to view/delete tsm 5.5 custom maintenance scripts using 6.2 admin center Hi all, I would like to create New maintenance scripts using the 6.2 Admin Center but first I need to view/delete the old Scripts that were created using the TSM 5.5 GUI. Is there a way to delete the old scripts when I try to view the script I get the following There is no maintenance script on the server. Thanks
Re: tsm reporter error, can not get report information
I have seen this in the past, when the server was very busy and did not respond to Operational Reporting queries in a timely fashion. The Operational Report would run successfully if submitted manually a little later. - Margaret Clark Systems Programmer San Diego Data Processing Corporation -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of William ZHANG Sent: Monday, May 24, 2010 6:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] tsm reporter error, can not get report information Hi All, Today morning my tsm daily report doesn't work, it report: Error - Server information But hourly report can work in TSM reporter. Nothing else, would you please give a clue to let me find the reason. Regards, william
Re: Associating a node for backup using the Admin Center 6.2 version
Policy domains view policy domains modify policy domain client node schedules modify schedule client nodes associate client node - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Timothy Hughes Sent: Wednesday, May 19, 2010 11:01 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Associating a node for backup using the Admin Center 6.2 version Hello All, Anyone know where I can find out how to Associate a node to a backup schedule using the Admin 6.2 Center? The TSM Admin Center Quick paths seems to show me everything but that task. Unless I am just overlooking it. Thanks in Advance!
Re: Windows 2000 client
5.4.0.2 was the last release that could be installed on Windows 2000. It works. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ADSM-L Sent: Tuesday, May 18, 2010 6:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows 2000 client Off the top of my head, I think 5.3.7.4 was a more recent Windows 2000- safe version that I used to deploy back in the day, but there may have been one or two further Win2K-able releases after that. //David Mc On 18 May 2010, at 14:21, Lee, Gary D. g...@bsu.edu wrote: I know this is old, but we have a situation. Tried to instal the latest tsm windows 2000 client I had downloaded. Gave us an error claiming it wasn't the correct client for that op sys. This was a security fix issued by ibm its name was tsm536c_2_x32.exe. On the off chance that it was a corrupt download, went to try and find it again, haven't been able to come up with it. So, what is the latest client fix for win 2000; and where do I find it? Thanks all. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Changing attributes
Thomas Denier wrote: We have always been able to clean this up by removing and recreating the service. We did not need to deinstall the client software or manually remove registry keys. That's fine as long as the client releases are relatively recent. Somewhere in the client history, TSM changed how it uses the registry, and you can get some very mysterious failures. Mysterious failures also happen when a Windows client is upgraded without first removing the services. The services registry key has to be manually corrected before the multiple schedulers may be active warnings will stop. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Thomas Denier Sent: Tuesday, March 16, 2010 1:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Changing attributes -Margaret Clark wrote: - Fixing the dsm.opt may not be enough. When Windows nodes are cloned with the TSM client in place, the registry will cause this interesting behavior even after the dsm.opt is updated. I've found I have to deinstall the TSM client and then delete the ADSM subkey HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM (from both controlset instances) before reinstalling. Windows adminsitrators at our site occasionally rename existing Windows systems. We almost never specify node names in dsm.opt files for Windows client; we let the client use the machine name as the node name. When a Windows client is renamed the client scheduler service continues to use the old node name, presumably because the node name was recorded in the registry when the service was created. We have always been able to clean this up by removing and recreating the service. We did not need to deinstall the client software or manually remove registry keys.
Re: AIX TSM Client 6.1.3.2 install failure
Did that package ever get refreshed? The FTP site shows nothing later than 8th March. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Andrew Raibeck Sent: Wednesday, March 10, 2010 5:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] AIX TSM Client 6.1.3.2 install failure We are working on a refresh of the package. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/i...@ibmus Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2010-03-10 18:33:58: [image removed] Re: AIX TSM Client 6.1.3.2 install failure Grigori Solonovitch to: ADSM-L 2010-03-10 18:39 Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Please respond to ADSM: Dist Stor Manager Which expansion media? AIX? Which version? gskta package is a smal package, expansion media is huge. Maybe it will be much better for IBM to fix TSM 6.1.3.2 package? Who can send this package to me by mail? From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Xav Paice [xpa...@oss.co.nz] Sent: Thursday, March 11, 2010 12:01 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] AIX TSM Client 6.1.3.2 install failure Both are on the expansion media, which you should be able to download from your Passport Advantage account. Nope, it's not in the download package (gsksa is, but gskta is not). Please consider the environment before printing this Email. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME.
Re: Changing attributes
Fixing the dsm.opt may not be enough. When Windows nodes are cloned with the TSM client in place, the registry will cause this interesting behavior even after the dsm.opt is updated. I've found I have to deinstall the TSM client and then delete the ADSM subkey HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM (from both controlset instances) before reinstalling. - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Schneider, Jim Sent: Tuesday, March 09, 2010 12:13 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Changing attributes In my environment we get that when server OLORIN was cloned from an image of NIROLO. Both servers have the same nodename value their dsm.sys (Unix) or dsm.opt (Windows) file. The name change occurs when the scheduling daemon or process checks with the TSM server. Fix the dsm.opt/dsm.sys file or stop the scheduling service on the server that is not supposed to be backed up. HTH, Jim Schneider -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Fred Johanson Sent: Tuesday, March 09, 2010 2:02 PM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] Changing attributes I've got a client that generates this 5-6 times a night: 03/09/10 03:29:03 ANR1639I Attributes changed for node NIROLO: TCP Name from OLORIN to NIROLO, TCP Address from 128.135.19.3 to 128.135.19.5, GUID from fd.5f.d0.81.cd.7b.11.de.a8.c7.00- .25.64.90.25.15 to 9a.9c.1b.81.31.8b.11.dd.a6.6f.00.19.b- 9.46.ae.e1. (SESSION: 103251) It goes back and forth, causing great confusion to TSM. I've asked the owner what he's doing and he asks me the same. Anyone with an explanation?
Re: Problems with new install of V6.1.0.2 client on Windows 2008 x64 system
I almost added that one in my previous post, but since you said it was a new install, I figured that couldn't be it! Glad you got it solved! - Margaret -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, October 27, 2009 6:14 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008 x64 system Actually, we figured it out and it had nothing to do with Java. It seems the new V6/all Java clients are very fragile when it comes to errors in the DSM.OPT file. When I had the user run the CLI, from the menu, it would flash and quit immediately. As soon as we ran DSMC manually, we saw the error (QUIET was spelled QUITE). Correcting this fixed everything. I don't ever recall seeing this kind of failure in any of the preceding client versions. From: Clark, Margaret mcl...@sddpc.org To: ADSM-L@VM.MARIST.EDU Date: 10/26/2009 05:00 PM Subject: Re: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008 x64 system Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU I've seen the same thing, when the client had an old version of Java loaded. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, October 26, 2009 6:30 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008 x64 system Subject says almost all of it. The only additional info I can add is the error he is seeing in the DSMJ error log: 10/26/2009 07:06:30: ANS1971E The remote client agent (dsmagent) could not be started.Error executing dsmagent ! java.lang.NullPointerException 10/26/2009 07:31:59: ANS1971E The remote client agent (dsmagent) could not be started.Error executing dsmagent ! java.lang.NullPointerException 10/26/2009 08:39:49: ANS1971E The remote client agent (dsmagent) could not be started. The only hit I see that is even close is: http://www-01.ibm.com/support/docview.wss?rs=663context=SSGSG7dc=DB550uid=swg1IC61768loc=en_UScs=UTF-8lang=enrss=ct663other which does talk about a v6.1.1.1 (still looking for it), eventhough this is a NEW install, not an upgrade? Your thoughts?
Re: Problems with new install of V6.1.0.2 client on Windows 2008 x64 system
Oh, and BTW... My favorite is that clients upgraded to 6.1.0.0 will fail because their previously-perfect option files contain references to SYSTEMSTATE. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Tuesday, October 27, 2009 6:14 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008 x64 system Actually, we figured it out and it had nothing to do with Java. It seems the new V6/all Java clients are very fragile when it comes to errors in the DSM.OPT file. When I had the user run the CLI, from the menu, it would flash and quit immediately. As soon as we ran DSMC manually, we saw the error (QUIET was spelled QUITE). Correcting this fixed everything. I don't ever recall seeing this kind of failure in any of the preceding client versions. From: Clark, Margaret mcl...@sddpc.org To: ADSM-L@VM.MARIST.EDU Date: 10/26/2009 05:00 PM Subject: Re: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008 x64 system Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU I've seen the same thing, when the client had an old version of Java loaded. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, October 26, 2009 6:30 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008 x64 system Subject says almost all of it. The only additional info I can add is the error he is seeing in the DSMJ error log: 10/26/2009 07:06:30: ANS1971E The remote client agent (dsmagent) could not be started.Error executing dsmagent ! java.lang.NullPointerException 10/26/2009 07:31:59: ANS1971E The remote client agent (dsmagent) could not be started.Error executing dsmagent ! java.lang.NullPointerException 10/26/2009 08:39:49: ANS1971E The remote client agent (dsmagent) could not be started. The only hit I see that is even close is: http://www-01.ibm.com/support/docview.wss?rs=663context=SSGSG7dc=DB550uid=swg1IC61768loc=en_UScs=UTF-8lang=enrss=ct663other which does talk about a v6.1.1.1 (still looking for it), eventhough this is a NEW install, not an upgrade? Your thoughts?
Re: Problems with new install of V6.1.0.2 client on Windows 2008 x64 system
I've seen the same thing, when the client had an old version of Java loaded. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Monday, October 26, 2009 6:30 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008 x64 system Subject says almost all of it. The only additional info I can add is the error he is seeing in the DSMJ error log: 10/26/2009 07:06:30: ANS1971E The remote client agent (dsmagent) could not be started.Error executing dsmagent ! java.lang.NullPointerException 10/26/2009 07:31:59: ANS1971E The remote client agent (dsmagent) could not be started.Error executing dsmagent ! java.lang.NullPointerException 10/26/2009 08:39:49: ANS1971E The remote client agent (dsmagent) could not be started. The only hit I see that is even close is: http://www-01.ibm.com/support/docview.wss?rs=663context=SSGSG7dc=DB550uid=swg1IC61768loc=en_UScs=UTF-8lang=enrss=ct663other which does talk about a v6.1.1.1 (still looking for it), eventhough this is a NEW install, not an upgrade? Your thoughts?
Re: Date, time and number format
So do tell, Richard: what do we do to change the date and time format now? I've been hunting for the instructions without success. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Monday, October 12, 2009 5:41 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Date, time and number format You should not add things to your options files which are not defined as valid for your software. DATEformat, NUMberformat, and TIMEformat have been obsolete specifications since TSM 3.7, when such controls were transferred to locale settings. The Options table may evidence the options, though not even coded in your server options file, apparently by virtue of some legacy server software. Richard Sims On Oct 12, 2009, at 1:33 AM, Grigori Solonovitch wrote: Hello Everybody, I have TSM Server 5.5.3.0 under AIX 5.3. select * from options gives: OPTION_NAME: DateFormat OPTION_VALUE: ? OPTION_NAME: TimeFormat OPTION_VALUE: ? OPTION_NAME: NumberFormat OPTION_VALUE: ? I have in dsmserv.opt file: DATEformat 1 TIMEformat 1 NUMberformat 1 I do not know from where we have ? in TSM Server table. What is this?
Re: rarely, tapes become logically unusable?
I suppose you've tried DELETE VOLUME T00015 DISCARDDATA=YES ? - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Allen S. Rout Sent: Tuesday, September 15, 2009 11:34 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] rarely, tapes become logically unusable? Hi, there. I have a small collection of tapes which appear to have become uncorrectably unusable. They were part of a server which has been decomissioned; now tsm: CTRLUPDATE LIBVOLUME 3592LIB T00015 status=private owner=GLMAIL ANR9787E The owner name specified is not defined to this server. ANS8001I Return code 11. tsm: CTRLUPDATE LIBVOLUME 3592LIB T00015 status=private owner=blargh ANR8969E The owner of volume T00015 can not be updated to owner BLARGH. ANS8001I Return code 27. So, somewhere in its black little heart, TSM remembers what server that tape went with, depite the fact that the server has been off since 2005. On the one hand this is good: it prevents me from accidentally overwriting tapes. On the other hand, it's now preventing me from deliberately overwriting tapes. What do I do? Ideally, I'd like to express to the server something like 'No really, call that blank again, I'd like to reuse it'. Relabel it, force=yes, checkin=scratch? Any ideas? - Allen S. Rout
Re: Dealloc prohibited - transaction failed
Did you try deleting by FSID? Laborious, but it works when other methods fail... e.g. (for filespace 1): DELETE FILESPACE KL10143J 1 NAMETYPE=FSID - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Loon, EJ van - SPLXM Sent: Wednesday, August 19, 2009 12:00 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Dealloc prohibited - transaction failed I was hoping to be able to solve it myself, since the server is running an unsupported TSM level (5.3.4.0), so I cannot open a PMR. Thanks anyway. Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of km Sent: dinsdag 18 augustus 2009 18:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: Dealloc prohibited - transaction failed On 18/08, Loon, EJ van - SPLXM wrote: Hi TSM-ers! I have two nodes which I cannot delete. When I issue a DELETE FILESPACE * for one of these node, I see the following errors in the log: ANR0984I Process 59041 for DELETE FILESPACE started in the BACKGROUND at 15:30:40. ANR0800I DELETE FILESPACE * for node KL10143J started as process 59041. ANR0802I DELETE FILESPACE * (backup/archive data) for node KL10143J started. ANRD ssalloc.c(1532): ThreadId 51 Dealloc prohibited - transaction failed. ANRD ThreadId 51 issued message from: ANRD ThreadId 51 0x000100017f78 outDiagf ANRD ThreadId 51 0x00010032d480 ssDealloc ANRD ThreadId 51 0x000100365534 AfDeallocSegments ANRD ThreadId 51 0x000100365e68 AfDeleteBitfileFromPool ANRD ThreadId 51 0x0001003663c8 AfDestroyAll ANRD ThreadId 51 0x0001003608a4 bfDestroy ANRD ThreadId 51 0x0001001816fc ImDeleteBitfile ANRD ThreadId 51 0x00010018a510 imDeleteObject ANRD ThreadId 51 0x0001003d3800 DeleteBackups ANRD ThreadId 51 0x0001003d4c80 imFSDeletionThread ANRD ThreadId 51 0x000163c8 StartThread ANRD ThreadId 51 0x0953650c _pthread_body ANRD imutil.c(7001): ThreadId 51 unexpected rc=87 from bfDestroy for objId=0.1066965103 ANRD ThreadId 51 issued message from: ANRD ThreadId 51 0x000100017f78 outDiagf ANRD ThreadId 51 0x000100181740 ImDeleteBitfile ANRD ThreadId 51 0x00010018a510 imDeleteObject ANRD ThreadId 51 0x0001003d3800 DeleteBackups ANRD ThreadId 51 0x0001003d4c80 imFSDeletionThread ANRD ThreadId 51 0x000163c8 StartThread ANRD ThreadId 51 0x0953650c _pthread_body ANRD imfsdel.c(1847): ThreadId 51 IM not able to delete object 0.1066965103, rc: 19 ANRD ThreadId 51 issued message from: ANRD ThreadId 51 0x000100017f78 outDiagf ANRD ThreadId 51 0x0001003d3840 DeleteBackups ANRD ThreadId 51 0x0001003d4c80 imFSDeletionThread ANRD ThreadId 51 0x000163c8 StartThread ANRD ThreadId 51 0x0953650c _pthread_body ANR0987I Process 59041 for DELETE FILESPACE running in the BACKGROUND processed 25 items with a completion state of FAILURE at 15:30:40. I cannot find both the return codes 19 and 78 in the list of known return codes for TSM... It's reproducible. Anybody seen this before? Thank you very much for any reply in advance! Kind regards, Eric van Loon Looks like an IBM support case, probably a missing object or something. -km ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 **
Re: Syntax of select statement
You could try replacing date(backup_end) = current_date -2 days with cast((current_timestamp-backup_end)days as decimal)2 - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Moyer, Joni M Sent: Wednesday, August 05, 2009 6:27 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Syntax of select statement Hi Everyone, I'm having some issues getting a script to output into an email as I would like it to and I'm not quite seeing what I am doing wrong. I am running the following: select node_name as Server , filespace_name as Possible failed File System , substr(char(backup_start),1,16) as backup_start,substr(char(backup_end),1,16) as backup_end from FILESPACES where (node_name like 'HMCH%' or node_name like 'HMPG' or node_name like 'FAX%' or node_name like 'OCS%' or node_name like 'OPM%' or node_name like 'QNM%' or node_name like 'SEV%' or node_name like 'SQL%' or node_name like 'DOC%' or node_name like 'W%' or node_name like 'E%') and date(backup_end) = current_date -2 days and it is giving me the output of: ANS8000I Server command: 'run windows_missed_backups' EMC-LS SYSTEM SERVICES 2009-02-22 01:29 2009-02-22 01:29 EMC-LS SYSTEM STATE 2009-02-22 00:45 2009-02-20 23:32 EMC-LS \\nasdx1\c$file:///\\nasdx1\c$ 2007-12-17 23:02 2007-12-17 23:03 EMEETINGS \\hmch1199\d$file:///\\hmch1199\d$ 2005-09-01 14:43 2005-09-01 14:43 EMEETINGS \\hmch1199\e$file:///\\hmch1199\e$ 2005-09-01 14:43 2005-09-01 14:43 ENVISION\\ni-highmark-ha\e$file:///\\ni-highmark-ha\e$ 2008-10-06 13:38 2008-10-06 13:39 EXCA1 EXCA1\SystemState\NULL\System State\SystemState 2009-08-05 02:49 2009-08-03 01:15 EXCA1 \\exca1\c$file:///\\exca1\c$ 2009-08-03 01:14 2009-08-03 01:16 EXCA1 \\exca1\d$file:///\\exca1\d$ 2009-08-03 01:16 2009-08-03 01:17 EXCA2 EXCA2\SystemState\NULL\System State\SystemState 2009-07-24 04:07 2009-07-24 06:06 EXCA2 \\exca2\c$file:///\\exca2\c$ 2009-07-25 01:44 2009-07-25 01:48 EXCA2 \\exca2\d$file:///\\exca2\d$ 2009-07-25 01:43 2009-07-25 01:44 EXHT1 EXHT1\SystemState\NULL\System State\SystemState 2009-08-03 03:40 2009-07-24 05:25 EXHT1 \\exht1\c$file:///\\exht1\c$ 2009-07-24 05:26 2009-07-24 05:29 but I would like for it to appear as follows: Server File System Start Date End Date EMC-LS SYSTEM SERVICES 2009-02-22 01:29 2009-02-22 01:29 EMC-LS SYSTEM STATE 2009-02-22 00:45 2009-02-20 23:32 EMC-LS \\nasdx1\c$file:///\\nasdx1\c$ 2007-12-17 23:02 2007-12-17 23:03 If anyone has any suggestion on how I can fix this I would really appreciate it a lot!!! Thanks in advance! Joni Moyer Storage Administrator III (717)302-9966 joni.mo...@highmark.com This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.
Re: TSM gui
Carol Trible wrote: It seems that long term customers tend to stick to the command line, but new customers who start with the Administration Center like it, so I would reccomend giving it a try. I started administering TSM in 2006, and my first task was to install the Administration Center for the first time at this site. I've used it ever since. I am currently using the 6.1 release to administer two 5.5.3.0 servers and one 5.5.1.0 server. (Incidentally, I had trouble finding the software for the new Admin Center, and so did the first three IBM staff members who tried to help me. Although the installation process tells you it is Installing... TSM Administration Center, the product name you have to look for now is Tivoli Storage Manager Reporting and Monitoring.) The 6.1 Admin Center is genuinely better than previous releases, and twice as fast, but it's still agonizingly slow for longer inquiries. Some queries are impossible when using the Admin Center command line interface, because they die before returning results. For the last few months, I've had a Servergraph tool to use as well, and inquiries that take only seconds with Servergraph take ten minutes using the Admin Center. I'd certainly recommend that new TSM administrators try out the Admin Center - it's so useful - but you still need a LOT of patience to use it. - Margaret Clark Systems Programmer, San Diego Data Processing Corporation
Re: Once again I've a problem on the TSM client side with specifying a path for an object
If there's nothing in the filespace that you need to keep, you can try this: delete filespace WHQ_FILESERV_1 2 nametype=FSID I've also been unable to delete filespaces using the filespace name, or indeed display them using the Admin Center, but I've been successful using the FSID. - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kauffman, Tom Sent: Monday, April 13, 2009 12:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Once again I've a problem on the TSM client side with specifying a path for an object We can't seem to find these from the client: Node Name Type Filespace FSID Client's Name for File Name --- -- -- WHQ_FILESERV_1 Bkup \\whq_fil-2 \TSMIMAGE-WINNT\ VOL_DATA eserv_1\- x$ WHQ_FILESERV_1 Bkup \\whq_fil-2 \TSMIMAGE-WINNT\ VOL_EXTENTS eserv_1\- x$ We're trying to delete them but we just get back the respnse that no objects matched the string - and if we try 'delete backup -pick \\whq_fileserv_1\x$\*file:///\\whq_fileserv_1\x$\*' we get a pick list that does NOT include the above. Is it possible we're logged on as the wrong userid? If so, how do we determine the correct userid? TIA Tom Kauffman NIBCO, Inc CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: TSM-Client starts wrong scheduler
Richard Sims pointed out the discrepancy between midnight and noon in your apparent scheduled start times, which is certainly worrying. I also notice that your scheduler is not starting up until almost 25 minutes after the scheduled start time. Why is that? If your startup window is short (say, 15 minutes), is it possible that your window really has elapsed, as the error message suggests? - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alexander Födisch Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM-Client starts wrong scheduler Hi, since a few weeks we have a strange behaviour with one of our Backup-Clients. When the scheduler should start, the clients says that the scheduler is out of time and plans the next window start: 01/08/2009 21:03:50 --- SCHEDULEREC QUERY BEGIN 01/08/2009 21:03:50 --- SCHEDULEREC QUERY END 01/08/2009 21:03:50 Next operation scheduled: 01/08/2009 21:03:50 01/08/2009 21:03:50 Schedule Name: EVANPDC_DAILY_INCR 01/08/2009 21:03:50 Action:Incremental 01/08/2009 21:03:50 Objects: 01/08/2009 21:03:50 Options: 01/08/2009 21:03:50 Server Window Start: 00:00:00 on 01/09/2009 01/08/2009 21:03:50 01/08/2009 21:03:50 Scheduler has been stopped. now the scheduler should start: 01/09/2009 00:24:51 TSM Backup-Archive Client Version 5, Release 5, Level 1.0 01/09/2009 00:24:51 Querying server for next scheduled event. 01/09/2009 00:24:51 Node Name: ZENTGPFSDATA.EVA.MPG.DE 01/09/2009 00:24:51 Session established with server BACKUP: Windows 01/09/2009 00:24:51 Server Version 5, Release 4, Level 3.0 01/09/2009 00:24:51 Server date/time: 01/09/2009 00:24:49 Last access: 01/09/2009 00:15:21 but it just plans the next one: 01/09/2009 00:24:51 --- SCHEDULEREC QUERY BEGIN 01/09/2009 00:24:51 --- SCHEDULEREC QUERY END 01/09/2009 00:24:51 Next operation scheduled: 01/09/2009 00:24:51 01/09/2009 00:24:51 Schedule Name: EVANPDC_DAILY_INCR 01/09/2009 00:24:51 Action:Incremental 01/09/2009 00:24:51 Objects: 01/09/2009 00:24:51 Options: 01/09/2009 00:24:51 Server Window Start: 12:00:00 on 01/09/2009 01/09/2009 00:24:51 01/09/2009 00:24:51 Executing scheduled command now. 01/09/2009 00:24:51 ANS1814E Unable to start the scheduled event 'EVANPDC_DAILY_INCR' 01/09/2009 00:24:51 ANS1815E Either the window has elapsed or the schedule has been deleted But sometimes it works. That's very strange. Any ideas? TSM-Server version: 5.4.3.0 TSM-Server OS: Windows Server 2003 TSM-Client version: 5.5.1.0 TSM-Client OS: SLES 10 SP2 Best, Alex -- Mit besten Grüßen / Best Regards Alexander Födisch Max Planck Institute for Evolutionary Anthropology -Central IT Department- Deutscher Platz 6 D-04103 Leipzig Phone: +49 (0)341 3550-168 +49 (0)341 3550-154 Fax:+49 (0)341 3550-119 Email: foedi...@eva.mpg.de
Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address.
I hope it works for you. We recently upgraded to 5.5.1 server on a z/OS platform, after which most of our scheduled backups failed, apparently because of some perceived discrepancy found by reverse lookup. We added the DNSLOOKUP NO parameter as suggested by IBM support (it is undocumented for z/OS) and by itself, it did not solve our problems. We also had to restart the client acceptors on all the clients. In a few cases we had to perform manual backups before the new server software was satisfied. - Margaret Clark Systems Programmer, San Diego Data Proc4essing Corporation -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 4:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. TSM will populate field TCP_ADDRESS in table NODES with the numeric address of the client when it connects, so not having name lookups performed is really no loss in functionality... And now that I know about that option, it's going in next restart, because it will cut latency, which will matter for things like when an RMAN client deletes its old backups in a flurry of hundreds of separate sessions in sequence. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:35 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Bill, Never heard of this option. Won't this make us unable to reach ANY clients then, unless we put them in the local /etc/hosts file? That would be impractical, with 1600 clients in our environment. Or will TSM use the cached copy it saved when the client first connected in? Do you use that in your environment? Does it work seamlessly, or are there gotchas? Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bill Boyer Sent: Thursday, September 18, 2008 1:31 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Try DSNLOOKUP NO in the dsmserv.opt file. The default is YES. Bill Boyer Hang in there, retirement is only thirty years away! - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 1:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM scheduler can't reach TSM client even though it seems to know it's IP address. Tim, We have tried this, but it doesn't help. When you issue a 'q node stlo-mpvadm f=d' the TSM scheduler clearly has the correct address cached for it: ... TCP/IP Name: STLO-MPVADM TCP/IP Address: 10.52.27.204 .. So the TSM scheduler seems to still know what the IP address is, but for some reason still does a DNS resolve I guess. Best Regards, John D. Schneider Phone: 314-364-3150 Cell: 314-750-8721 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Conway, Timothy Sent: Thursday, September 18, 2008 11:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. The simplest solution is upd node STLO-MPVADM HLA=10.52.27.204 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Schneider, John Sent: Thursday, September 18, 2008 9:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM scheduler can't reach TSM client even though it seems to know it's IP address. Greetings, We are running TSM 5.4.3.0 on AIX 5.3ML5. Most of our TSM clients are 5.4.x or 5.5.x. Most of our clients run schedmode prompted so the TSM server launches the schedule. We see an occasional problem where a Windows client is set up wrong in Active Directory (which feeds DNS), and the TSM scheduler won't be able to start the client scheduler. It will get errors such as: 09/18/08 05:51:12 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:52:58 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:54:44 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:56:30 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 05:58:16 ANR8213W Session open with stlo-mpvadm.company.com timed out. (SESSION: 243) 09/18/08 06:00:01 ANR2578W Schedule WIN_PROD_0300 in domain WIN_PROD for
Re: Anyone know of issues running older clients against 5.4.3 server?
We are using 5.4.1 server and have twenty-five clients at the 5.1.5 level or worse that are doing just fine. - Margaret Clark, San Diego Data Processing Corporation -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul Zarnowski Sent: Thursday, April 10, 2008 11:21 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Anyone know of issues running older clients against 5.4.3 server? We are about to upgrade our servers from 5.3.4 to 5.4.3. I'd like to know if anyone knows of any problems running older clients with a 5.4.x server. While I know IBM only supports 1 version back, it's usually the case that older clients continue to work (with some exceptions). Thanks for any feedback. We still have a bunch of 5.1.5 clients out there that we've been unsuccessful in prodding our users to upgrade from, so that's the level I'm most concerned about. ..Paul -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]
Re: Top 20 (or so) misunderstood things about TSM
My favorite is the customer who believes their every backup is on their own private tape, and will we just send it to them? - Margaret Clark, San Diego Data Processing -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston Sent: Monday, March 31, 2008 2:49 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Top 20 (or so) misunderstood things about TSM Hey there, folks! I'm working very hard on my next book, which will have some product-specific information in it. I'm covering multiple products, so I won't go TOO deep on individual products, but I'd like to do my best to cover misunderstood or frequently asked topics for each major product. I figured that no one would know better than this list which topics people tend to get confused. What topics do you think should go on that list? (I've got my personal preferences, but I don't want to prejudice your thoughts.) What are the top 5/20/30 things about TSM that you think people get wrong? TIA --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies
