Hmmm... doesn't look like it's the same thing - this instance has
never, to my knowledge, been touched by the windows gui. Another odd
thing we found in testing last night - storage unit group containing 2
of our filers, primarily used to as a stu for ndmp 3 way backups (when
we want them intentionally). Down the drives on the 2 filers, kick off
job that is supposed to go through them, and find it going through a
third filer that is not in the storage unit group. Somehow I don't
think it's managing the NDMP storage units quite right.

-Charlie

On 2/11/06, Michael Anderson <andersom68 AT yahoo DOT com> wrote:
> Charles,
>
> I have witnessed the same thing in my NDMP arena and
> opened a case with Veritas that went all the way up to
> engineering without resolution.  We determined the
> cause but there is no fix at the moment and will need
> to go into a MP.  They didn't feel that it would make
> it into MP2 due in March so they are looking at MP3.
>
> Here is my scenario:
> NDMP storage unit for filers A, B, and C created
> through the Windows GUI with appropriate filers as the
> NDMP host.  After submitting the storage unit
> openening filer B or C's properties through the GUI,
> Filer A is listed as the NDMP host.  Essentially what
> is happening is that the first NDMP Host will default
> to the NDMP Host for all storage units after creation.
>  The problem is with how the windows gui passes the
> api call to the database.
>
> Workaround:
> delete storage units and recreate at the command line:
>
> x:\VERITAS\NetBackup\bin\admincmd>bpstuadd -label
> <storage unit name> -density <tape density> -rt <robot
> type, ie: tld> -rn <robot number> -odo <on demand only
> 0=no 1=yes> -nh <ndmp hostname> -M <mastername> -mfs
> <fragment size> -cj <#drives>
>
> Continue with creating all storage units.  bpstulist
> to view and verify proper creation.  At this point do
> not access storage units through the Windows GUI,
> using the java gui or command line works just fine.
>
> BTW:  My environment is 6.0MP1
>
> Good Luck
>
>
>
> --- Charles Ballowe <cballowe AT gmail DOT com> wrote:
>
> > Situation:
> > NetBackup 5.0 - unix master
> > NetApp R200s
> >
> > So - one master, more than one netapp. There are
> > storage units
> > configured for each of the netapps and they claim to
> > be writing to
> > their right storage unit, but they seem to be doing
> > 3-way NDMP
> > backups. I.e. Job kicks of to backup a filesystem on
> > netapp1, job
> > kicks off and starts writing, look at the mounts and
> > the tape is on
> > netapp2 - netbackup shows that STU netapp1 is in
> > use. Netapp1 shows a
> > job running and sending data to netapp2.
> >
> > Is there any way to force NDMP backups to go to
> > tapes that are local
> > to a given netapp in this situation?
> >
> > -Charlie
> >
> > _______________________________________________
> > Veritas-bu maillist  -
> > Veritas-bu AT mailman.eng.auburn DOT edu
> >
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>