Professional Documents
Culture Documents
A Step-by-
Step Guide
http://www.ivobe.com/sap-software/how-to-do-sap-system-copy/
An SAP system copy is one thing a SAP Basis administrator will undoubtedly be asked to do. It is
common for companies to want their SAP test system to look like their production system and thus,
will require a copy of SAP system. It may even be on a regular basis (i.e. quarterly). It is our intention
to walk you through the steps of performing an SAP system copy by detailing (1) pre-copy steps, (2)
copy steps, and (3) post-copy steps.
This procedure expects that the SAP system and Oracle are already installed and the system copy is
just a database switch.
A. Pre-Copy Steps
1. Note what date / time to which you will restore.
2. Issue a freeze on transports to TEST. Emergencies will then go directly to PRODUCTION (if
a different TEST system is not available).
3. Note all transports that have not gone into PRODUCTION, but are in TEST.
4. Note all transports that have gone to PRODUCTION after the date / time of the restore point.
5. Shutdown SAP and Oracle on the TEST system.
6. Remove all Oracle data files on TEST.
Using the restore date and time, copy PRODUCTION data files, log files, and controlfile from
Copy files
tape to TEST.
Modify Control File Modify the control file to match the directory paths for TEST.
R3trans d
Check R/3
Connection
If R3trans d does not give a 0 return code it will be impossible to start SAP correctly.
Click Install -> Enter system number and key (You can get this from SAP Service Marketplace.)
Choose the profiles of the PRODUCTION server Profile -> Delete -> All versions -> of a profile
Execute.
Click Execute.
Choose X for released, finished, cancelled, and delete with forced mode.
Utilities -> For output devices Assign server
Execute.
Check the logon groups and delete the PRODUCTION logon groups and create the TEST logon
groups.
Delete old update requests.
SM12 (Delete Locks) Delete old lock requests.
SPAD -> Administration -> Check Consistency -> Delete all errors
SWU3 -> Red beach ball icon
SCC4 (Client Settings) Make sure the client settings are correct.
SGEN Execute in background (This will run for a long time. It is okay
(Regeneration of to continue to work in the TEST system, however it will be slow
programs) as the regeneration takes a lot of resources).