Microsoft geographically dispersed cluster.

Hi all,
I need help with Microsoft cluster.
How I could do geographical cluster throught Internet. I mean network configuration because both sites must be on the same IP network. I know that I can do this with VLANs or VPN tunels?
Could someone help me?
BR.
jl

I do not think you are on the appropriate forum for this. You should try the routing/switching or security forum.
Gilles.

Similar Messages

Oracle 11GR2 on windows 2008 Geo-Dispersed cluster

Hi all,
anyone can guide me about the installing oracle 11GR2 on windows 2008 Geo-dispersed cluster environment? Please guide and provide documentation if possible,
thanks

By "geo-dispersed", do you mean a cluster with servers is physically remote locations ? If so, the install process does not care about how far apart the servers are physically. Follow the standard install doc at http://download.oracle.com/docs/cd/E11882_01/install.112/e16773/toc.htm
Srini

Layer 2 over geographically disperse networks.

The situation that I am in is this:
I need to setup a DR site with a type of "flip the switch solution". I have the solution drawn up but what I need to figure out is if I can run the same subnet at the COLO or not. I realize this may be a really stupid question but just wanted to see if there is anyone with some insight into this. The WAN that this will be going across is running BGP with VRF-lite. I know this is not a lot of detail and can provide more if needed just want to see what kind of options I may have.
Thanks

