on 09-21-2013 11:31 AM
Dear All,
We plan to Set up DR (Diaster Recovery) from Production System.
Hostname, SID, Database ( ORACLE ) , OS (AIX 6.0 ) & Java Version are same in Source and Target DR System .
So we are adapting the System Copy Homogeneous Method.
Setup in Source System:
*******************************
Cluster : YES
Oracle: 11g Version
OS: AIX 6.0
Kernel Version : 720 WITH PATCH LEVEL 401
Installation did Using High Availability Method.
Two Servers Used namely Node A and Node B.
Dual Stack: ABAP+JAVA
NFS Mount is Used.
Node A (Below two are Running in Node A Server)
-- ASCS <Instance Number Used : 00 >---ABAP SAP Central Services
-- D03 <Instance Number Used : 03 >----Dialog Instance .
Node B (Below two are Running in Node B Server
-- DVEBMGS02 <Instance Number Used : 02 >----------->Central Instance + DB
--SCS01 <Instance Number Used : 01>---------------------->Java Instance.
Source System Export Completed and exported in an Exported Directory using Below Method as shown in below screenshot.
Setup in TARGET Diaster Recovery (DR ) System:
***************************************************************
Introduction: 2 Servers Allotted for DR . We need to make use of the two servers efficiently without Cluster.
Cluster : NO
I
Two Servers are given namely Node A and Node B in Target DR Server BUT WITHOUT cluster
Dual Stack: ABAP+JAVA
Here also NFS Mounts are used in Target DR System.
Oracle: 11g Version-------------------------------------------->Completed in Target DR
OS: AIX 6.0
Kernel Version : 720 WITH PATCH LEVEL 401-------------------------------------------->Completed in Target DR
In NODE A Server, We have Target Installation Started using the Below Method and two Instance (DVEBMGS02 & SCS01 ) are Present:
SAP NetWeaver 7.0 Support Release 3 ------->Software life-cycle
options-------->System Copy-------->Oracle--------->Target System
Installation ----->Central System ---->Based on AS ABAP and AS JAVA
----->Central Instance.
Node A:
-- DVEBMGS02 <Instance Number Used : 02 >----------->Central Instance + DB
--SCS01 <Instance Number Used : 01>---------------------->Java Instance.
The Target Installation stopped in Target DR System in Backup / Restore Phase and We have Taken the Offline backup and Restored in Target DR .
After Restore, We have Proceeded with the "TARGET DR Installation from BACKUP / RESTORE PHASE.
Kindly Clarify the Below Queries as per the information given above.
*****************************************************************************
1) We have allotted two Servers for DR Setup. No cluster concept used in DR setup but two servers are allotted for us.
So if we install the Dialog Instance in NODE B server, will the NODE A server (CI + DB ) and NODE B (D03 ) Server gets connected without Clusting concept???
2) Generally , Can we connect two SAP Servers ( Node A and Node B Servers ) without Clustering
3)In Target DR Setup, how can we make use of the Servers ( Node A and Node B ) efficiently without clustering. Is it possible to conect two SAP Servers without Clustering. .
4)How can we install ASCS because in our case ASCS is present in Source System (Node A server ) and how can we install in Target DR System.
5)How the Instances (ASCS ,D03, DVEBMGS02 & SCS ) should be distributed and Connected on TWO SAP Servers without Clustering
Kindly clarify the above Queries.
Regards,
Gayathri.K
Hello,
Q-1 You can connect 2 servers. In normal scenarios, when we install Dialog instance on another server then it connects to CI without any problem.
Q-2 Yes. As replied in Q-1.
Q-3 Same as above.
Q-4 Do you need cluster in DR site ? If not, then you need to install ASCS instance for that.
Q-5 You can connect n number of servers with central instance. You can install multiple dialog instances on different servers which will connect to CI for load balancing purpose. So, it is not just cluster that use 2 different servers.
In your this approach, I see some problem. Since, your system is dual stack system, so when you will start replication from primary to this DR site then secure storage and other settings that remains in database will be of primary instance. As a result, when you will start system then there is possibility that your Java system will not come up and you need to perform manual tasks in config tool. Please perform this testing prior to make your DR live.
Thanks
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
79 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.