I'm rather new to clustering and DAS and SAN storage devices so I am trying something rather simple to get me going, this is  the scenario

2 x Dell Servers of different spec both installed with Windows Server 2012 Standard Edition.

I have added the hyper-v role on both the servers.

1 x Dell MD3200 (DAS using SAS cables and SAS Controller Cards) I have created1 Virtual Disk of 2TB

Please note I am not using iScsi

My Intention is to do the following

Host Server 1

4 x Virtual Guests the Virtual Machine info and VHD's to be stored on the single Virtual Disk i created on the MD3200

Host Server 2

4 x Virtual Guests the Virtual Machine info and VHD's to be stored on the single Virtual Disk i created on the MD3200.

So basically both Host Server's can see and write information to the Single LUN Virtual Disk I created, and in the event that one of the hosts fails then the virtual guests merely cutover to the other host server, and the memory and processor power adjusts accordingly to handle the 8 machines it is now looking after.

Is this possible with out of the box features in Server 2012 Std? Will I have issues around data corruption due to different file systems? If possible then what is the process.

Do I connect Host Server 1 to the (DAS) Virtual Disk, create my VM's setup clustering on Host Server 1, then connect Host Server 2 to the DAS add it to the cluster and then create the VM's? Or do I connect both machines to the DAS setup the cluster and then start writing data (creating the vms) on the Host Servers.

Lastly could I use the same process for file servers? Which in essence is 2 x servers connected to the DAS, but I'm sure if I understand the above I will be able to answer this one myself. :-)

Thanking the technet world in advance.

Ahmed

This is my first cluster I have put together and I could use some advice on storage.  Currently the plan is to setup a 2 node cluster VM's that I will eventually make 4 nodes once tested.  The cluster will serve as an active - active cluster for several SQL instances.  The initial plan is to clear out some space on the LUN and connect to the SAN via a dedicated iSCSI connection.  Any suggestions would be greatly appreciated.

Thanks

http://kinomakino.blogspot.com

Hello,

We have 2-node Windows 2008 R2 Enterprise Edition failover cluster with Fibre shared storage (SAN) running SQL Server 2012 SP1. Below is current configuration - very simple and classic, I would say everything by the book:

This is what I think we want to achieve:

Objectives:

1. Upgrade Windows Operating System from Windows Server 2008 R2 to Windows Server 2012

2. Migrate to SQL Server 2012 Always On Availability Group (AAG) for High Availability and Disaster Recovery

My question is how to achieve both goals?

If possible I would like to upgrade OS first. Ideally I would like to upgrade on the same hardware (because it should be minimal impact - no need to migrate data). If this is not possible, we have new hardware I can use also. But I guess it will be more impact and actual data migration will be required.

For AAG what I'm honestly missing is what would be the name of the second SQL server? Lets say my servers called DB1 and DB2, and SQL server called DB. If I create AAG, and fail-over to replica server, would SQL server name be DB as well?

I know there is lots of documentation on AAG and I went through it but I cannot find any specific information about names.

Another question I have - would 3rd server (DB3) be part of the same MSCS cluster? Or it will be separate server? How fail-over exactly works - do I use Fail-over cluster Manager to initiate failover?

Sorry for lots of questions, but any information would be appreciated very much.

Thanks!

Hi Everyone,

We are trying to install SAP ECC 6.0 on Windows 2012 Failover Cluster. Request to share any document on Windows 2012 Failover Cluster that would be helpful in carrying out this activity

Thanks and Regards

Madhav

dear all,

i installed a hyper-v v3 cluster with 2 x W2k12 clusternodes. Attached a V3700 via ISCSI with 24x 1 TB SAS disks.

on the storage i have made 1 big 10rpm diskpot with 17 Terrabyte for 1 CSV. The cluster is hosting 12 vm´s @ the moment on this CSV.

now our customer wants to use the role "File Server" on the Cluster. My question now:

is it possible to use the (one and only 17 Terrabyte) existing CSV, where the vm´s also running on it. or may i have to do this on an several new CSV, wich i cant cause there is no space left on the storage to create a new LUN -> CSV.

if you need further informations so please let me know, or if something not so clear.

Thanks Markus

This is a fairly new deployment.  When I first started having this issue, I foundhttp://support.microsoft.com/kb/2779204, which suggests that gpupdate /force will temporarily resolve the issue.  That worked for me for several weeks, but no longer.  It was always temporary and I had to do it at least once a day, but even that doesn’t work anymore and my Hyper-V guests are stuck.  I also suspect if I have a Hyper-V host failure, the guests on the failed system will not come back up on the operational host.

kb2779204 suggest adding NT Virtual Machine\Virtual Machines in the entries for Log on as a Service.  I have created a dedicated OU for the virtual hosts (as suggested by the kb article) and moved them to the new OU. I then addedNT Virtual Machine\Virtual Machines in the entries for Log on as a Service, then gpupdate /force and then wait minutes, then hours. It still doesn’t work.  I get 2 slightly different depending on which server I initiate the live migration.

If from the server that currently is running the guest (HV1):

Live migration of 'Virtual Machine vg1' failed.

Virtual machine migration operation for 'dc4' failed at migration source 'HV1'. (Virtual machine ID 140C8893-44EC-481B-B8D5-52FCB8D422DC)

The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'HV2': General access denied error (0x80070005).

The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration because the destination host rejected the request: General access denied error (0x80070005).

If from the server attempting to move the guest to (HV2):

Live migration of 'Virtual Machine vg1' failed.

Virtual machine migration operation for 'vg1' failed at migration destination 'HV1'. (Virtual machine ID 140C8893-44EC-481B-B8D5-52FCB8D422DC)

'vg1' Failed to create Planned Virtual Machine at migration destination: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569). (Virtual machine ID 140C8893-44EC-481B-B8D5-52FCB8D422DC)

I have 16 VM's. Some with Windows server '03, Windows server '08, and Windows server '12 on them. I added them to the nodes in Failover Cluster Manager. Is Failover Cluster Manager designed for WIndows Server '03 and Win Serv '08. Google says its not configured to run with Win 08

Hello,

I have a two node windows 2012 cluster on which I have configured SQL Server 2012 High Availability Groups.

These two SQL server nodes are in different data centers.

These are used by ASP.NET application which is also running in 2 node NLB Cluster with each node being in a data center.

The following diagram depicts my setup

Now I when configuring the cluster, I am configuring it with "Node and File Share Majority"

I do not use any SAN at all. no Shared Storage.

I don't have any other data center. So no 3rd data center. Only 2 data centers.

Currently I have created a fileshare on web server 1 and configured the cluster. The problem is that if I loose the data center 1. then my cluster will go down. desptite the fact that my Web Server 2 and SQL Server (Mirror) are alive.

My intention is that even when an entire data center is down. my application contiues to work because I have all the components of my application (web server and database server) in the second data center.

Currently the file share is a single point of failure and since I don't have shared storage across data centers if the machine on which the file share resides goes down, then the cluster goes down... even though it has healthy machines in other data centers.

How do I resolve this? Can I provide 2 file shares? one on web server 1 and second on web server 2 as witness?

val it: unit=()

Hi,

I have setup up a two node Windows 2008 R2 cluster (Say, 'Node 1' and 'Node 2') . The AD/DomainCntroller machine (Say , 'AD 1') used for this setup was suddenly crashed. To bring up the 'AD 1' machine we had to uninstall the Active Directory/Domaincontroller application from this server.

Then we reinstalled AD application in 'AD 1' and recreated the OLD domain again. We have joined the 'Node 1 and 'Node 2' to the Domain again and now we are able to see nodes listed in 'Active Directory User and Computers'.

