ECM10

Enterprise Content Management
High Availability & Disaster Recovery
Cataldo Mega,
STSM IBM Content Manager 8
Architecture & Development, IBM Lab
Boeblingen, Germany,
cataldo_mega@de.ibm.com
Information Management Technical Conference 2008

Information Management Software | Enterprise Content Management
© IBM Corporation 2007. All Rights Reserved.
The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views.
They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or
other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the
information contained in this presentation, it is provided AS IS without warranty of any kind, express or implied. IBM shall
not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other
materials. Nothing contained in this presentation is intended to, nor shall have the effect of, creating any warranties or
representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license
agreement governing the use of IBM software.
References in this presentation to IBM products, programs, or services do not imply that they will be available in all
countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at
any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment
to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the
effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other
results.
IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Domino.Doc, Sametime, WebSphere, FileNet, Workplace,
WebSphere, Lotusphere, QuickPlace, and Quickr are trademarks of International Business Machines Corporation in the
United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or
both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.

Agenda
High Availability Fundamentals

Planning for High Availability
High Availability Technology for the IBM ECM Stack
Implementing High Availability for IBM Content Manager v8
Examples of ECM High Availability Solutions using IBM
Content Manager v8
Q and A

High Availability Fundamentals

Definition
Resilience is the ability of a system to provide and

maintain an acceptable level of service in the face of
various faults and challenges to normal operation. A
resilience system, resource, or structure is supposed to
sustain the impact of a business interruption and recover
and resume its operations to continue to provide at
minimum services.
In order for a production environment to achieve this goal

it is necessary to design, implement and deploy
High Avalaibility, Disaster Recovery and Backup &
Restore services.

Fundamentals
High Disaster
Availability Recovery
• What is it ?
• What is it?
• How to achieve it ?
• Many different levels
• Not a product question
. . . or answer • Cost versus Loss
• Only as strong as • Skills, Skills and Skills
the weakest link • Operations, operation
• Skills, Skills and Skills Backup and and operations
• Operations, operations Recovery
and operations
• A must have, Pre-Req for HA or DR

• CM solutions have multiple components
• Data integrity – how to achieve it?

Acronyms We Will Use
High Availability (HA)

Time to Recover (TTR)
Continuous Availability (CA)
Disaster Recovery (DR)
Load Balancing (LB)
Recovery Time Objectives (RTO)
Recovery Point Objective (RPO)
Maintenance Point Objective (MPO)
7

High Availability for ECM Solutions
The objective for HA should be to provide a

an affordable level of availability that supports the
business requirements and goals
High Availability Solutions Best Practices.....
Require significant upfront planning / analysis and continual
monitoring
Needs to balance cost versus acceptable business risk
Are not a specific to technology
Most of the time are within the same location or campus
If across locations, then it leans more towards Disaster Recovery
Should address all potential causes of an outage
Incorporates a variety of strategies and emerging technologies

How much is enough ?
Business Impact Analysis
The Business Impact Analysis (BIA) provides identification of

critical business processes required to operate the business
Identified business processes and applications seldom share
a common level of criticality, requiring the imposition of tiers
of availability
Key factor to consider during the BIA is the dollar value of the
business to be recovered.
A well-understood cost model of the business to be protected
is critical for a valid interpretation of the costs to deploy a
robust recovery system.

Key HA Architectural Metrics for Business Resilience
The definition of tiers of availability and resiliency provide the foundation for
a functional architecture. The key metrics that differentiate the tiers of
availability are the RTO, RPO, and MPO.
RTO - Recovery Time Objectives
– RTO defines the maximum time to return to operation
RPO – Recovery Point Objective
– RPO defines maximum allowable data loss
MPO – Maintenance Point Objective
– MPO defines the maximum allowable time window for
system maintenance
RTO, RPO and MPO are critical data points to consider during
architecture and design of an availability and resiliency model.
10

Time to Recover Segmentation Overview
Tier 7 - Highly automated, business wide, integrated solution
Tier 6 - Remote copy, disk mirroring

Zero or
Cost near zero
data Tier 5 - software two site, two phase commit
recreation Mission Critical
Highly Applications
Available
Tier 4 - Batch/Online database shadowing & journaling
minutes to hours
data recreation
Tier 3 - Electronic Vaulting Somewhat Critical
up to 24 hours Applications
data recreation Tier 2 - Hot Site
24-48 hours Not Critical
Tier 1 - Backup Applications
data recreation
15 Min. 1-4 Hr.. 4 -8 Hr.. 8-12 Hr.. 12-16 Hr.. 24 Hr.. Days
Time to Recover
*Note: Time to recover window for ECM solutions usually is in the range of up to tens of minutes! 11

