SIOS SANless clusters

SIOS SANless clusters High-availability Machine Learning monitoring

  • Home
  • Products
    • SIOS DataKeeper for Windows
    • SIOS Protection Suite for Linux
  • News and Events
  • Clustering Simplified
  • Success Stories
  • Contact Us
  • English
  • 中文 (中国)
  • 中文 (台灣)
  • 한국어
  • Bahasa Indonesia
  • ไทย

How To Build A Highly Available Server Solution?

March 16, 2021 by Jason Aw Leave a Comment

How To Build A Highly Available Server Solution?

How To Build A Highly Available Server Solution?

A key component to any high availability solution is figuring out how to redirect the client traffic. Almost every user-based application needs to connect to the server. Redirecting the client traffic will allow users to connect without having to know where the application or the database actually resides.

Most solutions recommend network-based IP redirection or network based DNS redirection. This works. However, the best solution for a high availability server in our experience is the use of a virtual IP address that can be switched from one server to another. The server is listening to connections from the virtual IP address, where it’s hosted on one server today and switched to another on another day.

To take it one step further, you can automate the failover. This is where the system makes decisions and switches the application when there is a failure detected. Bear in mind this step is key to building a highly available solution.

Benefits of Buy vs. Build High Availability Solution

This can be implemented using scripts and logic to check the status of processes and virtual IP addresses from one server to another. But one of the challenges we face in a buy vs build high availability solution is how much time we really have to spend in build. This includes time for script coding, API development such as cloudwatch API or lambda functions. Let’s not forget testing, and maintenance.

When I was younger, I was eager to write that code. But after  working for large Fortune 100 companies, and getting yelled at by a high level manager, when one of my scripts didn’t work at 3 am in the morning, I feel differently. This issue was exacerbated when I discovered an issue for a code I wrote a year ago. My managers wanted the highly available solution to work 100%. If it didn’t work, time to call up someone and yell at them.

SIOS Automates High Availability

Isn’t it cheaper in the long run to buy the solution and spend a little time to tweak it to fit into our setting? This is where SIOS high availability (HA) solutions come in, whatever the application or database. SIOS has the code to switch the stack of the processes from one server to another. This gives users and managers the peace of mind that comes from automating the failover orchestration and high availability.

There are two things that I love about the SIOS HA umbrella are. One, the code for the virtual IP where the IP address is added to the server and the application is restarted to listen to the connections. The second is enabled through the use of the application agnostic API set that SIOS provides. This allows anyone to protect any application by the use of plugins. Contact SIOS today to learn more about high availability solutions specific to your environment.

– Edmond Melkomian, PMP, MCSD, consultant, SIOS technology, Inc.

Reproduced from SIOS

Filed Under: Clustering Simplified Tagged With: Application availability, failover clustering, High Availability

Webinar: Failover Clustering in the Cloud – Understanding Your Options

May 24, 2019 by Jason Aw Leave a Comment

Failover Clustering in the Cloud – Understanding Your Options

Webinar: Failover Clustering in the Cloud – Understanding Your Options

Windows Server 2016 introduced Storage Spaces Direct, to allow for shared storage in Azure that could help with building and configuring a Windows cluster in the cloud. While this sounded like a killer feature (and it can be with proper infrastructure) it runs into challenges in cloud environments with limited bandwidth available for both storage and data traffic.

In this webinar, you will learn about the configuration of clusters in the cloud, some real-world examples of problems, and alternatives for maintaining a shared storage infrastructure within Azure.

Register Webinar: Failover Clustering in the Cloud – Understanding Your Options

Filed Under: News and Events Tagged With: Azure, Clustering, failover clustering, SQL Server

Data Protection and Failover Clustering During Migration To Cloud

May 29, 2018 by Jason Aw Leave a Comment

Data Protection and Failover Clustering During Migration To Cloud

Migrate Existing System Running SQL Server And WSFC Configuration To Cloud With SIOS For Data Protection and Failover Clustering

Gulliver is pursuing to migrate their existing on-premises systems to cloud.  For this project, they picked SIOS Data keeper to ensure real-time replication, data protection and failover clustering.

