Veritas-bu

[Veritas-bu] Incorrect storage unit choice while using ITC & storage groups (v 5.1.0)

2005-02-04 21:42:17
Subject: [Veritas-bu] Incorrect storage unit choice while using ITC & storage groups (v 5.1.0)
From: Rockey.Reed AT veritas DOT com (Rockey Reed)
Date: Fri, 4 Feb 2005 18:42:17 -0800
Mark,

>From what you describe, NetBackup is working as designed.  When a STUG is
called the first (primary) STU, if available, will be used for that job.
Secondly, you will notice the MUST_USE_LOCAL_DRIVE is not on the Media
servers any more.  The use of M_U_L_D was never designed for any server
except the Master server.  It was a mistake that it was ever assigned to the
Media server.

To ensure you use the correct server in the ITC, select the correct STU
instead of a STUG.  HTH.

Thanks,

Rockey J. Reed


-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of
Mark.Donaldson AT cexp DOT com
Sent: Friday, February 04, 2005 12:32 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Incorrect storage unit choice while using ITC &
storage groups (v 5.1.0)

For those that care, Veritas support has verified that the problem described
below was fixed in v4.5.3 and reintroduced in v5.x.  The fix should be in
5.1.3.

-M

-----Original Message-----

I've got a Solaris 8, NB v5.1 (not patched [yeah, yeah, MP2 is planned])
environment.  When I create a schedule using inline-tape-copy assigned to a
storage unit group, the primary choice in that storage group is being chosen
for the backup's destination rather than the STU for that media server
itself.  The media server has the "MUST_USE_LOCAL_DRIVE" directive in its
bp.conf file.  Touching the "DONT_USE_SLAVE" file actually causes 219 errors
rather than forcing the backup to the local STU.

For a non-ITC backup on the server, the storage unit assigned to that media
server is chosen.  Convert to ITC and it starts shipping it across the
network to the highest priority server listed in the storage group.

This tech note describes the problem perfectly,
http://support.veritas.com/docs/255235, in v4.5 and says it was fixed in
v4.5 [MF]P3.  Now I'm experiencing the same problem in v5.1 and I'm
wondering if anybody else has this problem (ie: did Veritas reintroduce the
bug?) or if it's just me.

Vx backline support (Australia) has the ticket right now.

-M

=================================================
  "They have computers, and they may have other 
  weapons of mass destruction." - Janet Reno
=================================================
  Mark Donaldson - SA - Corporate Express
=================================================
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>