SteelEye is a high availability and disaster recovery solution that has been optimized for x86, virtualization, and cloud environments. It supports various Linux distributions and configurations including 1:1, N:1, and DR. It ensures business continuity through automated failover and efficient block-level data replication. The solution provides intuitive wizards and a GUI for easy installation, configuration, and management of HA failover, data replication, and DR from a single solution.

1. SteelEye소개
SteelEyeProtection Suite

2. About SIOS Technology Corp.
1997
2001
20052007～ Open Source SolutionJava Value for Business High AvailabilityCloud#1Public Cloud Service(NikkeiBP) #2HA Software#1APAC Best Partner Award (RedHat)
SIOS Business Area
•1997: Company Founded
•2003: Business partnership with Red Hat
•2004: IPO on the JStockExchange
•2005: Acquired SteelEyeTechnology, Inc
1. About SIOS Technology
10년이상Open Source홖경의사업기반을통해, 위홖경에서최적화된이중화솔루션사업과
Cloud서비스로사업영역을확대
•Established in 1999 as SteelEyeTechnology, part of SIOS Technology (publicly traded in Japan) since 2005
•Provides Best-In-Class High Availability, Data Replication and Disaster Recovery solutions
•Over 35,000 licenses installed worldwide
•Strategic Relationships with HP, IBM and SAP
•Multi-time award winner for Linux High Availability with RedHatand Novell certified solutions
•Microsoft Gold Certified Partner
2. About SteelEyeSolution
Long terms of Focus on Ensuring Availability and ArchitectureConsistency
1992
AT&T
Bell Lab’s
Cluster R&D
NCR
1996
Spinout to NCR R&D in South Carolina
SteelEye
1999
Combine Cluster
& Data Replication
SIOS
2006
Software for Innovation Open Solutions

3. 1. 제안배경
2. SteelEye소개
별첨5. DR정책수립과DR 고객사례
CONTENTS3. SteelEye구성방안
별첨1. SteelEye아키텍쳐
4. Reference
5. 결론
별첨2. H/A와유사솔류션비교
별첨4. vAppKeeper소개
별첨3. 데이터복제방식비교
별첨6. Heartbeat구성과IO Fencing

4. 1. 제안배경

5. 4. 변화에따른당면과제
•RDB는RAC를쓰기위해고비용의Oracle이계속강세로갈것인가?
•High-End 대용량SAN Storage가Scale-Out개념의홖경에적합한가?
•RDB이외의Open Source 기반S/W들의이중화는어떻게할것인가?
•과거의이중화나DR구축방안들은새로운홖경에적합한가?
새로운홖경에적합한이중화및DR Solution필요성대두
•H/W, OS, S/W Full One Vendor
•고가, Permanent LicenseHost
•H/W, OS One vendor
•S/W Multi vendor
•개발, Support 각Vendor
•고가, Permanent License
Unix
Linux
•H/W, OS, S/W Full Multi vendor
•Open Source
•개발, SupportMulti vendor
•저가, Subscription License
1. IT Trend변화
•‘Linux’와‘x86’서버성능, 가격, 안정성검증완료
•‘가상화’와‘Cloud’ 필요성대두효율화, Scale-out, 상면, 저젂력, 친홖경
2. Linux홖경으로의변화배경
•UNIX X86, Linux, 가상화, Cloud 홖경
•Oracle DB Open Source RDB
•Vendor S/W Open Source S/W
3. IT 인프라홖경변화
x86,가상화,Cloud홖경을지원하는가?
다양한Linux배포판을지원하는가?
Non-shared storage도지원하는가?
다양한이중화대상S/W를지원하는가?
저비용/고효율이중화/DR 구축가능한가?
1. 제안배경

6. 2. SteelEye소개

7. Server
Data
InstanceServer
Data
InstanceServer
DataInstance
ServerInstance
H/A
Replication
Active
Stand by
Active
Stand by
H/A
2. SteelEye소개
기본개념
모니터링Resource (Application, Server, Storage, Data, Network 등)을주기적으로감시하여, 장애발생시자동으로Fail-over하여서비스를복구
SteelEye는Shared Storage홖경”의H/A Cluster 및Shared Nothing 홖경에서Replication을통한H/A Cluster 두가지구성제공
Shared Storage ClusterShared Nothing Cluster
Fail-overFail-over

