Re: sequential devices.

The tape volume shows as status 'Filling'. This is normal and just tells
You
that ADSM will continue to write to this tape

Could You issue a
   QUERY STGPOOL
and have a look at the results. It should show something like

Storage      Device       Estimated  %Util  %Migr  High   Low  Next
Pool Name    Class Name    Capacity                Mig%  Mig%  Storage
                               (MB)                            Pool
-----------  ----------  ----------  -----  -----  ----  ----  -----------
ARCHIVEPOOL  DISK           3,500.0   74.5   74.5    90    70  ARCHIVETAPE
ARCHIVEPOOL  DISK           3,500.0   74.5   74.5    90    70  ARCHIVETAPE
ARCHIVETAPE  CARTRIDGE     28,000.0   20.3   20.3   100    99
BACKUPPOOL   DISK           3,500.0   89.2   89.2    90    70  BACKUPTAPE
BACKUPTAPE   CARTRIDGE     28,000.0   56.1   56.1   100    99

You can see the High Mig% and the Low Mig%. If these are still set to 90
for the High and 70 (as the installation default is if I remember right)
for the low ADSM does the following:

ADSM starts to migrate a storage pool at the moment it is used up as much

  as the High Mig% value (shown by the %Migr value) - here 90% for the Disk

  storage pools.
It will go on migrating until the storage pool is used less that the Low
  Mig% value of here 70% -  and the client filespace which is currently
  being migrated has been entirely migrated (this may lead to 0% uage of
  the pool being migrated, but the Low Mig% is just the value under which
  ADSM has to go, it does not need to come as close as possible to it).
  The data that was migrated is now on the 'Next Storage Pool' and usually
  erased from the original storage pool (may be changed with 'Cache=Yes'
  for that storage pool, so the data will live as long as possible of the
  disk, speeding up a possible restore - but it will require additional
  space in the ADSM database as the data is now held in two locations).

So if the 'end migration criteria' is reached, ADSM stops migrating,
  regardless how full the tape is at that moment.
  This is what I am sure You faced.
The next time a migration will start for this storage pool (and
  Collocation is set to No for the tape storage pool) I am convinced that
  exactly the tape volume which is currently not used up to 100% will be
  requested for mount and ADSM will continue writing to it.

Best regards

Andreas Peikert, Systems Programmer
   aMaDEUS Data Processing GmbH
   P.O. Box,   D-85424 Erding,   Germany
   Fon: +49 (0)8122 43-5805
   Fax: +49 (0)8122 43-3260
   email: apeikert AT amadeus DOT net