IBM Resiliency Orchestration

12th Mar 2018

Nguyen Ha Tuan – Marketplace Services Leader
Email: [email protected]
Mobile: +84 903 888 362
Content

1. Introduction of IBM Resiliency Orchestration

2. Next Steps

2
1. Introduction of IBM Resiliency Orchestration

3
DR for Enterprise Applications Environment - Challenges
• Complex, Multi-Vendor • 80% outages of mission critical services
• Vendor specific recovery steps caused by people & process issues
• Prone to human errors • Dependency on technology experts
• RPO/RTO measured for Systems & • DR change ‘creep’ cannot be readily
not Applications identified
• Myriad of tools for monitoring

Business User
Access
Discrete Monitoring

APPLICATION FAIL-OVER AND FALL-BACK

Directory
APPLICATION ECO-SYSTEM REPLICATION
Services
DB REPLICATION OR
LOG-FORWARDING DB and
FILE SYSTEM REPLICATION Application
Server and
Network

DISK-BASED REPLICATION Storage

Data Center A Data Center B

4
Major gaps exist in achieving DR goals

1 2 3 4 5 6
Many Dynamic Outdated Testing There is an Gaps exist in
enterprises environments runbooks are disrupts over-reliance management
don’t have application common. organizations. on manual and
the means— recovery processes. governance
or desire—to activities. activities.
fully protect
critical assets.

5
Orchestration is necessary to deliver a consistent
and predictable DR experience.

Orchestration
Creating an intelligent workflow comprised of
individual automated actions with an awareness
Orchestration sits higher
of the entire process in the stack than automation,
overseeing the entire process
and ensuring the coordination
Automation of all required activities
Codifying a set of manual steps via the creation of
scripts that drive singular actions at independent
component levels
Key Features and Capabilities
ü Single Click Drills, Failover and Recovery
ü Continuous insight into application data loss and recovery
time
ü Validate complex recovery for multi-vendor physical/virtual
environments
ü Rapidly identify causes of recovery test failures
ü Automate redundant, resource-intensive, and expensive
DR procedures
ü Design recovery workflows, leverage out-of-box workflows
ü Perform recovery audit reporting and documentation
ü Leverage on the built-in recovery automation library and
best practices for multi-vendor technologies
Resiliency Orchestration Provision
Resource
tool overlays existing provisioning and
best practice
technologies and Reports
workflows

provides a lifecycle Compliance and

deviation reports
Failover
approach to DR process Automated
application
automation recover

Test
Out of the box DR
Monitor
Continual
Test and failover
RPO and RTO
and failback

Failback
Orchestration

Validate
“Pre-flight”
checks
8
Clear dashboards and reports help you continuously monitor
your enterprise resiliency program more effectively

Executive Dashboard
+ Application wise summary
of Recovery Readiness

+ Events requiring attention

+ RPO and data lag meter

+ Recovery workflows that

are active

9
DR administrators can visibly and accurately understand the
RTO via the solution—not based on anticipated manual effort
and availability of equipment

DR Administrator
Dashboard
+ Database logs position

+ Dashboard with monitoring,

alerts and reporting of
Disaster Recovery solution
health and data RPO and
RTO Service Level
Agreements

10
 IBM Cloud Resiliency Orchestration enhances standard
technology-run approach for Visibility, more efficiency and
reduced RTO/RPO both in hybrid and non-hybrid environments
From: To: Benefit
Minimal RTO and RPO visibility except Dashboard for continual monitoring Increase Visibility &
during tests/drills and predictions of RTO and RPO Reduce Risk

Intelligently automated run-books and

Manual, error-prone operation of Help to simplify and
processes with predefined patterns
DR processes and run-books for efficient implementation accelerate DR process

Complex approaches resulting in Simplified solution using 450+ recovery Reduce Production
longer recovery times and resource automation library patterns reducing Outages, recovery time &
intensity the recovery times and resources operating costs

Manual DR testing/drills Using technology to orchestrate Simplify DR testing

automated test plans and failovers exercises. Reduce
dependency on experts

Managing DR and resiliency at the

Traditional DR focused at IT Increase availability of
business process and application level
infrastructure level only business applications
through intelligent workflow management
Orchestration is designed to increase workload efficiency and
address the complete recovery stack by leveraging more than 450+
predefined patterns for efficient implementation

