Operations Orchestration Stands Up to the Most Demanding Use Cases—Disaster Recovery Is One of Them

by in IT Operations Management

Recover right, recover fast—with Micro Focus Operations Orchestration.

Almost every company is now a digital company, and no business is immune to the threat of IT downtime. Business continuity and operational risks are increasing due to cyberattack threats, natural disasters, business complexity of organizations, reliance on third parties, and frequency and risk of pandemics, according to a recent Forester/DR survey.

When disaster happens, lost employee, partner, and customer confidence is difficult to rebuild. That’s why having a resilient plan for business continuity and disaster recovery is critical. Should a disaster strike, your data and services must be accessible.

Are Your People and Processes Ready?

Many organizations are not prepared to recover rapidly from disruptive IT events. One key reason is that disaster recovery plans are built around time-consuming, error-prone manual tasks. Given the resource-intensive nature of disaster recovery procedures, companies can only run tests sporadically. A lack of formal central disaster recovery programs—without which central IT has limited or zero visibility of siloed systems—also curbs recovery robustness.

Automation and Process Orchestration—Where Disaster Recovery Preparedness Starts

A reliable disaster recovery plan relies on IT process automation and orchestrated workflows for recovery. Orchestration—the automated coordination of IT processes across teams, tools, and technologies—strings together disparate processes and standardizes IT processes across enterprise silos.

With orchestration of automated workflows, disaster recovery testing no longer places heavy demands on subject matter experts. Teams can test their disaster recovery plans regularly and always after any significant IT changes.

An Example of a Disaster Recovery Use Case—Recovery of an Email System

Let’s look at an orchestration workflow for recovering an email system.

In this scenario, an orchestration workflow starts the recovery process when a change ticket—declaring a disaster recovery event for an email system—is approved. Advanced orchestration steps include conducting network and destination system health checks, cloning destination servers, performing failover tasks, updating the configuration management database, re-enabling clustering and monitoring, and updating the service desk change request ticket. Server administrators are notified at various stages during the recovery process.

Be Prepared with Micro Focus Operations Orchestration

Micro Focus Operations Orchestration (OO) is an enterprise-scale orchestrator that automates and integrates across heterogeneous systems—from physical and virtual servers to network and storage devices, on premises or in the cloud. With OO, you can orchestrate almost any process and integrate with almost anything—from simple automation to complex end-to-end integrations.

Here’s how OO stands up to the most demanding use cases with these disaster-ready features:

  1. Low-code/no-code design interface—Easily build and debug recovery workflows in an intuitive visual interface—no programming required.
  2. Out-of-the-box content—Plug-and-play ready-made content into virtualization, cloud, database, and middleware recovery workflows.
  3. Superior control of automation steps—Define and control all steps in your recovery workflows with decision-making, parallel-processing, and error-handling logic.
  4. Highly parallelized runs—Run workflows in parallel—up to 100 flows per second—to accelerate recovery.
  5. Access to secure zones—Securely access devices in remote third-party sites with OO’s Remote Action Server (RAS) topology.
  6. UI automation powered by RPA robots—Keep your processes flowing with RPA robots when your recovery procedures require human intervention and your staff are unavailable.
  7. Rest APIs—Invoke your recovery workflows from almost anywhere—including monitoring tools, service catalogs, cloud portals, command line interfaces, and websites.
  8. Self-service portal—Trigger recovery workflows from a friendly user portal, whenever and wherever you need to.

Get Started by Creating a Robust Disaster Recovery Plan

Proactive planning is the key to successful disaster readiness. Your goal is to standardize, automate, and test for fast, error-free recovery.

To get started, prioritize your services. What do you recover first? Think about your services in layers—starting with services that matter most to your customers. Identify the infrastructure components and applications that must be recovered first, second, and third to restore those critical services.

If you’ve got public cloud in your infrastructure mix, make sure your disaster recovery plan includes cloud services hosted by your third-party cloud service provider (CSP).  Most CSPs use a shared responsibility model where security tasks are shared between you and the provider. Responsibility varies by service type, but almost always, you’re responsible for your data.

And remember—you’re not ready if you’re not testing. Testing your disaster recovery plan is the best way to make sure you’re prepared.

To learn more about disaster recovery with OO, download our latest Business Continuity and Disaster Recovery e-book.  This e-book highlights disaster recovery use cases, customer stories, and best practices for creating a robust disaster recovery plan.  


Have technical questions about Operations Orchestration? Visit the Operations Orchestration User Discussion Forum

Do you have an idea or product enhancement request for OO? Submit it in the Idea Exchange.  

We’d love to hear your thoughts on this blog. Comment below.


Operations Orchestration