Unsolved
This post is more than 5 years old
1 Message
0
3322
July 5th, 2012 14:00
hostname is not properly configured on the NetWorker Server
53362:winworkr: Cannot start session with server server: Client 'retiredhostname' is not properly configured on the NetWorker Server.
The hostname it is complaining about is not even in my client list. I am guessing it was a machine that was being backed up at one point in time but I cannot find that hostname anywhere.
I get this message when trying to restore files for a machine that has failed.
So I am on myhostname trying to recover files for deadhostname but it is complaining about a retiredhostname.
Server is running on Solaris10
myhostname is a windows 7 VM
deadhostname was a windows server 2003
retiredhostname was a mac
Thank you,
Jason
No Events found!
CarlosRojas
1.7K Posts
0
July 8th, 2012 02:00
Hi Jason,
Was "retiredname" ever a client on that networker server?
Is "deadhostname" still a valid client on your NetWorker server?
Has any of these 3 servers (retired, dead and myhost) any relationship? I mean, maybe retiredhostname was decomissioned and upgraded to deadhostname and that could be the reason why.
Being this error message shown during a restore I think that could be because some of those servers took the IP of any other servers, and that is when the issue arises.
NetWorker keeps tracking of all servers in the Media DB, and this will include information such as IP, hostname etc, so if any of the servers have either hostname or IP same as one of the decomissioned clients this error message will be shown.
There are different approaches, for example you can add the name in the alias field of the client that is complaining about:
add retiredhostname into the alias field of the deadhostname client, and give it a try.
You can also edit the hostname of the server and the client by adding an entry with:
IP deadhostname retiredhostname
So when trying to resolve the names it will detect that the same IP matches the 2 names.
Otherwise you can open a case with support so they can clean out your media DB, but be sure before that that the information backed up for client retiredhostname is no longer required to be restored.
Thank you.
Carlos.