Migrate production onto new hardware

[Rampa]

Hi,

Windows 2003 Enterprise
Oracle 10g
SAP R/3 4.6C

I have successfully moved our QA and Test boxes to new hardware by building the new box with a different OS hostname and refreshing the data from a backup of production. I ran both the boxes side by side and when everything was tested removed the old box from AD, renamed the new box and updated the profiles, tnsnames etc..

This works fine and i have encountered no issues. However, we need to move our production box onto new hardware but SAP have said they will not support the above method therefore i will need to use a Homogenous System Copy.

I will have to backup production, perform an export then copy this onto the new box. Remove the old Production server from AD and unplug from the network. Then, rename the new Prod box and add this to the domain. Install R/3 using the system copy.

Is this the only way to achieve this? Is there no way to run 2 systems in parallel then when ready 'switch off' the old box and bring up the new one?

I need to keep the same Hostname on the new box.

I hope this makes sense to someone.

Thanks,
Rampa

[Portal]

My SAP system are on a SAN system and when i switched from a 32-bit system to a new 64-bit systems. Here's what I did:

1. install new 64-bit system with SAP and Oracle.
2. install SAP with SAP's database load
3. test the system.
4. when ready, shutdown SAP and Oracle on source system
5. ask my SAN admin to move partition from source system to new system
6. convert DB to 64-bit
7. start SAP.

Note that steps 4 to 7 took me less than 15 minutes. SAP says they do not support this? I did it nonetheless.

Cheers

[Golfi]

Also, have a look at my recent post regarding the hardware license key which needs to be replaced if you have a new NIC.

http://www.sap-forum.org/showthread.php?t=877

[Rampa]

Thanks for the replies.

I guess what i am really after is having a system running in parallel with our production box and when everyone is happy it works switch over to the new box.

Is there anyway this can be done and supported by SAP?

Thanks,
Rampa

[Portal]

No, this is not supported. If both systems work in parallel, how will you switch data entered in the first one to the second one? You cannot use twice the same system and beleive that data will be in-sync.

[Rampa]

I wouldn't need them to be in sync. When we are happy the new system is working i would stop SAP on the old box, back it up then restore it to the new box. I would then change the Hostaname and IP address to reflect the old system, update the SAP and Oracle files with the new hostname and then begin using this as the production box.

I have tested and documented this procedure in-house (on our project and qa boxes) and it works fine and lets us do as much testing beforehand as well as cutting down the migration time.

Any input would be greatly appreciated. Also, if i am forced to carry out a Homogeneous copy can you outline the steps needed to transfer onto a new piece of hardware with the same hostname and ip address.

Many thanks for the responses!

Rampa

[Portal]

Ok, then, this is something else. read the homogeneous system, copy guide, you'll find all the post-processing steps that needs to be accomplished for the hostname and SID change.

This being said, I did the same thing as you but chose the SAN trick to make it faster. Are you on a SAN?

[ERP]

Hello,

1. What is the difference between the 2 boxes? Why do you have to move the system?
HomoCopy restores database from a backup. So the only difference between your method and the SAP supported one is the way how the system environment is built.

2. if you run 2 PRD systems in parallel then some important tests can not be done (most important INMO) and some restrictions have to be implemented

- users have to be warned that the "new" PRD system is only for test. All entered data will be lost.
- All interfaces have to be cut. You can not test whether interfaces works correctly or not because there is a possibility that the requests sent from new system will be replied toward the old system.

Regards,

ERP

[Rampa]

The reason we are moving is the old server is out of warranty and the new server is higher spec.

There will only be a few functional users testing the box and I agree that we can only do so much testing but it would be more than if we to carry out an install from scratch using a homogeneous copy.

Looking at the post Homogeneous copy steps for changing Hostaname and SID they are the same as what I have already.

I think I might go for it as I have tested the process and proved it works. I will just be refreshing the system as opposed to doing a system copy (again we use this method on a monthly basis to refresh our test boxes).

Then when we are happy the new box is working I will backup the old box then shut it down. Refresh the the new box, change the hostname and IP, update the profiles etc then startup SAP.

Hopefully all going well we will have a new Production box!

Regards.