Windows Server 2008 failover cluster in VirtualBox

Hi,
I'm a Windows NT student and I need help with understanding how to do clustering using multiple Windows 2008 R2 Enterprise servers in VirtualBox 4.3.8. I have a Windows 7 host computer. I was wondering if someone could provide clearly detailed step-by-step
directions (ex. Click this, then click that) on what I need to do prior to clustering, as well as starting the clustering process. Please ask if you need additional information.
Thank You.

I'm sorry. I'm such a noob. Should I have 3 virtual machines, where one is the domain controller and the other 2 are nodes? Or is it ok to just have 2 virtual machines?
It's optional. You just need your both cluster nodes (VMs) belong to the same domain. It can be own domain serviced by your private VM or it can be "external" one. See:
Using Guest Clustering for High Availability
http://technet.microsoft.com/en-us/library/dn440540.aspx
Active Directory domain requirements
Failover clusters require that nodes of the same cluster are members of the same Active Directory domain. However, there is no requirement that a guest cluster belongs to the same Active Directory
domain as the physical hosts on which the virtual machines are running.
Also you'll need some shared storage. See (same URL as above):
Storage options
The following tables lists the storage types that you can use to provide shared storage for a guest cluster.
Storage Type
Description
Shared virtual hard disk
New in Windows Server 2012 R2, you can configure multiple virtual machines to connect to and use a single virtual hard disk (.vhdx) file. Each virtual machine can access the virtual hard disk
just like servers would connect to the same LUN in a storage area network (SAN). For more information, see Deploy a Guest Cluster Using a Shared Virtual
Hard Disk.
Virtual Fibre Channel
Introduced in Windows Server 2012, virtual Fibre Channel enables you to connect virtual machines to LUNs on a Fibre Channel SAN. For more information, see Hyper-V
Virtual Fibre Channel Overview.
iSCSI
The iSCSI initiator inside a virtual machine enables you to connect over the network to an iSCSI target. For more information, see iSCSI
Target Block Storage Overview and the blog post Introduction of iSCSI Target
in Windows Server 2012.
Shared VHDX is out as you don't have proper software (Windows 7 is not supported as a host and Windows 2008 R2 does not support shared VHDX as a guest), virtual Fibre Channel is out as you again don't have Windows Server 2012 R2 (and don't have any FC gear).
So iSCSI is your only choice. Either spawn dedicated Windows (or other OS if you like UNIX) VM with iSCSI stack or use third-party Windows software running on your host. Windows Server 2008 R2 does not have iSCSI target embedded so you can get it here:
MSFT iSCSI Target 3.3 Download
http://www.microsoft.com/en-us/download/details.aspx?id=19867
Good luck and happy clustering :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Similar Messages

MSDTC set up in SQL Server 2008 failover cluster

Hi Guys,
I am in the process of setting up failover cluster using SQL Server 2008 (64Bit) Enterprise on Windows Server 2008 R2 (64Bit) I have completed almost all the works but I got few questions regarding MSDTC configuration whether the MSDTC disk should
be assigned from SAN or it should be local to the disk , Separate disk for each nodes in the cluter or 1 disk to be used across all the servers for MSDTC in windows fail over cluster.
With regards, Gopinath.

Hi Gopinath,
Please review the following similar blogs to get more details about configuring MDTC and pros & cons of different options.
How to Configure Multiple Instances of Distributed Transaction Coordinator (DTC) on a Windows Server Failover Cluster 2008
http://blogs.technet.com/b/askcore/archive/2009/02/18/how-to-configure-multiple-instances-of-distributed-transaction-coordinator-dtc-on-a-windows-server-failover-cluster-2008.aspx
How to configure DTC for SQL Server in a Windows 2008 cluster
http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Windows Server 2012r2 Failover Cluster Event Trace Log files

Hi
The only documentation I can find regarding event trace log files (Diagnostic.etl.*) for Failover Clustering relate to Server 2008/2008r2, which state that the etl files should be in C:\Windows\System32\winevt\Logs.
I have been exploring a clustering lab for Server 2012r2 and cannot find these files in that folder.
Strangely the PS cmdlet Get-ClusterLog still works!
Where are the etl files?
TIA

Hi,
Please check if the log is available in C:\ProgramData\Microsoft\Windows\WER\ReportQueue\.
If not, you can use Get-ClusterLog with the Destination parameter to get the log file.
Destination
Specifies the location to copy the cluster log(s) to. To copy to the current folder use "-Destination ." for this parameter.
http://technet.microsoft.com/en-us/library/ee461045.aspx
Thanks.
Jeremy Wu
TechNet Community Support

Windows server 2012 failover cluster error: Cluster resource 'Virtual Machine Configuration ... of type 'Virtual machine configuration in clustered role ... failed.

I have two windows 2012 host server that are clustered using windows failover cluster feature. Each server is hosting four VMs. When migrating from Host2 to Host1, the migration failed with the following error:
Cluster resource 'Virtual Machine Configuration SCPCSQLSRV01' of type 'Virtual Machine Configuration' in clustered role 'SCPCSQLSRV01' failed. The error code was '0x569' ('Logon failure: the user has not been granted the requested logon type at this computer.').
When this happens, the VM that I was migrating can no longer be started even on the original host. The only remedy is to restart the host server.
Any suggestion on resolving this problem?
Thanks
Ikad

Thanks. The article referred to above gives the solution to my issue. There is a group policy that is applied to the OU where the host servers were placed. Doing gpupdate /force temporarily removes the problem. Unfortunately the NT Virtual Machine\Virtual
Machines account is a special account that cannot be added like other accounts and granted the log on as a service right. The thread
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/d56f2eae-726e-409a-8813-670a406593e8 contains how it can be added which is by creating a group and running the command
Net localgroup VMTest “NT Virtual Machine\Virtual Machines” /add
to add it to a local group VMTest. VMTest is then assigned the right to log on as a service.
Ikad

Windows Server 2012 Failover Cluster (Hyper-V) Event Id 1196

Hi All,
I just installed Failover Cluster for Hyper-V on windows server 2012 with 2 nodes. I got following error event id 1196.
reCreated / deleted Cluster Host A record on DNS and nothing happened.
Any suggestion?
There is similar topic but it couldnt help
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/2ad0afaf-8d86-4f16-b748-49bf9ac447a3/
Regards

Hi,
You may refer to this article to troubleshoot this issue;
Event ID 1196 — Network Name Resource Availability
http://technet.microsoft.com/en-us/library/dd354022(v=WS.10).aspx
Check the following:
Check that on the DNS server, the record for the Network Name resource still exists. If the record was accidentally deleted, or was scavenged by the DNS server, create it again, or arrange to have a network administrator create it.
Ensure that a valid, accessible DNS server has been specified for the indicated network adapter or adapters in the cluster.
Check the system event log for Netlogon or DNS events that occurred near the time of the failover cluster event. Troubleshooting these events might solve the problem that prevented the clustered Network Name resource from registering the DNS name.
For more information please refer to following MS articles:
DNS Registration with the Network Name Resource
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
Lawrence
TechNet Community Support

Windows Server 2012R2 Failover Cluster error with mounted volumes

Hi all,
I've a problem with mounted volume on a WSFC build on top of Windows Server 2012R2, the situation is:
M: is the volume hosting mounting points
disk-1, disk-2, disk-3 are volume mounted on M:\SomeFolder
Theese volumes are used by a SQL Server Failover Cluster Instance, but my problem is related to WSFC. I've set dependencies so disk-1, disk-2, disk-3 depend upon H:
If I try a failover of the role "SQL Server" I observe that when the disk come online in the other node they fail with this error:
Cluster resource 'disk-1' of type 'Physical Disk' in clustered role 'SQL Server (ISQL2014A)' failed. The error code was '0xaa' ('The requested resource is in use.').
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.
If I manually take offline H: and than bring it online and then manually take online all disk (1 to 3) they come online with no error.
I'm going crazy!

I've found the root of the problem: the servers are virtual machine on a VMware ESX 5.5 infrastructure, VMware claims that on 5.5 multipath is supported for raw device mapping disks but disabling multipath (I've set to fixed path) the Windows Server Failover
Cluster stops to get problems.
Now we have opened a support call with VMware.

