We have a Storage Pool hierarchy something like:
DISK Stgpool (noliimt) --> File Stgpool (2GB limit) --> Tape Stgpool
(nolimit)
Clients backup to DISK, files smaller than 2GB migrate to "File"
stgpool, everything else migrates to Tape.
We've changed the MAXSIZE to 2GB and wanted to move all files from Tape
that are smaller than 2GB to the File Stgpool. This can be done by
moving everything to DISK and let migration handle it.
I thought it would be more efficient to just move this data to the File
stgpool but ran into the following error:
ANR1150W Move data process terminated for volume VOLNAME -
unable to move file to target storage pool due to
exclusion by size.
So I thought it was weird that Migration will honor the Nextstgpool when
a maxsize is set but MOVE DATA does not.
(Also client backups/archives will honor the nextstgpool).
Along with MOVE DATA, MOVE NODEDATA and RECLAMATION also do not work in
this scenario.
I called Tivoli Support and they said working as designed and are going
to update the documentation to state this.
My questions are:
- does anyone else think this is working a bit weird (ie.
Migration and client sessions work fine when writing to a stgpool with a
maxsize and nextstgpool but move data, move nodedata and reclamation do
not).
- Any other (efficient) way of doing what I want - move the
small files from tape to the file pool
Thanks,
Tim Rushforth
City of Winnipeg