Hello, for DR, in an "Active / Standby" solution you could extend layer 2 between sites, but all depends on which type of devices you have, which technology you could get comfortable with. I could suggest L2TPv3, (example here: http://www.networkworld.com/article/2343443/cisco-subnet/configuring-an-l2tpv3-ethernet-pseudowire.html) which is quite quick and easy to deploy. Just be mindful, of the default gateways of servers and hosts, where they would be, they'd have to be active in one place or the other depending on where hosts are based, you don't want them unnecessarily traversing a link to get to the default gateway. If switching on (albeit via shut/no shut/hsrp priority etc...) the SVI's or gateways in the DR site is part of the "flip the switch" it seems to work in my mind.

Cloning a Microsoft Cluster

Hi Experts
We are planning our Disaster Recovery Plan, we have some SAP applications which are difficult of install and configure,
so we are thinking that our best option is cloning the entire server to the secondary site, we have a tool named double take which can replicate from server to server.
next is the schemma:
we have a Cluster in Windows server 2008 R2 with two nodes,
it has installed SQL SERVER 2008 R2 on cluster and SAP.
we want to clon this cluster to the secondary site and start a replication with the mentioned tool,
we want to maintain the actual name of servers but we will change the IP of servers,
my principal questionis if we can clon the cluster and if exist a document or something where we could follow best practices..
thanks ind advance

No - you cannot create a clone. At least, not if you want it to be supported. There are all sorts of security ids generated in each instance of Windows Server and thing don't work well with the same SIDs on more than one system. Microsoft
does not support cloned systems.
However, it is possible to build a geographically dispersed cluster where some nodes are in the data center and the other nodes are in the DR site. This is dependent upon capabilities provided by the storage vendor, so you need to talk with your storage
vendor about how to configure it.
. : | : . : | : . tim

Oracle On Microsoft Cluster

Hi all,
I am in a testing enviornment.I had Microsoft 2 node cluster set up where the failover is happing.
I installed database software on 2 nodes and from one node i configured database where my datafiles are in storage.
I copied tnsnames,listener.ora from primary node to the second node.
On primary node my database is running fine,but when the failover happens and wheni log to my database its showing TNS error.
Please help..
Regards
Bobs

Hi Bobs;
What is DB version? What is OS version?
Please see below which could be helpful for your issue:How to Set Up a Two Node Cluster for Content Server on Microsoft Windows [ID 758916.1]
Microsoft Cluster Server and Oracle Fail Safe Quick Start Guide [ID 187410.1]
RAC on Windows 2008: Oracle Grid Infrastructure / Clusterware Currently Incompatible with Microsoft Failover Cluster (MSFC) [ID 1157711.1]
Database Administration in an Oracle Fail Safe/Microsoft Cluster Server Environment [ID 221202.1]
Regard
Helios

Convert from Cluster to Standalone

Hello.
I'm seeking some advice on an issue I need to overcome.
I have a SQL2012 Cluster running on Windows Server 2012 on XenServer. All cluster related storage is provided via iSCSI. The device that is providing the storage is failing and I need migrate the data off of that device with as little downtime as possible.
I also would like to avoid having to install a non-clustered instance of SQL Server..
Based on my research, it seems like what I'm trying to achieve is not impossible
This thread here: http://www.mssqltips.com/sqlservertip/2355/dismantling-a-sql-server-cluster-after-a-p2v-physical-to-virtual-migration/
Seems to be my best way forward given the fact that I want to resuse the existing installation and data. My plan is to snapshot my AD servers and SQL servers then with SQL and Clustering shutdown. After that, here is what I've come up with:
1. Remove Failover Clustering
2. Ensure iSCSI disk for SQL Data is mounted
3. Remove the Cluster key from the registry under HKLM\Software\Microsoft\Microsoft SQL Server\...
4. Add the Cluster IP to the host vNIC
5. Restart SQL Server and validate it "works"
6. Stop SQL Server and move data files and etc to new destination
7. Disconnect iSCSI disk
8. Change drive letter of new data disk
9. Restart SQL Server
Anyone mind sanity checking my logic here? When I remove the cluster service and resources, will that also remove SQL Server Instance/Service?
TIA,
Errol Neal

Have you considered storage replication as a solution? You introduce a 3rd node in your SQL Server failover clustered instance but using a disk that is an exact replica of your existing one. This is typically done for a geographically dispersed clusters.
The storage subsystem for the nodes are not shared so you can have different ones per node so long as the storage is replicated on a block-level.
Also, you can introduce another shared storage in your WSFC, shutdown SQL Server and copy all of the database files on the new storage via ROBOCOPY. Once done, you can swap the drive letters of the disks to make SQL Server think like nothing has changed.
So long as the drive letters of the new clustered disks are the same as the old one, everything will work fine.
Another option is configuring an Availability Group as a temporary solution while you fix the storage on your cluster. Add another node on your existing WSFC and install a standalone SQL Server 2012 instance on it. Configure an Availability Group between
the two and failover the databases to this instance while you fix the storage on your SQL Server failover clustered instance.
I don't recommend taking a snapshot of AD. Keep in mind that you have other objects in AD that may be affected when you take a snapshot. You may end up introducing issues in your environment.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

JMQ cluster and unstable connections

Hello all.
I have a few architectural questions about building an OpenMQ message-passing infrastructure between multiple offices which do not always have on-line internet connections. We also need to distribute the MQ mesh configuration info.
From the scale of my questions it seems, that I or our developers don't fully understand MQ, because I think that many of our problems and/or solution ideas (below) should already be implemented within the MQ middleware, and not by us from outside it.
The potential client currently has a (relatively ugly) working solution which they wanted to revise for simplification, if possible, but this matter is not urgent and answers are welcome at any timeframe :)
I'd welcome any insights, ideas and pointers as to why our described approach may be plain wrong :)
To sum this post up, here's my short questionnaire:
1) What is a good/best way to distribute MQ mesh config when not all nodes are available simultaneously?
2) What are the limitations on number of brokers and queues in one logical mesh?
3) Should we aim for separate "internal" and "external" MQ networks, or can they be combined into one large net?
4) Should we aim for partial solution external to OpenMQ (such as integration with SMTP for messaging, or SVN for config distribution), or can this quest be solved within OpenMQ functionality?
5) Can a clustered broker be forced to fully start without available master broker connection?
6) Are broker clusters inherently local-network, or is there some standard solution (pattern) for geographically disperse MQ clusters?
7) How to enforce pushing of the messages from one broker to another? Are any priority assignments available for certain brokers and "their" queues?
Detailed rumblings follow below...
We are thinking about implementing JMQ in a geographically disperse project, where it will be used for asynchronous communications to connect application servers in different branch offices with a central office. The problematic part is, that the central and especially branch offices are not expected to be always on-line, hence the MQ - whenever a connection is available, queued messages (requests, responses, etc.) are to be pushed to the other side's MQ broker. And if all goes well with the project, there may eventually be hundreds of such branch offices and more than one central office for failover, and a mesh of interconnection MQ agreements.
The basic idea is simple: an end-user of the app server in a branch generates a request, this request is passed via message queue to another branch or to a central office, then another app server processes it to generate a response and the answer is queued back to the requesting app server. At some time after the initial request, the end-user would see in his web-page that the request's status has been updated with a response value. A branch office's app server and MQ broker may be an appliance-server distributed as a relatively unmaintained "black box".
During the POC we configured several JMQ broker instances in this manner and it worked. From what I gather from our developers, each branch office's request and response queues are separate destinations in the system, and requests (from a certain branch) may be subscribed by any node, and responces (to a certain branch) may be submitted by any node. This may be restricted by passwords and/or certificate-based SSL tunnel channels, for example (suggestions welcome, though).
However, we also wanted to simplify spreading the configuration of the MQ nodes' network by designating "master brokers" (as per JMQ docs) which keep track of the config and each other broker downloads the cluster config from its master. Perhaps it was wrong on our side, and a better idea is available to avoid manual reconfiguration of each MQ broker whenever another broker or a queue destination is added?
Problem here is: it seems an "MQ cluster" is a local-network oriented concept. When we have a master broker in a central office, and the inter-connection is not up, branch offices loop indefinitely waiting for connection to a master, and reject client connections (published JMS port remains 0, and appropriate comments in the log files). In this case the branch office can not function until its JMQ broker connects to a central office, updates the MQ config, and permits client connections to itself.
Also we are not certain (and it seems to be a popular question on Google, too) how to enforce a queued message to be pushed to another side - to a broker "nearest" to the target app server? Can this be done within OpenMQ config, or does this require an MQ client application to read and manipulate such messages somehow? For example, when a branch office's "request" queue has a message, and a connection to central office comes online, this request data should end up in the central office's broker. Apparently, a message which physically remains in the branch office broker when the interconnection goes offline, is of little use to the central appserver...
I was thinking along the lines of different-priority brokers for a certain destinations, so that messages would automatically flow from further brokers to neares ones - like water flows from higher ground to lower ground in an aqueduct. It would then be possible to easily implement transparent routing between branch offices (available at non-intersecting times) via central office (always up).
How many brokers and destination can be interconnected at all (practically or theoretically/hardcoded)?
Possibly, there are other means to do some or all of this?
Ideas we've discussed internally include:
* Multiple networks of MQ brokers:
Have an "internal" broker (cluster) in each branch office which talks to the app server, and a separate "external" broker which is clustered with the central office's "master broker". Some branch office application transfers messages between two brokers local to its branch. Thus the local appserver works okay, and remote queuing works whenever network is available.
Possibly, the central office should also have separate internal and external broker setups?
* Multi-tiered net of MQ brokers:
Perhaps there can be "clusters of clusters" - with "external" tier-1 brokers being directly master brokers for local "internal" tier-2 clusters? Otherwise the idea of "miltiple networks of MQ brokers" above, without an extra app to relay messages between MQ brokers local to this app.
* Multi-protocol implementation of MQ+SMTP(+POP3/IMAP)
Many of our questions are solvable by SMTP. That is, we can send messages to a mailbox residing on a specific server (local in each office), and local appserver clients retrieve them by POP3 from the local mailbox server, and then submit responses over SMTP. This is approximately how the client currently solves this task now.
We don't really want to invent a bicycle, but maybe this approach can also be applied to JMQ (asynch traffic not over MQ protocol, but over SMTP like in SOAP-SMTP vs. SOAP-HTTP webservices)?
* HTTP/RCS-based config file:
The OpenMQ config allows for the detailed configuration file to be available in local filesystem or on a web server. It is possible to fetch the config file from a central office whenever the connection is up (wget, svn/cvs/etc.) and restart the branch broker.
Why is this approach good or bad? Advocates welcome :)
Thanks for reading up to the end,
and thanks in advance for any replies,
//Jim Klimov

