Content preview: I believe the incompatibility arises if you set
SESSIONSECURITY
to STRICT for your nodes. The default is TRANSITIONAL so you should be fine;
IIRC the only communication problems we had when upgrading our servers to
v7.1.8 was with library sharing. [...]
Content ana
Thanks for that link, I am more worried about any "gotcha's" caused by
upgrading the client to 7.1.8 or 8.1.2 before the storage servers get
upgraded (and start using the new authentication). What I had not
realized until I saw the chart is that the new clients are NOT backward
compatible with ol
There's pretty wide version compatibility between clients and servers; we
didn't go v7 server-side until pretty recently but have been running the v7
client for a while. IBM has a matrix published here:
http://www-01.ibm.com/support/docview.wss?uid=swg21053218
For basic backups and restores I thi
Our TSM storage servers were all upgraded last year to 7.1.7.2 (before this
new security update came out). Now I am wondering if I should start using
the updated client or not? If the servers stay at 7.1.7.2 for now is
there any harm in using the newer client? I would have to use 7.1.8.0 on
an
