SQL Server 的 Windows Server 容錯移轉叢集Windows Server Failover Clustering with SQL Server

適用於: 是SQL Server 否Azure SQL Database 否Azure SQL 資料倉儲 否平行處理資料倉儲 APPLIES TO: yesSQL Server noAzure SQL Database noAzure SQL Data Warehouse noParallel Data Warehouse

「Windows Server 容錯移轉叢集 (WSFC)」 是一組獨立伺服器,會一起運作以提高應用程式和服務的可用性。A Windows Server Failover Cluster (WSFC) is a group of independent servers that work together to increase the availability of applications and services. SQL Server 2017SQL Server 2017 利用 WSFC 服務和功能,以支援 AlwaysOn 可用性群組Always On availability groupsSQL ServerSQL Server 容錯移轉叢集執行個體。takes advantage of WSFC services and capabilities to support AlwaysOn 可用性群組Always On availability groups and SQL ServerSQL Server Failover Cluster Instances.

詞彙和定義Terms and Definitions

Windows Server 容錯移轉叢集 (WSFC):WSFC 是一組獨立伺服器,會一起運作以提高應用程式和服務的可用性。Windows Server Failover Cluster (WSFC) A WSFC is a group of independent servers that work together to increase the availability of applications and services.

節點Node
參與 WSFC 的伺服器。A server that is participating in a WSFC.

叢集資源Cluster resource
實體或邏輯實體,可為節點所擁有、恢復上線及離線、在節點之間移動,並以叢集物件方式進行管理。A physical or logical entity that can be owned by a node, brought online and taken offline, moved between nodes, and managed as a cluster object. 叢集資源在任何時間點只能由單一節點所擁有。A cluster resource can be owned by only a single node at any point in time.

角色Role
以單一叢集物件方式管理的叢集資源集合,用來提供特定功能。A collection of cluster resources managed as a single cluster object to provide specific functionality. 針對 SQL Server,角色將是 AlwaysOn 可用性群組 (AG) 或 AlwaysOn 容錯移轉叢集執行個體 (FCI)。For SQL Server, a role will be either an Always On Availability Group (AG) or Always On Failover Cluster Instance (FCI). 角色包含 AG 或 FCI 需要的所有叢集資源。A role contains all of the cluster resources that are required for an AG or FCI. 容錯移轉和容錯移轉一律在角色的內容中運作。Failover and failback always act in context of roles. 針對 FCI,角色將包含 IP 位址資源、網路名稱資源和 SQL Server 資源。For an FCI, the role will contain an IP address resource, a network name resource, and the SQL Server resources. AG 角色將包含 AG 資源;而且,如果設定接聽程式,則包含網路名稱和 IP 資源。An AG role will contain the AG resource, and if a listener is configured, a network name and an IP resource.

網路名稱資源Network name resource
以叢集資源方式管理的邏輯伺服器名稱。A logical server name that is managed as a cluster resource. 網路名稱資源必須與 IP 位址資源搭配使用。A network name resource must be used with an IP address resource. 這些項目可能需要 Active Directory Domain Services 和 (或) DNS 中的物件。These entries may require objects in Active Directory Domain Services and/or DNS.

資源相依性Resource dependency
另一個資源所相依的資源。A resource on which another resource depends. 如果資源 A 與資源 B 相依,則 B 是 A 的相依性。如果沒有資源 B,就無法啟動資源 A。If resource A depends on resource B, then B is a dependency of A. Resource A will not be able to start without resource B.

慣用擁有者Preferred owner
資源群組偏好在其上執行的節點。A node on which a resource group prefers to run. 每個資源群組都與依照喜好設定順序排序的慣用擁有者清單相關聯。Each resource group is associated with a list of preferred owners sorted in order of preference. 在自動容錯移轉期間,資源群組會移至慣用擁有者清單中的下一個慣用節點。During automatic failover, the resource group is moved to the next preferred node in the preferred owner list.

可能擁有者Possible owner
資源可在其上執行的次要節點。A secondary node on which a resource can run. 每個資源群組都與可能擁有者清單相關聯。Each resource group is associated with a list of possible owners. 角色只能容錯移轉至列為可能擁有者的節點。Roles can fail over only to nodes that are listed as possible owners.

仲裁模式Quorum mode
容錯移轉叢集中決定叢集可承受之節點失敗次數的仲裁設定。The quorum configuration in a failover cluster that determines the number of node failures that the cluster can sustain.

