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 Improve Customer Satisfaction in Technical Support

March 18, 2026 by Jason Aw Leave a Comment

How To Improve Customer Satisfaction in Technical Support

We have customers all over the world.  We speak different languages; we are in different time zones;  we are in different countries.  But there are many things that we have in common when it comes to technical support.  We all want and expect the best support when we have problems and need help.    What does wanting and expecting the best support actually mean for an IT team?

6 Customer Expectations for a Technical Support Team

Here’s what our customers tell us they expect from a Technical Support Team.

Listen to the Customer

Customers (just like everyone else) like to be listened to.  When talking to a customer, it is important to let the customer describe the problem.  As a Support engineer, take notes, listen to what the customer is describing, and ask follow-up questions to gather important information.  Do not interrupt the customer while they are talking.  To confirm you understand what the customer stated, summarize what the customer told you.   Summarize actions and make sure everyone is on the same page. Don’t assume you know the problem before the customer has described it.

Talk to a Real Person

Customers still prefer to talk to a “real” person and not an automated voice / AI/ ChatBot.   Customers like talking to a support agent right away who knows the product and not just following a script. Nothing is more frustrating than when you call to get help with a problem you are experiencing, and you have to go through multiple automations to try to get to a “real” person. Many times you end up going in circles and arrive back to the scenario in which you started!  Valuable time can be quickly wasted trying to get a “real” person on the phone to help you.   Customers calling in for help strongly prefer setting up a video conference to share the problem live with a support team.  A picture is worth 1000 words!  In our experience, trying to help customers without a visual and without asking “live” questions adds to the length of time to solve a problem.

Availability 24 x 7

Customers are all around the world and want to contact support at any time of the day or night.  We offer around-the-clock support every day of the week.  To accommodate this, we have multiple teams around the world that cover 24 hours a day, every day of the week.  When customers need us, we are there for them.  We have procedures in place to escalate cases when our team members need immediate assistance on critical downtime issues affecting the customer’s business. Our customers use our High Availability and Disaster Recovery software,  and our Technical Support team reinforces this goal by being ready to provide assistance whenever we are needed.

Experienced Support Engineers

Customers don’t have time to get on the phone with a person who can’t help them and needs to pass the call to someone else.  Customers want to talk to support engineers who can assist with their questions and problems. At SIOS, we make a point to ensure that customers are quickly put in contact with an experienced member of our technical support team so the issue can be addressed as soon as possible. Based upon our Customer Surveys, customers love our technical support team! Our support team has an average of 16 years of total support experience; this expertise allows issues to be addressed quickly and often without having to escalate cases to another group. Customers appreciate it when they are met with experienced personnel who can join a video conference and provide real-time assistance based on years of experience.

Be transparent

Customers appreciate transparency.  They want to know reality.   Don’t make promises that you cannot keep.  Always ensure that the customer understands what you are going to do to help them solve the problem and when you will be getting back in touch with them.  Explain the steps that need to be done to the customer as you go, and ensure that the steps are approved by the customer before you execute them.   Many customers need to get pre-approval prior to implementing changes to their systems.  In pursuit of transparency, it is important to give the customer frequent updates that give insight into the support process.  Even if your update is, “We are still analyzing the logs”, tell the customer this to keep them updated.   Don’t tell them what you think they want to hear; tell them the truth.

Customer Surveys

For every case customers open with technical support, a survey is sent to the customer when the case is closed.  This gives the customer an opportunity to provide feedback so our teams can continuously improve our products, documentation, and support. Our support team looks at completed customer surveys at least once a week and responds to customers who have concerns, ideas, and improvement suggestions, letting them know what actions we took on their feedback.   Customers often thank us for resolving their issues quickly and for demonstrating our commitment to their success by following through on the notes they leave us after the case is closed.

What Customers Expect from a 24/7 HA/DR Technical Support Team

Customers reaching out for technical support on HA/DR products want to know they are being heard by a real person, not a bot. They expect to talk to experienced agents who actually know how to fix their problems and who stay transparent about what’s happening every step of the way. By offering this human touch with 24/7 availability, we show our customers that we are always there when they need us. Today’s technical support isn’t just about solving a ticket; it’s about building trust, listening, and being reliable and honest whenever customers need assistance.

Looking for a technical support team that understands HA/DR? Schedule time with a SIOS HA expert to see how we deliver high availability, automated recovery, and reliable cluster deployments.

Author: Sandi Hamilton, Director of Product Support Engineering at SIOS

Reproduced with permission from SIOS

Filed Under: News and Events Tagged With: disaster recovery, High Availability

Designing High Availability Through Modularity and Abstraction

March 6, 2026 by Jason Aw Leave a Comment

The Critical Role of QA and Production Environments in High Availability

Designing High Availability Through Modularity and Abstraction

