Replication solution for MSCS Failover Cluster?

That is definitely the plan, just a matter of finding the best software solution to achieve that. I imagine StarWind free version is an option...

I am setting up a multi-site windows failover cluster (windows server 2008 r2), to be used for a print services cluster. My sites are connected via mlps network, but I've run into a bit of a snag: I need to have shared storage (cluster disk), and since it is across multiple sites, it is going to have to be 2 volumes that have replication between them that complies with MSCS (removing options like vmware replication and MS DFS). Each location has SAN storage, but are from different providers and cannot replicate between each other on that level, so I am looking for a (free or low-cost) software solution that I can put inside a VM at each location to serve as my cluster disk.
Any suggestions are greatly appreciated, thanks.
This topic first appeared in the Spiceworks Community

Similar Messages

Configure Database Control web page in MSCS Failover Cluster

I have a two-node windows 2000 cluster that is managed with Microsoft Cluster Services and Oracle FailSafe Manager. The cluster works fine, so does connecting to the database with SQL; however, I have been unable to use the database control EM web page to access the database. The page appears with the Database/Instance/Listener titles but no data/information appears.
There is a virtual host name and IP address for the cluster which I can use successfully when accessing thru SQL. I've tried the system name and the virtual cluster name in the http://<SYSTEMNAME>:1521/em web address. I've tried both without the "em".
The emctl agent is running. The dbconsole service is running correctly.
Which name should I use in the web address - host system name or virtual (cluster) host name? What configuration parameters am I missing?
Any help would be greatly appreciated.
Thanks in advance!

Problem could be same but reason could be diffrent
please paste the emos.trc and tell the oms version , platform.

Quorum location for Failover cluster file share witness

So, I've done quite a bit of searching for what I'm about to propose and I've been able to find nothing.
I currently have a multi site failover cluster hosting separate 2-node SQL clusters at each site connected through an Availability Group. For the failover cluster I am using a file share witness hosted on a server at the primary site. Both sites
are built entirely on vSphere 5.5 and have full replication for the production servers. If the primary site goes down (disaster), I'll need to force quorum in the secondary site to a new file share witness.
Well, I got to thinking...
Why not just replicate the server hosting the file share? I completely understand the reasoning behind not putting the file share witness on DFS, but a replicated virtual server, why not? If the primary site fails, the replicated server hosting
the file share witness is brought online with the rest of the production servers in the DR site. In that case, the only thing that changes is the server IP address, but ultimately, the server name and share where quorum is hosted all stays the same.
Ultimately this prevents needing to find a 3rd geographical/cloud location to host a quorum/witness at. I can't imagine it's this "simple", but maybe it is. If this is possible, and there's not something I'm missing, this essentially
makes the quorum file share witness site agnostic, meaning it could live or be moved anywhere that replication is allowed.
Ideas, thoughts? Am I missing something?
Thanks!
Chris Miller

Most likely it would be better to put this question to the High Availability forum -
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverClustering
But, might need a more complete definition of your environment. Are you saying that you have multiple 2-node clusters, each with one node in the primary and the second node in the DR site? And you have a single file share server located in primary that
is used to host the file share witnesses for all these clusters? You want to use VMware to replicate the file share server to the DR site so that it can be made available should the primary site fail?
It should work, but it will not be automatic. After all, the replicated VM will need to be brought online at the DR site so the SQL cluster will recognize it. That is not an automatic process. So the cluster will be down until
you bring the file share server online so it can be recognized. Not a whole lot different that simply forcing the DR SQL host to run without quorum.
. : | : . : | : . tim

Event Trace Session missing for Failover Cluster

I have a failover cluster setup and is managed via a Windows Domain controller for the failover cluster network. I am troubleshooting a potential issue with the failover cluster and the recommendation is to go into event viewer, app & service
logs, Microsoft, windows and look for failover cluster diagnostics and operations logs and these do not exist.
It appears they are created by having an event trace session associated with windows failover clustering but apparently it was't created when the cluster was created for some reason. I am wondering how to create the proper event trace session
in order to get these additional failover cluster logs created?

Hello,
the following forum mat be the better one for your needs:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverClustering
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

Failover Cluster Validation Report Error with IBM USB Remote NDIS Network device

