Data Protection for mySAP.com Technology Installation...
160
IBM Tivoli Storage Manager for Enterprise Resource Planning (5698–APR) Data Protection for mySAP.com ® Technology Installation & User’s Guide for DB2 UDB Version 3 Release 3. 11 SC33-6341-04
Transcript of Data Protection for mySAP.com Technology Installation...
-
IBM
Tivoli
Storage
Manager
for
Enterprise
Resource
Planning
(5698–APR)
Data
Protection
for
mySAP.com®
Technology
Installation
&
User’s
Guide
for
DB2
UDB
Version
3
Release
3.
11
SC33-6341-04
���
-
IBM
Tivoli
Storage
Manager
for
Enterprise
Resource
Planning
(5698–APR)
Data
Protection
for
mySAP.com®
Technology
Installation
&
User’s
Guide
for
DB2
UDB
Version
3
Release
3.
11
SC33-6341-04
���
-
Fifth
Edition
(April
2004)
This
edition
applies
to
Data
Protection
for
mySAP.com
technology
Version
3
Release
3
Modification
Level
11
(product
number
5698–DPR),
available
as
a
licensed
program
product,
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
Order
publications
through
your
IBM
representative
or
the
IBM
branch
office
serving
your
area.
Publications
are
not
stocked
at
the
addresses
given
below.
A
form
for
readers’
comments
is
provided
at
the
back
of
this
publication.
If
the
form
has
been
removed,
address
your
comments
to:
IBM
Deutschland
Entwicklung
GmbH
Enterprise
Solution
Development
Dept.
3848,
Bldg.
71032-05
Schoenaicher
Str.
220
71032
Boeblingen
Germany
FAX
(Germany):
07031
16
3619
FAX
(other
countries):
(+49)
7031
16
3619
Internet
Web
page:
http://www.ibm.com/software/tivoli
Make
sure
to
include
the
following
in
your
comment
or
note:
v
Title
and
order
number
of
this
book
v
Page
number
or
topic
related
to
your
comment
When
you
send
information
to
IBM,
you
grant
IBM
a
non-exclusive
right
to
use
or
distribute
the
information
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
©
Copyright
International
Business
Machines
Corporation
1995,
2004.
All
rights
reserved.
US
Government
Users
Restricted
Rights
–
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Note!
Before
using
this
information
and
the
product
it
supports,
be
sure
to
read
the
general
information
under
“Notices”
on
page
xi.
||
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
-
Contents
Figures
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Tables
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. ix
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xi
Trademarks
and
Service
Marks
.
.
.
.
.
.
.
. xi
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
. xiii
Who
Should
Read
This
Book
.
.
.
.
.
.
.
. xiii
How
to
Read
This
Book
.
.
.
.
.
.
.
.
.
. xiii
Where
to
Find
More
Information
.
.
.
.
.
.
. xiii
Naming
Conventions
used
in
this
Documentation
xiii
Contents
of
the
Data
Protection
for
mySAP.com
Package
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xiv
Supported
Platforms
.
.
.
.
.
.
.
.
.
.
. xiv
Platform
Differences
.
.
.
.
.
.
.
.
.
.
. xiv
Part
1.
Data
Protection
Basics
.
.
.
. 1
Chapter
1.
Concepts
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
. 3
DP
for
mySAP.com
and
DB2
BACKUP
DATABASE
and
RESTORE
DATABASE
.
.
.
.
.
.
.
.
. 3
DP
for
mySAP.com
and
BRARCHIVE
/
BRRESTORE
5
Chapter
2.
Developing
a
Backup
Strategy
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Types
of
Failures
and
the
Scope
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Trimming
the
Database
Size
.
.
.
.
.
.
.
. 8
Transaction
Rate
.
.
.
.
.
.
.
.
.
.
.
. 8
Backup
Windows
and
Recovery
Time
.
.
.
.
. 8
Implementing
the
Strategy
by
Scheduling
Automated
Backup
Runs
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
Scheduling
Products
.
.
.
.
.
.
.
.
.
.
. 9
Sample
Backup
Strategy
for
Daily
Backup
Processing
.
.
.
.
.
.
.
.
.
.
.
.
.
. 10
Chapter
3.
Introducing
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
. 11
Scope
of
Data
Protection
for
mySAP.com
.
.
.
. 12
Integration
of
Data
Protection
for
mySAP.com
with
SAP
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 12
Storing
Data
on
a
TSM
Server
.
.
.
.
.
.
.
. 13
Performance
Options
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
. 14
Parallel
(Multiple)
Sessions
.
.
.
.
.
.
.
. 15
Multiple
(Parallel)
Network
Paths
and
Multiple
(Parallel)
Servers
.
.
.
.
.
.
.
.
.
.
. 15
Incremental
and
Delta
Backup
.
.
.
.
.
.
. 15
RL
Compression
.
.
.
.
.
.
.
.
.
.
.
. 15
Automation
Options
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
. 15
Selectable
Management
Classes
.
.
.
.
.
.
. 15
Retain
Backups
by
Version
.
.
.
.
.
.
.
. 15
Multiple
DB2
Log
File
Copies
.
.
.
.
.
.
. 15
Alternate
Network
Paths
and
Servers
.
.
.
.
. 16
Messaging
.
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Productivity
Options
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Reporting
.
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Monitoring
the
Backup
Status
.
.
.
.
.
.
. 16
Performance
Analysis
.
.
.
.
.
.
.
.
.
. 16
Managing
Data
on
the
Backup
Server
.
.
.
. 16
Using
FlashCopy
to
Minimize
Backup
and
Restore
Windows
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 17
Integration
with
Data
Protection
for
IBM
Enterprise
Storage
Server
(ESS)
for
mySAP.com
. 17
Archiving
Inactive
Data
.
.
.
.
.
.
.
.
.
. 17
Part
2.
Installing
and
Using
.
.
.
.
. 19
Chapter
4.
Installing
or
Upgrading
Data
Protection
for
mySAP.com
.
.
.
.
.
. 21
Prerequisites
for
the
Installation
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
. 21
Installation
Planning
for
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
. 22
Installing
Data
Protection
for
mySAP.com
.
.
.
. 23
Initial
Installation
.
.
.
.
.
.
.
.
.
.
. 23
Upgrade
Installation
(Migration)
.
.
.
.
.
. 23
Installing
Data
Protection
for
mySAP.com
on
UNIX
(AIX,
Solaris)
.
.
.
.
.
.
.
.
.
. 23
Installing
Data
Protection
for
mySAP.com
on
Windows
.
.
.
.
.
.
.
.
.
.
.
.
.
. 24
Post-Installation
Steps
.
.
.
.
.
.
.
.
.
.
. 25
Review
of
the
TSM
Options
Files
.
.
.
.
.
. 26
Set
the
Password
.
.
.
.
.
.
.
.
.
.
. 26
Optional:
Restart
DB2
Instance
.
.
.
.
.
.
. 26
Verify
the
Installation
.
.
.
.
.
.
.
.
.
. 27
Upgrading
(Migration)
.
.
.
.
.
.
.
.
.
. 27
Upgrading
Data
Protection
for
mySAP.com
.
.
. 27
Migration
of
the
DP
for
mySAP.com
Profile
.
. 27
Creation
of
Configuration
Files
.
.
.
.
.
.
. 28
Special
Installation
.
.
.
.
.
.
.
.
.
.
.
. 29
Silent
Installation
.
.
.
.
.
.
.
.
.
.
. 29
Console
Installation
.
.
.
.
.
.
.
.
.
.
. 29
Firewall
Installation
.
.
.
.
.
.
.
.
.
. 29
Uninstalling
Data
Protection
for
mySAP.com
.
.
. 30
Uninstalling
Data
Protection
for
mySAP.com
from
UNIX
(AIX,
Solaris)
.
.
.
.
.
.
.
.
. 30
Uninstalling
Data
Protection
for
mySAP.com
from
Windows
.
.
.
.
.
.
.
.
.
.
.
. 30
Chapter
5.
Adjusting
Your
System
.
.
. 31
General
Performance
Considerations
.
.
.
.
.
. 31
Database
Server
Considerations
.
.
.
.
.
. 32
©
Copyright
IBM
Corp.
1995,
2004
iii
||
||||||||
|||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-
Network
Considerations
.
.
.
.
.
.
.
.
. 32
Backup
Server
Considerations
.
.
.
.
.
.
. 32
Adjustments
to
DP
for
mySAP.com
for
Improving
Performance
of
Data
Transfer
.
.
.
.
.
.
.
. 33
Multiplexing
.
.
.
.
.
.
.
.
.
.
.
.
. 34
Multiple
Sessions
.
.
.
.
.
.
.
.
.
.
. 34
Multiple
Network
Paths
.
.
.
.
.
.
.
.
. 35
Multiple
(Parallel)
Servers
.
.
.
.
.
.
.
. 35
Compression
.
.
.
.
.
.
.
.
.
.
.
.
. 36
Buffer
Size
.
.
.
.
.
.
.
.
.
.
.
.
.
. 36
Adjustments
for
Interaction
with
Other
Components
37
Adjustments
for
the
Administration
Assistant
.
. 37
Adjustments
for
Tivoli
Storage
Manager
.
.
.
. 37
Rules
for
Adjustments
in
the
DP
for
mySAP.com
Environment
.
.
.
.
.
.
.
.
.
.
.
.
.
. 39
Chapter
6.
Data
Protection
for
mySAP.com
Backup
Object
Manager
.
. 43
Backup
Object
Manager
Setup
.
.
.
.
.
.
.
. 44
Managing
Backup
Objects
.
.
.
.
.
.
.
.
. 45
Backup
Object
Manager
Commands
.
.
.
.
. 45
Backup
Object
Manager
Command
Options
.
. 47
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
. 49
Problem
Resolution
when
using
the
Backup
Object
Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 50
Chapter
7.
Using
the
Administration
Assistant
for
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
. 51
General
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
Prerequisites
.
.
.
.
.
.
.
.
.
.
.
.
.
. 52
Installation
.
.
.
.
.
.
.
.
.
.
.
.
.
. 53
Installing
the
Administration
Assistant
Server
(Base
Installation)
.
.
.
.
.
.
.
.
.
.
. 53
Installing
the
Administration
Assistant
NLS
Package
(optional)
.
.
.
.
.
.
.
.
.
.
. 56
Specifying
a
new
Administration
Assistant
Server
for
Data
Protection
for
mySAP.com
.
.
.
.
.
. 56
Verifying
the
Installation
.
.
.
.
.
.
.
.
.
. 57
Authorizing
Administration
Assistant
Users
.
.
. 58
Using
the
Administration
Assistant
.
.
.
.
.
. 58
Uninstalling
the
Administration
Assistant
.
.
.
. 58
Part
3.
Appendixes
.
.
.
.
.
.
.
.
. 59
Appendix
A.
The
Data
Protection
for
mySAP.com
Profile
.
.
.
.
.
.
.
.
. 61
Keyword
Reference
.
.
.
.
.
.
.
.
.
.
.
. 61
Sample
Data
Protection
for
mySAP.com
Profiles
.
. 67
Sample
Data
Protection
for
mySAP.com
Profile
for
Unix
.
.
.
.
.
.
.
.
.
.
.
.
.
. 67
Sample
Data
Protection
for
mySAP.com
Profile
for
Windows
.
.
.
.
.
.
.
.
.
.
.
.
. 70
Appendix
B.
Using
Data
Protection
for
mySAP.com
to
Back
Up
and
Restore
Files
and
Databases
.
.
.
.
.
.
.
.
. 73
73
Starting
a
Backup
.
.
.
.
.
.
.
.
.
.
. 73
Starting
a
Restore
.
.
.
.
.
.
.
.
.
.
. 74
Appendix
C.
Data
Protection
for
mySAP.com
Messages
.
.
.
.
.
.
.
. 77
How
To
Find
Message
Files
(Log
Files)
.
.
.
.
. 77
Data
Protection
for
mySAP.com
Message
Explanations
.
.
.
.
.
.
.
.
.
.
.
.
.
. 78
Appendix
D.
Troubleshooting
.
.
.
.
. 95
Problem
Resolution
during
Installation
and
Setup
95
Understanding
The
Setup
.
.
.
.
.
.
.
. 95
Location
of
Log
Files
.
.
.
.
.
.
.
.
.
. 97
General
Problem
Resolution
.
.
.
.
.
.
.
. 98
Problem
Resolution
During
Operation
.
.
.
.
. 100
Reproducable
(Repeatable)
Problems
.
.
.
. 100
Random
problems
.
.
.
.
.
.
.
.
.
.
. 101
Contacting
Your
IBM
/
Tivoli
Support
.
.
.
.
. 101
Appendix
E.
Data
Protection
for
mySAP.com
Setup
Examples
.
.
.
.
. 103
Sample
DB2
Vendor
INI
File
.
.
.
.
.
.
.
. 103
Rules
for
Adjustments
in
the
DP
for
mySAP.com
Environment
with
DB2
UDB
Version
7.x
.
.
.
. 103
Appendix
F.
Installation
Planning
Sheet
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 105
Appendix
G.
Alternate/Parallel
Backup
Paths
and
Backup
Servers
.
.
.
.
. 107
Parameter
Settings
-
SERVER
Statement
.
.
.
. 108
EXAMPLE
1:
Use
of
Alternate
Paths
for
Increased
Availability
.
.
.
.
.
.
.
.
.
. 109
EXAMPLE
2:
Use
of
Parallel
Paths
for
Increased
Performance
.
.
.
.
.
.
.
.
.
.
.
.
. 111
EXAMPLE
3:
Use
of
Alternate
Servers
for
Disaster
Recovery
.
.
.
.
.
.
.
.
.
.
. 112
Appendix
H.
Preparing
Tivoli
Storage
Manager
for
DP
for
mySAP.com
.
.
. 113
Configuring
the
Tivoli
Storage
Manager
Server
.
. 113
General
Considerations
for
TSM
.
.
.
.
.
. 113
Prerequisites
.
.
.
.
.
.
.
.
.
.
.
.
. 114
Adjusting
your
TSM
for
DP
for
mySAP.com
.
. 114
Configuring
the
Tivoli
Storage
Manager
Clients
.
. 117
General
Considerations
.
.
.
.
.
.
.
.
. 117
Tivoli
Storage
Manager
Clients
on
UNIX
Systems
.
.
.
.
.
.
.
.
.
.
.
.
.
. 117
Tivoli
Storage
Manager
Clients
on
Windows
Systems
.
.
.
.
.
.
.
.
.
.
.
.
.
. 118
Password
Handling
.
.
.
.
.
.
.
.
.
.
. 119
Password
Configuration
Matrix
(UNIX)
.
.
. 120
Password
Configuration
Matrix
(Windows)
.
. 121
Appendix
I.
Sample
Tivoli
Storage
Manager
Profiles
.
.
.
.
.
.
.
.
.
. 123
Sample
TSM
Profiles
for
UNIX
.
.
.
.
.
.
. 123
Client
User
Options
File
Sample
(dsm.opt)
.
. 123
Client
System
Options
File
Sample
(dsm.sys)
123
iv
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-
Include/Exclude
List
Sample
.
.
.
.
.
.
. 123
Sample
TSM
Profiles
for
Windows
.
.
.
.
.
. 124
Client
User
Options
File
Sample
(dsm.opt)
.
. 124
Client
Options
Files
Sample
(.opt)
.
. 124
Include/Exclude
List
Sample
.
.
.
.
.
.
. 125
Appendix
J.
Backup
Scheduling
Examples
.
.
.
.
.
.
.
.
.
.
.
.
. 127
UNIX
Crontab
Example
.
.
.
.
.
.
.
.
.
. 127
Elements
of
Backup
Schedules
for
UNIX
.
.
.
. 127
Crontab
File
Sample
.
.
.
.
.
.
.
.
.
. 127
Full
Offline
Backup
Shell
Script
Sample
.
.
. 128
Windows
Scheduling
Example
.
.
.
.
.
.
.
. 128
Elements
of
Backup
Schedules
for
Windows
.
.
. 129
Schedule
Batch
Sample
.
.
.
.
.
.
.
.
. 129
Full
Offline
Backup
Batch
File
Sample
.
.
.
. 129
Appendix
K.
Hints
and
Tips
for
Network
Settings
.
.
.
.
.
.
.
.
.
. 131
Networks
with
Large
Bandwidth-Delay
Product
131
SP
Switch
(RISC
6000)
.
.
.
.
.
.
.
.
.
. 132
Network
Settings
of
the
Tivoli
Storage
Manager
132
Glossary
.
.
.
.
.
.
.
.
.
.
.
.
. 133
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 137
Contents
v
-
vi
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
-
Figures
1.
DB2
UDB
Backup
Architecture
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4
2.
DB2
UDB
Log
File
Management
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
3.
DB2
UDB
Backup
Objects
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
4.
Production
Backup
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 10
5.
Scope
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 12
6.
Integration
of
Data
Protection
for
mySAP.com
with
DB2
UDB
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 13
7.
Data
Throughput
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 31
8.
Simplified
Data
Transfer
for
a
Backup
/
Restore
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 33
9.
Multiplexing
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 34
10.
Parallel
(Multiple)
Sessions
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 34
11.
Parallel
(Multiple)
Paths
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 35
12.
Parallel
(Multiple)
Servers
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 36
13.
Null
Block
Compression
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 36
14.
Data
Protection
for
mySAP.com
Backup
Object
Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 44
15.
Example
of
an
mySAP.com
Landscape
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 51
16.
Administration
Assistant
Server
Setup
(Base
Installation)
—
Specify
Ports
.
.
.
.
.
.
.
.
.
.
.
.
. 54
17.
Administration
Assistant
Server
Setup
(Base
Installation):
Correct
Hostname
Panel
.
.
.
.
.
.
.
.
.
. 55
18.
Administration
Assistant
Server
Setup
–
Destination
Directory
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 56
19.
Starting
the
Administration
Assistant
with
Netscape
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 57
20.
Administration
Assistant
Start
Panel
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 57
21.
SAP
and
Data
Protection
Configuration
files
on
UNIX
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 96
22.
General
Problem
Isolation
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 98
©
Copyright
IBM
Corp.
1995,
2004
vii
||||||
||||
||||
-
viii
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
-
Tables
1.
SERVER
Statement
and
Appropriate
Profile
and
Option
File
Settings.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 108
2.
Password
Handling
for
UNIX
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 120
3.
Password
Handling
for
Windows
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 121
4.
Tuning
of
Network
Settings
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 131
5.
Tuning
of
SP
Switch
Buffer
Pools
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 132
6.
Tuning
Tivoli
Storage
Manager
Configuration
File
Attributes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 132
©
Copyright
IBM
Corp.
1995,
2004
ix
||||
-
x
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
-
Notices
References
in
this
publication
to
IBM®
products,
programs,
or
services
do
not
imply
that
IBM
intends
to
make
these
available
in
all
countries
in
which
IBM
operates.
Any
reference
to
an
IBM
product,
program,
or
service
is
not
intended
to
state
or
imply
that
only
that
IBM
product,
program,
or
service
may
be
used.
Any
functionally
equivalent
product,
program,
or
service
that
does
not
infringe
any
of
the
intellectual
property
rights
of
IBM
may
be
used
instead
of
the
IBM
product,
program,
or
service.
The
evaluation
and
verification
of
operation
in
conjunction
with
other
products,
except
those
expressly
designated
by
IBM,
are
the
responsibility
of
the
user.
IBM
may
have
patents
or
pending
patent
applications
covering
subject
matter
in
this
document.
The
furnishing
of
this
document
does
not
give
you
any
license
to
these
patents.
You
can
send
license
inquiries,
in
writing,
to
IBM
Director
of
Licensing
IBM
Corporation
North
Castle
drive
Armonk,
NY
10504-1785
U.S.A
Any
references
in
this
information
non-IBM
Web
sites
are
provided
for
convenience
only
and
do
not
in
any
manner
serve
as
an
endorsement
of
those
Web
sites.
The
materials
at
those
Web
sites
are
not
part
of
the
materials
for
this
product
and
use
of
those
Web
sites
is
at
your
own
risk.
If
you
are
viewing
this
information
in
softcopy
form,
the
photographs
and
color
illustrations
may
not
appear.
Licensees
of
this
program
who
wish
to
have
information
about
it
for
the
purpose
of
enabling:
(i)
the
exchange
information
between
independently
created
programs
and
other
programs
(including
this
one)
and
(ii)
the
mutual
use
of
the
information
which
has
been
exchanged,
should
contact:
IBM
Deutschland
Informationssysteme
GmbH
Department
0215
Pascalstr.
100
70569
Stuttgart
Germany
Such
information
may
be
available,
subject
to
appropriate
terms
and
conditions,
including
in
some
cases
payment
of
a
fee.
Trademarks
and
Service
Marks
The
following
terms
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States
or
other
countries
or
both:
v
AFS
v
DB2
Universal
Database
v
AIX
v
IBM
v
RS/6000
v
SP
v
Tivoli
©
Copyright
IBM
Corp.
1995,
2004
xi
-
Solaris,
Java
and
all
Java-based
trademarks
and
logos
are
trademarks
or
registered
trademarks
of
Sun
Microsystems,
Incorporated,
in
the
United
States,
other
countries,
or
both.
R/3
and
mySAP.com
are
registered
trademarks
of
SAP
AG
in
Germany,
other
countries
or
both.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Microsoft,
Windows,
Windows
NT,
and
Windows
2000
are
registered
trademarks
of
Microsoft
Corporation
in
the
United
States,
other
countries,
or
both.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
xii
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
-
Preface
Who
Should
Read
This
Book
This
manual
is
intended
for
system
programmers
and
administrators
who
are
responsible
for
implementing
a
backup
solution
in
the
mySAP.com
environment
using
the
Tivoli
Storage
Manager.
It
explains
the
procedures
needed
to
install
and
customize
Data
Protection
for
mySAP.com,
the
interface
between
mySAP.com
and
the
Tivoli
Storage
Manager.
The
reader
should
be
familiar
with
mySAP.com,
Tivoli
Storage
Manager,
and
DB2
Universal
Database
(DB2
UDB)
documentation.
How
to
Read
This
Book
The
manual
is
split
into
three
parts,
of
which
the
first
is
a
general
introduction
into
data
protection,
the
second
describes
the
installation,
the
architecture
and
properties
of
Data
Protection
for
mySAP.com
and
the
third
part
(Appendices)
gives
reference
information.
The
Appendices
are
grouped
as
follows:
Appendix
A
to
F
refer
to
Data
Protection
for
mySAP.com,
Appendices
G
and
H
refer
to
TSM
and
Appendix
I
refers
to
scheduling.
If
you
are
a
person
experienced
in
data
protection,
you
might
want
to
skip
chapters
1
and
2,
however
you
may
want
to
browse
chapter
3
for
new
functions.
The
information
given
in
part
2
is
for
system
programmers
and
administrators
who
know
how
Data
Protection
for
mySAP.com
is
embedded
in
a
comprehensive
data
protecting
system.
If
you
are
a
data
protection
novice,
you
might
want
to
start
reading
the
publication
from
part
one
on.
This
way
you
get
introductional
information
of
what
protecting
your
data
means
and
what
needs
to
be
considered
while
setting
up
a
data
protection
system.
Where
to
Find
More
Information
For
more
information
about
Data
Protection
for
mySAP.com,
please
refer
to
the
Tivoli
Internet
home
page
at
http://www.ibm.com/software/tivoli/products/storage-mgr-erp/.
Note:The
most
up-to-date
version
of
this
book
is
available
on
the
Tivoli
software
information
center
at
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html.Look
under
’S’
for
’IBM
Tivoli
Storage
Manager
for
Enterprise
Resource
Planning’.
Naming
Conventions
used
in
this
Documentation
In
this
documentation,
″IBM
Tivoli
Storage
Manager
for
Enterprise
Resource
Planning
Data
Protection
for
mySAP.com
Technology″
is
usually
referred
to
as
″Data
Protection
for
mySAP.com″
or
″DP
for
mySAP.com″.In
this
documentation,
IBM
Tivoli
Storage
Manager
is
usually
referred
to
as
″Tivoli
Storage
Manager″
or
″TSM″.
©
Copyright
IBM
Corp.
1995,
2004
xiii
||
|
||||||
|||||
||||
http://www.ibm.com/software/tivoli/products/storage-mgr-erp/http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
-
Unless
otherwise
stated,
references
in
this
publication
to
UNIX®
apply
to
all
supported
UNIX-based
systems,
and
references
to
Windows®
apply
to
all
supported
Windows
platforms.
Contents
of
the
Data
Protection
for
mySAP.com
Package
The
Data
Protection
for
mySAP.com
package
includes
this
manual
and
machine
readable
material
on
a
CD-ROM.
See
the
README
file
for:
v
A
table
of
contents
of
the
package
v
Up-to-date
news
Supported
Platforms
For
a
list
of
supported
platforms
see
the
Release
Notice
(RELNOTE),
contained
in
your
mySAP.com
package.
Platform
Differences
There
are
only
small
differences
between
the
UNIX
and
Windows
versions
of
Data
Protection
for
mySAP.com.
One
of
these
differences
is
that
UNIX
uses
the
path
separator
″/″
compared
with
″\″
for
Windows
and
that
the
drive
letter
is
specified
for
Windows.
Non-trivial
differences
between
the
UNIX
and
Windows
versions
of
Data
Protection
for
mySAP.com
are
mentioned
explicitly.
xiv
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
|||
||
-
Part
1.
Data
Protection
Basics
©
Copyright
IBM
Corp.
1995,
2004
1
-
2
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
-
Chapter
1.
Concepts
of
Data
Protection
for
mySAP.com
This
chapter
explains
how
Data
Protection
for
mySAP.com
integrates
with
the
backup
and
restore
processes
of
DB2
and
the
SAPDBA
tools.
It
is
intended
as
a
supplement
to
your
mySAP.com,
DB2
UDB,
and
Tivoli
Storage
Manager
documentation.
If
you
are
already
experienced
in
Data
Protection
for
mySAP.com
for
DB2
UDB,
you
might
want
to
move
on
to
the
next
chapter.
DB2
backups
are
initiated
by
the
DB2
BACKUP
DATABASE
command.
DB2
backups
can
be
done
online
or
offline,
partial
or
full,
as
a
complete,
incremental,
or
as
a
delta
backup.
For
discussion
of
these
alternatives,
please
refer
to
your
DB2
documentation.
DB2
UDB
databases
are
restored
with
the
DB2
RESTORE
DATABASE
command.
DB2
restores
can
be
partial
or
full,
using
complete,
incremental,
or
delta
backups.
Partial
restores
can
be
done
online
or
offline;
full
restores
must
be
done
offline.
The
backup
of
DB2
offline
log
files
is
provided
by
the
SAPDBA
tool
BRARCHIVE,
the
restore
of
DB2
offline
log
files
is
provided
by
BRRESTORE.
DP
for
mySAP.com
and
DB2
BACKUP
DATABASE
and
RESTORE
DATABASE
The
DB2
Command
Line
Processor
(CLP)
interprets
commands
for
the
DB2
database
and
passes
control
to
a
DB2
Server
Process.
This
process
triggers
the
backup
or
restore,
loads
the
Data
Protection
for
mySAP.com
shared
library
dynamically
and
communicates
with
it
through
the
Vendor
API.
For
starting
a
backup
or
restore,
the
DB2
CLP
communicates
with
the
DB2
Server
Process,
providing
the
Server
Process
with
the
relevant
information
for
processing
the
data
base.
©
Copyright
IBM
Corp.
1995,
2004
3
|
|
||||
||
||||
|||
||
||
|
||||
||||
-
For
a
BACKUP
DATABASE
command,
the
DB2
Server
Process
v
creates
a
unique
timestamp
to
identify
the
backup
v
loads
Data
Protection
for
mySAP.com
dynamically
as
a
shared
library
v
reads
the
data
from
the
database
containers
v
reads
the
DB2
configuration
files
v
creates
data
blocks
containing
the
backup
image
and
passes
these
blocks
to
the
data
mover
part
of
DP
for
mySAP.com.
The
Data
Protection
for
mySAP.com
shared
library
passes
the
data
blocks
on
to
Tivoli
Storage
Manager
(TSM),
that
writes
the
data
blocks
to
the
storage
media
(tape
or
disk).At
the
end
of
the
backup
process,
the
DB2
Server
Process
logs
the
backup
in
the
Recovery
History
File.
For
a
RESTORE
DATABASE
command,
the
DB2
Server
Process
v
loads
Data
Protection
for
mySAP.com
dynamically
as
a
shared
library
v
requests
the
backup
data
from
the
shared
library
The
Data
Protection
for
mySAP.com
shared
library
v
checks
with
the
Tivoli
Storage
Manager
if
the
backup
image
is
available
v
retrieves
the
data
blocks
from
TSM
Figure
1.
DB2
UDB
Backup
Architecture
4
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
|
|
|
|
|
||
|||||
|
|
|
|
|
|
-
v
passes
the
data
blocks
to
the
DB2
Server
Process
The
DB2
Server
Process
v
restores
the
DB2
data
to
the
database
containers
v
logs
the
restore
in
the
Recovery
History
File
DP
for
mySAP.com
and
BRARCHIVE
/
BRRESTORE
DB2
log
files
in
a
mySAP.com
environment
can
have
four
different
states
during
their
life
cycle.
v
online
active
The
log
file
is
currently
being
used
by
DB2
for
logging
transactions.
v
online
retained
The
log
file
is
no
longer
being
used
for
logging
transactions,
but
it
contains
transactions
with
data
pages
that
have
not
yet
been
written
from
the
buffer
pool
to
disk.
It
will
be
needed
by
DB2
in
case
of
a
crash
recovery
or
for
roll-back.The
DB2
logging
user
exit
is
called
by
DB2
(if
configured)
to
copy
a
filled
online
log
file
to
the
log_archive
directory.Do
not
use
operating
system
commands
for
copying
online
log
files!
v
offline
retained
The
log
file
is
no
longer
being
used
by
DB2
and
does
not
contain
transactions
with
unwritten
data
pages.
It
is
not
crucial
for
a
crash
recovery
or
a
roll-back.
After
the
log
file
has
been
successfully
copied
to
the
log_archive
path
DB2
may
eventually
delete
the
log
file.
v
archived
retained
BRARCHIVE
has
successfully
archived
offline
retained
log
files
to
an
external
storage
medium,
for
example
Tivoli
Storage
Manager
or
a
tape
device.
SAP
utilities
support
the
backup
of
DB2
log
files:
Filled
or
closed
online
log
files
are
immediately
copied
from
the
log_dir
directory
by
the
DB2
logging
user
exit
to
Figure
2.
DB2
UDB
Log
File
Management
Chapter
1.
Concepts
of
Data
Protection
5
|
|
|
|
||
||
||
|||||||
|||||
|||
|
||
-
the
log_archive
directory.
Offline
log
files
are
backed
up
from
the
log_archive
directory
with
the
SAP
tool
BRARCHIVE.
Archived
retained
log
files
are
restored
with
the
SAP
tool
BRRESTORE.
For
a
detailed
description
of
the
DB2
logging
user
exit
functionality
and
of
the
SAP
utilities
BRARCHIVE
and
BRRESTORE,
refer
to
the
Database
Administration
Guide
in
your
mySAP.com
documentation.
For
archiving
DB2
log
files
(BRARCHIVE),
the
SAP
tool
v
creates
a
unique
timestamp
for
identification;
v
loads
Data
Protection
for
mySAP.com
dynamically
as
a
shared
library.
The
Data
Protection
for
mySAP.com
shared
library:
v
reads
the
data
from
file
v
creates
data
blocks
v
passes
the
data
blocks
on
to
TSM.
Tivoli
Storage
Manager
writes
the
data
blocks
to
the
storage
media
(preferably
disk).
The
SAP
tool
logs
the
archive
run
in
the
SAP
administration
database.
For
retrieving
logs
(BRRESTORE),
the
SAP
tool
v
loads
Data
Protection
for
mySAP.com
dynamically
as
a
shared
library
v
requests
the
backup
data
from
the
shared
library.
The
Data
Protection
for
mySAP.com
shared
library
v
checks
with
the
Tivoli
Storage
Manager
if
the
requested
log
file
data
is
available
v
retrieves
the
data
blocks
from
TSM
v
writes
the
data
blocks
to
a
file
on
disk.
The
SAP
tool
logs
the
retrieve
run
in
the
SAP
administration
database.
6
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
|||
|||
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
-
Chapter
2.
Developing
a
Backup
Strategy
This
chapter
helps
you
define
an
appropriate
backup
strategy
for
your
mySAP.com
system.
If
you
already
have
a
successful
backup
strategy
in
place
you
may
want
to
move
on
to
the
next
chapter.
The
strategy
you
choose
is
dependent
on
your
specific
requirements.
Consider
the
following
questions:
v
What
type
of
events
do
you
wish
to
protect
your
mySAP.com
system
against?
v
How
large
is
your
database?
v
What
is
the
transaction
rate
of
your
database?
v
How
fast
do
you
need
to
recover
from
a
failure?
v
What
backup
windows
are
available?
Types
of
Failures
and
the
Scope
of
Data
Protection
for
mySAP.com
In
case
of
a
corrupted
database
(user
errors
or
transaction
failures),
you
may
want
to
restore
the
database
to
a
specific
point
in
time.
In
this
case,
it
is
sufficient
to
restore
the
database
and
configuration
files.
To
do
this,
a
backup
image
of
the
database
and
the
corresponding
DB2
log
files
are
required.
When
storage
hardware
failures
occur,
you
may
want
to
restore
the
database
to
the
latest
possible
point
in
time.
In
this
case,
you
may
also
need
to
restore
database
executables,
mySAP.com
system
data
and
user
data
in
addition
to
the
database
image
and
the
DB2
log
files.
For
disaster
recovery,
you
will
need
to
restore
all
operating
system
data
and
all
of
the
above.
Data
Protection
for
mySAP.com
solely
covers
the
backup
and
restore
of
mySPA.com
database
objects,
as
shown
in
Figure
3.
Figure
3.
DB2
UDB
Backup
Objects
©
Copyright
IBM
Corp.
1995,
2004
7
|||||||||
|||
-
Please
note
that
there
is
no
provision
for
backing
up
online
DB2
log
files
that
are
required
for
crash
recovery.
Therefore,
it
is
recommended
to
place
the
DB2
log
directory
on
a
mirrored
disk.
In
order
to
protect
the
system
against
the
loss
of
mySAP.com
executables,
user
data,
or
even
operating
system
data
you
should
use
the
incremental
backup
capabilities
of
the
Tivoli
Storage
Manager
backup-archive
client
with
its
selective
incremental
backup
capabilities.
The
Tivoli
Storage
Manager
selective
incremental
backup
function
allows
you
to
define
an
include-exclude
list
of
files
that
is
applied
automatically
during
incremental
backup
operations.
For
further
information
about
include-exclude
lists,
see
your
Tivoli
Storage
Manager
manuals,
using
the
backup-archive
clients.
This
list
should
be
used
to
exclude
data
already
stored
using
Data
Protection
for
mySAP.com,
i.e.
all
database
files,
such
as
containers
and
offline
log
files.
Examples
of
include-exclude
lists
for
UNIX
can
be
found
in
Sample
TSM
Profiles
for
UNIX
(see
“Sample
TSM
Profiles
for
UNIX”
on
page
123)
and
for
Windows
in
Sample
TSM
Profiles
for
Windows
“Sample
TSM
Profiles
for
Windows”
on
page
124.
Sample
files
can
also
be
found
in
your
Data
Protection
for
mySAP.com
installation
package.
In
order
to
be
protected
against
the
complete
loss
of
the
operating
system,
for
example
in
the
case
of
a
storage
hardware
failure,
it
is
imperative
that
after
the
installation
of
the
operating
system
or
after
updates/upgrades
of
the
operating
system,
system
backups
are
made
with
the
operating
system
utilities,
e.g.
mksysb
for
AIX.
This
will
allow
you
to
start
your
system
from
the
backup
medium.
Base
backups
should
include
a
configured
TCP/IP
environment
as
well
as
the
Tivoli
Storage
Manager
client
including
the
API
in
order
to
be
able
to
restore
all
other
data.
Trimming
the
Database
Size
Obviously,
backing
up
and
restoring
large
databases
takes
longer
than
backing
up
and
restoring
smaller
databases.
Therefore,
you
may
want
to
consider
off-loading
inactive
data
to
an
archive.
DB2
CommonStore
for
SAP,
a
companion
product
to
Data
Protection
for
mySAP.com,
provides
this
functionality.
See
also
“Archiving
Inactive
Data”
on
page
17
and
http://www.ibm.com/software/data/commonstore/sap/.
Transaction
Rate
Due
to
high
transaction
rates,
mySAP.com
databases
usually
require
frequent
database
and
log
file
backups
Backup
Windows
and
Recovery
Time
Your
backup
strategy
usually
has
two
main
objectives:
v
Minimize
down-time
after
a
failure.
v
Minimize
the
impact
of
backup
activity
on
the
application.
These
are
conflicting
goals:
Generally,
recovery
is
fastest
when
an
up-to-date
full
backup
is
available,
and
only
few
or
no
log
files
need
to
be
applied.
Offline
backups
need
the
database
to
go
off-line.
If
your
database
needs
to
stay
on-line
all
the
time,
online
backups
must
be
employed.
They
take
more
time
as
they
share
system
resources
with
the
application.
It
should
also
be
noted
that
online
backups
contain
inconsistent
data.
After
restoring
an
online
backup,
the
database
must
be
rolled
forward
to
consistency
by
applying
the
log
files
generated
during
the
8
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
||||
|
|||
||||||
http://www.ibm.com/software/data/commonstore/sap/
-
backup
window.
Incremental
and
delta
backups
take
less
time
than
do
full
backups,
but
recovery
time
is
longer:
An
incremental
backup
saves
the
data
changed
since
the
latest
full
backup.
For
recovery
using
an
incremental
backup,
the
latest
full
backup
and
the
incremental
backup
must
be
restored.
A
delta
backup
saves
the
data
since
the
latest
backup.
For
recovery
using
a
delta
backup,
the
latest
full
backup
and
all
intermediate
delta
backups
must
be
restored.
Delta
backups
may
be
advisable
after
only
limited
changes
to
the
data.
The
longer
the
intervals
between
backups,
the
more
log
files
need
to
be
applied
in
order
to
roll
forward
a
database,
adding
to
the
time
required
for
recovery.
Therefore,
choose
backup
intervals
that
allow
you
to
guarantee
acceptable
recovery
results
while
not
using
up
too
many
database
resources.
Implementing
the
Strategy
by
Scheduling
Automated
Backup
Runs
To
ensure
that
all
your
data
will
be
backed
up
regularly
at
a
certain
time,
it
is
recommended
that
you
schedule
automated
backup
and
archive
operations.
Scheduling
Products
There
are
several
products
that
can
be
used
to
set
up
a
schedule,
for
example:
v
SAP
scheduler
(CCMS)
v
UNIX
crontab
/
Windows
scheduler
v
Tivoli
Storage
Manager
scheduler
v
IBM
Tivoli
Workload
Scheduler
SAP
Scheduler
Within
mySAP.com,
the
Computer
Center
Management
System
(CCMS)
provides
a
scheduler
for
database
administration
and
backup
planning
on
a
single
database
server.
The
scheduler
can
be
started
from
the
SAPGUI
command
line
(transaction
code
db13)
or
with
the
SAPGUI
menu
functions
(Tools
->
CCMS
->
DB
administration
->
DBA
scheduling).
UNIX
crontab
/
Windows
Scheduler
Another
possibility
of
backup
automation
on
the
database
server
level
is
offered
by
the
cron
jobs
for
UNIX
systems
or
schedule
services
for
Windows.
An
example
of
a
cron
job
can
be
found
in
“UNIX
Crontab
Example”
on
page
127.
Tivoli
Storage
Manager
Scheduler
The
Tivoli
Storage
Manager
also
provides
functions
for
automating
operations
of
all
its
clients.
Therefore,
the
scope
of
control
can
comprise
multiple
database
servers.
Schedule
definition
work
can
be
done
quickly
using
the
GUI
based
Tivoli
Storage
Manager
Web
administrative
client.
When
a
schedule
is
defined,
it
will
be
assigned
to
a
specific
policy
domain.
More
than
one
schedule
for
each
policy
domain
can
be
defined.
For
this
purpose,
the
mySAP.com
database
client
requires
a
schedule
that
can
execute
command
files.
The
command
files
(for
example
shell
scripts
on
UNIX)
contain
sequences
of
commands
that
are
run
at
a
scheduled
start
date
and
time.
Information
on
how
to
define
Tivoli
Storage
Manager
schedules
can
be
found
in
the
Tivoli
Storage
Manager
Administrator’s
Reference
manual.
Chapter
2.
Developing
a
Backup
Strategy
9
|
||
|
|
||
-
IBM
Tivoli
Workload
Scheduler
The
IBM
Tivoli
Workload
Scheduler
provides
event-driven
automation,
monitoring,
and
job
control
for
both
local
and
remote
systems.
More
information
can
be
found
at
http://www.ibm.com/software/tivoli/products/scheduler/.
Sample
Backup
Strategy
for
Daily
Backup
Processing
The
following
figure
illustrates
the
sequence
of
backup
runs
you
may
want
to
establish
for
a
daily
backup
schedule.
This
example
of
automated
backup
operations
shows
the
following
typical
tasks
v
Full
database
backup,
e.g.,
offline
or
without
application
load,
performed
each
night.
v
Offline
redo
logs
backed
up
to
disk
during
online
hours.
This
has
the
advantage
of
eliminating
the
need
for
extra
tape
mounts
for
relatively
small
files.
Note
Backups
can
be
performed
to
disks
as
well
as
to
tape
environments.
Tivoli
Storage
Manager
will
manage
the
data
regardless
of
the
storage
media.
However,
it
is
recommended
that
the
mySAP.com
database
is
directly
backed
up
to
tape.
v
Within
Tivoli
Storage
Manager,
archived
log
files
are
migrated
from
disk
to
tape
after
the
full
database
backup.
v
SAP
system
files
are
backed
up
incrementally
with
the
Tivoli
Storage
Manager
backup-archive
client.
v
The
last
backup
in
the
daily
cycle
is
the
backup
of
the
Tivoli
Storage
Manager
database.
This
should
always
be
done.
Figure
4.
Production
Backup
Example
10
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
||||
||
http://www.ibm.com/software/tivoli/products/scheduler/
-
Chapter
3.
Introducing
Data
Protection
for
mySAP.com
This
chapter
explains
the
Data
Protection
for
mySAP.com
architecture
and
gives
an
introduction
to
the
product
features.
Even
if
you
are
an
experienced
user
of
Data
Protection
for
mySAP.com
you
may
want
to
browse
this
overview
for
new
features.
It
is
not
the
intent
of
this
chapter
to
explain
how
to
use
the
SAP
utilities.
Installation
and
configuration
of
Data
Protection
for
mySAP.com
is
covered
extensively
later
in
this
document.
See
Chapter
4,
“Installing
or
Upgrading
Data
Protection
for
mySAP.com,”
on
page
21
and
Chapter
5,
“Adjusting
Your
System,”
on
page
31.
Data
Protection
for
mySAP.com
together
with
TSM
provides
a
reliable,
high
performance
and
production
oriented
backup
and
restore
solution
that
allows
you
to
backup
and
restore
your
DB2–based
mySAP.com
systems.
It
is
integrated
with
DB2’s
backup
and
recovery
facilities
and,
specifically
for
mySAP.com
environments,
SAP
administration
tools
BRARCHIVE
and
BRRESTORE
to
allow
you
to
follow
SAP’s
recommended
backup
and
recovery
procedures.
Being
optimized
for
mySAP.com
databases,
Data
Protection
for
mySAP.com
allows
you
to
manage
large
volumes
of
data
most
efficiently.
©
Copyright
IBM
Corp.
1995,
2004
11
|
|
||||
|||||
||||||||
-
Scope
of
Data
Protection
for
mySAP.com
Data
Protection
for
mySAP.com
and
the
SAP
utilities
for
archiving
and
retrieving
DB2
log
files
are
focused
on
the
database
objects,
where
over
90
%
of
the
data
on
an
SAP
database
server
reside.
Thus
Data
Protection
for
mySAP.com
will
be
used
for
backup
and
restore
of
database
contents,
control
files,
and
offline
DB2
log
files.
(See
Figure
5).
Other
files
such
as
SAP
and
DB2
executables
can
be
backed
up
using
the
Tivoli
Storage
Manager
backup-archive
client.
As
a
consequence,
in
the
case
of
a
disaster
recovery,
you
have
to
make
sure
that
all
DB2
and
SAP
executables
are
available
before
starting
restore
and
recovery
of
your
database
using
the
Data
Protection
for
mySAP.com
and
the
SAP
utilities.
Integration
of
Data
Protection
for
mySAP.com
with
SAP
Once
being
configured
Data
Protection
for
mySAP.com
operates
as
an
invisible
link
between
DB2
and
the
mySAP.com
Database
Administration
Tools
on
one
hand
and
Tivoli
Storage
Manager
on
the
other.
A
shared
library
is
dynamically
linked
by
DB2
backup
processes
and
by
the
SAP
utilities.
See
following
graphic.
Figure
5.
Scope
of
Data
Protection
for
mySAP.com
12
Data
Protection
for
mySAP.com
Technology
Installation
&
User’s
Guide
for
DB2
UDB
||
|
|||||
|||||
||
|||||
-
The
Data
Protection
for
mySAP.com
package
also
contains
the
Administration
Assistant,
aimed
at
increasing
the
administrator’s
productivity.
The
Administration
Assistant
typically
resides
on
a
different
server
and
communicates
with
Data
Protection
for
mySAP.com
via
TCP/IP.
It
can
control
several
instances
of
Data
Protection
for
mySAP.com.
Its
functionality
covers
configuring
an
instance
of
Data
Protection
for
mySAP.com,
data
transfer
performance
monitoring
and
monitoring
of
the
backup
status
of
connected
mySAP.com
systems
as
well
as
the
TSM
server
activity
related
to
these
mySAP.com
systems.
It
allows
you
to
monitor
and
administer
all
of
your
Data
Protection
for
mySAP.com
instances
remotely
via
an
applet
running
in
a
web
browser.
You
may
register
an
SAP
instance
with
the
Administration
Assistant
during
installation.
For
information
on
how
to
register
at
a
later
time
or
with
a
different
Administration
Assistant,
refer
to
“Adjustments
for
the
Administration
Assistant”
on
page
37.
Storing
Data
on
a
TSM
Server
Data
Protection
for
mySAP.com
transfers
data
to
and
from
the
backup
server
via
a
single
session
or
via
multiple
(parallel)
sessions
to
a
TSM
server.
Each
session
must
have
a
storage
device
associated
with
it.
The
SAP
backup
ID
is
persistently
linked
with
each
backup
file.
This
backup
ID
can
be
used
later
to
determine
all
files
required
for
a
complete
restore.
Figure
6.
Integration
of
Data
Protection
for
mySAP.com
with
DB2
UDB
Chapter
3.
Introducing
Data
Protection
for
mySAP.com
13
||||||||
|||||
||
|||||
-
Note
In
SAP
terminology
’backup’
means
backup
of
data
base
contents,
’archive’
(BRArchive)
means
the
backup
of
offline
DB2
log
files.
DP
for
mySAP.com
employs
the
TSM
archive
function
for
both
backup
types.
It
is
highly
recommended
to
use
tape
storage
for
the
database
contents,
as
this
has
consistently
proven
to
provide
the
best
data
throughput
for
backup
and
restore.
For
backing
up
log
files
it
is
recommended
to
use
a
disk-tape
storage
hierarchy
and
to
backup
each
DB2
log
file
right
after
it
is
placed
into
the
archive
directory.
This
yields
the
best
protection
against
data
loss
and
eliminates
the
necessity
to
mount
a
tape
for
each
DB2
log
file.
Collocation
is
a
function
in
TSM
to
ensure
that
client
data
is
kept
together
on
one
tape.
We
recommend
to
deactivate
collocation
for
backups
with
DP
for
mySAP.com
in
order
to
enable
parallel
sessions
to
use
multiple
tape
drives
in
parallel.
Collocation
must
also
be
deactivated
in
order
to
use
the
multiple
log
copy
function,
see
“Multiple
DB2
Log
File
Copies”
on
page
15.
Views
of
backups
on
the
TSM
server
are
generated
by
the
utility
backom.
For
details,
please
refer
to
Chapter
6,
“Data
Protection
for
mySAP.com
Backup
Object
Manager,”
on
page
43.
Note
DP
for
mySAP.com
can
be
configured
to
use
multiple
TSM
servers
to
improve
either
availability
(alternate
servers)
or
performance
(multiple