Hello all.
I have a few architectural questions about building an OpenMQ message-passing infrastructure between multiple offices which do not always have on-line internet connections. We also need to distribute the MQ mesh configuration info.
From the scale of my questions it seems, that I or our developers don't fully understand MQ, because I think that many of our problems and/or solution ideas (below) should already be implemented within the MQ middleware, and not by us from outside it.
The potential client currently has a (relatively ugly) working solution which they wanted to revise for simplification, if possible, but this matter is not urgent and answers are welcome at any timeframe :)
I'd welcome any insights, ideas and pointers as to why our described approach may be plain wrong :)
To sum this post up, here's my short questionnaire:
1) What is a good/best way to distribute MQ mesh config when not all nodes are available simultaneously?
2) What are the limitations on number of brokers and queues in one logical mesh?
3) Should we aim for separate "internal" and "external" MQ networks, or can they be combined into one large net?
4) Should we aim for partial solution external to OpenMQ (such as integration with SMTP for messaging, or SVN for config distribution), or can this quest be solved within OpenMQ functionality?
5) Can a clustered broker be forced to fully start without available master broker connection?
6) Are broker clusters inherently local-network, or is there some standard solution (pattern) for geographically disperse MQ clusters?
7) How to enforce pushing of the messages from one broker to another? Are any priority assignments available for certain brokers and "their" queues?
Detailed rumblings follow below...
We are thinking about implementing JMQ in a geographically disperse project, where it will be used for asynchronous communications to connect application servers in different branch offices with a central office. The problematic part is, that the central and especially branch offices are not expected to be always on-line, hence the MQ - whenever a connection is available, queued messages (requests, responses, etc.) are to be pushed to the other side's MQ broker. And if all goes well with the project, there may eventually be hundreds of such branch offices and more than one central office for failover, and a mesh of interconnection MQ agreements.
The basic idea is simple: an end-user of the app server in a branch generates a request, this request is passed via message queue to another branch or to a central office, then another app server processes it to generate a response and the answer is queued back to the requesting app server. At some time after the initial request, the end-user would see in his web-page that the request's status has been updated with a response value. A branch office's app server and MQ broker may be an appliance-server distributed as a relatively unmaintained "black box".
During the POC we configured several JMQ broker instances in this manner and it worked. From what I gather from our developers, each branch office's request and response queues are separate destinations in the system, and requests (from a certain branch) may be subscribed by any node, and responces (to a certain branch) may be submitted by any node. This may be restricted by passwords and/or certificate-based SSL tunnel channels, for example (suggestions welcome, though).
However, we also wanted to simplify spreading the configuration of the MQ nodes' network by designating "master brokers" (as per JMQ docs) which keep track of the config and each other broker downloads the cluster config from its master. Perhaps it was wrong on our side, and a better idea is available to avoid manual reconfiguration of each MQ broker whenever another broker or a queue destination is added?
Problem here is: it seems an "MQ cluster" is a local-network oriented concept. When we have a master broker in a central office, and the inter-connection is not up, branch offices loop indefinitely waiting for connection to a master, and reject client connections (published JMS port remains 0, and appropriate comments in the log files). In this case the branch office can not function until its JMQ broker connects to a central office, updates the MQ config, and permits client connections to itself.
Also we are not certain (and it seems to be a popular question on Google, too) how to enforce a queued message to be pushed to another side - to a broker "nearest" to the target app server? Can this be done within OpenMQ config, or does this require an MQ client application to read and manipulate such messages somehow? For example, when a branch office's "request" queue has a message, and a connection to central office comes online, this request data should end up in the central office's broker. Apparently, a message which physically remains in the branch office broker when the interconnection goes offline, is of little use to the central appserver...
I was thinking along the lines of different-priority brokers for a certain destinations, so that messages would automatically flow from further brokers to neares ones - like water flows from higher ground to lower ground in an aqueduct. It would then be possible to easily implement transparent routing between branch offices (available at non-intersecting times) via central office (always up).
How many brokers and destination can be interconnected at all (practically or theoretically/hardcoded)?
Possibly, there are other means to do some or all of this?
Ideas we've discussed internally include:
* Multiple networks of MQ brokers:
Have an "internal" broker (cluster) in each branch office which talks to the app server, and a separate "external" broker which is clustered with the central office's "master broker". Some branch office application transfers messages between two brokers local to its branch. Thus the local appserver works okay, and remote queuing works whenever network is available.
Possibly, the central office should also have separate internal and external broker setups?
* Multi-tiered net of MQ brokers:
Perhaps there can be "clusters of clusters" - with "external" tier-1 brokers being directly master brokers for local "internal" tier-2 clusters? Otherwise the idea of "miltiple networks of MQ brokers" above, without an extra app to relay messages between MQ brokers local to this app.
* Multi-protocol implementation of MQ+SMTP(+POP3/IMAP)
Many of our questions are solvable by SMTP. That is, we can send messages to a mailbox residing on a specific server (local in each office), and local appserver clients retrieve them by POP3 from the local mailbox server, and then submit responses over SMTP. This is approximately how the client currently solves this task now.
We don't really want to invent a bicycle, but maybe this approach can also be applied to JMQ (asynch traffic not over MQ protocol, but over SMTP like in SOAP-SMTP vs. SOAP-HTTP webservices)?
* HTTP/RCS-based config file:
The OpenMQ config allows for the detailed configuration file to be available in local filesystem or on a web server. It is possible to fetch the config file from a central office whenever the connection is up (wget, svn/cvs/etc.) and restart the branch broker.
Why is this approach good or bad? Advocates welcome :)
Thanks for reading up to the end,
and thanks in advance for any replies,
//Jim Klimov