Availability - The “5 Nines”
8760 4.38 0.09 0
8740 43.8
8720
Hours Per Year
87.6
8700 Unavail Hrs
8680 Avail Hrs
8660
8640
8620
99.00% 99.50% 99.95% 99.999% 100%
*Note: Typical Non-clustered Unix Availability. ECM Solution will range always below of what the platform provides! 12

Availability as a Metric for ECM Solutions
Availability is the product of the availability of all

components or the weakest link.
Need to measure the perceived availability as observed
by the end user or end point - an internal user, external
user, Business Partner or application
Availability 98.5% 98.5% 99.5% 98.1% 99.6% 97.3%
Fax, Scan, ISP / Load HTTP

Ingest Firewall
Import, . . . Network Balancer Server
Web CM / Data TSM,

Firewall Application Base Storage Optical / Retrieve
Server Server Tape
Availability 97.4% 98.3% 99.9% 99.8% 99.6% 99.7%
Total systems availability including all elements: Prod(A1..A12) = 87 % 13

Consider the Context
Key Components & Factors to consider

– Hardware
• Disk, CPU/Machine, Network
– Human Errors
– Planned / Unplanned Outages
– Disasters when they occur if they occur
Note: 6 Components with 99.5% Availability Comprise a

System with 97% Availability!
14

Free recovery does it exist ?
15

IBM Content Manager High Availability:

Generic High Availability Solutions Approach
16

Tested and Documented HA Configurations
Published White Papers:
IBM Content Manager V8.2
– Content Manager V8 Configuring High Availability in a Sun Cluster Environment
– Content Manager V8.3 Installing and Configuring High Availability in an AIX Clustered
Environment
– Content Manager Version 8 Configuring High Availability in a Microsoft Cluster
Services Environment
IBM Content Manager, IBM Document Manager and IBM Records Manager V8.3
– IBMContent Manager V8.3 for Windows: Configuring High Availability for Enterprise
Content Management Solution
– IBM Content Manager Content Manager V8.3 for Windows with Oracle 9i using RAC
for HA
– IBM DB2 Content Manager using DB2 HADR and resource manager replication
To be published:
– IBM Content Manager Content Manager V8.3 for AIX with Oracle 10g using Veritas
Cluster Server for HA
IBM Redbook:
Content Manager Backup/Recovery and High Availability: Strategies, Options, and
Procedures
17

IBM Content Manager v8 HA Solution Outline – SPoF
Capture Users, Devices

Paper
and Applications
Rich Media Browser / Devices /
Compound Applications
Single Points of Failure SPOF
Documents
- HTML
Documents
- etc . . . IICE DB HA: ECM Client Communication,
Dynamic load balancing, Tx fail-over
Mid-Tier /
Application Server
Content WAS DB Resource
Wide
Repository Bandwidth Manager
HA :CM LS Monitor Narrow
Cluster Scripts Bandwidth CM HA :
RM DB,
Referential
Integrity RM Services Cluster scripts
Library
Server TSM HA:
Central Resource
Manager
Catalog Narrow TSM DB
Bandwidth
TSM
Server
Streaming
Server
18

Technologies to Eliminate SPOF
Hardware
Platform Clustering
Database Clustering
Web Application Software Clustering
19

IBM Content Manager HA Relies On:
Platform high availability services
– High availability at hardware level
• Redundant Disk Subsystem
• Redundant Network
• Server Load Balancing - IP Sprayer
(IBM Network Dispatcher, Network Load Balancer, Big-IP)
OS specific cluster services like:
– System z built-in HA capabilities / Tivoli System Automation
– AIX HACMP, Tivoli System Automation
– SUN Cluster Services
– Microsoft Windows Server 2003 EE Cluster Service (MSCS)
– Veritas Cluster Server
Data base high availability services
• DB2 HADR*
• Oracle RAC
Application Container high availability services
• IBM WebSphere ND Cluster Services
• IBM WebSphere Edge Server Network Dispatcher or equivalent HW
20

Typical Configuration - DB2 Cluster using MSCS
21

DB2 Cluster – Hot Standby Configuration
One machine in the MSCS cluster

