This Blog provides information about running SAP Applications on the Microsoft Platform. The Blog is written by people who are working with SAP on the Microsoft Platform for decades.
If you want to upgrade your SAP landscape to SQL 2008 (R2) and Windows Server 2008 R2 there are two possibilities. In this blog I will explain the differences between the two approaches and the advantages and disadvantages of both.
Since old SAP releases are not supported on Windows Server 2008 R2 and SQL Server 2008 (R2), you will need to upgrade your SAP software in order to use the new Microsoft releases. You can either upgrade your SAP software on your old hardware, old Windows Server and old SQL Server. This approach is described in chapter 1.
The other approach is to migrate to new hardware, new Windows and new SQL Server first. This approach is described in chapter 2.
Your landscape must not be older than R/3 4.6C. Please see chapter 3 for all relevant SAP Notes.
You first upgrade your SAP release to a newer SAP release that supports Windows Server 2008 R2 and SQL Server 2008 R2. Those are all SAP NetWeaver releases 7.00 and higher. Since 7.30 does not support Windows Server 2003 or SQL Server 2005, you cannot use this migration path if you want to upgrade to 7.30.
After the upgrade you perform a backup/restore system copy (system copy with database specific tools). Please read SAP Note 1152240 for prerequisites of your specific SAP release.
A few months ago, I was working with SAP on a quick migration path for 4.6C, 6.20 and 6.40.
For this migration path you perform the DB specific system copy before you upgrade your SAP release. After the system copy, you are allowed to use your SAP system if you start the upgrade to the new release immediately after the system copy (see SAP Note 1476928 for more information).
The upgrade is performed on the new hardware, new Windows Server and SQL Server release and is therefore much quicker compared to your old landscape.
Thank you for your article. Right now I'm in the same situation to plan the upgrade of our SAP environment from 6.40/SQL2005/Win2k3 to 7.00/SQL2008R2/Win2k8R2. But there is one sentence in note 1443424 (Migration path to Win2008/MSSQL2008 for 4.6C and 6.20/6.40) which is confusing me:
"The upgrade must be started immediately after the system migration. >>>The system must not be used productively until you reach the end of the upgrade downtime.<<<"
It is no problem to START the upgrade after the migration, but first we have the online phases where I could stay productive if I be on scenario 1. With scenario 2 I have to be offline for many more hours or days from the start of the upgrade. This doesn't make sense to me. Do you have a solution for that? Or did I something missed?
your assumption is correct. The old releases are not supported on SQL2008R2/Win2008R2 and are therefore not allowed to be used in production during the preprocessing phases.
Scenario 2 has the advantages that the overall upgrade is much faster because I assume the you are using new hardware for the upgrade and you don't have to perform a system copy after your upgrade which also saves you a lot of time.
If scenario 2 makes sense for you depends on the performance difference between your old and your new hardware.
We are planning to upgrade our EP 6.0(was 640) on sql2000 and windows 2003(x32) to NW 7.3 on sql 2008 windows 2008(x64). We are planning on system copy of EP 6.0(was 640) from Source: on sql2000 and windows 2003(x32) to Target: on sql2008 R2 and windows 2008 R2 (x64).This will be followed by direct upgrade from EP6.0 (was 640) to NW 7.3 I am mainly looking at the notes:
I would greatly appreciate if anyone could comment on this approach and provide me with any insights based on your experience.