Scott was correct.

You still have to have at least one storage unit per media server.
Set the one on the SAN media server to "on demand only"

You will still want a separate class for the SAN media server.
Specify to use it's local storage unit.  You probably want to do the
same for all media servers.

Set up a class for the clients, and direct them to "any available".

You don't need MUST_USE_LOCAL_DRIVE.

Using the above configuration, all media servers will backup locally,
and network clients may backup to any EXCEPT the SAN media server,

L

P.S.  Storage Unit Groups are coming soon.  Instead of saying "any
EXCEPT these", you can group storage units together (say all of them
on a certain network) and point at that object.  And you can
prioritize usage (use local drives if available, network if not) which
is pretty cool too.


Prasad Chalikonda writes:
> Scott,
> 
>    Had to read the NBU Data Center Admin Guide (Pg. 30) and the SSO 
> guide (Pg. 58) about 5 times to figure this out. According to what I 
> understood, you and others are right.
> 
>  From Admin Guide: -
> Using "on-demand":
> Specifies whether the storage unit is available only on demand (that is, 
> only when a class
> or schedule is explicitly configured to use this storage unit). Clear 
> the box (default), to
> make the storage unit available to any class or schedule.
> 
> But you confused me with the the MUST_USE_LOCAL_DRIVE parameter.
> 
>  From SSO Guide: -
> In NetBackup Release 3.4 and Later
> The MUST_USE_LOCAL_DRIVE parameter was introduced to make directing a 
> server to
> use its own drives much easier. By adding this option, a backup of a SAN 
> media server
> (see page 57) will send the data over the SAN to a local drive.
> 
> So I guess what you described pertains to 3.2. With 3.4, all you need to 
> do is have that parameter in bp.conf and the server will back up locally.
> If this is true, all we need to do is use this parameter in bp.conf. 
> This eliminates the need for a separate STU, eliminates the need for a 
> separate class, and I don't have to worry about the SAN server (which 
> has about 80G of data) backing up other clients. 
> 
> Am I making sense?
> 
> Thanks very much.
> Prasad.
> 
> 
> scott.kendall AT abbott DOT com wrote:
> 
> > I don't think the product is smart enough to tell the difference between a 
> > SAN
> > media server and a normal media server.  I think it's just a licensing 
> > thing.
> > 
> > If you don't make the STU for the SAN media server "on-demand" it will be 
> > used
> > by clients.
> > 
> > You also have to put the SAN media server in a class where the STU is
> > specifically used instead of "any available".  This is true even if you are
> > forcing media servers to use themselves ("must use local drive").  If you 
> > have
> > this option on and have the STU configured as "on-demand" and don't specify
> > the STU (i.e. leave "any available") the backup will remain queued until the
> > window ends and then it will fail.
> > 
> > 
> > - Scott

-- 
Larry Kingery 
             "Time is the beauty of the road being long."