Windows Server 2008 R2 SP1 2-Node cluster - Replace failed node

Hi - I have a two node Windows Server 2008 R2 SP1 fail-over cluster (DHCP, File, Print) where one of the nodes have failed beyond recovery. What I would like to do is to evict the failed cluster node and install a new machine with Windows Server 2008
R2 SP1 and re use the same name and Ip adress and then join this machine as a node in the cluster.
Is there any recommended steps to do this, i'm mostly thinking about the part of re-using the same name and ip address for the new node? (e.g. is there any cleanup more than evict the node?)
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Hi,
I agree with Noah Sparks, you can evict the corrupt node, if you reinstall then add the new server system you can just join it to cluster, it shouldn’t any error.
If you have seen some the evicted node rejoin to cluster meet “The cluster node is already a member of the cluster” error, it may need pack the KB2549472
hotfix.
The related KB:
How to Evict a Node from a Windows Server 2008 Failover Cluster
http://technet.microsoft.com/en-us/library/bb676524(v=exchg.80).aspx
Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2
http://support.microsoft.com/kb/2549472
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to add a cloud machine as a node to existing windows fail over cluster having on-premise node in Windows server 2008 R2

Hi All,
We have a windows fail over cluster having one windows machine on local network as one of its node.
I want to add a virtual cloud machine available on microsoft azure as another node to this existing cluster.
Please suggest how to do this?
Thanking all in advance,
Raghvendra