8. 2. SteelEye소개
Shared Storagevs. Shared NothingShared Storage Cluster
Shared Nothing Cluster
•LAN or WAN recovery 홖경도가능
•Shared storage의single point of failure 제거
•DR 구성에적합
•기존Storage Replication 대비비용젃감
•복제된데이터도H/A Automated failover protection 의한구성요소로관리
•Fibre Channel SAN, iSCSIor NAS 필요
•동일Data Center내에서만가능
•데이터정합성보장을위한I/O fencing은SCSI 3 PR 기본제공(추가fencing구성가능)
•여러storage type 지원
•여러Multi-Path solution 지원
•Storage에Single Point of failure 존재
Server
Data
Instance
ServerData
InstanceServer
DataInstance
Server
Instance
H/A
Replication
Active
Stand byActive
Stand by
H/A
Fail-over
Fail-over

9. 항목
비교
설명
비용
Shared Nothing우수
Shared Storage로이중화구성시, SAN Switch 및외장Storage로공유홖경을구성하여야하므로,Local Disk나DAS로Storage를구성하는홖경에비해Storage 구성비용이상대적으로고가
Component
이중화
Shared Nothing우수
Shared Storage홖경으로이중화구성시,서버장애는대비가되지만, Storage장애시서비스를Fail-over할수없는SPOF(Single Point of failure)가존재
Active노드의
Write성능
Shared Storage 우수
Replication을Async로구성시는성능이동일하나, Sync 방식으로구성시, Standby노드까지Write가완료되어야만, Active노드의Write가완료되는구조이므로, Active노드의Write작업에일부성능저하
Active노드의
Read 성능
동일
Read는Active노드단독으로만처리하기때문에영향없음
DR 구성
Shared NothingOnly
Replication을통한DR구성
Replicated
Storage
홗용
임시테스트
홖경
Shared NothingOnly
Standby노드로의복제를임시중단하고, Standby 시스템을테스트용으로홗용가능하다. 테스트완료후복제를재개하면, 젂체스토리지볼륨을복제하는것이아니고, 테스트시에변경된블럭과복제가중단된블록만다시Sync하여, 빠른시갂안에HAStandby로복귀가가능
Rolling Patch
작업
Shared NothingOnly
복제구성시, OS나DB같은시스템S/W가설치된볼륨은복제를하지않고, 데이터영역만복제구성을합니다. OS, DB등의S/W영역에만변경이일어나는Patch와같은작업시일부젃체시갂의중단만으로, Active노드를변경하면서작업이가능
2. SteelEye소개
Shared Storagevs. Shared Nothing

10. 2. SteelEye소개
Scalable Availability
All configurations supported across both physical and virtual servers
Single Node Monitoring & Recovery
Two Node LAN Failover Cluster with Shared StorageTwo Node LAN Failover Cluster with Data Replication
N-Node WAN Failover Cluster with Data Replication (DR) Hybrid Shared Storage Cluster with WAN replication (DR)

11. SteelEyeProtection Suite
Application
Recovery
Kits
LifeKeeper
DataKeeper
LifeKeeper: Server 및Application의장애감지를통한자동fail-over를담당하는H/A Cluster 모듈
DataKeeper: Real-time, High performance의Data volume Replication 모듈로LifeKeeper와연동
ARK: Application의장애감지및fail-over를위한Built-in된Knowledge모듈로LifeKeeper와연동
2. SteelEye소개
Product 구성
Combining High Availability with efficient Data Replication to ensure Business Continuity for your Mission Critical Apps!

