48 error and DNS

[smwoodcrafts]

I am having a bit of a problem with this at times. There are times when a bunch of our backups fail with a 48 error. A problem ticket is generated and sent to the admin of the server we are backing up. They see that it is an issue with a backup and just reassign the trouble ticket to us. I don't see this as an issue with our server, since it usually works correctly. I figured I would ask the experts before taking a stand. Is there anything, on our server that would cause an error contacting the DNS? Our server is pointing to the correct ip addresses for our DNS.

Thanks,

smwoodcrafts

[creany]

morning

you need to be able to resolve forward and reverse DNS entries or backups can fail with status 48.

Couple of easy ways to test from Windows Servers

1. forward DNS lookup

nslookup hostname

should return you the FQDN and ip address

2. reverse DNS lookup

ping -a <Ip Address>

this should return the FQDN of the server and a ping response. if you are only getting the hostname this has got it from WINs and if only returning ip address you do not have a reverse DNS entry.

have fun with this

creany

[Deepak_G]

•  Ensure that all servers and clients are added to name service tables or local hosts file
   
•  Add host name/IP entries for the Master Server, Media Server and Client in their respective /etc/hosts files.
   

   Location of host file:

   UNIX:   /etc/hosts

   Windows:  %SystemRoot%\system32\drivers\etc\hosts

Ensure that all hosts involved have host entries for both themselves and one another.

Once you're done with this - Try with the following.

On Master

1. Start with a ping to the client

2. Try a telnet to the client

3. bptestbpcd -client CLIENTNAME

On Client

1. install path\veritas\netbackup\bin\bpclntcmd -self

2. install path\veritas\netbackup\bin\bpclntcmd -server MASTERSERVERNAME

3. install path\veritas\netbackup\bin\bpclntcmd -pn

If this all works and if you get a proper response, you should have no trouble in connectivity

[Marianne · Accepted solution]

You will agree that you are experiencing an unusual amount of network/firewall related problems.

None of these were ever solved - it seems as if you have simply given up (it actually becomes very demotivating to even try and help you...):

https://www-secure.symantec.com/connect/forums/error-i-dont-understand
https://www-secure.symantec.com/connect/forums/cant-connect-client
https://www-secure.symantec.com/connect/forums/job-failing-24-error-then-42-error
https://www-secure.symantec.com/connect/forums/windows-firewall-problems
https://www-secure.symantec.com/connect/forums/job-failing-58-error-cant-figure-out-why
https://www-secure.symantec.com/connect/forums/nbu-7-and-sql-backups

SUGGESTION:
Since your master server is on 7.0.1, the 'NetBackup Domain Network Analyzer' - nbdna.exe is installed. It is located in <install-path>\veritas\netbackup\bin\support.

Extract from 7.0.1 Release Notes:
Description:
The nbdna script analyzes the NetBackup domain and its configuration for network issues, performance, and behavior. It addresses the host name look-up and the connectivity between the NetBackup hosts and their roles within the NetBackup domain.

Extract from 7.0.1 Troubleshooting Guide:
Network troubleshooting utilities
A set of utility programs (commands) verifies various aspects of network configuration inside and outside NetBackup to ensure that there is no misconfiguration. The utilities also provide user-friendly messages for any errors they find.
Network configuration broadly falls into two categories:
■ Hardware, operating system, and NetBackup level settings. Examples include correct DNS lookups, firewall port openings, and network routes and connections. The NetBackup Domain Network Analyzer (nbdna) verifies this configuration.
■ A set of utilities including bptestcd and bptestnetconn verifies the NetBackup level settings. These settings include CONNECT_OPTIONS and CORBA endpoint selection.


USAGE: nbdna
         [-phase=<0|1|2>] [-verbose] [-sfo]
         [-server | -lookup]
         [-odir=<override_output_directory>]
         [-tmp=<override_tmp_directory>]
         [-dump]
         [-f=<listfile.txt>] [-overwritelist]
         [-version] [-help]

 You must be a root or super user to execute nbdna.
 WARNING for NBAC environment: authenticate before executing nbdna.

    [-phase=<0|1|2>] Set the test phase.  Default is 0.
          [-verbose] display progress to standard out (on screen).
              [-sfo] produce script friendly reports.
           [-server] run server test only.
           [-lookup] run name lookup test only.
             [-odir] override output directory. Default: current working directory.
              [-tmp] override temporary directory. Default: system temp directory.
             [-dump] dumps server, client, and lookup test list to a file.
                [-f] Read hostnames from file and add to test lists.
    [-overwritelist] Overwrite all test lists with list file.
          [-version] just display version info then exit.

        Phase 0: Default mode. Name lookup test and socket connection test.
        Phase 1: Includes Phase 0. Add basic NBU service test for SERVER list.
        Phase 2: Includes Phase 0. Add basic NBU service test for SERVER and CLIENT list.
 

[smwoodcrafts]

Thanks for the feedback. I am going back and updating as much as I can A couple are still pending as it is the holiday time and our network team is bare boned. The firewall guys are both off. I will take your advice. In my defense, a little anyway, I am quite the newbie in all of this and am in the process of really getting an undetstanding of everythign that's going on and cleaning up old messes in the process. Some problems that I've had appear to be errors in configuration done by others that are no longer around. Anyway, I will go back and update the threads you pointed out and mark solutions. Movng forward, I will try to be more courteous and keep open threads updated and mark solution.

smwoodcrafts