Becoming Proactive on High Availability and Disaster ... B03.pdf · Becoming Proactive on HA/DR...

Becoming Proactive on HA/DR Readiness 1

Becoming Proactive on High Availability and Disaster Recovery Readiness

Ed Shelton Senior Product Manager

SYMANTEC VISION 2013

Disclaimer

Any information regarding pre-release Symantec offerings, future updates, or other planned modifications is subject to ongoing evaluation by Symantec and therefore subject to change. This information is provided without warranty of any kind, express or implied. Customers who purchase Symantec offerings should make their purchase decision based upon features that are currently available.



Executive Summary


Availability requirements continue to increase • Business services are complex and multi-layered

• Even small IT changes increase our HA/DR risks

Need to become proactive • Stop fire fighting

• Find and fix the HA/DR risks before they are a problem

Disaster Recovery Advisor • Only solution to cover the entire IT infrastructure

• Proactively reports on the HA/DR risks


Understanding the Real Availability Needs

Availability needs can be higher than expected


Service requires fewer than 52.56 min/year of downtime

Each component requires 99.999% availability

52.56

10 5.26 min/yr

Business Service

99.99% availability Storage LDAP

Middleware Replicated DB

Network

Web Farm

10 Components – Such as


What are the Causes of Downtime?


Ever-increasing risk • Each change in the infrastructure introduces risk

Causes of downtime • Most downtime (72%) is caused by configuration management 1

• 80% of mission critical downtime is due to people and process 2

Ris

k

Time

HA/DR Test

1 2010 Symantec Disaster Recovery Survey; 2 Gartner


Success Story: Tier 1 Application Disaster Recovery

6

DRA found: Tier 1 application with no disaster recovery capabilities

• Application owner failed to turn replication on after application maintenance

Situation

• Replication turned back on • Application’s disaster recovery readiness restored • DRA validates the disaster recovery readiness of the application on a weekly basis • Without DRA:

• Would have been identified with a major outage or during annual disaster recovery test

Results

Site 2 Site 1

APP

Becoming Proactive on HA/DR Readiness

Broken Replication


Ava

ilab

ility

Improving Availability by Improving IT Maturity


Maturity

1 Awareness

2 Committed

3 Proactive

4 Service Aligned

5 Business

Partnership

Source: Gartner 2012

Gartner’s IT Maturity Model Each step represents significant improvements

and benefits for Availability.


Ava

ilab

ility



Maturity

1 Awareness

2 Committed

3 Proactive

4 Service Aligned

5 Business

Partnership


Committed: •Fix things faster when

outage occurs


Ava

ilab

ility



Maturity

1 Awareness

2 Committed

3 Proactive

4 Service Aligned

5 Business

Partnership


Proactive: •Proactive processes and tools •DR management


Ava

ilab

ility



Maturity

1 Awareness

2 Committed

3 Proactive

4 Service Aligned

5 Business

Partnership


Service Aligned: •Proactive monitoring •Diverse DR testing


Ava

ilab

ility



Maturity

1 Awareness

2 Committed

3 Proactive

4 Service Aligned

5 Business

Partnership


Business Partnership: •Warning of potential outages • Integrated HA/DR with BC


Ava

ilab

ility



Maturity

1 Awareness

2 Committed

3 Proactive

4 Service Aligned

5 Business

Partnership


Disaster Recovery Advisor The only solution that automatically discovers and reports on the HA/DR risks in an IT infrastructure. •Accelerating organizations up the Maturity scale •Reducing costs •Reducing downtime


Disaster Recovery Advisor Executive Summary by a Customer


Disaster Recovery Advisory is a polling, analytics, & reporting tool targeted at proactively identifying system configurations of High-Availability & Disaster Recovery.

Put quite simply this is like AntiVirus software that looks for fail-over signatures, instead of virus-signatures.


How DRA Increases IT Maturity

• Regular scanning of the critical IT infrastructure

• Review of risks found

Stage 3: Proactive


Data Risk 6%

Redundacy Best Practices

39%

Performance 16%

Tampering 5%

Downtime 6%

Extended Recovery

Time 10%

General Best Practices

18%

Risk Distribution by Type



•Define the SLAs for DRA to check •Define and report risks based on IT Service

Stage 4: Service Alignment



Integrate DRA with CMDB


Stage 5: Business Partnership


CMDB

DRA

On-boarding

Automatically create tickets on risks found

DRA

Ticketing


Success Story: Eliminating a Concentration Risk

17

DRA found: Concentration risk – Clustered VMDKs mounted on the same array

• A single array outage or network outage to Site 1 would bring down multiple sites

Situation

