windows_advanced_failover

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
windows_advanced_failover [2019/11/04 18:48] – [Configuration] andonovjwindows_advanced_failover [2019/11/05 19:43] (current) – external edit 127.0.0.1
Line 26: Line 26:
   - Access Points for Administering the Cluster -> Choose the Cluster Name -> Next   - Access Points for Administering the Cluster -> Choose the Cluster Name -> Next
   - Confirmation -> Next   - Confirmation -> Next
-  - +  - Prerequisites Check -> Next 
 +  - Completed -> Close 
 + 
 +I had to create a 3rd server. WINNODEC and addining it to the domain: SQLDOM.COM, since WINNODEA and WINNODEB were in different organizational unit (OU). With winnodeA being Domain controler and winnodeB being part of the cluster. 
 + 
 +After creating the 3rd server, installing failover capabilities and adding it to the domain. All tests passed :) Exept the single network ones. 
 + 
 +Now we have empty failover cluster without any disk failovers or IP failovers or storage pool: 
 + 
 +{{ :failovercluster.jpg?600 |}} 
 + 
 + 
 +I have also allowed communication between the servers on LDAP level and made them trusted for delegation of service: 
 + 
 +{{ :security_delegation.jpg?400 |}} 
 + 
 + 
 + 
  • windows_advanced_failover.1572893290.txt.gz
  • Last modified: 2019/11/05 02:48
  • (external edit)