".. but is it also updates for each time a volume is added or deleted
from a storagepool?"

Might consider doing a q volhist and check modification date on
volhist.out to get an answer if it gets updated..

-H.  

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Remco Post
Sent: den 25 april 2008 13:24
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] How long should we keep volhist?

Quoting Richard Sims <rbs AT BU DOT EDU>:

> On Apr 25, 2008, at 5:22 AM, Jim Young wrote:
>
>> Whats the knock on effect of not clearing your volhist anyway?
>> Short of getting a large text file hanging around.
>
> The large, flat file doesn't just hang around: it is completely 
> rewritten at each volume transition, where the TSM server has to run 
> through all its volhistory entries, format, and write each entry to 
> the file designated by the VOLUMEHistory server option - no matter how

> busy it is with other tasks.
>

Is this true? I know the volhist files are updated each time a database
backup is completed, but is it also updates for each time a volume is
added or deleted from a storagepool? Of course, the volhist table in the
db is continuously updated, but that should not be to big a problem
(well, after about 5 years or so it might).

Are there any other downsides we can think of?

>   Richard Sims  http://people.bu.edu/rbs/



-- 

Met vriendelijke groeten,

Remco Post, PLCS


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.