Windows Failover Cluster를 관리 하다보면 Domain과 너무 강하게 연결 되어 있다는 것을 알 수 있습니다. Windows Server 2016 이전에는 Failover Cluster를 구축할 때 Active Directory Domain이 꼭 필요 했었기 때문에 단순이 SQL Server Cluster를 만들기 위해서 Active Directory 서버가 필요했습니다. 그리고 Active Directory가 잘 관리 되지 않으면 Failover Cluster의 인증 문제나 Network Name 리소스에 문제가 생기기도 하였습니다.

Windows Server 2016 부터는 Multi-Cluster, Workgroup Cluster 가 나오면서 이 문제가 많이 해결되었습니다.

Windows Server, version 1709에서는 더 새로운 기능이 추가되었는데 Failover Cluster를 다른 도메인으로 이동할 수 있는 기능 입니다. Active Directory와 Failover Cluster 관계를 살펴 보면 Cluster 이름이 CNO라는 것으로 Active Directory에 등록되어 있고 각 리소스의 Network Name Resource가 VCO라는 것으로 Active Directory에 등록되어 있는 것입니다. CNO, VCO 그리고 각 노드의 Computer Object 들이 각각 권한 설정이 되어 있습니다.

Windows Server, version 1709에서는 아래 방법으로 Domain을 이동할 수 있습니다.

환경 : 모든 노드가 Windows Server, version 1709 Failover Cluster

        FS-CLUSTER 라는 파일 서버가 리소스로 등록되어 있습니다.


1. 모든 Cluster Network Name 리소스를 Offline으로 만듭니다.

2. Cluster 타입을 Workgroup으로 만듭니다.

   Remove-ClusterNameAccount -Cluster MyCluster -DeleteComputerAccounts

3. Active Directory Users and Computers 에서 CNO와 VCO가 삭제된 것을 확인합니다.

4. Cluster 서비스를 중지하고 시작 유형을 변경 합니다.

   Stop-Service -Name ClusSvc

   Set-Service -Name ClusSvc -StartupType Manual

5. Failover Cluster 노드를 Workgroup으로 변경한 후 다시 새로운 Domain에 join 합니다.

6. Cluster 서비스를 다시 시작하고 시작 유형을 변경합니다.

   Start-Service -Name ClusSvc

   Set-Service -Name ClusSvc -StartupType Automatic

7. Cluster 이름과  Network Name 리소스를 Online 시킵니다.

   Start-ClusterGroup -Name "Cluster Group"

   Start-ClusterResource -Name FS-Clus

8. 새로운 Domain에 등록 합니다. (Network Name 리소스는 꼭 Online 상태이어야 합니다.)

   New-ClusterNameAccount -Name MyCluster-Domain NewDomain.com -UpgradeVCOs

9. 새로운 도메인의 Active Directory Users and Computers 에서 새로 생성된 CNO, VCO를 확인합니다.

10. 파일 서버 리소스를 시작 합니다.

   Start-ClusterGroup -Name FS-Cluster


기업 환경에서는 Windows Server, version 1709를 아직은 적용하지 못할 것이기 때문에 이 기능을 사용할 수 없겠지만 Windows Server의 기능들이 빠르게 변화하고 있는 것을 확인할 수 있었습니다.


감사합니다.

Failover Clustering & Hyper-V 관련 Hotfix 모음 입니다.

Windows Server 2012 
  Recommended hotfixes and updates for Windows Server 2012-based failover clusters
  https://support.microsoft.com/en-us/kb/2784261 

 

Creating multiple File Server resources in one group may not work correctly in a Windows Server 2012 Failover Cluster
  https://support.microsoft.com/en-us/kb/2993295

 

  Starting or Live Migrating Hyper-V virtual machines may fail with error 0x80070569 on

Windows Server 2012-based computers
  https://support.microsoft.com/en-us/kb/2779204

 

  Stop error 0x9E and failover cluster can't come online in Windows Server 2012
  https://support.microsoft.com/en-us/kb/3130902

 

 

Windows Server 2012 and Windows Server 2012 R2
  Hyper-V virtual machines cannot be connected to sometimes when TCP connections reconnect in Windows
https://support.microsoft.com/en-us/kb/2972254
Article ID: 2972254 - Last Review: 03/10/2016 08:04:00 - Revision: 8.0
  This issue occurs when a TCP connection breaks and then reconnects. A TCP acknowledgement is not received in the node-to-node communication on a Windows Server 2012 R2 failover cluster, and the node that does not receive the TCP acknowledgement is removed from the active failover cluster membership. Error 5023 is logged in the cluster.log file of the node that is removed from the active failover cluster membership. For example, the following error 5023 is logged in the cluster.log file on the   FC-NODE2 node that corresponds to the previous System log:
