cancel
Showing results for 
Search instead for 
Did you mean: 

Hardware migration Netweaver04 Windows + SQL

Former Member
0 Kudos

Hi All,

I`d like to know the checklist and the steps for a hardware migration that concerns a BW 3.5 on a Netweaver04 from a Windows 2000 SP4 with SQL v8 to windows 2003 on a new hardware.

Thanks a lot for your help!

Siav

Edited by: Saleki Siavauch on Aug 6, 2008 8:56 AM

Edited by: Saleki Siavauch on Aug 6, 2008 9:15 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

I would recommend that you refer to the homogeneosus system copy guide whihc is available at

http://service.sap.com/systemcopy

Moving between different releases is still termed a homogeneous system copy. The guide will describe the supported methods for copying the system which is one of two things

-> A complete database backup and restore

-> A complete export using sapinst and an import into a new target system.

So long as your system is abap only this should be relatively simple.

Kind Regards,

David

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi David,

Thanks a lot!

Siav

Former Member
0 Kudos

Hi Kevin,

Many thanks for your help!

I think I`ve not been clear enough, it`s an OS and a hardware migration from a W2000 / SQL2000 to a W2003 / SQL2005.

Does what you`ve explained is matching this case?

Many thanks!

Former Member
0 Kudos

Hi Nagaraju,

Thanks for your reply, that helps but I`d like to upgrade also the OS from W2000 to W2003.

Does this upgrade can be done by copying SAP datas from a w2000 to an other hardware platforn installed on W2003?

I do believe that won`t be possible with the restore you`re talking about (because of OS differences)?

Thanks!

Edited by: Saleki Siavauch on Aug 7, 2008 8:34 AM

Former Member
0 Kudos

>

> Hi Nagaraju,

>

> Thanks for your reply, that helps but I`d like to upgrade also the OS from W2000 to W2003.

> Edited by: Saleki Siavauch on Aug 7, 2008 8:34 AM

1. Backup the \usr\sap directory and copy it off to a remote location. Record down the SAP* NT services you have.

- The SAP NT services should be SAP<SID>_<SysNo> and SAPOSCOL.

2. Backup the SAP DB and copy it off to a remote location. Test the backup files by restoring to remote location.

3. Make sure you have all the install bits to install SQL 2000.

4. Record the users, configuration, collation page, etc for the SQL 2000 installation.

5. Flatten and server and rebuild with Windows 2003.

6. Reinstall SQL 2000, restore the SAP DB, and reconfigure per information you recorded in step 4. Make sure you verify the SAP system user access to the SAP DB.

7. Restore the \usr\sap directory from the copy you made in step 1.

8. run: sc
server create "SAPOSCOL" binpath= "drive:\path_to_kernel\saposcol.exe service"

9. run the sapstartsrv.exe and restore the SAP<SID>_<SysNo> NT service.

10. Change both the SAPOSCOL and SAP<SID>_<SysNo> NT service to use a domain account if needed.

11. Start SAP.

This is the cleanest way, I'm not a big fan of "upgrading the O/S". Instead, I rather flatten and rebuild the entire server using the new O/S.

Former Member
0 Kudos

Hi,

As I understand from your statement that you plan to migrate SAP data from old hardware to new hardware. In that case, You need to carry out the following activites.

1. Install Windows 2000 on the new hardware

2. Apply the Service pack (SP4)

3. Install BW3.5 on the target system

4. Peform online backup from the source system

5. Restore Online backup on to the target system

6. Apply all archive logs

7. Bring up the server and make sure all the RFC connections are working.

8. Release server to users.

Hope it helps.

Thanks,

Naga