Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
jrokita

New Member
Registered:
Posts: 6
Reply with quote  #1 

Does anyone use two engines for reasons other than to handle load?

We are considering using two engines to allow a larger maintenance window.
The thought is that we would be able to take one engine down to apply changes and patches.
My understanding is that we would then need to support two Lists and keep them synchronized. I'm interested in learning what the trade offs might be. Many thanks for sharing your thoughts on this!

0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #2 
only for failover / Disaster recovery, and then one is turned off at all times.

You will probably not get much advantage in the maintenance, as the upgraded engine will not work with the existing database until it has been upgraded too.

If you have a cloned server for managing failures as we often do at customer sites, you can upgrade the offline one and then upgrade the database, then upgrade the other. If you have a spare copy of the database, you can also test the upgrade worked.

We used to have an identical copy of each server. If a server failed (which often happens because of an unthinking 'windows update' policy), we could fire up the other server, get that working, and then diagnose the problem on the original server. That was a huge benefit, but even in these days of virtual machines, few customers want to invest in the additional 'stand-by' server (even though we have been reliably informed additional software licenses are not required).

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
jrokita

New Member
Registered:
Posts: 6
Reply with quote  #3 
Thank you, Jerome!  I think we'll probably use just one Engine. Best Regards, Jane


Quote:
Originally Posted by Jerome
only for failover / Disaster recovery, and then one is turned off at all times.

You will probably not get much advantage in the maintenance, as the upgraded engine will not work with the existing database until it has been upgraded too.

If you have a cloned server for managing failures as we often do at customer sites, you can upgrade the offline one and then upgrade the database, then upgrade the other. If you have a spare copy of the database, you can also test the upgrade worked.

We used to have an identical copy of each server. If a server failed (which often happens because of an unthinking 'windows update' policy), we could fire up the other server, get that working, and then diagnose the problem on the original server. That was a huge benefit, but even in these days of virtual machines, few customers want to invest in the additional 'stand-by' server (even though we have been reliably informed additional software licenses are not required).
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!