We can start with the SAN Client Guide: http://www.symantec.com/business/support/index?page=content&id=DOC3658
About your question of the STU's, if you use a FT Media you will use the same STU's you create for any Tape Drives or Disk you may have the only difference is that you will enable the SAN Client option on the client side and only if the comunication between SAN Client and FT Media Server across the SAN is healthy the backup will go through the SAN if for any reason the SAN client cannot see the FT Media Server through the SAN zoning the client will deliver the data through the TCP/IP network to the same FT Media Server but with this it will be just a regular backup.
The only special things about this is the SAN configuration\
FT Media Server:
1. You need at least 1 HBA and must be a Qlogic QLA24XX (there other few models that you can use but this is key to make this work)
2. You need to configure the Qlogic HBA with the Symantec Customized Drivers meaning you will unistall the Qlogic drivers and install the Symantec ones
3. Once the HBA Symantec Drivers are loaded you need to configure the HBA in to Target Mode so your SAN Clients can be zone to this special and dedicated HBA (This HBA haves nothing to do with the Tape Drives or Disk ones, must be a dedicated HBA for FT traffic)
4. Once Zoning is done check the NB FT Services are up mainly are 2: NBFTSVR and NBFDRV64, first one controls the configuration and second one HBA and PIPES
SAN Client:
1. You need at least 1 HBA (Any make and model) in initiator mode
2. You need to create the zones between SAN Client HBA and FT Media Server HBA
3. You will need to configure the SAN Client driver this changes based on the OS but you will find this in the Guide is quite simple but keep in mind that the idea is to trick the OS and make it think it haves its own tape drives (PIPES) but really are channels or pipes to the FT Media Server.
4. Once zoning is done you need to enable the SAN Client with bpclntcmd -sanclient 1, this will tell to the client that it will first try to run an SAN backup and if fails can use regular TCP/IP, this also can be change to instead of using the IP network to just fail.
5. Confirm the SAN Client service is up and running.
Once this setup is done you can run a couple of commands from the FT Media Server to confirm you can see the client:
nbftconfig -listactive [-C <client name> -verbose]
nbftconfig -listtargets
nbftconfig -[lc]listclients -C <client name> [-verbose]
nbftconfig -listclients -Me <FT Media>
nbftconfig -rescanclient <client name>
nbftconfig -getconfig
This is only a quick look is a lot of work to do and highly recommend you to read the guide follow every single step.
And one final thing be sure your SAN team creates Alieases for each Media Server HBA other way if an HBA fails and needs to be replace you will need to rezone to every single client and is a pain.
