Homogenous system copy

[ganesh_borase2]

Hello everybody,

we have existing SAP 5.0 in windows 2003 standard edition clustering environment (database : SQL 2000)

now, we have a plan to migrate the existing SAP 5.0 on the new hardware (64-Bit) with the clustering environment.

So please suggest me correct procedure from the following for the migrate

1. Install the SAP on the new hardware (64-bit) and then only copy the database and attach to the fresh installed SAP

also copy the USR folder.

2. Homogenous copy.

Thanks

Ganesh

[xymanuel]

Hi Ganesh,

follow the upgrade Guide like Markus recommended.

Just 2 things:

- Use the MSSQL Upgrade Tools from SAP! You'll find them in the Marketplace.

The Tools will upgrade the SQL Schema an prepare the Database for SQL 2005.

Our migrationpaths were like this (no Cluster Env):

Install new DB Server Environment (MSSQL 2005 64bit) parallel to the running Landscape.

At go live:

1. Stop old SQL 2000, then Shut down old server and remove it from Network.

2. Represent DB and Log LUNs from old Server to new 64 bit OS. Rename the new Server to the name of the old.

3. Attach DB Files in new SQL 2005.

4. Run SAP MSSQL Migration Tools. Finished.

5. Let the old Server untouched for Fallback Szenarios.

Be aware, that if you attach the 2000 DB to the 2005 SQL Server, there is no way back (except of Recover).

Kind regards

Manuel

[markus_doehr2]

I would go for homogeneous system copy together with a database upgrade to SQL Server 2005.

Start with

Note 960769 - Windows: Migration from 32-bit to 64-bit (x86_64)

If you copy the user folder your system will still be 32bit since the kernel you currently run is 32bit. You'll need a new 64bit kernel.

Markus

[ganesh_borase2]

Dear Markus

Thanks for suggestion.

After referring homogenous copy guide, I have plan

On new target system

1. Configure the windows clustering.

2. Install SQl 2000/SQL 2005 database

3. Copy the source system database.

4. then start the fresh SAP installation

<your SAP system>> <software lift-cycle options>><system copy>-->Target system> > <system varient>> technical stack

is it write steps?

but what about the usr application folder

because on fresh installation, that contain not contain the Kernel level.

also some change request files, also some supporting patch files,

2. what is exact difference between the Export/Import the database?

Please suggest me.

Thanks

[markus_doehr2]

- you install the database software with sql4sap.vbs

- you start sapinst with the system copy option

- you'll provide the necessary DVDs (including a 64bit kernel)

- the installation will start running and stops at a point where it asks you to copy the database

- you continue with sapinst

After that you copy \usr\sap\trans etc. but not the kernel.

All those steps are listed in the guide

Markus

[ganesh_borase2]

Hi!

Please suggest

what is exact difference between the Export/Import the database and Homogenous system copy?

Thanks

[markus_doehr2]

Homoegeneous system copy means: you copy a source system to a target system.

There are two methods to do that:

- R3load export/import

- database copy (or detach/attach in case of MS SQL Server)

Markus

[ganesh_borase2]

Hi Markus,

As per suggestion you start sapinst with the system copy option

But when I start the installation only following options are available

so there is no option for system copy

*SAP ERP 2004 SR1*
              ABAP System 
                MS SQL Server
                 Unicode
                    Central Instance installation
                    Database instance installation
                    Dialog instance installation
                    Internet Graphic server upgrade/installation
                   ABAP Database content Export
              Non unicode
 *SAP Netweaver'04 Support Release 1} 

*

Thanks

[Former Member]

The system copy option is under addtional life-cycle menu (something like this) but well documented under system copy guide.