Rainer,
Here is the export command that we ran for this NT server
EXPORT NODE PHLHR FILES=* FILED=ALL TOS=AIXTSM-MAIN.
It is my understanding that this should move all of this nodes data.
When we move a W2K node I add the UNIFILES=* parameter.
I did notice that my 4.2 server might be having an expiration issue. I
just updated the client option file to look back at the old server and I
noticed that there were 1 active and 9 inactive copies for some of the
backup data for this node. The management class should be 1 active and 4
inactive. We have not made any changes to OS/390 server in months. Now I'm
wondering if I have an expiration issue....
YIKES, this like a stinking snowball rolling downhill....
- Brian
Brian L. Nick
Systems Technician - Enterprise Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900
E-MAIL: Brian.Nick AT phoenixwm DOT com
PHONE: (860)403-2281
"Rainer Holzinger"
<Rainer.Holzinger@UPM-K To:
ADSM-L AT VM.MARIST DOT EDU
YMMENE.COM> cc:
Sent by: "ADSM: Dist Subject: Antwort: Re:
Export / Import
Stor Manager"
<ADSM-L AT VM.MARIST DOT EDU>
01/12/2004 10:47 AM
Please respond to
"ADSM: Dist Stor
Manager"
Brian,
what exactly was the export command you entered?
Could it be that only active files have been exported/imported?
I don't know how inactive files are handled at export/import which have
been deleted from client. Are they exported?
regards, Rainer
Alexander
Verkooijen An:
ADSM-L AT VM.MARIST DOT EDU
<alexander@SARA. Kopie:
NL> Thema: Re: Export / Import
Gesendet von:
"ADSM: Dist Stor
Manager"
<[email protected]
T.EDU>
12.01.2004 16:41
Bitte antworten
an "ADSM: Dist
Stor Manager"
You're right, I hadn't noticed that. The number of files
should have been the same.
Regards,
Alexander
------------------------------------------------------------
Alexander Verkooijen
Senior Systems Programmer
High Performance Computing
SARA Computing & Networking Services
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
> On Behalf Of Brian L. Nick
> Sent: maandag 12 januari 2004 16:35
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Export / Import
>
>
> That was my original assumption but if you look at the 'q occ' results
> there is a discrepancy in the number of files as well. That is my main
> concern.
>
> Thanks,
> Brian
>
>
>
>
> "Alexander
> Verkooijen" To:
> ADSM-L AT VM.MARIST DOT EDU
> <[email protected] cc:
> L> Subject: Re:
> Export / Import
> Sent by: "ADSM:
> Dist Stor
> Manager"
> <[email protected]
> .EDU>
> 01/12/2004 10:30
> AM
> Please respond to
> "ADSM: Dist Stor
> Manager"
>
>
>
>
> I'm not sure but since the physical space occupied decreases
> could it be that the export/import process reconstruct the
> aggregates and thus removes any 'holes' you may have had
> in your aggregates on the OS/390 server?
>
> Regards,
>
> Alexander
>
> ------------------------------------------------------------
> Alexander Verkooijen
> Senior Systems Programmer
> High Performance Computing
> SARA Computing & Networking Services
>
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
> > On Behalf Of Brian L. Nick
> > Sent: maandag 12 januari 2004 16:05
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Export / Import
> >
> >
> > Good morning everyone,
> >
> > We are in the process of migrating from TSM 4.2.1.9 running
> > on OS/390 2.10
> > to TSM 5.2 on AIX 5.1. Due to incompatible media we are using
> > the server to
> > server export import process to move node data, however I am seeing
> > discrepancies in the amounts of data to move. Here is an
> > example from a 'Q
> > OCC" command:
> >
> >
> > q occ PHLHR (os/390 2.10 TSM 4.2 )
> >
> > Node Name Type Filespace FSID Storage Number of
> Physical
> > Logical
> > Name Pool Name Files
> Space
> > Space
> >
> Occupied
> > Occupied
> >
> (MB)
> > (MB)
> > ---------- ---- ---------- ----- ---------- ---------
> ---------
> > ---------
> > PHLHR Bkup \\phlhr\c$ 1 OFFSITE_- 14,214
> 1,950.01
> > 1,870.58
> > STK9840
> > PHLHR Bkup \\phlhr\c$ 1 STD_BACK- 928
> 2.06
> > 1.90
> > UP_DIRE-
> > CTORIES
> > PHLHR Bkup \\phlhr\c$ 1 STD_BACK- 13,286
> 1,949.20
> > 1,869.93
> > UP_STK9-
> > 840
> > PHLHR Bkup \\phlhr\d$ 2 OFFSITE_- 25,447
> 35,257.46
> > 35,020.67
> > STK9840
> > PHLHR Bkup \\phlhr\d$ 2 STD_BACK- 336
> 0.82
> > 0.77
> > UP_DIRE-
> > CTORIES
> > PHLHR Bkup \\phlhr\d$ 2 STD_BACK- 25,111
> 35,257.18
> > 35,020.44
> > UP_STK9-
> > 840
> >
> >
> > q occ (AIX 5.1 TSM 5.2)
> >
> > Node Name Type Filespace FSID Storage P Number of Physical
> > Logical
> > Name ool Name Files Space O
> > Space Oc
> > ccupied
> > cupied (
> >
> (MB)
> > MB)
> > ---------- ---- ---------- ----- ---------- ---------
> ---------
> > ---------
> > PHLHR Bkup \\phlhr\c$ 1 PRODCSP 11,810
> 1,144.67
> > 1,144.66
> > PHLHR Bkup \\phlhr\c$ 1 PRODOCP 11,810
> 1,144.67
> > 1,144.66
> > PHLHR Bkup \\phlhr\d$ 2 PRODCSP 15,472
> 4,738.94
> > 4,738.92
> > PHLHR Bkup \\phlhr\d$ 2 PRODOCP 15,472
> 4,738.94
> > 4,738.92
> >
> > Is there a known issue with exporting data from 4.2 to 5.2?
> > Any help is
> > greatly appreciated.
> >
> > Thanks,
> > Brian
> >
> >
> >
> >
> > Brian L. Nick
> > Systems Technician - Enterprise Storage Solutions
> > The Phoenix Companies Inc.
> > 100 Bright Meadow Blvd
> > Enfield CT. 06082-1900
> >
> > E-MAIL: Brian.Nick AT phoenixwm DOT com
> > PHONE: (860)403-2281
> >
> >
> >
> >
> > **************************************************************
> > *********************
> > CONFIDENTIAL: This communication, including attachments, is
> > intended only for
> > the exclusive use of addressee and may contain proprietary,
> > confidential
> > and/or privileged information. If you are not the intended
> > recipient, you are
> > hereby notified that you have received this document in
> > error, and any use,
> > review, copying, disclosure, dissemination or distribution
> is strictly
> > prohibited. If you are not the intended recipient, please
> > notify the sender
> > immediately by return e-mail, delete this communication and
> > destroy any and
> > all copies of this communication.
> >
> > **************************************************************
> > *********************
> >
>
>
>
>
>
>
>
> **************************************************************
> *********************
> CONFIDENTIAL: This communication, including attachments, is
> intended only for
> the exclusive use of addressee and may contain proprietary,
> confidential
> and/or privileged information. If you are not the intended
> recipient, you are
> hereby notified that you have received this document in
> error, and any use,
> review, copying, disclosure, dissemination or distribution is strictly
> prohibited. If you are not the intended recipient, please
> notify the sender
> immediately by return e-mail, delete this communication and
> destroy any and
> all copies of this communication.
>
> **************************************************************
> *********************
>
***********************************************************************************
CONFIDENTIAL: This communication, including attachments, is intended only for
the exclusive use of addressee and may contain proprietary, confidential
and/or privileged information. If you are not the intended recipient, you are
hereby notified that you have received this document in error, and any use,
review, copying, disclosure, dissemination or distribution is strictly
prohibited. If you are not the intended recipient, please notify the sender
immediately by return e-mail, delete this communication and destroy any and
all copies of this communication.
***********************************************************************************
|
