[ADSM-L] Question about "Storage hierarchy"

Dear all,

switching to an new employer allows me to read all^H^H^H some of IBM'sdocumentation about TSM ;-)

inside the server documentation there's a short description on "Example:How the server determines where to store files in a hierarchy" [1].within this there's written:

"If the DISKPOOL storage pool has no maximum file size specified, theserver checks for enough space in the pool to store the physical file.If there is not enough space for the physical file, the server uses thenext storage pool in the storage hierarchy to store the file."

=> does this really mean, that when one client is flooding my stagingpools the migration processes becme concurrent to new data that iswritten directly to the NEXTSTGPool, because the first pool is full? ifthe next pool has a limited number of mount points (e.g. tape drives)this will cause the next, eben bigger problem.


if so, what's the best practise to empty the staging pool?

- setting a max filesize does not solve the problem, especially if thereare many files- perhaps "DISABLE SESSIONS CLIENT" -- this seems to be no really goodanswer :-(


Thanks & best regards,
Bjørn

[1]http://pic.dhe.ibm.com/infocenter/tsminfo/v7r1/index.jsp?topic=%2Fcom.ibm.itsm.srv.doc%2Ft_volume_seq_define.html

[1] http://tinyurl.com/p23j5eo

--

Bjørn Nachtwey                    <mailto:bjoern.nachtwey AT gwdg DOT de>
Arbeitsgruppe IT-Infrastruktur               Tel. +49 551 201-2181
----------------------------------------------------- G W D G ----
Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen
Am Fassberg 11, 37077 Göttingen
E-Mail: gwdg AT gwdg DOT de                   Tel.:   +49 (0)551 201-1510
URL:    http://www.gwdg.de             Fax:    +49 (0)551 201-2150
Geschäftsführer:            Prof. Dr. Ramin Yahyapour
Aufsichtsratsvorsitzender:  Dipl.-Kfm. Markus Hoppe
Sitz der Gesellschaft:      Göttingen
Registergericht:            Göttingen  Handelsregister-Nr. B 598