You are absolutely correct on that statement. Migration (for performance
reasons) does NOT reconstruct aggregated bitfiles. Thus expired (or
reclaimable space) in the aggregate is not 'reclaimed' at the point of
migration. One of the chief reasons for this, other than performance, was the
th
At 10:26 AM 4/26/2009, Nick Laflamme wrote:
On Apr 26, 2009, at 9:03 AM, Remco Post wrote:
On Apr 26, 2009, at 12:10 , Peter Buschman wrote:
Apologies if this is a well-known question but I am scratching my
head trying to answer it.
Basically, what I want to know is if a migration job in TSM
On Apr 26, 2009, at 9:03 AM, Remco Post wrote:
On Apr 26, 2009, at 12:10 , Peter Buschman wrote:
Apologies if this is a well-known question but I am scratching my
head trying to answer it.
Basically, what I want to know is if a migration job in TSM job will
also migrate expired data on the vo
On Apr 26, 2009, at 12:10 , Peter Buschman wrote:
Apologies if this is a well-known question but I am scratching my
head trying to answer it.
Basically, what I want to know is if a migration job in TSM job will
also migrate expired data on the volumes it is migrating. In a
sense, I am wonderin
Apologies if this is a well-known question but I am scratching my
head trying to answer it.
Basically, what I want to know is if a migration job in TSM job will
also migrate expired data on the volumes it is migrating. In a
sense, I am wondering if part of the effect of reclamation can be
achiev
