Re: Mac mini redundant server implementation

On Sep 24, 10:52 pm, Steve de Mena <st...@xxxxxxxxxxxxxxx> wrote:
On 9/22/11 12:24 PM, KDT wrote:



On Sep 22, 11:54 am, ed<n...@xxxxxxxxxxxxxxx>  wrote:
On Wednesday, September 21, 2011 9:04:28 PM UTC-7, KDT wrote:
On Sep 21, 11:25 pm, Steve de Mena<st...@xxxxxxxxxxxxxxx>  wrote:
...
You don't blindly buy some 3rd party product that effectively yanks
the power cord out of the socket and plugs it back in and pray that
the system is uncorrupted and starts OK.

Steve

Your question was"how do you reboot the server remotely at 3am"

well, no, the question was 'what do you do?' when the server fails.  you're happy with a simple reboot capability, and obviously steve is not..  i.e. you guys are arguing about different things.  to be fair though, steve's question obviously wasn't specific, but it's also clear that he doesn't like what *you'd* consider enough, but you glommed onto a perceived question which wasn't what was actually asked (which isn't that uncommon with you.  :P ).

No his perceived question was "what do you do if your system fails at
3am in the morning".  I answered the question asked, what would I do?

Well the first thing I do is check to see if my backup server which is
continuously monitoring my primary server automatically took over, if
not I do a manual takeover.  If so, I roll over and go back to sleep
and worry about it in the morning.  But then again, I know the answer
to "how do you get 99% uptime"? is not a question about a blade server
it's about removing single points of failure.

I gave you an answer.

What world do you guys live in where every server had a hot standby
backup?  That's not even the case in the ultra mega complex
environments I work in.


Then you don't work with servers where uptime is critical....



99% uptime by the way is a very poor uptime statistic.  No large
corporation would accept uptime that low.   How many airplanes would
crash on landing at Chicago O'Hare if "99%" were acceptable?

I never made any claims either way about how good "99%" uptime is. I
simply said that you *cran't* guarantee any decent level of uptime
with single points of failure whether or not you have a blade server.


Steve

.

Relevant Pages

  • Re: MCNGP.com Status
    ... > Affordablehost.com does not simply claim to offer uptime guarantees. ... > networking failures and services or software running on your server. ... > measure network downtime from the time the trouble ticket is opened by a ... > Affordablehost.com guarantees that your server hardware will be available ...
    (microsoft.public.cert.exam.mcse)
  • Re: secondary domain controller
    ... Ideally they would need 100% uptime for their hours ... I had a Compaq Server with redundant PS, NICs, Hard drives etc go down ... on me because a CPU fan blew and for some reason the BIOS decided to shut ... Do you want to spend the time moving data or fixing ...
    (microsoft.public.windows.server.sbs)
  • Re: Would someone PLEASE answer this question?? Third posting of it!
    ... Who cares what the percentage value of the uptime is, ... are never inconvenienced by a downed server then it can be called 100%. ... SBS is a number of servers, it's not unheard of for one or more of them to ... You can also schedule these reports to run at certain ...
    (microsoft.public.windows.server.sbs)
  • Re: What Platform does GMAIL works
    ... > I personally can't think any server OS engineers with their right mind, ... > server's uptime and make it avaliable by default. ... The 'uptime' as presented in these reports is the "time since last reboot" ... > undesirable indicator to be released to the outsiders. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Migration from win2000 to 2008
    ... I have only 1 DC currently, intergrated DNS ... The replication generated an error: ... The failure occurred at 2009-11-13 12:47.44. ... The RPC server is unavailable.. ...
    (microsoft.public.windows.server.migration)