2008 R2 Multi-Site Cluster Possible without Third Party Software?

2008 R2 Multi-Site Cluster Possible without Third Party Software? I know it has been asked, but I haven't seen a specific answer. We are using Dell Compellent Storage and I created several read only replicated volumes at our DR site. I
am having issues failing over to the volumes after I use cluster cli to mount the read only volumes.
Any help would be appreciated greatly!

2008 R2 Multi-Site Cluster Possible without Third Party Software? I know it has been asked, but I haven't seen a specific answer. We are using Dell Compellent Storage and I created several read only replicated volumes at our DR site. I
am having issues failing over to the volumes after I use cluster cli to mount the read only volumes.
Any help would be appreciated greatly!
To have this working reliably you need to have 1) redundant and pretty fatty pipes between your sites (Primary and Disaster Recovery) and 2) your storage (Compellent in your case) being placed in third location. If you'll have both conditions met you'll
have decent performance and would avoid brain split issue when both sites would be up and uplink between sites is down. Good links on geo clustering:
Geo Cluster for Windows
http://clusteringformeremortals.com/2009/09/15/step-by-step-configuring-a-2-node-multi-site-cluster-on-windows-server-2008-r2-%E2%80%93-part-1/
Geo
Cluster for Windows 2008
http://blogs.technet.com/b/johnbaker/archive/2008/03/28/windows-server-2008-geo-clustering-multi-site-clustering.aspx
Geographically Dispersed Clustering
http://msmvps.com/blogs/jtoner/
Hope this helped :)
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.

