Professional Documents
Culture Documents
Pre-Copy Requirements: SAP System Copy Procedure..
Pre-Copy Requirements: SAP System Copy Procedure..
Here is a procedure I have put together over the years for SAP system copies.
Some of it is specific for the landscapes I setup. This one is for ECC 6.0 on SQL
2005 in Windows Server 2003, but I am sure the general procedure can be very
helpful:
The backup/restore method and the detach/attach method have the following
advantages compared to the R3load/database independent method:
Pre-Copy Requirements
An SAP ECC 6.0 system, QAS, (similar to PRD in memory and disk configuration)
should be installed with a valid SAP license key. (NOTE: Be certain that both the DNS
name and NetBIOS name of the server are in all CAPITALS, 8 characters or less, and
contain no special characters.)
The source system should be backed up (Full Backup) and the media should be
accessible from the target system.
Perform a backup of the original QAS system to restore to in case of difficulties.
Anything from the target that will need to be restored (user definitions, profiles,
jobs, printers, RFC destinations, etc.) after the copy must be saved out. In addition,
take a snapshot of the client change settings (SCC4), system change options (SE03),
workbench organizer/transport system configuration (SE06), and any other setting
that will need to be restored in the target system.
Identify which transports exist in QAS but not in PRD and remind the owners that
all transports which have not moved to PRD before the copy will no longer exist in
QAS. Preferably, everything should be pushed through pre-copy (including LCP and
CRT imports, Hot Packs, and other SAP transports associated with notes).
Communicate to everyone that any spool data, datasets, master data, etc. which
exist only in QAS will need to be moved elsewhere, printed out, or otherwise
repositioned before the copy.
Security profiles and user lists need to be repositioned so they can be recreated
post-copy.
Any external programs affected by the move (BSI, etc.) must be dealt with post-
copy.
System Copy Steps
1. Create Java Export files from the source system:
a. Logon to the source server as an administrator
c. Go to SAP ERP 6.0 > Software Life-Cycle Options > System Copy > MS SQL
Server > Source System Export > Central System > Based on AS ABAP and AS Java >
Database and Central Instance and click Next
g. Enter the backup directory you wish to use for the java migration data in the
Export Location field and click Next
h. Verify the information in the Parameter Summary screen and click Next
j. Copy the export directory to the Target Server for later use
2. Stop the target SAP system with the SAP Management Console
3. Make a copy of all the files in the \QAS\SYS\profile\ directory
4. Create a new backup of the source SAP system database
5. Restore the target SAP system database from the backup created in step 4.
Depending on database size this can take several minutes or several hours.
6. Run the SAP-provided system copy tool:
a. Logon to the target server as an administrator
f. Leave the default path for JDK Directory and click Next
q. Browse to the Migration Export copied in step 1-j and click Next
r. Enter J2EE_ADMIN in the Administrator User field, enter the Administrative
Password in both password fields, and click Next
v. Verify the information in the Parameter Summary screen and click Next
w. Enter the Solution Manager Key and click Next *see appendix for
generating the Solution Manager Key
x. Depending on system size, this may take several minutes or several hours
7. Stop the target SAP system using the SAP Management Console
8. Restore the files copied in step 3
9. Start the target SAP system
10. Cancel any production batch jobs:
a. Transaction SM37, enter job name, user *, and date range including the
next day, job status released and click execute
11. Delete Source System profiles and Import the correct SAP profiles
a. Transaction RZ10
12. Delete Source System Licenses and install the new Licenses
d. If you are unable to install the permanent license key, it may be necessary
to truncate the SAPLIKEY table first, then repeat 12-c
b. Transaction STMS
14. (Optional) Change the login screen to reflect the correct system information
a. Transaction SE61
a. Transaction SCC4
e. Then change the Logical System to the appropriate name, and save
a. Transaction SWU3
17. If you are using BI, re-activate the system in RSA1 on the BI system
18. Check the BSI Tax Factory connection by executing report RPUBTCU0 from
Transaction SE38. The results should show no errors. Warnings are okay.
19. Verify the Adobe Document Services connection
a. Transaction SM59
c. Go to the Logon & Security tab and enter the Administrative Password in the
password field, and save
d. Transaction SE38
f. A simple adobe form with lines and numbers will be rendered if successful
a. Transaction SPAD
e. In the mapping field select the appropriate application server, and save
Appendix:
- Generating a solution manager key
- The target system is installed using the exports from the source system - On the
SAPinst screen SAP SystemDatabase make sure to select Homogeneous System
Copy (MS SQL Server-specific: Detach/Attach or Backup).
- For more information about the system copy procedure, see also SAP Notes 193816
and 151603.
- With SQL Server, you can use backup images across the platforms I386, IA64, x64.
That is, you can make a backup on one type of platform and use it on another type.
- You can only attach SQL Server 2000 files to SQL Server 2005 but not vice versa.