We are setting up Microsoft Windows Server 2008 R2 Failover Cluster on IBM X3850 X5 and get errors in the Failover cluster Validation Report due to the IBM USB Remote NDIS Network Device is using APIPA adresses and both servers are using same APIPA-adresse.
How should I configure the Server and OS for the Failover cluster to be MS approved?
IBM don't recommend that i disable the Network device, but it is a possible solution!?!

What I did was use ipconfig /all to see the settings it is using and then when and set the ip setting on the NDIS driver to be that except I increment the last value by 1 for each node so that they do not have the same IP address. I ran the
cluster validation again and it came up clean and I have not experienced any issues yet. It does give warnings about it being an Automatic Private IP Address and should not be used, which is ok because we are not going to use it anyways.
Rich Baumet

Replication solutions with Oracle 8i

Hello,
I'm looking for solutions to make real time replications from an Oracle 8i database.
For more details :
- we have an existing database with Oracle 8i
- we want to replicate this database: the replicated database will be used by a web application.
- we need the replication to be in real-time
For the moment i didn't find much informations on the web and it seems that replication solutions for the version 8i are quiet limited.
If someone have any idea on how i can do this, it would be helpfull.
Thanks,

Among the problems, though, is that there are numerous ways to architect a replication process. That architecture requires you to make various trade-offs. Without understanding what you're attempting to gain in a business sense from the replication process, though, it's impossible to even attempt to figure out which trade-offs to make.
One option would be to create a new database for the reporting app and create a fast-refreshable materialized view in the reporting database for every table in the source system. In the source system, you'd then create materialized view logs on every table in the source database. If you want the reporting system to be transactionally consistent, you'd need to put the various materialized views into one or more refresh groups and schedule those refresh groups to run every 5 minutes.
That would probably get close to having data on the reporting system within 10 minutes of it being created on the source system. The downsides, though, would include
- Every transaction on the source system now needs to synchronously write to the materialized view logs. This is roughly equivalent to creating a new trigger on every table in your system, which can be a decent load.
- The reporting system will have to poll the source system for data changes every few minutes. That's likely to put a pretty decent load on the source system.
- Making DDL or large DML changes to the source requires the source system admins to be conscious of the destination system's needs (the destination system's materialized view may need to be recreated and an initial full refresh may need to be done which may impact the timing of the change on the source system).
- The source system admins (and the destination system admins) have to monitor the refresh process, the size of the materialized view logs, etc.
- Spreading information across multiple systems increases the liklihood of improper data disclosure because you have less ability to figure out who has access to any particular piece of data, for example.
For a reporting application, I'm really hard pressed to imagine that these downsides are worth whatever benefit you're trying to achieve.
Justin

Packets sent out the wrong Interface on Hyper-V 2012 Failover Cluster

Here is some background information:
2 Dell PowerEdge servers running Windows Server 2012 w/ Hyper-V in a Failover Cluster environment. Each has:
1 NIC for Live Migration 192.168.80.x/24 (connected to a private switch)
1 NIC for Cluster Communication 192.168.90.x/24 (connected to a private switch)
1 NIC for iscsi 192.168.100.x/24 (connected to a private switch)
1 NIC for host management with a routable public IP (*connected to corp network) w/ gateway on this interface
1 NIC for Virtual Machine traffic (*connected to corp network)
All NICs are up, we can ping the IPs between servers on the private network and on the public facing networks. All functions of hyper-v are working and the failover cluster reports all interfaces are up and we receive no errors. Live migration
works fine. In the live migration settings i have restricted the use of the 2 NICs (live migration or cluster comm).
My problem is that our networking/security group sees on occasion (about every 10 minutes with a few other packets thrown in at different times) syn packets that are destined for the 192.168.80.3 interface goes out of the public interface and is dropped
at our border router. These should be heading out of the 192.168.80.x or 192.168.90.x interfaces without ever hitting our corporate network. Anyone have an idea of why this might be happening? Traffic is on TCP 445.
Appreciate the help.
Nate

Hi,
Please check live migration and Cluster Communication network settings in cluster:
In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
Expand Networks.
Right-click the network that you want to modify settings for, and then click Properties.
There are two options:
Allow cluster network communication on this network-- Allow clients to connect through this network
Do not allow cluster network communication on this network
If the network is used only for cluster node communication, clear “Allow clients to connect through this network” option.
Check that and give us feedback for further troubleshooting, for more information please refer to following MS articles:
Modify Network Settings for a Failover Cluster
http://technet.microsoft.com/en-us/library/cc725775.aspx
Lawrence
TechNet Community Support

