Search results for query: *

Resolved! Seems that somebody enabled a non-physically connected interface on the NDMPclient. The NDMP responses did not go down the default route to the NetBackup server - therefore no acknowledgement received by NetBackup server. Weird, thanks for all the help from everybody to eliminate...

Have you run a disk fsck on the D partition yet? Also, just to isolate Veritas from the problem, have you just done a simple 1 to 1 copy of the data to another area of disk - check out the time it takes for the copy.

I am still investigating this issue with support vendors, early indications seem it may be related to file systems filling up.

Transpires that there is an issue with our NDMPclient. The backup paths do exist, but the communication from the NDMPclient is halted with an error - NDMP data halt internal error. Data halt interupt. Error manifests itself with a error 99 code - which makes sence. Thanks for the help.

I have an ndmp client which currently does not backup and results in an error 99: 03/12/2004 10:29:54 <backupserver> <ndmpclient> backup of client <ndmpclient> exited with status 99 (NDMP backup failure) --> The client does authenticate with the set_ndmp_attr -verify...

I recently had this problem on our network of 200 clients (all flavours) - a useful utility to check out the network interfaces is iperf. It has a valuable -d flag which will highlight any full/half duplex issues with your NetBackup clients - 99% of the time if you eliminate these issues first...