data protection for mysap.com technology installation...
TRANSCRIPT
-
IBM
Tivoli
Storage
Manager
for
Enterprise
Resource
Planning
(5698APR)
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
Version
3
Release
3.
10
SC33-6340-04
-
IBM
Tivoli
Storage
Manager
for
Enterprise
Resource
Planning
(5698APR)
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
Version
3
Release
3.
10
SC33-6340-04
-
Fifth
Edition
(December
2003)
This
edition
applies
to
Data
Protection
for
mySAP.com
technology
Version
3
Release
3
Modification
Level
10
(product
number
5698DPR),
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,
2003.
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://www.ibm.com/software/tivoli
-
Contents
Figures
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Tables
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. ix
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xi
Trademarks
and
Service
Marks
.
.
.
.
.
.
.
. xi
Naming
Conventions
used
in
this
Documentation
xii
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
. xiii
Who
Should
Read
This
Book
.
.
.
.
.
.
.
. xiii
How
to
Read
This
Book
.
.
.
.
.
.
.
.
.
. xiii
Where
to
Find
More
Information
.
.
.
.
.
.
. xiii
Part
1.
Data
Protection
Basics
.
.
.
. 1
Chapter
1.
Concepts
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
. 3
Oracle
Backup/Restore
and
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
DP
for
mySAP.com
and
BACKINT
.
.
.
.
.
. 3
DP
for
mySAP.com
and
RMAN
.
.
.
.
.
.
. 4
Chapter
2.
Developing
a
Backup
Strategy
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5
Planning
a
Backup
Strategy
for
the
Operating
System
5
Planning
a
Backup
Strategy
for
Your
Oracle
Database
5
Planning
a
Backup
Strategy
for
Backup
Protocols
and
Profiles
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
Planning
a
Backup
Strategy
for
mySAP.com
System
Data
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 8
Part
2.
Installing
and
Using
.
.
.
.
. 11
Chapter
3.
Introducing
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
. 13
Scope
of
Data
Protection
for
mySAP.com
.
.
.
. 14
Integration
of
Data
Protection
for
mySAP.com
with
SAP
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 14
Storing
data
on
a
TSM
Server
.
.
.
.
.
.
.
. 15
Performance
Options
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Parallel
Sessions
.
.
.
.
.
.
.
.
.
.
.
. 17
Multiplexing
.
.
.
.
.
.
.
.
.
.
.
.
. 17
Disk
Sorting
.
.
.
.
.
.
.
.
.
.
.
.
. 17
Parallel
Server
and
Parallel
Path
.
.
.
.
.
. 17
Individual
Tablespace
Locking
.
.
.
.
.
.
. 17
Incremental
Backup
.
.
.
.
.
.
.
.
.
. 17
RL
Compression
.
.
.
.
.
.
.
.
.
.
.
. 18
Automation
Options
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
. 18
Selectable
Management
Classes
.
.
.
.
.
.
. 18
Retain
Backups
by
Version
.
.
.
.
.
.
.
. 18
Multiple
Redo
Log
Copies
.
.
.
.
.
.
.
. 18
Alternate
Server
and
Path
.
.
.
.
.
.
.
. 18
Frontend/Backend
Processing
.
.
.
.
.
.
. 18
Reporting
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Message
Logging
.
.
.
.
.
.
.
.
.
.
. 19
Using
FlashCopy
to
Minimize
Backup
and
Restore
Windows
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19
Integration
with
Data
Protection
for
IBM
Enterprise
Storage
Server
(ESS)
for
mySAP.com
. 19
Archiving
Inactive
Data
.
.
.
.
.
.
.
.
.
. 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,
HP-UX,
Linux)
.
.
.
.
. 23
Installing
Data
Protection
for
mySAP.com
on
Windows
.
.
.
.
.
.
.
.
.
.
.
.
.
. 25
Post
Installation
Steps
.
.
.
.
.
.
.
.
.
.
. 26
Review
of
the
TSM
Option
File
.
.
.
.
.
.
. 26
The
Password
.
.
.
.
.
.
.
.
.
.
.
. 26
Verifying
the
Installation
.
.
.
.
.
.
.
.
. 27
Specifying
an
Administration
Assistant
Server
.
. 28
Upgrading
Data
Protection
for
mySAP.com
(Migration)
.
.
.
.
.
.
.
.
.
.
.
.
.
. 29
Special
Installation
.
.
.
.
.
.
.
.
.
.
.
. 29
Silent
Installation
.
.
.
.
.
.
.
.
.
.
. 29
Console
Installation
.
.
.
.
.
.
.
.
.
.
. 29
Firewall
Installation
.
.
.
.
.
.
.
.
.
. 30
Uninstalling
Data
Protection
for
mySAP.com
.
.
. 30
Uninstalling
Data
Protection
for
mySAP.com
from
UNIX
(AIX,
Solaris,
HP-UX,
Linux)
.
.
. 30
Uninstalling
Data
Protection
for
mySAP.com
from
Windows
.
.
.
.
.
.
.
.
.
.
.
. 30
Chapter
5.
Adjusting
your
System
.
.
. 31
Adjustments
for
Improving
Performance
of
Data
Transfer
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 31
Restore
Objectives
.
.
.
.
.
.
.
.
.
.
. 31
General
Aspects
of
Data
Transfer
.
.
.
.
.
. 32
Optimizing
the
mySAP.com
Database
Server
(Production
Server)
for
Data
Transfer
.
.
.
.
. 33
Optimizing
The
Network
.
.
.
.
.
.
.
.
. 38
Optimizing
The
Backup
Server
(TSM
Server)
.
. 39
Optimizing
the
Settings
for
the
Tivoli
Storage
Manager
.
.
.
.
.
.
.
.
.
.
.
.
.
. 40
Optimizing
Your
Environment
.
.
.
.
.
.
. 40
Adjustments
for
the
Administration
Assistant
.
.
. 41
Adjustments
for
High
Availability
.
.
.
.
.
.
. 42
Copyright
IBM
Corp.
1995,
2003
iii
||
||||||||||
||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-
Considerations
for
Using
IBM
HACMP
for
AIX
42
Adjustments
for
Automation
.
.
.
.
.
.
.
. 47
Password
Adjustments
.
.
.
.
.
.
.
.
. 47
Scheduling
Automated
Backup
Runs
.
.
.
.
. 50
Actions
used
for
Adjusting
your
System
.
.
.
.
. 53
Chapter
6.
Using
Data
Protection
for
mySAP.com
with
RMAN
.
.
.
.
.
.
. 55
RMAN
Setup
on
UNIX
Systems
.
.
.
.
.
.
. 55
RMAN
Setup
on
Windows
Systems
.
.
.
.
.
. 57
Chapter
7.
Using
Data
Protection
with
the
File
Manager
.
.
.
.
.
.
.
.
.
. 59
Data
Protection
for
mySAP.com
File
Manager
.
.
. 59
Chapter
8.
Using
the
Administration
Assistant
for
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
. 63
General
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 63
Prerequisites
.
.
.
.
.
.
.
.
.
.
.
.
.
. 64
Installation
.
.
.
.
.
.
.
.
.
.
.
.
.
. 65
Installing
the
Administration
Assistant
Server
(Base
Installation)
.
.
.
.
.
.
.
.
.
.
. 65
Installing
the
Administration
Assistant
NLS
Package
(optional)
.
.
.
.
.
.
.
.
.
.
. 68
Specifying
a
new
Administration
Assistant
Server
for
Data
Protection
for
mySAP.com
.
.
.
.
.
. 68
Verifying
the
Installation
.
.
.
.
.
.
.
.
.
. 69
Authorizing
Administration
Assistant
Users
.
.
. 70
Using
the
Administration
Assistant
.
.
.
.
.
. 70
Uninstalling
the
Administration
Assistant
.
.
.
. 70
Chapter
9.
Cloning
the
mySAP.com
System
.
.
.
.
.
.
.
.
.
.
.
.
.
. 71
What
is
Cloning
?
.
.
.
.
.
.
.
.
.
.
.
. 71
mySAP.com
System
Cloning
Example
.
.
.
.
. 71
Part
3.
Appendixes
.
.
.
.
.
.
.
.
. 73
Appendix
A.
Alternate/Parallel
Backup
Paths
and
Backup
Servers
.
.
.
.
.
. 75
Parameter
Settings
-
SERVER
Statement
.
.
.
.
. 76
EXAMPLE
1:
Use
of
Alternate/Parallel
Paths
for
Increased
Availability
.
.
.
.
.
.
.
.
.
. 77
EXAMPLE
2:
Use
of
Alternate/Parallel
Paths
for
Increased
Performance
.
.
.
.
.
.
.
.
.
. 79
EXAMPLE
3:
Use
of
Alternate/Parallel
Servers
for
Disaster
Recovery
.
.
.
.
.
.
.
.
.
. 80
Appendix
B.
The
Data
Protection
for
mySAP.com
Profile
.
.
.
.
.
.
.
.
. 81
Keyword
Reference
.
.
.
.
.
.
.
.
.
.
.
. 81
Sample
Data
Protection
for
mySAP.com
Profile
for
UNIX
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 90
Sample
Data
Protection
for
mySAP.com
Profile
for
Windows
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 94
Appendix
C.
Preparing
Tivoli
Storage
Manager
for
DP
for
mySAP.com
.
.
.
. 99
Configuring
the
Tivoli
Storage
Manager
Server
.
. 99
General
Considerations
for
TSM
.
.
.
.
.
. 99
Prerequisites
.
.
.
.
.
.
.
.
.
.
.
.
. 100
Adjusting
your
TSM
for
DP
for
mySAP.com
.
. 100
Configuring
of
Tivoli
Storage
Manager
Clients
.
. 103
General
Considerations
.
.
.
.
.
.
.
.
. 103
Tivoli
Storage
Manager
Clients
on
UNIX
Systems
.
.
.
.
.
.
.
.
.
.
.
.
.
. 103
Tivoli
Storage
Manager
Clients
on
Windows
Systems
.
.
.
.
.
.
.
.
.
.
.
.
.
. 104
Appendix
D.
Sample
Tivoli
Storage
Manager
Profiles
.
.
.
.
.
.
.
.
.
. 107
Sample
TSM
Profiles
for
UNIX
.
.
.
.
.
.
. 107
Client
User
Options
File
Sample
(dsm.opt)
.
. 107
Client
System
Options
File
Sample
(dsm.sys)
107
Include/Exclude
List
Sample
.
.
.
.
.
.
. 107
Sample
TSM
Profiles
for
Windows
.
.
.
.
.
. 108
Client
User
Options
File
Sample
(dsm.opt)
.
. 108
Client
Options
Files
Sample
(.opt)
.
. 108
Include/Exclude
List
Sample
.
.
.
.
.
.
. 110
Appendix
E.
Elements
of
Backup
Schedules
.
.
.
.
.
.
.
.
.
.
.
.
. 111
Elements
of
Backup
Schedules
for
UNIX
.
.
.
. 111
Crontab
File
Sample
.
.
.
.
.
.
.
.
.
. 111
Full
Offline
Backup
Shell
Script
Sample
.
.
. 112
Save
and
Delete
Redo
Logs
Shell
Script
Sample
112
Elements
of
Backup
Schedules
for
Windows
.
.
. 113
Schedule
Batch
Sample
.
.
.
.
.
.
.
.
. 113
Full
Offline
Backup
Batch
File
Sample
.
.
.
. 114
Save
and
Delete
Redo
Logs
Batch
File
Sample
114
Appendix
F.
Tips
and
Hints
for
SAP
Backup
Utilities
.
.
.
.
.
.
.
.
.
. 117
Tips
and
Hints
for
BRARCHIVE
.
.
.
.
.
.
. 117
Hints
for
BRARCHIVE
Version
3.1G
or
Higher
.
. 120
Examples
Using
MAX_SESSIONS
and
REDOLOG_COPIES
.
.
.
.
.
.
.
.
.
.
. 120
mySAP.com
Backup
and
Recovery
Scenarios
Using
Data
Protection
for
mySAP.com
.
.
.
.
.
.
. 121
Backup
Scenarios
.
.
.
.
.
.
.
.
.
.
. 122
Restore/Recovery
Scenario
.
.
.
.
.
.
.
. 126
Appendix
G.
Troubleshooting
.
.
.
. 131
Problem
Resolution
during
Installation
and
Setup
131
Understanding
The
Setup
.
.
.
.
.
.
.
. 131
Location
of
Log
Files
.
.
.
.
.
.
.
.
.
. 133
BACKINT
Problem
Resolution
.
.
.
.
.
. 134
RMAN
Problem
Resolution
.
.
.
.
.
.
.
. 136
Problem
Resolution
During
Operation
.
.
.
.
. 138
Reproducable
(Repeatable)
Problems
.
.
.
. 138
Random
problems
.
.
.
.
.
.
.
.
.
.
. 139
Contacting
Your
IBM
/
Tivoli
Support
.
.
.
.
. 139
Invoking
Data
Protection
for
mySAP.com
manually
139
Backup
Function
.
.
.
.
.
.
.
.
.
.
. 140
Restore
Function
.
.
.
.
.
.
.
.
.
.
. 140
iv
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-
Inquire
Function
.
.
.
.
.
.
.
.
.
.
. 141
Delete
Function
.
.
.
.
.
.
.
.
.
.
. 141
Appendix
H.
Data
Protection
for
mySAP.com
Messages
.
.
.
.
.
.
. 143
How
To
Find
Message
Files
(Log
Files)
.
.
.
.
. 143
Data
Protection
for
mySAP.com
Message
Explanations
.
.
.
.
.
.
.
.
.
.
.
.
. 144
Data
Protection
for
mySAP.com
File
Manager
Error
Messages
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 162
Appendix
I.
Installation
Planning
Sheet
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 163
Glossary
.
.
.
.
.
.
.
.
.
.
.
.
. 165
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 169
Contents
v
|
|
|
-
vi
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
Figures
1.
DP
for
mySAP.com
with
SAPDBA
using
the
BACKINT
Interface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
2.
DP
for
mySAP.com
with
SAPDBA
using
the
RMAN
Interface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4
3.
Backup
Scenarios
Within
a
mySAP.com
Oracle
Environment
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7
4.
Scope
of
Data
Protection
for
mySAP.com
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 14
5.
Integration
of
Data
Protection
for
mySAP.com
with
SAP
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 15
6.
Data
Throughput
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 32
7.
Simplified
Data
Transfer
for
a
Backup
/
Restore
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 33
8.
Multiplexing
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 35
9.
Parallel
Sessions
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 36
10.
Parallel
Paths
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 37
11.
Parallel
Servers
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 37
12.
Null
Block
compression
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 38
13.
Sample
Environment
for
HACMP
Takeover
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 42
14.
Production
Backup
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 52
15.
File
Manager
Result
of
an
Inquiry
Procedure
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 60
16.
File
Manager
Result
of
an
Inquiry
Procedure
Showing
File
Names
.
.
.
.
.
.
.
.
.
.
.
.
.
. 60
17.
Example
of
an
mySAP.com
Landscape
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 63
18.
Administration
Assistant
Server
Setup
(Base
Installation)
Specify
Ports
.
.
.
.
.
.
.
.
.
.
.
.
. 66
19.
Administration
Assistant
Server
Setup
(Base
Installation):
Correct
Hostname
Panel
.
.
.
.
.
.
.
.
.
. 67
20.
Administration
Assistant
Server
Setup
Destination
Directory
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 68
21.
Starting
the
Administration
Assistant
with
Netscape
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 69
22.
Administration
Assistant
Start
Panel
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 69
23.
SAP
and
Data
Protection
configuration
files
on
UNIX
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 132
24.
Problem
Isolation
for
Backint
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 134
25.
Problem
Isolation
for
RMAN
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 136
Copyright
IBM
Corp.
1995,
2003
vii
||||
||||
||||||||
||||||
-
viii
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
Tables
1.
SAP
Backup
Profile
Parameter
Combinations
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 27
2.
Tuning
of
Network
Settings
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 39
3.
Tuning
of
SP
Switch
Buffer
Pools
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 39
4.
Tuning
Tivoli
Storage
Manager
Configuration
File
Attributes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 40
5.
Password
Handling
for
UNIX
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 49
6.
Password
Handling
for
Windows
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 50
7.
Overview
of
Actions
for
Adjusting
your
System
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 53
8.
File
Extensions
for
Shared
Libraries
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 55
9.
SERVER
Statement
and
Appropriate
Profile
and
Option
File
Settings.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 76
Copyright
IBM
Corp.
1995,
2003
ix
||
-
x
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
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
to
non-Tivoli
or
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
AIX
v
IBM
v
RS/6000
v
SP
v
Tivoli
Copyright
IBM
Corp.
1995,
2003
xi
-
R/3
and
mySAP.com
are
registered
trademarks
of
SAP
AG
in
Germany,
other
countries,
or
both.
Oracle
is
a
registered
trademark
of
Oracle
Corporation.
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.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Linux
is
a
registered
trademark
of
Linus
Torvalds
and
others.
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.
Naming
Conventions
used
in
this
Documentation
In
this
documentation,
Data
Protection
for
mySAP.com
technology
is
usually
referred
to
as
Data
Protection
for
mySAP.com
or
DP
for
mySAP.com.
The
product
IBM
Tivoli
Storage
Manager
is
usually
referred
to
as
Tivoli
Storage
Manager
or
TSM.
Note
Unless
otherwise
stated,
references
in
this
publication
to
UNIX
apply
to
all
supported
UNIX-based
systems
as
well
as
to
Linux,
and
references
to
Windows
apply
to
all
supported
Windows
platforms.
xii
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
||||
|||
-
Preface
Who
Should
Read
This
Book
This
manual
is
intended
for
system
programmers
and
administrators
who
are
responsible
for
implementing
a
backup
solution
in
a
mySAP.com
environment
using
the
Tivoli
Storage
Manager.
It
describes
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
the
documentation
for
mySAP.com,
Tivoli
Storage
Manager
and
Oracle.
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
architecture
and
properties
of
Data
Protection
for
mySAP.com
and
the
third
part
(Appendix)
gives
samples
and
profiles.
If
you
are
a
person
experienced
in
data
protection,
you
might
want
to
skip
part
1
and
turn
right
away
to
Part
2.
The
information
given
there
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
novice
in
data
protection,
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
during
a
setup
of
a
data
protection
system.
Where
to
Find
More
Information
For
more
information
about
Data
Protection
for
mySAP.com,
refer
to
the
Tivoli
Internet
home
page
at
http://www.ibm.com/software/tivoli.
Note:The
most
up-to-date
version
of
this
book
is
available
in
the
Tivoli
Information
Center
at
http://www.ibm.com/software/tivoli/library.
Copyright
IBM
Corp.
1995,
2003
xiii
|
|
||||
||||
||||
http://www.ibm.com/software/tivolihttp://www.ibm.com/software/tivoli/library
-
xiv
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
Part
1.
Data
Protection
Basics
Copyright
IBM
Corp.
1995,
2003
1
-
2
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
Chapter
1.
Concepts
of
Data
Protection
for
mySAP.com
This
chapter
is
meant
for
users
who
are
new
to
Data
Protection
for
mySAP.com.
If
you
are
experienced
in
Data
Protection
for
mySAP.com,
you
might
want
to
skip
the
following
chapter.
Oracle
Backup/Restore
and
Data
Protection
for
mySAP.com
The
SAP
database
administration
tools
offer
all
the
functions
necessary
to
administer
a
database.
The
SAP
DBA
BRTOOLS
for
Oracle,
(BRBACKUP,
BRARCHIVE,
BRRESTORE)
provide
for
online
or
offline,
partial
or
full
backup
of
tablespaces
(done
by
BRBACKUP),
backup
of
archived
redo
log
files
(done
by
BRARCHIVE)
and
system
guided
restore/recover
capabilities
(done
by
BRRESTORE
and
BRRECOVER).
Oracle
also
provides
its
own
administration
utility
RMAN
(Recovery
MANager)
which
is
of
specific
value
when
incremental
backups
are
required.
Data
Protection
for
mySAP.com
is
seamlessly
integrated
with
the
SAP
BRTOOLS
and
Oracles
RMAN
and
is
optimized
to
handle
unattended,
24
hour,
7
days/week
production
backup/restore
tasks.
DP
for
mySAP.com
and
BACKINT
Figure
1
shows
the
interaction
between
the
SAPDBA
Utilities,
DP
for
mySAP.com
and
the
BACKINT
Interface
in
order
to
do
backup
/
restores.
The
mySAP.com
tools
(SAPDBA
Utilities)
use
tables
in
the
Oracle
database
and
system
data
in
order
to
record
the
status
of
the
data
file
backups
and
logfile
backups.
This
information
will
allow
mySAP.com
to
restore
automatically
the
correct
data
files
and
their
specific
database
transaction
log
files
(redo
log
files),
if
necessary.
The
data
files
reside
in
the
Oracle
database
(Oracle
Instance).
Data
Protection
for
mySAP.com
runs
as
a
separate
process
independent
of
the
database.
It
receives
the
data
through
the
Backint
interface
and
saves
the
data
to
the
Tivoli
Storage
Manager.
A
backup
run
will
proceed
as
follows
(see
circled
numbers):
Figure
1.
DP
for
mySAP.com
with
SAPDBA
using
the
BACKINT
Interface
Copyright
IBM
Corp.
1995,
2003
3
|
|
|||
||
||||||
|||||
|
|||
||||||||
|
-
1.
SAPDBA
utility
BRBACKUP
informs
Oracle
what
data
has
to
be
backed
up
and
puts
the
database
into
the
proper
backup
state
(online
or
offline).
2.
BRBACKUP
calls
DP
for
mySAP.com
via
the
BACKINT
interface
with
a
list
of
all
files
to
be
backed
up.
3.
DP
for
mySAP.com
(via
BACKINT
interface)
backs
up
all
requested
files
from
the
database
and
reports
back
to
BRBACKUP.
BRBACKUP
thereby
increases
its
data
to
include
the
files
that
were
backed
up.
(data
stream
to
file
repository)
4.
BACKINT
saves
the
data
to
TSM.
5.
SAPDBA
updates
the
file
repository,
which
holds
information
about
the
status
of
the
files.
DP
for
mySAP.com
and
RMAN
Figure
2
shows
the
interaction
between
the
SAPDBA
Utilities,
DP
for
mySAP.com
and
RMAN
in
order
to
do
backup
/
restores.
The
mySAP.com
Tools
(DBA
Utilities)
use
tables
in
the
Oracle
database
and
system
data
in
order
to
record
the
status
of
the
data
file
backups
and
logfile
backups.
This
information
will
allow
mySAP.com
at
a
later
time
to
restore
automatically
the
correct
data
files
and
their
specific
database
transaction
log
files.
The
data
files
reside
in
the
Oracle
database
(Oracle
Instance).
Data
Protection
for
mySAP.com
runs
as
a
separate
process
independent
of
the
database.
It
receives
the
data
through
the
Backint
interface
and
saves
the
data
to
the
Tivoli
Storage
Manager.
A
backup
run
will
proceed
as
follows
(see
circled
numbers):
1.
SAPDBA
utility
BRBACKUP
informs
Oracle
RMAN
what
data
has
to
be
backed
up.
The
RMAN
process
puts
the
database
into
the
proper
backup
state
(online
or
offline).
2.
The
Oracle
server
process
loads
DP
for
mySAP.com
and
interacts
with
it
through
the
Media
Management
API.
3.
DP
for
mySAP.com
backs
up
all
requested
files
from
the
database
and
reports
back
to
BRBACKUP.
BRBACKUP
thereby
increases
its
data
to
include
the
files
that
were
backed
up
(data
stream
to
file
repository).
4.
DP
for
mySAP.com
saves
the
data
to
a
TSM
server.
5.
SAPDBA
updates
the
file
repository,
which
holds
information
about
the
status
of
the
files.
RMAN
has
its
own
file
repository,
with
a
control
file
for
a
separate
recovery
catalog
database.
Figure
2.
DP
for
mySAP.com
with
SAPDBA
using
the
RMAN
Interface
4
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
||
||
|||
|
||
|
|||
|||||||
|
|||
||
|||
|
|||
-
Chapter
2.
Developing
a
Backup
Strategy
This
section
describes
how
to
define
an
appropriate
backup
strategy
for
your
mySAP.com
system.
It
is
intended
as
a
supplement
to
your
mySAP.com,
Oracle,
and
Tivoli
Storage
Manager
documentation.
There
are
several
requirements
that
your
strategy
must
meet.
The
most
important
factors
you
need
to
consider
include:
v
The
types
of
events
you
wish
to
protect
your
mySAP.com
system
against
v
How
quickly
you
need
to
be
able
to
return
to
normal
operation
after
a
failure
v
The
intervals
and
times
of
day
during
which
backups
can
be
performed
v
The
events
and
points
in
time
you
need
to
be
able
to
recover,
depending
on
the
type
of
outage
Data
Protection
for
mySAP.com
lets
you
back
up
mySAP.com
database
data
using
the
SAP
backup
interface
BACKINT
directly
to
Tivoli
Storage
Manager
storage.
However,
these
backups,
which
use
the
SAP
database
utilities
BRBACKUP
and
BRARCHIVE,
are
only
backups
of
the
database
or
the
offline
redo
logs.
Hence,
to
protect
your
complete
system
against
failures
affecting
SAPDBA
or
other
mySAP.com
system
data,
you
should
use
standard
Tivoli
Storage
Manager
commands
or
the
Tivoli
Storage
Manager
graphical
user
interface
(GUI)
to
additionally
backup
this
system
data.
To
be
prepared
for
recoveries
from
a
severe
disaster,
the
procedures
described
below
must
become
an
integral
part
of
your
overall
disaster
recovery
plan.
Planning
a
Backup
Strategy
for
the
Operating
System
In
order
to
be
protected
against
a
complete
loss
of
the
operating
system,
it
is
imperative
that
after:
v
the
installation
of
the
operating
system
v
updates/upgrades
of
the
operating
system
appropriate
system
backups
are
made
with
the
operating
system
dependent
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
user
dependent
data.
Planning
a
Backup
Strategy
for
Your
Oracle
Database
In
order
to
be
able
to
recover
from:
v
user
errors
v
statement
failures
v
transaction
failures
v
media
failures
Copyright
IBM
Corp.
1995,
2003
5
-
that
could
affect
your
Oracle
database,
save
the
following
objects
on
a
regular
basis:
v
Data
files
v
Control
files
v
Online
redo
logs
v
Offline
redo
logs
Files
belonging
to
a
specific
tablespace
(data
files)
are
backed
up
by
BRBACKUP.
This
is
done
at
the
file
level,
where
offline
or
online
backups
are
possible.
The
control
file
is
saved
by
BRBACKUP
whenever
a
tablespace
backup
occurs.
Online
redo
logs
are
saved
by
BRBACKUP
whenever
a
full
offline
database
backup
occurs.
Note
Oracle
provides
mirroring
of
the
control
and
online
redo
log
files
to
protect
the
running
database
system
against
corruption
of
these
active
files.
(The
AIX
LVM
facilities
can
also
be
used
to
mirror
these
files.)
Offline
redo
logs
are
saved
by
BRARCHIVE.
You
can
specify
that
the
redo
logs
are
to
be
deleted
from
their
original
location
when
BRARCHIVE
completes
successfully.
Additional
information
on
BRARCHIVE
operations
can
be
found
in
Appendix
F,
Tips
and
Hints
for
SAP
Backup
Utilities,
on
page
117.
Apart
from
backing
up
all
database
relevant
data
(data
files,
control
file,
online
redo
log
files,
and
offline
redo
log
files)
it
is
also
recommended
that
you
back
up
v
SAP
system
data
v
Oracle
system
data
v
Operating
system
data
This
data
should
be
backed
up
with
the
incremental
backup
function
of
the
Tivoli
Storage
Manager
backup/archive
client.
Figure
3
on
page
7
shows
the
various
backup
scenarios
within
a
mySAP.com
database
server
machine.
6
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
The
database
itself
is
backed
up
with
Data
Protection
for
mySAP.com,
whereas
the
SAP,
Oracle
and
operating
system
protocols
are
backed
up
directly
by
the
Tivoli
Storage
Manager.
Planning
a
Backup
Strategy
for
Backup
Protocols
and
Profiles
Every
BRBACKUP
and
BRARCHIVE
run
is
divided
into
two
parts.
The
first
part
backs
up
objects
such
as:
v
mySAP.com
data
files
v
database
control
files
v
online
redo
log
files
v
offline
redo
log
files
depending
on
the
action
started
(see
previous
section).
The
second
part
of
a
BRBACKUP
or
BRARCHIVE
is
responsible
for
backing
up
the
following
profiles:
v
init.dba
(SAPDBA
profile)
v
init.ora
(Oracle
profile)
v
init.sap
(SAP
backup
profile)
v
init.utl
(Data
Protection
for
mySAP.com
profile)
and
the
protocol
files
v
back.log
(BRBACKUP
summary
log)
v
arch.log
(BRARCHIVE
summary
log)
v
detailed
BRBACKUP/BRARCHIVE
log
v
reorg.log
(main
SAPDBA
log)
v
struct.log
(structure
log)
Figure
3.
Backup
Scenarios
Within
a
mySAP.com
Oracle
Environment
Chapter
2.
Developing
a
Backup
Strategy
7
-
These
profiles
and
protocols
are
used
by
the
SAP
database
utilities
whenever
backups
or
restores/recoveries
are
required.
Unless
you
use
an
additional
security
method,
for
example
an
additional
file
system
backup,
these
profiles
or
protocol
files
can
only
be
restored
in
combination
with
Data
Protection
for
mySAP.com.
For
this
purpose,
you
can,
for
example,
use
the
Data
Protection
for
mySAP.com
File
Manager
(see
Data
Protection
for
mySAP.com
File
Manager
on
page
59).
In
the
case
of
a
recovery
scenario
after
a
disaster,
it
may
be
time
consuming
to
restore
the
backup
protocols
or
profiles
by
means
of
Data
Protection
for
mySAP.com
or
the
Data
Protection
for
mySAP.com
File
Manager.
Hence,
it
is
recommended
that
you
back
up
the
directories
and
file
systems
containing
these
files
separately.
You
can
find
the
files
in
the
following
directories:
UNIX
/oracle//sapreorg
(SAPDBA
and
structure
logs)
/oracle//sapbackup
(BRBACKUP
logs)
/oracle//saparch
(BRARCHIVE
logs)
/oracle//dbs
(profiles)
Windows
:\oracle\\sapreorg
(SAPDBA
and
structure
logs)
:\oracle\\sapbackup
(BRBACKUP
logs)
:\oracle\\saparch
(BRARCHIVE
logs)
:\orant\database
(profiles)
Planning
a
Backup
Strategy
for
mySAP.com
System
Data
In
addition
to
the
backup
operations
performed
with
BRBACKUP
and
BRARCHIVE,
you
may
want
to
protect
your
system
against
the
loss
of
mySAP.com
system
data,
user
data,
or
even
operating
system
data
that
is
not
stored
with
BRBACKUP
or
BRARCHIVE.
You
can
use
the
incremental
backup
capabilities
of
the
Tivoli
Storage
Manager
backup/archive
client
to
do
this.
The
Tivoli
Storage
Manager
incremental
backup
function
lets
you
define
an
include/exclude
list
of
files
that
is
applied
automatically
during
incremental
backup
operations.
This
include/exclude
list
should
be
used
to
exclude
data
already
stored
using
Data
Protection
for
mySAP.com.
This
would
be
all
database
relevant
data,
such
as
data
files,
the
control
file,
and
online/offline
redo
logs.
For
further
information
about
include/exclude
lists,
see
your
Tivoli
Storage
Manager
manuals,
Using
the
Backup-Archive
Clients.
Examples
of
include/exclude
lists
for
UNIX
can
be
found
in
Sample
TSM
Profiles
for
UNIX
on
page
107
and
for
Windows
in
Sample
TSM
Profiles
for
Windows
on
page
108.
Sample
files
can
be
found
in
your
DP
for
mySAP.com
installation
package.
8
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
|
||||||||||
||||||||||
|
-
The
information
saved
with
the
BRBACKUP
and
BRARCHIVE
utilities
is
usually
located
in
the
following
file
systems
or
directories:
UNIX
/oracle//saparch/
/oracle//sapdata1/
/oracle//sapdata2/
/oracle//sapdata3/
/oracle//sapdata4/
/oracle//sapdata5/
/oracle//sapdata6/
.
.
.
/oracle//origlogA/
/oracle//origlogB/
Windows
:\oracle\\saparch\
:\oracle\\sapdata1\
:\oracle\\sapdata2\
:\oracle\\sapdata3\
:\oracle\\sapdata4\
:\oracle\\sapdata5\
:\oracle\\sapdata6\
.
.
.
:\oracle\\origlogA\
:\oracle\\origlogB\
Add
these
directories
to
the
list
of
paths
to
be
excluded
in
the
include/exclude
list
of
your
Tivoli
Storage
Manager
backup/archive
client.
This
will
prevent
you
from
saving
the
database
data
twice.
Chapter
2.
Developing
a
Backup
Strategy
9
||||||||||||
||||||||||||
-
10
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
Part
2.
Installing
and
Using
Copyright
IBM
Corp.
1995,
2003
11
-
12
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
-
Chapter
3.
Introducing
Data
Protection
for
mySAP.com
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
Oracle
based
mySAP.com
systems.
It
is
integrated
with
SAPs
backup
and
recovery
utilities
BRRECOVER,
SAPDBA,
BRBACKUP,
BRARCHIVE,
and
BRRESTORE,
and
allows
you
to
follow
SAPs
backup
and
recovery
procedures.
Being
specifically
optimized
for
mySAP.com
databases,
Data
Protection
for
mySAP.com
allows
you
to
manage
large
volumes
of
data
most
efficiently.
This
chapter
gives
you
an
overview
of
the
environment
and
functions
of
Data
Protection
for
mySAP.com.
It
is
not
the
intent
of
this
chapter
to
explain
how
to
use
the
SAP
utilities.
Although
the
usage
of
the
SAP
utilities
is
sketched
in
Appendix
F,
Tips
and
Hints
for
SAP
Backup
Utilities,
on
page
117,
we
recommend
to
read
the
SAP
manuals
for
BRRECOVER
and
SAPDBA.
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).
Copyright
IBM
Corp.
1995,
2003
13
|
|
||||||||
||||||||
-
Scope
of
Data
Protection
for
mySAP.com
The
SAP
utilities
for
backup
and
recovery
of
a
mySAP.com
Oracle
databases
are
focused
on
the
content
of
the
database,
where
over
90
%
of
the
data
reside.
Thus
Data
Protection
for
mySAP.com
will
be
used
for
backup
and
restore
of
data
files,
control
files,
and
online
and
offline
redo
logs
(See
Figure
4).
Other
files
such
as
SAP
and
Oracle
executables
can
be
backed
up
using
the
Tivoli
Storage
Manager
Backup
Archive
Client.
As
a
consequence
-
in
case
of
a
disaster
recovery
-
you
have
to
make
sure
that
all
Oracle
and
SAP
executables
are
available
before
starting
restore
and
recovery
of
your
database
using
the
SAP
utilities.
Integration
of
Data
Protection
for
mySAP.com
with
SAP
Figure
5
on
page
15
shows
that
once
being
configured
Data
Protection
for
mySAP.com
operates
as
an
invisible
connection
between
the
mySAP.com
Database
Administration
Tools
and
Tivoli
Storage
Manager.
It
provides
you
with
two
different
adapters
supporting
different
backup
and
recovery
scenarios:
v
backint:
an
executable
that
is
called
directly
by
SAP.
It
can
be
used
to
perform
full
online
and
offline
backups
as
well
as
backups
of
control
and
redo
log
files.
v
a
shared
library
that
is
dynamically
linked
by
Oracles
RMAN
(an
executable
installed
during
the
Oracle
database
installation).
If
a
backup
is
performed
using
this
library
SAP
does
not
communicate
with
Data
Protection
for
mySAP.com
directly.
It
communicates
through
Oracles
RMAN
process
instead.
When
using
RMAN
and
this
shared
library
you
can
perform
incremental
database
backups.
You
can
configure
SAP
such
that
it
uses
only
backint
but
you
can
never
configure
it
to
use
only
RMAN:
backint
is
always
used
for
the
backup
of
control
and
redo
log
files.
Both
adapters
-
backint
and
the
media
management
library
for
Oracle
-
share
a
configuration
file
init.utl,
which
describes
how
to
perform
backups
and
Figure
4.
Scope
of
Data
Protection
for
mySAP.com
14
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
||
|
||||
||||
||
||||
||
|||||
|||
||
-
restores,
and
which
can
be
used
to
customize
Data
Protection
for
mySAP.com
to
your
environment
and
according
to
your
needs.
Both
adapters
communicate
with
the
TSM
Server
through
an
API
that
is
shared
with
other
IBM
Tivoli
Data
Protection
products,
and
both
require
that
ProLE
-
a
background
process
that
is
part
of
the
Data
Protection
for
mySAP.com
package
-
is
running.
The
Data
Protection
for
mySAP.com
package
contains
an
additional
(optional)
component
-
the
Administration
Assistant
-
aimed
at
increasing
the
administrators
productivity.
The
functionality
covers
configuring
a
DP
for
mySAP
instance,
data
transfer
performance
monitoring
and
monitoring
of
success
and
failure
of
backup/restore
operations.
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.
To
register
an
SAP
instance
to
the
Administration
Assistant
Server
simply
add
the
location
of
the
Administration
Assistant
to
the
command
line
arguments
of
ProLE.
Storing
data
on
a
TSM
Server
DP
mySAP.com
transfers
data
to/from
the
TSM
server
in
one
or
multiple
(parallel)
sessions
to
a
TSM
server.
Each
session
must
have
a
storage
device
associated
with
it.
DP
mySAP.com
uses
the
Archive/Retrieve
functions
in
order
to
backup/restore
data
to/from
TSM.
Thus
the
SAP
backup
ID
can
be
persistently
linked
to
each
backup
file
via
a
file
descriptor
available
with
the
Archive
function.
This
backup
ID
is
very
important,
as
it
is
later
used
by
SAPs
restore
utility
to
determine
all
files
required
for
a
complete
restore.
Note:
In
SAP
terminology
backup
(BRBackup)
means
backup
of
data
files,
archive
(BRArchive)
means
backup
of
archived
redo
log
files.
DP
for
mySAP.com
for
both
backup
types
uses
the
TSM
Archive
function.
Figure
5.
Integration
of
Data
Protection
for
mySAP.com
with
SAP
Chapter
3.
Introducing
Data
Protection
for
mySAP.com
15
||||||
|||||||||
||
|||||||
|||
-
It
is
highly
recommended
to
use
tape
storage
for
the
datafiles
of
a
database,
as
this
has
consistently
proven
to
provide
the
best
data
throughput
for
backup
and
restore.
In
addition
the
files
sequence
from
backup
is
then
maintained
for
restore
as
well,
which
will
yield
shortest
possible
restore
windows.For
backing
up
log
files
it
is
recommended
to
use
a
disk-tape
storage
hierarchy
and
to
backup
each
redo
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
20
MB
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
use
multiple
tape
drives
in
parallel.
Collocation
deactivated
is
also
necessary
to
use
the
multiple
log
copy
function,
see
Multiple
Redo
Log
Copies
on
page
18.
Views
of
backups
on
the
TSM
Server
can
be
generated
by
the
SAP
administration
tools
either
by
using
their
own
local
(detailed)
backup
log
or
by
inquiring
the
TSM
server
through
DP
for
mySAP.com.
Manual
access
to
the
backup
repository
is
provided
through
a
specific
File
Manager
-backfm
-
shipped
with
DP
for
mySAP.com.
It
allows
the
administrator
to
bypass
the
SAP
tools
to
inquire,
delete
and
restore
backups
/
files.
Note:
DP
for
mySAP.com
can
be
configured
to
use
multiple
TSM
servers
to
improve
either
availability
(alternate
servers)
or
performance
(multiple
servers).
DP
for
mySAP.com
accesses
only
those
servers
defined
in
its
profile
when
inquiring
for
the
backup
repository.
Therefore
care
has
to
be
taken
when
removing
TSM
servers
from
the
DP
for
mySAP.com
profile
while
they
still
hold
valid
backup
data.
Database
backups
are
usually
kept
for
a
specified
time
until
they
become
unnecessary.
In
order
to
manage
backup
storage
space
efficiently
these
backups
should
then
be
deleted
so
tapes
can
be
reclaimed.
There
are
two
ways
to
perform
this
deletion:
by
setting
the
archive
retention
period
or
by
using
the
DP
for
mySAP.com
versioning
function,
see
below,
which
will
delete
whole
backup
generations
(full
backups
plus
related
redo
log
backups)
when
the
specified
number
of
versions
is
exceeded.
Note:
Since
the
SAP
backup
log
cannot
be
updated
by
DP
for
mySAP.com
,
it
may
still
contain
old
backups
although
they
are
already
deleted
(expired).
Performance
Options
of
Data
Protection
for
mySAP.com
To
achieve
good
data
transfer
rates
for
backup
and
restore
you
have
to
make
sure
that
the
following
three
components
all
have
good
data
transfer
rates:
the
disks
on
which
the
database
is
located,
the
network
between
the
database
host
and
the
TSM
Server,
and
the
backup
storage
device
containing
the
backup.
Keep
in
mind
that
the
weakest
of
these
components
constrains
your
backup/restore
performance
and
thus
appears
as
a
bottleneck.
Data
Protection
for
mySAP.com
offers
a
variety
of
options
to
optimize
the
data
transfer
rate
for
each
of
these
components
(see
Appendix
B,
The
Data
Protection
for
mySAP.com
Profile,
on
page
81
for
a
detailed
explanation
of
these
parameters
and
their
relationship
to
the
various
bottlenecks).
16
Data
Protection
for
mySAP.com
Technology
Installation
&
Users
Guide
for
Oracle
||||||||
|||||
||||||
||||||
|||||||
||
||
||||||||||
-
Parallel
Sessions
Data
Protection
for
mySAP.com
allows
you
to
backup
or
restore
data
to
multiple
tape
drives
in
parallel.
Parallelism
is
achieved
by
using
more
than
one
session
to
send
data
to
a
TSM
Server
(MAXSESSIONS).
For
details
see
the
profile
keyword
on
page
85.
Multiplexing
Multiplexing
allows
you
to
simultaneously
transfer
data
from
different
files
through
one
session
(MULTIPLEXING
)
in
order
to
maximize
tape
performance.
This
is
useful
since
tape
drives
often
have
higher
data
transfer
rates
than
the
disks
containing
the
tablespaces
of
your
SAP
database.
Note
that
most
customers
combine
multiplexing
and
parallel
sessions
to