When starting the Cluster Service in Node 1 and Node 2, it started successfully. However in the 'Failover Cluster Manager' window, the 'ClutserNameService' is Offline and it failing with the following error with Event ID 1207.

"Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'xxxxxxx.com' for the following reason:
Unable to get Computer Object using GUID." 

ANALYSIS  DONE : Since the AD was recreated, the 'CNO' object doesn't exist in the AD. I believe this is the reason for the 1207 Event. 

Like per-staging of 'CNO', I have created a computer object manually in the AD. Then took the GUID of this object and updated the GUID in Node 1 and Node 2 registry using the Regeidt --> HKEY_LOCAL_MACHINE--> Cluster--> Resources -->ClusterResourceName--> Parameter --> ObjectGUID .

Still I am facing the problem.

Please help to over come this situation.

Best Regards,

Krishna.

Dear Experts,

Recently we have built a Windows Server 2008 R2 two node failover cluster on top of VMware virtual machines by using raw device mapping (quorum disk and shared disk).

Cluster has been created successfully without any issues (Cluster validation check was successful).

Now we are in the process of testing cluster disk failover between nodes.

Manual failover is happening without any trouble if both the nodes are online.

Automatic failover of cluster disk also happening if we are restarting the active cluster node.

But the problem is that after restarting active node (now this is passive node and cluster service also running), if we are trying to manually fallback the cluster disk resources, it is getting failed.

At this point, if we are looking on the failover cluster service manager console we can see a red cross on top of that node even though the cluster service is started on that node. After 7 Min the node will come in normal mode and then it behave as normal.

Any idea why this red color (node shows as offline) is coming after restart?

Any patch is required for resolving this issue?

Thanks,
Santhosh

Santhosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA

We are having troubles trying to add a node to a cluster where there is an AlwaysOn Availability Group role, all systems are using Windows Server 2012. This node was previously working without problems, but was evicted during an operation, and we are trying again to add this node to the claster.

The cluster is working OK, because we have other avaibility groups working in the same cluster. Both cluster and node are in the same network and domain.

The cluster validation was completed without  errors. This is the report generated after the unsuccessfull adding process:

Any hint about how to resolve this problem would be very appreciated.

Hi all, I am having an issue hopefully someone can help me with. I have recently inherited a 2 node cluster, both nodes are one half of an ASUS RS702D-E6/PS8 so both nodes should be near identical. They are both running Hyper-V Server 2008 R2 hosting some 14 VM's.

Each node is hooked up via cat5e to a PromiseVessRAID 1830i via iSCSI using one of the servers onboard NICs each, whose cluster network is setup as Disabled for cluster use (the way I think it is supposed to be not the way I had originally inherited it) on it's own Class A Subnet and on it's own private physical switch...

The SAN hosts a 30GB CSV Witness Disk and 2 2TB CSV Volumes, one for each node labeled Volume1 and Volume2. Some VHD's on each.

The Cluster Clients connect to the rest of the company via the Virtual ExternalNIC adapters created in Hyper-V manager but physically are off of Intel ET Dual Gigabit adapters wired into our main core switch which is set up with class c subnets.

I also have a crossover cable wired up running to the other ports on the Intel ET Dual Port NICs using yet a third Class B Subnet and is configured in the Failover Cluster Manger as internal so there are 3 ipv4 Cluster networks total.

Even though the cluster passes the validation tests with flying colors I am not convinced all is well. With Hyperv1 or node 1, I can move the CSV's and machines over to hyperv2 or node 2, stop the cluster service on 1 and perform maintenance such as a reboot or install patches if needed. When it reboots or I restart the cluster service to bring it back online, it is well behaved leaving hyperv2 the owner of all 3 CSV's Witness, Volume 1 and 2. I can then pass them back or split them up any which way and at no point is cluster service interrupted or noticed by users, duh I know this is how it is SUPPOSED to work but...

