ADSM-L

Re: export/import

2003-11-13 05:48:29
Subject: Re: export/import
From: John Naylor <john.naylor AT SCOTTISH-SOUTHERN.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 13 Nov 2003 10:47:33 +0000
Joni,
If your tms is DFRMM there should be no problem about reading another
systems tape.
The problem would come if you wanted to write to it.
John




Joni Moyer <joni.moyer AT highmark DOT com>@vm.marist.edu> on 11/12/2003 
07:01:11
PM

Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>

Sent by:    "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>


To:    adsm-l AT vm.marist DOT edu
cc:
Subject:    Re: export/import


I can write to tape, but since this concerns tsm on the mainframe and the
stk silos are run with tms, I don't think that I can remove one tape from
the test silo arena and have it read in the production tms.  The production
tms won't recognize the tape volser and I don't think this will work...

Also, is the data deleted from the original tsm server or is it just a
copy?  I don't want to lose important data while trying to do this.

Thanks!


***************************************************************
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
joni.moyer AT highmark DOT com
***************************************************************



             "Prather, Wanda"
             <Wanda.Prather@JH
             UAPL.EDU>                                                  To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     Re: export/import


             11/12/2003 01:29
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






If you're just trying to move some client data from one TSM server to
another, you also have the alternative of just using a tape!

Run EXPORT on the first TSM server, write the data to a tape.
Run IMPORT on the second TSM server, specify the volser of that tape.

That's all there is to it!
It's much faster than using server-to-server communication, because with
server-to-server, you have to transmit the data via TCP-IP.

The only reason you MUST use server-to-server for export/import, is if you
have no compatible media that both servers can read/write.



-----Original Message-----
From: Joni Moyer [mailto:joni.moyer AT HIGHMARK DOT COM]
Sent: Wednesday, November 12, 2003 1:00 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: export/import


Hello all!

I am just trying to get a better idea of how export/import data between 2
tsm os/390 servers works.  I know that in order to do this I will have to
create server to server communication.  I will then export the data for
certain nodes onto virtual memory.  What virtual memory is used?  How does
tsm know where to put this information?  When tsm exports data, does it
just make a copy of the information from the originator and then import the
copy onto the new server(location) or does it delete the information off of
the originating server?

Also, do I have to have the exact same management classes defined on the
server that will import the data or can I reassign a new management class
name to the files and directories?  If I don't have the same management
class defined will it get the default management class for that policy
domain?  Do I have to have the same policy domain and policy set as well?
I want it changed when I move them from test to production, but I wasn't
exactly sure how this would work...

Thanks for any input you might have on this topic!


***************************************************************
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603 **New as of 11/1/03
Fax:(717)302-5974
joni.moyer AT highmark DOT com
 ***************************************************************



**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************