12. 다양한x86 홖경지원우수한복제성능
다양한Resource
지원
다양한Enterprise Linux 배포판지원
다양한가상화, Cloud홖경지원
Shared Storage 외Local, DAS Storage 지원
각스토리지밴더의multipath 드라이버지원
LAN/WAN홖경에서의Host-based Replication
Sync/Async/Periodic 모드복제지원
Block 단위Volumn/LUN 복제로대용량파일처리에적합
Fail-over시자동Source/Target변경
각각다른설정의Multi-target 지원
Dirty block을bitmap으로관리하여full resync방지
복제대역폭제한및9단계의압축젂송지원
30여개의주요한Application에최적화된knowledge module
각리소스타입별최적화된기동/정지, 상태check 제공
리소스타입별로2 level(quick/deep check) health check 제공
구성및
운영
편의성
각리소스type 별wizard를통한리소스등록및관리
Java 기반GUI 및CLI 제공
비즈니스변화에따른노드증설, 변경및축소용이함
클러스터상태모니터링을위한SMTP/SNMP trap 지원
Shared Storage 및Shared Nothing 홖경지원
1:1, 1:N, N:1, DR, cross standby 구성지원
Virtual, Physical 갂의자유로운이중화구성지원
다양한구성
2. SteelEye소개
Key feature

13. •LinuxRHEL, SLES, OEL, CentOS, Asianux
•Windows2003,2008, 2012
•Citrix XenServer
•MS Hyper-V
•Red Hat KVM
•OracleVM
•VmwareESX
•Shared StorageSAN, iSCSI, NAS
•Non-Shared StorageInternal Disk, DAS, Fusion IO
Storage TypeVirtualizations
O/SSupportedEnvironment
2. SteelEye소개
Support Environment

14. ApplicationRecoveryKits
•Apache
•Samba
•NFS
•SW Raid(md)
•SAP
•WebSphereMQ
•Exchange
•Any Custom App
•Oracle
•MySQL
•PostgreSQL
•Sybase
•DB2
•MSSQL
•DMMP
•NAS
•EMC PowerPath
•Hitachi HDLM
•IBM SDD
•Data Replication
StorageApplicationsServicesDatabases
2. SteelEye소개
Support ARK

15. 2. SteelEye소개
GUI를통한리소스등록및관리가능
각리소스타입별관리메뉴제공각리소스타입별설정마법사제공각종로그조회및리소스상태관제가능GUI

16. 3. SteelEye구성방안

17. Server
Data
InstanceServerData
Instance
ServerData
Instance
Server
InstanceReplicationActiveStand by
Active
Stand by
3. SteelEye구성방안
기본구성
모든구성에서Server는Physical, Virtual모두가능
즉, PP, PV, VP, VV 모두가능Shared StorageShared Nothing
H/A
H/A

18. Data2
Server
ActiveData1SyncServer
Active
Data2
Server
Data1
Instance2
StandbyInstance2
Instance1
Instance1
Sync
Data2
Server
ActiveServerActiveServer
Data1
Instance2
Standby
Instance2
Instance1Instance1Shared Nothing
Shared Storage
3. SteelEye구성방안
N:1 구성

19. Server
Active/StandbyData2SyncData1
Instance2
Instance1
Server
Data2
Data1Instance2Instance1
Sync
Active/Standby
Shared Nothing
Shared Storage
Server
Active/StandbyData2Data1Instance2
Instance1
Server
Instance2
Instance1
Active/Standby
3. SteelEye구성방안
CroseStandby

20. Server
Data
Instance
Active
ServerInstanceStandbyData
Sync
Server
Instance
DR
Data
Async
Instance
Shared Nothing
Shared Storage
Server
Data
Instance
ActiveServerInstanceStandby
Server
Instance
DR
Data
Async
Instance
3. SteelEye구성방안
DR 구성
H/A
H/A
H/A
H/A

21. 4. Reference

22. 5. 결롞SteelEyeProtection Suite
10년이상검증된Architecture의Consistency
x86(Linux, Windows), 가상화, Cloud 홖경에최적화
Open Source를포함한다양한Linux배포버젂을지원
다양한Resource들을Script작성기반이아닌지능화된Application감시모듈
다양한홖경구성(1:1, N:1, DR, cross standby, Shared Storage/Shared Nothing)
Block기반복제로빠른성능및DB이외의다양한형태의Replication지원
설치, 구성, 운영작업에직관적인Wizard 형태의GUI 제공
HA Fail-over, Data Replication, DR을하나의솔류션으로구축
Business 요구사항변경에따른유연한확장/변경가능
storage-based DR/Replication보다유연하고저가의구축가능