DRM for the complete stack Recovery Automation Library that includes:
Platforms Applications Replication
Application Application environment, startup, shutdown
•Linux flavors •WebSphere,WebLogic • NetApp SnapMirror
•Windows , IIS • EMC SRDF,
Database RPO, Dump and Apply, Health •AIX, HP UX •SAP RecoverPoint
•Solaris •MQ Server • HP Continuous Access
•Oracle Exadata •Oracle • IBM Global Mirror,
Network Failover—DNS, NAT, NetScalar •FlexPod •MS SQL Server SVC
•VMware •IBM DB2 • Hitachi TrueCopy/UR
•Amazon Web Services •PostgreSQL • Database Native
OS Health, bring up, shutdown •IBM iSeries •MySQL Replications
•IBM z Systems •MS Exchange • Oracle Dataguard,
•SAP HANA SQL Log Shipping,
Replication/stor
Health, data lag, start, stop, split/join Mirroring etc.
age

Create/start/stop instance, provision

Cloud
storage, network, security groups

12
IBM Cloud Resiliency Orchestration – delivery options
IBM Global
Command Center
Production Datacenter Disaster Recovery Datacenter
On Premise / Bluemix / AWS On Premise / Bluemix / AWS
§
Internet
Replication
§
Orchestration Server Orchestration Orchestration Secure VPN
Link
Server Firewalls
§ §
VM VM VM VM

Production Servers and Storage DR Servers and Storage

• Orchestration server at Primary • IBM Global Command Center provides

and DR Site Monitoring & management.
• Three options – On premise, • Local SME and PM Services
Bluemix & AWS
Savings driven by IBM RO – Based on actual deployments

14
 • Increase the reliability & availability of Application
recovery, Reduce Production outages (Top 3 Global
IT challenge)
• Visibility with clear dashboard
• Enables rapid decision making during a disaster
• Enables proactive management
• Rapid root cause identification
Key benefits and • Dramatically reduce DR exercise and failover time
Value Proposition • Reduces dependency on experts
• Single-Click Recovery for enterprise applications
using multi-vendor technologies
• Provide continuous validation
• Scale DR with the same resources
• Meet Compliance & Regulatory requirements
WHY IBM?

16
Leverage IBM’s expertise, experience and leadership
to help propel innovation at your company.

50 years of business continuity and

disaster recovery experience 10K clients
protected

Protect information in more

than
300+ in
data centers 10 years of
experience
and innovation in
8M+
Sq. ft.

75
data protection data center
countries services raised floor
17

6,000 2.3 100%

Professionals exabytes of Success in meeting
dedicated to business customer data commitments to clients
continuity managed who declared incidents 17
India’s largest private bank with 4000+ branches, 12000+
ATMs [HDFC, reference customer available for customer
dialogue]
Key Business Requirements Technical Summary:
Perform DR switchover, run live in DR situation and switchback §1 active, sync to 1 near site,
Perform this 4 times a year for compliance with banking regulations in India async to 1 far site
Reduce man hours and resources for DR testing, reporting, monitoring §Linux, AIX with LPARs,
Manage a heterogeneous environment with multiple OS/DB/App/Replication Windows, Solaris
Technical Solution Features
§MS SQL, Oracle, DB2
Resiliency Orchestration managing 2-site as well as 3-site DR for applications
Workflows for intrusive and non-intrusive DR drills §Hitachi Universal Replicator,
Open Stack by design ideal for scalability ODG, MSSQL Log
Business Process Integration for End of Day, Start of Day activities Shipping/Mirroring, DB2 HADR
Customer & IBM Lessons Learned Applications protected:
Application files/forms inconsistency across DC-DR necessitates
replication § Core Banking, Retail
Need to prepare for failure of complete site as well as single application Banking, RTGS/NEFT
Recovery needs to be both sequential as well as parallel (Money transfer), SWIFT,
Technical Benefit Netbanking, MutualFund,
DR drill success up from <65% to >95% Foreign Office banking,
Single pane to manage DR Billing, Treasury
1-click DR testing/recovery for single and multiple applications Relationship:
Built-in reporting and DR monitoring along with real time alerts for deviations § >10 years term
Manage all replications from a single pane
Reduce manpower/man hours for DR testing, monitoring, reporting by at least RTO RPO
75% Business 2 hrs Near 0
Implementation Objective
Start with 5 applications Tested Actual <1 hr Near 0
Scale-up DR program
Year on year growth as per bank’s business growth
India’s 4th largest private bank with 3000+ branches, 9000+
ATMs, IBM Managed services
Key Business Requirements Technical Summary:
Perform DR testing 4 times a year for compliance with banking regulations in India §1 active, sync to 1 near site,
Reduce man hours and resources for DR testing, reporting, monitoring async to 1 far site
Manage a heterogeneous environment with multiple OS/DB/App/Replication,
§AIX with LPARs, Windows,
physical and virtual environment
Technical Solution Features §MS SQL, Oracle
Resiliency Orchestration managing 2-site as well as 3-site DR for applications §EMC SRDF, NetApp
Workflows for intrusive and non-intrusive DR drills SnapMirror, ODG, MSSQL
Business Process Integration for End of Day, Start of Day activities Log Shipping/Mirroring
Resiliency Orchestration managing physical as well virtual environment (Hot/Warm) §VMWare
Customer & IBM Lessons Learned
§Cyberark integration
Phased deployment
Applications covered:
Hot/Warm DR required for virtual environment for shorter RTOs with
application awareness § Core Banking, Retail
CyberArk Integration Banking, RTGS/NEFT
Technical Benefit (Money transfer), SWIFT,
Single pane to manage DR Netbanking, MutualFund,
1-click DR testing/recovery for single and multiple applications Foreign Office banking,
Built-in reporting and DR monitoring along with real time alerts for deviations Billing, Treasury
Manage all replications from a single pane Relationship:
Reduce manpower/man hours for DR testing, monitoring, reporting by at least 75% § >4 years term
Implementation
Start with 5 applications RTO RPO
Keep adding applications under Resiliency Orchestration scope Business 2 hrs Near 0
Managed Service by IBM Objective
Tested Actual <1 hr Near 0