The company aimed to build an IT infrastructure capable of responding swiftly and flexibly to the growth of these businesses. Protection of important data is essential as they shift to the cloud.

The system owned by Gulliver included the used car sale system “Dolphinet”. Most parts of this system has been built and operated on physical servers in their data center. Therefore, reform is definitely in their pipeline to achieve the expansion goal of 1,600 global stores.

Full Transition From On-Premise To Cloud

IT Team Tsukishima School said that for Gulliver, IT is the core of the business. Thus, having a strong and secure IT foundation would allow the company respond to rapid business expansion. Since 2011, the company has been contemplating a full-scale system migration to the AWS cloud service. Their entire operation can be controlled in the cloud which is easy and fast.

Challenges Faced in Migrating to the Cloud

Many of Gulliver’s systems are constructed with Microsoft products such as Windows Server, SQL Server of relational database, IIS (Internet Information Services) of Web server, .NET Framework of application development and execution environment.

The first challenge in transitioning to the cloud is the question of how to implement these platforms in AWS.

“We initially considered utilizing the SQL Server function supported by RDS (Relational Database Service), but we are also trying to use redundant (clustering) important systems and user management (Active Directory link) We did not have all the necessary functions yet. So, we considered other methods but the risks were too many many and too huge to undertake.”

Redundancy Plan To Ensure High Availability

So Gulliver chose to use the virtual server’s Amazon Elastic Compute Cloud (Amazon EC 2) natively. The existing environment including the failover clustering (WSFC) function of Windows Server running on-premises is used directly. Therefore, DataKeeper played an important role in synchronizing the data of the existing environment as it is.

Achieve Real-Time Data Protection Without Using Shared Storage

DataKeeper performs data replication in real time between the production node and the standby node and protects data until just before the failure occurs. Compared to the general storage mirroring function, volume mirroring is realized at low cost. It can be utilized according to various needs such as the system configuration and the importance of data and the necessity of measures against disaster recovery (DR).

Simple HA Cluster Without Using Shared Storage On AWS

It is advantageous to be able to have HA cluster system (application protection configuration) without using external shared storage premised on failover clustering like WSFC. This is the point where Gulliver chose to adopt DataKeeper for Data Protection and Failover Clustering.

Gulliver’s Tsukishima said, “I was surprised that DataKeeper looks as if it is sharing storage from WSFC. The speed of mirroring is good. When an abnormality happens in HA cluster operation, I am extremely satisfied that it is easy to isolate and deal with. Whether it is on the clustering (WSFC) side or the data replication (DataKeeper) side, it becomes a quick and fuss free process. This point applies even when we are configuring the physical server. It became possible to shift to AWS without changing the operation form of the existing system at all. ”

Gulliver intends to move on to the rest of the existing system by 2014. At the same time, it is implementing the newly developed system in AWS.

To find out more about SIOS products, go here
To read about how SIOS helped Gulliver achieve data protection and failover clustering in their cloud migration go here

Filed Under: Success Stories Tagged With: Cloud, data protection, data protection and failover clustering, failover clustering, Windows Server Failover Clustering

Learn Windows Server 2012 R2 Failover Clustering

March 12, 2018 by Jason Aw Leave a Comment

Learn Windows Server 2012 R2 Failover Clustering – Microsoft Virtual Academy

For those who have never been exposed to clustering or just new to clustering in Windows Server 2012 R2, this is the class for you. Symon Perriman (@SymonPerriman), 5nine Software Vice President of Business Development and Elden Christensen, Microsoft Principal Program Manager Lead, live and breathe failover clustering. With such great knowledgeable instructors, this two men would definitely be able to give you some great ideas on your next project or simply give you an alternative view. You can’t ask for any better instructors. Stop what you are doing and watch this RIGHT NOW!

http://www.microsoftvirtualacademy.com/training-courses/failover-clustering-in-windows-server-2012-r2

Reproduced with permission from https://clusteringformeremortals.com/2015/02/12/learn-windows-server-2012-r2-failover-clustering-microsoft-virtual-academy/