Thus far, this series has explored parallels between technical design and rhetoric. The “rhetoric” of a technical solution, the strategy of communicating meaning and purpose, is presented via the design patterns and concepts. The design patterns and concepts exist as a conceptual foundation, upon which the meaning is translated into an applied form when put into practice during implementation.

As previously discussed, the continuity and integrity of this conceptual foundation are paramount to ensuring that solutions are kept up to a standard that is conducive to maintenance, improvement, and long-term reliability. External factors influencing a solution’s design challenge the goal of upholding the conceptual foundations put forth in a solution’s design. These external factors can conflict with the standing principles, and thus, tools, applications, and platforms used in a solution must be chosen mindfully.

In the third and final part of this blog series, modularity and abstraction will be explored as a means to put boundaries in place and ensure that projects with a wide scope can continue to reap the benefits of a well-formed, rhetorically sound design.

High Availability Design Principles: Why Modularity and Abstraction Matter

Before addressing modularization and abstraction as strategies, it is important to understand why these should be implemented. Starting broadly with an analogy, a speaker trying to convince their audience to agree with their plan might first need to outline multiple foundational points. In doing so, each pillar of their argument’s foundation gets put forth and justified.

The speaker first must set up the “A implies B” and “C implies D” basis, upon which they can form the argument “B and D imply E”. This strategy ensures that the reasoning in which “A implies B” does not cross-contaminate and detract from the separate point “C implies D”. This strategy is frequently used because it allows each component of the speaker’s argument to stand independently of others. If the argument “C implies D” is flawed, it can be reconciled while the argument “A implies B” remains sound.

The reason for this structure is the same reason why technical systems are decentralized – a problem in a point of sale system can be remediated without the need to expand the remediation efforts to the databases, APIs, network architecture, and so on. The strategies referenced above are, of course, in reference to the concepts of modularity and abstraction.

Modularity in High Availability Architectures

First, addressing modularity, this is the practice of creating systems from components that are self-contained. In the rhetorical sense, the arguments “A implies B” and “C implies D” are simply modules of reasoning that get assembled into the argument as a whole.

More technically, modularized components (such as the point of sale system in the previous example) allow issues to be addressed entirely within the module where the issue originates.  Each module in the solution acts as a building block, and a problem in a single building block can be resolved without dismantling the entire solution.

Abstraction as a Strategy for Scalable Infrastructure Design

Closely related to modularity is “abstraction”. Abstraction is the practice of ensuring the design of the overall solution is independent and agnostic to the design of the modules that compose the overall solution.

Further, abstraction as a design strategy also holds that each module is independent and agnostic to the design of every other module. When a solution is designed to use abstracted elements, these elements can be reused and applied in use cases that allow for understanding to be amplified throughout the project.

Designing High Availability That “Stays Out of the Way”

When designs are built of modular components, boundaries are drawn. These boundaries ensure that each module can “Stay out of the way” of the other modules. When the components are abstracted, the contents of each module can be understood more easily.

In turn, the boundaries serve as a structure by which the design can be understood, and the abstraction within these boundaries serves as an entry point to understand the foundations of the use case. The structure provided via modularity and abstraction mirrors the role of rhetoric in providing a framework by which purpose is understood.

Managing Complex Network Architectures with Modular HA Solutions

As technical solutions are being developed to address more complex problems, the need for a solid framework in that solution’s design grows as well. Network architecture, often the culmination of many solutions that are complex in their own right, serves as a fantastic example of the increasingly complex problem and growing requirement for solid frameworks in design. Furthermore, network architecture often suffers from continual growth as it has to absorb the sprawling web of systems that contribute to the purpose of a growing business.

Layered on top of this, the solution architecture must then employ solutions for High Availability and/or Disaster Recovery. This creates a hot spot for design conflicts to arise, but can be easily mitigated with the strategies of modularization and abstraction.

Applying Modularity and Abstraction with SIOS High Availability Software

The benefits of High Availability software can be achieved without the baggage of complexity and hacked solutions. SIOS LifeKeeper, as an example of a design-compliant High Availability tool, is created in a way that the principles of its operation can mesh seamlessly with the environment in which it is used.

LifeKeeper is modular, as it does not impose requirements outside of the LifeKeeper-protected systems. LifeKeeper also facilitates the abstraction of infrastructure components to bite-sized elements – systems that work together to ensure availability are grouped into a “cluster”.

Through this abstraction, the rhetoric of the environment remains strong – understanding the makeup of one cluster lays the foundation to understand all clusters. Layers of the design can be understood for their purpose; there is no need for asterisks and special considerations on how implementations differ across the design. As the clusters act independently of other clusters or external solution components, a boundary can be drawn where the design elements of each respective layer are contained, avoiding conflict with other layers of the infrastructure.

Building Long-Term Resilient Infrastructure with SIOS Protection Suite