SAP B1 2007A in a cluster.

Good <timeofday>,
   I am setting up a cluster to have high availability for my B1 install, well at least a failover.
   Funny enough, my server doesn't support hardware virtualization so it's not an option at this time, however I do have access to Windows 2008 R2 and SQL 2008 both enterprise editions and the decision to go with Microsoft's failover cluster has been made.
The issue is the server tools, I'm trying to set them up as generic application into the SQL portion of the cluster, unfortunately the service manager keeps picking up the Node's server name rather than the SQL server name and will not connect, I cannot perform my updates of SAP and likely will have problems with any services run by the manager, DI, Backup, Mailer and so on.
   Is there a way to tell the service what the server name is? Force the proper connection thru either a configuration file or registry entry. The microsoft clustering software allows me to setup a virtual registry for the applications for that purpose.
   Anyone else tried this type of configuration? Any white paper, how to on the subject?
   Any other solution to have a fail over SAP B1 server?
Thanks,

After many hours of inquiring, searching and digging... There is an obscur SAP Note that says clearly, NOT SUPPORTED.
Best thing I could do, was to keep a server with the same configuration ready to connect to my SAN and take over from the dead server.
So for anyone interested in this topic. Save you time, search the SAP Notes for Support and high availability.
Hope that helps others.

SQL Cluster - Unable to obtain IP Address from System Center IP Pool