provides dedicated failover support
Other machine participates in the
database system.
If the machine participating in the
database system fails, the
database server on it will be
started on the failover machine.
If, in a partitioned database
system, you are running multiple
logical nodes on a machine and it
fails, the logical nodes will be
started on the failover machine.
22

DB2 Cluster - Mutual Takeover Configuration
Both workstations participate in

the database system
If one of the workstations in the
MSCS cluster fails, the
database server on the failing
machine will be started to run
on the other machine.
In a mutual takeover
configuration, a database
server on one machine can fail
independently of the database
server on another machine.
23

WebSphere Clustering Technologies

WebSphere v6 is architected out of the box for Clustering no
hardware clustering solution is required
WebSphere Application Server releases 6.0 and XD introduce a new high
availability architecture that is based on an internal component referred to as
Distribution and Consistency Services (DCS)
DCS is an implementation of Group Communication Services (GCS)
DCS provides a mechanism for communicating information (Distribution)
among members with a given (Consistency and Synchronization) Quality
of Service (QoS) for Performance, Scalability and Availability
An inherent part of DCS and an integral part of its services is failure
detection mechanisms that support and allow guaranteed QoS
DCS Services are provided through two main interfaces :
– Membership and Synchrony Service – HA Manager Component
– Data Replication Service – DRS Component
24

Websphere Network Deployment
IBM WebSphere Application Server Network Deployment provides:
– Clustering
– High availability for distributed configurations.
– Simplified administration using the development tool interface
– Intelligent workload distribution across a cluster
– Failure bypass
– Edge Server Component, delivers sophisticated load balancing, caching
and centralized security capabilities
– Web services enhancements
WLM / Failover
– HTTP Plug-in for Servlet Requests
– EJS WLM for EJB Requests
25

Managed vs. Unmanaged Cells
Unmanaged cell: Managed cell:
– basic, single node – complex, possibly distributed,
heterogeneous, clustered
– part of the default configuration
WebSphere Application Server
– managed by the default V5 / V6 installation
WebSphere Application Server
– managed by the a WebSphere
V5 administrative server: server1
Application Server Network
– default administrative server is Deployment Administrative
limited in its capabilities to Server: dmgr
administer multiple application
– On managed nodes, the default
servers and respective Web
administrative server (server1),
applications
is disabled
26

WebSphere Scalability using Clustering & Cloning
Vertical Scalability Horizontal Scalability

Node 1 Node 1 Node 2
Application Server Application Server Application Server
Clone 1 Clone 1 Clone 2
Application Server
Clone 2
Plug-in
HTTP
Server
Servlet Requests
27

HA By Layer in a WAS Environment
Tier 1 Tier 2 Tier 3 Tier 4
Presentation HTTP / DMZ Application Data
Active Active Active Passive
CM eClient1
CM e-Client1‘
II4C
CM e-Client1 CM 2e-Client‘ CM8 LS DB

Httpd‘ CM8 LS‘ DB
Httpd
CM8 RM1 CM8 RM1‘ WAS CM8 RM‘ DB
Clust VCS CM8 RM DB
ers
RME RME‘ IRM DB

IRM DB‘
IRM 413 IRM 413 IICE DB‘

IICE DB‘
Deployment
Manager Machine B Machine C Machine D Machine D
Node
NAS Storage
CM RM LBOS
Machine A
CM RM Staging
28

Solution High Availability with IBM

Content Manager 8 : Implementing High
Availability for IBM Content Manager 8
29

IBM Content Manager Architecture – Library Server
Database application
SP SP SP SP
Stored procedures for access
Manages users / access control
DB2/Oracle Contains data model definition
Document routing process
Net Search
Manages all metadata
Extender/OracleText
Client access points and server for
queries
Defines Content Manager System
30

IBM Content Manager Architecture – Resource Manager
HTTP / HTTPS
HTTP Server
Manages all physical
files
Replicator
WebSphere
Plugin Web Application
Purger HTTP / HTTPS
Identified by the
Stager
Application
hostname
Migrator Server
Administration Client
Resource
Async Manager uses Secured Sockets
Recovery Web Application
(HTTPS).
JDBC JDBC
DB2 Client Runtime Requires a database

DB2 Transport
RMDB
31

Important IBM Content Manager Components for HA
Library Server: Resource Manager
– LS database – RM database
– LS Monitor (service) – RM Web Application
– Full text search engine – RM Services
– The storage space
– TSM
The bold components have been evaluated and tested.