強制仲裁Force quorum
即使僅少數仲裁必要元素正在通訊中,也會啟動叢集的程序。The process to start the cluster even though only a minority of the elements that are required for quorum are in communication.

Windows Server 容錯移轉叢集概觀Overview of Windows Server Failover Clustering

Windows Server 容錯移轉叢集提供基礎結構功能,支援 Microsoft SQL ServerSQL Server 和 Microsoft Exchange 等託管伺服器應用程式的高可用性和災害復原案例。Windows Server Failover Clustering provides infrastructure features that support the high-availability and disaster recovery scenarios of hosted server applications such as Microsoft SQL ServerSQL Server and Microsoft Exchange. 如果叢集節點或服務失敗,該節點上裝載的服務可在稱為 「容錯移轉」 (Failover) 的程序中自動或手動轉移至另一個可用的節點。If a cluster node or service fails, the services that were hosted on that node can be automatically or manually transferred to another available node in a process known as failover.

WSFC 中的節點會一起運作,共同提供這些類型的功能:The nodes in a WSFC work together to collectively provide these types of capabilities:

  • 分散式的中繼資料和通知。Distributed metadata and notifications. WSFC 服務和託管應用程式中繼資料是在叢集中的每個節點上進行維護。WSFC service and hosted application metadata is maintained on each node in the cluster. 此中繼資料除了包含託管應用程式設定之外,還包含 WSFC 組態和狀態。This metadata includes WSFC configuration and status in addition to hosted application settings. 對節點中繼資料或狀態所做的變更會自動傳播到 WSFC 中的其他節點。Changes to a node's metadata or status are automatically propagated to the other nodes in the WSFC.

  • 資源管理。Resource management. WSFC 中的個別節點可以提供實體資源,例如直接附加的儲存體、網路介面和共用磁碟儲存體存取。Individual nodes in the WSFC may provide physical resources such as direct-attached storage, network interfaces, and access to shared disk storage. 託管應用程式會自行註冊為叢集資源,並可設定對其他資源的啟動和健全狀況相依性。Hosted applications register themselves as a cluster resource, and may configure startup and health dependencies upon other resources.

  • 健全狀況監視。Health monitoring. 節點間和主要節點健全狀況偵測是透過活動訊號式網路通訊和資源監視的組合來完成。Inter-node and primary node health detection is accomplished through a combination of heartbeat-style network communications and resource monitoring. WSFC 的整體健全狀況是由 WSFC 中節點的仲裁投票所決定。The overall health of the WSFC is determined by the votes of a quorum of nodes in the WSFC.

  • 容錯移轉協調。Failover coordination. 每個資源都是設定為在主要節點上裝載,而且每個資源都可以自動或手動轉移至一個或多個次要節點。Each resource is configured to be hosted on a primary node, and each can be automatically or manually transferred to one or more secondary nodes. 以健全狀況為主的容錯移轉原則會控制節點之間資源擁有權的自動轉移。A health-based failover policy controls automatic transfer of resource ownership between nodes. 在發生容錯移轉時,節點和託管應用程式會收到通知,以便它們可以適當反應。Nodes and hosted applications are notified when failover occurs so that they may react appropriately.

如需詳細資訊,請參閱:容錯移轉叢集概觀 - Windows ServerFor more information, see: Failover Clustering Overview - Windows Server

SQL Server AlwaysOn 技術和 WSFCSQL Server Always On Technologies and WSFC

SQL Server 2017SQL Server 2017 AlwaysOn 是利用 WSFC 的高可用性和災害復原方案。Always On is a high availability and disaster recovery solution that takes advantage of WSFC. AlwaysOn 功能提供彈性的整合式解決方案,以提高應用程式可用性、提供更佳的硬體投資報酬率,以及簡化高可用性部署和管理。The Always On features provide integrated, flexible solutions that increase application availability, provide better returns on hardware investments, and simplify high availability deployment and management.

AlwaysOn 可用性群組Always On availability groups 和 AlwaysOn 容錯移轉叢集執行個體都會使用 WSFC 作為平台技術,並且將元件註冊為 WSFC 叢集資源。Both AlwaysOn 可用性群組Always On availability groups and Always On Failover Cluster Instances use WSFC as a platform technology, registering components as WSFC cluster resources. 相關資源會合併為一個可相依於其他 WSFC 叢集資源的「角色」 。Related resources are combined into a role, which can be made dependent upon other WSFC cluster resources. WSFC 接著可以感測需要重新啟動 SQL ServerSQL Server 執行個體並發出訊號,或自動將它容錯移轉至 WSFC 中的不同伺服器節點。The WSFC can then sense and signal the need to restart the SQL ServerSQL Server instance or automatically fail it over to a different server node in the WSFC.