Before you even start working on the SQL side, you will need to create a Windows Server 2008 R2 cluster with no shared storage. You can actually test that in-house. Create a VM running 2008 R2 and cluster it with your physical (from your description,
I am assuming physical) 2008 R2 machine. Create it with a file share witness for quorum. Then configure your environment to see that it works as expected.
Once you know how to configure the cluster between physical and VM with a file share witness, build it to Azure. The location of the FSW gets to be an interesting choice. To have a FSW in Azure means that you will need another VM in Azure to
host the file share, meaning you have two quorum votes in Azure and one in-house. Or, you could create a file share witness on an in-house system, giving you two quorum votes in-house and one in Azure.
In the FSW in Azure scenario, if you have a loss of the in-house server, automatic failover occurs because two quorum votes exist in Azure. With FSW in-house, depending on the loss you have in-house, you might have to force quorum to get the Azure
single-node cluster to run. Loss of access to Azure reverses those scenarios. Neither one is optimal, but it does provide some level of recoverability.
. : | : . : | : . tim

The cluster resource could not be found-SAP ECC on Windows Server 2008 MSCS

Hi,
I'm installing SAP ECC 6.0 on Windows server 2008 MSCS Cluster. As mentioned in the guide, i've created a service and added a resource.
I was able to successfully configure the DB installation and cluster configuration. But when I start the ASCS installation, the installation fails when it tries to create system folders with the following error.
Error when sharing file system export (share) saploc : The cluster resource could not be found
I'm using a user with domain admin access and also a member of the local administrators group. I've even tried to install using the domain administrator user but still the problem exists.
Can anyone please let me know where am I going wrong ?
NB: The host on which I'm installing is not a domain controller but it is a member of a domain.
Regards,
Varadharajan M

Yes Krishna,
I've not created any shared folders manually and I've used the "Use domain of current user" option.
Actually SAPINST has created the usr and sap folder in the SAP drive (say E: drive) which is a clustered disk. The name of that clustered sidk is "Clustered Disk 1". I could able to open up the shared directories available in that SAP virtual host by issuing
<SAPGRP>. I don't know where am I going wrong:( I've also opened a call with a SAP and waiting for their reply.
Regards,
Varadharajan M

Maximum Nodes supported for NLB and Cluster in Windows Server 2008 Standard Edition ?

Hi.
I am looking for information How many nodes supported for NLB and Cluster in Windows Server 2008 Standard Edition ?
If you can provide for all the versions that would be great.
-Thanks
- Ajay Chanana

Hi,
You can configure a Windows server 2008 NLB cluster with up to 32 nodes. However,
scaling beyond 8 nodes will cause a slight performance hit because the network traffic is broadcasted to every node and only one NLB node accepts the connection.
For more detailed information, please refer to the link below:
FAQ Week for NLB: Tuesday
Best regards,
Susie

Active-Passive Failover cluster in Windows Server 2008 R2

Hi,
As per the client requirements, I build an active-passive Oracle 11g R2 database cluster in Windows Server 2008 R2.
(Used Microsoft cluster as Client don't have Fail Safe licence)
As per the configuration, I follow the below mentioned steps:
a)OS vendor configured Active-Passive Windows Cluster
b)Installed Oracle 11g R2 on both the nodes with same ORACLE_HOME name
c)Create Listener and configured it with cluster IP in Node1
d)Create Database from Node1. Physical files location are all in Storage
e)Create Oracle Service with the same name in the 2nd node and copy all the files like spfile,tnsnames.ora,listener.ora,password file to Node2
f)Configure Listener with the same Oracle SID.
g)Test database failover from Node2 with Listener registration
h)Open the Windows Failover Manager to configure the Oracle Database and Listener Service in the Cluster Group
Now I am facing problem by moving Cluster Group movement. Whenever trying to moving the group, Listerner service is not getting up by Cluster Manager as quorum is not included in the group and that quorum disk is not moving in the failover node with the Oracle Cluster Group. As per my understanding Quorum having information of Cluster IP which has been configured with Listener.
But when I am shutdown one node, then in the other node all the resources successfully moving and cluster able to online all the resources. I guess at that time Quorum is also moving and thus cluster can able to make Listener online.
Please suggest how to resolve this issue. Means how can I make Listener up instead having any dependencies with Quorum in the fail over node?
Thanks a lot for your help.

