I have my copypools set up to deliver most data to FILE device storage
pools. I used to use DISK, but FILE seems to replace DISK in many ways, so
I'm using that for a new server.
Alas, during backups, my consoles get over run with ANR8340I, 0511I, and
0514I messages
03/18/2009 09:50:37 ANR0514I Session 2581 closed volume
/tsmstg/part02/000001E0.BFS. (SESSION: 2581)
03/18/2009 09:50:37 ANR8340I FILE volume /tsmstg/part02/000001E0.BFS
mounted. (SESSION: 2581)
03/18/2009 09:50:37 ANR0511I Session 2581 opened output volume
/tsmstg/part02/000001E0.BFS. (SESSION: 2581)
03/18/2009 09:50:38 ANR0514I Session 2581 closed volume
/tsmstg/part02/000001E0.BFS. (SESSION: 2581)
FILE devices don't have Mount Retention settings; I can't ask TSM to leave a
volume open for 1 minute in case the client comes back again for it.
For the same of my activity log and my console sessions, is there a way to
tell TSM not to be so aggressive about dismounting and/or closing these
volumes every time a session hesistates for a moment?
Or should I just tell myself I'm abusing FILE devices and ought to use DISK
storage pools to receive incoming data?
Thanks,
Nick
|