99.99%的耐用性。这是什么意思?这是、什么意思、耐用性

2023-09-11 08:40:51 作者:一念天堂一念地狱

亚马逊S3提供了两种方案:

  

存储   (专为99.999999999%耐久度)

  

减少冗余存储   (专为99.99%耐久度)

专为在某一年提供的对象99.999999999%的耐久性和99.99%的可用性。

继承人链接

所以,如果我有10 000文件,我可以期待宽松之一,平均每年有第二个计划?我是跨preting这是否正确?

编辑:莫比我必须把它更加明确:

你怎么跨preT尤其是设计的一部分。例如,如果提供99.9%的可用性我保证,并支付刑事每小时更多的或者类似的东西。 但是,如果我设计了系统99.9%的可用性,我选择用知识的部分,该系统将可能有0.1%的统计平均停机时间。

占的部首 占的拼音 占的组词 占的意思

这并不一定意味着我保证什么。它正是该系统是专为...

解决方案

RRS将生存一个数据中心的总损失,以及使用多个驱动器等常规S3存储将生存两人的损失。

在99.999999999%的耐久性图是位毫无意义 - 他们引用的东西小于A K / T事件的概率大小的彗星撞击地球,如果发生,我们不会担心我们的S3数据

取下来亚马逊政治或经济事件的概率比三AWS地区同时被破坏的风险要高得多,所以我拒绝了这种说法,在S3上的数据并不需要进行备份虽然是很好的了解,该系统的设计是为了生存最不测。

有您已连接到您的AWS账号泄露的系统,并且丢失数据这样的风险是较高的了,所以始终保持脱机备份

Amazon S3 offers two plans:

Storage (Designed for 99.999999999% Durability)

and

Reduced Redundancy Storage (Designed for 99.99% Durability)

Designed to provide 99.999999999% durability and 99.99% availability of objects over a given year.

Heres the link

So if I have 10 000 files I can expect to loose one in average with the second plan per year? am I interpreting that correctly?

Edit: Maby I have to put it more clearly:

How do you interpret especially the "designed for" part. If for example offer 99,9% availability I guarantee that and pay a penal for every hour more or something like that. But if I design the system for 99,9% availability, I choose the parts with the knowledge that the system will probably have a downtime of 0.1% on statistical average.

That does not necessarily mean that I guarantee anything. Its just what the system is designed for...

解决方案

RRS will survive the total loss of one data centre, as well using multiple drives, etc. Regular S3 storage will survive the loss of two.

The 99.999999999% durability figure is a bit pointless - they're quoting something less than the the probability of a K/T event sized comet hitting Earth, and if that happened we wouldn't be worrying about our S3 data.

The probability of a political or economic event taking down Amazon is a much higher than the risk of three AWS regions being simultaneously destroyed, so I reject that notion that data in S3 "doesn't need to be backed up" although it is good to know that the system has been designed to survive most eventualities.

The risk of having a system you have connected to your AWS account compromised, and losing data that way, is higher again, so always keep offline backups.