ADSM-L

Re: Export / Import

2004-01-12 10:32:55
Subject: Re: Export / Import
From: Alexander Verkooijen <alexander AT SARA DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 12 Jan 2004 16:30:35 +0100
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.
> 
> **************************************************************
> *********************
> 

<Prev in Thread] Current Thread [Next in Thread>