1·Naming standards for business continuity.
业务连续性的命名标准。
2·Category structures for business continuity.
用于业务连续性的类别结构。
3·D.Review business continuity planning process.
检查经营持续性计划程序。
4·There is a good reason for that: business continuity.
这么做有充分的理由：业务连贯性。
5·Implementing plans for failover mechanisms, business continuity, and disaster recovery.
实现故障转移机制、业务连续性和灾难恢复计划。
6·The structure chosen for discussion in this article is a business continuity structure.
本文讨论的结构是一个业务连续性结构。
7·"Traditional" security impact (business continuity, disaster recovery, physical security).
“传统的”安全影响(业务连续性、灾难恢复、物理安全)。
8·Unfortunately, very few systems are built from the business continuity perspective backwards.
不幸的是，很少有系统在构建时考虑到后面的业务连续性。
9·Failover is ideal for applications that must be continuously available for business continuity.
对于需要提供业务连续性的应用程序来说，故障转移是一个理想选择。
10·Immediately adopt an enterprise wide mentality of business continuity and data center automation.
或者马上在整个企业范围建立业务连续性和数据中心自动化意识。