Debra,
I just went thru an ADSM/MVS to ADSM/AIX conversion (110 clients, 600 GB
of stored client data). I was told by ADSM support that you cannot
restore the database between disparate systems (i.e. MVS and AIX) and
had to use the IMPORT/EXPORT facilities. This involved an EXPORT SERVER
on MVS, an IMPORT SERVER on AIX, and then doing the EXPORT/IMPORT on a
node by node basis to bring the client data over. We were able to get a
loaner 3490E (tabletop model with autoloader) and hooked it up the
RS/6000 - we did get a 3494 library with our RS/6000 but only put 3590
drives in it. Here are a couple of options to consider..
1) Scrounge up a 3480 or 3490 and hook it up to your RS/6000 (short
term lease, get a loaner box from IBM or somebody else, etc.)
2) If I'm not mistaken, I think you can put a channel card in an RS/6000
and hook it up to mainframe devices (i.e. 3480's, 3490's) If this is
true, you can hook up your RS/6000 to an available slot on a mainframe
tape controller, take one of the tape drives offline to MVS and use it
on the RS/6000 to do your IMPORTs
I did not have the opportunity to try out the FILE devclass, mainly
because of the size of some of the clients involved... not even sure it
would work between the different systems.
As far as thruput goes, this depends a great deal on the number and size
of the files being moved. Some of our larger Novell servers (800,000
files, 40 GB of data stored on ADSM) took up to 2 days to Export
(Imports were faster). Our Unix database servers, where most of the
files being moved are much larger (70-80 GB of data stored on ADSM),
only took 24-30 hours to Export and 16-20 hours to Import.
All in all, our conversion went well (especially given the short
timeframe we had to get it done) but I did run into some problems and
found some undocumented options that helped move things along. If
you're interested, feel free to contact me directly and we can discuss
these issues offline.
Tim Pittson
tpittson AT himail.hcc DOT com
>----------
>From: Debra Young[SMTP:djyoung AT VOYAGER DOT NET]
>Sent: Wednesday, November 06, 1996 5:45 PM
>To: Multiple recipients of list ADSM-L
>Subject: Re: adsm migration from mvs to aix server
>
>At 10:02 AM 11/4/96 PST, you wrote:
>>Debra Young asked about how to migrate data from an mvs server to aix server
>>...with no compatible devices.
>>
>>A couple thoughts...
>>
>>Probably your only option if you don't have compatible devices between your
>>MVS adsm server and your aix server...is to use the FILE devclass on both
>>MVS and AIX. Export data to the FILE devclass on mvs...this device class
>>emulates tape but puts the data on disk...these disk files then need to
>>be transferred across the network to the aix system and then imported with
>>the FILE devclass on the aix server.
>>
>>As export processing is very slow going, you should consider some
>>alternatives. For example, start client backups (a couple a day) to the
>>new aix server and let the majority of backup data on the mvs server
>>expire (so it doesn't have to be moved). Then you can export just
>>the archive/hsm data. Another option is to just take the ALLACTIVE
>>data (archive, hsm and only the most recent backup copy).
>>
>>hope this helps...greg tevis
>>
>>
>We are trying to figure out the 'best' way to get the data moved. What are
>the numbers for exporting data? We currently have lines that can transfer
>768kb/sec from the client to the server. However, we can move 100,000
>kb/sec from MVS to AIX (maximum numbers, of course). It would appear that
>exporting would be faster than a 'full' backup the first time the backup
>schedule runs.
>
>Another thing I was asked to look into is exporting by filespace, instead of
>node. We have one client that has 54G of archived data. If we went from
>MVS to AIX using the FILE devclass, wouldn't I have to have at least 54G of
>disk on both systems?
>
>Is there some way to use the network as the object of the FILE devclass? I
>was told about 'piping' data from one device to another. Obviously, I am
>not UNIX literate... If there is a way to use the network, not disk space,
>as the intermediary of the export/import, it would save time and storage
>space.
>
>Any help will be greatly appreciated!!
>
>
>Deb Young
>Dow Corning Corp
>
|
