All,
I recently started to share a library between two TSM instances. I thought I calculated the scheduling needs/drives, scratch tapes etc. One thing I failed to plan for is now proving to be quiet a pain.
09/21/09 09:55:46 ANR1440I All drives in use. Process 13 being preempted by
higher priority operation. (SESSION: 23199)
09/21/09 09:55:47 ANR0409I Session 23199 ended for server MCTSM02
(Linux/x86_64). (SESSION: 23199)
09/21/09 09:55:48 ANR1020W Migration process 13 terminated for storage pool
DISKPOOL - process canceled. (SESSION: 22342, PROCESS:
13) I only have one HSM enabled client (I very thankful for this) associated with one of the TSM servers. I've configured the node on the server side to only use 1 mount point and I believe I set a very low priority on the nodes schedule (prob doesn't apply to the actual job). It would appear that the HSM client is seemingly mounting tapes etc virtually all the time. I'll admit that I'm not sure how it is supposed to operate but I do know that it seems to want to mount tapes throughout the day and it's schedule starts at midnight running once per day. The node is scheduled with this option
-[SIZE=-1]-subdir=yes -postschedulecmd="dsmautomig"[/SIZE]
1. TSM prioritizes restores so i suppose HSM falls into this category. Anyone know of a way I could make HSM be the lowest priority?
2. I'd like HSM to migrate files after the backup - I don't believe anyone is recalling files. What could cause it to run like this. I believe the HSM client v is 5.5.2
Thanks
I recently started to share a library between two TSM instances. I thought I calculated the scheduling needs/drives, scratch tapes etc. One thing I failed to plan for is now proving to be quiet a pain.
09/21/09 09:55:46 ANR1440I All drives in use. Process 13 being preempted by
higher priority operation. (SESSION: 23199)
09/21/09 09:55:47 ANR0409I Session 23199 ended for server MCTSM02
(Linux/x86_64). (SESSION: 23199)
09/21/09 09:55:48 ANR1020W Migration process 13 terminated for storage pool
DISKPOOL - process canceled. (SESSION: 22342, PROCESS:
13) I only have one HSM enabled client (I very thankful for this) associated with one of the TSM servers. I've configured the node on the server side to only use 1 mount point and I believe I set a very low priority on the nodes schedule (prob doesn't apply to the actual job). It would appear that the HSM client is seemingly mounting tapes etc virtually all the time. I'll admit that I'm not sure how it is supposed to operate but I do know that it seems to want to mount tapes throughout the day and it's schedule starts at midnight running once per day. The node is scheduled with this option
-[SIZE=-1]-subdir=yes -postschedulecmd="dsmautomig"[/SIZE]
1. TSM prioritizes restores so i suppose HSM falls into this category. Anyone know of a way I could make HSM be the lowest priority?
2. I'd like HSM to migrate files after the backup - I don't believe anyone is recalling files. What could cause it to run like this. I believe the HSM client v is 5.5.2
Thanks