Re: Microcode levels and atape/atldd upgrade
They will say not, but the history on this list at www.adsm.org will say otherwise. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: Diana Noble [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 8:20 AM To: [EMAIL PROTECTED] Subject: Microcode levels and atape/atldd upgrade Before upgrading to TSM 4.2.2 from 4.1.2, I would like to upgrade our atape and atldd drivers to the latest level on our AIX 4.3.3 system. Does anyone know if I need to have the microcode levels of our 3590's upgraded when I do the atape upgrade? Thanks, Diana
Re: TSM server problem
I have seen similar things. You have to put on 4.2.2 to correct this problem. However, a recycle of the dsmserv will fix the problem. The issue manifests itself in several ways. I have only seen the problem once. I am still on 4.2.1.15 which partially fixes the problem. The problem is caused by a bunch of idle drives dismounting at the same time. Apparently, there were some threading of updates to instorage control blocks that get hosed. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: Henk ten Have [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 11:17 AM To: [EMAIL PROTECTED] Subject: TSM server problem I couldn't find an APAR that describes what we have been seeing on our 4.2.1.11 (AIX 4.3.3) server during the last few weeks so I was wondering if we have discovered new bug. First we got this message in the activity log: 06/09/02 10:39:38 ANR1229W Volume 000591 cannot be backed up - volume is offline or access mode is "unavailable" or "destroyed". We did a 'q vol f=d'. The access mode of the volume was 'Available' so we dismissed it as a freak incident until the message repeated itself the next day. This time we opened the (3494) library and verified that the volume was in the correct cell. We tried a 'restore volume' followed by a 'delete volume'. The delete failed: ANR2405E DELETE VOLUME: Volume 000591 is currently in use by clients and/or data management operations. ANS8001I Return code 14. At that time there were no processes or sessions that used that particular volume. Also we had four other volumes that displayed the same behaviour. We halted the server and restarted it again which solved the problem. The volumes were no longer 'in use'. Today we noticed two other volumes that seem to have the same problem so I'm beginning to suspect that I've found a bug in the server. All these volumes have one thing in common: When I seacrh the activity log for their mounts and dismounts I can't find a dismount message after their last mount (before they become 'unavailable'). It is as if the volumes are unmounted by the library but TSM isn't being notified of this. Anyone seen this before? Cheers, Henk.
Re: NSM Upgrade Experience
And, if that isn't SAD enough, at 16:58 today, the AIX tar file for 4.2.2.5 got updated! (Who knows what they just changed, if anything!?!) -Original Message- From: Don France [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:53 PM To: 'ADSM: Dist Stor Manager' Cc: '[EMAIL PROTECTED]' Subject: RE: NSM Upgrade Experience Ooops... we just advised a customer to install 4.2.2.5 --- for SumTab fix, didn't know there is a (yet) new bug for expiration (introduced by 4.2.2.4???) Are you sure that 4.2.2.6 is needed for EXPIRE INVENTORY to work, again ?!? (There is nothing about expiration in the .4 or .5 APAR abstracts... Were you/they referring to the "conflict lock" issue? Geesh, .5 just came out...sigh:() Don France Technical Architect -- Tivoli Certified Consultant San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jolliff, Dale Sent: Thursday, June 20, 2002 2:57 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience I got my 5100-02 patch when someone at 800-IBM-SERV was playing phone tag between myself and the CE when he was out investigating our PMH on duplicate IP addresses. I was told by level 2 this afternoon to avoid expiration on 4.2.2.4 until 4.2.2.6 is available Real Soon Now. -Original Message- From: Talafous, John G. [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 2:25 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience As I understand, support for TSM 4.1 expires June 30, 2002. So if you want to be supported, you have no choice but to upgrade to TSM 4.2. We too have been trying to implement EC017 on our NSM, and have had two failed attempts at the upgrade. The upgrade to AIX 5 and TSM 4.2.1.9 requires an AIX load from 4mm tape. We got a bad 4mm tape. You know, WORN technology (Write Once, Read Never). About 10% of the way into the upgrade to AIX 5 we couldn't read the tape. Tried and tried and tried. But it was bad. We had to recover from the MKSYSB we did that morning. That's why we take MKSYSB's. The second time we tried the EC script failed because \dbaa1dk31\db has on HDISK2. Huh? How did that happen. It turned out that when the recover was done from the MKSYSB all the HDISKS were renumbered by AIX. It took us a couple days with Level II support to get that straightened around. Took Level II about 4 hours dialed in running AIX commands to re-do things and put \dbaa1dk31\db back on HDISK31. We have scheduled our third attempt at EC017 for Sunday, June 30. I've also been told by Level II that anyone preparing to install EC017 should open a PMR prior to the upgrade so support can track the activity. I was also told that not very many NSM sites have done this upgrade, so many will be out of support. And what's this about OS patch 5100-02. Where do I get it and where do I find these kinds of patches? Is there some piece of documentation I've missed or did I just not catch something? Good luck to all!!! John G. Talafous Information Systems Technical Principal Global Software Support - Data Management telephone: (330)-471-3390 e-mail: [EMAIL PROTECTED] http://www.ctnvm.inside.tkr/~talafous/ http://www.cis.corp.inside.tkr/networkstorage/
Re: upgrade from v4.2.2.5 to v5.1.0.0 failed (AIX)
>Did you apply the latest patches to 5.1.0.0? (5.1.0.2, I believe.) Yes, when the v5.1 CD didn't come up, I applied v5.1.1.0 (in the maintenance section of the ftp site). Same results. It's acting like some of the database wasn't converted with the upgrade. I then tried to do ./dsmserv upgradedb, no change. When I put v4.2.2.5 back on, I tried starting it up on the chance that the database hadn't been converted. No such luck. So, after 6.5 hours, I have my 100GB server back! Gretchen Thiele Princeton University
Re: solved my case... RE: How to flush DRM references, anybody know ?
Thanx for sharing, Dwight!!! Don France Technical Architect -- Tivoli Certified Consultant San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Cook, Dwight E Sent: Thursday, June 20, 2002 1:59 PM To: [EMAIL PROTECTED] Subject: solved my case... RE: How to flush DRM references, anybody know ? Well, just got off the phone with IBM. they had me doing all sorts of queries looking for DR plans to delte but absolutely nothing was there UNTIL I did a "q machine" and another guys desk top AIX box was listed... I did a "delete machine blah" and now I'm no longer using DRM ! Just thought I'd pass this along... Dwight -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 12:03 PM To: [EMAIL PROTECTED] Subject: Re: How to flush DRM references, anybody know ? Dwight, if you find out, would you please pass on the info? We don't need DRM anymore, but I can't figure out how to get rid of it, either. -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: How to flush DRM references, anybody know ? I've already opened a problem with Tivoli but anyone know how to flush all references to DRM ? At one point in time in an attempt to issue a "q pr" the "q" was left off and the "pr" initiated a prepare. Now my server shows I'm using DRM ! In the past I just stuck on the license so it would report valid BUT I just upgraded to 4.2.0.0, then 4.2.2.0 and the drm.lic file doesn't exist ! ! ! and my server reports license as "FAILED" so I'm looking for a way to flush all internal references to DRM ! anyone know ? Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suit 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109
Re: NSM Upgrade Experience
Ooops... we just advised a customer to install 4.2.2.5 --- for SumTab fix, didn't know there is a (yet) new bug for expiration (introduced by 4.2.2.4???) Are you sure that 4.2.2.6 is needed for EXPIRE INVENTORY to work, again ?!? (There is nothing about expiration in the .4 or .5 APAR abstracts... Were you/they referring to the "conflict lock" issue? Geesh, .5 just came out...sigh:() Don France Technical Architect -- Tivoli Certified Consultant San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jolliff, Dale Sent: Thursday, June 20, 2002 2:57 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience I got my 5100-02 patch when someone at 800-IBM-SERV was playing phone tag between myself and the CE when he was out investigating our PMH on duplicate IP addresses. I was told by level 2 this afternoon to avoid expiration on 4.2.2.4 until 4.2.2.6 is available Real Soon Now. -Original Message- From: Talafous, John G. [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 2:25 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience As I understand, support for TSM 4.1 expires June 30, 2002. So if you want to be supported, you have no choice but to upgrade to TSM 4.2. We too have been trying to implement EC017 on our NSM, and have had two failed attempts at the upgrade. The upgrade to AIX 5 and TSM 4.2.1.9 requires an AIX load from 4mm tape. We got a bad 4mm tape. You know, WORN technology (Write Once, Read Never). About 10% of the way into the upgrade to AIX 5 we couldn't read the tape. Tried and tried and tried. But it was bad. We had to recover from the MKSYSB we did that morning. That's why we take MKSYSB's. The second time we tried the EC script failed because \dbaa1dk31\db has on HDISK2. Huh? How did that happen. It turned out that when the recover was done from the MKSYSB all the HDISKS were renumbered by AIX. It took us a couple days with Level II support to get that straightened around. Took Level II about 4 hours dialed in running AIX commands to re-do things and put \dbaa1dk31\db back on HDISK31. We have scheduled our third attempt at EC017 for Sunday, June 30. I've also been told by Level II that anyone preparing to install EC017 should open a PMR prior to the upgrade so support can track the activity. I was also told that not very many NSM sites have done this upgrade, so many will be out of support. And what's this about OS patch 5100-02. Where do I get it and where do I find these kinds of patches? Is there some piece of documentation I've missed or did I just not catch something? Good luck to all!!! John G. Talafous Information Systems Technical Principal Global Software Support - Data Management telephone: (330)-471-3390 e-mail: [EMAIL PROTECTED] http://www.ctnvm.inside.tkr/~talafous/ http://www.cis.corp.inside.tkr/networkstorage/
TSM 5.1 Technical Guide Redbook
All, FYI, the TSM 5.1 Technical Guide Redbook is out: http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246554.h tml?Open -- Joshua S. Bassi Sr. Solutions Architect @ rs-unix.com IBM Certified - AIX 5L, SAN, Shark eServer Systems Expert -pSeries HACMP Tivoli Certified Consultant- ADSM/TSM Cell (415) 215-0326
Re: upgrade from v4.2.2.5 to v5.1.0.0 failed (AIX)
Gretchen, I had a exact same plan to migrate from 4.2.2 to 5.1 in two weeks. I guess I need to reschedule it until I gether better information. Would you please keep us posted on this topic? Regards, Jin Bae Chi (Gus) Data Center 614-287-2496 614-287-5488 Fax e-mail: [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 06/20/02 03:16PM >>> I now in the process of recovering to v4.2.2.5 from an attempted upgrade to v5.1.0.0 (from the CD). All went well from an installation point of view, but when I started the server I got: ANRD iminit.c(820): ThreadId<0> Error 8 converting Group.Members to Backup.Groups. Called it in as a sev 1 over an hour ago, but haven't gotten a callback yet. Since this is production, I can't wait anymore and decided to recover. Not sure what to do now except wait for support to call back. I really need the move nodedata command... Gretchen Thiele Princeton University
Re: NSM Upgrade Experience
I got my 5100-02 patch when someone at 800-IBM-SERV was playing phone tag between myself and the CE when he was out investigating our PMH on duplicate IP addresses. I was told by level 2 this afternoon to avoid expiration on 4.2.2.4 until 4.2.2.6 is available Real Soon Now. -Original Message- From: Talafous, John G. [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 2:25 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience As I understand, support for TSM 4.1 expires June 30, 2002. So if you want to be supported, you have no choice but to upgrade to TSM 4.2. We too have been trying to implement EC017 on our NSM, and have had two failed attempts at the upgrade. The upgrade to AIX 5 and TSM 4.2.1.9 requires an AIX load from 4mm tape. We got a bad 4mm tape. You know, WORN technology (Write Once, Read Never). About 10% of the way into the upgrade to AIX 5 we couldn't read the tape. Tried and tried and tried. But it was bad. We had to recover from the MKSYSB we did that morning. That's why we take MKSYSB's. The second time we tried the EC script failed because \dbaa1dk31\db has on HDISK2. Huh? How did that happen. It turned out that when the recover was done from the MKSYSB all the HDISKS were renumbered by AIX. It took us a couple days with Level II support to get that straightened around. Took Level II about 4 hours dialed in running AIX commands to re-do things and put \dbaa1dk31\db back on HDISK31. We have scheduled our third attempt at EC017 for Sunday, June 30. I've also been told by Level II that anyone preparing to install EC017 should open a PMR prior to the upgrade so support can track the activity. I was also told that not very many NSM sites have done this upgrade, so many will be out of support. And what's this about OS patch 5100-02. Where do I get it and where do I find these kinds of patches? Is there some piece of documentation I've missed or did I just not catch something? Good luck to all!!! John G. Talafous Information Systems Technical Principal Global Software Support - Data Management telephone: (330)-471-3390 e-mail: [EMAIL PROTECTED] http://www.ctnvm.inside.tkr/~talafous/ http://www.cis.corp.inside.tkr/networkstorage/
Re: Backup trigger
Thanks, Max, I 'q log' and lowered the log full percentage and db backup got triggered. Problem solved!! Thanks much again. Regards, Jin Bae Chi (Gus) Data Center 614-287-2496 614-287-5488 Fax e-mail: [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 06/19/02 11:32PM >>> Hi, db backup trigger is checked the log full perecentage not the db pct. util. You must use "q log" to see the pct. util. Max Jin Bae Chi <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 06/20/2002 03:20:00 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Backup trigger Hi, TSM experts, We're running TSM 4.2.2 on AIX 4.3.3. I got a problem with backup trigger. I set Log Full Percentage to 50 and Inc. between Fulls to 6, Device class is 3575CLASS and db backup trigger is enabled. Recovery Log mode is Rollforward. When I 'q db', it shows 'pct util' is 65.6, but I still get the following msg; ANR2121W ATTENTION: More than 8.84766 MB of the database has changed and the last database backup was more than 24 hours ago. Use the BACKUP DB command to provide for database recovery. What did I do wrong that db backup trigger doesn't start? Thanks for your advice. Regards, Jin Bae Chi (Gus) Data Center 614-287-2496 614-287-5488 Fax e-mail: [EMAIL PROTECTED]
solved my case... RE: How to flush DRM references, anybody know ?
Well, just got off the phone with IBM. they had me doing all sorts of queries looking for DR plans to delte but absolutely nothing was there UNTIL I did a "q machine" and another guys desk top AIX box was listed... I did a "delete machine blah" and now I'm no longer using DRM ! Just thought I'd pass this along... Dwight -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 12:03 PM To: [EMAIL PROTECTED] Subject: Re: How to flush DRM references, anybody know ? Dwight, if you find out, would you please pass on the info? We don't need DRM anymore, but I can't figure out how to get rid of it, either. -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: How to flush DRM references, anybody know ? I've already opened a problem with Tivoli but anyone know how to flush all references to DRM ? At one point in time in an attempt to issue a "q pr" the "q" was left off and the "pr" initiated a prepare. Now my server shows I'm using DRM ! In the past I just stuck on the license so it would report valid BUT I just upgraded to 4.2.0.0, then 4.2.2.0 and the drm.lic file doesn't exist ! ! ! and my server reports license as "FAILED" so I'm looking for a way to flush all internal references to DRM ! anyone know ? Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suit 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109
Re: 4.1.X TSM code base
If you have run and are comfortable with new PTF then I would definitely upgrade other server to prevent problem before it happens. David Longo >>> [EMAIL PROTECTED] 06/20/02 03:52PM >>> We have two large TSM servers... One of them, running 4.1.1.0 recently had some problems with expiring old data. After a bunch of give and take with TSM support, Tivoli/IBM told us to upgrade the server to 4.1.6.0. We did that and it fixed the issue. Now, we the 2nd TSM server is at Version 4, Release 1, Level 2.0. Am I going to gain anything in problem avoidance if patch that server up to the 4.1.6.0 PTF? We are not currently having any issues otherwise. And before you mention it, I know that 4.1X is nearing end of life on support. Thanks, David N. Reiss TSM Support Engineer [EMAIL PROTECTED] 407-736-3912 "MMS " made the following annotations on 06/20/2002 06:35:21 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: Réf. : Re: NSM Upgrade Experience
I would wait if I had it to do over again and get the DB cleared up prior to upgrade. I do have it on fairly good authority that 4.2.2.6 will be out Real Soon Now. The corruption we have is something to do with the backups table (or at least whatever keeps track of the backups) we can see some nodes filesystems in occupancy, but not filespaces, and some the other way round. We also have huge amounts of duplicate archive directories from nodes that insist on archiving zillions of files, one file at a time. Most of these nodes all ran the 3.1.x series of clients at one point or another which is where most of the duplicates came from. The DB is over 76GB at 90% capacity (and we are out of disk - tomorrow, we start breaking mirrors), and takes over 3 hours to do a db backup on a *really* good day. I would like to do a db audit, but I'm barely keeping ahead of the lynch mob as it is ;) -Original Message- From: Guillaume Gilbert [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 2:20 PM To: [EMAIL PROTECTED] Subject: Réf. : Re: NSM Upgrade Experience We are currently testing version 4.2.2.2. Of course this is done on a very small basis so its hard to bump in to these problems. My production db is 18gb. Should I wait until this is solved before leaving version 4.1.3 which has been very good to me the past year and a half? When you talk abour corruption, what kind was it. I have some ANRD messages that pop up here and there and support has told me to do an audit db. This is very hard to schedule in my environnement since we have oracle, db2 and notes apllications logging all through the day. I must say that Beat Largo's message has made me more confident about the duration of an audit. I might be able to squeeze it in an 8 hour window. Guillaume Gilbert CGI Canada "Jolliff, Dale" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-20 14:10:07 Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Pour :[EMAIL PROTECTED] cc : Objet : Re: NSM Upgrade Experience The corruption was in the DB before the upgrade. There is a bad lock contention problem when running expiration with 4.2.2.0-4. (4.2.2.4 did mitigate the problem some but didn't solve it) We had symptoms prior to the upgrade, since the upgrade to 4.2.2 we have been crashing on a regular basis. I just shipped off a core dump, activity log and output from a lot of show commands this morning to level 2 that showed an expiration process hanging and the scheduler manager crashing. It's not pretty, and I wouldn't go there if I didn't have to. Again, YMMV - I may just be one unlucky S.O.B. -Original Message- From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 11:12 AM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience Dale, Thanks for the info. The majority of the work will be completed by the CE under the NSM agreement but I was told there will need to be some housekeeping tasks that we need to do anyway. We'll be prepared for that and make sure that everything is checked and documented. What sort of problems did you encounter with the database corruption? Our TSM databases are between 70 and 110GB so database corruption is somewhat of a concern to us. Regards Rizwan -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 1:54 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience Our NSM support contract calls for a CE onsite to do all upgrades of that nature. We went directly to 4.2.20 and AIX 5.1 with EC 17. Aside from that, immediately after the upgrade, apply OS patch 5100-02 immediately. It's a big one, 600+ MB. From the looks of it, it affects almost every fileset in the OS. It fixes some duplicate IP address errors you'll see in errpt. After than, double check your NIC settings - if you do not do auto-negotiation on the link, you'll need to reset it. If I had it to do over again, I think I would stay with something earlier than 4.2.2 - there are some serious locking issues that some corruption in our DB has made almost unbearable for us. YMMV, of course. -Original Message- From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 7:00 AM To: [EMAIL PROTECTED] Subject: NSM Upgrade Experience Hello, Is there anyone out there that has upgraded their NSM's to TSM version 4.2.1.9? The upgrade procedure will also include an AIX upgrade to 5.1 (currently 4.3.3). As the NSM's are black boxes the upgrade involves a mksysb restore (upgrade) and customisation to be carried out by ourselves. In total the outage is approximately 9 hours. I'd like to hear from anyone who has attempted this. Regards Rizwan Shamim Central Backup Service (CBS) Merrill Lynch Europe PLC Tel: 020 7995 1176 Mobile: 0787 625 8246 mailto:[EMAIL
Re: NSM Upgrade Experience
The best result I heared so far was a customer who switched his RS/6000 in the NSM with a windows 2000 server, and also used the SSA disks took same time and less pain.. Peter At 15:24 20-06-2002 -0400, you wrote: >As I understand, support for TSM 4.1 expires June 30, 2002. So if you want >to be supported, you have no choice but to upgrade to TSM 4.2. > >We too have been trying to implement EC017 on our NSM, and have had two >failed attempts at the upgrade. The upgrade to AIX 5 and TSM 4.2.1.9 >requires an AIX load from 4mm tape. We got a bad 4mm tape. You know, WORN >technology (Write Once, Read Never). About 10% of the way into the upgrade >to AIX 5 we couldn't read the tape. Tried and tried and tried. But it was >bad. We had to recover from the MKSYSB we did that morning. That's why we >take MKSYSB's. > >The second time we tried the EC script failed because \dbaa1dk31\db has on >HDISK2. Huh? How did that happen. It turned out that when the recover was >done from the MKSYSB all the HDISKS were renumbered by AIX. It took us a >couple days with Level II support to get that straightened around. Took >Level II about 4 hours dialed in running AIX commands to re-do things and >put \dbaa1dk31\db back on HDISK31. > >We have scheduled our third attempt at EC017 for Sunday, June 30. I've also >been told by Level II that anyone preparing to install EC017 should open a >PMR prior to the upgrade so support can track the activity. I was also told >that not very many NSM sites have done this upgrade, so many will be out of >support. > >And what's this about OS patch 5100-02. Where do I get it and where do I >find these kinds of patches? Is there some piece of documentation I've >missed or did I just not catch something? > >Good luck to all!!! >John G. Talafous >Information Systems Technical Principal >Global Software Support - Data Management >telephone: (330)-471-3390 >e-mail: [EMAIL PROTECTED] >http://www.ctnvm.inside.tkr/~talafous/ >http://www.cis.corp.inside.tkr/networkstorage/
Re: Why my LANFree backup some folder success, some folder failed ?
Thanks a lot Paul. It looks like even my LAN backup is not so successful now. Jason Guo "Seay, Paul" <[EMAIL PROTECTED]> wrote: It seems to me I have seen this before. It had something to do with the COMMMETHOD and the LANFREECOMMETHODs conflicting, but I cannot remember how it was fixed. I will ask the person that fixed it. It took us a month to figure out what was going on. Support was nearly useless on this one. If I remember there was a missing documentation requirement for LAN Free. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: Mike Brown [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 19, 2002 11:21 AM To: [EMAIL PROTECTED] Subject: Why my LANFree backup some folder success, some folder failed? hi there: Why my LANFree backup some folder success, some folder failed? I am useing TSM server version 4.2.1.11 running on AIX 4.3.3; TSM storage Agent version 4.2.1.11 for Win2k, 3583 Tape library; 2108 FC-SCSI bridge, 2109 FC-Switch, 4.2.1.20 TSM client for win2k; Some of my folders can successfully backup, but most of my folders will fail. So far the only successful backup is the "installation files". I trying to backup c:\document and settings faild, C:\setup (all installation files) success, c:\Tivoli (TSNM directory) failed. When ever it failed, sesssion hang. Simillar problem for both LANFREECOMMMETHOD set to namedpipe and set to TCP/IP. And I have enought Database space and enought memory. The error message for failed, when I use named pipe, here is error message from TSM Storage Agent console: NR3174E Communication error with managed server COMPAQSTA. ANR0527W Transaction failed for session 85 for node W2K-TARANTELLA (WinNT) - sufficient database space is not available. ANR8263W Error sending data on Named Pipes, session 85.WriteFile Return code is 232. ANR8336I Verifying label of LTO volume 239ACP in drive 3580DRV1 (\\.\tape1). ANR0400I Session 99 started for node W2K-TARANTELLA (WinNT) (Named Pipe). ANR8468I LTO volume 239ACP dismounted from drive 3580DRV1 (\\.\tape1) in libra The failed error massage when I using TCP for lanfreebackup is as following, from TSM Storage Agent console: TSM:COMPAQSTA> ANR8218W Session terminated when no data read on socket 65836. ANR3174E Communication error with managed server COMPAQSTA. ANR0527W Transaction failed for session 6 for node W2K-TARANTELLA (WinNT) - sufficient database space is not available. ANR8336I Verifying label of LTO volume 239ACP in drive 3580DRV0 (\\.\tape0). ANR0406I Session 16 started for node W2K-TARANTELLA (WinNT) (Tcp/Ip 127.0.0.1(- 1713)). ANR8468I LTO volume 239ACP dismounted from drive 3580DRV0 (\\.\tape0) in library LTO3583. ANR0403I Session 6 ended for node W2K-TARANTELLA (WinNT). Do you have any ideal about this? Any information is apprecated. - Do You Yahoo!? Sign-up for Video Highlights of 2002 FIFA World Cup - Do You Yahoo!? Sign-up for Video Highlights of 2002 FIFA World Cup
Re: Moving DB, LOG, & DiskPool from SAN to local drives
Thank you, Andrew. --- Andrew Carlson <[EMAIL PROTECTED]> wrote: > For the DB and LOG, I would create the files on the > local drives, then > mirror the DB and LOG to them, then delete the copy > on the SAN once the > mirroring completes. For the disk pools, you can > define the new disk > pools on the local drives, then make the SAN disk > pools read only, and, > if you have some time, they will shrink by > themselves, then you can > issue move data command to move whats left. > > > Andy Carlson|\ >_,,,---,,_ > Senior Technical Specialist ZZZzz > /,`.-'`'-. ;-;;,_ > BJC Health Care|,4- > ) )-,_. ,\ ( `'-' > St. Louis, Missouri > '---''(_/--' `-'\_) > Cat Pics: http://andyc.dyndns.org/animal.html > > > On Wed, 19 Jun 2002, Chuck Lam wrote: > > > Hi, > > > > I have TSM 4.1.4 running off AIX 4.3.3. All my > TSM > > Data(DB, LOGs, DISKPOOL) are currently in a > Storage > > Area Network. Due to requirement of my company, I > need > > to move them off to local disk drives. I like to > ask > > if anyone has gone through this process before, > can > > share some of his or her experience. How do you > > safeguard the data while you're moving the > Database > > and the Logs? Can this be done online while the > daily > > backups are still going on?...etc. > > > > TIA > > > > __ > > Do You Yahoo!? > > Yahoo! - Official partner of 2002 FIFA World Cup > > http://fifaworldcup.yahoo.com > > __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
Re: upgrade from v4.2.2.5 to v5.1.0.0 failed (AIX)
Did you apply the latest patches to 5.1.0.0? (5.1.0.2, I believe.) -Original Message- From: Gretchen L. Thiele [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 3:16 PM To: [EMAIL PROTECTED] Subject: upgrade from v4.2.2.5 to v5.1.0.0 failed (AIX) I now in the process of recovering to v4.2.2.5 from an attempted upgrade to v5.1.0.0 (from the CD). All went well from an installation point of view, but when I started the server I got: ANRD iminit.c(820): ThreadId<0> Error 8 converting Group.Members to Backup.Groups. Called it in as a sev 1 over an hour ago, but haven't gotten a callback yet. Since this is production, I can't wait anymore and decided to recover. Not sure what to do now except wait for support to call back. I really need the move nodedata command... Gretchen Thiele Princeton University
Re: Réf. : Re: NSM Upgrade Experience
We are running on 2 NSM's version 4.2.2.4 with a database of 38 gig,.We have not seen any problems so far. The eca needs to be applied on a later time. Peter At 15:20 20-06-2002 -0400, you wrote: >We are currently testing version 4.2.2.2. Of course this is done on a very >small basis so its hard to bump in to these problems. My production db is >18gb. Should I wait >until this is solved before leaving version 4.1.3 which has been very good >to me the past year and a half? > >When you talk abour corruption, what kind was it. I have some ANRD >messages that pop up here and there and support has told me to do an audit >db. This is very hard to >schedule in my environnement since we have oracle, db2 and notes >apllications logging all through the day. I must say that Beat Largo's >message has made me more confident >about the duration of an audit. I might be able to squeeze it in an 8 hour >window. > >Guillaume Gilbert >CGI Canada > > > > >"Jolliff, Dale" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-20 14:10:07 > >Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > >Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > >Pour :[EMAIL PROTECTED] >cc : >Objet : Re: NSM Upgrade Experience > >The corruption was in the DB before the upgrade. >There is a bad lock contention problem when running expiration with >4.2.2.0-4. >(4.2.2.4 did mitigate the problem some but didn't solve it) > >We had symptoms prior to the upgrade, since the upgrade to 4.2.2 we have >been crashing on a regular basis. > >I just shipped off a core dump, activity log and output from a lot of show >commands this morning to level 2 that showed an expiration process hanging >and the scheduler manager crashing. > > >It's not pretty, and I wouldn't go there if I didn't have to. > >Again, YMMV - I may just be one unlucky S.O.B. > > > > >-Original Message- >From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 20, 2002 11:12 AM >To: [EMAIL PROTECTED] >Subject: Re: NSM Upgrade Experience > > >Dale, > >Thanks for the info. > >The majority of the work will be completed by the CE under the NSM agreement >but I was told there will need to be some housekeeping tasks that we need to >do anyway. We'll be prepared for that and make sure that everything is >checked and documented. > >What sort of problems did you encounter with the database corruption? Our >TSM databases are between 70 and 110GB so database corruption is somewhat of >a concern to us. > >Regards > >Rizwan > > > > >-Original Message- >From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 20, 2002 1:54 PM >To: [EMAIL PROTECTED] >Subject: Re: NSM Upgrade Experience > > >Our NSM support contract calls for a CE onsite to do all upgrades of that >nature. >We went directly to 4.2.20 and AIX 5.1 with EC 17. > >Aside from that, immediately after the upgrade, apply OS patch 5100-02 >immediately. >It's a big one, 600+ MB. From the looks of it, it affects almost every >fileset in the OS. >It fixes some duplicate IP address errors you'll see in errpt. > >After than, double check your NIC settings - if you do not do >auto-negotiation on the link, you'll need to reset it. > >If I had it to do over again, I think I would stay with something earlier >than 4.2.2 - there are some serious locking issues that some corruption in >our DB has made almost unbearable for us. > >YMMV, of course. > > > > >-Original Message- >From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] >Sent: Thursday, June 20, 2002 7:00 AM >To: [EMAIL PROTECTED] >Subject: NSM Upgrade Experience > > >Hello, > >Is there anyone out there that has upgraded their NSM's to TSM version >4.2.1.9? > >The upgrade procedure will also include an AIX upgrade to 5.1 (currently >4.3.3). As the NSM's are black boxes the upgrade involves a mksysb restore >(upgrade) and customisation to be carried out by ourselves. In total the >outage is approximately 9 hours. > >I'd like to hear from anyone who has attempted this. > >Regards > > > > Rizwan Shamim > Central Backup Service (CBS) > Merrill Lynch Europe PLC > Tel: 020 7995 1176 > Mobile: 0787 625 8246 > mailto:[EMAIL PROTECTED] > > >
4.1.X TSM code base
We have two large TSM servers... One of them, running 4.1.1.0 recently had some problems with expiring old data. After a bunch of give and take with TSM support, Tivoli/IBM told us to upgrade the server to 4.1.6.0. We did that and it fixed the issue. Now, we the 2nd TSM server is at Version 4, Release 1, Level 2.0. Am I going to gain anything in problem avoidance if patch that server up to the 4.1.6.0 PTF? We are not currently having any issues otherwise. And before you mention it, I know that 4.1X is nearing end of life on support. Thanks, David N. Reiss TSM Support Engineer [EMAIL PROTECTED] 407-736-3912
upgrade from v4.2.2.5 to v5.1.0.0 failed (AIX)
I now in the process of recovering to v4.2.2.5 from an attempted upgrade to v5.1.0.0 (from the CD). All went well from an installation point of view, but when I started the server I got: ANRD iminit.c(820): ThreadId<0> Error 8 converting Group.Members to Backup.Groups. Called it in as a sev 1 over an hour ago, but haven't gotten a callback yet. Since this is production, I can't wait anymore and decided to recover. Not sure what to do now except wait for support to call back. I really need the move nodedata command... Gretchen Thiele Princeton University
Réf. : Re: NSM Upgrade Experience
We are currently testing version 4.2.2.2. Of course this is done on a very small basis so its hard to bump in to these problems. My production db is 18gb. Should I wait until this is solved before leaving version 4.1.3 which has been very good to me the past year and a half? When you talk abour corruption, what kind was it. I have some ANRD messages that pop up here and there and support has told me to do an audit db. This is very hard to schedule in my environnement since we have oracle, db2 and notes apllications logging all through the day. I must say that Beat Largo's message has made me more confident about the duration of an audit. I might be able to squeeze it in an 8 hour window. Guillaume Gilbert CGI Canada "Jolliff, Dale" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2002-06-20 14:10:07 Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Envoyé par : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Pour :[EMAIL PROTECTED] cc : Objet : Re: NSM Upgrade Experience The corruption was in the DB before the upgrade. There is a bad lock contention problem when running expiration with 4.2.2.0-4. (4.2.2.4 did mitigate the problem some but didn't solve it) We had symptoms prior to the upgrade, since the upgrade to 4.2.2 we have been crashing on a regular basis. I just shipped off a core dump, activity log and output from a lot of show commands this morning to level 2 that showed an expiration process hanging and the scheduler manager crashing. It's not pretty, and I wouldn't go there if I didn't have to. Again, YMMV - I may just be one unlucky S.O.B. -Original Message- From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 11:12 AM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience Dale, Thanks for the info. The majority of the work will be completed by the CE under the NSM agreement but I was told there will need to be some housekeeping tasks that we need to do anyway. We'll be prepared for that and make sure that everything is checked and documented. What sort of problems did you encounter with the database corruption? Our TSM databases are between 70 and 110GB so database corruption is somewhat of a concern to us. Regards Rizwan -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 1:54 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience Our NSM support contract calls for a CE onsite to do all upgrades of that nature. We went directly to 4.2.20 and AIX 5.1 with EC 17. Aside from that, immediately after the upgrade, apply OS patch 5100-02 immediately. It's a big one, 600+ MB. From the looks of it, it affects almost every fileset in the OS. It fixes some duplicate IP address errors you'll see in errpt. After than, double check your NIC settings - if you do not do auto-negotiation on the link, you'll need to reset it. If I had it to do over again, I think I would stay with something earlier than 4.2.2 - there are some serious locking issues that some corruption in our DB has made almost unbearable for us. YMMV, of course. -Original Message- From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 7:00 AM To: [EMAIL PROTECTED] Subject: NSM Upgrade Experience Hello, Is there anyone out there that has upgraded their NSM's to TSM version 4.2.1.9? The upgrade procedure will also include an AIX upgrade to 5.1 (currently 4.3.3). As the NSM's are black boxes the upgrade involves a mksysb restore (upgrade) and customisation to be carried out by ourselves. In total the outage is approximately 9 hours. I'd like to hear from anyone who has attempted this. Regards Rizwan Shamim Central Backup Service (CBS) Merrill Lynch Europe PLC Tel: 020 7995 1176 Mobile: 0787 625 8246 mailto:[EMAIL PROTECTED]
Re: sql tdp 2.2 pit error
> ok Thanks. now where do I go once I click on the link? Paul, ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntsql/v221/ Site : ftp.software.ibm.com Directory : /storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntsql/v221/ Files : IP22467.CD.EXE IP22467.EXE IP22467.README.1ST IP22467.README.FTP I hope this helps. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Live your life as an exclamation, not an explanation. - Strive for excellence, not perfection.
Re: TSM server problem
Look for msgno=8469 and see if the dismounts have been failing. I get this kind of behavior occasionally and have found that the dismount fails (hardware problem) and TSM transiently reports volumes unavailable. Henk ten Have <[EMAIL PROTECTED] To: [EMAIL PROTECTED] >cc: Sent by: Subject: TSM server problem "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] IST.EDU> 06/20/2002 10:17 AM Please respond to "ADSM: Dist Stor Manager" I couldn't find an APAR that describes what we have been seeing on our 4.2.1.11 (AIX 4.3.3) server during the last few weeks so I was wondering if we have discovered new bug. First we got this message in the activity log: 06/09/02 10:39:38 ANR1229W Volume 000591 cannot be backed up - volume is offline or access mode is "unavailable" or "destroyed". We did a 'q vol f=d'. The access mode of the volume was 'Available' so we dismissed it as a freak incident until the message repeated itself the next day. This time we opened the (3494) library and verified that the volume was in the correct cell. We tried a 'restore volume' followed by a 'delete volume'. The delete failed: ANR2405E DELETE VOLUME: Volume 000591 is currently in use by clients and/or data management operations. ANS8001I Return code 14. At that time there were no processes or sessions that used that particular volume. Also we had four other volumes that displayed the same behaviour. We halted the server and restarted it again which solved the problem. The volumes were no longer 'in use'. Today we noticed two other volumes that seem to have the same problem so I'm beginning to suspect that I've found a bug in the server. All these volumes have one thing in common: When I seacrh the activity log for their mounts and dismounts I can't find a dismount message after their last mount (before they become 'unavailable'). It is as if the volumes are unmounted by the library but TSM isn't being notified of this. Anyone seen this before? Cheers, Henk.
Re: NSM Upgrade Experience
As I understand, support for TSM 4.1 expires June 30, 2002. So if you want to be supported, you have no choice but to upgrade to TSM 4.2. We too have been trying to implement EC017 on our NSM, and have had two failed attempts at the upgrade. The upgrade to AIX 5 and TSM 4.2.1.9 requires an AIX load from 4mm tape. We got a bad 4mm tape. You know, WORN technology (Write Once, Read Never). About 10% of the way into the upgrade to AIX 5 we couldn't read the tape. Tried and tried and tried. But it was bad. We had to recover from the MKSYSB we did that morning. That's why we take MKSYSB's. The second time we tried the EC script failed because \dbaa1dk31\db has on HDISK2. Huh? How did that happen. It turned out that when the recover was done from the MKSYSB all the HDISKS were renumbered by AIX. It took us a couple days with Level II support to get that straightened around. Took Level II about 4 hours dialed in running AIX commands to re-do things and put \dbaa1dk31\db back on HDISK31. We have scheduled our third attempt at EC017 for Sunday, June 30. I've also been told by Level II that anyone preparing to install EC017 should open a PMR prior to the upgrade so support can track the activity. I was also told that not very many NSM sites have done this upgrade, so many will be out of support. And what's this about OS patch 5100-02. Where do I get it and where do I find these kinds of patches? Is there some piece of documentation I've missed or did I just not catch something? Good luck to all!!! John G. Talafous Information Systems Technical Principal Global Software Support - Data Management telephone: (330)-471-3390 e-mail: [EMAIL PROTECTED] http://www.ctnvm.inside.tkr/~talafous/ http://www.cis.corp.inside.tkr/networkstorage/
Re: TDP for Exchange incremental failure
> Backup of storage group Directory failed. > Unable to perform an incremental backup because a required Microsoft > Exchange database log file could not be found. > > Four days ago, the last full backup ran ok and the two incrementals > afterwards (three days ago and the day before yesterday) ran fine too. > There is no other backups software (that could have removed the transaction > logs) running on this machine. > Does anybody know what happened here? Eric, This is the Exchange Server's way of telling you that you need to run a full backup. In some cases, having to do with database reorganization or such, Exchange forces a full backup. To enforce this, they cause all incremental backups to fail until a full backup is done. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Live your life as an exclamation, not an explanation. - Strive for excellence, not perfection.
Re: NSM Upgrade Experience
The corruption was in the DB before the upgrade. There is a bad lock contention problem when running expiration with 4.2.2.0-4. (4.2.2.4 did mitigate the problem some but didn't solve it) We had symptoms prior to the upgrade, since the upgrade to 4.2.2 we have been crashing on a regular basis. I just shipped off a core dump, activity log and output from a lot of show commands this morning to level 2 that showed an expiration process hanging and the scheduler manager crashing. It's not pretty, and I wouldn't go there if I didn't have to. Again, YMMV - I may just be one unlucky S.O.B. -Original Message- From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 11:12 AM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience Dale, Thanks for the info. The majority of the work will be completed by the CE under the NSM agreement but I was told there will need to be some housekeeping tasks that we need to do anyway. We'll be prepared for that and make sure that everything is checked and documented. What sort of problems did you encounter with the database corruption? Our TSM databases are between 70 and 110GB so database corruption is somewhat of a concern to us. Regards Rizwan -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 1:54 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience Our NSM support contract calls for a CE onsite to do all upgrades of that nature. We went directly to 4.2.20 and AIX 5.1 with EC 17. Aside from that, immediately after the upgrade, apply OS patch 5100-02 immediately. It's a big one, 600+ MB. From the looks of it, it affects almost every fileset in the OS. It fixes some duplicate IP address errors you'll see in errpt. After than, double check your NIC settings - if you do not do auto-negotiation on the link, you'll need to reset it. If I had it to do over again, I think I would stay with something earlier than 4.2.2 - there are some serious locking issues that some corruption in our DB has made almost unbearable for us. YMMV, of course. -Original Message- From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 7:00 AM To: [EMAIL PROTECTED] Subject: NSM Upgrade Experience Hello, Is there anyone out there that has upgraded their NSM's to TSM version 4.2.1.9? The upgrade procedure will also include an AIX upgrade to 5.1 (currently 4.3.3). As the NSM's are black boxes the upgrade involves a mksysb restore (upgrade) and customisation to be carried out by ourselves. In total the outage is approximately 9 hours. I'd like to hear from anyone who has attempted this. Regards Rizwan Shamim Central Backup Service (CBS) Merrill Lynch Europe PLC Tel: 020 7995 1176 Mobile: 0787 625 8246 mailto:[EMAIL PROTECTED]
Re: How to flush DRM references, anybody know ?
Dwight, if you find out, would you please pass on the info? We don't need DRM anymore, but I can't figure out how to get rid of it, either. -Original Message- From: Cook, Dwight E [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: How to flush DRM references, anybody know ? I've already opened a problem with Tivoli but anyone know how to flush all references to DRM ? At one point in time in an attempt to issue a "q pr" the "q" was left off and the "pr" initiated a prepare. Now my server shows I'm using DRM ! In the past I just stuck on the license so it would report valid BUT I just upgraded to 4.2.0.0, then 4.2.2.0 and the drm.lic file doesn't exist ! ! ! and my server reports license as "FAILED" so I'm looking for a way to flush all internal references to DRM ! anyone know ? Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suit 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109
spacetrigger for LOG
Hello, I was just wondering if anyone happens to know if TSM has to be in rollforward mode for the recovery log's spacetrigger to work? There is no reference in any of the books about this, but I have put a spacetrigger on for the recovery log and it didn't extend when it hit the 80% mark that I specified. I have looked into this and the only place I found that you need to have TSM in rollforward mode is with the DB spacetrigger. Does anyone have any suggestions/ideas on this matter? Thanks! Joni Moyer Associate Systems Programmer [EMAIL PROTECTED] (717)975-8338
Re: sql tdp 2.2 pit error
ok Thanks. now where do I go once I click on the link? Paul > -Original Message- > From: Del Hoobler [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, June 20, 2002 12:53 PM > To: [EMAIL PROTECTED] > Subject: Re: sql tdp 2.2 pit error > > > We just installed a new node with SQL TDP 2.2 and when we go and do > > a PIT this is the error we receive. > > any thoughts? > > > > ACO5801E A log must be selected to use point in time. > > Paul, > > Make sure you are running version 2.2.1. > (It is available on the ftp.software.ibm.com.) > You need to select a log in order to do a point in time restore. > Microsoft will stop replaying transactions > once it hits the point in time specified. > If it still fails, please call IBM support. > > Thanks, > > Del > > > > Del Hoobler > IBM Corporation > [EMAIL PROTECTED] > > - Live your life as an exclamation, not an explanation. > - Strive for excellence, not perfection.
How to flush DRM references, anybody know ?
I've already opened a problem with Tivoli but anyone know how to flush all references to DRM ? At one point in time in an attempt to issue a "q pr" the "q" was left off and the "pr" initiated a prepare. Now my server shows I'm using DRM ! In the past I just stuck on the license so it would report valid BUT I just upgraded to 4.2.0.0, then 4.2.2.0 and the drm.lic file doesn't exist ! ! ! and my server reports license as "FAILED" so I'm looking for a way to flush all internal references to DRM ! anyone know ? Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suit 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109
Re: sql tdp 2.2 pit error
> We just installed a new node with SQL TDP 2.2 and when we go and do > a PIT this is the error we receive. > any thoughts? > > ACO5801E A log must be selected to use point in time. Paul, Make sure you are running version 2.2.1. (It is available on the ftp.software.ibm.com.) You need to select a log in order to do a point in time restore. Microsoft will stop replaying transactions once it hits the point in time specified. If it still fails, please call IBM support. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] - Live your life as an exclamation, not an explanation. - Strive for excellence, not perfection.
Re: TSM server problem
Are you seeing any I/O errors on these tapes or errors on the drives? What type of process was mounting the tapes - backup stg, reclamation etc.? David Longo >>> [EMAIL PROTECTED] 06/20/02 11:17AM >>> I couldn't find an APAR that describes what we have been seeing on our 4.2.1.11 (AIX 4.3.3) server during the last few weeks so I was wondering if we have discovered new bug. First we got this message in the activity log: 06/09/02 10:39:38 ANR1229W Volume 000591 cannot be backed up - volume is offline or access mode is "unavailable" or "destroyed". We did a 'q vol f=d'. The access mode of the volume was 'Available' so we dismissed it as a freak incident until the message repeated itself the next day. This time we opened the (3494) library and verified that the volume was in the correct cell. We tried a 'restore volume' followed by a 'delete volume'. The delete failed: ANR2405E DELETE VOLUME: Volume 000591 is currently in use by clients and/or data management operations. ANS8001I Return code 14. At that time there were no processes or sessions that used that particular volume. Also we had four other volumes that displayed the same behaviour. We halted the server and restarted it again which solved the problem. The volumes were no longer 'in use'. Today we noticed two other volumes that seem to have the same problem so I'm beginning to suspect that I've found a bug in the server. All these volumes have one thing in common: When I seacrh the activity log for their mounts and dismounts I can't find a dismount message after their last mount (before they become 'unavailable'). It is as if the volumes are unmounted by the library but TSM isn't being notified of this. Anyone seen this before? Cheers, Henk. "MMS " made the following annotations on 06/20/2002 01:12:23 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. =
page_shadow_token
What is, and how is the page_shadow_token calculated/created in the dsmserv.dsk file?
Re: Moving DB, LOG, & DiskPool from SAN to local drives
For the DB and LOG, I would create the files on the local drives, then mirror the DB and LOG to them, then delete the copy on the SAN once the mirroring completes. For the disk pools, you can define the new disk pools on the local drives, then make the SAN disk pools read only, and, if you have some time, they will shrink by themselves, then you can issue move data command to move whats left. Andy Carlson|\ _,,,---,,_ Senior Technical Specialist ZZZzz /,`.-'`'-. ;-;;,_ BJC Health Care|,4- ) )-,_. ,\ ( `'-' St. Louis, Missouri '---''(_/--' `-'\_) Cat Pics: http://andyc.dyndns.org/animal.html On Wed, 19 Jun 2002, Chuck Lam wrote: > Hi, > > I have TSM 4.1.4 running off AIX 4.3.3. All my TSM > Data(DB, LOGs, DISKPOOL) are currently in a Storage > Area Network. Due to requirement of my company, I need > to move them off to local disk drives. I like to ask > if anyone has gone through this process before, can > share some of his or her experience. How do you > safeguard the data while you're moving the Database > and the Logs? Can this be done online while the daily > backups are still going on?...etc. > > TIA > > __ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com >
Re: DB backups
I have seen the latest and fastest computer causing log pin. Cause? due to incorrect NIC setting, like 100 Half duplex, and/or incorrect setting at the switch. Have u tried to backup using 10 MB with half duplex? I did, it will drive u crazy. Sung Y. Lee E-mail [EMAIL PROTECTED] "Seay, Paul" cc: Sent by: "ADSM: Subject: Re: DB backups Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 06/19/2002 07:47 PM Please respond to "ADSM: Dist Stor Manager" Roll forward will even work in highly active environments, BUT, if you have one constipated turtle you are screwed. That can cause a log pin. Typically, it is the 286 PC that is running on a 1200 baud line with a 50% error rate from Afghanistan. You get the point. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180 -Original Message- From: Remeta, Mark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 19, 2002 12:05 PM To: [EMAIL PROTECTED] Subject: Re: DB backups Hi Dan, Roll forward mode would work unless you have as much activity as Wanda does. In that case you cannot use it because your log fills up to fast. Mark -Original Message- From: Daniel Sparrman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 19, 2002 6:58 AM To: [EMAIL PROTECTED] Subject: Re: DB backups Hi You don't have to do full backups every hour to be able to do point-in-time restore of the database. Having your recovery log in roll-forward mode, means that you don't have to backup your database. In case of a corrupt database, you just restore you're database that you have backed up earlier, and then tell TSM to do a point-in-time restore. This means that after TSM has restored the database from the tape, it will inspect the log, to see what transactions have been made after the database backup. This was what I was trying to explain in my last message. Using this scenario, you don't have to backup your database twice a day. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 HÄGERNÄS Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Remco Post <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2002-06-18 11:35 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:Re: DB backups Hi, The question is more, do you really want to be able to do a point-in-time restore of your database. In case of a real disaster, you'll probably be very happy if you get the server back to a state it was in 24 hours before the disaster. In case of database corruption, You'll probably cannot afford to restore 10 times just to find an approx point in time for the corrupting transaction, which is still in you log... I guess that maybe a few incremental db backups during the day would be good enough for most pe
Re: TSM and Exchange 2000 Disaster recovery in AD
Hi The Exchange server will backup the adressbook and the information store. The normal backup/restore client backups the the active directory. When doing a restore, you first restore the files and system objects(AD), and then restore the information store. In this way, all the information from both Exchange and the AD will be both backed up and restored when you choose to do so. No, there is no brick level restore for TSM. However, some of my colleauges have successfully used BackupExec NT/2000 client to backup using brick-level to a TSM server. I haven't done this myself, however they have told me that somehow you can configure the BackupExec client to send data to the TSM server. There has been rumors that Tivoli is working on a brick-level restore client. How much of this is true, I don't know... Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 HÄGERNÄS Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 "Consiglio, Tony" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2002-06-20 14:47 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:TSM and Exchange 2000 Disaster recovery in AD Hello, We will be moving to Exchange 2000 in the future. As far a I know at this point TSM doesn't allow Brick level backup or restore. How a is TSM set for doing Disaster recovery of Mail server in AD? Does anyone have any experience in doing this yet? Thanks Tony Anthony F.Consiglio Senior Systems Analyst II Network Engineer, LAN Systems Tel: 645-7340, FAX: 645-3543 E-MAIL: [EMAIL PROTECTED]
Re: NSM Upgrade Experience
Dale, Thanks for the info. The majority of the work will be completed by the CE under the NSM agreement but I was told there will need to be some housekeeping tasks that we need to do anyway. We'll be prepared for that and make sure that everything is checked and documented. What sort of problems did you encounter with the database corruption? Our TSM databases are between 70 and 110GB so database corruption is somewhat of a concern to us. Regards Rizwan -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 1:54 PM To: [EMAIL PROTECTED] Subject: Re: NSM Upgrade Experience Our NSM support contract calls for a CE onsite to do all upgrades of that nature. We went directly to 4.2.20 and AIX 5.1 with EC 17. Aside from that, immediately after the upgrade, apply OS patch 5100-02 immediately. It's a big one, 600+ MB. From the looks of it, it affects almost every fileset in the OS. It fixes some duplicate IP address errors you'll see in errpt. After than, double check your NIC settings - if you do not do auto-negotiation on the link, you'll need to reset it. If I had it to do over again, I think I would stay with something earlier than 4.2.2 - there are some serious locking issues that some corruption in our DB has made almost unbearable for us. YMMV, of course. -Original Message- From: Shamim, Rizwan (London) [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 7:00 AM To: [EMAIL PROTECTED] Subject: NSM Upgrade Experience Hello, Is there anyone out there that has upgraded their NSM's to TSM version 4.2.1.9? The upgrade procedure will also include an AIX upgrade to 5.1 (currently 4.3.3). As the NSM's are black boxes the upgrade involves a mksysb restore (upgrade) and customisation to be carried out by ourselves. In total the outage is approximately 9 hours. I'd like to hear from anyone who has attempted this. Regards Rizwan Shamim Central Backup Service (CBS) Merrill Lynch Europe PLC Tel: 020 7995 1176 Mobile: 0787 625 8246 mailto:[EMAIL PROTECTED]
Re: Select statements
I tried naming the column, but that didn't seem to work. Using the column number as you and Paul suggested worked fine. Thanks for the help! -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 19, 2002 10:32 AM To: [EMAIL PROTECTED] Subject: Re: Select statements It's an SQL thing. SQL operations occur in a certain order. When you do a SELECT to query a table, the results you get back are actually another (temporary) table. "where" clauses are applied to columns in the original table "order" clauses are applied to the columns in the result table Backup_start isn't in your "results" table, because you didn't ask for that. Date(backup_start) is a function, not a column name, so that doesn't work, either. Naming the column will fix it: select date(backup_start) as GUMP , node_name , filespace_name from filespaces where backup_start<=current_timestamp - 110 days order by GUMP (There is probably a better written explantion for this somewhere, but my solution for dealing with these SQL issues was to marry a DBA :>) Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert -Original Message- From: Jolliff, Dale [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 19, 2002 8:33 AM To: [EMAIL PROTECTED] Subject: Select statements Is this really working as designed? order by date(backup_start) doesn't work either. This is TSM 4.2.2.4 on AIX select date(backup_start), node_name, filespace_name from filespaces - where backup_start<=timestamp(current_date - 110 days ) - order by backup_start ANR2964E The reference 'BACKUP_START' is not a column of the SQL result table. | ...V... tart<=timestamp(current_date - 110 days ) order by backup_start ANS8001I Return code 3.
Re: Microcode levels and atape/atldd upgrade
You don't have to, but we were *strongly* recommended to go to microcode level 35A on our 3590 E1As (FC attach), which should - together with Atape 7.0.7.0 - solve some long-running troubles we've had. Richard Foster Norsk Hydro asa
TSM server problem
I couldn't find an APAR that describes what we have been seeing on our 4.2.1.11 (AIX 4.3.3) server during the last few weeks so I was wondering if we have discovered new bug. First we got this message in the activity log: 06/09/02 10:39:38 ANR1229W Volume 000591 cannot be backed up - volume is offline or access mode is "unavailable" or "destroyed". We did a 'q vol f=d'. The access mode of the volume was 'Available' so we dismissed it as a freak incident until the message repeated itself the next day. This time we opened the (3494) library and verified that the volume was in the correct cell. We tried a 'restore volume' followed by a 'delete volume'. The delete failed: ANR2405E DELETE VOLUME: Volume 000591 is currently in use by clients and/or data management operations. ANS8001I Return code 14. At that time there were no processes or sessions that used that particular volume. Also we had four other volumes that displayed the same behaviour. We halted the server and restarted it again which solved the problem. The volumes were no longer 'in use'. Today we noticed two other volumes that seem to have the same problem so I'm beginning to suspect that I've found a bug in the server. All these volumes have one thing in common: When I seacrh the activity log for their mounts and dismounts I can't find a dismount message after their last mount (before they become 'unavailable'). It is as if the volumes are unmounted by the library but TSM isn't being notified of this. Anyone seen this before? Cheers, Henk.