As with any software or tool, SIOS Protection Suite (SIOS LifeKeeper and/or SIOS DataKeeper) influences the design of environments in which they are used. Though these patterns are brought in by virtue of having a LifeKeeper and DataKeeper protected environment, SIOS LifeKeeper and SIOS DataKeeper carefully selected the patterns in use to ensure that these patterns enable abstraction and modularity within the solution as a whole. As a result of the layered abstraction enabled by both LifeKeeper and DataKeeper, the introduction of these utilities facilitates integration with the IT infrastructure that maintains cohesion in the solution’s design.

As a result of the design patterns employed, clusters protected by SIOS Protection Suite (LifeKeeper and/or DataKeeper) compose an abstract and modular element that fits seamlessly into existing designs and solutions. LifeKeeper and DataKeeper do more than simplify the administration of single systems or each respective cluster; LifeKeeper and DataKeeper work with the principles at play in a deployment.

Creating infrastructure becomes simplified and more efficient as the use of SIOS Protection Suite allows for a simple method of understanding the system’s role in the design, while at the same time providing a simple method for implementing High Availability and Disaster Recovery. Administrators may use LifeKeeper and DataKeeper as a tool to improve their ability to understand, operate, and improve upon the solution for years to come.

See how high availability can support your infrastructure’s design—without adding complexity. Request a demo today!

Author: Philip Merry, CX Software Engineer at SIOS

Reproduced with permission from SIOS

Filed Under: Clustering Simplified Tagged With: disaster recovery, High Availability

Common Customer Misconceptions

February 11, 2026 by Jason Aw Leave a Comment

Common Customer Misconceptions

Common Customer Misconceptions

High availability (HA) and disaster recovery (DR) are often misunderstood.

Listen to the full conversation in this podcast as Greg Tucker unravels common customer misconceptions about HA/DR—from overestimating what cloud providers guarantee to misjudging the complexity of solutions like SQL Server Always On Availability Groups. Greg shares real examples of avoidable mistakes, explains how SIOS helps customers rethink their HA/DR assumptions, and offers practical advice for IT leaders looking to make informed, resilient infrastructure decisions.

Reproduced with permission from SIOS

Filed Under: Clustering Simplified Tagged With: disaster recovery, High Availability

Ensuring IT Resilience and Service Continuity in State and Local Government

January 20, 2026 by Jason Aw Leave a Comment

Ensuring IT Resilience and Service Continuity in State and Local Government

White Paper: Ensuring IT Resilience and Service Continuity in State and Local Government

Local government operations rely on always-available IT systems — from court and tax databases to 911 dispatch and school platforms. When these systems go down, the impact is immediate and far-reaching, affecting public safety, legal processes, payroll, and community trust. Many agencies struggle with aging infrastructure, tight budgets, and small IT teams managing complex hybrid environments.

SIOS helps solve these challenges with high availability (HA) and disaster recovery (DR) solutions that prevent downtime, protect critical data, and keep essential public services running, without requiring major infrastructure changes or deep HA expertise.

Reproduce with permission from SIOS

Filed Under: Clustering Simplified Tagged With: disaster recovery, High Availability and DR, SIOS Datakeeper, SIOS LifeKeeper for Linux, SIOS LifeKeeper for Windows, State & Local Government

SAP Disaster Recovery: Techniques and Best Practices

January 5, 2026 by Jason Aw Leave a Comment

SAP Disaster Recovery Techniques and Best Practices

SAP Disaster Recovery: Techniques and Best Practices

In this Enterprise Times article, Harry Aujla, partner alliance director at SIOS, examines why disaster recovery (DR) deserves as much strategic attention as high availability (HA) in protecting SAP environments and ensuring business continuity. He clarifies the differences between HA and DR, emphasizing that while HA aims to keep systems running during localized failures, DR focuses on restoring operations after major incidents such as cyberattacks or natural disasters.

The article outlines the business, financial, and regulatory risks of underinvesting in DR, then guides readers through two core recovery models, sitewide recovery and application-level recovery, highlighting the benefits, trade-offs, and cost considerations of each. Aujla concludes that there is no one-size-fits-all approach to SAP disaster recovery, urging organizations to align their strategy with business priorities, service-level requirements, and tolerance for downtime to build a resilient and practical recovery plan.

Reproduced with permission from SIOS

Filed Under: Clustering Simplified Tagged With: disaster recovery, High Availability, high availability - SAP

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

Recent Posts

  • Fail Open vs. Fail Closed: Why It’s a False Dilemma (and How True HA Fixes It)
  • The 5-Step Checklist for Validating Your Failover Setup
  • Managing an Inherited DataKeeper Cluster: Challenges and Best Practices
  • Setting Up Nginx Load Balancer on AWS
  • With Great Power: Cluster Maintenance Best Practices

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 © 2026 · Enterprise Pro Theme on Genesis Framework · WordPress · Log in