To whom it may concern;
We run reclaims manually at this time do to tape drive constraints. I
was running reclamation earlier which I started by updating the
sequential storage pools reclaim threshold from 100% to 95%. I cancelled
the job to free up drives for tape loading/unloading. Since that ti
To Whom It May Concern:
Expiration ran over 24 hours yesterday. I cancelled it when the DB
backup job started. We recently migrated 30-40 volumes from an old
sequential pool that became went into pending. About 30 volumes passed
the re-use delay period and went to scratch 2 days ago. I was wonderi
To Whom It May Concern:
Starting two days ago our daily inventory expiration job began ran over
24 hours. Previously it ran for 2-4 hours. The number of objects
processed was anywhere from 30,000-700,000 but usually was in the
250,000 range. Now it is processing 4,000,000 objects in about 24 hours
PROTECTED] On Behalf Of
Hughes, George
Sent: Friday, November 03, 2006 8:41 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Inventory expiration suddenly grew by order of magnitude.
To Whom It May Concern:
Starting two days ago our daily inventory expiration job began ran over
24 hours. Previously it ran for
Is TSM planning on adding data deduplication similar to avamar? I
understand how TSM does not duplicate data now but minor edits in files
or simple file name changes would result in additional copies of the
entire file using TSM today.
We recently had a pitch from EMC on avamar. I can think of som