if I try the same thing with Node 2, that is move the witness and volumes to node 1 as owner and migrate all VM's over, stop cluster service on node 2, do whatever I have to do and reboot, as soon as node 2 tries to go back online, it tries to snatch volume 2 back, but it never succeeds and then the following error is logged in cluster event log:

Hyperv1

Event ID: 5120

Source: Microsoft-Windows-FailoverClustering

Task Category: Cluster Shared Volume

The listed message is:Cluster Shared Volume 'Volume2' ('HyperV1 Disk') is no longer available on this node because of 'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until a path to the volume is reestablished.

Followed 4 seconds later by:

Hyperv1

event ID: 1069

Source: Microsoft-Windows-FailoverClustering

Task Catagory: Resource Control Manager

Message: Cluster Resource 'Hyperv1 Disk in clustered service or application '75d88aa3-8ecf-47c7-98e7-6099e56a097d' failed.

- AND -

2 of the following:

Hyperv1

event ID: 1038

Source: Microsoft-Windows-FailoverClustering

Task Catagory: Physical Disk Resource

Message: Ownership of cluster disk 'HyperV1 Disk' has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.

Followed 1 second later by another 1069 and then various machines are failing messages.

If you browse to\\hyperv-1\c$\clusterstorage\ or\\hyperv-2\c$\Clusterstorage\, Volume 2 is indeed missing!!

This has caused me to panic a few times as the first time I saw this I thought everything was lost but I can get it back by stopping the service on node 1 or shutting it down, restarting node 2 or the service on node 2 and waiting forever for the disk to list as failed and then shortly thereafter it comes back online. I can then boot node 1 back up and let it start servicing the cluster again. It doesn’t pull the same craziness node 2 does when it comes online; it leaves all ownership with 2 unless I tell I to move.

I am very new to clusters and all I know at this point is this is pretty cool stuff but basically if it is running don’t mess with it is the attitude I have taken with it but there is a significant amount of money tied up in this hardware and we should be able to leverage this as needed, not wonder if it is going to act up again. 

To me it seems for a ‘failover’ cluster it should be way more robust than this...

I can go into way more detail if needed but I didn’t see any other posts on this specific issue no matter what forum I scoured. I’m obviously looking for advice on how to get this resolved as well as advice on whether or not I wired the cluster networks correctly. I am also not sure about what protocols are bound to what nics anymore and what the binding order should be, could this be what is causing my issue?

I have NVSPBIND and NVSPSCRUB on both boxes if needed.

Thanks!

-LW

Hi,

One of our client has Exchange server 2010 with Hyper-v and they are running two site DC and DR. Witness server are located in DC site with other physical server, this server is also running file server service. When they down DC's Exchange server then Exchange server are running fine from DR site. But when they down witness server after 1 to 2 hour's later then DR Exchange Database is dismounted state and Exchange server is not working. Their High availability of exchange server with DAG for mailbox. Why this problem occur.

Hi,

I'm running an Exchange 2010 SP1 DAG on Windows 2008 R2 SP1.  We are using an INFOBLOX appliance for DNS resolution.

DNS resolution is working and SRV records are created.

On one of the two clusternodes I get warning 1579 and error 1196 every 15 minutes.  After looking around on the internet and technet, I found kb 977158 stating the problem and resolution.  However this hotfix is not applicabel on Windows 2008 R2 SP1 .

How can I resolve these annoying events?

Event 1196 failoverClustering:

Hi Everyone,

I have a 2 node file cluster on windows server 2008 R2 SP1, was well working before. However since few days its giving me trouble. 

Node1=FS01

Node2=FS02

when ever there is a failover from FS01 to FS02 the E Drive (shared SAN drive) doesn't appear on the server however the Quorum is available, the disk management does not allow me to bring the E Drive online as the option is degraded also there is an error "disk offline due to policy set by administrator" something like that. When the cluster is moved back to FS01 the E Drive works fine.

Regards

Abdul Majeed.