Dear Friends,

Kindly share the documents with your own experience as you haveonfigured cluster and hyper V with two servers.

Server operating system: 2012 R2.

Single shared storage disk space configured in both the servers.

Hello guys,

  I had a problem in my cluster where the CSV settings were lost and the VMs were in state critical, we had to redo the cluster again, but when we add the virtual machines in Failover Cluster, it generates errors .. only two machines that were added.

I started looking for something similar on the net, but I did not succeed. So I did a test with a VM that did not criticize and I exported and imported and to my surprise that VM was added to the failover cluster. With everything I can not do this with the other VMs, since they are production.

What I'm finding is that it went into state saved and did not return to the original.

Does anyone have any ideas that can help me?

below

There was a failure bringing the virtual machine configuration resource 'Virtual Machine Configuration ' online.

There was a failure configuring the virtual machine role for 'name_virtualmachine'.
An error occurred while attempting to bring the resource 'Virtual Machine Configuration ' online.

The cluster resource could not be brought online by the resource monitor

thank you.

Dear Friends,

Have configured additional mailbox in outlook 2016. however, while opeing it in outlook, getting error attached. Have reconfigurred outlook and checked, same issue. Have configured same mailbox on user laptop, its opening. (This user uses laptop and desktop. issue only with his desktop)

Operating system on the desktop: Windows 7.

Kindly help me with solution.

Any one knows why I am getting the following error ? It's windows 2016

https://blogs.msdn.microsoft.com/igorpag/2016/01/25/configure-an-ilb-listener-for-sql-server-alwayson-availability-groups-in-azure-arm/

Hello

I have four nodes that is configured as a set switch with two nic ports.

To this I have two switches.

If one switch fails all node remains online but if one switch becomes isolted but is fully functional the node doesn´t understand that it should failover. So the nodes that is active on that switch goes offline.

How do I solve this

Thankyou

Hello,

I have question regarding to virtual machine. I have created hyperV cluster and on one node I created 2 virutal machines. Problem is that in cluser I can see only one virtual machine that I choose in HyperV manager . If I select in HyperV manager second VM then in Cluster I can see second machine. Of course booth are running. This is how it works on WS2016

On WS2012 in Cluser I can see both VM that are pn pysical server in one node. I dont have to switch in HyperV manager. Am I making some mistake ? 

Best regards,

Bartek

Hi, i support a small Failover Cluster two node setup of Server 2012 R2 which has an iscsi SAN for storage and a teamed 10Gb link dedicated to guest vm network access. Recently we have noticed the following:

A live migration of a guest vm from one host to the other results in:

Loss of network connection TO the guest vm from anywhere (either host, other vms, outside real physical pc etc)

Network connectivity FROM the guest vm however is ok (so the guest retains internet access, dns lookups, can ping other devices

After 10 minutes full network access to the guest vm returns

Things i have noted:

MAC address of guest vm seems to stay the sameRunning a wireshark indicates that there are two GARP's announced at the point where connectivity ceases

Wireshark shows icmp requests from the guest vm to other devices (so we are actually pinging the devices we think we are pinging).

The 10Gb network link is via a cisco sg500x stack of 4 switches, the MAC addrss table refresh on this appears to be 300 secs.

Has anybody seen anyhting like this before ?

Thanks

Roger

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
---------

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.

Best regards,

Andy

Hello!

We have a Hyper V cluster setup which includes Multiple blade servers  all are running Windows 2012.  When i try to live migrate between nodes,only one node occurred below error.

Note:

That node hardware configuration are same as other nodes.

--------------------------------------------------------------------------------------------------------------------------------------------

Hello Team,

My cluster is getting disconnected when i open failover cluster manager.

When i ping the cluster name , it's requested timed out.

I tried to move the server hosting cluster from one esxi node to another in different ESXi cluster and could see one service went offline and again i moved back server hosting cluster to the original ESXi node on which it was residing.

Please let me if i can restart cluster service on the server once , I am not able to connect to my cluster and it's says "Cluster got disconnected".

Paramesh KA

Hi Guys,

I am currently testing the Fail-Over Cluster with Windows Server 2016, and it works wonderful for me based on my current requirements. Now, how many file server roles can I have to a single cluster as I am planning to have 15 file server roles to host my 15 file shares? Is it a good idea to have this as a long term approach?

Thanks,

Paul

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.

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,

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 ?

Hello. 

I am trying to add a hyper V cluster to Virtual Machine Manager Console. However it says that it cannot connect to the cluster with error 25300/ ID 13805.

But I have other Hyper V clusters that are successfully added. 

Network/Ip address wise, the successfully added hyper V cluster and the failed cluster are both not in the same segment as the Virtual Machine Manager console. 

Both successful and failed hyper V clusters are able to telnet 5985 to and fro to SCVMM. 

Not sure if this is a scvmm issue or cluster issue, I wish to find out what settings that I might have missed in comparison to the two Hyper V clusters settings.

I have posted the same question on the scvmm thread. 

Hi,

We just lost 5 node hyper-v cluster with 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

I have a 2-node server 2012R2 Hyper-V cluster with 3 CSV's the problem is the free space that does not display the correct disk remaining. Last 2 week ago the free space is decreasing(now down from 2 TB to 80 GB). I try to deleted VM from that CSV, but free space not increasing. the free space that does display the correct disk remaining when I move CSV owner to other cluster node.

Now the free space is decreasing(now down from 2 TB to 140 GB) again. The actual disk remaining should be around 210GB. 

Could you please advise me how to resolve this issue?.

Thank you

Arkom   

Hi,

I am trying to create a failover cluster without AD. The 2 Winserver 2016 machines are in Azure cloud.

They are on same subnet but workgroup machines. able to ping each other using the private IP.

In order to create a domain independent failover cluster in Azure, i followed the instructions here

http://woshub.com/workgroup-failover-cluster-windows-server-2016/

https://techcommunity.microsoft.com/t5/Premier-Field-Engineering/Domain-Independent-Cluster-and-Availability-Group/ba-p/371462

Since i do not have a DNS server, i am using FQDN of the workgroup machines.

I added the Failover cluster role , when i open "Failover cluster managaer" and click create a new cluster, i am unable to find the 2nd machine to add to cluster.

Basically, i have 1 machine with FCI role installed, but unable to add the 2nd machine.

In command prompt i cannot ping both of them using fqdn, but ping through ip address works fine.I feel i missed out on some settings in IP address or DNS address.

Can someone guide me on the prerequisites or step by step instruction to create a domain independent failover cluster?
After this is complete, i need to add SQL server always on availability group on top of this...