Upgrade ecc5 to ecc6 on 32 bit - then migrate to 64 bit

[laurie_mcginley]

A quick question.

We are planning for an upgrade from ecc6, win 2003, sqlserver 2005, clustered. Our ultimate goal is to go to ECC6 on 64-bit hardware and virtualize. I need to explain a couple of different scenarios for an upgrade and the process in general to a group of management and infrastructure folks next week. Specifically I need to be able to explain the upgrade of ecc5 to ecc6 in the current hardware environment, (the new hardware may not be here in time), then migrate that version to the 64-bit version.

As I understand it the "migrate" is a system copy from the 32-bit system on to the 64-bit system. I've done a system copy from our current system to a sandbox of the same installation.

What I'm not yet quite clear on is doing the copy from the 32-bit to a 64-bit system. Would I need to download and install the ECC6 product for 64-bit? I could not use the product install files that we will have for the 32-bit version correct?

Eventually they would like to bring SAP into the virtual environment they are planning. I understand it isn't yet supported (soon...) on Windows 2008 R2, so we wouldn't go directly there. Currently we are using Microsoft clustering for HA option. I would expect to keep that until such time as a move to the virtual is an option.

Any advice or clarifications you may have are very welcome.

Laurie McGinley

[laurie_mcginley]

Further info needed.

Now the question comes up regarding a 3 system landscape.

So if I'm to do a system copy to get from 32-bit to 64-bit I understand the mechanics of that. What I'm not clear on now is how that works in a TEST QAS PROD landscape.

If i migrate TEST, can I continue to support PROD via transports until it gets migrated a few days or weeks later? Or do all 3 systems need to go pretty much at once. Or hold off any critical fixes until all 3 are on the 64 bit platform.

Seems like one answered question leads to more questions I need to ask!

Thanks

Laurie McGinley

Edited by: Laurie McGinley on Aug 5, 2010 3:22 PM

[sunny_pahuja2]

Hi,

Yes, you can transport between the systems. Check SPA note 192822. Check below extract from this note:

15. I run a 3 system landscape. Will I still be able to transport in between systems if I do not upgrade all of them to 64-bit?

yes.

The transport environment is not only database bit independent, it is rather than that even database version and even database platform independent. As long as the transport tools are installed in the correct bit-version on each of your systems, there will be no problems in transporting in between R3 systems, where the database runs with different bit-versions.

Thanks

Sunny

[laurie_mcginley]

Thanks Sunny, that would be good news. I'll check the note out.

Laurie

[sunny_pahuja2]

Hi,

First of all SAP does not support window 2008 R2 whether in virtual or not.

For migration from 32 bit to 64 bit, check SAP Note 960769 - Windows: Migration from 32-bit to 64-bit (x86_64)

Thanks

Sunny

[laurie_mcginley]

Thank you both for your responses. They were both helpful. I've a better understanding and will be able to give our admin folks a little more info now.

Thanks,

Laurie

[tomas_black]

Hello Laurie,

I'm not an expert in clustering but I can try to help on the migration/upgrade question.

- the migration from 32 to 64bit, same OS, platform, etc, is the Homogeneous System Copy. And when performing the 'copy' from 32 to 64bit system you will need the 64bit version of the tolls/products. You can't use - for sure - the 32bit version you have. Same thing for the system upgrade: what matters is the source version, so bear this in mind, you'll have to have the 64bit version of the tools.

I hope this help in some way

Best regards,

Tomas Black