You will probably need to add to alias those 2 new cards. As to how to control which card is used this is easy - there is parameter server network interface in device and client resources and also what you specify in storage node filed will get used by NW when sending data from client.

made a mistake: The client is configured as server1 (and not client1) on the server.

This is similar to our setup here: production LAN (192.168.x.x) and backup LAN (172.16.x.x).

On the server we have a primary DNS for the backup LAN, so e.g. server1.backup.lan is 172.16.0.2 (NIC #1) or 172.16.1.2 (NIC #2). The client is configured as client1 on the server with the client's FQDN server1.example.com configured as an alias. On the client we have the corresponding NW server's IP in the hosts file, either 172.16.0.1 or 172.16.1.1.

This works without problems since version 6.1.4, currently we run 7.3.4.

Hello Hrvoje\Olaf,
Thanks for the information.
I have few doubts. Can you please clarify.

1) Is there any way to check which LAN\IP address is used during backup by Networker.

2) I am not able to fine 'Server Network interface' in the device resource.

3) Can IP address be used in 'Server Network interface'

3) The output of 'nslookup' from "nm62instads.inst.scs.com"

C:\Documents and Settings\Administrator.INST>nslookup nm62instads.inst.scs.com
Server: nm62instads.inst.scs.com
Address: 180.144.193.210

Name: nm62instads.inst.scs.com
Addresses: 180.144.193.210, 10.143.71.55, 10.58.118.222


We want Networker uses 180.144.193.210 LAN Since other LAN will be used by some other application.
Note: This machine is itself a backup server and we are not using the host file. We are using the DNS lookup.



4) Ping output from "nm62instads.inst.scs.com"

C:\Documents and Settings\Administrator.INST>ping nm62instads.inst.scs.com

Pinging nm62instads.INST.SCS.COM [180.144.193.210] with 32 bytes of data:

Reply from 180.144.193.210: bytes=32 time<1ms TTL=128
Reply from 180.144.193.210: bytes=32 time<1ms TTL=128
Reply from 180.144.193.210: bytes=32 time<1ms TTL=128
Reply from 180.144.193.210: bytes=32 time<1ms TTL=128

Ping statistics for 180.144.193.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator.INST>

5) Why we have to add alias for those 2 new cards we don't want to use additional LAN for backup.

6) The client also have additional LAN cards. What Will be the impact on backup. For all client too machine we want to use dedicated LAN.

Please feel free if you need any other information about the customer configuration.



Thanks
With Regards
Hemant Joshi
Nokia Siemens Networks
7th Floor, Estate Building, Dickinson Road
Bangalore 560001

Hello,
Any suggestion\Idea ?


Thanks
With Regards
Hemant Joshi.

Hello,
We are getting following errors during the backup of nm62instdmcs.inst.scs.com and nm62instcs2.inst.scs.com.
But the backup is successful.

