I was talking to a Tivoli Level 2 person and got a bit of good
news on this - TSM has maintenance levels of "a.b.c.d" as we all know (for
example 4.2.2.5). When changing server levels, the first 3 numbers of the
TSM Server level have to match the San Storage Agents when applying
maintenance. The last level (the fixtest level) does NOT have to be the
same. For example, a 4.2.2.5 TSM server is compatible with a 4.2.2.0 San
Storage Agent. Of course, this doesn't help anyone going from 4.2.2.4 to
5.1.1.0. In this case, all San Storage Agents and TSM servers code levels
have to updated at the same time.
At 05:39 PM 6/21/2002 -0400, you wrote:
>Server Software question along with SAN Clients. Tivoli says they have to
>match at the same level.
>
>Paul D. Seay, Jr.
>Technical Specialist
>Naptheon, INC
>757-688-8180
>
>
>-----Original Message-----
>From: Consiglio, Tony [mailto:[EMAIL PROTECTED]]
>Sent: Friday, June 21, 2002 9:08 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Do you lob it on or do you fully test before that next releas
>e?
>
>
>Paul,
> Is this question based on the upgrade to the "Server software" or
>the "client backup/restore software".
>
>-----Original Message-----
>From: Seay, Paul [mailto:[EMAIL PROTECTED]]
>Sent: Friday, June 21, 2002 1:56 AM
>To: [EMAIL PROTECTED]
>Subject: Do you lob it on or do you fully test before that next release?
>
>
>After seeing all the pain everyone is experiencing going from 4.2.2 to
>5.1.1. I thought I would ask this question to see what everyone is doing.
>We intend to create an entire environment to test the upgrade with and then
>actually perform it.
>
>What is everyone else doing?
>What is your server platform?
>How are you handling the SAN client incompatibility issues?
>
>Paul D. Seay, Jr.
>Technical Specialist
>Naptheon, INC
>757-688-8180
Money is not the root of all evil - full backups are.
