Hi, we are just testing the migration of a TSM 5.1.9.5 (AIX 4.3) to a TSM 5.2.7.2 (AIX 5.2). So far everything seems OK, policies and data were exported and imported just fine, but I noticed a discrepancy in the file sizes shown in a select from contents for ALL files (data are from a ContenManager)! This is an example:
On the old TSM tsm: ECKWAND>select * from contents where file_name='/MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD' VOLUME_NAME: /tivoli1/stgpool/archiv_po4_1_file01 NODE_NAME: ARCHIV_PO TYPE: Bkup FILESPACE_NAME: /OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1 FILE_NAME: /MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD AGGREGATED: No FILE_SIZE: 56210 SEGMENT: CACHED: No FILESPACE_ID: 6 FILESPACE_HEXNAME: FILE_HEXNAME: After the import on the new TSM: tsm: TEST-KANDEL>select * from contents where file_name='/MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD' VOLUME_NAME: /usr/local/tsm/server2/data/apo4_01 NODE_NAME: ARCHIV_PO TYPE: Bkup FILESPACE_NAME: /OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1 FILE_NAME: /MC_ARCHIV_PO4_1/ MC_ARCHIV_PO4_1AKKDBJHB.DMD AGGREGATED: 124/256 FILE_SIZE: 11195180 SEGMENT: CACHED: No FILESPACE_ID: 1 FILESPACE_HEXNAME: FILE_HEXNAME: Note the difference in FILE_SIZE: 56210 vs. 11195180! This seems strange! And what does the difference in the field AGGREGATED mean (No vs. 124/256)? Interestingly enough, I can restore the object from the new TSM and inspect it in a viewer (it's a TIFF) just fine. The dsmc query shows it as: tsm> query backup "/OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1//MC_ARCHIV_PO4_1/MC_ARCHIV_PO4_1AKKDBJHB.DMD" Size Backup Date Mgmt Class A/I File ---- ----------- ---------- --- ---- API 55,858 B 03/25/01 00:11:12 MC_ARCHIV_ A /OBJRZ/FRN/ADSM/192.168.126.134/MC_ARCHIV_PO4_1/MC_ARCHIV_PO4_1/MC_ARCHIV_PO4_1AKKDBJHB.DMD Another thing is puzzeling me: the blank in the filename in the "select", which is not appearing in the "query backup" result. Any hints? TIA Andreas