[Veritas-bu] STU usage with SSO

This is all correct except one minor point that's a little foggy below.
MULD has been changed since it was first released so that, in the event a
slave's drives are all down, it will go ahead and back up to another media
server using the normal rules.  When MULD was first released, backup jobs
for the slave would fail if all its drives were down.  I can't recall
whether it was a patch that changed this, or going from 3.2 to 3.4.

Thanks,
Gregg Yurchak
VERITAS Professional Services
Biloxi, MS
Cell:   228.324.6939
Office: 228.575.6299


-----Original Message-----
From: scott.kendall AT abbott DOT com [mailto:scott.kendall AT abbott DOT com] 
Sent: Wednesday, November 28, 2001 5:58 PM
To: Prasad Chalikonda
Cc: veritas-bu
Subject: Re: [Veritas-bu] STU usage with SSO


You need an STU or the media server won't be used.  That's what ties the
NetBackup component and the Media Manager component together to make the
whole
thing work.  You have one of two options.

Configure it as "on-demand" in which case only those clients specifically
calling it at the class and/or schedule will use it.  The advantage is that
you guarantee no clients will use this media server unless you have directly
told them to.  The disadvantage (in this release) is that you can only
specify
one, so if the STU is unavailable for some reason, the backup will not go to
another media server and will fail.

Or, don't configure it as "on-demand", in which case anyone can use it.  The
advantage here is that you don't need a separate class for each media
server.
You can put one or more media servers in a class and have the STU set to
"any
available".  If each media server has been told it must use local drives,
the
media server will use itself to back itself up.  If you have not configured
the media server with the "must use local drives" option it could back up to
any media server.  If it's drives are down, it will use another media server
(and go over the network) instead of just failing.  The disadvantage is that
you can't guarantee another client won't backup through this media server.
You could put it last in the STU list alphabetically and hope that no
clients
use it, but that's all.


- Scott



 

                    Prasad Chalikonda

                    <prasadchalikonda@        To:
scott.kendall AT abbott DOT com                                          
                    yahoo.com>                cc:     veritas-bu
<veritas-bu AT mailman.eng.auburn DOT edu>                    
                                              Subject:     Re: [Veritas-bu]
STU usage with SSO                          
                    11/28/2001 11:48

                    AM

 

 






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.







_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu