R3LOAD/JLOAD Method: The R3LOAD method is used for copying SAP NetWeaver systems based on ABAP, while the JLOAD method is used for SAP NetWeaver systems based on JAVA. These methods provide a means to copy the systems during system migration.
Database and Operating System Independence: The SAP database and operating system independent system copy method is available for all SAP supported databases and operating system combinations. This method allows for flexibility in copying systems across different database and operating system platforms.
Homogeneous System Copy: The homogeneous system copy refers to copying a system using the same database and operating system. It can be performed using database-specific methods such as backup and restore. Database-specific methods are often faster compared to R3LOAD/JLOAD as it eliminates the need to export and import the database.
Heterogeneous System Copy: In some cases, heterogeneous system copy is required, which involves changing the operating system or/and database while copying the system. Some databases provide database-specific copy methods that support heterogeneous system copies. These methods allow for efficient copying of systems across different operating systems.
Homogenous System copy and Heterogeneous system copy of all these database are supported by R3LOAD and JLOAD : DB2 for z/OS , DB2/400, DB2 for LUW (Db2 for Linux , Unix and Windows ) , SAP HANA, MaxDB (SAP), MS SQL Server, Oracle, Sybase ASE (SAP)
Read About INCV in our upcoming blog
When migrating databases to different operating systems, straightforward restore processes may work. However, for heterogeneous system copies with different operating systems, SAP approval is necessary. SAP uses database-specific methods to ensure system copy integrity and compatibility. Contact SAP for guidance before proceeding. The SAP OS/DB Migration Check is required even for simpler restore processes to ensure a reliable migration.
The database-specific system copy methods for Java systems eliminate the need for JLOAD export/import, simplifying the migration process.
However, SAPINST still needs to be run on both the source and target systems.
SAPINST collects essential system information from the source system, which is necessary to adjust and configure the target system accordingly.
This information helps ensure that the target system runs smoothly on the new platform, maintaining system compatibility and functionality during the migration process.