System Copy and System Refresh: Key Concepts and Procedures

Definition of System Copy

• Creating a duplicate system or an exactly similar system using an existing system's database.
• Used to build new systems like training systems, proof of concept (POC) systems, or to migrate to a new environment.

When is System Copy Needed?

1. End-User Training:
   • Build a new system identical to the production system (e.g., from December 20th to train users for a go-live on January 1st).
   • Ensures users can practice without affecting the real-time production system.
2. Proof of Concept (POC):
   • Create a new system to test upgrades or new implementations (e.g., upgrading from ECC6 EHP8 to S4HANA).
   • Solves issues on the POC system before applying the changes to the development, quality, and finally production systems.
3. Testing:
   • Create a test system to replicate production scenarios and solve issues before impacting real-time data.

Tools & Procedures for System Copy

Software Provisioning Manager (SWPM)

• A tool used to perform various activities such as system installation, system copy, uninstallation, system rename, dual stack split.
• Installation Master: GUI-based tool for installing SAP systems.

Types of System Copy

1. Homogeneous System Copy
   • Source and target systems have the same OS and database.
   • Can be performed using Backup/Restore Method or R3 Load Method.
   • Backup/Restore Method: Uses tools like BR tools or HANA Studio.
   • R3 Load Method: Uses SWPM; needs r3load.exe file.
2. Heterogeneous System Copy
   • Source and target systems have different OS or databases.
   • Performed using R3 Load Method with Migration Key.
   • SWPM converts source files into target-compatible formats.

Processes

Homogeneous Copy (Backup/Restore Method)

• Suitable if both systems are already existing (e.g., refreshing quality system with production data).
• Steps: Take backup from source system (Production), restore into target system (Quality).

R3 Load Method for Homogeneous Copy

• Use SWPM, select Source system, export data; use same OS and database for the target system.

Heterogeneous Copy (R3 Load Method)

• Requires Migration Key to convert data formats.
• Steps similar to homogeneous copy but involves converting data to the target database and OS formats.

System Refresh vs. System Copy

System Refresh

• Definition: Updating an existing system with data from another system (e.g., production to quality).
• Uses Backup/Restore Method.
• Homogeneous only (same OS and database).

System Copy

• Definition: Creating a new system using an existing system’s data.
• Can be homogeneous or heterogeneous.

Practical Scenarios to Understand

1. Training System:
   • Homogeneous Copy: SWPM R3 Load Method to create identical production system for training (same OS and database).
2. POC System for Upgrade:
   • Heterogeneous Copy: SWPM R3 Load Method with Migration Key (e.g., Oracle to HANA).
3. Quality System Data Refresh:
   • Back up production data and restore to quality using BR tools (Backup/Restore Method).
4. Development System Testing:
   • Regularly scheduled backup and refresh to ensure quality system mirrors production environment accurately.

SWPM Usage for Various Tasks

• Installation, uninstallation, system copy, system rename, dual stack split of SAP systems.
• Installation Master for GUI-based installations.
• r3load.exe for data loading during system copy.
• Migration Key for heterogeneous copy.

Key Points to Remember

• Homogeneous System Copy: Same OS and DB; use R3 Load or Backup/Restore Method.
• Heterogeneous System Copy: Different OS or DB; use R3 Load Method with Migration Key.
• System Refresh: Only for Homogeneous Copy; use Backup/Restore Method.
• SWPM: Crucial tool for system operations (installation, copy, rename).

Conclusion

System copy is essential for maintaining, upgrading, and testing SAP environments. The correct method and tools ensure minimal downtime and effective data migration or duplication.