Hi everyone,
we are trying to deploy a SQL cluster into a windows azure pack tenant cloud.
Our azure pack environment contains:
- 4X Hyper-V server in a failover cluster
- 1X SCVMM server
- multiple WAP server
Steps we have done:
-   Windows failover cluster is installed and configured successfully
-   Quorum disk was configured successfully
-   SQL server 2014 installation (via static IP) is successfully. But routing between the VMs is not possible.
-   SQL server 2014 installation (via DHCP) fails at the end of the installation with following error:
       -> We used DHCP to obtain an IP from the scvmm IP pool.
(01) 2015-04-22 15:29:11 Slp: Running Action: cluster_ip_address_cluster_config_Cpu64
(01) 2015-04-22 15:29:11 Slp: Action Data:
(01) 2015-04-22 15:29:11 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64
(01) 2015-04-22 15:29:11 Slp:   Scenario = install
(01) 2015-04-22 15:29:11 Slp:   Timing = ConfigNonRC
(01) 2015-04-22 15:29:11 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.ClusterConfiguration.ClusterIPAddressPrivateConfigObject
(01) 2015-04-22 15:29:11 Slp:   FeatureName = SQL_Engine_Core_Inst
(01) 2015-04-22 15:29:11 Slp:   FeatureCpuType = Cpu64
(01) 2015-04-22 15:29:11 Slp:   FeaturePackageId = sql_engine_core_inst
(01) 2015-04-22 15:29:11 Slp:   FeatureClusterState = CompleteFailoverCluster
(01) 2015-04-22 15:29:11 Slp: Creating IPv4 address 'SQL IP Address 1 (SQLADFS)'.
(01) 2015-04-22 15:29:11 Slp: Creating cluster resource 'SQL IP Address 1 (SQLADFS)' of type 'IP Address' in group 'SQL Server (ADFS)'
(01) 2015-04-22 15:29:11 Slp: Bringing IP address resource 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (ADFS)' Resource='SQL IP Address 1 (SQLADFS)'' online
(01) 2015-04-22 15:29:11 Slp: Bringing cluster resource 'SQL IP Address 1 (SQLADFS)' online
(01) 2015-04-22 15:29:12 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
(01) 2015-04-22 15:29:12 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-04-22 15:29:12 Slp: Inner exceptions are being indented
(01) 2015-04-22 15:29:12 Slp:
(01) 2015-04-22 15:29:12 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
(01) 2015-04-22 15:29:12 Slp:     Message:
(01) 2015-04-22 15:29:12 Slp:         The cluster resource 'SQL IP Address 1 (SQLADFS)' could not be brought online. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure
. Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:         .
(01) 2015-04-22 15:29:12 Slp:     HResult : 0x86d8003a
(01) 2015-04-22 15:29:12 Slp:         FacilityCode : 1752 (6d8)
(01) 2015-04-22 15:29:12 Slp:         ErrorCode : 58 (003a)
(01) 2015-04-22 15:29:12 Slp:     Data:
(01) 2015-04-22 15:29:12 Slp:       resourceName = SQL IP Address 1 (SQLADFS)
(01) 2015-04-22 15:29:12 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
(01) 2015-04-22 15:29:12 Slp:       DisableRetry = true
(01) 2015-04-22 15:29:12 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
(01) 2015-04-22 15:29:12 Slp:         Message:
(01) 2015-04-22 15:29:12 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The
group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:                 .
(01) 2015-04-22 15:29:12 Slp:         HResult : 0x86d70002
(01) 2015-04-22 15:29:12 Slp:                 FacilityCode : 1751 (6d7)
(01) 2015-04-22 15:29:12 Slp:                 ErrorCode : 2 (0002)
(01) 2015-04-22 15:29:12 Slp:         Data:
(01) 2015-04-22 15:29:12 Slp:           ExceptionMessage = Generic failure
(01) 2015-04-22 15:29:12 Slp:           StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
(01) 2015-04-22 15:29:12 Slp:         Stack:
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:         Inner exception type: System.Management.ManagementException
(01) 2015-04-22 15:29:12 Slp:             Message:
(01) 2015-04-22 15:29:12 Slp:                         Generic failure
(01) 2015-04-22 15:29:12 Slp:             HResult : 0x80131501
(01) 2015-04-22 15:29:12 Slp:             Data:
(01) 2015-04-22 15:29:12 Slp:               WmiErrorCode = Failed
(01) 2015-04-22 15:29:12 Slp:               WatsonData = Failed@5023
(01) 2015-04-22 15:29:12 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:               ErrorType = 1
(01) 2015-04-22 15:29:12 Slp:               Operation = ExecMethod
(01) 2015-04-22 15:29:12 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL IP Address 1 (SQLADFS)"
(01) 2015-04-22 15:29:12 Slp:               ProviderName = WinMgmt
(01) 2015-04-22 15:29:12 Slp:               StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:             Stack:
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject
inParameters, InvokeMethodOptions options)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
We have tried to reinstall the servers multiple times, without result.
Can anyone assist us in this case?
Thanks
Kind Regards
Julian

