cancel
Showing results for 
Search instead for 
Did you mean: 

Backup Failing with 25.

RichardRana
Level 3

Hi,

Master : Solaris 10 running 7.1.0.2

Media : Solaris 10 running 7.1.0.2

Client : Windows 2008 - NBU 7.1.0.2

 

The backup jobs are failing with 25. Investigations showed that the client had be assigned multiple ip address.

 

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-50-56-A3-0B-4B
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.134.115.60(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.61(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.62(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.63(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.64(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.65(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.66(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.67(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.68(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.69(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   IPv4 Address. . . . . . . . . . . : 10.134.115.70(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.134.115.1
   DNS Servers . . . . . . . . . . . : 10.130.32.52
                                       10.14.6.85
   Primary WINS Server . . . . . . . : 10.133.64.134
   Secondary WINS Server . . . . . . : 10.133.64.135
                                       10.14.1.228
                                       10.14.1.229
   NetBIOS over Tcpip. . . . . . . . : Enabled

 

And the nslookup also showed all the ips in DNS enteris. The backup runs fine when one of the ip is used as the client name. but fails when the client name is used.

 

Can anyone help me to get a sucessfull backup using the client name.

 

Thanks in Advance,

Richard.

 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified

What is the reason for that many IP addresses for the same hostname?
All on the same NIC?

As explained before - a product such as NBU needs consistent forward and reverse lookup.

Try this as workaround - edit hosts file on the client and add hostname for each IP address, e.g:

10.134.115.60 NXTSTWSPDA01
10.134.115.61 NXTSTWSPDA01a
10.134.115.62 NXTSTWSPDA01b
10.134.115.63 NXTSTWSPDA01c
.....

 

Then add NXTSTWSPDA01 as Preferred Network in Client's Host Properties.

View solution in original post

9 REPLIES 9

revarooo
Level 6
Employee

So when you use a IP address it works but not a hostname? 

If that's the case check the IP -> Hostname on the media server /etc/hosts (or DNS) and ensure it matches the IP that "works"

RichardRana
Level 3

I have tried the same. Added the host entry on the media server. but still failed with the same error. Looks like it reached the client on one ip and the return is from another and it takes different Ip every time. Not sure how to get the same ip respond every time.

 

Anonymous
Not applicable

Check the media server doesnt have some old entry in ARP

 

arp -a

or

ip neighbor

 

Delete the entry.

arp -d

 

Alternatively, troubleshoot with bpclntcmd command on the media server.

DOCUMENTATION: Explanation of bpclntcmd options, the system calls being used, and recommended troubl...

Anonymous
Not applicable

DOCUMENTATION: How network interfaces are selected in NetBackup 6.x/7.x when there are multiple NICs...

EDIT: Just noticed this is for Servers/Hosts not Clients.

But have a look into the Preferred Network properties on the Master Server.

there is a section in the Sysadmin Guide Vol I

The Preferred Network properties are useful in NetBackup environments that include multihomed hosts—the hosts that are connected to two or more networks, or hosts that have two or more network addresses.

RichardRana
Level 3

Hi Stuart,

 

There are no old DNS enteries  of this client in media servers.

And on executing the bpclntcmd command it returned an output as below. where the ips are not related to master, media or the client.

 

D:\Program Files\NetBackup\bin>bpclntcmd -pn
expecting response from server pronbu01.unix.gsm1900.org
206.29.165.49 *NULL* 206.29.165.49 54652

Marianne
Level 6
Partner    VIP    Accredited Certified

What does 'bpclntcmd -self' show?

Seems client hostname has multiple IP addresses on the same subnet. This creates havoc in an environment where consistent forward and reverse lookup is needed (as you have experienced in NBU).

What is the reason for this?

If this is a cluster with multiple Service/Resource groups, each IP address should be associated with a unique virtual hostname - either in DNS or in local hosts file.

 

RichardRana
Level 3

HI Marianne,

This is what bpclntcmd -self returned.

 D:\Program Files\NetBackup\bin>bpclntcmd -self
gethostname() returned: 10.134.115.60
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.60
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.61
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.62
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.63
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.64
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.65
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.66
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.67
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.68
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.69
host 10.134.115.60: NXTSTWSPDA01.gsm1900.org at 10.134.115.70
aliases:     NXTSTWSPDA01.gsm1900.org     10.134.115.70     10.134.115.69     10
.134.115.68     10.134.115.67     10.134.115.66     10.134.115.65     10.134.115
.64     10.134.115.63     10.134.115.62     10.134.115.61     10.134.115.60
 

 And also the NS lookup keeps pointing all the ips to the same name. Seems to be no virtual names in DNS or in local host

 

 nslookup nxtstwspda01
Server:         10.142.56.132
Address:        10.142.56.132#53

Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.62
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.63
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.64
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.65
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.66
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.67
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.68
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.69
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.70
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.60
Name:   nxtstwspda01.gsm1900.org
Address: 10.134.115.61

 

 

 

Marianne
Level 6
Partner    VIP    Accredited Certified

What is the reason for that many IP addresses for the same hostname?
All on the same NIC?

As explained before - a product such as NBU needs consistent forward and reverse lookup.

Try this as workaround - edit hosts file on the client and add hostname for each IP address, e.g:

10.134.115.60 NXTSTWSPDA01
10.134.115.61 NXTSTWSPDA01a
10.134.115.62 NXTSTWSPDA01b
10.134.115.63 NXTSTWSPDA01c
.....

 

Then add NXTSTWSPDA01 as Preferred Network in Client's Host Properties.

RichardRana
Level 3

Hi Marianne,

 

Thanks for the help. I added the entry below on client, master and media servers and the backups are now progressing fine.

10.134.115.60 nxtstwspda01      nxtstwspda01.gsm1900.org

 

Thanks once again for helping in resolving this long pending issue.

 

Regards,
Richard.