Don't overlook that you want to make SURE that in a SAN environment, the stu
that is picked for a SAN client is the one that has that client listed as a
media server. Define one stu for each robot for that particular client at
most, with an appropriate number of drives, but don't allow it to just make
an alphabetical choice when picking the stu used. If it does not
consistently pick itself to backup through, then you will have to force it
to use its own stu by selecting it instead of "any available."

Remember, a stu is basically for load balancing purposes in a SAN
environment, so you can make these choices yourself. To load balance a group
of clients, you can move them from one robot to the other by changing the
robot number. You can choose how many tape drives each should use, moving a
higher number of drives to a specific client's stu. To do this correctly,
however, each client needs to have its own stu that lists a number of drives
that it should use a specific robot that it should use. And allowing the
software to override your careful planning is a BAD idea! Use the "any
available" option with extreme care and watch which media servers the
clients use carefully!


-----Original Message-----
What I would do is create 1 stu with 4 drives for each media server for each
32 drive robot.  Then a 2 drive stu for each media server for each 16 drive
robot.  Name the stus so they are picked out of the list alphabetically in a
manner that spreads the load nicely across the media servers and robots.
That
would give you a total of 40 stus.