The State of Availability: New Business Demands

High Availability / Disaster Recovery
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Historically, many IT shops took data and application availability for granted, but what "taking it for granted" meant differed from one organization to the next. In some cases, a certain rationale was assumed: "Of course we have to protect the availability of our systems; if they're not available, our users can't do their work." In other cases, availability itself was assumed: "Hardware almost never fails, so there's no need to worry about availability." Neither attitude serves the business well.

The IT department might intuitively recognize the need for high availability, but in the quantitative, dollars-and-cents world of the CFO, "we need it because we need it," doesn't cut it. If that's your only justification for investing in higher availability, your systems will likely remain unprotected.

Depending on hardware reliability to ensure data and application availability is perilous because, yes, hardware is very reliable these days, but that only means that it rarely breaks down. It doesn't mean that a disaster or some lesser incident, such as a power failure or an operator error, won't force critical data and applications offline. Moreover, reliable hardware does nothing to stop the need for the frequent maintenance that often requires shutting systems down.

Thus, to fulfill the needs of the business, IT managers must justify, in hard-dollar terms, an investment in high availability and, after winning approval for it, take the necessary steps to combat the otherwise inevitable downtime. The case can be made by measuring the cost of each hour of downtime and the number of downtime hours that can be avoided. Multiplying those two values usually results in a number that is far higher than the cost of improving availability, thereby proving the potential for a large return on investment.

The good news—or bad news, depending on your perspective—is that, because of strong trends in the three areas of continuity, consolidation, and compliance, IT managers now find it much easier to justify high availability investments. In fact, many CFOs are now or soon will be beating down the doors of their IT departments to demand that IT managers take immediate action on the availability front.


Over the past half-decade, many screaming headlines have heralded stories of weather-related, tectonic, and terrorist catastrophes, putting disasters at the top of many people's minds. The threat to human life is, and should be, the paramount concern in these circumstances, but it's not the only concern. Today, most people's livelihoods and lives depend information technology to some extent. In the face of a disaster, at least one that can be predicted in advance, people can evacuate, but there is rarely time or logistic capacity to move computing hardware on such short notice.

Obviously, disasters are not the only causes of unexpected downtime. Hardware reliability numbers are now exceptionally high, often reported as at least three "nines" (i.e., 99.9% reliable), but that grossly understates the problem. Modern applications typically depend on a complex computing environment that encompasses a wide variety of components, possibly including many servers, data storage devices, routers, and other technologies, any of which may fail at any time. Thus, even if each component is 99.9% reliable, if a critical business application depends on 100 pieces of hardware, the infrastructure required to run that application is not 99.9% reliable, but rather 99.9% raised to the hundredth power, or a little under 90.48% reliable. That doesn't sound bad until you do the arithmetic. For a 24x7 operation, 90.48% reliable translates into about 834 hours of downtime annually. And that's just for "rare" hardware failures. It says nothing about software, network, or electricity grid reliability.

The impact of all of that downtime on a company's profitability can be staggering. Industry studies show that, depending on the industry and the size of the company, downtime costs can range up to almost $3 million per hour.

Planned maintenance is another obvious downtime source. Because you can schedule maintenance for slow times, the hourly downtime costs tend to be lower than for unplanned events, but because maintenance is significantly more frequent than hardware and software failures, disasters, and human errors, the annual cost of planned downtime is generally considerably higher. And, with more companies operating around-the-clock thanks to the Internet and globalization, those planned downtime hours are becoming more costly no matter when they're scheduled, thereby further raising the annual cost.

It's largely the disaster headlines that have driven many companies to look more closely at business continuity, often dedicating full-time resources to address the related issues, not just in IT, but also in the areas of personnel, business processes, logistics, and non-IT equipment. As these new continuity groups delve into their mandates, they often quickly come to recognize two IT-related facts: First, their businesses are so completely dependent on IT infrastructure that business continuity can be guaranteed only by assuring the availability of data and applications. And, second, to ensure data and application availability, it's necessary to look beyond disasters and address all potential causes of downtime.


