Yep... just see the README; the usual conditions for upgrade on either the server or the client is (a) once you upgrade the client, you *can* use the new client features (ie, the ones specific to client operations), and you *cannot* go back (this is a more recent caveat, in that new levels add new objects to the database); (b) upgrade the server, at your convenience, just realize you cannot exploit new server features (even if supported by the client), until the proper, supporting server level is installed.
Muddy as heck? Read the README for the server or the client; the README file contains the full details you need to know... but, in general, using the same features you've already been using does not require both server and client be at the same level. A 3.1 client can talk to a 4.1 server, and (also) a 4.2 or even 5.1 client can talk to 4.1 server (just cannot use any new, 4.2 features that would require cooperation from the server). The developers have gone to great lengths to ensure client and server upgrades are not locked into each other... review the README for your specific situation. Don France Technical Architect -- Tivoli Certified Consultant Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390 San Jose, Ca (408) 257-3037 mailto:don_france@;att.net Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of Bill Dourado Sent: Sunday, November 03, 2002 6:41 AM To: [EMAIL PROTECTED] Subject: Re: Daylight saving Disaster Don, What I need to know in the short term, (if anybody has experience) , is it OK having 4.2.3.1 clients running on TSM Server 4.1.1.4 ? Bill Dourado Ext 5134 DFrance <DFrance-TSM@ To: [EMAIL PROTECTED] ATT.NET> cc: Sent by: Subject: Re: Daylight saving Disaster "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 02/11/02 22:00 Please respond to "ADSM: Dist Stor Manager" It was the client code that was previously fixed, more than once, in the 3.1 and 3.7 timeframe --- sounds like the DST code for Windows got broken, again. 4.1.x is downlevel, for support contract purposes -- unless things are different for you. Don France Technical Architect -- Tivoli Certified Consultant Tivoli Storage Manager, WinNT/2K, AIX/Unix, OS/390 San Jose, Ca (408) 257-3037 mailto:don_france@;ayett.net (change aye to a, for replies) Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@;VM.MARIST.EDU]On Behalf Of Bill Dourado Sent: Saturday, November 02, 2002 7:03 AM To: [EMAIL PROTECTED] Subject: Daylight saving Disaster Importance: High Hi there I am in big trouble after daylight saving when clocks went backup one hour. All the clients(50) are attempting to do full backups ! My TSM Server version is 4.1.4.1 The clients(Windows 2000 & NT) are mostly 4.1.1.0 , a few are 3.1.07 & 3.1.0.6. I have temporarily suspended all backup schedules except for the business critical clients. I have upgraded one of clients to 4.2.3.1 and intend to upgrade the rest of the clients. Will I run into any problems bearing in mind my TSM Server version is 4.1.4.1 ? T.I.A Bill Dourado