• DRA recommended that VMDK images should be mounted in varied storage locations • Removal of concentration risk • Without DRA:

• Would have been identified with a major host outage • Outage would impact a large number of applications

Results

Site 1

VMDK Images

Site 2

VMDK Images



How DRA Works


Analyze Report Scan

• Collects data agentlessly

• Runs unobtrusively in the background

• Schedule scans to meet business needs

• Analyzes over 5,000 gap signatures

• Assesses the entire environment, Symantec and non-Symantec solutions

• Provides actionable reports with clear remediation steps

• Includes a dashboard of key risk categories

• Offers a graphical view of the topology


DRA architecture


Web Interface

Windows 2008 R2 Server x64

Oracle 11g

Storage Arrays • EMC: SYMCLI / NaviCLI

• HDS/HP XP: HiCommand / CommandView API

• IBM: DSCLI / XCLI

• NetApp: ZAPI / SSH / Telnet

Servers • SSH / WinRM / WMI

• OS / Vendor read-only commands and queries

• Valid user credentials / keys

Databases • JDBC using read-only user credentials

Virtual Machines • VMware API using read-only user credentials

• AIX VIO: HMC CLI

• UNIX: OS commands

Optional Collectors


Success Story: Improving Resiliency and Performance

20

DRA found: Single I/O Path = A single point of failure and performance bottleneck

• SAN I/O was configured with a single path causing performance degradation

Situation

• Configuration changed to meet certified architecture • Application performance and resiliency improved • Without DRA:

• Would have been identified with a major outage • Application would have continued to experience performance degradation

Results


SAN

SAN

SAN

SAN

SAN

SAN


Success Story: Core Web Application High Availability

21

DRA found: Application configuration doubled the risk of downtime

• Downtime in either datacenter would cause an outage in the Core Web Application

Situation

• Core application installed locally • Application will remain online if either site experiences an outage • Without DRA:

• Would have been identified with a major outage • Outage would have impacted customer, Web-facing services

Results

Site 1 Site 2



Disaster Recovery Advisor


Automated discovery of HA/DR risks • Scans entire infrastructure to find risks

• Looks for over 5,000 risks out of the box

Actionable reports • Risks (what and where) are reported with steps to fix the problem

• Risk reporting can be tuned to individual environments

Unobtrusive scanning and analysis • Agentless technology collects data unobtrusively

• Scans and analysis are scheduled to business needs


Executive Summary


Availability requirements continue to increase • Business services are complex and multi-layered

• Even small IT changes increase our HA/DR risks

Need to become proactive • Stop fire fighting

• Find and fix the HA/DR risks before they are a problem

Disaster Recovery Advisor • Only solution to cover the entire IT infrastructure

• Proactively reports on the HA/DR risks

Thank you!

Copyright © 2013 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice.


Ed Shelton

Senior Product Manager

[email protected]

650-793-4959

Dylon Mills

Technical Product Manager

[email protected]

678-427-6799


Appendix



DRA support matrix

Symantec Disaster Recovery Advisor 26

Replication Operating System Storage

Volume Management Multi-Pathing

Databases

Clustering

•Solaris 8+ •HPUX 11.0+ •AIX 4+ • Linux RedHat AS 3+ • Linux SuSE 8+ •Windows 2000+ •VMware

•EMC Symmetrix – All

•EMC CLARiiON (6.19+)

•NetApp Filers – All

•HDS AMS series (500 & 1000),

USP (TagmaStore, USP V, USP VM)

• IBM DS 6xxx, 8xxx

• IBM XIV

• IBM SVC

•EMC TimeFinder, SRDF •EMC MirrorView, SnapView •NetApp SnapMirror, SnapShots, SnapVault

•HDS TrueCopy, ShadowImage, UniversalReplicator, TrueShadow

• IBM FlashCopy, FlashCopy/SE, Metro Mirror, Global Mirror, Global copy

•Core supported OS VMs •Veritas Volume Manager • LVM 2

•Oracle 8.1.7+ •MS SQL Server 2000 SP3+ •Sybase 12.5+ •DB2 UDB 8.1+

•Veritas DMP •EMC PowerPath •HP PVLinks, HPDM • Linux MPIO • IBM AIX MPIO, SDD •Hitachi HDLM •NetApp DSM

•Veritas Cluster Server •HP MC/SG, PolyServe • IBM PowerHA •Sun Cluster •MSCS • Linux cluster

Date post:	07-Mar-2018
Category:	Documents
Upload:	ngoduong
View:	214 times
Download:	1 times

Becoming Proactive on High Availability and Disaster ... B03.pdf · Becoming Proactive on HA/DR...

Documents