data archiving introduction

mySAP TechnologyData Archiving

Georg FischerGeorg FischerGeorg FischerGeorg FischerSAP AG

� SAP AG 2001, mySAP Technology Data Archiving,G. Fischer 2

Agenda

�

Overview

�Introducing Data Archiving

�Access to Archived Data

�Managing Data Archiving Projects

�How to get further Information


Agenda

�

Overview






Data Archiving

R/3 DB

Application Data

Archive and Delete

ArchiveFiles

OnlineAccess

Data Objects


�System availability� Faster upgrade to higher software releases� Faster Euro conversion� Shorter runtime for backup and recovery

�Efficient use of resources� Reduced hardware costs

� Storage, CPU, Memory� Reduced administration costs

�Shorter response times in dialog mode

Benefits


The Rising Significance of Data

�The top concern for 90% of all IT managers:“Managing data and information overflow intelligently”(Survey by CSC Ploenzke AG, 2000)

�“Globally, data storage is becoming a major branch of industry and the central focus of information technology”(Dataquest, GartnerGroup Research Note: Storage will dominate server spending)

� Relative hardware investment� 1998: 57% servers, 43% storage� 2002: 20% servers, 80% storage


What Does Data Storage Cost ?

�

„Hard disks are inexpensive! If I need more database space, I’ll add another disk to my storage system.“(Customer statement)

Test system (1,2,...) EURO system

Production system

???-System


The Distribution of Storage Costs

�According to a study by the Giga Information Group, hard disk costs represent less than a quarter of storage costs.

Various(training, other costs)

10%

Environment(Electricity, physical space)

3%

Storage Mgmt (Soft- & Hardware)

19%

Hard disk

23%Personnel

45%


Customer Experiences

�German and American customers report storage costs (without personnel costs) of US$ 4,000 - 15,000 per gigabyte in a productive database.

�German customers report outsourcing storage costs of DM 1,000 per month and per gigabyte.


Agenda

�

Overview






Data Archiving and Storage

R/3 DB

Applicationdata File systemData stream

Control stream

SAP Functions Partner Functions (optional)

SAP R/3 System External Storage System

• Optical archivesystem

• HSMSystem

• Storagesystem

SAP ArchiveLink


Archive Development Kit - ADK

�Development tool for Data Archiving solutions� SAP AG

� Application developers integrate archiving functionality into the application� Customer

� Archiving solutions for customer-specific tables and extension

Archive files

ADKAdjustment of code page, numberformat, structure changes, compression, file handling, batch interface

R/3 DBR/3 DBApplication

datamySAP.comApplication


Archiving Object

�Definition of logical units in business processes

�All programs required for archiving, for example preprocessing, read, write and delete programs

�Definition of required Customizing

Data

Archiving Object

Customizing

Programs


Archiving Session Phases

Write phase

Delete phaseFile 1

Delete phaseFile 2


Agenda

�

Overview






Archive Information System - AS

�Browsing through archive files

�Configurable reporting based on infostructures� Ad-hoc access to archive files� Using database tables for fast access

�Direct access to single data objects

�Access to original documents via SAP ArchiveLink

�Early availability as transport down to Release 3.1i(SAP Note 99388)


Archive Information System - AS

Archive Information System

Archive Retrieval Configurator

Archive files

create read

Archive Explorer

Archive InformationStructure


AS: Access to Archived Data

Access archived data


Document Relationship Browser - DRB

�Simultaneous access to archived and online data

�Start via new transaction ALO1 or via SAP AS

�All common archiving objects are connected� SD: sales documents, deliveries, billing documents, sales activities� MM: purchasing documents, purchase requisitions, invoice documents,

material documents� FI: financial accounting documents� CO: line items

�Early availability as transport down to Release 3.1i(SAP Note 217404)


DRB: Access via SAP AS


DRB: Access via Transaction ALO1


Agenda

�

Overview






Find the Right Time

Database Size

050

100150200250300350400450500

1998

1201

1999

0101

1999

0201

1999

0301

1999

0401

1999

0501

1999

0601

1999

0701

1999

0801

1999

0901

1999

1001

1999

1101

Date

[GB

]

Date Aktual Size in GB Monthly Growth in GB19990101 33.17 1.9019990201 36.09 2.9219990301 73.78 37.6919990401 137.96 64.1819990501 190.01 52.0519990601 256.99 66.9819990701 324.87 67.8819990801 376.00 51.1319990901 428.37 52.3719991001 438.06 9.6919991101 470.25 32.19


Positioning

�Data archiving for a “healthy” system� data archiving should not be seen as the last chance to prevent system

collapse after all possible hardware upgrades have been exhausted

�Bring data archiving into the planning stage� maintain R/3 System performance

�Data archiving is an interdisciplinary process� data archiving requires a high degree of cooperation between user

departments and the IT department


Find the Right Time

�Experiences from customer projects

�Why should Data Archiving not be postponed?� The project gets more complex the bigger the database has grown� The archiving programs need more resources� Longer recovery time in case of disaster� The maintenance windows for „data hygiene tasks“ might become

insufficient� Increased down time when installing higher software releases� Several archiving objects can be used soon after going live� Slower system response time makes all online users less efficient


Phases of an Archiving Project

DataAnalysis

Design undConception Test Implemen-

tationBuild

Project Team

� Project manager� IT department� User department� Auditing/

controlling� Persons

responsible for application

� Externals

� Table sizes� Growth rate� Assigned

archiving objects� Dependencies� Legal

requirements� Residence� Access

requirements� Authorizations� Storage media

� Documentation concept (audit)

� Archiving concept

� business part� technical part

� Implementationplan

� activities� schedule

� Long-term archiving plan

� management archive files

� SAP Notes� Transports� Maintain variants� Configure server� Customizing� Storage system� Execute data

archiving� Possible

postprocessing

� Based on the test phase

� Preparation� Execution� Follow-up


Data Prevention

Do youneed

this data?

Do youneed

this data?Step 1

Retain Datain Database!Retain Datain Database!

N

Can yousummarizethis data?

Can yousummarizethis data?

Step 2

Y

Switch off thecreation

of this data!

Switch off thecreation

of this data!

N

Summarizethis data!

Summarizethis data!

Y

Can youarchive

this data?

Can youarchive

this data?Step 3

N

Y

Use DataArchiving!


Customer 1

�Starting point:Approx. 290 gigabyte DB size and approx. 15 gigabyte DB growth per month

�Aim:Reduction of DB growth rate to:� Reduce hardware costs� Maintain stable system performance

� Response times and system administration� Faster implementation of support packages and upgrade projects� Local currency conversion

�Archiving:19 archiving objects from FI, CO, MM, SD and HR

�Result (at October 2000):>200 gigabyte archived


Customer 1

0,00

100,00

200,00

300,00

400,00

500,00

600,00

700,00 01

.03.

1999

01.0

4.19

99

01.0

5.19

99

01.0

6.19

99

01.0

7.19

99

01.0

8.19

99

01.0

9.19

99

01.1

0.19

99

01.1

1.19

99

01.1

2.19

99

01.0

1.20

00

01.0

2.20

00

01.0

3.20

00

01.0

4.20

00

01.0

5.20

00

01.0

6.20

00

01.0

7.20

00

01.0

8.20

00

01.0

9.20

00

DB growth:~15 GB/month

'Without'Archiving

InitialArchiving

Reduction:~60GB

With regularly archiving

DB growth: ~7 GB/month

Allocated DB size

Allocated DB content

Expected sizewithout Archiving


Customer 2

�Starting point:Approx. 300 gigabyte DB size and approx. 5 gigabyte DB growth per week

�Aim:“To archive high impact areas as aggressively as possible and establish a procedure and infrastructure for a repeatable, ongoing archiving process”

�Archiving:Projekt divided into 4 phasesArchiving objects from FI, CO, MM, SD, PCA, IDOC

�Result:Project phase I approx. 100 gigabyte archived (1999)Project phase I – III approx. 160 gigabyte archived (2000)


Kunde 2

Database Volume Forecast

0,0

200,0

400,0

600,0

800,0

1000,0

1200,0

1400,0

Jun 9

9Okt

99Feb

00Ju

n 00

Okt 00

Feb 01

Jun 0

1Okt

01Feb

02Ju

n 02

Okt 02

Feb 03

Jun 0

3Okt

03Feb

04Ju

n 04

Timeline

Volu

me

(GB)

Volume withArchiving

VolumewithoutArchiving


Agenda

�

Overview






Documentation

�Data Prevention Checklist� Version 2.0� October 2000

�Managing SAP Archiving Projects� Version 2.0� April 2000

�Data Archiving and the EURO� Version 3.1� February 2001

http://service.sap.com/data-archiving� Media Center Literature or� Section „Publications“


Presentations

�SAP Data Archiving Introduction� August 2000

�Data Archiving Projects� August 2000

�Data Archiving and SAP Retail� August 2000

http://service.sap.com/data-archiving� Media Center Presentations


Trainings

�SAP Training Courses

�BC660: Data Archiving� Level 3� 3 Days

�BC670: Data Archiving - Retrieval Programming� Level 3� 2 Days


Copyright

� No part of this presentation may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

� Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered trademarks of Microsoft Corporation.

� IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

� ORACLE® is a registered trademark of ORACLE Corporation, California, USA.� INFORMIX®-OnLine for SAP is a registered trademark of Informix Software Incorporated.� UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.� HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of Technology, 545 Technology Square, Cambridge, MA 02139.

� JAVA® is a registered trademark of Sun Microsystems, Inc. , 901 San Antonio Road, Palo Alto, CA 94303 USA.

� JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

� SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com Workplace, mySAP.com Business Scenarios, mySAP.com Application Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP Business Workflow, SAP EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit, SEM, are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

data archiving introduction

Documents

storage sap ag

data storage cost

system sap ag

information sap ag

archiving functionality

dialog modebenefits

outsourcing storage

quarter of storage costs