Hi Zlatko!
This is 'normal behavior'. When backups go to a 100% full diskpool TSM tries
to allocate storage in the nextstgpool defined for your diskpool, which is
probably your primary tapepool. So all backups are going to wait for
mountpoint in the tapepool. That's why the client backups seem to 'hang'.
Although migration kicks in and frees the diskpool, these clients will never
switch back to the diskpool.
You should always try to prevent a 100% full diskpool. I agree that this is
not always possible, unless you have a very large one. I have run into this
situation numerous times, which can result in very nasty problems (Oracle
databases stop working, because the archive logfiles are not backed up).
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines