It looks like there's confusion in the name resolution with that NetWorker client. You should check that it is using the name you expect and that the alias field in the NetWorker client properties is filled out correctly with all aliases of the client machine. If you have multpile NICs, you should fill out the 'Server network interface' field in 'Globals (1 of 2)' of the client properties to define which network will be used to contact the NetWorker server.
Did you had a crash or DNS misbehavior? What those two messages suggest is that client information cannot be found (at least not as presented by initial save auth) and that different names for same client are seen as two different clients (and most likely you have two different clientids too). In essence, something in respect to naming is not configured correctly and this should be fixed asap.
coganb
736 Posts
0
November 6th, 2013 00:00
Hi,
It looks like there's confusion in the name resolution with that NetWorker client. You should check that it is using the name you expect and that the alias field in the NetWorker client properties is filled out correctly with all aliases of the client machine. If you have multpile NICs, you should fill out the 'Server network interface' field in 'Globals (1 of 2)' of the client properties to define which network will be used to contact the NetWorker server.
Here's a useful article for more on NetWorker Name Resolution Best Practices
-Bobby
ble1
4 Operator
•
14.4K Posts
0
November 6th, 2013 00:00
Did you had a crash or DNS misbehavior? What those two messages suggest is that client information cannot be found (at least not as presented by initial save auth) and that different names for same client are seen as two different clients (and most likely you have two different clientids too). In essence, something in respect to naming is not configured correctly and this should be fixed asap.