FYI, v5.1 supports server-2-server export-import in a single step; you no
longer need to run the intermediate data thru virtual volumes --- it works
abit like CMS-pipelines, once you get it setup on both sides, data flows
from server-a (node-data-on-tape input) to server-b
(new-node-data-on-new-tape). It's still a pain, but only half as much as
pre-5.1 days.
Also, there was an earlier post, sometime in the last year, where someone
successfully transferred their TSM db from one Unix flavor to another...
don't recall who (or how), but they reported success!@!
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 AT ayett DOT 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 AT VM.MARIST DOT EDU]On Behalf Of
Prather, Wanda
Sent: Friday, November 22, 2002 12:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Migration from AIX to Solaris
You can do server to server export/import of the data now, with a DRM
license, using server-to-server virtual volumes.
It's just a pain to set up, and takes QUITE some time: You have to read the
data on your source system (EXPORT), transmit it to the new server via
TCP/IP, which writes it out on your target server; then you reimport it to
the target server, which reads it again and writes it out to the target
storage pool.
-----Original Message-----
From: Allen Barth [mailto:allen.barth AT DB DOT COM]
Sent: Friday, November 22, 2002 11:50 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Migration from AIX to Solaris
Wanda,
I agree with what you've stated, and will admit I hadn't thought it
through to the tapes. But as you say even if it did work, it would be
unsupported.
I thought I read something somewhere about a 'no tape server to server
export/import' feature. That would aid moving the data and rebuilding
the db, but it would still take some time to finish.
Regards,
Al Barth
"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/22/02 10:37 AM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Migration from AIX to Solaris
Al,
As far as anything I have ever read here and in the manuals, moving the DB
across OS's is NOT supported.
What you describe will work going from AIX to AIX, but if it works going
from AIX to Solaris, it's an unsupported accident.
The other issue is the data that exists on tape. If you were able to NFS
mount the DB to Solaris and use it, then what happens when you try to do a
RESTORE? You are using a TSM-on-Solaris tape driver to read data that
was
written with TSM-on-AIX tape drivers. I don't know if that is feasible
and
again, it isn't supported if a problem does occur.
I've heard that somewhere in 5.2 or higher Tivoli is planning something to
help moving a server across platforms, but we aren't there yet.
-----Original Message-----
From: Allen Barth [mailto:allen.barth AT DB DOT COM]
Sent: Friday, November 22, 2002 11:22 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Migration from AIX to Solaris
Are you saying that the internal format of the db changes between OS's?
If not, I wonder if this would work:
Install ITSM on Solaris
Export filesystems on AIX containing db and log areas
NFS mount those filesystems to Solaris
Update dsmserv.dsk on Solaris to point to NFS db and log areas
Insights, ideas, gotcha's all welcome.
Al Barth
"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
11/22/02 09:41 AM
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Migration from AIX to Solaris
The big obstacle here is no, you can't move a TSM DB across platforms.
You can EXPORT the definitions, like policies, mgmt classes, schedules,
admins, etc. and reimport them to the new server; you can EXPORT and
IMPORT
the client data as well, but this is really rebuilding the DB on the new
server as the IMPORTS occur; and it's obviously time-consuming.
There are two ways to approach the move: some people just start backups
on
the new server, leave the old one around for a while until the data ages
enough to be useless, then shut it down. Other people try to do the
EXPORT/IMPORT thing. Your decision will depend on your circumstances, how
much time you have, and how much backup & archive data.
To do the EXPORT/IMPORT, you either have to have compatible media, or use
server-to-server virtual volumes to transmit the data from one TSM server
to
the other. (This requires a DRM license, I think for the target server.)
As far as using the same library, the answer is "probably". I don't
know
if you can share the 3583 with TSM library sharing, if so that would be
ideal as it would let you use the drives as needed. The other alternative
is to physically share the library and dedicate some drives to the new
server and some to the old server until you get all the data moved. Don't
know enough about the 3583 to get further than that.
That's hardly a complete answer, but maybe it will get you on the road to
the next set of questions....
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
-----Original Message-----
From: Doug Baker [mailto:dbaker AT WESLEYAN DOT EDU]
Sent: Friday, November 22, 2002 8:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Migration from AIX to Solaris
Hi everyone,
Currently we're running TSM 4.2.3.0 on AIX, attached to an IBM 3583
library. I'm curious about the prospects of migrating the TSM system
from AIX to Solaris.
1. Is it feasible to do this with the same library? (does the existing
data on the 3583 tapes need to be converted, or can a TSM database be
exported from AIX to Solaris, and the new server read from the existing
data?)
2. Is there a guide to doing this with the new versions of TSM? I recall
folks talking about an old ADSM Redbook, but I don't know if the same
rules apply to TSM.
I imagine this is a vast topic, so I'll start with these questions.
Thanks!
Doug
dbaker AT wesleyan DOT edu
|
