Upgrade and Redundancy

[said_shepl]

Hi Expert,

    We have a 3 tire SAP System (DEV,QAS and PRD),

we under Windows 2003 and SQl 2005 Environment,

We are upgrade our DEV & QAS Environment to Windows 2012 and SQL 2012,

We now plan to Upgrade our Production server also to the same (Win,SQL) 2012,

Also we want to  make a redundancy server to Our production serve as (active to passive Or active to active) in anticipation of any database corruption because we face this problem in the first of this year.

What's the correct solution we can do it?

what's available material to help me to implement this solution?

what's the type of replication we can do?

How we can make a tow sap system work in the same DB on time?

Are anther sap instance on the new server will take the same name or not?

Summary i want to find a solution for no down time if database corrupted suddenly.

BR

Said Shepl

[Former Member]

Hi,

If you have a mock run on you QA system just before the production then even full backup of your Production can work as fall back solution.

If you need system readily available then the only option is to create a DR and keep it down before you start the actual upgrade on Primary so that your Standby can be activated if any issue during the upgrade.

Regards,

Nick Loy

[said_shepl]

Dear Deepak,

        Are you mean by create manual DR setup within co-location of Production system.

make the following:-

1- we must a build new server and

2- install sql 2012 on it

3- make a system copy with the same instance name,

4- Built replication between the tow server.

According to we have a production system is up now and work in SQL 2005,

BR

Said Shepl

[former_member184473]

Hello Said,

Before upgrading to SQL Server 2012, make sure your source system (Wid 2003/SQL 2005) have the minimum SP Stack required as per note 1651862.

Also check note 1676665 for further information.

Best regards,

Eduardo Rezende

[former_member188883]

Hi Said,

As you have MSSQL 2005 in PRD , your DR should also have 2005. This will ensure a fall back system available incase you have problems with PRD DB upgrade.

Hope this helps.

Regards,

Deepak Kori

[said_shepl]

Dear Deepak,

        we was have this solution before that but on 2003 and sql 2005.

Our Production server was on SAN storage and cluster with tow SAP instance(Central instance on a server and Dialog instance on another server) built on Windows Cluster.

Due to Electricity problem our database on SAN is corrupted,

Because of this we want a solution for completely separated server and with separated DB with minimum Down Time .

BR

Said Shepl

[former_member188883]

Hi Said,

Due to Electricity problem our database on SAN is corrupted,
Because of this we want a solution for completely separated server and with separated DB with minimum Down Time .

You can create manual DR setup within co-location of Production system.

Here you manually sync up DR system with data and logs. This can be used incase your Primary goes down . This DR system will have same hostname ( virtual hostname) so that users need not change any entry in SAPlogon pad while using DR system.

You may also look for other alternate solution which is based on SAN replication. Check with respective hardware vendor for the same.

Hope this helps

Regards,

Deepak Kori

[former_member188883]

Hi Said,

You may implement DR solution using MSSQL 2012 Alway-on solution.

Refer to blogs in the link below

http://blogs.msdn.com/b/saponsqlserver/archive/tags/alwayson/

Additionally information in link

SQL Server AlwaysOn - SAP Business Continuity - SAP Library

Hope this helps.

Regards,

Deepak Kori