hello
I was going through your post and i am also doing the same thing here at our organisation for Oracle 10g R2
Can you pls send me any docs u r having for configuration of Oracle in windows clusters .
And, can you pls elaborate on this point
e)Create Oracle Service with the same name in the 2nd node and copy all the files like spfile,tnsnames.ora,listener.ora,password file to Node2.
Pls send me the details at [email protected] or you can contact me at 08054641476.
Thanks in advance.

Failover of ASCS takes very long on a Windows Server 2008 Cluster

Hello everybody,
I have configured a ABAP SCS (NetWeaver 7.0) running on a Windows Server 2008 Cluster. The database runs on SQL Server 2008 which is also configured for use in the MSCS. The ASCS and the database run fine in the Cluster. So far so good.
When I want to move the SAP Group which contains the ASCS from on node the other node, then the failover will take very long (approximately 2-3 minutes). The Service of the group will go offline in a few seconds, but the Instance needs about 1 minute to go offline and on the other node it needs more then one minute to become online.
The failover of the databaseinstance will take only about 10 seconds.
Have you got any ideas why the failover of the SAP Group will take so long?
Thanks for your help in advance!
Kind Regards,
Wolfgang

One minute would be somewhat long if you are running a faster server and just the ABAP environment. But I've seen ABAP/JAVA systems take up to 10 minutes to restart on a win 2005 clustered system.
Have you looked through the developer traces?
J. Haynes

"Failed to connect to the service manager" when I try to add nodes to a cluster on Windows Server 2008 R2

Hello,
I get the following error message everytime I try to add a node to an existing cluster "Failed to connect to the service manager".
I'm running Windows Server 2008 R2,
Any ideas?

Hi saeedawadx,
Please run the cluster validation and post the error or warning information, in normal scenario the “Failed to connect to the service manager” issue often caused by the firewall
or AV soft block the others node connect, please try to disable the firewall and AV soft then try again.
The following related article will give more helpful tips,
The case of the server who couldn’t join a cluster – operation returned because the timeout period expired
http://blogs.technet.com/b/roplatforms/archive/2010/04/28/the-case-of-the-server-who-couldn-t-join-a-cluster-operation-returned-because-the-timeout-period-expired.aspx
Trouble Connecting to Cluster Nodes? Check WMI!
http://blogs.msdn.com/b/clustering/archive/2010/11/23/10095621.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Oracle 10g R2 whitout RAC in a cluster hw (Windows Server 2008 cluster)

Hi,
Is this possible?
I ask it 'cause my customer wants to improve this solution.
I know that Oracle 10gR2 vs Windows Server 2008 is not supported and Oracle Standalone vs Hardware Cluster, neither too, but it's possible or will be a source of big problems?
Thanks in advance.
JRC.

Hi lain;
Please check Re: oracle10g on linux cluster
In my issue we were working on linux cluster. Our aim is
we have 3 server and they are linux cluster OS level. Let us call those server A,B and C... We want to make oracle10g works on server A and when server A is gone oracle10g on B server take place of A, if server B gone too, oracle10g on C server take place of B.... In each server we had different numver of database. I mean on machine a we have 3 database, on server B we have 4 database and on server C we have 7
What i do for this:
1. I install 10g database software only (not created database)
2. using netca and create listener for each database
3. using dbca and create database for each server.While on dbca wizard i gave SAN path for dbf
4. Linux admin arrange all other stuff(I mean when db1 on server A crash server B take responsibility of Server A and db1 keep working)
I hope it helps you
Regard
Helios

Adding nodes to Windows Server 2008 R2 Hyper-V Cluster..

Currently we have a 3 node Windows Server 2008 R2 Hyper-V Cluster in production. There are about 3 terrabytes worth of VMs running across these nodes.
It is over-committed, so i've setup two new nodes to add to the cluster.
I've done this before in a SQL cluster but never a Hyper-V cluster.
If I don't run validation when adding the nodes, will there be downtime?
The quorum is setup for disk majority, everything is identical on all nodes that needs to be. Shared storage is recognized and ready on the new nodes. I've gone through every checklist that Microsoft has. I'm just curious if the virtual machines will go
offline on the current nodes when i add the two new nodes.
Everything is identical down to the wsus updates installed. From networking to storage everything is perfect.
I don't want to run validation as I know that'll take everything offline.

Hi,
It is recommend to run a validation test. You can select custom test. (skip storage).
When add the new node to existing cluster . it will not bring down existing VM.
Lai (My blog:- http://www.ms4u.info)

Windows Server 2008 failover cluster in VirtualBox

Similar Messages

Maybe you are looking for