Text item: Body.822
To have full manual control over the expire inventory process, put
'expinterval 0' in the server options file;  you must then run the 'expire
inventory' command periodically.

The reclamation process is an internal driver of the 'move data' command,
and is single threaded.  You can do much the same thing manually by issuing
the 'move data' commands yourself.  Set up some kind of automation or
script to do 'query volume', capture the output, locate which volumes are
low usage, and issue as many simultaneous 'move data' commands as you want.
 Some of these commands might conflict with each other - i.e. moving tapes
a & b where a file spans both tapes.  I don't know how to avoid it, but
also, the server should be able to handle it gracefully.

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.
_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: Expiration and Reclamation...
09-12-96 03:06 PM

Date:         Thu, 12 Sep 1996 15:06:15 -0500
From:         LAbbinante <LAbbinante AT ual DOT com>
Subject:      Expiration and Reclamation...
To:           Multiple recipients of list ADSM-L <ADSM-L AT vm.marist DOT edu>

Good afternoon all!
Is there any way to NOT have expiration to kick off every time the ADSM
server is cycled?  Also, is there any way to have more than one
reclamation process running to expedite the process?
Thanks in advance,
Larry Abbinante
labbinante AT ual DOT com