重要!!IMPORTANT!! 若要充分利用 SQL ServerSQL Server AlwaysOn 技術,應該符合數個 WSFC 相關的必要條件。To take full advantage of SQL ServerSQL Server Always On technologies, you should apply several WSFC-related prerequisites.

如需詳細資訊,請參閱:AlwaysOn 可用性群組的必要條件、限制和建議 (SQL Server)For more information, see: Prerequisites, Restrictions, and Recommendations for Always On Availability Groups (SQL Server)

執行個體層級高可用性與 AlwaysOn 容錯移轉叢集執行個體搭配使用Instance-level High Availability with Always On Failover Cluster Instances

AlwaysOn「容錯移轉叢集執行個體」(FCI) 是在 WSFC 中跨多個節點安裝的 SQL ServerSQL Server 執行個體。An Always On Failover Cluster Instance (FCI) is a SQL ServerSQL Server instance that is installed across nodes in a WSFC. 這種類型的執行個體相依於儲存體和虛擬網路名稱的資源。This type of instance depends on resources for storage and virtual network name. 儲存體可以使用光纖通道、iSCSI、FCoE 或 SAS 做為共用磁碟儲存體,或透過儲存空間直接存取 (S2D) (英文) 來使用本機掛接的儲存體。The storage can use Fibre Channel, iSCSI, FCoE, or SAS for shared disk storage, or use locally attached storage with Storage Spaces Direct (S2D). 虛擬網路名稱資源相依於一個或多個虛擬 IP 位址,每個位址都位於不同的子網路。The virtual network name resource depends on one or more virtual IP addresses, each in a different subnet. SQL Server 服務和 SQL Server Agent 服務也是資源,而且也都相依於儲存體和虛擬網路名稱資源。The SQL Server service and the SQL Server Agent service are also resources, and both are dependent upon the storage and virtual network name resources.

在發生容錯移轉時,WSFC 服務會將執行個體的資源擁有權轉移到指定的容錯移轉節點。In the event of a failover, the WSFC service transfers ownership of instance's resources to a designated failover node. 然後 SQL ServerSQL Server 執行個體會在容錯移轉節點上重新啟動,而且資料庫會照常復原。The SQL ServerSQL Server instance is then re-started on the failover node, and databases are recovered as usual. 在任何給定的時刻,只有一個叢集節點可以裝載 FCI 和基礎資源。At any given moment, only a single node in the cluster can host the FCI and underlying resources.

注意: Always On 容錯移轉叢集執行個體需要對稱共用磁碟儲存體,例如存放區域網路 (SAN) 或 SMB 檔案共用。NOTE: An Always On Failover Cluster Instance requires symmetrical shared disk storage such as a storage area network (SAN) or SMB file share. 共用磁碟存放磁碟區必須可供 WSFC 叢集中所有可能的容錯移轉節點使用。The shared disk storage volumes must be available to all potential failover nodes in the WSFC cluster.

如需詳細資訊,請參閱:AlwaysOn 容錯移轉叢集執行個體 (SQL Server)For more information, see: Always On Failover Cluster Instances (SQL Server)

資料庫層級高可用性 AlwaysOn 可用性群組Always On availability groupsDatabase-level High Availability with AlwaysOn 可用性群組Always On availability groups

AlwaysOn「可用性群組」(AG) 是可一起進行容錯移轉的一或多個使用者資料庫。An Always On Availability Group (AG) is a one or more user databases that fail over together. 可用性群組是由主要 「可用性複本」 (Availability Replica) 和一到四個次要複本所組成,這些次要複本是透過 SQL Server 記錄式資料移動提供資料保護的方式維護,不需要共用儲存體。An availability group consists of a primary availability replica and one to four secondary replicas that are maintained through SQL Server log-based data movement for data protection without the need for shared storage. 每個複本都是由位於 WSFC 的不同節點上的 SQL ServerSQL Server 執行個體所裝載。Each replica is hosted by an instance of SQL ServerSQL Server on a different node of the WSFC. 可用性群組和對應的虛擬網路名稱會註冊為 WSFC 叢集中的資源。The availability group and a corresponding virtual network name are registered as resources in the WSFC cluster.

