System Copy GuidesVolume 1 Homogeneous System Copy using Online/Offline Database Backup Company : Enterprise Area : System Copy Scenario : Online/Offline backup DOCUMENT APPROVALS Name Consultant Project Manager Trinty Touch Core Team Process Owner Project Manager Responsibility Signature Date . 0 Date Author Reviewed By Change Control .DOCUMENT INFORMATION Project Name System Copy Document Name Document Location Backup restoration DOCUMENT HISTORY Version 1.0 Document Name Backup restoration V1. If The system copy takes place between systems with different platforms ( at least one of the component must be different. we call this HOMOGENEOUS SYSTEM COPY.7. You should perform upgrades in a test system first. There 3 ways of a Homogeneous System Copy in R/3 Systems. 1. you have to create all drives where datafiles resides on source system. Restore Online/Offline Backup of Source System onto Target System.1. To copy large clients. The command reference given in this guide is taken from a homogeneous system copy done on AIX 4. Differences of other platforms such as Windows will be shown in the same sections. You have sufficient free space for sapdata directories on target system.7 platform. This guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.1/Oracle 9.1. Recovery of Oracle Database on Target System. Create CONTROLFILE creation script on Source System. 3. The procedure described tested on AIX 4. Thus. OS or RDBMS ).1/Oracle 8.3. Homogeneous System Copy using R3LOAD Procedure. AIX 5. Homogeneous System Copy using Online / Offline Database Backup. . Homogeneous System Copy using Online/Offline Database Backup This guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.1. Also Patch levels must be same.2.7 platforms. Use most current database backup in order to shorten database creation time. Completion of System Copy Prerequisites Following conditions must be provided to copy a system: Both Source and Target Systems must have Same Operating System and Database System. Steps for a Homogeneous system copy are briefly as below: Preparations on Target System. AIX 5.1. 2. training or standby system (Oracle and Informix: standby systems cannot be created with a system copy).3. For Windows systems. If a client very large to export/import. Homogeneous System Copy using R3COPY Procedure. we call this HETEROGENEOUS SYSTEM COPY.3/Oracle 8.0 and Win2K/Oracle 8. demo.7. This way you can identify customer pecific problems which might result from modifications. Modification of CONTROLFILE script and creation of CONTROLFILEs of Target System. To recover a system on another machine with the same platform after a crash.Area : SAP Basis Topic : Homogeneous System Copy using Online/Offline Database Backup Author : System Copy Guides Homogeneous System Copy using Online/Offline Database Backup Reasons for Copying a SAP System SAP recommends that you make a system copy in order to build a test. we can sort the general needs for a system copy as follow: To create a new training system for end-user or project team education To create a DEMO system To create a Test system for upgrade or other purposes. it is better to do a system copy rather than client transport. If a system copy takes place between systems with same platform ( operating system and database system ) .3/Oracle 8. Here below are the commands to clean directories. Data and Log directories on target system must be cleaned before restoring source database. Procedure: 1. . Before this. Backup source system Take back up of source system (either with DB13 or Brtools). you have to stop all SAP and Oracle processes.Type : Handbook Document Area : SAP Basis Topic : Homogeneous System Copy using Online/Offline Database Backup Author : Procedure 1. Stop sap and db along with its services.sql’. 2. Place backup log file *.afd in sapbackup folder.Type : Handbook Document Area : SAP Basis Topic : Homogeneous System Copy using Online/Offline Database Backup Author : Take backup of controlfile at source system Sql>Alter database backup controlfile to trace as ‘d:\new. Activities to be done on target system First of all. copy the whole backup to target system. Empty following folders: SAPDATA_HOME\sapdata1\sysaux SAPDATA_HOME\sapdata1\system SAPDATA_HOME\sapdata1\temp SAPDATA_HOME\sapdata1\undo SAPDATA_HOME\sapdata1\cntrl SAPDATA_HOME\sapdata2\sr3_1 ………sr3_n SAPDATA_HOME\sapdata3\sr3702_1 ……… sr3702_n SAPDATA_HOME\sapdata4\sr3usr_1 Also delete all the three control files placed at: SAPDATA_HOME\origlogA\cntrl SAPDATA_HOME\origlogB\cntrl SAPDATA_HOME\sapdata1\cntrl . OrilogB. sapdata1. change <sid> set Noresetlogs to resetlogs change reuse to set.Type : Handbook Document Area : SAP Basis Topic : Homogeneous System Copy using Online/Offline Database Backup Author : 3. Start db services.afd –d disk –c The restore will be started. 5. 4. Control file Recovery delete the control file that are restored from backup from orilogA. to restore the backup. login with <sid>adm user and open the command prompt Sidadm> brrestore –m full –b *. Controlfile got generated. * in case of online backup. run command . Restoration from backup on target system Now. now we need to paste that backup to sapdata_home\oraarch) Then. Save the file. Login with sidadm user: login in db : sql>@’trace file path’. Edit the controlfile backup trace file: Delete all the matter above the ‘startup nomount’ and below the ‘characterset’. we do have backup of Archive logs. Install Sap License through Tcode: slicense 2. if SID is not changed) License in new system created on target system. OPS$HOSTNAME\SAPSERVICESID Create user “OPS$Host_name\SIDADM” identified externally. Logon to the SAP R/3 System and goto TCODE SE06. Sql> alter database open resetlogs.connect to “OPS$Host_name\SAPSERVICEDSID”. You can use previous systems (on target system. Grant select. Se06 Change all of the Source System Objects to Target System Objects as asked. Change the password for sapsr3 user Sidadm> brconnect –u /-f chpass –o sapsr3 (it will ask for new password to set) Default password is “sap” Post Installation Step : As your Hardware Key is not changed. Create user “OPS$host_name\SAPSERVICESID” identified externally. Grant resource.sapuser to “OPS$host_name\SIDSERVICESID”. you don't have to get additional License Key from SAPNET. Grant resource.sapdba to “Host_name$DEV\ORASID”.connect. 1. Select "Database Copy or Migration" and execute "Post Installation Processing". Create table sapuser as select * from “OPS$Host_name\SIDADM”.sapuser. OPS$HOSTNAME\ORASID.dba. Grant resource.connect. 6.sapdba to “OPS$Host_name\SIDADM”.dba.Type : Handbook Document Area : SAP Basis Topic : Homogeneous System Copy using Online/Offline Database Backup Author : Sql> recover database until cancel using backup controlfile. Create users as per note 50088 Create the users: OPS$HOSTNAME\SIDADM. Create user “OPS$host_name\ORASID” identified externally. .update on “OPS$Host_name\SIDADM”. After all of above steps. .Type : Handbook Document Area : SAP Basis Topic : Homogeneous System Copy using Online/Offline Database Backup Author : 3. you have completed a System Copy using Online/Offline Database Backup. Delete old TMS configuration and make new configuration for TMS via STMS TCODE. 4.