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