Re: [ADSM-L] TSM Server 7.1.4 woes
I think this is NOT acceptable.
Many systems are no longer officially supported.
We never had such a situation in the past 20 years!!!!
In many countries you are legally required to archive systems
(especially ERP systems) for at least 10 years after you have made
certain changes to the original system.
Such scenarios MUST be supported by a serious vendor.
The lifetime of systems is 15+ years in the field of mechanical engineering.
It is NOT possible to upgrade systems to new OS versions every year.
On 26.04.2016 17:19, Michael Prix wrote:
> Yes. Where it is possible to upgrade.
> Michael PrixOn Di, 2016-04-26 at 15:03 +0000, Rhodes, Richard L. wrote:
>> Were you able to restore files after upgrading a client to a supported
>> -----Original Message-----
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
>> Michael Prix
>> Sent: Tuesday, April 26, 2016 7:04 AM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: TSM Server 7.1.4 woes
>> Hello all,
>> it is well known that older clients are out of support, but still continue
>> to work with the capabilities they were designed for.
>> Now I and some colleagues of mine upgraded customers to TSM 7.1.4 and 7.1.5,
>> with client-versions ranging from 5.5 to 7.1, and all of a sudden all
>> <=6.1 can still backup to the server, but aren't any longer able to
>> restore/retrieve files. ANR4035W is reported.
>> While this might not be a situation where one could get support from IBM, it
>> is still a new situation as we as old *SMers are used to the fact that old
>> clients remain useable after an upgrade.
>> Michael Prix
>> The information contained in this message is intended only for the personal
>> and confidential use of the recipient(s) named above. If the reader of this
>> message is not the intended recipient or an agent responsible for delivering
>> it to the intended recipient, you are hereby notified that you have received
>> this document in error and that any review, dissemination, distribution, or
>> copying of this message is strictly prohibited. If you have received this
>> communication in error, please notify us immediately, and delete the
>> original message.