Change DNS Alias of EV Server
Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.
I am attempting to change the DNS alias of one of my EV servers (mailbox archiving) to a new name. I have removed the old alias from DNS and added the new DNS alias pointing to the EV server. I have flushed the dns on all 3 of my EV servers and can properly resolve the alias to the new server.
However, when I do the Update Service Location as stated in this article, http://support.veritas.com/docs/290132, it simply responds that the server is not available with the following information:
Update service locations is now complete
Admin Service on EV02: OK
Admin Service on EV04: OK
The site has 3 servers
Server ev1.domain.name.com is not available.
Check the computer is reachable on the network.
Server EV02
Alias 1: ev2.domain.name.com
Enterprise Vault Indexing Service: OK
Enterprise Vault Shopping Service: OK
Enterprise Vault Directory Service: OK
Enterprise Vault Task Controller Service: OK
Enterprise Vault Storage Service: OK
Server EV04
Alias 1: ev4.domain.name.com
Enterprise Vault Indexing Service: OK
Enterprise Vault Shopping Service: OK
Enterprise Vault Directory Service: OK
Enterprise Vault Task Controller Service: OK
Enterprise Vault Storage Service: OK
This is what the first support engineer told me to do. Still waiting for the callback explaining why it's not working but figured I would check here.
Thanks.
discussion Filed Under:
Comments
Hi Mkimier, You need to
Hi Mkimier,
You need to update the alias in the ComputerEntry table, that's all :)
Once you have updated the ComputerEntry table, refresh the VAC or close it and open it again, then run USL if you want but there is no need to.
--wayne
www.quadrotech-it.com - All your EV Tools
Have you only changed the DNS
Have you only changed the DNS alias or have you moved EV to a new server?
http://seer.entsupport.symantec.com/docs/293911.htm
Check out page 3
Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec Platinum Partner | www.trace3.com
I did not change servers,
I did not change servers, just changing the alias.
Matthew Kimler Current Environment: - Enterprise Vault 9.2 - Discovery Accelerator 89.2 - vSphere 4 (all application hosts & SQL servers are virtualized)
Hmmm
It seems that in that table, the ComputerName has the aliases and the ComputerAlternateName has the actual server host names. So, it's backwards from what the article says.
I'm going to try changing it anyways and will see what happens. I'll let you know tomorrow if I blew up anything. :)
Matthew Kimler Current Environment: - Enterprise Vault 9.2 - Discovery Accelerator 89.2 - vSphere 4 (all application hosts & SQL servers are virtualized)
Hi
Hi Mkimier,
ComputerAlternateName is the alias, it should be the FQDN too. Update that and you should be good to go. Please keep us updated and mark the post as a solution if we helped you.
-wayne
www.quadrotech-it.com - All your EV Tools
Would you like to reply?
Login or Register to post your comment.