Secondary Enterprise Server and DR

m_e_wade

Active Member
How would you do this:
Customer has two Enterprise server, located several hundred miles apart across a WAN. The Primary system is fully functional and live. The secondary server has been set up identically with it’s own Deployment server, but are known to the system as a Second Enterprise server and a Secondary Deployment server. Libraries are being mirrored from the Primary to the Secondary with third party software.

Customer wants two things – He wants DV and PY to run from the secondary system like a second Enterprise server, with it’s own set of development Fat Clients and JAS server.

He then wants PD available for Disaster recovery. Something along the idea of a DNS alias added which would tell the DR (secondary) server to answer requests for either system.

Two things:
1. Would it be necessary to create a second subsystem for PD, or would it be able to run on 6013 without conflict when the primary server is up?
2. If OL, SY, and DD are being mirrored, can the DV and PY environments on the second server use the copies on the second server so they don’t have to work across the WAN for that information?

Any and all opinions are welcome.

Thanks!

E1 8.11, iSeries (both servers), Tools Release 8.95, WebSphere 5.x
 
We have an exact set-up as what you have described.
We have accomplished this by creating a Lpar for the DR system on the DR machine. On the other Lpar we run the non production environments which have their own Enterprise server and deployment server.

Let me know if you have any specific questions.
 
Back
Top