Being a university, we also have older/non-mainstream systems we backup (IRIX anyone? DEC VAX?).
Looks like 5.3 (which is no longer supported) is the highest you can go for RH3 - per this page: https://www-304.ibm.com/support/docview.wss?uid=swg21303997 Red Hat Enterprise Linux 3 (AS,WS,ES) (need compat-gcc-c++-7.3-2.96.122.i386.rpm) Red Hat Enterprise Linux 4 (AS,WS,ES) RedFlag 4.1 To answer your next question, Yes we have clients at 5.2.3 backing up to a 5.5.5 server with no issues. Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 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 From: Richard Rhodes <[email protected]> To: [email protected] Date: 05/18/2011 03:20 PM Subject: [ADSM-L] linux client for RHES v3 Sent by: "ADSM: Dist Stor Manager" <[email protected]> Hi everyone, We have just found that we have to start TSM backups of a RedHat Enterprise Linux ES Release 3 server (that's what I'm told the version is). I went looking on IBM's web site - the oldest compatibility info I can come up with is for TSM client v5.4.1 as supporting RH v5. Does anyone have any idea what TSM client would work on RedHat Enterprise Linux ES Release 3 . . . if any? (Then I get to try and find that client!!!!) Thanks Rick ----------------------------------------- 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.
