I had to go from 3.1 to 3.7 then to 4.1.2
The reason is that I did not want to lose any backups during the upgrade.
The 3.1 client is not supported under 4.1 server but is on 3.7 I brought
server up to 3.7 upgraded all clients to 4.1.2 (latest available at the
time) then upgraded to 4.1 server.
Watch your Netware servers because I lost long name support on 4 servers.
One crashed during upgrade (not related) & had to go back 2 weeks to restore
with long file names. My suggestion is to use 4.1.2.14 According to Tivoli
the memory leak is fixed (you don't need to use cron to start scheduler).
If you are supporting long file names on your Netware servers make sure the
MEMORYEFFICIENTBACKUP option is set to YES in dsm.opt
-----Original Message-----
From: Foley, Joe [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 2:36 PM
To: [EMAIL PROTECTED]
Subject: version 3 to version 4 help
Hi All
I am (finally!) preparing to upgrade from ADSM 3.1 to TSM 4.1 and am
slightly overwhelmed by the choices available. My current plan is as
follows:
Server (Windows NT)
Currently 3.1.2.40 upgrade to 4.1.0.0 then to 4.1.3.0
Windows NT clients
Currently 3.1.0.7f2 upgrade to 4.1.2.12
Netware clients
Currently 3.1.0.8 upgrade to 4.1.2.13
If anyone has advice (specifically known problems) regarding these client
and server versions or the upgrade process in general, I would greatly
appreciate input. I'm upgrading in a test bed first, of course, but any
first hand experience would be great. Thanks!
Joe Foley
Bain & Company, Inc
|
|
|
| ___________________NOTICE____________________________
This electronic mail transmission contains confidential information
intended only for the person(s) named. Any use, distribution,
copying or disclosure by any other person is strictly prohibited.
If you received this transmission in error, please notify the sender
by reply e-mail and then destroy the message. Opinions, conclusions,
and other information in this message that do not relate to the official
business of Bain & Company shall be understood to be neither given
nor endorsed by the Company. When addressed to Bain clients, any
information contained in this e-mail is subject to the terms and conditions
in the governing client contract.
_____________________________________________________
