Re: TSM upgrade from 3.7 to 5.1
It is AIX 4.3.3 -Original Message- From: Joshua Bassi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 10:13 AM To: [EMAIL PROTECTED] Subject:Re: TSM upgrade from 3.7 to 5.1 Sachin, What platform are you on? The upgrade procedure varies based upon the operating system the TSM server is running on. Please provide the OS version and release for us to assist you with the installation further. Also, you should have received a Quick Start guide with your TSM upgrade. Installation info can also be found there. It can also be downloaded at the TSM web site www.tivoli.com/tsm. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Ganu Sachin, IBM Sent: Monday, September 23, 2002 8:20 PM To: [EMAIL PROTECTED] Subject: TSM upgrade from 3.7 to 5.1 Hi I am planning to upgrade my TSM from 3.7 to 5.1 . Can someone help me out for the procedure ? Will it overwrite my existing TSM db ? Regards Sachin Ganu
Re: Reading data from tape
I assume the tapes from your onsite and offsite pool have also been taken??? Otherwise just mark the tape destroyed and restore it, all the data will come back from the onsite or offsite copy pool. ..Rikk -Original Message- From: Gill, Geoffrey L. [mailto:[EMAIL PROTECTED]] Sent: 23 September 2002 23:08 To: [EMAIL PROTECTED] Subject: Reading data from tape I hope someone has a real good knowledge of how TSM data is written to/read from tape. I'm in a predicament that I may never be able to get tapes back to read any node data off of them unless I can satisfactorily answer questions. Unfortunately I don't know the questions yet so I don't even know what to ask here. Perhaps someone who is knowledgeable about 3590 tape technology or someone from Tivoli monitoring the list can help with this. I hate to have to call Tivoli since so far I haven't got much in the way of answers on the other questions I've been asking on classified material on tape. What kind of questions would you expect to answer if a tape was removed from the library with mixed node data on it and it was needed to restore some other node's data. Keep in mind that the tape was removed because it originally had classified material stored on it. It may or may not still have the data depending on expiration. I already know how to explain the ins and outs of expiration/reclamation but we all know the DATA is really still there. My guess is I'm never really going to be able to get these tapes back and whatever data was on them is probably gone forever but I need to at least be able to answer some questions like are they indexed or how the data is stored, how it's read back etc. Thanks for the help, Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154 Equitas Limited, 33 St Mary Axe, London EC3A 8LL, UK NOTICE: This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify [EMAIL PROTECTED] and delete the message and any attachments accompanying it immediately. Equitas reserve the right to monitor and/or record emails, (including the contents thereof) sent and received via its network for any lawful business purpose to the extent permitted by applicable law Registered in England: Registered no. 3173352 Registered address above
Re: CPU information Gatherer
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of More importantly, can some of the windows guys amongst you advise how to do something similar for NT4 and Win2K? Preferably without having any special services running and without having any reskits installed. set | grep NUMBER_OF_PROCESSORS -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
AIX TSM v4.2.1.25 client dsmerror - TCP/IP received rc 25 trying to accept connection from server?
Enviro: TSM client 4.2.1.25 running on H50 AIX 4.3.3.10. I get this 1 client dsmerror, no other error message of any kind, except this one: 09/23/02 11:05:19 TCP/IP received rc 25 trying to accept connection from server. I don't have any other kinds of client errors with this client in the activity log. Someone last week put this same error message out for discussion, but I never heard discussion of it. Does anyone know what this means? I seem to recall not receiving this same error with my AIX TSM v4.1.2 client, though. Comments? Ken Sedlacek AIX/TSM/UNIX Administrator [EMAIL PROTECTED] IBM Certified Specialist: RS/6000 AIX v4.3 Support IBM Certified Specialist: RS/6000 SP PSSP 3 Tivoli Certified Consultant - Tivoli Storage Manager v4.1
Re: ADSM-L Digest - 22 Sep 2002 to 23 Sep 2002 (#2002-264)
Abdulaziz, Officially TSM doesn't support MetaFrame. I found the main problem to be the remapping of the drives, TSM seems to be hard coded to backup system objects from drive c:. If i don't remap drives on MetaFrame, TSM seems to work fine. john [EMAIL PROTECTED] 09/24/02 12:05AM Date:Mon, 23 Sep 2002 10:13:42 +0300 From:Abdulaziz Almuammar [EMAIL PROTECTED] Subject: how to backup CITRIX server? Hi guys, i have CITRIX META FRAME 1.8 and i want to backup this server. the = problem is=20 i installed the windows2000 client 4.2.2 on it but when i schedule the = backup some how the schedule stops and the backup dosen't go fine. i = tried to backup the server manually but i found that it didnt backup all = data and it finished fast. is there a special client for CITRIX? i have TSM server 4.1.5 thaks,
test
test
[no subject]
Hi there, all you tsm-ers! Maybe someone has a few hints for me: Planning to upgrade TSM-Server from 4.2.1.11 to 5.1. Are there any known problems? Next thing is Data Warehouse runs DB2 UDB EEEin an SP-Environment, will be upgraded to DB2 7xx. on a new S85 machine with FastT FibreChannel, all arriving on Friday. Since our Library is an Ultrium 3584 also with FC Drives, attached to both server and DB2-Machine, my idea ist to have the client on the Data Warehouse send the DB-Backups directly to the tapes and the Metadata to the server. What is the best (most simple and least complicated!) way to achieve this?? Thanks in advance for your help [EMAIL PROTECTED] Michael Klemmer AIX-TSM-Tivoli Admin Spar Handels-AG Hamburg Germany
Re: how to backup CITRIX server?
I am using 4.2.2.0 client to backup W2K Citrix servers. System doesn't have a C drive. Has I, J K. Installed TSM on I drive. Remember to set correct Drive paths for logs etc. as they will default to C. Backs up System Objects o.k. David Longo [EMAIL PROTECTED] 09/23/02 03:13AM Hi guys, i have CITRIX META FRAME 1.8 and i want to backup this server. the problem is i installed the windows2000 client 4.2.2 on it but when i schedule the backup some how the schedule stops and the backup dosen't go fine. i tried to backup the server manually but i found that it didnt backup all data and it finished fast. is there a special client for CITRIX? i have TSM server 4.1.5 thaks, MMS health-first.org made the following annotations on 09/24/2002 10:34:43 AM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Anyone tried 5.1.1.6?
I'm on 5.1.1.4 on AIX 4.3.3. The biggest headaches with expiration are resolved, but it appears that once MAXSESS is hit, it is never decremented until the server is recycled. I could go back to 5.1.1.x, the interim release I ran on for most of August and September, or I could put in 5.1.1.6. But recent experiences make me very leery of this. Has anyone out there tried 5.1.1.6 with a large system, like 300+ clients?? Anything good or bad to report??
TSM and multiprocessing
Hello TSMers, is TSM Server 4.2 able to do multiprocessing? How can I configure it? MfG Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
Re: Anyone tried 5.1.1.6?
Hi Fred, I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday. All I can say is 'not pretty'. This is due to the SYSTEM OBJECT problem. If you don't know what this is, you will soon if you have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6 servers. The basic problem is that TSM isn't expiring anything in the SYSTEM OBJECTs filespace. Some of our clients had over 20GB in these filespaces! Needless to say, the database blew up while trying to find out what was going on. To see if you have this problem, you can type in show version nodename SYSTEM OBJECT namet=uni file (only use namet=uni if the filespace is unicode). Then check through the file and look for the number of occurrences of a file, say ROUTE.EXE. A normal SYSTEM OBJECT filespace, with four versions, shouldn't be over a gig. The good news is that v5.1.1.6 does NOT have the SYSTEM OBJECT problem and the new server is doing very well. I am writing up the post mortem on the conversion and will post to the list later this week (at the request of Tivoli level 2). Gretchen Thiele Princeton University
Re: Anyone tried 5.1.1.6?
Gretchen, I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't run expiration for six weeks. But I haven't had a scheduled session accepted since I hit MAXSESS at 3:04 yesterday morning. Are you seeing this in 5.1.1.6? At 10:39 AM 9/24/2002 -0400, you wrote: Hi Fred, I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday. All I can say is 'not pretty'. This is due to the SYSTEM OBJECT problem. If you don't know what this is, you will soon if you have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6 servers. The basic problem is that TSM isn't expiring anything in the SYSTEM OBJECTs filespace. Some of our clients had over 20GB in these filespaces! Needless to say, the database blew up while trying to find out what was going on. To see if you have this problem, you can type in show version nodename SYSTEM OBJECT namet=uni file (only use namet=uni if the filespace is unicode). Then check through the file and look for the number of occurrences of a file, say ROUTE.EXE. A normal SYSTEM OBJECT filespace, with four versions, shouldn't be over a gig. The good news is that v5.1.1.6 does NOT have the SYSTEM OBJECT problem and the new server is doing very well. I am writing up the post mortem on the conversion and will post to the list later this week (at the request of Tivoli level 2). Gretchen Thiele Princeton University
starting TSM without it doing anything
Is there a way to start TSM server without it doing anything? Kinda like a single-user mode? Sometimes, I like to run an audit after rebooting TSM and the tape library, but as soon as I start TSM, it begins to do various things like space reclamation etc. I *could* remember to disable sessions and increase the reclamation threshold before shutting it down, but sometimes I don't remember to do these things. Currently running TSM server 4.1.3 on AIX 4.3.3 ML 10. johnn
Re: Upgrade and DB2 LAN-free
Michael, Upgrade to 5.1 should not be a problem. The default hint - take a backup of your (v4.2.1) TSM DB to have the ability to step back. What do you mean library is attached to both server and DB2-machine? If drives are direct-attached (without SAN switch) you can define several library control paths but cannot share drives for TSM LAN-free backups. If drives are SAN switch/fabric-sttached you can use TSM LAN-free if DB2 UDB v7.x is at FP04 or FP05 (sorry cannot recall the exast FP). Be aware that you cannot use same FC HBAs for FastT and LTO. Side remark: why you have chosen FastT (midrange storage) for high-end database server? How can you be sure FastT would not be a bottleneck for DB2 performance. The way to achieve this is straightforward - setup a ITSM storage agent on the S85, define LAN-free in dsm.sys/dsm.opt (ones used by TSM API client, not B/A client) and define backup/userexit in DB2 to use TSM. Some usefull hints can be found in the redbook Backing up DB2 using TSM (SG24-6247) Will DB2 EEE be only version upgraded again to EEE on cluster or will go to EE/EEE-version on single machine? BTW: Why you put subject on your test post and not on the real one? Use subjects, they help to identify your post among hundreds of other posts. Zlatko Krastev IT Consultant Klemmer Michael [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 24.09.2002 16:49 Please respond to klemmer To: [EMAIL PROTECTED] cc: Subject: Hi there, all you tsm-ers! Maybe someone has a few hints for me: Planning to upgrade TSM-Server from 4.2.1.11 to 5.1. Are there any known problems? Next thing is Data Warehouse runs DB2 UDB EEEin an SP-Environment, will be upgraded to DB2 7xx. on a new S85 machine with FastT FibreChannel, all arriving on Friday. Since our Library is an Ultrium 3584 also with FC Drives, attached to both server and DB2-Machine, my idea ist to have the client on the Data Warehouse send the DB-Backups directly to the tapes and the Metadata to the server. What is the best (most simple and least complicated!) way to achieve this?? Thanks in advance for your help [EMAIL PROTECTED] Michael Klemmer AIX-TSM-Tivoli Admin Spar Handels-AG Hamburg Germany
Re: Problem deleting filespace SYSTEM OBJECT
Hello, in the meantime I upgraded to 5.1.1.6. With this level I could delete the filespace without problem. However, I couldn't resist to try cleanup backupgroup again. Under 5.1.1.4 it worked. It only seemed strange that it obviously didn't finish its work, as Joel described: On 5.1.1.4, I did the CLEANUP BACKUPGROUP and I still could not delete the system objects. I reran the cleanup command numerous times and each time it reported inspecting and deleting fewer objects than the previous run. On 5.1.1.6 cleanup backupgroup stopped immediately with return code 4. In the activity log I found the following messages: 09/24/02 10:31:51 ANR2017I Administrator GERHARD issued command: CLEANUP BACKUPGROUPS 09/24/02 10:31:51 ANRD imutil.c(6663): ThreadId67 Failure deleting member 0 585368742 for group 1637 3 - encountered repeatedly in loop. 09/24/02 10:31:51 ANRD imutil.c(3931): ThreadId67 Error 19 deleting dependents for node 0 fs 0 and leader 1637 3. Now I'm little bit concerned. Is cleanup backupgroup broken or is it my database? My suggestion to all TSM admins is to do a QUERY OCCUPANCY * SYSTEM OBJECT to verify that you do not have excessive copies. How can you tell from the output of the q occ command how many excessive copies you have? BTW, I cannot confirm that system objects are not expired. I used the following SQL statement in the middle and at the end of an expiration process: select sum(num_files) from occupancy where filespace_name='SYSTEM OBJECT' The first number I got was 1043479, the last 1012998. So I got rid of at least 30481 files. Best regards Gerhard --- Gerhard Rentschleremail:[EMAIL PROTECTED] Regional Computing Center tel. ++49/711/685 5806 University of Stuttgart fax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany
Re: starting TSM without it doing anything
You can set TCPPORT to 1600, or something, in the options file and use the WebAdmin to see what you want. I don't know if you can use SETOPT to reopen 1500 or not. At 10:56 AM 9/24/2002 -0400, you wrote: Is there a way to start TSM server without it doing anything? Kinda like a single-user mode? Sometimes, I like to run an audit after rebooting TSM and the tape library, but as soon as I start TSM, it begins to do various things like space reclamation etc. I *could* remember to disable sessions and increase the reclamation threshold before shutting it down, but sometimes I don't remember to do these things. Currently running TSM server 4.1.3 on AIX 4.3.3 ML 10. johnn
Re: Anyone tried 5.1.1.6?
Hi Fred, I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't run expiration for six weeks. It's a pain, I've got a routine set up to find the oversized SYSTEM OBJECT filespaces and then delete them, but I have two servers with thousands of WinXP/2K nodes that bloated the databases up to 250GB. I'm just trying to stay above water on these two and then just move the nodes to a v5 server for a big 'do over'. Sigh. Bottom line, get your SYSTEM OBJECT filesystems in check now! But I haven't had a scheduled session accepted since I hit MAXSESS at 3:04 yesterday morning. Are you seeing this in 5.1.1.6? Not sure what problem you are seeing. If all of your sessions are in use, i.e., you've hit MAXSESS, I wouldn't expect any scheduled sessions to get in. Or am I missing something? Gretchen Thiele Princeton University
CLEANUP BACKUPGROUPS in v5.1.1.6
I ran into this in my conversion, too: ANRD imutil.c(6663): ThreadId67 Failure deleting member 0 585368742 for group 1637 3 - encountered repeatedly in loop. It took an audit (fix=yes detail=yes) to correct. If you try to run expire invent, you will notice that it has a tough time ending. There are other things that I ran into during the audit that I will write up and submit this week. Gretchen Thiele Princeton University
Re: Anyone tried 5.1.1.6?
In previous versions, when MAXSESS is hit, everybody either goes into a wait (I once saw over a thousand waiting because of a communications problem) or they are retried until the number of active goes below the maximum. On this patch, once the max is hit, it stays. So in an empty system, a SQL dump scheduled for 9:00 this morning was rejected for all sessions in use. If I recylce the machine, the count starts over. At 10:55 AM 9/24/2002 -0400, you wrote: But I haven't had a scheduled session accepted since I hit MAXSESS at 3:04 yesterday morning. Are you seeing this in 5.1.1.6? Not sure what problem you are seeing. If all of your sessions are in use, i.e., you've hit MAXSESS, I wouldn't expect any scheduled sessions to get in. Or am I missing something? Gretchen Thiele Princeton University
Sharing library between two TSM servers.
Hi TSMers, I have an STKL700e library that I would like to share between two different TSM servers - Has some body that before? could I please get some feed back on that . STK is providing us ACSLS - but the catch is that it has to be installed on a different server than TSM ( IBM does not support TSM and ACSLS sever on the server server). Also, Is it possible to share the library between TSM and commvault. Thanks in advance Mansoor Bajwa Canadian Pacific Railway. -- IMPORTANT NOTICE - AVIS IMPORTANT -- Computer viruses can be transmitted via email. Recipient should check this email and any attachments for the presence of viruses. Sender and sender company accept no liability for any damage caused by any virus transmitted by this email. This email transmission and any accompanying attachments contain confidential information intended only for the use of the individual or entity named above. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above email address. Le courrier électronique peut être porteur de virus informatiques. Le destinataire doit donc passer le présent courriel et les pièces qui y sont jointes au détecteur de virus. Lexpéditeur et son employeur déclinent toute responsabilité pour les dommages causés par un virus contenu dans le courriel. Le présent message et les pièces qui y sont jointes contiennent des renseignements confidentiels destinés uniquement à la personne ou à lorganisme nommé ci-dessus. Toute diffusion, distribution, reproduction ou utilisation comme référence du contenu du message par une autre personne que le destinataire est formellement interdite. Si vous avez reçu ce courriel par erreur, veuillez le détruire immédiatement et en informer lexpéditeur à ladresse ci-dessus. -- IMPORTANT NOTICE - AVIS IMPORTANT --
Re: Backupset from other client?
That did the trick. I guess that if you had removed the old client's name and filespace areas, you would have to redefine the client before you could do this. When you use the virtualnodename, you are asked for the clients name and password which makes sense. Thanks for the assist... -- Kevin W. Reed - Unix Systems Engineer ConocoPhillips -Original Message- From: Richard Stratton [SMTP:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 4:14 PM To: [EMAIL PROTECTED] Subject: Re: Backupset from other client? Kevin, You may have to connect to the TSM Server via the backup agent on 'Ash' while emulating the backup agent 'Phxrst03' by using the VIRTUALNODENAME option when you invoke dsmc ie: dsmc -virtualnodename=Phxrst03 Rick -Original Message- From: Reed, Kevin: [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 3:34 PM To: [EMAIL PROTECTED] Subject: Backupset from other client? I'm attempting to restore a couple files from a backupset that was made on a client before it was moved to a new box and had its name changed. Both the clients were connected to the same tsm server. When the backupset was made, the client was called : phxrst03. That backup set still exists on the tsm server but I can't seem to get to it from the new box. Old NamePhxrst03 New NameAsh Backupset PHXRST03_FULL_BACKUPSET.10462763 When I issue the restore command on the new box (Ash), it says it can't find the backupset. tsm restore backupset PHXRST03_FULL_BACKUPSET.10462763 /apps/temp/* /tmp/ -loc=server The error is: ANS1934E Backup set 'PHXRST03_FULL_BACKUPSET.10462763' not found However, the tsmserver the client is connected to does have the backupset and can see it: Node NameBackup Set Name Date/Time Retention Device Description --- --- --- -- PHXRST03 PHXRST03_FULL_BACKUPSET.10462763 09/18/02 09:19:35 180 LTO No Description I think I am missing a step here. Even though the tsm server can see the file, the client ash doesn't seem to know about it. What do I need to do to get the ash client to access the backupset made by phxrst03?? -- Kevin W. Reed - Unix Systems Engineer ConocoPhillips
Re: Sharing library between two TSM servers.
You can share the library with more than 1 TSM server if using ACSLS. This will allow you to assign the tape drives in the library to one TSM server or another by defining the library type as external. If you want to dynamically share drives in the Storage Tek library between multiple TSM servers then you will also have to install and configure Gresham's EDU DistribuTape software on each TSM server. I don't know about commvault. Nici Nici Albrecht MDR Consulting Education 210-860-4641 Mansoor Bajwa wrote: Hi TSMers, I have an STKL700e library that I would like to share between two different TSM servers - Has some body that before? could I please get some feed back on that . STK is providing us ACSLS - but the catch is that it has to be installed on a different server than TSM ( IBM does not support TSM and ACSLS sever on the server server). Also, Is it possible to share the library between TSM and commvault. Thanks in advance Mansoor Bajwa Canadian Pacific Railway. -- IMPORTANT NOTICE - AVIS IMPORTANT -- Computer viruses can be transmitted via email. Recipient should check this email and any attachments for the presence of viruses. Sender and sender company accept no liability for any damage caused by any virus transmitted by this email. This email transmission and any accompanying attachments contain confidential information intended only for the use of the individual or entity named above. Any dissemination, distribution, copying or action taken in reliance on the contents of this email by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please immediately delete it and notify sender at the above email address. Le courrier électronique peut être porteur de virus informatiques. Le destinataire doit donc passer le présent courriel et les pièces qui y sont jointes au détecteur de virus. Lexpéditeur et son employeur déclinent toute responsabilité pour les dommages causés par un virus contenu dans le courriel. Le présent message et les pièces qui y sont jointes contiennent des renseignements confidentiels destinés uniquement à la personne ou à lorganisme nommé ci-dessus. Toute diffusion, distribution, reproduction ou utilisation comme référence du contenu du message par une autre personne que le destinataire est formellement interdite. Si vous avez reçu ce courriel par erreur, veuillez le détruire immédiatement et en informer lexpéditeur à ladresse ci-dessus. -- IMPORTANT NOTICE - AVIS IMPORTANT --
ANR9999D smnode.c.5323.: Error validating inserts for event
We get this message when using the MS Exchange TDP, and I think also when running the MS SQL TDP. We are running a V4.1.3 server on AIX, with V2.2.0 of the TDP clients. Is there something we can do to stop getting this message without upgrading the server? Will upgrading to V4.2.x of the server clear this up?
Re: TSM and multiprocessing
The multiprocessing capabilities in TSM are built in and do not need to be configured. IBM recommends that a TSM server be installed on a system with 4 CPUs at most. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Sascha Braeuning Sent: Tuesday, September 24, 2002 7:41 AM To: [EMAIL PROTECTED] Subject: TSM and multiprocessing Hello TSMers, is TSM Server 4.2 able to do multiprocessing? How can I configure it? MfG Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
TSM Database tables
Hi All; An easy one perhaps but I would like to know How can I find out all the TSM table names? TIA regards; Hussein A. -Original Message- From: Sam Haziprodromu [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Missing volume Hi *smers, I have a strange problem for me. We deleted the data from a volume to make it a scratch and we can not see the volume when we do a q libvol or q volume. We can't see the volume. In the activity log the process ran to successful conclusion. Help TIA Sam Haziprodromu I.T.
Re: Anyone tried 5.1.1.6?
At 10:55 AM 9/24/02 -0400, you wrote: Hi Fred, I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't run expiration for six weeks. It's a pain, I've got a routine set up to find the oversized SYSTEM OBJECT filespaces and then delete them, but I have two servers with thousands of WinXP/2K nodes that bloated the databases up to 250GB. I'm just trying to stay above water on these two and then just move the nodes to a v5 server for a big 'do over'. Sigh. Bottom line, get your SYSTEM OBJECT filesystems in check now! But I haven't had a scheduled session accepted since I hit MAXSESS at 3:04 yesterday morning. Are you seeing this in 5.1.1.6? Not sure what problem you are seeing. If all of your sessions are in use, i.e., you've hit MAXSESS, I wouldn't expect any scheduled sessions to get in. Or am I missing something? Gretchen Thiele Princeton University
Re: TSM Database tables
Hussein Abdirahman wrote: Hi All; An easy one perhaps but I would like to know How can I find out all the TSM table names? TIA regards; Hussein A. -Original Message- From: Sam Haziprodromu [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Missing volume Hi *smers, I have a strange problem for me. We deleted the data from a volume to make it a scratch and we can not see the volume when we do a q libvol or q volume. We can't see the volume. In the activity log the process ran to successful conclusion. Help TIA Sam Haziprodromu I.T. Sam, You can do the following: select * from syscat.tables or if you just want the table names and nothing else: select tabname from syscat.tables That will do it. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===
Re: TSM Database tables
select tabname from syscat.tables -Original Message- From: Hussein Abdirahman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 12:22 PM To: [EMAIL PROTECTED] Subject: TSM Database tables Hi All; An easy one perhaps but I would like to know How can I find out all the TSM table names? TIA regards; Hussein A. -Original Message- From: Sam Haziprodromu [mailto:[EMAIL PROTECTED]] Sent: Monday, September 23, 2002 3:21 PM To: [EMAIL PROTECTED] Subject: Missing volume Hi *smers, I have a strange problem for me. We deleted the data from a volume to make it a scratch and we can not see the volume when we do a q libvol or q volume. We can't see the volume. In the activity log the process ran to successful conclusion. Help TIA Sam Haziprodromu I.T.
Re: TSM and multiprocessing
from a client point of view, look at resourceutilization (1-10) Things like a base dsmc incr will fire off a thread to process each ~mount point~ to be processed... you still only see one task on the client but will see multiple sessions on the server. I believe the max sessions will be 8 if you use resourceutil 10 Dwight -Original Message- From: Sascha Braeuning [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 9:41 AM To: [EMAIL PROTECTED] Subject: TSM and multiprocessing Hello TSMers, is TSM Server 4.2 able to do multiprocessing? How can I configure it? MfG Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED]
Servergraph TSM on solaris-2.8
Hi all, just an Fyi. not sure if anyone else have experienced this, We have TSM server 4.2.20 running on sol-2.8 and we were trying to eval servergraph, the servergraph process started killing the TSM server leading to core dumps! we have a PMR open with Tivoli and have updated servergraph with the issue as well. Apparently IBM said that this is a bug on the 4.2.20 that when contacted with multiple *dsmadmc -console* processes to the server has lead it to go down. Both the parties seem to be looking into this -C
Re: Servergraph TSM on solaris-2.8
For the record - we're innocent! dsmadmc -console sometimes crashes this release of TSM on Solaris. We are unrepentant in our use of dsmadmc -console. We have Servergraph installed at maybe 100 other sites, and have never seen this happen before. TSM says it's a known problem: I quote from Tivoli support: It appears that one of these console sessions was starting, but encountered an error causing it to be closed. Somehow when we attempt to close the session during this sequence of events, an invalid memory reference is made causing the server to core dump. This appears to be a defect in the TSM Server, and I will be pursuing this with development. Just for the record. - Mr. Lindsay Morris Lead Architect, Servergraph 859-253-8000 ofc 425-988-8478 fax -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Chetan H. Ravnikar Sent: Tuesday, September 24, 2002 1:01 PM To: [EMAIL PROTECTED] Subject: Servergraph TSM on solaris-2.8 Hi all, just an Fyi. not sure if anyone else have experienced this, We have TSM server 4.2.20 running on sol-2.8 and we were trying to eval servergraph, the servergraph process started killing the TSM server leading to core dumps! we have a PMR open with Tivoli and have updated servergraph with the issue as well. Apparently IBM said that this is a bug on the 4.2.20 that when contacted with multiple *dsmadmc -console* processes to the server has lead it to go down. Both the parties seem to be looking into this -C
Re: ADSM-L Digest - 19 Sep 2002 to 20 Sep 2002 (#2002-261)
Hi, Having the communication time out(comtimeout) on the server set very low could cause a tcp/ip time out problem. Please increase the commtimeout to 500 seconds, the default is 60 seconds. To have a successful restore, the password signon process'tdpipswd' must be successful. Regards. Cai Date:Thu, 19 Sep 2002 15:11:29 +0100 From:Deborah Stephenson [EMAIL PROTECTED] Subject: TDP(?) error Hi We are trying to perform an Informix onbar restore from one node to another. We get the following errors (please note there are no TDP messages registed in the activity log): dsierror.log == 19/09/02 13:40:58 TcpOpen: TCP/IP error connecting to server. 19/09/02 13:40:58 sessOpen: Failure in communications open call. rc: -50 dsmerror.log == blank bar_act.log == 2002-09-19 13:40:58 23326 21832 /s026/informix/bin/onbar_d -r -p 2002-09-19 13:40:58 23326 21832 XBSA Error (BSAInit): An unspecified XBSA error has occurred: 96 2002-09-19 13:40:58 23326 21832 Due to the previous error, logical restore will not be attempted. 2002-09-19 13:40:58 23326 21832 /s026/informix/bin/onbar_d: process exit 96 (0x60) 2002-09-19 13:42:00 21840 23334 /s026/informix/bin/onbar_d -r -l 2002-09-19 13:42:00 21840 23334 ERROR: Unable to start logical restore before physical restore. 2002-09-19 13:42:00 21840 23334 /s026/informix/bin/onbar_d: process exit 151 (0x97) actlog = tsm: LITS-ADSM-SERVERq act begint=13:20 Date/Time Message -- 19/09/02 13:26:20ANR0407I Session 26 started for administrator ADMIN (AIX) (Tcp/Ip 25.109.195.161(33184)). 19/09/02 13:26:23ANR2017I Administrator ADMIN issued command: QUERY ACTLOG 19/09/02 13:27:23ANR0405I Session 26 ended for administrator ADMIN (AIX). 19/09/02 13:28:42ANR0406I Session 27 started for node S00026 (AIX) (Tcp/Ip 25.109.195.161(33185)). 19/09/02 13:28:55ANR0403I Session 27 ended for node S00026 (AIX). 19/09/02 13:41:36ANR0407I Session 28 started for administrator ADMIN (AIX) (Tcp/Ip 25.109.195.161(33191)). 19/09/02 13:41:36ANR2017I Administrator ADMIN issued command: ISSUE MESSAGE e Restore failed on rcadb. Please check logs 19/09/02 13:41:36ANR1498E Restore failed on rcadb. Please check logs 19/09/02 13:41:36ANR0405I Session 28 ended for administrator ADMIN (AIX). /usr/tivoli/tsm/client/informix/tdpipswd yields the following message: * * Tivoli Data Protection for Informix * * Password file initialization/update program * * ROOT privilege needed to update value on UNIX * * Enter your current password: Enter your new password: For verification, enter your new password again: Server signon failed: ANS1017E (RC-50) Session rejected: TCP/IP connection failure Any help would be appreciated. Debbie -- Cai Lam FVT - Tivoli Data Protection products Email: [EMAIL PROTECTED]; Phone: (408)256-2581
Re: starting TSM without it doing anything
Why not add DISABLESCHED YES to the DSMSERV.OPT file, log in and DISABLE SESSIONS to keep others out. Now this won't stop any migrations or reclamations from kicking off if the thresholds have been exceeded, but no schedules will take off. One of the steps in our disaster recovery instructions is to add the DISABLESCHEDS YES to the server options file before starting it. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Fred Johanson Sent: Tuesday, September 24, 2002 11:10 AM To: [EMAIL PROTECTED] Subject: Re: starting TSM without it doing anything You can set TCPPORT to 1600, or something, in the options file and use the WebAdmin to see what you want. I don't know if you can use SETOPT to reopen 1500 or not. At 10:56 AM 9/24/2002 -0400, you wrote: Is there a way to start TSM server without it doing anything? Kinda like a single-user mode? Sometimes, I like to run an audit after rebooting TSM and the tape library, but as soon as I start TSM, it begins to do various things like space reclamation etc. I *could* remember to disable sessions and increase the reclamation threshold before shutting it down, but sometimes I don't remember to do these things. Currently running TSM server 4.1.3 on AIX 4.3.3 ML 10. johnn
Re: Anyone tried 5.1.1.6?
Gretchen, I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday. All I can say is 'not pretty'. This is due to the SYSTEM OBJECT problem. Can you elaborate on the system object problem that you were dealing with? I've searched for an APAR that fits the description that you've given, but I have not been able to locate a reference to the APAR. I've looked in the 5.1.1.6 readme and searched through Tivoli's/IBM's search mechanisms. Thanks, Ted
HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
Up until a few days ago, we were backing up only small amounts of data for several nodes each night. Then an emergency request came in to start nightly incremental backups using the TSM Domino TDP for a Domino mail server that does not do transaction logging. (Note: The Domino support staff estimates implementation of transaction logging 3-4 weeks from now I wish it were sooner!) All of a sudden we went from a total backup of no more than 11GB per night to more than double that, with almost 20-23 GB per night coming from that one new node alone. This node's data is sent over a 100 MB ethernet connection. Even with client compression turned on, the best throughput rate we've seen is 566 Kb/sec., and that was when the backup was run on a Sunday when there is very little activity on all systems involved (client, server, network). When other backups are running during the night, the best we've seen is 368.72 Kb/sec. This results in the backup for this one node taking at least 17 hours to run to completion. Before the addition of this new node, I had all my processes (expiration, reclamation, migration, backup storage pool) running separately and not at the same time as client backup sessions. Now we no longer have enough time in the day to do this. I need to change the way my processes run, but I have several questions I need answered before I do this. If anyone can help me with the following questions, I would appreciate it: 1) What are the implications of the process generated when I issue backup stg backuppool offsite-pool running at the same time that a node is currently in session backing up to the backuppool storage pool? 1a) Will the backup stg process finish during the node's session? 2) Do we need to be in a state where there are no active processes and/or backup/restore sessions running while the TSM database backup is running? 2a) What kind of state would the TSM database be in if it was restored from a backup that had other processes or backup/restore sessions running at the time it was taken? 3) Is there any problem with running an expire inventory while any of the following are running?: - a node backup session - a node restore session - migration - reclamation 4) Is there a problem running migration and reclamation at the same time if they both access the same pool? I would have thought the only problem might be a wait for a tape while one process is using it, but that this probably would only occur occasionally. I have a reclamation process running that caused a message Removable volume 30050 is required for space reclamation. A migration process is running which requires writing to the same tape pool that 300050 is in, however 300050 displays as last being written to the day before. 5) I have very little knowledge of networking. Could someone comment on the throughput values we are seeing? Our max of 566 Kb/sec is no where near the 100 Mb/sec I have been told our ethernet connection is.
Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
Check your network settings on your server. Some network cards do not Auto-negotiate with certain switches. If everything is set to Auto-negotiate, set the network card and the port of the switch it is plugged into to 100 MB/s Full duplex. I was getting the same throughput on some of my TSM servers until I did that and then I started to get 8-9 Megabyte/sec performance. Your performance may vary. Thank You, Matt Martinez Workgroup Support Analyst IDEXX Laboratories, Inc 207-856-0656 [EMAIL PROTECTED] -Original Message- From: Barbara Andrews [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 3:06 PM To: [EMAIL PROTECTED] Subject:HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ? Up until a few days ago, we were backing up only small amounts of data for several nodes each night. Then an emergency request came in to start nightly incremental backups using the TSM Domino TDP for a Domino mail server that does not do transaction logging. (Note: The Domino support staff estimates implementation of transaction logging 3-4 weeks from now I wish it were sooner!) All of a sudden we went from a total backup of no more than 11GB per night to more than double that, with almost 20-23 GB per night coming from that one new node alone. This node's data is sent over a 100 MB ethernet connection. Even with client compression turned on, the best throughput rate we've seen is 566 Kb/sec., and that was when the backup was run on a Sunday when there is very little activity on all systems involved (client, server, network). When other backups are running during the night, the best we've seen is 368.72 Kb/sec. This results in the backup for this one node taking at least 17 hours to run to completion. Before the addition of this new node, I had all my processes (expiration, reclamation, migration, backup storage pool) running separately and not at the same time as client backup sessions. Now we no longer have enough time in the day to do this. I need to change the way my processes run, but I have several questions I need answered before I do this. If anyone can help me with the following questions, I would appreciate it: 1) What are the implications of the process generated when I issue backup stg backuppool offsite-pool running at the same time that a node is currently in session backing up to the backuppool storage pool? 1a) Will the backup stg process finish during the node's session? 2) Do we need to be in a state where there are no active processes and/or backup/restore sessions running while the TSM database backup is running? 2a) What kind of state would the TSM database be in if it was restored from a backup that had other processes or backup/restore sessions running at the time it was taken? 3) Is there any problem with running an expire inventory while any of the following are running?: - a node backup session - a node restore session - migration - reclamation 4) Is there a problem running migration and reclamation at the same time if they both access the same pool? I would have thought the only problem might be a wait for a tape while one process is using it, but that this probably would only occur occasionally. I have a reclamation process running that caused a message Removable volume 30050 is required for space reclamation. A migration process is running which requires writing to the same tape pool that 300050 is in, however 300050 displays as last being written to the day before. 5) I have very little knowledge of networking. Could someone comment on the throughput values we are seeing? Our max of 566 Kb/sec is no where near the 100 Mb/sec I have been told our ethernet connection is.
Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Barbara Andrews Even with client compression turned on, the best throughput rate we've seen is 566 Kb/sec., and that was when the backup was run on a Sunday when there is very little activity on all systems involved (client, server, network). When other backups are running during the night, the best we've seen is 368.72 Kb/sec. This results in the backup for this one node taking at least 17 hours to run to completion. I've often said that TSM is one of the finest problem finders in the tech industry today. It will show you bus problems, adapter bottlenecks, network missettings, and SAN misconfigurations faster than anything else in the market. Your network problems doubtless existed prior to the change in your backup schema; you just didn't see it because you didn't stress the network with it. I would say that you need to check the speed and duplex settings for *all* network hardware in the line of the problem--the Notes server's NIC, the switch port that it's plugged into, the switch port that the TSM server is plugged into, and the NIC for the TSM server. They should (in most cases) all be set to 100 full duplex for a 100mb Ethernet network. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
I've already seen one reply to check the NIC settings - those will get you every time. An easy check that can really pay off. Another thing to check is to see if the client is CPU or I/O bound. If your CPU utilization is at 100% (or near it), client side compression can slow you down. If the DASD is I/O bound, you'll need to address that area to improve performance. To answer the questions: 1. The source storagepool is examined at the beginning of the backup stgpool process, so any data that comes in after the process starts is not going to be copied. That is as dangerous as it sounds - you may not have all the data you need offsite. 1a. Yes, it will finish, since it doesn't know about the data the client has been sending. 2. Sort of the same as question 1 above, but the database backup will pick up changes as it goes (after the end of the backup process). However, if you have a process running that doesn't complete/commit it's changes, they may not get backed up. It's a crapshoot, and can be dangerous, so I'd recommend you avoid it if you can. 2a. The backup will have the image as it was when the backup was taken. If there is data being copied from tape to tape, and the old, now scratch, tape is reused between the TSM database backup and the restore, the data can be overwritten. See reuse delay for ways to close this exposure. 3. Expire Inventory can run parallel to anything else. With reclamation/migration, you may expire a file you just spent time reclaiming, so if you can avoid it, you should, but then there are only 24 hours in the day... 4. No, you can run migration and reclamation at the same time, and you're right - you may fight for tapes/drives. With the message you are getting - does the tape get mounted? I think that message just means that TSM wants the tape - it's just an FYI. 5. Yes, that is VERY slow. Your actual performance may vary depending on a lot of factors, but that is definitely slow. Nick Cassimatis [EMAIL PROTECTED] Today is the tomorrow of yesterday.
Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
Around here, we call TSM backups our Computer/Server/Node/Client Stress Tester. I totally agree Mark, we currently used TSM backup stress tester to test our Gigabyte interface and it did show pros and cons of the setup of the GB network. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD |-+ | | Mark Stapleton | | | stapleto@BERBEE.| | | COM | | | Sent by: ADSM: | | | Dist Stor| | | Manager | | | [EMAIL PROTECTED]| | | .EDU| | || | || | | 09/24/2002 03:45 | | | PM | | | Please respond to| | | ADSM: Dist Stor | | | Manager | | || |-+ --| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup | |sessions ? | --| From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Barbara Andrews Even with client compression turned on, the best throughput rate we've seen is 566 Kb/sec., and that was when the backup was run on a Sunday when there is very little activity on all systems involved (client, server, network). When other backups are running during the night, the best we've seen is 368.72 Kb/sec. This results in the backup for this one node taking at least 17 hours to run to completion. I've often said that TSM is one of the finest problem finders in the tech industry today. It will show you bus problems, adapter bottlenecks, network missettings, and SAN misconfigurations faster than anything else in the market. Your network problems doubtless existed prior to the change in your backup schema; you just didn't see it because you didn't stress the network with it. I would say that you need to check the speed and duplex settings for *all* network hardware in the line of the problem--the Notes server's NIC, the switch port that it's plugged into, the switch port that the TSM server is plugged into, and the NIC for the TSM server. They should (in most cases) all be set to 100 full duplex for a 100mb Ethernet network. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
TDP for Exchange 402 Errors: Second Try
We are experiencing the backup failed 402 error condition nightly on at least 1 of our Exchange Servers. We are running: The latest TDP for Exchange Exchange 5.5 SP4 NT 4 60a TSM Server AIX 4.3.3 ML10 TSM 4.2.2.12 Gigabit The NT hardware is Gigabit ethernet, ESS Disk with the latest SDD driver, Magstar Tape. LAN Backup. The 402 error condition is related to file handle or other memory resource shortages in Exchange or NT. Essentially, until we reboot the box or cycle the Exchange service the problem is around and no backups will run. The funny piece is it can back up the directory but not the information stores. Level 2 has made us aware of the potential Microsoft fixes but we have them all in place. We are out of ideas and desperately seeking any suggestions. We have theorized that the SDD driver has a leak or the ESS disk is so fast it overloads the internal buffer and file handles in Exchange. Has anyone else seen a similar situation after making all the suggested changes? If so, have you fixed it and how? Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180
Re: HELP!... What processes can/can't run simultaneously andwhat throttles throughput on backup sessions ?
Another simple test to do to prove to Network guys and others that TSM is not the problem is to do some FTP's from some of the clients to the TSM server. Performance here is strictly network/CPU/disk not TSM. Only exception is if you have heavy backups or restores going at the time. David Longo [EMAIL PROTECTED] 09/24/02 03:20PM Check your network settings on your server. Some network cards do not Auto-negotiate with certain switches. If everything is set to Auto-negotiate, set the network card and the port of the switch it is plugged into to 100 MB/s Full duplex. I was getting the same throughput on some of my TSM servers until I did that and then I started to get 8-9 Megabyte/sec performance. Your performance may vary. Thank You, Matt Martinez Workgroup Support Analyst IDEXX Laboratories, Inc 207-856-0656 [EMAIL PROTECTED] -Original Message- From: Barbara Andrews [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 3:06 PM To: [EMAIL PROTECTED] Subject:HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ? Up until a few days ago, we were backing up only small amounts of data for several nodes each night. Then an emergency request came in to start nightly incremental backups using the TSM Domino TDP for a Domino mail server that does not do transaction logging. (Note: The Domino support staff estimates implementation of transaction logging 3-4 weeks from now I wish it were sooner!) All of a sudden we went from a total backup of no more than 11GB per night to more than double that, with almost 20-23 GB per night coming from that one new node alone. This node's data is sent over a 100 MB ethernet connection. Even with client compression turned on, the best throughput rate we've seen is 566 Kb/sec., and that was when the backup was run on a Sunday when there is very little activity on all systems involved (client, server, network). When other backups are running during the night, the best we've seen is 368.72 Kb/sec. This results in the backup for this one node taking at least 17 hours to run to completion. Before the addition of this new node, I had all my processes (expiration, reclamation, migration, backup storage pool) running separately and not at the same time as client backup sessions. Now we no longer have enough time in the day to do this. I need to change the way my processes run, but I have several questions I need answered before I do this. If anyone can help me with the following questions, I would appreciate it: 1) What are the implications of the process generated when I issue backup stg backuppool offsite-pool running at the same time that a node is currently in session backing up to the backuppool storage pool? 1a) Will the backup stg process finish during the node's session? 2) Do we need to be in a state where there are no active processes and/or backup/restore sessions running while the TSM database backup is running? 2a) What kind of state would the TSM database be in if it was restored from a backup that had other processes or backup/restore sessions running at the time it was taken? 3) Is there any problem with running an expire inventory while any of the following are running?: - a node backup session - a node restore session - migration - reclamation 4) Is there a problem running migration and reclamation at the same time if they both access the same pool? I would have thought the only problem might be a wait for a tape while one process is using it, but that this probably would only occur occasionally. I have a reclamation process running that caused a message Removable volume 30050 is required for space reclamation. A migration process is running which requires writing to the same tape pool that 300050 is in, however 300050 displays as last being written to the day before. 5) I have very little knowledge of networking. Could someone comment on the throughput values we are seeing? Our max of 566 Kb/sec is no where near the 100 Mb/sec I have been told our ethernet connection is. MMS health-first.org made the following annotations on 09/24/2002 04:27:35 PM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except
Re: Anyone tried 5.1.1.6?
Gretchen, I've looked at our servers and have over 1.2 terabyte in system object data, and 11,700,000 files. This from 1400 nodes. Do you mean to say by delete them you actually go out and del fi * SYSTEM OBJECT? I looked at one object and there were 14 inactive versions...we keep 4 and run expiration weekly. I don't think many (if any) of our clients restore from these data, but do you mean literally that you delete them? Thanks. Regards. John At 10:55 AM 9/24/02 -0400, Gretchen L. Thiele wrote: Hi Fred, I've seen the SYSTEM OBJECT problem, it's especially pretty when you can't run expiration for six weeks. It's a pain, I've got a routine set up to find the oversized SYSTEM OBJECT filespaces and then delete them, but I have two servers with thousands of WinXP/2K nodes that bloated the databases up to 250GB. I'm just trying to stay above water on these two and then just move the nodes to a v5 server for a big 'do over'. Sigh. Bottom line, get your SYSTEM OBJECT filesystems in check now! But I haven't had a scheduled session accepted since I hit MAXSESS at 3:04 yesterday morning. Are you seeing this in 5.1.1.6? Not sure what problem you are seeing. If all of your sessions are in use, i.e., you've hit MAXSESS, I wouldn't expect any scheduled sessions to get in. Or am I missing something? Gretchen Thiele Princeton University
Re: Anyone tried 5.1.1.6?
Hi John, I've looked at our servers and have over 1.2 terabyte in system object data, and 11,700,000 files. This from 1400 nodes. Do you mean to say by delete them you actually go out and del fi * SYSTEM OBJECT? Yup, delete them, they'll back up again. We had over 15TB in these files and I'm down to 11TB now. If you delete them now (presumably without error), you'll save yourself a lot of CLEANUP BACKUPGROUPS processing later. Either way, it has to happen. Oh, and you might have to defrag your database... I've done this on a small server (4.5% utilized on 166 GB allocated) and it took all day to get to v5.1.1.6. I probably would have fared better if I had deleted all of the SYSTEM OBJECT files, but I only nuked the ones above 1 GB. I didn't defrag this one because the level of fragmentation was only about one percent. Again, I'm writing the whole thing up for the list... It's a risk, because our bare metal restore procedures depend on a current SYSTEM OBJECT backup, but I can't let the database swell to infinite proportions - the performance is horrible. Luckily, the problem is fixed in v5.1.1.6. Gretchen Thiele Princeton University
Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
Another thing to consider is that each time an email comes in to the Domino server, some user file is getting changed. If a file is changed while TSM is backing it up, it starts over (depending on your settings). This bit us when we started backing up our Domino server. Since you are using the TDP (which we weren't at first) this might not be an issue, but it's worth looking into. Nancy Reeves Technical Support, Wichita State University [EMAIL PROTECTED] 316-978-3860
Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ?
Mark; run the command netstat -v on the backup interface and take a look at - Drop packets - Recieve errors - Transmit errors - CRC errors - DMA overruns - The recieve and transmit queue size. - Any collisions (single or otherwise) Like others said, Hard code all the devices involved to 100 MB (no auto_negotiate). I believe this change will require a reboot of the system. - Try and get used to the different switches of the netstat command - Also, run a traceroute (tracert in the case of NT) from both sides and see if you are using the proper route. If not you will need to change routing table. Hope this helps. Regards; Hussein M. Abdirahman AIX administrator IrwinToy LTD. Toronto - Canada -Original Message- From: Mark Stapleton [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 24, 2002 3:45 PM To: [EMAIL PROTECTED] Subject: Re: HELP!... What processes can/can't run simultaneously and what throttles throughput on backup sessions ? From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Barbara Andrews Even with client compression turned on, the best throughput rate we've seen is 566 Kb/sec., and that was when the backup was run on a Sunday when there is very little activity on all systems involved (client, server, network). When other backups are running during the night, the best we've seen is 368.72 Kb/sec. This results in the backup for this one node taking at least 17 hours to run to completion. I've often said that TSM is one of the finest problem finders in the tech industry today. It will show you bus problems, adapter bottlenecks, network missettings, and SAN misconfigurations faster than anything else in the market. Your network problems doubtless existed prior to the change in your backup schema; you just didn't see it because you didn't stress the network with it. I would say that you need to check the speed and duplex settings for *all* network hardware in the line of the problem--the Notes server's NIC, the switch port that it's plugged into, the switch port that the TSM server is plugged into, and the NIC for the TSM server. They should (in most cases) all be set to 100 full duplex for a 100mb Ethernet network. -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: Anyone tried 5.1.1.6?
SNIP It's a risk, because our bare metal restore procedures depend on a current SYSTEM OBJECT backup, but I can't let the database swell to infinite proportions - the performance is horrible. Luckily, the problem is fixed in v5.1.1.6. Gretchen Thiele Princeton University You can always rename the filespace and allow a backup or two to complete before deleting the old filespace.(At least on the NT platform)
TSM contractor in Houston needed
Looking for contractor to work on TSM in NT environment in Houston area, time and materials, maybe 100 hours per year. Regards, Orin Orin Rehorst Port of Houston Authority (Largest U.S. port in foreign tonnage) e-mail: [EMAIL PROTECTED] Phone: (713)670-2443 Fax: (713)670-2457 TOPAS web site: www.homestead.com/topas/topas.html
Re: Anyone tried v5.1.1.6?
You can always rename the filespace and allow a backup or two to complete before deleting the old filespace.(At least on the NT platform) This is an excellent suggestion! Also, you don't want to do so many at a time that your database becomes 'unbalanced' (a level 2 caveat). Again, identify that you have the problem, then plan your course of action. Gretchen Thiele Princeton University
Re: Anyone tried 5.1.1.6?
Hi Fred, I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday. All I can say is 'not pretty'. This is due to the SYSTEM OBJECT problem. If you don't know what this is, you will soon if you have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6 servers. Does this problem only occur with WinXP and Win2K clients? What about Win9x and WinNT? Either I don't have any Win2K/WinXP clients, or TSM does not set the platform to Win2k/WinXP? Are these OS's also known by some version number of NT? The basic problem is that TSM isn't expiring anything in the SYSTEM OBJECTs filespace. Some of our clients had over 20GB in these filespaces! Needless to say, the database blew up while trying to find out what was going on. To see if you have this problem, you can type in show version nodename SYSTEM OBJECT namet=uni file (only use namet=uni if the filespace is unicode). Then check through the file and look for the number of occurrences of a file, say ROUTE.EXE. A normal SYSTEM OBJECT filespace, with four versions, shouldn't be over a gig. The good news is that v5.1.1.6 does NOT have the SYSTEM OBJECT problem and the new server is doing very well. I am writing up the post mortem on the conversion and will post to the list later this week (at the request of Tivoli level 2). Gretchen Thiele Princeton University Steve Roder, University at Buffalo HOD Service Coordinator VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) TSM/ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564)
Re: Anyone tried 5.1.1.6?
I found that the SYSTEM OBJECT which were not unicode were never deleted unless I did it manually. A QUERY OCC * SYSTEM OBJECT (without the NAMETYPE=UNICODE option) will let you know if you have that problem. Also, did you run the command CLEANUP BACKUPGROUPS? For me, on 5.1.1.4 it ran but never cleaned everything up and it wouldn't run on 5.1.1.6. I finally had to do an AUDITDB FIX=YES. On Tue, 24 Sep 2002, Gretchen L. Thiele wrote: Hi Fred, I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday. All I can say is 'not pretty'. This is due to the SYSTEM OBJECT problem. If you don't know what this is, you will soon if you have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6 servers. The basic problem is that TSM isn't expiring anything in the SYSTEM OBJECTs filespace. Some of our clients had over 20GB in these filespaces! Needless to say, the database blew up while trying to find out what was going on. To see if you have this problem, you can type in show version nodename SYSTEM OBJECT namet=uni file (only use namet=uni if the filespace is unicode). Then check through the file and look for the number of occurrences of a file, say ROUTE.EXE. A normal SYSTEM OBJECT filespace, with four versions, shouldn't be over a gig. The good news is that v5.1.1.6 does NOT have the SYSTEM OBJECT problem and the new server is doing very well. I am writing up the post mortem on the conversion and will post to the list later this week (at the request of Tivoli level 2). Gretchen Thiele Princeton University
Re: Anyone tried 5.1.1.6?
W2K is known as NT 5.0 to TSM. Do a q node blah f=d for your client node on TSM server and see what it comes up as. Haven't had any XP clients yet to see what it is known as. David Longo [EMAIL PROTECTED] 09/24/02 08:21PM Hi Fred, I just took a v4.2.2.12 AIX server to v5.1.1.6 last Saturday. All I can say is 'not pretty'. This is due to the SYSTEM OBJECT problem. If you don't know what this is, you will soon if you have WinXP and Win2K clients backing up to v4 and pre v5.1.1.6 servers. Does this problem only occur with WinXP and Win2K clients? What about Win9x and WinNT? Either I don't have any Win2K/WinXP clients, or TSM does not set the platform to Win2k/WinXP? Are these OS's also known by some version number of NT? The basic problem is that TSM isn't expiring anything in the SYSTEM OBJECTs filespace. Some of our clients had over 20GB in these filespaces! Needless to say, the database blew up while trying to find out what was going on. To see if you have this problem, you can type in show version nodename SYSTEM OBJECT namet=uni file (only use namet=uni if the filespace is unicode). Then check through the file and look for the number of occurrences of a file, say ROUTE.EXE. A normal SYSTEM OBJECT filespace, with four versions, shouldn't be over a gig. The good news is that v5.1.1.6 does NOT have the SYSTEM OBJECT problem and the new server is doing very well. I am writing up the post mortem on the conversion and will post to the list later this week (at the request of Tivoli level 2). Gretchen Thiele Princeton University Steve Roder, University at Buffalo HOD Service Coordinator VM Systems Programmer UNIX Systems Administrator (Solaris and AIX) TSM/ADSM Administrator ([EMAIL PROTECTED] | (716)645-3564) MMS health-first.org made the following annotations on 09/24/2002 09:10:22 PM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: Anyone tried 5.1.1.6?
I found that the SYSTEM OBJECT which were not unicode were never deleted unless I did it manually. A QUERY OCC * SYSTEM OBJECT (without the NAMETYPE=UNICODE option) will let you know if you have that problem. Also, did you run the command CLEANUP BACKUPGROUPS? For me, on 5.1.1.4 it ran but never cleaned everything up and it wouldn't run on 5.1.1.6. I finally had to do an AUDITDB FIX=YES. Actually, this problem occurs with both unicode and nonunicode SYSTEM OBJECT filesystems. If you delete the nonunicode filesystem it will rebackup as unicode. The new unicode SYSTEM OBJECT filesystem will continue accumulate extra versions as well. I could run CLEANUP BACKUPGROUPS with an earlier v5 version, but it didn't work (I ran it, but then ran it again and it found more errors). The CLEANUP didn't work (got the loop problem) under v5.1.1.6, but then the AUDITDB didn't work! This is what I'm writing up... Gretchen Thiele Princeton University
Archive or backup question
We have a cache directory on an AIX server that has about 8 million objects. We want to archive this maybe twice a week for DR purposes and only keep one copy. The trouble being it blows out our database with all the objects and the schedule log blows out the files space where it is saved to. Does anyone know of anyway to backup/archive this amount of objects and not blow out both the DB and the filespace? Any help or comments would be appreciated. Antony Ryan Support Specialist KAZ Computer Services 118 Bennett Street East Perth WA 6004 Phone: 1300 657 627 +61 8 6212 0100 Mobile: 0438 074 895 Fax: +61 8 6212 0101 A division of KAZ Group Limited - visit our web site at http://www.kaz.com.au The above message has been scanned and meets the Insurance Commission of Western Australia's Email security policy requirements for outbound transmission. This email (facsimile) and any attachments may be confidential and privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this email (facsimile) is strictly prohibited. If you have received this email (facsimile) in error please contact the Insurance Commission. Web: www.icwa.wa.gov.au Phone: +61 08 9264
Re: Archive or backup question
Hi Anthony, I'm assuming that this filesystem needs to be online all the time. Are you mirrored, and can you do an AIX Split mirror backup? If so, split the mirror, change the lv type to something other than JFS and do an image backup. I've not tried this, but it should work. Regards Steve Harris AIX and TSM Admin Queensland Health, Brisbane Australia [EMAIL PROTECTED] 25/09/2002 11:57:02 We have a cache directory on an AIX server that has about 8 million objects. We want to archive this maybe twice a week for DR purposes and only keep one copy. The trouble being it blows out our database with all the objects and the schedule log blows out the files space where it is saved to. Does anyone know of anyway to backup/archive this amount of objects and not blow out both the DB and the filespace? Any help or comments would be appreciated. Antony Ryan Support Specialist KAZ Computer Services 118 Bennett Street East Perth WA 6004 Phone: 1300 657 627 +61 8 6212 0100 Mobile: 0438 074 895 Fax: +61 8 6212 0101 A division of KAZ Group Limited - visit our web site at http://www.kaz.com.au The above message has been scanned and meets the Insurance Commission of Western Australia's Email security policy requirements for outbound transmission. This email (facsimile) and any attachments may be confidential and privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this email (facsimile) is strictly prohibited. If you have received this email (facsimile) in error please contact the Insurance Commission. Web: www.icwa.wa.gov.au Phone: +61 08 9264 ** This e-mail, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost if you receive it and you are not the intended recipient(s), or if it is transmitted/ received in error. Any unauthorised use, alteration, disclosure, distribution or review of this e-mail is prohibited. It may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this e-mail in error, you are asked to immediately notify the sender by telephone or by return e-mail. You should also delete this e-mail message and destroy any hard copies produced. **
Re: Reading data from tape
Well, I'll take a shot at this. Haven't worked with 3590 tape in a while but your questions are applicable to any tape. 1. If these tapes were removed then your onsite and/or offsite reclamations should start failing soon as they try to use a tape that isn't there. 2. If your know which tape volser's were removed, then do a q vol blah f=d on them and see what stgpool they were in and when last accessed. Maybe if actlog retention is long enough, you can do a q actlog and search for volser and see when removed and by what command. 3. Simplest but could be looog output - do a q content on the volumes. This will show you all the nodes and files that are on this tape. You can use some SQL selects to get a more refined list if needed. 4. Even though data may be expired it is still on the tape, but not easily accessible unless you have a DB backup tape made at the time the tapes were removed. 5. I don't know the fine details on how data is written on tape but believe there is little or no indexing on the tape, it's all in the the DB. (Now some tape tape technologies have some kind of information in the header - like the VCR on 3570 tapes). 6. As a summary, it depends on how important the data is that you need back. And if there is classified data on these tapes, how will they get that back without you? David Longo [EMAIL PROTECTED] 09/23/02 06:08PM I hope someone has a real good knowledge of how TSM data is written to/read from tape. I'm in a predicament that I may never be able to get tapes back to read any node data off of them unless I can satisfactorily answer questions. Unfortunately I don't know the questions yet so I don't even know what to ask here. Perhaps someone who is knowledgeable about 3590 tape technology or someone from Tivoli monitoring the list can help with this. I hate to have to call Tivoli since so far I haven't got much in the way of answers on the other questions I've been asking on classified material on tape. What kind of questions would you expect to answer if a tape was removed from the library with mixed node data on it and it was needed to restore some other node's data. Keep in mind that the tape was removed because it originally had classified material stored on it. It may or may not still have the data depending on expiration. I already know how to explain the ins and outs of expiration/reclamation but we all know the DATA is really still there. My guess is I'm never really going to be able to get these tapes back and whatever data was on them is probably gone forever but I need to at least be able to answer some questions like are they indexed or how the data is stored, how it's read back etc. Thanks for the help, Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail:mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154 MMS health-first.org made the following annotations on 09/24/2002 11:14:40 PM -- This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ==
Re: TSM and multiprocessing
Hi Sascha, This holds true for all the OS's except MVS-OS/390-z/os - on the mainframe you need to specify multithreading yes/no to enable multi CP usage. If set to no TSM will only use one CP. Cheers Christo -- The multiprocessing capabilities in TSM are built in and do not need to be configured. IBM recommends that a TSM server be installed on a system with 4 CPUs at most. -- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark Tivoli Certified Consultant - ADSM/TSM eServer Systems Expert -pSeries HACMP AIX, HACMP, Storage, TSM Consultant Cell (831) 595-3962 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Sascha Braeuning Sent: Tuesday, September 24, 2002 7:41 AM To: [EMAIL PROTECTED] Subject: TSM and multiprocessing Hello TSMers, is TSM Server 4.2 able to do multiprocessing? How can I configure it? MfG Sascha Bräuning Sparkassen Informatik, Fellbach OrgEinheit: 6322 Wilhelm-Pfitzer Str. 1 70736 Fellbach Telefon: (0711) 5722-2144 Telefax: (0711) 5722-1634 Mailadr.: [EMAIL PROTECTED] __ The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed and others authorised to receive it. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful. Absa is liable neither for the proper, complete transmission of the information contained in this communication, nor for any delay in its receipt, nor for the assurance that it is virus-free.
Help,cartridge remove question
Hi all, I have a 3494 library,my adsm version is 3.1.6,now my library slot will be full,so I want to move some cartridges out of the library.The operations I will have as follow: backup db devclass=tapeclass move media * stgpool=backup move media * stgpool=archive Is this all?Or I need any more opertions?
