Merry Christmas, or rather Happy Boxing Day, to all. I have a new V6 TSM
server under my tree. I used the media method, and it worked. Still
sorting out a number of lesser issues. With a 90GB databse, the extract
took 3.5 hours and the insert took 12.5 hours, for a rate of about
6gb/hour, which is within the range the documentation says to expect.
The "media" was a devtype=file RAID array mounted via NFS, which worked
fine. The whole process took quite a bit longer, because of the work
necessary between the extract and the insert steps to redefine the disk
space from the V5 DB and logs for V6 use. In V5 we had been using Raw
Logical Volumes for DB and Log, and I had to define filesystems. Unix
permissions were also a pain, going from running V5 under the root user,
to V6 under a non-root user. No rocket science here; you just have to
slog through a whole bunch of routine Unix permission issues.
1. You will need more disk space than you thought. Have extra on hand.
2. Do not ignore the time it will take you for the manual steps. Add a
number of hours to your downtime window. IBM's time estimates for the
extract and insert steps are fairly accurate, but they do not take into
account your time performing manual steps.
3. The following is left out of the Upgrade manuals: Before extracting
the database, you must see document
http://www-01.ibm.com/support/docview.wss?uid=swg21443606
which says to do the following before extracting the database:
export DSMSERV_DIR=/usr/tivoli/tsm/upgrade/bin
4. I think I am seeing some V6.2.3 issues that are fixed in 6.2.5. I am
considering a quick update to V6.2.5. I stumbled across a GUID string
compare issue that was supposedly fixed in 6.2.2, described in APAR
IC68005. This prevented me from running dsmapipw to set the API password
for database backups. TSM Service directed me to the local fix described
in IC68005, which worked, which was to add DBMTRUSTEDGUIDIGNORE YES to
dsmserv.opt.
5. MEMORIZE the upgrade manual! Print the relevant chapter for your
scenario and check off the steps. About halfway through, I got tired and
my brain turned to jelly, and I forgot where I was. Having a paper
record of where you are will be very helpful. This TSM V6 upgrade thing
is a marathon. Do not embark on it unless you are very prepared,
organized, and well-rested.
This is the only time I will do this. Our other TSM5 server is being
"upgraded" by the replacement method, and it's replacement is already up
and running, with clients being moved over piecemeal. Some by export,
and some by a new full backup. It was older hardware that would not have
been capable of running TSM6. The server I just upgraded in-place was
newer and is doing OK on TSM6. Comparing the two methods, I can
recommend this in-place upgrade if you have a large number of clients.
You don't have to change anything on the clients, of which this server
has about 1,000.
Roger Deschner University of Illinois at Chicago rogerd AT uic DOT edu
============== Chicago: What other great city would erect ==============
=========== its statue of Abraham Lincoln in Grant Park, and ===========
============= its statue of Ulysses Grant in Lincoln Park? =============
On Tue, 25 Dec 2012, Lee Calhoun wrote:
>Hi Roger,
>
>I did a migration from TSM 5.5.20 to 6.2.2.2 back in 2011. I tried to use the
>media method, but it did not work. I then learned of APAR IC61396, which said
>that our current version of TSM (5.5.2.0) does not support the media method.
>This was 18 months ago, and I don't know if that APAR has since been updated.
>Since you are at 5.5.1.0 you might also be affected.
>
>At the time the consultant we were using told us in his experience most people
>use the network method for this type of upgrade. I ended up doing the network
>method and it worked just fine.
>
>Good luck with it in any case,
>
>Lee
>Lee Calhoun
>Lead Systems Engineer,
>Storage & Backups Group
>Columbia University Information Technology
>612 West 115th Street, Room #703
>Mail Code: 6001
>New York NY 10025-7799
>phone: 212-854-5119 fax: 212-662-6442
>email: Lc7 AT columbia DOT edu
>
>----------------------------------------------------------------------
>
>Date: Sun, 23 Dec 2012 08:53:59 +0000
>From: Steven Langdale <steven.langdale AT GMAIL DOT COM>
>Subject: Re: Happy Holiday TSM Server upgrade V5 to V6
>
>Not me Roger, but good luck too you and I hope it goes well!
>
>Keep us informed how you are getting on, I'd be interested in how long it
>takes.
>
>All the best, Steven.
>On Dec 23, 2012 4:16 AM, "Roger Deschner" <rogerd AT uic DOT edu> wrote:
>
>> Anybody else out there spending the holiday upgrading a TSM V5 server
>> to TSM V6? The one I'm doing has a 150GB database, and I'm using the
>> "media method", so it's going to take a while. It's going from
>> V5.5.1.0 to V6.2.3.0, on AIX 5.3. This was the only time I could get
>> permission to bring this server down for several days.
>>
>> No huge problems yet; just wondering how many others out there are
>> doing the same thing right now?
>>
>> Roger Deschner University of Illinois at Chicago rogerd AT uic DOT
>> edu
>> ===== While it may be true that a watched pot never boils, the one
>> ===== ==== you don't keep an eye on can make an awful mess of your
>> stove. ==== ========================= -- Edward Stevenson
>> ==========================
>>
> -----------------------------
>
>Date: Sun, 23 Dec 2012 13:20:55 -0500
>From: Zoltan Forray <zforray AT VCU DOT EDU>
>Subject: Re: Happy Holiday TSM Server upgrade V5 to V6
>
>I have done both ways. Put up a 6.1 server new and all new TSM requests
>went there. Then came new 6.2 servers and migrated off some 5.5 servers via
>exports.
>
>Most recently was rebuilding one of the old empty 5.5 machines with more
>memory and latest RedHat, restored 5.5 server DB to it, installed 6.3 and
>upgraded.
>
>-------------
>Zoltan Forray
>TSM Software & Hardware Administrator
>Virginia Commonwealth University
>UCC/Office of Technology Services
>zforray AT vcu DOT edu - 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
> On Dec 23, 2012 1:04 PM, "Skylar Thompson" <skylar2 AT u.washington DOT edu>
>wrote:
>
>> Me too. When we went from v5->v6 we ended up going with a new system
>> and migrating backups gradually using EXPORT NODE to avoid the lengthy
>> database migration. I'd be curious to know if we really did save a lot
>> of time, since our databases were about the size of yours.
>>
>> On 12/23/2012 12:53 AM, Steven Langdale wrote:
>> > Not me Roger, but good luck too you and I hope it goes well!
>> >
>> > Keep us informed how you are getting on, I'd be interested in how
>> > long it takes.
>> >
>> > All the best, Steven. On Dec 23, 2012 4:16 AM, "Roger Deschner"
>> > <rogerd AT uic DOT edu> wrote:
>> >
>> >> Anybody else out there spending the holiday upgrading a TSM V5
>> >> server to TSM V6? The one I'm doing has a 150GB database, and I'm
>> >> using the "media method", so it's going to take a while. It's
>> >> going from V5.5.1.0 to V6.2.3.0, on AIX 5.3. This was the only
>> >> time I could get permission to bring this server down for several
>> >> days.
>> >>
>> >> No huge problems yet; just wondering how many others out there
>> >> are doing the same thing right now?
>> >>
>> >> Roger Deschner University of Illinois at Chicago
>> >> rogerd AT uic DOT edu ===== While it may be true that a watched pot
>> >> never boils, the one ===== ==== you don't keep an eye on can make
>> >> an awful mess of your stove. ==== ========================= --
>> >> Edward Stevenson ==========================
>> >>
>>
>>
>> --
>> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
>> -- Genome Sciences Department, System Administrator
>> -- Foege Building S048, (206)-685-7354
>> -- University of Washington School of Medicine
>>
>
> -----------------------------
>
|
