I'm curious to hear from others about the length of time it takes
for expiration processing to run on their V2 servers.

We currently have a 30GB database and it seems to take as much
as twelve (12) hours to run 'expire inventory'. For each of the
last two days I've had to kill it after five or six hours, due to
the load it puts on the server.

The amount of time it takes seems to have increased quite a bit
in the last month, although I attribute that to the fact that our
ADSM server has now been in production for over one year, and
some of our retain versions parameters are set at 365 days.

As for the recent responses regarding V3, I haven't done much
with any of the GUI clients, so I can't comment on how those have
changed, but we are very encouraged by the performance
improvements brought upon by server file aggregation.

We are seeing as much as a five-fold increase in the data
transfer (wall clock) times for some backup sessions. One session
last night ran at 10+ GB / hr. over ATM. A similarly equipped V2
client and server averages 2-3 GB / hr.

 -- Tom

"If I could dot the 'i' in a Michigan     Thomas A. La Porte
 game and the good lord came to take me   DBA, Feature Animation
 the next day ... at least I could        DreamWorks SKG
 die happy." - Beano Cook, ESPN           <tlaporte AT anim.dreamworks DOT com>