Wednesday, July 27, 2011

Hardware Migration

· Download required software and patches from service market place
· Compare filesystem space with source system database
· Set page memory
Actions on Target server
· Install Oracle RDBMS software
· Apply RDBMS patch to the source patch level
· Install SAP NW2004 with ABAP content
· Install Java add in on ABAP
· Request and Install SAP license for new hardware
· Start J2EE on new server
· Upgrade Kernel to the source patch level
· Take full backup of database
· Take java filesystem backup
· Bring down target server along with DB
· Stop all the services related to oracle and SAP
· Delete data from sapdatas , origlogs and mirrlogs in target system
Actions on source server
· Request Downtime for source server
· Suspend jobs using report btctrns1 in source server
· Bring down application along with DB in source server
· Stop all services related to Oracle and SAP in source server
· Start zipping of sapdatas, origlogs and mirrorlogs
· Zip J2EE filesystem j2EE,SCS, SYS folders.
· Copy the zipped data manually via Wan to target server
Actions on target server
· Unzip the zipped files and place or overwrite them according to the structure
· Change hostname in ABAP according to SAP note 8307
· Change hostname in RZ70
· Change hostname in j2ee config tool according to SAP note 757692
· Start DB,
· Delete source ops$ users and recreate for target server and change the password
· Start SAP and J2EE
· Re Install SAP license
· Reconfigure SMLG,RZ10,RZ04,RZ12, DB13 etc.. accordingly
· Check RFC connections and reconfigure if required
· Reconfigure STMS
· Reconfigure SLD and JCO destinations using visual admin tool.
· Restart cluster for changes to be affected
· Check SLD and portal
· In SLD change hostname in profile and server settings if required
· Reschedule jobs using report btctrns2
· Configure backup strategy
· Take full database backup along with J2EE filesystem.


sap test said...

Appreciable job! You did great job. It is not easy to write step by step procedure for hardware migration. Well done. Keep it up!

Prologic Corporation said...

This is a good article & good site.Thank you for sharing this article. It is help us following categorize:
healthcare, e commerce, programming, multi platform,inventory management, cloud-based solutions, it consulting, retail, manufacturing, CRM, technology means, digital supply chain management, Delivering high-quality service for your business applications,
Solutions for all Industries,
Getting your applications talking is the key to better business processes,
Rapid web services solutions for real business problems,
Web-based Corporate Document Management System,
Outsourcing Solution,
Financial and Operations Business Intelligence Solution,

Our address:
2002 Timberloch Place, Suite 200
The Woodlands, TX 77380


Shruti Ramalingam said...

Thanks for the great information ,was looking for this information from long.Great blog SAP Basis Training in Chennai

Anonymous said...

Hi, We are planning to migrate our SAP ECC 6.0 EHP4 and DB2 database (running in VMWare virtual machines) from one datacentre in South Africa to another datacentre in Frankfurt. The new datacentre has a different IP range and different domain from the current datacentre. My questions are : 1) what are the alternatives for this migration ? 2) Can we move the VMs from the current datacentre to the new one ? 3) What about the different IP range and domain ? That would be an issue ? Thanks in advance. Sergio Sanchez (