ADSM-L

Re: Expiration not working

2000-04-19 17:57:38
Subject: Re: Expiration not working
From: Matthew Glanville <matthew.glanville AT KODAK DOT COM>
Date: Wed, 19 Apr 2000 17:57:38 -0400
Had this problem with ADSM 3.1.2.50 on Solaris 2.6, and have it with TSM
3.7.2 on Solaris 2.6
as well.

It didn't show it's ugly head until a bunch of archives that were
archived 1 year ago started to expire.  It seems to have a real problem
on nodes that have daily automated archives of things like log files,
where there is alot of repitition.

Apparantly there is a fix in ADSM 3.1.2.55, a skipfiles=yes option for
expire inventory, too bad I went to TSM 3.7.2 with no fix...

In the readme for ADSM 3.1.2.55
IY06778 MULTITHREADED EXPIRATION RUNS VERY SLOWLY, BITFILES EXAMINED
INCREMENT VERY SLOWLY

Seems like for every archived directory, it has to examine every other
archived directory with that same path or beneath it to verify if it can
be expired or not.  To avoid this use a skipdirs=yes option.  I don't
know if it works or not.

Also fter a week of expiring my database buffer requests went through
the roof

         Total Buffer Requests: -994,372,051

--
matthew.glanville AT kodak DOT com
matthew.glanville AT kodak DOT com
(716) 477-9371 phone
(716) 477-5241 fax
<Prev in Thread] Current Thread [Next in Thread>