32

HA for IBM Content Manager (DB2) databases
Recommended HA Clusters:
Heartbeat
MSCS, HACMP, Sun Cluster,
Veritas…
Approach: Cluster Cluster
– 2 nodes (one active, one standby) Node 1 Node 2
– Shared disk
– Heartbeat monitoring system and
database health
– Failover initiated by cluster DB2 + DB2 +
software Content Content
Benefits: Manager Manager
binaries binaries
Short downtime, easy to setup
Concerns:
Disk subsystem is single point of
failure FastT / DB2 data 33

High Availability for Web Applications
IBM WebSphere Application Server Network Deployment

provides:
– Clustering
– High availability for distributed configurations.
– Simplified administration using the development tool
interface
– Intelligent workload distribution across a cluster
– Failure bypass
– Edge Server Component, delivers sophisticated load
balancing, caching and centralized security capabilities
– Web services enhancements
34

WAS ND for IBM Content Manager Resource Manager
(simplified)
App Server 1
RM App
Cluster 1 Storage
RM Services
IP Sprayer Service Cluster
Cluster 2 DB
RM Services
App Server 2
RM App
35

High Availability for Services
Library Server: Solution:

– Library Server Monitor – Use a cluster software that can
monitor these applications
Resource Manager:
– Windows: MSCS
– Purger
– Ensures they are only active on
– Migrator
one node
– Stager
– Provides failover
– Replicator
– Use the sample script provided by
Q: Can they run in parallel on two the IBM Content Manager V8.3 HA
nodes? White Paper
A: NO, not with IBM Content Manager
V8.3 Yes with IBM Content Manager V8.4
!!!
Q: What impact if they fail ?
A: Most likely none if for a limited
time only
36

IBM Content Manager HA – Complex Configuration
WebSphere cell
Deployment manager https SSLv3
HTTPD Client side Cert
request
SiteMinder
Agent
CM8 RM App cluster IRM App cluster IICE cluster

User registry
Server Server Server (LDAP)
JSPs JMS WebSphere

Adapters
SSO
CM APIs (II4C)
Veritas CS
RM Services
RM Services Oracle 10 g
CM8 LS DB Oracle 10 g
CM8 RM DB
Veritas CS
CM RM LBOS IRM DB
CM RM Staging IICE DB LS Monitor
LS Monitor
NAS Storage
37

IBM Content Manager HA – Complex Configuration
Tier 1 Tier 2 Tier 3 Tier 4

Presentation HTTP / DMZ Application Data
eClient / Mid-tier High availability /
Thin clustered servers
Network HTTP (w/ or w/o hot
clients dispatcher server Application spare)
(1) (1) server
(1)
Library Server
(1)
TSM
Server
Shared Disk,
Failover Failover Single
Copy of
Database(s),
Logs, Critical Files
Resource
Network HTTP Application manager
dispatcher server server (DB and
WIN32 (2) (2) (2) Filesystem)
clients
WAS
Application.
Shared devices
disk/tape/optical
Requires
WAS 6.x ND
38

Hardware Requirements Cheat Sheet
Hardware: Quantity Comment (used for test)

IBM XSeries Server Mod 360
DB2 Content Manager Library Server / 2 4x way Intel Xeon server
Resource Manager database nodes 4 GB Memory
4x IBM SCSI internal disks
DB2 Content Manager Resource Manager 2 2x Intel 1000 Gigabit Network adapters:
WebSphere Application Server cluster 1x 100 Mbps public network
nodes: 1x 1000 Mbps point-point private
heartbeat network

Network load distributor: (2) 2x way Intel Xeon server (HT)
IBM WebSphere Edge Server Load Balancer 4 GB Memory
2x IBM SCSI internal disks
2x Intel 1000 Gigabit Network adapters
1x 100 Mbps public network

Windows Domain Controller 1
IBM FASTT Model 600
Storage subsystem: 1
100 Mbps VLAN Cisco Router
Network 1
39

Implemented High Availability Topology on Windows
Node 6 9.30.45.22 (HA6)
WAS
Net.Dispatcher
cluster
Heartbeat
Net
Dispatcher LDAP
Deployment
MSCS cluster 2 MSCS cluster 1
Manager
secondary
Node 3 9.30.45.80 (HA2)

