云计算灾难恢复双副本原理_灾难恢复在云计算中的优势

云计算灾难恢复双副本原理

Disaster Recovery plans and infrastructures are a necessity for large enterprises for which operating would be an issue if their mission critical applications were to crash or become unavailable. Most DR infrastructures have adopted the method of replicating the infrastructure and hardware of the primary site at a backup location; this ensures that when an issue occurs at the primary site, applications can still be served from an unaffected location that contains the necessary capacity. However, replicating an already complex infrastructure is time consuming and costly to not just build, but to maintain too. Cloud DR looks to build upon DR plans by providing a virtualised cloud infrastructure that is able to operate idly with minimal resources, but can scale up to cope with demand when the primary site fails.

对于大型企业来说，灾难恢复计划和基础架构是必不可少的，如果大型企业的关键任务应用程序崩溃或变得不可用，那么运营将成为一个问题。 大多数灾难恢复基础架构都采用了在备份位置复制主站点的基础架构和硬件的方法。 这样可以确保当主站点出现问题时，仍可以从不受影响的位置(包含必要的容量)为应用程序提供服务。 但是，复制已经很复杂的基础结构不仅要建立而且要维护也很费时间和成本。 Cloud DR希望通过提供虚拟化的云基础架构来构建DR计划，该虚拟化的云基础架构能够以最少的资源闲置运行，但是可以扩展以在主站点发生故障时满足需求。

减少灾难恢复成本 (Reduction in DR costs)

Moving a DR configuration into the cloud can help you to realise huge cost savings by reducing the amount of physical infrastructure that you need to maintain and rely on to protect you in the event of a disaster that takes down your primary data centre locations. Because a DR environment only requires resources that are of a bare minimum when it isn’t being actively used, the amount that you are paying will also be the bare minimum.

将灾难恢复配置迁移到云中，可以减少需要维护的物理基础架构的数量，并在灾难导致主要数据中心位置崩溃时保护您所需的物理基础架构，从而帮助您节省大量成本。 由于DR环境仅在不被积极使用时才需要资源的最低限度，因此您所支付的金额也将是最低限度的。

As a physical DR environment is comprised of hardware and resources that are equal to that of your primary sites, the amount being paid for is often the same as that of the primary site, the only difference being that most of the time these resources are lying idle. So in effect, with traditional DR you could be paying for unused resources a lot of the time. In a cloud DR configuration, if it is called into action then additional resources can be automatically provisioned as the environment scales to cope with the demand being placed on it. Once demand recedes, the resources are then returned to the cloud. With cloud DR you will only ever be paying for resources that are actually being used, which is where the cost efficiencies arise.

由于物理灾难恢复环境由与您的主站点相同的硬件和资源组成，因此所支付的金额通常与主站点的金额相同，唯一的区别是，大多数时间这些资源都在说谎闲。 因此，实际上，使用传统灾难恢复，您可能会花费很多时间来支付未使用的资源。 在云灾难恢复配置中，如果将其采取行动，则可以随着环境的扩展自动配置其他资源，以应对对其提出的需求。 一旦需求减少，资源便返回到云中。 使用云灾难恢复，您将只需要为实际使用的资源付费，这就是提高成本效率的地方。

虚拟化满足不可预测的需求 (Virtualization caters for unpredictable demand)

With traditional DR, the capacity of the DR environment is equal to that of the primary site. So whilst there will be enough capacity to meet demand when the primary site is down, it does mean that even when the DR environment is in use that there could still be a substantial amount of free resources. These are free resources that you will still be paying for. DR in the cloud accounts for this unpredictable demand by scaling up to account for the demand placed on it, so you are only ever paying for resources that are actually being used, therefore there will never be any spare resources. This can also be of assistance for times where demand is actually more than even the primary site can handle.

使用传统灾难恢复，灾难恢复环境的容量等于主站点的容量。 因此，尽管在主站点关闭时将有足够的容量来满足需求，但这确实意味着，即使在使用灾难恢复环境时，仍然可能会有大量的空闲资源。 这些都是免费资源，您仍然需要付费。 云中的灾难恢复可以通过扩展规模来解决这一不可预测的需求 ，因此您只需要为实际使用的资源付费，因此永远不会有任何备用资源。 在需求实际上甚至超出主站点所能承受的时候，这也可能会有所帮助。

恢复时间最短 (Minimal recovery time)

With cloud DR, the backup environment will be ready to serve your mission critical applications the moment any issues are detected at your primary sites. In the event that your primary site does become unavailable, your end-users shouldn’t notice any difference as we have designed the failover process to take place with minimal downtime. Once your end-users have been transferred to the DR environment, you can get to work repairing the primary site as soon as possible to minimise the amount of time that is spent utilising the recovery site. Once you have repaired the issue and are confident that the primary site is ready to be returned to live use, the transfer from the DR site to primary site will also be flawless and completed with minimal downtime. These processes make sure that issues don’t have the opportunity to have a large, negative impact on your business; although sometimes they may take time and money to repair, from your end-user’s perspective at least your business will continue to operate as normal because they will still be able to access their mission critical applications and data without issue.

借助云灾难恢复，一旦在主站点上发现任何问题，备份环境就可以为关键任务应用程序提供服务。 万一您的主站点确实不可用，您的最终用户应该不会注意到任何差异，因为我们将故障转移过程设计为在停机时间最少的情况下进行。 将最终用户转移到灾难恢复环境后，您可以尽快修复主站点，以最大程度地减少使用恢复站点所花费的时间。 一旦您解决了问题，并确信可以将主站点恢复为可以使用，则从灾难恢复站点到主站点的传输也将是完美无缺的，并且可以在最少的停机时间内完成。 这些流程可确保问题没有机会对您的业务产生较大的负面影响； 尽管有时他们可能需要花费时间和金钱进行维修，但从最终用户的角度来看，至少您的业务将继续正常运行，因为他们仍然能够毫无问题地访问其关键任务应用程序和数据。

翻译自: https://www.eukhost.com/blog/webhosting/advantages-of-disaster-recovery-in-cloud-computing/

云计算灾难恢复双副本原理