Virtual IP load balancer

Question

Friends, I am not able to run backups on a client which is also having a virtual IP as load balancer. Description of the problem: --------------------------------------- We are using Linux Backup Server 7.3.2 Client is Linux server, Version 7.3.2. The client is having VIP (virtual IP) assigned as load balancer. I am able to ping both ways from backup server and the client successfully, using hostnames and IP address. All required firewall ports are open. All other clients on the same subnet inside the DMZ are backing up successfully. When I run the backup , the backup is failing for this client with the error ' :/tmp save: SYSTEM error: client `xx.150.100.171' is not properly configured.'. The actual client's IP address is in fact 'xx.150.100.139'. When I do a traceroute from the backup server to the client , the traceroute is ending at the virtual IP 'xx.150.100.171' instead of the actual IP 'xx.150.100.139'. When I run traceroute from the backup server to the client $ /usr/sbin/traceroute hostname traceroute to hostname(xx.150.100.139), 30 hops max, 38 byte packets 1 xx.150.100.163 (xx.150.100.163) 0.910 ms 0.434 ms 1.202 ms 2 xx.150.100.171 (xx.150.100.171) 1.286 ms 0.572 ms 1.083 ms $ Traceroute is ending at the virtual IP When I traceroute ICMP ECHO packets instead of UDP datagrams from the backup server to the client $ traceroute -I hostname traceroute to hostname (xx.150.100.139), 30 hops max, 38 byte packets 1 xx.150.100.163 (xx.150.100.163) 0.488 ms 0.262 ms 0.276 ms 2 hostname (xx.150.100.139) 0.346 ms 0.311 ms 0.335 ms $ Works fine, so it depends on the content of the packets. Network guys are saying a load balancer is supposed to work exactly like this. A handshake is first established between the Virtual IP and the backup server. After a successful handshake data traffic is started. Network guys also said the exact problem was resolved for another customer using NetBackup. So, is there a setting in Legato to fix this? I really really appreciate your help. Thank You.

ble1 · Answer

This is not Legato problem at all, but to fix it simply put 171 to alias list of 139. And I would suggest to use hostnames instead of IPs.

Bandaru1 · Answer

After adding 171 as an alias to 139, the backup connected and completed sucessfully. We are using hostnames only. I have added the IP 171 as an alias to the hostname in the client resource.Thank You.

NetWorker

Was this post helpful?