> searching the archives I've found:
> > "ALL" grabs all of the physical and virtual drives
> > with physical and virtual client definitions.

It certainly does in some situations, though not all.  Sometimes a small
number of drives are silently excluded (because they are successfully
mapped to another name that you're not backing up right now).

> > I have had to explicitly define the drives to get around this issue.
> > Any suggestions? Has anyone seen this before?

That's what I've had to do as a workaround before.

> This is exactly the problem we are facing now.
> Suddenly NetWorker began to backup all cluster resources on the physical 
> as well as on the virtual clients.
> (Triple backup of 400++ GB was totaly unexpected :-)
> This has not happend before, cluster backup went well with "ALL" for all 
> clients, 10 cluster, >15 month.
> 
> We have NOTHING changed (fingers crossed :-) in NetWorker resources nor in 
> the cluster configs.
> Only the network guys walked over the floor whistling - they are "fixing" 
> some DNS issues.
> But "nslookup" (std+reverse) gives no clue, every thing looks O.K.


> Hints about fixing this problem are pretty much appreciated.
> e.g. other tools aside from "nslookup", ...

There's definitely some things associated with name resolution, but the
details are hidden in the code.  I've filed RFE's to have more
information about what is required and what is actually being resolved
added to the debug output.

Have you gone through the suggestions that Dave Mussulman mentioned in
this article?

https://listserv.temple.edu/cgi-bin/wa?A2=ind0602&L=NETWORKER&P=R4067&I=-3

-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER