Possible causes for backups to fail with Network Issues

[Bharath_Achar]

Hello,

backup enivornment:

master :7.1.0.2 ; Unix

Clinet  : both 6.X and 7.X ; windows &  unix.

Storage : 4  PureDisk appliances and 1 tape library.                        

  My question:

what are the possible reasons for backups to fail with network coomunication issues(give error status) and the corresponding steps to resolve.

 Please let me know what all the things we need to check for network issues. Ans also please do not refer any document or links here.

 Regards,

 Bharath

[Zahid_Haseeb]

Ans also please do not refer any document or links here.

Its very difficiult to suggest you without any TN/document

few suggestions are:

Suggestion #1

bptestbpcd command.  This command is helpful because, unlike ping or nslookup, it tests for connection to a NetBackup Client using client connection options at the NetBackup communication level. example of usage:

1. From a Windows command prompt change into the <installpath>\veritas\netbackup\bin\admincmddirectory, or in a UNIX console window, change into the /usr/openv/netbackup/bin/admincmddirectory.

2. Type bptestbpcd /? to list the command parameters.
3. Run the command bptestbpcd -client xxxx (where xxxx is a clientname) to test connection to a client.
4. To view further details, run the command bptestbpcd -client xxxx -verbose (where xxxx is a clientname).
5. To trace through the connection process, run the command bptestbpcd -client xxxx -debug (where xxxx is a clientname).

for more details:

http://www.symantec.com/business/support/index?page=content&id=TECH42657

Suggesion#2

Its although a TN. But informational. 

http://www.symantec.com/business/support/index?page=content&id=HOWTO34204

[Marianne]

If you need a list of all possible network errors, please go through NBU Status Codes Reference Guide

Chapter 1 contains a list of all NBU status codes along with description of errors as well as recommendations of how to troubleshoot and fix.

Searching for the word 'network' in the pdf will take you to all relevant status codes.

[mph999 · Accepted solution]

And now, for the most unhelpful, but probably most accurate answer ,,,

Any network issue 'could' cause a problem in NetBackup.  Forget status codes, just make sure the network is rock solid.  Make sure all hostnames can resolve and try and limit the chance of an issue.

Status codes don't always help that much - take status 24, or 25 - both very very common codes, each one has many many possible causes.  I would say, it is not possible to give a 'direct' answer for any network related status codes,

Really with network related status codes, they are only an approximate guide to the likely area of the issue.

Even with "hostname not found", if you have a faily 'complex' job, for example a redirected restore, it is not possible to just say 'there is the problem' - usually at least there are multiple areas the problem could be in as several machines are involved.  Yes, we know it is a name resolution issue, but which hostname, and on which machine.

Martin