System Copy Methods
Unit Overview
This unit gives an overview of available SAP system copy methods. Of most importance are information about SAP products which cannot be migrated the standard way and R3LOAD restrictions that exist if a PREPARE of an upgrade was run or the Incremental Table Conversion (ICNV) was not finished.
Unit Objectives
After completing this unit, you will be able to:
• Evaluate the database-specific and -unspecific options for performing SAP homogeneous or heterogeneous system copies (OS/DB Migrations)
Unit Contents
Lesson: System Copy Methods... 48 Exercise 3: System Copy Methods ... 53
Lesson: System Copy Methods
Lesson Overview
Contents
• Database-specific and -unspecific methods for SAP homogeneous or heterogeneous system copies (OS/DB Migrations)
Lesson Objectives
After completing this lesson, you will be able to:
• Evaluate the database-specific and -unspecific options for performing SAP homogeneous or heterogeneous system copies (OS/DB Migrations)
Business Example
In as customer project, it must be figured out, what’s the best method to move a system from one platform to another. The right approach depends on the involved database and the type of operating system used.
Figure 34: Comment
Any Hotline or Remote Consulting effort that results from the use of a copy or migration procedure that has not been officially approved by SAP will be billed.
TADM70 Lesson: System Copy Methods
Figure 35: R3LOAD Method
DB2 for LUW = DB2 for Linux, UNIX, Windows
The above table shows that all SAP supported database systems can be copied to each other by using R3LOAD.
Note:
1. The database specific methods might be faster than the R3LOAD (if released by SAP)
2. The database specific methods might be faster for an OS migration than R3LOAD (if released by SAP).
On earlier SAP release the PREPARE phase imports and implements ABAP
Dictionary changes which cannot be unloaded consistently by R3LOAD. A complete reset of all PREPARE changes is not possible. Restarting the PREPARE phase on the migrated system will not help. If it applies to your SAP release it is mentioned in the system copy guide and/or in a corresponding SAP Note.
The Incremental Table Conversion implements database-specific methods which cannot be unloaded consistently by R3LOAD (danger for loss of data). Before using R3LOAD, finish all table conversions! The transaction ICNV should not show any entry.
Figure 37: R3LOAD Restrictions (2)
For BW 3.0 and 3.1 R3LOAD system copies the appropriate Support Package level must be applied and a certain patch level for R3LOAD and R3SZCHK is required (according SAP Note 777024).
Related SAP Notes:
• 771209 “NetWeaver 04: System copy (supplementary note)” • 777024 “BW 3.0 and BW 3.1 System copy (supplementary note)” • 888210 “NetWeaver 7.**: System Copy (supplementary note)”
TADM70 Lesson: System Copy Methods
Figure 38: Database Specific System Copy Methods (ABAP)
Certain databases can be even migrated to other operating systems by a simple restore. However, heterogeneous system copies by database-specific methods must be approved by SAP. If in doubt contact SAP before executing such kind of OS migration. The SAP OS/DB Migration Check is required anyway!
Notes on database specific methods for ABAP based systems (make sure that the method is also valid for JAVA Add-In installations):
1. DB2: Copy - Database copy on the same host, Dump - Database copy to another host.
2. DB4: SAVLIB/RSTLIB method, see SAP Note: 585277 3. DB6: Database director (redirect restore) or brdb6 tools.
4. DB6: Cross platform restore since DB2 UDB version 8 (for AIX, HP-UX, Solaris), see SAP Note: 628156
5. HDB: Check http://help.sap.com/hana_appliance for the respective guide 6. INF: Informix Level 0 Backup, see SAP Notes: 89698, 173970.
7. ADA: Cross platform restore if source and target OS is of same endian type. SAP Note: 962019
8. MSS: Detach/Attach database files, see SAP Notes: 151603, 339912
9. ORA: The SAPINST Backup/Restore method is released for all products. SAP Notes: 659509, 147243
10. ORA: Transportable Tablespace / Database, see SAP Notes: 1035051, 1003028, 1367451
11. SYB: Backup/Restore, see SAP Note: 1591387
Operating system Endian types, see SAP Note: 552464
Figure 39: Database Specific System Copy Methods (JAVA)
SAPINST runs an internal function called “Migration Tool Kit” (“Migration
Controller”) to adjust the SAP JAVA target system for the new instance name, instance number, host name, etc.
TADM70 Lesson: System Copy Methods
Exercise 3: System Copy Methods
Exercise Objectives
After completing this exercise, you will be able to:
• Know in which cases to prefer homogeneous system copies with R3LOAD/JLOAD against database specific methods.
• Understand how to handle OS migrations with database tools.
Business Example
For a SAP system move, it should be known what the available options and their specific prerequisites are. R3LOAD is quite flexible, but needs more time for the export/import compared to a backup/restore scenario. Nevertheless, there can be good reasons to use R3LOAD anyway.
Task 1:
The homogeneous copy of an ABAP system performed with database specific means is in most cases much faster than using the R3LOAD method.
1. What could be some of the reasons for using the R3LOAD method? 2. Which specific checks should be done before using R3LOAD to export the
source system?
Task 2:
Some databases allow OS migrations of SAP systems using database specific means. 1. Is it necessary in this case to order an SAP OS/DB Migration Check for
productive systems?
2. Is a test and final migration required for productive systems? 3. Must one be certified in order to perform an OS/DB migration?
Solution 3: System Copy Methods
Task 1:
The homogeneous copy of an ABAP system performed with database specific means is in most cases much faster than using the R3LOAD method.
1. What could be some of the reasons for using the R3LOAD method?
a) The source and target systems use the same operating system and database type but different versions.
b) The target disk layout is completely different from the source system and the database specific copy method does not allow adapting to new disk layouts.
c) If the database storage unit names include the SAP SID, the installation of the target database according the R3LOAD method will allow you to choose new names.
d) Data archiving is done in the source database and the system copy to the target system should also be used to reduce the amount of required disk space
e) In the case that systems should be moved in or out of a MCOD database. 2. Which specific checks should be done before using R3LOAD to export the
source system?
a) Make sure the PREPARE for the next SAP upgrade was not started (if this restriction applies to your SAP System release) and verify that the Incremental Table Conversion (ICNV) has completed.
Task 2:
Some databases allow OS migrations of SAP systems using database specific means. 1. Is it necessary in this case to order an SAP OS/DB Migration Check for
productive systems?
a) It doesn’t matter which method is used to perform a heterogeneous system copy of a productive SAP ABAP System. The SAP OS/DB Migration Check is required anyway.
2. Is a test and final migration required for productive systems?
a) A test and a final system migration is required, when performing an SAP heterogeneous system copy.
TADM70 Lesson: System Copy Methods
3. Must one be certified in order to perform an OS/DB migration?
a) Yes, an OS/DB migration certification is required to perform the system copy.
Lesson Summary
You should now be able to:
• Evaluate the database-specific and -unspecific options for performing SAP homogeneous or heterogeneous system copies (OS/DB Migrations)
TADM70 Unit Summary
Unit Summary
You should now be able to:
• Evaluate the database-specific and -unspecific options for performing SAP homogeneous or heterogeneous system copies (OS/DB Migrations)