Link to home
Start Free TrialLog in
Avatar of AliQahtani
AliQahtaniFlag for Saudi Arabia

asked on

Server naming best practice

Hi Experts,
I want to know if there is a best practice for naming servers. The servers will be VMware
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Host or Guests?

esxXXXX

esxiXXXX

use fully qualified domain names
ASKER CERTIFIED SOLUTION
Avatar of tpitch-ssemc
tpitch-ssemc
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It really depends on where you are.  I've been at places where they use "code names"  I disagree with that 100%....with all due respect to those that use that method.

I'd use something like

vmware1

what hanccocka said works great too.  What is your current naming convention?  I'd try to follow that.

Thanks

Mike
the problem with naming them after characters, it's very difficult at a glance, if a server is down and missing!

compared to server01, server02, .... server053

you can always then say ah server 23 is down, because it's missing, otherwise you have to go recite all the character names, very pretty it looks, but not very practical!

we had a client that name Citrix Application Servers are the Simpsons characters, it was a large farm, and they could never work out which servers were missing!
I don't particularly like naming them after a finite list of things such as characters from a TV show, or even planets. We had a small server base and started naming characters. Association was great because each character served a role- ie Newman was the mail server (because he was the mail man in the show). But it worked fine until we started hitting 10+ servers, now we're having to use some obscure names that don't fit; ie we'd roll over to a new show and really cause confusion.

I'm a really big fan of ACME-Function01 fashing. Having lived through a company merger I started this should we even be purcahsed by someone else or vice versa. That way we can easily integrate the two networks. If you were to use server01 and the company you merge with was using server01 that would make things more challenging. But that's probably over thinking it way too much. I once had a manager that didn't know anything about technology, so I called the server by their function. So when someone would say Exchange01 is down he knew what that meant.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial