HP Shadowbase: Better TCO for Business Continuity. Shadowbase Product Overview with Shadowbase Success Stories. Business Continuity, Data Integration & Synchronization, Application Integration, Tools, Utilities, and Add-ons.Shadowbase Product Suite Overview. Business Continuity & Application Availability Environments, Active/Passive Disaster Recovery, Sizzling-Hot, Takeover (SZT), Active/Active Continuous Availability, Eliminate Planned Downtime for Migrations & Upgrades (ZDM), Data Integration & Data Synchronization, Homogenous & Heterogeneous Environments, Data Transformation, Scrubbing, Filtering & Cleansing, Extend Replication Capabilities with Embedded Application Logic, Application Integration, Build Event-driven Architectures–No more polling for needed data, Build Real-Time Architectures– Process events as the occur; no more working with “stale” data, Integrate Disparate Applications with no Application Code Changes, Integrate at data-layer, avoiding costly adapters & middleware. Key Availability Metrics: RPO & RTO Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are used to describe business continuity, (BC) requirements; discussion below relates primarily to distributed BC architectures, RPO-describes the point in time to which the data must be recovered– How much data can my business afford to lose?, RTO- describes the time from when a failure occurs until the business process must become active again.

1. HP Shadowbase: Better TCO for Business Continuity
Description: HP Shadowbase: Better TCO for Business Continuity. Shadowbase Product Overview
with Shadowbase Success Stories. Business Continuity, Data Integration & Synchronization, Application
Integration, Tools, Utilities, and Add-ons. Shadowbase Product Suite Overview. Business Continuity &
Application Availability Environments, Active/Passive Disaster Recovery, Sizzling-Hot, Takeover (SZT),
Active/Active Continuous Availability, Eliminate Planned Downtime for Migrations & Upgrades (ZDM),
Data Integration & Data Synchronization, Homogenous & Heterogeneous Environments, Data
Transformation, Scrubbing, Filtering & Cleansing, Extend Replication Capabilities with Embedded
Application Logic, Application Integration, Build Event-driven Architectures–No more polling for needed
data, Build Real-Time Architectures– Process events as the occur; no more working with “stale” data,
Integrate Disparate Applications with no Application Code Changes, Integrate at data-layer, avoiding costly
adapters & middleware. Key Availability Metrics: RPO & RTO Recovery Point Objective (RPO) and
Recovery Time Objective (RTO) are used to describe business continuity, (BC) requirements; discussion
below relates primarily to distributed BC architectures, RPO-describes the point in time to which the data
must be recovered– How much data can my business afford to lose?, RTO- describes the time from when a
failure occurs until the business process must become active again.
Reference URL:http://business.wesrch.com/paper-details/pdf-BU1H5HZEWYECG-hp-shadowba
se-better-tco-for-business-continuity