位於主要複本節點的 「可用性群組接聽程式」 (Availability Group Listener) 會回應連接到虛擬網路名稱的內送用戶端要求,並根據連接字串中的屬性,將每個要求重新導向至適當的 SQL ServerSQL Server 執行個體。An availability group listener on the primary replica's node responds to incoming client requests to connect to the virtual network name, and based on attributes in the connection string, it redirects each request to the appropriate SQL ServerSQL Server instance.

發生容錯移轉時會運用 WSFC,將另一個 SQL ServerSQL Server 執行個體上的次要複本重新設定為可用性群組的主要複本,而不會將共用實體資源的擁有權轉移至另一個節點。In the event of a failover, instead of transferring ownership of shared physical resources to another node, WSFC is leveraged to reconfigure a secondary replica on another SQL ServerSQL Server instance to become the availability group's primary replica. 然後可用性群組的虛擬網路名稱資源會轉移至該執行個體。The availability group's virtual network name resource is then transferred to that instance.

在任何給定的時刻,只有一個 SQL ServerSQL Server 執行個體可以裝載可用性群組的主要資料庫複本,每個相關的次要複本必須位於個別的執行個體,而且每個執行個體必須位於個別的實體節點。At any given moment, only a single SQL ServerSQL Server instance may host the primary replica of an availability group's databases, all associated secondary replicas must each reside on a separate instance, and each instance must reside on separate physical nodes.

注意: AlwaysOn 可用性群組Always On availability groups 不需要部署容錯移轉叢集執行個體或使用對稱共用儲存體 (SAN 或 SMB)。NOTE: AlwaysOn 可用性群組Always On availability groups do not require deployment of a Failover Cluster Instance or use of symmetric shared storage (SAN or SMB).

容錯移轉叢集執行個體 (FCI) 可與可用性群組一起使用,以加強可用性複本的可用性。A Failover Cluster Instance (FCI) may be used together with an availability group to enhance the availability of an availability replica. 不過,為了避免 WSFC 叢集中可能的競爭情形,不支援可用性群組自動容錯移轉至裝載於 FCI 的可用性複本,或從該複本容錯移轉。However, to prevent potential race conditions in the WSFC cluster, automatic failover of the availability group is not supported to or from an availability replica that is hosted on a FCI.

如需詳細資訊,請參閱: 可用性群組概觀 (SQL Server)For more information, see: Overview of Always On Availability Groups (SQL Server)

WSFC 健全狀況監視和容錯移轉WSFC Health Monitoring and Failover

AlwaysOn 方案的高可用性是透過下列方式完成:對實體和邏輯 WSFC 叢集資源的主動式健全狀況監視,以及自動容錯移轉至備援硬體和重新設定備援硬體。High availability for an Always On solution is accomplished though proactive health monitoring of physical and logical WSFC cluster resources, together with automatic failover onto and re-configuration of redundant hardware. 系統管理員也可以起始可用性群組或 執行個體從某個節點 「手動容錯移轉」 SQL ServerSQL Server (Manual Failover) 至另一個節點。A system administrator can also initiate a manual failover of an availability group or SQL ServerSQL Server instance from one node to another.

節點、容錯移轉叢集執行個體和可用性群組的容錯移轉原則Failover Policies for Nodes, Failover Cluster Instances, and Availability Groups

「容錯移轉原則」 是在 WSFC 節點、SQL ServerSQL Server 容錯移轉叢集執行個體 (FCI) 和可用性群組層級上設定。A failover policy is configured at the WSFC node, the SQL ServerSQL Server Failover Cluster Instance (FCI), and the availability group levels. 這些原則根據狀況不良的叢集資源狀態和節點反應速度的嚴重性、持續時間和頻率,可能會觸發服務重新啟動或叢集資源從某個節點 「自動容錯移轉」 (Automatic Failover) 到另一個節點,也可能會觸發可用性群組主要複本從某個 SQL ServerSQL Server 執行個體移至另一個執行個體。These policies, based on the severity, duration, and frequency of unhealthy cluster resource status and node responsiveness, can trigger a service restart or an automatic failover of cluster resources from one node to another, or can trigger the move of an availability group primary replica from one SQL ServerSQL Server instance to another.

可用性群組複本的容錯移轉不會影響基礎 SQL ServerSQL Server 執行個體。Failover of an availability group replica does not affect the underlying SQL ServerSQL Server instance. FCI 容錯移轉會將裝載的可用性群組複本隨著執行個體移動。Failover of a FCI moves the hosted availability group replicas with the instance.

如需詳細資訊,請參閱:Failover Policy for Failover Cluster InstancesFor more information, see: Failover Policy for Failover Cluster Instances