Merger and acquisition activity ebbs and flows. Anecdotal and statistical evidence suggests that it is on the rise again. It may not be intuitively obvious, but business consolidation tends to heighten the demand for highly available information technology. On reflection, the reason is obvious: It costs little, if anything more to protect the availability of a server that is responsible for processing $1 billion worth of business than one that is responsible for $500 million.

To reduce hardware, software, and personnel costs, consolidated businesses typically merge at least some of the information technology of the previously separate firms. When they do, each server becomes responsible for managing a higher value of business. Thus, the justification for protecting the availability of those servers becomes correspondingly easier.

A different type of consolidation trend is occurring in some firms that are not merger and acquisition participants. When low-cost servers first hit the market, the thinking was that money could be saved by switching from mainframes and high-end midrange systems to cheaper commodity servers. But the economies proved to be false. Hardware costs often were lower, but the cost of software licenses for the larger number of servers and, much worse, the cost of installing, maintaining, securing, and backing up all of those distributed servers frequently swamped the hardware savings.

Consequently, many firms are reconsolidating those distributed servers onto centralized midrange systems, sometimes taking advantage of multi-operating system capabilities, such as on the iSeries, to run different platforms on a single server. The effect on the demand for high availability from this form of consolidation is similar to the effect from merger and acquisition activity: As each server becomes responsible for a higher percentage of the company's revenues, the importance of protecting its availability increases proportionately.


Continuity and consolidation trends have raised availability on businesses' priorities lists, but another dominant trend has made it a "must have" rather than just a "should have": an increasingly stringent regulatory environment. Compliance with new and strengthened regulations is now the focus of considerable corporate attention because failure to comply can bring substantial fines and, depending on the law broken, possibly also a jail sentence for the company's executives.

This article is not a detailed analysis of the relevant laws, nor is it written by a lawyer. You should, therefore, consult a legal expert when considering how regulations will affect your high availability requirements. In addition, the following primarily addresses the U.S. regulatory environment. Since most laws pertain to a single jurisdiction—typically, national, state/provincial, or local—if you're reading this from outside the U.S., further investigation of the relevant laws is advised.

Thanks in part to the accounting scandals of a few years ago and intensified concerns regarding security, businesses face a more stringent regulatory environment than in the past. Some of the new laws affect all businesses, some affect just public companies, while others are restricted to particular industries. A number of these regulations—including Sarbanes-Oxley (SOX), the Basel II accord, the Basel Committee's Capital Adequacy Directive (CAD III), the Gramm-Leach-Bliley Financial Services Modernization Act, and the Health Insurance Portability and Accountability Act (HIPAA), among others—require that organizations pay close attention to the integrity and availability of their data.

Sarbanes-Oxley (SOX)

SOX was passed primarily in response to major accounting scandals. Regulations enacted under the bill require that publicly traded companies report annually on the effectiveness of their financial controls. Accordingly, corporations now have a much tighter focus on ensuring that they have the proper controls and audit processes in place to prevent and detect fraud. The legislation has significant consequences for non-compliance, including civil and criminal penalties.

SOX's Section 404, which demands that members of management certify their responsibility for financial controls and report on the adequacy and shortcomings of the controls, and Section 409, which requires the timely reporting of financial information, are the sections of the act that are most relevant to data and application availability. To fulfill the requirements of these sections, highly accessible systems are required to exhibit best practices and to ensure the complete, accurate, and timely provision of information for financial reporting, audits, and fraud investigations.

Basel II Accord

The international banking regulations of the Basel II Accord apply to all European banks and investment firms, as well as about 20 of the most internationally important banks in America. To help achieve the objective of reducing the risk to banks' liquidity, Basel II specifically requires that banks protect the availability of their data. Furthermore, the Basel Committee's Capital Adequacy Directive (CAD III) requires that banks have information about their assets and associated risks readily available. Specifically, a background document produced by the Basel Committee states that "Banks should have effective capacity, business continuity and contingency planning processes to help ensure the availability of e-banking systems and services."


Eight agencies and the states are charged with managing and enforcing the regulations that stem from the Gramm-Leach-Bliley Financial Modernization Act of 1999, which applies to any organization that collects or transfers private financial information for the purpose of doing business or providing a service.

