SAP System Copy.pdf

System Copy GuidesVolume 1

Homogeneous System Copy using Online/OfflineDatabase Backup

Company :Enterprise Area : System CopyScenario : Online/Offline backup

DOCUMENT APPROVALS

Name Responsibility Signature Date

Consultant

Project Manager

Trinty TouchCore Team

Process Owner

Project Manager

DOCUMENT INFORMATION

Project Name Document Name Document LocationSystem Copy Backup restoration

DOCUMENT HISTORY

Version Document Name Date Author ReviewedBy

ChangeControl

1.0 Backup restorationV1.0

Area : SAP BasisTopic : Homogeneous System Copy using Online/Offline Database BackupAuthor :

System Copy GuidesHomogeneous System Copy using Online/OfflineDatabase BackupReasons for Copying a SAP SystemSAP recommends that you make a system copy in order to build a test, demo, training or standbysystem (Oracle and Informix: standby systems cannot be created with a system copy). You shouldperform upgrades in a test system first. This way you can identify customer pecific problems whichmight result from modifications. Thus, we can sort the general needs for a system copy as follow:To create a new training system for end-user or project team educationTo create a DEMO systemTo create a Test system for upgrade or other purposes.To recover a system on another machine with the same platform after a crash.To copy large clients. If a client very large to export/import, it is better to do a system copy ratherthan client transport.If a system copy takes place between systems with same platform ( operating system and databasesystem ) , we call this HOMOGENEOUS SYSTEM COPY.If The system copy takes place between systems with different platforms ( at least one of thecomponent must be different, OS or RDBMS ), we call this HETEROGENEOUS SYSTEM COPY.There 3 ways of a Homogeneous System Copy in R/3 Systems.1. Homogeneous System Copy using Online / Offline Database Backup.2. Homogeneous System Copy using R3LOAD Procedure.3. Homogeneous System Copy using R3COPY Procedure.This guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.The procedure described tested on AIX 4.3.3/Oracle 8.1.7, AIX 5.1/Oracle 8.1.7, AIX 5.1/Oracle 9.2.0and Win2K/Oracle 8.1.7 platforms.The command reference given in this guide is taken from a homogeneous system copy done on AIX4.3.3/Oracle 8.1.7 platform. Differences of other platforms such as Windows will be shown in the samesections.Homogeneous System Copy using Online/Offline DatabaseBackupThis guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.Steps for a Homogeneous system copy are briefly as below:Preparations on Target System.Restore Online/Offline Backup of Source System onto Target System.Create CONTROLFILE creation script on Source System.Modification of CONTROLFILE script and creation of CONTROLFILEs of Target System.Recovery of Oracle Database on Target System.Completion of System CopyPrerequisitesFollowing conditions must be provided to copy a system:Both Source and Target Systems must have Same Operating System and Database System. AlsoPatch levels must be same.You have sufficient free space for sapdata directories on target system.For Windows systems, you have to create all drives where datafiles resides on source system.Use most current database backup in order to shorten database creation time.

Type : Handbook DocumentArea : SAP BasisTopic : Homogeneous System Copy using Online/Offline Database BackupAuthor :

Procedure1. Data and Log directories on target system must be cleaned before restoring source database.Here below are the commands to clean directories. Before this, you have to stop all SAP andOracle processes.

Procedure:1. Backup source system

Take back up of source system (either with DB13 or Brtools).


Take backup of controlfile at source systemSql>Alter database backup controlfile to trace as d:\new.sql;

2. Activities to be done on target system

First of all, copy the whole backup to target system. Place backup log file *.afd in sapbackup folder. Stop sap and db along with its services. Empty following folders:

SAPDATA_HOME\sapdata1\sysauxSAPDATA_HOME\sapdata1\systemSAPDATA_HOME\sapdata1\tempSAPDATA_HOME\sapdata1\undoSAPDATA_HOME\sapdata1\cntrlSAPDATA_HOME\sapdata2\sr3_1 sr3_nSAPDATA_HOME\sapdata3\sr3702_1 sr3702_nSAPDATA_HOME\sapdata4\sr3usr_1Also delete all the three control files placed at:SAPDATA_HOME\origlogA\cntrlSAPDATA_HOME\origlogB\cntrlSAPDATA_HOME\sapdata1\cntrl


3. Restoration from backup on target system

Now, to restore the backup, login with adm user and open the command promptSidadm> brrestore m full b *.afd d disk c

The restore will be started.

4. Control file Recovery

delete the control file that are restored from backup from orilogA, OrilogB, sapdata1. Edit the controlfile backup trace file:

Delete all the matter above the startup nomount and below the characterset;change set Noresetlogs to resetlogschange reuse to set.

Save the file. Start db services. Login with sidadm user:

login in db :sql>@trace file path;Controlfile got generated.

5. * in case of online backup, we do have backup of Archive logs, now we need to paste thatbackup to sapdata_home\oraarch)Then, run command


Sql> recover database until cancel using backup controlfile; Sql> alter database open resetlogs;6. Create users as per note 50088

Create the users: OPS$HOSTNAME\SIDADM, OPS$HOSTNAME\ORASID,OPS$HOSTNAME\SAPSERVICESID

Create user OPS$Host_name\SIDADM identified externally; Grant resource,connect,dba,sapdba to OPS$Host_name\SIDADM; Create user OPS$host_name\ORASID identified externally; Grant resource,connect,dba,sapdba to Host_name$DEV\ORASID; Create user OPS$host_name\SAPSERVICESID identified externally; Grant resource,connect to OPS$Host_name\SAPSERVICEDSID; Create table sapuser as select * from OPS$Host_name\SIDADM.sapuser; Grant select,update on OPS$Host_name\SIDADM.sapuser to

OPS$host_name\SIDSERVICESID;

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, you don't have to get additional License Key from

SAPNET. You can use previous systems (on target system, if SID is not changed) License in newsystem created on target system.

1. Install Sap License through Tcode: slicense2. Logon to the SAP R/3 System and goto TCODE SE06. Select "Database Copy or Migration" and

execute "Post Installation Processing".

Se06Change all of the Source System Objects to Target System Objects as asked.


3. Delete old TMS configuration and make new configuration for TMS via STMS TCODE.4. After all of above steps, you have completed a System Copy using Online/Offline Database

Backup.

Database Backup

SAP System Copy.pdf

Documents

Transcript of SAP System Copy.pdf