My best guess without additional details being given is you have different
reclamation
thresholds for each of these storage pools. The difference is probably
expired or
deleted files in an aggregate on the copy storage pool that are not in the
primary
pool because reclamation and aggregate reconstruction has already occurred
in the primary storage pool.
David Bohm
TSM server development
email - [EMAIL PROTECTED]
Sergio Cherchyk <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 12/27/2000
09:51:38 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: copy pool
Hi all.
I have two TSM servers installed in AIX 4.3 boxes with Sun libraries in
different sites. In my HQ I take almost all the backups and I do a daily
copy pool to the remote site.
The local server (HQ) is TSM 3.7.2 and the remote one is 4.2.0.
The problem is that my local backup pool has 2.7 TB of data while the
remote pool has 3.7 TB. I expected a differential in the remote pool but
1TB (~30% more) seems to me too much for an overhead.
Questions:
How does TSM handle the expirations in a copy pool?
It is normal the overhead that I'm seeing?
If it is not, what can I do to reduce it?
Thanks to all.
--------------------------------------------
Sergio R. Cherchyk
Arquitectura Tecnol�gica - Midrange
Banco R�o de la Plata S.A. - Grupo BSCH
Mire 480, 2do piso - 1036 Cap. Fed.
Argentina
Tel. (054)-11-4341-1643
Fax. (054)-11-4341-1264
--------------------------------------------
