>Its capabilities will be expanded -- it will be able to re-assemble and 
>re-split dumps, so the source and destination volume sizes need not match.  
>The >command will still be separate from the usual amdump runs, and won't do 
>the usual report-sending or log-rotating.

>To put it another way, amvault will benefit from the improvements being made 
>to how changers, devices and data are handled, but I won't have a chance to 
>address the higher-level questions of scheduling, metadata maintenance, 
>tertiary tape cycles, etc.

Good working Dustin. 
One more question on amvault what would be the result of calling 'amvault 
latest' for a giving configuration -  I would expect to 
get the most resent 0 dump on each volume in the disk list is that correct ?

-- GG