cancel
Showing results for 
Search instead for 
Did you mean: 

Disaster Recovery/High availability iSeries Windows

Former Member
0 Kudos

Hi,

We have iSeries (i550) server that runs SAP 4.7. Taking into account, the hardware failures in the past we have decided to implement a high availability/disaster free site/server.

Taking cost into consideration, we want this live DR site for our Production server(iSeries) to be on Windows platforms. I am not sure how we can achieve this.

We want to have SAP running on iSeries to have a standby backup server on Windows that should track changes on iSeries system, copy/update the same changes to the target - backup SAP database on Windows and in event of Hardware failure/ link breakdown the Windows server should be available to the users with the most recent changes. It means that there should be no or minimal downtime and there should be no data loss.

Can anyone please suggest options to achieve this? Kindly share the DR/HA solutions you have implemented for your SAP landscape

Regards,

Nick Ron

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Nick,

We implemented ORION HA for our DR system real time replication from PRD server to DEV server. We have the same OS V5R4 (i550) and SAP version 4.7

Best regards,

Francis

Former Member
0 Kudos

Hi,

Volker, Thanks! for your inputs. Appreciated. I am exploring on the Remote Journal method however not sure if it would be an ideal solution for high availability and whether it can take care in case of Hardware failure. Any other method or solution you would like to suggest.

We are trying to build a DR site which should get activated with minimal or no downtime.

Can someone share the DR methods you have been following or know if any foolproof methods are there?

Thanks! in advance.

Regards,

Nick Ron

Former Member
0 Kudos

Designing a highly available systems can take quite a bit of planning. There can also be some confusion between HA and DR. The two key objectives for DR to be defined are often referred to as Recovery Time Objective (RTO) and Recovery Point Objective (RPO). Basically this means how long can you afford to be without a system, and how much data can you afford to lose? This is normally a business decision, and may lead to a response of zero and zero. The lower these numbers are the faster the costs rise, and designing a system with no single points of failure can prove quite difficult. For example the enqueue server.

System i has a basket full of solutions - some within i5/OS, some are additional products and some are products offered by our Business Partners. The iSeries HA page might help:

http://www-03.ibm.com/systems/power/software/availability/solutions.html

There is also a white paper that shows one way of doing it using POWERHA.

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101325

I think what I'm trying to say is that without completely understanding your situation, the business, locations, budget, current IT infrastructure, available skill etc I think its impossible to tell you what the answer is.

Former Member
0 Kudos

Hi Nick,

I would say, that is pretty easy:

It is just impossible !!!!

You need the same OS & DB for ANY replication tool, as you cannot apply logs otherwise ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de