Tuesday, November 3, 2015

Basic trouble shooting steps

Basic trouble shooting steps:

We have assumed below details for backup server and client name:

abcbackupserver.com=  Backup Server
xyzclient.com =            Client name


On Client:
  • Ensure networker client package is installed:

  • Ensure networker services are running on client:

  • Networker requires that both forward and reverse FQDN resolution is working fine.  Nslookup should be checked from both backup server and client (Both reverse and forward lookup):

         nslookup  abcbackupserver.com
         nslookup  "IP address" {Reverse Lookup}
  • Check and update the hosts file entries on the client and backup server if you have DNS issue.

        Unix/Linux : /etc/hosts
        Windows : C:\Windows\System32\drivers\etc

  • You should check if your client/backup server can contact each other.

From client :
tracert  or traceroute  abcbackupserver.com


From Backup server:

  • ping -a  xyzclient.com
  • rpcinfo -p xyzclient.com
    program vers proto   port  service
    100000    2   tcp   7938  portmapper
    100000    2   udp   7938  portmapper
    390436    1   tcp   9842
    390435    1   tcp   9164
    390113    1   tcp   7937  nsrexecd

  • Networker requires that both forward and reverse FQDN resolution is working fine.  Nslookup should be checked from both backup server and client (Both reverse and forward lookup):

        nslookup  xyzclient.com
        nslookup  "IP address" {Reverse Lookup}

  • If networker client services are running fine even though you are getting failed error like nothing to save or not properly configured, then you should check nslookup as well as below command and check for any canonical name or any aliases name for failed clients. If found, they should be added to the Aliases entry.

        nsradmin -s  xyzclient.com  -p 390113

bash-4.1$ nsradmin -s xyzclient.com  -p 390113
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> p
                        type: NSRLA;
                        name: xyzclient.com ;
  • Here you will also get the any virtual or cluster configuration IP associated with failed client in IP address section. If you observed different IP’s, nslookup them and add those in Remote Access entry.

        IP address: x.x.x.x, y.y.y.y, z.z.z.z
  • If you are getting connection refused or backup server not present in client server file. Also check your backup server's entry should present in client server file which is located

       Unix: /nsr/res/servers
       Windows: C:\\installation directory\\Legato\\nsr\\res\\ servers

  • You should check if your client/backup server can contact each other.

From Backup Server :

  • tracert  or traceroute  xyzclient.com  

  • If you are getting connection refused or Time out error make sure below port range should open Bi-Directional

  • Need to allow bi-directional TCP traffic on ports 7937-9936 to backup data from the Client to the Backup Server

  • Need to allow bi-directional TCP traffic on ports 7937-9936 to backup data from the Client to the Storage Node




No comments:

Post a Comment

Test1