WSFC 資源健全狀況偵測WSFC Resource Health Detection

WSFC 中的每個資源都可以定期或視需要報告其狀態和健全狀況。Each resource in a WSFC can report its status and health, periodically or on-demand. 有許多情況皆意味著資源失效,例如停電、磁碟或記憶體錯誤、網路通訊錯誤或無反應的服務。A variety of circumstances may indicate resource failure; e.g. power failure, disk or memory errors, network communication errors, or non-responsive services.

WSFC 資源 (例如網路、儲存體或服務) 可以彼此相依。WSFC resources such as networks, storage, or services can be made dependent upon one another. 資源的累積健全狀況是透過其個別資源相依性的健全狀況連續積存其健全狀況來決定。The cumulative health of a resource is determined by successively rolling up its health with the health of each of its resource dependencies.

WSFC 節點間健全狀況偵測和仲裁投票WSFC Inter-node Health Detection and Quorum Voting

WSFC 中的每個節點都會參與定期活動訊號通訊,以與其他節點共用節點的健全狀況。Each node in a WSFC participates in periodic heartbeat communication to share the node's health status with the other nodes. 沒有回應的節點是視為處於失敗狀態。Unresponsive nodes are considered to be in a failed state.

「仲裁」 是一種機制,可透過確保 WSFC 中有足夠的資源上線,協助確保 WSFC 啟動並執行。Quorum is a mechanism that helps ensure that the WSFC is up and running through ensuring enough resources are online in the WSFC. 如果 WSFC 有足夠的投票,則其狀況會良好,而且可以提供節點層級容錯。If the WSFC has enough votes, it is healthy and able to provide node-level fault tolerance.

「仲裁模式」 是在指定仲裁投票所使用方法以及指定何時執行自動容錯移轉或使叢集離線的 WSFC 設定。A quorum mode is configured in the WSFC that dictates the methodology used for quorum voting and when to perform an automatic failover or take the cluster offline.

提示!!TIP!! 最佳做法是 WSFC 中一定要有奇數的仲裁投票。It is best practice to always have an odd number of quorum votes in a WSFC. 為了仲裁投票目的, SQL ServerSQL Server 不需要在叢集中的所有節點上安裝。For the purposes of quorum voting, SQL ServerSQL Server does not have to be installed on all nodes in the cluster. 另一個伺服器可以做為仲裁成員,或者 WSFC 仲裁模式可設定為使用遠端檔案共用做為平局決勝者 (Tiebreaker)。An additional server can act as a quorum member, or the WSFC quorum model can be configured to use a remote file share as a tie-breaker.

如需詳細資訊,請參閱:WSFC 仲裁模式和投票組態 (SQL Server)For more information, see: WSFC Quorum Modes and Voting Configuration (SQL Server)

透過強制仲裁執行災害復原Disaster Recovery Through Forcing Quorum

根據操作實務和 WSFC 設定,在發生自動和手動容錯移轉時,您仍然可以維持強固且容錯的 SQL ServerSQL Server AlwaysOn 解決方案。Depending upon operational practices and WSFC configuration, you can incur both automatic and manual failovers, and still maintain a robust, fault-tolerant SQL ServerSQL Server Always On solution. 不過,如果 WSFC 中適合投票之節點的仲裁無法彼此通訊,或者 WSFC 叢集的健全狀況驗證失敗,則 WSFC 可能會離線。However, if a quorum of the eligible voting nodes in the WSFC cannot communicate with one another, or if the WSFC cluster otherwise fails health validation, then the WSFC may go offline.

如果 WSFC 因未規劃的災害或持續硬體或通訊失敗而離線,則需要手動管理介入「強制仲裁」 ,使非容錯設定中的存活叢集節點恢復上線。If the WSFC goes offline because of an unplanned disaster, or due to a persistent hardware or communications failure, then manual administrative intervention is required to force quorum and bring the surviving cluster nodes back online in a non-fault-tolerant configuration.

隨後,也必須採取一連串步驟,重新設定 WSFC、復原受影響的資料庫複本,以及重新建立新仲裁。Afterwards, a series of steps must also be taken to reconfigure the WSFC, recover the affected database replicas, and to re-establish a new quorum.

如需詳細資訊,請參閱:透過強制仲裁執行 WSFC 災害復原 (SQL Server)For more information, see: WSFC Disaster Recovery through Forced Quorum (SQL Server)

SQL Server AlwaysOn 元件與 WSFC 之間的關聯性Relationship of SQL Server AlwaysOn Components to WSFC

