System Refresh

System Refresh: Backup/Restore Method (Oracle & Linux Environment)

Scenario

Source System

• SAP ECC6.0 with Kernel Release 700
• Oracle Database 11g
• SUSE Linux

Target System

• SAP ECC6.0 with Kernel Release 700
• Oracle Database 11g
• SUSE Linux

•  Point in Time Recovery Method

Pre-Steps

1. Check the database backup for source and target systems are completed successfully.

2. Check the sapdata directory size for source and target systems are sufficient.

# df -kh | grep sapdata

3. Put the system messages via transaction code SM02 on the target system to warn users that the system refresh is happening.

4. Create a control file of the source system and sent to the target system. Please be aware that the creation of the control file is advisable to generate after the source system backup is completed. This is because we are using point in time recovery method. This is to avoid any other sapdata is added in between the control file is created.

5. On transaction code SE10. Tick all for Request Type and tick only Modifiable for Request Status. List down all the transport that has not been released. Forward the transport list to the appropriate team (Functional) for further analysis. (Hint) You can released the transport directly via transaction code SE03. All Modifiable transport will wipe out after the system refresh.

6. If your refresh system is in CUA landscape (child CUA), please take the screenshot as per this linkhttp://itsiti.com/find-cua-parent-sap-system

7. Take screenshot of SCC4: Client Overview (including the each client details). Compare with the source system and please be noted that on each client that are not existed, you will need to use SAP_ALL during the client copy process.

8. Screenshot of SCOT, STMS, SMLG, RZ12, RZ04, DB13, BD54, WE20, WE21, SM37 – capture all released jobs, STRUSTSSO2, SE06, RSA1, RSA7.

9. Export the User Master Export (UME) from client 000 and client production(s). Please refer tohttp://itsiti.com/sap-client-export-import-using-scc8

10. Export the all the printer configured to your local computer/laptop. Please refer tohttp://itsiti.com/export-import-printers-in-sap

11. Export the RFCDOC & V_TBDLS tables via transport of copies. Please refer tohttp://itsiti.com/export-import-table-rfcdoc-v_tbdls-via-transport-of-copies

System Refresh

1. Bring down the target system and delete the SAP data files on the target system. Now, copy the SAP data files from source to the target system.

2. Edit the control file (adapt the control file to target SAP system). Create the control file and open the database.

3. Add Temp files to database (PSAPTEMP)

4. Import the table.

5. Disable R/3 RFC destinations

6. Cleanup SID –dependent tables

7. Create the OPS$ connect mechanism.

Post Steps

1. Install License Keys.

2. Disable Background work processes

3. Check SAP/Oracle connectivity

R3trans -d

4. Edit and adapt below configurations from the following transaction codes and reports
• SCC4 – Change Client Role
• SE06 – Set System Change settings
• STMS – Configure Transport System
• SCOT – Disable Smtp Client
• SM37 – Set All Batch Jobs To Scheduled Mode
• SICK – Check System Is Ok After Restart
• DB02 – Refresh Database Stats
• BD54 – Change Logical System Descriptions
• SPAD – Convert Printers
• RZ10 – Import Active Profiles
• RZ04 – Delete And Recreate Op Modes
• Update RFC Destinations
• Delete Old OSCOL Definitions
• SMLG – Delete And Recreate Login Groups
• SM61 – Update Batch Processing Servers
• RSTS0022 – Delete Old Temse Objects
• RSBTCDEL2 – Delete Old Batch Job Logs
• SE61 – SAP Sign On Message
• Delete And Recreate DB13 Jobs
• RZ12 – Delete And Recreate RFC Login Groups
• SCUA, SCUM, SCUG, SCUL – Central User Administration
• WE20, WE21 – Partner Profiles
• SM36 – Configure SAP standard jobs
• SWU3 – Automatic Workflow Customizing
• SECSTORE – Administration program for SECURE STORAGE
• SCC7 – Import / Post processing of users
• SM21 – Check system log
• ST22 – ABAP dump

5. Perform full backup and hand over to ABAP and FUNCTIONAL team to verify!