How to change SAP from Cluster to Standalone configuration

[Former Member]

Hi All,

We have ECC 6.0(no EHP), Windows 2003 SP2, SQL Server 2005 SP4 configured in a Failover cluster with MSCS (we will eventually upgrade OS and DB).

We have a requirement to switch SAP and SQL Server from the current cluster configuration to standalone.

I would appreciate if anyone could provide me with the steps to do this and/or any hints or things to watch when executing this procedure?

Regards,

[former_member188883 · Accepted solution]

Hi Ariel,

As you might be aware both Windows 2003 and MSSQL 2005 are out of support from SAP.

Also I understand from your message that you plan to upgrade OS and DB.

The best approach would be to migrate existing ECC system to a new hardware with new OS and DB combination. Target system should be installed without cluster during migration.

You may check PAM for supported OS and DB version for ECC environment.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Thanks Deepak,

We will go the migration route to a new system without cluster.

Ariel

[Former Member]

Also, as additional information that confirm the above approach.

Check the following quotes from SAP Note:

1494740  - SAP System Migration from Older Windows Releases to Newer Ones

" In-place upgrades on Microsoft Failover Clusters are not supported.

Microsoft does not support in-place upgrades from a Windows Server 2003 cluster (MSCS) to Windows Server 2008 Failover Cluster, or from any Windows Server that is part of a Failover Cluster.

Therefore, you cannot use the in-place upgrade for a high-availability SAP system on Windows."

AND

The following list shows some examples where you must perform a system copy and you cannot perform the Windows in-place upgrade.

• The hardware vendor does not support the Windows target release version.
• The database vendor does not support the Windows target release version.
• SAP does not support the SAP release on the Windows target release version.
• There is no downtime time slot to do a Windows in-place upgrade.
• For your productive system only short downtime periods are allowed, which might be exceeded when performing the in-place upgrade.
• You run an SAP system with Microsoft Failover Cluster.
• You use incompatible third-party applications or system drivers.
• You use Windows on Itanium servers (IA64).