9.30.45.77 (HA1)
Net
Dispatcher Node 1
WAS
WAS
Deployment HTTP WAS CM LS 192.168.1.1
Manager Node plug-in App
App
primary agent RM Database(s)
9.30.45.22
192.168.1.2
Public
Clients Internet Heartbeat
Network
Public 192.168.1.4
Network Heartbeat
Name IPADDR
CM RM 192.168.1.3
LS 9.30.45.77 Node WAS
WAS
HTTP WAS Database(s)
192.168.1.1 agent App
plug-in App
App Node 2
RM 9.30.45.95
192.168.1.3
FC-AL 9.30.45.95 (HA3)
App1 9.30.45.80
192.168.1.2
Node 4 9.30.45.97 (HA4)
App2 9.30.45.97 LBOS
192.168.1.4
Net.Disp. 9.30.45.22
WAS ND
40

High Availability & Disaster Recovery at

the DRV the German Pension Agency
41

Outline of the DMS
Geschäfts-
BfA BfA
logik
Erfassungs- …
eReha Verfahren Verfahren
System
Archive Solution 1 n
Integrationsschicht
Strict decoupling between DMS JMS, RMI, HTTP
Archive System and Business WAS WAS

Messaging WAS Core Group Messaging
Logic Layer Verfahrens- Verfahrens-
schnittstelle
WAS Cluster schnittstelle
Dienste-
Schicht
DMS Zugriffsdienst
All access is controlled in a DMS Zugriffsdienst
WAS ND v6 WAS ND v6
controlled and conform manner Server 1 Server 2
exclusively over the business logic

WAS ND v6
Ressourcenschicht
interface layer Deployment Mgr 1
WAS ND v6
Resource
Manager 1
Deployment Mgr 2 Resource
VCS Manager 2
Every individual component is by it Library Server WAS ND v6
Oracle TSM Oracle

self highly available and scalable DMS Server 1 DMS Server 2
All access calls are transactional

and DMS system state is kept SAN LS DB Objekte RM DB
consistent
Archive services are accessed via Tape
Library
Tape
Library
Web Services, RMI, JMS und

HTTP(s) integration layer Rechenzentrum 1 Rechenzentrum 2
42

Hardware Configuration
Content Manager:
– 2 Fujitsu-Siemens Prime Power 850 Servers
– Each 16 CPU; 32GB RAM; attached to SAN
Services Layer:
– 2 Fujitsu Siemens Prime Power 450 Servers
– Each 8 CPU; 8 GB RAM
SAN (EMC Symmetrix)
– Corporate wide environment
– Replicated into 2 locations
TAPE Libraries „StorageTek SL8500“ with LTO 3 drives
– Used for backup and offline storage
43

Software
Operating System: Sun Solaris 8

IBM Content Manager 8.3
– Oracle 10 G as database
– WebSphere Application Server 6 Network Deployment
– TSM 5.3 to manage all storage areas
Services Layer:
– WebSphere Application Server 6 Network Deployment
– Custom GBS implementation
Other:
– Veritas Net Backup Backup of servers and databases
– Veritas Cluster Server High Availability
– InputAccel Scanning
– BMC Patrol Monitoring
44

High Availability Concept

Clients
Combination of:
– Veritas Cluster Server (VCS)
for Content Manager
– WebSphere Application
Server Network Deployment
(WAS ND) cloning
WAS ND vertical cloning
(clones on same node):
– Services layer: 2 clones each
– Resource Manager: 4 clones
WAS ND horizontal cloning SAN
(different nodes):
– Services layer only
45

The Veritas Cluster
Manages: Normal distribution:
– The mount operations of the – Node 1:
file systems from the SAN • LS Oracle Instance
– The operation of the Oracle • WAS ND Deployment Mgrs
instances for the Library – Node 2:
Server and Resource • RM Oracle Instance
Manager • RM Application
– The WAS ND Deployment • RM Services
Managers for the Resource • TSM Server
Manager and Services Layer Failover:
– The Resource Manager – Other node takes over all load
Migrator and Purger services – Constraints: Limited HW
– The TSM Server resources and power
46

Questions?
47

Backup and Recovery
Using existing backup environment and software

– Veritas NetBackup (for servers)
– Veritas NetBackup Oracle Agent for databases
– 2 distributed Backup Admin Systems
• Send backup commands
• Manager storage
• Notify administrators on success or failure
– 2 distributed tape libraries used for backup
• In normal operation, ever backup is written in parallel to
both location
• Failure results in single copy and notification.
48