Hi Darryl,
thanks for your supply.
We don't have an DHCP in the Cloud. System Center DHCP is used for assigning IP addresses and routing inforamtion to the vms.
This works fine for assigning IP addresses to the vms.
At my current point of understanding network virtualisation with system Center, we do not have an alternative to this way of assigning IP addresses.
Kind Regards
Julian

Guest two node Failover Cluster with SAS HBA and Windows 2012 R1

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George

Hi all, i have two IBM x3560 brand new servers with V3700 IBM Storage. The Servers are connected to the storage through four SAS HBA adabters (two HBA's on each server). I want to create a two node guest Fileserver Failover Cluster. I can present the
LUN's to the guest machines, but when i 'm running the cluster creation wizard it can't see any disk. I can see the disks on disk management console. Is there any way to achive this (the cluster creation) using my SAS HBA presented
disks, or i have to use iSCSI to present the disks to my cluster?
Thank you in advance, George
1) Update to R2 and use shared VHDX which is a better way to go. See:
Shared VHDX
http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-feature-in-windows-server-2012-r2.aspx
Clustering
Options
http://blogs.technet.com/b/josebda/archive/2013/07/31/windows-server-2012-r2-storage-step-by-step-with-storage-spaces-smb-scale-out-and-shared-vhdx-virtual.aspx
2) If you want to stick with non-R2 (which is a BAD idea b/c tons of reasons) you can spawn an iSCSI target on top of your storage, make it clustered and make it provide LUs to your guest VMs. See:
iSCSI Target in Failover
http://technet.microsoft.com/en-us/library/gg232632(v=ws.10).aspx
iSCSI Target Failover Step-by-Step
http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
3) Use third-party software providing clustered storage (active-active) out-of-box.
I would strongly recommend to upgrade to R2 and use shared VHDX.
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.

SQL 2008 R2 cluster installation failure - Failed to find shared disks

Hi,
The validation tests in the SQL 2008R2 cluster installation (running Windows 2008 R2) fails with the following error. The cluster has one root mount point with multiple mount points :
"The cluster on this computer does not have a shared disk available. To continue, at least one shared disk must be available'.
The "Detail.txt" log has alot of "access is denied" errors and here is just a sample. Any ideas what might be causing this issue?
2010-09-29 12:54:08 Slp: Initializing rule      : Cluster shared disk available check
2010-09-29 12:54:08 Slp: Rule applied features : ALL
2010-09-29 12:54:08 Slp: Rule is will be executed : True
2010-09-29 12:54:08 Slp: Init rule target object: Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterSharedDiskFacet
2010-09-29 12:54:09 Slp: The disk resource 'QUORUM' cannot be used as a shared disk because it's a cluster quorum drive.
2010-09-29 12:54:09 Slp: Mount point status for disk 'QUORUM' could not be determined. Reason: 'The disk resource 'QUORUM' cannot be used because it is a cluster quorum drive.'
2010-09-29 12:54:09 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca48-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:09 Slp:     Access is denied.
2010-09-29 12:54:09 Slp: Mount point status for disk 'SQL01_BAK01' could not be determined. Reason: 'The search for mount points failed. Error: Access is denied.'
2010-09-29 12:54:10 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca4f-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:10 Slp:     Access is denied.
2010-09-29 12:54:10 Slp: Mount point status for disk 'SQL01_DAT01' could not be determined. Reason: 'The search for mount points failed. Error: Access is denied.'
2010-09-29 12:54:10 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca56-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:10 Slp:     Access is denied.
Thanks,
PK

