Keith, yes, the TSM library client needs a FC connection to the drives yes
that you want it to use.
- imagine a library manager managing 80+ drives for 10+ other servers, and
> all data moving via this one LM, not a scalable solution
- Occam's razor applies
For as far as I know the data doesn't move via the LM, it just mounts the
drives on request, the LM is not in the data path.
> - HBA's with default firmware can only act as initiators, not as targets
This is true, but what does it have to do with a TSM LM? :-)
> - thus, the library manager can't receive any data from the other servers
I feel like I am missing something here, what's going on!? :-)
The problem is with things such as SA's, they can't run on a library client
for as far as I know.