19
A large SaaS core banking of core banking services, on
cloud, supports >150 smaller Indian banks
Key Business Requirements
Indian banking regulations in India require DR testing 4 times a year Technical Summary:
Core banking scope
§1 active DC-DR per app
Technical Solution Features
Single Resiliency Orchestration server managing multiple customers across 3 data §P Series LPARS
centers §Oracle DBs
P-series with virtualization with Oracle database using native replication §SaaS model
DR scope covers both infra AND application
§DR for Infra and Application
Customer & IBM Lessons Learned
tier
Application files/forms inconsistency across DC-DR necessitates replication
Need to perform drills for multiple banks at the same time
Technical Benefit Applications covered:
Single pane to manage DR for all customers Core banking
1-click DR testing/recovery for single and multiple banks
Built-in reporting and DR monitoring along with real time alerts for deviations
Reduce man hours and resources for DR testing, reporting, monitoring
Relationship
Implementation 3 years term
Aggressive time frame
2 stage implementation RTO RPO
5 banks done in phase 1, rest in phase 2
Stage 1 November 2013 Business 4 hrs 15m
Objective
Stage 2 January 2015
Tested Actual <1 hr <5m

20
A Middle East bank orchestrates the DR for
vSphere/SRM, Solaris, Win, Oracle, SQL, SRDF.

Key Business Requirements

Meet banking regulations in UAE requiring annualized DR testing
Technical Summary:
Core Banking, Retail Banking, Money transfer, SWIFT, Netbanking,
Technical Solution Features §2 DC
Single Resiliency Orchestration managing 2 data centers §Solaris & Windows Physical
Solaris & Windows Physical §Windows based VM,
Windows based VM,
§vSphere, w/ SRM
vSphere, w/ SRM
100+ MS SQL, Oracle DBs §100+ MS SQL, Oracle DBs
EMC SRDF §EMC SRDF
DR scope covers both infra AND application
Customer & IBM Lessons Learned
Applications protected:
Recovery plan needs to be split, app in DRM, remainder within SRM § Core Banking, Retail
Single pane glass for both virtual and physical Banking, Money transfer,
Integration with CyberArk SWIFT, Netbanking
Technical Benefit
1-click DR testing/recovery for single and multiple applications Relationship
Built-in reporting and DR monitoring along with real time alerts for deviations 2 years
Reduce man hours and resources for DR testing, reporting, monitoring
RTO RPO
Business 4 hrs 15m
Objective
Tested Actual <1 hr <5m

21
2. Next Steps

22
Next Steps

1. Conduct a Presentation and Demo

2. Official SOW development & submission

3. Contracting and Signing

23
© Copyright IBM Corporation 2017 IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many THE INFORMATION IN THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT
IBM Corporation jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A ANY WARRANTY, EXPRESS OR IMPLIED, INCLUDING WITHOUT ANY
IBM Global Technology Services current list of IBM trademarks is available on the web at “Copyright and trademark information" at WARRANTIES OF MERCHANTABILITY FITNESS FOR A PURPOSE AND
3039 Cornwallis Rd., Bldg 201 ibm.com/legal/copytrade.shtml ITIL is a registered trademark and a registered community mark of The Minister ANY WARRANTY OR CONDITION OF NON-INFRINGEMENT. IBM products
Research Triangle Park, NC 27709 for the Cabinet Office, and is registered in the U.S. Patent and Trademark Office. This document is current as of are warranted according to the terms and conditions of the agreements under
the initial date of publication and may be changed by IBM at any time. Not all offerings are available in every which they are provided.
Produced in the United States of America country in which IBM operates.
March 2017

24