This doesn't make complete sense. How do I move it to different storage
pools ?
The configuration on the AIX TSM server is completely different than the
zOS TSM server. Different names, etc.
"Rushforth, Tim" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/03/2003 11:06 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: EXPORT NODE to SERVER question/issue....
When running an "EXPORT NODE xxxx TOSERVER=XXX", data ends up in the
storagepools specified in the policy domain for node xxxx on the target
server. This could be an archive pool for archive data. Data does not
end
up as one file - if you export 50 files, 50 files are imported on the
target
server.
It sounds like you are talking about virtual volumes - these do indeed end
up as 1 file in the archivepool of the destination server.
-----Original Message-----
From: Jim Sporer [mailto:[EMAIL PROTECTED]
Sent: June 3, 2003 9:43 AM
To: [EMAIL PROTECTED]
Subject: Re: EXPORT NODE to SERVER question/issue....
The data does go into the archive pool. The specific archive pool is
determined by the policy domain and management class. More info can be
obtained in the following redbook.
The ADSM Server-to-Server Implementation and Operation redbook
goes into this subject.
Jim Sporer
At 08:45 AM 6/3/2003 -0400, you wrote:
>Hmmmm......
>
>Thanks for the details.
>
>One question, you specifically said the "data ends up in your archive
>storage pool as a single file".
>
>Is this true about the ARCHIVE pool ? Why the ARCHIVE pool ? Which
>ARCHIVE pool ? Can I control this ?
>
>If this really is true, this is probably the cause of my problem since I
>have a very SMALL archive pool on the receiving server since I don't do
>much if any archiving there !
>
>
>
>
>Jim Sporer <[EMAIL PROTECTED]>
>Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>06/02/2003 05:16 PM
>Please respond to "ADSM: Dist Stor Manager"
>
>
> To: [EMAIL PROTECTED]
> cc:
> Subject: Re: EXPORT NODE to SERVER question/issue....
>
>
>When you do a server to server export the data ends up in your archive
>storage pool as a single file. If for some reason the export fails
before
>completion you lose everything. We had some rather large nodes that we
>exported that took upwards of 10 to 15 hours. We would occasionally have
>network problems that would require us to start from scratch. To get
>around the problem we started doing the exports by filespace.
>Jim Sporer
>
>At 04:07 PM 6/2/2003 -0400, you wrote:
> >I am now on my fourth attempt to do an EXPORT NODE to SERVER, from my
zOS
> >TSM server (5.1.6.4) to our AIX TSM server (5.1.6.2).
> >
> >The reason I am on my fourth attempt is that it seems to
> >quit/drop-dead/whatever for no apparent reason I can fathom.
> >
> >The last attempt, while the final status said "SUCCESSFULL", further
> >digging for an error message found one that said "INCOMPLETE" (not sure
> >why a previous "failure" still registers as "successfull" but I am not
> >concerned about this, right now).
> >
> >Eventhough each attempt seems to move some data, nothing seems to
appear
> >on the receiving end.
> >
> >My question(s):
> >
> >1. Where is the stuff being imported/exported going if it doesn't
seem
> >to appear on the other end ?
> >2. If it actually does send some files across and I run the EXPORT
> >again, does it just skip the files previously sent ?????
> >3. What if an *EXACT* copy of the file(s) I am export/importing
already
> >exists on the receiving end ? Does it ignore it ?