Failover cluster programming

Hello,
I'm writing a windows service that has to be clustered by Windows Server Failover Cluster (WSFC).
When I do planned failover, WSFC stops the service on the owning node and starts the service on the destination node. I'm trying to find a way to tell to the WSFC "Hey man, don't stop me because of xxxxxxxx".

Hi Andrea,
This forum is discuss and ask questions about the C# programming language, IDE, libraries, samples, and tools. I am afraid you posted in an inappropriate forum.
About Windows Server Failover Cluster (WSFC) should be posted in Windows server forums. And they are on the technet web site. This web site is for help in writing software.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/fb7c5fc0-7ab4-4ecc-9634-ebc17ab57a3e/where-is-the-forum-for-windows-failover-cluster-programming-help?forum=whatforum
Please consider posting in that forum. Thanks for your understanding.
Best regards,
Kristin
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.
Click
HERE to participate the survey.

2008 R2 failover cluster dns

Hello,
Wondering if there is any best practices when it comes to setting up DNS. Options are either dynamic DNS or add static A records for nodes and cluster name. Also I understand that there will be no DNS servers specified in TCP properties of the heartbeat
NIC.
Thanks

Hi,
please check "Network infrastructure and domain account requirements for a failover Cluster"
http://technet.microsoft.com/en-us/library/ff182359(v=ws.10).aspx#BKMK_Account_Infrastructure
The cluster should automatic register DNS records for ech cluster node and for the cluster name.
And yes, you do not need to specify DNS servers for heartbeat, livemigration or CSV NIC.
Hope that helps
Regards
Sebastian

Windows Server Failover Cluster Tahniques

We have Two Servers Ready to be Deploy the SQL 2012; Need to make Cluster of These two nodes.
We have Servers with 900 GB Unallocated local Disk Space in each server.
We Don't have any kind of Shared Storage.
My Questions are:
- how to make Qourum?
- How to Use these Two Disks on each server so that Data will be Replicated?
- After Making the Cluster, how to Install the SQL server?

Hi,
The shared storage is necessary for the failover cluster, if you don’t have the share storage you can’t build the failover cluster. The two node local disk space can’t be
used as the CSV storage.
More information:
Understanding Cluster Shared Volumes in a Failover Cluster
http://technet.microsoft.com/en-us/library/dd759255.aspx
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.

Replication solutions

Hi,
I got requirement of data to be sync at different locations. One will be the centralized database and other databases are on different locations like three to four locations. So, what would be the best solution in this case Should I use replication, streams or any other third party tool.
Thank you for your cooperation.
Kind Regards,
Adnan Hamdus Salam

Hi,
I'm using the Oracle streaming since last 2 Year.
Oracle Streaming is the best oracle replication solution for synchronize the multiple remote databases.
There are various other alternative as well like Oracle Golden Gate, Oracle Advance Replication, Oracle Materialized Views
Regards
Hitgon
Edited by: hitgon on Jan 11, 2012 2:40 AM

Dedicated network for AlwaysON replication traffic when a replica is a Failover Cluster Instance

Hi,
We are planning to setup dedicated network for our Availability Group replication traffic. We have a Failover Cluster Instance as the primary replica and a standalone SQL server instance as the secondary.
I understand that we will need to manually configure the database mirroring endpoints on both the replicas to listen on the specific IP.
But how do I configure the database mirroring endpoint on the Failover Cluster Instance ?
Please help.
Thanks and Regards,
Jisha

If you have a dedicated network for your Availability Group replication traffic between the FCI and the standalone instance, you need to identify if there will be other network services included in the mix. For example, your public network is already using
it's own DNS server by virtue of Active Directory integration. Your dedicated network for replication traffic may or may not have its own DNS server so configuring the endpoints would involve using either IP addresses like the one highlighted in the
blog post or using hosts file with fully qualified domain names so you can use them when creating the endpoints
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Cannot add multiple members of a failover cluster to a DFSR replication group

