I have two nodes that when a backup kicks in with the scheduler, lists a
different node in the communication address. This different server is
listed for both nodes. I have checked DNS and everything is fine there.
Also I have checked the host file on all nodes and there isn't anything
unusual there either. All nodes backup fine, but I wasn't sure if this
would affect preformance or not?? An example is shown below:
ANR0406I Session 26028 started for node ES2 (WinNT)
(Tcp/Ip ms848-1.ycdsb.ca(3890)). (SESSION: 26028)
You'll notice both communication addresses are
the same, but different client nodes.
ANR0406I Session 25789 started for node ES3 (WinNT)
(Tcp/Ip ms848-1.ycdsb.ca(1100)). (SESSION: 25789)
ANR0406I Session 25693 started for node ES1 (WinNT)
(Tcp/Ip es1.ycdsb.ca(3088)). (SESSION: 25693) For
this node and all others the communication address is the same as the
actual node name.
Has anyone noticed this before?? Any info would be appreciated.
Chris
______________________________________________
This message is for the sole use of the intended recipients and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not an intended recipient,
please contact the sender by reply email and destroy all copies of the original
message. Thank you for your cooperation.
