• Solutions
  • By Industry
    • Distribution
    • Security
    • Gaming
    • Government
    • Healthcare
    • Manufacturing
    • Media & Entertainment
    • Travel, Transportation & Logistics
  • By IT Need
    • Proactively Prevent Downtime
    • Protect Data for Compliance
    • Achieve Disaster Resilience
    • Reduce CAPEX & OPEX
    • Provide HA in Remote Locations
  • Small & Medium Business Solutions
  • Windows Business Application Availability
    • BlackBerry HA
    • Exchange HA
    • SharePoint HA
    • SQL HA
    • XenApp HA
    • BlackBerry DR
    • Exchange DR
    • SharePoint DR
    • SQL DR
    • Virtual Server DR
• Products
  • Overview
  • everRun MX
  • everRun MX Express
  • everRun MX Extend FT+DR
  • everRun SplitSite
  • everRun HA & FT
  • everRun Advantage
  • Product FAQs
• Services
  • everRun Services Overview
  • Consulting Services
  • Training Services
    • Authorized Training Centers
  • Assurance Program
  • Customer Portal
  • Requesting Technical Support
  • Technical Community Login
  • everRun Assist Web Support
• Partners
  • Partners Overview
  • Citrix Alliance
  • Microsoft Alliance
  • ISV Partners
  • Why Resell Marathon
  • Partner Program FAQs
  • Find A Reseller
  • Partner Login
• Resources
  • Resource Center
  • White Papers
  • Webinar Recordings
  • ROI Calculator
  • Collateral
  • Flash Demos
  • Glossary
    • Symmetric Multi-Processing
    • Continuous Application Availability
    • Application Availability
    • Disaster Recovery
    • Failover
    • Fault Tolerance
    • High Availability
    • High Availability Cluster
    • Server Redundancy
  • Customer Endorsements
  • Success Stories
  • Product Reviews
  • Analyst Opinions
  • Exporting everRun Products
• News & Events
  • Latest News
  • Press Releases
  • In The News
  • Events & Webinars
• About Us
  • Overview
  • Announcement
  • Why Marathon
  • Executive Team
  • Board of Directors
  • Awards
  • Careers
    • Current Openings
    • Benefits
  • Corporate Offices
  • Contact Us

Blog

Disaster tolerance (DT) is a proactive way to prevent system failure from impacting application and data availability. A disaster tolerant solution isn’t going to recover the data if there’s a disaster. Instead it will tolerate the fault if a disaster occurs – keeping an organization’s critical applications up and running at all times. It is not recovery, but rather prevention.

Software technology that makes it possible for multiple systems to be provisioned and managed as if they were a single computing resource. (See the original article by Dan Kusnetzky here)

Hardware and software technology that presents a view of the network that differs from the physical view. So, a personal computer may be allowed to only see systems it is allowed to access. Another common use is making multiple network links appear to be a single link. (See the original article by Dan Kusnetzky here)

Hardware and software technology that hides where storage systems are and what type of device is actually storing applications and data. This technology also makes it possible for many systems to share the same storage devices without knowing that others are also accessing them. This technology also makes it possible to take a snapshot of a live system so that it can be backed up without hindering online or transactional applications. (See the original article by Dan Kusnetzky here)

Hardware and software technology that hides physical hardware configuration from system services, operating systems or applications. This type of Virtualization technology can make one system appear to be many or many systems appear to be a single computing resource to achieve goals ranging from raw performance, high levels of scalability, reliability/availability, agility or consolidation of multiple environments onto a single system. (See the original article by Dan Kusnetzky here)

Hardware and software technology that allows nearly any device to access any application without either having to know too much about the other. The application sees a device it's used to working with. The device sees an application it knows how to display. In some cases, special purpose hardware is used on each side of the network connection to increase performance, allow many users to share a single client system or allow a single individual to see multiple displays. (See the original article by Dan Kusnetzky here)

A few months back we acknowledged here on our blog the common misconceptions behind the term “virtualization.” After thinking about it some more, we realized that there are many commonly used terms in the High Availability, Clustering and Disaster Recovery space that could also benefit from some clarification. To alleviate some of the confusion and help standardize the language around Availability, we’ve created a glossary of terms to be housed on our blog (click the Glossary tab). Here, we’ll provide our take on common phrases that will help IT Managers make educated decisions when considering an Availability, Virtualization or Disaster Recovery solution. We encourage you to help us cultivate the glossary by commenting on our definitions, or provide us with your own. The terms identified are just a jumping-off point, so please feel free to suggest other terms you would like to see defined.

The goal of this is to give IT Professionals from CIO’s to IT Managers a place to find clear and consistent definitions, rather than being bamboozled by the disparate “lingo” being thrown around within the industry.

Virtualization.info blogger Alessandro Perilli, describes the importance of high availability here stating:

“In case downtimes are not affordable at all we have to approach high availability configurations, where cluster nodes share and balance traffic load, or less expensive hot-standby configurations, where one or more secondary node are ready to take over if the primary has a failure.”

To better understand the concept of HA, and see how HA software works, visit this link and watch a video demo of high availability, or what we like to call infinite availability in action.

Fault-tolerant architecture allows a system to continue working even when part of the system fails. Fault-tolerant servers provide continuous availability through hardware failures by utilizing and operating redundant components. Mark McCarthy posted this definition on Tech Target, which we feel is a great simplified definition. He states:

“Fault-tolerant describes a computer system or component designed so that, in the event that a component fails, a backup component or procedure can immediately take its place with no loss of service.”

Disaster recovery is a plan which enables the protection and restoration of critical information in the event of disruption. Disaster recovery management includes functions such as identifying the critical and vital information, determining recovery needs, developing backup solutions and implementing the backup/recovery solution.

This is the term that has caused the most confusion within the market, yet provides the lowest level of availability and requires a fairly heavy implementation process. Data replication can be more accurately described as a data storage and backup strategy that involves moving data from one server to another server using an asynchronous model to allow for unlimited distances between servers.

Continuous availability virtually guarantees a computing system is operational in the event of any disruption. The concerns for continuous availability focus on two things, the recovery of applications, data and data transactions prior to the moment of disruption, and 24x7 system availability regardless of the planned or unplanned downtime event.

Diana Huggins, a blogger for IT Professionals, describes clustering as:

“a technology that lets you increase the availability of a server, service or application so it does not become a single point of failure.”

This description is completely true. We find a simplified definition makes understanding clustering more comprehensible. Clustering strategies are typically used for scaling out performance, load balancing, and recovery. The way we see it, clustering is connecting at least two servers together with one acting as a standby for protection. Clustering solutions are rules based and require custom coding and scripting that define the failover and recovery policy and procedures unique to their environment.

Everyone is talking about it as if everyone can provide it, one way or another. Once you dig just slightly below the surface it becomes apparent that there are nearly as many definitions for availability as there are vendors touting it. Some consider availability of the data, while others availability of the server or storage subsystem.

At its core availability is defined as “present and ready for use; at hand; accessible”. The level of availability depends on an organization’s service level. Once the business needs for availability are understood, appropriate solutions can be researched and identified. Check out this white paper to “Breaking Through the Noise of Application Availability.”