Nothing says "You've been missed" when after 2 days off, you've 1500 emails, 3 'really critical things' and a 2 day backlog of work.
Including one absolutely fookin' critical restore, an urgent demand for additional disk space on a veritas cluster, and a pointy haired manager demanding I rename servers to 'conform'.
I'm considering my opinion on that latter. Ya see, the naming convention is basically just a bag of spooge. Basically, all our servers end up as S?RUGnnnn where the question mark is to signify the 'role' of the server. Unfortunately, the 'spec' was written by an arsehat who gave a load of letters, the only one of which is typically relevant is 'A' for 'Application'. So we have an awful lot of SARUGnnnnn servers, which is starting to get chronically meaningless. Increasingly of late, there's been queries of "can you check so-and-so on SARUGnnnn' which gets the response 'which one's that then?'.
(To which I typically interject 'I told you so').
Now I'm being told that "When we have the single console it will be important to be seen to conform.", which frankly is just bollocks. Yes, I fully agree that there are situations where you want similar names. When you've a cluster of 500 nearly identical servers for example. But we're rapidly reaching the point where we have 'generic server number 1, 2, 3, 4, 5,' and so we have to go look it up in our database in order to have any idea of what it is/does/who's it is etc.
When one is doing systems admin, getting your servers mixed up is really not a good thing.
Including one absolutely fookin' critical restore, an urgent demand for additional disk space on a veritas cluster, and a pointy haired manager demanding I rename servers to 'conform'.
I'm considering my opinion on that latter. Ya see, the naming convention is basically just a bag of spooge. Basically, all our servers end up as S?RUGnnnn where the question mark is to signify the 'role' of the server. Unfortunately, the 'spec' was written by an arsehat who gave a load of letters, the only one of which is typically relevant is 'A' for 'Application'. So we have an awful lot of SARUGnnnnn servers, which is starting to get chronically meaningless. Increasingly of late, there's been queries of "can you check so-and-so on SARUGnnnn' which gets the response 'which one's that then?'.
(To which I typically interject 'I told you so').
Now I'm being told that "When we have the single console it will be important to be seen to conform.", which frankly is just bollocks. Yes, I fully agree that there are situations where you want similar names. When you've a cluster of 500 nearly identical servers for example. But we're rapidly reaching the point where we have 'generic server number 1, 2, 3, 4, 5,' and so we have to go look it up in our database in order to have any idea of what it is/does/who's it is etc.
When one is doing systems admin, getting your servers mixed up is really not a good thing.