Hi!

My company is setting up two Windows Server 2016 RDS servers in a high availability group. I would like to understand how many device cals I need in a high availability environment.

Lets say both servers are served by the connection broker using load balancing. I have 100 device cals. 40 devices active on node 1 and 40 on node 2. So there are 80 permanent cals assigned and 20 free.

What happens when node 1 goes down and all clients reconnect to node 2. Do they acquire new licences?(only 20 non-assigned cals are available) or do they connect with the same permanent cals they used on node 1?

Found this (https://www.microsoftpressstore.com/articles/article.aspx?p=2346349&seqNum=4) document on the forum here, but did not find the reply to my question.

EDIT: the document from the link above says the following:
"Splitting (device) CALs between two RD Licensing servers is slightly more expensive because you need to purchase additional CALs for the secondary RD Licensing server."

One could interpret that as the necessity to buy all licences twice.

Best regards,

Andy

Hi All,

We have a 2 nodes Windows Server 2012 R2 Hyper-V cluster in production.

To test Hyper-V replication, we setup an additional 2 node cluster running server 2016. This cluster is used as the replica (secondary site).  

The replication started happily for 2 offline VMs and towards the end of the initial copy, one of the node from the primary site cluster (2012 R2) went blue screen. The owner of the replicating VM was node 2 and the replication broker was running on node 2 as well.

Bug check analysis below, appreciate if some one can shed some light on this issue.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

FILE_SYSTEM (22)
Arguments:
Arg1: 00000000000e00f6
Arg2: ffffd001bb9b8438
Arg3: ffffd001bb9b7c40
Arg4: fffff800024d994a

Debugging Details:
------------------

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  9600.17415.amd64fre.winblue_r4.141028-1500

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  ProLiant DL380p Gen8

SYSTEM_SKU:                 

BIOS_VENDOR:  HP

BIOS_VERSION:  P70

BIOS_DATE:  08/02/2014

DUMP_TYPE:  1

BUGCHECK_P1: e00f6

BUGCHECK_P2: ffffd001bb9b8438

BUGCHECK_P3: ffffd001bb9b7c40

BUGCHECK_P4: fffff800024d994a

CPU_COUNT: 30

CPU_MHZ: a85

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3e

CPU_STEPPING: 4

CPU_MICROCODE: 6,3e,4,0 (F,M,S,R)  SIG: 428'00000000 (cache) 428'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x22

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  ADM01

ANALYSIS_SESSION_TIME:  05-02-2019 20:47:01.0954

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

EXCEPTION_RECORD:  ffffe80023307880 -- (.exr 0xffffe80023307880)
ExceptionAddress: ffffe80023307888
   ExceptionCode: 00000006
  ExceptionFlags: 00000000
NumberParameters: 0

LAST_CONTROL_TRANSFER:  from fffff801f8c9d980 to fffff800025d29a0

STACK_TEXT: 
ffffd001`bb9b73e8 fffff801`f8c9d980 : 00000000`00000022 00000000`000e00f6 ffffd001`bb9b8438 ffffd001`bb9b7c40 : nt!KeBugCheckEx
ffffd001`bb9b73f0 fffff801`f8d208f7 : fffff801`f8ce1908 00000000`00000000 00000000`00000000 00000000`00000000 : CsvFs!CsvFsExceptionFilter+0xf8
ffffd001`bb9b7430 fffff800`025c1a96 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : CsvFs!CsvFsFsdCreate$filt$0+0x15
ffffd001`bb9b7470 fffff801`f8cd8852 : fffff801`f8ce1918 ffffd001`bb9b8438 ffffd001`bb9b8a80 00000000`00000000 : nt!_C_specific_handler+0x86
ffffd001`bb9b74e0 fffff800`025d9eed : 00000000`00000000 ffffd001`bb9b7640 ffffd001`bb9b8438 00000000`00000000 : CsvFs!_GSHandlerCheck_SEH+0x76
ffffd001`bb9b7510 fffff800`0255c125 : 00000000`00000001 fffff801`f8c93000 ffffd001`bb9b8400 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd
ffffd001`bb9b7540 fffff800`025604de : ffffd001`bb9b8438 ffffd001`bb9b8140 ffffd001`bb9b8438 ffffc002`29e27ae0 : nt!RtlDispatchException+0x1a5
ffffd001`bb9b7c10 fffff800`025de5c2 : ffffe800`23307880 ffffd001`bb9b8380 ffffe000`b3c1a040 fffff800`024d9e27 : nt!KiDispatchException+0x646
ffffd001`bb9b8300 fffff800`025dcd14 : 00000000`00000000 ffffe800`1ddca1c0 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffd001`bb9b84e0 fffff800`024d994a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x214
ffffd001`bb9b8670 fffff801`f8ccb370 : 00000000`00000000 ffffe800`1ddca1c0 00000000`00000000 00000000`00000000 : nt!IoGetRelatedDeviceObject+0xa
ffffd001`bb9b86a0 fffff801`f8ccbc81 : ffffe800`1ddca1c0 ffffd001`bb9b8770 ffffd001`bb9b8960 ffffe800`1ddca1c0 : CsvFs!CsvFsSyncFsControl+0x38
ffffd001`bb9b8720 fffff801`f8d03214 : 00000000`00000000 ffffe800`1ddca1c0 ffffe800`205ddce0 ffffe800`1a369700 : CsvFs!CsvFsTunnelQueryFileRevision+0x85
ffffd001`bb9b88f0 fffff801`f8d0227e : ffffe800`1a2591d0 00000000`000902d4 ffffe800`1ddca1c0 00000000`00000000 : CsvFs!CsvFsQueryFileRevision+0x144
ffffd001`bb9b8980 fffff801`f8d010ab : 00000000`000902d4 ffffc002`29e27ae0 ffffc002`7a80f010 ffffe800`1a2591d0 : CsvFs!CsvFsHandleInternalFsCtl+0xae
ffffd001`bb9b89c0 fffff801`f8cffe50 : ffffe800`1ddca1c0 ffffc002`7a80f010 ffffc002`29e27ae0 ffffe800`1a2591d0 : CsvFs!CsvFsUserFsCtrl+0x8bf
ffffd001`bb9b8a40 fffff801`f8cffccd : ffffe800`1ddca1c0 00000000`00000001 ffffe800`1a2591d0 00000000`00000000 : CsvFs!CsvFsCommonFileSystemControl+0xe0
ffffd001`bb9b8a80 fffff801`f76f4b1e : 00000000`00000000 00000000`00000000 ffffe800`2b312c80 00000000`00000000 : CsvFs!CsvFsFsdFileSystemControl+0x145
ffffd001`bb9b8b10 fffff801`f76f8188 : ffffd001`bb9b8bd8 ffffe800`2b312c80 ffffe800`2b312d58 00000000`00000000 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2ce
ffffd001`bb9b8bb0 fffff801`f7722eda : ffffe800`62694d46 ffffe800`2b312d58 ffffe800`205ddce0 00000000`00000000 : fltmgr!FltPerformSynchronousIo+0x2b8
ffffd001`bb9b8c60 fffff801`f77231a9 : ffffd001`bb9b8fd1 ffffe800`23307880 ffffd001`bb9b8db8 00000000`00000000 : fltmgr!IssueControlOperation+0x14e
ffffd001`bb9b8ce0 fffff801`f7751ce1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltFsControlFile+0x45
ffffd001`bb9b8d40 fffff801`f7752d52 : ffffe000`bd432010 ffffe800`27948350 ffffd001`bb9b8e18 00000000`00000000 : cvcbt+0x3ce1
ffffd001`bb9b8dd0 fffff801`f775ad50 : ffffe000`bd432010 ffffe800`27948350 ffffc001`fbe486c0 ffffe800`0000001b : cvcbt+0x4d52
ffffd001`bb9b8e50 fffff801`f775a85e : ffffe000`eb48ad58 ffffd000`303d84f8 ffffd000`303d84e0 ffffc001`fbe48660 : cvcbt+0xcd50
ffffd001`bb9b8f00 fffff801`f775a9fb : ffffe000`eb48ad58 ffffd000`303d84f8 ffffc001`fbe48660 ffffd000`303d84e0 : cvcbt+0xc85e
ffffd001`bb9b8f40 fffff800`025d62f7 : ffffc002`16d98bf0 ffffd000`303d8529 ffffe800`23307880 00000000`00000000 : cvcbt+0xc9fb
ffffd001`bb9b8f80 fffff800`025d62bd : ffffe800`27948301 00000000`00011800 00000000`00000001 fffff800`024c0a7d : nt!KxSwitchKernelStackCallout+0x27
ffffd000`303d8200 fffff800`024c0a7d : ffffd000`00000012 ffffe800`27948301 00000000`00000006 fffff800`02725b5b : nt!KiSwitchKernelStackContinue
ffffd000`303d8220 fffff801`f775ebaf : fffff801`f775a9c0 ffffc002`16d98bf0 00000000`10000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x2fd
ffffd000`303d8310 fffff801`f77694ed : fffff801`f775a9c0 ffffe000`eb48ad58 ffffd000`303d84f8 ffffc001`fbe48660 : cvcbt+0x10baf
ffffd000`303d8380 fffff801`f76f403f : ffffe000`eb48ad58 ffffd000`303d84f8 ffffd000`303d84e0 ffffe000`bd432440 : cvcbt+0x1b4ed
ffffd000`303d8480 fffff801`f76f6d8d : ffffd000`303d85f8 ffffd000`303d8500 ffffe800`181e7000 00000000`000008ff : fltmgr!FltpPerformPreCallbacks+0x29f
ffffd000`303d8590 fffff800`024d3ae6 : ffffd000`303d86f0 ffffe800`1c6ebdb0 ffffe800`1a2b1df0 ffffe800`1c6ebda0 : fltmgr!FltpPreFsFilterOperation+0x2dd
ffffd000`303d8660 fffff800`02860fe8 : 00000000`00000000 ffffd000`303d87b0 fffff801`f8ce5b40 ffffe000`b9636f10 : nt!FsFilterPerformCallbacks+0x12a
ffffd000`303d86b0 fffff800`024d258f : 00000000`00000005 ffffe000`cb9585a0 ffffe000`cb9586b8 ffffe000`cb9585a0 : nt!FsRtlAcquireFileExclusiveCommon+0xf8
ffffd000`303d8970 fffff800`024ce941 : ffffe000`c7e3b7f0 00000000`00000000 fffff800`00000000 00000009`8c000000 : nt!CcWriteBehindInternal+0x2df
ffffd000`303d8a00 fffff800`024cecf9 : 00000000`00000000 ffffe000`b3d73cf0 ffffe800`f8406150 00000000`00000000 : nt!CcWriteBehind+0x95
ffffd000`303d8aa0 fffff800`0251e38c : fffff801`f840c300 ffffe800`23307900 fffff800`0276a3c0 00000000`00000000 : nt!CcWorkerThread+0x22d
ffffd000`303d8b50 fffff800`02583c70 : 00000000`00000000 ffffe800`23307880 00000000`00000080 ffffe800`23307880 : nt!ExpWorkerThread+0x28c
ffffd000`303d8c00 fffff800`025d8fc6 : ffffd001`b5593180 ffffe800`23307880 ffffd001`b559fdc0 ffffd000`303d8d90 : nt!PspSystemThreadStartup+0x58
ffffd000`303d8c60 00000000`00000000 : ffffd000`303d9000 ffffd000`303d3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

THREAD_SHA1_HASH_MOD_FUNC:  1e249f2320ec81cd4a51898c23c4873ff9352319

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  9c468e10205fe846d505545f21d552f94a7d9eee

THREAD_SHA1_HASH_MOD:  72a602436973088709b6b7f1e52a9d9bf366a3ff

FOLLOWUP_IP:
CsvFs!CsvFsExceptionFilter+f8
fffff801`f8c9d980 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  CsvFs!CsvFsExceptionFilter+f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CsvFs

IMAGE_NAME:  CsvFs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5434e8a6

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  f8

FAILURE_BUCKET_ID:  0x22_CsvFs!CsvFsExceptionFilter

BUCKET_ID:  0x22_CsvFs!CsvFsExceptionFilter

PRIMARY_PROBLEM_CLASS:  0x22_CsvFs!CsvFsExceptionFilter

TARGET_TIME:  2019-04-30T03:32:37.000Z

OSBUILD:  9600

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  400

PRODUCT_TYPE:  3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

OSEDITION:  Windows 8.1 Server TerminalServer DataCenter SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2014-10-29 08:38:48

BUILDDATESTAMP_STR:  141028-1500

BUILDLAB_STR:  winblue_r4

BUILDOSVER_STR:  6.3.9600.17415.amd64fre.winblue_r4.141028-1500

ANALYSIS_SESSION_ELAPSED_TIME:  6dc8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x22_csvfs!csvfsexceptionfilter

FAILURE_ID_HASH:  {6fcdb60f-8e12-d6e8-8b1a-c52939f01fff}

Followup:     MachineOwner
---------

I have 2016 Functional level cluster with Server 2019 (basically in a process of replacing 2016 host with 2019)

If VM is running on 2019 host I can poweroff, quick migrate to 2016 host, power on & all is good

But Live migration always gives me above error

All I am getting in Event Data is (very descriptive?!):

Live migration of 'Virtual Machine Test' failed.

Nothing else, no reason.

If VM is running on 2016 host I CAN do live migration to 2019 fine! (albeit with errors reported in this thread, but I do NOT have VMM being used!)

vm\service\ethernet\vmethernetswitchutilities.cpp(124)\vmms.exe!00007FF7EA3C2030: (caller: 00007FF7EA40EC65) ReturnHr(138) tid(2980) 80070002 The system cannot find the file specified.
    Msg:[vm\service\ethernet\vmethernetswitchutilities.cpp(78)\vmms.exe!00007FF7EA423BE0: (caller: 00007FF7EA328FEE) Exception(7525) tid(2980) 80070002 The system cannot find the file specified.
] 

Both host are IDENTICAL hardware on same firmware level of every component!

There is NOTHING relating to even attempting migration in local host Hyper-V VMMS/Admin/Operational logs

In Hyper-V High Availability/Admin I get same error but with Even ID 21111

Seb

Hi,

We just lost 5 node hyper-v cluster with no access to iscsi csv volumes.

Is it possible that we could reconnect iscsi volumes to some different physical server to get VMs back.

If we do that I guess we will have RAW volumes connected to non clustered server?

Is any way we could get information from csv volumes back?

Thanks

Hello

Need one hint on HA to a prob i have in a test env.
- Cluster of 2x nodes SQL Server 2016 @ Windows server 2012R2

- Have 3 databases in HA group and running fine.

- Did some switchover within the SQL and runned fine so far.

- Did tests to the Windows server and they were not so good, on of the tests was todisconnect primary Replica _network card_ on the cluster and Everything stopped.
The secondary replica that should be taking over, did not, and left the Windows Server Failover Cluster
The databases become unused on Secondary Replica.

To repair this, i do: turn back the network on primary replica, re-add the secondary replica to the cluster, make the Role to go Online on the Secondary Replica. Seems very odd

Im running this infra on a VM environment.

What am i missing?
Thanks in advance

Hi Guys,

I have configured a cluster with two nodes both nodes have exact hardware but when I simulate failure I get the below error message.



Also when I try to do live migration a VM it stops at 3%.

Failed to create Planned Virtual Machine at migration destination: An unexpected error occurred. (0x800300FD). (Virtual machine ID 5055410D-C5F0-42FE-B3EF-D92DB11F0395)

What could be issue ?

Hi community,

Is that possible to add a second virtual IP address (on different subnet from the first VIP) on a windows failover cluster?

I don't find where I can add it from the console.

Thanks for your return.

BR,

What is the proper way to shut down a cluster?

We have been testing to find a way to have a node shutdown without the VMs moving all over the place.

We have a three node cluster in production, but to test different shutdown procedures I have set up a 2 node cluster with a share in Node and File Share majority.

My goal is to shut down the cluster without any of the VMs moving to a different host.

Thus far I have tried pausing the nodes with Do NOT Drain Roles specified. I have one role off and the other running. I understand that in an HA cluster that ideally you would want all of your roles to transfer to an online host whether they are running or not, but there has to be a way to force the role to stay where it is on failure. Right now, if we have to shut down our cluster in the event that power is out and we run out of battery, we do not know where a VM will be when they come back online.

I understand we can specify a preferred node for the VM, but is there a way to set the cluster up so that when a node is shut down the VMs do not transfer? We are looking to create a powershell script to run from the UPS when we reach a certain run time, but I have no idea what the process is, so I don't know how to get my script in line.

Any suggestions will be appreciated. Until then I will keep reading and testing.

Thank You

Dear Support,

I have two servers one with 6 cores intel Xeon E5_2620  2.0 Ghz and the other  with 8 cores intel Xeon E5_2640 V3 2.6Ghz.

i plan to install windows server 2016 with hyper-V, my question is can i configure high availability between the two server with two different cpu

thank you

Hi,

I have 2 Windows Server 2008 R2 servers configured in fail-over cluster environment with 7 Cluster disks.

Yesterday I got an error in the "cluster event" that the "Cluster Disk 2" is failed and not coming online.



When I am trying to manually making online these disks, I am getting this error

I have validated the cluster configuration and it failed.

I have checked for the disk in my disk management, and its showing offline, and I am not getting any option to bring it online.

I have also tried making disk online through diskpart, but it did not work.

Now what is happening, when I move my cluster disks from one node to another, its working fine and applications hosted on cluster is also running.

But when I restart one node from the cluster, disks goes down in another node as well with error in event viewer.

Can anyone help??

Hi,

I installed 2 windows 2012 servers and created a cluster of these 2 servers.

I created 2 iscsi target from the iomega ix4-200d Nas.

I used the microsoft iscsi initiator to connect to the 2 iscsi drives from the 2 servers.

When I go to add the storage on the cluster failover console, I see that the added disk is in failed state.

When I try to bring it online I get an error and it shows in the event viewer:

Cluster resource 'Cluster Disk 1' of type 'Physical Disk' in clustered role 'Available Storage' failed. The error code was '0x1' ('Incorrect function.').

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Any help will be appreciated.

Thank you.

-Mehdi

Hello just wondering if it is ok to have 2 failover clusters, where the cluster networks are in the same VLAN, or if this may cause issues between nodes of the different clusters. example scenario for clarity below.

1. a Hyper-V 3 node cluster is in place, and has 2 cluster networks, on seperate private VLAN's / subnets (cluster and Live migration nets.)

2. A guest cluster of 2 VM's is hosted on this hyper-v cluster, in this case, is it ok to have this guest clusters network utilize the same cluster network as the host, same vlan / same subnet, but with different IP's from the subnet obviously.

Is this ok, or is there any potential for the cluster nodes from the different clusters to have issues with this, I cant find any detail on this point, only lots of information about multi subnet clusters, which is not relevant.

Cheers.

I have a server 2019 cluster, when I run validation I get a warning The setting for HangRecoveryAction on this cluster is not the default and recommended setting, can someone tell me how I set it.

Thanks

Greetings. My question is more pertaining to SQL Server Always On, but I figured if this piece doesn't work that won't for sure.

That said, I found this doc for a rolling upgrade from 2012 R2 to 2016, but this assumes there's an existing 2012 R2 cluster. What if I simply want to  create a new cluster w 2012 R2 on one node and 2016 on the other for the purpose of migrating to a new data center where the vendor doesn't still support 2012 R2? 

I know there are MANY things wrong with this plan, but I still need to find out if it's possible for management. 

Thanks in advance! ChrisRDBA

Hi,

I have a requirement to change cluster IP and its node's IP address, wanted to know its impact on witness disk.

What will happen to the witness disk if IP addresses are changed? 

Thank you!

My domain contains 2 member servers named Server1 and Server2 running W2K12R2. Server1 and Server2 have failover cluster feature installed. Servers are configured as nodes in failover cluster. I add additional 2 nodes in cluster. I need to ensure that cluster stops working if 3 nodes get failed. Which property I should configure?

Hi Experts

i am new to Windows Clustering i have only little knowledge. i was asked in an interview if you have two nodes in a sql cluster.and instance has failed over from node1 to node2, what will you check.

1. i said i will generate cluster validation report and check

2. I said i will check any issue related to hardware, if HBA is down.

Experts guide me, what could be the reason of fail over and what needs to be checked.

On windows server 2012 R2 and windows server 2019

I have been trying to setup a Clustered file server role and then I wanted to point at it trough a load balancer. But When I try to access the shares with the cname, the shares are not enumerated, or shown.



I used

setspn -a host/cname cluster_role_name

and

setspn -a host/cname.fqdn cluster_role_name

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

3. Add a new REG_DWORD 32bit entry using the edit menu.

Value name: DisableStrictNameChecking

Any Ideas What I am missing?