When I have done server-to-server EXPORT/IMPORT to servers with incompatible
media types, there were some differences in the logical/physical space
occupied on the target server. I assume that was due to differences in how
blocks are formatted with the different media, because testing restores
worked fine, and I got exactly the same number of files on the source and
target servers.
But your results are more disturbing, because the number of FILES is
different on the source and target server. Clearly there are files (or
objects) missing.
Some things to check that can affect the number of files after an IMPORT:
1) Did you specify ALLDATA or ALLACTIVE on your EXPORT NODE command?
2) Are ALL management classes/copy groups EXACTLY the same on the source and
target server, including the management class the directories will bind to?
If not, repeat the IMPORT with them EXACTLY the same.
3) Did EXPIRATION run on the target server before you took these statistics,
possibly deleting a lot of files?
4) Did you ever run CLEAN BACKUPGROUPS on your 4.2.x server? If not, (and
you backup WIn2K clients) I wonder if there are some "dead/disconnected"
files that were not really accessible and therefore did not export.
If you check all those things and still have no answer, what I would do is
pick a couple of filespaces, run SELECT to dump the contents of the BACKUPS
table for each of those filespaces, and write a script to compare the two.
That should give you an idea of which files are missing from the target
server.
If the results still don't make sense, I would open a PMR with IBM.
-----Original Message-----
From: Brian L. Nick [mailto:BRIAN.NICK AT PHOENIXWM DOT COM]
Sent: Monday, January 12, 2004 10:05 AM
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.
****************************************************************************
*******
|
