Hi Zoltan,
I've witnessed this too in the past when using EXPORT NODE and comparing occupancy between the two servers - I might expect the source server's data to occupy more space, and the target to occupy less space if, on the source server, data has been 'maturing' there and there might be some extra space taken by expired objects contained within larger aggregates (in the TSM internal storage sense) - during the export of the node's data, this effect would have been negated as the data is contained within newly created aggregates on the target server.
It seems like a reasonable explanation to me - anyone with a more intricate knowledge of TSM aggregation internals able to offer a more detailed reasoning?
Rgds,
| David McClelland
Storage and Systems Management Specialist IBM Tivoli Certified Deployment Professional (ITSM 5.2) SSO UK Service Delivery – Storage Services IBM Global Services – IBM United Kingdom |  |
| Zoltan Forray/AC/VCU <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 24/10/2005 15:23
|
|
I just moved a node from an MVS/zOS TSM server we are phasing out, to our
AIX TSM server.
I am wondering why the occupancy sizes are different. The file counts are
the same.
MVS TSM server (v5.2.4.2)
Backup Files 1,027,310
Backup Size 383.2GB
Archive Files 732,454
Archive Data 39.5GB
AIX TSM server (v5.3.1.3)
Backup Files 1,027,310
Backup Size 377.7GB
Archive Files 732,454
Archive Data 39.3GB
Difference 422.8GB (MVS) vs 417.0GB (AIX)
I have 6TB to move and am a little concerned about these "losses" !
