Hello everyone,
To date, I have not had any problems upgrading/patching my one production
6.1.x server - just getting ready to upgrade from 6.1.3.4 to 6.1.4.1
(anyone else do this on a Linux platform ? Any problems
-> done yesterday on Redhat 5, no problems...
Personally, I installed more TSM servers on v6 (aix, linux, win maybe zLinux
next) and I installed v6.1 because v6.2 wasn't ready or only at level
6.2.x.0 I prefer leave test other users before...
For v6.1 system I advise to remain in this major level with last patch
6.1.4.1 (because of the non 100% confident upgrade path) but for new I agree
to go straight to v6.2.
--
-
Cordiali saluti / Meilleures salutations
Maurizio Teruzzi
http://www.teruzzi.ch
ftp://ftp.teruzzi.ch
Skype user: TERUZZI
2010/9/8 Remco Post <r.post AT plcs DOT nl>
> I've not yet had the pleasure of upgrading from 6.1 to 6.2. The installer
> (deployment engine) is supposed to take care of everything, but I also know
> from experience that the DE is not IBM's best product.
>
> Now, as for new installs, or upgrades from version 5, please skip 6.1, and
> avoid at least one upgrade problem...
>
>
>
> --
>
> Gr., Remco
>
> On 7 sep. 2010, at 23:01, "John D. Schneider" <
> john.schneider AT COMPUTERCOACHINGCOMMUNITY DOT COM> wrote:
>
> > Remco,
> > If TSM 6.1 is dead, and everybody should just go to 6.2, then please
> > respond to the user's posted problem. He was running 6.1 and tried to
> > upgrade to 6.2.1.1, and had such a miserable failure that he ended up
> > wiping out all his efforts and starting over. How does he get to 6.2 if
> > the upgrade won't work?
> > Can anybody else tell us about the 6.1 to 6.2 upgrade path? Is this
> > user's experience isolated to Linux? Or is it a complete aberation for
> > this user, but nobody else is getting this sort of problem during an
> > upgrade?
> >
> > I have a customer who upgraded from 5.5.x to 6.1.0.0 (yes, I know, I
> > have no idea why they installed that version) and of course they are
> > unhappy about it. So they asked me today to upgrade it to a stable
> > version, and I was going to suggest 6.1.4, since I have other customers
> > stable on that release. But if it makes more sense to go straight to
> > 6.2.1.1, I am happy to do that, but I would like to have some confidence
> > in the upgrade path before I make my recommendation.
> >
> > Best Regards,
> >
> > John D. Schneider
> > The Computer Coaching Community, LLC
> > Office: (314) 635-5424 / Toll Free: (866) 796-9226
> > Cell: (314) 750-8721
> >
> >
> >
> > -------- Original Message --------
> > Subject: Re: [ADSM-L] New server - 6.1.4.1 or 6.2.1.1?
> > From: Remco Post <r.post AT PLCS DOT NL>
> > Date: Tue, September 07, 2010 2:22 pm
> > To: ADSM-L AT VM.MARIST DOT EDU
> >
> > Repeat after me: TSM 6.1 is dead! :)
> >
> > Really, 6.1 is never a good choice, always go straight to 6.2.
> >
> > --
> >
> > Gr., Remco
> >
> > On 7 sep. 2010, at 20:39, Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
> > wrote:
> >
> >> I am putting up 2-new Linux based 6.x servers that will eventually
> replace
> >> older 5.5.x boxes.
> >>
> >> My issue/question is........ should I go with 6.1.4.1 or 6.2.1.1?
> >>
> >> Part of the reason for asking this is due to my bad experience with
> trying
> >> to upgrade a test server from 6.1.3.4 to 6.2.1 - total failure - upgrade
> >> would not run to completion - kept telling me the database had issues
> >> (eventhough it was a virgin, empty 6.1.3.4 instance just installed) and
> it
> >> got so badly torqued when I tried to remove the half-install, I had to
> >> have the OS guy just wipe it and start all over. Then I installed
> 6.2.1.1
> >> virgin and it has been sitting there (waiting to have it shipped
> offsite).
> >>
> >> To date, I have not had any problems upgrading/patching my one
> production
> >> 6.1.x server - just getting ready to upgrade from 6.1.3.4 to 6.1.4.1
> >> (anyone else do this on a Linux platform ? Any problems?)
> >>
> >> Your thoughts?
> >> Zoltan Forray
> >> TSM Software & Hardware Administrator
> >> Virginia Commonwealth University
> >> UCC/Office of Technology Services
> >> zforray AT vcu DOT edu - 804-828-4807
> >> Don't be a phishing victim - VCU and other reputable organizations will
> >> never use email to request that you reply with your password, social
> >> security number or confidential personal information. For more details
> >> visit http://infosecurity.vcu.edu/phishing.html
>
|
