What are the pros of switching DNS names with a database server hardware upgrade?
Posted
by
wilbbe01
on Server Fault
See other posts from Server Fault
or by wilbbe01
Published on 2012-11-21T04:28:30Z
Indexed on
2012/11/21
5:02 UTC
Read the original article
Hit count: 132
When we upgrade to new hardware at work we usually increment a number in the DNS name. For example. We have a server called database-2, that is slated to become database-3 in the coming days.
I haven't been able to find a good reason why this is good behavior. To me the work of trying to catch all end user machines, as well as all servers dependent on the database server is far riskier than simply moving the database and ip/name with it to the new hardware. A little over a year ago we spent several months of requests coming in, as infrequent users began using software that needed to be updated to point to a new DNS name. I am struggling to find answers as to why this is a good practice.
So the question. Why is using DNS names as a "server hardware version identifier" a good idea? What am I overlooking?
Thanks much.
© Server Fault or respective owner