The document describes DataVard OutBoard, a solution for managing data growth in SAP BW environments. It addresses challenges such as increasing storage costs and slower system performance as data volumes rise over time. OutBoard uses compression and tiered storage across different databases and storage types to reduce storage usage and costs. It provides a single management interface and integrates fully with SAP systems.
2. Data volume growth is alarming!
? 47% of respondents
ranked data growth in
their top three
challenges.
C Gartner, User Survey Analysis: Key Trends Shaping the
Future of Data Center Infrastructure Through 2011
? Average annual
growth rate 40% to
60% per year
C Computerworld, 2010
2 ? 2008
3. Data growth is eating up your storage!
? Buying more storage does not
solve the problem
? The larger your DB, more time
is needed for backup &
recovery, system copies, and
upgrades.
? The larger your DB the more
performance is impacted
and if that was not enough
3 ? 2008
4. Productive data is like an iceberg
Data in
productive Manage the root cause
BW
1. Data on
disc Our experience:
2. data center
1 GB in PROD
takes
3. Backups
10 - 18 GB
in total storage
4 ? 2008
5. The solution: NearLine Storage with
Outboard
Fight the root cause Profit from effects
? Outboard frees capacity on ? Reduce storage costs
your DB. Immediate relief of
? Save time for backup &
30+%.
recovery, system copies and
? Slow down data growth upgrades
automatically
? Improve performance for hot and
Implement a smart ILM strategy: warm data
cold data is compressed in
Outboard (avg. 95%)
&
5 ? 2008
6. SAP BW Information Lifecycle Management
with OutBoard
USER
Newest data HOT BW Accelerator
0-2 years WARM
OutBoard?
? Data stored cost-
optimized and audit-proof
>2 years ? Compressed by 95%
COLD ? Available anytime for
reporting and loading
6 ? 2008
7. SAP BW Architecture with Near-Line Storage
Enterprise Query, Reporting & Analysis
BW Accelerator
Analytical Engine
InfoObjects / Master Data
Data Flow Control / Process Chains
Meta Data Repository / Documents
Enterprise Data Warehouse
(Architected)
Near-Line Storage
Data Marts
Data Store
Object
(volatile) Data Warehouse Layer
SAP NLS
Interface (historical)
DataSource / PSA
7 ? 2008
8. OutBoard? Cockpit & Object Browser
The OutBoard? cockpit serves as
central access point to all
OutBoard? functions.
The Object Browser gives a
full overview on all
InfoProviders & PSAs stored
in OutBoard?.
? 2008
9. OutBoard? - Compressed vs.
Uncompressed data volume
Actual customer example of compression ratio
? 2008
10. Cost savings with a live example
Linear growth
2.5 Assumptions
2 ? Data growth 30% p.a.
1.5
No Outboard
? Avg. compression rate
With Outboard Lin
90%
1
DB capa ? Immediate relief 40%
0.5
? Data retention time
0 2 years
2011 2012 2013 2014 2015
Exponential growth
3.5
3
2.5
2 No Outboard exp
1.5 With Outboard exp
1 DB capa
0.5
0
2011 2012 2013 2014 2015
? 2008
11. No-stress purchasing and implementation
? 1 day installation on existing system
C 10 days consulting incl. analysis and support
? 1 Productive system = 1 Price
C OutBoard? is priced per productive system, not by data volume
in NLS or users
? No separate hardware or database
? Try before you buy (1 month)
11 ? 2008
12. OutBoard? in a nutshell
? Only warm data in online database. Cold data is
World-class Compression compressed by up to 95% at full availability.
Reduces Data Growth ? Immediate relief of 30+%
? No 3rd party database (e.g. Sybase) required
100% Integrated in SAP: ? Technically simple architecture reduces risk, simplifies
One Technology, No Risk! operation and guarantees efficient operation
? SAP Netweaver certified
? Easy installation and operation with minimal training
required
Fair & Simple Pricing ? No additional software or hardware required
? Simple pricing per production system (instead of per-user)
? No hidden cost
Improve System ? Reduced database improves performance of BW reporting
? Backup & restore times are reduced
Operation and ? Improves disaster recovery due to minimized data in one
Performance DB
12 ? 2008
14. Introduction
? SAP HANA as an in-memory solution offers undreamt-of
possibilities, in particular by the extreme acceleration of
the loading processes.
? By the high cost of operation and the acquisition of
HANA, we see a functional gap: data can be kept only
in memory.
? We recommend to close this gap through a combination
of near-line-storage (NLS) and a smart storage
management solution.
14
14 ? 2008
15. Outboard 2.0 C Data Management with
HANA
SAP
cluster
tables Business Warehouse
Near-Line Storage
? Native to
Data Aging
Sybase IQ &
SAP NLS
External /
Interface
MaxDB
? Remote DB Remote
(via RFC) DB
Storage
Mgmt.
? File HANA
? Corporate File / DB
Cloud Cloud
? End of
lifecycle Deletion
To accommodate a variety of customer needs in terms of reporting speed and TCO reduction we offer a range of
storage layers:
1. SAP cluster tables for high compression and fast access. These tables will be stored in HANA
2. External DB: Sybase IQ & MaxDB native or Remote DB
3. File or Enterprise cloud: delivers the best TCO and allows for maximum flexibility
4. At the end of the lifecycle data can be deleted from OutBoard automatically
15 ? 2008
16. Storage Layer Concept
Enables you to manage cost of storage
inline with the value of information.
Data can be transfered to other layers
managing various aging thresholds.
Example:
1.Up to 2 years in HANA
2.2-3 years in cluster tables on HANA
3.3-7 years in external / remote DB
4.7-15 years in file
5.15+ will be deleted
16 ? 2008
17. Layer 2: External / Remote DB
Sybase IQ MaxDB
Storage
Business Warehouse
ODBC
Mgmt.
Near-Line Storage
RFC
Separate SAP Netweaver
HANA
DB2 ORACLE MS SQL
DB
This option allows you to reuse your existing DB licenses and know-how to store aged data in a cost efficient way.
? Sybase IQ as a data smart store that allows for fast access while being operated at lower TCO than HANA
? SAP MaxDB is a proven and robust technology that delivers superior TCO and seamlessly integrates into any SAP
landscape
? Remote DB allows you store and read the data via RFC connection to/from a SAP NetWeaver (and the corresponding
underlying DB); this option best leverages existing investments and is operated at low cost
17 ? 2008
18. Layer 3: File / Cloud
Storage
Business Warehouse
Mgmt.
Near-Line Storage
Cloud
File
Server
HANA
DB
This option delivers the best TCO and allows for maximum flexibility as storage can be allocated on
the fly.
Due to the slow access speed this option is recommended for very aged data only and for corporate
memory, PSA, change log.
18 ? 2008
19. For more information please contact:
David A. Fox
Managing Principal
Consultant
T: 888-325-6496 x511
E: dfox@claricent.com
or go to http://claricent.com/outboard
19 www.claricent.com ? twitter/claricent ? facebook/claricent
? 2008
Editor's Notes
#2: An outboard motor is a propulsion system for boats, consisting of a self-contained unit that includes engine, gearbox and propeller or jet drive.Less risk C proven SAP technology = less risk that something can go wrong after an upgrade; dependency on database vendor (e.g. PBS is using Sybase IQ and SAP bought Sybase. What will happen with the database now ?)BWA ready C some solution are competing with BWA by giving similar technology at lower price than SAP. However NLS interface is meant for aged data, SAP will not add functionality which will allow BWA competitors to be better.