Filed Under: Clustering Simplified Tagged With: Clustering, failover clustering, Microsoft Virtual Academy, Windows Server 2012

Overcoming Performance Issues With SQL Server Alwayson Availability Groups

February 5, 2018 by Jason Aw Leave a Comment

Asynchronous vs synchronous replication on AlwaysOn

From attending the sessions at PASS Summit this week, it has become obvious that AlwaysOn is a hot topic with about six sessions dedicated to this solution . The one thing that I learned is that although the solution certainly has its applications, most of the successful deployments are based on using AlwaysOn in an asynchronous fashion. The reason people avoid the synchronous replication option is that the overhead is too great. During synchronous replication any write must be committed on the replica before it is committed on the source. In the testing that I have done, this overhead introduced can be as much as 68%.

For example, in a test where I have a database inserting about 1,000,000 rows per second and we measure the throughput on the log file, we see that with no mirroring in place we are writing about 400 MBps. Once we start replicating that database with AlwaysOn Availability Groups across a 10 Gbps LAN, we see about a 68% drop off in performance, with this particular database slowing down to about 250,000 inserts per second.

Asynchronous vs synchronous replication on AlwaysOn
Figure 1 – MBps written to a SQL Server database before and after AlwaysOn Synchronous Mirroring

If you are considering the solution as a replacement to your failover cluster, this drop off should be of a major concern to you. In order to achieve the automatic failover that you are accustomed to in failover clustering, you must use synchronous mirroring, which means that you must live with this performance hit. Generally this is not going to be acceptable, which is probably why you don’t hear the experts recommending such configurations on a regular basis.

So what should you do?

Should you stick with you traditional failover cluster and a SAN? What if you want to take advantage of fast, high speed storage such as Fusion-io? In that case, you can’t use a traditional cluster…or can you?

The good news is that you can build a cluster without a SAN and do it all without the expense, limitations and overhead associate with AlwaysOn Availability Groups (more on the limitations and expense in my next blog post). By using DataKeeper Cluster Edition you can build clusters without shared storage AND the overhead associated with Synchronous replication is closer to 10% vs. the close to 70% we see with AlwaysOn Availability Groups.

Come to booth 351 at #SQLPASS and I’ll be glad to demonstrate how the solution works.

Reproduced with permission from https://clusteringformeremortals.com/2012/11/09/how-to-overcome-the-performance-problems-with-sql-server-alwayson-availability-groups-sqlpass/

Filed Under: Clustering Simplified Tagged With: alwayson, Asynchronous, failover clustering, SIOS DataKeeper Cluster Edition, SQL Server, Synchronous

  • « Previous Page
  • 1
  • 2
  • 3
  • 4
  • Next Page »

Recent Posts

  • Transitioning from VMware to Nutanix
  • Are my servers disposable? How High Availability software fits in cloud best practices
  • Data Recovery Strategies for a Disaster-Prone World
  • DataKeeper and Baseball: A Strategic Take on Disaster Recovery
  • Budgeting for SQL Server Downtime Risk

Most Popular Posts

Maximise replication performance for Linux Clustering with Fusion-io
Failover Clustering with VMware High Availability
create A 2-Node MySQL Cluster Without Shared Storage
create A 2-Node MySQL Cluster Without Shared Storage
SAP for High Availability Solutions For Linux
Bandwidth To Support Real-Time Replication
The Availability Equation – High Availability Solutions.jpg
Choosing Platforms To Replicate Data - Host-Based Or Storage-Based?
Guide To Connect To An iSCSI Target Using Open-iSCSI Initiator Software
Best Practices to Eliminate SPoF In Cluster Architecture
Step-By-Step How To Configure A Linux Failover Cluster In Microsoft Azure IaaS Without Shared Storage azure sanless
Take Action Before SQL Server 20082008 R2 Support Expires
How To Cluster MaxDB On Windows In The Cloud

Join Our Mailing List

Copyright © 2025 · Enterprise Pro Theme on Genesis Framework · WordPress · Log in