Interesting, I will keep an eye on this, unfortunately I had logging
too high and the job was not in the activity monitor anymore so
Symantec could not pinpoint the issue, next time it happens (if it
recurs) will dig and grab that information more quickly.

On Wed, Sep 5, 2012 at 1:56 AM, Privat Gmail <mian71 AT gmail DOT com> wrote:
> I had him recreate the reverse lookup pointers for the machines that had the 
> vnet_cache issue. The ssh connection to these machines also seemed to benefit 
> from the reverse lookup
>
> Regards
> Michael
>
>
>
> Den 04/09/2012 kl. 19.45 skrev William Brown <william.d.brown AT gsk DOT com>:
>
>> Interested to know what you did when " DNS administrator removed the reverse 
>> lookup zones ".
>>
>> Did you ask them to reinstate the reverse lookup, or reconfigure NetBackup 
>> to no longer require it, or what?   I ask because occasionally we have 
>> discussions about this, and have a few environments without reverse lookup - 
>> as they are non-production we use hosts files, but I just wonder what 'most' 
>> people do.
>>
>> William D L Brown
>>
>> -----Original Message-----
>> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
>> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of 
>> Michael Graff Andersen
>> Sent: 04 September 2012 13:55
>> To: Justin Piszcz
>> Cc: veritas-bu AT mailman.eng.auburn DOT edu
>> Subject: Re: [Veritas-bu] NetBackup 7.5.0.3: bprd vnet_cached_getnameinfo() 
>> for x.x.x.x failed, Unknown error 18446744073709551614 (-2)
>>
>> Hello Justin
>>
>> I have seen the same thing on Netbackup 7.1.0.2 after our DNS administrator 
>> removed the reverse lookup zones
>>
>> Took a day or two after the change before the vnet entries appeared in the 
>> problems log.
>>
>> I would try to run bpclntcmd -clear_host_cache first
>>
>> Regards
>> Michael
>>
>> 2012/9/4 Justin Piszcz <jpiszcz AT lucidpixels DOT com>:
>>> Hello,
>>>
>>> Upgraded from 7.1 to 7.5.0.3 (7.1->7.5->7.5.0.3).
>>>
>>> During a regular hot catalog backup I saw this:
>>> 1346454000 1 2 16 master 0 0 0 *NULL* bprd vnet_cached_getnameinfo()
>>> for x.x.x.x failed, Unknown error 18446744073709551614 (-2)
>>> 1346540401 1 2 16 master  0 0 0 *NULL* bprd vnet_cached_getnameinfo()
>>> for x.x.x.x failed, Unknown error 18446744073709551614 (-2)
>>>
>>> Everything had been running for several days without a single problem,
>>> this happened recently, also the test environment running for 5-6+
>>> months has never had this problem.
>>>
>>> I opened a case with Symantec but was curious if anyone had seen this 
>>> before?
>>>
>>> Thoughts?
>>>
>>> Justin.
>>> _______________________________________________
>>> 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
>>
>>
>> ________________________________
>>
>> This e-mail was sent by GlaxoSmithKline Services Unlimited
>> (registered in England and Wales No. 1047315), which is a
>> member of the GlaxoSmithKline group of companies. The
>> registered address of GlaxoSmithKline Services Unlimited
>> is 980 Great West Road, Brentford, Middlesex TW8 9GS.
>>
>> _______________________________________________
>> 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
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu