我通过不同的托管提供商运行大约 5 个不同的托管服务器。 在过去的两个月里，我工作的一台服务器宕机了两次。 两次都出乎意料且相当长（36 小时和 4 小时）。 有问题的服务器是 VPS，而不是共享服务器。 根据我与其他服务器/提供商（VPS 和共享）的经验，这似乎是不可接受的停机时间。
- 你怎么认为？
- 您认为服务器的合理停机时间是多少（计划内和计划外）？
I run about 5 different hosted servers, through a variety of hosting providers. In the past two months, one of the servers I work on has been down twice. Both times were unexpected and fairly long (36 hours and 4 hours). The server in question is a VPS not a shared server. Given my experience with my other servers/providers (both VPS and shared) this seems like an unacceptable amount of downtime.
- What do you think?
- What do you consider a reasonable amount of downtime for your servers (planned and unplanned)?
发布评论
评论（2）
你得到你所付出的。
您与提供商的 SLA 是什么？ 你有吗？ 如果有任何一个因素可以解释价格差异，那就是这个。 如果您需要保证正常运行时间（例如 3 个 9），那么您就必须为此付费。 例如，5 个 9 的正常运行时间将使您花费更多。
回答您的问题：您是否得到了有关此次停机原因的解释？ 36小时太长了。 4小时不一定（如果很少的话）。 是硬件故障吗？ 如果是这样，你对此无能为力。 我曾经有一个提供商，他们偶尔会填满他们的配置，并且邮件会停止工作，直到我告诉他们修复它。 对我来说，这是不可接受的。
You get what you pay for.
What's your SLA with your provider? Do you even have one? If there's any one factor that explains the difference in price, it's this. If you need guaranteed uptime (3 9s for example) then you'll have to pay for it. 5 9s uptime, for example, will cost you considerably more.
To answer your question: did you get an explanation as to the causes of this downtime? 36 hours is excessively long. 4 hours not necessarily (if its rare). Was it a hardware fault? If so, you can't do much about those. I once had a provider who would occasionally stuff up their config and mail would stop working until I told them to fix it. To me, that was unacceptable.
服务器硬件将出现故障。 这只是时间问题。 我不会试图确定什么是合理的，而是会问您另一个问题：您的配置可能失败的所有可能方式是什么？您是否准备更改您的设置以解决这些可能性？
例如，假设您的网站托管在单个 VPS 上。 一些故障示例可能包括：
您可以通过部署负载均衡器和第二个 VPS 来降低#1 和 #2 导致站点瘫痪的风险。 这种降低的风险值得额外花费吗？
这种讨论在某些时候会变成灾难恢复问题。
Server hardware will fail. It is only a matter of time. Rather than trying to determine what is reasonable I would ask you another question: What are all of the possible ways that your configuration could fail and are you prepared to change your setup to account for these possibilities?
For example, let's say that your website is hosted on a single VPS. A few examples of failures might be:
You could lower your risk of #1 and #2 taking down your site by deploying a load balancer and a second VPS. Is this decreased risk worth the additional expense?
This discussion turns into a matter of disaster recovery at some point.