Server 2012 RTM. I have two physical servers, in two separate data centers 35 miles apart, with a GbE link over metro fibre between them. Both have a large (10TB+) local RAID storage arrays, but given the physical separation there is no physical shared storage.
The hosts need to be in a Windows failover cluster (WSFC), so that I can run high-availability VMs and SQL Availability Groups across these two hosts for HA and DR. VM and SQL app data storage is using a SOFS (scale out file server) network share on separate
servers.
I need to be able to use DFSR to replicate multi-TB user data file folders between the two local storage arrays on these two hosts for HA and DR. But when I try to add the second server to a DFSR replication group, I get the error:
The specified member is part of a failover cluster that is already a member of the replication group. You cannot add multiple members for the same cluster to a replication group.
I'm not clear why this has to be a restriction. I need to be able to replicate files somehow for HA & DR of the 10TB+ of file storage. I can't use a clustered file server for file storage, as I don't have any shared storage on these two servers. Likewise
I can't run a HA single DFSR target for the same reason (no shared storage) - and in any case, this doesn't solve the problem of replicating files between the two hosts for HA & DR. DFSR is the solution for replicating files storage across servers with
non-shared storage.
Why would there be a restriction against using DFSR between multiple hosts in a cluster, so long as you are not trying to replicate folders in a shared storage target accessible to both hosts (which would obviously be a problem)? So long as you are not replicating
folders in c:\ClusterStorage, there should be no conflict.
Is there a workaround or alternative solution?

Yes, I read that series. But it doesn't address the issue. The article is about making a DFSR target highly available. That won't help me here.
I need to be able to use DFSR to replicate files between two different servers, with those servers being in a WSFC for the purpose of providing other clustered services (Hyper-V, SQL availability groups, etc.). DFSR should not interfere with this, but it
is being blocked between nodes in the same WSFC for a reason that is not clear to me.
This is a valid use case and I can't see an alternative solution in the case where you only have two physical servers. Windows needs to be able to provide HA, DR, and replication of everything - VMs, SQL, and file folders. But it seems that this artificial
barrier is causing us to need to choose either clustered services or DFSR between nodes. But I can't see any rationale to block DFSR between cluster nodes - especially those without shared storage.
Perhaps this blanket block should be changed to a more selective block at the DFSR folder level, not the node level.

Transactional replication from a failover cluster instance to a SQL Server Express DB

Hello,
I have been poking around on Google trying to understand if there are any gotchas in configuring transactional replication on a instance DB of a failover cluster, to a SQL Server Express DB. Also, this client would like to replicate a set of tables between
two instances DB's which both reside on nodes of the cluster.
Everything I've read suggests there is no problem using transactional replication on clustered instance as long as you use a shared snapshot folder. I still have some concerns:
1) Should the distributor need to live on a separate instance?
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber.
There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Thanks in advance.

1) Should the distributor need to live on a separate instance?
Answer: It is recommended to configure the distributor on the different server, but it also be configured on Publisher/subscriber server. (Subscriber in our case is not possible as its a Express edition)
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber. There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Answer: If you configure both publisher and distributor on the same server and the SQL instance is failed over, the data synchronization/replication is suspended till the instance comes online.
Once the instance is up,all the replication jobs will start again and it will continue to synchronize the data to subscriber. No manual intervention is required.

Non MSCS HA Solution for Win 2008 /SQL 2008

Hello Team
Is there a NON MSCS solution out there for doing HA in Windows? SQL Environment. So far the HA use cases that I have seen are based on MSCS , However I would like to know if there is an SAP support solution for NON CLUSTERED (NON-MSCS) setup for HA. E.g.: Considering the route of SQL DB Mirroring, and would like to know possible solutions for CI to be able to reconnect to the secondary DB Host in case of Hardware Failover of Primary DB Host.
Please point me to the right documentation repository for possible Win/SQL HA Scenarios. The standard Install Guide did not provide the details that we are looking for.
Any hits and directions are very much appreciated. VMware Solutions ?
Thanks,
Uday

Hi Uday,
Yes, there's SAP support for SQL DB mirroring. You can check the note 965908 - SQL Server Database Mirroring and SAP Applications
Additionally, read the statement in the note 106275 - Availability of SAP components on MS Cluster Service
Alternative cluster solutions
Alternatively, other forms of clustering/high
availability are also possible but installation and support
must be provided by the SAP HA solution or implementation partner.
SAP only supports the standard configurations detailed above on Windows and
reserves the right to require that other high-availability solutions be deactivated
when support is required
Best regards,
Orkun Gedik

Replication solution for MSCS Failover Cluster?

Similar Messages

Maybe you are looking for