Hi,
We were asked by the PSS engineer to give the following privileges the account used to install SQL Server - i am referring to the user domain account as apposed to the SQL service account. These privileges were already applied to the
SQL service account prior to the SQL installation. Assigning these privileges to the user account resolved the issue.
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
Thanks for everyones assistance.
Cheers,
PK

Install Oracle 11 On Windows 2008 Cluster

Hi,
I am planning to go for the installation of Oracle 11g R2 on Microsoft Windows 2008 cluster.
Can any one suggest me how can i go with the installation.
I have done Oracle 11g R2 RAC implementation and Oracle 11g R2 on dedicated microsoft Servers.
Can anyone help me out to sort out this problem.It would be helpful for me.
Is there any documentation on this.
Regards
Bobs

Hi all,
I have just got a link which might help me and others.
http://download.oracle.com/docs/cd/E16161_01/doc.342/e14976/toc.htm
Regards
Bobs

Cluster Service 1146 & 1230 event id

Dear Team,
I am facing a cluster problem in server 2012 r2 its showing me error event id 1146 & 1230
i am not able to start my cluster service my production is total down please help
Here is log with this link pls help
https://onedrive.live.com/redir?resid=4A228E11EF76B735!193&authkey=!AKCOUxUeE4FEu8A&ithint=file%2ctxt
Ravi Tandon
8400414038

Hi,
The log is incomplete. The error 1146 or 1230 is not included in the log file you uploaded.
According to my search result, error 1146 & 1230 could be caused by dll crash issue. You can search in your local log file to see if you can find such entry:
Error server.domain.com 1230 Microsoft-Windows-FailoverClustering Cluster resource 'AA_BBBB' (resource type '', DLL 'XXXXX.dll') either crashed or deadlocked.
If so, search for the dll file to see if you can find any detailed information. Sometimes it could belong to a third party application and you can try to uninstall it to see the result. Or if it belong to a Role or Service, you can try to repair/reinstall
it.
And as Tim said, analysis log on TechNet forum is a little difficult as log files are large and almost all log files contain company information. You can try to submit a case to Microsoft for an efficient response.
If you have any feedback on our support, please send to [email protected]

SCOM cluster monitoring

Hi all,
recently a client of mine complained that he wasn't alerted on a cluster service that stopped on some of his machines. i checked and found the reason was that i do not have the windows server 2012 cluster management monitoring MP installed.
when googling for it, i got to: http://www.microsoft.com/en-us/download/confirmation.aspx?id=2268
but from what i understand, this MP is for all servers type (2003, 2008). i have 2003/8 installed, only need 2012. if i go ahead and install this MP, will it just upgrade the versions of the 2003/8 MPs? can that hurt me somehow? i mean like cause subscriptions
not to work or whatever.
thanks,
Uri

Hi Uri,
From the guide:
"If you have version 6.0.6277.0 of the Windows Server 2003 Cluster Management Pack:
If you have installed the Windows Server 2003 Cluster Management Pack 6.0.6277.0, remove the following management pack files prior to importing this management pack:
Microsoft.Windows.2003.Cluster.Management.Monitoring
Microsoft.Windows.2003.Cluster.Management.Library
Microsoft.Windows.Cluster.Management.Monitoring
Microsoft.Windows.Cluster.Management.Library
If you have any other version of the Windows Server Failover Cluster Management Pack, you can upgrade the management pack without performing the previous steps.
An in-place upgrade is supported for Windows Server 2003 Cluster Management Pack versions 6.0.6277.1 and higher."
Natalya

Microsoft geographically dispersed cluster.

Similar Messages

Maybe you are looking for