We have installed ERP 2005 SR2 on a HA cluster environment (MSCS) on Windows 2003 with MSSQL 2005. The CI is installed locally on node A and the DI is installed locally on node B. The database is setup to run on node B as well.
We figured that both the CI and the DI should be running at the same time, but this seems to cause some issues with the processing of background jobs and RFC communication to one external system. I could not find anything about this in the installation guide for ERP 2005.
When we stopped the DI on node B, this problem disappeared.
<b>Update:</b> We have 4 DI's (application servers) installed outside the cluster, so the DI in question is the DI which is installed on node B.
<b>Can anyone confirm if the CI and DI is intended to run simultaneously, or if the DI should be brought online ONLY when node A (the CI) fails?</b>
PS: useful help will be rewarded.
Message was edited by:
My understanding is that CI doesn't need to care because CI has nothing to do
with DI, because CI is not dependent of DI, but DI is dependent of CI.
If CI failed, DI will be affected. If DI fails, CI will not be affected
unless DI has critical services like updates.
My guess is they are ok to run simultaneously.