00000b7c.00001254::Date-Time WARN [PULLER FC-NODE2] ReadObject failed with GracefulClose(1226)' because of 'channel to remote endpoint fe80::####:####:####:####%##:~49256~ is closed'.
00000b7c.00000fa8::Date-Time ERR [CORE] mscs::NodeObject::OnMessageReceived:

(5023)' because of 'Can't remove sent messages from an empty sent messages queue.'
00000b7c.00000fa8::Date-Time ERR [NODE] Node 8: Error processing message from n1, starting Regroup.

Notefe80::####:####:####:####%## represents the hexadecimal number that represents an IPv6 address.  

 

Stop error code 0xD1, 0x139, or 0x3B and cluster nodes go down in Windows Server 2012 R2 or Windows Server 2012
https://support.microsoft.com/en-us/kb/3055343
  Article ID: 3055343 - Last Review: 03/08/2016 19:13:00 - Revision: 6.0
  Issue 1
  When you delete network interfaces on a server that is running Windows Server 2012   R2 or Windows Server 2012, you experience random and intermittent crashes on the system, and you also receive one of the following Stop error messages:
  •0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  •0X139: KERNEL_SECURITY_CHECK_FAILURE
  •0x3B: SYSTEM_SERVICE_EXCEPTION
  Issue 2
  Some cluster nodes that are running Windows Server 2012 R2 or Windows Server 2012 go down because of the corruption in NDIS and netcfg.

 

  Hyper-V integration components update for Windows virtual machines that are running on a Windows 10-based host
  https://support.microsoft.com/en-us/kb/3063109 

 

Cluster service stops during the VSS backup in a Windows Server 2012 R2 or Windows Server 2012-based Hyper-V cluster 
  https://support.microsoft.com/en-us/kb/3090343

 

 

Windows Server 2012 R2
  A virtual machine that is running on Windows Server 2012 R2 may not start
  https://support.microsoft.com/en-us/kb/2962295

 

  Disk resource does not come online in Windows Server 2012 R2 or Windows Server 2008 R2-based failover cluster
  https://support.microsoft.com/en-us/kb/3033918
  Article ID: 3033918 - Last Review: 03/11/2016 03:55:00 - Revision: 4.0
  Assume that a disk resource name contains unauthorized file system characters, such as colon (:) or backslash (\), in a Windows Server 2012 R2 or Windows Server 2008 R2-based failover cluster, and the disk becomes dirty. In this situation, the chkdsk command does not run as expected, and the disk resource cannot come online.

  Stop Error "0x0000007E" occurs in a Windows Server 2012 R2-based Hyper-V cluster
  https://support.microsoft.com/en-us/kb/3063000

 

Cluster validation fails in the "Validate Simultaneous Failover" test in a Windows Server 2012 R2-based failover cluster
https://support.microsoft.com/en-us/kb/3091057
Article ID: 3091057 - Last Review: 03/11/2016 06:33:00 - Revision: 3.0
When you run failover cluster validation, the validation may fail during the storage validation tests. It may occur by using Validate a Configuration Wizard from Failover Cluster Manager or by initiating validation that uses the "Test-Cluster" PowerShell cmdlet. 

 

 

Windows 10

Hy  A multi-site failover cluster goes into a split brain situation in Windows Server 2012 R2 
  https://support.microsoft.com/en-us/kb/3123593

 

Hyper-V integration components update for Windows virtual machines that are running on a Windows 10-based host

https://support.microsoft.com/en-us/kb/3063109?sd=rss&spid=16796
Article ID: 3063109 - Last Review: 03/11/2016 01:56:00 - Revision: 4.0
Issue 1
Consider the following scenario:
•You connect a VM to a virtual switch that uses a physical adapter.
•You enable the single root I/O virtualization (SR-IOV) option in Virtual Switch Manager.
•You disable the physical adapter on the Hyper-V guest while network I/O is running in the VM.
In this scenario, the VM crashes.
Issue 2
The current Write Ahead Logging (WAL) implementation incorrectly assumes that the Virtual Hard Disk (VHD) ownership never changes. However, the ownership does change in multiple VM group replication in a shared VHD scenario

 

Windows Server 2012, 2012 R2 Failover Cluster Hotfix 입니다.

"0x00000050" Stop error on a failover cluster that is running Windows Server 2012 R2 or Windows Server 2012
https://support.microsoft.com/en-us/kb/3047331?sd=rss&spid=16796
Article ID: 3047331 - Last Review: 01/12/2016 21:34:00 - Revision: 2.3

+ Recent posts