ADSM-L

Re: Migrating to TSM V5.2

2004-10-20 13:30:18
Subject: Re: Migrating to TSM V5.2
From: "Meadows, Andrew" <AMeadows AT BMI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 20 Oct 2004 12:14:57 -0500
I have a 45 GB database and had the same results around 20 minutes and
we were up and ready to roll. This was from version 5.2.1.1 to 5.2.3.0
on AIX 5.1

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sam Sheppard
Sent: Wednesday, October 20, 2004 12:03 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Migrating to TSM V5.2

---------------------------- Top of message ----------------------------
>>--> 10-20-04  10:01  S.SHEPPARD     (SHS)    Re: Migrating to TSM V5.2

We recently migrated from TSM 5.1.8 to 5.2.3 on z/OS 1.4 and it only
took around 20 minutes.

Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
-----------------------------------------------------------------------`


---------------------------- Top of message ----------------------------
>>--> 10-20-04  09:19  ..NETMAIL     ()     Re: Migrating to TSM V5.2
Date: Wed, 20 Oct 2004 12:17:28 -0400
From: "Jim Kirkman" <jmk AT EMAIL.UNC DOT EDU>
Subject: Re: Migrating to TSM V5.2 on z?OS
To: ADSM-L AT VM.MARIST DOT EDU
_________________________________Top_of_Message_________________________
________

I'm interested in finding out if anyone else has experienced the long
upgradedb Dave mentions with his 5.1.9 to 5.2.3 upgrade on Z/OS? While
we have no current plans for an upgrade (5.1.7.4 on Z/OS 1.4) we have
never experienced anywhere close to this 11 hr window with any of our
upgrades and our db is basically the same size. Would the fact that
we've never been at 4.2 (where the cleanup process first appeared I
believe) play into this?

Just curious, thanks!

David Moore wrote:

> Robert -
>
> Both TSM Tech Support and a local consultant recommended that we run
the 'clea
nup backupgroups' utility before we moved up to 5.2 (btw, mine is a z/OS
shop an
d we recently moved from 5.1.9 to 5.2.3).  This utility cleans up
orphaned datab
ase objects, which will extend your upgradedb run significantly if not
cleaned u
p.  My understanding is that the utility only became available with
5.1.73.  So,
 we upgraded from 5.1.65 to 5.1.9 back in June in preparation for the
recent upg
rade.  Then, a few weeks ago, we went to 5.2.3.
>
> Incidentally, the upgrade from 5.1.9 to 5.2.3 took quite a while for
us - abou
t 11 hours, because of the UPGRADEDB parameter.  My TSM DB is about 23
GB.  Othe
r TSM Admins have reported quicker upgrade rates, so your time may very
well be
better.  But, as a word of warning, allow a fairly large upgrade window,
so you
don't have to restore to your previous version - like I did the first
time I att
empted it.
>
> Good luck,
> Dave.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
Of
> Klein, Robert (NIH/CIT)
> Sent: Monday, October 18, 2004 9:27 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Migrating to TSM V5.2 on z?OS
>
>
> Believe it or not, we are still running TSM V4.2.2 on OS/390.  We are
> planning to upgrade our OS to z/OS and, along with that, to upgrade to
TSM
> V5.2.  I have heard that on some other platforms (e.g. AIX) one cannot
go
> directly from 4.2.2 to V5x.  I don't see anything about such a
restriction
> in the V5.2 for z/OS Quick Start manual, but wanted to check whether
anyone
> was aware of this issue for migration to 5.2 on z/OS.  Thanks for any
input.

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
919-698-8615

-----------------------------------------------------------------------`
********************************************
This message is intended only for the use of the Addressee and
may contain information that is PRIVILEGED and CONFIDENTIAL.

If you are not the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited.

If you have received this communication in error, please erase
all copies of the message and its attachments and notify us
immediately.

Thank you.
********************************************

<Prev in Thread] Current Thread [Next in Thread>