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 ANR9999D 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]
