cancel
Showing results for 
Search instead for 
Did you mean: 

DR system for NW MS-SQL 2005

Former Member
0 Kudos

Hi experts,

We are planning to implement a production with a DR system. The DR system located at remote site will be a standby machine for the production system on MSSQL 2005 win 2008. Both of these severs able to ping each other via WAN and having the same specs.

Both the Production and DR system is NW 7.0 with ABAP + JAVA (XI & EP) and we are planning to install with same SID.

The DR system will be install using system copy. On the regular update from Production to DR, we are planning to use MSSQL Log Shipping method.

1) Log shipping has taken care the MSSQL 2005 part. However, we are not sure on the Java part transfer from the production to the DR? How is normally done.

2) The production server has a local hard disk and external storage(san). The db files will be installed on external storage and Windows on local hd. Where is SAP applications normally installed, local hard disk or external storage (san). What is the advantage and disadvantage for installing in local and external?

Appreaciate any help on this and if you could guide me to some documents specifically related to the above.

Any precaution when do the installation to take note.

Thanks in advance.

kb

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

For Java .. use file replication tools to do replication.. The required files are available at /usr/sap/SID/../J2EE..

But remember this will not be same as installing Java packages . You will have to install Java packages separately ...

regards,

Pravash Raikar

Former Member
0 Kudos

Hi Kb,

Log shipping has taken care the MSSQL 2005 part. However, we are not sure on the Java part transfer from the production to the DR? How is normally done

Is your Abap+Java running with same database?(I mean is that Jual stack or Single stack)

I guess its Jual stack.( Abap+Java on same Database)

If its Jual Stack, Logshipping is enough.No need to think specially for Java.

If its Single stack,that means your ABAP and Java Engines are running on seperate databases.

In this case, Logshipping will take care of your ABAP (your databse is SQL) and you need to restore your JAVA databse separately and its manual process. I am not aware, whether some automated procedure is there for JAVA as Logshipping exists in SQL.

The production server has a local hard disk and external storage(san). The db files will be installed on external storage and Windows on local hd. Where is SAP applications normally installed, local hard disk or external storage (san). What is the advantage and disadvantage for installing in local and external?

Generally OS files will be install in local disk.And our SAP DB files recommended to install in SAN.

Its because, you can get more performance from SAN than the local disk.

Thanks & Regards,

Nagendra.

Former Member
0 Kudos

Hi KB,

I can share my experience and i hope that would help you in building DR setup

Assumming you have both Production & DR systems builded. In brief, we have OS level scheduled tasks to copy the content of our \usr\sap directory content into DR systems at regular intervals. And below are the no of schedule task that you need...

1. Ensure your SAN based disk content are in sync, In our setup we ensure both DB & CI content is stored in SAN based disk and are in sync all the time (using the concept of establish/split of EMC SAN)

2. Ensure, you all the required Profiles (that are specific to DR system host names) are in place.

3. create a schedule taks, for copying all DLLs of OS directory (winnt)

4. create a schedule task, for copying your DI instance \usr\sap content

5. create all environment variables

6. When you want to fail-over (PROD->DR), ABAP stack of system would come online provided DB & it's coresponding \sa\<SID> and profiles content in place.

7. For JAVA based instance you need to reform ConfigTool changes, wherein you modify the DB Connection specific settings and Instance Properties such that your DR system ConfigTool contains the DR system hostnames rather Production (because the \usr\sap & DB content is from Production system copied over to DR)

All these above mentioned scheduled tasks to copy the content of Production System over DR system is using ROBOCOPY of windows command line utility. so you need completely knowledge of ROBOCOPY to prepare those scripts such that expected content is copied over to DR systems.

My only intention was to give some glance overview of preparing DR systems prior to DR activation and while DR activation. Beyond this scope of explaination certainly not that i can share in this forum.

I hope this helps in startup with your preparation.

Regards

Sekhar