Skip to main content

Mastering SAP System Copy: Planning a Seamless Migrations in Detail



Source System




System Information 

  • SAP products installed

  • Versions of installed products, for example, enhancement packages, support packages,

kernel version, operating system, and database system

  • Current system landscape

  • Number of systems in a production state

  • System migration order and time schedule

  • Maximum system downtimes for migration purposes

  • System access in case of hosting environments

  • Check all software components to be certain that they can be migrated, especially Java-based components



Technical Information

  • Current hardware (RAM, CPUs, disk subsystem) 

  • Size of the source databases (compressed/uncompressed) 

  • Free local disk space for unloading the database 

  • Largest tables and indexes 

  • Code pages used 

  • Tables in ABAP Dictionary but not in DB or the reverse 

  • External files and interfaces 

  • Procedure for transporting the dump files from the source to the target system

Target System 

Technical Information 

  • Current hardware (RAM, CPUs, disk subsystem) 

  • Size of the source databases (compressed/uncompressed) 

  • Free local disk space for unloading the database 

  • Largest tables and indexes 

  • Code pages used 

  • Tables in ABAP Dictionary but not in DB or the reverse 

  • External files and interfaces



  • Number of CPUs and I/O subsystem details aid in determining the optimal number of export processes.

  • Source database sizes and sizes of the largest tables impact the duration of the migration.

  • During the first test migration, allocate 10%-15% of the uncompressed source database size as free space in the export file system.

  • Determine the approach for handling external files such as spool files, archives, logs, transport files, and interfaces that need to be copied to the target system.

  • If the source and target systems are located in different locations, decide on the available media or methods for transporting the dump files.



A migration test run is essential when for the production system 



Task Name

Detailed 

1. Install migration tools and prepare the source system

- Research and select appropriate migration tools

- Install the chosen migration tools 

- Review the source system and ensure it meets the prerequisites for migration 

- Take necessary backups of the source system

2. Export data from the SAP source system

- Identify the data to be exported 

- Configure the export parameters 

- Initiate the data export process 

- Verify the completeness and integrity of the exported data

3. Install the SAP product and the database software on the target system

- Prepare the target system hardware and software environment 

- Install the required SAP product on the target system 

- Install the compatible database software on the target system



4. Transport/share the data export to the target system

- Transfer the exported data to the target system 

- Ensure the data transfer is secure and reliable 

- Verify the integrity of the transferred data



5. Create an empty target database

- Set up the necessary database instance on the target system 

- Configure database parameters and settings 

- Create the empty target database



6. Load the data export into the target database

- Identify the data import methods supported by the target database 

- Configure the data import parameters 

- Initiate the data import process 

- Validate the data import and ensure its accuracy



7. Complete the installation and perform the follow-up tasks

- Finalize the installation of the SAP product on the target system 

- Configure additional system settings 

- Apply necessary patches and updates 

- Perform system checks and validations



8. Configure the test environment

- Set up a dedicated test environment 

- Configure test system parameters and settings 

- Prepare test data and scenarios


9. Extensively test the migrated system

- Execute various test cases and scenarios 

- Validate the functionality and performance of the migrated system 

- Address any issues or discrepancies identified during testing 

- Obtain user feedback and incorporate necessary adjustments



So as in any project we do the following and it will be talked in detail in later blogs , Final Migration Planning :  


  • Create a cut-over plan 

  • Perform the migration 

  • Perform the follow-up tasks 

  • Check the system 

  • Run a backup 

  • Start production work

Comments

Post a Comment

You might find these interesting

8 Must-Know Questions About Object Store on SAP Business Technology Platform

What is the problem that Object Store solves ? Modern enterprise systems increasingly deal with massive volumes of unstructured data such as documents, logs, media files, and backups. Traditional relational databases are not optimized for such workloads. What is Object Store ? Object storage—commonly referred to as blob storage—addresses this gap by providing scalable, durable, and cost-efficient storage for unstructured data. Object storage is a storage architecture designed to manage unstructured data as discrete units called objects.  Each object consists of: Binary data (file content) : Image , File etc Metadata (descriptive attributes) : File size, Content type, Last modified timestamp, Storage class (hot, cool, archive) Unique identifier (key or URL) : unique path-like string used to locate a blob inside a bucket Unlike file systems or relational databases, object storage does not rely on hierarchical file structures or schemas. The SAP BTP Object Store service is a managed, ...