2 、故障转移的概述 | 2 、Overview of Failover | ||||||||||||||||||||||||||||||||
下表概述了在不同的可用性和故障转移模式下支持的故障转移形式。对于每个对,有效的可用性模式和故障转移模式由主副本的模式和一个或多个辅助副本的模式的交集决定。 | The following table summarizes which forms of failover are supported under different availability and failover modes. For each pairing, the effective availability mode and failover mode is determined by the intersection of the modes of the primary replica plus the modes of one or more secondary replicas. | ||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||
* 如果对已同步的次要副本发出强制故障转移命令,次要副本的行为与手动故障转移时的行为相同。 | * If you issue a forced failover command on a synchronized secondary replica, the secondary replica behaves the same as for a manual failover. | ||||||||||||||||||||||||||||||||
在故障转移过程中,数据库不可用的时间取决于故障转移的类型及其原因。 | The amount of time that the database is unavailable during a failover depends on the type of failover and its cause. | ||||||||||||||||||||||||||||||||
重要 | Important | ||||||||||||||||||||||||||||||||
为了支持在故障转移后进行客户端连接,除包含的数据库外,必须在新的主数据库上手动重新创建在任何先前主数据库上定义的登录名和作业。有关详细信息,请参阅 管理可用性组中数据库的登录名和作业(SQL Server)。 | To support client connections after failover, except for contained databases, logins and jobs defined on any of the former primary databases must be manually recreated on the new primary database. For more information, see Management of Logins and Jobs for the Databases of an Availability Group(SQL Server). | ||||||||||||||||||||||||||||||||
故障转移集 | Failover Sets | ||||||||||||||||||||||||||||||||
就故障转移集而言,可理解为某一给定可用性组的可能的各种故障转移形式。一个故障转移集由主副本和支持某一给定故障转移形式的辅助副本构成,如下所示: | The forms of failover that are possible for a given availability group can be understood in terms of failover sets. A failover set consists of the primary replica and secondary replicas that support a given form of failover, as follows: | ||||||||||||||||||||||||||||||||
· 自动故障转移集(可选): 在给定的可用性组中,仅当一对可用性副本(包括当前主副本)配置为使用同步提交模式以及自动故障转移(如果有)时,才发生这种故障转移。仅当辅助副本当前已与主副本同步时,自动故障转移集才会生效。 | · Automatic failover set (optional): Within a given availability group, a pair of availability replicas (including the current primary replica) that are configured for synchronous-commit mode with automatic failover, if any. An automatic failover set takes effect only if the secondary replica is currently SYNCHRONIZED with the primary replica. | ||||||||||||||||||||||||||||||||
· 同步提交故障转移集(可选): 在给定的可用性组中,仅当一组(两个或三个)可用性副本(包括当前主副本)配置为使用同步提交模式(如果有)时,才发生这种故障转移。仅当辅助副本配置为使用手动故障转移模式,并且至少一个辅助副本当前已与主副本同步时,同步提交故障转移集才会生效。 | · Synchronous-commit failover set (optional): Within a given availability group, a set of two or three availability replicas (including the current primary replica) that are configured for synchronous-commit mode, if any. A synchronous-commit failover set takes effect only if the secondary replicas are configured for manual failover mode and at least one secondary replica is currently SYNCHRONIZED with the primary replica. | ||||||||||||||||||||||||||||||||
· 整个故障转移集: 在给定的可用性组内,其运行状态当前为联机的所有可用性副本的集合,而不考虑可用性模式和故障转移模式。仅当当前没有辅助副本已与主副本同步时,整个故障转移集才会变为相关的。 | · Entire failover set : Within a given availability group, the set of all availability replicas whose operational state is currently ONLINE, regardless of availability mode and of failover mode. The entire failover set becomes relevant when no secondary replica is currently SYNCHRONIZED with the primary replica. | ||||||||||||||||||||||||||||||||
当您将可用性副本配置为同步提交以及自动故障转移时,此可用性副本将成为自动故障转移集的一部分。但是,该集是否生效则取决于当前主副本。在某一给定时间实际可用的故障转移形式取决于当前有效的故障转移集。 | When you configure an availability replica as synchronous commit with automatic failover, the availability replica becomes part of the automatic failover set. However whether the set takes effect depends the current primary. The forms of failover that are actually possible at a given time depends on what failover sets are currently in effect. | ||||||||||||||||||||||||||||||||
例如,考虑一个可用性组,它有四个可用性副本,如下所示: | For example, consider an availability group that has four availability replicas, as follows: | ||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||
每个辅助副本的故障转移行为取决于哪个可用性副本当前是主副本。基本上,对于给定的辅助副本而言,针对当前主副本的故障转移行为是最坏的情况。下图说明辅助副本的故障转移行为如何随当前主副本而变化,以及该行为是配置为异步提交模式(仅限强制故障转移)还是同步提交模式(具有或没有自动故障转移)。 | The failover behavior for each secondary replica depends on which availability replica is currently the primary replica. Basically, for a given secondary replica, the failover behavior is the worst case given the current primary replica. The following figure illustrates how the failover behavior of secondary replicas varies depending on the current primary replica, and whether it is configured for asynchronous-commit mode (with only forced failover) or synchronous-commit mode (with or without automatic failover). | ||||||||||||||||||||||||||||||||
|
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/81227/viewspace-2654913/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/81227/viewspace-2654913/