nm62instdmcs.inst.scs.com:ALL 06/26/08 15:53:09 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instdmcs.inst.scs.com, address 192.168.11.13
* nm62instdmcs.inst.scs.com:ALL 06/26/08 15:53:09 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instdmcs.inst.scs.com, address 192.168.10.13
* nm62instdmcs.inst.scs.com:ALL nsrexec: authtype
* nm62instdmcs.inst.scs.com:ALL savefs: RPC error: Program not registered
* nm62instdmcs.inst.scs.com:ALL savefs: Cannot access nsr server `nm62instdmcs.INST.SCS.COM'
savefs nm62instdmcs.inst.scs.com: failed.
* nm62instcs2.inst.scs.com:ALL 06/26/08 15:53:09 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instcs2.inst.scs.com, address 192.168.11.11
* nm62instcs2.inst.scs.com:ALL 06/26/08 15:53:09 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instcs2.inst.scs.com, address 192.168.10.11
* nm62instcs2.inst.scs.com:ALL nsrexec: authtype
* nm62instcs2.inst.scs.com:ALL savefs: RPC error: Program not registered
* nm62instcs2.inst.scs.com:ALL savefs: Cannot access nsr server `nm62instCS2.inst.scs.com'
savefs nm62instcs2.inst.scs.com: failed.
* nm62instdmcs.inst.scs.com:ALL 1 retry attempted
* nm62instdmcs.inst.scs.com:ALL 06/26/08 15:53:12 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instdmcs.inst.scs.com, address 192.168.11.13
* nm62instdmcs.inst.scs.com:ALL 06/26/08 15:53:12 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instdmcs.inst.scs.com, address 192.168.10.13
* nm62instdmcs.inst.scs.com:ALL nsrexec: authtype
* nm62instdmcs.inst.scs.com:ALL savefs: RPC error: Program not registered
* nm62instdmcs.inst.scs.com:ALL savefs: Cannot access nsr server `nm62instdmcs.INST.SCS.COM'
savefs nm62instdmcs.inst.scs.com: failed.
* nm62instcs2.inst.scs.com:ALL 1 retry attempted
* nm62instcs2.inst.scs.com:ALL 06/26/08 15:54:47 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instcs2.inst.scs.com, address 192.168.11.11
* nm62instcs2.inst.scs.com:ALL 06/26/08 15:54:47 nsrexec: Diagnostic: Reverse DNS lookup failed for host nm62instcs2.inst.scs.com, address 192.168.10.11
* nm62instcs2.inst.scs.com:ALL nsrexec: authtype
* nm62instcs2.inst.scs.com:ALL savefs: RPC error: Program not registered
* nm62instcs2.inst.scs.com:ALL savefs: Cannot access nsr server `nm62instCS2.inst.scs.com'


Output of nslookup of client machine:


C:\Documents and Settings\Administrator.INST>nslookup NM62INSTcs2
Server: nm62instads.inst.scs.com
Address: 180.144.193.210

Name: NM62INSTcs2.inst.scs.com
Addresses: 180.144.192.199, 192.168.11.11, 192.168.10.11


C:\Documents and Settings\Administrator.INST>nslookup NM62INSTdmcs
Server: nm62instads.inst.scs.com
Address: 180.144.193.210

Name: NM62INSTdmcs.inst.scs.com
Addresses: 180.144.136.79, 192.168.10.13, 192.168.11.13


Even though there are above errors, we assume that backup is succesful using the first LAN in binding order(180.144.192.199,180.144.136.79) as success message is shown in the Legato UI and logs.

1) If legato is actually using the first LAN for backup then why does it try to do a reverse lookup for other LAN's in the machine ?
2) Since we do not actually use the other 2 LAN's on the machine for backup, is reverse lookup for other LAN's still required to be done by legato? Is there any way to avoid this reverse lookup for other LAN's?
3) Could there have been any problem due to the reverse lookup error messages above which we are unable to find out?

The same errors are also seen in winworkr UI

Output of nslookup of backup server:

C:\Documents and Settings\Administrator.INST>nslookup NM62INSTfs
Server: nm62instads.inst.scs.com
Address: 180.144.193.210

Name: NM62INSTfs.inst.scs.com
Addresses: 180.144.228.83, 192.168.10.10, 192.168.11.10



While invocation of winworkr from nm62instdmcs.inst.scs.com and nm62instdmcs.inst.scs.com, the winworkr is showing the "Reverse DNS failed for host NM62INSTfs address 192.168.10.10" and "Reverse DNS failed for host NM62INSTfs address 192.168.11.10" but winworkr comes up and restore functionality is working fine. Is there anyway to avoid these messages..

Please Help !!!!


With Regards
Hemant Joshi

You could easily verify that with netstat or some sort of sniffer.


It should be under storage node. You will also find it under client properties.


Yes, but if your DNS works find I see no problem in using associated name.


??? So you have multiple IPs associated with same NIC? That's not recommended at all.


If it doesn't get used usually you do not have to add it unless your routing is funny and they get pinged/used somehow. You can also look at that as additional authentication.


None... if you use dedicated LAN then you use dedicated LAN.