Hi ALL!
We use IBM CM to archive, retrieve files on TSM.
Archive works in a pretty standard way to diskpool -> migrate to primary tape pool -> and backup primary stgp to copy pool on another DR TSM server.
Retrieve works as designed, as mentioned in this article
http://www-01.ibm.com/support/docview.wss?uid=swg21380647
just only from primary tape pool.
Is it possible to set up TSM server to balance retrieval request among primary and copy pool somehow? To better utilize drives on DR TSM server and speed up retrieval.
When capple of our volumes from primary pool became unavailable accidentaly we saw that some retrieve request's were redirected on copy pool. That was exactly I had asked about. May be the only way to do this is to make volume anavailable intentionally?
Thank you!
We use IBM CM to archive, retrieve files on TSM.
Archive works in a pretty standard way to diskpool -> migrate to primary tape pool -> and backup primary stgp to copy pool on another DR TSM server.
Retrieve works as designed, as mentioned in this article
http://www-01.ibm.com/support/docview.wss?uid=swg21380647
just only from primary tape pool.
Is it possible to set up TSM server to balance retrieval request among primary and copy pool somehow? To better utilize drives on DR TSM server and speed up retrieval.
When capple of our volumes from primary pool became unavailable accidentaly we saw that some retrieve request's were redirected on copy pool. That was exactly I had asked about. May be the only way to do this is to make volume anavailable intentionally?
Thank you!
