Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP

NetWeaver
2004s SR2

n When you perform a system copy, all software units or usage types in the
source system are copied
to the target system. This means that none of the usage types in the target
system can be excluded
from the system copy, nor can you select usage types.
n Dos and Don'ts for system copy:
l Do:
uSave configuration data and runtime data in the J2EE database only. If you
absolutely need
to save this data to the file system level, you must use the Software
Deployment Manager
(SDM) to save the data.
uFollow the Open SQL standard.
uMake sure that all communication runs through the database pool.
l Don't:
uSave any system and infrastructure-specific data in business objects. Use a
pointer to the
central storage of such information, for example:
t SAP SystemID and SID (SAPSID =SID=system name)
t Host name
t IP addresses
t Services and Ports
t Logical destinations and logical system names
t Other technical infrastructure names
uUse file system persistency.
uSet up dependencies between Java and ABAP.
uTry to copy the Java part of an ABAP+Java system to a Java standalone
system or vice versa.

12/120 PUBLIC 12/04/2006

2 Planning

2 Planning
This section describes how to plan your system copy.
Recommendation

We recommend that you make a system copy in order to set up a test, demo,
training, or standby
system.
Only valid for: Oracle

You cannot create standby systems with a system copy. You should perform
upgrades in a test system
first. This way you can identify customer-specific problems that might result
from modifications.
End of: Oracle

You can apply the system copy for:

n Setting up system landscapes (where the SAP systems have different
SAPSIDs).
n Creating systems for testing, demonstration, training, and standby.
Depending on the purpose of
the system, it might be advisable to use the same SAP system ID, even
though this prevents you
from including the system in a system group for transports.
Caution

The SAP system release of the source and target systems must be the same.
Note

You can set up the SAP system infrastructure (development, quality

assurance, and production
system) without making a system copy as follows:
n Install all SAP systems, starting with the development system. Customize
the development
system as described in the implementation documentation.

n Transport the client-dependent and client-independent data to the quality

assurance and
production systems.
However, if you do not follow this concept, you can also install a system,
customize it and then
perform a system copy.
When copying a system which contains production data it is important to
choose the right moment
for the copy. This could be a month-end or year-end closing.
12/04/2006 PUBLIC 13/120
2 Planning
Process

1. In the event of a major change in hardware configuration (for example,

new machine type, new
hard disk configuration, new file system type), consult your SAP-authorized
hardware partner.
2. Create a plan to perform the system copy.
Consider the downtime of the source system (for preparations and copying)
when planning
the system copy.
3. Read the following SAP Note for up-to-date information:
SAP Note 970518 (Homogeneous and Heterogeneous System Copy for SAP
Systems Based on SAP NetWeaver
2004s SR2)
4. Decide which system copy procedure you want to use:
n The database-specific procedure [page 23] using tools provided by the
database vendor
Some database vendors offer specific tools for copying a database. These
tools let you:
l Restore a backup of one database (source database) in another one (target
database) (backup
method)

l Unload the source database and load the data into the target database
n The database-independent procedure [page 56] using SAP tools
Use this method if database-specific methods are either not available or not
suitable.
Note

For a heterogeneous system copy, only the database-independent

method is available.
These methods are not supported for all database systems. See the
following table to check which
copy methods are available for your database system:
Database OS Platform Available Methods

MaxDB UNIX Use one of the following:

n System Copy Procedure on UNIX [page 57] using R3load
n MaxDB-specific procedure [page 54] for a homogeneous system
copy only
MaxDB Windows Use one of the following:
n System Copy Procedure on Windows [page 59] using R3load
n MaxDB-specific procedure [page 54] for a homogeneous system
copy only
IBM DB2 for
i5/OS
IBM System i Use one of the following:
n System Copy Procedure on IBM System i [page 60] using R3load
n IBM System i Specific Procedure [page 53] for a homogeneous
system copy only
For more information, see SAP Note 585277.
14/120 PUBLIC 12/04/2006
2 Planning
Database OS Platform Available Methods

IBM DB2 for

Linux, UNIX,

and Windows
UNIX or Windows Use one of the following:
n
Only valid for: UNIX

System Copy Procedure on UNIX [page 57] using R3load

End of: UNIX

n
Only valid for: Windows

System Copy Procedure on Windows [page 59] using R3load

End of: Windows

n The backup method of IBM DB2 for Linux, UNIX, and

Windows is supported for SAP systems based on SAP
NetWeaver 2004s SR2. For more information, see IBM DB2
for Linux, UNIX, and Windows Specific Procedure [page 35].
IBM DB2 for z/OS IBM eServer zSeries Use one of the following:
n
Only valid for: UNIX

System Copy Procedure on UNIX [page 57] using R3load

End of: UNIX

n
Only valid for: Windows

System Copy Procedure on Windows [page 59] using R3load

End of: Windows

n The IBM DB2 for z/OS specific procedure as described in IBM

DB2 for z/OS Specific Procedure [page 38] for a homogeneous
system copy only .
Oracle UNIX Use one of the following:
n
Only valid for: UNIX

System Copy Procedure on UNIX [page 57] using R3load

End of: UNIX

n The R3load method with Export/Import Monitors (see

R3load Procedures Using the Migration Monitor [page 93])

n Oracle-Specific Procedure [page 25] for a homogeneous system
copy only
Oracle Windows Use one of the following:
n
Only valid for: Windows

System Copy Procedure on Windows [page 59] using R3load

End of: Windows

n The R3load method with Export/Import Monitors

(see R3load Procedures Using the Migration Monitor [page 93]).
n Homogeneous system copy only:
The Oracle backup/restore method (see Oracle-Specific
Procedure [page 25] and SAP Note 676468).
MS SQL Server Windows Use one of the following:
n
Only valid for: Windows

System Copy Procedure on Windows [page 59] using R3load

End of: Windows

n The R3load method with Export/Import Monitors (see

R3load Procedures Using the Migration Monitor [page 93]).
12/04/