The regulation that is most relevant to the availability discourse is the Safeguards Rule, which governs processes and controls designed to protect customers' financial data. Among other requirements, it specifies that financial institutions must protect against any anticipated threats or hazards to the security or integrity of such information. Thus, financial institutions must protect against the destruction of customer and account data whether from equipment failure, disasters, or human error.

This rule, which is enforced by the Federal Trade Commission, threatens fines of thousands of dollars a day, not to mention public embarrassment, as a consequence of non-compliance.

Health Insurance Portability and Accountability Act (HIPAA)

HIPAA has a particular focus on health information privacy, but it also requires that participants in the healthcare sector protect the integrity and availability of any health information they collect, maintain, use, or transmit. The act defines the healthcare industry very broadly to include not just healthcare insurers and providers, but also healthcare information clearinghouses. These clearinghouses include practically all organizations that touch healthcare data in any way, including, for example, banks that process health claims, outsourcing firms that key in patient records or insurance policy data, and so on.

HIPAA precisely defines "availability" as "the property that data or information is accessible and useable upon demand by an authorized person." The inclusion of the phrase "upon demand" means that it is probably not sufficient to just back up data overnight and send it offsite. An organization that requires days to recover damaged data likely wouldn't be considered to have fulfilled the "upon demand" requirement.

Service Level Agreements

In many businesses, compliance means more than adhering to government-imposed regulations. In response to competitive pressures, many companies, particularly in the business-to-business market, voluntarily include Service Level Agreements (SLAs) in their sales contracts. These SLAs set legally binding benchmarks that vendors must meet.

There's no universal standard for the form of an SLA. For example, an application service provider (ASP) might include a clause that promises that its applications will be available to customers 99.9% of the time, around the clock. A hardware seller might promise that, in the event of a problem, replacement parts and/or a technician will arrive within a certain number of hours or days after the problem is reported. A supplier of raw material or components for a just-in-time manufacturer may guarantee deliveries within a certain timeframe after receiving an order. The number and variety of possible SLA clauses is limitless but, to be meaningful, they typically specify significant penalties that will be paid as compensation for lack of compliance.

In the ASP example cited above, the need for system availability in order to fulfill the SLA terms is obvious and direct. The need may be more obscure in other cases, but availability is required to meet many SLA terms. Most businesses are dependent on their information technology. For example, a company that creates a customized SLA for each customer, digitizes it once signed, and stores it only electronically may not even be aware of its specific SLA obligations if its systems are unavailable. Likewise, if the company needs to dispatch a technician or a spare part to a customer in order to fulfill an SLA agreement, that may be difficult or impossible to do without access to the systems that assign those resources. Consequently, as SLAs are included in an increasing number of contracts and as their terms grow stricter, SLA compliance will become a rising factor in organizations' demands for higher availability.

The Growing Availability Imperative

A discussion of how to achieve higher availability is beyond the scope of this article. It is, however, clear that if you have not yet begun to look at that question of how, you likely will have to soon. The ongoing trends in the "three C's" of the contemporary business and technology environment (continuity, consolidation and compliance) are conspiring to force availability higher on the business agenda and consequently on the IT agenda. If high availability is not an imperative in your organization today, it probably will be tomorrow.

Alan Arnold is President and COO of Vision Solutions. Prior to joining Vision in 2000, he was a senior technology executive and subject matter expert for IBM technology at Cap Gemini Ernst & Young U.S. LLC. Arnold is recognized as an expert in the field of managed availability technology. He has authored or co-authored five books on technology and business topics that have been published worldwide. He has also written numerous articles for some of the leading publications in the industry.



Support MC Press Online





  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things

    Read Node.js for Enterprise IBM i Modernization Now!


  • Profound Logic Solution Guide

    SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation.
    Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects.
    The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the companyare not aligned with the current IT environment.

    Get your copy of this important guide today!


  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.


  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline



  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Why Migrate When You Can Modernize?

    LANSABusiness users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.


  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact


  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using as a pre-built development environment



  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.



  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.



  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails


  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.



  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks



  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.