Backup of the SAN
Controlled by Backup Admin Systems using Veritas Net

Backup
Backup is:
– Online: Oracle database don‘t have to be stopped
– Created as a “Snapshot”: Database is only for a few
seconds in backup mode
– LAN Free: Backup is managed within SAN, data mover
copies blocks within SAN
– Serverless block level: Data is copied as disk blocks directly
from the ECM Symmetry to the tape
– Implemented as incremental backups
49

Veritas Net Backup for Oracle
50

Backup Times and Cycles
Backups are created online

Outside of business hours
– Mon-Fri: 22:00-06:00, Sat+Sun: 14:00-06:00
Cycles:
– Initial (full): after major changes, at least 2 copies are
maintained
– Veritas Net Backup: daily, kept for 30 days
– TSM: daily, synchrous and asynchrouns, depending on
retention setting kept for up to 100 years
51

Disaster Strategy
All data is stored in at least 2 copies in different IT centers

– Managed by the SAN internally (creates mirror)
• SAN contains: databases, database logs, TSM disk pools
– All non-disk storage (for example tapes) are created redundant
• TSM is writing to 2 tape pools
All the data is always stored in at least 2 locations
Is supported by Backup strategy

– Backups are written to 2 tapes
– Storage of backup media offsite
52

Storage Management for IBM Content Manager
RM TSM 1 – DRVTSM00
Policy Domain: ICMDOM
Policy Set: ICMPOL
Management Class: ICMMC

Permanente Dokumente speichern
Primary Pool SAN Storage
ICMDISKPOOL
Primary Pool Tape

Retrieve Staging ICMTAPEPOOL
Permanente
Area
derzeit
Deaktiviert
Copy Pool
ICMTAPECOPY Tape
Purger
Temporäre Dokumente speichern

RM Disk Pool
SAN Storage
53

ECM10

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ECM10

Uploaded by

Copyright:

Available Formats

Enterprise Content Management

High Availability & Disaster Recovery

Information Management Technical Conference 2008

© IBM Corporation 2007. All Rights Reserved.

Information Management Technical Conference 2008

High Availability Fundamentals

Information Management Technical Conference 2008

High Availability Fundamentals

Information Management Technical Conference 2008

Resilience is the ability of a system to provide and

In order for a production environment to achieve this goal

Information Management Technical Conference 2008

• A must have, Pre-Req for HA or DR

Information Management Technical Conference 2008

Acronyms We Will Use

High Availability (HA)

Information Management Technical Conference 2008

The objective for HA should be to provide a

Information Management Technical Conference 2008

Business Impact Analysis

The Business Impact Analysis (BIA) provides identification of

Information Management Technical Conference 2008

Key HA Architectural Metrics for Business Resilience

Information Management Technical Conference 2008

Tier 7 - Highly automated, business wide, integrated solution

Tier 6 - Remote copy, disk mirroring

Information Management Technical Conference 2008

8760 4.38 0.09 0

Information Management Technical Conference 2008

Availability as a Metric for ECM Solutions

Availability is the product of the availability of all

Fax, Scan, ISP / Load HTTP

Web CM / Data TSM,

Availability 97.4% 98.3% 99.9% 99.8% 99.6% 99.7%

Total systems availability including all elements: Prod(A1..A12) = 87 % 13

Information Management Technical Conference 2008

Key Components & Factors to consider

– Planned / Unplanned Outages

– Disasters when they occur if they occur

Note: 6 Components with 99.5% Availability Comprise a

Information Management Technical Conference 2008

Information Management Technical Conference 2008

IBM Content Manager High Availability:

Information Management Technical Conference 2008

Information Management Technical Conference 2008

Capture Users, Devices

Information Management Technical Conference 2008

Web Application Software Clustering

Information Management Technical Conference 2008

Information Management Technical Conference 2008

Information Management Technical Conference 2008

One machine in the MSCS cluster

Information Management Technical Conference 2008

Both workstations participate in

Information Management Technical Conference 2008

WebSphere Clustering Technologies

Information Management Technical Conference 2008

Information Management Technical Conference 2008

Information Management Technical Conference 2008

Vertical Scalability Horizontal Scalability

Information Management Technical Conference 2008

Active Active Active Passive

CM e-Client1 CM 2e-Client‘ CM8 LS DB