SQL ServerSQL Server AlwaysOn 和 WSFC 功能與元件之間有數層關聯性。Several layers of relationships exist between SQL ServerSQL Server Always On and WSFC features and components.

AlwaysOn 可用性群組是裝載在 SQL ServerSQL Server 執行個體上。Always On availability groups are hosted on SQL ServerSQL Server instances.
指定邏輯可用性群組接聽程式網路名稱連線至主要或次要資料庫的用戶端要求,會重新導向至基礎 SQL ServerSQL Server 執行個體或 SQL ServerSQL Server FCI 的適當執行個體網路名稱。A client request that specifies a logical availability group listener network name to connect to a primary or secondary database is redirected to the appropriate instance network name of the underlying SQL ServerSQL Server instance or SQL ServerSQL Server FCI.

「SQL Server 執行個體」(SQL Server Instance) 是在單一節點上主動裝載。SQL Server instances are actively hosted on a single node.
獨立的 SQL ServerSQL Server 執行個體 (如果有) 永遠位於具有靜態執行個體網路名稱的單一節點。If present, a stand-alone SQL ServerSQL Server Instance always resides on a single Node with a static instance network name. SQL ServerSQL Server FCI (如果有) 是作用於兩個以上具有單一虛擬執行個體網路名稱的其中一個可容錯移轉節點。If present, a SQL ServerSQL Server FCI is active on one of two or more possible failover nodes with a single virtual Instance Network Name.

「節點」(Node) 是 WSFC 叢集的成員。Nodes are members of a WSFC cluster.
所有節點的 WSFC 組態中繼資料和狀態都是儲存在各節點上。WSFC configuration metadata and status for all nodes is stored on each node. 每一部伺服器都可提供非對稱的儲存體或共用儲存體 (SAN) 磁碟區讓使用者或系統資料庫使用。Each server may provide asymmetric storage or shared storage (SAN) volumes for user or system databases. 每個伺服器都至少有一個位於一個或多個 IP 子網路的實體網路介面。Each server has at least one physical network interface on one or more IP subnets.

WSFC 會監視健全狀況,並管理一組伺服器的設定。The WSFC monitors health and manages configuration for a group of servers.
WSFC 機制會傳播 WSFC 設定中繼資料以及 WSFC 中所有節點狀態的變更。The WSFC mechanisms propagate changes to WSFC configuration metadata and status to all nodes in the WSFC. 如果使用磁碟見證,則中繼資料也會儲存在該處。If a disk witness is used, the metadata is also stored there. 根據預設,WSFC 的每個節點都會取得仲裁的投票,並在需要且設定時使用見證。By default, each node of the WSFC gets a vote towards quorum and a witness will be used if necessary and is configured.

AlwaysOn 可用性群組Always On availability groups 登錄機碼是 WSFC 叢集的子機碼。registry keys are subkeys of the WSFC cluster.
如果您刪除後重新建立 WSFC,則必須針對原始 WSFC 上已啟用 AlwaysOn 可用性群組Always On availability groups 的每個伺服器執行個體,停用後重新啟用 AlwaysOn 可用性群組Always On availability groups 功能。If you delete and re-create a WSFC, you must disable and re-enable the AlwaysOn 可用性群組Always On availability groups feature on each server instance that was enabled for AlwaysOn 可用性群組Always On availability groups on the original WSFC. 如需詳細資訊,請參閱啟用和停用 AlwaysOn 可用性群組 (SQL Server)For more information, see Enable and Disable Always On Availability Groups (SQL Server).

SQL Server AlwaysOn 元件內容圖表SQL Server AlwaysOn Component Context Diagram

相關工作Related Tasks

相關內容Related Content

另請參閱See Also

AlwaysOn 容錯移轉叢集執行個體 (SQL Server) Always On Failover Cluster Instances (SQL Server)
AlwaysOn 可用性群組概觀 (SQL Server) Overview of Always On Availability Groups (SQL Server)
WSFC 仲裁模式和投票組態 (SQL Server) WSFC Quorum Modes and Voting Configuration (SQL Server)
容錯移轉叢集執行個體的容錯移轉原則 Failover Policy for Failover Cluster Instances
透過強制仲裁執行 WSFC 災害復原 (SQL Server)WSFC Disaster Recovery through Forced Quorum (SQL Server)
SQL Server 2016 支援 Windows Server 2016 儲存空間直接存取 (英文)SQL Server 2016 Supports Windows Server 2016 Storage Spaces Direct