> He is correct.  In order for NBU to backup like a local device, which is
> what you want in a SAN environement, you have to designate a storage device
> for each of your SAN media servers.

...

Thanks for the clarifications..

One more question - our environment will have a master server, a
secondary, and 5 SAN media servers. All servers are SAN-attached to the
tape drives.

Is there any functional difference between the secondary and the SAN
media server?

What I'm getting at is if I set the classes so that they can write to
'Any_available' storage unit, will the SAN media servers potentially get
used by other clients in the same way that the secondary server gets
used?

What I would LIKE to set up is to have non SAN-attached clients back up
through the master or secondary servers ONLY, and have the SAN media
server systems back themselves up ONLY.

Compounding this is that we will have three storage units available, a
total of 15 drives shared using SSO.

If I just set ALL classes to use 'Any_available' storage unit, will the
non SAN-attached clients potentially write to the SAN media servers?

The alternate approach looks a little ugly - setting up specific classes
for the SAN media servers so that they write to specific storage units,
and setting those storage units up to be on-demand only. This will work,
but the number of extra classes required to do this might get silly....

Cheers,

Ross

-- 
Ross Parker            |      UNIX Sys Admin, Perl and C,
Systems/Network Admin  |        Networking and security
Telus Mobility         |
                       |      Lisp has all the visual appeal of oatmeal
parker AT bctm DOT com        |   with fingernail clippings mixed in (Larry 
Wall)